Installation failed

[Gast]

Ich habe einen Rasperry Pi4 8GB, mit diesem kann ich auch das neueste Loxberry-image nicht laden. Wenn ich das image auf der Karte habe und das Gerät starte endet es in einem wunderschön bunten Bildschirm. Dies passiert auch, wenn man den rasperry pi ohne karte startet und diese dann einschiebt. Dann fängt er zwar an zu laden endet aber im bunten Bildschirm.

Irgend eine Idee, was ich noch testen kann ? Habe die hier aufgeführten werte ausprobiert, hat alles nicht funktioniert.
Image 2.2.0c endet zwar nicht im crash, dafür wird neuere software verlangt.

[Gast]

Hello,

this is my first post here so I would like to thank the whole team/community for all your work on LB, it is unbelievable what it can be done with it . Sadly, I cannot test it further, because I have same issue as above.

I have new Pi 4 (1GB), through Win32DiskImager I deployed Pippin from the latest link (2.2.0.d). First it occur to me, that RJ45 has a link, but no data goes through (orange lighting, no green blinking) and obviously no ARP/DHCP lease Mikrotik router (have static rule for LB and Miniserver). Because is brand new, I thought that Pi is damaged from manufacturing. I deployed recommended (rel. 2022-01-28) image via Raspberry Pi Imager. LAN immediately went on (and keyboard too, more below), saw MAC on router and Pi gets the IP from DHCP.

So I tried to deploy older LB version, but for Bilbo 2.0.0 is mine Pi 4 too young . So again deployed back to 2.0.0.d Pippin. On screen is the same error as above ("failed to start raise network interfaces"). I thought that I will try some advise f.e. HERE or HERE, but I discovered that keyboard is not working either. Well, that would be probably because it is wireless with USB dongle (even if on another devices its install itself via Plug&Play), so I went to the local Electro store for garbage cable keyboard (I know, shame on me I didn't have cable keyboard already home ), but doesn't working either . So without keyboard and network Pi is actually bricked - I cannot find a way how to solve at least one of this problem. Of course, I tried to save network.txt file to boot to activate LAN and WLAN "manually" but it is not work for me. Not sure if it is because WLAN has a space in the name, but it seems for me that I cannot set LAN/WLAN "manually" because network is just not specify/set in the OS, or I would like to try if the eth rename (mentioned in external articles above) can work but I cannot get to the system without a keyboard .

Is there any way I can f.e. deploy LB on VirtualBox, probably change the eth and then copy to SD card and try it in Pi?

Thank you and have a nice day
FrKal

[Prof.Mobilux]

Wlan should work. LAN is broken on newer Pi4. Blank/space in the name could be the problem. Change it and try to set wlan manually with network.txt

then please send me the output of the following commands mentioned here: https://www.loxforum.com/forum/proje...218#post339218

[Gast]

Have probably same issue as hmates in previous posts. I have UniFi too and there is WPA2 the lowest option. Could be this the issue that it is not working? If yes, I look into the Rasp. documentation HERE (chapter "Setting up a Headless Raspberry Pi") and I was thinking that creation of wpa_supplicant.conf may help, but I want to ask here first for sure...

My network.txt:
auto lo
iface lo inet loopback

allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-ssid HammondTest
wpa-psk GeorgeS680 (passwd changed for show)

I was thinking, can I setup open network (without security) and connect LB to it? I don't like this much but for testing purposes... and after LB joined I would activate MAC filter with whitelist only the MAC of LB. If yes, I just delete "wpa-psk" line or network.txt would look different?

Thank you
FrKal

Hi, Thanks for your support in advance! Below see my network.txt content. Only doubt I have is wpa-psk in the file vs wpa2 security I have on my wifi. I´m running Unifi, there is no possibility to choose weaker security than wpa2. Standard Raspbian image is running without problem.

auto lo
iface lo inet loopback

allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-ssid xwlan
wpa-psk 1234567890

[Prof.Mobilux]

No, wpa2 isn‘t the problem. Connect a monitor for debugging.

[Gast]

It seems that "Network is Online" but I cannot see it in DHCP lease list

[Prof.Mobilux]

I prepared another test image for the newer Raspberry Pis 4 (Rev. 1.5). Thanks to Gast for testing!

With this image USB and Ethernet should work again on these newer Pis. Please test it!

https://download.loxberry.de/testing/images/rasppi/loxberry-image-rasppi-2.2.0e_pippin.img.7z

[Gast]

Pippin 2.2.0e IS WORKING!!! You are awesome!

Right after deploy, LAN receive/send data, I see it in DHCP, even wireless keyboard via USB dongle is working. I'm already in web setup page via IP address.

Thank you! If there is any further test I should do, please let me know!

Have a nice day
FrKal

[w4Rd3n]

Prof.Mobilux
Link isnt working anymore. can you fix it or putit directly to loxberry downloads page ?
Thank you

[Prof.Mobilux]

Is it really so complicated to have a look into the wiki?!?! Sometimes I have the feeling that we are in kindergarten here… https://loxwiki.atlassian.net/wiki/s...+Spiegel-Sites

https://loxberry.woerstenfeld.de/download/testing/images/rasppi/

[Witte]

Hallo zusammen,
ich wollte kurz mitteilen, wie ich LoxBerry V2.2.1.2
auf einem Raspberry PI4B Revision 1.5 zum laufen gebracht habe und was nicht funktioniert hat:
Kopieren von start*.elf Dateien hat nicht funktioniert vom aktuellen RaspiOS Image

[LIST][*]Release date: April 4th 2022[*]System: 32-bit[*]Kernel version: 5.10[*]Debian version: 10 (buster)[/LIST]

hat nicht funktioniert.
Auch das kopieren von der gesamten Boot Partition hat nicht funktioniert.
Was funktioniert hat: Startup in einem Raspberry Pi 4B Revision 1.2 und danach ein rpi-update durchführen hat dann zum Erfolg geführt.
Wenn also jemand einen älteren RPi daheim hat, auf dem starten und das update durchführen.
Bisher keine Problem festgestellt mit dem System.