| 1 |
Hi, Alan. |
| 2 |
|
| 3 |
On Sun, Feb 24, 2013 at 06:08:19PM +0200, Alan McKinnon wrote: |
| 4 |
> On 24/02/2013 13:02, Alan Mackenzie wrote: |
| 5 |
> > On Sun, Feb 24, 2013 at 10:44:19AM +0200, Alan McKinnon wrote: |
| 6 |
> >> On 23/02/2013 19:18, Alan Mackenzie wrote: |
| 7 |
> >>> Hi, Gentoo! |
| 8 |
|
| 9 |
> >>> Just built the new kernel 3.7.9 last night, and it's one of these |
| 10 |
> >>> "nothing works" situations. |
| 11 |
|
| 12 |
> > Sorry, I was exaggerating here. I can work normally as long as I don't |
| 13 |
> > try to use a peripheral, such as printer, audio, or scanner. My network |
| 14 |
> > connection is working OK. |
| 15 |
|
| 16 |
> >>> It seems the problems are with the device files, whose ownership is set |
| 17 |
> >>> to "root root" (rather than, e.g., "root audio") and whose permissions |
| 18 |
> >>> are set to crw------- (rather than the expected crw-rw----). |
| 19 |
|
| 20 |
> >>> I'm still running udev-171-r10. This might well make a difference. |
| 21 |
|
| 22 |
> >>> Needless to say, everything works under kernel 3.6.11. It would be nice |
| 23 |
> >>> if there were some mistake in my kernel config. |
| 24 |
|
| 25 |
> >>> Could somebody help me get this fixed, please. |
| 26 |
|
| 27 |
[ .... ] |
| 28 |
|
| 29 |
> I suppose your next step is to examine udev's logs where it creates the |
| 30 |
> various devices. |
| 31 |
|
| 32 |
And I promised myself some months ago I would _never_ spend time on udev |
| 33 |
innards. ;-( |
| 34 |
|
| 35 |
So, I set the debugging options inside /etc/conf.d/udev, which causes |
| 36 |
/run/udev/udev.log to be created. |
| 37 |
|
| 38 |
On the failing 3.7.9, /run/udev/udev.log terminates abruptly with an |
| 39 |
error message, with the entire file, 55 lines, looking like this: |
| 40 |
|
| 41 |
1361736665.547175 [1761] parse_file: reading '/lib/udev/rules.d/10-dm.rules' as rules file |
| 42 |
1361736665.547289 [1761] parse_file: reading '/run/udev/rules.d/10-root-link.rules' as rules file |
| 43 |
[ ..... ] |
| 44 |
1361736665.553901 [1761] parse_file: reading '/lib/udev/rules.d/95-upower-wup.rules' as rules file |
| 45 |
1361736665.553924 [1761] parse_file: reading '/lib/udev/rules.d/97-bluetooth-hid2hci.rules' as rules file |
| 46 |
1361736665.553971 [1761] udev_rules_new: rules use 108624 bytes tokens (9052 * 12 bytes), 31856 bytes buffer |
| 47 |
1361736665.553977 [1761] udev_rules_new: temporary index used 48860 bytes (2443 * 20 bytes) |
| 48 |
1361736665.554010 [1761] main: error creating epoll fd: Function not implemented |
| 49 |
|
| 50 |
I hope "epoll fd", whatever that may be, is something critically |
| 51 |
important to justify just stopping udev. But it can't be that important |
| 52 |
if kernel 3.6.11 doesn't emit such an event. It looks like the kernel's |
| 53 |
event interface has changed. |
| 54 |
|
| 55 |
It seems that the contents of /dev, such as they were, were created |
| 56 |
directly by the kernel when devtmpfs was mounted. Normally they would be |
| 57 |
modified into something usable by udev. |
| 58 |
|
| 59 |
Maybe I should just bite the bullet and go through the pain of updating |
| 60 |
my udev to version 197-r8. :-( |
| 61 |
|
| 62 |
> -- |
| 63 |
> Alan McKinnon |
| 64 |
> alan.mckinnon@×××××.com |
| 65 |
|
| 66 |
-- |
| 67 |
Alan Mackenzie (Nuremberg, Germany). |
Archives