[opensuse-arm] Raspberry Pi 3 B+ ?
I have just acquired two of these, one for my son's school project, one for our mediacentre. Using the KDE appliance, it boots up fine, but as soon as I start setting up the wifi, it crashes. Then I tried usig yast to set date&time - crash. -- Per Jessen, Zürich (7.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Per, which openSUSE version are you running on your Pi? I would try to test WiFi with just the command line interface, to make sure it has nothing to do with KDE. If you can track it down to KDE then some error message/debug information would be helpfull. Always feel free to open a bug report about it with as much information as possible, so it can be tracked down properly. Regards, Alex~ On Fri, Mar 01, 2019 at 01:59:36PM +0100, Per Jessen wrote:
I have just acquired two of these, one for my son's school project, one for our mediacentre. Using the KDE appliance, it boots up fine, but as soon as I start setting up the wifi, it crashes. Then I tried usig yast to set date&time - crash.
--
Alexander Bergmann
Alexander Bergmann wrote:
Hi Per,
which openSUSE version are you running on your Pi?
I would try to test WiFi with just the command line interface, to make sure it has nothing to do with KDE. If you can track it down to KDE then some error message/debug information would be helpfull.
Always feel free to open a bug report about it with as much information as possible, so it can be tracked down properly.
Thanks Alex - I think I might just do that. I started using the Leap15 KDE applicance, now I have switched to TW, I now have working ethernet, but instead the wifi doesn't show up. Instead, changing date&time with Yast worked fine :-) /Per -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Freitag, 1. März 2019, 13:59:36 CET schrieb Per Jessen:
I have just acquired two of these, one for my son's school project, one for our mediacentre. Using the KDE appliance, it boots up fine, but as soon as I start setting up the wifi, it crashes. Then I tried usig yast to set date&time - crash.
What image did you use? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Axel Braun wrote:
Am Freitag, 1. März 2019, 13:59:36 CET schrieb Per Jessen:
I have just acquired two of these, one for my son's school project, one for our mediacentre. Using the KDE appliance, it boots up fine, but as soon as I start setting up the wifi, it crashes. Then I tried usig yast to set date&time - crash.
What image did you use?
Sorry, I did mean to add that, - http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances... I've just now switched to trying out TW instead. I'll let you know how that goes. I should also mention I'm not using KDE sofar, only the shell. -- Per Jessen, Zürich (8.7°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Freitag, 1. März 2019, 15:02:40 CET schrieb Per Jessen:
Axel Braun wrote:
Am Freitag, 1. März 2019, 13:59:36 CET schrieb Per Jessen:
I have just acquired two of these, one for my son's school project, one for our mediacentre. Using the KDE appliance, it boots up fine, but as soon as I start setting up the wifi, it crashes. Then I tried usig yast to set date&time - crash.
What image did you use?
Sorry, I did mean to add that, -
http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances /openSUSE-Leap15.0-ARM-KDE-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.ra w.xz
I've just now switched to trying out TW instead. I'll let you know how that goes. I should also mention I'm not using KDE sofar, only the shell.
I'm using the LXQT image, runs quite well and did not notice WIFI issues so far. It needs a zypper up before running properly. I think an updated new image is more or less at the doorstep -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Per Jessen wrote:
Axel Braun wrote:
Am Freitag, 1. März 2019, 13:59:36 CET schrieb Per Jessen:
I have just acquired two of these, one for my son's school project, one for our mediacentre. Using the KDE appliance, it boots up fine, but as soon as I start setting up the wifi, it crashes. Then I tried usig yast to set date&time - crash.
What image did you use?
Sorry, I did mean to add that, -
http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances...
I've just now switched to trying out TW instead. I'll let you know how that goes. I should also mention I'm not using KDE sofar, only the shell.
Quick summary - with Leap15 from the image above, I have ethernet and wlan devices, but I cannot activate them. I tried creating a plain user, but YaST crashed, also when attempting to set date&time. Then I switched to Tumbleweed: http://download.opensuse.org/ports/aarch64/tumbleweed/images/openSUSE-Tumble... With that, I have ethernet, but no wifi, not even a wlan device. I see my Logitech trackball recognised in dmesg output, but sddm-greeter is spinning using up 250% CPU. -- Per Jessen, Zürich (8.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Per Jessen wrote:
Quick summary -
with Leap15 from the image above, I have ethernet and wlan devices, but I cannot activate them. I tried creating a plain user, but YaST crashed, also when attempting to set date&time.
Then I switched to Tumbleweed:
http://download.opensuse.org/ports/aarch64/tumbleweed/images/openSUSE-Tumble...
With that, I have ethernet, but no wifi, not even a wlan device. I see my Logitech trackball recognised in dmesg output, but sddm-greeter is spinning using up 250% CPU.
Over the weekend I switched back to Leap15, but using the LQXT image. KDE just seemed a little too "heavy" for the Raspi. LQXT seems quite snappy, and although the ethernet interface still isn't running, I managed to get the wifi up. Last night, I started a "zypper patch" which wanted to update/install some 658 packages. This was a bit of a pain - the wifi interface kept going up and down like a yoyo, sometimes loosing the default route. It also kept changing the MAC address, randomly: Mar 3 21:32:24 dresden dhcpd: DHCPACK on 192.168.7.56 to 0a:13:0b:2c:96:be via eth0 Mar 3 21:37:35 dresden dhcpd: DHCPACK on 192.168.7.56 to 9a:7a:64:00:22:de via eth0 Mar 3 21:42:55 dresden dhcpd: DHCPACK on 192.168.7.56 to fe:e5:18:7f:ca:43 via eth0 Mar 3 21:48:13 dresden dhcpd: DHCPACK on 192.168.7.56 to 0a:dd:4c:96:00:c1 via eth0 Mar 3 21:53:23 dresden dhcpd: DHCPACK on 192.168.7.56 to 22:6d:fd:e2:dd:82 via eth0 Mar 3 21:58:43 dresden dhcpd: DHCPACK on 192.168.7.56 to 82:32:ac:ce:ec:bc via eth0 Mar 3 22:03:57 dresden dhcpd: DHCPACK on 192.168.7.56 to 02:fc:a1:cc:d3:60 via eth0 Mar 3 22:14:28 dresden dhcpd: DHCPACK on 192.168.7.56 to da:ab:ac:bd:a1:4b via eth0 Mar 3 22:19:44 dresden dhcpd: DHCPACK on 192.168.7.56 to 3a:58:9f:d1:0b:15 via eth0 Mar 3 22:25:01 dresden dhcpd: DHCPACK on 192.168.7.56 to 7a:c0:b5:e0:f7:2a via eth0 Mar 3 22:30:16 dresden dhcpd: DHCPACK on 192.168.7.56 to 2e:e0:8c:b7:c5:15 via eth0 Mar 3 22:35:32 dresden dhcpd: DHCPACK on 192.168.7.56 to aa:95:18:c2:e9:03 via eth0 Mar 3 22:40:52 dresden dhcpd: DHCPACK on 192.168.7.56 to 4a:81:74:76:4c:97 via eth0 Mar 3 22:51:20 dresden dhcpd: DHCPACK on 192.168.7.56 to 8e:19:2e:37:40:14 via eth0 Mar 3 22:56:36 dresden dhcpd: DHCPACK on 192.168.7.56 to 7a:d7:4a:e1:79:0d via eth0 Mar 3 23:01:57 dresden dhcpd: DHCPACK on 192.168.7.56 to a2:60:72:98:19:a4 via eth0 Mar 3 23:07:09 dresden dhcpd: DHCPACK on 192.168.7.56 to c2:d9:36:93:ee:85 via eth0 Mar 3 23:12:25 dresden dhcpd: DHCPACK on 192.168.7.56 to 82:ee:e6:b7:d0:90 via eth0 Mar 3 23:20:16 dresden dhcpd: DHCPACK on 192.168.7.56 to 72:28:67:3b:6f:ad via eth0 Mar 3 23:22:58 dresden dhcpd: DHCPACK on 192.168.7.56 to da:41:ef:48:ab:b7 via eth0 Mar 3 23:33:31 dresden dhcpd: DHCPACK on 192.168.7.56 to 1a:94:2d:c0:31:55 via eth0 Mar 3 23:38:45 dresden dhcpd: DHCPACK on 192.168.7.56 to 7a:ed:de:be:a7:10 via eth0 Mar 3 23:49:18 dresden dhcpd: DHCPACK on 192.168.7.56 to 56:61:be:83:df:e0 via eth0 Mar 3 23:54:34 dresden dhcpd: DHCPACK on 192.168.7.56 to 56:ba:50:1b:35:19 via eth0 Mar 3 23:59:49 dresden dhcpd: DHCPACK on 192.168.7.56 to fe:0a:70:5a:a9:56 via eth0 Mar 4 00:05:16 dresden dhcpd: DHCPACK on 192.168.7.56 to 72:84:b1:e1:90:33 via eth0 Mar 4 00:10:21 dresden dhcpd: DHCPACK on 192.168.7.56 to 16:9e:7e:4a:3c:d1 via eth0 Mar 4 00:15:37 dresden dhcpd: DHCPACK on 192.168.7.56 to 72:6d:1d:af:3b:95 via eth0 Mar 4 00:20:54 dresden dhcpd: DHCPACK on 192.168.7.56 to de:73:4f:ee:12:13 via eth0 Mar 4 00:26:10 dresden dhcpd: DHCPACK on 192.168.7.56 to 3a:5b:3f:fb:55:e8 via eth0 Mar 4 00:31:25 dresden dhcpd: DHCPACK on 192.168.7.56 to ee:a6:74:8e:76:fd via eth0 Mar 4 00:36:41 dresden dhcpd: DHCPACK on 192.168.7.56 to 32:52:1a:25:1e:f7 via eth0 Mar 4 00:41:58 dresden dhcpd: DHCPACK on 192.168.7.56 to ee:3c:98:b9:8e:7f via eth0 Mar 4 00:47:13 dresden dhcpd: DHCPACK on 192.168.7.56 to 82:f6:a1:89:e7:8d via eth0 Mar 4 00:52:29 dresden dhcpd: DHCPACK on 192.168.7.56 to 1a:c3:36:6c:63:8b via eth0 This morning after finishing the download, I restarted 'zypper patch', which is almost done now, only 30 packages left :-) -- Per Jessen, Zürich (13.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Per Jessen wrote: [snip]
- the wifi interface kept going up and down like a yoyo, sometimes loosing the default route. It also kept changing the MAC address, randomly:
It looks like this is caused by NetworkManager. I don't understand why it is running though, wicked is in charge? Before I restarted just now, I saw NetworkManager logging messages about "set-hw-addr" ? Currently, after completing the zypper patch, and masking out NetworkManager, both interfaces are running, but I cannot log in to the GUI. I keep being thrown back to the login screen. I think something may well have gone wrong during the zypper patch ? I would like to repeat the exercise with the LXQT image, but I would need to get the ethernet interface to run. 'ifup eth0' takes a while, then reports 'setup-in-progress'. -- Per Jessen, Zürich (13.9°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Per Jessen wrote:
I would like to repeat the exercise with the LXQT image, but I would need to get the ethernet interface to run. 'ifup eth0' takes a while, then reports 'setup-in-progress'.
The following works: Starting with the LXQT image: http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances... After the first boot, I have a machine without network. I stop/disable NetworkManager and I can now make the wifi work. I then upgraded the kernel and rebooted - now I have ethernet and I can complete with a zypper patch. LXDE looks good, it's quite fast and responsive. With KDE, I also had sound working, that one I still have to work on. I think I saw a kernel oops. -- Per Jessen, Zürich (11.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fri, Mar 01, 2019 at 01:59:36PM +0100, Per Jessen wrote:
I have just acquired two of these, one for my son's school project, one for our mediacentre. Using the KDE appliance, it boots up fine, but as soon as I start setting up the wifi, it crashes. Then I tried usig yast to set date&time - crash.
Are they equipped with _appropriate_ power supplies? RPi3 is said to have higher demands than just an ordinary 5V/2.5A plugger. Some shops sell 3.0 amps minimum, others swear by raising Vout to 5.2V. My assumption is those rascals like to demand sudden current bursts, e.g. when certain peripherials kick in or the CPU gets to do some work. For the media centre you might want to look at libreELEC, for a comparison, just to see whether that runs stable. OTOH it's only 32-bits wide :-P https://libreelec.tv/downloads_new/raspberry-pi-3-3/ Torsten -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 01.03.19 um 14:53 schrieb Torsten Duwe:
For the media centre you might want to look at libreELEC, for a comparison, just to see whether that runs stable. OTOH it's only 32-bits wide :-P https://libreelec.tv/downloads_new/raspberry-pi-3-3/
Or just plain raspbian, does multimedia very well out of the box. BTW: what is the benefit of a 64bit system on a 1GB RAM machine? Apart from breaking most of the multimedia stuff and being dog slow compared to raspbian? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Stefan Seyfried wrote:
Am 01.03.19 um 14:53 schrieb Torsten Duwe:
For the media centre you might want to look at libreELEC, for a comparison, just to see whether that runs stable. OTOH it's only 32-bits wide :-P https://libreelec.tv/downloads_new/raspberry-pi-3-3/
Or just plain raspbian, does multimedia very well out of the box.
Okay, I'll check those out too. The key thing is getting it to run MythTV.
BTW: what is the benefit of a 64bit system on a 1GB RAM machine? Apart from breaking most of the multimedia stuff and being dog slow compared to raspbian?
I did think it seemed a bit slow, when compared to running Leap15 on my NanoPis. Is that likely? -- Per Jessen, Zürich (8.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Freitag, 1. März 2019 15:00:13 CET Stefan Seyfried wrote:
Am 01.03.19 um 14:53 schrieb Torsten Duwe:
For the media centre you might want to look at libreELEC, for a comparison, just to see whether that runs stable. OTOH it's only 32-bits wide :-P https://libreelec.tv/downloads_new/raspberry-pi-3-3/
Or just plain raspbian, does multimedia very well out of the box.
BTW: what is the benefit of a 64bit system on a 1GB RAM machine? Apart from breaking most of the multimedia stuff and being dog slow compared to raspbian?
You should know better. 32bit limits the address space to 4 GB. 1 is exclusive to the kernel, leaves 3 to userland. Subtract code and data, and mmapping anything larger than 2 GB fails. Also, building software on 32 bit archs gets quite hard for more and more packages, as the linker runs out of memory. So you end up with less packages. ASLR on 32bit is mostly ineffective, due to the limited address space. Which multimedia stuff breaks due to 32bit? What exactly is slow? Or are you just ranting, like you do all the time? TW runs fine on x86_64 and on several different ARM SoCs. I have some Pine64 here, RPIs, an RK3399 STB. Raspbian would be able to run on one of these ... Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019
Am 01.03.19 um 19:07 schrieb Stefan Brüns:
On Freitag, 1. März 2019 15:00:13 CET Stefan Seyfried wrote:
Am 01.03.19 um 14:53 schrieb Torsten Duwe:
For the media centre you might want to look at libreELEC, for a comparison, just to see whether that runs stable. OTOH it's only 32-bits wide :-P https://libreelec.tv/downloads_new/raspberry-pi-3-3/
Or just plain raspbian, does multimedia very well out of the box.
BTW: what is the benefit of a 64bit system on a 1GB RAM machine? Apart from breaking most of the multimedia stuff and being dog slow compared to raspbian?
You should know better. 32bit limits the address space to 4 GB. 1 is exclusive to the kernel, leaves 3 to userland. Subtract code and data, and mmapping anything larger than 2 GB fails.
Well, yes. Unfortunately I cannot really imagine where this is going to be a real problem on a raspberry pi.
Also, building software on 32 bit archs gets quite hard for more and more packages, as the linker runs out of memory. So you end up with less packages.
This machine has 1GB of RAM, so it will run out of memory anyway. BTW: I cannot complain about raspbians package selection, everything I needed (except vdr-plugin-rpihddevice, which I compiled easily, and which is impossible to build on openSUSE) was just available in the standard repos.
ASLR on 32bit is mostly ineffective, due to the limited address space.
Which multimedia stuff breaks due to 32bit? What exactly is slow? Or are you just ranting, like you do all the time?
All the OMX and mmal is disabled on ARM64 https://github.com/raspberrypi/userland/blob/master/CMakeLists.txt#L11 Try to compile omxplayer, ffmpeg with omx encoder and mmal decoder and vdr-plugin-rpihddevice for example. Slow is "if I just want to use the raspberry pi as a console server with screen and usbserial headless via ssh, then with openSUSE Leap or Tumbleweed, everything lags and feels slow" (and the machine is not really doing anything). Do the exact same thing with raspbian and it is snappy, even if it's live transcoding full-hd video in the background or running as a lazycast receiver (full-HD video decoding via VLC in that case).
TW runs fine on x86_64 and on several different ARM SoCs. I have some Pine64 here, RPIs, an RK3399 STB. Raspbian would be able to run on one of these ...
Yes, that's why I wanted to use openSUSE on the raspis, too, just one system on all boxes. But it was just not usable. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Stefan, Am 01.03.19 um 15:00 schrieb Stefan Seyfried:
BTW: what is the benefit of a 64bit system on a 1GB RAM machine?
We didn't design this hardware. AArch64 is what SUSE supports for SLES. If you prefer to run 32-bit openSUSE on 64-bit hardware, you are free to do that as well. There is no openQA for armv7hl or armv6hl though, and build hardware for AArch32 is slowly getting sparse.
Apart from breaking most of the multimedia stuff and being dog slow compared to raspbian?
Don't compare apples to oranges: The Raspberry Pi guys did not upstream their cpufreq driver, so if you compare mainline 32-bit to 64-bit the observed difference should be fairly negligible. There was also a discussion on the opensuse-kernel list about our preemption config that can influence _perceived_ performance. But as I've told you before: If you prefer other Linux distros, please stop trolling on our opensuse-arm mailing list. Otherwise mind your tone and feel free to contribute to making mainline Linux & openSUSE better. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Torsten Duwe wrote:
On Fri, Mar 01, 2019 at 01:59:36PM +0100, Per Jessen wrote:
I have just acquired two of these, one for my son's school project, one for our mediacentre. Using the KDE appliance, it boots up fine, but as soon as I start setting up the wifi, it crashes. Then I tried usig yast to set date&time - crash.
Are they equipped with _appropriate_ power supplies? RPi3 is said to have higher demands than just an ordinary 5V/2.5A plugger.
Ah, I was not aware. Well, the power supply says 5V/3400mA, it has multiple usb sockets at max 2400/socket, Looking at the power supply supplied by e.g. Conrad, they are also 2500mA.
Some shops sell 3.0 amps minimum, others swear by raising Vout to 5.2V. My assumption is those rascals like to demand sudden current bursts, e.g. when certain peripherials kick in or the CPU gets to do some work.
That is possible, but sofar I'm still installing :-) Also, when I tried with TW a little later, it worked fairly well, at least it didn't crash.
For the media centre you might want to look at libreELEC, for a comparison, just to see whether that runs stable. OTOH it's only 32-bits wide :-P https://libreelec.tv/downloads_new/raspberry-pi-3-3/
Thanks, I'll check it out. -- Per Jessen, Zürich (6.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (7)
-
Alexander Bergmann -
Andreas Färber -
Axel Braun -
Per Jessen -
Stefan Brüns -
Stefan Seyfried -
Torsten Duwe