Jump to content

0xFF

Members
  • Posts

    2
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Good morning, I cannot seem to get the the newest image (22.08 Bullseye) to boot. I've noticed the disk arrangement is significantly different than the known working image I am using. Here is what I see on the known working image... #fdisk -l Disk /dev/mmcblk0: 28.9 GiB, 30985420800 bytes, 60518400 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: gpt Disk identifier: 2A33F1A5-75EA-4125-AC19-16C0435D774A Device Start End Sectors Size Type /dev/mmcblk0p1 64 8063 8000 3.9M Linux filesystem /dev/mmcblk0p2 16384 24575 8192 4M Linux filesystem /dev/mmcblk0p3 24576 32767 8192 4M Linux filesystem /dev/mmcblk0p4 32768 262143 229376 112M EFI System /dev/mmcblk0p5 262144 60518366 60256223 28.7G Linux filesystem #cat /etc/debian_version 9.9 The newest image is in has a DOS partition table and only one partition. Disk /dev/sdc: 28.91 GiB, 31016878080 bytes, 60579840 sectors Disk model: STORAGE DEVICE 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: 0x1640add5 Device Boot Start End Sectors Size Id Type /dev/sdc1 32768 3833855 3801088 1.8G 83 Linux Also may be important to note my rock pi S has no onboard flash, only SD slot. Am I missing something? Thank you for your time.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines