View previous topic :: View next topic |
Author |
Message |
tebers Tux's lil' helper
Joined: 24 Apr 2002 Posts: 115 Location: Germany, Kirchheim near Munich
|
Posted: Tue May 21, 2002 6:20 pm Post subject: errors in devfs registrar |
|
|
While having taking a closer look to my startup of the pc with dmesg I have found this
Code: |
...
Freeing unused kernel memory: 212k freed
Adding Swap: 530136k swap-space (priority -1)
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide0(3,3), internal journal
PCI: Found IRQ 5 for device 00:0a.0
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
00:0a.0: 3Com PCI 3c905C Tornado at 0x6800. Vers LK1.1.16
devfs_register(1): could not append to parent, err: -17
devfs_register(a1): could not append to parent, err: -17
devfs_register(1): could not append to parent, err: -17
devfs_register(a1): could not append to parent, err: -17
|
so how can I get rid of this errors and where do they come from ?
What details should I supply yet for this ?
Thorsten |
|
Back to top |
|
|
tebers Tux's lil' helper
Joined: 24 Apr 2002 Posts: 115 Location: Germany, Kirchheim near Munich
|
Posted: Sun Jun 02, 2002 9:48 pm Post subject: |
|
|
no one so far that knows how I can deal with the above errors ?
any tips how to investigate this ?
Thorsten |
|
Back to top |
|
|
lx Veteran
Joined: 28 May 2002 Posts: 1012 Location: Netherlands
|
Posted: Sun Jun 02, 2002 9:57 pm Post subject: |
|
|
I also have some of these message with my nvidia driver (which works flawlessly)
found site http://www.atnf.csiro.au/people/rgooch/linux/docs/devfs.html:
Quote: | Strange kernel messages
You may see devfs-related messages in your kernel logs. Below are some messages and what they mean (and what you should do about them, if anything).
* devfs_register(fred): could not append to parent, err: -17
You need to check what the error code means, but usually 17 means EEXIST. This means that a driver attempted to create an entry fred in a directory, but there already was an entry with that name. This is often caused by flawed boot scripts which untar a bunch of inodes into /dev, as a way to restore permissions. This message is harmless, as the device nodes will still provide access to the driver (unless you use the devfs=only boot option, which is only for dedicated souls:-). If you want to get rid of these annoying messages, upgrade to devfsd-v1.3.20 and use the recommended RESTORE directive to restore permissions.
|
Cya lX. _________________ "Remember there's a big difference between kneeling down and bending over.", Frank Zappa |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|