Next time you should compress the image with xz
that way you can flash the image without decompressing it.
Taks a lot I havenāt got my consolĆ© yet (Iām in the 28xxx batch) but I do really want to use Kali in my devise. Iām tired of using headless SBC each time.
Kali or Parrot Security? Rolling release or stable release? I think Iām going to give Parrot a better look when my Devterm adapter arrives, and if my uConsole arrives.
No audio even after installing patch. What am I missing?
Hey folks,
Thx a lot for this Kali-image, I like it more than the original uconsole āosā
Great work and thx again !
hey guys i found that the kali image is always booting up in powersave mode in case that you wonder why it appears a little bit slow. it than run only at 0.60GHz created some executable files on desktop to change it because i did not found any settings for the CPU operating modes and don`t want to type the commands in the terminal every time i reboot or boot up. Here the screenshots of the CPU performance modes.
how to make it executable on desktop by double click:
need to open terminal on desktop and put the following script in (./test is example file change to your filename).
PS: I also overclock the CPU a bit but do it only on your own risk!
PPS: best in mine opinion is ondemand mode because it is not to slow but also don`t run all the time on full performance. so it did not heat up to much/fast and did not drain the battery to fast.
please let me know what you think was it helpful?
I wasnāt aware of this so Iāll look into it and maybe re-upload the image but only if this compresses it a little? The original file was over the basic storage limit for Google Drive which is why I compressed it in the first place.
If you xz
compress the image itāll still be small but with the added benefits of not having to decompress the image before flashing.
Thanks mate, Iāll keep this in mind for the future. Iāll maybe give it a shot and re-upload it.
Will there ever be a Kali for uconsole kit a-06 or is it better to try to make it yourself? I canāt leave this to Alfred.
I havenāt seen any images for the A06. So far my image creation skills are lacking.
I have a plan to internally replace the A06 along with the motherboard on a Rasberry Pi 5, although I will have to rewire the USB and Ethernet ports as they make the board too thick for the device case. In general, you will have to shake out everything from the case except the display and keyboard; I think the battery module should also be replaced. The obvious advantages are a bunch of distributions, a processor, a graphics core and USB 3.0. The downside is that heat needs to be removed. If it works, Iāll send you a report.
May as well just wait and get a pilet if youāre going to do all that.
you would still need to add the drivers for the display and backlight to whatever distro you want for it to work. just cramming a pi5 in there wonāt change that.
and some way to drive the display.
So sorry ive been pretty busy with a lot but im trying to be back and active again
Excellent work on the Kali port to the uConsole! Its mostly working smoothly after some tinkering but now hitting an issue due to the BOOT partition being 255MB and full. I cannot update the packages now so im wondering if there is a work around to increase the BOOT partition size? Im asking before I jump down the rabbit hole trying to solve this. Any help, much appreciated!
I would probably use gparted to shrink another partition, then move anything between boot and the free space to the right, this should make contiguous space next to boot, then expand boot to take the free space. Itās theory for me, but Iāve had to do this when expanding windows VM storage, or needing to expand the recovery partition for windows updates. Worked for those conditions so it should work for what you need.
Gparted because gui so you can visualize what you need to do.
And that said, yes there are risks, back up important stuff before trying this.
Cheers Greg_E, I tried using GParted and it allowed the resizing of the ROOTFS partition and the allowed me to change the BOOT partition size into the now freed up space but I couldnāt allocate the extra space on the boot partition as it was coming up with an error due to it being a FAT32 file system. So down the rabbit hole I went skippingā¦ The solution has taken a good few attempts but iāve figured it out and would like to share. What I did was to start from fresh with a new image of Kali on the SD card installed via the RPI imager for windows, I then fitted another SD with the bookworm OS into the uConsole then using a usb SD card reader fitted with the Kali OS SD, plugged it into the uConsole, Installed GParted, Changed the ROOTFS (EXT4) partition so that I had 257mb free on the left hand side of the ROOT partition. Once that had finished I ejected the SD card and connected it to my Win10 machine. Using AOMEI Partition assistant I resized the BOOT partition and checked it. Once that was done I refitted it to the uConsole and allowed the system to set up from fresh and everything is working. I lost my original image but that wasnt the end of the world. I tried many different solutions to this problem including many fresh starts, using an Ubuntu machine to do changes natively in Linux and they all had issues dealing with the FAT32 file system. Im sure someone can probably do it via command line in Linux but im not that savvy with command line. Hope this helps somebody.
The reason for the not being able to do everything via AOMEI partition assistant is because it has a hard time dealing with EXT4 file systems.