I purchased a RaspBerry Pi 3B, downloaded the image for TW and after I
select to boot the image The boot starts and then hangs forever. It does
not matter which image I try they all lockup at boot.
Any help appreciated.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
You get the ARM version???
You might be better off in the mailing list: opensuse-arm@opensuse.org, I don’t see many ARM device users here, and I know there were a couple of threads in the ML in the RPi3
See https://lists.opensuse.org/opensuse-arm/
I just purchased a RPi Zero, and reviewed just about everything I can find about openSUSE and the RPi family.
Make sure you’re installing the images from this page, and following the install instructions (for the RPi 3, this is <not> the correct image for any other RPi)
https://en.opensuse.org/HCL:Raspberry_Pi3
If it’s still hanging (I’d be surprised),
Then you’ll need to try to boot to a console, if the TW image doesn’t work then mount in a chroot (Instructions are somewhere in the ARM documentation, if you can’t find it then post here again) and inspect the bootlog entries for that boot, the following displays the last boot
journalctl -b -1
TSU
On 09/20/2016 04:36 PM, Knurpht wrote:
>
> kensch;2793295 Wrote:
>> I purchased a RaspBerry Pi 3B, downloaded the image for TW and after I
>> select to boot the image The boot starts and then hangs forever. It does
>> not matter which image I try they all lockup at boot.
>> Any help appreciated.
>>
>> –
>> Ken
>> linux since 1994
>> S.u.S.E./openSUSE since 1996
>
> You might be better off in the mailing list: opensuse-arm@opensuse.org,
> I don’t see many ARM device users here, and I know there were a couple
> of threads in the ML in the RPi3
> See https://lists.opensuse.org/opensuse-arm/
>
>
For gogalthorp: Yes it was the ARM version as that’s all that is
available under the Pi version.
I’ll look in the opensuse-arm list for clues or add myself to the list
and post my problem there.
Thanks for the info.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
On 09/21/2016 10:06 AM, tsu2 wrote:
>
> I just purchased a RPi Zero, and reviewed just about everything I can
> find about openSUSE and the RPi family.
>
> Make sure you’re installing the images from this page, and following the
> install instructions (for the RPi 3, this is <not> the correct image for
> any other RPi)
> https://en.opensuse.org/HCL:Raspberry_Pi3
>
> If it’s still hanging (I’d be surprised),
> Then you’ll need to try to boot to a console, if the TW image doesn’t
> work then mount in a chroot (Instructions are somewhere in the ARM
> documentation, if you can’t find it then post here again) and inspect
> the bootlog entries for that boot, the following displays the last boot
>
> Code:
> --------------------
> journalctl -b -1
> --------------------
>
>
> TSU
>
>
Thank you TSU. I’m archiving this post for future use.
The RPi I currently have is doing it’s thing under Raspian, running as a
print server for the Apple devices in the network providing AirPrint
connection to non AirPrint printers. It was actually an easier setup
then with openSUSE. I think I’ll buy another Pi to test openSUSE TW with.
By the way, people are impressed with how small the “computer” is. 
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
Do yourself a favor and buy a Raspi 2b if you don’t need wifi.
I didn’t get ANY TW on a raspi 3 running stable and recognize a monitor yet. Raspian and Kali doing very fine on this machine!
https://en.opensuse.org/HCL:Raspberry_Pi3#Tips_for_openSUSE_Tumbleweed_.28upstream.29
PS: a black screen doesn’t mean your system is up!
Try to ssh into the raspi 3 with “root” and “linux”, wouldn’t be surprised if it works.
On 09/21/2016 11:06 AM, suse rasputin wrote:
>
> Do yourself a favor and buy a Raspi 2b if you don’t need wifi.
>
In this case wifi is needed.
So far it’s running well under raspian. I have no plans to do anything
further with this setup unless it stops working. (If it ain’t broke
don’t fix it).
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
Ok, I meant if you buy one for playing around, 2B might be the better option, currently (you can add wifi with a small USB-stcik any time).
There was a “not” missing in me last post, black screen -> can mean functional system, but no screen detected (ssh will work). I tried some tweaks to get the monitor recognized at a raspi 3, to no avail. Raspi 2 is the best choice in my opinion, enough performance not to fall asleep with every command and stable TW available yet.
Have fun!
On 09/22/2016 11:16 AM, suse rasputin wrote:
>
> Ok, I meant if you buy one for playing around, 2B might be the better
> option, currently (you can add wifi with a small USB-stcik any time).
>
> There was a “not” missing in me last post, black screen -> can mean
> functional system, but no screen detected (ssh will work). I tried some
> tweaks to get the monitor recognized at a raspi 3, to no avail. Raspi 2
> is the best choice in my opinion, enough performance not to fall asleep
> with every command and stable TW available yet.
>
> Have fun!
>
>
Thanks for the information. In my case when booting I could select the
default boot entry and hit enter, but at that point the screen would go
black and even with waiting a few minutes I could not ssh to the Pi3B.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
Hi again!
I REALLY don’T get why this is soooo different for different users! I read some posts that one guy could boot his raspi 3 normally and got a GUI. I tried about 10 different images last week, (and 2 different monitors), after the stub never saw a graphics output leading to a GUI.
Even the tip and image proposed here
https://lists.opensuse.org/opensuse-arm/2016-09/msg00068.html
don’t lead me anywhere.
Even adding code to config.txt (in boot/cv) to give the correct video mode (1080p) results in no GUI, and I see
# 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
0.000000] efi: efi: SMBIOS=0x35b10000 efi:
0.000000] No NUMA configuration found
0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x0000000036ffffff]
0.000000] NUMA: Adding memblock [0x0 - 0xfff] on node 0
0.000000] NUMA: Adding memblock [0x1000 - 0x2611bfff] on node 0
0.000000] NUMA: Adding memblock [0x2611c000 - 0x2611cfff] on node 0
0.000000] NUMA: Adding memblock [0x2611d000 - 0x35b0ffff] on node 0
0.000000] NUMA: Adding memblock [0x35b10000 - 0x35b10fff] on node 0
0.000000] NUMA: Adding memblock [0x35b11000 - 0x36f86fff] on node 0
0.000000] NUMA: Adding memblock [0x36f87000 - 0x36f87fff] on node 0
0.000000] NUMA: Adding memblock [0x36f88000 - 0x36ffffff] on node 0
0.000000] NUMA: Initmem setup node 0 [mem 0x00000000-0x36ffffff]
0.000000] NUMA: NODE_DATA [mem 0x36fea980-0x36fec6ff]
0.000000] Zone ranges:
0.000000] DMA [mem 0x0000000000000000-0x0000000036ffffff]
0.000000] Normal empty
0.000000] Movable zone start for each node
0.000000] Early memory node ranges
0.000000] node 0: [mem 0x0000000000000000-0x0000000000000fff]
0.000000] node 0: [mem 0x0000000000001000-0x000000002611bfff]
0.000000] node 0: [mem 0x000000002611c000-0x000000002611cfff]
0.000000] node 0: [mem 0x000000002611d000-0x0000000035b0ffff]
0.000000] node 0: [mem 0x0000000035b10000-0x0000000035b10fff]
0.000000] node 0: [mem 0x0000000035b11000-0x0000000036f86fff]
0.000000] node 0: [mem 0x0000000036f87000-0x0000000036f87fff]
0.000000] node 0: [mem 0x0000000036f88000-0x0000000036ffffff]
0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000036ffffff]
0.000000] On node 0 totalpages: 225280
0.000000] DMA zone: 3520 pages used for memmap
0.000000] DMA zone: 0 pages reserved
0.000000] DMA zone: 225280 pages, LIFO batch:31
0.000000] PERCPU: Embedded 17 pages/cpu @ffff800036f9b000 s30616 r8192 d30824 u69632
0.000000] pcpu-alloc: s30616 r8192 d30824 u69632 alloc=17*4096
0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
0.000000] Detected VIPT I-cache on CPU0
0.000000] CPU features: enabling workaround for ARM erratum 845719
0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 221760
0.000000] Policy zone: DMA
0.000000] Kernel command line: BOOT_IMAGE=/boot/Image-4.4.19-7-default root=UUID=48e606c6-69e8-497e-b89e-f61ca0a2f4d0 root=/dev/disk/by-id/mmc-SL16G_0x681c34c2-part2 disk=/dev/disk/by-id/mmc-SL16G_0x681c34c2 resume=/dev/disk/by-id/mmc-SL16G_0x681c34c2-part3 quiet splash=silent plymouth.enable=0 console=ttyS0,115200n8 console=tty
0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
0.000000] software IO TLB [mem 0x31b10000-0x35b10000] (64MB) mapped at [ffff800031b10000-ffff800035b0ffff]
0.000000] Memory: 796524K/901120K available (7012K kernel code, 1051K rwdata, 5180K rodata, 908K init, 1081K bss, 104596K reserved, 0K cma-reserved)
0.000000] Virtual kernel memory layout:
vmalloc : 0xffff000000000000 - 0xffff7bffbfff0000 (126974 GB)
vmemmap : 0xffff7bffc0000000 - 0xffff7fffc0000000 ( 4096 GB maximum)
0xffff7bffc0000000 - 0xffff7bffc0dc0000 ( 13 MB actual)
fixed : 0xffff7ffffa7fd000 - 0xffff7ffffac00000 ( 4108 KB)
PCI I/O : 0xffff7ffffae00000 - 0xffff7ffffbe00000 ( 16 MB)
modules : 0xffff7ffffc000000 - 0xffff800000000000 ( 64 MB)
memory : 0xffff800000000000 - 0xffff800037000000 ( 880 MB)
.init : 0xffff800000c6a000 - 0xffff800000d4d000 ( 908 KB)
.text : 0xffff800000080000 - 0xffff800000c6a000 ( 12200 KB)
.data : 0xffff800000d4d000 - 0xffff800000e53e00 ( 1052 KB)
....
0.040887] Brought up 4 CPUs
0.040905] SMP: Total of 4 processors activated.
0.040914] CPU: All CPU(s) started at EL2
0.040931] alternatives: patching kernel code
0.041479] devtmpfs: initialized
0.045481] SMBIOS 3.0 present.
0.045495] DMI: raspberrypi rpi/rpi, BIOS 2016.07 09/19/2016
0.045716] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
0.046010] pinctrl core: initialized pinctrl subsystem
0.046856] NET: Registered protocol family 16
0.077642] cpuidle: using governor ladder
0.107650] cpuidle: using governor menu
0.107715] fsl-mc bus type registered
0.107764] MC object device driver fsl_mc_dprc registered
0.107789] MC object device driver fsl_mc_allocator registered
0.107919] vdso: 2 pages (1 code @ ffff800000d55000, 1 data @ ffff800000d54000)
0.107945] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
0.108231] DMA: preallocated 256 KiB pool for atomic allocations
0.108334] Serial: AMBA PL011 UART driver
0.148873] ACPI: Interpreter disabled.
0.149204] vgaarb: loaded
0.149491] SCSI subsystem initialized
0.149598] libata version 3.00 loaded.
0.150553] NetLabel: Initializing
0.150557] NetLabel: domain hash size = 128
0.150560] NetLabel: protocols = UNLABELED CIPSOv4
0.150605] NetLabel: unlabeled traffic allowed by default
0.150802] clocksource: Switched to clocksource arch_sys_counter
0.181133] AppArmor: AppArmor Filesystem Enabled
0.181354] pnp: PnP ACPI: disabled
0.188957] NET: Registered protocol family 2
0.189478] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
0.189572] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
0.189701] TCP: Hash tables configured (established 8192 bind 8192)
0.189857] UDP hash table entries: 512 (order: 2, 16384 bytes)
0.189887] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
0.190087] NET: Registered protocol family 1
0.190122] PCI: CLS 0 bytes, default 128
0.190368] Unpacking initramfs...
2.108759] Freeing initrd memory: 6536K (ffff800027012000 - ffff800027674000)
2.109208] kvm [1]: error: KVM vGIC probing failed
2.109249] kvm [1]: error initializing Hyp mode: -19
2.110222] futex hash table entries: 1024 (order: 5, 131072 bytes)
2.110349] audit: initializing netlink subsys (disabled)
2.110423] audit: type=2000 audit(2.079:1): initialized
2.111198] HugeTLB registered 2 MB page size, pre-allocated 0 pages
2.111318] zbud: loaded
2.111712] VFS: Disk quotas dquot_6.6.0
2.111759] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
2.113796] Key type asymmetric registered
2.113809] Asymmetric key parser 'x509' registered
2.113890] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
2.113983] io scheduler noop registered
2.113992] io scheduler deadline registered
2.114016] io scheduler cfq registered (default)
2.115349] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
2.115383] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
2.115834] efifb: probing for efifb
2.115949] efifb: framebuffer at 0x3d513000, mapped to 0xffff000000300000, using 7012k, total 7011k
2.115955] efifb: mode is 1824x984x32, linelength=7296, pages=1
2.115958] efifb: scrolling: redraw
2.115964] efifb: Truecolor: size=8:8:8:8, shift=24:0:8:16
2.139133] Console: switching to colour frame buffer device 228x61
2.161624] fb0: EFI VGA frame buffer device
2.162240] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
2.163231] bcm2835-aux-uart 3f215040.serial: could not get clk: -517
2.163468] Serial: AMBA driver
2.163955] Unable to detect cache hierarchy from DT for CPU 0
2.164387] mousedev: PS/2 mouse device common for all mice
2.165552] ledtrig-cpu: registered to indicate activity on CPUs
2.165647] EFI Variables Facility v0.08 2004-May-17
2.165660] efivars: get_next_variable: status=8000000000000007
2.165737] hidraw: raw HID events driver (C) Jiri Kosina
2.166845] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
2.167454] NET: Registered protocol family 10
2.168791] registered taskstats version 1
2.168907] zswap: loaded using pool lzo/zbud
2.168961] page_owner is disabled
2.183067] Key type encrypted registered
2.183103] AppArmor: AppArmor sha1 policy hashing enabled
2.183452] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 72, base_baud = 0) is a PL011 rev2
2.184207] console [ttyS0] disabled
2.184237] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 61, base_baud = 31224999) is a 16550
2.201186] console [ttyS0] enabled
2.201560] raspberrypi-firmware soc:firmware: Attached to firmware from 2016-09-02 11:49
2.201747] hctosys: unable to open rtc device (rtc0)
2.204973] Freeing unused kernel memory: 908K (ffff800000c6a000 - ffff800000d4d000)
2.219092] random: systemd: uninitialized urandom read (16 bytes read, 2 bits of entropy available)
2.219926] random: systemd: uninitialized urandom read (16 bytes read, 2 bits of entropy available)
2.220010] random: systemd: uninitialized urandom read (16 bytes read, 2 bits of entropy available)
2.222420] systemd[1]: systemd 228 running in system mode. (+PAM +AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
2.222896] systemd[1]: Detected architecture arm64.
2.222919] systemd[1]: Running in initial RAM disk.
2.223015] systemd[1]: Set hostname to <nohostname>.
...
7.789372] audit_printk_skb: 99 callbacks suppressed
7.789397] audit: type=1130 audit(7.759:44): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
7.791068] audit: type=1130 audit(7.769:45): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
7.912200] audit: type=1130 audit(7.889:46): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
8.027576] audit: type=1130 audit(7.999:47): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udev-trigger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
8.278718] i2c-bcm2835 3f805000.i2c: Could not read clock-frequency property
8.291424] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
8.358519] usbcore: registered new interface driver usbfs
8.358594] usbcore: registered new interface driver hub
8.358717] usbcore: registered new device driver usb
8.614273] [drm] Initialized drm 1.1.0 20060810
9.263596] bcm2835-rng 3f104000.rng: hwrng registered
...
9.461952] hub 1-0:1.0: USB hub found
9.461992] hub 1-0:1.0: 1 port detected
9.463922] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
9.464118] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
9.464261] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
9.464381] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
9.464442] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
9.464565] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
9.464574] checking generic (3d513000 6d9000) vs hw (0 ffffffffffffffff)
9.464579] fb: switching to vc4drmfb from EFI VGA
9.465224] Console: switching to colour dummy device 80x25
9.466162] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
9.466171] [drm] No driver support for vblank timestamp query.
9.501953] bcm2835-clk 3f101000.cprman: pllh: rate out of spec: 4155000000 vs (600000000, 3000000000)
9.526635] Console: switching to colour frame buffer device 240x67
9.581920] vc4-drm soc:gpu: fb0: frame buffer device
… I see a lot of “bcm2835”, while the raspi 3 has a bcm2837 AFAIK…
I really don’t know how people get this to boot correctly. Or why these images do result in so different outcome on different raspi 3…
Your posted log suggests there might be some inaccessible memory locations… Unknown whether the errors are critical enough to substantially affect how the system runs. In any case, those errors appear to be upstream, and for at least 2 errors I see early bug reports (They’re just starting to trace whatever the cause might be).
Your bcm2835 mentions relate to an i2c board, I assume you have one on top of your RPi?
TSU
Hi again!
Nope, no extras, just plain raspi 3, a usb hub for keyboard/trackball and an LG HDMI monitor. Very strange!
How did Mr. Samba from my post linked above get this up and running on a raspi 3? I don’t get this…
raspu
PS: As mentioned earlier, my setup is doing absolutely fine with jessie light (with GUI) and kali.
…just to add:
I installed on this raspi 3 via ssh tigervnc and started it, but the server dies after login + 1-2 mouse clicks with segmentation faults. So: I guess there is something going wrong with the RAM, or?
Tried todays built with desktop from here:
Boots fine, as usual finds no appropriate settings for my monitor, but with TigerVNC installed running stable and doing fine so far.
On 09/23/2016 03:29 PM, Ken Schneider wrote:
> On 09/22/2016 11:16 AM, suse rasputin wrote:
>>
>>
>
> Thanks for the information. In my case when booting I could select the
> default boot entry and hit enter, but at that point the screen would go
> black and even with waiting a few minutes I could not ssh to the Pi3B.
>
Follow up.
I found my problem to be one of not having enough patience. When the
screen went dark I had a message on the monitor stating “No Signal”. I
wrongly took this to mean that the Rpi hung. After trying again I waited
for about thirty minutes and switched back to the input on the monitor
for the Rpi and saw a login window.
Still more experimenting to do after I get settled in my winter home in
Florida. Keep up the good work.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
Hi again!
I use SanDisk Ultra class 10 in 8 and 16 GB, on the raspi 3 the first boot took about 5 min or so for the ssh login, afterwards takes less then a minute or so.
Winter is fun! 
If you want to add samba support to the default filemanager, Thunar, you have to install gvfs-…-samba as well as sshfs. Reboot. Samba works…
Don’t try to access forums.opensuse.org with Firefox in aarch64 TW ! Process has 275 MiB RAM and explodes before you see the first pixel