Re: SusE 9.3 Riddled With Bugs! Don't Waste Your Money Or Your Time!!!

From: Thomas Tootle (tootlet_at_m33access.com)
Date: 04/24/05 

Date: Sun, 24 Apr 2005 13:30:18 -0400

Malke wrote:
> NoName wrote:
>
>
>>David Bolt <blacklist-me@davjam.org> wrote in
>>news:8vt5rDF+xpaCFwWB@dev.null.davjam.org:
>>
>>
>>>On Sat, 23 Apr 2005, NoName <me@nospam.net> wrote:-
>>>
>>>While this is almost like something a troll might post, some of this
>>>does bear resemblance to issues raised after a friend installed 9.3
>>>on his system.
>>>
>>>
>>>>I have read the thread about the problems someone was having. I also
>>>>had quite a time getting 9.3 to run on my computer which has had 9.0,
>>>>9.1 both with no problems. The first install had several issues
>>>>during setup and the install failed after 1 day. The system on login
>>>>would enter the X screen instead of going to KDE or Gnome. You could
>>>>start xterm and run in a window but nothing I did would change
>>>>anything.
>>>
>>>While I haven't had any problems with 32-bit 9.3 installed on my
>>>wifes' system[0], I have had to talk someone through getting the KDM
>>>login screen back and, consequently, their proper KDE desktop.
>>>
>>>As a bit of background, the friend in question did a full install
>>>with virtually all the packages on the DVD. After having the system
>>>up and running for a while, doing all the updates available as
>>>required, he then installed the Nvidia driver. After a reboot, since
>>>he also dual-boots WinXP, the login had reset to XDM.
>>>
>>>At this point, he phoned me and we went through the steps of ensuring
>>>that KDE still worked and resetting the login manager to KDM. Here's
>>>the steps we went through:
>>>
>>>1, switch to runlevel 3 by swapping to a console and, as root, typing
>>>init 3;
>>>2, start up YaST and going into System -> Editor for /etc/sysconfig
>>>files;
>>>3, under Desktop -> Display Manager -> DISPLAYMANAGER, reset this to
>>>kdm;
>>>4, press ALT-F to exit and save the settings;
>>>5, exit YaST and switch back to runlevel 5;
>>>6, reboot and see if it restarts KDM from a reboot.
>>>
>>>You don't really need to reboot the system as switching to runlevel 5
>>>restarts X. However for the paranoid, unsure, or just plain
>>>untrusting, this should help to ease the mind.
>>>
>>>
>>>>I uninstalled by reformatting the partition and did a complete
>>>>re-install. After doing the online update the same thing happened
>>>>again immediatly.
>>>
>>>You didn't install the nVidia driver did you? If so, and others have
>>>the same problem, there may be a problem with the driver installation
>>>script.
>>>
>>><Snip moan about it being slow>
>>>
>>>This is something I haven't noticed, nor has the friend mentioned
>>>above. If anything, to me, it feels a little faster than the
>>>previously installed version[0].
>>>
>>>
>>>[0] even though it's a 64-bit system. Only reason for installing
>>>32-bit was so I didn't have to mirror the 64-bit updates as well as
>>>the 32-bit updates.
>>>
>>>[1] 9.0
>>>
>>>Regards,
>>> David Bolt
>>>
>>
>>First, NOT A TROLL! hehe
>>
>>
>>The above incident was fairly described, now the offending machine is
>>correctly running 9.3. Still, dhcp is quite slow sometimes 2 - 3
>>second waits before initiating page loads. Konqueror is the worst
>>offender, Firefox does a little better as does Mozilla. Some pages
>>simply won't load except on mozilla. The firewall must be
>>responsible??? not sure.
>>
>>Due to this I still use the square glass system for internet access
>>most of the time. read MS
>>
>>Nope on the nvidia driver... I am running a G400 Dual head ( in single
>>mode with 3d active ) All else I could say since now the evidence is
>>gone is operator error COULD have accidently checked the nvidia
>>driver??? Alshiemers (sp) might be coming to visit ;-)
>>
>
> Well, I am absolutely *not* a troll, but I had similar issues with 9.3
> (32-bit) and finally had to go back to 9.1. I've had SuSE on this box
> since 8.0 with no problems, very vanilla hardware, with an old but
> trusty Nvidia Elsa Gladiac 64 for the video. I keep /home on a second
> hard drive, so format hda as swap and /. This has worked well.
>
> I installed 9.3 and everything looked great except apps weren't stable
> (like OO and Firefox). From looking in the newsgroup, I saw that I had
> made the mistake of installing all 4 of the multimedia updates,
> although I waited until the installation process was done. I got the
> grey box login with no shutdown options and then lots of failures with
> DCOP and then no KDE at all.
>
> So I formatted again and redid everything, making sure I deleted all the
> hidden files in my /home profile first. Great. Everything worked, and I
> only chose 1 of the multimedia updates. The system was really nice,
> stable and so I happily configured all my apps and then - yes, without
> me doing anything in particular we were back to the original problem.
>
> I gave 9.3 one more try, formatting a third time. Again, the system
> failed inexplicably (to me) because I hadn't done anything specific or
> made more changes - just logged out and then was presented with the
> grey box and after logging in, nothing except a blank screen and not
> even a console prompt. I'm sure a more clever user might have figured
> it out, but aside from the graphics problem I really didn't like 9.3 as
> much as 9.1. It was slower than 9.1 on my 1.2 Athlon with 512MB of RAM
> and I didn't like the newer KDE as well. So I reinstalled 9.1 with no
> problems whatsoever.
>
> Please don't get me wrong - this is *not* any kind of a slam against
> SuSE. This is the first time I've had any big problems installing a
> SuSE os and I've bought all the versions to help support SuSE. 9.2 was
> the only one I've skipped because I was happy with 9.1 and there were
> reported problems with 9.2. I really don't think I'll take the chance
> and put 9.3 on the laptop, even though 9.1's power management isn't
> very good. I'll probably try 9.3 again on one of the test boxen.
>
> Malke\

Greetings,
My nephew with an ATI video card and Intel system had a working system.
After a couple of reboots he lost the ability to login to KDE and went
only to CLI. I wiped my 9.2 and attempted to load it on ABIT NF7 running
Athlon 3000XP, 1 Gb RAM and a Nvidia Ultra 5700 Ultra and 2 Sony
monitors. Can't get it working beyond CLI despite 3 installs. Never had
this much problem before. I'm going to reformat with Knoppix, reinstall
with the CD's instead of DVD and not do an on line update for a while
and see if that gives me a working system. I think there's a problem
here. But I'm not giving up on SUSE.
T

Relevant Pages

  • Re: Goodbye SuSE 9.2. Hello gentoo!
    ... Windows or Linux is the laptop. ... All three Athlon boxes run SuSE fast enough that it doesn't get in the way - ... Certain tasks would load quicker, ... Yoper is almost instant as clicking the fstab icon opens a terminal session ...
    (alt.os.linux.suse)
  • [SLE] A few questions
    ... I can't use locate in SUSE 9.1 Pro is there a reason why it isn't installed? ... an option a new window opens and that takes a while. ... installing apt and now my system is broken, and I blame the fact that I had ...
    (SuSE)
  • [SLE] Re: A better SuSE Support DB?
    ... revenue from those who decided to use a different distribution ... Linux distributions (Debian, Mandrake, and SuSE) only SuSE is ... installing from the 'net, to throw some cash at the people behind ... individual packages that comprise SuSE Linux, ...
    (SuSE)
  • Re: Firefox+flash dont load page correctly in F8 - same versions in F7 do
    ... It's a tabbed "sub-window", ... load and work ... Firefox, uninstalling icedtea, installing Sun's Java, installing ... got the stock listing, but no updating. ...
    (Fedora)
  • Problem with drives "tagged as part of hardware RAID array"
    ... It's not specifically a SUSE ... The storage here will be 5 x 120 GB Maxtor drives, ... drive having a problem so that it could not be used for installing on. ... recognized one of the disks as being part of its array. ...
    (alt.os.linux.suse)