Skip to content
Snippets Groups Projects
New look: Off

qemu-vexpress not booting since kernel 4.14

    • Closed Imported Issue created by Administrator @root

    It's not booting since linux-postmarketos-stable 4.14 (3f7b44a9). It does boot with the prior kernel 4.13.12 (e70d09b6)

    I used the current pmbootstrap master and compiled the kernels in this environment rather than checking out old revisions of pmbootstrap. So it seems to be the kernel itself and not likely pmbootstrap environment.

    It does boot kernel 4.16 compiled with vexpress_defconfig. I think it's some config in config-postmarketos-stable.armhf. No configs were manually changed between 4.13.12 and 4.14. The differences are all a result of the autogenerated config going from 4.13 to 4.14. So it's possibly some new default maybe.

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Administrator mentioned in merge request !1615 (merged) · Imported

      mentioned in merge request !1615 (merged)

      By Oliver Smith on 2018-07-08T21:38:25

    • Administrator
      Administrator @root · Imported
      Author Owner

      We have not changed much from the default config, from what I can tell with git log on the config file. Notable changes were:

      • enable modules needed for wireguard (!1231 (merged))
      • make sure that these are enabled: CONFIG_DRM_VIRTIO_GPU, CONFIG_VIRTIO_PCI, CONFIG_VIRTIO_BALLOON (!861 (merged))

      Would you like to create a new config, based on vexpress_defconfig, that works with the updated kernels?

      Thank you very much for opening the issue, and for your analysis @ryang2678!

      By Oliver Smith on 2018-07-09T20:09:25

    • Administrator
      Administrator @root · Imported
      Author Owner

      Here's a branch for linux-postmarketos-stable with a config based on vexpress_defconfig:
      https://gitlab.com/ryang2678/pmbootstrap/tree/qemu-vexpres-config

      Based on the git log I've enabled the configs for DRM QXL, namespaces, DRM Virtio GPU, and Wireguard. These are untested. I tried QXL with QEMU -vga qxl but it doesn't seem to work for ARM guests on x86_64 host anyways.

      The nokia-n900 uses this kernel too. Someone would need to get that device working with the vexpress based config. I can't do it since I don't have this device.

      The same would apply for linux-postmarketos-mainline. The sony-amami device uses that kernel. We could created a config based on vexpress but it would need someone to get that config working with amami.

      By ryang on 2018-07-10T16:15:15

    • Administrator
      Administrator @root · Imported
      Author Owner

      I tried QXL with QEMU -vga qxl but it doesn't seem to work for ARM guests on x86_64 host anyways.

      Thanks for testing, then it doesn't make sense to enable it anymore.

      The nokia-n900 uses this kernel too. Someone would need to get that device working with the vexpress based config. I can't do it since I don't have this device.

      Sure, there are enough people with a N900 running postmarketOS.

      @MartijnBraam: you adjusted the linux-postmarketos-stable kernel config for the N900 last time, would you like to take it from here?

      The same would apply for linux-postmarketos-mainline. The sony-amami device uses that kernel. We could created a config based on vexpress but it would need someone to get that config working with amami.

      The amami barely boots with the mainline kernel (I'm not sure if the screen is even working), and mainlining progress has halted. I would advise to remove the dts patch and remove the mainline kernel subpackage from the amami device package, and when mainlining the amami continues, then it would make more sense to base it on linux-postmarketos-qcom. We could link the current mainlining progress in the device's wiki page, so it can easily be picked up again.

      Thank you very much @ryang2678!

      By Oliver Smith on 2018-07-11T19:42:37

    • Administrator
      Administrator @root · Imported
      Author Owner

      Sure, there are enough people with a N900 running postmarketOS.

      @MartijnBraam: you adjusted the linux-postmarketos-stable kernel config for the N900 last time, would you like to take it from here?

      The current config looks like originated from the N900 device and was adapted to include vexpress.

      Perhaps it might be more prudent to try getting N900 working with multi_v7_defconfig. This appears to be a config that targets multiple ARMv7 platforms. Vexpress on QEMU does work with this config. And maybe even rpi aswell (https://wiki.gentoo.org/wiki/Raspberry_Pi/Mainline_Kernel#Configure_the_kernel).

      By ryang on 2018-07-11T22:21:30

    • Administrator
      Administrator @root · Imported
      Author Owner

      Yeah @ryang2678 is right, the linux-postmarketos kernel is actually based on the linux-postmarketos-omap kernel I made first in 4eff2fea which was then edited to make it boot in qemu with the vexpress drivers (78cfdc9f)

      This might also be why its now broken. I think it might be possible to fully merge defconfig_vexpress and defconfig_rx51 to make the linux-postmarketos-* configs

      By Martijn Braam on 2018-07-13T20:42:40

      Edited by Administrator
    • Administrator moved to pmaports#40 (closed) · Imported

      moved to pmaports#40 (closed)

      By Bart Ribbers on 2018-09-17T21:47:53

    Please register or sign in to reply