dukla2000
Posts: 188
Joined: Tue Jan 10, 2012 12:02 am
Location: Reading.UK.EU

aarch64 on Pi3

Sat Sep 10, 2016 10:48 pm

Hi there

I am having problems getting openSuSE to boot.

The openSUSE-Tumbleweed-ARM-XFCE-raspberrypi3_aarch64.aarch64-2016.09.06-Build9.2.raw.xz image runs through some promising screen messages, gets to
Starting Switch Root
then dies (no more activity, HDMI signal lost).

The openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.09.06-Build7.1.raw.xz when expanded to an SDcard creates an empty DOS partitiion that unsurpringly wont boot. If I copy the contents of ROOT/boot/vc to the DOS partition it boots as far as a GRUB prompt, presumably more is needed in the DOS partition.

Any hints how to get this to boot, preferably I guess the XFCE version, are welcome.

TIA
Daily driver: Pi3B, 64GB Samsung Evo+ @100MHz, DVB-T, onboard WiFi for internet, BT/USB dongle for KB/mouse, 250GB HDD via USB for media, Raspbian Jessie Lite with Openbox desktop.
Museum: Pi B

dukla2000
Posts: 188
Joined: Tue Jan 10, 2012 12:02 am
Location: Reading.UK.EU

Re: aarch64 on Pi3

Sun Sep 11, 2016 12:44 pm

My mistake. Given enough time (several minutes) the XFCE version eventually loads.

Busy playing: I have it on a relatively slow sdcard at the moment.

ps - OK, been playing with openSUSE aarch64 for the past 36 hours and in general it works quite well. However there are too many quirks for me to continue to use it at present (which is a shame as I have been using SUSE on my desktop since 2003!) The delay in initial boot is (on my sdcard, YMMV!) 8 mins with screen off, about 10 minutes in total. So be patient!

Dealbreaker – no omxplayer in any of the repositories. The default videoplayer doesnt't seem to work at all.

Quirks (irritating but probably surmountable given a bit more effort!)
  • There appears to be a 30 second pause in both the shutdown and startup routines which is irksome
    I could find no way to monitor temp and CPU speed or work out which scheduler was in use. The /sys/devices/system/cpu/... and /sys/class/thermal/... trees are not created.
    Config.txt is confusing – the one in the DOS partition does not seem to be used for all parameters. Certainly /boot/vc/config.txt is used for screen/HDMI settings. I didn't bottom out where to put settings like (or if they even work)
    • dtparam=sd_overclock=100
      decode_MPG2=0x...
      dtoverlay=pi3-disable-bt
    No vcgencmd
    Certainly gpu_mem=64 is ignored even when in both config.txt – somewhere there appears to be a hardcoded 256MB setting.
    Similarly there is a hardcoded kernel start line setting to try recover from a hibernation file. Frustratingly the normal way of sorting this in YaST (/etc/sysconfig editor) made no difference (i.e. was ignored).
    Similarly irritating (compared to Raspbian) is that having placed HDMI settings that work for my screen in /boot/vc/config.txt, X starts with no relevant parms passed to it and promptly interrogates my (duff) EDID and settles on sub-optimum settings!
    Neither onboard WiFi nor bluetooth activated – no biggie for me as even with Rasbian I use a BT dongle.
    Both Firefox and Midori cause coredumps. Epiphany worked fine for me though.
    BT power is off after a reboot. Once on though the BT stack seems more robust than Raspbian (keyboard/mouse staying connected)
Daily driver: Pi3B, 64GB Samsung Evo+ @100MHz, DVB-T, onboard WiFi for internet, BT/USB dongle for KB/mouse, 250GB HDD via USB for media, Raspbian Jessie Lite with Openbox desktop.
Museum: Pi B

User avatar
pi-anazazi
Posts: 414
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: aarch64 on Pi3

Tue Sep 13, 2016 5:48 am

Did you install the packman repository (necessary for all kinds of multimedia in opensuse)? (in Yast -> Repositories -> Add -> Communitiy repositories)

I read somewhere about omxplayer, iirc :-)

Have here one opensuse running, but don't need multimedia on this, can burn a new card to try If you need a helping hand ;-)
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 414
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: aarch64 on Pi3

Tue Sep 13, 2016 5:55 am

PS: Why don't you try the image from this directory?

http://download.opensuse.org/repositori ... i2/images/
Kind regards

anazazi

dukla2000
Posts: 188
Joined: Tue Jan 10, 2012 12:02 am
Location: Reading.UK.EU

Re: aarch64 on Pi3

Wed Sep 14, 2016 9:34 pm

pi-anazazi wrote:Did you install the packman repository (necessary for all kinds of multimedia in opensuse)? (in Yast -> Repositories -> Add -> Communitiy repositories)

I read somewhere about omxplayer, iirc :-)

Have here one opensuse running, but don't need multimedia on this, can burn a new card to try If you need a helping hand ;-)
Yup I added Packman, but the aarch64 library is pretty thin. No lame, xine, omxplayer.... Suspect links2linux may not have an aarch64 box in their farm yet.

The link in your second post is the armv7 stuff, not aarch64. Figure I am dumb enough to try the aarch64 option for bragging rights - for armv7 may as well stick to Raspbian.
Daily driver: Pi3B, 64GB Samsung Evo+ @100MHz, DVB-T, onboard WiFi for internet, BT/USB dongle for KB/mouse, 250GB HDD via USB for media, Raspbian Jessie Lite with Openbox desktop.
Museum: Pi B

User avatar
pi-anazazi
Posts: 414
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: aarch64 on Pi3

Thu Sep 15, 2016 7:03 am

I tried the aarch64, but didn't get ANYthing up or running at first, the 2016.09.11. built boots, but picks totally wrong video mode for my monitor, so no GUI. Via serial console I can login, do updates etc, but not much more.

Would be fun to have the raspi 3 stable with opensuse. Have a raspi 2B with opensuse, running headless with VNC, but not stable enough yet for use in a NAS, I guess. Wait'n see... ;-)
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 414
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: aarch64 on Pi3

Thu Sep 15, 2016 9:36 am

Update:

Boot takes not much longer than with raspian here. No idea what's the problem ;-)

Have a second user now on the XFCE image, although it refused to make the users directory in /home...

Installed tigervnc, get a connection, but very shaky at that time.

In the serial console I see a lot of

Code: Select all

i2c-bcm2835 3f805000.i2c: i2c transfer failed: 100
...could not find anything meaningful on this yet.

tbc :-D
Kind regards

anazazi

dukla2000
Posts: 188
Joined: Tue Jan 10, 2012 12:02 am
Location: Reading.UK.EU

Re: aarch64 on Pi3

Thu Sep 15, 2016 9:54 am

Yup, also had the i2c fail messages clocking regularly (in dmesg).

The first image I played with I created a user and then had password problems trying to log in (also mentioned elsewhere). The second time I tried with a fresh image (and waited the full 10 odd minutes for Yast first boot to complete properly) I
- created a new user (via Yast)
- went straight back in Yast and reset the password
- the user then worked fine with a directory tree (documents, download, bin etc) created in /home
Daily driver: Pi3B, 64GB Samsung Evo+ @100MHz, DVB-T, onboard WiFi for internet, BT/USB dongle for KB/mouse, 250GB HDD via USB for media, Raspbian Jessie Lite with Openbox desktop.
Museum: Pi B

User avatar
pi-anazazi
Posts: 414
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: aarch64 on Pi3

Thu Sep 15, 2016 10:19 am

On the first boot the file system get's re-sized to use the whole card, afaik, therefore it takes some time for the first boot.

Would love to see the HDMI come up, but I get in the display

"HDMI out of range 35.7 kHz / 32 Hz"

and in the console

Code: Select all

DRAM:  880 MiB                                                      
RPI 3 Model B (0xa02082)                                            
MMC:   bcm2835_sdhci: 0                                             
reading uboot.env                                                   

** Unable to read "uboot.env" from mmc0:1 **                        
Using default environment                                           

In:    serial                                                       
Out:   lcd                                                          
Err:   lcd                                                          
Net:   Net Initialization Skipped                                   
No ethernet found.                                                  
starting USB...                                                     
USB0:   Core Release: 2.80a                                         
scanning bus 0 for devices... 3 USB Device(s) found                 
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 1 Ethernet Device(s) fou
nd                                                                  
Hit any key to stop autoboot:  0                                    
switch to partitions #0, OK                                         
mmc0 is current device                                              
Scanning mmc 0:1...                                                 
7192 bytes read in 80 ms (86.9 KiB/s)                               
Found EFI removable media binary efi/boot/bootaa64.efi              
reading efi/boot/bootaa64.efi                                       
128000 bytes read in 33 ms (3.7 MiB/s)                              
## Starting EFI application at 0x01000000 ...                       
Scanning disks on usb...                                            
Scanning disks on mmc...                                            
MMC Device 1 not found
MMC Device 2 not found
MMC Device 3 not found
Found 5 disks
Welcome to GRUB!

Please press t to show the boot menu on this console
EFI stub: Booting Linux Kernel...
EFI stub: UEFI Secure Boot is enabled.
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map..
.
[    2.100501] kvm [1]: error: KVM vGIC probing failed
[    2.100545] kvm [1]: error initializing Hyp mode: -19
[    2.154515] bcm2835-aux-uart 3f215040.serial: could not get clk: 
-517
[    9.679284] bcm2835-clk 3f101000.cprman: pllh: rate out of spec: 
4155000000 vs (600000000, 3000000000)

Welcome to openSUSE Tumbleweed 20160913 - Kernel 4.4.19-7-default (ttyS0).
Dunno how to force the kernel to use an adequate monitor profile...
Kind regards

anazazi

dukla2000
Posts: 188
Joined: Tue Jan 10, 2012 12:02 am
Location: Reading.UK.EU

Re: aarch64 on Pi3

Thu Sep 15, 2016 8:37 pm

If you set "the usual" parameters in /boot/vc/config.txt (NOT the config.txt in the DOS partition which is also mounted as /boot/efi !) you will see decent screen stuff during boot. e.g. I have

Code: Select all

# Display settings
hdmi_group=2
hdmi_mode=82
# Add sound over HDMI when group=2, except blows display as per group=1!
# hdmi_drive=2
hdmi_ignore_edid=0xa5000080
framebuffer_depth=32
framebuffer_ignore_alpha=1
hdmi_pixel_encoding=2
and get 1920*1080

Code: Select all

chris@dukla:~> dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.19-7-default (geeko@buildhost) (gcc version 6.1.1 20160815 [gcc-6-branch revision 239479] (SUSE Linux) ) #1 SMP Fri Aug 26 12:54:34 UTC 2016 (a3a3ea6)
[    0.000000] Boot CPU: AArch64 Processor [410fd034]
...
[    2.144584] efifb: probing for efifb
[    2.144728] efifb: framebuffer at 0x3d402000, mapped to 0xffff000000300000, using 8100k, total 8100k
[    2.144733] efifb: mode is 1920x1080x32, linelength=7680, pages=1
[    2.144736] efifb: scrolling: redraw
[    2.144742] efifb: Truecolor: size=8:8:8:8, shift=24:0:8:16
[    2.173260] Console: switching to colour frame buffer device 240x67
[    2.201135] fb0: EFI VGA frame buffer device
which is what I expect.

However in /var/log/Xorg.0.log I get 1024*768

Code: Select all

[    64.873] X Protocol Version 11, Revision 0
[    64.874] Build Operating System: openSUSE SUSE LINUX
[    64.874] Current Operating System: Linux dukla 4.4.19-7-default #1 SMP Fri Aug 26 12:54:34 UTC 2016 (a3a3ea6) aarch64
[    64.874] Kernel command line: BOOT_IMAGE=/boot/Image-4.4.19-7-default root=UUID=ae73dae6-cb17-4cb4-b5d3-120122b1640c root=/dev/disk/by-id/mmc-SA64G_0x258c0706-part2 disk=/dev/disk/by-id/mmc-SA64G_0x258c0706 resume=/dev/disk/by-id/mmc-SA64G_0x258c0706-part3 quiet splash=silent plymouth.enable=0 console=ttyS0,115200n8 console=tty
[    64.874] Build Date: 27 July 2016  05:15:26PM
[    64.874]  
...
[    65.298] (II) modeset(0): Output HDMI-1 connected
[    65.298] (II) modeset(0): Using exact sizes for initial modes
[    65.298] (II) modeset(0): Output HDMI-1 using initial mode 1024x768 +0+0
[    65.299] (II) modeset(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[    65.299] (==) modeset(0): DPI set to (96, 96)
Actually suspect this may be an artefact of using Eric Anholt's opensource driver - need to work out how to get X to use sensible parameters.

{This post BTW is from aarch64 using epiphany}

Code: Select all

chris@dukla:~> uname -a
Linux dukla 4.4.19-7-default #1 SMP Fri Aug 26 12:54:34 UTC 2016 (a3a3ea6) aarch64 aarch64 aarch64 GNU/Linux
Daily driver: Pi3B, 64GB Samsung Evo+ @100MHz, DVB-T, onboard WiFi for internet, BT/USB dongle for KB/mouse, 250GB HDD via USB for media, Raspbian Jessie Lite with Openbox desktop.
Museum: Pi B

User avatar
pi-anazazi
Posts: 414
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: aarch64 on Pi3

Fri Sep 16, 2016 5:46 am

....yesss, I edited the WRONG config.txt! ;-) Will give it a try later!

Hope that the system becomes stable with these modifications.

PS:

Dunno what I'm doing wrong here, added to /boot/vc/config.txt

Code: Select all

#display
hdmi_group=2
hdmi_mode=82
hdmi_ignore_edid=0xa5000080
framebuffer_depth=32
framebuffer_ignore_alpha=1
hdmi_pixel_encoding=2
...but I get:

Code: Select all

# dmesg                                                                              
[    0.000000] Booting Linux on physical CPU 0x0                                                  
[    0.000000] Initializing cgroup subsys cpuset                                                  
[    0.000000] Initializing cgroup subsys cpu                                                     
[    0.000000] Initializing cgroup subsys cpuacct                                                 
[    0.000000] Linux version 4.4.19-7-default (geeko@buildhost) (gcc version 6.1.1 20160815 [gcc-6
-branch revision 239479] (SUSE Linux) ) #1 SMP Fri Aug 26 12:54:34 UTC 2016 (a3a3ea6)             
[    0.000000] Boot CPU: AArch64 Processor [410fd034]                                             
[    0.000000] Getting EFI parameters from FDT:                                                   
[    0.000000] EFI v2.05 by Das U-boot   
......
[    2.090204] efifb: probing for efifb                                                           
[    2.090323] efifb: framebuffer at 0x3d513000, mapped to 0xffff000000300000, using 7012k, total 
7011k                                                                                             
[    2.090328] efifb: mode is 1824x984x32, linelength=7296, pages=1                               
[    2.090332] efifb: scrolling: redraw                                                           
[    2.090338] efifb: Truecolor: size=8:8:8:8, shift=24:0:8:16                                    
[    2.113484] Console: switching to colour frame buffer device 228x61                            
[    2.135959] fb0: EFI VGA frame buffer device 
....
Which is total nonsense.
Kind regards

anazazi

dukla2000
Posts: 188
Joined: Tue Jan 10, 2012 12:02 am
Location: Reading.UK.EU

Re: aarch64 on Pi3

Fri Sep 16, 2016 11:37 am

pi-anazazi wrote:Dunno what I'm doing wrong here, added to /boot/vc/config.txt ...
A couple of things:
- The group=2/mode=82 I use is 1080p @ 60Hz which works for my cheapo monitor. You need to work a setup that works for your monitor from here

- I did a YaST/update all packages last night and the latest version stuff DOES NOW USE the config.txt in the DOS partition!

- I discovered a major delay during boot was wicked - swapping to Network Manager (via YaST) saves about 25 secs during boot.

- think 1 of the 'limitations' of this release at present is the device tree. Seems to be pretty hardcoded in a couple of places to use bcm2710-rpi-3-b.dtb (which curiously enough I can't find in the tree!) rather than /boot/dtb/bcm2837-rpi-3-b.dtb (which is there!). Highly likely the reason the sdhci driver is running in PIO mode, probably the cause of the i2c log messages and at a guess sound isn't working - haven't tried it.

- I did try adding

Code: Select all

bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbdepth=32 bcm2708_fb.fbswap=1
to the boot command line (a shameless crib from my Raspbian log). It did go in but still the screen reverts to 1024*768

Code: Select all

[    0.000000] Kernel command line: BOOT_IMAGE=/boot/Image-4.4.19-7-default root=UUID=ae73dae6-cb17-4cb4-b5d3-120122b1640c root=/dev/disk/by-id/mmc-SA64G_0x258c0706-part2 disk=/dev/disk/by-id/mmc-SA64G_0x258c0706 quiet splash=silent plymouth.enable=0 console=ttyS0,115200n8 console=tty bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbdepth=32 bcm2708_fb.fbswap=1
...
[    2.162318] efifb: probing for efifb
[    2.162458] efifb: framebuffer at 0x3d402000, mapped to 0xffff000000300000, using 8100k, total 8100k
[    2.162464] efifb: mode is 1920x1080x32, linelength=7680, pages=1
[    2.162468] efifb: scrolling: redraw
[    2.162473] efifb: Truecolor: size=8:8:8:8, shift=24:0:8:16
[    2.190200] Console: switching to colour frame buffer device 240x67
[    2.217194] fb0: EFI VGA frame buffer device
...
[   15.658258] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
[   15.658544] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
[   15.658770] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
[   15.658969] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
[   15.659085] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
[   15.659247] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
[   15.659266] checking generic (3d402000 7e9000) vs hw (0 ffffffffffffffff)
[   15.659275] fb: switching to vc4drmfb from EFI VGA
[   15.659573] Console: switching to colour dummy device 80x25
[   15.661397] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   15.661413] [drm] No driver support for vblank timestamp query.
[   15.662270] vc4-drm soc:gpu: No connectors reported connected with modes
[   15.662284] [drm] Cannot find any crtc or sizes - going 1024x768
[   15.692024] Console: switching to colour frame buffer device 128x48
[   15.711205] vc4-drm soc:gpu: fb0:  frame buffer device
Daily driver: Pi3B, 64GB Samsung Evo+ @100MHz, DVB-T, onboard WiFi for internet, BT/USB dongle for KB/mouse, 250GB HDD via USB for media, Raspbian Jessie Lite with Openbox desktop.
Museum: Pi B

User avatar
pi-anazazi
Posts: 414
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: aarch64 on Pi3

Sat Sep 17, 2016 9:38 am

sorry for late reply my computer tricked me with the disk labels and so I dd'ed the raspi Tumbleweed image over my workstations root partition :twisted:

Back with a fresh system now :-D

Tried the latest

Code: Select all

openSUSE-Tumbleweed-ARM-XFCE-raspberrypi3_aarch64.aarch64-2016.09.11-__not__set-Build8.2.raw.xz
, but gave the same error with graphics on first boot, subsequently I manipulated BOTH (!)! config.txt files as outlined above, my monitor should be doing fine with 1080p.

Same nonsense in dmesg with this weird graphic mode, so no GUI yet and VNC very unstable, collapsing every second with segmentation faults...

tbc :-)
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 414
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: aarch64 on Pi3

Sat Sep 17, 2016 9:57 am

Tried with another monitor and HDMI to DVI cable, no GUI, in the serial console I get the login, dmesg

Code: Select all

sudo dmesg                                                                   
[sudo] password for root:                                                                         
[    0.000000] Booting Linux on physical CPU 0x0                                                  
[    0.000000] Initializing cgroup subsys cpuset                                                  
[    0.000000] Initializing cgroup subsys cpu                                                     
[    0.000000] Initializing cgroup subsys cpuacct                                                 
[    0.000000] Linux version 4.4.19-7-default (geeko@buildhost) (gcc version 6.1.1 20160815 [gcc-6
-branch revision 239479] (SUSE Linux) ) #1 SMP Fri Aug 26 12:54:34 UTC 2016 (a3a3ea6)             
[    0.000000] Boot CPU: AArch64 Processor [410fd034]                                             
[    0.000000] Getting EFI parameters from FDT:                                                   
[    0.000000] EFI v2.05 by Das U-boot                                                            
[    0.000000] efi: efi:  SMBIOS=0x35b14000 efi:                                                  
[    0.000000] No NUMA configuration found           
....
....
....
[    2.116405] efifb: probing for efifb                                                           
[    2.116534] efifb: framebuffer at 0x3d4a7000, mapped to 0xffff000000300000, using 7500k, total 
7500k                                                                                             
[    2.116540] efifb: mode is 1600x1200x32, linelength=6400, pages=1                              
[    2.116543] efifb: scrolling: redraw                                                           
[    2.116550] efifb: Truecolor: size=8:8:8:8, shift=24:0:8:16                                    
[    2.142130] Console: switching to colour frame buffer device 200x75                            
[    2.167113] fb0: EFI VGA frame buffer device                    
1600x1200 is OK, but....
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 414
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: aarch64 on Pi3

Mon Sep 19, 2016 6:26 am

Does anybody have a clue where to find the Github etc repos for these aarch64 development, or commits, bugs? would love to learn more on the opensuse pi projects for ARM 7 and 8... :-)
Kind regards

anazazi

User avatar
pi-anazazi
Posts: 414
Joined: Fri Feb 13, 2015 9:22 pm
Location: EU

Re: aarch64 on Pi3

Wed Sep 28, 2016 12:24 pm

Hihi, snapshot with XFCE is doing fine

http://download.opensuse.org/repositori ... i3/images/

...detects no useful display setting, but via ssh installed TigerVNC and it's stable up to now, did some initial installation/configuration.

Nice! :-)
Kind regards

anazazi

Return to “openSUSE”

Who is online

Users browsing this forum: No registered users and 1 guest