Can someone check support for RPi OTG? Req RPi 1 or RPi Zero today

English Install/Boot/Login
1

Would appreciate someone checking and verifying this on a RPi 1 or RPi Zero (Tumbleweed),
Am not personally set up to test yet, and is both an important option and on the RPi Zero almost imperative that this method which enables connecting to the RPi using an ordinary USB data cable in headless mode (no monitor, keyboard or mouse) works.

Is described here, is supposed to work only on RPi 1 and RPi Zero currently (Don’t know if support to others is possible since this was first enabled)
https://gist.github.com/gbaman/975e2db164b3ca2b51ae11e45e8fd40a

Aside from just plugging in the values, this is a relatively recent addition to raspbian, unknown whether was added upstream so that other distros like openSUSE gets the kernel modules automatically.

Required kernel module

dwc2

With the above module, it becomes possible to load a number of optional other kernel modules on boot, including the following which provides “ethernet over USB” which if configured enables SSH into the RPi out of the box.

g_ether

The following might return the answer

ls -R /lib/modules/`uname -r`/kernel/ | grep dwc2

TIA,
TSU

2

Hi again!

OT: Bought “my” zero (only one per customer AFAIK) some days ago, want to make it learn how to fly (no motors, just wind :-D) with cam attached soon. Absolutely headless, no network needed!

I ran on raspi 1b with TW kernel 4.6.2.1-default

ls -R /lib/modules/`uname -r`/kernel/ | grep dwc2

which gave me no output…

As a second option I would ALWAYS consider the serial consol (just three pins), but you need a 3.3V to 5V (normally USB) converter, normal serial console on your computer+serial cable won’t help much.

Anyways, TW on raspi 1/zero is not really fun (maybe as JEOS, haven’t tried that yet). Maybe start with raspian light (no GUI and stuff like Wolfram engine)

Fun!

PS: I guess you got the authoritative answer already :slight_smile:

https://lists.opensuse.org/opensuse-arm/2016-09/msg00060.html

3

Thx for the suggestions, yes I <just> saw that answer on the mailing list.
I think that there are GPIO pins for both 3.3V and 5V… But I’m unclear, are you describing some kind of hardware?

Too bad, I was hoping that the module was “just” disabled but could still be loaded but it might be that the module was blacklisted.

Am hoping that if the module is blacklisted, it might be made available in a future release… After, it’s Tumbleweed, right?

:slight_smile:

TSU

4

Nope, the serial console output is 3.3V, you need pins #6, 8, and 10 according to this schema

https://pinout.xyz/

…if you ad 5v to pin #2 or 4 you can directly power up the whole raspi, no microUSB power supply needed. Don’t EVER try anything with 5V on ANY OTHER pins, everything 3.3v. Will directly kill your toy.

You need an adapter like this here:

https://www.modmypi.com/raspberry-pi/gpio-and-breadboarding/gpio-debugging-console-cables/usb-to-ttl-serial-cable-debug--console-cable-for-raspberry-pi](https://www.amazon.com/s/ref=sr_pg_1?rh=i%3Aaps%2Ck%3Aserial+console+usb+raspberry+pi&keywords=serial+console+usb+raspberry+pi&ie=UTF8&qid=1474481866&spIA=B00GRP8EZU,B01C6Q4GLE,B008634VJY,B00J4N9T9C)https://www.amazon.com/s/ref=sr_pg_1?rh=i%3Aaps%2Ck%3Aserial+console+usb+raspberry+pi&keywords=serial+console+usb+raspberry+pi&ie=UTF8&qid=1474481866&spIA=B00GRP8EZU,B01C6Q4GLE,B008634VJY,B00J4N9T9C

5

For anyone reading this thread later,

What suse_rasputin is describing is this…

The RPi has an embedded UART chip which everyone should know means support for RS-232 serial communications, the common serial port we’ve seen in all computing devices going back to earliest times. On big Desktops, we’ve used DB-9 connectors and before that the DB-25 connector.

On the RPi,
serial communications are exposed on pins 8 (Tx) and 10 (Rx).

When you have a serial connection like this, you can run any app that uses a standard serial protocol, including a terminal console.

But, as noted you need special hardware to connect to, and use these pins…
Nowadays, unless you have an old-style Desktop with a DB-9 or DB-25 connector that can speak “pure” serial, you’ll more likely need a device that can convert the Rx/Tx to communications using a USB connection on your laptop or desktop.

So, special hardware is required, which is the Amazon link suse_rasputin provided.
You can decide whether you want to spend your money on this special hardware or get a mini-HDMI to regular HDMI cable (assuming your display supports HDMI, else you have more issues).

I doubt the 5V (or 3.3V) power connections are needed for a console connection, but the 5V connection might be a convenient means to power the RPi instead of using the micro-USB connection. Powering the device is a completely separate issue from running apps.

If the OTG modules I want to use function properly, all this extra expense and additional connections can be avoided.

TSU

6

…just to add, even if the OTG stuff works (sometimes… :wink: ) it’s good to have a second option to get into your raspi, just in case.

If you want do some stuff with these little machines on the longer run, it’s always good to have such a cable, in my experience. And the serial communication is not a one-way street, one can disable the output from raspi boot and use the interface for input from another device (logging, data, whatever…).

7

Saw your post on raspi zero not blinking while booting
https://lists.opensuse.org/opensuse-arm/2016-09/msg00073.html

Don’t panic, saw that also with some images, no blink at all, but after some time (give it some 20-30 min for the first boot with re-sizing partitions, just to be really sure) you might be able to ssh the device. Have an eye on your routers DHCP log in the meantime :smiley:

Or watch the serial console, which gives you a good impression what’s really going on.

8

PS: something on the really weird boot process GPU -> CPU

https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=6685

http://wiki.beyondlogic.org/index.php?title=Understanding_RaspberryPi_Boot_Process

9

Thx for those links,
They describe the boot process using files I see in the raspbian,
But raises questions about openSUSE because files are missing (the only files that are present are config.txt, the bin file and the ELF file).
Should files be missing? is there really no need for any special kernel parameters? Is the kernel being loaded some way not described in your links?

Is why I was asking for where source is located and a flow definition to know if something was different or missing compared to the raspbian.

TSU

10

…depends on if you describt the SD-card before or after first boot. After first boot completed (!) on an arm6 TW there are three (!) partitions:

  • EFI
  • BOOT
  • ROOT

on EFI there should be

EFI> ls -al
total 3064
drwxr-xr-x  2 s users   16384 Jan  1  1970 .
drwxr-x---+ 3 root    root       60 Sep 25 18:49 ..
-rw-r--r--  1 s users   17932 Jun 21 13:13 bootcode.bin
-rw-r--r--  1 s users     847 Jun 21 13:13 Config.txt
-rw-r--r--  1 s users    6480 Jun 21 13:13 fixup.dat
-rw-r--r--  1 s users    1494 Jun 21 13:13 LICENCE.broadcom
-rw-r--r--  1 s users 2743224 Jun 21 13:13 start.elf
-rw-r--r--  1 s users  339072 Jun 21 13:13 u-boot.bin

on BOOT you should see

ls -al
total 19110
drwxr-xr-x  7 root root    1024 Sep 21 10:36 .
drwxr-x---+ 4 root root      80 Sep 25 18:51 ..
-rw-r--r--  1 root root       0 Jun 21 13:13 0x6f2d79f2
lrwxrwxrwx  1 root root       1 Jun 21 02:01 boot -> .
-rw-r--r--  1 root root    1725 Mai 31 14:48 boot.readme
-rw-r--r--  1 root root    2722 Jun 21 02:08 boot.scr
-rw-r--r--  1 root root    2650 Jun 21 02:08 boot.script
-rw-r--r--  1 root root  146359 Jun 12 21:21 config-4.6.2-1-default
lrwxrwxrwx  1 root root      11 Jun 21 12:17 dtb -> dtb-4.6.2-1
drwx------  2 root root    1024 Jun 21 13:13 dtb-4.6.2-1
drwxr-xr-x  2 root root    1024 Jun 21 02:08 efi
lrwxrwxrwx  1 root root      22 Jun 21 12:26 initrd -> initrd-4.6.2-1-default
-rw-------  1 root root 6102920 Sep 21 10:36 initrd-4.6.2-1-default
drwx------  2 root root   12288 Jun 21 13:12 lost+found
-rw-r--r--  1 root root  263881 Jun 13 12:24 symvers-4.6.2-1-default.gz
-rw-r--r--  1 root root     207 Jun 13 12:24 sysctl.conf-4.6.2-1-default
-rw-r--r--  1 root root 2407008 Jun 13 11:19 System.map-4.6.2-1-default
drwxr-xr-x  2 root root    1024 Jun 21 13:13 vboot
drwxr-xr-x  2 root root    1024 Jun 21 12:09 vc
-rw-r--r--  1 root root 5824485 Jun 13 12:40 vmlinux-4.6.2-1-default.gz
lrwxrwxrwx  1 root root      22 Jun 21 12:26 zImage -> zImage-4.6.2-1-default
-rw-r--r--  1 root root 4712272 Jun 13 11:20 zImage-4.6.2-1-default
-rw-r--r--  1 root root      65 Jun 13 12:24 .zImage-4.6.2-1-default.hmac

And root looks like usual TW root…

11

Hooking up to a monitor,
It does look like the RPi TW JeOS boot process proceeded silently, there are a series of files loaded and ethernet enabled, finally dropping to a prompt

boot>

I’ll have to get a USB keyboard hooked up so I can verify the kernel,
Then I’m speculating in my mind that if the raspbian and openSUSE boot process should be the same, the process might still read a cmdline.txt I can add that isn’t there now, and I can insert some of the commands from raspbian into the openSUSE file.

Maybe by tomorrow evening I might have figured out a bunch of things if no one has certain answers for now.

TSU

12

Currently, the SDcard only has the files listed in what you describe as the EFI partition.
This image has been booted “fully” as far as it will boot or not boot, and currently ends with a “boot>” prompt

boot>

So, it appears that the image is not completely dead, but may not have proceeded beyond stage 1.
I should know more when I can attach a keyboard and explore what can be seen from this prompt.

TSU

13

I think I located the reason for your “no output.”

Am studying now how the raspbian loads Device Tree Overlays during the boot process which vastly extends hardware support to numerous types of hardware such as daughterboards, I/O devices and more… a virtually unlimited number of possible connected hardware which isn’t likely included in the kernel.

Without this support, the RPi is severely limited.
The alternative to a Device Tree Overlay would be typing in definitions by hand and modding to add and query modules individually.

But, if my early guess is correct, it won’t be difficult to migrate to the openSUSE RPi… It might be as simple as copying some files and a couple command line modifications.

This is the documentation describing how DT Overlays are used in the current raspbian kernel…

This is a “very important” missing feature in the current openSUSE RPi until it also supports.

TSU

14

Three ideas:

  • you used the image from here

http://download.opensuse.org/ports/armv6hl/tumbleweed/images/

dated 21-JUN-2016? My copy from there works fine on raspi 1b. I never tried the JeOS image, however.

  • you used the command
xzcat [image].raw.xz | dd bs=4M of=/dev/sdX iflag=fullblock oflag=direct; sync

to copy to SD-card?

  • Try a different size/speed class/brand of SD-card. Raspis can be picky with the controllers on these cards, sometimes.

Fun! :slight_smile:

15

PS: booted the JeOS image linked above on a raspi 1b, no problem, takes SOME time, but then I can login as root.

Random MAC assigned to eth0 as described elsewhere

https://forums.opensuse.org/showthread.php/520025-ARM6-version-random-MAC-on-Raspberry-Pi-1B

16

I can confirm this error message here

https://lists.opensuse.org/opensuse-arm/2016-09/msg00077.html

but if you wait long enough the system boots correctly subsequently, no problems here.

17

…and a

zypper dup

on this SD-card leads to

Linux name 4.7.3-1-default #1 Thu Sep 8 13:08:03 UTC 2016 (7ad9c1d) armv6l armv6l armv6l GNU/Linux
18

The TW JeOS image I’m using, downloaded this past week (could you have changed the “12” to a “21”)?

openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2016.06.12-Build2.10.raw.xz

The card is good,
It’s an 8GB Class 10, and I have another one running raspbian.
As I described, it’s not like the card isn’t recognized, the boot process apparently starts, and then just sits at a command prompt and won’t go any further.

I let the system sit for over an hour before,
I’ll try again later today.

If it’s really stuck at the end of Stage 1, I wonder if there is a command to help it along to Stage 2…

TSU

19

I took the date from the “last modified” column on the download page, there it says 21-JUN-2016 :wink:

After the kernel update I have no output on the screen attached after loading the kernel (after the penguin disappears, replacing the raspberry in the debian bootscreen…)

ssh gives me

top
top - 01:05:49 up 5 min,  1 user,  load average: 0,06, 0,34, 0,21
Tasks:  66 total,   1 running,  65 sleeping,   0 stopped,   0 zombie
%Cpu(s):  1,0 us,  0,7 sy,  0,0 ni, 98,3 id,  0,0 wa,  0,0 hi,  0,0 si,  0,0 st
KiB Mem :   444228 total,   350644 free,    22100 used,    71484 buff/cache
KiB Swap:   509928 total,   509928 free,        0 used.   410976 avail Mem 

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                 
 1042 usser     20   0    8560   3560   2936 R 1,629 0,801   0:01.04 top                                     
  998 usser     20   0   14992   3532   2776 S 0,326 0,795   0:00.35 sshd                                    
    1 root      20   0    6728   4792   3796 S 0,000 1,079   0:12.74 systemd                                 
    2 root      20   0       0      0      0 S 0,000 0,000   0:00.00 kthreadd                                
    3 root      20   0       0      0      0 S 0,000 0,000   0:00.30 ksoftirqd/0                             
    4 root      20   0       0      0      0 S 0,000 0,000   0:00.20 kworker/0:0                             
    5 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 kworker/0:0H                            
    6 root      20   0       0      0      0 S 0,000 0,000   0:00.12 kworker/u2:0                            
    7 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 lru-add-drain                           
    8 root      rt   0       0      0      0 S 0,000 0,000   0:00.00 watchdog/0                              
    9 root      20   0       0      0      0 S 0,000 0,000   0:00.01 kdevtmpfs                               
   10 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 netns                                   
   11 root      20   0       0      0      0 S 0,000 0,000   0:00.00 khungtaskd                              
   12 root      20   0       0      0      0 S 0,000 0,000   0:00.00 oom_reaper                              
   13 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 writeback                               
   14 root      20   0       0      0      0 S 0,000 0,000   0:00.00 kcompactd0                              
   15 root      25   5       0      0      0 S 0,000 0,000   0:00.00 ksmd                                    
   16 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 crypto                                  
   17 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 kintegrityd                             
   18 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 bioset                                  
   19 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 kblockd                                 
   20 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 ata_sff                                 
   21 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 devfreq_wq                              
   22 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 watchdogd                               
   23 root      20   0       0      0      0 S 0,000 0,000   0:00.11 kworker/0:1                             
   24 root      20   0       0      0      0 S 0,000 0,000   0:00.00 kswapd0                                 
   59 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 kthrotld                                
   60 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 dwc2                                    
   61 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 kpsmoused                               
   62 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 ipv6_addrconf                           
   63 root      20   0       0      0      0 S 0,000 0,000   0:00.00 kworker/u2:1                            
   78 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 deferwq                                 
   84 root      20   0       0      0      0 S 0,000 0,000   0:00.00 kworker/0:2                             
  115 root      20   0       0      0      0 S 0,000 0,000   0:00.00 kauditd                                 
  125 root      20   0       0      0      0 S 0,000 0,000   0:00.14 kworker/0:4                             
  196 root     -51   0       0      0      0 S 0,000 0,000   0:00.00 irq/86-mmc0                             
  201 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 bioset                                  
  202 root      20   0       0      0      0 S 0,000 0,000   0:11.40 mmcqd/0                                 
  203 root       0 -20       0      0      0 S 0,000 0,000   0:00.07 kworker/0:1H                            
  212 root      20   0       0      0      0 S 0,000 0,000   0:00.01 jbd2/mmcblk0p3-                         
  213 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 ext4-rsv-conver                         
  271 root      20   0   21000  10484  10196 S 0,000 2,360   0:01.18 systemd-journal                         
  293 root      20   0   13296   3404   2768 S 0,000 0,766   0:01.20 systemd-udevd                           
  373 root      20   0       0      0      0 S 0,000 0,000   0:00.00 jbd2/mmcblk0p2-                         
  374 root       0 -20       0      0      0 S 0,000 0,000   0:00.00 ext4-rsv-conver                         
  394 root      16  -4   11764   2088   1868 S 0,000 0,470   0:00.05 auditd                                  
  415 message+  20   0    7048   3744   3204 S 0,000 0,843   0:00.65 dbus-daemon                             
  416 root      20   0    7820   4440   3756 S 0,000 0,999   0:00.24 wickedd-auto4                           
  417 root      20   0    7820   4524   3840 S 0,000 1,018   0:00.27 wickedd-dhcp6                           
  419 root      20   0    4276   2704   2448 S 0,000 0,609   0:00.15 systemd-logind                          
  421 root      20   0    7824   4652   3964 S 0,000 1,047   0:00.22 wickedd-dhcp4                           
  427 root      20   0    7940   4692   3888 S 0,000 1,056   0:00.36 wickedd                                 
  429 root      20   0    2796   1812   1688 S 0,000 0,408   0:00.03 agetty                                  
  430 root      20   0    2796   1732   1612 S 0,000 0,390   0:00.03 agetty                                  
  432 root      20   0    7840   4700   3972 S 0,000 1,058   0:00.29 wickedd-nanny                           
  876 root      20   0    8368   4716   4264 S 0,000 1,062   0:00.16 sshd                                    
  879 ntp       20   0    9384   5008   4468 S 0,000 1,127   0:00.21 ntpd

And I see this here:

dmesg
    0.000000] Booting Linux on physical CPU 0x0
    0.000000] Linux version 4.7.3-1-default (geeko@buildhost) (gcc version 6.2.1 20160830 [gcc-6-branch revision 239856] (SUSE Linux) ) #1 Thu Sep 8 13:08:03 UTC 2016 (7ad9c1d)
    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
    0.000000] Machine model: Raspberry Pi Model B rev2
    0.000000] Memory policy: Data cache writeback
    0.000000] On node 0 totalpages: 114688
    0.000000] free_area_init_node: node 0, pgdat c097147c, node_mem_map dbc0a000
    0.000000]   Normal zone: 1008 pages used for memmap
    0.000000]   Normal zone: 0 pages reserved
    0.000000]   Normal zone: 114688 pages, LIFO batch:31
    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
    0.000000] pcpu-alloc: [0] 0 
    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 113680
    0.000000] Kernel command line: root=/dev/disk/by-id/mmc-SDC_0xe74065eb-part3 loader=uboot disk=/dev/disk/by-id/mmc-SDC_0xe74065eb resume=/dev/disk/by-id/mmc-SDC_0xe74065eb-part4   quiet splash=silent plymouth.enable=0  dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 rootflags=commit=120,data=writeback 
    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    0.000000] Memory: 437648K/458752K available (6211K kernel code, 530K rwdata, 2476K rodata, 472K init, 760K bss, 21104K reserved, 0K cma-reserved, 0K highmem)
    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   DTCM    : 0xfffe8000 - 0xfffe8000   (   0 kB)
                   ITCM    : 0xfffe0000 - 0xfffe0000   (   0 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xdc800000 - 0xff800000   ( 560 MB)
                   lowmem  : 0xc0000000 - 0xdc000000   ( 448 MB)
                   pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
                   modules : 0xbf000000 - 0xbfe00000   (  14 MB)
                     .text : 0xc0008000 - 0xc0883fa8   (8688 kB)
                     .init : 0xc0884000 - 0xc08fa000   ( 472 kB)
                     .data : 0xc08fa000 - 0xc097e890   ( 531 kB)
                      .bss : 0xc097f000 - 0xc0a3d078   ( 761 kB)
    0.000000] NR_IRQS:16 nr_irqs:16 16
    0.000025] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
    0.000061] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
    0.000142] bcm2835: system timer (irq = 27)
    0.001199] Console: colour dummy device 80x30
    0.001378] console [tty1] enabled
    0.001407] Calibrating delay loop... 835.58 BogoMIPS (lpj=4177920)
    0.040248] pid_max: default: 32768 minimum: 301
    0.040791] Security Framework initialized
    0.040839] AppArmor: AppArmor initialized
    0.041196] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
    0.041216] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
    0.042854] CPU: Testing write buffer coherency: ok
    0.042918] ftrace: allocating 23582 entries in 47 pages
    0.149172] Setting up static identity map for 0x8200 - 0x825c
    0.154102] devtmpfs: initialized
    0.159038] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
    0.159485] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
    0.159744] pinctrl core: initialized pinctrl subsystem
    0.161415] NET: Registered protocol family 16
    0.162132] DMA: preallocated 256 KiB pool for atomic coherent allocations
    0.163183] cpuidle: using governor ladder
    0.163203] cpuidle: using governor menu
...
...
   30.750121] raspberrypi-firmware soc:firmware: Attached to firmware from 2016-09-02 11:49
   32.676407] vc4-drm soc:gpu: bound 20902000.hdmi (ops vc4_hdmi_ops [vc4])
   32.680992] vc4-drm soc:gpu: bound 20206000.pixelvalve (ops vc4_crtc_ops [vc4])
   32.684243] vc4-drm soc:gpu: bound 20207000.pixelvalve (ops vc4_crtc_ops [vc4])
   32.684729] vc4-drm soc:gpu: bound 20807000.pixelvalve (ops vc4_crtc_ops [vc4])
   32.684926] vc4-drm soc:gpu: bound 20400000.hvs (ops vc4_hvs_ops [vc4])
   32.685134] [drm:vc4_v3d_bind [vc4]] *ERROR* V3D_IDENT0 read 0xdeadbeef instead of 0x02443356
   32.694547] vc4-drm soc:gpu: failed to bind 20c00000.v3d (ops vc4_v3d_ops [vc4]): -22
   32.703330] vc4-drm soc:gpu: master bind failed: -22
   32.703416] vc4-drm: probe of soc:gpu failed with error -22
   32.936215] smsc95xx v1.0.4
...
20

oh:

https://lists.opensuse.org/opensuse-bugs/2016-09/msg01450.html

…so I would skip zypper dup for the time and go with the old kernel for the time being :slight_smile: