I updated my ClearfogPro today and noticed (that like in the last updates), updating the linux-u-boot-clearfogpro-next package fails,
with the error "/dev/mmcblk2" doesn't exist".
This happen obviously, because I don't have a SD Card installed, as I am using a M.2 SSD to boot and as root.
Quick check inside the .deb file revealed the platform_install.sh which only tries writing the u-boot.mmc version to /dev/mmcblk2.
For me this is not a big problem, I know how to get the correct u-boot into place (/usr/lib/linux-u-boot-next-clearfogpro_5.60_armhf/u-boot.sata) but new users might find it difficult.
Would it be possible to let the users select the device for writing the u-boot when the mmc variant fails?
Just a popup with a text saying: "Could not write u-boot to default location (sdcard/mmc), please specify device" and a textbox below...
(Might even look into doing something like this myself and then send a PR)
Or does Armbian normally keep track of where the u-boot is and I just did something wrong when moving from sdcard to ssd?
Greetings,
count-doku
EDIT:
Just realised this might apply to other boards to, if it would better fit into Development or so, please move.
Question
Heisath
Hi,
I updated my ClearfogPro today and noticed (that like in the last updates), updating the linux-u-boot-clearfogpro-next package fails,
with the error "/dev/mmcblk2" doesn't exist".
This happen obviously, because I don't have a SD Card installed, as I am using a M.2 SSD to boot and as root.
Quick check inside the .deb file revealed the platform_install.sh which only tries writing the u-boot.mmc version to /dev/mmcblk2.
For me this is not a big problem, I know how to get the correct u-boot into place (/usr/lib/linux-u-boot-next-clearfogpro_5.60_armhf/u-boot.sata) but new users might find it difficult.
Would it be possible to let the users select the device for writing the u-boot when the mmc variant fails?
Just a popup with a text saying: "Could not write u-boot to default location (sdcard/mmc), please specify device" and a textbox below...
(Might even look into doing something like this myself and then send a PR)
Or does Armbian normally keep track of where the u-boot is and I just did something wrong when moving from sdcard to ssd?
Greetings,
count-doku
EDIT:
Just realised this might apply to other boards to, if it would better fit into Development or so, please move.
Link to comment
Share on other sites
1 answer to this question
Recommended Posts