Discussion:
fbdev requirement of qemu
(too old to reply)
PETER EASTHOPE
2008-07-10 01:30:11 UTC
Permalink
Folk,

I've installed qemu, xserver-xorg-video-fbdev and libggi-target-fbdev
and tried to boot an image.

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

This error report ensues.
=======================| DirectFB 1.0.1 |=======================
(c) 2001-2007 The DirectFB Organization (directfb.org)
(c) 2000-2004 Convergence (integrated media) GmbH
------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2008-05-15 14:24)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
--> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system' core!
--> Initialization error!
Could not initialize SDL - exiting
========================================

qemu has no 'fbdev' option that I can see.
Is another package needed to make fbdev work?

Thanks for any ideas, ... Peter E.
--
http://members.shaw.ca/peasthope/
http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/
--
To UNSUBSCRIBE, email to debian-user-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Richard Möhn
2008-07-12 09:50:18 UTC
Permalink
Post by PETER EASTHOPE
I've installed qemu, xserver-xorg-video-fbdev and libggi-target-fbdev
and tried to boot an image.
qemu -m 40 -boot d -cdrom /home/peter/Desk*/AosCD.iso
This error report ensues.
=======================| DirectFB 1.0.1 |=======================
(c) 2001-2007 The DirectFB Organization (directfb.org)
(c) 2000-2004 Convergence (integrated media) GmbH
------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2008-05-15 14:24)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
--> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system' core!
--> Initialization error!
Could not initialize SDL - exiting
========================================
qemu has no 'fbdev' option that I can see.
Is another package needed to make fbdev work?
Thanks for any ideas, ... Peter E.
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
--
To UNSUBSCRIBE, email to debian-user-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Richard Möhn
2008-07-12 16:10:08 UTC
Permalink
Post by Richard Möhn
Post by PETER EASTHOPE
I've installed qemu, xserver-xorg-video-fbdev and libggi-target-fbdev
and tried to boot an image.
qemu -m 40 -boot d -cdrom /home/peter/Desk*/AosCD.iso
This error report ensues.
=======================| DirectFB 1.0.1 |=======================
(c) 2001-2007 The DirectFB Organization (directfb.org)
(c) 2000-2004 Convergence (integrated media) GmbH
------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2008-05-15 14:24)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
--> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system' core!
--> Initialization error!
Could not initialize SDL - exiting
========================================
qemu has no 'fbdev' option that I can see.
Is another package needed to make fbdev work?
Thanks for any ideas, ... Peter E.
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:

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 0x031d: 640x400 (+1280), 16 bits
Mode 0x031e: 640x400 (+2560), 24 bits
Mode 0x0320: 1600x1200 (+1600), 8 bits
Mode 0x0322: 1600x1200 (+3200), 16 bits
Mode 0x0324: 1600x1200 (+6400), 24 bits
Mode 0x032a: 640x480 (+1920), 24 bits
Mode 0x032b: 800x600 (+2400), 24 bits
Mode 0x032c: 1024x768 (+3072), 24 bits
Mode 0x032d: 1280x1024 (+3840), 24 bits
Mode 0x032e: 320x200 (+320), 8 bits
Mode 0x0331: 320x240 (+320), 8 bits
Mode 0x0333: 320x240 (+640), 16 bits
Mode 0x0334: 320x240 (+1280), 24 bits
Mode 0x033b: 1400x1050 (+1400), 8 bits
Mode 0x033c: 1400x1050 (+2800), 16 bits
Mode 0x033e: 1400x1050 (+5600), 24 bits
Mode 0x0341: 400x300 (+400), 8 bits
Mode 0x0343: 400x300 (+800), 16 bits
Mode 0x0344: 400x300 (+1600), 24 bits
Mode 0x0351: 512x384 (+512), 8 bits
Mode 0x0353: 512x384 (+1024), 16 bits
Mode 0x0354: 512x384 (+2048), 24 bits
Mode 0x0371: 720x480 (+720), 8 bits
Mode 0x0373: 720x480 (+1440), 16 bits
Mode 0x0374: 720x480 (+2160), 24 bits
Mode 0x0375: 720x480 (+2880), 24 bits
Mode 0x0376: 720x576 (+720), 8 bits
Mode 0x0378: 720x576 (+1440), 16 bits
Mode 0x0379: 720x576 (+2160), 24 bits
Mode 0x037a: 720x576 (+2880), 24 bits

So you have to add the value beginning with "0x" that matches to your video
settings to the kernel line in the /boot/grub/menu.lst.

Richard
--
To UNSUBSCRIBE, email to debian-user-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Andrei Popescu
2008-07-13 14:30:14 UTC
Permalink
Post by Richard Möhn
Post by Richard Möhn
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
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)
p***@shaw.ca
2008-07-13 16:10:14 UTC
Permalink
Hello Richard Möhn and Andrei Popescu,

rm> ... since I cannot answer soon if you will not reply today ...

Sorry. I am not ignoring replies. Work
prevented attention before the weekend.

rm> ... installed hwinfo and that printed this list ...

Many thanks. Will try specifying video modes
when at work in Vancouver this week and try to
report success or failure by the next weekend.

ap> I'm using vga=0x368 ...

Logically, the reason for specifying a video
mode at startup is not obvious. Why can't qemu
and directfb proceed using a default video mode?

Thanks, ... Peter E.
--
http://carnot.yi.org/
= http://carnot.pathology.ubc.ca/
Desktops.OpenDoc http://members.shaw.ca/peasthope/
--
To UNSUBSCRIBE, email to debian-user-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Loading...