I recently used zypper to upgrade the kernel on my Raspberry Pi 3B+
running openSUSE 42.3 and it now fails to boot. If I watch the boot
process I see the message “Loading initial ramdisk …” and then about a
second later the Pi reboots. The previous kernel, 4.4.162-78, boots
without error. Additionally if I use “yast bootloader” to change the
default boot entry it doesn’t seem to change anything. This is
effectively a headless system so if I ever do need to reboot it I have
to dig out keyboard and monitor to manually change the kernel to boot
Any ideas as to how I can sort the problem with 4.4.165-81 and also why
I can’t change the default entry?
Hi
I’m assuming you don’t have a serial cable to hook up to the RPi? You can ssh to the system after booting the old kernel? If so can you check the output from;
Thanks for your reply. Yes I can SSH once booting the old kernel and no
I don’t have a serial cable. Sorry.
There is no output from the command you gave. Running “yast bootloader”
shows that as far as yast is concerned the default bootloader should be
4.4.162-78 (this is what is highlighted when I bring up the list of
options) but when the system boots it actually loads 4.4.165-81
Hope that helps
Thanks
Paul
On 13/01/2019 16:56, malcolmlewis wrote:
>
> Paul;2891467 Wrote:
>> I recently used zypper to upgrade the kernel on my Raspberry Pi 3B+
>> running openSUSE 42.3 and it now fails to boot. If I watch the boot
>> process I see the message “Loading initial ramdisk …” and then about a
>> second later the Pi reboots. The previous kernel, 4.4.162-78, boots
>> without error. Additionally if I use “yast bootloader” to change the
>> default boot entry it doesn’t seem to change anything. This is
>> effectively a headless system so if I ever do need to reboot it I have
>> to dig out keyboard and monitor to manually change the kernel to boot
>>
>> Any ideas as to how I can sort the problem with 4.4.165-81 and also why
>> I can’t change the default entry?
>>
>> Thanks
>>
>> Paul
> Hi
> I’m assuming you don’t have a serial cable to hook up to the RPi? You
> can ssh to the system after booting the old kernel? If so can you check
> the output from;
>
> Code:
> --------------------
>
> cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT
>
> --------------------
>
>
> Again via ssh you can run YaST, just the ncurses one, yast as apposed to
> yast2, can you check if you can change the default entry via this
> method?
>
>
Thanks for your reply. Yes I can SSH once booting the old kernel and no
I don’t have a serial cable. Sorry.
There is no output from the command you gave. Running “yast bootloader”
shows that as far as yast is concerned the default bootloader should be
4.4.162-78 (this is what is highlighted when I bring up the list of
options) but when the system boots it actually loads 4.4.165-81
<snip>
Hi
So what kernels are down in /boot? Try rebuilding initrd and grub via;
su -
mkinitrd
grub2-mkconfig -o /boot/grub2/grub.cfg
I’m interested in the output of the grub line especially the cma= entry.
In yast bootloader the third tab “Bootloader options” the openSUSE 42.3
entry should be to the latest kernel, you need to select the entry with
the kernel name in the entry.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
linuxpi:~ # ls -l /boot | grep initrd
-rw------- 1 root root 6568536 Dec 20 13:02 initrd-4.4.162-78-default
-rw------- 1 root root 6568536 Dec 20 13:04 initrd-4.4.165-81-default
linuxpi:~ # grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/Image-4.4.165-81-default
Found initrd image: /boot/initrd-4.4.165-81-default
Found linux image: /boot/Image-4.4.162-78-default
Found initrd image: /boot/initrd-4.4.162-78-default
done
If I open /boot/grub2/grub.cfg there is no cma= entry
In yast bootloader the third tab “Bootloader options” the openSUSE 42.3
entry should be to the latest kernel, you need to select the entry with
the kernel name in the entry.
That’s what I have done. I run “yast bootloader” → Alt+L → Alt+F and
this brings up a box with 5 entries
openSUSE Leap 42.3
openSUSE Leap 42.3, with Linux 4.4.165-81-default
openSUSE Leap 42.3, with Linux 4.4.165-81-default (recovery mode)
openSUSE Leap 42.3, with Linux 4.4.162-78-default
openSUSE Leap 42.3, with Linux 4.4.162-78-default (recovery mode)
The 4th of these is highlighted but upon rebooting it still tries to
boot 4.4.165-81
Thanks
Paul
On 13/01/2019 23:32, malcolmlewis wrote:
On Sun 13 Jan 2019 07:26:07 PM CST, Paul wrote:
Thanks for your reply. Yes I can SSH once booting the old kernel and no
I don’t have a serial cable. Sorry.
There is no output from the command you gave. Running “yast bootloader”
shows that as far as yast is concerned the default bootloader should be
4.4.162-78 (this is what is highlighted when I bring up the list of
options) but when the system boots it actually loads 4.4.165-81
Hi
So what kernels are down in /boot? Try rebuilding initrd and grub via;
> su -
> mkinitrd
> grub2-mkconfig -o /boot/grub2/grub.cfg
>
>
> I’m interested in the output of the grub line especially the cma= entry.
>
> In yast bootloader the third tab “Bootloader options” the openSUSE 42.3
> entry should be to the latest kernel, you need to select the entry with
> the kernel name in the entry.
>
I should have also said that 4.4.165-81 still doesn’t boot
Thanks
Paul
On 14/01/2019 10:58, Paul wrote:
>
> linuxpi:~ # ls -l /boot | grep initrd
> -rw------- 1 root root 6568536 Dec 20 13:02 initrd-4.4.162-78-default
> -rw------- 1 root root 6568536 Dec 20 13:04 initrd-4.4.165-81-default
>
> linuxpi:~ # grub2-mkconfig -o /boot/grub2/grub.cfg
> Generating grub configuration file ...
> Found theme: /boot/grub2/themes/openSUSE/theme.txt
> Found linux image: /boot/Image-4.4.165-81-default
> Found initrd image: /boot/initrd-4.4.165-81-default
> Found linux image: /boot/Image-4.4.162-78-default
> Found initrd image: /boot/initrd-4.4.162-78-default
> done
>
If I open /boot/grub2/grub.cfg there is no cma= entry
In yast bootloader the third tab “Bootloader options” the openSUSE 42.3
entry should be to the latest kernel, you need to select the entry with
the kernel name in the entry.
That’s what I have done. I run “yast bootloader” → Alt+L → Alt+F and
this brings up a box with 5 entries
openSUSE Leap 42.3
openSUSE Leap 42.3, with Linux 4.4.165-81-default
openSUSE Leap 42.3, with Linux 4.4.165-81-default (recovery mode)
openSUSE Leap 42.3, with Linux 4.4.162-78-default
openSUSE Leap 42.3, with Linux 4.4.162-78-default (recovery mode)
The 4th of these is highlighted but upon rebooting it still tries to
boot 4.4.165-81
Thanks
Paul
On 13/01/2019 23:32, malcolmlewis wrote:
On Sun 13 Jan 2019 07:26:07 PM CST, Paul wrote:
Thanks for your reply. Yes I can SSH once booting the old kernel and no
I don’t have a serial cable. Sorry.
There is no output from the command you gave. Running “yast bootloader”
shows that as far as yast is concerned the default bootloader should be
4.4.162-78 (this is what is highlighted when I bring up the list of
options) but when the system boots it actually loads 4.4.165-81
Hi
So what kernels are down in /boot? Try rebuilding initrd and grub via;
>> su -
>> mkinitrd
>> grub2-mkconfig -o /boot/grub2/grub.cfg
>>
>>
>> I’m interested in the output of the grub line especially the cma= entry.
>>
>> In yast bootloader the third tab “Bootloader options” the openSUSE 42.3
>> entry should be to the latest kernel, you need to select the entry with
>> the kernel name in the entry.
>>
>
I added the below to the end of this file, rebuilt grub, verified that
the cma entry had been appended to the relevant line and rebooted.
Unfortunately it still won’t boot 4.4.165-81
Code:
GRUB_CMDLINE_LINUX_DEFAULT=" cma=300M"
Thanks
Paul
On 14/01/2019 13:26, malcolmlewis wrote:
>
> Hi
> Can you change the kernel options to include cma=300, for example on my
> Leap 15.0 RPi it’s;
>
> Code:
> --------------------
>
> GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 splash=silent plymouth.enable=0 swiotlb=512 cma=300M console=ttyS1,115200n8 root=UUID=xxxx rw "
>
> --------------------
>
> Can you confirm how similar yours is.
>
> Then rebuild grub via;
>
> Code:
> --------------------
>
> grub2-mkconfig -o /boot/grub2/grub.cfg
>
> --------------------
>
>
I added the below to the end of this file, rebuilt grub, verified that
the cma entry had been appended to the relevant line and rebooted.
Unfortunately it still won’t boot 4.4.165-81
Code:
GRUB_CMDLINE_LINUX_DEFAULT=" cma=300M"
Thanks
Paul
On 14/01/2019 13:26, malcolmlewis wrote:
>
> Hi
> Can you change the kernel options to include cma=300, for example on
> my Leap 15.0 RPi it’s;
>
> Code:
> --------------------
>
> GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 splash=silent
> plymouth.enable=0 swiotlb=512 cma=300M console=ttyS1,115200n8
> root=UUID=xxxx rw " --------------------
>
> Can you confirm how similar yours is.
>
> Then rebuild grub via;
>
> Code:
> --------------------
>
> grub2-mkconfig -o /boot/grub2/grub.cfg
>
> --------------------
>
>
Hi
Since it’s also missing this, swiotlb=512 can you add that as well and
rebuild.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I’ve managed to video the relevant part of the screen when it crashes.
As previously stated I get “Loading initial ramdisk …” and then about
a second later I get
and then a list for values from x0 to at least x19, each with a hex value
Thanks
Paul
On 14/01/2019 18:22, malcolmlewis wrote:
>
> On Mon 14 Jan 2019 04:47:28 PM CST, Paul wrote:
>
> /etc/default/grub contained only GRUB_CMDLINE_LINUX. This has the value
>
> Code:
> --------------------
>
> GRUB_CMDLINE_LINUX=" root=/dev/disk/by-id/mmc-xxxx-part2
> disk=/dev/disk/by-id/mmc-xxxx resume=/dev/disk/by-id/mmc-xxxx-part3
> quiet splash=silent plymouth.enable=0 console=ttyS0,115200n8 quiet"
>
> --------------------
>
> I added the below to the end of this file, rebuilt grub, verified that
> the cma entry had been appended to the relevant line and rebooted.
> Unfortunately it still won’t boot 4.4.165-81
>
> Code:
> --------------------
>
> GRUB_CMDLINE_LINUX_DEFAULT=" cma=300M"
>
> --------------------
>
> Thanks
>
> Paul
>
> On 14/01/2019 13:26, malcolmlewis wrote:
>>
>> Hi
>> Can you change the kernel options to include cma=300, for example on
>> my Leap 15.0 RPi it’s;
>>
>> Code:
>> --------------------
>>
>> GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 splash=silent
>> plymouth.enable=0 swiotlb=512 cma=300M console=ttyS1,115200n8
>> root=UUID=xxxx rw " --------------------
>>
>> Can you confirm how similar yours is.
>>
>> Then rebuild grub via;
>>
>> Code:
>> --------------------
>>
>> grub2-mkconfig -o /boot/grub2/grub.cfg
>>
>> --------------------
>>
>>
>
>
>
> Hi
> Since it’s also missing this, swiotlb=512 can you add that as well and
> rebuild.
>
Hi
So can you post the full output from the grub command line?
I wonder if removing the newer kernel and re-installing may kick things into life, else jump on IRC Freenode #opensuse-arm to see what the guys there have to say about your issue. Perhaps you can get a serial cable for the RPi? I use a PL2303HX USB to TTL to UART COM Cable, it would help a lot to get more info…
Uninstalling and re-installing 165-81 hasn’t made any difference. I also
spotted in the output of mkinitrd the following line
I: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log
--force /boot/initrd-4.4.165-81-default 4.4.165-81-default
W: /lib/modules/4.4.165-81-default//modules.dep is missing. Did you run
depmod?
I reinstalled kernel-default, kernel-default-devel and kmod-compat,
reran mkinitrd and this error went away however I still can’t boot 165-81
I can order a serial cable but it won’t be here for couple of days.
There’s nowhere around here that I can go to and buy one
Thanks
Paul
On 16/01/2019 15:46, malcolmlewis wrote:
>
> Paul;2891561 Wrote:
>> Sorry this made no difference either
>>
>> I’ve managed to video the relevant part of the screen when it crashes.
>> As previously stated I get “Loading initial ramdisk …” and then about
>> a second later I get
>>
>>>
> Code:
> --------------------
> > >
> > EFI stub: Booting Linux Kernel…
> > “Synchronous Abort” handler, esr 0x96000044
> > ELR: 26bd0f00
> > LR: 26bd0fe4
> >
> --------------------
>>>
>>
>> and then a list for values from x0 to at least x19, each with a hex
>> value
>>
>> Thanks
>>
>> Paul
>>
>> On 14/01/2019 18:22, malcolmlewis wrote:
>>>
>>> Hi
>>> Since it’s also missing this, swiotlb=512 can you add that as well
>> and
>>> rebuild.
>>>
> Hi
> So can you post the full output from the grub command line?
>
> I wonder if removing the newer kernel and re-installing may kick things
> into life, else jump on IRC Freenode #opensuse-arm to see what the guys
> there have to say about your issue. Perhaps you can get a serial cable
> for the RPi? I use a PL2303HX USB to TTL to UART COM Cable, it would
> help a lot to get more info…
>
>
Hi
The cable will certainly help to try and figure out what’s up with the booting with that kernel, especially for any bug report… I don’t have a B+ only B’s so not sure I could duplicate. I’ll lay down a Leap 42.3 image maybe tomorrow night or Sunday and see if can duplicate anything.
Adapter arrived today. Below is the full output from an attempt to boot
165-81
U-Boot 2017.05 (May 08 2017 - 15:27:50 +0000)
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... 4 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
scanning usb for ethernet devices... 1 Ethernet Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
14974 bytes read in 153 ms (94.7 KiB/s)
Found EFI removable media binary efi/boot/bootaa64.efi
reading efi/boot/bootaa64.efi
124416 bytes read in 32 ms (3.7 MiB/s)
## Starting EFI application at 01000000 ...
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...
"Synchronous Abort" handler, esr 0x96000044
ELR: 26bc1f00
LR: 26bc1fe4
x0 : 0000000000000070 x1 : 0000000000000000
x2 : 0000000000000720 x3 : 0000000000000001
x4 : 0000000036b3aa98 x5 : 0000000000000000
x6 : 0000000000000000 x7 : 0000000036f85418
x8 : 0000000000000001 x9 : 0000000035b08000
x10: 000000000000ffff x11: 00000000ffffd800
x12: 00000000ffffdc00 x13: 00000000359bd4c0
x14: 0000000000000001 x15: 000000000000200c
x16: 0000000000000000 x17: 00000000fffffffe
x18: 0000000000000100 x19: 0000000036b2bad0
x20: ffff000008e37e30 x21: 0000000000000001
x22: 0000000035b07008 x23: 0000000036b3aae0
x24: 000000000000002c x25: 0000000036b2b9e8
x26: 0000000036f87518 x27: 0000000000000000
x28: 0000000000000001 x29: 0000000036b2b900
Resetting CPU ...
resetting ...
Hope that helps and if you need anything further please ask
Thanks
Paul
On 18/01/2019 04:06, malcolmlewis wrote:
>
> Paul;2891788 Wrote:
>>
>> I can order a serial cable but it won’t be here for couple of days.
>> There’s nowhere around here that I can go to and buy one
>>
> Hi
> The cable will certainly help to try and figure out what’s up with the
> booting with that kernel, especially for any bug report… I don’t have
> a B+ only B’s so not sure I could duplicate. I’ll lay down a Leap 42.3
> image maybe tomorrow night or Sunday and see if can duplicate anything.
>
>
Adapter arrived today. Below is the full output from an attempt to boot
165-81
U-Boot 2017.05 (May 08 2017 - 15:27:50 +0000)
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… 4 USB Device(s) found
scanning usb for storage devices… 0 Storage Device(s) found
scanning usb for ethernet devices… 1 Ethernet Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
14974 bytes read in 153 ms (94.7 KiB/s)
Found EFI removable media binary efi/boot/bootaa64.efi
reading efi/boot/bootaa64.efi
124416 bytes read in 32 ms (3.7 MiB/s)
Starting EFI application at 01000000 …
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!
Hi
Can you confirm the original image name/version etc you put onto the SD
card?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Is there a file I can check for this information? If not then I think I
used
openSUSE-Leap42.3-ARM-XFCE-raspberrypi3.aarch64-2017.07.26-Build1.1.raw.xz
Thanks
Paul
On 22/01/2019 14:21, malcolmlewis wrote:
> Hi
> Can you confirm the original image name/version etc you put onto the SD
> card?
>
Is there a file I can check for this information? If not then I think I
used
openSUSE-Leap42.3-ARM-XFCE-raspberrypi3.aarch64-2017.07.26-Build1.1.raw.xz
Thanks
Paul
On 22/01/2019 14:21, malcolmlewis wrote:
> Hi
> Can you confirm the original image name/version etc you put onto the
> SD card?
>
Hi
Can you post the output from;
zypper lr -d
Hopefully they all point to ports repositories…
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Repository priorities are without effect. All enabled repositories share
the same priority.
# | Alias | Name
| Enabled | GPG Check | Refresh | Priority | Type | URI
| Service
--+-----------------------------------+-----------------------------------+---------+-----------+---------+----------+--------+-----------------------------------------------------------------------------+--------
1 | openSUSE-Ports-Leap-42.3-Update | openSUSE-Ports-Leap-42.3-Update
| Yes | (r ) Yes | Yes | 99 | rpm-md |
http://download.opensuse.org/ports/update/leap/42.3/oss/
|
2 | openSUSE-Ports-Leap-42.3-repo-oss |
openSUSE-Ports-Leap-42.3-repo-oss | Yes | (r ) Yes | Yes | 99
| yast2 |
http://download.opensuse.org/ports/aarch64/distribution/leap/42.3/repo/oss/
|
Thanks
Paul
On 22/01/2019 15:27, malcolmlewis wrote:
On Tue 22 Jan 2019 01:32:22 PM CST, Paul wrote:
Is there a file I can check for this information? If not then I think I
used
openSUSE-Leap42.3-ARM-XFCE-raspberrypi3.aarch64-2017.07.26-Build1.1.raw.xz
Thanks
Paul
On 22/01/2019 14:21, malcolmlewis wrote:
Hi
Can you confirm the original image name/version etc you put onto the
SD card?
Hi
Can you post the output from;
> zypper lr -d
>
> Hopefully they all point to ports repositories…
>
