[prev in list] [next in list] [prev in thread] [next in thread]
List: haiku-bugs
Subject: Re: [Haiku-bugs] [Haiku] #2350: Segment violation in
From: "mmlr" <trac () haiku-os ! org>
Date: 2008-07-27 12:47:26
Message-ID: 052.22846b7cdcb765c9722a6a24d6e53fe1 () haiku-os ! org
[Download RAW message or body]
#2350: Segment violation in FillRectNoClipping when booting on eeePC
---------------------------------+------------------------------------------
Reporter: exparrot | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: Servers/app_server | Version: R1 development
Resolution: | Blockedby:
Platform: x86 | Blocking:
---------------------------------+------------------------------------------
Comment(by mmlr):
The way I work around it is to boot in safe video mode by booth setting
"Use Failsafe Video Mode" and choosing a video mode in the boot menu, then
when booted use the Screen preflet to select any mode different than the
current one (doesn't matter). This will cause a settings file to be
written. The resolution used when rebooting is then chosen based on the
preferred mode of the graphics driver disregarding the settings file. The
issue seems that the preferred mode isn't used when there is no settings
file at all. What I could imagine is that when there is a settings file it
will try to set that mode, which will fail for the intel driver (as it
only allows the native resolution) and then fall back to the preferred
mode. If there is no settings file, it won't try setting the mode and
won't fall back either.
--
Ticket URL: <http://dev.haiku-os.org/ticket/2350#comment:8>
Haiku <http://dev.haiku-os.org>
The Haiku operating system.
_______________________________________________
Haiku-bugs mailing list
Haiku-bugs@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/haiku-bugs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic