(06-06-2021, 07:00 PM)moonwalkers Wrote: (06-06-2021, 12:27 PM)thequailman Wrote: Hello, I've been struggling to get Debian testing or unstable displaying something on the screen with a custom install. Everything boots OK, but X won't start or any display manager (GDM etc). I'm booting with u-boot+uefi though, maybe that's the issue? I don't know how to do a custom /boot for non-UEFI though (I think there's a config.txt file I need? grub?). UEFI was easier to get going with. Any chance you could send me the contents of your /boot directory or instructions on how you populated it? maybe a fdisk dump too? I do not use UEFI, opting for booting directly from u-boot instead. Here is my disk layout:
Code: $ sudo fdisk -l
Disk /dev/mmcblk2: 58.24 GiB, 62537072640 bytes, 122142720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: <derp>
Device Start End Sectors Size Type
/dev/mmcblk2p1 64 32767 32704 16M Linux reserved
/dev/mmcblk2p2 32768 122140671 122107904 58.2G Linux filesystem
When you say "everything boots OK", does that mean you get your usual basic VT1 through VT6 where you can enter your username and password in text mode and get to your basic shell of choice (bash, zsh, fish, whatever)? If yes, then I'd start troubleshooting by trying `startx` command, which should be a part of `xinit` package.
just to clarify (I could be completely wrong - sorry not as experienced): - debootstrrab sid to mmclk2p2
- chroot into mmclk2p2
- install additional packages (like linux-image-5.10.0-7-arm64 to get at least .38)
- you say "I also have `u-boot-menu` package installed, that automatically generates extlinux-style boot menu for u-boot." How so?
Sorry again for my ignorance
(06-10-2021, 09:37 AM)sepp Wrote: just to clarify (I could be completely wrong - sorry not as experienced):- debootstrrab sid to mmclk2p2
- chroot into mmclk2p2
- install additional packages (like linux-image-5.10.0-7-arm64 to get at least .38)
- you say "I also have `u-boot-menu` package installed, that automatically generates extlinux-style boot menu for u-boot." How so?
Sorry again for my ignorance
Off the top of my head (it's been a while), the installation I did was essentially these steps: - create two partitions on eMMC using GPT partitioning, one starting on sector 64 and ending on sector 32767, 32704 sectors in size, and another starting at sector 32768 and until the end of the available eMMC space. The first partition is just a protective partition for u-boot (link to the version I used is above), second I formatted with ex4 and used whole for my Debian installation.
- mounted second partition in live microSD. Because I just wanted to fuck around, I manually downloaded and unpacked bunch of packages until I could get APT to work in a chroot, but standard debootstrap would've worked just fine too, and much faster.
- chroot into mmcblk2p2.
- install linux-image-arm64, which, if you're on Sid/Unstable, will pull in linux-image-5.10.0-7-arm64 as dependency and will generally keep your kernel up-to-date.
- install u-boot-menu. Adjust /etc/default/u-boot to your taste, run `sudo u-boot-update`. Check that you now have /boot/extlinux/extlinux.conf that points to your /boot/vmlinuz-5.10.0-7-arm64
- make sure to install network-manager before you attempt rebooting - without it you'll have hard time connecting to WiFi, and without WiFi you'll have hard time installing the rest of the packages.
- after getting successful boot and WiFi connection using nmcli I configured zram swap and at that point it was just the matter of installing the rest of the packages I cared about
Note that the steps above would initially yield a system with no GUI whatsoever, but you should be able to boot with terminal and WiFi, and that's really all you should need to get going.
This message was created with 100% recycled electrons
(06-10-2021, 06:14 PM)moonwalkers Wrote: (06-10-2021, 09:37 AM)sepp Wrote: just to clarify (I could be completely wrong - sorry not as experienced):- debootstrrab sid to mmclk2p2
- chroot into mmclk2p2
- install additional packages (like linux-image-5.10.0-7-arm64 to get at least .38)
- you say "I also have `u-boot-menu` package installed, that automatically generates extlinux-style boot menu for u-boot." How so?
Sorry again for my ignorance
Off the top of my head (it's been a while), the installation I did was essentially these steps:- create two partitions on eMMC using GPT partitioning, one starting on sector 64 and ending on sector 32767, 32704 sectors in size, and another starting at sector 32768 and until the end of the available eMMC space. The first partition is just a protective partition for u-boot (link to the version I used is above), second I formatted with ex4 and used whole for my Debian installation.
- mounted second partition in live microSD. Because I just wanted to fuck around, I manually downloaded and unpacked bunch of packages until I could get APT to work in a chroot, but standard debootstrap would've worked just fine too, and much faster.
- chroot into mmcblk2p2.
- install linux-image-arm64, which, if you're on Sid/Unstable, will pull in linux-image-5.10.0-7-arm64 as dependency and will generally keep your kernel up-to-date.
- install u-boot-menu. Adjust /etc/default/u-boot to your taste, run `sudo u-boot-update`. Check that you now have /boot/extlinux/extlinux.conf that points to your /boot/vmlinuz-5.10.0-7-arm64
- make sure to install network-manager before you attempt rebooting - without it you'll have hard time connecting to WiFi, and without WiFi you'll have hard time installing the rest of the packages.
- after getting successful boot and WiFi connection using nmcli I configured zram swap and at that point it was just the matter of installing the rest of the packages I cared about
Note that the steps above would initially yield a system with no GUI whatsoever, but you should be able to boot with terminal and WiFi, and that's really all you should need to get going. Thank you very much - will certainly give it a try this weekend
I also tried to follow instructions and cannot run 5.10 linux image. Still have black screen. The good news is it was not necessary to reinstall Bullseye. Just boot from microSD, access /boot/extlinux/extlinux.conf and modify the kernel to boot.
I also learned that /boot/extlinux/extlinux.conf in Debian is not maintained by extlinux package, but by u-boot-update. That is why there is no possibility to choose interactively the kernel (am I missing something?).
Additionally to linux-image-5.10.0-7-arm64 and its metapackage linux-image-arm it was also installed firmware-linux-free package. Maybe this one was more important, there is also firmware-linux-nonfree and their metapackage firmware-linux.
(06-12-2021, 06:16 AM)alpopa Wrote: I also tried to follow instructions and cannot run 5.10 linux image. Still have black screen. The good news is it was not necessary to reinstall Bullseye. Just boot from microSD, access /boot/extlinux/extlinux.conf and modify the kernel to boot.
I also learned that /boot/extlinux/extlinux.conf in Debian is not maintained by extlinux package, but by u-boot-update. That is why there is no possibility to choose interactively the kernel (am I missing something?).
Additionally to linux-image-5.10.0-7-arm64 and its metapackage linux-image-arm it was also installed firmware-linux-free package. Maybe this one was more important, there is also firmware-linux-nonfree and their metapackage firmware-linux.
Interesting... I think u-boot version may have an effect on whether boot is successful or not, because when I try to boot official Debian installation media on PBP it also boots to black screen, and the only difference between it and my working system should be u-boot. I'm not using the fully open-source build of u-boot, I use BSP u-boot by mrfixit (see the link in the first post). Until 5.10.38 kernel booting from microSD to edit /boot/extlinux/extlinux.conf and point it back to xmixahx's 5.8.5 when Debian kernel is updated and fails to boot is what I was doing as well.
u-boot-update is the command, which is provided by the package u-boot-menu. As to the reason there is no possibility to choose kernel interactively - that depends on u-boot build, as there are some builds that do allow that.
I do have firmware-misc-nonfree package installed, I completely forgot to mention that. Like I said, it's been a while since I did the initial installation of Debian on my machine, and the only difference between getting it to work initially and having it working now is using official Debian kernel. Looking at the package contents, it has "Rockchip cdn DisplayPort controller firmware, version 3.1 (rockchip/dptx.bin)", which is the more probable explanation of the black screen if it is missing, though if I remember correctly that firmware should be necessary for the external display, not internal one... But then, if I understand correctly the issue with black built-in screen is related to initializing that very same DisplayPort controller.
I'm gonna see if I can add firmware-misc-nonfree to the SD card image and get the official installer to work that way for PBP.
This message was created with 100% recycled electrons
06-12-2021, 11:38 AM
(This post was last modified: 06-22-2021, 08:28 AM by alpopa.)
For me it is clear that the black screen is due to missing / misconfigured DisplayPort driver. When booting a working version I can see backlight, some traces etc. None of these is visible when booting 5.10 official kernel from Debian repository as if display would be physically disconnected from the mainboard.
I will try also to play with firmware packages to see if it helps.
Unfortunately, this doesn't work. I installed:
- linux-image-arm64 (and its dependences linux-image-5.10.0-7-arm64, firmware-linux-free)
- firmware-linux (and its dependences firmware-amd-graphics, firmware-linux-nonfree, firmware-misc-nonfree)
But the result is the same.
Additional note: When booting Manjaro, which does boot to GUI, it shows traces about misconfigured DP port. I am not sure if it matters or is related.
enough of the guessing game
I ordererd a serial adapter
(06-12-2021, 11:38 AM)alpopa Wrote: For me it is clear that the black screen is due to missing / misconfigured DisplayPort driver. When booting a working version I can see backlight, some traces etc. None of these is visible when booting 5.10 official kernel from Debian repository as if display would be physically disconnected from the mainboard.
I will try also to play with firmware packages to see if it helps.
Unfortunately, this doesn't work. I installed:
- linux-image-arm64 (and its dependences linux-image-5.10.0-7-arm64, firmware-linux-free)
- firmware-linux (and its dependences firmware-amd-graphics, firmware-misc-nonfree)
But the result is the same.
Additional note: When booting Manjaro, which does boot to GUI, it shows traces about misconfigured DP port. I am not sure if it matters or is related.
I'm glad I'm not the only one seeing this. I have been pulling my hair out for over two weeks trying different combinations. I posit it's a problem with the laptop monitor--it's not detected, maybe that's what you mean by DisplayPort? One thing I haven't tried is video out from a USB-C stick, but I'm not sure what that will prove. Regardless, there is a bug here but I'm not sure where--the kernel?
as posted in this other thread:
moonwalkers Wrote: Wrote:(06-07-2021, 06:49 PM)jbrock Wrote: Wrote:This is so perplexing to me.
Have you all tried this image? https://d-i.debian.org/daily-images/arm6...ard-images
I think the included kernel is ready / almost fully ready. I actually prepared one today and tried booting it, just for the heck of it - I'm perfectly happy with the system that's already installed on my machine - but the thing came up with black screen :-( I'm not sure what is the exact reason - whether the kernel hasn't yet been updated in the SD card image or the u-boot version in it has some issue.
This boots too but you need a serial console to configure (and an usbnet compatible USB2Ether Interface)
but gnome starts but on login:
Code: ....
Jun 22 13:14:02 Pine64 kernel: [ 16.173332] Bluetooth: BNEP socket layer initd
Jun 22 13:14:02 Pine64 udisksd[617]: failed to load module mdraid: libbd_mdraidy
Jun 22 13:14:02 Pine64 udisksd[617]: Failed to load the 'mdraid' libblockdev pln
Jun 22 13:14:03 Pine64 udisksd[617]: Cleaning up mount point /media/sepp/C184-2)
Jun 22 13:14:03 Pine64 udisksd[617]: Acquired the name org.freedesktop.UDisks2 s
Jun 22 13:14:04 Pine64 tracker-miner-f[731]: Set scheduler policy to SCHED_IDLE
Jun 22 13:14:04 Pine64 tracker-extract[730]: Set scheduler policy to SCHED_IDLE
Jun 22 13:14:04 Pine64 tracker-miner-f[731]: Setting priority nice level to 19
Jun 22 13:14:04 Pine64 tracker-extract[730]: Setting priority nice level to 19
Jun 22 13:14:05 Pine64 tracker-miner-f[731]: Unable to get XDG user directory p.
Jun 22 13:14:05 Pine64 tracker-miner-f[731]: Unable to get XDG user directory p.
Jun 22 13:14:05 Pine64 tracker-miner-f[731]: Unable to get XDG user directory p.
Jun 22 13:14:05 Pine64 tracker-miner-f[731]: Unable to get XDG user directory p.
Jun 22 13:14:05 Pine64 tracker-miner-f[731]: Unable to get XDG user directory p.
Jun 22 13:14:05 Pine64 tracker-miner-f[731]: Unable to get XDG user directory p.
Jun 22 13:14:05 Pine64 tracker-miner-f[731]: Unable to get XDG user directory p.
Jun 22 13:14:05 Pine64 tracker-miner-f[731]: Unable to get XDG user directory p.
Jun 22 13:14:05 Pine64 tracker-miner-f[731]: Unable to get XDG user directory p.
Jun 22 13:14:05 Pine64 gnome-session[751]: gnome-session-binary[751]: WARNING: t
Jun 22 13:14:05 Pine64 gnome-session[751]: gnome-session-binary[751]: WARNING: t
Jun 22 13:14:05 Pine64 gnome-session[751]: gnome-session-binary[751]: WARNING: t
Jun 22 13:14:06 Pine64 goa-daemon[806]: goa-daemon version 3.38.0 starting
Jun 22 13:14:06 Pine64 upowerd[823]: did not recognise USB path /sys/devices/plt
Jun 22 13:14:08 Pine64 gnome-shell[791]: Failed to initialize accelerated iGPU/h
Jun 22 13:14:08 Pine64 gnome-shell[791]: Integrated GPU /dev/dri/card0 selectedy
Jun 22 13:14:09 Pine64 gnome-shell[791]: Disabling DMA buffer screen sharing fo.
Jun 22 13:14:09 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:)
Jun 22 13:14:09 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:'
Jun 22 13:14:10 Pine64 gnome-shell[791]: Getting parental controls for user 116
Jun 22 13:14:11 Pine64 gnome-shell[791]: Unset XDG_SESSION_ID, getCurrentSessio.
Jun 22 13:14:11 Pine64 gnome-shell[791]: Will monitor session c1
Jun 22 13:14:11 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:)
Jun 22 13:14:11 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:'
Jun 22 13:14:12 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:)
Jun 22 13:14:12 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:'
Jun 22 13:14:13 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:)
Jun 22 13:14:13 Pine64 /usr/libexec/gdm-wayland-session[892]: dbus-daemon[892]:)
Jun 22 13:14:13 Pine64 /usr/libexec/gdm-wayland-session[892]: dbus-daemon[892]:'
Jun 22 13:14:13 Pine64 /usr/libexec/gdm-wayland-session[950]: SpiRegistry daemoy
Jun 22 13:14:13 Pine64 gnome-shell[791]: Error looking up permission: GDBus.Errn
Jun 22 13:14:13 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:)
Jun 22 13:14:13 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:1
Jun 22 13:14:13 Pine64 gsd-sharing[962]: Failed to StopUnit service: GDBus.Erro1
Jun 22 13:14:13 Pine64 gsd-sharing[962]: Failed to StopUnit service: GDBus.Erro1
Jun 22 13:14:13 Pine64 gsd-sharing[962]: Failed to StopUnit service: GDBus.Erro1
Jun 22 13:14:13 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:'
Jun 22 13:14:13 Pine64 org.gnome.Shell.desktop[899]: glamor: 'wl_drm' not suppod
Jun 22 13:14:13 Pine64 org.gnome.Shell.desktop[899]: Missing Wayland requiremend
Jun 22 13:14:13 Pine64 org.gnome.Shell.desktop[899]: Failed to initialize glamow
Jun 22 13:14:14 Pine64 ibus-daemon[918]: GChildWatchSource: Exit status of a ch.
Jun 22 13:14:14 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:)
Jun 22 13:14:14 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:'
Jun 22 13:14:14 Pine64 colord[1096]: failed to get edid data: EDID length is tol
Jun 22 13:14:14 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:)
Jun 22 13:14:14 Pine64 gnome-session-binary[751]: Entering running state
Jun 22 13:14:14 Pine64 xbrlapi.desktop[1108]: openConnection: connect: No such y
Jun 22 13:14:14 Pine64 xbrlapi.desktop[1108]: cannot connect to braille devices0
Jun 22 13:14:15 Pine64 gsd-media-keys[981]: Failed to grab accelerator for keybl
Jun 22 13:14:15 Pine64 gsd-media-keys[981]: Failed to grab accelerator for keybm
Jun 22 13:14:15 Pine64 gsd-media-keys[981]: Failed to grab accelerator for keybe
Jun 22 13:14:15 Pine64 gsd-media-keys[981]: Failed to grab accelerator for keybt
Jun 22 13:14:15 Pine64 org.gnome.Shell.desktop[1138]: The XKEYBOARD keymap comp:
Jun 22 13:14:15 Pine64 org.gnome.Shell.desktop[1138]: > Warning: Unsup.
Jun 22 13:14:15 Pine64 org.gnome.Shell.desktop[1138]: > X11 c.
Jun 22 13:14:15 Pine64 org.gnome.Shell.desktop[1138]: Errors from xkbcomp are nr
Jun 22 13:14:16 Pine64 gsd-color[966]: failed to get edid: unable to get EDID ft
Jun 22 13:14:16 Pine64 gsd-color[966]: unable to get EDID for xrandr-eDP-1: unat
Jun 22 13:14:16 Pine64 /usr/libexec/gdm-wayland-session[746]: dbus-daemon[746]:'
Jun 22 13:14:16 Pine64 gnome-shell[791]: Registering session with GDM
Jun 22 13:14:19 Pine64 org.gnome.Shell.desktop[791]: libinput error: event6 - w
Jun 22 13:14:22 Pine64 kernel: [ 35.808121] vbus_5vout: disabling
Jun 22 13:14:35 Pine64 tracker-miner-f[1187]: Set scheduler policy to SCHED_IDLE
Jun 22 13:14:35 Pine64 tracker-miner-f[1187]: Setting priority nice level to 19
Jun 22 13:14:35 Pine64 tracker-extract[1186]: Set scheduler policy to SCHED_IDLE
Jun 22 13:14:35 Pine64 tracker-extract[1186]: Setting priority nice level to 19
Jun 22 13:14:35 Pine64 goa-daemon[1287]: goa-daemon version 3.38.0 starting
Jun 22 13:14:36 Pine64 gnome-keyring-ssh.desktop[1321]: SSH_AUTH_SOCK=/run/userh
Jun 22 13:14:36 Pine64 gnome-keyring-pkcs11.desktop[1320]: SSH_AUTH_SOCK=/run/uh
Jun 22 13:14:36 Pine64 gnome-keyring-secrets.desktop[1322]: SSH_AUTH_SOCK=/run/h
Jun 22 13:14:36 Pine64 gnome-session[1310]: gnome-session-binary[1310]: GnomeDe.
Jun 22 13:14:36 Pine64 gnome-session[1310]: gnome-session-binary[1310]: GnomeDe.
Jun 22 13:14:37 Pine64 gnome-shell[1332]: Failed to initialize accelerated iGPUh
Jun 22 13:14:37 Pine64 gnome-shell[1332]: Integrated GPU /dev/dri/card0 selectey
Jun 22 13:14:37 Pine64 gnome-shell[1332]: Disabling DMA buffer screen sharing f.
Jun 22 13:14:38 Pine64 gnome-shell[1332]: Getting parental controls for user 100
Jun 22 13:14:38 Pine64 gnome-shell[1332]: Unset XDG_SESSION_ID, getCurrentSessi.
Jun 22 13:14:38 Pine64 gnome-shell[1332]: Will monitor session 2
Jun 22 13:14:39 Pine64 gnome-shell[1332]: Telepathy is not available, chat inte.
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 gnome-shell[1332]: Warning: Hiding app because parental p
Jun 22 13:14:40 Pine64 at-spi-dbus-bus.desktop[1335]: dbus-daemon[1335]: Activa)
Jun 22 13:14:40 Pine64 at-spi-dbus-bus.desktop[1335]: dbus-daemon[1335]: Succes'
Jun 22 13:14:40 Pine64 at-spi-dbus-bus.desktop[1427]: SpiRegistry daemon is runy
Jun 22 13:14:40 Pine64 kernel: [ 55.107765] FAT-fs (mmcblk1p1): Volume was no.
Jun 22 13:14:40 Pine64 udisksd[617]: Mounted /dev/mmcblk1p1 at /media/sepp/C1840
Jun 22 13:14:40 Pine64 gnome-session-binary[1310]: Entering running state
Jun 22 13:14:40 Pine64 at-spi2-registr[1427]: Failed to register client: GDBus.t
Jun 22 13:14:40 Pine64 at-spi2-registr[1427]: Unable to register client with ser
Jun 22 13:14:40 Pine64 gnome-session[1310]: gnome-session-binary[1310]: GnomeDe.
Jun 22 13:14:40 Pine64 gnome-session[1310]: gnome-session-binary[1310]: GnomeDe.
Jun 22 13:14:41 Pine64 gnome-shell[1332]: Error looking up permission: GDBus.Ern
Jun 22 13:14:41 Pine64 gsd-usb-protect[1476]: Failed to fetch USBGuard parametes
Jun 22 13:14:42 Pine64 gsd-color[1440]: failed to get edid: unable to get EDID t
Jun 22 13:14:42 Pine64 gsd-color[1440]: unable to get EDID for xrandr-eDP-1: unt
Jun 22 13:14:42 Pine64 gsd-color[966]: unable to get EDID for xrandr-eDP-1: unat
Jun 22 13:14:42 Pine64 gsd-media-keys[1450]: Failed to grab accelerator for keyl
Jun 22 13:14:42 Pine64 gsd-media-keys[1450]: Failed to grab accelerator for keym
Jun 22 13:14:42 Pine64 gsd-media-keys[1450]: Failed to grab accelerator for keye
Jun 22 13:14:42 Pine64 gsd-media-keys[1450]: Failed to grab accelerator for keyt
Jun 22 13:14:43 Pine64 gnome-shell[1332]: GNOME Shell started at Tue Jun 22 202)
Jun 22 13:14:43 Pine64 gnome-shell[1332]: Registering session with GDM
Jun 22 13:14:43 Pine64 gnome-shell[791]: Connection to xwayland lost
Jun 22 13:14:43 Pine64 ibus-daemon[1074]: GChildWatchSource: Exit status of a c.
Jun 22 13:14:44 Pine64 gnome-shell[1332]: Could not release device (13,69): GDBn
Jun 22 13:14:44 Pine64 kernel: [ 59.030969] input: HAILUCK CO.,LTD USB KEYBOA5
Jun 22 13:14:44 Pine64 kernel: [ 59.031430] input: HAILUCK CO.,LTD USB KEYBOA6
Jun 22 13:14:44 Pine64 kernel: [ 59.031827] input: HAILUCK CO.,LTD USB KEYBOA7
Jun 22 13:14:44 Pine64 gnome-shell[1332]: Could not release device (13,70): GDBn
Jun 22 13:14:44 Pine64 gnome-shell[1332]: Could not release device (13,71): GDBn
Jun 22 13:14:44 Pine64 kernel: [ 59.089067] input: HAILUCK CO.,LTD USB KEYBOA8
Jun 22 13:14:44 Pine64 kernel: [ 59.089754] input: HAILUCK CO.,LTD USB KEYBOA9
Jun 22 13:14:44 Pine64 kernel: [ 59.091062] hid-multitouch 0003:258A:001E.0001
Jun 22 13:14:44 Pine64 gnome-shell[1332]: Could not release device (13,72): GDBn
Jun 22 13:14:44 Pine64 kernel: [ 59.131435] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.132499] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.133631] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.134523] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.135406] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.136443] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.137321] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.138227] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.139103] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.139983] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.141019] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.142055] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.142911] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.143758] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.144614] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.145465] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.146313] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.147158] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.148003] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.149067] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.149915] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.150791] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.151679] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.152725] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.153623] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.154479] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.155359] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.156216] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.157102] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.157987] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.158868] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 kernel: [ 59.159743] rockchip-dp ff970000.edp: AUX CH )
Jun 22 13:14:44 Pine64 gnome-shell[1332]: Could not release device (13,73): GDBn
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: unknown object (11), message get_)
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: error in client communication (pi)
Jun 22 13:14:44 Pine64 gsd-keyboard[1448]: Error 22 (Invalid argument) dispatch.
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: unknown object (11), message get_)
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: error in client communication (pi)
Jun 22 13:14:44 Pine64 gsd-color[1440]: Error 22 (Invalid argument) dispatching.
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: unknown object (11), message get_)
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: error in client communication (pi)
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: unknown object (11), message get_)
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: error in client communication (pi)
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: unknown object (11), message get_)
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: error in client communication (pi)
Jun 22 13:14:44 Pine64 gsd-wacom[1477]: Error 22 (Invalid argument) dispatching.
Jun 22 13:14:44 Pine64 gjs[1657]: Error 22 (Invalid argument) dispatching to Wa.
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: unknown object (11), message get_)
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: error in client communication (pi)
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: unknown object (11), message get_)
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: error in client communication (pi)
Jun 22 13:14:44 Pine64 evolution-alarm[1475]: Error 22 (Invalid argument) dispa.
Jun 22 13:14:44 Pine64 gsd-media-keys[1450]: Error 22 (Invalid argument) dispat.
Jun 22 13:14:44 Pine64 gnome-shell[1332]: WL: error in client communication (pi)
Jun 22 13:14:44 Pine64 gsd-power[1453]: Error 22 (Invalid argument) dispatching.
Jun 22 13:14:44 Pine64 kernel: [ 59.360487] mmcblk2: p1
Jun 22 13:14:45 Pine64 gnome-shell[1332]: Connection to xwayland lost
Jun 22 13:14:45 Pine64 ibus-daemon[1652]: GChildWatchSource: Exit status of a c.
Jun 22 13:14:45 Pine64 gnome-software[1460]: plugin fwupd took 2.0 seconds to dp
Jun 22 13:14:53 Pine64 tracker-miner-f[731]: Error while sending AddMatch() mesd
Jun 22 13:14:53 Pine64 tracker-miner-f[731]: Error while sending AddMatch() mesd
Jun 22 13:14:53 Pine64 tracker-miner-f[731]: Error while sending AddMatch() mesd
Jun 22 13:14:54 Pine64 gnome-software[1460]: plugin appstream took 8.5 seconds p
Jun 22 13:14:54 Pine64 gnome-software[1460]: enabled plugins: desktop-categoriea
Jun 22 13:14:54 Pine64 gnome-software[1460]: disabled plugins: dpkg, dummy, reps
Jun 22 13:15:05 Pine64 tracker-miner-f[1878]: Set scheduler policy to SCHED_IDLE
Jun 22 13:15:05 Pine64 tracker-miner-f[1878]: Setting priority nice level to 19
Jun 22 13:15:05 Pine64 tracker-extract[1876]: Set scheduler policy to SCHED_IDLE
Jun 22 13:15:05 Pine64 tracker-extract[1876]: Setting priority nice level to 19
Jun 22 13:15:05 Pine64 tracker-miner-f[1878]: Unable to get XDG user directory .
Jun 22 13:15:05 Pine64 tracker-miner-f[1878]: Unable to get XDG user directory .
Jun 22 13:15:05 Pine64 tracker-miner-f[1878]: Unable to get XDG user directory .
Jun 22 13:15:05 Pine64 tracker-miner-f[1878]: Unable to get XDG user directory .
Jun 22 13:15:05 Pine64 tracker-miner-f[1878]: Unable to get XDG user directory .
Jun 22 13:15:05 Pine64 tracker-miner-f[1878]: Unable to get XDG user directory .
Jun 22 13:15:05 Pine64 tracker-miner-f[1878]: Unable to get XDG user directory .
Jun 22 13:15:05 Pine64 tracker-miner-f[1878]: Unable to get XDG user directory .
Jun 22 13:15:05 Pine64 tracker-miner-f[1878]: Unable to get XDG user directory .
Jun 22 13:15:05 Pine64 gnome-session[1914]: gnome-session-binary[1914]: WARNINGt
Jun 22 13:15:05 Pine64 gnome-session[1914]: gnome-session-binary[1914]: WARNINGt
Jun 22 13:15:05 Pine64 gnome-session[1914]: gnome-session-binary[1914]: WARNINGt
Jun 22 13:15:06 Pine64 goa-daemon[1955]: goa-daemon version 3.38.0 starting
Jun 22 13:15:07 Pine64 gnome-shell[1937]: Failed to initialize accelerated iGPUh
Jun 22 13:15:07 Pine64 gnome-shell[1937]: Integrated GPU /dev/dri/card0 selectey
Jun 22 13:15:07 Pine64 gnome-shell[1937]: Disabling DMA buffer screen sharing f.
Jun 22 13:15:07 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906)
Jun 22 13:15:07 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906'
Jun 22 13:15:08 Pine64 gnome-shell[1937]: Getting parental controls for user 116
Jun 22 13:15:09 Pine64 gnome-shell[1937]: Unset XDG_SESSION_ID, getCurrentSessi.
Jun 22 13:15:09 Pine64 gnome-shell[1937]: Will monitor session c2
Jun 22 13:15:09 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906)
Jun 22 13:15:09 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906'
Jun 22 13:15:09 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906)
Jun 22 13:15:09 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906'
Jun 22 13:15:10 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906)
Jun 22 13:15:10 Pine64 /usr/libexec/gdm-wayland-session[2013]: dbus-daemon[2013)
Jun 22 13:15:10 Pine64 /usr/libexec/gdm-wayland-session[2013]: dbus-daemon[2013'
Jun 22 13:15:10 Pine64 /usr/libexec/gdm-wayland-session[2047]: SpiRegistry daemy
Jun 22 13:15:10 Pine64 gnome-shell[1937]: Error looking up permission: GDBus.Ern
Jun 22 13:15:10 Pine64 gsd-rfkill[2068]: Could not open rfkill device: Could non
Jun 22 13:15:10 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906)
Jun 22 13:15:10 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[19061
Jun 22 13:15:10 Pine64 gsd-sharing[2051]: Failed to StopUnit service: GDBus.Err1
Jun 22 13:15:10 Pine64 gsd-sharing[2051]: Failed to StopUnit service: GDBus.Err1
Jun 22 13:15:10 Pine64 gsd-sharing[2051]: Failed to StopUnit service: GDBus.Err1
Jun 22 13:15:10 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906'
Jun 22 13:15:10 Pine64 org.gnome.Shell.desktop[2021]: glamor: 'wl_drm' not suppd
Jun 22 13:15:10 Pine64 org.gnome.Shell.desktop[2021]: Missing Wayland requiremed
Jun 22 13:15:10 Pine64 org.gnome.Shell.desktop[2021]: Failed to initialize glamw
Jun 22 13:15:11 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906)
Jun 22 13:15:11 Pine64 gnome-session-binary[1914]: Entering running state
Jun 22 13:15:11 Pine64 xbrlapi.desktop[2175]: openConnection: connect: No such y
Jun 22 13:15:11 Pine64 xbrlapi.desktop[2175]: cannot connect to braille devices0
Jun 22 13:15:11 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906)
Jun 22 13:15:11 Pine64 /usr/libexec/gdm-wayland-session[1906]: dbus-daemon[1906'
Jun 22 13:15:11 Pine64 gsd-media-keys[2074]: Failed to grab accelerator for keym
Jun 22 13:15:11 Pine64 gsd-media-keys[2074]: Failed to grab accelerator for keye
Jun 22 13:15:11 Pine64 gsd-media-keys[2074]: Failed to grab accelerator for keyt
Jun 22 13:15:11 Pine64 gsd-media-keys[2074]: Failed to grab accelerator for keyl
Jun 22 13:15:11 Pine64 gsd-color[2055]: failed to get edid: unable to get EDID t
Jun 22 13:15:11 Pine64 gsd-color[2055]: failed to create device: failed to obtah
Jun 22 13:15:11 Pine64 gnome-shell[1937]: Registering session with GDM
Jun 22 13:15:11 Pine64 ibus-daemon[2176]: GChildWatchSource: Exit status of a c.
Jun 22 13:15:12 Pine64 geoclue[941]: Service not used for 60 seconds. Shutting .
Jun 22 13:15:21 Pine64 tracker-miner-f[1878]: Error while sending AddMatch() med
Jun 22 13:15:21 Pine64 tracker-miner-f[1878]: Error while sending AddMatch() med
Jun 22 13:15:21 Pine64 tracker-miner-f[1878]: Error while sending AddMatch() med
Jun 22 13:15:21 Pine64 pipewire-media-session[1919]: error id:0 seq:194 res:-32r
no idea what goes wrong is the root cause here - anyone?
06-24-2021, 12:03 AM
(This post was last modified: 06-24-2021, 11:32 AM by sepp.
Edit Reason: added NVMe
)
Here is my experience with the official bullseye sdcard images
In short: Most stuff working out of the box
- Gnome(Wayland) crashes on login - still no solution
- Wireles needed some manual tweeking
Steps:
Flash the image as described here https://d-i.debian.org/daily-images/arm6...rd-images/ in the README
You need a serial adapter
Code: minicom -D /dev/ttyUSB0 -b 1500000
on a 2nd computer
This is a netinstall image so you need network connnectivity. I used an USB 2 Ethernet adapter
Boot the SD card and answer the questions in the serial console
Once done boot again from the SD card. Now you have a working console on the laptop screen
I installed Gnome but once I tried to logon (default Gnome) it crashed.
Though Gnome on XOrg and Gnome classic both work.
Wifi does not work out of the box due to missing firmware. I "borrowed" it from Armbian. Copy the Armbian /lib/firmware/bcrm/ folder contents and
ln -s brcmfmac43456-sdio.txt brcmfmac43456-sdio.pine64,pinebook-pro.txt
and Wifi works
I tried also installing to NVMe that the installer provides - no success does not boot
|
