Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
On 1/23/20 9:08 AM, Andreas Schwab wrote: > On Jan 22 2020, Michael Ströder wrote: > >> Unfortunately only this messages are printed on screen even with loglevel=7: >> >> Loading Linux 5.4.10-1-default >> Loading initial ramdisk ... >> EFI stub: Booting Linux Kernel... >> EFI stub: Using DTB from configuration table >> EFI stub: Exiting boot services and installing virtual address map... > > You probably need earlycon to see more. I've added earlycon=pl011,0x20201000,115200n8 to the kernel parameter line. But no more log output. The complete line looks like this: linux /boot/zImage-5.4.10-1-default root=UUID=524bdedd-9576-4cff-9915-3059c7d19ccc loglevel=7 plymouth.enable=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200n8 kgdboc=ttyAMA0,115200 earlycon=pl011,0x20201000,115200n8 rootflags=commit=120,data=writeback root=UUID=524bdedd-9576-4cff-9915-3059c7d19ccc rw -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
On Jan 22 2020, Michael Ströder wrote: > Unfortunately only this messages are printed on screen even with loglevel=7: > > Loading Linux 5.4.10-1-default > Loading initial ramdisk ... > EFI stub: Booting Linux Kernel... > EFI stub: Using DTB from configuration table > EFI stub: Exiting boot services and installing virtual address map... You probably need earlycon to see more. Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
On 1/20/20 8:27 AM, Guillaume Gardet wrote: > IIRC, with grub 2.04 update, we need kernel 5.4+ for armv6. I see. > Could you boot with loglevel=7 and remove the 'quiet' option, please? > Hopefully, you should have more kernel traces to share. Unfortunately only this messages are printed on screen even with loglevel=7: Loading Linux 5.4.10-1-default Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... Ciao, Michael. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
RE: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
I created https://bugzilla.opensuse.org/show_bug.cgi?id=1161337 to track this
bug properly.
Guillaume
> -Original Message-
> From: Guillaume Gardet
> Sent: 20 January 2020 12:25
> To: Guillaume Gardet ; Michael Ströder
> ; Matthias Brugger ; openSUSE
> ARM ML
> Subject: RE: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
>
> For the record, it was tracked as
> http://bugzilla.suse.com/show_bug.cgi?id=1145646
>
> Matthias, any idea?
>
> Guillaume
>
> > -Original Message-
> > From: Guillaume Gardet
> > Sent: 20 January 2020 08:28
> > To: Michael Ströder ; Matthias Brugger
> > ; openSUSE ARM ML
> > Subject: RE: [opensuse-arm] RPI1 does not boot after Tumbleweed
> > upgrade
> >
> > Hi,
> >
> > > -Original Message-
> > > From: Michael Ströder
> > > Sent: 18 January 2020 16:51
> > > To: Guillaume Gardet ; Matthias Brugger
> > > ; openSUSE ARM ML
> > > Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed
> > > upgrade
> > >
> > > On 11/12/19 2:47 PM, Guillaume Gardet wrote:
> > > >> -Original Message-
> > > >> From: Matthias Brugger
> > > >> Sent: 08 November 2019 12:26
> > > >> To: Michael Ströder ; openSUSE ARM ML
> > > >>
> > > >> Cc: Guillaume Gardet
> > > >> Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed
> > > >> upgrade
> > > >>
> > > >> On 08/11/2019 12:14, Michael Ströder wrote:
> > > >>> I'm running Tumbleweed on RPI1 (armv6). It does not boot after
> > > >>> upgrade to kernel 5.3.x (tested versions 5.3.6..5.3.8). During
> > > >>> upgrade there were no error messages.
> > > >>>
> > > >>> It just hangs after this grub message:
> > > >>>
> > > >>> "Loading initial ramdisk ..."
> > > >>>
> > > >>> Booting into 5.2.14 via grub works correctly.
> > > >>>
> > > >>> Any idea what went wrong?
> > > >>
> > > >> No not yet. Guillaume was looking into this yesterday. At least
> > > >> now we have a data point from which to start bisecting (that
> > > >> would be my way of
> > > fixing this).
> > > >> Could you do that, or maybe Guillaume?
> > > >>
> > > >> I won't have time for this until at least next week.
> > > >
> > > > I tried kernel 5.4-rc7 from kernel:HEAD repo and it does boot properly.
> > > > I would suggest to lock kernel update for now until 5.4 reaches
> > > > Tumbleweed in
> > > some days/weeks.
> > >
> > > After today's upgrade to kernel 5.4.10 the boot hangs after grub
> > > with message
> > >
> > > "UEFI stub: Exiting boot services and installing virtual address map..."
> > >
> > > Booting into 5.2.14 also does not work anymore. Fails with an error
> > > message displayed shortly complaining about failure of memory
> > > allocation and jumps back to grub.
> >
> > IIRC, with grub 2.04 update, we need kernel 5.4+ for armv6.
> > Could you boot with loglevel=7 and remove the 'quiet' option, please?
> > Hopefully, you should have more kernel traces to share.
> >
> > Cheers,
> > Guillaume
> >
> >
> >
> > >
> > > Ciao, Michael.
> > IMPORTANT NOTICE: The contents of this email and any attachments are
> > confidential and may also be privileged. If you are not the intended
> > recipient, please notify the sender immediately and do not disclose
> > the contents to any other person, use it for any purpose, or store or
> > copy the information in any medium. Thank you.
> > IMPORTANT NOTICE: The contents of this email and any attachments are
> > confidential and may also be privileged. If you are not the intended
> > recipient, please notify the sender immediately and do not disclose
> > the contents to any other person, use it for any purpose, or store or
> > copy the information in any medium. Thank you.
> > N r y隊Z)z{. 櫛맲 r z ^ ˬz N ( ֜ ^ ޭ隊Z)z{. 櫛 0 Ǩ
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
RE: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
Hi,
> -Original Message-
> From: Michael Ströder
> Sent: 18 January 2020 16:51
> To: Guillaume Gardet ; Matthias Brugger
> ; openSUSE ARM ML
> Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
>
> On 11/12/19 2:47 PM, Guillaume Gardet wrote:
> >> -Original Message-
> >> From: Matthias Brugger
> >> Sent: 08 November 2019 12:26
> >> To: Michael Ströder ; openSUSE ARM ML
> >>
> >> Cc: Guillaume Gardet
> >> Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed
> >> upgrade
> >>
> >> On 08/11/2019 12:14, Michael Ströder wrote:
> >>> I'm running Tumbleweed on RPI1 (armv6). It does not boot after
> >>> upgrade to kernel 5.3.x (tested versions 5.3.6..5.3.8). During
> >>> upgrade there were no error messages.
> >>>
> >>> It just hangs after this grub message:
> >>>
> >>> "Loading initial ramdisk ..."
> >>>
> >>> Booting into 5.2.14 via grub works correctly.
> >>>
> >>> Any idea what went wrong?
> >>
> >> No not yet. Guillaume was looking into this yesterday. At least now
> >> we have a data point from which to start bisecting (that would be my way of
> fixing this).
> >> Could you do that, or maybe Guillaume?
> >>
> >> I won't have time for this until at least next week.
> >
> > I tried kernel 5.4-rc7 from kernel:HEAD repo and it does boot properly.
> > I would suggest to lock kernel update for now until 5.4 reaches Tumbleweed
> > in
> some days/weeks.
>
> After today's upgrade to kernel 5.4.10 the boot hangs after grub with message
>
> "UEFI stub: Exiting boot services and installing virtual address map..."
>
> Booting into 5.2.14 also does not work anymore. Fails with an error message
> displayed shortly complaining about failure of memory allocation and jumps
> back
> to grub.
IIRC, with grub 2.04 update, we need kernel 5.4+ for armv6.
Could you boot with loglevel=7 and remove the 'quiet' option, please?
Hopefully, you should have more kernel traces to share.
Cheers,
Guillaume
>
> Ciao, Michael.
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
N�r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0�Ǩ�
Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
On 11/12/19 2:47 PM, Guillaume Gardet wrote: >> -Original Message- >> From: Matthias Brugger >> Sent: 08 November 2019 12:26 >> To: Michael Ströder ; openSUSE ARM ML > a...@opensuse.org> >> Cc: Guillaume Gardet >> Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade >> >> On 08/11/2019 12:14, Michael Ströder wrote: >>> I'm running Tumbleweed on RPI1 (armv6). It does not boot after upgrade >>> to kernel 5.3.x (tested versions 5.3.6..5.3.8). During upgrade there >>> were no error messages. >>> >>> It just hangs after this grub message: >>> >>> "Loading initial ramdisk ..." >>> >>> Booting into 5.2.14 via grub works correctly. >>> >>> Any idea what went wrong? >> >> No not yet. Guillaume was looking into this yesterday. At least now we have a >> data point from which to start bisecting (that would be my way of fixing >> this). >> Could you do that, or maybe Guillaume? >> >> I won't have time for this until at least next week. > > I tried kernel 5.4-rc7 from kernel:HEAD repo and it does boot properly. > I would suggest to lock kernel update for now until 5.4 reaches Tumbleweed in > some days/weeks. After today's upgrade to kernel 5.4.10 the boot hangs after grub with message "UEFI stub: Exiting boot services and installing virtual address map..." Booting into 5.2.14 also does not work anymore. Fails with an error message displayed shortly complaining about failure of memory allocation and jumps back to grub. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
RE: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
Hi, > -Original Message- > From: Matthias Brugger > Sent: 08 November 2019 12:26 > To: Michael Ströder ; openSUSE ARM ML a...@opensuse.org> > Cc: Guillaume Gardet > Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade > > Hi Michael, > > On 08/11/2019 12:14, Michael Ströder wrote: > > HI! > > > > I'm running Tumbleweed on RPI1 (armv6). It does not boot after upgrade > > to kernel 5.3.x (tested versions 5.3.6..5.3.8). During upgrade there > > were no error messages. > > > > It just hangs after this grub message: > > > > "Loading initial ramdisk ..." > > > > Booting into 5.2.14 via grub works correctly. > > > > Any idea what went wrong? > > > > No not yet. Guillaume was looking into this yesterday. At least now we have a > data point from which to start bisecting (that would be my way of fixing > this). > Could you do that, or maybe Guillaume? > > I won't have time for this until at least next week. I tried kernel 5.4-rc7 from kernel:HEAD repo and it does boot properly. I would suggest to lock kernel update for now until 5.4 reaches Tumbleweed in some days/weeks. Guillaume > > Regards, > Matthias IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
Hi Michael, On 08/11/2019 12:14, Michael Ströder wrote: > HI! > > I'm running Tumbleweed on RPI1 (armv6). It does not boot after upgrade > to kernel 5.3.x (tested versions 5.3.6..5.3.8). During upgrade there > were no error messages. > > It just hangs after this grub message: > > "Loading initial ramdisk ..." > > Booting into 5.2.14 via grub works correctly. > > Any idea what went wrong? > No not yet. Guillaume was looking into this yesterday. At least now we have a data point from which to start bisecting (that would be my way of fixing this). Could you do that, or maybe Guillaume? I won't have time for this until at least next week. Regards, Matthias -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
RE: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
Hi, > -Original Message- > From: Michael Ströder > Sent: 08 November 2019 12:15 > To: openSUSE ARM ML > Subject: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade > > HI! > > I'm running Tumbleweed on RPI1 (armv6). It does not boot after upgrade to > kernel 5.3.x (tested versions 5.3.6..5.3.8). During upgrade there were no > error > messages. > > It just hangs after this grub message: > > "Loading initial ramdisk ..." > > Booting into 5.2.14 via grub works correctly. Thanks for pointing the faulty part. > > Any idea what went wrong? We probably need to check updates on config first: https://kernel.opensuse.org/cgit/kernel-source/log/config/armv6hl/default?h=stable And then, we may need to bisect kernel updates. Cheers, Guillaume > > Ciao, Michael. > -- > To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org > To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
[opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
HI! I'm running Tumbleweed on RPI1 (armv6). It does not boot after upgrade to kernel 5.3.x (tested versions 5.3.6..5.3.8). During upgrade there were no error messages. It just hangs after this grub message: "Loading initial ramdisk ..." Booting into 5.2.14 via grub works correctly. Any idea what went wrong? Ciao, Michael. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
RE: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
Hi,
> -Original Message-
> From: Guillaume Gardet
> Sent: 12 September 2019 10:04
> To: Michael Ströder ; opensuse-arm@opensuse.org
> Subject: RE: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
>
>
>
> > -Original Message-
> > From: Michael Ströder
> > Sent: 11 September 2019 20:44
> > To: opensuse-arm@opensuse.org
> > Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed
> > upgrade
> >
> > On 9/11/19 8:31 PM, Freek de Kruijf wrote:
> > > Op woensdag 11 september 2019 20:26:41 CEST schreef Freek de Kruijf:
> > >> I did have the same problem as Michael. After a "zypper dup --no-r"
> > >> the system did not boot anymore. I used the serial connection with
> > >> the RPi1 and there was no output at all.
> > >>
> > >> So I did check the content of the first partition on the SD. It did
> > >> lack the
> > >> 6 files present in: raspberrypi-firmware-2019.09.04-1.1.noarch.rpm
> > >> On my desktop I unpacked these files and put them on the first partition.
> > >> After that the system boots again.
> > >>
> > >> The question is: why were these files removed in the upgrade?
> > >
> > > I found also the answer:
> > > they are wrongly placed in /boot/vc/ instead of /boot/efi/ .
> >
> > I can confirm that manually copying the files fixed booting. Thanks.
> >
> > And as Freek I also suspect /boot/vc/ is wrong path because package
> > raspberrypi-firmware-2019.09.04-1.1.noarch is installed but 1.
> > partition is mounted on /boot/efi/.
>
> The files should be copied to the right location, see:
> https://bugzilla.opensuse.org/show_bug.cgi?id=1150408#c1
An update is available on Tumbleweed update channel:
http://download.opensuse.org/ports/aarch64/update/tumbleweed/
or
http://download.opensuse.org/ports/armv7hl/update/tumbleweed/
http://download.opensuse.org/ports/armv6hl/update/tumbleweed/
Depending on you architecture.
Please make sure to have this update channel in your repositories list and
remove old raspberrypi-firmware and install it again ( do NOT use zypper update
or zypper dup):
zypper rm raspberrypi-firmware
zypper in raspberrypi-firmware
Thanks,
Guillaume
N�r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0�Ǩ�
RE: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
> -Original Message-
> From: Michael Ströder
> Sent: 11 September 2019 20:44
> To: opensuse-arm@opensuse.org
> Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
>
> On 9/11/19 8:31 PM, Freek de Kruijf wrote:
> > Op woensdag 11 september 2019 20:26:41 CEST schreef Freek de Kruijf:
> >> I did have the same problem as Michael. After a "zypper dup --no-r"
> >> the system did not boot anymore. I used the serial connection with
> >> the RPi1 and there was no output at all.
> >>
> >> So I did check the content of the first partition on the SD. It did
> >> lack the
> >> 6 files present in: raspberrypi-firmware-2019.09.04-1.1.noarch.rpm
> >> On my desktop I unpacked these files and put them on the first partition.
> >> After that the system boots again.
> >>
> >> The question is: why were these files removed in the upgrade?
> >
> > I found also the answer:
> > they are wrongly placed in /boot/vc/ instead of /boot/efi/ .
>
> I can confirm that manually copying the files fixed booting. Thanks.
>
> And as Freek I also suspect /boot/vc/ is wrong path because package
> raspberrypi-firmware-2019.09.04-1.1.noarch is installed but 1. partition is
> mounted on /boot/efi/.
The files should be copied to the right location, see:
https://bugzilla.opensuse.org/show_bug.cgi?id=1150408#c1
Cheers,
Guillaume
>
> Ciao, Michael.
> --
> To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
> To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
N�r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0�Ǩ�
Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
On 9/11/19 8:31 PM, Freek de Kruijf wrote: Op woensdag 11 september 2019 20:26:41 CEST schreef Freek de Kruijf: I did have the same problem as Michael. After a "zypper dup --no-r" the system did not boot anymore. I used the serial connection with the RPi1 and there was no output at all. So I did check the content of the first partition on the SD. It did lack the 6 files present in: raspberrypi-firmware-2019.09.04-1.1.noarch.rpm On my desktop I unpacked these files and put them on the first partition. After that the system boots again. The question is: why were these files removed in the upgrade? I found also the answer: they are wrongly placed in /boot/vc/ instead of /boot/efi/ . I can confirm that manually copying the files fixed booting. Thanks. And as Freek I also suspect /boot/vc/ is wrong path because package raspberrypi-firmware-2019.09.04-1.1.noarch is installed but 1. partition is mounted on /boot/efi/. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
Op woensdag 11 september 2019 20:31:16 CEST schreef Freek de Kruijf: > Op woensdag 11 september 2019 20:26:41 CEST schreef Freek de Kruijf: > > I did have the same problem as Michael. After a "zypper dup --no-r" the > > system did not boot anymore. I used the serial connection with the RPi1 > > and > > there was no output at all. > > > > So I did check the content of the first partition on the SD. It did lack > > the 6 files present in: raspberrypi-firmware-2019.09.04-1.1.noarch.rpm On > > my desktop I unpacked these files and put them on the first partition. > > After that the system boots again. > > > > The question is: why were these files removed in the upgrade? > > I found also the answer: > they are wrongly placed in /boot/vc/ instead of /boot/efi/ . Bugzilla #1150408 -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
Op woensdag 11 september 2019 20:26:41 CEST schreef Freek de Kruijf: > I did have the same problem as Michael. After a "zypper dup --no-r" the > system did not boot anymore. I used the serial connection with the RPi1 and > there was no output at all. > > So I did check the content of the first partition on the SD. It did lack the > 6 files present in: raspberrypi-firmware-2019.09.04-1.1.noarch.rpm > On my desktop I unpacked these files and put them on the first partition. > After that the system boots again. > > The question is: why were these files removed in the upgrade? I found also the answer: they are wrongly placed in /boot/vc/ instead of /boot/efi/ . -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
On Wed, 11 Sep 2019 20:26:41 +0200 Freek de Kruijf wrote: > Op woensdag 11 september 2019 16:36:53 CEST schreef Guillaume Gardet: > > > -Original Message- > > > From: Michael Ströder > > > Sent: 11 September 2019 16:17 > > > To: Guillaume Gardet ; openSUSE ARM ML > > > > > > Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade > > > > > > > > > > > > On 9/11/19 3:53 PM, Guillaume Gardet wrote: > > > > > > >> From: Michael Ströder > > > >> Sent: 11 September 2019 13:55 > > > >> > > > >> > > > >> > > > >> On 9/11/19 1:47 PM, Guillaume Gardet wrote: > > > >> > > > >>>> -Original Message- > > > >>>> From: Michael Ströder > > > >>>> Sent: 11 September 2019 13:34 > > > >>>> > > > >>>> > > > >>>> > > > >>>> I'm running Tumbleweed on RPI1 (armv6). It does not boot after last > > > >>>> upgrade to kernel from 5.2.10 to 5.2.13. During upgrade there were > > > >>>> no error messages. > > > >>> > > > >>> > > > >>> > > > >>> Did you update the kernel only, or the whole distribution (maybe > > > >>> including > > > >> > > > >> firmware)? > > > >> > > > >> > > > >> > > > >> I did the usual full upgrade with > > > >> zypper dup -l --no-allow-vendor-change --no-recommends > > > > > > > > > > > > > > > > Did you run out of space, maybe? > > > > > > > > > > > > No. There's plenty of space on the partitions: > > > - The firmware partition still has 15MB available and 1.5M used. > > > - On the OS partition (where's /boot) 4.9GB are still available. > > > > > > > > > > > > > If the rainbow screen is not display, this means that the firmware is > > > > not > > > > > > loaded/started properly. > > > > > > > IIRC, there was a firmware update with latest snapshot. > > > > > > > > > > > > Can I check whether the firmware files are complete? > > > > > > I read again your 1st email and it seems that you are missing the firmware > > files on the 1st partition of your SD card. > My list: > > total 6340 > > drwxr-xr-x 3 root root2048 Sep 8 21:15 EFI > > -rwxr-xr-x 1 root root 28432 Sep 7 13:21 bcm2708-rpi-b-plus.dtb > > -rwxr-xr-x 1 root root 28173 Sep 7 13:21 bcm2708-rpi-b.dtb > > -rwxr-xr-x 1 root root 27950 Sep 7 13:21 bcm2708-rpi-cm.dtb > > -rwxr-xr-x 1 root root 28634 Sep 7 13:21 bcm2708-rpi-zero-w.dtb > > -rwxr-xr-x 1 root root 27898 Sep 7 13:21 bcm2708-rpi-zero.dtb > > -rwxr-xr-x 1 root root 29520 Sep 7 13:21 bcm2709-rpi-2-b.dtb > > -rwxr-xr-x 1 root root 31325 Sep 7 13:21 bcm2710-rpi-3-b-plus.dtb > > -rwxr-xr-x 1 root root 30706 Sep 7 13:21 bcm2710-rpi-3-b.dtb > > -rwxr-xr-x 1 root root 29504 Sep 7 13:21 bcm2710-rpi-cm3.dtb > > -rwxr-xr-x 1 root root 44472 Sep 7 13:21 bcm2711-rpi-4-b.dtb > > -rwxr-xr-x 1 root root 52296 Sep 4 12:07 bootcode.bin > > -rwxr-xr-x 1 root root1476 Nov 30 2018 config.txt > > -rwxr-xr-x 1 root root6736 Sep 4 12:07 fixup.dat > > -rwxr-xr-x 1 root root6092 Sep 4 12:07 fixup4.dat > > drwxr-xr-x 2 root root 16384 Sep 8 21:01 overlays > > -rwxr-xr-x 1 root root 2877892 Sep 4 12:07 start.elf > > -rwxr-xr-x 1 root root 2762820 Sep 4 12:07 start4.elf > > -rwxr-xr-x 1 root root 8 Sep 8 21:16 startup.nsh > > -rwxr-xr-x 1 root root 443036 Jul 18 12:21 u-boot.bin > > > > You can get them from the raspberrypi-firmware package: > > http://download.opensuse.org/ports/armv6hl/tumbleweed/repo/oss/noarch/raspb > > errypi-firmware-2019.09.04-1.1.noarch.rpm > You can use ark or 7zip (any > > other archive extractor) to extract the files from this RPM. > > I tried the latest JeOS-raspberrypi image for RPi1 from > > http://download.opensuse.org/ports/armv6hl/tumbleweed/images/openSUSE-Tumbl > > eweed-ARM-JeOS-raspberrypi.armv6l-2019.09.04-Snapshot20190907.raw.xz and I > > have no problem. > > > Cheers, > > Guillaume > > I did have the same problem as Michael. After a "zypper dup --no-r" the > system > did not boot anymore. I used the serial connection with the RPi1 and there > was > no output at all. > > So I did check the content of the first partition on the SD. It did lack the > 6 > files present in: raspberrypi-firmware-2019.09.04-1.1.noarch.rpm > On my desktop I unpacked these files and put them on the first partition. > After that the system boots again. > > The question is: why were these files removed in the upgrade? > Probably some pattern/dependency change broke this. Thanks Michal -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
Op woensdag 11 september 2019 16:36:53 CEST schreef Guillaume Gardet: > > -Original Message- > > From: Michael Ströder > > Sent: 11 September 2019 16:17 > > To: Guillaume Gardet ; openSUSE ARM ML > > > > Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade > > > > > > > > On 9/11/19 3:53 PM, Guillaume Gardet wrote: > > > > >> From: Michael Ströder > > >> Sent: 11 September 2019 13:55 > > >> > > >> > > >> > > >> On 9/11/19 1:47 PM, Guillaume Gardet wrote: > > >> > > >>>> -Original Message- > > >>>> From: Michael Ströder > > >>>> Sent: 11 September 2019 13:34 > > >>>> > > >>>> > > >>>> > > >>>> I'm running Tumbleweed on RPI1 (armv6). It does not boot after last > > >>>> upgrade to kernel from 5.2.10 to 5.2.13. During upgrade there were > > >>>> no error messages. > > >>> > > >>> > > >>> > > >>> Did you update the kernel only, or the whole distribution (maybe > > >>> including > > >> > > >> firmware)? > > >> > > >> > > >> > > >> I did the usual full upgrade with > > >> zypper dup -l --no-allow-vendor-change --no-recommends > > > > > > > > > > > > Did you run out of space, maybe? > > > > > > > > No. There's plenty of space on the partitions: > > - The firmware partition still has 15MB available and 1.5M used. > > - On the OS partition (where's /boot) 4.9GB are still available. > > > > > > > > > If the rainbow screen is not display, this means that the firmware is > > > not > > > > loaded/started properly. > > > > > IIRC, there was a firmware update with latest snapshot. > > > > > > > > Can I check whether the firmware files are complete? > > > I read again your 1st email and it seems that you are missing the firmware > files on the 1st partition of your SD card. My list: > total 6340 > drwxr-xr-x 3 root root2048 Sep 8 21:15 EFI > -rwxr-xr-x 1 root root 28432 Sep 7 13:21 bcm2708-rpi-b-plus.dtb > -rwxr-xr-x 1 root root 28173 Sep 7 13:21 bcm2708-rpi-b.dtb > -rwxr-xr-x 1 root root 27950 Sep 7 13:21 bcm2708-rpi-cm.dtb > -rwxr-xr-x 1 root root 28634 Sep 7 13:21 bcm2708-rpi-zero-w.dtb > -rwxr-xr-x 1 root root 27898 Sep 7 13:21 bcm2708-rpi-zero.dtb > -rwxr-xr-x 1 root root 29520 Sep 7 13:21 bcm2709-rpi-2-b.dtb > -rwxr-xr-x 1 root root 31325 Sep 7 13:21 bcm2710-rpi-3-b-plus.dtb > -rwxr-xr-x 1 root root 30706 Sep 7 13:21 bcm2710-rpi-3-b.dtb > -rwxr-xr-x 1 root root 29504 Sep 7 13:21 bcm2710-rpi-cm3.dtb > -rwxr-xr-x 1 root root 44472 Sep 7 13:21 bcm2711-rpi-4-b.dtb > -rwxr-xr-x 1 root root 52296 Sep 4 12:07 bootcode.bin > -rwxr-xr-x 1 root root1476 Nov 30 2018 config.txt > -rwxr-xr-x 1 root root6736 Sep 4 12:07 fixup.dat > -rwxr-xr-x 1 root root6092 Sep 4 12:07 fixup4.dat > drwxr-xr-x 2 root root 16384 Sep 8 21:01 overlays > -rwxr-xr-x 1 root root 2877892 Sep 4 12:07 start.elf > -rwxr-xr-x 1 root root 2762820 Sep 4 12:07 start4.elf > -rwxr-xr-x 1 root root 8 Sep 8 21:16 startup.nsh > -rwxr-xr-x 1 root root 443036 Jul 18 12:21 u-boot.bin > > You can get them from the raspberrypi-firmware package: > http://download.opensuse.org/ports/armv6hl/tumbleweed/repo/oss/noarch/raspb > errypi-firmware-2019.09.04-1.1.noarch.rpm You can use ark or 7zip (any > other archive extractor) to extract the files from this RPM. > I tried the latest JeOS-raspberrypi image for RPi1 from > http://download.opensuse.org/ports/armv6hl/tumbleweed/images/openSUSE-Tumbl > eweed-ARM-JeOS-raspberrypi.armv6l-2019.09.04-Snapshot20190907.raw.xz and I > have no problem. > Cheers, > Guillaume I did have the same problem as Michael. After a "zypper dup --no-r" the system did not boot anymore. I used the serial connection with the RPi1 and there was no output at all. So I did check the content of the first partition on the SD. It did lack the 6 files present in: raspberrypi-firmware-2019.09.04-1.1.noarch.rpm On my desktop I unpacked these files and put them on the first partition. After that the system boots again. The question is: why were these files removed in the upgrade? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
RE: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
> -Original Message- > From: Michael Ströder > Sent: 11 September 2019 16:17 > To: Guillaume Gardet ; openSUSE ARM ML > > Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade > > On 9/11/19 3:53 PM, Guillaume Gardet wrote: > >> From: Michael Ströder > >> Sent: 11 September 2019 13:55 > >> > >> On 9/11/19 1:47 PM, Guillaume Gardet wrote: > >>>> -Original Message- > >>>> From: Michael Ströder > >>>> Sent: 11 September 2019 13:34 > >>>> > >>>> I'm running Tumbleweed on RPI1 (armv6). It does not boot after last > >>>> upgrade to kernel from 5.2.10 to 5.2.13. During upgrade there were > >>>> no error messages. > >>> > >>> Did you update the kernel only, or the whole distribution (maybe > >>> including > >> firmware)? > >> > >> I did the usual full upgrade with > >> zypper dup -l --no-allow-vendor-change --no-recommends > > > > Did you run out of space, maybe? > > No. There's plenty of space on the partitions: > - The firmware partition still has 15MB available and 1.5M used. > - On the OS partition (where's /boot) 4.9GB are still available. > > > If the rainbow screen is not display, this means that the firmware is not > loaded/started properly. > > IIRC, there was a firmware update with latest snapshot. > > Can I check whether the firmware files are complete? I read again your 1st email and it seems that you are missing the firmware files on the 1st partition of your SD card. My list: total 6340 drwxr-xr-x 3 root root2048 Sep 8 21:15 EFI -rwxr-xr-x 1 root root 28432 Sep 7 13:21 bcm2708-rpi-b-plus.dtb -rwxr-xr-x 1 root root 28173 Sep 7 13:21 bcm2708-rpi-b.dtb -rwxr-xr-x 1 root root 27950 Sep 7 13:21 bcm2708-rpi-cm.dtb -rwxr-xr-x 1 root root 28634 Sep 7 13:21 bcm2708-rpi-zero-w.dtb -rwxr-xr-x 1 root root 27898 Sep 7 13:21 bcm2708-rpi-zero.dtb -rwxr-xr-x 1 root root 29520 Sep 7 13:21 bcm2709-rpi-2-b.dtb -rwxr-xr-x 1 root root 31325 Sep 7 13:21 bcm2710-rpi-3-b-plus.dtb -rwxr-xr-x 1 root root 30706 Sep 7 13:21 bcm2710-rpi-3-b.dtb -rwxr-xr-x 1 root root 29504 Sep 7 13:21 bcm2710-rpi-cm3.dtb -rwxr-xr-x 1 root root 44472 Sep 7 13:21 bcm2711-rpi-4-b.dtb -rwxr-xr-x 1 root root 52296 Sep 4 12:07 bootcode.bin -rwxr-xr-x 1 root root1476 Nov 30 2018 config.txt -rwxr-xr-x 1 root root6736 Sep 4 12:07 fixup.dat -rwxr-xr-x 1 root root6092 Sep 4 12:07 fixup4.dat drwxr-xr-x 2 root root 16384 Sep 8 21:01 overlays -rwxr-xr-x 1 root root 2877892 Sep 4 12:07 start.elf -rwxr-xr-x 1 root root 2762820 Sep 4 12:07 start4.elf -rwxr-xr-x 1 root root 8 Sep 8 21:16 startup.nsh -rwxr-xr-x 1 root root 443036 Jul 18 12:21 u-boot.bin You can get them from the raspberrypi-firmware package: http://download.opensuse.org/ports/armv6hl/tumbleweed/repo/oss/noarch/raspberrypi-firmware-2019.09.04-1.1.noarch.rpm You can use ark or 7zip (any other archive extractor) to extract the files from this RPM. I tried the latest JeOS-raspberrypi image for RPi1 from http://download.opensuse.org/ports/armv6hl/tumbleweed/images/openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2019.09.04-Snapshot20190907.raw.xz and I have no problem. Cheers, Guillaume > > > I have some RPi1 on my desk, I will try to have a look by the end of the > week. > > Thank you. > > Ciao, Michael. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
On 9/11/19 3:53 PM, Guillaume Gardet wrote: From: Michael Ströder Sent: 11 September 2019 13:55 On 9/11/19 1:47 PM, Guillaume Gardet wrote: -Original Message- From: Michael Ströder Sent: 11 September 2019 13:34 I'm running Tumbleweed on RPI1 (armv6). It does not boot after last upgrade to kernel from 5.2.10 to 5.2.13. During upgrade there were no error messages. Did you update the kernel only, or the whole distribution (maybe including firmware)? I did the usual full upgrade with zypper dup -l --no-allow-vendor-change --no-recommends Did you run out of space, maybe? No. There's plenty of space on the partitions: - The firmware partition still has 15MB available and 1.5M used. - On the OS partition (where's /boot) 4.9GB are still available. If the rainbow screen is not display, this means that the firmware is not loaded/started properly. > IIRC, there was a firmware update with latest snapshot. Can I check whether the firmware files are complete? I have some RPi1 on my desk, I will try to have a look by the end of the week. Thank you. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
RE: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
> -Original Message- > From: Michael Ströder > Sent: 11 September 2019 13:55 > To: Guillaume Gardet ; openSUSE ARM ML > > Subject: Re: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade > > On 9/11/19 1:47 PM, Guillaume Gardet wrote: > >> -Original Message- > >> From: Michael Ströder > >> Sent: 11 September 2019 13:34 > >> > >> I'm running Tumbleweed on RPI1 (armv6). It does not boot after last > >> upgrade to kernel from 5.2.10 to 5.2.13. During upgrade there were no > >> error messages. > > > > Did you update the kernel only, or the whole distribution (maybe including > firmware)? > > I did the usual full upgrade with > zypper dup -l --no-allow-vendor-change --no-recommends Did you run out of space, maybe? > > In former failure cases some links to dtb files were missing after an > upgrade in /boot. There are no dtb files in /boot anymore. > > > By boot screen, you mean: > > a. the rainbow screen > > b. u-boot steps > > c. grub screen > > ? > > None of them is displayed. If the rainbow screen is not display, this means that the firmware is not loaded/started properly. IIRC, there was a firmware update with latest snapshot. I have some RPi1 on my desk, I will try to have a look by the end of the week. Cheers, Guillaume > > > Do you have a serial connection? > > Unfortunately not. > > Ciao, Michael. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
RE: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
Hi, > -Original Message- > From: Michael Ströder > Sent: 11 September 2019 13:34 > To: openSUSE ARM ML > Subject: [opensuse-arm] RPI1 does not boot after Tumbleweed upgrade > > HI! > > I'm running Tumbleweed on RPI1 (armv6). It does not boot after last > upgrade to kernel from 5.2.10 to 5.2.13. During upgrade there were no > error messages. Did you update the kernel only, or the whole distribution (maybe including firmware)? > > At first glance the content of /boot and the firmware partition (ls of > both appended below) looks ok to me. But it does not show the boot screen. By boot screen, you mean: a. the rainbow screen b. u-boot steps c. grub screen ? Do you have a serial connection? Cheers, Guillaume > > Any idea what went wrong? > > Ciao, Michael. > > -- /boot --- > -rw-r--r-- 1 root root 65 Aug 25 14:00 .zImage-5.2.10-1-default.hmac > -rw-r--r-- 1 root root 65 Sep 7 00:46 .zImage-5.2.13-1-default.hmac > -rw-r--r-- 1 root root 2804018 Aug 25 14:00 System.map-5.2.10-1-default > -rw-r--r-- 1 root root 2804143 Sep 7 00:13 System.map-5.2.13-1-default > -rw-r--r-- 1 root root 1725 Jul 31 14:24 boot.readme > -rw-r--r-- 1 root root 181536 Aug 25 14:00 config-5.2.10-1-default > -rw-r--r-- 1 root root 181536 Sep 6 22:45 config-5.2.13-1-default > -rw-r--r-- 1 root root0 Sep 10 14:37 do_purge_kernels > drwxr-xr-x 2 root root 4096 Nov 30 2018 efi/ > drwxr-xr-x 6 root root 4096 Sep 10 14:48 grub2/ > lrwxrwxrwx 1 root root 23 Sep 10 14:37 initrd -> > initrd-5.2.13-1-default > -rw--- 1 root root 13740612 Sep 10 14:45 initrd-5.2.10-1-default > -rw--- 1 root root 13741540 Sep 10 14:48 initrd-5.2.13-1-default > -rw-r--r-- 1 root root 11 Nov 30 2018 mbrid > -rw-r--r-- 1 root root 306143 Aug 25 14:00 symvers-5.2.10-1-default.gz > -rw-r--r-- 1 root root 306154 Sep 7 00:19 symvers-5.2.13-1-default.gz > -rw-r--r-- 1 root root 207 Aug 25 14:00 sysctl.conf-5.2.10-1-default > -rw-r--r-- 1 root root 207 Sep 7 00:19 sysctl.conf-5.2.13-1-default > -rw-r--r-- 1 root root 1484762 Nov 30 2018 unicode.pf2 > drwxr-xr-x 3 root root 4096 Sep 10 14:35 vc/ > -rw-r--r-- 1 root root 7443992 Aug 25 14:00 vmlinux-5.2.10-1-default.gz > -rw-r--r-- 1 root root 7447454 Sep 7 00:25 vmlinux-5.2.13-1-default.gz > lrwxrwxrwx 1 root root 23 Sep 10 14:37 zImage -> > zImage-5.2.13-1-default > -rw-r--r-- 1 root root 6187360 Aug 25 14:00 zImage-5.2.10-1-default > -rw-r--r-- 1 root root 6187360 Sep 7 00:46 zImage-5.2.13-1-default > > --- /dev/sdb1 --- > drwxr-xr-x 4 root root 16384 Jan 1 1970 ./ > drwxr-xr-x 18 root root 4096 Sep 7 11:58 ../ > drwxr-xr-x 3 root root 2048 Nov 30 2018 EFI/ > -rwxr-xr-x 1 root root 27529 Jul 28 20:57 bcm2708-rpi-0-w.dtb* > -rwxr-xr-x 1 root root 28432 Sep 10 14:35 bcm2708-rpi-b-plus.dtb* > -rwxr-xr-x 1 root root 28173 Sep 10 14:35 bcm2708-rpi-b.dtb* > -rwxr-xr-x 1 root root 27950 Sep 10 14:35 bcm2708-rpi-cm.dtb* > -rwxr-xr-x 1 root root 28634 Sep 10 14:35 bcm2708-rpi-zero-w.dtb* > -rwxr-xr-x 1 root root 27898 Sep 10 14:35 bcm2708-rpi-zero.dtb* > -rwxr-xr-x 1 root root 29520 Sep 10 14:35 bcm2709-rpi-2-b.dtb* > -rwxr-xr-x 1 root root 31325 Sep 10 14:35 bcm2710-rpi-3-b-plus.dtb* > -rwxr-xr-x 1 root root 30706 Sep 10 14:35 bcm2710-rpi-3-b.dtb* > -rwxr-xr-x 1 root root 29504 Sep 10 14:35 bcm2710-rpi-cm3.dtb* > -rwxr-xr-x 1 root root 44472 Sep 10 14:35 bcm2711-rpi-4-b.dtb* > -rwxr-xr-x 1 root root 1476 Sep 10 14:35 config.txt* > -rwxr-xr-x 1 root root 1476 Sep 10 14:35 config.txt.rpmsave* > drwxr-xr-x 2 root root 16384 Sep 10 14:35 overlays/ > -rwxr-xr-x 1 root root 8 Nov 30 2018 startup.nsh* > -rwxr-xr-x 1 root root 443036 Jul 28 20:54 u-boot.bin* IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
[opensuse-arm] RPI1 does not boot after Tumbleweed upgrade
HI! I'm running Tumbleweed on RPI1 (armv6). It does not boot after last upgrade to kernel from 5.2.10 to 5.2.13. During upgrade there were no error messages. At first glance the content of /boot and the firmware partition (ls of both appended below) looks ok to me. But it does not show the boot screen. Any idea what went wrong? Ciao, Michael. -- /boot --- -rw-r--r-- 1 root root 65 Aug 25 14:00 .zImage-5.2.10-1-default.hmac -rw-r--r-- 1 root root 65 Sep 7 00:46 .zImage-5.2.13-1-default.hmac -rw-r--r-- 1 root root 2804018 Aug 25 14:00 System.map-5.2.10-1-default -rw-r--r-- 1 root root 2804143 Sep 7 00:13 System.map-5.2.13-1-default -rw-r--r-- 1 root root 1725 Jul 31 14:24 boot.readme -rw-r--r-- 1 root root 181536 Aug 25 14:00 config-5.2.10-1-default -rw-r--r-- 1 root root 181536 Sep 6 22:45 config-5.2.13-1-default -rw-r--r-- 1 root root0 Sep 10 14:37 do_purge_kernels drwxr-xr-x 2 root root 4096 Nov 30 2018 efi/ drwxr-xr-x 6 root root 4096 Sep 10 14:48 grub2/ lrwxrwxrwx 1 root root 23 Sep 10 14:37 initrd -> initrd-5.2.13-1-default -rw--- 1 root root 13740612 Sep 10 14:45 initrd-5.2.10-1-default -rw--- 1 root root 13741540 Sep 10 14:48 initrd-5.2.13-1-default -rw-r--r-- 1 root root 11 Nov 30 2018 mbrid -rw-r--r-- 1 root root 306143 Aug 25 14:00 symvers-5.2.10-1-default.gz -rw-r--r-- 1 root root 306154 Sep 7 00:19 symvers-5.2.13-1-default.gz -rw-r--r-- 1 root root 207 Aug 25 14:00 sysctl.conf-5.2.10-1-default -rw-r--r-- 1 root root 207 Sep 7 00:19 sysctl.conf-5.2.13-1-default -rw-r--r-- 1 root root 1484762 Nov 30 2018 unicode.pf2 drwxr-xr-x 3 root root 4096 Sep 10 14:35 vc/ -rw-r--r-- 1 root root 7443992 Aug 25 14:00 vmlinux-5.2.10-1-default.gz -rw-r--r-- 1 root root 7447454 Sep 7 00:25 vmlinux-5.2.13-1-default.gz lrwxrwxrwx 1 root root 23 Sep 10 14:37 zImage -> zImage-5.2.13-1-default -rw-r--r-- 1 root root 6187360 Aug 25 14:00 zImage-5.2.10-1-default -rw-r--r-- 1 root root 6187360 Sep 7 00:46 zImage-5.2.13-1-default --- /dev/sdb1 --- drwxr-xr-x 4 root root 16384 Jan 1 1970 ./ drwxr-xr-x 18 root root 4096 Sep 7 11:58 ../ drwxr-xr-x 3 root root 2048 Nov 30 2018 EFI/ -rwxr-xr-x 1 root root 27529 Jul 28 20:57 bcm2708-rpi-0-w.dtb* -rwxr-xr-x 1 root root 28432 Sep 10 14:35 bcm2708-rpi-b-plus.dtb* -rwxr-xr-x 1 root root 28173 Sep 10 14:35 bcm2708-rpi-b.dtb* -rwxr-xr-x 1 root root 27950 Sep 10 14:35 bcm2708-rpi-cm.dtb* -rwxr-xr-x 1 root root 28634 Sep 10 14:35 bcm2708-rpi-zero-w.dtb* -rwxr-xr-x 1 root root 27898 Sep 10 14:35 bcm2708-rpi-zero.dtb* -rwxr-xr-x 1 root root 29520 Sep 10 14:35 bcm2709-rpi-2-b.dtb* -rwxr-xr-x 1 root root 31325 Sep 10 14:35 bcm2710-rpi-3-b-plus.dtb* -rwxr-xr-x 1 root root 30706 Sep 10 14:35 bcm2710-rpi-3-b.dtb* -rwxr-xr-x 1 root root 29504 Sep 10 14:35 bcm2710-rpi-cm3.dtb* -rwxr-xr-x 1 root root 44472 Sep 10 14:35 bcm2711-rpi-4-b.dtb* -rwxr-xr-x 1 root root 1476 Sep 10 14:35 config.txt* -rwxr-xr-x 1 root root 1476 Sep 10 14:35 config.txt.rpmsave* drwxr-xr-x 2 root root 16384 Sep 10 14:35 overlays/ -rwxr-xr-x 1 root root 8 Nov 30 2018 startup.nsh* -rwxr-xr-x 1 root root 443036 Jul 28 20:54 u-boot.bin* smime.p7s Description: S/MIME Cryptographic Signature
