[Leaplist] LCD = Out of Range problem - Debian AMD64

[Stephen Cullum]

I had a problem a while back with my laptop viewing my virtual consoles 
they were black but the Gui console was ok. It also uses a nVidia 
graphic card. There was a bug in the nVidia driver. It eventual was 
fixed but for a while after every grub update after a kernel update I 
had to add vga=791 on my kernal line in my grub menu.lst file. It looked 
like this.

title Ubuntu, kernel 2.6.15-22-386
root (hd0,4)
kernel /boot/vmlinuz-2.6.15-22-386 root=/dev/hda5 ro quiet splash vga=791
initrd /boot/initrd.img-2.6.15-22-386
savedefault
boot

 The normal display of 640X480 wouldn't display. The vga=791 set the 
display to 1280X1024 which worked.

there are other display modes

(This is notes on vesa frame buffer settings. Got from Linus Annoyances 
For Geeks. Today's date is 6/26/2006.

Frame Buffer know-how is at 
http://www.tldp.org/HOWTO/Framebuffer-HOWTo.html  .

Table 5-3. VESA video modes

Bits    640x480    800x600    1024x76  1280x1024  1600x1200

8    769    771    773     775         796

16    785    788    791      794         798

32    786    789    792     795         799      )

I have used this on the menu.lst , for grub on the kernel line , used

vga=791 , to pass this vesa parameter to the kernel.

It would be easy to try this by editing your menu.lst grub conf. file.


Phil Barnett wrote:
> Whit Hansell wrote:
>> hey guys,
>> Lookin' for an answer to a prob' I've run up against.  amonth ago or 
>> so on a Sat. AM, the power dropped and my mobo was dead when it came 
>> back on.  So went to ComppUSA and bought a new one, an Asus M3A78-CM 
>> and put an AMD Athlon X2 5200 2.7Ghz processor on it and 4 G RAM.  
>> Onboard video and sound.
>>
>> Anyway, It all comes up just fine and dandy, w. the latest Debian 
>> AMD5 Lenny netinstall but found that when I try to do anything in 
>> terminal (F1-F6) I get a black screen and teh monitor sends out an 
>> "Out of Range" sgnal.  It's strange because when it boots up, I get 
>> terminal output up to the login screen which works just fine.  But 
>> then after login and KDE opens up, I can't get back to the termial.  
>> It has even messed up my shutdown.  The other  day for grins, I did a 
>> reboot and it took a whie for the KDE to close and then go to 
>> terminal for the "shutdown" messages but then after KDE shutdown, the 
>> terminal screen was black and it just sat there w. the mouse pointer 
>> siltting there.  AFter a while, I just typed itn "shutdown -h now" 
>> thinking it would take over and just shutdown the system, but it 
>> didnt' and i fianally used the switch to turn off the machine.  Then 
>> when I turned it back on all the partitions had to be re"journald" 
>> which tells me the system got stuck somewhere but aI coudn not see 
>> where because the terminal was black.
>>
>> I have googled "out of range" and amd64 but all I can really find is 
>> where people have had problems w. getting  past the splash screen or 
>> such.  That's not my problem.  I need to find out what conf file I 
>> need to tweak to set up the correct range (I'm assuming 60Hz) at a 
>> 1024 X 768 resolution from the login screen and after.  At least 
>> that's my assumption.  The LCD is  a NIKO 2+0+R(been a good little 
>> monitor so far) with Hres 48.37, Vres 60.01, Pixel Clock 64.51 Mhz at 
>> 1024 X 768.  The onboard video is ATIRV610  Direct X10.0.  I have the 
>> resin KDE set at 1024 X 768 at 60Hz.
>>
>> If anyone has any ideas or experience at this I'd sure appreciate 
>> some input.  I'm googled out.
>>  i've not been able to find anyone who has had a similar problem, or 
>> at least who had gotten it figured out.
> Well, I have a tiny bit of input.
>
> Somewhere in an upgrade in the last few months, my laptop (HP, nVidia 
> video) started getting a blank black screen when I press Ctrl-Alt-F2-F6
>
> Ctrl-F1 brings me back to the GUI. (KDE)
>
> ps ax in a gui terminal shows that I have 5 instances of 
> /sbin/mingetty running, but I can't seem to switch to them.
>
> I'm guessing that I have the same problem on totally different hardware.
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.