load/unload modules automatically

orschiro · 2010-02-01 21:52:14

Hello guys,

to be able to eject a disk after pressing the eject-button of my cd/dvd drive I have to unload/load the modules manually with the following commands:

rmmod sr_mod
rmmod cdrom
modprobe cdrom lockdoor=0
modprobe sr_mod

After that I can eject it without any problems. I thought I can automatise this by adding options cdrom lockdoor=0 to /etc/modprobe.d/modprobe.conf and finally load the modules in my /etc/rc.conf like the following:

MODULES=([...] "cdrom lockdoor=0" sr_mod)

But it still doesn't work. What's wrong?

Thank you in advance.

DeeCodeUh · 2010-02-02 02:46:46

Wow, that's really an advanced way to do something that should be so simple.
What makes it so you have to do all of that?

brebs · 2010-02-02 05:34:43

Is "cdrom" compiled into your kernel, or a module in /lib/modules/ ?

If it's compiled into your kernel, then you need to specify lockdoor a different way:

In /boot/grub/menu.lst, add this to the kernel line:
cdrom.lockdoor=0

The reason that this is done in a different way is that it confuses the heck out of us. There's no other reason

tomk · 2010-02-02 07:05:49

Don't put the option in the MODULES array - use /etc/modprobe.d/* only.

orschiro · 2010-02-02 08:10:32

Hello guys,

thank you for your answers.

In /boot/grub/menu.lst, add this to the kernel line:
cdrom.lockdoor=0

This seems to be enough to get it working. I checked it. But why is this done via kernel parameter and not with modprobe.d? It's even not necessary to have an entry in modprobe.conf.

brebs · 2010-02-02 17:54:40

orschiro wrote:

why is this done

Linux isn't designed to be user/newbie friendly. That's the reason, in a nutshell

tomk · 2010-02-02 18:47:42

Possible explanation: if you're loading the cdrom module in your initramfs image, that would happen before /etc/modprobe.d/* is available, so the option would not be applied. The fix is to include the modprobe.d files in the FILES section of your mkinitcpio.conf.

orschiro · 2010-02-02 19:07:56

The fix is to include the modprobe.d files in the FILES section of your mkinitcpio.conf.

But that's the strange thing, it is already included.

Misfit138 · 2010-02-02 19:22:00

brebs wrote:

orschiro wrote:
why is this done
Linux isn't designed to be user/newbie friendly. That's the reason, in a nutshell

I see you are going through a phase of discovery. I too fall prey to such revelations of clarity, which often manifest themselves in the most forthright and cynical reality imaginable.

I think I might like being a dreamer better.

tomk · 2010-02-02 21:07:09

orschiro wrote:

The fix is to include the modprobe.d files in the FILES section of your mkinitcpio.conf.
But that's the strange thing, it is already included.

OK... you didn't say anything about your initramfs up to this, hence my suggestion.

Arch Linux

#1 2010-02-01 21:52:14

load/unload modules automatically

#2 2010-02-02 02:46:46

Re: load/unload modules automatically

#3 2010-02-02 05:34:43

Re: load/unload modules automatically

#4 2010-02-02 07:05:49

Re: load/unload modules automatically

#5 2010-02-02 08:10:32

Re: load/unload modules automatically

#6 2010-02-02 17:54:40

Re: load/unload modules automatically

#7 2010-02-02 18:47:42

Re: load/unload modules automatically

#8 2010-02-02 19:07:56

Re: load/unload modules automatically

#9 2010-02-02 19:22:00

Re: load/unload modules automatically

#10 2010-02-02 21:07:09

Re: load/unload modules automatically

Board footer