[opensuse-arm] Some progress with official images for Tumbleweed on Raspberry Pi 4B
I just tried the JeOS, XFCE and KDE versions of the "official" Tumbleweed images for the Raspberry Pi 4. They use kernel 5.4.10. openSUSE-Tumbleweed-ARM-{JeOS,XFCE,KDE}-raspberrypi4.aarch64-2020.01.08- Snapshot20200115.raw.xz Console input from the keyboard attached to a USB interface now works, however not in the grub2 window. I could switch between the tty{1-6} screens. However with XFCE and KDE there was no login screen on tty7. The console also gives a prompt for login, however after entering root there is no prompt for the password. I did not try to login via the serial line. On the console the system also shows there is an Ethernet connection working, and shows the IPv4 and IPv6 addresses, of which at least IPv4 reacts on an outside ping. It does present its public key, which is stored in ~/.ssh/known_hosts on the outside host. However ssh access hangs when a public key for this type of access is presented. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Am Montag, 20. Januar 2020, 12:38:00 CET schrieb Freek de Kruijf:
I just tried the JeOS, XFCE and KDE versions of the "official" Tumbleweed images for the Raspberry Pi 4. They use kernel 5.4.10. openSUSE-Tumbleweed-ARM-{JeOS,XFCE,KDE}-raspberrypi4.aarch64-2020.01.08- Snapshot20200115.raw.xz
Console input from the keyboard attached to a USB interface now works, however not in the grub2 window. I could switch between the tty{1-6} screens. However with XFCE and KDE there was no login screen on tty7.
Sounds like X didn't start. Is xf86-video-fbdev installed?
The console also gives a prompt for login, however after entering root there is no prompt for the password.
I did not try to login via the serial line.
On the console the system also shows there is an Ethernet connection working, and shows the IPv4 and IPv6 addresses, of which at least IPv4 reacts on an outside ping. It does present its public key, which is stored in ~/.ssh/known_hosts on the outside host. However ssh access hangs when a public key for this type of access is presented.
You mean when you ssh to the pi, it hangs after the host key exchange? Cheers, Fabian -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op maandag 20 januari 2020 21:19:20 CET schreef Fabian Vogt:
Hi,
Am Montag, 20. Januar 2020, 12:38:00 CET schrieb Freek de Kruijf:
I just tried the JeOS, XFCE and KDE versions of the "official" Tumbleweed images for the Raspberry Pi 4. They use kernel 5.4.10. openSUSE-Tumbleweed-ARM-{JeOS,XFCE,KDE}-raspberrypi4.aarch64-2020.01.08- Snapshot20200115.raw.xz
Console input from the keyboard attached to a USB interface now works, however not in the grub2 window. I could switch between the tty{1-6} screens. However with XFCE and KDE there was no login screen on tty7.
Sounds like X didn't start. Is xf86-video-fbdev installed?
I have no access to the system, not even via the serial console. Don't know how to inspect the SD card.
The console also gives a prompt for login, however after entering root there is no prompt for the password.
I did not try to login via the serial line.
On the console the system also shows there is an Ethernet connection working, and shows the IPv4 and IPv6 addresses, of which at least IPv4 reacts on an outside ping. It does present its public key, which is stored in ~/.ssh/known_hosts on the outside host. However ssh access hangs when a public key for this type of access is presented.
You mean when you ssh to the pi, it hangs after the host key exchange?
Yes. I did "ssh -v".
Cheers, Fabian
BTW. The XFCE system also reports errors in the ext4 file system. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 20/01/2020 12:38, Freek de Kruijf wrote:
I just tried the JeOS, XFCE and KDE versions of the "official" Tumbleweed images for the Raspberry Pi 4. They use kernel 5.4.10. openSUSE-Tumbleweed-ARM-{JeOS,XFCE,KDE}-raspberrypi4.aarch64-2020.01.08- Snapshot20200115.raw.xz
Console input from the keyboard attached to a USB interface now works, however not in the grub2 window. I could switch between the tty{1-6} screens. However
USB does not work in the grub window, as for now we don't have USB support in U-Boot, it will be work in progress: https://hackweek.suse.com/19/projects/uefi-slash-grub-keyboard-support-on-ra...
with XFCE and KDE there was no login screen on tty7.
The console also gives a prompt for login, however after entering root there is no prompt for the password.
I did not try to login via the serial line.
On the console the system also shows there is an Ethernet connection working, and shows the IPv4 and IPv6 addresses, of which at least IPv4 reacts on an outside ping. It does present its public key, which is stored in ~/.ssh/known_hosts on the outside host. However ssh access hangs when a public key for this type of access is presented.
Be patient, it takes a while. We will need to add the HW RNG to speed things up. I think this should be part of openSUSE Leap 15.2, maybe you want to try this images: https://download.opensuse.org/ports/aarch64/distribution/leap/15.2/appliance... RaspberryPi3 image should work (TM) on the RPi4 as well. Regards, Matthias -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op dinsdag 21 januari 2020 11:51:03 CET schreef Matthias Brugger:
Be patient, it takes a while. We will need to add the HW RNG to speed things up. I think this should be part of openSUSE Leap 15.2, maybe you want to try this images: https://download.opensuse.org/ports/aarch64/distribution/leap/15.2/appliance s/
RaspberryPi3 image should work (TM) on the RPi4 as well.
I tried the JeOS and XFCE RPi3 15.2 images om my RPi4. Both give a live system with keyboard access and a working network, both Ethernet and Wi-Fi and output on the HDMI screen. As was to be expected no keyboard access in grub2. However starting the display manager in XFCE did not work. Message about OnFailure which shows plymouth-quit.service. On my desktop the file /usr/lib/ systemd/system/plymouth-quit.service is delivered by the package plymouth. After installation of this package on the RPi4, this file did not appear. Also the system does only see 1 GB of memory, while my RPi4 has 4 GB. The XFCE system performed very slow when I was installing some extra software using zypper. Might be caused by a partly faulty SD card; after a reboot I got ext4 errors.
Regards, Matthias
-- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-----Original Message----- From: Freek de Kruijf <freek@opensuse.org> Sent: 22 January 2020 10:38 To: opensuse-arm@opensuse.org Subject: Re: [opensuse-arm] Some progress with official images for Tumbleweed and Leap 15.2 on Raspberry Pi 4B
Op dinsdag 21 januari 2020 11:51:03 CET schreef Matthias Brugger:
Be patient, it takes a while. We will need to add the HW RNG to speed things up. I think this should be part of openSUSE Leap 15.2, maybe you want to try this images: https://download.opensuse.org/ports/aarch64/distribution/leap/15.2/app liance s/
RaspberryPi3 image should work (TM) on the RPi4 as well.
I tried the JeOS and XFCE RPi3 15.2 images om my RPi4. Both give a live system with keyboard access and a working network, both Ethernet and Wi-Fi and output on the HDMI screen.
Thanks for testing!
As was to be expected no keyboard access in grub2.
However starting the display manager in XFCE did not work. Message about OnFailure which shows plymouth-quit.service. On my desktop the file /usr/lib/ systemd/system/plymouth-quit.service is delivered by the package plymouth. After installation of this package on the RPi4, this file did not appear.
Also the system does only see 1 GB of memory, while my RPi4 has 4 GB.
This was due to a bug in u-boot which should be fixed. I guess the update did not reach Leap:15.2 yet. Matthias?
The XFCE system performed very slow when I was installing some extra software using zypper. Might be caused by a partly faulty SD card; after a reboot I got ext4 errors.
You can try to remove 'swiotlb=512 cma=300M' from kernel cmdline in grub. Cheers, Guillaume
Regards, Matthias
-- fr.gr.
member openSUSE Freek de Kruijf
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 22/01/2020 10:50, Guillaume Gardet wrote:
-----Original Message----- From: Freek de Kruijf <freek@opensuse.org> Sent: 22 January 2020 10:38 To: opensuse-arm@opensuse.org Subject: Re: [opensuse-arm] Some progress with official images for Tumbleweed and Leap 15.2 on Raspberry Pi 4B
Op dinsdag 21 januari 2020 11:51:03 CET schreef Matthias Brugger:
Be patient, it takes a while. We will need to add the HW RNG to speed things up. I think this should be part of openSUSE Leap 15.2, maybe you want to try this images: https://download.opensuse.org/ports/aarch64/distribution/leap/15.2/app liance s/
RaspberryPi3 image should work (TM) on the RPi4 as well.
I tried the JeOS and XFCE RPi3 15.2 images om my RPi4. Both give a live system with keyboard access and a working network, both Ethernet and Wi-Fi and output on the HDMI screen.
Thanks for testing!
As was to be expected no keyboard access in grub2.
However starting the display manager in XFCE did not work. Message about OnFailure which shows plymouth-quit.service. On my desktop the file /usr/lib/ systemd/system/plymouth-quit.service is delivered by the package plymouth. After installation of this package on the RPi4, this file did not appear.
Also the system does only see 1 GB of memory, while my RPi4 has 4 GB.
This was due to a bug in u-boot which should be fixed. I guess the update did not reach Leap:15.2 yet. Matthias?
Looks really strange to me, as this should have been fixed a while ago. Can you try to update the u-boot-rpiarm64 package please and reboot. Regards, Matthias
The XFCE system performed very slow when I was installing some extra software using zypper. Might be caused by a partly faulty SD card; after a reboot I got ext4 errors.
You can try to remove 'swiotlb=512 cma=300M' from kernel cmdline in grub.
Cheers, Guillaume
Regards, Matthias
-- fr.gr.
member openSUSE Freek de Kruijf
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op donderdag 23 januari 2020 10:10:15 CET schreef Matthias Brugger:
Looks really strange to me, as this should have been fixed a while ago. Can you try to update the u-boot-rpiarm64 package please and reboot.
Regards, Matthias
I found u-boot-rpi3 was installed in the image. Tested only the JeOS image. After installation of u-boot-rpiarm64, which removed u-boot-rpi3, and a reboot the system saw the 4GB memory. However the system also reported ext4 errors and some commands crashed. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-----Original Message----- From: Freek de Kruijf <freek@opensuse.org> Sent: 24 January 2020 11:51 To: opensuse-arm@opensuse.org Subject: Re: [opensuse-arm] Some progress with official images for Tumbleweed and Leap 15.2 on Raspberry Pi 4B
Op donderdag 23 januari 2020 10:10:15 CET schreef Matthias Brugger:
Looks really strange to me, as this should have been fixed a while ago. Can you try to update the u-boot-rpiarm64 package please and reboot.
Regards, Matthias
I found u-boot-rpi3 was installed in the image. Tested only the JeOS image. After installation of u-boot-rpiarm64, which removed u-boot-rpi3, and a reboot the system saw the 4GB memory.
Great!
However the system also reported ext4 errors and some commands crashed.
Does dmesg show some errors regarding SD card? Guillaume
-- fr.gr.
member openSUSE Freek de Kruijf
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op vrijdag 24 januari 2020 11:53:56 CET schreef Guillaume Gardet:
However the system also reported ext4 errors and some commands crashed.
Does dmesg show some errors regarding SD card?
Guillaume
Installed JeOS image on SD card. Via ssh entered the RPi4 system. Installed u- boot-rpiarm64 and did a reboot. Entered the system again via ssh. This was extremely slow before a login prompt was shown and the prompt for the password. Saw with "top i" the amount of memory. Also hwinfo --memory reported: 01: None 00.0: 10102 Main Memory [Created at memory.74] Unique ID: rdCR.CxwsZFjVASF Hardware Class: memory Model: "Main Memory" Memory Range: 0x00000000-0xf1446fff (rw) Memory Size: 3 GB + 768 MB Config Status: cfg=new, avail=yes, need=no, active=unknown dmesg shows a lot of messages like below: [ 190.326171] ------------[ cut here ]------------ [ 190.326258] WARNING: CPU: 0 PID: 418 at ../drivers/mmc/host/sdhci.c:1094 sdhci_prepare_data+0x960/0x978 [sdhci] [ 190.326262] Modules linked in: af_packet iscsi_ibft iscsi_boot_sysfs nls_iso8859_1 nls_cp437 vfat fat btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 broadcom xhci_pci bcm_phy_lib rfkill xhci_hcd mdio_bcm_unimac cpufreq_dt raspberrypi_hwmon raspberrypi_cpufreq iproc_rng200 bcm2835_wdt pcie_brcmstb genet uio_pdrv_genirq uio crct10dif_ce leds_gpio mmc_block dwc2 sdhci_iproc sdhci_pltfm sdhci udc_core usbcore gpio_raspberrypi_exp clk_raspberrypi mmc_core i2c_bcm2835 bcm2835_dma phy_generic gpio_regulator fixed dm_mirror dm_region_hash dm_log sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs [ 190.326353] CPU: 0 PID: 418 Comm: kworker/0:1H Tainted: G W 5.3.18-lp152.1-default #1 openSUSE Leap 15.2 (unreleased) [ 190.326358] Hardware name: raspberrypi rpi/rpi, BIOS 2019.10 12/20/2019 [ 190.326380] Workqueue: kblockd blk_mq_run_work_fn [ 190.326389] pstate: 40000085 (nZcv daIf -PAN -UAO) [ 190.326405] pc : sdhci_prepare_data+0x960/0x978 [sdhci] [ 190.326419] lr : sdhci_prepare_data+0x960/0x978 [sdhci] [ 190.326423] sp : ffff0000103939d0 [ 190.326428] x29: ffff0000103939d0 x28: ffffb30f6b188148 [ 190.326436] x27: 0000000000000002 x26: ffffb30f6c5e0800 [ 190.326444] x25: ffffb30f6cf05000 x24: 0000000000000001 [ 190.326450] x23: 0000000000418958 x22: ffffb30f6b1882e0 [ 190.326457] x21: ffff2327e5999000 x20: ffffb30f6b188360 [ 190.326463] x19: ffffb30f6cf05580 x18: ffffffffffffffff [ 190.326469] x17: 0000000000000001 x16: 0000000000000007 [ 190.326475] x15: ffff2327e5999708 x14: 6f74202c29736574 [ 190.326481] x13: 7962203633353536 x12: ffff2327e59c0000 [ 190.326487] x11: 0000000000000000 x10: ffff2327e5bd2000 [ 190.326494] x9 : 0000000000000000 x8 : 0000000000000003 [ 190.326500] x7 : 0000000000000461 x6 : 00000000536549d7 [ 190.326506] x5 : 0000000000000001 x4 : ffffb30f7b77f2c8 [ 190.326513] x3 : ffffb30f7b77f2c8 x2 : f19f862514c0b000 [ 190.326519] x1 : 0000000000000000 x0 : 0000000000000024 [ 190.326526] Call trace: [ 190.326541] sdhci_prepare_data+0x960/0x978 [sdhci] [ 190.326555] sdhci_send_command+0xf0/0x618 [sdhci] [ 190.326568] sdhci_request+0xe8/0x120 [sdhci] [ 190.326605] __mmc_start_request+0x88/0x1b0 [mmc_core] [ 190.326639] mmc_start_request+0x98/0xd0 [mmc_core] [ 190.326652] mmc_blk_mq_issue_rq+0x5d4/0x7d0 [mmc_block] [ 190.326662] mmc_mq_queue_rq+0x14c/0x328 [mmc_block] [ 190.326669] blk_mq_dispatch_rq_list+0xb0/0x440 [ 190.326676] blk_mq_do_dispatch_sched+0x6c/0x110 [ 190.326684] blk_mq_sched_dispatch_requests+0x128/0x1f0 [ 190.326693] __blk_mq_run_hw_queue+0xd0/0x138 [ 190.326701] blk_mq_run_work_fn+0x28/0x38 [ 190.326712] process_one_work+0x200/0x450 [ 190.326720] worker_thread+0x50/0x4d0 [ 190.326727] kthread+0x130/0x138 [ 190.326736] ret_from_fork+0x10/0x18 [ 190.326741] ---[ end trace 8235e3938456c6b5 ]--- Hope this is what you are looking for. Currently the system, after this last message of dmesg, is responsive and repeating dmesg does not show any additions to its output. Did again a reboot. The system was more responsive and less output from dmesg. The last message was about swiotlb buffer full. Remembered a recommendation to remove swiotlb=512 from the command line in grub. Did so and did a reboot. Access via ssh was fast. No obvious error messages in dmesg anymore. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op vrijdag 24 januari 2020 11:53:56 CET schreef Guillaume Gardet:
Does dmesg show some errors regarding SD card?
Guillaume
Also tried the XFCE image. Removed swiotlb=512 from grub2.conf before booting this image. Things went OK, except no login screen for XFCE. Entered via ssh and installed u-boot-rpiarm64. Did a reboot and had slow respons. Entering via ssh provided an unexpected prompt after some error messages. At the end of dmesg got: [ 69.353406] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 193.212508] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:747: group 16, block bitmap and bg descriptor inconsistent: 16384 vs 19791 free clusters [ 193.333075] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p2, blocknr = 0). There's a risk of filesystem corruption in case of system crash. [ 298.387322] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:747: group 48, block bitmap and bg descriptor inconsistent: 16768 vs 24768 free clusters [ 335.068930] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:747: group 64, block bitmap and bg descriptor inconsistent: 16768 vs 24768 free clusters [ 337.118447] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p2, blocknr = 0). There's a risk of filesystem corruption in case of system crash. [ 344.421203] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p2, blocknr = 0). There's a risk of filesystem corruption in case of system crash. -bash-4.4# Above line is the console prompt. systemctl status display-manager gave: ● display-manager.service - X Display Manager Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-01-24 14:02:23 UTC; 11min ago Process: 2314 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS) Main PID: 2555 (code=exited, status=1/FAILURE) dec 13 10:57:09 bach2 display-manager[2314]: W: This will result in an 'us' X keyboard layout as default jan 24 14:00:57 bach2 display-manager[2314]: Starting service lightdm..done jan 24 14:00:53 bach2 systemd[1]: display-manager.service: PID file /var/run/ displaymanager.pid not readable (yet?) after start: No such file or directory jan 24 14:00:57 bach2 systemd[1]: Started X Display Manager. jan 24 14:01:51 bach2 lightdm[2555]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files jan 24 14:02:23 bach2 systemd[1]: display-manager.service: Main process exited, code=exited, status=1/FAILURE jan 24 14:02:23 bach2 systemd[1]: display-manager.service: Unit entered failed state. jan 24 14:02:23 bach2 systemd[1]: display-manager.service: Triggering OnFailure= dependencies. jan 24 14:02:23 bach2 systemd[1]: display-manager.service: Failed to enqueue OnFailure= job: No such file or directory jan 24 14:02:23 bach2 systemd[1]: display-manager.service: Failed with result 'exit-code'. After a reboot all looks OK, except the display-manager. Problem seems to be the X11 server. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fri, Jan 24, Freek de Kruijf wrote:
[ 193.333075] JBD2: Spotted dirty metadata buffer (dev = mmcblk0p2, blocknr = 0). There's a risk of filesystem corruption in case of system crash. [ 298.387322] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:747: group 48, block bitmap and bg descriptor inconsistent: 16768 vs 24768 free clusters
I have a kubernetes cluster running on four Pi4 without any issues. This sounds like your sd-card is not 100% ok anymore. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op vrijdag 24 januari 2020 21:8 CET schreef Freek de Kruijf: Repeated some of the tests on jan 24 using XFCE image for raspberrypi3.
jan 24 14:02:23 bach2 systemd[1]: display-manager.service: Triggering OnFailure= dependencies. jan 24 14:02:23 bach2 systemd[1]: display-manager.service: Failed to enqueue OnFailure= job: No such file or directory
Was resolved by installing plymouth, but seems not necessary. Also another error message about org.freedesktop.Accounts was resolved by installing packet accountsservice.
jan 24 14:02:23 bach2 systemd[1]: display-manager.service: Failed with result 'exit-code'.
After a reboot all looks OK, except the display-manager. Problem seems to be the X11 server.
Still a problem. I have packages xf86-video-fbdev and xf86-video-fbturbo installed, but still the error message in /var/log/Xorg.0.log: open /dev/dri/card0 : No such file or directory Associated with xf86-video-fbturbo is a device /dev/fb0, is that somehow a replacement for this device? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op maandag 20 januari 2020 12:38:00 CET schreef Freek de Kruijf:
I just tried the JeOS, XFCE and KDE versions of the "official" Tumbleweed images for the Raspberry Pi 4. They use kernel 5.4.10. openSUSE-Tumbleweed-ARM-{JeOS,XFCE,KDE}-raspberrypi4.aarch64-2020.01.08- Snapshot20200115.raw.xz
Tried again the XFCE image for Tumbleweed with great success!!! However I don't see any sound device. Is there a kernel module/driver to load to have sound via HDMI or the mini jack interface? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (5)
-
Fabian Vogt -
Freek de Kruijf -
Guillaume Gardet -
Matthias Brugger -
Thorsten Kukuk