Skip to content
Snippets Groups Projects
New look: Off

supervise-lightdm not found - No desktop at all.

    • Closed Imported Issue created by Administrator @root

    Describe your issue

    What's the expected behaviour?

    I installed pmos edge on espressowifi (i.e. espresso3g or Samsung Galaxy Tab 2) for the first time following instructions in wiki. It should at least be able to show any DE or GUI that doesn't use Wayland, but doesn't. Neither xfce4 nor mate nor any other flavor I tried worked.

    What's the current behaviour?

    The best I receive is an empty black screen with one white blinking cursor.

    How to reproduce your issue?

    Install pmos with pmbootstrap init and install and finally flasher via sideload. Boot system.

    What device are you using?

    espressowifi (espresso3g)

    On what postmarketOS version did you encounter the issue?

    • edge (master branch)
    • v21.12

    On what environment did you encounter the issue?

    Phone environments

    • Phosh
    • Plasma Mobile
    • Sxmo (Wayland/Sway)

    Other

    • No environment
    • GNOME
    • KDE Plasma
    • Kodi
    • MATE
    • Shelli
    • Sway
    • Weston
    • Xfce4
    • fbkeyboard
    • i3wm
    • Sxmo (Xorg/Dwm)

    How did you get postmarketOS image?

    What's the build date of the image? (in yyyy-mm-dd format)

    2022-02-20

    Additional information

     * status: stopped
samsung-espressowifi:~$ sudo rc-service lightdm start --verbose
 * Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh /etc/init.d/lightdm start
 * Starting Display Manager ...
 * supervise-daemon: fopen `/var/run/supervise-lightdm.pid': No such file or directory
 * Detaching to start `/usr/bin/lightdm'                                  [ ok ]
samsung-espressowifi:~$

    I sshd into device and first found that lightdm wasn't running. Tried to restart and received this message. Tried to install tinydm while building the image and start but also with no success. As far as I read lightdm should start by default after installing image, shouldnt it?

    Maybe X-log helps?

    [    80.040] (==) Matched fbdev as autoconfigured driver 1
[    80.040] (==) Assigned the driver to the xf86ConfigLayout
[    80.040] (II) LoadModule: "modesetting"
[    80.040] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    80.044] (II) Module modesetting: vendor="X.Org Foundation"
[    80.044] 	compiled for 1.21.1.3, module version = 1.21.1
[    80.044] 	Module class: X.Org Video Driver
[    80.044] 	ABI class: X.Org Video Driver, version 25.2
[    80.044] (II) LoadModule: "fbdev"
[    80.044] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    80.045] (II) Module fbdev: vendor="X.Org Foundation"
[    80.045] 	compiled for 1.21.1.1, module version = 0.5.0
[    80.045] 	Module class: X.Org Video Driver
[    80.045] 	ABI class: X.Org Video Driver, version 25.2
[    80.045] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    80.046] (II) FBDEV: driver for framebuffer: fbdev
[    80.046] (++) using VT number 7

[    80.046] (WW) Falling back to old probe method for modesetting
[    80.056] (II) modeset(0): using default device
[    80.056] (WW) Falling back to old probe method for fbdev
[    80.056] (II) Loading sub module "fbdevhw"
[    80.056] (II) LoadModule: "fbdevhw"
[    80.057] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    80.057] (II) Module fbdevhw: vendor="X.Org Foundation"
[    80.057] 	compiled for 1.21.1.3, module version = 0.0.2
[    80.057] 	ABI class: X.Org Video Driver, version 25.2
[    80.057] (II) FBDEV(1): using default device
[    80.067] (II) modeset(G0): using drv /dev/dri/card0
[    80.067] (EE) 
Fatal server error:
[    80.068] (EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
[    80.069] (EE) 
[    80.069] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    80.069] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    80.069] (EE) 
[    80.094] (EE) Server terminated with error (1). Closing log file.
samsung-espressowifi:/var/log#

    lightdm.log throws

    [+0.22s] DEBUG: Process 1841 exited with return value 1
[+0.22s] DEBUG: XServer 0: X server stopped
[+0.22s] DEBUG: Releasing VT 7
[+0.22s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.22s] DEBUG: Seat seat0: Display server stopped
[+0.22s] DEBUG: Seat seat0: Stopping session
[+0.22s] DEBUG: Seat seat0: Session stopped
[+0.22s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.22s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+0.22s] DEBUG: Seat seat0: Creating greeter session
[+0.22s] DEBUG: Seat seat0: Failed to find session configuration lightdm-gtk-greeter
[+0.22s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+0.22s] DEBUG: Seat seat0: Stopping
[+0.22s] DEBUG: Seat seat0: Stopped
[+0.22s] DEBUG: Required seat has stopped
[+0.22s] DEBUG: Stopping display manager
[+0.22s] DEBUG: Display manager stopped
[+0.22s] DEBUG: Stopping daemon
[+0.23s] DEBUG: Exiting with return value 1
samsung-espressowifi:/var/log#

    and x-0.log

    samsung-espressowifi:/var/log# tail -n40 lightdm/x-0.log

X.Org X Server 1.21.1.3
X Protocol Version 11, Revision 0
Current Operating System: Linux samsung-espressowifi 5.15.2 #5-postmarketOS SMP PREEMPT Thu Jan 6 00:18:50 UTC 2022 armv7l
Kernel command line: console=tty0 PMOS_NO_OUTPUT_REDIRECT ignore_loglevel
 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 21 18:24:40 2022
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
samsung-espressowifi:/var/log#

    Maybe s.o. has a hint for me. As I am rather new to pmos I`m probably doing sth wrong?

    5 of 20 checklist items completed
    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
      Administrator @root · Imported
      Author Owner

      CC @MightyM17

      By Newbyte on 2022-02-21T19:48:46

    • Administrator added category::device label · Imported

      added category::device label

    • Administrator added device-samsung-espresso7 label · Imported

      added device-samsung-espresso7 label

      • Administrator
        Administrator @root · Imported
        Author Owner

        Looks like some issue with graphics. In Xorg logs (WW) are warnings and (EE) are errors. The point of failure is:

        (EE) Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices

        Doesn't seem to be related to lightdm. X11 fails to start because of some graphics driver issue (at least that's my interpretation). Without X11, lightdm can't start.

        By Jakko on 2022-02-21T22:55:40

        Edited by Ghost User
      • Administrator
        Administrator @root · Imported
        Author Owner

        Or maybe something wrong with the xorg config file (source) installed at /etc/X11/xorg.conf.d/99-modesetting.conf. However, I wouldn't modify this file until there is more feedback on this.

        By Jakko on 2022-02-21T22:55:40

      • Administrator
        Administrator @root · Imported
        Author Owner

        Yeah it seems like our gpu doesnt like x11, wayland (for eg phosh) should work just fine, anyways going to switch to pure mainline soon. The wiki says wayland will work.

        By Mighty on 2022-02-22T07:27:28

        Edited by Administrator
      • Administrator
        Administrator @root · Imported
        Author Owner

        You mean it will work with wayland out of the box then? without the need to patch you mention in the wiki? So maybe I better let the device lie and wait for that switch :thinking:

        By Homer S. on 2022-02-22T08:14:07

      • Administrator
        Administrator @root · Imported
        Author Owner

        I dont really know when I will get time to make the switch, so what works is phosh (with the patched wlroots). Xfce worked for me back when I tried, with a new modsetting, but things might have changed now, its that the powervr gpu blobs dont like x11. Pure mainline will not have gpu tho*

        By Mighty on 2022-02-22T08:36:50

      • Administrator
        Administrator @root · Imported
        Author Owner

        I don't depend on the device. So there's no special hurry in my case. I guess I have yet enough to learn how to install everything properly until you do :smile: Thank you for your help!

        By Homer S. on 2022-02-22T10:49:40

      • Administrator
        Administrator @root · Imported
        Author Owner

        We wont be able to use HW accelerated UIs with pure mainline so its like we win some we lose some, for now phosh is the best option, if you have trouble installing it please ask :D

        By Mighty on 2022-02-22T14:32:54

      • Administrator
        Administrator @root · Imported
        Author Owner

        Thanks for offering! :smile: Actually I do have some problems with installation. But should I ask here or will I find you anywhere in the matrix-groups? Just not to spam this issue with not exactly related questions ...

        Because I yet managed to install pmos with phosh on the device, I could even start the wifi, but then after I lay it aside and tried to turn it on again after a while I had to hold the power-button to have the screen lit. After leaving the powerbutton the screen got black immediately again. I tried to unlock screen by holding the power button - which of course made the device restart before I could :face_palm:

        Well, an when I let the device start again it couldn't write any longer on data-partition (on which I installed pmos) and in recovery I also cannot mount data or repair it or whatever. So it seems the system is broken and I would have to reset it completely to factory status again?

        Additionally: I tried to install it with -fde paramater but it denied because couldn`t find /run/luksdevice ...

        It`s all a bit tricky :grimacing:

        By Homer S. on 2022-02-22T14:50:05

      • Administrator
        Administrator @root · Imported
        Author Owner

        We do have power button support, just clicking it will show you the lock screen and you can unlock it. It always worked for me, about the data partition, TWRP cannot read what pmOS so it complains about /data or /system wherever you installed it. couldn't write any longer on data-partition can you send any logs or smth? You can contact me as mighty17 on matrix.

        By Mighty on 2022-02-23T04:33:50

      • Please register or sign in to reply
      • Administrator
        Administrator @root · Imported
        Author Owner

        You should be able to run xfce/mate/shelli etc now, please tell how it works so I can close this issue

        By Mighty on 2022-04-03T19:51:16

        Edited by Ghost User
      • Administrator
        Administrator @root · Imported
        Author Owner

        I tried sxmo-dwm, sxmo-sway and xfce4. Everything starts fine, xfce4 works. sxmo doesn't work after start. At least I wasn't able to use it neither by buttons nor by gestures. It's a pitty.

        Strange: Device couldn't find WIFI under the current edge image under sxmo or xfce4 yet. Even if I turned device of and restarted it with recovery.

        By Homer S. on 2022-04-03T19:51:16

      • Administrator
        Administrator @root · Imported
        Author Owner

        Could you send dmesg for when wifi doesnt work... as it works for me, I suppose you tried nmtui/nmcli and it didnt work? xfce4 also as indicator for wifi in top right area, try that. I'll have to check why sxmo does not work (it needs acceleration?)

        By Mighty on 2022-04-04T13:04:10

      • Administrator
        Administrator @root · Imported
        Author Owner

        nmcli gives me

        dummy0: nicht verwaltet
	"dummy0"
	dummy, F2:A8:FE:D3:97:40, sw, mtu 1500

usb0: nicht verwaltet
	"usb0"
	ethernet (musb-hdrc), 66:47:9D:CB:23:8A, hw, mtu 1500

sit0: nicht verwaltet
	"sit0"
	iptunnel (sit), 00:00:00:00, sw, mtu 1480

lo: nicht verwaltet
	"lo"
	loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

        Seems to fit to the startmessage that it "Couldn't find a wireless interface".dmesg.txt The xfce4 network indicator shows also no device and only offers VPNsettings in menu.

        The thing with sxmo is that it loads, I can touch the workbench icons but nothing else and then I can't do nothing more except restart device. I thought that I wouldn't need hw acceleration for a suckless dm ...?

        By Homer S. on 2022-04-04T20:15:55

      • Administrator
        Administrator @root · Imported
        Author Owner

        Looks like modules are not loaded, can you send output of lsmod and ls of /lib/modules

        By Mighty on 2022-04-05T05:26:41

      • Administrator
        Administrator @root · Imported
        Author Owner 
        samsung-espressowifi:~$ lsmod
Module                  Size  Used by    Tainted: G  
aes_arm_bs             24576  2 
crypto_simd            16384  1 aes_arm_bs
cryptd                 20480  2 crypto_simd

samsung-espressowifi:~$ sudo ls -la /lib/modules
total 12
drwxr-xr-x    3 root     root          4096 Apr  3 21:14 .
drwxr-xr-x   15 root     root          4096 Apr  3 21:15 ..
drwxr-xr-x    3 root     root          4096 Apr  3 21:15 5.17.0
samsung-espressowifi:~$ 
samsung-espressowifi:~$ modprobe -r 
modprobe: can't change directory to '5.15.2': No such file or directory
samsung-espressowifi:~$

        I guess my misstake is that I haven't updated the kernel yet, right? And now it is a pain in the a** just to get into the download mode :sob:

        I would say, it's nothing wrong with your work. It's just me forgetting the obvious :smirk: just close the issue, please.

        By Homer S. on 2022-04-05T12:38:20

      • Administrator
        Administrator @root · Imported
        Author Owner

        You dont need to get into download mode, apk upgrade should update kernel for you, I can give the boot.img if you want flash via twrp. Seems like you are on 5.15 (and have modules of 5.17, im surprised how lmao) instead of 5.17 :P please update, i do wonder how did you manage to get xfce and sxmo running on 5.15 kernel (which had gpu support iirc). This can also be an issue with pmOS-update-kernel so thats interesting :o

        By Mighty on 2022-04-05T18:42:48

        Edited by Administrator
      • Administrator
        Administrator @root · Imported
        Author Owner

        Well ... I started phosh with my other sdcard. After rebooting it I got to download mode and could pmbootstrap flasher flash_kernel. Obviously that work because as I tried to start phosh again it doesn't find wifi AND it doesn't manage to start the usb device to ssh into the device and it doesn't start the X server. So there's a shell login. I can't do anything with it than reboot device. So my formerly working setup is broken now :tired_face:

        OK, sxmo doesn't work correctly without p-wlroots. WIFI did work after hard reboot with recovery. Struggeling with screen orientation but that's more a sxmo thing I guess.

        By Homer S. on 2022-04-05T21:39:41

        Edited by Administrator
      • Administrator
        Administrator @root · Imported
        Author Owner

        And sxmo doesn't work so well unfortunately:

        dmesg:

           29.565979] emif_probe: error getting device data
[   29.569519] emif_probe: error getting device data
[   29.579742] omap-aes 4b701000.aes: will run requests pump with realtime priority
[   29.662567] emif_probe: error getting device data
[   29.665893] emif_probe: error getting device data
[   29.962432] EXT4-fs (dm-0): re-mounted. Quota mode: none.
[   33.023040] mms114 2-0048: TSP Rev: 0x17, HW Rev: 0x0, Firmware Ver: 0x43
[  780.448303] mms114 2-0048: Wrong touch type (3)
[  780.478546] mms114 2-0048: Wrong touch type (3)
[  780.492858] mms114 2-0048: Wrong touch type (3)
[  780.507720] mms114 2-0048: Wrong touch id (11)
[  780.522338] mms114 2-0048: Wrong touch id (14)
[  780.537567] mms114 2-0048: Wrong touch type (3)
[  780.552124] mms114 2-0048: Wrong touch type (3)
[  780.566986] mms114 2-0048: Wrong touch type (3)
[  780.581695] mms114 2-0048: Wrong touch type (3)
[  780.596313] mms114 2-0048: Wrong touch type (3)
[  780.611785] mms114 2-0048: Wrong touch type (3)
[  780.626556] mms114 2-0048: Wrong touch type (3)
[  780.641235] mms114 2-0048: Wrong touch type (3)
[  780.656127] mms114 2-0048: Wrong touch type (3)
[  780.670928] mms114 2-0048: Wrong touch type (3)
[  780.685607] mms114 2-0048: Wrong touch type (3)
[  780.700500] mms114 2-0048: Wrong touch type (3)
[  780.715393] mms114 2-0048: Wrong touch type (3)
[  780.730224] mms114 2-0048: Wrong touch type (3)
[  780.744689] mms114 2-0048: Wrong touch type (3)
[  780.759429] mms114 2-0048: Wrong touch type (3)
[  780.773956] mms114 2-0048: Wrong touch type (3)
[  780.804046] mms114 2-0048: Wrong touch type (3)
[  781.041076] mms114 2-0048: Wrong touch type (3)
[  781.055938] mms114 2-0048: Wrong touch type (3)
[  781.070709] mms114 2-0048: Wrong touch type (3)
[  781.085845] mms114 2-0048: Wrong touch type (3)
[  781.100646] mms114 2-0048: Wrong touch type (2)
[  781.130798] mms114 2-0048: Wrong touch type (0)
[  781.145660] mms114 2-0048: Wrong touch id (14)
[  781.160339] mms114 2-0048: Wrong touch id (12)
[  781.175384] mms114 2-0048: Wrong touch id (15)
[  781.190551] mms114 2-0048: Wrong touch type (0)
[  781.206207] mms114 2-0048: Wrong touch id (11)
[  781.206207] mms114 2-0048: Wrong touch type (0)
[  781.220794] mms114 2-0048: Wrong touch id (15)
[  781.220794] mms114 2-0048: Wrong touch type (0)
[  781.266540] mms114 2-0048: Wrong touch id (14)
[  781.266662] mms114 2-0048: Wrong touch type (0)
[  781.279693] mms114 2-0048: Wrong touch type (2)
[  781.279693] mms114 2-0048: Wrong touch type (0)
[  781.295166] mms114 2-0048: Wrong touch type (0)
[  781.309265] mms114 2-0048: Wrong touch id (15)
[  781.309265] mms114 2-0048: Wrong touch type (0)
[  781.325012] mms114 2-0048: Wrong touch type (0)
[  781.339294] mms114 2-0048: Wrong touch type (0)
[  781.354003] mms114 2-0048: Wrong touch id (13)
[  781.354003] mms114 2-0048: Wrong touch type (0)
[  781.369140] mms114 2-0048: Wrong touch type (0)
[  781.369140] mms114 2-0048: Wrong touch id (11)
[  781.383880] mms114 2-0048: Wrong touch id (13)
[  781.383972] mms114 2-0048: Wrong touch id (12)
[  781.398284] mms114 2-0048: Wrong touch type (0)
[  781.398284] mms114 2-0048: Wrong touch id (12)
[  781.412963] mms114 2-0048: Wrong touch id (11)
[  781.412963] mms114 2-0048: Wrong touch id (12)
[  781.427978] mms114 2-0048: Wrong touch type (3)
[  781.427978] mms114 2-0048: Wrong touch id (13)
[  781.443237] mms114 2-0048: Wrong touch type (3)
[  781.443237] mms114 2-0048: Wrong touch id (13)
[  781.457672] mms114 2-0048: Wrong touch id (14)
[  781.457672] mms114 2-0048: Wrong touch id (14)
[  781.472290] mms114 2-0048: Wrong touch type (2)
[  781.472290] mms114 2-0048: Wrong touch id (14)
[  781.486480] mms114 2-0048: Wrong touch type (2)
[  781.486602] mms114 2-0048: Wrong touch id (15)
[  781.501922] mms114 2-0048: Wrong touch type (2)
[  781.501922] mms114 2-0048: Wrong touch type (0)
[  781.545898] mms114 2-0048: Wrong touch type (0)
[  781.560943] mms114 2-0048: Wrong touch type (0)
[  781.575653] mms114 2-0048: Wrong touch type (0)
[  781.590332] mms114 2-0048: Wrong touch id (12)
[  781.590454] mms114 2-0048: Wrong touch type (0)
[  781.606903] mms114 2-0048: Wrong touch type (0)
[  781.607025] mms114 2-0048: Wrong touch type (0)
[  781.622558] mms114 2-0048: Wrong touch type (0)
[  781.622680] mms114 2-0048: Wrong touch type (0)
[  781.639892] mms114 2-0048: Wrong touch id (14)
[  781.639892] mms114 2-0048: Wrong touch type (0)
[  781.654418] mms114 2-0048: Wrong touch type (0)
[  781.654418] mms114 2-0048: Wrong touch type (0)
[  781.664764] mms114 2-0048: Wrong touch type (0)
[  781.664764] mms114 2-0048: Wrong touch type (0)
[  781.681091] mms114 2-0048: Wrong touch type (0)
[  781.681091] mms114 2-0048: Wrong touch type (0)
[  781.699035] mms114 2-0048: Wrong touch type (0)
[  781.699035] mms114 2-0048: Wrong touch type (0)
[  781.710906] mms114 2-0048: Wrong touch type (0)
[  781.710906] mms114 2-0048: Wrong touch type (0)
[  781.725646] mms114 2-0048: Wrong touch id (15)
[  781.725646] mms114 2-0048: Wrong touch type (0)
[  781.741546] mms114 2-0048: Wrong touch id (14)
[  781.741546] mms114 2-0048: Wrong touch type (0)
[  781.757751] mms114 2-0048: Wrong touch id (13)
[  781.757873] mms114 2-0048: Wrong touch type (0)
[  781.772613] mms114 2-0048: Wrong touch id (12)
[  781.772735] mms114 2-0048: Wrong touch type (0)
[  781.783721] mms114 2-0048: Wrong touch id (11)
[  781.783721] mms114 2-0048: Wrong touch type (0)
[  781.800231] mms114 2-0048: Wrong touch type (3)
[  781.800262] mms114 2-0048: Wrong touch type (0)
[  781.812591] mms114 2-0048: Wrong touch type (3)
[  781.812591] mms114 2-0048: Wrong touch type (0)
[  781.830688] mms114 2-0048: Wrong touch type (3)
[  781.830688] mms114 2-0048: Wrong touch type (0)
[  781.844085] mms114 2-0048: Wrong touch type (3)
[  781.844207] mms114 2-0048: Wrong touch type (0)
[  781.860015] mms114 2-0048: Wrong touch type (3)
[  781.860015] mms114 2-0048: Wrong touch type (0)
[  781.873352] mms114 2-0048: Wrong touch id (14)
[  781.889678] mms114 2-0048: Wrong touch type (3)
[  781.889770] mms114 2-0048: Wrong touch id (15)
[  781.903198] mms114 2-0048: Wrong touch type (0)
[  781.914916] mms114 2-0048: Wrong touch type (0)
[  781.930755] mms114 2-0048: Wrong touch type (0)
[  781.946868] mms114 2-0048: Wrong touch type (3)
[  781.946960] mms114 2-0048: Wrong touch id (14)
[  781.964477] mms114 2-0048: Wrong touch type (3)
[  781.964569] mms114 2-0048: Wrong touch id (14)
[  781.977783] mms114 2-0048: Wrong touch type (0)
[  781.989562] mms114 2-0048: Wrong touch type (3)
[  781.989685] mms114 2-0048: Wrong touch id (12)
[  782.003204] mms114 2-0048: Wrong touch type (0)
[  782.034515] mms114 2-0048: Wrong touch type (0)
[  782.050537] mms114 2-0048: Wrong touch type (3)
[  782.063079] mms114 2-0048: Wrong touch type (3)
[  782.118896] mms114 2-0048: Wrong touch type (3)

        Something's wrong with the touch at least :shrug:

        !! OK, with p-wlroots the touch under sxmo now works. Still no internet but I'm coming forward slowly ...

        By Homer S. on 2022-04-05T21:22:48

        Edited by Administrator
      • Administrator
        Administrator @root · Imported
        Author Owner

        In your current pmbootstrap, there might be the "wrong" (newest) kernel version. You should try to flash a boot.img file instead, @MightyM17 can provide you that file. The kernel version of that boot.img file should match the kernel version of the modules in /lib/modules, looks like it was kernel version 5.15.2.

        Once flashed, you should be able to boot into postmarketOS. Then upgrade packages, new kernel will be installed, so the modules of that new kernel will become available in /lib/modules. After that, you have to flash the newest kernel, which now also fits with /lib/modules.

        In case you can use fastboot interface, you don't need to flash the old kernel boot.img, you can boot that file directly by fastboot boot boot.img. That way you don't need to flash the old kernel and later on flash the new kernel.

        By Jakko on 2022-04-05T22:59:57

      • Administrator
        Administrator @root · Imported
        Author Owner

        Btw, you seem to have different installations (Phosh, Xfce4, sxmo). Within those installions, there might be different kernel versions installed, e.g. some on 5.15.2, some on 5.17.0. But you'll have only one kernel version flashed on your boot partition. So you have to "synchronize" those installations, aka. upgrade all of them to the newest kernel as described above.

        By Jakko on 2022-04-05T23:06:22

      • Administrator
        Administrator @root · Imported
        Author Owner

        Ah, maybe it's the other way around: In your post further above it looks like you have kernel version 5.17.0 in your /lib/modules but the modprobe -r command asks for kernel version 5.15.2. Whatsoever, the kernel version you boot with has to match kernel version in /lib/modules.

        By Jakko on 2022-04-05T23:15:03

      • Administrator
        Administrator @root · Imported
        Author Owner

        This seems like quite the mess, okay with the latest 5.17 you will not need p-wlroots or any hacks as we removed gpu support so things should work out of the box, so please update the kernel xD

        By Mighty on 2022-04-06T05:23:16

      • Administrator
        Administrator @root · Imported
        Author Owner

        Emmm ... Is it possible that I can't choose phosh any longer? It isn't offered while bootstrap init? Because GPU support was removed?

        By Homer S. on 2022-04-06T16:17:19

      • Please register or sign in to reply
    • Administrator
      Administrator @root · Imported
      Author Owner

      According to this issue we have decided to drop powervr support from pmOS, there is an ongoing effort to use a fork and host those packages, but I currently am quite busy with exams so thats on hold. You can still choose phosh with pmbootstrap config ui phosh and it runs quite fine with software rendering (llvmpipe)

      By Mighty on 2022-04-06T17:44:10

      Edited by Ghost User
    • Administrator
      Administrator @root · Imported
      Author Owner

      Closing issue due to inactivity.

      By Robert Eckelmann on 2024-08-14T14:12:41

    • Administrator closed · Imported

      closed

    Please register or sign in to reply