LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Kernel not loading udev at boot (https://www.linuxquestions.org/questions/slackware-14/kernel-not-loading-udev-at-boot-897273/)

ADX 08-14-2011 02:45 PM

Kernel not loading udev at boot
 
I've been tinkering around with kernels lately, and the last two I've built (v3 and v3.0.1) aren't loading udev (dhcpd doesn't initialize) at boot.

syslog:

Code:

Aug 14 14:08:13 - udevd[1762]: bind failed: Address already in use
Aug 14 14:08:13 - udevd[1762]: error binding control socket, seems udevd is already running
Aug 14 14:08:13 - kernel: [    0.315054] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Aug 14 14:08:13 - kernel: [    0.315254] DLM (built Apr  9 2011 22:44:24) installed
Aug 14 14:08:13 - kernel: [    0.320793] OCFS2 User DLM kernel interface loaded
Aug 14 14:08:13 - kernel: [    0.321524] GFS2 (built Apr  9 2011 22:45:04) installed
Aug 14 14:08:13 - kernel: [    0.329426] Console: switching to colour frame buffer device 128x48
Aug 14 14:08:13 - kernel: [    3.384437] Compaq SMART2 Driver (v 2.6.0)
Aug 14 14:08:13 - kernel: [    3.386198] scsi: <fdomain> Detection failed (no card)
Aug 14 14:08:13 - kernel: [    3.386553] Emulex LightPulse Fibre Channel SCSI driver 8.3.18
Aug 14 14:08:13 - kernel: [    3.386621] Copyright(c) 2004-2009 Emulex.  All rights reserved.
Aug 14 14:08:13 - kernel: [    3.403346] GDT-HA: Storage RAID Controller Driver. Version: 3.05
Aug 14 14:08:13 - kernel: [    3.405578] 3ware Storage Controller device driver for Linux v1.26.02.003.
Aug 14 14:08:13 - kernel: [    3.407808] 3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
Aug 14 14:08:13 - kernel: [    4.901927] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Aug 14 14:08:13 - kernel: [    6.678686] synth name on entry is: (null)
Aug 14 14:08:13 - kernel: [    6.689476] registered taskstats version 1
Aug 14 14:08:13 - kernel: [    6.773430] EXT3-fs (sda3): error: couldn't mount because of unsupported optional features (240)
Aug 14 14:08:13 - kernel: [    6.775475] EXT2-fs (sda3): error: couldn't mount because of unsupported optional features (240)
Aug 14 14:08:13 - kernel: [    6.793145] VFS: Mounted root (ext4 filesystem) readonly on device 8:3.
Aug 14 14:08:13 - kernel: [    8.897154] asus_laptop: Error calling BSTS
Aug 14 14:08:13 - kernel: [    9.279620] sdhci-pci 0000:09:01.1: Will use DMA mode even though HW doesn't fully claim to support it.
Aug 14 14:08:13 - kernel: [  11.268296] nvidia: module license 'NVIDIA' taints kernel.
Aug 14 14:08:13 - kernel: [  11.271397] Disabling lock debugging due to kernel taint
Aug 14 14:08:13 - kernel: [  11.988283] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  280.13  Wed Jul 27 16:53:56 PDT 2011
Aug 14 14:08:31 - console-kit-daemon[1959]: WARNING: Failed to acquire org.freedesktop.ConsoleKit
Aug 14 14:08:31 - console-kit-daemon[1959]: WARNING: Could not acquire name; bailing out



Here is the procedure I followed:

I used the current kernel (2.6.37.6) config.gz to do "make oldconfig" and then tweaked it using "make xconfig". I compiled bzImage and the modules, followed by "make modules_install".

I copied the bzImage, .config, and System.map into /boot. The aforementioned are symlinked there as well.

Code:

[root@x:/boot]# file System.map && file config && file vmlinuz
System.map: symbolic link to `System.map-custom-3.0.1'
config: symbolic link to `config-custom-3.0.1'
vmlinuz: symbolic link to `vmlinuz-custom-3.0.1'

Code:

[root@x:/usr/src]# file linux
linux: symbolic link to `linux-3.0.1/'

This next step, I think, is the part that is causing problems.

I removed the /etc/rc.d/rc.modules symlink from rc.modules-2.6.37.6. I then copied the rc.modules-2.6.37.6 ---> rc.modules-3.0.1 and created a new symlink to it.

Code:

[root@x:/var/log]# file /etc/rc.d/rc.modules
/etc/rc.d/rc.modules: symbolic link to `rc.modules-3.0.1'

Any ideas?

Richard Cranium 08-15-2011 07:47 AM

Did you check the process list to see if udev was really running or not?

ADX 08-15-2011 03:27 PM

Quote:

Originally Posted by Richard Cranium (Post 4443422)
Did you check the process list to see if udev was really running or not?

Code:

root      1501  0.0  0.0  17716  1492 ?        S<s  15:11  0:00 /sbin/udevd --daemon
root      2309  0.0  0.0  17712  1408 ?        S<  15:12  0:00 /sbin/udevd --daemon
root      2310  0.0  0.0  17712  1408 ?        S<  15:12  0:00 /sbin/udevd --daemon

This keeps showing up in the syslog too:

Code:

Aug 15 15:16:29 GPC udevd[1766]: bind failed: Address already in use
Aug 15 15:16:29 GPC udevd[1766]: error binding control socket, seems udevd is already running

I guess the daemon does initialize, but some things are being skipped (dhcpd, wireless/Ethernet cards, usb)..


All times are GMT -5. The time now is 09:46 PM.