It is not clear what you are trying to do, but is not related to my port. Please open your own thread and ask your questions or try to find an already existing thread where to ask how to proceed with your mods.If add "modprobe panel-novatek-nt36523" in init file (on initramfs) before frame buffer string else screen is working and show splash
Does this mean you settle for the device to reverse power the HUB? Like the USB light you showed in the EDK2 thread? That's so cool!Testing downstream kernel, it seems to work flawless, i have FULL USB working, including charger sense and proper battery reporting.
View attachment 5893801
Indeed, the usb works perfectly, if you plug an usb hub will sense the hub and will provide power and power the usb devices, if you plug then keyboard and mouse will be powered on and will work, the image show the leds lit on the, hub, keyboard and mouse, if you plug a stick will be detected and mounted (if contain a known partition)Does this mean you settle for the device to reverse power the HUB? Like the USB light you showed in the EDK2 thread? That's so cool!
I see that someone ported Ubuntu already and it seems to work https://forum.xda-developers.com/t/ubuntu-on-xiaom7i-pad-5-nabu.4597149
Hi, thanks.@serdeliuk
I am really happy with the tablet running alpine. A couple of questions/ requests..
1. Power button - volume buttons.. are not working. I was able to auto turn off screen or lock it from power management.. but if sleep is setup, the only way to wake is hard restart device. Can you please help fix this ?
2. Any way we can modify the reboot to slot a or slot be from Linux itself so that we can easily dual boot without an external computer? In Android we can use the magisk app to do this if rooted..
3. We are not yet taking full capabilities of screen. YouTube video in Firefox are limited to 720p60 . Any way we can change that now or in future?
4. Any guide to use Ubuntu instead of alpine (pmos ) ? i.e., to build Ubuntu image using your methods ?
You're working hard on this project and we are grateful for that.
Thanks![]()
/home/user # apk add qbootctl
....
/home/user # qbootctl -help
qbootctl: qcom bootctrl HAL port for Linux
-------------------------------------------
qbootctl [-c|-m|-s|-u|-b|-n|-x] [SLOT]
<no args> dump slot info (default)
-h this help text
-c get the current slot
-a get the active slot
-b SLOT check if SLOT is marked as bootable
-n SLOT check if SLOT is marked as successful
-x [SLOT] get the slot suffix for SLOT (default: current)
-s SLOT set to active slot to SLOT
-m [SLOT] mark a boot as successful (default: current)
-u [SLOT] mark SLOT as unbootable (default: current)
/home/user # qbootctl -s a
SLOT 0: Set as active slot
/home/user # reboot
Hi, I tried changing the power button settings in the settings > powermanagement > button behavior . It did not work for me. Also, I activated the automatic lock and screen dim. No matter what, even if I click on the keyboard, the screen is not turning back on. The only way for me to retrieve is to reboot again.Hi, thanks.
Power and volume buttons should work, yet the power button is not assigned to do what is expected to do, I think was set to lock the screen instead, or ask what to do. Does not do this? You can change the behaviour in settings.
The sleep do not work yet as the panel power management is incomplete, when enter to power down state is not able to power up again and throw a kernel panic, will be fixed at some point, but not soon.
The reboot to the other slot was already discussed, please revise the replies here, there are a few options, yet I didn't tested them properly.
In regards to firefox I think this was solved changing the browser, I didn't properly tested the UI as I was busy solving kernel drivers.
I do not have any guide for Ubuntu at hand, there is a new port based on my kernel please check their thread in my previous reply is a link, however you can always use Debian's debootstrap tool to create a system image with any Debian based distros, including Ubuntu (if they have a distro/build for arm64), I suppose that they used debootstrap, it is easy as far as I can recall all you need to do is to have a Linux system with debootstrap tool, then create a folder where those packages will be installed, in the end create a an empty img file, mount the file then copy all. You can even use my system image (recommended) remove almost all, but keep kernel drivers and firmware files and put over the debootstrap folder content.
Thanks for the help. I shall try this and let you know what happens.@SivaMaxwell qbootctl is, and works, unfortunately is a cli tool probably there is a gui for it too
Code:/home/user # apk add qbootctl .... /home/user # qbootctl -help qbootctl: qcom bootctrl HAL port for Linux ------------------------------------------- qbootctl [-c|-m|-s|-u|-b|-n|-x] [SLOT] <no args> dump slot info (default) -h this help text -c get the current slot -a get the active slot -b SLOT check if SLOT is marked as bootable -n SLOT check if SLOT is marked as successful -x [SLOT] get the slot suffix for SLOT (default: current) -s SLOT set to active slot to SLOT -m [SLOT] mark a boot as successful (default: current) -u [SLOT] mark SLOT as unbootable (default: current) /home/user # qbootctl -s a SLOT 0: Set as active slot /home/user # reboot
I can't recall the button status on the github binary, but should work, by default button event handling is unchecked, to make them work you may need to use the following settings (all tabs), if you use sleep your device will not wake up, as the panel will fail to power up again.Hi, I tried changing the power button settings in the settings > powermanagement > button behavior . It did not work for me. Also, I activated the automatic lock and screen dim. No matter what, even if I click on the keyboard, the screen is not turning back on. The only way for me to retrieve is to reboot again.
Please note that this thread is not about Ubuntu, the debootstrap was mentioned as a courtesy info, yet not related to my work.Hi! I try to boot Ubuntu, but now only can boot funcional grub. Can use volume buttons to select options and power off button to select option. But Ubuntu not boot.
I try to create image with debootstrap utility and keep your kernel and firmware.
I follow guide to create Ubuntu image posted few posts ago and not boot. Can compile kernel based in your work, with latest parches, for enable dualrole (for use USB hub ) but at the moment not boot.
I see Xiaomi-elish is now in mainline kernel, I know soc is diferent, but you pached kernel for Nabu soc are in mainline, it's correct?
Can I ask why is the reason Nabu isn't in mainline sources?
I installed your postmarked version in my Nabu and work fine. Thanks for your work.
I keep trying port Ubuntu and Grub some days more...
totally different answer but, i recently installed windows 11 on my pad 5. i uninstalled it . works great but i want to remove the windows partition because it only shows 51GB on my tabletI see that someone ported Ubuntu already and it seems to work https://forum.xda-developers.com/t/ubuntu-on-xiaom7i-pad-5-nabu.4597149
Any Linux distribution that support ARM64 should work, why not, why not?
Different answer? I am not sure what else to reply, I am not porting Ubuntu, somebody else did and I pointed to his work.totally different answer but, i recently installed windows 11 on my pad 5. i uninstalled it . works great but i want to remove the windows partition because it only shows 51GB on my tablet
OK. I understand, sorry for being off topic, I delete it.Tenga en cuenta que este hilo no es sobre Ubuntu, el debootstrap se mencionó como información de cortesía, pero no está relacionado con mi trabajo.
!!! --SI USAS EL INSTALADOR, PUEDES suavizar tu PATA--!!!!
Es posible que no necesite usar grub o cualquier tipo de instalador, la herramienta debootstrap lo hace fácil, imite un sistema operativo después de la instalación, después de usar debootstrap, el resultado es la partición del sistema después de la instalación, es posible que deba copiar muchas cosas (por determinar) de la partición del sistema pmos, como archivos de firmware, módulos del kernel, /boot content (si lo hubiera), etc. En resumen, debe usar mi boot.img con algunas carpetas de mi system.img agregadas a su debootstrap-system.img para poder arrancar su sistema operativo.
Si aún tiene problemas, haga su pregunta en nuestro propio hilo o use el hilo de Ubuntu.
Nabu no está en el kernel oficial de la línea principal, ya que nadie se molestó en limpiar y corregir errores en los parches y enviarlos para su revisión para ser incluidos en la línea principal.
Boot process is something not related to the OS; so it is not possible in PMOS, Windows or Android, the bootloader is something different, and out of scope of this thread, please use a Grub specialized thread or create your own Grub thread and ask your questions.OK. I understand, sorry for being off topic, I delete the last post.
I try to explain myself better...
I was compiling some kernels in pmos to try to boot it with grub.
Because? If you can boot pmos from grub, you can use only one slot to boot windows, android and pmos (can be seen in the attachment).
I google it about this and I only see this information https://gitlab.com/postmarketOS/pmaports/-/issues/1531 and https://gitlab.com/postmarketOS/boot-deploy
I don't know how is the boot process in pmos (for this reason I ask you about ubuntu),
I now have a precompiled aarch64 grub installed on the efi partition (until I can compile it to pmos) and need help on the kernel flags needed to boot it from grub.
I try this:
timeout 1 default postmarketOS menu title boot prev kernel label postmarketOS kernel /vmlinuz fdt /sm8150-xiaomi-nabu.dtb initrd /initramfs
But not work :-(
¿Can you think it is possible in pmos?
I am not yet back on working as I am travelling Europe right now, by the middle of the month I will be back home and hopefully able to reload the work on the patches and images.Thanks for the speedy response. I agree with you, having a reliable touch is more important than one time delay.
I used your defconfig but no luck, maybe I mixed a few things in between, I will try fresh.
By the way, did you manage to resume your work on audio patches for 6.1?
We all are waiting![]()
All the kernels between 6.2 and the latest are very unstable on our tablet, the clocks freezes and upon boot/reboot and the UFS is not properly initialized, so multiple reboots are required to have back clocks and UFS working.Hi @serdeliuk,
I have tried the `map220v` 6.4 branch, but I could only get it working once, otherwise, it fails at boot with the error `boot partition not found`.
I tried the same with your patches on 6.1, tried with plasma desktop, and used firmware from your preview build, but my screen turns blank upon boot.
I'm using `pmbootstrap` to manage the builds.
Do you have any suggestions to make a proper rootfs/kernel?
By the way, the touch worked immediately in 6.4 (no 80s wait) and is more sensitive, and the system felt more polished, maybe because of a better touch experience. Bluetooth however didn't work.
Thanks for the speedy response. I agree with you, having a reliable touch is more important than one time delay.All the kernels between 6.2 and the latest are very unstable on our tablet, the clocks freezes and upon boot/reboot and the UFS is not properly initialized, so multiple reboots are required to have back clocks and UFS working.
You should use my patches against kernel 6.1 using my def_config provided in the same archive, the screen goes black at some point but for a few seconds then the login gui should be provided.
My touch driver has the 80 delay, the driver provided in the map220v 6.4 kernel is not mine and initialize perfectly, but not on every boot, sometimes you need to reboot twice to have the touch working, so I prefer to wait 80s and have the touch working at first boot.
Hope to hear from you soonI am not yet back on working as I am travelling Europe right now, by the middle of the month I will be back home and hopefully able to reload the work on the patches and images.
Thanks for the info, if are bluetooth and if i will make the BT work then for sure I will find a way to make them work, will be a bit difficult to test as i do not have the keyboard or the pen and are a bit expensive....It's bluetooth, as well as the Smart Pen, but they don't work in non-stock... GSIs, for exemple