RE: [opensuse-arm] keeping multiple kernels on ARM systems ?
Ah, this board still uses boot.script. We should switch it to standard distro
boot, if the board supports it.
That way, it will look for all defined folders:
https://github.com/openSUSE/u-boot/commit/5637f1acf10c604ef8f25d43eb4d4fa1d6d4b4e4#diff-aecb24fbaef4b3e2b77f88fa3b5ec0b7R144
Cheers,
Guillaume
> -Original Message-
> From: Per Jessen
> Sent: 28 April 2020 12:25
> To: opensuse-arm@opensuse.org
> Subject: Re: [opensuse-arm] keeping multiple kernels on ARM systems ?
>
> Per Jessen wrote:
>
> > Matthias Brugger wrote:
> >
> >> Can you try if you put your custom dtb into /boot/dtb/current/ I
> >> suppose this directory does not get overwritten when updating the
> >> kernel.
> >>
> >> Would be nice to get feedback on this :)
> >
> > I'll see what I can do - I have a third nanopi that needs updating, I
> > think.
>
> Looking at boot.script from the jeOS image:
>
> http://download.opensuse.org/ports/armv7hl/distribution/leap/15.0/appliances
> /openSUSE-Leap15.0-ARM-JeOS-nanopineo.armv7l-2018.07.02-
> Buildlp150.1.1.raw.xz.
>
> it does not look at /boot/dtb/current. On my nanopis, I have hardcoded
> 'fdtfile' =
> 'sun8i-h3-nanopi-neo-air.dtb', but I see no search order, only one
> 'ftdfolder' (=
> /boot/dtb)
>
>
>
>
> --
> Per Jessen, Zürich (15.8°C)
> http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
>
> --
> 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] keeping multiple kernels on ARM systems ?
Per Jessen wrote: > Matthias Brugger wrote: > >> Can you try if you put your custom dtb into >> /boot/dtb/current/ >> I suppose this directory does not get overwritten when updating the >> kernel. >> >> Would be nice to get feedback on this :) > > I'll see what I can do - I have a third nanopi that needs updating, I > think. Looking at boot.script from the jeOS image: http://download.opensuse.org/ports/armv7hl/distribution/leap/15.0/appliances/openSUSE-Leap15.0-ARM-JeOS-nanopineo.armv7l-2018.07.02-Buildlp150.1.1.raw.xz. it does not look at /boot/dtb/current. On my nanopis, I have hardcoded 'fdtfile' = 'sun8i-h3-nanopi-neo-air.dtb', but I see no search order, only one 'ftdfolder' (= /boot/dtb) -- Per Jessen, Zürich (15.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
RE: [opensuse-arm] Raspi4/Leap 15.2/wrong disk size
> -Original Message- > From: Axel Braun > Sent: 28 April 2020 09:26 > To: opensuse-arm@opensuse.org > Subject: Re: [opensuse-arm] Raspi4/Leap 15.2/wrong disk size > > Hello Guillaume, > > Am Dienstag, 28. April 2020, 08:30:12 CEST schrieb Guillaume Gardet: > > Hi Alex, > > > > > -Original Message- > > > From: Axel Braun > > > Sent: 27 April 2020 22:12 > > > To: opensuse-arm@opensuse.org > > > Subject: Re: [opensuse-arm] Raspi4/Leap 15.2/wrong disk size > > > > > > Hi, > > > > > > Am Freitag, 24. April 2020, 21:39:55 CEST schrieb Fabian Vogt: > > > > > > > Just tried this, but keyboard is not reacting at that stage > > > > > > > (means: > > > > > > > 'E' at > > > > > > > the grub screen does not work, interruption of autoboot does > > > > > > > not work > > > > > > > either) ... although I used the keyboard with the Raspi3 > > > > > > > before > > > > > > > > > > > > U-boot for RPi4 does not have USB support yet, so you cannot > > > > > > use USB keyboard for u-boot, nor grub! > > > > > > > > > > So serial console is the only chance at the moment? > > > > > > > > You could simply edit grub.cfg and shrink the partition again > > > > before rebooting. As long as you don't run mkinitrd or something > > > > like that the kiwi code for resizing is still active. > > > > > > I did various tests today, with the original image and the updated > > > as well, but could not reproduce the issue. File system was always > > > grown to partition size. Thats good on the one hand, but somewhat > > > unsatisfying on the other hand... > > It could be due to a problem when the image was copied to uSD card. > > Some software checks what was written to uSD card once copied. This > > has been useful for me in the past as the check sometimes fail. > > I was using: > xzcat openSUSE-Leap-15.2-ARM-LXQT-raspberrypi4.aarch64-2020.02.26- > Build1.63.raw.xz | dd bs=4M of=/dev/mmcblk0 iflag=fullblock oflag=direct > status=progress; sync Nowadays, I tend to avoid dd as you can copy to the wrong disk and break your system very easily. I prefer to use tools which perform a filtering and expose only removable devices. I know that Etcher [0] performs a check after the copy. I guess other tools would do it as well. Not sure about imagewriter. Maybe people here have suggestions of other software? Cheers, Guillaume [0]: https://www.balena.io/etcher/ > > > > > -- > 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. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Raspi4/Leap 15.2/wrong disk size
Hello Guillaume, Am Dienstag, 28. April 2020, 08:30:12 CEST schrieb Guillaume Gardet: > Hi Alex, > > > -Original Message- > > From: Axel Braun > > Sent: 27 April 2020 22:12 > > To: opensuse-arm@opensuse.org > > Subject: Re: [opensuse-arm] Raspi4/Leap 15.2/wrong disk size > > > > Hi, > > > > Am Freitag, 24. April 2020, 21:39:55 CEST schrieb Fabian Vogt: > > > > > > Just tried this, but keyboard is not reacting at that stage > > > > > > (means: > > > > > > 'E' at > > > > > > the grub screen does not work, interruption of autoboot does not > > > > > > work > > > > > > either) ... although I used the keyboard with the Raspi3 before > > > > > > > > > > U-boot for RPi4 does not have USB support yet, so you cannot use > > > > > USB keyboard for u-boot, nor grub! > > > > > > > > So serial console is the only chance at the moment? > > > > > > You could simply edit grub.cfg and shrink the partition again before > > > rebooting. As long as you don't run mkinitrd or something like that > > > the kiwi code for resizing is still active. > > > > I did various tests today, with the original image and the updated as > > well, but could not reproduce the issue. File system was always grown to > > partition size. Thats good on the one hand, but somewhat unsatisfying on > > the other hand... > It could be due to a problem when the image was copied to uSD card. > Some software checks what was written to uSD card once copied. This has been > useful for me in the past as the check sometimes fail. I was using: xzcat openSUSE-Leap-15.2-ARM-LXQT-raspberrypi4.aarch64-2020.02.26- Build1.63.raw.xz | dd bs=4M of=/dev/mmcblk0 iflag=fullblock oflag=direct status=progress; sync -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
RE: [opensuse-arm] Raspi4/Leap 15.2/wrong disk size
Hi Alex, > -Original Message- > From: Axel Braun > Sent: 27 April 2020 22:12 > To: opensuse-arm@opensuse.org > Subject: Re: [opensuse-arm] Raspi4/Leap 15.2/wrong disk size > > Hi, > > Am Freitag, 24. April 2020, 21:39:55 CEST schrieb Fabian Vogt: > > > > > > Just tried this, but keyboard is not reacting at that stage (means: > > > > > 'E' at > > > > > the grub screen does not work, interruption of autoboot does not > > > > > work > > > > > either) ... although I used the keyboard with the Raspi3 before > > > > > > > > U-boot for RPi4 does not have USB support yet, so you cannot use > > > > USB keyboard for u-boot, nor grub! > > > > > > So serial console is the only chance at the moment? > > > > You could simply edit grub.cfg and shrink the partition again before > > rebooting. As long as you don't run mkinitrd or something like that > > the kiwi code for resizing is still active. > > I did various tests today, with the original image and the updated as well, > but > could not reproduce the issue. File system was always grown to partition size. > Thats good on the one hand, but somewhat unsatisfying on the other hand... It could be due to a problem when the image was copied to uSD card. Some software checks what was written to uSD card once copied. This has been useful for me in the past as the check sometimes fail. Cheers, Guillaume > > Thanks to all for your support! > Axel > > > -- > 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. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
