The 02.12.31 at 18:12, Ralph De Witt wrote:
Thanks that seemed to clear up the multiple devices, but I think I may still have a small problem . See the 4th line down in my startup log and the errors in the System log. Are these a problem or not.
Start up log:
<6>Linux port (c) 1998 Building Number Three Ltd & Jan "Yenya" Kasprzak. <4>ide-floppy driver 0.99.newide <6>SCSI subsystem driver Revision: 1.00 <3>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
That? No, no problem, just a nuisance. I have that as well. I think it happens when the kernel is starting, and it loads modules ion the initial ram disk. It then needs some module, probably that "scsi_hostadapter", which is not on the ramdisk, and can not be got from /lib/modules either, because the "/" is not mounted yet. So, the boot procedure continues, and when the root filesystem is mounted then it will load that module if it still needs it. I suppose it could be cleared copying that module to the initial ram disk, but I don't think it is necessary, or not in my case, at least O:-)
System log:
Dec 31 17:54:40 linux su: pam_unix2: session started for user root, service su
Dec 31 17:54:44 linux kernel: cdrom: open failed. Dec 31 17:54:44 linux kernel: cdrom: open failed. Dec 31 17:54:44 linux kernel: ide-scsi: hdd: unsupported command in request queue (0)
This is different...
Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 64 Dec 31 17:54:44 linux kernel: ide-scsi: hdd: unsupported command in request queue (0)
Is there a cdrom in the hdd unit? Try a different one, a comercial one containing data (not music); for example, one of the suse cds. I assume hdd is the cdrom or recorder unit, the one you use ide-scsi for. Beats me... -- Cheers, Carlos Robinson