Re: kde troubles....
On Tue, 19 Aug 2008 19:17:25 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Wed, Aug 20, 2008 at 12:59:59AM +0200, Polytropon wrote: On Mon, 18 Aug 2008 15:36:37 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 03:57 +0200, Polytropon wrote: On Sun, 17 Aug 2008 17:41:42 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 02:02 +0200, Polytropon wrote: Yes, since I need to use FreeBSD 7 after an accident destroying all my data where fsck cannot help anymore, and FreeBSD 7 and it's software does not behave the way I think it should... :-( After my Nov., 1999 disk failure, I found that my 4G tape had overwritten stuff; I lost 10 months of data files. . For me, it was July 2nd. The data is still there, but I can't access it because the inode at the entry to my home directory has died, and fsck_ffs says stupid things. :-) Can you connect with your network in any way? A couple years ago I had an Oh no situation where I figured everything was lost, but by booting single-user a network wizard somewhere nearby came by and moved /home, /etc/ and /usr/local/etc to my Ubuntu computer. It was voodoo to me. Still is. Suggest to hang on to your drive and see if there is some net-wizard nearby you. What is a net-wizard? Terminology not clear to me... I have put the original defective harddisk aside and I'm toying around (sadly, it isn't more than that) with a dd image of the partition. Some time ago, I setup a FreeBSD 7 system on another harddisk which I am using right now. So I don't have general problems, it's just... all my data (programming, photography) is lost. :-( Sometimes when I have many instantiations of kde-gnash going I grind to a crawl, then to a near halt. This is with 7.0. I didn't see that with 6.x. I'm just using plain Opera, no Flash stuff at all. I can open up eBay and middle-click some articles. Load goes up to 100% and Opera is inresponsive, up to the point when all pages have been loaded completely. Have you posted to the kernel hackers? Can you borrow someone's fast[er] hardware and duplicate your configuration? No, I don't have access to newer x86 stuff, only older stuff that runs faster (!) as I had mentioned. I cannot image this to be a kernel issue. I never had such problems from FreeBSD 4 up to 6. Maybe it's really... that my hardware is too old... Unreal! My first thought would be to check out your faster 2.0GHz hardware. I've got a CD that tests drives and said my two drives on the Dell (2.4GHz) were okay. I cannot image this to be a drive problem (see the same stuff done on the same hardware, just with different FreeBSD versions); I know gcc does optimization, and that I can't compare FreeBSD 5 to FreeBSD 7. It's just magnitudes of time consumtion that do really irritate me. But I don't mind. Runs at night, next day it's done. The make times _were_ of the 2 GHz P4 machine. It compiles FreeBSD 7 as fast as the 300 MHz P3 did with FreeBSD 5. But as an explaination for better understanding: I'm not the guy who compiles his applications day by day. I setup a system, buildworld and buildkernel with KERNCONF, then install all stuff via pkg_add -r and just compile mplayer (because of flags to be set at compile time); after this, I _never_ touch the system anymore. (Exception: Servers I do maintain get their neccessary security updates, for example for system, SSH, Apache or MySQL; portupgrade is my tool of choice there.) Is there any kind of DOS/Win tool to check the microprocessor? I don't know such tools. make buildworld usually is my choice to see if a system is okay, and memtest live CD. I'm not sure if my hardware is still Windows compatible because I've got no Windows around. It can't be fans completely, but how many do you have. No, can't, fans run fine, xmbmon shows normal values. I should buy a new computer, shouldn't I? =^_^= My 1998 Kayaks have three fans keeping the 400MHz uproc cool. Same here, too, three fans. Your data makes no sense whatsoever!! I'd like to try out what happens when I do install FreeBSD 5 again. In fact, I put in a FreeBSD 5 hard disk and... wow... how fast! I would never try this. StarOffice and OpenOffice 1 had precompiled packages for use with pkg_add -r, but this was years ago. I'm running 2.4 (I think), I only use the word-processor, and it's fine. ... . That's what I have LaTeX for. :-) But I have to admit that I did use StarOffice for some purposes, and it was a nice program. Please do keep me and the rest of the list up to date regarding your hardware problems. I hope I can find out some informations with a bit mor substance in order to formulate better questions that lead me to some advice that will change the situation. And I repeat:
Re: kde troubles....
On Wed, Aug 20, 2008 at 07:26:46PM +0200, Polytropon wrote: On Tue, 19 Aug 2008 19:17:25 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Wed, Aug 20, 2008 at 12:59:59AM +0200, Polytropon wrote: On Mon, 18 Aug 2008 15:36:37 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 03:57 +0200, Polytropon wrote: On Sun, 17 Aug 2008 17:41:42 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 02:02 +0200, Polytropon wrote: Yes, since I need to use FreeBSD 7 after an accident destroying all my data where fsck cannot help anymore, and FreeBSD 7 and it's software does not behave the way I think it should... :-( After my Nov., 1999 disk failure, I found that my 4G tape had overwritten stuff; I lost 10 months of data files. . For me, it was July 2nd. The data is still there, but I can't access it because the inode at the entry to my home directory has died, and fsck_ffs says stupid things. :-) Can you connect with your network in any way? A couple years ago I had an Oh no situation where I figured everything was lost, but by booting single-user a network wizard somewhere nearby came by and moved /home, /etc/ and /usr/local/etc to my Ubuntu computer. It was voodoo to me. Still is. Suggest to hang on to your drive and see if there is some net-wizard nearby you. What is a net-wizard? Terminology not clear to me... Sorry; my own made-up tern for someone who excels at computer networking. Such a person who be able to figure out any networking problems very quickly. I have put the original defective harddisk aside and I'm toying around (sadly, it isn't more than that) with a dd image of the partition. Some time ago, I setup a FreeBSD 7 system on another harddisk which I am using right now. So I don't have general problems, it's just... all my data (programming, photography) is lost. :-( If your original disk is in one piece, your data is there. When I was running v 5.4 some years ago FBSD suddenly hit a kernel panic. I was able to use another local server to ask for help and a network and/or kernel guy drove over, use ifconfig with a series of flags and free addresses on my 10.0.0.1 network to create a route to another server. This, of course, in single-user mode. Then he and I tarballed ans sent several dozens of megs to another server. How? I have absolutely no clue. I had to reinstall everything from my CD set and upgrade. Then moved my saved data back over. If your original drive is defective, it is time to get your data off and onto another drive. dd is a good move, if it works. Do you see any data transfered? If the disk is dead, then it probably means calling a data-recovery expert. Sometimes when I have many instantiations of kde-gnash going I grind to a crawl, then to a near halt. This is with 7.0. I didn't see that with 6.x. I'm just using plain Opera, no Flash stuff at all. I can open up eBay and middle-click some articles. Load goes up to 100% and Opera is inresponsive, up to the point when all pages have been loaded completely. Have you used other browsers? lynx or links (in graphics mode)? Have you posted to the kernel hackers? Can you borrow someone's fast[er] hardware and duplicate your configuration? No, I don't have access to newer x86 stuff, only older stuff that runs faster (!) as I had mentioned. I cannot image this to be a kernel issue. I never had such problems from FreeBSD 4 up to 6. Maybe it's really... that my hardware is too old... I seriously doubt that, since I have 7.0 running on my mail, DNS , and web server. But no X11. Unreal! My first thought would be to check out your faster 2.0GHz hardware. I've got a CD that tests drives and said my two drives on the Dell (2.4GHz) were okay. I cannot image this to be a drive problem (see the same stuff done on the same hardware, just with different FreeBSD versions); I know gcc does optimization, and that I can't compare FreeBSD 5 to FreeBSD 7. It's just magnitudes of time consumtion that do really irritate me. But I don't mind. Runs at night, next day it's done. The make times _were_ of the 2 GHz P4 machine. It compiles FreeBSD 7 as fast as the 300 MHz P3 did with FreeBSD 5. This is beyond wierd. What happens if you go back to 6.x? And use the default optimization...?? But as an explaination for better understanding: I'm not the guy who compiles his applications day by day. I setup a system, buildworld and buildkernel with KERNCONF, then install all stuff via pkg_add -r and just compile mplayer (because of flags to be set at compile time); after this, I _never_ touch the
Re: kde troubles....
On Wed, 20 Aug 2008 15:16:55 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Wed, Aug 20, 2008 at 07:26:46PM +0200, Polytropon wrote: On Tue, 19 Aug 2008 19:17:25 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Wed, Aug 20, 2008 at 12:59:59AM +0200, Polytropon wrote: On Mon, 18 Aug 2008 15:36:37 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 03:57 +0200, Polytropon wrote: On Sun, 17 Aug 2008 17:41:42 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 02:02 +0200, Polytropon wrote: Yes, since I need to use FreeBSD 7 after an accident destroying all my data where fsck cannot help anymore, and FreeBSD 7 and it's software does not behave the way I think it should... :-( After my Nov., 1999 disk failure, I found that my 4G tape had overwritten stuff; I lost 10 months of data files. . For me, it was July 2nd. The data is still there, but I can't access it because the inode at the entry to my home directory has died, and fsck_ffs says stupid things. :-) Can you connect with your network in any way? A couple years ago I had an Oh no situation where I figured everything was lost, but by booting single-user a network wizard somewhere nearby came by and moved /home, /etc/ and /usr/local/etc to my Ubuntu computer. It was voodoo to me. Still is. Suggest to hang on to your drive and see if there is some net-wizard nearby you. What is a net-wizard? Terminology not clear to me... Sorry; my own made-up tern for someone who excels at computer networking. Such a person who be able to figure out any networking problems very quickly. I have put the original defective harddisk aside and I'm toying around (sadly, it isn't more than that) with a dd image of the partition. Some time ago, I setup a FreeBSD 7 system on another harddisk which I am using right now. So I don't have general problems, it's just... all my data (programming, photography) is lost. :-( If your original disk is in one piece, your data is there. Yes, but inaccessible. I do claim yes, it is because I could examine the filesystem's dd image with the fsdb tool. Furthermore, I tried a trial version of a Windows recovery program under wine. It showed that some of the files are still there. My wish is that I get fsck to restore the hierarchy within my home directory into lost+found/, while 1st instance entries surely will have their (lost) names replaced by the respective inode number, but that's no big deal (thanks to the file command). When I was running v 5.4 some years ago FBSD suddenly hit a kernel panic. I was able to use another local server to ask for help and a network and/or kernel guy drove over, use ifconfig with a series of flags and free addresses on my 10.0.0.1 network to create a route to another server. This, of course, in single-user mode. Then he and I tarballed ans sent several dozens of megs to another server. How? I have absolutely no clue. I had to reinstall everything from my CD set and upgrade. Then moved my saved data back over. Well, this is an obvious solution if you can access your data but have problems with the system's startup. SUM is sufficient to establish a network connection as a means to transfer the data off the disk; another means would be to mount the disk inside another running FreeBSD system. If your original drive is defective, it is time to get your data off and onto another drive. The drive isn't defective. After the surprise crash is behaves completely normal. But that's not interesting because I don't use this drive, I only would access it if I needed another dd image of the partition - it's just easier to deal with the image than with the physical disk. dd is a good move, if it works. It does, and, most interesting, it replicates the error (the lost inode entry) from the original partition. Do you see any data transfered? I could move all home directories (of the other users) and the archive directory from this partition. From the other partitions I could copy the important parts of the system configuration and proprietary service programs. The only thing that's not accessible due to the defective inode entry is my own home directory. If the disk is dead, then it probably means calling a data-recovery expert. I'm glad I don't see a need for this at the moment. Well, this may be a strange confession, but having used FreeBSD since 4.0 should have put me into the state of being able to solve this problem on my own, but sadly, I'm not. Too diffuse, too complicated. Different fsck_ffs versions with different errors. Sometimes when I have many instantiations of kde-gnash going I grind to a crawl, then to a near halt. This is with 7.0. I
Re: kde troubles....
On Mon, 18 Aug 2008 03:57:32 +0200 Polytropon [EMAIL PROTECTED] wrote: In the good old times, you could update your applications and they ran faster on the same hardware. That's what I've loved FreeBSD for. Today, the applications run slower after every update, so I have to update my hardware in order to just keep the speed? http://en.wikipedia.org/wiki/Wirth's_law ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde troubles....
On Mon, 18 Aug 2008 15:36:37 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 03:57 +0200, Polytropon wrote: On Sun, 17 Aug 2008 17:41:42 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 02:02 +0200, Polytropon wrote: Yes, since I need to use FreeBSD 7 after an accident destroying all my data where fsck cannot help anymore, and FreeBSD 7 and it's software does not behave the way I think it should... :-( After my Nov., 1999 disk failure, I found that my 4G tape had overwritten stuff; I lost 10 months of data files. . For me, it was July 2nd. The data is still there, but I can't access it because the inode at the entry to my home directory has died, and fsck_ffs says stupid things. :-) Are you using gcc 4.3 with -O3? % cc --version cc (GCC) 4.2.1 20070719 [FreeBSD] I have noticed that 4.3 generates faster binaries. Well, I don't care if buildworld lasts 3, 4 or 5 hours, but 9 hours? With FreeBSD 5, everything went fine, but as I am using FreeBSD 7 now, things seem (!) to run much slower. Opera does 100% CPU load, the USB keyboard is detected minutes after startup, the duplex printer does not print duplex anymore... In the good old times, you could update your applications and they ran faster on the same hardware. That's what I've loved FreeBSD for. Today, the applications run slower after every update, so I have to update my hardware in order to just keep the speed? Sounds like DOS/Windows. Bah, that's why I'm using FreeBSD - to benefit from the speed improvements in the same (!) hardware. Sadly, this doesn't seem to be true anymore...? Every new release, Intel counts up its $billions in faster uprocessors. With our stuff, it may be X11 and possibly sloppy hacking. I can't tell since I just gave away my old 750MHz for a 2.4GHz Dell. I may tell this: My 300 MHz P2 runs faster than my 2000 MHz P4! And I won't buy any new stuff as long as the old one is working well, just to keep the same speed? Wrong universe. Something must be wrong here... Examples, please? ball-park [estimates] for times are okay. On FreeBSD 7 before and after update (RVS is a custom kernel): # time make buildkernel KERNCONF=RVS 3289.368u 529.669s 1:05:25.90 97.2% -4998+1011k 594+1344io 19pf+0w 3503.732u 524.399s 1:11:05.53 94.4% -4434+1071k 15322+1391io 363pf+0w # time make buildworld 11457.047u 2151.158s 3:54:15.31 96.8% -151+1107k 23315+5217io 2542pf+0w # time make installkernel KERNCONF=RVS 17.396u 12.587s 0:46.89 63.9% 392+738k 5+1213io 248pf+0w # time make buildworld buildkernel KERNCONF=RVS -DUSBDEBUG 16574.070u 2516.128s 6:06:03.90 86.9% -191+-1116k 33078+6212io 3131pf+0w # time make buildkernel KERNCONF=RVS -D USBDEBUG 4032.019u 572.636s 1:58:29.08 64.7% -2702+1072k 14386+1288io 366pf+0w # time make buildkernel KERNCONF=RVS -D USBDEBUG 18232.967u 2427.404s 7:19:49.24 78.2% 391+379k 47250+5754io 3049pf+0w # time make installkernel KERNCONF=RVS 18.890u 12.131s 1:11.85 43.1% 412+2177k 2908+2267io 1597pf+0w # time make buildworld buildkernel KERNCONF=RVS 18992.839u 2569.146s 9:12:00.28 65.1% 927+762k 25593+6358io 2506pf+0w On FreeBSD 5 with the same hardware configuration: With CPUFLAGS: # make buildworld buildkernel KERNCONF=wega 17494.415u 2562.134s 5:46:42.25 96.4% -698+-372k 43107+2928io 2827pf+0w Without CPUFLAGS: # make buildworld buildkernel KERNCONF=wega 17474.169u 2481.368s 5:46:30.40 95.9% -1038+-774k 39520+2905io 2595pf+0w # make buildkernel KERNCONF=wega 2326.380u 234.457s 43:42.15 97.6% 1183+1677k 3176+188io 112pf+0w /usr/ports# portupgrade XFree86-Server 332.595u 82.812s 2:12:18.97 5.2%172+637k 2631+391io 550pf+0w /usr/ports/x11-servers/driglide# make install clean 333.174u 82.905s 7:06.14 97.6% 961+1097k 575+30io 156pf+0w /usr/ports/multimedia/mplayer# time make WITH_SDL=yes WITH_VORBIS=yes WITH_XANIM=yes WITH_REALPLAYER=yes WITH_LIVEMEDIA=yes WITH_XANIM=yes WITH_REALPLAYER=yes WITH_LIVEMEDIA=yes WITH_OPTIMIZED_CFLAGS=yes WITHOUT_RUNTIME_CPUDETECTION=yes HAVE_GNOME=no CFLAGS=-O3 -pipe -ffast-math install clean 3622.758u 602.146s 1:19:43.90 88.3% 1243+2304k 1424+1448io 915pf+0w # make buildworld buildkernel 5608.712u 1595.130s 2:13:18.67 90.0%-2759+2043k 33442+2608io 15274pf+0w # make buildworld 5086.993u 1431.086s 1:58:16.33 91.8%-2924+2023k 44932+2512io 3939pf+0w # make buildkernel KERNCONF 1102.491u 278.194s 25:18.58 90.9% 3629+1716k 4965+669io 193pf+0w # make buildkernel KERNCONF 1182.203u 294.622s 26:12.71 93.9%
Re: kde troubles....
On Wed, Aug 20, 2008 at 12:59:59AM +0200, Polytropon wrote: On Mon, 18 Aug 2008 15:36:37 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 03:57 +0200, Polytropon wrote: On Sun, 17 Aug 2008 17:41:42 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 02:02 +0200, Polytropon wrote: Yes, since I need to use FreeBSD 7 after an accident destroying all my data where fsck cannot help anymore, and FreeBSD 7 and it's software does not behave the way I think it should... :-( After my Nov., 1999 disk failure, I found that my 4G tape had overwritten stuff; I lost 10 months of data files. . For me, it was July 2nd. The data is still there, but I can't access it because the inode at the entry to my home directory has died, and fsck_ffs says stupid things. :-) Can you connect with your network in any way? A couple years ago I had an Oh no situation where I figured everything was lost, but by booting single-user a network wizard somewhere nearby came by and moved /home, /etc/ and /usr/local/etc to my Ubuntu computer. It was voodoo to me. Still is. Suggest to hang on to your drive and see if there is some net-wizard nearby you. Are you using gcc 4.3 with -O3? % cc --version cc (GCC) 4.2.1 20070719 [FreeBSD] I have noticed that 4.3 generates faster binaries. Well, I don't care if buildworld lasts 3, 4 or 5 hours, but 9 hours? With FreeBSD 5, everything went fine, but as I am using FreeBSD 7 now, things seem (!) to run much slower. Opera does 100% CPU load, the USB keyboard is detected minutes after startup, the duplex printer does not print duplex anymore... Sometimes when I have many instantiations of kde-gnash going I grind to a crawl, then to a near halt. This is with 7.0. I didn't see that with 6.x. In the good old times, you could update your applications and they ran faster on the same hardware. That's what I've loved FreeBSD for. Today, the applications run slower after every update, so I have to update my hardware in order to just keep the speed? Sounds like DOS/Windows. Bah, that's why I'm using FreeBSD - to benefit from the speed improvements in the same (!) hardware. Sadly, this doesn't seem to be true anymore...? Every new release, Intel counts up its $billions in faster uprocessors. With our stuff, it may be X11 and possibly sloppy hacking. I can't tell since I just gave away my old 750MHz for a 2.4GHz Dell. I may tell this: My 300 MHz P2 runs faster than my 2000 MHz P4! And I won't buy any new stuff as long as the old one is working well, just to keep the same speed? Wrong universe. Something must be wrong here... Have you posted to the kernel hackers? Can you borrow someone's fast[er] hardware and duplicate your configuration? Examples, please? ball-park [estimates] for times are okay. On FreeBSD 7 before and after update (RVS is a custom kernel): # time make buildkernel KERNCONF=RVS 3289.368u 529.669s 1:05:25.90 97.2% -4998+1011k 594+1344io 19pf+0w 3503.732u 524.399s 1:11:05.53 94.4% -4434+1071k 15322+1391io 363pf+0w # time make buildworld 11457.047u 2151.158s 3:54:15.31 96.8% -151+1107k 23315+5217io 2542pf+0w # time make installkernel KERNCONF=RVS 17.396u 12.587s 0:46.89 63.9% 392+738k 5+1213io 248pf+0w # time make buildworld buildkernel KERNCONF=RVS -DUSBDEBUG 16574.070u 2516.128s 6:06:03.90 86.9% -191+-1116k 33078+6212io 3131pf+0w # time make buildkernel KERNCONF=RVS -D USBDEBUG 4032.019u 572.636s 1:58:29.08 64.7% -2702+1072k 14386+1288io 366pf+0w # time make buildkernel KERNCONF=RVS -D USBDEBUG 18232.967u 2427.404s 7:19:49.24 78.2% 391+379k 47250+5754io 3049pf+0w # time make installkernel KERNCONF=RVS 18.890u 12.131s 1:11.85 43.1% 412+2177k 2908+2267io 1597pf+0w # time make buildworld buildkernel KERNCONF=RVS 18992.839u 2569.146s 9:12:00.28 65.1% 927+762k 25593+6358io 2506pf+0w On FreeBSD 5 with the same hardware configuration: With CPUFLAGS: # make buildworld buildkernel KERNCONF=wega 17494.415u 2562.134s 5:46:42.25 96.4% -698+-372k 43107+2928io 2827pf+0w Without CPUFLAGS: # make buildworld buildkernel KERNCONF=wega 17474.169u 2481.368s 5:46:30.40 95.9% -1038+-774k 39520+2905io 2595pf+0w # make buildkernel KERNCONF=wega 2326.380u 234.457s 43:42.15 97.6% 1183+1677k 3176+188io 112pf+0w /usr/ports# portupgrade XFree86-Server 332.595u 82.812s 2:12:18.97 5.2%172+637k 2631+391io 550pf+0w /usr/ports/x11-servers/driglide# make install clean 333.174u 82.905s 7:06.14 97.6% 961+1097k 575+30io 156pf+0w
Re: kde troubles....
On Mon, 2008-08-18 at 03:57 +0200, Polytropon wrote: On Sun, 17 Aug 2008 17:41:42 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 02:02 +0200, Polytropon wrote: Yes, since I need to use FreeBSD 7 after an accident destroying all my data where fsck cannot help anymore, and FreeBSD 7 and it's software does not behave the way I think it should... :-( After my Nov., 1999 disk failure, I found that my 4G tape had overwritten stuff; I lost 10 months of data files. . i know the feeling. It's not that I want to complain, I'll stay with FreeBSD, I'm just a little upset. Things behave much slower, allthough the system boots faster. X and the applications seem to eat up every bit of performance boost the new OS gave them. Are you using gcc 4.3 with -O3? I have noticed that 4.3 generates faster binaries. Still, I cringe with 7.0. I haven't tried to compute the 7th root of infinity yet, :-) ... . In the good old times, you could update your applications and they ran faster on the same hardware. That's what I've loved FreeBSD for. Today, the applications run slower after every update, so I have to update my hardware in order to just keep the speed? Sounds like DOS/Windows. Every new release, Intel counts up its $billions in faster uprocessors. With our stuff, it may be X11 and possibly sloppy hacking. I can't tell since I just gave away my old 750MHz for a 2.4GHz Dell. (Off topic, sorry.) xdm works very well, but only tried logging in as root. missing .xsession and .ctwmrc that i used more many, Many years. i'll tell you, after using FBSD since 2.0.5, i'm ready to give omething prepackaged a try. The only things I do compile is wirld, kernel, and mplayer. For everything else, pkg_add -r is very welcome. By the way, compiling lasts much longer in FreeBSD 7. I think this is due to more optimization, but from 1 to 9 hours... what's wrong here?! Examples, please? ball-park [estimates] for times are okay. The worst ting for me is re-compiling OO Of course, xdm won't give you the functionality that kdm offers. A nice replacement for xdm, by the way, is wdm, which you can use together with Windowmaker, but without it, too. Especially if you want to use different window managers, wdm allows a simple means to switch them at login time. Ah, you may be the perfect man to ask about this multi-wm launch daemon. I saw it once a long, long time ago. I would really like to try different window managers. I used ctwm for Years, but that sseemed to limit my use of certain apps. Mostly in the Gnome/KDE world. S, bit bit bit I got used to the default gnome desktop/wm on my Ubuntu computer. I wound up trying KDE and used it until it finally broke after a power surge or power-out. What are your top w managers? To the LIST: I found my missing .xinitrc. but now my .xsession file is gone. This is my ~/.xsession: It allows sourcing of the settings from ~/.cshrc (because the C shell is my usual dialog shell) and then executes ~/.xinitrc: #!/bin/csh source ~/.cshrc exec ~/.xinitrc So you can keep all your settings in ~/.xinitrc, for example: #!/bin/sh xmodmap ~/.xmodmaprc xsetroot -solid rgb:3b/4c/7a xset b 100 1000 15 xset r rate 250 30 xset s off xset -dpms exec wmaker Both files are +x attributes. o I'll try your startup config, thanks. Sometimes I'll get up but my xmodmap never touch my rc file; bothers me. going to reboot after rm'ing kdm.pid. You should be able to restart kdm from the console, but I think your setting includes automatic kdm start after system startup, controlled by /etc/ttys. Right. There is a way of havving gnome boot into graphics mode, but since I'm a CLI type except for Xterms , I like to see the console. The portupgrade finished; time to reboot and see if that fixed anything. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde troubles....
Gary Kline wrote: AFter a power glitch last night I was able to relogin as room, but # kdm fails with the error: can't create /var/run/kdm.pid. Try deleting that file and reboot if you are starting kdm in ttys. If that by itself doesn't work there are a number of other files to clean as well, but they don't come into play until after kdm is running and you are attempting to start a KDE session as a particular user. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde troubles....
On Sun, 17 Aug 2008 15:04:34 -0700, Gary Kline [EMAIL PROTECTED] wrote: AFter a power glitch last night I was able to relogin as room, but # kdm fails with the error: can't create /var/run/kdm.pid. I check that file and, yup, it's there. Maybe removing this PID file and retrying to start kdm should solve the problem? It is possible that kdm refuses to start while this file is present (and kdm is guessing that another kdm instance is running already). -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde troubles....
On Sun, Aug 17, 2008 at 06:12:27PM -0400, Michael Powell wrote: Gary Kline wrote: AFter a power glitch last night I was able to relogin as room, but # kdm fails with the error: can't create /var/run/kdm.pid. Try deleting that file and reboot if you are starting kdm in ttys. If that by itself doesn't work there are a number of other files to clean as well, but they don't come into play until after kdm is running and you are attempting to start a KDE session as a particular user. nojoy. the err message is gone, but KDE creates an /rmpty kdm.pid and does nothing. stdout says Information: reading current kdmrc . \n and then: Infirmation: current kdmrc is from kde 3.1 . Nothing else; what else neeeds cleaning? thanks. gary -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Gary Kline [EMAIL PROTECTED] http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde troubles....
On Mon, Aug 18, 2008 at 12:14:26AM +0200, Polytropon wrote: On Sun, 17 Aug 2008 15:04:34 -0700, Gary Kline [EMAIL PROTECTED] wrote: AFter a power glitch last night I was able to relogin as room, but # kdm fails with the error: can't create /var/run/kdm.pid. I check that file and, yup, it's there. Maybe removing this PID file and retrying to start kdm should solve the problem? It is possible that kdm refuses to start while this file is present (and kdm is guessing that another kdm instance is running already). danke, uber nien.[1] if you see my reply to Mike Power, that's a no-go. I tried to get KDE up hours ago, but after failing, thought I'd try building kde4, ja? nope. that bombed somewhere while I was getting stuff done on my ubuntu desktop. ever have the urge to put your fist thru the CRT? (*) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] [1] how fractured is that!? -- Gary Kline [EMAIL PROTECTED] http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde troubles....
On Sun, 17 Aug 2008 16:30:07 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, Aug 18, 2008 at 12:14:26AM +0200, Polytropon wrote: Maybe removing this PID file and retrying to start kdm should solve the problem? It is possible that kdm refuses to start while this file is present (and kdm is guessing that another kdm instance is running already). danke, uber nien.[1] [1] how fractured is that!? I thinks it's danke, aber nein. if you see my reply to Mike Power, that's a no-go. The PID file should not be empty, it should contain the PID of kdm as text. Another problem seems to be that the kdm from KDE 4 does need a different configuration file than KDE 3... maybe you can remove / rename version 3 of the file and see if there are any defaults for version 4, eventually generated automatically? I tried to get KDE up hours ago, but after failing, thought I'd try building kde4, ja? nope. Eventually testing xdm instead of kdm - just to see if this one is working - would be a first step. I'm no KDE user, so I'm sorry I can't help any more. that bombed somewhere while I was getting stuff done on my ubuntu desktop. If you use precompiled packages, there should not be a problem. If you're interested in a preconfigured and working KDE and you don't mind that it's KDE 3 on a FreeBSD 6 system, why not try PC-BSD or DesktopBSD? ever have the urge to put your fist thru the CRT? (*) Yes, since I need to use FreeBSD 7 after an accident destroying all my data where fsck cannot help anymore, and FreeBSD 7 and it's software does not behave the way I think it should... :-( -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde troubles....
Gary Kline wrote: [snip] the err message is gone, but KDE creates an /rmpty kdm.pid and does nothing. This is not good. The file should contain a number. [snip] It would also be helpful to know how you are trying to run KDE. There are two ways, the first being to have a line like: ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure in /etc/ttys which starts kdm as a graphical login at boot. The other is to boot and login as user, then do the startx command which needs startkde to be in .xinitrc and/or .xsession in your Home directory. Nothing else; what else neeeds cleaning? Not sure what got munged with your power glitch, but a couple of times in the past when I've had trouble getting KDE to start I would login as root (or su) without X running and delete some stuff. Look in your user home directory for something like .DCOPserver_hostname_:0; there will be two - one is a link to the other. Delete both of these and delete the ksocket-yourusername folder in /tmp. Also while in /tmp look for .X0-lock and delete. Look for the folders .ICE-unix and .X11-unix and delete all the sockets you find in these two folders. Make note both of these folders should have the sticky bit set. Also delete the /var/run/kdm.pid again like before. This is how I've gotten KDE to start in the past after an uh-oh. It also may not pertain to your particular situation. One thing you can do to troubleshoot X if you are using startx (ie not starting kdm at login with the ttys line above) is to have an empty .xinitrc and/or .xsession. Then when you run X the twm window manager should come up, as it is the default for X. This way you can drive a wedge between Is it an X problem or a KDE problem? Good luck and I hope you get it going. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde troubles....
On Mon, 2008-08-18 at 02:02 +0200, Polytropon wrote: On Sun, 17 Aug 2008 16:30:07 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, Aug 18, 2008 at 12:14:26AM +0200, Polytropon wrote: Maybe removing this PID file and retrying to start kdm should solve the problem? It is possible that kdm refuses to start while this file is present (and kdm is guessing that another kdm instance is running already). danke, uber nien.[1] [1] how fractured is that!? I thinks it's danke, aber nein. if you see my reply to Mike Power, that's a no-go. The PID file should not be empty, it should contain the PID of kdm as text. Another problem seems to be that the kdm from KDE 4 does need a different configuration file than KDE 3... maybe you can remove / rename version 3 of the file and see if there are any defaults for version 4, eventually generated automatically? I tried to get KDE up hours ago, but after failing, thought I'd try building kde4, ja? nope. Eventually testing xdm instead of kdm - just to see if this one is working - would be a first step. I'm no KDE user, so I'm sorry I can't help any more. that bombed somewhere while I was getting stuff done on my ubuntu desktop. If you use precompiled packages, there should not be a problem. If you're interested in a preconfigured and working KDE and you don't mind that it's KDE 3 on a FreeBSD 6 system, why not try PC-BSD or DesktopBSD? ever have the urge to put your fist thru the CRT? (*) Yes, since I need to use FreeBSD 7 after an accident destroying all my data where fsck cannot help anymore, and FreeBSD 7 and it's software does not behave the way I think it should... :-( i know the feeling. xdm works very well, but only tried logging in as root. missing .xsession and .ctwmrc that i used more many, Many years. i'll tell you, after using FBSD since 2.0.5, i'm ready to give omething prepackaged a try. To the LIST: I found my missing .xinitrc. but now my .xsession file is gone. . going to reboot after rm'ing kdm.pid. . ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde troubles....
On Sun, 17 Aug 2008 17:41:42 -0700, Gary Kline [EMAIL PROTECTED] wrote: On Mon, 2008-08-18 at 02:02 +0200, Polytropon wrote: Yes, since I need to use FreeBSD 7 after an accident destroying all my data where fsck cannot help anymore, and FreeBSD 7 and it's software does not behave the way I think it should... :-( i know the feeling. It's not that I want to complain, I'll stay with FreeBSD, I'm just a little upset. Things behave much slower, allthough the system boots faster. X and the applications seem to eat up every bit of performance boost the new OS gave them. In the good old times, you could update your applications and they ran faster on the same hardware. That's what I've loved FreeBSD for. Today, the applications run slower after every update, so I have to update my hardware in order to just keep the speed? (Off topic, sorry.) xdm works very well, but only tried logging in as root. missing .xsession and .ctwmrc that i used more many, Many years. i'll tell you, after using FBSD since 2.0.5, i'm ready to give omething prepackaged a try. The only things I do compile is wirld, kernel, and mplayer. For everything else, pkg_add -r is very welcome. By the way, compiling lasts much longer in FreeBSD 7. I think this is due to more optimization, but from 1 to 9 hours... what's wrong here?! Of course, xdm won't give you the functionality that kdm offers. A nice replacement for xdm, by the way, is wdm, which you can use together with Windowmaker, but without it, too. Especially if you want to use different window managers, wdm allows a simple means to switch them at login time. To the LIST: I found my missing .xinitrc. but now my .xsession file is gone. This is my ~/.xsession: It allows sourcing of the settings from ~/.cshrc (because the C shell is my usual dialog shell) and then executes ~/.xinitrc: #!/bin/csh source ~/.cshrc exec ~/.xinitrc So you can keep all your settings in ~/.xinitrc, for example: #!/bin/sh xmodmap ~/.xmodmaprc xsetroot -solid rgb:3b/4c/7a xset b 100 1000 15 xset r rate 250 30 xset s off xset -dpms exec wmaker Both files are +x attributes. going to reboot after rm'ing kdm.pid. You should be able to restart kdm from the console, but I think your setting includes automatic kdm start after system startup, controlled by /etc/ttys. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde troubles....
On Sun, 2008-08-17 at 20:17 -0400, Michael Powell wrote: Gary Kline wrote: [snip] the err message is gone, but KDE creates an /rmpty kdm.pid and does nothing. This is not good. The file should contain a number. [snip] It would also be helpful to know how you are trying to run KDE. There are two ways, the first being to have a line like: ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure in /etc/ttys which starts kdm as a graphical login at boot. The other is to boot and login as user, then do the startx command which needs startkde to be in .xinitrc and/or .xsession in your Home directory. i do not have KDE start by /etc/ttys; i start it as root via kdm. i just tried startxx and have my KDE env back up. i have many many more spps that i had thought; will axe most. the thing of note is that as root, startx splat a screen full of X11 errors that prob'ly are meaningful to X11 wizards. it looked like there were two or more illegal actions... is there any way of my capturing the output and posting it to the list ? Nothing else; what else neeeds cleaning? Not sure what got munged with your power glitch, but a couple of times in the past when I've had trouble getting KDE to start I would login as root (or su) without X running and delete some stuff. Look in your user home directory for something like .DCOPserver_hostname_:0; there will be two - one is a link to the other. Delete both of these and delete the ksocket-yourusername folder in /tmp. Also while in /tmp look for .X0-lock and delete. Look for the folders .ICE-unix and .X11-unix and delete all the sockets you find in these two folders. Make note both of these folders should have the sticky bit set. Also delete the /var/run/kdm.pid again like before. This is how I've gotten KDE to start in the past after an uh-oh. It also may not pertain to your particular situation. One thing you can do to troubleshoot X if you are using startx (ie not starting kdm at login with the ttys line above) is to have an empty .xinitrc and/or .xsession. Then when you run X the twm window manager should come up, as it is the default for X. This way you can drive a wedge between Is it an X problem or a KDE problem? o xdm by itsekf brings up root; startx with startkde brings up kde. For reasons beyond me, kdm balks at creating /var/run/kdm.pid. Oh, and since I did a complete portupgrade recently, I did an X -configure and am now using the new xorg.conf. thanks much. time to call it a century! gary Good luck and I hope you get it going. -Mike ___ 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]
