SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Distribution: Solaris 10, Solaris Express Community Edition
Posts: 547
Rep:
SCSI HD device problem...
Hi.
I installed a slackware-current box with 3 SCSI devices. I made several partitions and all went fine... until the box rebooted with an USB disk drive plugged in. After the reboot, the USB disk had become the device "sda" and the other devices were "shifted by one".
Any idea or suggestion? Shouldn't there be a "bus priority" between the SCSI bus and the USB bus when assigning devices? I thought about creating some udev rule but I don't sort of... like this solution.
EDIT: I'm using kernel 2.6.17.13
Last edited by crisostomo_enrico; 09-14-2006 at 03:29 PM.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,697
Rep:
Not a slack user but one would think the scsi would come before usb. Here are a few of my thoughts.
1. Make sure bios boot squence puts usb last if usb boot is available.
2. In the kernel I would make scsi and usb as modules if already not.
3. Now as modules load the scsi modules first either in /etc/modprobe.conf or if it is /etc/modules.conf.
4. Maybe load usb modules in a script much later during the boot.
5. Othr thought is build scsi into the kernel and leave usb as modules.
compile your kernel with scsi support in the bzImage, not as moudle, since you are using it to boot are you? compile the all usb devices support as moudules.
sorry Brian, didn't read through your post at first.
Distribution: Solaris 10, Solaris Express Community Edition
Posts: 547
Original Poster
Rep:
Thanks Brian1 and Number22!
Well, I didn't build a new kernel because I could use Pat's kernel in extra/... And I'm not modprobing it in the initrd because I'm now (now...) booting from hda3. And the SCSI adapter module, aic7xxx, is (and I left it) blacklisted in /etc/modprobe.d/blacklist. I load it from /etc/rc.modules-2.6.17.13. The point, probably, is (according to Pat) providing a dynamic /dev and force module probing at the same time. Indeed I was wondering why running rc.udev *before* modprobing modules in rc.modules, which is the real problem I'm having.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,697
Rep:
If using an aic7xxx controller based card then I would build that into the kernel as default. In older 2.4 kernels aic7xxx needed to be built into the kernel if I remember correctly. On my zic7xxx controllers the aic7xxx is built into the kernel. Maybe I may build one as a module and see if the USB takes dominace on my system. How well that is for a rainy day project.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.