"Keith" == Keith O'Connell <[EMAIL PROTECTED]> writes:
Keith> know that I need 2.4.x for my sound to work. I then
Keith> installed kernel-image 2.4.16-k7 to the system and
Keith> everything including the sound works fine, and has done for
Keith> about 10 days.
Keith> Today I went to backup some data to CD and my CD writer was
Keith> not recognised. Infact my scsi sub-system was not
Keith> recognised. I played around for a while but could not get
Keith> it to work. Eventually, as it had worked under potato, I
Keith> rebooted into 2.2.20 and it worked fine.
Keith> Now, I am not completly new, but not far from it. For
Keith> people like me, and newer ones the fact that the
Keith> instalation kernel (2.2.20) when replaced by a distribution
Keith> kernel image from the same source (2.4.18) would be
Keith> expected to run the same hardware, and it doesnt in this
Keith> case. A truly new person would have just said, "I didn't
Keith> get this trouble from Windows!"
Well, a truly new person can't go from Windows 95 to Windows 2000 with
a single apt-get command either! That's not really a fair
comparison. There's a reason going from Potato to Woody with 'apt-get
upate && apt-get -f dist-upgrade" does not upgrade your kernel.
I have not owned a SCSI Linux system in 5 years so I'm handicapped
here anyway, but you need to provide us with *much* more
information. If you collected the kind of information most readers
want, I'm guessing you'd likely end up solving your problem by
yourself anyway :-)
Do you have a real SCSI device? Or are you using IDE SCSI emulation?
If you do have a real SCSI device, what is the SCSI controller? (Look
in dmesg output under 2.2.20 for this vital bit of information).
Okay, so you know your SCSI controller. I'd bet that driver is built
as a module in 2.4.16 (my 2.4.18 kernel is like that). Look in
/lib/modules/2.4.16-k7/kernel/drivers/scsi/ for a matching module
file. Do a 'modprobe driver' (less the .o) and see if things work. If
it does, add that module name to /etc/modules so it works
automagically the next time you boot.
If this is the wrong track I'm leading you down, at least tell us more
about your machine and what exactly is happening. I really don't want
to be patronizing (honestly), but saying that "you played around for a
little while but could not get it to work" makes is very hard for
people to help you out.
Apologies if I'm way off, but hey, I've got next to nothing to work
with!
Cheers!
Shyamal
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
