Arch Linux

verve

Member

Registered: 2008-09-08

Posts: 30

How do I tell sd_mod to stop probing my CD drive?

I guess I have to tweak modprobe.conf but I don't know the parameters.

It's weird because sr_mod is supposed to handle scsi cd drives, not sd_mod.

Oh and it'd be even better if I could assign the cd drive as an ata, since it's not a writer so it doesn't need scsi_mod/sr_mod/etc.

e:do I have to add dependancies in rc.conf if I disable autoloading? Or does it behave like plain old modprobe; automatically loading deps prior to the main modules?

Last edited by verve (2008-09-15 21:45:06)

Onwards

Member

From: Pakistan

Registered: 2007-04-18

Posts: 108

Re: How do I tell sd_mod to stop probing my CD drive?

How do u know sr_mod isn't handling ur cdrom ? Blacklist sr_mod and see if u can still use ur cdrom.

verve

Member

Registered: 2008-09-08

Posts: 30

Re: How do I tell sd_mod to stop probing my CD drive?

Yes, sr_mod handles my cd drive. e: I know because it doesn't work without it(specifing an equivalent ide module would remedy this, but it won't affect my problem with sd_mod).

Here's the whole situation: I'm trying to slim down my initramfs so I only include stuff I can't boot without, sd_mod being one of them. My modules are: dock, scsi_mod, libata, sd_mod, and jfs. Hooks: base, udev (for UUID), and other stuff that doesn't really matter like keymap and usbinput.

This gets me booted fine and dandy, but the dmesg log shows sd_mod making calls to my ide cd drive and assigning parameters such as changing IDE transfer rate to UDMA 50, etc. I want to stop this! I want my modules in initramfs to only handle stuff for booting.

I assume someone else has been in a similar situation where they had to tell particular modules to handle specific drives. Say you want the old ide modules to handle a drive -- because it performs better that way or whatever -- but you still want sd_mod to handle another: you gotta tweak modprobe.conf to suit your needs.

e: Oh and I'd like to let it be known how disgusting is udev at automatically loading modules. Before going with the manual module loading route I had to blacklist intel-agp (nvidia is doing it's job... aaand  udev blissfully ignored that my onboard video is disabled via bios. Bizarre), ath5k (udev tries to load both ath5k and ath-pci. why? It should be smart enough to know which modules conflict and which don't) and it also tried to load a heapload of ide & sata modules that went unused because of scsi_mod and derivants.

Last edited by verve (2008-09-16 23:23:40)