Hi all

I'm having some udev problems on slackware-current (udev-062, kernel 2.6.12.3).

The udev daemon udevd seems to be not running... I don't know if this is normal or not. When i plug in usb devices hotplug recognises them correctly but udev doesn't do anything (such as creating the devices). I assume because it is not running.

Strangely enough /etc/rc.d/rc.udev does not seem to start udevd, it only runs udevstart.

When i manually run udevstart after plugging something in, it works fine. (so the udev rules are fine)

When i manually start udevd (simply udevd&) a lot of stuff breaks including my virtual consoles i think (all terminal emulators including Konsole won't work anymore).

Any help greatly appreciated (trying to get my Palm sync to work, it already works with the manual udevstart execution after hitting the hotsync button).

PS: Anyone know of a way to get KPilot or some equivalent app to store the downloaded data encrypted? I keep my passwords on my Palm and there's little point in having an encrypted KWallet when they're in clear-text on the disk too.

what does dmesg say?

To what exactly?

If, for example, I insert my external usb harddisk:

usb 1-2: new high speed USB device using ehci_hcd and address 2
ub(1.2): GetMaxLUN returned 0, using 1 LUNs
uba: uba1

and that's it. The device /dev/uba is never created. (unless i manually run udevstart again)

udev doesn't seem to make any noise in /var/log/messages during boot (a grep udev came out empty).

An external usb HDD would usually show up as /dev/sd*

You might have forgotten to compile the right option with your kernel.

device drivers -> USB support -> Freecom USB/ATAPI Bridge support

and

device drivers -> USB support -> SanDisk SDDR-09 (and other SmartMedia) support

While it is true that I don't have any explanation for the change of usb storage device names (from sd* to ub*), some time ago, it still works fine and so it's not a problem. The problem is the devices not being created automatically on plug-in.

It may already be useful if someone using a correctly working Slackware with udev could tell me if udevd is running, and what file starts it at boot-up (rc.udev?) and any config changes they had to make. (or working udev.rules file)

isn't this your prob. ?

http://www.linuxquestions.org/questi...hreadid=343394

egag

I didn't have any specific alsa problems, but tried going back to udev-50 (the one from 10.1) and.. it worked!

udevd is running after boot and all devices are created automatically.

/me adds exclude rule for udev to swaret.conf

Still wonder what the problem with the new version is though.

i guess if the latest udev gives prob.'s with alsa, it's no suprise that other prob.'s might come out.
and if you wonder what's the prob exactly, don't give it to much time.
they'll probably change udev again before you find a workaround.
( in fact the newest is udev-063 )

egag

Look in your kernel config file and see if you see this:

# Block devices
#
CONFIG_BLK_DEV_UB=y

There'll be several other CONFIG_whatever's under #Block devices but according to what you've said so far I'd be willing to bet that CONFIG_BLK_DEV_UB is set to y or m. I'm not sure about the 2.6.12 kernel series but in the 2.6.11 series the help file for UB says that if you enable it you will cripple usb-storage. Having UB set to y or m is why your USB storage devices are being assigned ub* instead of sd*. You may want to look at the help file for UB and see if this problem still exists.

Here is the help file from my 2.6.11.5 kernel config:
Later,
MMYoung