http://bugzilla.novell.com/show_bug.cgi?id=608237
http://bugzilla.novell.com/show_bug.cgi?id=608237#c1
Lee Matheson changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lee_matheson@hotmail.com
--- Comment #1 from Lee Matheson 2010-05-24 14:23:26 UTC ---
One idea is a work around to this (removal of sax2), which might be to produce
a wiki with useful information to help users when there is no sax2 (and when
Xorg auto config does not work), listing work arounds for different drivers.
ie possibly things like using the boot code: "linux xdriver=vesa" or "linux
xdriver=fbdev" (although those did not work well for me last time I tried
them).
other possible entries to a Graphic work around wiki would be how to force a
vesa or fbdev boot when the "nomodeset" boot code does not work. For example,
I successfully booted a laptop to the fbdev driver on an 11.3 liveCD when the
"nomodeset" did not work (ie neither intel, nor vesa drivers worked). I did
this by using "vi" to edit /etc/X11/xorg.conf.d/50-Device.conf, adding the
line:
Driver "fbdev"
Thats a painful approach, but what else is there ?
.. that is just an example, but if we are to remove sax2, I do not believe we
can simply rely on Xorg automatically working, with 'nomodeset' as a work
around. Thats not enough in my opinion.
We need something more when sax2 is dropped, and maybe we can cover this with a
good (really really good) wiki with work arounds !
Thanks for all your work ... I'm just trying to make my life easier on the
forum support side of the house, when the complaints start coming in (which I
predict will happen).
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.