El 29 d’octubre de 2019 16:42:28 CET, Guillaume Gardet <Guillaume.Gardet@arm.com> ha escrit:
Hi,
Matthias, what is the current status of RPi4?
Cheers, Guillaume
-----Original Message----- From: Freek de Kruijf <freek@opensuse.org> 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