Search This thread

khamai

Member
May 18, 2015
7
0
If add "modprobe panel-novatek-nt36523" in init file (on initramfs) before frame buffer string else screen is working and show splash
 
If add "modprobe panel-novatek-nt36523" in init file (on initramfs) before frame buffer string else screen is working and show splash
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.
 
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!
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)
If you plug the power adapter then the usb mode is changed and the tablet start to charge if it is required, even power source type is detected and turbo/quick/std charging modes works as expected.
Unfortunately the graphic card does not proper init and the PMOS UI does not start, yet.
 
  • Like
Reactions: E!ad

coal686

Senior Moderator / Developer Rel. / Mod Liaison
Staff member
Apr 13, 2012
11,019
20,690
Tampa-ish, FL
OnePlus 9 Pro
A couple of off-topic posts, one of which attacked moderation, have been deleted. The moderation team is discussing what if anything needs to be done so the thread is in compliance with our rules and will work directly with the OP if needed. Please keep the discussion on topic; I'll be subscribing to the thread to make sure everyone remains civil. If you have any questions, please feel free to send me a PM.

Thanks,
coal686
Senior Moderator
Developer Relations Team
 
  • Like
Reactions: Badger50 and alecxs

SivaMaxwell

Senior Member
Sep 25, 2016
123
33
coimbatore
Xiaomi Mi A3
POCO M3
@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 🙏👍👍👍
 
Last edited:
  • Like
Reactions: serdeliuk
@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 🙏👍👍👍
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.
 
Last edited:
  • Like
Reactions: SivaMaxwell
@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
 
  • Like
Reactions: SivaMaxwell

SivaMaxwell

Senior Member
Sep 25, 2016
123
33
coimbatore
Xiaomi Mi A3
POCO M3
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.
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.
 

SivaMaxwell

Senior Member
Sep 25, 2016
123
33
coimbatore
Xiaomi Mi A3
POCO M3
@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
Thanks for the help. I shall try this and let you know what happens.
 
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.
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.
1689929015909.png
 
  • Like
Reactions: SivaMaxwell
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...
Please note that this thread is not about Ubuntu, the debootstrap was mentioned as a courtesy info, yet not related to my work.
!!!--IF YOU USE THE INSTALLER YOU CAN soft BRICK YOUR PAD--!!!!
You may need to not use grub or any kind of installer, debootstrap tool makes that easy, mimic an os after install, after you use debootstrap the result is the system partition after install, over you may need to copy a lot of stuff (to be determined) from pmos system partition, as firmware files, kernel modules, /boot content (if any), etc. On short, you need to use my boot.img with a few folders from my system.img added to your debootstrap-system.img to be able to boot your OS.

If you still have issues pleas ask your question in our own thread or use the Ubuntu thread.

Nabu is not in the official mainline kernel as nobody bothered to clean and fix bugs in the patches and send them for review to be included in mainline.
 
  • Like
Reactions: SivaMaxwell

Xleyxo

Member
Dec 20, 2021
11
1
Xiaomi Mi Pad 5
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
Different answer? I am not sure what else to reply, I am not porting Ubuntu, somebody else did and I pointed to his work.
In regards to your unused partitions you may want to review and/or ask your questions on my other thread Resize internal storage on Xiaomi Pad 5 (nabu) and install PostmarketOS Preview
 
  • Like
Reactions: SivaMaxwell

LesGaR

Senior Member
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.
OK. I understand, sorry for being off topic, I delete it.
 
Last edited:
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?
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.

You may want to read about Qualcomm boot process if you are trying to use Grub on a QCOM device, and think what mode you are using, UEFI or Legacy? But this is not something to discuss here, please create your own thread.
 
  • Like
Reactions: SivaMaxwell

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    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 :)
    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.
    1
    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.
    1
    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.
    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.
    1
    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.
    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 :)
    1
    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.
    Hope to hear from you soon :)
  • 43
    [UPDATE 08 Feb 2023]
    - I am using official linux kernel Linux-6.1.10
    - Preview images are available for download xiaomi-nabu-pmos-preview.6.1.10.tar.gz
    - The GUI user/pass are the standard PMOS ones
    1. user: user
    2. pass: 147147
    - Use the info from this thread about how to resize your internal storage and flash preview images
    1. Resize internal storage on Xiaomi Pad 5 (nabu) and install PostmarketOS Preview
    - Latest stable mainline kernel 6.1.10 for xiaomi pad 5 (nabu) patches are now available (include defconfig), check release section.
    1. Touch pad takes 80 seconds to initialize at boot time, you may need to wait for it.
    2. Battery status does not work yet, i have placed a bash app that can collect battery status from dmesg, you have a shortcut on desktop, do not keep the app open, will drain battery.
    _______________________________
    Donate a coffee to support development:
    Donate via PayPal to serdeliuk



    [UPDATE 23 Jan 2023]
    - XDA staff is pushing me to provide kernel source waving the linux kernel's GPL OpenSource license.
    I am using the latest stable linux kernel which can be found here linux-6.1.7.tar.xz
    - I am using as well some mods made by others which are put together by map220v and this kernel may be found here sm8150-mainline
    - As anyone may know kernel modules/drivers can be closed source and my kernel modules will remain as such until i decide that i am ready to make them OpenSource.

    JUST TO BE NOTED, I DIDN'T PROVIDED YET ANY ROM OR BINARY KERNEL, SO I AM NOT BOUND TO ANY GPL

    [UPDATE 20 Jan 2023]
    - Mainlined to the latest kernel 6.2-rc4
    - Created the HowTo Resize internal storage on Xiaomi Pad 5 (nabu) and install PostmarketOS Preview
    - Preparing the preview images, please check https://github.com/serdeliuk/xiaomi-nabu-postmarketos

    [UPDATE 17 Dec 2022]
    - Fixed battery charging, now battery is charging as well, on slow speed.
    Yet the battery indicator still do not work properly

    [UPDATE 22 Oct 2022]
    - finally working battery status
    1666434328506.png

    1666436173168.jpeg


    [UPDATE 11 Sep 2022]
    - mainlined to 6.0-RC4
    - GPU is finally working
    - panel and brightness is working
    - bluetooths is working

    [UPDATE 2 Jul 2022]
    - mainlined to the latest available kernel, 5.19.0-RC4
    - WiFi finally works
    nabu.wifi.ok.jpg

    Hello,

    I have successfully ported PostmarketOS to my Xiaomi Pad 5 tablet.
    pmos.working.touch.jpg

    I have fixed SPI touchscreen and currently boot from B slot, on A slot is still Android (dual boot)
    WiFI do not work yet and the network is provided via USB, as the ssh access on the tablet too.

    # here you can find the official page for this device
    PostmarketOS Xiaomi-nabu page

    I will keep you posted about the progress.

    Best regards

    M
    10
    I have a bit of success, finally working battery status as you can see on images updated on #1 post
    9
    I have created the official device page, is not ready yet, but a start
    PostmarketOS Xiaomi-nabu page
    9
    It's bluetooth, as well as the Smart Pen, but they don't work in non-stock... GSIs, for exemple
    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....
    There is just a matter of time to make the already ported touchscreen driver from downstream to mainline to have the pen working, in regards to the keyboard that should work directly (without charging) the pogo pins probably have a hall sensor to activate the power output to charge the keyboard when connected, the same should exists on the other side for pen, but those are far away on my development scale, as right now i am trying to bring up the multi touch gestures and prepare a release, as the wifi works, even without GPU the tablet is usable as a Linux device already.
    8
    I have a bit of success here, WiFi finally works, see post #1 for a nice image.