AArgghh !! Oh... I feel much better now :) Probably best to include the full saga here so that someone might be able to help. Recently my 32-bit hardware died due to old age. The 1.2 Ghz Athlon just couldn't make it through the day any more. I had to switch to AMD64 hardware even though I didn't want to. Nothing but 64-bit hardware available. Little did I know that my adventure through the world of 64-bit Linux software was going to be more hard work than a trip that I once did to the bottom of Everest with very little food in my backpack. I kicked off with Debian Etch AMD64. It just about worked but no printer drivers forced me to try various versions of Kubuntu and Ubuntu. No, printer drivers for my Samsung printer in there either. Crashing kernels. Crashing KDE. Crashing Gnome. Bits of ceiling falling off. Time to go and see the doctor for some of those strange tablets. So, next up (after wasting time with Fedora - screams loudly) I tried OpenSuSE 10.3 for AMD64. Worked first time. Printer prints. Rock solid. Nvidia graphics card just works as well. Until last Friday when after an update with YaST(2) I played a game of Doom on my workstation. At the end of the game it exited abnormally and the KDE screen came back up at about 640x480 resolution. Should have been about 1400x1280 (or similar). Couldn't fix it. After a reboot I find that X-windows and KDM/KDE try to start and then fall over. Back to the black screen and command line. I use Alpine for mail and so for me it's not too bad. However, the usual things like OpenOffice.org and Inkscape are no longer accessible. Can anyone out there suggest what could be wrong and how to fix it ? I've tried the OpenSuSE rescue disk. It just bombs out. Can't start YaST. Can't access and library in /usr/lib64/ since the update which means that no part of the system can start or do anything. I can run smart and update the system with that but even that complains and not being able to access /usr/lib64/. Perhaps a chmod or chown in /usr/lib64 might be of some use ? Below is the output of .xession-errors............................ xauth: creating new authority file /home/richard/.serverauth.3878 X Window System Version 7.2.0 Release Date: Tue Jan 22 17:03:42 UTC 2008 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux sheflug 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC x86_64 Build Date: 22 January 2008 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 27 22:11:06 2008 (==) Using config file: "/etc/X11/xorg.conf" (II) Module already built-in (II) Module already built-in (II) Module already built-in (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) No profile for user 'richard' found ===== BEGIN MILESTONES (/usr/sbin/sabayon-apply) ===== MainThread 2008/05/27 22:11:08.8916 (sabayon-apply): Fatal exception! Exiting abnormally. MainThread 2008/05/27 22:11:08.8923 (sabayon-apply): Traceback (most recent call last): File "/usr/sbin/sabayon-apply", line 99, in <module> sys.exit (util.EXIT_CODE_FATAL) SystemExit: 1 ===== END MILESTONES (/usr/sbin/sabayon-apply) ===== ===== BEGIN RING BUFFER (/usr/sbin/sabayon-apply) ===== MainThread 2008/05/27 22:11:08.8916 (sabayon-apply): Fatal exception! Exiting abnormally. MainThread 2008/05/27 22:11:08.8923 (sabayon-apply): Traceback (most recent call last): File "/usr/sbin/sabayon-apply", line 99, in <module> sys.exit (util.EXIT_CODE_FATAL) SystemExit: 1 ===== END RING BUFFER (/usr/sbin/sabayon-apply) ===== This configuration for the debug log can be re-created by putting the following in ~/sabayon-debug-log.conf (use ';' to separate domain names): [debug log] max lines = 1000 /etc/X11/xim: Checking whether an input method should be started. /etc/X11/xim: user environment variable LANG=en_GB.UTF-8 sourcing /etc/sysconfig/language to get the value of INPUT_METHOD INPUT_METHOD is not set or empty (no user selected input method). Trying to start a default input method for the locale en_GB.UTF-8 ... There is no default input method for the current locale. kde-config: error while loading shared libraries: /usr/lib64/libidn.so.11: cannot read file data: Invalid argument startkde: Starting up... /opt/kde3/bin/kdeinit: error while loading shared libraries: /usr/lib64/libidn.so.11: cannot read file data: Invalid argument startkde: Could not start kdeinit. Check your installation. Warning: connect() failed: : Connection refused ksmserver: error while loading shared libraries: /usr/lib64/libidn.so.11: cannot read file data: Invalid argument ERROR: Couldn't attach to DCOP server! startkde: Shutting down... arts-start: error while loading shared libraries: /usr/lib64/libidn.so.11: cannot read file data: Invalid argument Warning: connect() failed: : Connection refused Error: Can't contact kdeinit! startkde: Running shutdown scripts... startkde: Done. waiting for X server to shut down -- Richard www.sheflug.org.uk -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Richard Ibbotson wrote:
through the world of 64-bit Linux software was going to be more hard
first, if you ever have to reinstall that 32 bits software runs very well on 64 bits hardware, so you are not at all obliged to use 64 bits distros, you even shouldn't do. 64 bit distros are only worth if you have more than 4Gb ram (much more)
Can anyone out there suggest what could be wrong and how to fix it ?
you say kde don't start, so you should fall back in terminal only mode? in this mode you *can* use yast. You can also as a worst but fast solution use sax2-vesa to enable the basic vesa X system. should work nearly anywhere jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Richard Ibbotson wrote:
through the world of 64-bit Linux software was going to be more hard
first, if you ever have to reinstall that 32 bits software runs very well on 64 bits hardware, so you are not at all obliged to use 64 bits distros, you even shouldn't do. ^^^^^^^^^^^^^^^^^^^^^ Why not? I keep seeing this said, most often by yourself, but I've yet to see anyone actually give a good reason for not doing so. There's been multiple comments on how Flash doesn't work but, as you point out, 32bit software runs on it and so you can find ways around that little problem. And, so far, I've been running versions of 64bit since SUSE 10.0 without
On Sun, 1 Jun 2008, jdd sur free wrote:- problems.
64 bit distros are only worth if you have more than 4Gb ram (much more)
Or you have some tasks where the software benefits from the extra registers. Or just because you have 64bit hardware and want to use a 64bit distro on it. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys SUSE 10.1 32bit | openSUSE 10.2 32bit | openSUSE 10.3 32bit | openSUSE 11.0RC1 SUSE 10.1 64bit | openSUSE 10.2 64bit | openSUSE 10.3 64bit RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David Bolt wrote:
Why not? I keep seeing this said, most often by yourself, but I've yet to see anyone actually give a good reason for not doing so.
I have yet to see any benchmark giving advantage to do so, but it would be good to know jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Jun 2, 2008 at 12:29 AM, jdd sur free <jdanield@free.fr> wrote:
David Bolt wrote:
Why not? I keep seeing this said, most often by yourself, but I've yet to see anyone actually give a good reason for not doing so.
I have yet to see any benchmark giving advantage to do so, but it would be good to know
jdd
-- Jean-Daniel Dodin
Perhaps quote just a tad more of the original Jean. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
Perhaps quote just a tad more of the original Jean.
we are speaking of 64bits/32bits. I see several problems 64 bits specifics in the mailing lists and any time somebody ask why use 64bits, no significative performance enhancement versus 32 bit system (on 64 bits machines). but I would be glad to see 64 bits distro works well jdd -- Jean-Daniel Dodin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
jdd sur free wrote:
John Andersen wrote:
Perhaps quote just a tad more of the original Jean.
we are speaking of 64bits/32bits. I see several problems 64 bits specifics in the mailing lists and any time somebody ask why use 64bits, no significative performance enhancement versus 32 bit system (on 64 bits machines).
but I would be glad to see 64 bits distro works well
64' IS an advantage....depends on what you're doing. Working on large images in Gimp or Bibble, for example, is much faster than with 32'. Fred -- Linux is an old Latin word meaning, "I don't have to support your Windows anymore." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
no significative performance enhancement versus 32 bit system (on 64 bits machines).
Not our experience. 64 bit computing wins significantly. ==John ffitch -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-06-03 at 07:32 +0100, jpff wrote:
no significative performance enhancement versus 32 bit system (on 64 bits machines).
Not our experience. 64 bit computing wins significantly.
It depends on what you compute. Typically, for home use, it doesn't make much difference to use 64 or 32 bit software on 64 bit hardware. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIRRaztTMYHG2NR9URAqYbAJ972GPBOsO803nsdc8rN/5icLb8jwCfe9Ao eD2c3ZdJRWncUNv1nfEzSdQ= =xxPt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 3 Jun 2008 07:32:17 +0100 jpff <jpff@codemist.co.uk> wrote:
no significative performance enhancement versus 32 bit system (on 64 bits machines).
Not our experience. 64 bit computing wins significantly.
I've been using 64-bits for over 15 years (Tru64 Unix on the Alpha chip). 64-bits does not guarantee a performance advantage. I have found through benchmarking and other testing that in some cases 64-bits will improve performance, and in other cases that 64-bits will hurt performance. In my own company's product. We are very memory intensive, but after porting it to 64-bits on an Itanium processor, we still could not beat the 32-bit application on x86. However, based on experience, Linux, built for x86-64 does perform better. Certainly memory management is better, but also you are dealing with double the registers. -- -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
On Mon, 2 Jun 2008, jdd sur free wrote:-
David Bolt wrote:
Why not? I keep seeing this said, most often by yourself, but I've yet to see anyone actually give a good reason for not doing so.
I have yet to see any benchmark giving advantage to do so, but it would be good to know
Unfortunately, I can't provide any benchmarks as I always[0] install 64bit, not 32bit, distros on my 64bit hardware. What I can say is that I've not had any issues that couldn't be fixed while running the various 64bit versions of openSUSE. [0] I did once install the 32bit version of 10.0 on one of the systems that's now running 64bit 10.3. The idea at the time was to dual-boot between the 32 and 64 bit systems because I didn't have the available hardware to run both versions on separate hardware. However, I didn't actually follow through with that idea as I acquired another 32bit system and so no longer had the need to dual-boot. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys SUSE 10.1 32bit | | openSUSE 10.3 32bit | openSUSE 11.0RC1 SUSE 10.1 64bit | openSUSE 10.2 64bit | openSUSE 10.3 64bit RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Richard Ibbotson wrote:
AArgghh !!
[snip]
Can anyone out there suggest what could be wrong and how to fix it ? I've tried the OpenSuSE rescue disk. It just bombs out. Can't start YaST. Can't access and library in /usr/lib64/ since the update which means that no part of the system can start or do anything. I can run smart and update the system with that but even that complains and not being able to access /usr/lib64/. Perhaps a chmod or chown in /usr/lib64 might be of some use ? Below is the output of .xession-errors............................
It looks like you're not using the nVidia driver. You can startup the OS with init 3, which will give you text mode....command line. Log in, su to root, run yast. Check the "marked" repositories and make sure "nVidia" is selected. Then, do an update, reboot. Fred -- Linux is an old Latin word meaning, "I don't have to support your Windows anymore." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-06-01 at 20:45 +0100, Richard Ibbotson wrote: ...
So, next up (after wasting time with Fedora - screams loudly) I tried OpenSuSE 10.3 for AMD64. Worked first time. Printer prints. Rock solid. Nvidia graphics card just works as well.
Until last Friday when after an update with YaST(2) I played a game of Doom on my workstation. At the end of the game it exited abnormally and the KDE screen came back up at about 640x480 resolution. Should have been about 1400x1280 (or similar). Couldn't fix it. After a reboot I find that X-windows and KDM/KDE try to start and then fall over. Back to the black screen and command line. I use Alpine for mail and so for me it's not too bad. However, the usual things like OpenOffice.org and Inkscape are no longer accessible.
Can anyone out there suggest what could be wrong and how to fix it ? I've tried the OpenSuSE rescue disk. It just bombs out. Can't start YaST. Can't access and library in /usr/lib64/ since the update which means that no part of the system can start or do anything. I can run smart and update the system with that but even that complains and not being able to access /usr/lib64/. Perhaps a chmod or chown in /usr/lib64 might be of some use ? Below is the output of .xession-errors............................
Maybe some files are missing or bad. I would try: rpm --verify -a | less -S and check the output (the explanation is in "man rpm"). If an rpm has missing or bad files, reinstall that rpm. Also, run "rcrpmconfigcheck", which might list if some rpm has a config file that that didn't get installed or something (like your configuration file being replaced by a new one from the rpm). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIQyiDtTMYHG2NR9URAl42AJ9DVbBnOl+QjCD0X0zwHRd23oyAPgCeLZFO 0wCawtiT2+nkfdR41zs1S+8= =YlR8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Carlos E. R. -
David Bolt -
Fred A. Miller -
jdd sur free -
Jerry Feldman -
John Andersen -
jpff -
Richard Ibbotson