Hi, My system is SuSE 9,3 with a 32-bit processor. The Graphic card is a Rage 128. On Saturday (or Sunday morning) I applied the outstanding YOU Security patches. I think they were: - mozilla - MozillaFirefox - xli - qt3 - gnome-filesystem - acroread The kdebase3 update had already been applied by this stage. The system worked just fine until I powered down. The next time I tried to use the system, startx took me into some other window-manager. The most important message (just after /etc/X11/xorg.conf was loaded) was: (EE) R128(0): No DFP detected Backing out all of the updates by reverting /home, /usr, /opt, /etc, /var, /bin, /sbin and /lib (maybe 1 or 2 directories more) fixed the problem. Going forwards again was just the same - everything worked just fine after the update, until I powered down and restarted. Running sax2 did not help either. Has anyone been confronted with this before? -- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
El Lunes, 2 de Mayo de 2005 22:24, Andrew Williams escribió:
Hi,
My system is SuSE 9,3 with a 32-bit processor. The Graphic card is a Rage 128. On Saturday (or Sunday morning) I applied the outstanding YOU Security patches. I think they were: - mozilla - MozillaFirefox - xli - qt3 - gnome-filesystem - acroread The kdebase3 update had already been applied by this stage.
The system worked just fine until I powered down. The next time I tried to use the system, startx took me into some other window-manager. The most important message (just after /etc/X11/xorg.conf was loaded) was:
(EE) R128(0): No DFP detected
Backing out all of the updates by reverting /home, /usr, /opt, /etc, /var, /bin, /sbin and /lib (maybe 1 or 2 directories more) fixed the problem.
Going forwards again was just the same - everything worked just fine after the update, until I powered down and restarted. Running sax2 did not help either.
Has anyone been confronted with this before?
Yeah, me too. Suse 9.3 is the most unstable version ever. I've had lots of trouble. Konqueror is a disaster(and I speak of konqueror just only on 9.3, because under suse 9.2 /kde/konqueror-3.4 worked ever fine for me). For me the main problems are: 1-konqueror every five minutes 2-kdelibs/konqueror can't resolved apropiately dns after you log out and in again kdession(this happends only, it seems, to user who have a local server running, kpf for example) as a result of this, konqueror is unable lo load images and web pages correctly, and sometimes complains of not finding domains 3-Yast breaks kde, so you have to bring X up by hand, or get back to the rpms in the installation DVD. 4-Some encrypted cd/dvds are not shown and red correctly, so you have I have to go to ma wife's suse 9.2 notebook to be able to get retrieve data. 5-monitor and graphic card values are handled awfully, so from time to time you get a "colorfull-multi-line-divided" desktop, and have to restart x, allways fearing the os has destroyed your hardware. and so on I've been using suse for several years now, and I think(I can say with responsability) that suse 9.3 is-- although the boldest release ever(technically speaking)--the most unstable till date regards jorge
-- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
Hi, I'm also running 9.3 with all the latest patches and I do not have any of the problems mentioned below. I would even say, to me, 9.3 is more stable than 9.2 However, I must admit I once had similar problems after I tried the "suspend-to-disk" feature. My computer didn't wake up, so I had to reset which screwed up my filesystem. After that, everything seemed to be okay at first, but there were some strange problems like RPM crashing with a segfault only upon installation of certain packages (cvs-*.rpm in my case). After a reinstallation, all those problems were gone. So it's quiet obvious that the filesystem (ReiserFS) screwed up. It also was no problem to install all patches provided by YOU then. Greetings Adrian Am Tuesday 03 May 2005 00:15 schrieb Jorge Luis Arzola:
El Lunes, 2 de Mayo de 2005 22:24, Andrew Williams escribió:
Hi,
My system is SuSE 9,3 with a 32-bit processor. The Graphic card is a Rage 128. On Saturday (or Sunday morning) I applied the outstanding YOU Security patches. I think they were: - mozilla - MozillaFirefox - xli - qt3 - gnome-filesystem - acroread The kdebase3 update had already been applied by this stage.
The system worked just fine until I powered down. The next time I tried to use the system, startx took me into some other window-manager. The most important message (just after /etc/X11/xorg.conf was loaded) was:
(EE) R128(0): No DFP detected
Backing out all of the updates by reverting /home, /usr, /opt, /etc, /var, /bin, /sbin and /lib (maybe 1 or 2 directories more) fixed the problem.
Going forwards again was just the same - everything worked just fine after the update, until I powered down and restarted. Running sax2 did not help either.
Has anyone been confronted with this before?
Yeah, me too. Suse 9.3 is the most unstable version ever. I've had lots of trouble. Konqueror is a disaster(and I speak of konqueror just only on 9.3, because under suse 9.2 /kde/konqueror-3.4 worked ever fine for me).
For me the main problems are:
1-konqueror every five minutes 2-kdelibs/konqueror can't resolved apropiately dns after you log out and in again kdession(this happends only, it seems, to user who have a local server running, kpf for example) as a result of this, konqueror is unable lo load images and web pages correctly, and sometimes complains of not finding domains 3-Yast breaks kde, so you have to bring X up by hand, or get back to the rpms in the installation DVD. 4-Some encrypted cd/dvds are not shown and red correctly, so you have I have to go to ma wife's suse 9.2 notebook to be able to get retrieve data. 5-monitor and graphic card values are handled awfully, so from time to time you get a "colorfull-multi-line-divided" desktop, and have to restart x, allways fearing the os has destroyed your hardware.
and so on
I've been using suse for several years now, and I think(I can say with responsability) that suse 9.3 is-- although the boldest release ever(technically speaking)--the most unstable till date
regards
jorge
-- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
On Tuesday 03 May 2005 3:03 am, Adrian Gygax wrote:
I'm also running 9.3 with all the latest patches and I do not have any of the problems mentioned below. I would even say, to me, 9.3 is more stable than 9.2
'Have to agree.......no "breakage" here on this box nor others. Fred -- The only bug free software from MickySoft is still shrink-wrapped in their warehouse..."
On May 3, 2005 11:04 am, Fred A. Miller wrote:
On Tuesday 03 May 2005 3:03 am, Adrian Gygax wrote:
I'm also running 9.3 with all the latest patches and I do not have any of the problems mentioned below. I would even say, to me, 9.3 is more stable than 9.2
'Have to agree.......no "breakage" here on this box nor others.
Fred
-- The only bug free software from MickySoft is still shrink-wrapped in their warehouse..."
I have just ordered 9.3 myself. I'm curious, do you guys recommend I perform an upgrade or a fresh install? I am running 9.1 pro. Thanks, Alvin -- Please reply to only this mailing-list so others can take part as well. Thanks.
On Tuesday 03 May 2005 10:03 am, Alvin Beach wrote:
On May 3, 2005 11:04 am, Fred A. Miller wrote:
On Tuesday 03 May 2005 3:03 am, Adrian Gygax wrote:
I'm also running 9.3 with all the latest patches and I do not have any of the problems mentioned below. I would even say, to me, 9.3 is more stable than 9.2
'Have to agree.......no "breakage" here on this box nor others.
Fred
-- The only bug free software from MickySoft is still shrink-wrapped in their warehouse..."
I have just ordered 9.3 myself. I'm curious, do you guys recommend I perform an upgrade or a fresh install? I am running 9.1 pro.
Do a "custom" install, that is keep your partitions, but format them and do a fresh install.....format all BUT HOME!!!! KEEP /home and you won't loose your mail, etc. Now, to keep you address book(s) and bookmarks, be SURE you export both and burn them along with your /home dir. to a CD FIRST! Backups are a MUST......just in case. ;) Fred -- The only bug free software from MickySoft is still shrink-wrapped in their warehouse..."
On Tuesday 03 May 2005 16:03, Alvin Beach wrote:
On May 3, 2005 11:04 am, Fred A. Miller wrote:
On Tuesday 03 May 2005 3:03 am, Adrian Gygax wrote:
I'm also running 9.3 with all the latest patches and I do not have any of the problems mentioned below. I would even say, to me, 9.3 is more stable than 9.2
'Have to agree.......no "breakage" here on this box nor others.
Fred
-- The only bug free software from MickySoft is still shrink-wrapped in their warehouse..."
I have just ordered 9.3 myself. I'm curious, do you guys recommend I perform an upgrade or a fresh install? I am running 9.1 pro.
Thanks,
Alvin
Hi Alvin, I tried the following: - update 7.0->8.2 and fresh install 8.2 - update 8.2->9.1 and fresh install 9.1 - update 9.1->9.2 (ftp) Speaking from that experience, my personal opinion is that a fresh install works better (I'm still hunting some rough edges from the 9.1->9.2). The advantages for me is that it also removes a lot of garbage and the whole system works more smoothly. Having said that, here are the buts: - I used 'custom install' option, which might sound terrifying, but you are guided pretty nicely through the process - If you do customise your package selection instead of accepting one of the default selections, it might be more work - All the 'personal data' which have nothing to do with the system are on separate partitions in my set-up, so I just used the old partitioning and formatted the partitions with the mount points root, /opt and /usr , leaving all personal data untouched. Since the installation went flawlessly I was ready to go immediately with all my personal data at hand. Whatever you do, do a backup in case something goes wrong (at least of your home directories and anything in the /data or /usr/local directories if you have those. You should also check at least the back-up option for /etc system configuration files during the Yast installation/update. Cheers gl -- Günter Lichtenberg ========>mailto:lichten@sron.nl SRON (EOS) Sorbonnelaan 2 3584 CA UTRECHT the Netherlands Tel.: +31 30 253 5719 FAX : +31 30 254 0860
Hi Alvin, I recently did an update on my Laptop from 9.1 pro to 9.3 pro and all went smoothly. But, in any case, you have to backup your stuff, because you never know what happens to your configuration files during the update. E.g., Mail settings or address entries could be lost due to another kmail config file version etc. On the other hand, SuSE seems to have remedied most of the update issues they had in earlier versions, and updating really can save a lot of hassle depending on your setup. In my case, it were the ssh hostkeys, the samba server setups, setup of our backup facility etc. which made me try the update. So my recommendation is: 1) Backup your machine 2) try the update 3) if the result is unacceptable, re-install from scratch and pull your stuff from the update.
I have just ordered 9.3 myself. I'm curious, do you guys recommend I perform an upgrade or a fresh install? I am running 9.1 pro.
Thanks,
Alvin
-- Michael Schmuker University of Frankfurt Chair of Cheminformatics http://www.modlab.de
Hmmmmm, I think I know what you mean. The same happens if you use yast to change resolutions after installation. After that and after restart of X (e.g. by rebooting) you get a grey login manager looking really really ugly. Indeed this is xdm, the worst graphical thing on earth (while working everywhere, though). Just edit /etc/sysconfig/displaymanager and change xdm back to kdm. It's really a shame that this obvious bug was not found by SuSE Quality Assurance. I know 3 users (including me) which tried SuSE 9.3 and we all catched this one. Best, Daniel Am Montag, 2. Mai 2005 22:24 schrieb Andrew Williams:
Hi,
My system is SuSE 9,3 with a 32-bit processor. The Graphic card is a Rage 128. On Saturday (or Sunday morning) I applied the outstanding YOU Security patches. I think they were: - mozilla - MozillaFirefox - xli - qt3 - gnome-filesystem - acroread The kdebase3 update had already been applied by this stage.
The system worked just fine until I powered down. The next time I tried to use the system, startx took me into some other window-manager. The most important message (just after /etc/X11/xorg.conf was loaded) was:
(EE) R128(0): No DFP detected
Backing out all of the updates by reverting /home, /usr, /opt, /etc, /var, /bin, /sbin and /lib (maybe 1 or 2 directories more) fixed the problem.
Going forwards again was just the same - everything worked just fine after the update, until I powered down and restarted. Running sax2 did not help either.
Has anyone been confronted with this before?
-- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
On May Wednesday 2005 1:04 pm, Daniel Eckl wrote:
Hmmmmm, I think I know what you mean.
The same happens if you use yast to change resolutions after installation.
After that and after restart of X (e.g. by rebooting) you get a grey login manager looking really really ugly. Indeed this is xdm, the worst graphical thing on earth (while working everywhere, though).
Just edit /etc/sysconfig/displaymanager and change xdm back to kdm.
It's really a shame that this obvious bug was not found by SuSE Quality Assurance. I know 3 users (including me) which tried SuSE 9.3 and we all catched this one.
Well, now you will know that at least one early adopter didn´t have this problem. OTH, The9.3 didn´t recognize some firewire drives that had been ¨ just working" on 9.2.. And worse, no editing of the fstab would give me a mount point. Finally made as if to install and told it not to install anything in /home and wouldn´t you know it was suddenly legal. Although I did lose a lot of media files. I suspect at least part of that problem was my fault.. it wanted to install the whole Suse on it.. But I said no.. if this were a Hal computer I´d be pretty upset by now.. j
Thanks. I had stupidly thought that startx was trying to start kde and failing, not that the config was simply wrong (After a YOU security update - it was fine before). I had upgraded 9.2 to 9,3. For some arcane reason I had to reboot to make the /etc/sysconfig/displaymanager changes (which I did via YaST) active. Just running 'startx' was not enough, booting into runlevel 5 (which had unilaterally used that other window-manager before) worked just fine. Thanks again. Now I'll apply those security updates again. I had backed them out while repeatedly rebooting to see which one was the problem. Daniel Eckl wrote:
Hmmmmm, I think I know what you mean.
The same happens if you use yast to change resolutions after installation.
I tried that as well to see if it helped.
After that and after restart of X (e.g. by rebooting) you get a grey login manager looking really really ugly. Indeed this is xdm, the worst graphical thing on earth (while working everywhere, though).
Just edit /etc/sysconfig/displaymanager and change xdm back to kdm.
It's really a shame that this obvious bug was not found by SuSE Quality Assurance. I know 3 users (including me) which tried SuSE 9.3 and we all catched this one.
Best, Daniel
participants (9)
-
Adrian Gygax -
Alvin Beach -
Andrew Williams -
Daniel Eckl -
Fred A. Miller -
Guenter Lichtenberg -
jfweber＠bellsouth.net -
Jorge Luis Arzola -
Michael Schmuker