| View previous topic :: View next topic |
| Author |
Message |
sfy n00b


Joined: 10 Feb 2003 Posts: 12 Location: Gothenburg/Sweden
|
Posted: Wed Feb 19, 2003 11:07 pm Post subject: Problems with scsi emulation |
|
|
I have problems configuring my cd-rw to work with scsi emulation. I have browsed the forum and read most of the suggestions, but I still havn't got it to work. I did as this thread suggests, but with no result, so I thought I stick with the "old" way of doing things and pass hdX=ide-scsi to the kernel. I even compiled scsi-support, scsi-generic and scsi-cdrom into the kernel as someone mentioned it worked that way, but not as a module. When I run cdrecord -scanbus I still get the:
| Code: |
Cdrecord 2.0 (i586-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
|
When I run "modprobe ide-scsi" I get the following in dmesg:
| Code: |
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0, lun 0 Inquiry 00 00 00 ff 00
hdb: irq timeout: status=0xd0 { Busy }
hdb: ATAPI reset complete
hdb: irq timeout: status=0xc0 { Busy }
hdb: ATAPI reset complete
hdb: status error: status=0x08 { DataRequest }
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
hdb: drive not ready for command
scsi : aborting command due to timeout : pid 1, scsi0, channel 0, id 0, lun 0 Inquiry 00 00 00 ff 00
SCSI host 0 abort (pid 1) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
.....
snip (lots of lines)
......
SCSI host 0 abort (pid 1) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
scsi : aborting command due to timeout : pid 1, scsi0, channel 0, id 0, lun 0
scsi : aborting command due to timeout : pid 1, scsi0, channel 0, id 0, lun 0 |
The cd-rw isn't present in /dev/scsi or in /dev/ide/busX/hostX/targetX/cd
I know that it should work, because it worked fine under Mandrake 9.0.
I'm using 2.4.19-r10
| Code: |
Fstab:
/dev/hda1 /boot ext3 noauto,noatime 1 2
/dev/sfyvg/rootlv / reiserfs notail 0 1
/dev/sfyvg/homelv /home reiserfs notail 0 0
/dev/sfyvg/loglv /var/log reiserfs notail 0 0
/dev/hda3 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
proc /proc proc defaults 0 0
|
| Code: |
devfsd.conf
# Autoload the sg module if generic scsi driver compiled as module.
#LOOKUP ^sg$ MODLOAD ACTION sg
# Give the cdrw group write permissions to /dev/sg0
# This is done to have non root user use the burner (scan the scsi bus)
REGISTER ^scsi/host.*/bus.*/target.*/lun.*/generic PERMISSIONS root.cdrw 660
# General note for the following auto creation of symlinks:
#
# If you change the device that the symlink points to,
# you should also remove the symlink before restarting
# devfsd
# Create /dev/cdrom for the first cdrom drive
LOOKUP ^cdrom$ CFUNCTION GLOBAL mksymlink cdroms/cdrom0 cdrom
REGISTER ^cdroms/cdrom0$ CFUNCTION GLOBAL mksymlink $devname cdrom
UNREGISTER ^cdroms/cdrom0$ CFUNCTION GLOBAL unlink cdrom
# Create /dev/cdrw for the first cdrom on the scsi bus
# (change 'sr0' to suite your setup)
LOOKUP ^cdrw$ CFUNCTION GLOBAL mksymlink sr0 cdrw
REGISTER ^sr0$ CFUNCTION GLOBAL mksymlink $devname cdrw
UNREGISTER ^sr0$ CFUNCTION GLOBAL unlink cdrw
|
Does anyone have a suggestion? |
|
| Back to top |
|
 |
Vancouverite Apprentice


Joined: 28 Sep 2002 Posts: 162 Location: Vancouver, Canada
|
Posted: Thu Feb 20, 2003 3:52 am Post subject: |
|
|
This is how I get my CD-RW to work:
I compile everything as modules.
1)SCSI emulation support
2)SCSI support
3)SCSI CD-ROM support
4)SCSI Generic support
In /etc/modules.autoload
sg
ide-scsi
In /etc/conf.d/local.start
cdrecord -scanbus >/dev/null
Kernel option: hdx=ide-scsi
I think you are missing #1 |
|
| Back to top |
|
 |
sfy n00b


Joined: 10 Feb 2003 Posts: 12 Location: Gothenburg/Sweden
|
Posted: Thu Feb 20, 2003 7:19 am Post subject: |
|
|
| No actually I have that one as a module, but that should do, shouldn't it? Will go mad from this subject soon :) |
|
| Back to top |
|
 |
Vancouverite Apprentice


Joined: 28 Sep 2002 Posts: 162 Location: Vancouver, Canada
|
Posted: Thu Feb 20, 2003 8:54 am Post subject: |
|
|
| The only other thing that comes to mind is to enable vendor specific extensions. But I imagine you've already tried this. All CD-RW's I've installed have worked for me doing what I previously posted. Does the kernel detect the drive during boot? Strange that there is nothing under /dev for it. |
|
| Back to top |
|
 |
sfy n00b


Joined: 10 Feb 2003 Posts: 12 Location: Gothenburg/Sweden
|
Posted: Thu Feb 20, 2003 4:55 pm Post subject: |
|
|
| Yes, included vendor spec. to be safe, but that didn't help. I can't see why it says that my cr-rw is busy. It shouldn't have anything to do :) |
|
| Back to top |
|
 |
sfy n00b


Joined: 10 Feb 2003 Posts: 12 Location: Gothenburg/Sweden
|
Posted: Mon Feb 24, 2003 9:18 am Post subject: |
|
|
| Now it works! I don't know how but it does. I tried to install the vanilla sources to see if they would work better with my cd-rw. They didn't so I put my old kernel (gentoo-r10) back again. I didn't change it in any way nor did I make any changes to lilo.conf of anything that should have anything to do with scsi emulation. However, after this it worked...strange... |
|
| Back to top |
|
 |
cchapman Guru


Joined: 16 Jan 2003 Posts: 440 Location: Fremont, NE
|
Posted: Tue Feb 25, 2003 2:52 pm Post subject: |
|
|
| Any idea's if you have a DVD-rom and CD-RW. It sees my burner as scsi but does not work when trying to cdrecord -scanbus pops up error(dont have error, at work right now) |
|
| Back to top |
|
 |
cchapman Guru


Joined: 16 Jan 2003 Posts: 440 Location: Fremont, NE
|
Posted: Tue Feb 25, 2003 2:53 pm Post subject: |
|
|
| Sorry, it doesnt see it as a burner, it sees it as a cdrom. |
|
| Back to top |
|
 |
Vancouverite Apprentice


Joined: 28 Sep 2002 Posts: 162 Location: Vancouver, Canada
|
Posted: Wed Feb 26, 2003 7:04 am Post subject: |
|
|
| Isn't it strange how doing nothing sometimes makes things work? Many months ago I bought a Radeon 7500 and couldn't get it to work on 2 different occasions. It was a bad scene... I was getting a variety of beep codes, my monitor started whining and all I eventually got on the screen was flashing multi coloured happy faces and other weird characters. Finally my old Voodoo3 goes down in flames so I figured I'd give that stupid Radeon another try and it has worked perfectly since installation. |
|
| Back to top |
|
 |
CheshireCat Guru


Joined: 25 Aug 2002 Posts: 572
|
Posted: Tue Mar 25, 2003 3:05 am Post subject: |
|
|
| I have lots of trouble with my CDRW drive, and I'm seeing the same problems. I was using 2.4.19-r10 + an updated grsecurity, then I tried out 2.5.63 for a little bit. It worked fine before, it worked fine (without ide-scsi) under 2.5, but 2.5 gave me lots of crashes. I went back to 2.4.19, and sometimes it will write or mount a disc once, sometimes it won't at all, and I start seeing the same reset and timeout messages in dmesg. In my case, I am still getting the devices in /dev. When the problems start, cdrecord starts saying that the drive is an Adaptec (I have a Yamaha drive). I've upgraded 2.4.20-ck4 + ptrace patch, and I still have these problems. |
|
| Back to top |
|
 |
|