Hello,

I have a strange problem which I never had in the past when using a lenovo
laptop with a somewhat identical configuration.

I'm using CURRENT with a lenovo w500 (model 4063-34G). This model has one of
these switchable dual graphics.
(ATI Mobility Radeon FireGL V5700 + Intel's integrated GMA 4500MHD)
<http://www5.pc.ibm.com/de/products.nsf/$wwwPartNumLookup/_NRC34GE?OpenDocume
nt>
<http://www.pcpro.co.uk/reviews/246624/lenovo-thinkpad-w500.html>

(X11 identifies the ati card as a "ati mobility radeon HD 3650)
<http://www.wiroth.net/dmesg.ati>
<http://www.wiroth.net/Xorg.0.log.ati>

For now, I'm using the intel adapter, as the ati adapter is very, very slow
when watching a movie.
I'm using the following display bios settings:
a) Default Primary Video Device: Internal
b) Boot Display Device: ThinkPad LCD
c) Graphics Device: "Integrated Graphics"
d) OS Detection for Switchable Graphics: Disabled

Now, let me explain the problem in my simple words.

I'm dualbooting between windows xp and openbsd:
partition 1 - openbsd current
partition 2 - windows xp

Partition 2 is fully encrypted with truecrypt (http://www.truecrypt.org).

In a non technical terminology when I boot, the following happens:
the Truecrypt prompt/"boot loader" appears, I have two choices:

a) Enter a passphrase to access the windows bootloader
If I choose this option and enter a passphrase the windows xp bootloader
appears and I can still choose to boot into windows xp or openbsd (I have
followed the guidelines at <http://www.openbsd.org/faq/faq4.html#Multibooting>
to add the openbsd partition boot record to the boot.ini of windows xp).
Here is the Xorg.0.log:
<http://www.wiroth.net/Xorg.0.log>
Here is the dmesg:
<http://www.wiroth.net/dmesg.working>

If I boot via a) into Openbsd, X11 _IS_ working, no problem here!

b) Now, if I bypass the authentication and boot directly into openbsd.
The openbsd kernel is loaded, but now I'm _NOT_ able to start X11.
Here is the NON-working Xorg.0.log:
<http://www.wiroth.net/Xorg.0.log.not.working>
Here is the dmesg.boot:
<http://www.wiroth.net/dmesg.not.working>
(I don't think there is a difference between the two DMESG, but I included
them in case someone would like to have a look into it)

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

Thanks a lot for your help!
Didier

Reply via email to