On Tue, Mar 10, 2009 at 11:43:51AM +0000, Didier Wiroth wrote: > > > Here is a snip of the error message: > > > (II) Loading /usr/X11R6/lib/modules//libvgahw.so > > > (II) Module vgahw: vendor="X.Org Foundation" > > > compiled for 1.5.3, module version = 0.1.0 > > > ABI class: X.Org Video Driver, version 4.1 > > > (II) intel(0): Creating default Display subsection in Screen section > > > "Builtin Default intel Screen 0" for depth/fbbpp 24/32 > > > (==) intel(0): Depth 24, (--) framebuffer bpp 32 > > > (==) intel(0): RGB weight 888 > > > (==) intel(0): Default visual is TrueColor > > > (II) intel(0): Integrated Graphics Chipset: Intel(R) Mobile IntelB. > > GM45 > > > Express Chipset > > > (--) intel(0): Chipset: "Mobile IntelB. GM45 Express Chipset" > > > (--) intel(0): Linear framebuffer at 0xD0000000 > > > (--) intel(0): IO registers at addr 0xF4400000 > > > (EE) intel(0): Unable to map mmio range. Invalid argument (22) > > > > > > Fatal server error: > > > Caught signal 11. Server aborting > > > > > > > Can you send us the pcidump -v output for both cases? > > > > Also what kind of interface is truecrypt using? Is it switching to > > some graphics mode that would change the state of the card in some > > way? > > > > -- > > Matthieu Herrb > > Yes, but unfortunately there is no difference between the 2 pcidump files, > both files are identical :-/ > > 1) http://www.wiroth.net/error/x11/W500.pcidump.not.working > 2) http://www.wiroth.net/error/x11/W500.pcidump.working > > > The truecrypt bootloader is loaded before any OS is loaded. To me, it looks > like a standard text console (but I must admit I'm not (very) technical). > http://www.wiroth.net/error/x11/1_truecrypt_bootloader.jpg > > 1) The working case: > I enter a Passphrase to access the "windows xp" bootloader, from here, I > choose to boot Openbsd, see here: > http://www.wiroth.net/error/x11/2_a_xp_bootloader_working.jpg > When I follow this boot procedures, I can start X11. > > 2) The failing case: > If I choose to bypass Passphrase authentication in Truecrypt by pressing ESC, > the OpenBSD boot prompt appears immediately and OpenBSD starts to boot > normally, see here: > http://www.wiroth.net/error/x11/2_b_bypass_xp_bootloader_and_load_openbsd.jpg > But now, it is not possible to start x11, I get the error message seen > previously in this message. The weird thing is that "pcidump -v" does not show > any difference .... > > If you need any additional information I let me know!
pcidump -xx output for both cases. normally the more interesting result anyway. oh, and the data you're passing on not to be MIME attached, the list strips those. -0- -- "See - the thing is - I'm an absolutist. I mean, kind of ... in a way ..."
