Re: Keyboard stops working
On 3/2/07, Arnie Stender [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tijnema ! wrote: On 3/1/07, Dan Nicholson [EMAIL PROTECTED] wrote: On 3/1/07, Tijnema ! [EMAIL PROTECTED] wrote: On 2/28/07, Barius Drubeck [EMAIL PROTECTED] wrote: Second thing: 1927 ?00:00:00 smbd 1932 ?00:00:00 smbd 1919 ?00:00:00 winbindd 1928 ?00:00:00 winbindd You seem to be running multiple copies of certain daemons. It is possible that these daemons start child processes but I can't tell, since your ps output doesn't use the -H option nor give the PPID. If they are indeed duplicate instances, I can't predict the result but I don't think it is healthy. These are child processes, no need to worry about :) No, it is a problem. You have two copies of each process that are trying to use the exact same resources. What happens when a request comes in for smbd? Who gets it? They don't care that they're child processes. I don't know, but it happens also when i just start them by hand. Tijnema, If you use the command 'ps -ef' you will get the PID (process ID) and the PPID (parent process ID). Unless you have a lot of things starting at the same time I would expect the PID of the child to be the next consecutive number higher than the PID of the parent. If they are indeed parent and child processes then the PPID of the child will be the same as the PID of the parent. If the PPID of the child is not the same as the PID of the parent then they are independent processes not parent/child. Yeah, they are really child processes, here's the part of 'ps -ef' root 1941 1 0 Feb28 ? 00:00:00 nmbd root *1945* 1 0 Feb28 ? 00:00:00 winbindd root 1946 *1945* 0 Feb28 ? 00:00:00 winbindd root *1950* 1 0 Feb28 ? 00:00:00 smbd root 1953 *1950* 0 Feb28 ? 00:00:00 smbd So it's fine i guess. See again Dan's earlier posting. KDM and startx are normally alternative ways to start X. By alternative, I mean mutually exclusive, one or the other but not both. But there's no double X server running, i will do some expiriments with it, but KDE is running fine again. Btw, i think KDM doesn't start, but i like it. It is my own server, and when it starts up, i don't see a login screen, but i'm directly logged in as root in KDE. That's what i always wanted :) Then stop running kdm, kicker, etc. from the console. It's impossible to know who has control in this situation. Why did your keyboard stop working? I don't know, but starting up a bunch of extra processes doesn't help narrow down problems. If you don't want to use kdm, then use startx. This is explained in blfs: http://www.linuxfromscratch.org/blfs/view/svn/kde/config.html If you do this from a bootscript, the X session will be as running as root. That would be an issue for me, but maybe not for you. It means that anyone can press the power button on your computer has root access. -- Dan I have removed kdm, kwin, kicker and kdesktop from my boot list, and now (somehow) everything is working fine, except that my resolution is at 640x480, but i think that is because my nVidia drivers aren't loaded now... Tijnema -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Keyboard stops working
On 2/28/07, Barius Drubeck [EMAIL PROTECTED] wrote: On Tuesday 27 February 2007 23:15, Tijnema ! wrote: Thanks anyway, and please have a look at my ps -A result. First weird thing: 1882 tty2 00:00:13 X 1936 tty1 00:00:00 agetty 1937 ?00:00:00 agetty 1938 tty3 00:00:00 agetty 1939 tty4 00:00:00 agetty 1940 tty5 00:00:00 agetty 1941 tty6 00:00:00 agetty Normally X runs on virtual console 7 and shows up in ps listing without a controlling terminal. Somehow, you managed to start X on tty2, I'm not sure if that is intentional or not. But anyhow, you shouldn't be spawning a getty on the same tty as you run X. That is IMHO almost guaranteed to cause a conflict. thanks, didn't noticed that. Will fix this one for sure. Second thing: 1927 ?00:00:00 smbd 1932 ?00:00:00 smbd 1919 ?00:00:00 winbindd 1928 ?00:00:00 winbindd You seem to be running multiple copies of certain daemons. It is possible that these daemons start child processes but I can't tell, since your ps output doesn't use the -H option nor give the PPID. If they are indeed duplicate instances, I can't predict the result but I don't think it is healthy. These are child processes, no need to worry about :) See again Dan's earlier posting. KDM and startx are normally alternative ways to start X. By alternative, I mean mutually exclusive, one or the other but not both. But there's no double X server running, i will do some expiriments with it, but KDE is running fine again. Btw, i think KDM doesn't start, but i like it. It is my own server, and when it starts up, i don't see a login screen, but i'm directly logged in as root in KDE. That's what i always wanted :) -- Barius -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Keyboard stops working
On 3/1/07, Dan Nicholson [EMAIL PROTECTED] wrote: On 3/1/07, Tijnema ! [EMAIL PROTECTED] wrote: On 2/28/07, Barius Drubeck [EMAIL PROTECTED] wrote: Second thing: 1927 ?00:00:00 smbd 1932 ?00:00:00 smbd 1919 ?00:00:00 winbindd 1928 ?00:00:00 winbindd You seem to be running multiple copies of certain daemons. It is possible that these daemons start child processes but I can't tell, since your ps output doesn't use the -H option nor give the PPID. If they are indeed duplicate instances, I can't predict the result but I don't think it is healthy. These are child processes, no need to worry about :) No, it is a problem. You have two copies of each process that are trying to use the exact same resources. What happens when a request comes in for smbd? Who gets it? They don't care that they're child processes. I don't know, but it happens also when i just start them by hand. See again Dan's earlier posting. KDM and startx are normally alternative ways to start X. By alternative, I mean mutually exclusive, one or the other but not both. But there's no double X server running, i will do some expiriments with it, but KDE is running fine again. Btw, i think KDM doesn't start, but i like it. It is my own server, and when it starts up, i don't see a login screen, but i'm directly logged in as root in KDE. That's what i always wanted :) Then stop running kdm, kicker, etc. from the console. It's impossible to know who has control in this situation. Why did your keyboard stop working? I don't know, but starting up a bunch of extra processes doesn't help narrow down problems. If you don't want to use kdm, then use startx. This is explained in blfs: http://www.linuxfromscratch.org/blfs/view/svn/kde/config.html If you do this from a bootscript, the X session will be as running as root. That would be an issue for me, but maybe not for you. It means that anyone can press the power button on your computer has root access. -- Dan It's my server, and i don't need any security, also, when it starts up it shares / as root :) So i will remove kdm etc from the boot, but i guess it will go wrong again, like i had (other email) Tijnema -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Keyboard stops working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tijnema ! wrote: On 3/1/07, Dan Nicholson [EMAIL PROTECTED] wrote: On 3/1/07, Tijnema ! [EMAIL PROTECTED] wrote: On 2/28/07, Barius Drubeck [EMAIL PROTECTED] wrote: Second thing: 1927 ?00:00:00 smbd 1932 ?00:00:00 smbd 1919 ?00:00:00 winbindd 1928 ?00:00:00 winbindd You seem to be running multiple copies of certain daemons. It is possible that these daemons start child processes but I can't tell, since your ps output doesn't use the -H option nor give the PPID. If they are indeed duplicate instances, I can't predict the result but I don't think it is healthy. These are child processes, no need to worry about :) No, it is a problem. You have two copies of each process that are trying to use the exact same resources. What happens when a request comes in for smbd? Who gets it? They don't care that they're child processes. I don't know, but it happens also when i just start them by hand. Tijnema, If you use the command 'ps -ef' you will get the PID (process ID) and the PPID (parent process ID). Unless you have a lot of things starting at the same time I would expect the PID of the child to be the next consecutive number higher than the PID of the parent. If they are indeed parent and child processes then the PPID of the child will be the same as the PID of the parent. If the PPID of the child is not the same as the PID of the parent then they are independent processes not parent/child. Arnie -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF53giI9lqJPlLBqQRAu4QAJ0Vg82QNrv8xjgc0GG6C5Ve2its/ACgil2d DQXDUpiYqM1IRs/i8xCLYhk= =uCZo -END PGP SIGNATURE- -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Keyboard stops working
On Tuesday 27 February 2007 23:15, Tijnema ! wrote: Thanks anyway, and please have a look at my ps -A result. First weird thing: 1882 tty2 00:00:13 X 1936 tty1 00:00:00 agetty 1937 ?00:00:00 agetty 1938 tty3 00:00:00 agetty 1939 tty4 00:00:00 agetty 1940 tty5 00:00:00 agetty 1941 tty6 00:00:00 agetty Normally X runs on virtual console 7 and shows up in ps listing without a controlling terminal. Somehow, you managed to start X on tty2, I'm not sure if that is intentional or not. But anyhow, you shouldn't be spawning a getty on the same tty as you run X. That is IMHO almost guaranteed to cause a conflict. Second thing: 1927 ?00:00:00 smbd 1932 ?00:00:00 smbd 1919 ?00:00:00 winbindd 1928 ?00:00:00 winbindd You seem to be running multiple copies of certain daemons. It is possible that these daemons start child processes but I can't tell, since your ps output doesn't use the -H option nor give the PPID. If they are indeed duplicate instances, I can't predict the result but I don't think it is healthy. See again Dan's earlier posting. KDM and startx are normally alternative ways to start X. By alternative, I mean mutually exclusive, one or the other but not both. -- Barius -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Keyboard stops working
On 2/27/07, Tijnema ! [EMAIL PROTECTED] wrote: Well i just managed to get KDE working fine and some other software. And now my keyboard stops working, it works in the bios and in grub, but when my own boot program starts up samba and KDE. it stops working This is what my own boot program loads: Are you not using the bootscripts? /usr/kde-3.5.5/bin/kdm /usr/kde-3.5.5/bin/kdesktop /usr/kde-3.5.5/bin/kicker /usr/kde-3.5.5/bin/kwin startx Once you start kdm, you shouldn't need any of the extra stuff. It should start X and and then the proper KDE session. I think you might be having problems because you're starting multiple copies of the desktop session executables: kwin, kdesktop, etc. Just run kdm from a bootscript. It should start a login manager. When you login, it should start a default KDE session for you. Look at the gdm bootscript setup in blfs-bootscripts. kdm should work basically the same. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Keyboard stops working
On 2/27/07, Dan Nicholson [EMAIL PROTECTED] wrote: On 2/27/07, Tijnema ! [EMAIL PROTECTED] wrote: Well i just managed to get KDE working fine and some other software. And now my keyboard stops working, it works in the bios and in grub, but when my own boot program starts up samba and KDE. it stops working This is what my own boot program loads: Are you not using the bootscripts? Nope, just my own program, but it was working fine before. /usr/kde-3.5.5/bin/kdm /usr/kde-3.5.5/bin/kdesktop /usr/kde-3.5.5/bin/kicker /usr/kde-3.5.5/bin/kwin startx Once you start kdm, you shouldn't need any of the extra stuff. It should start X and and then the proper KDE session. I think you might be having problems because you're starting multiple copies of the desktop session executables: kwin, kdesktop, etc. I think you readed my other message on this list too, i noted that i wasn't be able to start KDE normal, and this solved it for me. And it was working fine, just installed OpenSSH and vsfptd. That's all. Tijnema Just run kdm from a bootscript. It should start a login manager. When you login, it should start a default KDE session for you. Look at the gdm bootscript setup in blfs-bootscripts. kdm should work basically the same. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Keyboard stops working
On 2/27/07, Tijnema ! [EMAIL PROTECTED] wrote: On 2/27/07, Dan Nicholson [EMAIL PROTECTED] wrote: On 2/27/07, Tijnema ! [EMAIL PROTECTED] wrote: /usr/kde-3.5.5/bin/kdm /usr/kde-3.5.5/bin/kdesktop /usr/kde- 3.5.5/bin/kicker /usr/kde-3.5.5/bin/kwin startx Once you start kdm, you shouldn't need any of the extra stuff. It should start X and and then the proper KDE session. I think you might be having problems because you're starting multiple copies of the desktop session executables: kwin, kdesktop, etc. I think you readed my other message on this list too, i noted that i wasn't be able to start KDE normal, and this solved it for me. And it was working fine, just installed OpenSSH and vsfptd. That's all. Alright, but if you're going to use startx, then everything you're doing before it is useless. Or the other way around if you're using kdm. If you want to launch kwin, kdesktop, etc., they should be started by startx (through .xinitrc) or kdm. I'm guessing that they're bombing right now because you're calling them from the console, not from an X session. I don't know what caused things to work or not work correctly for you, but it would help to follow one procedure or the other. What you're doing right now is bound to cause issues. You're launching two instances of X and multiple instances of the kde session programs. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Keyboard stops working
On 2/27/07, Dan Nicholson [EMAIL PROTECTED] wrote: On 2/27/07, Tijnema ! [EMAIL PROTECTED] wrote: On 2/27/07, Dan Nicholson [EMAIL PROTECTED] wrote: On 2/27/07, Tijnema ! [EMAIL PROTECTED] wrote: /usr/kde-3.5.5/bin/kdm /usr/kde-3.5.5/bin/kdesktop /usr/kde- 3.5.5/bin/kicker /usr/kde-3.5.5/bin/kwin startx Once you start kdm, you shouldn't need any of the extra stuff. It should start X and and then the proper KDE session. I think you might be having problems because you're starting multiple copies of the desktop session executables: kwin, kdesktop, etc. I think you readed my other message on this list too, i noted that i wasn't be able to start KDE normal, and this solved it for me. And it was working fine, just installed OpenSSH and vsfptd. That's all. Alright, but if you're going to use startx, then everything you're doing before it is useless. Or the other way around if you're using kdm. If you want to launch kwin, kdesktop, etc., they should be started by startx (through .xinitrc) or kdm. I'm guessing that they're bombing right now because you're calling them from the console, not from an X session. I don't know what caused things to work or not work correctly for you, but it would help to follow one procedure or the other. What you're doing right now is bound to cause issues. You're launching two instances of X and multiple instances of the kde session programs. -- Dan I was able to startup SSH deamon with the mouse, and so i could use the keyboard to create a log of the command ps -A see the attachment... but well, i only did install a few programs and now the keyboard isn't working anymore, i mean KDE was working fine. Just realised one more thing, and it seems that it is the problem, i set the default bootlevel to 5, instead of 4 where i had it in. In my boot program things there's no difference between runlevel 4 5. but i see cups doesn't start in runlevel 4. S99cups exists in rc3.d rc5.d not in rc4.d. cups was working fine in runlevel 3 I added cups to runlevel 4 now, and that actually is the problem, and i think i know why... My own program loader is S00, cups is S99 Now i've set cups to S95 and my own program loader to S98 so it gets loaded after cups. And that fixed the problem Thanks anyway, and please have a look at my ps -A result. Tijnema -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page PID TTY TIME CMD 1 ?00:00:00 init 2 ?00:00:00 migration/0 3 ?00:00:00 ksoftirqd/0 4 ?00:00:00 events/0 5 ?00:00:00 khelper 6 ?00:00:00 kthread 8 ?00:00:00 kblockd/0 9 ?00:00:00 kacpid 67 ?00:00:00 khubd 130 ?00:00:00 pdflush 131 ?00:00:00 pdflush 133 ?00:00:00 aio/0 132 ?00:00:00 kswapd0 134 ?00:00:00 jfsIO 135 ?00:00:00 jfsCommit 136 ?00:00:00 jfsSync 137 ?00:00:00 xfslogd/0 138 ?00:00:00 xfsdatad/0 724 ?00:00:00 kseriod 767 ?00:00:00 ata/0 770 ?00:00:00 khpsbpkt 790 ?00:00:00 kpsmoused 804 ?00:00:03 kjournald 881 ?00:00:00 udevd 1634 ?00:00:00 kjournald 1636 ?00:00:00 kjournald 1842 ?00:00:00 kdm 1846 ?00:00:00 startx 1856 ?00:00:00 syslogd 1874 ?00:00:00 klogd 1881 ?00:00:00 xinit 1882 tty2 00:00:13 X 1902 ?00:00:00 nmbd 1919 ?00:00:00 winbindd 1920 ?00:00:00 mdnsd 1927 ?00:00:00 smbd 1928 ?00:00:00 winbindd 1932 ?00:00:00 smbd 1933 ?00:00:01 cupsd 1936 tty1 00:00:00 agetty 1937 ?00:00:00 agetty 1938 tty3 00:00:00 agetty 1939 tty4 00:00:00 agetty 1940 tty5 00:00:00 agetty 1941 tty6 00:00:00 agetty 1951 ?00:00:00 startkde 1954 ?00:00:00 dbus-launch 1955 ?00:00:00 dbus-daemon 1987 ?00:00:00 start_kdeinit 1988 ?00:00:00 kdeinit 1991 ?00:00:00 dcopserver 1995 ?00:00:00 klauncher 1997 ?00:00:00 kded 2006 ?00:00:00 kwrapper 2008 ?00:00:00 ksmserver 2010 ?00:00:00 kwin 2012 ?00:00:02 kdesktop 2015 ?00:00:01 kicker 2017 ?00:00:00 kio_file 2029 ?00:00:01 artsd 2031 ?00:00:00 kaccess 2037 ?00:00:02 kttsmgr 2041 ?00:00:00 klipper 2043 ?00:00:00 knotify 2051 ?00:00:00 korgac 2055 ?00:00:00 kio_file 2059 ?00:00:00 sshd 2071 ?00:00:00 kio_system 2088 ?00:00:00 sshd 2092 pts/100:00:00 bash 2096 ?00:00:00 smbd 2099 pts/100:00:00 ps -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
