laptop graphics problem with 9.2
In the two years I have had my Compaq 1500 laptop, I have at various times had Fedora Core 2 and SuSE (various, the last being 9.0) on it. I've never had problems with it until I tried to update to 9.2. Running sax2 brings up a white screen. I tried plugging in another lcd external monitor, and resolution on that one was 640X480, 16 colors. I had been routinely running 1280x1024, with 16 bit resolution. It has to be the driver, and in 9.0 I got good results using a generic LCD monitor. That no longer works.
On Sun, 2005-01-23 at 13:44 -0800, Tim Hanson wrote:
In the two years I have had my Compaq 1500 laptop, I have at various times had Fedora Core 2 and SuSE (various, the last being 9.0) on it. I've never had problems with it until I tried to update to 9.2. Running sax2 brings up a white screen.
I tried plugging in another lcd external monitor, and resolution on that one was 640X480, 16 colors.
I had been routinely running 1280x1024, with 16 bit resolution.
It has to be the driver, and in 9.0 I got good results using a generic LCD monitor. That no longer works.
Hi Tim, Did you try "SaX2 -l" (lower case "L"?) or "SaX2 --lowres"? This will invoke SaX2 in standard 16 color 640 x 480 60 Hz VGA mode, allowing you to proceed with the installation graphically. This usually circumvents the dreaded "black screen of death" -- or in your case, hopefully, the "white screen" of death. ;-) DDC detection is switched off in this case, so you'll need to define or pick your display components manually. HTH & regards, - Carl
On Sun, 2005-01-23 at 17:58 -0500, Carl E. Hartung wrote:
I had been routinely running 1280x1024, with 16 bit resolution.
It has to be the driver, and in 9.0 I got good results using a generic LCD monitor. That no longer works.
Hi Tim,
Did you try "SaX2 -l" (lower case "L"?) or "SaX2 --lowres"?
No such luck. I had high hopes too, since now that you mention it I used that argument a few years ago on another computer. The sole difference between 9.0 / 9.1 and this appears to be that earlier there was no driver for HSD150PK12-A monitor, while now sax forces the use of a flawed one, even in lowres mode. I don't know how to find this driver, but if I could find it, would naming it something else or moving it do the trick?
Op maandag 24 januari 2005 10:19, schreef Tim Hanson:
On Sun, 2005-01-23 at 17:58 -0500, Carl E. Hartung wrote:
I had been routinely running 1280x1024, with 16 bit resolution.
It has to be the driver, and in 9.0 I got good results using a generic LCD monitor. That no longer works.
Hi Tim,
Did you try "SaX2 -l" (lower case "L"?) or "SaX2 --lowres"?
No such luck. I had high hopes too, since now that you mention it I used that argument a few years ago on another computer.
The sole difference between 9.0 / 9.1 and this appears to be that earlier there was no driver for HSD150PK12-A monitor, while now sax forces the use of a flawed one, even in lowres mode. I don't know how to find this driver, but if I could find it, would naming it something else or moving it do the trick?
Perhaps: 1) set the framebuffer to a 1024x768 mode. Edit the file /boot/grub/menu.lst and change the vga= paramater to: vga=0x317 --> reboot everything is fine now :-) 2) try to use the ati driver but remind that may not work. Just call the following command as root: sax2 -m 0=ati --> configure the resolution -- Richard Bos Without a home the journey is endless
On Mon, 2005-01-24 at 11:57 +0100, Richard Bos wrote: 1) set the framebuffer to a 1024x768 mode. Edit the file /boot/grub/menu.lst and change the vga= paramater to: vga=0x317 --> reboot everything is fine now :-) 2) try to use the ati driver but remind that may not work. Just call the following command as root: sax2 -m 0=ati --> configure the resolution No good. The vga parameter was already set to 0x317, sax2 with the -i and -r arguments didn't work. Does anyone know how I can remove the config file for that monitor? That is the only difference between the old and the new configuration.
participants (3)
-
Carl E. Hartung -
Richard Bos -
Tim Hanson