Re: [gentoo-user] udevstart at boot?
On Sunday 18 December 2005 00:42, a tiny voice compelled Richard Fish to write: On 12/17/05, Ernie Schroder [EMAIL PROTECTED] wrote: Is /dev/dsp actually missing on startup, or just created with the wrong permissions? Apparently it has the wrong permissions, or so says the message when I start KDE,but if I reset them, next boot they are changed. Either resetting permissions, or doing # udevstart allows me to use /dev/dsp as user but changes don't survive a reboot. Hmm, /dev/dsp is only necessary for legacy OSS support...it should not be necessary with KDE, which _should_ be able to use the ALSA interface. Do you have the alsa USE flag set? Hmm, no IIRC, when I first installed on this box, I had to go with oss (nforce2 mobo w/onboard sound). What are the permissions that it is being created with? (Do ls -l /dev/dsp from a console after startup without logging into KDE). Are you using a device tarball (RC_DEVICE_TARBALL in /etc/conf.d/rc)? Yes. I would suggest turning TARBALL off. It is almost certainly not needed today. Turned it off. Let's see One possibility is that the device is comfing from the tarball, but not being recreated by udev for some reason. You can check this with: tar -tjvf /lib/udev-state/devices.tar.bz2 $ sudo tar -tjvf /lib/udev-state/devices.tar.bz2 | grep dsp crw--- root/audio14,19 2004-02-19 04:28:48 dsp1 crw--- root/audio14,35 2004-02-19 04:28:48 dsp2 crw--- root/audio14,51 2004-02-19 04:28:48 dsp3 Also, what messages do you get on bootup between Starting udevd and Mounting /dev/pts... Can't see Starting udevd is dmesg or kern.log.0 will try to catch it next boot Do you CONFIG_SND_PCM_OSS=y or =m in your kernel configuration? cat /usr/src/linux/.config | grep SND_PCM_OSS CONFIG_SND_PCM_OSS=y Rebooting with these changes. I'll get back to you soon. Thanks again. -Richard Rebooting with these changes. I'll get back to you soon. Thanks again. -- Regards, Ernie 100% Microsoft and Intel free 08:07:29 up 8:26, 2 users, load average: 0.21, 0.69, 0.66 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On Sunday 18 December 2005 08:35, a tiny voice compelled Ernie Schroder to write: On Sunday 18 December 2005 00:42, a tiny voice compelled Richard Fish to write: On 12/17/05, Ernie Schroder [EMAIL PROTECTED] wrote: Is /dev/dsp actually missing on startup, or just created with the wrong permissions? Apparently it has the wrong permissions, or so says the message when I start KDE,but if I reset them, next boot they are changed. Either resetting permissions, or doing # udevstart allows me to use /dev/dsp as user but changes don't survive a reboot. Hmm, /dev/dsp is only necessary for legacy OSS support...it should not be necessary with KDE, which _should_ be able to use the ALSA interface. Do you have the alsa USE flag set? Hmm, no IIRC, when I first installed on this box, I had to go with oss (nforce2 mobo w/onboard sound). What are the permissions that it is being created with? (Do ls -l /dev/dsp from a console after startup without logging into KDE). (loged into kde but I have not done # udevstart as of yet): lrwxrwxrwx 1 root root 9 Dec 18 03:45 /dev/dsp - sound/dsp After doing # udevstart: $ sudo udevstart [EMAIL PROTECTED] ~ $ ls -l /dev/dsp lrwxrwxrwx 1 root root 9 Dec 18 09:02 /dev/dsp - sound/dsp Looks the same to me, but I seem to have permissions for /dev/dsp Saytime works now, it didn't give me audio befor udevstart. Look at the times wierd huh? Now, before logging into KDE: lrwxrwxrwx Time is still odd Are you using a device tarball (RC_DEVICE_TARBALL in /etc/conf.d/rc)? Yes. I would suggest turning TARBALL off. It is almost certainly not needed today. Turned it off. Let's see Not a good idea there. A device node for my nvidia graphics card was not created. I edited xorg.conf, changing driver from nvidia to nv just to get X up and running Gotta recreate them. I guess. OK created the nvidia devices like so: mknod -m 660 /dev/nvidia0 c 195 0 mknod -m 660 /dev/nvidia1 c 195 1 mknod -m 660 /dev/nvidiactl c 195 255 And changed back to TARBALL=on Let's see changed back to nvidia and rebooted. X working properly. One possibility is that the device is comfing from the tarball, but not being recreated by udev for some reason. You can check this with: tar -tjvf /lib/udev-state/devices.tar.bz2 $ sudo tar -tjvf /lib/udev-state/devices.tar.bz2 | grep dsp crw--- root/audio14,19 2004-02-19 04:28:48 dsp1 crw--- root/audio14,35 2004-02-19 04:28:48 dsp2 crw--- root/audio14,51 2004-02-19 04:28:48 dsp3 Also, what messages do you get on bootup between Starting udevd and Mounting /dev/pts... Can't see Starting udevd is dmesg or kern.log.0 will try to catch it next boot I don't see Starting udevd but I do see: Configuring System to use udev setting /sbin/udevsend as hotplug agent mounting devpts at /dev/pts Do you CONFIG_SND_PCM_OSS=y or =m in your kernel configuration? cat /usr/src/linux/.config | grep SND_PCM_OSS CONFIG_SND_PCM_OSS=y Rebooting with these changes. I'll get back to you soon. Thanks again. -Richard Rebooting with these changes. I'll get back to you soon. Thanks again. -- Regards, Ernie 100% Microsoft and Intel free 08:07:29 up 8:26, 2 users, load average: 0.21, 0.69, 0.66 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ -- Regards, Ernie 100% Microsoft and Intel free 08:53:27 up 7 min, 2 users, load average: 0.58, 0.43, 0.18 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On Sunday 18 December 2005 10:13, a tiny voice compelled Ernie Schroder to write: On Sunday 18 December 2005 08:35, a tiny voice compelled Ernie Schroder to write: On Sunday 18 December 2005 00:42, a tiny voice compelled Richard Fish to write: Hmm, /dev/dsp is only necessary for legacy OSS support...it should not be necessary with KDE, which _should_ be able to use the ALSA interface. Do you have the alsa USE flag set? Hmm, no Changed the KDE sound system to ALSA same problem. Is there something I would have to rebuild with the alsa flag? -- Regards, Ernie 100% Microsoft and Intel free 10:26:28 up 1 min, 2 users, load average: 0.78, 0.36, 0.13 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On Sunday 18 December 2005 15:30, Ernie Schroder wrote: On Sunday 18 December 2005 10:13, a tiny voice compelled Ernie Schroder to write: On Sunday 18 December 2005 08:35, a tiny voice compelled Ernie Schroder to write: On Sunday 18 December 2005 00:42, a tiny voice compelled Richard Fish to write: Hmm, /dev/dsp is only necessary for legacy OSS support...it should not be necessary with KDE, which _should_ be able to use the ALSA interface. Do you have the alsa USE flag set? Hmm, no Changed the KDE sound system to ALSA same problem. Is there something I would have to rebuild with the alsa flag? -- Regards, Ernie 100% Microsoft and Intel free 10:26:28 up 1 min, 2 users, load average: 0.78, 0.36, 0.13 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ Ernie, Have you checked something simple, your user is in the audio group? -- Big Tone -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
Ernie Schroder wrote: I'm obviously looking in the wrong places, but I can't find documentation on getting udev to start at boot. Sound and a few other things you don't notice right away fail to work until I do: # udevstart /dev/dsp is created with correct permissions and I'm good to go. The question is: How to I get udev to start at boot? Which version of udev do you have installed? What is the output of cat /proc/sys/kernel/hotplug? Daniel -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On Sunday 18 December 2005 14:01, a tiny voice compelled Tony Davison to write: On Sunday 18 December 2005 15:30, Ernie Schroder wrote: On Sunday 18 December 2005 10:13, a tiny voice compelled Ernie Schroder to write: On Sunday 18 December 2005 08:35, a tiny voice compelled Ernie Schroder to write: On Sunday 18 December 2005 00:42, a tiny voice compelled Richard Fish to write: Hmm, /dev/dsp is only necessary for legacy OSS support...it should not be necessary with KDE, which _should_ be able to use the ALSA interface. Do you have the alsa USE flag set? Hmm, no Changed the KDE sound system to ALSA same problem. Is there something I would have to rebuild with the alsa flag? -- Regards, Ernie 100% Microsoft and Intel free 10:26:28 up 1 min, 2 users, load average: 0.78, 0.36, 0.13 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ Ernie, Have you checked something simple, your user is in the audio group? -- Big Tone Yes, early on the 2 users are there. Good question though, if someone else is following this thread. -- Regards, Ernie 100% Microsoft and Intel free 14:43:33 up 3:44, 2 users, load average: 0.51, 0.66, 0.56 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On Sunday 18 December 2005 14:14, a tiny voice compelled Daniel Drake to write: Ernie Schroder wrote: I'm obviously looking in the wrong places, but I can't find documentation on getting udev to start at boot. Sound and a few other things you don't notice right away fail to work until I do: # udevstart /dev/dsp is created with correct permissions and I'm good to go. The question is: How to I get udev to start at boot? Which version of udev do you have installed? What is the output of cat /proc/sys/kernel/hotplug? Daniel $ emerge -vp udev snip [ebuild R ] sys-fs/udev-070-r1 (-selinux) -static 0 kB $ cat /proc/sys/kernel/hotplug /sbin/udevsend I have added /sbin/udevstart to /etc/conf.d/local.start and it seems that /dev/dsp is recreated with the right permissions and the annoying message is gone. Not the most elegant solution, but effective. -- Regards, Ernie 100% Microsoft and Intel free 14:46:10 up 3:47, 3 users, load average: 0.31, 0.46, 0.49 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On Sat, 2005-12-17 at 21:36 -0500, Ernie Schroder wrote: I'm obviously looking in the wrong places, but I can't find documentation on getting udev to start at boot. Sound and a few other things you don't notice right away fail to work until I do: # udevstart /dev/dsp is created with correct permissions and I'm good to go. The question is: How to I get udev to start at boot? I had thought that the place to do this was in grub.conf. Following some instructions I found searching the gentoo forums, I edited my kernel line like so: title Gentoo-2.6.14 root (hd0,0) kernel /bzImage-2.6.14-gentoo-r4 root=/dev/hda5 dev=udev video=vesafb:ywrap,mtrr vga=0x317 IIRC its not dev=udev, it's jsut plain udev Also If you see why the boot complains about my video mode, feel free to comment. -- Regards, Ernie 100% Microsoft and Intel free 21:17:06 up 23 min, 2 users, load average: 0.34, 0.59, 0.57 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ -- Lares Moreau [EMAIL PROTECTED] | LRU: 400755 http://counter.li.org lares/irc.freenode.net | Gentoo x86 Arch Tester | ::0 Alberta, Canada Public Key: 0D46BB6E @ subkeys.pgp.net | Encrypted Mail Preferred Key fingerprint = 0CA3 E40D F897 7709 3628 C5D4 7D94 483E 0D46 BB6E signature.asc Description: This is a digitally signed message part
Re: [gentoo-user] udevstart at boot?
On 12/18/05, Ernie Schroder [EMAIL PROTECTED] wrote: What are the permissions that it is being created with? (Do ls -l /dev/dsp from a console after startup without logging into KDE). (loged into kde but I have not done # udevstart as of yet): lrwxrwxrwx 1 root root 9 Dec 18 03:45 /dev/dsp - sound/dsp Damn symlinks. Need to see: ls -l /dev/sound/dsp tar -tjvf /lib/udev-state/devices.tar.bz2 $ sudo tar -tjvf /lib/udev-state/devices.tar.bz2 | grep dsp crw--- root/audio14,19 2004-02-19 04:28:48 dsp1 crw--- root/audio14,35 2004-02-19 04:28:48 dsp2 crw--- root/audio14,51 2004-02-19 04:28:48 dsp3 No /dev/dsp, so your tarball can't be having any effect here... -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On 12/18/05, Ernie Schroder [EMAIL PROTECTED] wrote: On Sunday 18 December 2005 10:13, a tiny voice compelled Ernie Schroder to write: On Sunday 18 December 2005 08:35, a tiny voice compelled Ernie Schroder to write: On Sunday 18 December 2005 00:42, a tiny voice compelled Richard Fish to write: Hmm, /dev/dsp is only necessary for legacy OSS support...it should not be necessary with KDE, which _should_ be able to use the ALSA interface. Do you have the alsa USE flag set? Hmm, no Changed the KDE sound system to ALSA same problem. Is there something I would have to rebuild with the alsa flag? Yes...you can keep arts but have it use alsa if you set the alsa USE flag on arts. Or you can skip arts altogether and have it use alsa by setting +alsa on kdelibs. [ebuild R ] kde-base/arts-3.5.0 +alsa ... [ebuild U ] kde-base/kdelibs-3.5.0-r1 [3.5.0] -acl +alsa ... -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On Sunday 18 December 2005 18:54, a tiny voice compelled Richard Fish to write: On 12/18/05, Ernie Schroder [EMAIL PROTECTED] wrote: What are the permissions that it is being created with? (Do ls -l /dev/dsp from a console after startup without logging into KDE). (loged into kde but I have not done # udevstart as of yet): lrwxrwxrwx 1 root root 9 Dec 18 03:45 /dev/dsp - sound/dsp Damn symlinks. Need to see: ls -l /dev/sound/dsp ls -l /dev/sound/dsp crw-rw 1 root audio 14, 3 Dec 18 05:59 /dev/sound/dsp users are in the audio group tar -tjvf /lib/udev-state/devices.tar.bz2 $ sudo tar -tjvf /lib/udev-state/devices.tar.bz2 | grep dsp crw--- root/audio14,19 2004-02-19 04:28:48 dsp1 crw--- root/audio14,35 2004-02-19 04:28:48 dsp2 crw--- root/audio14,51 2004-02-19 04:28:48 dsp3 No /dev/dsp, so your tarball can't be having any effect here... The tarball has to be having some effect. When I turned it off and rebooted, I had no /dev/nvidia* devices. I recreated them, turned TARBALL back on and added /sbin/udevstart to /etc/conf.d/local.start. This might not be the right way to solve this but it does the trick. I would however like to fix this the right way. -Richard -- Regards, Ernie 100% Microsoft and Intel free 19:30:44 up 8:31, 3 users, load average: 0.01, 0.05, 0.12 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ -- gentoo-user@gentoo.org mailing list
[gentoo-user] udevstart at boot?
I'm obviously looking in the wrong places, but I can't find documentation on getting udev to start at boot. Sound and a few other things you don't notice right away fail to work until I do: # udevstart /dev/dsp is created with correct permissions and I'm good to go. The question is: How to I get udev to start at boot? I had thought that the place to do this was in grub.conf. Following some instructions I found searching the gentoo forums, I edited my kernel line like so: title Gentoo-2.6.14 root (hd0,0) kernel /bzImage-2.6.14-gentoo-r4 root=/dev/hda5 dev=udev video=vesafb:ywrap,mtrr vga=0x317 Also If you see why the boot complains about my video mode, feel free to comment. -- Regards, Ernie 100% Microsoft and Intel free 21:17:06 up 23 min, 2 users, load average: 0.34, 0.59, 0.57 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On 12/17/05, Ernie Schroder [EMAIL PROTECTED] wrote: I'm obviously looking in the wrong places, but I can't find documentation on getting udev to start at boot. Sound and a few other things you don't notice right away fail to work until I do: # udevstart /dev/dsp is created with correct permissions and I'm good to go. The question is: How to I get udev to start at boot? Udevstart doesn't actually start udevd...it just rescans the devices and recreates device nodes. The actual udev daemon is started by /sbin/rc, possibly via /lib/rc-scripts/add-ons/udev-start.sh depending upon your version of baselayout. Having RC_DEVICES=udev or auto should be sufficient to start udevd on startup. Setting dev=udev in grub.conf is not necessary, and probably won't change anything. Now for your missing device nodes, maybe you just need to do: rc-update -a coldplug default kernel /bzImage-2.6.14-gentoo-r4 root=/dev/hda5 dev=udev video=vesafb:ywrap,mtrr vga=0x317 Also If you see why the boot complains about my video mode, feel free to comment. 1. If you are using vesafb-tng, you cannot use vga= to set the video mode. It must be part of the video option like so: video=vesafb:[EMAIL PROTECTED],ywrap,mtrr 2. If you are not using vesafb-tng, you cannot use video=, so you should take out that option. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On Saturday 17 December 2005 21:55, a tiny voice compelled Richard Fish to write: On 12/17/05, Ernie Schroder [EMAIL PROTECTED] wrote: I'm obviously looking in the wrong places, but I can't find documentation on getting udev to start at boot. Sound and a few other things you don't notice right away fail to work until I do: # udevstart /dev/dsp is created with correct permissions and I'm good to go. The question is: How to I get udev to start at boot? Udevstart doesn't actually start udevd...it just rescans the devices and recreates device nodes. The actual udev daemon is started by /sbin/rc, possibly via /lib/rc-scripts/add-ons/udev-start.sh depending upon your version of baselayout. via /lib/rc-scripts/add-ons/ contains devfs start and stop and udev start and stop scripts. /sbin/rc looks right Having RC_DEVICES=udev or auto should be sufficient to start udevd on startup. Setting dev=udev in grub.conf is not necessary, and probably won't change anything. Having RC_DEVICES=udev or auto Where?? Now for your missing device nodes, maybe you just need to do: rc-update -a coldplug default moved coldplug from boot to default no joy kernel /bzImage-2.6.14-gentoo-r4 root=/dev/hda5 dev=udev video=vesafb:ywrap,mtrr vga=0x317 Also If you see why the boot complains about my video mode, feel free to comment. 1. If you are using vesafb-tng, you cannot use vga= to set the video mode. It must be part of the video option like so: video=vesafb:[EMAIL PROTECTED],ywrap,mtrr Thanks that did it 2. If you are not using vesafb-tng, you cannot use video=, so you should take out that option. -Richard -- Regards, Ernie 100% Microsoft and Intel free 22:27:31 up 4 min, 2 users, load average: 2.34, 0.91, 0.36 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On Saturday 17 December 2005 22:48, a tiny voice compelled Richard Fish to write: On 12/17/05, Ernie Schroder [EMAIL PROTECTED] wrote: On Saturday 17 December 2005 21:55, a tiny voice compelled Richard Fish to write: Having RC_DEVICES=udev or auto should be sufficient to start udevd on startup. Setting dev=udev in grub.conf is not necessary, and probably won't change anything. Having RC_DEVICES=udev or auto Changed from auto to udev no joy. Where?? Sorry: /etc/conf.d/rc. Now for your missing device nodes, maybe you just need to do: rc-update -a coldplug default moved coldplug from boot to default no joy Is /dev/dsp actually missing on startup, or just created with the wrong permissions? Apparently it has the wrong permissions, or so says the message when I start KDE,but if I reset them, next boot they are changed. Either resetting permissions, or doing # udevstart allows me to use /dev/dsp as user but changes don't survive a reboot. Are you using a device tarball (RC_DEVICE_TARBALL in /etc/conf.d/rc)? Yes. I've tried to read up on udev. but I guess I'm pretty thick headed. I do appreciate the hand holding. -Richard -- Regards, Ernie 100% Microsoft and Intel free 23:46:51 up 5 min, 2 users, load average: 0.47, 0.60, 0.28 Linux 2.6.14-gentoo-r42.6.14-r-4_new i686 AMD Athlon(tm) XP 2400+ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] udevstart at boot?
On 12/17/05, Ernie Schroder [EMAIL PROTECTED] wrote: Is /dev/dsp actually missing on startup, or just created with the wrong permissions? Apparently it has the wrong permissions, or so says the message when I start KDE,but if I reset them, next boot they are changed. Either resetting permissions, or doing # udevstart allows me to use /dev/dsp as user but changes don't survive a reboot. Hmm, /dev/dsp is only necessary for legacy OSS support...it should not be necessary with KDE, which _should_ be able to use the ALSA interface. Do you have the alsa USE flag set? What are the permissions that it is being created with? (Do ls -l /dev/dsp from a console after startup without logging into KDE). Are you using a device tarball (RC_DEVICE_TARBALL in /etc/conf.d/rc)? Yes. I would suggest turning TARBALL off. It is almost certainly not needed today. One possibility is that the device is comfing from the tarball, but not being recreated by udev for some reason. You can check this with: tar -tjvf /lib/udev-state/devices.tar.bz2 Also, what messages do you get on bootup between Starting udevd and Mounting /dev/pts... Do you CONFIG_SND_PCM_OSS=y or =m in your kernel configuration? -Richard -- gentoo-user@gentoo.org mailing list
