Control: tag -1 moreinfo On Sun, 2017-01-15 at 01:32 +0100, Axel Beckert wrote: > Package: src:linux > Version: 4.9.2-2 > Severity: important > > Dear Debian Linux Kernel Maintainers, > > booting linux-image-4.9.0-1-amd64/4.9.2-2 instead of > linux-image-4.8.0-2-amd64/4.8.15-2 (or > linux-image-4.8.0-2-grsec-amd64/4.8.15-2+grsec201701031913+1) shows a > severe regression on my system wrt. to X.org: > > With 4.8.15-2, all three screens, USB mouse and USB keyboard work fine > under X and the screens have the expected resolutions. > > With 4.9.2-2, several things failed: > > * X is only shown on two of three screens and both show the same > contents instead of different content. > > * Resolution is only (1x) 1024x768 instead of the expected 1920x1080 + > 1280x720 (+ 2048x1152) This looks like X is having to use a generic vesa driver. > * As soon as X starts, neither USB keyboard nor mouse are working > anymore under X. Pressing Ctrl-Alt-F1 to get to a text console has no > effect. (I do get a text console if I login remotely via SSH as root > and call "chvt 1". On the text console the USB keyboard is working > again.) I don't know why that would happen, though. > The most relevant difference from the two Xorg.0.log files seems to be: > > 4.8: (II) xfree86: Adding drm device (/dev/dri/card0) > 4.8: xf86EnableIOPorts: failed to set IOPL for I/O (No such device) > 4.8: (II) modeset(0): using drv /dev/dri/card0 > 4.8: (WW) Falling back to old probe method for fbdev > > 4.9: (EE) open /dev/dri/card0: No such file or directory > 4.9: (WW) Falling back to old probe method for modesetting > 4.9: (EE) open /dev/dri/card0: No such file or directory This confirms X didn't find a DRM/KMS driver. [...] > 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) > Subsystem: ASRock Incorporation HD Graphics 530 [1849:1912] > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin A routed to IRQ 11 > Region 0: Memory at de000000 (64-bit, non-prefetchable) [size=16M] > Region 2: Memory at c0000000 (64-bit, prefetchable) [size=256M] > Region 4: I/O ports at f000 [size=64] > [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] > Capabilities: <access denied> [...] And no driver is bound to the graphics device. This device is still listed in i915's device ID table, so it should have been loaded and would then have probed the device (even though that may have failed). Yet it's not even on the loaded module list. Does 'modprobe i915' have any effect? Ben. -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out.
Attachment:
signature.asc
Description: This is a digitally signed message part