In my case, the 4416S as configured by the PC vendor, used to hang on
bootup, something that was corrected by disabling wide-negotiation in
the Adaptec BIOS. This allowed me to boot without kernel panics and
caused the 4416S to come up normally, most of the time.
The main problem has been getting past that stage. Both the playing of
audio-CDs and the burning of CDs has consistently failed.
On Mon, 21 Jun 1999 [EMAIL PROTECTED] wrote:
> "Erich J. Ritzmann" wrote:
>
> > [5]/var/log/messages contains repeated instances of:
> > Jun 16 12:58:36 bach kernel: sr0: CDROM (ioctl) error, command:
> > UNKNOWN(0x42) 02 40 01 00 00 00 00 10 00
> > Jun 16 12:58:36 bach kernel: extra data not valid Current error sr00:00:
> > sense key Hardware Error
> > Jun 16 12:58:36 bach kernel: Additional sense indicates Track following
> > error
> > Jun 16 12:58:43 bach kernel: sr0: CDROM (ioctl) error, command:
> > UNKNOWN(0x42) 02 40 01 00 00 00 00 10 00
> > Jun 16 12:58:43 bach kernel: extra data not valid Current error sr00:00:
> > sense key Hardware Error
> > Jun 16 12:58:43 bach kernel: Additional sense indicates Track following
> > error
>
> This indicates a hardware problem in the CD device itself.
I'm getting the same error on TWO different 4416S devices. I complained
to the vendor, and all I got was the old "it works with Windoze98; I
wish I could help you in some way..." spiel.
> > [6]recreating the problem:
> > Simply placing an audio CD into the drive and starting the CDPLAYER
> > software.
>
> Do you get the same problem on more than one CD? If you get this on one audio
> CD then I would claim a defective CD (judging by the above messages). If you
> get this on all CDs then I would guess a mis-mounted CD device.
Every audio CD I've tried.
> > [8.2]/var/log/messages associated with the cdrecord failure:
> > Jun 16 06:44:16 bach modprobe: can't locate module char-major-97
> > Jun 16 06:44:16 bach last message repeated 3 times
> > Jun 16 06:44:16 bach kernel: (scsi0:0:3:0) Performing Domain
> > validation.
> > Jun 16 06:44:16 bach kernel: (scsi0:0:3:0) Successfully completed
> > Domain validation.
> > Jun 16 06:44:35 bach modprobe: can't locate module char-major-97
> > Jun 16 06:44:35 bach last message repeated 3 times
> > Jun 16 07:19:58 bach kernel: scsi : aborting command due to timeout
> > : pid 129455, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 4d 00
> > a5 00 00 02 00
> > Jun 16 07:19:58 bach kernel: scsi : aborting command due to timeout
> > : pid 129456, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 50 45
> > 87 00 00 02 00
> > Jun 16 07:19:58 bach kernel: SCSI host 0 abort (pid 129456) timed
> > out - resetting
> > Jun 16 07:19:58 bach kernel: SCSI bus is being reset for host 0
> > channel 0.
> > Jun 16 07:19:58 bach kernel: (scsi0:0:3:0) Synchronous at 4.4
> > Mbyte/sec, offset 15.
> > Jun 16 07:19:58 bach kernel: (scsi0:0:0:0) Synchronous at 40.0
> > Mbyte/sec, offset 8.
>
> That looks suspiciously like a cdrecord issue, but I wouldn't know for sure
> since I don't have a CD-R at the moment. However, I would recommend you check
> your CD-R drives mounting screws and use the following suggestions:
<snip>
> Most of the time when I see CD devices with track following issues that aren't
> limited to specific CDs, it is 99% of the time mounting related, and sometimes
> that mounting related problem is a permanent damage issue as well.
Well, this one has four screws attaching a rail, the rail riding somewhat
loosely in the track; opportunties for distortion are minimal, I would
think. Also, changing to the new 4416S did not change the general
behaviour, as one would expect in a distortion related problem.
What's more, in the off chance that the SCSI bus was behaving strangely
due to some stray capacitance in the cables, I replaced both wide, and
narrow cables with very short cables and removed all devices except the
boot drive and the 4416S. This also, without any change in behaviour.
The crazy thing about this is, that I configured a nearly identical
system for a colleague back in February, and it worked fine. That was
with RH5.2, and who knows what firmware. At that time downloaded the
latest boot images + kernel from your FTP site. This time around I am
using RH6.0 but have the same results on both the RH6 kernel and the
latest stable kernel (2.2.10).
> Opinions expressed are my own, but
> they should be everybody's.
Good one!
--
Erich
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
