July 2001 - openSUSE Users - openSUSE Mailing Lists

um, ignore previous message
by Bob Rea 01 Jul '01

01 Jul '01

Sorry i suddenly realized,where the menus were and turned off the macos menu seting <blush /> -- Bob Rea Fear of Hell is pernicious; So is fear of Heaven. rear(a)sirius.com http://www.sirius.com/~rear

1 0

upgraded, where are the menus in apps
by Bob Rea 01 Jul '01

01 Jul '01

I upgraded from 7.1 to 7.2. Apps, such as kmail no longer have menubars. How so I get them back? I have been poking aorund the KDE control center but I can't see the place to change this. -- Bob Rea Fear of Hell is pernicious; So is fear of Heaven. rear(a)sirius.com http://www.sirius.com/~rear

1 0

Fixed! -> Re: [SLE] gcc?? / kernel compile issues
by Ambrosius 01 Jul '01

01 Jul '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 25 June 2001 02:11, you ( Mads Martin Jørgensen ) wrote: > * Ambrosius <ambrosius(a)mailandnews.com> [Jun 25. 2001 00:07]: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Sunday 24 June 2001 22:55, you ( Mads Martin Jørgensen ) wrote: > > I can't even do a make xconfig! > > ======================================== > > Well here's the last few lines after make xconfig: > > > > root@jezebelle:/usr/src/linux-2.4.5 > make xconfig > > rm -f include/asm > > ( cd include ; ln -sf asm-i386 asm) > > make -C scripts kconfig.tk > > make[1]: Entering directory `/usr/src/linux-2.4.5/scripts' > > cat header.tk >> ./kconfig.tk > > ./tkparse < ../arch/i386/config.in >> kconfig.tk > > echo "set defaults \"arch/i386/defconfig\"" >> kconfig.tk > > echo "set ARCH \"i386\"" >> kconfig.tk > > cat tail.tk >> kconfig.tk > > chmod 755 kconfig.tk > > make[1]: Leaving directory `/usr/src/linux-2.4.5/scripts' > > wish -f scripts/kconfig.tk > > Xlib: connection to ":0.0" refused by server > > Xlib: Invalid MIT-MAGIC-COOKIE-1 key > > Application initialization failed: couldn't connect to display ":0.0" > > Error in startup script: invalid command name "button" > > while executing > > "button .ref" > > (file "scripts/kconfig.tk" line 51) > > make: *** [xconfig] Error 1 > > Try doing a 'make menuconfig' in a shell instead. If you really want > the xconfig remember to export the display correctly, and allow the > connection on user side. Found the problem. folks figured I'd respond to list (never hurts to have it on the archives). Turns out I had two problems: 1. BIOS Flash to a unstable version. (seems the bios file 6vx7-4x.f38 has some issues) 2. Mismatched RAM modules. (I yanked mods out of my machine and used my wife's as a test bench). After putting one of these modules in her machine and putter her's in mine I could compile the kernel with one bombout. So I booted to windoze (shiver) and flashed to older bios revision... Since then it's been ok, and my CPU temp has dropped down off the 80+ level too. After a fresh compile and an immediate reboot to enter BIOS and check temp there it was a full 20 degress cooler. Now I know that some would drop because the proc was no longer under load, but bear in mind this is in comparison to same sequence with bios f38. I've sent emails to gigabyte but no response. (shrug). Thanks for your help in this matter guys, it's appreciated :-) Next task: Is there a way to make the nvidia 1251 drivers run under mantel's 2.4.5 kernel? What am I missing? THey even bomb in my vanilla compile too. Any thoughts? Danke' Ambrosius - -- ¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ??????????????????????????????? Name: Harold aka "Ambrosius" Email: ambrosius(a)mailandnews.com (L)ICQ Number: 117212600 Distro: SuSE Linux 7.1 Pro Registered Linux User: 216397 ¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ??????????????????????????????? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7OdIz1UIAeY3WgCcRArNfAKCTAlRT3Nej2FoYaOUl5MSiEZbAFQCgnwBw sHPGk9e3iaPk8SJvbYADHGY= =xWX7 -----END PGP SIGNATURE-----

3 4

Re: [SLE] yast2 problem in stock 7.2 Pro ?
by W. D. McKinney 01 Jul '01

01 Jul '01

Thanks.... I forgot about this :-) Regards /Dee * Anders Johansson <andjoh(a)cicada.linux-site.net> [Jun 30. 2001 18:40]: > You're logged on as deem, but running yast2 as root. X will prevent you from > this. As user deem do > > xhost +inet:localhost > > to let local users connect to the running X server. > > X will always prevent people other than the one who started it from > connecting to it, unless you do the above > > Regards > Anders > > On Sunday 01 July 2001 04:34, you wrote: > > Thought I'd try yast2 on my testbox for 7.2 : > > > > root@papa:/home/deem > yast2 > > Xlib: connection to ":0.0" refused by server > > Xlib: Invalid MIT-MAGIC-COOKIE-1 key > > y2controlcenter: cannot connect to X server :0.0 > > > > What's this problem ? > > > > /Dee

1 0

yast2 problem in stock 7.2 Pro ?
by W. D. McKinney 01 Jul '01

01 Jul '01

Thought I'd try yast2 on my testbox for 7.2 : root@papa:/home/deem > yast2 Xlib: connection to ":0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key y2controlcenter: cannot connect to X server :0.0 What's this problem ? /Dee

2 1

Fwd: KOffice Review: KWord
by Jonathan Drews 01 Jul '01

01 Jul '01

For the SuSE list members here is a very nice overview of Koffice's Kword. ---------- Forwarded Message ---------- Subject: KOffice Review: KWord Date: Sat, 30 Jun 2001 17:38:16 +0000 From: Kent Nguyen <kent(a)mslinux.com> To: KDE User List <kde-user(a)lists.netcentral.net> Hi guys, I finished up the first part of my KOffice review: KWord. If you're interested you can read all about KWord here: http://www.mslinux.com/reviews/koffice.html KWord is a frame and component based word processor. One of its kind to date. It a good design: doc/view model and an excellent team. -- Cheers, Jonathan

2 1

SuSE 7.2 installation woes
by Rachel Greenham 01 Jul '01

01 Jul '01

... I think I've got it working now though. But it seems overall to have been a rather more painful experience than I had installing 7.1 on the same machines. Firstly, I installed it on my ageing Pico Consul laptop. That went off without a hitch, ironically enough. Then today I installed it on a new Athlon 1.33 / Via KT133A system. Now, although I had a fairly clean SuSE 7.1 system on there, I've got into the habit of always installing from scratch rather than performing upgrades. It's just my way, I don't trust upgrading, I've seen some pretty insane machines that are the result of that, and anyway it gives me a chance to spring-clean. So... The first problem is that Yast2 wouldn't recognise the mouse. It's a Logitech Pilot Wheel Mouse plugged in via USB. SuSE 7.1 not only worked with it, but installed right out of the box with it. However, with SuSE 7.2, it just wouldn't see it. I dug out the adapter to plug it into the PS/2 port instead, rebooted etc., but it still wouldn't see the mouse. So for a bit I tried to continue anyway with Yast2 using the keyboard. This progressed until I asked it I wanted to use the whole disk (as partitioned by SuSE 7.1). This as you know selects all the partitions on the disk for deletion. Only Yast2 insisted that these partitions were not contiguous and so refused to go any further. So I installed using Yast1. This more or less went off without a hitch, while nevertheless being a reminder of more primitive times :-). The most annoying thing here was that it asked me to configure gpm before having started the USB manager service, so of course it still wouldn't see my USB mouse. So, let it finish and do it then, no problems. sax2 configured X (with the USB mouse) no problems. This is in contrast to my laptop where I had no end of problems getting sax2 to run itself on my S3Virge-MX+. "sax2 -m 0=vga" did it in the end. I got some minor screen corruption on the framebuffer console with my Voodoo 3 card, but thought little of it. It seems to take a long time to switch VC from the console to X when framebuffer console is enabled. Minor gripes: Yast2 doesn't show package version numbers Yast1 doesn't any longer show package file lists. Why do SuSE have the X and KDE2 upgrades separate from the main updates directory? I'd love to just point YOU at it and go, but as it is, I have to use Yast1 and pick them out from all over. Further problems are nothing to do with SuSE: I was building my own kernel from vanilla-2.4.5 so I can have it built for Athlon rather than Pentium and cut out a lot of the irrelevant stuff This is all basically OK, I'm now used to the various things I need to make sure I'm doing to keep the SuSE scripts etc. happy (build this and that as a module, that sort of thing). My problems continued to be with the framebuffer console. Firstly, I compiled in the specific 3dfx/Voodoo3 fbdev support, but that didn't work at all - didn't crash, just didn't show anything until kdm started. Recompiled with that out, and just VESA fb support in, and it seemed at first to be fine, but then I started to see the same sort of display corruption I'd seen briefly on the SuSE kernel. (I may have been optimistic to tell it to use VESA mode 795 (1280x1024x24bit)) Then it got markedly worse and wouldn't even switch to X properly - basically I think the Voodoo3 card itself crashed - the machine was fine, I could log on and recover and reboot from the laptop. Rebuild the kernel again with no framebuffer console support at all, and put "vga=normal" in /etc/lilo.conf and sanity is restored. (Though I quite *like* having big consoles from time to time.) So I think there are some Issues regarding using Framebuffer Console on the Voodoo3 card. Conversely, this also works fine on my laptop, set rather more conservatively to VESA mode 773 (1024x768x8bit). In fact, as the laptop has a propensity to crash when in VGA text mode (never in X which leads me to suspect dodgy BIOS issues), I specifically wanted to try fb-console. I haven't been using it long enough like that yet to know if it works. -- Rachel

1 0