Skip to content
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

img on git #8

Open
ghost opened this issue Sep 23, 2021 · 4 comments
Open

img on git #8

ghost opened this issue Sep 23, 2021 · 4 comments

Comments

@ghost
Copy link

ghost commented Sep 23, 2021

Arch console -works
Void X -works
Arch test disk 3 "X" -works

Arch and Kali versions "X" are unbootable from usb
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

qemu script error on (Mac)
qemu-system-arm: could not load kernel 'zImage'
Bildschirmfoto 2021-09-25 um 16 14 13

@quarkscript
Copy link
Owner

Thank you for feedback!

You are right, looks like some images cannot find root partition while boot from pendrive. I maked them from sdcard. The difference between last disk images and previous are kernel and custom-mesa packages. I've kept the previous images in case the new one doesn't work. So I think I'll delete the buggy disk images and make a new one for kali.

As for qemu, that means no kernel image file. You may extract kernel image file like:

fdisk kali_xe303c12_test.img 

Welcome to fdisk (util-linux 2.37.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk kali_xe303c12_test.img: 1.84 GiB, 1973420032 bytes, 3854336 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: 7B9134D9-0F06-6D4E-8DF0-318D59DC159D

Device                  Start     End Sectors  Size Type
kali_xe303c12_test.img1  8192   40959   32768   16M ChromeOS kernel
kali_xe303c12_test.img2 40960 3854302 3813343  1.8G ChromeOS root fs

Command (m for help): q

sudo mount -t btrfs -o,loop,offset=$((512*40960)) kali_xe303c12_test.img dsk
cp dsk/boot/zImage zImage
sudo umount dsk

and run from qemu

qemu-system-arm -machine virt -m 1024 -kernel zImage -append "root=/dev/vda2" -serial stdio -drive if=none,file=kali_xe303c12_test.img,format=raw,id=hd0 -device virtio-blk-device,drive=hd0 -netdev user,id=net0 -device virtio-net-device,netdev=net0 
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.13.8 (root@kali) (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT Mon Aug 9 15:13:57 EDT 2021
...
Kali GNU/Linux Rolling kali ttyAMA0

kali login: root
Password: toor
Linux kali 5.13.8 #1 SMP PREEMPT Mon Aug 9 15:13:57 EDT 2021 armv7l
...
root@kali:~#

but I do not know if Mac support btrfs filesystem

@quarkscript
Copy link
Owner

I have re-signed and re-flashed the kernel on the kali image and it boots from a pendrive on my chromebook.

@ghost
Copy link
Author

ghost commented Oct 30, 2021

I have re-signed and re-flashed the kernel on the kali image and it boots from a pendrive on my chromebook.

Link will be updated ?

@quarkscript
Copy link
Owner

quarkscript commented Oct 31, 2021

Link updated
Screenshot_2021-10-31_07-36-23

by the way edim could be used to create empty disk image with any custom size https://youtu.be/ALJR2doOipc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant