On Tue, 2016-04-26 at 14:43 +0200, Harald Dunkel wrote: > Without GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX I get > > Apr 26 13:07:57 usbpc kernel: [ 18.245417] AES CTR mode by8 optimization > enabled > Apr 26 13:07:57 usbpc kernel: [ 18.256518] alg: No test for > fips(ansi_cprng) (fips_ansi_cprng) > Apr 26 13:07:57 usbpc kernel: [ 18.271819] fbcon: mgadrmfb (fb0) is primary > device > Apr 26 13:07:57 usbpc kernel: [ 18.340257] ipmi_si IPI0001:00: Found new > BMC (man_id: 0x000157, prod_id: 0x0048, dev_id: 0x21) > Apr 26 13:07:57 usbpc kernel: [ 18.340261] ipmi_si IPI0001:00: IPMI kcs > interface initialized > Apr 26 13:07:57 usbpc kernel: [ 18.539515] Console: switching to colour > frame buffer device 160x64 > Apr 26 13:07:57 usbpc kernel: [ 18.577386] mgag200 0000:03:00.0: fb0: > mgadrmfb frame buffer device > Apr 26 13:07:57 usbpc kernel: [ 18.585608] [drm] Initialized mgag200 1.0.0 > 20110418 for 0000:03:00.0 on minor 0 > Apr 26 13:07:57 usbpc kernel: [ 18.588803] intel_rapl: Found RAPL domain > package > Apr 26 13:07:57 usbpc kernel: [ 18.588817] intel_rapl: Found RAPL domain > core > > The console output doesn't get stuck, either. > > > > > That might be an effect of the driver being confused by GRUB's > > modesetting. I don't know. > Maybe. OTOH, upstream's kernel (built on unstable) just works, > using the same grub configuration, installed on the same bootable > USB stick and booted on the same hardware.
I'm guessing that you didn't built the mgag200 driver (CONFIG_DRM_MGA),
right?
> Do you think there could be a side effect of the recent patch
> cleanup for mgag200 & cirrus done for 4.4~rc5-1~exp1?
Yes, very likely.
Ben.
--
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou
signature.asc
Description: This is a digitally signed message part
