Re: [opensuse-arm] Raspi4/Leap 15.2/wrong disk size
Am Mittwoch, 22. April 2020, 16:33:03 CEST schrieb Guillaume Gardet: > Adding Matthias in Cc. > > > -Original Message- > > From: Axel Braun > > Sent: 22 April 2020 16:22 > > To: opensuse-arm@opensuse.org > > Subject: [opensuse-arm] Raspi4/Leap 15.2/wrong disk size > > > > Hi, > > I'm trying the Raspi 4 image (openSUSE-Leap-15.2-ARM-LXQT- > > raspberrypi4.aarch64-2020.02.26-Build1.63.raw.xz) updated to the latest > > patch level, and encounter an issue with the reported disk size: > > > > raspi4:/home/test # fdisk -l > > Disk /dev/mmcblk1: 29.6 GiB, 31734104064 bytes, 61980672 sectors > > Units: sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 512 bytes I/O size > > (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk > > identifier: 0x0b54e5bb > > > > Device Boot Start End Sectors Size Id Type > > /dev/mmcblk1p1 2048 133119 131072 64M c W95 FAT32 (LBA) > > /dev/mmcblk1p2 133120 1157119 1024000 500M 82 Linux swap / > > Solaris > > /dev/mmcblk1p3 1157120 61978769 60821650 29G 83 Linux > > > > -> so far so good, 29G available for / > > > > But: > > raspi4:/home/test # df -h > > Filesystem Size Used Avail Use% Mounted on > > devtmpfs903M 0 903M 0% /dev > > tmpfs 943M 0 943M 0% /dev/shm > > tmpfs 943M 1.1M 942M 1% /run > > tmpfs 943M 0 943M 0% /sys/fs/cgroup > > /dev/mmcblk1p3 4.0G 3.8G 39M 99% / > > /dev/mmcblk1p1 64M 8.4M 56M 14% /boot/efi > > tmpfs 189M 0 189M 0% /run/user/1000 > > > > -> only 4G for / in the running system, ext4 file system. > > (I fixed this with resize2fs) > > > > Is this an issue of the used image? > > The resize of the partition should happen on first boot. > Would you have serial traces of the boot? How can I get those? > Could you file a bug on Bugzilla to track it, please? Sure Best, Axel -- 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
Adding Matthias in Cc. > -Original Message- > From: Axel Braun > Sent: 22 April 2020 16:22 > To: opensuse-arm@opensuse.org > Subject: [opensuse-arm] Raspi4/Leap 15.2/wrong disk size > > Hi, > I'm trying the Raspi 4 image (openSUSE-Leap-15.2-ARM-LXQT- > raspberrypi4.aarch64-2020.02.26-Build1.63.raw.xz) updated to the latest patch > level, and encounter an issue with the reported disk size: > > raspi4:/home/test # fdisk -l > Disk /dev/mmcblk1: 29.6 GiB, 31734104064 bytes, 61980672 sectors > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes I/O size > (minimum/optimal): > 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0b54e5bb > > Device Boot Start End Sectors Size Id Type > /dev/mmcblk1p1 2048 133119 131072 64M c W95 FAT32 (LBA) > /dev/mmcblk1p2 133120 1157119 1024000 500M 82 Linux swap / Solaris > /dev/mmcblk1p3 1157120 61978769 60821650 29G 83 Linux > > -> so far so good, 29G available for / > > But: > raspi4:/home/test # df -h > Filesystem Size Used Avail Use% Mounted on > devtmpfs903M 0 903M 0% /dev > tmpfs 943M 0 943M 0% /dev/shm > tmpfs 943M 1.1M 942M 1% /run > tmpfs 943M 0 943M 0% /sys/fs/cgroup > /dev/mmcblk1p3 4.0G 3.8G 39M 99% / > /dev/mmcblk1p1 64M 8.4M 56M 14% /boot/efi > tmpfs 189M 0 189M 0% /run/user/1000 > > -> only 4G for / in the running system, ext4 file system. > (I fixed this with resize2fs) > > Is this an issue of the used image? The resize of the partition should happen on first boot. Would you have serial traces of the boot? Could you file a bug on Bugzilla to track it, please? Thanks, Guillaume > > Thx > 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
[opensuse-arm] Raspi4/Leap 15.2/wrong disk size
Hi, I'm trying the Raspi 4 image (openSUSE-Leap-15.2-ARM-LXQT- raspberrypi4.aarch64-2020.02.26-Build1.63.raw.xz) updated to the latest patch level, and encounter an issue with the reported disk size: raspi4:/home/test # fdisk -l Disk /dev/mmcblk1: 29.6 GiB, 31734104064 bytes, 61980672 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0b54e5bb Device Boot Start End Sectors Size Id Type /dev/mmcblk1p1 2048 133119 131072 64M c W95 FAT32 (LBA) /dev/mmcblk1p2 133120 1157119 1024000 500M 82 Linux swap / Solaris /dev/mmcblk1p3 1157120 61978769 60821650 29G 83 Linux -> so far so good, 29G available for / But: raspi4:/home/test # df -h Filesystem Size Used Avail Use% Mounted on devtmpfs903M 0 903M 0% /dev tmpfs 943M 0 943M 0% /dev/shm tmpfs 943M 1.1M 942M 1% /run tmpfs 943M 0 943M 0% /sys/fs/cgroup /dev/mmcblk1p3 4.0G 3.8G 39M 99% / /dev/mmcblk1p1 64M 8.4M 56M 14% /boot/efi tmpfs 189M 0 189M 0% /run/user/1000 -> only 4G for / in the running system, ext4 file system. (I fixed this with resize2fs) Is this an issue of the used image? Thx Axel -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
RE: [opensuse-arm] keeping multiple kernels on ARM systems ?
Guillaume Gardet wrote: > Hi, > >> -Original Message- >> From: Per Jessen >> Sent: 19 April 2020 10:39 >> >> Question - the multiple kernels feature ought to have retained my dtb >> directory contents in /boot/dtb-4.12.14-lp150.12.48/ ? Or not ? > > AFAIK, there is no multiversion support for DTB. And DTB should even > be kernel version agnostic, but I know this is not really the case. > > Your /boot/dtb-4.12.14-lp150.12.48/ folder should have been dropped > (if there was no *.old file inside) and a new > /boot/dtb-4.12.14-lp150.12.82/ should have been created with the > update of your DTB package. Is it missing? Hi Guillaume 12.48 was not dropped as I had a file named *.old in there - I also had my working DTB in here, and that was gone. The new 12.82 directory only had the openSUSE supplied DTB which does not work (sufficiently well). I was happy when I noticed the 12.48 directory, thinking I can just quickly copy the old DTB over -- Per Jessen, Zürich (19.3°C) http://www.cloudsuisse.com/ - your owncloud, hosted 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] keeping multiple kernels on ARM systems ?
Hi, > -Original Message- > From: Per Jessen > Sent: 19 April 2020 10:39 > To: opensuse-arm@opensuse.org > Subject: [opensuse-arm] keeping multiple kernels on ARM systems ? > > (repost from opensuse@o.o) > I'm sure many have this feature enabled, just in case. Keeping multiple > kernels > and module versions around. > > On one of my ARM systems, yesterday I ran an update "zypper patch" (Leap > 15.0), > which installed a new kernel 4.12.14-lp150.12.82-lpae, the old one being > 4.12.14- > lp150.12.48-lpae. > > Both initrds were rebuilt, I have two kernels, two sets of modules - but my > dtb > was cleared out: /boot/dtb-4.12.14-lp150.12.48/ - empty apart from one file I > had > renamed to .old. > > I use my own DTB, but this did not prevent the system from booting, instead it > did stop the network from coming up (wifi device not correctly defined in the > openSUSE supplied DTB). I had to climb some 10meters up a ladder to retrieve > the box, disassemble it and put a serial console on it :-) > > Question - the multiple kernels feature ought to have retained my dtb > directory > contents in /boot/dtb-4.12.14-lp150.12.48/ ? Or not ? AFAIK, there is no multiversion support for DTB. And DTB should even be kernel version agnostic, but I know this is not really the case. Your /boot/dtb-4.12.14-lp150.12.48/ folder should have been dropped (if there was no *.old file inside) and a new /boot/dtb-4.12.14-lp150.12.82/ should have been created with the update of your DTB package. Is it missing? Cheers, Guillaume > > > -- > Per Jessen, Zürich (17.3°C) > > > -- > 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.
