Re: KDE 3.5 Crashing
Gemma Fletcher wrote: I apologize in advance if this advice is too rudimentary. Rudimentry is good :) I am a BSD noob :D Sounds more like hardware. You did not say how you tested your memory. If you did not use Memtest86, get and run that. Also run fsck manually. I used Memtest and I have had already run fsck since my poor hard drive was compaining bitterly of so many cold restarts. There were some errors that were cleaned up - and it seems a bit more stable as in it can go a few hours before freezing [snip] I've had many freezes with FreeBSD 6.2 and nvidia cards on at least 3 separate systems. The thing that has fixed it on every system has been to use portdowngrade to reset the nvidia driver to: nvidia-driver-1.0.8776 (possibly with an extra _4 in the portdowngrade list) Hope this helps. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: KDE 3.5 Crashing
Gemma Fletcher wrote: I apologize in advance if this advice is too rudimentary. Rudimentry is good :) I am a BSD noob :D Sounds more like hardware. You did not say how you tested your memory. If you did not use Memtest86, get and run that. Also run fsck manually. I used Memtest and I have had already run fsck since my poor hard drive was compaining bitterly of so many cold restarts. There were some errors that were cleaned up - and it seems a bit more stable as in it can go a few hours before freezing Mark wrote: [snip] I've had many freezes with FreeBSD 6.2 and nvidia cards on at least 3 separate systems. The thing that has fixed it on every system has been to use portdowngrade to reset the nvidia driver to: nvidia-driver-1.0.8776 (possibly with an extra _4 in the portdowngrade list) Hope this helps. Awesome - will def try it. I ended up pulling my card out and just running the onboard - which works - but annoys me endlessly. Thanks for the help! :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fw: KDE 3.5 Crashing(Solved)
Thanks everyone for their help! Final result was my video card. I had a power surge a few weeks ago - and while I have a surge protector it stilled messed my card up a bit. So periodically the card would die and so would the system. Pulled it out and used the onboard and problem solvered. Hello Gemma, Hello Nikola Although it really looks like hardware, you can also do this to be 100% sure it isn't software related: (1) Had you used that computer before you have installed FreeBSD? It would be a nice idea to post here the output of your 'dmesg' or /var/log/messages. Yes it was running XP - will post output once I finalise this car sale and have a spare moment. :) (2) Have you tried to run a small script as Matthias proposed? Not yet - am reading up on how to run a script :) (3) Are you sure your ports are up-to-date? If in doubt, install ports-mgmt/portupgrade and run # portversion -v -L = To cut a long scary story short sort of. I've actually reinstalled 6.2, 4 times as I seem to have so many little things missing I wasn't sure if it was me or the install. So upgrading ports always eneded up crashing. Anyway first few times went the full install, final time went with as just a user install without X. After that i installed X and then KDE from the ports collection. Attempted a 7.2 upgrade thinking that might help a few problems and in a word - nightmare. A week later after finally getting past the libxfct step the actual upgrade crashed as it couldn't seem to create the xorg-libraries 7.2 directory. So I just decided to ignore it for a while. But aside from xorg - everything else is up to date. (4) If yes, as of how to check X without KDE, do the following: (a) run 'xinit' without ~/.xinitrc file to avoid starting KDE and or any other window manager; (once you start it, you can go back by 'exit' or Ctrl+Alt+Backspace; please note that you must put the mouse over the window in order to move focus on it); (b) check if there are warning -- (WW) -- or other suspicious messages in /var/log/Xorg.0.log; (c) while in pure xinit session, run Firefox or other application that is not KDE/Qt related; (d) run Opera, Skype or similar app that is Qt- but not KDE-related; (e) run KDE applications (Konqueror, KMail, etc.) and report one by one what happened, from (1) to (4e). Maybe it helps to isolate the problem, besides hardware tests :) Will try the above this arvo when i do the rest. Thanks heaps :) Nikola Lečić Gemma ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 3.5 Crashing
On Fri, 15 Jun 2007, Gemma Fletcher wrote: Edit: Resending as having problems with my mail. If it pops up twice then apologies :) Hi list :) Installed BSD 6.2 a few days ago and am totally new to it all. I installed KDE 3.5 and it was working nicely until it juststopped. No obvious crash - it just froze. Had to reboot the system with the reset button as no other method was working. So I thought it might be my sound since it wasn't configured and I had read a few things that said that sometimes caused KDE to crash. Also disabled a few buggy plugins and what not and still it keeps on freezing on me. The annoying thing is its totally random - It could be running for several hours before it freezes; and sometimes it freezes the moment I log on. Its frozen at last count 7 times today and I ended up having to do a some random hardrive check as boot up was starting to fail and logging me in as single mode user only. Anyway - to get to the point; is there a log somewhere that I can check out in console mode which incidently never crashes that might help me pinpoint the problem? Thanks in advance, Gemma I apologize in advance if this advice is too rudimentary. Sounds more like hardware. You did not say how you tested your memory. If you did not use Memtest86, get and run that. Also run fsck manually. If the hardware checks out okay, you can try to isolate what is failing. Turn of various compoents one at a time. For example turn off the wireles interface and work normally. If that still fails, set up a dd command or a benchmark program to run under kde buut without the network. You can set up either of these to run overnight so you should get a good idea that the test worked or not. If you get a failure without the network repeat the test using twm (its built into xorg). If all this fails to identify the problem you need at least to get a kernel dump. The developers handbook has information on this. Hope this helps, DougD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 3.5 Crashing
I apologize in advance if this advice is too rudimentary. Rudimentry is good :) I am a BSD noob :D Sounds more like hardware. You did not say how you tested your memory. If you did not use Memtest86, get and run that. Also run fsck manually. I used Memtest and I have had already run fsck since my poor hard drive was compaining bitterly of so many cold restarts. There were some errors that were cleaned up - and it seems a bit more stable as in it can go a few hours before freezing If the hardware checks out okay, you can try to isolate what is failing. Turn of various compoents one at a time. For example turn off the wireles interface and work normally. If that still fails, set up a dd command or a benchmark program to run under kde buut without the network. You can set up either of these to run overnight so you should get a good idea that the test worked or not. If you get a failure without the network repeat the test using twm (its built into xorg). I pulled out my wifi card (since i wasn't even using the darn thing), the only other thing to pull is my video card (Nividia GForce 6600) - the rest (sound, my ethernet card etc) are all onboard. Now I have being trying to find something comparable to windows where there is a device manager where i can disable or enable hardware. Is there something like that? Or is it console command only? I've been reading through the handbook and the KDE doc but haven't come across much. I'll try a benchmark prog and then try twm if there's a prob. If all this fails to identify the problem you need at least to get a kernel dump. The developers handbook has information on this. Hope this helps, Help heaps, Thanks :) DougD Gemma ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 3.5 Crashing
On Sat, 16 Jun 2007 20:45:57 +1000 Gemma Fletcher [EMAIL PROTECTED] wrote: On Friday 15 June 2007 21:41, Matthias Apitz wrote: El día Friday, June 15, 2007 a las 09:33:27PM +1000, Gemma Fletcher escribió: Can you check if only X or KDE is frozen, or the system at all? Try to connect from some other host on the network. Try to do some RAM testing as well. matthias Ok my RAM is fine and dandy. I'm not sure how to check to see if only KDE is frozen. Once is freezes I can't do anything. Not even reset with ctrl-alt-del. And my keyboard usually goes dead indicated by my numlock light turning off Its just me - so I have no other host to connect from. I did notice something though that i forgot to mention- it usually only crashes if I am doing some internet related activity. Ie.Browsing, checking email, IM'ing etc If I just do normal stuff like spreadsheeting, or developing or whatever it seems to run fine. Hello Gemma, Although it really looks like hardware, you can also do this to be 100% sure it isn't software related: (1) Had you used that computer before you have installed FreeBSD? It would be a nice idea to post here the output of your 'dmesg' or /var/log/messages. (2) Have you tried to run a small script as Matthias proposed? (3) Are you sure your ports are up-to-date? If in doubt, install ports-mgmt/portupgrade and run # portversion -v -L = (4) If yes, as of how to check X without KDE, do the following: (a) run 'xinit' without ~/.xinitrc file to avoid starting KDE and or any other window manager; (once you start it, you can go back by 'exit' or Ctrl+Alt+Backspace; please note that you must put the mouse over the window in order to move focus on it); (b) check if there are warning -- (WW) -- or other suspicious messages in /var/log/Xorg.0.log; (c) while in pure xinit session, run Firefox or other application that is not KDE/Qt related; (d) run Opera, Skype or similar app that is Qt- but not KDE-related; (e) run KDE applications (Konqueror, KMail, etc.) and report one by one what happened, from (1) to (4e). Maybe it helps to isolate the problem, besides hardware tests :) Nikola Lečić ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 3.5 Crashing
On Jun 15 at 20:01 +1000, Gemma Fletcher wrote: Installed BSD 6.2 a few days ago and am totally new to it all. I installed KDE 3.5 and it was working nicely until it juststopped. No obvious crash - it just froze. Had to reboot the system with the reset button as no other method was working. [...] Are you using dial-up with kppp? I recently saw a freeze-then-reboot under KDE 3.5 which was fixed by using ppp (user-mode) rather than kppp (kernel-mode) for dial-up. Tim. pgpaFpIPI3Sj7.pgp Description: PGP signature
Re: KDE 3.5 Crashing
Timothy Bourke wrote: On Jun 15 at 20:01 +1000, Gemma Fletcher wrote: Installed BSD 6.2 a few days ago and am totally new to it all. I installed KDE 3.5 and it was working nicely until it juststopped. No obvious crash - it just froze. Had to reboot the system with the reset button as no other method was working. [...] Are you using dial-up with kppp? I recently saw a freeze-then-reboot under KDE 3.5 which was fixed by using ppp (user-mode) rather than kppp (kernel-mode) for dial-up. Tim. Next time instead of a reboot, try Ctrl-Alt-Backspace. that should try a shutdown of the X server ... might save you a hard reboot :) Also are you sure it's KDE? Could it be a weird video driver? Does it happen with other WMs? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 3.5 Crashing
On Jun 19 at 13:57 +1000, Timothy Bourke wrote: [...] using ppp (user-mode) rather than kppp (kernel-mode) for dial-up. To be more clear: the 'k' in kppp is for KDE, but it uses kernel mode ppp (pppd) to make the connection. Tim. pgpWjBIzhAYFN.pgp Description: PGP signature
Re: KDE 3.5 Crashing
Timothy Bourke wrote: On Jun 15 at 20:01 +1000, Gemma Fletcher wrote: Installed BSD 6.2 a few days ago and am totally new to it all. I installed KDE 3.5 and it was working nicely until it juststopped. No obvious crash - it just froze. Had to reboot the system with the reset button as no other method was working. [...] Are you using dial-up with kppp? I recently saw a freeze-then-reboot under KDE 3.5 which was fixed by using ppp (user-mode) rather than kppp (kernel-mode) for dial-up. Tim. Next time instead of a reboot, try Ctrl-Alt-Backspace. that should try a shutdown of the X server ... might save you a hard reboot :) Also are you sure it's KDE? Could it be a weird video driver? Does it happen with other WMs? Ok haven't had a chance to look at anything today (buying a new car yay me!) but just to quickly answer the above. * I'm not using dial-up at all. Cable ftw! * I tried the Ctrl-Alt-Backspace, but my keyboard doesn't seem to respond at all. It's seems about as futile as flogging a dead horse. I haven't tried any other WMs -- I went with KDE since that was the only one I had ever heard of and it had a nice install section in the handbook about it :) Could anyone suggest perhaps a different one I could try? Either way - I'll be following a the suggestions in a few previous emails about trying to isolate the problem and see where I end up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 3.5 Crashing
Hello Gemma, Hello Nikola Although it really looks like hardware, you can also do this to be 100% sure it isn't software related: (1) Had you used that computer before you have installed FreeBSD? It would be a nice idea to post here the output of your 'dmesg' or /var/log/messages. Yes it was running XP - will post output once I finalise this car sale and have a spare moment. :) (2) Have you tried to run a small script as Matthias proposed? Not yet - am reading up on how to run a script :) (3) Are you sure your ports are up-to-date? If in doubt, install ports-mgmt/portupgrade and run # portversion -v -L = To cut a long scary story short sort of. I've actually reinstalled 6.2, 4 times as I seem to have so many little things missing I wasn't sure if it was me or the install. So upgrading ports always eneded up crashing. Anyway first few times went the full install, final time went with as just a user install without X. After that i installed X and then KDE from the ports collection. Attempted a 7.2 upgrade thinking that might help a few problems and in a word - nightmare. A week later after finally getting past the libxfct step the actual upgrade crashed as it couldn't seem to create the xorg-libraries 7.2 directory. So I just decided to ignore it for a while. But aside from xorg - everything else is up to date. (4) If yes, as of how to check X without KDE, do the following: (a) run 'xinit' without ~/.xinitrc file to avoid starting KDE and or any other window manager; (once you start it, you can go back by 'exit' or Ctrl+Alt+Backspace; please note that you must put the mouse over the window in order to move focus on it); (b) check if there are warning -- (WW) -- or other suspicious messages in /var/log/Xorg.0.log; (c) while in pure xinit session, run Firefox or other application that is not KDE/Qt related; (d) run Opera, Skype or similar app that is Qt- but not KDE-related; (e) run KDE applications (Konqueror, KMail, etc.) and report one by one what happened, from (1) to (4e). Maybe it helps to isolate the problem, besides hardware tests :) Will try the above this arvo when i do the rest. Thanks heaps :) Nikola Lečić Gemma ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 3.5 Crashing
On Friday 15 June 2007 21:41, Matthias Apitz wrote: El día Friday, June 15, 2007 a las 09:33:27PM +1000, Gemma Fletcher escribió: Can you check if only X or KDE is frozen, or the system at all? Try to connect from some other host on the network. Try to do some RAM testing as well. matthias Ok my RAM is fine and dandy. I'm not sure how to check to see if only KDE is frozen. Once is freezes I can't do anything. Not even reset with ctrl-alt-del. And my keyboard usually goes dead indicated by my numlock light turning off Its just me - so I have no other host to connect from. I did notice something though that i forgot to mention- it usually only crashes if I am doing some internet related activity. Ie.Browsing, checking email, IM'ing etc If I just do normal stuff like spreadsheeting, or developing or whatever it seems to run fine. Gemma ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 3.5 Crashing
On Saturday 16 June 2007 18:54, Matthias Apitz wrote: Can you check if only X or KDE is frozen, or the system at all? Try to connect from some other host on the network. Try to do some RAM testing as well. Ok my RAM is fine and dandy. I'm not sure how to check to see if only KDE is frozen. Once is freezes I can't do anything. Not even reset with ctrl-alt-del. And my keyboard usually goes dead indicated by my numlock light turning off Its just me - so I have no other host to connect from. I did notice something You could launch some script in one of the consles (not in KDE) like: while true; do date /tmp/log ; sync ; sleep 60 ; done and when it freeze wait some fife minutes before power cycle and later check if the script continued while KDE was frozen; Ok will definatley try that. though that i forgot to mention- it usually only crashes if I am doing some internet related activity. Ie.Browsing, checking email, IM'ing etc If I just do normal stuff like spreadsheeting, or developing or whatever it seems to run fine. Is this with a Wifi card? No - although I do have a WiFi card installed that I am not using - it was from my wireless broadband days. Should i pull it out? matthias ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KDE 3.5 Crashing
Hi list :) Installed BSD 6.2 a few days ago and am totally new to it all. I installed KDE 3.5 and it was working nicely until it juststopped. No obvious crash - it just froze. Had to reboot the system with the reset button as no other method was working. So I thought it might be my sound since it wasn't configured and I had read a few things that said that sometimes caused KDE to crash. Also disabled a few buggy plugins and what not and still it keeps on freezing on me. The annoying thing is its totally random - It could be running for several hours before it freezes; and sometimes it freezes the moment I log on. Its frozen at last count 7 times today and I ended up having to do a some random hardrive check as boot up was starting to fail and logging me in as single mode user only. Anyway - to get to the point; is there a log somewhere that I can check out in console mode which incidently never crashes that might help me pinpoint the problem? Thanks in advance, Gemma ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KDE 3.5 Crashing
Edit: Resending as having problems with my mail. If it pops up twice then apologies :) Hi list :) Installed BSD 6.2 a few days ago and am totally new to it all. I installed KDE 3.5 and it was working nicely until it juststopped. No obvious crash - it just froze. Had to reboot the system with the reset button as no other method was working. So I thought it might be my sound since it wasn't configured and I had read a few things that said that sometimes caused KDE to crash. Also disabled a few buggy plugins and what not and still it keeps on freezing on me. The annoying thing is its totally random - It could be running for several hours before it freezes; and sometimes it freezes the moment I log on. Its frozen at last count 7 times today and I ended up having to do a some random hardrive check as boot up was starting to fail and logging me in as single mode user only. Anyway - to get to the point; is there a log somewhere that I can check out in console mode which incidently never crashes that might help me pinpoint the problem? Thanks in advance, Gemma ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 3.5 Crashing
El día Friday, June 15, 2007 a las 09:33:27PM +1000, Gemma Fletcher escribió: Edit: Resending as having problems with my mail. If it pops up twice then apologies :) Hi list :) Installed BSD 6.2 a few days ago and am totally new to it all. I installed KDE 3.5 and it was working nicely until it juststopped. No obvious crash - it just froze. Had to reboot the system with the reset button as no other method was working. So I thought it might be my sound since it wasn't configured and I had read a few things that said that sometimes caused KDE to crash. Also disabled a few buggy plugins and what not and still it keeps on freezing on me. The annoying thing is its totally random - It could be running for several hours before it freezes; and sometimes it freezes the moment I log on. Its frozen at last count 7 times today and I ended up having to do a some random hardrive check as boot up was starting to fail and logging me in as single mode user only. Anyway - to get to the point; is there a log somewhere that I can check out in console mode which incidently never crashes that might help me pinpoint the problem? Can you check if only X or KDE is frozen, or the system at all? Try to connect from some other host on the network. Try to do some RAM testing as well. matthias -- Matthias Apitz Manager Technical Support - OCLC PICA GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclcpica.org/ http://guru.UnixArea.de/ b http://gurucubano.blogspot.com/ OCLC PICA GmbH, Geschaeftsfuehrer: Christine Magin-Weeger, Norbert Weinberger Sitz der Gesellschaft: Oberhaching, HRB Muenchen: 113261 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
