You are not logged in.

#1 2012-01-06 23:50:03

usagi
Member
Registered: 2011-11-21
Posts: 54

[solved] udev fails to register anything on boot after kmod

Hello,

After yesterday's kmod upgrade, i can't seem to get udev to modprobe anything on boot. Udev throws about two dozen errors during boot complaining about "no such file or directory", but /sbin/modprobe exists, and seems to work fine with udev after the boot process is complete. i know this because i can remove and replace the USB cables to the computer, and udev picks up and modprobes the correct drivers. The same devices (keyboard, mouse) fail to load during boot.

I would throw in the errors, but dmesg doesn't seem to catch them. Most are of the form "udev: error: /sbin/modprobe "/sbin/modprobe [some "dash arguments"]  usb:*huge alphanumeric string*" This is from memory, so excuse any probable inaccuracies.

Any ideas or starting points?

Thanks,
--Aaron

Last edited by usagi (2012-01-07 00:58:47)

Offline

#2 2012-01-07 00:15:32

karol
Archivist
Registered: 2009-05-06
Posts: 25,426

Re: [solved] udev fails to register anything on boot after kmod

This has been discussed on the ML, which I'm sure you've read.
http://mailman.archlinux.org/pipermail/ … 22324.html
http://mailman.archlinux.org/pipermail/ … 23874.html

Last edited by karol (2012-01-07 00:17:04)

Offline

#3 2012-01-07 00:17:22

usagi
Member
Registered: 2011-11-21
Posts: 54

Re: [solved] udev fails to register anything on boot after kmod

To be quite honest, I didn't even know there was a mailing list. I'll post back up when I'm better versed.

Offline

#4 2012-01-07 00:18:36

karol
Archivist
Registered: 2009-05-06
Posts: 25,426

Re: [solved] udev fails to register anything on boot after kmod

usagi wrote:

To be quite honest, I didn't even know there was a mailing list. I'll post back up when I'm better versed.

Why are you using [testing] w/o being subscribed to the ML?
https://wiki.archlinux.org/index.php/Te … testing.5D

Offline

#5 2012-01-07 00:27:43

usagi
Member
Registered: 2011-11-21
Posts: 54

Re: [solved] udev fails to register anything on boot after kmod

karol wrote:
usagi wrote:

To be quite honest, I didn't even know there was a mailing list. I'll post back up when I'm better versed.

Why are you using [testing] w/o being subscribed to the ML?
https://wiki.archlinux.org/index.php/Te … testing.5D

Because i don't read directions, apparently. Subscribing now. thanks for the tip.

Found my issue too. According to the mailing list, the /sbin/modprobe is a symlink to /usr/bin (which, imho, is an asinine thing to do. what's the point of /bin and /sbin if you're just symlinking to /usr?). Since i have a seperate /usr partition (actually, a seperate /usr DRIVE), it's not mounted on boot.

So, now my query becomes: is there a way to mount an arbitrary drive before boot commences?

Last edited by usagi (2012-01-07 00:29:19)

Offline

#6 2012-01-07 00:51:09

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,092
Website

Re: [solved] udev fails to register anything on boot after kmod

usagi wrote:

So, now my query becomes: is there a way to mount an arbitrary drive before boot commences?

Expect support for this (mounting /usr) in mkinitcpio "soon". If you want to help speed along the process, here's an untested patch. Zero assumptions are made about the partition -- you will need to include any modules necessary for creating the partition in MODULES= (if it differs at all from your / partition).

Last edited by falconindy (2012-01-07 00:51:29)

Offline

#7 2012-01-07 00:57:59

usagi
Member
Registered: 2011-11-21
Posts: 54

Re: [solved] udev fails to register anything on boot after kmod

many thanks falconindy. marking as solved, as the original issue is, sort of. anyhow, just as an academic measure, is there any way to do this with a mkinitcpio hook or similar?

Offline

#8 2012-01-07 01:11:06

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 12,690

Re: [solved] udev fails to register anything on boot after kmod

And, as most newbies aren't using testing, this post is being moved to a more appropriate sub-forum.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Online

#9 2012-01-07 03:33:24

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,092
Website

Re: [solved] udev fails to register anything on boot after kmod

falconindy wrote:
usagi wrote:

So, now my query becomes: is there a way to mount an arbitrary drive before boot commences?

Expect support for this (mounting /usr) in mkinitcpio "soon". If you want to help speed along the process, here's an untested patch. Zero assumptions are made about the partition -- you will need to include any modules necessary for creating the partition in MODULES= (if it differs at all from your / partition).

I should point out that  it's actually a little more involved than just "apply the patch".

1) make sure you have util-linux>=2.20.1-2
2) add 'shutdown' and 'fsck' to your initramfs hooks in /etc/mkinitcpio.conf. shutdown only needs to be somewhere after base. 'fsck' should go after autodetect if your /usr is the same FS as root, before autodetect if its different.
3) apply said patch.
4) in /etc/fstab, set passno to 0 for your /usr partition (it'll be checked in the initramfs)
5) regenerate your initramfs.

Thanks to usagi for testing this and providing valuable feedback.

Last edited by falconindy (2012-01-07 13:43:38)

Offline

#10 2012-01-12 15:58:15

horrovac
Member
Registered: 2012-01-12
Posts: 5

Re: [solved] udev fails to register anything on boot after kmod

Quick and dirty solution to this issue:

copy /usr/bin/kmod to /sbin/modprobe
copy /usr/lib/libz.so.1 to /lib/libz.so.1 (required by kmod)

It's of course not a solution at all, rather a hack, but it works for me, for now. When kmod or libz are updated one would need to copy them again manually, and once the /usr mounting issue is fixed, restore the old config (remove /lib/libz.so.1 and make /sbin/modprobe a symlink to /usr/bin/kmod again).

I have to agree with the previous comment that there isn't lot of point installing kmod in /usr and then symlinking it from /sbin, there is a reason why there is a /bin and /sbin to begin with. I have no knowledge about the rationale of doing it this way, but it is a rather bad idea and asking for trouble (q.e.d.). Putting it in /sbin, statically linked, would be better, if at all possible.

Offline

#11 2012-01-13 05:00:09

rolis
Member
Registered: 2012-01-11
Posts: 1

Re: [solved] udev fails to register anything on boot after kmod

falconindy wrote:
falconindy wrote:
usagi wrote:

So, now my query becomes: is there a way to mount an arbitrary drive before boot commences?

Expect support for this (mounting /usr) in mkinitcpio "soon". If you want to help speed along the process, here's an untested patch. Zero assumptions are made about the partition -- you will need to include any modules necessary for creating the partition in MODULES= (if it differs at all from your / partition).

I should point out that  it's actually a little more involved than just "apply the patch".

1) make sure you have util-linux>=2.20.1-2
2) add 'shutdown' and 'fsck' to your initramfs hooks in /etc/mkinitcpio.conf. shutdown only needs to be somewhere after base. 'fsck' should go after autodetect if your /usr is the same FS as root, before autodetect if its different.
3) apply said patch.
4) in /etc/fstab, set passno to 0 for your /usr partition (it'll be checked in the initramfs)
5) regenerate your initramfs.

Thanks to usagi for testing this and providing valuable feedback.

the patch worked for me. my /usr is ext4 on lvm.

Offline

Board footer

Powered by FluxBB