> > 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:
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)
07-17-2008, 02:12 AM
PETER EASTHOPE
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:~#
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
07-17-2008, 08:02 AM
Andrei Popescu
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)
07-22-2008, 02:11 AM
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.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
08-11-2008, 07:20 AM
Andrei Popescu
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)
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
08-11-2008, 04:26 PM
Andrei Popescu
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)
VGA modes for the supported resolutions
