Messages in this thread |  | | | Date | Wed, 17 Nov 2004 12:55:05 +0100 | | From | Philipp Matthias Hahn <> | | Subject | Re: Linux 2.6.10-rc2 SAVAGEFB startup crash |
| |
Hello!
On Wed, Nov 17, 2004 at 05:20:58AM +0800, Antonino A. Daplas wrote: > > That fixed the crash, but the screen looks very broken on my notebook > > after boot. Switching between XFree86 and SavageFB also locked up the > > kernel hard. > > Try booting at the native resolution of your notebook, for example: > > video=savagefb:1024x768@60
The "@60" did it. (Reading "man 4x savage" -> "UseBIOS" gives my the impression, that this is important for some mobile chips.)
On Wed, Nov 17, 2004 at 05:43:02AM +0800, Antonino A. Daplas wrote: > > after boot. Switching between XFree86 and SavageFB also locked up the > > As for the lockup between X and the console, can you try this patch? ... > - FBINFO_HWACCEL_XPAN; > + FBINFO_HWACCEL_XPAN | > + FBINFO_MISC_MODESWITCHLATE;
That (partly) solved the lockup: I was able start XFree86, switch back to Console, but on return to X11, the X11 screen wasn't restored correctly, the mouse left a trail behind and switching to console again didn't work. (a remove "chvt 1" as root still worked). Exiting and than restarting XFree86 sometimes didn't initialize the screen correctly.
While writing this email, my notebook locked up again hard and I had to powercycle it.
BYtE Philipp -- / / (_)__ __ ____ __ Philipp Hahn / /__/ / _ \/ // /\ \/ / /____/_/_//_/\_,_/ /_/\_\ pmhahn@titan.lahn.de - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |