https://bugzilla.novell.com/show_bug.cgi?id=339640#c14
--- Comment #14 from Robert Davies 2007-11-15 20:21:49 MST ---
Well I've made a lot of progress, and got a 'brokenmodules=" workround for 1 of
my ATA controller problems. So when I make time (at night) to really go at
these bugs it does make headway.
What I think happened, is that during install, you run a kernel from CD.
Then after rpm's are installed, we reboot. I think my timing was bad, and I
got 2.6.22.9-0.4 which has a number of serious bugs, which affected me and
halted the Install process as it stopped the network connection.
That left me with unfinished YOU bit of the install, and having to Abort the
installation.
So I didn't get to the installation SaX2 stuff. I had to boot after, swap NICs
and muck around. Trying to use the 'nv' driver later failed, and there was the
error message that the chipset was unrecognised (that I am meant to forget; so
I ended up with vesa driver.
The GE 8300 GS is a 128MB card, that wants to use system memory, so perhaps it
doesn't like a 64MB default Graphics Aperture size, the machine has 4GiB RAM,
so it wants to "steal" much more RAM than 64 MB.
I can't see how I can do much with the SaX2 bug report, unless I move monitors
around, test what happens on older hardware with SuSE 8.2, then OS 10.3. I'll
have to rpm -e the Nvidia stuff, and try to switch to nv driver.
It'll be no more time consuming to backup, partition, and then do basic
graphics install taking all defaults and see what I get. It's a 2 for 1. If
the 3D update fails same way then we know much more, if it doesn't then you can
blame me, and I can blame SuSE kernel-bigsmp-2.6.22.9-0.4 :)
I'm talking myself into it, aren't I? The alternative is to leave 2 Bugs, with
out getting to the bottom of the problems.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.