This is virtually the same bug as 190631 (which was closed unsolved). starting xorg with an i810e without xorg.conf + hal gives errors unknown type(0xffffffff)=0xff and VESA BIOS not detected The main differences are: intel driver instead of i810 xorg doesn't crash but starts up relevant xorg.conf entries (II) Module int10: vendor="X.Org Foundation" compiled for 1.5.3, module version = 1.0.0 ABI class: X.Org Video Driver, version 4.1 (II) intel(0): initializing int10 (II) intel(0): Primary V_BIOS segment is: 0xc000 (EE) intel(0): unknown type(0xffffffff)=0xff (II) intel(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, EDX=0x00000000 (II) intel(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, EDI=0x00002000 (II) intel(0): CS=0xc000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, GS=0x0000 (II) intel(0): EIP=0x00000dbc, EFLAGS=0x00003200 (II) intel(0): code at 0x000c0dbc: fb fc 66 50 66 53 66 51 66 52 56 57 55 06 1e 8b ec ba d4 03 ec 50 ba ce 03 ec 50 ba c4 03 ec 50 (II) stack at 0x00001ffa: 00 06 00 00 00 32 (II) intel(0): VESA BIOS not detected (II) intel(0): this driver cannot do DDC without VBE (--) intel(0): Chipset: "i810e" (--) intel(0): Linear framebuffer at 0xE8000000 (--) intel(0): IO registers at addr 0xEFF80000 (II) intel(0): Kernel reported 51712 total, 1 used (II) intel(0): I810CheckAvailableMemory: 206844k available (==) intel(0): Will alloc AGP framebuffer: 24576 kByte (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
Created attachment 190422 [details] Xorg.0.log
Created attachment 190424 [details] output of emerge --info
(In reply to comment #0) > The main differences are: > intel driver instead of i810 > xorg doesn't crash but starts up So it works then???
Please get back to us. Thanks
Yes, xorg seems to work. However, I would expect this 'symptom' not to appear at all, and that it might affect other things (e.g. when it says 'vesa bios not detected', I suspect this might cause e.g. problems when trying framebuffer, or it might have impact on what you can do with xrandr. In other words, I believe that although the report doesn't seem to have an ill effect today, that I think it might pop up in later situations. I would agree however, that this is definitely not a high priority. On the other hand, if I can provide additional useful input, I will do so. P.S. I am traveling a lot, with sometimes limited email access that I then use preferably for work, so replying can indeed sometimes take a while. Br
(In reply to comment #5) > Yes, xorg seems to work. Glad to hear that. > However, I would expect this 'symptom' not to appear at all The thing is, i810e is considered a very old chipset. Given all the code churn done in the past few months, it's amazing old chips even still work given they saw nearly no testing by those writing the drivers... > and that it might affect other things (e.g. when it says 'vesa bios not > detected', I suspect this might cause e.g. problems when trying framebuffer, or > it might have impact on what you can do with xrandr. In other words, I believe > that although the report doesn't seem to have an ill effect today, that I think > it might pop up in later situations. > I would agree however, that this is definitely not a high priority. On the > other hand, if I can provide additional useful input, I will do so. My suggestion here is for you to keep an eye on how your system behaves. Unless things go wrong, let's just ignore this and hope for the best. Please don't hesitate to open new bugs should anything go wrong Thanks
And closing with the proper resolution. Thanks
