[Xorg-driver-geode] Xorg.0.log for GEODE on FreeBSD

[Jordan Crouse]

On 18/12/07 19:21 -0800, Larry Maloney wrote:
> I thought I would share my Xorg.0.log
>
> I can use the Generic VGA drivers OK. 
> VESA doesn't seem to work for me.
>
> I can't compile the drivers for FreeBSD, cause it appears the Make is setup 
> for Linux.

Indeed.  Most of the users of the drivers are very Linux centric, and I
apologize for being so selfish. :)

> I can try to modify the build/drivers for FreeBSD if anyone can tell me if 
> I should be able to do that.....

I don't see why not.  We'll gladly take any patches you can give us.

> If I run X -configure I get the following:
>
> II) Loading sub module "int10"
> (II) LoadModule: "int10"
> (II) Reloading /usr/local/lib/xorg/modules//libint10.so
> (II) VESA(0): initializing int10
> (==) VESA(0): Write-combining range (0xa0000,0x20000) was already clear
> (II) VESA(0): Primary V_BIOS segment is: 0xc000
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (II) VESA(0): VESA BIOS detected
> (II) VESA(0): VESA VBE Version 2.0
> (II) VESA(0): VESA VBE Total Mem: 8192 kB
> (II) VESA(0): VESA VBE OEM: Advanced Micro Devices
> (II) VESA(0): VESA VBE OEM Software Rev: 1.0
> (II) VESA(0): VESA VBE OEM Vendor: Elpin Systems VGA BIOS
> (II) VESA(0): VESA VBE OEM Product: GEODE LX
> (II) VESA(0): VESA VBE OEM Product Rev: Version 6.12
> (WW) VESA(0): Failed to set write-combining range (0xee000000,0x800000)
> (II) VESA(0): virtual address = 0x2873f000,
>    physical address = 0xee000000, size = 8388608
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (==) VESA(0): Write-combining range (0x0,0x1000) was already clear
> (II) VESA(0): VBESetVBEMode failed(==) VESA(0): Write-combining range 
> (0x0,0x1000) was already clear
> c000:0282: A2 ILLEGAL EXTENDED X86 OPCODE!

Ouch.  This looks like vesa is behaving badly.  Wouldn't be the first time.

> I wonder if this is because I compiled my kernel and world with an 
> optimization flag that isn't liked?
>
> I used -march=i586, enabled 3dNow and mmx.

Those should be correct.  

I'm looking forward to what you come up with.

Thanks,
Jordan