VGA modes for the supported resolutions
 

On Sat,12.Jul.08, 18:06:11, Richard Möhn wrote:

> > Say me the resolution and colour depth of your screen and I say you
> > what to add after vga= to the kernel line of your /boot/grub/menu.lst.
> >
> > Nice greetings
> >
> > Richard
> >
> Ok, since I cannot answer soon if you will not reply today I have
> installed hwinfo and that printed this list to me:

Oh, you're a life-saver. I've beet STFW for the mode 1680x1050, but with
your tip I got it.

Here's another list in case some other poor guy is looking for it:


,----[ hwinfo --framebuffer ]
| 02: None 00.0: 11001 VESA Framebuffer
| [Created at bios.450]
| Unique ID: rdCR.VSBbdW2x3qC
| Hardware Class: framebuffer
| Model: "NVIDIA G86 Board - NV_NB8M "
| Vendor: "NVIDIA Corporation"
| Device: "G86 Board - NV_NB8M "
| SubVendor: "NVIDIA"
| SubDevice:
| Revision: "Chip Rev"
| Memory Size: 14 MB
| Memory Range: 0xd5000000-0xd5dfffff (rw)
| Mode 0x0300: 640x400 (+640), 8 bits
| Mode 0x0301: 640x480 (+640), 8 bits
| Mode 0x0303: 800x600 (+800), 8 bits
| Mode 0x0305: 1024x768 (+1024), 8 bits
| Mode 0x0307: 1280x1024 (+1280), 8 bits
| Mode 0x030e: 320x200 (+640), 16 bits
| Mode 0x030f: 320x200 (+1280), 24 bits
| Mode 0x0311: 640x480 (+1280), 16 bits
| Mode 0x0312: 640x480 (+2560), 24 bits
| Mode 0x0314: 800x600 (+1600), 16 bits
| Mode 0x0315: 800x600 (+3200), 24 bits
| Mode 0x0317: 1024x768 (+2048), 16 bits
| Mode 0x0318: 1024x768 (+4096), 24 bits
| Mode 0x031a: 1280x1024 (+2560), 16 bits
| Mode 0x031b: 1280x1024 (+5120), 24 bits
| Mode 0x0330: 320x200 (+320), 8 bits
| Mode 0x0331: 320x400 (+320), 8 bits
| Mode 0x0332: 320x400 (+640), 16 bits
| Mode 0x0333: 320x400 (+1280), 24 bits
| Mode 0x0334: 320x240 (+320), 8 bits
| Mode 0x0335: 320x240 (+640), 16 bits
| Mode 0x0336: 320x240 (+1280), 24 bits
| Mode 0x033d: 640x400 (+1280), 16 bits
| Mode 0x033e: 640x400 (+2560), 24 bits
| Mode 0x0345: 1600x1200 (+1600), 8 bits
| Mode 0x0346: 1600x1200 (+3200), 16 bits
| Mode 0x0347: 1400x1050 (+1400), 8 bits
| Mode 0x0348: 1400x1050 (+2800), 16 bits
| Mode 0x0349: 1400x1050 (+5600), 24 bits
| Mode 0x034a: 1600x1200 (+6400), 24 bits
| Mode 0x0352: 2048x1536 (+8192), 24 bits
| Mode 0x0360: 1280x800 (+1280), 8 bits
| Mode 0x0361: 1280x800 (+5120), 24 bits
| Mode 0x0362: 768x480 (+768), 8 bits
| Mode 0x0364: 1440x900 (+1440), 8 bits
| Mode 0x0365: 1440x900 (+5760), 24 bits
| Mode 0x0368: 1680x1050 (+1680), 8 bits
| Mode 0x0369: 1680x1050 (+6720), 24 bits
| Mode 0x037c: 1920x1200 (+1920), 8 bits
| Mode 0x037d: 1920x1200 (+7680), 24 bits
| Config Status: cfg=new, avail=yes, need=no, active=unknown
`----

I'm using vga=0x368 since 8 bits are enough for the console and at 24
it's too slow. Maybe I should try nvidiafb? But I recall some problems
with the non-free module... Maybe someone else has tried this?

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

VGA modes for the supported resolutions
 

Folk,

[As soon as I have a tunnel working, thread continuity will be possible.]

Andrei Popescu wrote,
",----[ hwinfo --framebuffer ]
| 02: None 00.0: 11001 VESA Framebuffer
| [Created at bios.450]
..."

hwinfo gives no output on this system.
dalton:~# hwinfo --framebuffer
dalton:~#

What is needed to have a framebuffer?

Thanks, ... Peter E.

--
http://members.shaw.ca/peasthope/
http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

VGA modes for the supported resolutions
 

On Wed,16.Jul.08, 19:12:51, PETER EASTHOPE wrote:
> Folk,
>
> [As soon as I have a tunnel working, thread continuity will be possible.]
>
> Andrei Popescu wrote,
> ",----[ hwinfo --framebuffer ]
> | 02: None 00.0: 11001 VESA Framebuffer
> | [Created at bios.450]
> ..."
>
> hwinfo gives no output on this system.
> dalton:~# hwinfo --framebuffer
> dalton:~#
>
> What is needed to have a framebuffer?

That's a shot in the dark, but try booting with vga=788

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

VGA modes for the supported resolutions
 

Andrei & Richard,

ap> That's a shot in the dark, but try booting with vga=788

That also fails on the IBM NetVist machine.
But the machine at home gives sensible
output from "hwinfo --framebuffer".
I'll try qemu on it next weekend.

Thanks for the help, ... Peter E.



--
http://carnot.yi.org/
= http://carnot.pathology.ubc.ca/
Desktops.OpenDoc http://members.shaw.ca/peasthope/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

VGA modes for the supported resolutions
 

Andrei, Richard & others,

At Thu, 17 Jul 2008 11:02:51 +0300 Andrei Popescu wrote,
ap> That's a shot in the dark, but try booting with vga=788

Thanks. I have a little progress.

On the Toshiba 4000 CDS this weekend,
"vga=788" gives a display.

Also I found that a vga/vesa number which
is faulty, will prompt grub or the kernel
to display a list of configurations and
wait for a choice.

When the system prompt appears I can again try

qemu -m 40 -boot d -cdrom /home/peter/AosCD.iso

Some text from qemu flashes briefly on the
screen and then it grinds to a halt with
this message.

Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory
Could not open SDL display

I've installed the kqemu packages yet
/dev/kqemu is absent.

What is the problem with kqemu?

Thanks for any further ideas,
... Peter E.




--
http://members.shaw.ca/peasthope/
http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

VGA modes for the supported resolutions
 

On Sun,10.Aug.08, 16:17:14, peasthope@shaw.ca wrote:

[...]

> Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory
> Could not open SDL display
>
> I've installed the kqemu packages yet
> /dev/kqemu is absent.
>
> What is the problem with kqemu?

When I was using qemu I had this (now it's disabled, of course)

$ grep kqemu /etc/modprobe.d/00local
#options kqemu major=0

so /dev/kqemu gets created automatically

You will also have to list kqemu in /etc/modules to have it load on
every boot. Otherwise you will have to modprobe it by hand.

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

VGA modes for the supported resolutions
 

Andrei,

ap> $ grep kqemu /etc/modprobe.d/00local
#options kqemu major=0
...
...list kqemu in /etc/modules ...

Good. Thanks! kqemu works now.

I still have this message about SDL.

newton:~# qemu -m 40 -hda /dev/sda -cdrom /home/peter/AosCD.iso -boot d
Could not open SDL display
newton:~#

libsdl1.2debian-all is installed but "man sdl"
and "man libsdl" yield nothing. Any tips on
making SDL work?

Thanks, ... Peter E.


--
http://members.shaw.ca/peasthope/
http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

VGA modes for the supported resolutions
 

On Mon,11.Aug.08, 08:42:17, peasthope@shaw.ca wrote:
> Andrei,
>
> ap> $ grep kqemu /etc/modprobe.d/00local
> #options kqemu major=0
> ...
> ...list kqemu in /etc/modules ...
>
> Good. Thanks! kqemu works now.
>
> I still have this message about SDL.
>
> newton:~# qemu -m 40 -hda /dev/sda -cdrom /home/peter/AosCD.iso -boot d
> Could not open SDL display
> newton:~#
>
> libsdl1.2debian-all is installed but "man sdl"
> and "man libsdl" yield nothing. Any tips on
> making SDL work?

I vaguely recall an issue with my mouse related to SDL (which is why I
eventually dropped qemu in favor of virtualbox-ose). Try the qemu docs.

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)