View previous topic :: View next topic |
Author |
Message |
dsd Developer
Joined: 30 Mar 2003 Posts: 2162 Location: nr London
|
Posted: Mon Mar 15, 2004 8:50 pm Post subject: |
|
|
sorry, i did not see your nvidia problems. however there is plenty of info in this thread about that issue. please read the last few pages.
udev does not handle module loading or unloading. udev is therefore not involved with your oops/call-trace when you reload alsa modules. udev is not involved with shutdown. udev is not a service, so it will generally not output into /var/log/messages (debug info only). udev has created your nodes for your USB stick, you are having a problem mounting them - udev has done its part, the rest is not its responsibility. as nothing apperas in /v/l/messages when you plug your mouse in, the system is not detecting it at all - not udevs fault. udev has created all of the ALSA nodes that it has been instructed to, you have not configured your kernel for OSS emulation - again, not udevs problem.
please keep the thread on-topic. _________________ http://dev.gentoo.org/~dsd |
|
Back to top |
|
|
revertex l33t
Joined: 23 Apr 2003 Posts: 806
|
Posted: Mon Mar 15, 2004 9:43 pm Post subject: lm-sensors and udev |
|
|
Hi! anybody here does have lm-sensors working? |
|
Back to top |
|
|
meowsqueak Veteran
Joined: 26 Aug 2003 Posts: 1549 Location: New Zealand
|
Posted: Mon Mar 15, 2004 10:12 pm Post subject: Re: lm-sensors and udev |
|
|
revertex wrote: | Hi! anybody here does have lm-sensors working? |
I do, but it's not got much to do with udev, does it? |
|
Back to top |
|
|
PrakashP Veteran
Joined: 27 Oct 2003 Posts: 1249 Location: C.C.A.A., Germania
|
Posted: Mon Mar 15, 2004 10:49 pm Post subject: |
|
|
I also have the problem of system hanging at unloading hotlug... then sometimes it helps to ctrl+c, init 3, reboot.
Nevertheless, I went to 2.6.4 vanilla and then I don't have above prob. |
|
Back to top |
|
|
revertex l33t
Joined: 23 Apr 2003 Posts: 806
|
Posted: Tue Mar 16, 2004 5:04 am Post subject: Re: lm-sensors and udev |
|
|
meowsqueak wrote: |
I do, but it's not got much to do with udev, does it? |
I just question about lm-sensors because after migrated to udev i lost my sensors, at least seems possible to get lm-sensors working with udev.
I've got i2c and sensors compiled as modules, the modules are loaded, but no avail, no sensors are found.
I was thinking it's udev fault, but seems my fault!
Just have empty folders, may i need to create something?
Thank you!
--SOLVED--
i forgot to reemerge lmsensors after update my kernel!!!
Last edited by revertex on Tue Mar 16, 2004 2:27 pm; edited 2 times in total |
|
Back to top |
|
|
nepenthe Guru
Joined: 14 Jul 2002 Posts: 317 Location: Sanford, ME
|
Posted: Tue Mar 16, 2004 5:20 am Post subject: |
|
|
dsd wrote: | sorry, i did not see your nvidia problems. however there is plenty of info in this thread about that issue. please read the last few pages.
udev does not handle module loading or unloading. udev is therefore not involved with your oops/call-trace when you reload alsa modules. udev is not involved with shutdown. udev is not a service, so it will generally not output into /var/log/messages (debug info only). udev has created your nodes for your USB stick, you are having a problem mounting them - udev has done its part, the rest is not its responsibility. as nothing apperas in /v/l/messages when you plug your mouse in, the system is not detecting it at all - not udevs fault. udev has created all of the ALSA nodes that it has been instructed to, you have not configured your kernel for OSS emulation - again, not udevs problem.
please keep the thread on-topic. |
He's very right As per noted in the udev FAQ ftp://kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ
Quote: | Q: But udev will not automatically load a driver if a /dev node is opened
when it is not present like devfs will do.
A: If you really require this functionality, then use devfs. It is still
present in the kernel.
Q: But wait, I really want udev to automatically load drivers when they
are not present but the device node is opened. It's the only reason I
like using devfs. Please make udev do this.
A: No. udev is for managing /dev, not loading kernel drivers.
Q: Oh come on, pretty please. It can't be that hard to do.
A: Such a functionality isn't needed on a properly configured system. All
devices present on the system should generate hotplug events, loading
the appropriate driver, and udev will notice and create the
appropriate device node. If you don't want to keep all drivers for your
hardware in memory, then use something else to manage your modules
(scripts, modules.conf, etc.) This is not a task for udev.
Q: But I love that feature of devfs, please?
A: The devfs approach caused a lot of spurious modprobe attempts as
programs probed to see if devices were present or not. Every probe
attempt created a process to run modprobe, almost all of which were
spurious. |
heh =) |
|
Back to top |
|
|
Jefklak l33t
Joined: 26 Oct 2003 Posts: 818 Location: Belgium
|
Posted: Tue Mar 16, 2004 12:25 pm Post subject: |
|
|
PrakashKC wrote: | I also have the problem of system hanging at unloading hotlug... then sometimes it helps to ctrl+c, init 3, reboot. |
Could someone get more info about this, or a fix?
It's very annoying!
Hotplug also generates this in my /var/log/messages:
Code: | no modules for INPUT porudct 0011/0002/0007/0000
no modules for INPUT product 0011/0001/0001/0ab41
no modules for USB product 010/206 (three times) |
? |
|
Back to top |
|
|
snowpatch n00b
Joined: 09 Mar 2003 Posts: 38 Location: Philadelphia
|
Posted: Tue Mar 16, 2004 3:21 pm Post subject: hotplug messages |
|
|
I am getting the same sort of messages on bootup when hotplug starts:
Code: | * Starting USB and PCI hotplugging...
no modules for INPUT product 0011/0002/0007/0000
no modules for INPUT product 0011/0002/0001/0000
no modules for INPUT product 0011/0001/0001/ab41 [ok] |
I did find this thread relating to hotplug:
https://forums.gentoo.org/viewtopic.php?t=148650
I am using hotplug-20040311. |
|
Back to top |
|
|
neenee Veteran
Joined: 20 Jul 2003 Posts: 1786
|
|
Back to top |
|
|
Jefklak l33t
Joined: 26 Oct 2003 Posts: 818 Location: Belgium
|
Posted: Tue Mar 16, 2004 3:51 pm Post subject: |
|
|
neenee wrote: | https://bugs.gentoo.org/show_bug.cgi?id=44543 |
Nice, so it's not only me... I wonder what strange error this is...
I managed to get everything working (USB mouse inclusive) except my flash drive. When I plug it in, what device in /dev should be created by udev then? Should I use sda1? Should I create a rule for it? Thanks! |
|
Back to top |
|
|
nevynxxx Veteran
Joined: 12 Nov 2003 Posts: 1123 Location: Manchester - UK
|
Posted: Tue Mar 16, 2004 3:55 pm Post subject: |
|
|
Mine shows up as sda with sda1 as the read/write partition. _________________ My Public Key
Wanted: Instructor in the art of Bowyery |
|
Back to top |
|
|
Jefklak l33t
Joined: 26 Oct 2003 Posts: 818 Location: Belgium
|
Posted: Tue Mar 16, 2004 3:57 pm Post subject: |
|
|
nevynxxx wrote: | Mine shows up as sda with sda1 as the read/write partition. |
Could you give me a snap of your /etc/fstab please?
That would help a lot!
(sorry for the off-topic thing dsd... I'll shut up now ) |
|
Back to top |
|
|
nevynxxx Veteran
Joined: 12 Nov 2003 Posts: 1123 Location: Manchester - UK
|
Posted: Tue Mar 16, 2004 4:15 pm Post subject: |
|
|
I don't have it in fstab, not on any machine I cabn access, and the fstab entry only maps *from* the /dev/ entry, not *to* it. To dictate what entry it gets in /dev/ you need to modify /etc/udev/udev.rules.
I havn't done this yet as I'm having trouble finding the serial number off the flash drive, it doesn't seem to have one. _________________ My Public Key
Wanted: Instructor in the art of Bowyery |
|
Back to top |
|
|
Jefklak l33t
Joined: 26 Oct 2003 Posts: 818 Location: Belgium
|
Posted: Tue Mar 16, 2004 4:37 pm Post subject: |
|
|
But once you got the serial number and the udev.rules you'll need to make an entry in fstab like this
Code: | /dev/sda1 /mnt/usbstick vfat noauto,user 0 0 |
No?
This is what I have, but it doesn't do anything...
My hotplug still crashes when I want to reboot my system... This is something VERY annoying, I can't manually shut down my computer every time, that's bad for the HDD! Has someone experienced this and found a solution? |
|
Back to top |
|
|
nevynxxx Veteran
Joined: 12 Nov 2003 Posts: 1123 Location: Manchester - UK
|
Posted: Tue Mar 16, 2004 4:47 pm Post subject: |
|
|
Jefklak wrote: | But once you got the serial number and the udev.rules you'll need to make an entry in fstab like this
Code: | /dev/sda1 /mnt/usbstick vfat noauto,user 0 0 |
No?
This is what I have, but it doesn't do anything...
My hotplug still crashes when I want to reboot my system... This is something VERY annoying, I can't manually shut down my computer every time, that's bad for the HDD! Has someone experienced this and found a solution? |
Only if you want to make life easier when you mount the drive. you can just as easily type
Code: |
mount /dev/sda1 /mnt/keyfob
|
which is what I do. It is not udev's job to mount the drive though, that is the job of hotplug or hal not sure which. Udev is *only* to create the device node, the /dev entry. You wont ever need the fstab stuff, it just makes life easier.
this includes mounting drives at boot, it could be done otherwise, using udev, hal, etc and in the furture possibly will be, but at the moment fstab is the default way of doing this. _________________ My Public Key
Wanted: Instructor in the art of Bowyery |
|
Back to top |
|
|
dsd Developer
Joined: 30 Mar 2003 Posts: 2162 Location: nr London
|
Posted: Tue Mar 16, 2004 4:54 pm Post subject: |
|
|
nevynxxx wrote: | I havn't done this yet as I'm having trouble finding the serial number off the flash drive, it doesn't seem to have one. |
correct, not all devices have a serial number. some have serial numbers, but do not export this info over the USB protocol. even so, there are a bazillion other ways of writing udev rules to identify devices (e.g. vendor/product id) - have you read my page? _________________ http://dev.gentoo.org/~dsd |
|
Back to top |
|
|
nevynxxx Veteran
Joined: 12 Nov 2003 Posts: 1123 Location: Manchester - UK
|
Posted: Tue Mar 16, 2004 4:59 pm Post subject: |
|
|
dsd wrote: |
correct, not all devices have a serial number. some have serial numbers, but do not export this info over the USB protocol. even so, there are a bazillion other ways of writing udev rules to identify devices (e.g. vendor/product id) - have you read my page? |
Hmmm I didn't know that devices could choose to not have a s/n, thats a pain because this device only gives a model, thats it, all the info you get, no manufacturer or anything, so if I had 2....grrrr.
Indeed I have read your page, it was very informative and I have pointed others too it too, the trouble is my rule isn't working and I don't have the time to figure out why. I'm trying to pick it up by bus="usb" model="USB DISK Pro" which is what the model shows as in dmesg. But I'm not at the comp to show you the exact line I'm using, the best I could do is the dmesg output. _________________ My Public Key
Wanted: Instructor in the art of Bowyery |
|
Back to top |
|
|
Jefklak l33t
Joined: 26 Oct 2003 Posts: 818 Location: Belgium
|
|
Back to top |
|
|
dsd Developer
Joined: 30 Mar 2003 Posts: 2162 Location: nr London
|
Posted: Tue Mar 16, 2004 9:19 pm Post subject: |
|
|
nevynxxx wrote: | Hmmm I didn't know that devices could choose to not have a s/n, thats a pain because this device only gives a model, thats it, all the info you get, no manufacturer or anything, so if I had 2....grrrr. |
every USB device has a vendor ID and a product ID. these can generally be used to identify a device. they are a 4 digit hex number, e.g. "0x12BC"
as this info is in sysfs, you can write udev rules for this.. show me the udevinfo output if you need me to point out what the product and vendor ID's are, or check the rule you have written.. _________________ http://dev.gentoo.org/~dsd |
|
Back to top |
|
|
OneOfOne Guru
Joined: 28 May 2003 Posts: 368
|
Posted: Wed Mar 17, 2004 11:20 am Post subject: |
|
|
Jefklak wrote: | nevynxxx wrote: | Mine shows up as sda with sda1 as the read/write partition. |
Could you give me a snap of your /etc/fstab please?
That would help a lot!
(sorry for the off-topic thing dsd... I'll shut up now ) |
with this version of hotplug modem_run would go zombie (or actually D) when it tries to upload the firmware on my usb modem (Speedtouch 330).
peace |
|
Back to top |
|
|
nevynxxx Veteran
Joined: 12 Nov 2003 Posts: 1123 Location: Manchester - UK
|
Posted: Wed Mar 17, 2004 11:42 am Post subject: |
|
|
dsd wrote: |
every USB device has a vendor ID and a product ID. these can generally be used to identify a device. they are a 4 digit hex number, e.g. "0x12BC"
as this info is in sysfs, you can write udev rules for this.. show me the udevinfo output if you need me to point out what the product and vendor ID's are, or check the rule you have written.. |
I will do that, but it will ahve to wait until I get home from work in about 7:30 hours. _________________ My Public Key
Wanted: Instructor in the art of Bowyery |
|
Back to top |
|
|
elmie Tux's lil' helper
Joined: 12 Sep 2002 Posts: 124 Location: Brisbane - Australia
|
Posted: Thu Mar 18, 2004 8:19 am Post subject: |
|
|
udev works like a charm for me..
I have nptl (bleeding edge stuff) , udev, alsa, usb and dvd burner and everything is working a Ok.
I totally running a pure udev system, there is no more traces of devfs anymore..
udev is great....
I love it when I can have cool names... never thought mapping devices can be so much fun.
three cheers for the guru who thought of udev.. and the person/s who made the docs and posting here.. woot! |
|
Back to top |
|
|
timmy n00b
Joined: 24 May 2002 Posts: 56 Location: Bath, UK
|
Posted: Thu Mar 18, 2004 11:08 am Post subject: |
|
|
I've applied this patch to my dev-sources kernel tree, however /dev/ppp still doesn't get created automatically for me.
I have ppp_generic compiled as a module, which gets automatically loaded by /etc/init.d/net.ppp0 as long as /dev/ppp already exists.
Does it need to be compiled into the kernel or loaded via modules.autoload to create /dev/ppp? Or is there something I can do to modules.conf (or udev.rules) to get it autoloading properly?
Tim |
|
Back to top |
|
|
gungholady Guru
Joined: 19 Oct 2003 Posts: 392
|
Posted: Thu Mar 18, 2004 4:21 pm Post subject: |
|
|
Following the information I found here and in Decibel's primer, I have changed my system to pure udev. My problem is that everytime I need to reboot, I have to re-emerge nvidia-kernel and nvidia-glx followed by opengl-update nvidia before my openGL screensavers will work. I'm now using the 2.6.4 kernel. There is no devpts in this kernel only devpts attributes. So that option has not been selected. Here is the relevant part of my kernel configuration:
Quote: | # General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set |
and:
Quote: | # Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y |
I have this in /etc/udev/udev.rules
Quote: | # Nvidia devices
KERNEL="nvidia[0-9]", NAME="nvidia/%k", SYMLINK="%k"
KERNEL="nvidiactl", NAME="nvidia/%k", SYMLINK="%k" |
And this in /etc/conf.d/local.start
Quote: | mknod -m 660 /dev/nvidia0 c 195 0
mknod -m 660 /dev/nvidia1 c 195 1
mknod -m 660 /dev/nvidiactl c 195 255 |
Nvidia is in my /etc/modules.autoload/kernel-2.6 file. What am I missing? I shouldn't have to re-emerge the nvidia-kernel and nvidia-glx everytime I have to reboot. |
|
Back to top |
|
|
Evil Dark Archon Guru
Joined: 21 Dec 2002 Posts: 562 Location: Santa Rosa, CA
|
Posted: Thu Mar 18, 2004 5:54 pm Post subject: |
|
|
what version of nvidia-kernel/glx are you using? _________________ This post has been over explained for newb-informing purposes.
Registered Linux user 347334
Abit AV8-3rd eye, AMD Athlon64 3500+ 90nm, ATI Radeon x850 pro |
|
Back to top |
|
|
|