pdl
n00b
Joined: 06 Apr 2006
Posts: 42
|
 Posted: Fri Jan 16, 2009 5:40 pm Post subject: uvesafb will not start |
 |
|
Reading the high-level discussion of bugs 196848 and 245254 didn't help me.
I would like to try uvesafb on a diskless thin client. I get all my source files from the portage tree, and followed the instructions on spock's devsite with care. Boot messages include the following. (The first line may be relevant; googling suggests that this EBDA is not standard.)
| Code: |
Jan 16 07:44:26 chuck v86d: EBDA too big (3fc00), truncating.
Jan 16 07:44:26 chuck uvesafb: Elpin Systems VGA BIOS, Cyrix GX, Version 2.07, OEM: Cyrix, VBE v2.0
Jan 16 07:44:26 chuck uvesafb: Getting mode info block for mode 0x124 failed (eax=0x14f, err=0)
Jan 16 07:44:26 chuck uvesafb: vbe_init() failed with -22
Jan 16 07:44:26 chuck uvesafb: probe of uvesafb.0 failed with error -22
|
I learned enough from reading those bug reports to re-emerge v86d with the debug flag turned on so that it would make me the program testvbe. Here's the output from that:
| Code: |
chuck ~ # testvbe
VBE Version: 2.00
OEM String: Cyrix
OEM Vendor Name: Elpin Systems VGA BIOS
OEM Prod. Name: Cyrix GX
OEM Prod. Rev: Version 2.07
ID attr mode
---------------------------
0100 009f 640x400-8
0101 009f 640x480-8
0102 001f 800x600-4
0103 009f 800x600-8
0104 001f 1024x768-4
0105 009f 1024x768-8
0106 001f 1280x1024-4
0107 009f 1280x1024-8
0108 008f 80x60-4
0109 008f 132x25-4
010a 008f 132x43-4
010b 008f 132x50-4
010c 008f 132x60-4
010d 009f 320x200-15
010e 009f 320x200-16
0110 009f 640x480-15
0111 009f 640x480-16
0113 009f 800x600-15
0114 009f 800x600-16
0116 009f 1024x768-15
0117 009f 1024x768-16
011a 009f 1280x1024-16
0120 009f 320x200-8
0121 009f 320x240-8
0122 009f 320x240-15
0123 009f 320x240-16
Getting Mode Info Block for mode 0124 failed with eax = 014f
|
What I really want is mode 0x11A; what I asked for (see below) is the humbler 0x117.
Some bug disussions suggested compiling uvesafb as a module. My kernel is almost all monolithic, but I did this. The following commands show what I think I am asking uvesafb to do for me. (Note that the requested mode is listed as a possibility by testvbe.)
| Code: |
chuck ~ # cat /proc/cmdline
rw root=/dev/nfs ip=dhcp nfsroot=192.168.2.1:/gentoo/evo/EVO-chuck
chuck ~ # cat /etc/modules.autoload.d/kernel-2.6 | grep -v '#'
uvesafb mode=1024x768-16,vtotal:4
|
My situation is further complicated by doing all the compiling for the actual boot device in a chroot jail on another computer. Inside that environment, I have klibc 1.5.12-r1 and gcc 4.1.2. How all these pieces work together is a bit of a mystery to me. In particular, I cannot say with confidence that leaving a compiled copy of klibc lying around did me any good when compiling v86d or the kernel ... I just trusted portage to acquaint these packages with one another, if an introduction was truly essential.
PS: "uname -a" says
| Code: | | Linux chuck 2.6.26-gentoo-r4 #13 Wed Jan 14 21:19:50 PST 2009 i586 Geode(TM) Integrated Processor by National Semi Geode by NSC GNU/Linux |
Thanks for your interest. Any suggestions? |
|
Kernel & Hardware
