Am Montag, 31. Januar 2005 00:07 schrieb Pollywog: > This is what I had tried: > > #mkdir --mode=755 /dev/thinkpad > #mknod --mode=664 /dev/thinkpad/thinkpad c 10 170 > #chown root:thinkpad /dev/thinkpad/thinkpad > > This worked but the device would disappear after a reboot.
Hello, its probably not recommended but I solved similar problems with udev by adding some stuff to the non existant file /etc/udev/links.conf For example for support of my AVM Fritzcard via ISDN 4 Linux: # ISDN M isdn0 c 45 0 M isdnctrl0 c 45 64 L isdnctrl /dev/isdnctrl0 M ippp0 c 45 128 M isdn1 c 45 1 M isdnctrl1 c 45 65 M ippp1 c 45 129 M isdn2 c 45 2 M isdnctrl2 c 45 66 M ippp2 c 45 130 M isdn3 c 45 3 M isdnctrl3 c 45 67 M ippp3 c 45 131 M isdn4 c 45 4 M isdnctrl4 c 45 68 M ippp4 c 45 132 M isdn5 c 45 5 M isdnctrl5 c 45 69 M ippp5 c 45 133 M isdn6 c 45 6 M isdnctrl6 c 45 70 M ippp6 c 45 134 M isdn7 c 45 7 M isdnctrl7 c 45 71 M ippp7 c 45 135 M isdninfo c 45 255 > > Alternatively you can add 'thinkpad' to /etc/modules. > > I had not tried this, I had added nvram to that file and solved that > problem. I will try adding thinkpad to that file also. If that works okay. I tried that with "hisax" and it didn't work. Also udev didn't remember manually added device nodes. So I used the approach I described above and this works fairly well. At work I used this approach to make udev VMware aware. Still the cleaner approach would be some nice udev rules I guess. But I already invested lots of time into fixing those issues with udev. So I will use that work-around for now. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
