| View previous topic :: View next topic |
| Author |
Message |
DrWoland
l33t
Joined: 13 Nov 2004
Posts: 603
|
 Posted: Sun Jan 09, 2005 7:46 am Post subject: Is this supposed to happen on a "purely udev" syst |
 |
|
| Code: |
bash-2.05b# dir /dev
admmidi fd0 nvram ram9 stdout tty23 tty40 tty58 vc
adsp floppy port random tts tty24 tty41 tty59 vcc
amidi full ptmx rd tty tty25 tty42 tty6 vcs
audio hda pts sda tty0 tty26 tty43 tty60 vcs1
cdrom hdb ram0 sda1 tty1 tty27 tty44 tty61 vcs2
cdrom1 ide ram1 sda2 tty10 tty28 tty45 tty62 vcs3
cdroms initctl ram10 sda5 tty11 tty29 tty46 tty63 vcs4
cdrw inotify ram11 sda6 tty12 tty3 tty47 tty7 vcs5
cdrw1 input ram12 sda7 tty13 tty30 tty48 tty8 vcs6
console kmem ram13 sda8 tty14 tty31 tty49 tty9 vcs7
core kmsg ram14 sequencer tty15 tty32 tty5 ttyS0 vcsa
dmmidi lp0 ram15 sequencer2 tty16 tty33 tty50 ttyS1 vcsa1
dsp mem ram2 sg0 tty17 tty34 tty51 ttyS2 vcsa2
dvd midi ram3 shm tty18 tty35 tty52 ttyS3 vcsa3
dvdrw misc ram4 snd tty19 tty36 tty53 ttyS4 vcsa4
fb mixer ram5 sndstat tty2 tty37 tty54 ttyS5 vcsa5
fb0 null ram6 sound tty20 tty38 tty55 ttyS6 vcsa6
fbsplash nvidia0 ram7 stderr tty21 tty39 tty56 ttyS7 vcsa7
fd nvidiactl ram8 stdin tty22 tty4 tty57 urandom zero
|
I thought only the devices I actually have were going to be in /dev  I turned off the tarball option, even moved the tarball to make sure it wasn't getting loaded, and this still happens. I left devfs support in the kernel because it solved my nvidia problem (nvidia wouldn't load because it uses two devfs commands), but I have gentoo=nodevfs in my grub.conf and udev is working properly as far as I can tell. So uh what's with all the extra crap?
Edit: I was getting the same thing when devfs wasn't even compiled, before I compiled it back in to fix Nvidia... so I'm guessing this is udev's doing... Is this normal? |
|
| Back to top |
|
 |
Daemonax
Apprentice
Joined: 30 Apr 2004
Posts: 211
|
| Posted: Sun Jan 09, 2005 8:27 am Post subject: |
|
|
Uhh well if you have devfs still in the kernel then it's probably not using udev?
_________________
The God idea is growing more impersonal and nebulous in proportion as the human mind is learning to understand natural phenomena and in the degree that science progressively correlates human and social events. -- Emma Goldman |
|
| Back to top |
|
|
dsd
Developer
Joined: 30 Mar 2003
Posts: 2162
Location: nr London
|
|
| Back to top |
|
|
Zarhan
Veteran
Joined: 27 Feb 2004
Posts: 1016
|
| Posted: Sun Jan 09, 2005 1:59 pm Post subject: |
|
|
Follow the instructions in section three:
http://www.gentoo.org/doc/en/udev-guide.xml
After typing in code listing 3.1 (mounting / at /test --bind), just do rm -rf /test/dev/*. Then recreate null and console devices, as per instructions. |
|
| Back to top |
|
|
dsd
Developer
Joined: 30 Mar 2003
Posts: 2162
Location: nr London
|
| Posted: Sun Jan 09, 2005 4:24 pm Post subject: |
|
|
the devices shown are a "clean" udev layout. they will just come back, even if you do recreate the "hidden" nodes behind the udev mount on the root disk.
_________________
http://dev.gentoo.org/~dsd |
|
| Back to top |
|
|
DrWoland
l33t
Joined: 13 Nov 2004
Posts: 603
|
| Posted: Sun Jan 09, 2005 4:40 pm Post subject: |
|
|
| Luineancaion wrote: | | Uhh well if you have devfs still in the kernel then it's probably not using udev? |
devfs is disabled in every way possible, it's just NVIDIA uses devfs commands to create its nodes and crashes without it. |
|
| Back to top |
|
|
AstralStorm
Tux's lil' helper
Joined: 06 Nov 2003
Posts: 80
Location: /dev/null
|
| Posted: Sun Jan 09, 2005 4:46 pm Post subject: |
|
|
| DrWoland wrote: | | devfs is disabled in every way possible, it's just NVIDIA uses devfs commands to create its nodes and crashes without it. |
Well, not here - emerge nvidia-kernel should suit you fine without devfs.
You may only have to add udevstart to /etc/conf.d/local.start. |
|
| Back to top |
|
|
DrWoland
l33t
Joined: 13 Nov 2004
Posts: 603
|
| Posted: Sun Jan 09, 2005 4:56 pm Post subject: |
|
|
| AstralStorm wrote: | | DrWoland wrote: | | devfs is disabled in every way possible, it's just NVIDIA uses devfs commands to create its nodes and crashes without it. |
Well, not here - emerge nvidia-kernel should suit you fine without devfs.
You may only have to add udevstart to /etc/conf.d/local.start. |
Are you saying recompiling nvidia-kernel with devfs not compiled into the kernel will solve my devfs dependency? |
|
| Back to top |
|
|
chunderbunny
Veteran
Joined: 31 May 2004
Posts: 1281
Location: 51°24'27" N, 0°57'15" W
|
| Posted: Sun Jan 09, 2005 5:06 pm Post subject: |
|
|
Firstly, you really ought to recompile your nvidia module every time you make a change to the kernel. There is no devfs dependancy as far as I am aware (I have NEVER used devfs and I don't have any problems with nvidia.)
Secondly, the layout you have in /dev appears to be what I would expect to see in a udev system. WIth devfs you would typically find nearly a thousand entries in /dev, what you have is practically nothing. With newer version of the kernel you can decrease the number of tty nodes created if you wish (I find 31 to be perfectly acceptable) which would help a little. The only odd thing i see in your /dev is a number of ramdisk entries, but I guess you could have something configured to use those. |
|
| Back to top |
|
|
DrWoland
l33t
Joined: 13 Nov 2004
Posts: 603
|
| Posted: Sun Jan 09, 2005 5:28 pm Post subject: |
|
|
| chunderbunny wrote: | Firstly, you really ought to recompile your nvidia module every time you make a change to the kernel. There is no devfs dependancy as far as I am aware (I have NEVER used devfs and I don't have any problems with nvidia.)
Secondly, the layout you have in /dev appears to be what I would expect to see in a udev system. WIth devfs you would typically find nearly a thousand entries in /dev, what you have is practically nothing. With newer version of the kernel you can decrease the number of tty nodes created if you wish (I find 31 to be perfectly acceptable) which would help a little. The only odd thing i see in your /dev is a number of ramdisk entries, but I guess you could have something configured to use those. |
No, but I did notice that it creats 16 ramdisks during boot, just haven't had time to figure out why.
I'll recompile NVIDIA and get back to you.
What are all the tty's anyway? |
|
| Back to top |
|
|
DrWoland
l33t
Joined: 13 Nov 2004
Posts: 603
|
| Posted: Sun Jan 09, 2005 5:46 pm Post subject: |
|
|
You were right, re-compiling the nvidia kernel and then putting it into autoload.d/kernel2.6 did the trick. Before, it would give me an error on boot and not load nvidia, now it loads it just fine and everything works perfect. Thanks, I'm not devfs free 
As for the ramdisks, is that configured in the kernel? I don't remember setting anything like this... |
|
| Back to top |
|
|
dsd
Developer
Joined: 30 Mar 2003
Posts: 2162
Location: nr London
|
| Posted: Sun Jan 09, 2005 5:51 pm Post subject: |
|
|
yes. udev mounts itself on a ramdisk so you shouldnt remove it.
_________________
http://dev.gentoo.org/~dsd |
|
| Back to top |
|
|
DrWoland
l33t
Joined: 13 Nov 2004
Posts: 603
|
| Posted: Sun Jan 09, 2005 6:22 pm Post subject: |
|
|
| dsd wrote: | | yes. udev mounts itself on a ramdisk so you shouldnt remove it. |
So you're saying by me just disabling ramdisks in the kernel, I just pooped on udev?  |
|
| Back to top |
|
|
dsd
Developer
Joined: 30 Mar 2003
Posts: 2162
Location: nr London
|
| Posted: Sun Jan 09, 2005 6:45 pm Post subject: |
|
|
probably, at least on my system it is mounted as ramfs :
| Code: | # mount
[snip]
none on /dev type ramfs (rw)
[snip]
|
it may have fallen back to tmpfs if ramfs is not present, or it may have not mounted at all but be working directly on your root partition
_________________
http://dev.gentoo.org/~dsd |
|
| Back to top |
|
|
Zarhan
Veteran
Joined: 27 Feb 2004
Posts: 1016
|
| Posted: Sun Jan 09, 2005 7:01 pm Post subject: |
|
|
I don't have ramXX entries in /dev.
| Code: |
linux # grep RAM .config
# CONFIG_BLK_DEV_RAM is not set
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_INITRAMFS_SOURCE=""
CONFIG_NVRAM=y
CONFIG_RAMFS=y
# CONFIG_CRAMFS is not set
# CONFIG_FRAME_POINTER is not set
|
And my system works perfectly, using udev. |
|
| Back to top |
|
|
|
Kernel & Hardware
