Hi, Am Dienstag, 24. September 2019, 16:49:42 CEST schrieb Matthias Brugger:

Hi,

On 24/09/2019 13:24, Linux Kamarada wrote:

...

Hi, everyone!

AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. [1]

I’ve bought that board, I know the very basics on how to use it [2] and I want to help to port openSUSE to it. How can I start?

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

I just gave that image a try and after a while staring at a console with no activity I noticed that it's the JeOS with jeos-firstboot, so I had to remove "console=tty" to actually see anything. Using the HDMI console won't really work without USB support. Also, chrony-wait should be disabled, it delays booting by 10min as no network is currently working. What doesn't work: - USB (expected), but the OTG port seems to be available. It's forced to host mode by the kernel though as gadget support is not enabled - WiFi: brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 I see that you force-disabled WiFi stuff in JeOS.kiwi, I had to copy over the firmware manually - Ethernet: Gets detected just fine, but when actually sending packets the kernel freezes (sometimes with NETDEV WATCHDOG: eth0 (bcmgenet): transmit queue 1 timed out) - Sometimes the UART (clock?) glitches and there's garbled text What does work: - u-boot, grub, kernel, sd card, serial - I/O activity LED :D - cpufreq: Speed of "bc" corresponds roughly to CPU frequency So very nice progress already! I'll try to build a kernel with dwc2 peripheral support, maybe that's enough. Probably not though, considering it's USB-C... Cheers, Fabian

Regards, Matthias

[1] https://build.opensuse.org/project/monitor/home:mbrugger:branches:RPi4

...

Let’s have a lot of fun! :D

[1]: https://forums.opensuse.org/showthread.php/536541-Can-Raspberry-Pi-4-run-ope...

https://www.reddit.com/r/openSUSE/comments/c6xvnr/raspberry_pi_4/

https://www.raspberrypi.org/forums/viewtopic.php?t=244248

[2]: https://kamarada.github.io/pt/2019/09/20/primeiros-passos-no-raspberry-pi-co... (in Brazilian Portuguese, but English translation is on the way)

Antonio The Linux Kamarada Project http://kamarada.github.io/

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 25/09/2019 13:16, Matthias Brugger wrote:

On 25/09/2019 11:57, Fabian Vogt wrote:

...

Hi,

Am Dienstag, 24. September 2019, 16:49:42 CEST schrieb Matthias Brugger:

...

Hi,

On 24/09/2019 13:24, Linux Kamarada wrote:

...

Hi, everyone!

AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. [1]

I’ve bought that board, I know the very basics on how to use it [2] and I want to help to port openSUSE to it. How can I start?

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

I just gave that image a try and after a while staring at a console with no activity I noticed that it's the JeOS with jeos-firstboot, so I had to remove "console=tty" to actually see anything. Using the HDMI console won't really work without USB support.

Why? HDMI output should work.

...

Also, chrony-wait should be disabled, it delays booting by 10min as no network is currently working.

Yes, networking is on my list.

...

What doesn't work: - USB (expected), but the OTG port seems to be available. It's forced to host mode by the kernel though as gadget support is not enabled - WiFi: brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 I see that you force-disabled WiFi stuff in JeOS.kiwi, I had to copy over the firmware manually

Does it work reliably? I heard that it has some hick-ups.

...

- Ethernet: Gets detected just fine, but when actually sending packets the kernel freezes (sometimes with NETDEV WATCHDOG: eth0 (bcmgenet): transmit queue 1 timed out) - Sometimes the UART (clock?) glitches and there's garbled text

Really? Did you change anything in the config.txt? I haven't experienced this up to now.

...

What does work: - u-boot, grub, kernel, sd card, serial - I/O activity LED :D - cpufreq: Speed of "bc" corresponds roughly to CPU frequency

So very nice progress already!

Thanks :)

...

I'll try to build a kernel with dwc2 peripheral support, maybe that's enough. Probably not though, considering it's USB-C...

That's not enough. Nicolas is working on some patches to enable PCI, which is needed by USB.

Thinking twice I suspect that this was not correct.

Regards, Matthias

...

Cheers, Fabian

...

Regards, Matthias

[1] https://build.opensuse.org/project/monitor/home:mbrugger:branches:RPi4

...

Let’s have a lot of fun! :D

[1]: https://forums.opensuse.org/showthread.php/536541-Can-Raspberry-Pi-4-run-ope...

https://www.reddit.com/r/openSUSE/comments/c6xvnr/raspberry_pi_4/

https://www.raspberrypi.org/forums/viewtopic.php?t=244248

[2]: https://kamarada.github.io/pt/2019/09/20/primeiros-passos-no-raspberry-pi-co... (in Brazilian Portuguese, but English translation is on the way)

Antonio The Linux Kamarada Project http://kamarada.github.io/

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi, Am Mittwoch, 25. September 2019, 13:43:44 CEST schrieb Fabian Vogt:

Hi,

Am Mittwoch, 25. September 2019, 13:16:37 CEST schrieb Matthias Brugger:

...

On 25/09/2019 11:57, Fabian Vogt wrote:

...

Hi,

Am Dienstag, 24. September 2019, 16:49:42 CEST schrieb Matthias Brugger:

...

Hi,

On 24/09/2019 13:24, Linux Kamarada wrote:

...

Hi, everyone!

AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. [1]

I’ve bought that board, I know the very basics on how to use it [2] and I want to help to port openSUSE to it. How can I start?

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

I just gave that image a try and after a while staring at a console with no activity I noticed that it's the JeOS with jeos-firstboot, so I had to remove "console=tty" to actually see anything. Using the HDMI console won't really work without USB support.

Why? HDMI output should work.

Yes, but without any ability for interaction not really useful.

...

...

Also, chrony-wait should be disabled, it delays booting by 10min as no network is currently working.

Yes, networking is on my list.

...

What doesn't work: - USB (expected), but the OTG port seems to be available. It's forced to host mode by the kernel though as gadget support is not enabled - WiFi: brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 I see that you force-disabled WiFi stuff in JeOS.kiwi, I had to copy over the firmware manually

Does it work reliably? I heard that it has some hick-ups.

It doesn't work at all here, it fails because of the mentioned timeout.

...

...

- Ethernet: Gets detected just fine, but when actually sending packets the kernel freezes (sometimes with NETDEV WATCHDOG: eth0 (bcmgenet): transmit queue 1 timed out) - Sometimes the UART (clock?) glitches and there's garbled text

Really? Did you change anything in the config.txt? I haven't experienced this up to now.

Nope. I see it occasionally after between grub and the login prompt. I can't 100% rule out a bad connection, but as it doesn't glitch out after logging in at all I think that's unlikely.

...

...

What does work: - u-boot, grub, kernel, sd card, serial - I/O activity LED :D - cpufreq: Speed of "bc" corresponds roughly to CPU frequency

So very nice progress already!

Thanks :)

...

I'll try to build a kernel with dwc2 peripheral support, maybe that's enough. Probably not though, considering it's USB-C...

That's not enough. Nicolas is working on some patches to enable PCI, which is needed by USB.

For the USB-A ports, yes. Also for USB-C which is connected to the dwc2 which the kernel already initializes properly?

My kernel-default wasn't picked up by OBS yet for the last three hours :-/

Success! It works fine with a USB-C -> USB-A cable. Run: -CONFIG_USB_DWC2_HOST=y +# CONFIG_USB_DWC2_HOST is not set -# CONFIG_USB_DWC2_DUAL_ROLE is not set +CONFIG_USB_DWC2_DUAL_ROLE=y modprobe libcomposite u_ether mount none -t configfs /mnt cd /mnt/usb_gadget mkdir g1 cd g1 mkdir configs/c.1 functions/eem.usb0 ln -s functions/eem.usb0 configs/c.1/ echo fe980000.usb > UDC Forward a network connection, then: echo "BOOTPROTO=dhcp" > /etc/sysconfig/network/ifcfg-usb0 ifup usb0 and you can ssh onto the pi4 and download stuff. localhost:~ # hdparm -tT /dev/mmcblk1 /dev/mmcblk1: Timing cached reads: 1632 MB in 2.00 seconds = 816.32 MB/sec HDIO_DRIVE_CMD(identify) failed: Invalid argument Timing buffered disk reads: 126 MB in 3.01 seconds = 41.90 MB/sec I played around with some other programs and it seems like CPU performance has roughly doubled compared to a 3B+. Even over X11 forwarding applications run very smoothly. On my wish list is now to have u-boot use the device tree from the firmware for its own initialization as well, so that hardcoding of addresses isn't necessary anymore. That way we wouldn't need a new u-boot-rpi4 flavor and new JeOS flavors installing it instead of u-boot-rpi3. Cheers, Fabian

Cheers, Fabian

...

Regards, Matthias

...

Cheers, Fabian

...

Regards, Matthias

[1] https://build.opensuse.org/project/monitor/home:mbrugger:branches:RPi4

...

Let’s have a lot of fun! :D

[1]: https://forums.opensuse.org/showthread.php/536541-Can-Raspberry-Pi-4-run-ope...

https://www.reddit.com/r/openSUSE/comments/c6xvnr/raspberry_pi_4/

https://www.raspberrypi.org/forums/viewtopic.php?t=244248

[2]: https://kamarada.github.io/pt/2019/09/20/primeiros-passos-no-raspberry-pi-co... (in Brazilian Portuguese, but English translation is on the way)

Antonio The Linux Kamarada Project http://kamarada.github.io/

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi, Am Mittwoch, 25. September 2019, 17:01:16 CEST schrieb Guillaume Gardet:

Hi,

...

-----Original Message----- From: Fabian Vogt Sent: 25 September 2019 07:42 To: opensuse-arm@opensuse.org Cc: Matthias Brugger ; Linux Kamarada ; Nicolas Saenz Julienne Subject: Re: [opensuse-arm] Raspberry Pi 4 Model B

Hi,

Am Mittwoch, 25. September 2019, 13:43:44 CEST schrieb Fabian Vogt:

...

Hi,

Am Mittwoch, 25. September 2019, 13:16:37 CEST schrieb Matthias Brugger:

...

On 25/09/2019 11:57, Fabian Vogt wrote:

...

Hi,

Am Dienstag, 24. September 2019, 16:49:42 CEST schrieb Matthias Brugger:

...

Hi,

On 24/09/2019 13:24, Linux Kamarada wrote: > Hi, everyone! > > AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. [1] > > I’ve bought that board, I know the very basics on how to use it > [2] and I want to help to port openSUSE to it. How can I start? >

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

I just gave that image a try and after a while staring at a console with no activity I noticed that it's the JeOS with jeos-firstboot, so I had to remove "console=tty" to actually see anything. Using the HDMI console won't really work without USB support.

Why? HDMI output should work.

Yes, but without any ability for interaction not really useful.

...

...

Also, chrony-wait should be disabled, it delays booting by 10min as no network is currently working.

Yes, networking is on my list.

...

What doesn't work: - USB (expected), but the OTG port seems to be available. It's forced to host mode by the kernel though as gadget support is not enabled - WiFi: brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 I see that you force-disabled WiFi stuff in JeOS.kiwi, I had to copy over the firmware manually

Does it work reliably? I heard that it has some hick-ups.

It doesn't work at all here, it fails because of the mentioned timeout.

...

...

- Ethernet: Gets detected just fine, but when actually sending packets the kernel freezes (sometimes with NETDEV WATCHDOG: eth0 (bcmgenet): transmit queue 1 timed out) - Sometimes the UART (clock?) glitches and there's garbled text

Really? Did you change anything in the config.txt? I haven't experienced this up to now.

Nope. I see it occasionally after between grub and the login prompt. I can't 100% rule out a bad connection, but as it doesn't glitch out after logging in at all I think that's unlikely.

...

...

What does work: - u-boot, grub, kernel, sd card, serial - I/O activity LED :D - cpufreq: Speed of "bc" corresponds roughly to CPU frequency

So very nice progress already!

Thanks :)

...

I'll try to build a kernel with dwc2 peripheral support, maybe that's enough. Probably not though, considering it's USB-C...

That's not enough. Nicolas is working on some patches to enable PCI, which is needed by USB.

For the USB-A ports, yes. Also for USB-C which is connected to the dwc2 which the kernel already initializes properly?

My kernel-default wasn't picked up by OBS yet for the last three hours :-/

Success! It works fine with a USB-C -> USB-A cable. Run:

-CONFIG_USB_DWC2_HOST=y +# CONFIG_USB_DWC2_HOST is not set -# CONFIG_USB_DWC2_DUAL_ROLE is not set +CONFIG_USB_DWC2_DUAL_ROLE=y

Could you send a patch to get this into openSUSE/SUSE kernels configs (master, stable, 15.2, etc.), please?

I noticed that dual-role modes were already enabled for dwc2+dwc3 on armv6+armv7. Pull requests to those three branches are sent. SLES doesn't support USB gadget mode AFAIK, so I didn't do anything there. I guess that's also how this ended up being host-only for arm64. Cheers, Fabian

Thanks, Guillaume

...

modprobe libcomposite u_ether mount none -t configfs /mnt cd /mnt/usb_gadget mkdir g1 cd g1 mkdir configs/c.1 functions/eem.usb0 ln -s functions/eem.usb0 configs/c.1/ echo fe980000.usb > UDC

Forward a network connection, then:

echo "BOOTPROTO=dhcp" > /etc/sysconfig/network/ifcfg-usb0 ifup usb0

and you can ssh onto the pi4 and download stuff.

localhost:~ # hdparm -tT /dev/mmcblk1 /dev/mmcblk1: Timing cached reads: 1632 MB in 2.00 seconds = 816.32 MB/sec HDIO_DRIVE_CMD(identify) failed: Invalid argument Timing buffered disk reads: 126 MB in 3.01 seconds = 41.90 MB/sec

I played around with some other programs and it seems like CPU performance has roughly doubled compared to a 3B+. Even over X11 forwarding applications run very smoothly.

On my wish list is now to have u-boot use the device tree from the firmware for its own initialization as well, so that hardcoding of addresses isn't necessary anymore. That way we wouldn't need a new u-boot-rpi4 flavor and new JeOS flavors installing it instead of u-boot-rpi3.

Cheers, Fabian

...

Cheers, Fabian

...

Regards, Matthias

...

Cheers, Fabian

...

Regards, Matthias

[1] https://build.opensuse.org/project/monitor/home:mbrugger:branches :RPi4

> Let’s have a lot of fun! :D > > > [1]: > https://forums.opensuse.org/showthread.php/536541-Can-Raspberry- > Pi-4-run-openSUSE-LEAP-15-1/ > > https://www.reddit.com/r/openSUSE/comments/c6xvnr/raspberry_pi_4 > / > > https://www.raspberrypi.org/forums/viewtopic.php?t=244248 > > [2]: > https://kamarada.github.io/pt/2019/09/20/primeiros-passos-no-ras > pberry-pi-com-noobs-e-raspbian/ (in Brazilian Portuguese, but > English translation is on the way) > > > Antonio > The Linux Kamarada Project > http://kamarada.github.io/

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi, Am Mittwoch, 25. September 2019, 19:01:29 CEST schrieb Guillaume Gardet:

...

-----Original Message----- From: Fabian Vogt Sent: 25 September 2019 08:29 To: opensuse-arm@opensuse.org Cc: Guillaume Gardet ; Matthias Brugger ; Linux Kamarada ; Nicolas Saenz Julienne ; nd Subject: Re: [opensuse-arm] Raspberry Pi 4 Model B

Hi,

...

Hi,

...

-----Original Message----- From: Fabian Vogt Sent: 25 September 2019 07:42 To: opensuse-arm@opensuse.org Cc: Matthias Brugger ; Linux Kamarada ; Nicolas Saenz Julienne Subject: Re: [opensuse-arm] Raspberry Pi 4 Model B

Hi,

Am Mittwoch, 25. September 2019, 13:43:44 CEST schrieb Fabian Vogt:

...

Hi,

Am Mittwoch, 25. September 2019, 13:16:37 CEST schrieb Matthias Brugger:

...

On 25/09/2019 11:57, Fabian Vogt wrote: > Hi, > > Am Dienstag, 24. September 2019, 16:49:42 CEST schrieb Matthias

Brugger:

...

>> Hi, >> >> On 24/09/2019 13:24, Linux Kamarada wrote: >>> Hi, everyone! >>> >>> AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. >>> [1] >>> >>> I’ve bought that board, I know the very basics on how to use >>> it [2] and I want to help to port openSUSE to it. How can I start? >>> >> >> I'm working on some (still hacky) support for RPi4. >> You can find the JeOS image in my home project [1]. >> Beware that I was able to break the build of U-Boot yesterday. >> I'll try to fix this tonight. > > I just gave that image a try and after a while staring at a > console with no activity I noticed that it's the JeOS with > jeos-firstboot, so I had to remove "console=tty" to actually > see anything. Using the HDMI console won't really work without USB support.

Why? HDMI output should work.

Yes, but without any ability for interaction not really useful.

...

> Also, chrony-wait should be disabled, it delays booting by > 10min as no network is currently working.

Yes, networking is on my list.

> What doesn't work: > - USB (expected), but the OTG port seems to be available. It's > forced to host > mode by the kernel though as gadget support is not enabled > - WiFi: brcmfmac: brcmf_sdio_htclk: HT Avail timeout > (1000000): clkctl 0x50 > I see that you force-disabled WiFi stuff in JeOS.kiwi, I had to copy over

...

...

...

...

> firmware manually

Does it work reliably? I heard that it has some hick-ups.

It doesn't work at all here, it fails because of the mentioned timeout.

...

> - Ethernet: Gets detected just fine, but when actually sending packets

Am Mittwoch, 25. September 2019, 17:01:16 CEST schrieb Guillaume Gardet: the the

...

...

...

...

> kernel freezes (sometimes with > NETDEV WATCHDOG: eth0 (bcmgenet): transmit queue 1 timed > out) > - Sometimes the UART (clock?) glitches and there's garbled > text

Really? Did you change anything in the config.txt? I haven't experienced this up to now.

Nope. I see it occasionally after between grub and the login prompt. I can't 100% rule out a bad connection, but as it doesn't glitch out after logging in at all I think that's unlikely.

...

> What does work: > - u-boot, grub, kernel, sd card, serial > - I/O activity LED :D > - cpufreq: Speed of "bc" corresponds roughly to CPU frequency > > So very nice progress already!

Thanks :)

> I'll try to build a kernel with dwc2 peripheral support, maybe that's enough. > Probably not though, considering it's USB-C...

That's not enough. Nicolas is working on some patches to enable PCI, which is needed by USB.

For the USB-A ports, yes. Also for USB-C which is connected to the dwc2 which the kernel already initializes properly?

My kernel-default wasn't picked up by OBS yet for the last three hours :-/

Success! It works fine with a USB-C -> USB-A cable. Run:

-CONFIG_USB_DWC2_HOST=y +# CONFIG_USB_DWC2_HOST is not set -# CONFIG_USB_DWC2_DUAL_ROLE is not set +CONFIG_USB_DWC2_DUAL_ROLE=y

Could you send a patch to get this into openSUSE/SUSE kernels configs (master, stable, 15.2, etc.), please?

I noticed that dual-role modes were already enabled for dwc2+dwc3 on armv6+armv7. Pull requests to those three branches are sent.

Thanks a lot!

Got merged meanwhile, but apparently not synced to kernel.opensuse.org yet. Got merged already:

...

SLES doesn't support USB gadget mode AFAIK, so I didn't do anything there.

Hmm, looks like it should be changed, no?

SLE has CONFIG_USB_GADGET=n, so doing that would be a rather big change which needs discussion. It's not just a module which can be marked as unsupported. I don't know whether any platform currently supported by SLE even has USB device controllers. Cheers, Fabian Currently SLE has CONFIG_USB_GADGET=n. Cheers, Fabian

Cheers, Guillaume

...

I guess that's also how this ended up being host-only for arm64.

Cheers, Fabian

...

Thanks, Guillaume

...

modprobe libcomposite u_ether mount none -t configfs /mnt cd /mnt/usb_gadget mkdir g1 cd g1 mkdir configs/c.1 functions/eem.usb0 ln -s functions/eem.usb0 configs/c.1/ echo fe980000.usb > UDC

Forward a network connection, then:

echo "BOOTPROTO=dhcp" > /etc/sysconfig/network/ifcfg-usb0 ifup usb0

and you can ssh onto the pi4 and download stuff.

localhost:~ # hdparm -tT /dev/mmcblk1 /dev/mmcblk1: Timing cached reads: 1632 MB in 2.00 seconds = 816.32 MB/sec HDIO_DRIVE_CMD(identify) failed: Invalid argument Timing buffered disk

reads:

...

126 MB in 3.01 seconds = 41.90 MB/sec

I played around with some other programs and it seems like CPU performance has roughly doubled compared to a 3B+. Even over X11 forwarding applications run very smoothly.

On my wish list is now to have u-boot use the device tree from the firmware for its own initialization as well, so that hardcoding of addresses isn't necessary anymore. That way we wouldn't need a new u-boot-rpi4 flavor and new JeOS flavors installing it instead of u-boot-rpi3.

Cheers, Fabian

...

Cheers, Fabian

...

Regards, Matthias

> > Cheers, > Fabian > >> Regards, >> Matthias >> >> [1] >> https://build.opensuse.org/project/monitor/home:mbrugger:bran >> ches >> :RPi4 >> >>> Let’s have a lot of fun! :D >>> >>> >>> [1]: >>> https://forums.opensuse.org/showthread.php/536541-Can-Raspbe >>> rry- Pi-4-run-openSUSE-LEAP-15-1/ >>> >>> https://www.reddit.com/r/openSUSE/comments/c6xvnr/raspberry_ >>> pi_4 >>> / >>> >>> https://www.raspberrypi.org/forums/viewtopic.php?t=244248 >>> >>> [2]: >>> https://kamarada.github.io/pt/2019/09/20/primeiros-passos-no >>> -ras pberry-pi-com-noobs-e-raspbian/ (in Brazilian >>> Portuguese, but English translation is on the way) >>> >>> >>> Antonio >>> The Linux Kamarada Project >>> http://kamarada.github.io/

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-----Original Message----- From: Fabian Vogt Sent: 25 September 2019 07:42 To: opensuse-arm@opensuse.org Cc: Matthias Brugger ; Linux Kamarada ; Nicolas Saenz Julienne Subject: Re: [opensuse-arm] Raspberry Pi 4 Model B

Hi,

Am Mittwoch, 25. September 2019, 13:43:44 CEST schrieb Fabian Vogt:

...

Hi,

Am Mittwoch, 25. September 2019, 13:16:37 CEST schrieb Matthias Brugger:

...

On 25/09/2019 11:57, Fabian Vogt wrote:

...

Hi,

Am Dienstag, 24. September 2019, 16:49:42 CEST schrieb Matthias Brugger:

...

Hi,

On 24/09/2019 13:24, Linux Kamarada wrote:

...

Hi, everyone!

AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. [1]

I’ve bought that board, I know the very basics on how to use it [2] and I want to help to port openSUSE to it. How can I start?

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

I just gave that image a try and after a while staring at a console with no activity I noticed that it's the JeOS with jeos-firstboot, so I had to remove "console=tty" to actually see anything. Using the HDMI console won't really work without USB support.

Why? HDMI output should work.

Yes, but without any ability for interaction not really useful.

...

...

Also, chrony-wait should be disabled, it delays booting by 10min as no network is currently working.

Yes, networking is on my list.

...

What doesn't work: - USB (expected), but the OTG port seems to be available. It's forced to host mode by the kernel though as gadget support is not enabled - WiFi: brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 I see that you force-disabled WiFi stuff in JeOS.kiwi, I had to copy over the firmware manually

Does it work reliably? I heard that it has some hick-ups.

It doesn't work at all here, it fails because of the mentioned timeout.

...

...

- Ethernet: Gets detected just fine, but when actually sending packets the kernel freezes (sometimes with NETDEV WATCHDOG: eth0 (bcmgenet): transmit queue 1 timed out) - Sometimes the UART (clock?) glitches and there's garbled text

Really? Did you change anything in the config.txt? I haven't experienced this up to now.

Nope. I see it occasionally after between grub and the login prompt. I can't 100% rule out a bad connection, but as it doesn't glitch out after logging in at all I think that's unlikely.

...

...

What does work: - u-boot, grub, kernel, sd card, serial - I/O activity LED :D - cpufreq: Speed of "bc" corresponds roughly to CPU frequency

So very nice progress already!

Thanks :)

...

I'll try to build a kernel with dwc2 peripheral support, maybe that's enough. Probably not though, considering it's USB-C...

That's not enough. Nicolas is working on some patches to enable PCI, which is needed by USB.

For the USB-A ports, yes. Also for USB-C which is connected to the dwc2 which the kernel already initializes properly?

My kernel-default wasn't picked up by OBS yet for the last three hours :-/

Success! It works fine with a USB-C -> USB-A cable. Run:

-CONFIG_USB_DWC2_HOST=y +# CONFIG_USB_DWC2_HOST is not set -# CONFIG_USB_DWC2_DUAL_ROLE is not set +CONFIG_USB_DWC2_DUAL_ROLE=y

modprobe libcomposite u_ether mount none -t configfs /mnt cd /mnt/usb_gadget mkdir g1 cd g1 mkdir configs/c.1 functions/eem.usb0 ln -s functions/eem.usb0 configs/c.1/ echo fe980000.usb > UDC

Forward a network connection, then:

echo "BOOTPROTO=dhcp" > /etc/sysconfig/network/ifcfg-usb0 ifup usb0

and you can ssh onto the pi4 and download stuff.

localhost:~ # hdparm -tT /dev/mmcblk1 /dev/mmcblk1: Timing cached reads: 1632 MB in 2.00 seconds = 816.32 MB/sec HDIO_DRIVE_CMD(identify) failed: Invalid argument Timing buffered disk reads: 126 MB in 3.01 seconds = 41.90 MB/sec

I played around with some other programs and it seems like CPU performance has roughly doubled compared to a 3B+.

A72 vs A53. 😉 You may also have CPUFreq which boost perfs, if you are running a 5.3+ kernel. Cheers, Guillaume

Even over X11 forwarding applications run very smoothly.

On my wish list is now to have u-boot use the device tree from the firmware for its own initialization as well, so that hardcoding of addresses isn't necessary anymore. That way we wouldn't need a new u-boot-rpi4 flavor and new JeOS flavors installing it instead of u-boot-rpi3.

Cheers, Fabian

...

Cheers, Fabian

...

Regards, Matthias

...

Cheers, Fabian

...

Regards, Matthias

[1] https://build.opensuse.org/project/monitor/home:mbrugger:branches :RPi4

...

Let’s have a lot of fun! :D

[1]: https://forums.opensuse.org/showthread.php/536541-Can-Raspberry- Pi-4-run-openSUSE-LEAP-15-1/

https://www.reddit.com/r/openSUSE/comments/c6xvnr/raspberry_pi_4 /

https://www.raspberrypi.org/forums/viewtopic.php?t=244248

[2]: https://kamarada.github.io/pt/2019/09/20/primeiros-passos-no-ras pberry-pi-com-noobs-e-raspbian/ (in Brazilian Portuguese, but English translation is on the way)

Antonio The Linux Kamarada Project http://kamarada.github.io/

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Tue, Sep 24, 2019 at 11:49 AM Matthias Brugger wrote:

Hi,

On 24/09/2019 13:24, Linux Kamarada wrote:

...

Hi, everyone!

AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. [1]

I’ve bought that board, I know the very basics on how to use it [2] and I want to help to port openSUSE to it. How can I start?

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

Regards, Matthias

[1] https://build.opensuse.org/project/monitor/home:mbrugger:branches:RPi4

Hi, folks! I know how to use OBS and KIWI, but when it comes to compile kernels, I'm a complete noob... also, I'm getting started with Raspberry Pi. I thought that would be easier, as there are at least three Linux distributions now (Raspbian [1], LibreELEC and Manjaro) supporting Raspberry Pi 4. Isn't there a kind of copy/paste that could allow us to boot openSUSE reusing Raspbian configs, for instance? What I've done so far... I downloaded Matthias' image: openSUSE-Tumbleweed-JeOS.aarch64-15.1.0-RaspberryPi4-Build61.1.raw.xz (did I choose the right one?) and flashed into the SD card using balenaEtcher [2]. During boot, I saw something like GRUB (did you say U-Boot?). My RPi4 is connected to a HDMI monitor, which worked, but USB keyboard did not respond and I got only this: https://paste.opensuse.org/42439427 Am I doing something wrong? [1]: English translation is here: https://kamarada.github.io/en/2019/09/29/getting-started-on-raspberry-pi-wit... [2]: https://www.balena.io/etcher/ Antonio The Linux Kamarada Project http://kamarada.github.io/ -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Tue, Oct 1, 2019 at 5:56 AM Matthias Brugger wrote:

On 01/10/2019 04:17, Linux Kamarada wrote:

...

Hi, folks!

I know how to use OBS and KIWI, but when it comes to compile kernels, I'm a complete noob... also, I'm getting started with Raspberry Pi.

I thought that would be easier, as there are at least three Linux distributions now (Raspbian [1], LibreELEC and Manjaro) supporting Raspberry Pi 4.

Isn't there a kind of copy/paste that could allow us to boot openSUSE reusing Raspbian configs, for instance?

What do you mean by Rasbian configs? Do you mean the kernel config? We are trying to support RPi4 with the mainline kernel. Raspbian uses a downstream kernel which only works on RPis, so the kernel config won't work on our mainline kernel.

Yes, that's what I meant: kernel config :) I thought about, using openSUSE tools, build a kernel close to the Raspbian's one. Maybe that's what Manjaro did. Now I have 3 SD cards with Raspbian, Manjaro and openSUSE (your in development port). Talking about kernel versions... openSUSE Leap 15.1 for x86-64 - 4.12.14 (I use it on my laptop) Manjaro ARM 19.08 with XFCE - 4.19.65 * Raspbian Buster (10.0) - 4.19.66 * see they are close? Your latest build - 5.3.rc8 (according to openSUSE-Tumbleweed-JeOS ... .packages) openSUSE Tumbleweed for x86-64 - 5.3.1 (according to software.opensuse.org) In kernel.org: stable - 5.3.2 longterm - 4.19.76 I think I'm going to follow your work, but in parallel I will try to port openSUSE Leap 15.1 to RPi4 using an older kernel (4.19.x). Or maybe I will work on 15.2, it seems people are already working on it. I've got a lot to study: how to build ARM packages with OBS, how to compile kernels, how to build OEM images with KIWI / OBS (I'm used to build live ISOs)... Thank you for your efforts and explanations! Antonio The Linux Kamarada Project http://kamarada.github.io/ -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Tue, Oct 1, 2019 at 9:37 AM Linux Kamarada wrote:

On Tue, Oct 1, 2019 at 5:56 AM Matthias Brugger wrote:

...

What do you mean by Rasbian configs? Do you mean the kernel config? We are trying to support RPi4 with the mainline kernel. Raspbian uses a downstream kernel which only works on RPis, so the kernel config won't work on our mainline kernel.

Yes, that's what I meant: kernel config :)

I thought about, using openSUSE tools, build a kernel close to the Raspbian's one. Maybe that's what Manjaro did.

I'm trying to build the Linux kernel provided by the Raspberry Pi Foundation, its source is available here: https://github.com/raspberrypi/linux/tree/raspberrypi-kernel_1.20190925-1 And build instructions can be found here: https://www.raspberrypi.org/documentation/linux/kernel/building.md I was able to cross-compile it using my 64-bit PC at home. Also, I was able to build something at OBS: https://build.opensuse.org/package/show/home:kamarada:15.1:dev:RPi4/raspberr... But OBS built it for x86_64, while armv7l and aarch64 were excluded. What am I doing wrong? Thank you! Antonio The Linux Kamarada Project http://kamarada.github.io/ -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Tue, Nov 5, 2019 at 6:30 AM Matthias Brugger wrote:

On 04/11/2019 23:23, Linux Kamarada wrote:

...

I'm trying to build the Linux kernel provided by the Raspberry Pi Foundation, its source is available here:

Why are you doing this?

Although I agree the best way is what you are doing (trying to integrate the RPi4 modules into the upstream Linux kernel), I believe the fastest way of getting a working Leap 15.1 on a RPi4 is to use the same kernel provided by the Raspberry Pi Foundation and already used by Raspbian and Manjaro. So, I decided to try that other direction.

...

But OBS built it for x86_64, while armv7l and aarch64 were excluded.

What am I doing wrong?

You need to change the the project's meta and add a repository for arm. This should give you the idea: https://build.opensuse.org/projects/hardware:boot/meta

Thanks! Now things are building: https://build.opensuse.org/project/monitor/home:kamarada:15.1:dev:RPi4 Have you seen Request 736763? :-o https://build.opensuse.org/request/show/736763 "This is a humble request to remove this project. Accepting this request will free resources on our always crowded server. Please decline this request if you want to keep this repository nevertheless. Otherwise this request will get accepted automatically in near future. Such requests get not created for projects with open requests or if you remove the OBS:AutoCleanup attribute. Created by Admin 29 days ago In state new This request will be automatically accepted in __1 day__." :-o (emphasis added) Please, deny it :D Antonio The Linux Kamarada Project http://kamarada.github.io/ -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op vrijdag 8 november 2019 12:35:03 CET schreef Matthias Brugger:

Out of interest, what's the most urgent thing you need in RPi4 that is not supported by our image right now (I know we are missing a lot of stuff still).

For me, the order of importance is: 1. Make wired Ethernet working with ssh access, so you don't need to configure the system to run. It should run using DHCP from the image. 2. Make keyboard, mouse and display working, so a desktop can be used. 3. Make Wi-Fi working. 4. Make USB 3.0 working.

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

Op zondag 10 november 2019 18:48:11 CET schreef Matthias Brugger:

On 09/11/2019 17:25, Freek de Kruijf wrote:

...

Op vrijdag 8 november 2019 12:35:03 CET schreef Matthias Brugger:

...

Out of interest, what's the most urgent thing you need in RPi4 that is not supported by our image right now (I know we are missing a lot of stuff still).

For me, the order of importance is: 1. Make wired Ethernet working with ssh access, so you don't need to configure the system to run. It should run using DHCP from the image. 2. Make keyboard, mouse and display working, so a desktop can be used.

Keyboard and mouse will need to get connected to the USB3.0 port, or are you able to connect and power the deivce via the type-C connector?

Yes. I power the device via the USB-C with a 5V 3A unit with a converter cable.

Regards, Matthias

...

3. Make Wi-Fi working. 4. Make USB 3.0 working.

...

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

Op vrijdag oktober 2019 23:15:42 CEST schreef Freek de Kruijf:

Op dinsdag 24 september 2019 16:49:42 CEST schreef Matthias Brugger:

...

Hi,

On 24/09/2019 13:24, Linux Kamarada wrote:

...

Hi, everyone!

AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. [1]

I’ve bought that board, I know the very basics on how to use it [2] and I want to help to port openSUSE to it. How can I start?

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

Regards, Matthias

Today I got my RPi4B system. I tried both images on:

https://download.opensuse.org/repositories/home:/mbrugger:/branches:/RPi4/ openSUSE_Tumbleweed_ARM/

but did not get any result; that is: nothing on the HDMI screen. Tried both outputs.

What am I doing wrong?

I connected a serial device to the UART pins on the GPIO and got the system running with output and input on this console. Build31.12 from the above repository did not work. The above working system is with Build26.1. Updated the wiki to reflect this fact. I tried to enable Wired Ethernet but this failed so far. Any suggestions? -- 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/10/2019 18:18, Freek de Kruijf wrote:

Op vrijdag oktober 2019 23:15:42 CEST schreef Freek de Kruijf:

...

Op dinsdag 24 september 2019 16:49:42 CEST schreef Matthias Brugger:

...

Hi,

On 24/09/2019 13:24, Linux Kamarada wrote:

...

Hi, everyone!

AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. [1]

I’ve bought that board, I know the very basics on how to use it [2] and I want to help to port openSUSE to it. How can I start?

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

Regards, Matthias

Today I got my RPi4B system. I tried both images on:

https://download.opensuse.org/repositories/home:/mbrugger:/branches:/RPi4/ openSUSE_Tumbleweed_ARM/

but did not get any result; that is: nothing on the HDMI screen. Tried both outputs.

You will need to add console=tty boot parameter. But no USB, so no keyboard...

...

What am I doing wrong?

I connected a serial device to the UART pins on the GPIO and got the system running with output and input on this console.

Build31.12 from the above repository did not work. The above working system is with Build26.1.

Updated the wiki to reflect this fact.

Thanks. The project is not meant to always provide working images. I'm working on a Tumbleweed image.

I tried to enable Wired Ethernet but this failed so far. Any suggestions?

Wait, the patches are not upstream. We are working on it. Regards, Matthias -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op maandag 21 oktober 2019 11:00:49 CEST schreef u:

On 20/10/2019 18:18, Freek de Kruijf wrote:

...

Op vrijdag oktober 2019 23:15:42 CEST schreef Freek de Kruijf:

...

Op dinsdag 24 september 2019 16:49:42 CEST schreef Matthias Brugger:

...

Hi,

On 24/09/2019 13:24, Linux Kamarada wrote:

...

Hi, everyone!

AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. [1]

I’ve bought that board, I know the very basics on how to use it [2] and I want to help to port openSUSE to it. How can I start?

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

Regards, Matthias

Today I got my RPi4B system. I tried both images on:

https://download.opensuse.org/repositories/home:/mbrugger:/branches:/RPi4 / openSUSE_Tumbleweed_ARM/

but did not get any result; that is: nothing on the HDMI screen. Tried both outputs.

You will need to add console=tty boot parameter. But no USB, so no keyboard...

...

...

What am I doing wrong?

I connected a serial device to the UART pins on the GPIO and got the system running with output and input on this console.

Build31.12 from the above repository did not work. The above working system is with Build26.1.

Updated the wiki to reflect this fact.

Thanks. The project is not meant to always provide working images. I'm working on a Tumbleweed image.

I do not expect that. It is meant to warn other users.

...

I tried to enable Wired Ethernet but this failed so far. Any suggestions?

Wait, the patches are not upstream. We are working on it.

OK. I am patiently waiting. Indeed the message Chester Lin mentioned is found in the journal. But I do not have the skills to do anything with his suggestion. I even have a problem with screen to connect via my USB serial line to the RPi4. I can't find how to change the window size from 24x80 to something larger. I tried "C-a : width -w 132 48" and "C-a : displays" these values, but my lines are cut off at 80.

Regards, Matthias

-- fr.gr. member openSUSE Freek de Kruijf -- 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 18 oktober 2019 23:15:42 CET schreef Freek de Kruijf:

Op dinsdag 24 september 2019 16:49:42 CEST schreef Matthias Brugger:

...

Hi,

On 24/09/2019 13:24, Linux Kamarada wrote:

...

Hi, everyone!

AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. [1]

I’ve bought that board, I know the very basics on how to use it [2] and I want to help to port openSUSE to it. How can I start?

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

Regards, Matthias

Today I got my RPi4B system. I tried both images on:

https://download.opensuse.org/repositories/home:/mbrugger:/branches:/RPi4/ openSUSE_Tumbleweed_ARM/

but did not get any result; that is: nothing on the HDMI screen. Tried both outputs.

What am I doing wrong?

Tried openSUSE-Tumbleweed-JeOS.aarch64-15.1.0-RaspberryPi4-Build42.8.raw.xz and got some results: output/input on the serial line. However no network connection. The eth0 interface is UP and has link local addresses 169... and fe80::..., but apparently not a proper connection. I tried Buster on this system and got it working, both via the serial line and via ssh, but I did not get any output on the HDMI interface. This seems to be a known problem with certain monitors. I have a TV screen and an ACER display with HDMI and VGA input, but also a HDMI->VGA converter gives nothing on the screen. So, my question is: should I get something in the current state on the HDMI screen? Is there anything I can do to help with getting TW or Leap 15.1/2 running on the RPI4? -- 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

El 29 d’octubre de 2019 16:42:28 CET, Guillaume Gardet ha escrit:

Hi,

Matthias, what is the current status of RPi4?

Cheers, Guillaume

...

-----Original Message----- From: Freek de Kruijf Sent: 29 October 2019 16:40 To: opensuse-arm@opensuse.org Subject: Re: [opensuse-arm] Raspberry Pi 4 Model B

Op vrijdag 18 oktober 2019 23:15:42 CET schreef Freek de Kruijf:

...

Op dinsdag 24 september 2019 16:49:42 CEST schreef Matthias Brugger:

...

Hi,

On 24/09/2019 13:24, Linux Kamarada wrote:

...

Hi, everyone!

AFAIK openSUSE does not support Raspberry Pi 4 Model B yet. [1]

I’ve bought that board, I know the very basics on how to use it [2] and I want to help to port openSUSE to it. How can I start?

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

Regards, Matthias

Today I got my RPi4B system. I tried both images on:

https://download.opensuse.org/repositories/home:/mbrugger:/branches:/R

...

Pi4/ openSUSE_Tumbleweed_ARM/

but did not get any result; that is: nothing on the HDMI screen. Tried both outputs.

What am I doing wrong?

Tried openSUSE-Tumbleweed-JeOS.aarch64-15.1.0-RaspberryPi4- Build42.8.raw.xz and got some results: output/input on the serial line. However no network connection. The eth0 interface is UP and has link local addresses 169... and fe80::..., but apparently not a proper connection.

Network is not working. I send a first version to enable it, but it needa rework. I'll send b2 soon. My plan is to integrate it into tumbleweed image, as soon as it gets accepted upstream.

...

I tried Buster on this system and got it working, both via the serial line and via ssh, but I did not get any output on the HDMI interface. This seems to be a known problem with certain monitors. I have a TV screen and an ACER display with HDMI and VGA input, but also a HDMI->VGA converter gives nothing on the screen.

You need to boot with the HDMI cable comnected to the RPi4. This should give you an EFI framebuffer. Work on the KMS driver is in progress but will take a while.

...

So, my question is: should I get something in the current state on

the HDMI

...

screen?

Try to add console=tty to your kernel boot parameters. Beware that USB is not working ATM. Another thing we are working on, stay tuned.

...

Is there anything I can do to help with getting TW or Leap 15.1/2 running on the RPI4?

You could try if i2c and SPI is working on the pins. 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.

-- Enviat des del meu dispositiu Android amb el K-9 Mail. Disculpeu la brevetat. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Hi,

-----Original Message----- From: Freek de Kruijf Sent: 30 October 2019 23:16 To: opensuse-arm@opensuse.org Subject: Re: [opensuse-arm] Raspberry Pi 4 Model B

Op woensdag 30 oktober 2019 20:56:42 CET schreef Matthias Brugger:

...

You need to boot with the HDMI cable comnected to the RPi4. This should give you an EFI framebuffer. Work on the KMS driver is in progress but will take a while.

...

...

So, my question is: should I get something in the current state on

the HDMI

...

screen?

Try to add console=tty to your kernel boot parameters. Beware that USB is not working ATM. Another thing we are working on, stay tuned.

No output on the HDMI interface. Is there a way to from within the system that video output to which HDMI port is active?

...

...

...

Is there anything I can do to help with getting TW or Leap 15.1/2

running on the

...

RPI4?

You could try if i2c and SPI is working on the pins.

Can you point me to some documentation to see how these things should work?

You can check the following wiki pages https://en.opensuse.org/openSUSE:I2C and https://en.opensuse.org/openSUSE:SPI Guillaume

I did work with python-RPi.GPIO.

...

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. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-----Original Message----- From: Matthias Brugger Sent: 31 October 2019 14:52 To: Guillaume Gardet ; Freek de Kruijf ; opensuse-arm@opensuse.org Subject: Re: [opensuse-arm] Raspberry Pi 4 Model B

On 31/10/2019 09:45, Guillaume Gardet wrote:

...

Hi,

...

-----Original Message----- From: Freek de Kruijf Sent: 30 October 2019 23:16 To: opensuse-arm@opensuse.org Subject: Re: [opensuse-arm] Raspberry Pi 4 Model B

Op woensdag 30 oktober 2019 20:56:42 CET schreef Matthias Brugger:

...

You need to boot with the HDMI cable comnected to the RPi4. This should give you an EFI framebuffer. Work on the KMS driver is in progress but will take a while.

...

...

So, my question is: should I get something in the current state on

the HDMI

...

screen?

Try to add console=tty to your kernel boot parameters. Beware that USB is not working ATM. Another thing we are working on, stay tuned.

No output on the HDMI interface. Is there a way to from within the system that video output to which HDMI port is active?

It's the one next to the USB Type-C connector.

So, this is HDMI0. The other one is HDMI1. Guillaume

Regards, Matthias

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. N�����r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0�����Ǩ�

On 02/11/2019 11:29, Freek de Kruijf wrote:

Op dinsdag 24 september 2019 16:49:42 CET schreef Matthias Brugger:

...

Hi,

I'm working on some (still hacky) support for RPi4. You can find the JeOS image in my home project [1]. Beware that I was able to break the build of U-Boot yesterday. I'll try to fix this tonight.

Regards, Matthias

I am still unable to get any output on an attached HDMI monitor. Also using Raspbian Buster is not showing anything on the screen.

If you don't see any output with Raspbian than this hints to a problem with your HW setup. Check the cable/monitor etc. Regards, Matthias

This last system has a application, tvservice, to manipulate the output to the screen. It shows HDMI0 is active.

Is there something in openSUSE which does the same?

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org