Karsten: Thanks for your note. In the meantime I did try kernel 2.2.17 which had the uniform CD rom driver 3.31 instead of 2.56 in 2.2.15. WIth this I had not problem. So I presume it was the CDrom driver which was at fault.
Sebastian Canagaratna Department of Chemistry Ohio Northern University Ada, OH 45810 > Not sure specifically if there's a CD error in 2.2.14, though I *did* > run into a smbfs conflict. > > However, kernels in the range 2.2.13(?) - 2.2.16 have known root-level > exploits. 2.2.17 is strongly recommended. The other alternative may be > to fall back to 2.0.38 or thereabouts, which may lack some functionality > but is a solid and dependable kernel AFAIK (if anyone knows differently, > speak now). > > -- > Karsten M. Self <kmself@ix.netcom.com> http://www.netcom.com/~kmself > Evangelist, Opensales, Inc. http://www.opensales.org > What part of "Gestalt" don't you understand? Debian GNU/Linux rocks! > http://gestalt-system.sourceforge.net/ K5: http://www.kuro5hin.org > GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0 > On Thu, Sep 14, 2000 at 09:13:32AM -0400, Sebastian Canagaratna ([EMAIL > PROTECTED]) wrote: > > Hi: > > > > I was using slink with 2.2.1 with scsi hard disk and a scsi cd > > (SONY-CDU-76S) and everything was fine. I recently upgraded > > to potato and left the kernel at 2.2.1 and everything was OK. > > I thenk installed 2.2.15 which was on the CD and now the SCSI > > hard disk is recognized and so is the CD on boot up, but when I > > try to read a CD it times out after probe failure. Is this a known > > problem with 2.2.15 or am I doing something wrong. Even ppp > > appears to fail. I did a make modules and modules_install. The > > SCSI part is in the kernel, not as part of a module. Would > > it help to install 2.2.12 or 2.2.17? >
