I'm using LinuxBIOS and when I boot into Linux 2.6.17 and start X, it can't find
my video bios, so it checks the default location (V_BIOS 0xC0000) and gives me
(EE) ATI(0): V_BIOS address 0x3e0 out of range. I changed the constant to 0xc000
and it worked and found the bios. I think it is an endian problem and that the
constant should be run through an Endian converter before being used.
Created attachment 8647 [details]
Same here, Linux, AMD64 architecture.
News ... when forcing the correct location by adding:
Option "BiosLocation" "786432"
int10 uses 0xC0000 (=786432 decimal) and happily proceeds, but then X hangs hard right after loading the DDC and VBE extensions - no crash, but 100% CPU load, nothing happening, no reaction to normal kill, only kill -9 helps. (Same setup as in previous logfile)
Paired with #9920, I'm tempted to believe that the int10 infrastructure is seriously b0rked on Linux/AMD64.
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
hmm, seems to work fine on amd64 (which is little-endian) these days. closing speculatively since there's been a hell of a lot work done on int10/x86emu since then: please reopen if this is still a problem for you.
(In reply to comment #4)
> hmm, seems to work fine on amd64 (which is little-endian) these days. closing
> speculatively since there's been a hell of a lot work done on int10/x86emu
> since then: please reopen if this is still a problem for you.
Closing the bug per above comment.