Pierre Labastie wrote:
Le 03/03/2015 12:23, Fernando de Oliveira a écrit :
On 03-03-2015 06:15, Pierre Labastie wrote:
[...]
I just tagged the last server/ packages. About x/, the problems are:
- I have not been able to use the vesa driver with server-1.17.1. It
builds OK, though, and I can tag it lfs77_built.
Vesa works fine with VMware, although not with the good resolution I
want. Cannot test now, as I said above.
I must be wrong somewhere. For me, whatever the kernel configuration and the
qemu vga emulation, vesa never starts.
I tried on my HW (nvidia), but got:
[ 479.537] (II) LoadModule: "vesa"
[ 479.537] (II) Loading /opt/xorg/lib/xorg/modules/drivers/vesa_drv.so
[ 479.537] (II) Module vesa: vendor="X.Org Foundation"
[ 479.537] compiled for 1.17.1, module version = 2.3.3
[ 479.537] Module class: X.Org Video Driver
[ 479.537] ABI class: X.Org Video Driver, version 19.0
[ 479.537] (II) VESA: driver for VESA chipsets: vesa
[ 479.537] (++) using VT number 1
[ 479.537] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 479.537] vesa: Ignoring device with a bound kernel driver
[ 479.537] (WW) Falling back to old probe method for vesa
[ 479.537] (EE) Screen 0 deleted because of no matching config section.
[ 479.537] (II) UnloadModule: "vesa"
[ 479.537] (EE) Device(s) detected, but none match those in the config file.
[ 479.537] (EE)
Fatal server error:
[ 479.537] (EE) no screens found(EE)
I tried removing nvidia/nouvou support from the kernel and it still didn't work.
This time I got:
[ 59.339] (II) LoadModule: "vesa"
[ 59.339] (II) Loading /opt/xorg/lib/xorg/modules/drivers/vesa_drv.so
[ 59.340] (II) Module vesa: vendor="X.Org Foundation"
[ 59.340] compiled for 1.17.1, module version = 2.3.3
[ 59.340] Module class: X.Org Video Driver
[ 59.340] ABI class: X.Org Video Driver, version 19.0
[ 59.340] (II) VESA: driver for VESA chipsets: vesa
[ 59.340] (++) using VT number 1
[ 59.340] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 59.345] (II) Loading sub module "vbe"
[ 59.345] (II) LoadModule: "vbe"
[ 59.345] (II) Loading /opt/xorg/lib/xorg/modules/libvbe.so
[ 59.345] (II) Module vbe: vendor="X.Org Foundation"
[ 59.345] compiled for 1.17.1, module version = 1.1.0
[ 59.345] ABI class: X.Org Video Driver, version 19.0
[ 59.345] (II) Loading sub module "int10"
[ 59.345] (II) LoadModule: "int10"
[ 59.345] (II) Loading /opt/xorg/lib/xorg/modules/libint10.so
[ 59.347] (II) Module int10: vendor="X.Org Foundation"
[ 59.347] compiled for 1.17.1, module version = 1.0.0
[ 59.347] ABI class: X.Org Video Driver, version 19.0
[ 59.347] (II) VESA(0): initializing int10
[ 59.347] (EE) VESA(0): Cannot read int vect
[ 59.347] (II) UnloadModule: "vesa"
Google says it's a bug in xorg:
https://bugs.freedesktop.org/show_bug.cgi?id=89353
Note that I did not use the fix_modesetting patch for xorg-server.
I'll try reverting the change in xorg-server and see if that makes a difference.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
