Failed to detect SCSI CD-R

finite · 01-27-2005, 05:02 PM

Okay, straight to business. Slackware 10 based system running kernel 2.6.10. Having insane difficulties detecting my SCSI CD burner. I've managed to init the host adapter just fine, it uses the atp870u driver. Here's the output during boot:

Code:

ACPI: PCI interrupt 0000:00:07.0[A] -> GSI 10 (level, low) -> IRQ 10
   ACARD AEC-671X PCI Ultra/W SCSI-3 Host Adapter: 0 IO:e800, IRQ:10.
         ID:  7  Host Adapter
scsi0 : ACARD AEC-6710/6712/67160 PCI Ultra/W/LVD SCSI-3 Adapter Driver V2.6+ac

However it claims there are no devices attached.

Code:

cat /proc/scsi/scsi 
Attached devices:

And cdrecord is of no help.

Code:

cdrecord -scanbus
Cdrecord 2.00.3 (i686-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'.

I even stumbled upon ye olde scsitools package, and tried that.

Code:

rescan-scsi-bus 
Host adapter 0 (atp870u) found.
0 new device(s) found.               
0 device(s) removed.

It's a damn phantom device.

The device works fine in Windows 2000, so it's not a hardware issue. I believe I had it working at some stage with a previous distro, possibly 2.4 kernel. I hope the atp870u code isn't simply broken in 2.6, as I finally configured all my other devices to work on the latest stable kernel, I can't see myself going back now.

Anyhow, thanks in advance for any help, any suggestions at all would be great, this has been a real chore to try to fix.

michaelk · 01-27-2005, 05:12 PM

Are the SCSI drivers compiled in the kernel or modules?
Is the scsi_mod module loading?

finite · 01-28-2005, 05:22 AM

I've tried compiling atp870u both built-in and as a module, doesn't seem to matter. I don't seem to be building scsi_mod for some reason, what's the kernel option for that?

EDIT: Nevermind, I realised its the base option. It was compiled into the kernel, I'll try as module and recompile/install.

EDIT: Okay, doesn't seem to have made a difference. Same output from the apps I executed in the first post, but heres the relevant part of lsmod should that be of use:

Code:

atp870u                21536  0 
st                     34844  0 
sr_mod                 13796  0 
sg                     29280  0 
sd_mod                 12240  0 
scsi_mod               72864  5 atp870u,st,sr_mod,sg,sd_mod

finite · 02-17-2005, 03:48 AM

I hope you guys don't burn me for bumping, but I still haven't had any luck at all with this. I don't suppose anyone who reads this post uses a CD writer on an Acard SCSI adapter. Or maybe someone has managed to get my burner model (MATSHITA CW-7502) to work using a different adapter?

finite · 12-04-2006, 11:07 PM

Just in case anyone has found this via forum search/google... I finally managed to fix this problem today. All I had to do was manually switch the SCSI ID on my CDROM to 4 (via the jumpers at the back of the drive). It was previously unset (so, auto-assigned ID), which I guess the windows drivers could handle, but not the linux ones.