-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't mounting loopdev #2
Comments
Which host system do you have? Have you installed losetup? |
My PC runs Debian Bookworm, losetup is installed |
You can try printing out the variable returned from losetup -f and add Debug with "set -x" or bash -x in the first line of the buildimg.sh https://github.com/frank-w/BPI-Router-Images/blob/main/buildimg.sh#L43C3-L43C3 It looks like this fails (and $LDEV is empty)...maybe you see an error? |
Same here. When i use the deault uboot image from upstream everything is working fine. But when i pack uboot myself with ./build.sh createimg i see the following on imagebuild
Running on Ubuntu 22.04.4 LTS |
Looks like Partprobe does not find any partitions.. You could try using fdisk or parted on the loopdev to show gpt. Gpt itself is created with parted in build.sh in mtk-atf branch in my uboot repo |
got following output from parted
|
The img file is downloaded from my uboot releases? Which exactly (you see downloadlink when running the buildimg script)? Maybe there is a build issue. |
Last build of 2024.07 for r4 looks good so far https://github.com/frank-w/u-boot/actions/runs/10661486395/job/29547044343#step:16:829 |
I'm build uboot with If i use auto-dowload uboot from upstream everything works as expected |
Have you changed build.conf to the right board? Per default it is bpi-r2 which image can be created from uboot branch due to binary preloader...and this image contains only 2 partitions...so will cause your error. for bpi-r3 and r4 uboot needs to be packed in atf (mtk-atf branch) and createimg is in this build.sh,not in uboot branch. See ci pipeline (.github/workflows/build.yaml) for more |
Thanks for your fast reply and clarification. I will try it tomorrow. |
Any new state here? |
Hi,
Thanks for greate work.
I have some problem with
mmcbootpart
when mounting loopdevsetting up imgfile to loopdev... losetup: bpi-r3_bookworm_6.1.img: failed to use device: No such device mounting loopdev... mount: /home/ninh/apps/BPI-Router-Images/mnt/BPI-BOOT: special device p5 does not exist. dmesg(1) may have more information after failed mount system call. mounting BPI-BOOT failed
The text was updated successfully, but these errors were encountered: