Problem starting X after upgrade to 4.4
Tony Power
tony at witnessthepower.net
Thu Feb 4 15:34:59 PST 2016
Hi guys,
Haven't posted here before, hoping someone can point me in the right
direction please. I'm having some difficulties using the new
xf86-video-intel driver. I originally installed version 4.2 of the OS and
configured X, it started without issue. After upgrading to version 4.4
recently, starting X results in a short and faintly audible high pitched
noise followed by loss of signal to the screen.
Device info -
vgapci0 at pci0:0:2:0: class=0x030000 card=0x01ad1028 chip=0x27728086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82945G/GZ Integrated Graphics Controller'
class = display
subclass = VGA
vgapci1 at pci0:0:2:1: class=0x038000 card=0x01ad1028 chip=0x27768086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82945G/GZ Integrated Graphics Controller'
class = display
Driver -
xf86-video-intel 2.99.917
/var/log/messages (after startx) -
Feb 3 21:58:38 scabb kernel: info: [drm] Initialized drm 1.1.0 20060810
Feb 3 21:58:38 scabb kernel: drm0 on vgapci0
Feb 3 21:58:38 scabb kernel: info: [drm] AGP at 0xd0000000 256MB
Feb 3 21:58:38 scabb kernel: info: [drm] Memory usable by graphics device
= 256M
Feb 3 21:58:38 scabb kernel: iicbus0: <Philips I2C bus> on iicbb0 addr 0xff
Feb 3 21:58:38 scabb kernel: iicbus2: <Philips I2C bus> on iicbb1 addr 0xff
Feb 3 21:58:38 scabb kernel: iicbus4: <Philips I2C bus> on iicbb2 addr 0xff
Feb 3 21:58:38 scabb kernel: iicbus6: <Philips I2C bus> on iicbb3 addr 0xff
Feb 3 21:58:38 scabb kernel: iicbus8: <Philips I2C bus> on iicbb4 addr 0xff
Feb 3 21:58:38 scabb kernel: iicbus10: <Philips I2C bus> on iicbb5 addr 0xff
Feb 3 21:58:38 scabb kernel: info: [drm] Supports vblank timestamp
caching Rev 2
(21.10.2013).
Feb 3 21:58:38 scabb kernel: info: [drm] Driver supports precise vblank
timestamp
query.
Feb 3 21:58:38 scabb kernel: info: [drm] failed to find VBIOS tables
Feb 3 21:58:38 scabb kernel: looking up kenv for "drm.video.vga1"
Feb 3 21:58:38 scabb kernel: didn't find value for kenv drm.video.vga1
Feb 3 21:58:38 scabb kernel: MAPPABLE_END VS END 0000000010000000
0000000010000000
xorg.conf device section -
Section "Device"
Identifier "Card0"
Driver "intel"
BusID "PCI:0:2:0"
EndSection
xorg.0.log -
[ 269.268] X.Org ANSI C Emulation: 0.4
[ 269.268] X.Org Video Driver: 19.0
[ 269.268] X.Org XInput driver : 21.0
[ 269.268] X.Org Server Extension : 9.0
[ 269.268] (--) PCI:*(0:0:2:0) 8086:2772:1028:01ad rev 2, Mem @
0xeff00000/524288,
0xd0000000/268435456, 0xefec0000/262144, I/O @ 0x0000e890/8, BIOS @
0x????????/65536
[ 269.268] (--) PCI: (0:0:2:1) 8086:2776:1028:01ad rev 2, Mem @
0xeff80000/524288
[ 269.268] (II) "glx" will be loaded. This was enabled by default and also
specified in the config file.
[ 269.268] (II) LoadModule: "glx"
[ 269.332] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[ 269.384] (II) Module glx: vendor="X.Org Foundation"
[ 269.384] compiled for 1.17.4, module version = 1.0.0
[ 269.384] ABI class: X.Org Server Extension, version 9.0
[ 269.384] (==) AIGLX enabled
[ 269.384] (II) LoadModule: "intel"
[ 269.426] (II) Loading /usr/local/lib/xorg/modules/drivers/intel_drv.so
[ 269.575] (II) Module intel: vendor="X.Org Foundation"
[ 269.575] compiled for 1.17.4, module version = 2.99.917
[ 269.575] Module class: X.Org Video Driver
[ 269.575] ABI class: X.Org Video Driver, version 19.0
[ 269.575] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 269.575] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 269.575] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 269.575] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200,
6200, P6300
[ 269.575] (--) Using syscons driver with X support (version 2.0)
[ 269.575] (--) using VT number 9
Would anyone know if there is a fix for this? I could fall back to the
vesa driver but would prefer not to if possible.
Cheers,
Tony
More information about the Users
mailing list