vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| In article <bg06q0$jtt$1@news.x-echo.com>, pasthe wrote: > I want to add the following informations with dates according to the > syslog and messages files in /var/log. A detail : my ZIP drive 100 Mo I didn't / won't try to read it all, but I think I found some of your confusion in what I did read (the text you wrote.) >================ > > As you can see, in despite of the append, no device nammed "sr0" appears > in the messages.Even if there was a symbolic link such as /dev/cdrom -> > /dev/sr0, it was not possible to read a CD in the drive. I tried severa > l reboots : no sr0 as emulated SCSI device. The 'append="hdc=ide-scsi"' does NOT load SCSI drivers. "modprobe ide-scsi" does that. The append only tells the kernel, "Hey kernel, please don't let your mean old ide-cdrom driver grab my precious CD-RW drive, because I would like to use it as a burner." I haven't tried this yet, but I believe that if ide-cdrom is not built into the kernel ("M" or "N"), the append line is unnecessary. (Can anyone confirm or refute that?) The kernel message for sr0 in a modular kernel comes when the SCSI bus (virtual SCSI in the case of ide-scsi) is scanned. If kmod is enabled (which it is in Slackware kernels) it sees all the devices on the bus and loads their drivers. > After installation of the kernel-sources, I could get the following mess > ages in the syslog file : > >================ messages in "syslog" file [snip] > If all these details can help you now for understanding ..... It does not. > And it is not necessary to answer .... No, but I'm going to try to help YOU understand. Something else DID happen. You can prove this to yourself by "removepkg kernel-source" and rebooting. If no sr0 in dmesg, try "modprobe ide-scsi" and check again. It IS possible (conceivable anyway) that something related to the kernel-source package prevented / enabled the loading of your ide-scsi module. But are you sure you didn't edit /etc/rc.d/rc.modules or /etc/modules.conf inbetween these attempts? That seems a more likely explanation. Armed with better understanding, you can figure this out, if it really matters to you. -- /dev/rob0 - preferred_email=i$((28*28+28))@softhome.net or put "not-spam" or "/dev/rob0" in Subject header to reply |