SliTaz Forum
You are not logged in.
Pages: 1
Hello, I was tinkering with the BIOS dump of the tablet, which now no longer has access to the USB ports.
It's no secret that my English is poor, perhaps very poor, but here I see the messages that appeared on the screen in question.
*,0,135,1,xHCI Mode,Enabled,"Enabled,Disabled","Mode of operation of xHCI controller.
Disable:Forces only USB 2.0 to be supported in the OS.
Enable:Allows USB 3.0 to be supported in the OS and BIOS.
Auto:This mode uses ACPI protocol to provide an option that enables the xHCI controller and reroute USB ports via the _OSC ACPI method call.
Smart Auto:This mode is similar to Auto, but it adds the capability to route the ports to xHCI or EHCI according to setting used in previous boots (for non-G3 boot) in the pre-boot environment. This allows the use of USB 3.0 devices prior to OS boot.[This mode will be hidden when XHCI Controller setting Disable]
I chose the “Disable” option to try to improve USB compatibility, where it clearly states that it maintains support for the operating system in USB 2.0.
Disable:Forces only USB 2.0 to be supported in the OS.
Did I misunderstand, or did the translator of the bios write complete nonsense?
-------------------------------------------------------------------------
Salve, stavo armeggiando con il dump del bios del tablet che ora non ha più accesso alle porte usb.
Non è un segreto che mastico l'inglese male, forse molto male, ma qui vedo le scritte che mi si presentarono nella schermata incriminata.
*,0,135,1,xHCI Mode,Enabled,"Enabled,Disabled","Mode of operation of xHCI controller.
Disable:Forces only USB 2.0 to be supported in the OS.
Enable:Allows USB 3.0 to be supported in the OS and BIOS.
Auto:This mode uses ACPI protocol to provide an option that enables the xHCI controller and reroute USB ports via the _OSC ACPI method call.
Smart Auto:This mode is similar to Auto, but it adds the capability to route the ports to xHCI or EHCI according to setting used in previous boots (for non-G3 boot) in the pre-boot environment. This allows the use of USB 3.0 devices prior to OS boot.[This mode will be hidden when XHCI Controller setting Disable]
scelsi per tentare una migliore compatibilità sulle usb la voce “Disable”, dove dice sembra senza ombra di dubbio che mantiene il supporto per il sistema operativo in USB 2.0
Disable:Forces only USB 2.0 to be supported in the OS..
Ho capito male Io, o il traduttore del bios ha scritto un emerita cazzata!
Offline
Hi gibor,
No you good understand, i read same as you.
Disable: Forces only USB 2.0 to be supported in the OS.
In that case only usb port work as 2.0 norme.
Can you have access to bios dump, maybe you can try to reflash it and reset to default ?
Offline
Hi Shann, it's a long story...
I'm trying them all, but apparently I haven't succeeded yet.
The system boots normally and lets me connect to Wi-Fi. I've tried various methods from the SSH shell, but so far none have been successful.
The “Insyde” BIOS is managed by the H2OFFT utilities, and all versions have given me problems:
the DOS version, with dosbox, gives an error when accessing memory (if you want details, I'll have to try again)
the Windows version, launched with wine, complains that shellexecuter is missing.
The Linux version gives an error when compiling phy_alloc
InsydeH2OFFT_x86_LINUX64_100.00.08.18/driver/phy_alloc.c:573:26: error: expected declaration specifiers or ‘...’ before string constant
573 | MODULE_SUPPORTED_DEVICE( “Insyde” );
Using a programmer, I read the “winbond w25q64fw” flash memory and obtained the raw dump.bin.
Edited with H2OEZE, restored defaults, exported and executed the flash, but it still does not activate the USBs even though they are enabled in the H2OEZE menu...
I have dd backups of all three fat32 and 2 ext4 (mmcbxxx) memories from when it was still working, but I just don't understand where this damn EFI stores its settings!
Translated with DeepL.com (free version)
--------------------------------------------------------------------------
Ciao shann, storia lunga...
le sto provando un po tutte, ma a quanto pare non sono ancora riuscito nell'intento.
Il sistema si avvia normalmente e lascia collegare in wifi. Dalla shell in ssh ho tentato vari metodi, ma per ora nessuno è andato a buon fine.
Il bios “Insyde” è gestito dalle utility H2OFFT, e tutte le versioni mi hanno dato problemi:
la versione dos, con dosbox, da errore per l'accesso alla memoria (se vuoi i dettagli debbo riprovare)
la versione window, avviata con wine, lamenta shellexecuter mancante.
La versione linux, da errore nella compilazione di phy_alloc
InsydeH2OFFT_x86_LINUX64_100.00.08.18/driver/phy_alloc.c:573:26: error: expected declaration specifiers or ‘...’ before string constant
573 | MODULE_SUPPORTED_DEVICE( "Insyde" );
tramite programmatore ho letto la memoria flash “winbond w25q64fw” ed ho ricavato il dump.bin secco.
Editato con H2OEZE, ripristinato i default, esportato ed eseguito il flash, continua a non attivare le usb nonostante dal menu di H2OEZE siano abilitate...
ho i backup in dd di tutte e tre le memorie fat32 e 2 ext4 (mmcbxxx) di quando era ancora funzionante, ma non capisco proprio dove memorizzi i settaggi questo EFI del piffero!
Offline
Hi gibor,
Search i do related to [c]error: expected declaration specifiers or ‘...’ before string constant[/c] is variable not initialize correctly.
Please do you have link to download Insyde file, for try to fix compilation or put tarball if not huge as attachment. Thanks
If remind EFI var is store on nvram, maybe you could see more info under /sys/firmware/efi/efivars
Offline
Hello, I don't think it's free!
https://gitgud.io/walkman8196/lnsider_Bl0S_TooIs/-/blob/master/For_Linux_OS/h2offt-100.00.08.18-1.bin.src.rpm?ref_type=heads
NVRAM appears to be empty; the efibootmgr tool responds as follows:
efibootmgr -v
EFI variables are not supported on this system.
However, Clonezilla saved the file efi-nvram.dat in a backup, which contains the text
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0000,2001,2002,2003
Boot0000* EFI Hard Drive PciRoot(0x0)/Pci(0x17,0x0)/Ctrl(0x0)/HD(1,GPT,e259e40c-cdd0-a841-88b3-2c5e08f62cd8,0x1000,0x96000)RC
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 17 / 01 05 08 00 00 00 00 00 / 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 60 09 00 00 00 00 00 0c e4 59 e2 d0 cd 41 a8 88 b3 2c 5e 08 f6 2c d8 02 02 / 7f ff 04 00
data: 52 43
Boot0001* EFI USB Device (General) PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/USB(1,0)/HD(1,MBR,0x8867174e,0x800,0xeff800)RC
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 03 05 06 00 00 00 / 03 05 06 00 01 00 / 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 f8 ef 00 00 00 00 00 4e 17 67 88 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 7f ff 04 00
data: 52 43
Boot2001* EFI USB Device RC
dp: 7f ff 04 00
data: 52 43
Boot2002* EFI DVD/CDROM RC
dp: 7f ff 04 00
data: 52 43
Boot2003* EFI Network RC
dp: 7f ff 04 00
data: 52 43
Empty two mysterious partitions mmcblk1boot0 mmcblk1boot1 both 4.2MB!
Offline
Hi Shann, mission accomplished ^_^
ROM dump with CH341
UEFIExtract https://github.com/LongSoft/UEFITool/releases
UEFIExtract mydump.bin
In the same folder, I found the extracted dump with a file named mydump.bin.report.txt
I opened that file mydump.bin.report.txt with leafpad (or any editor of your choice)
In the descriptions, you will find the Type and Subtype indications, where I searched for the NVRAM entry
You can see that it has a start and occupied length: in my case, HEX 500000 and 40000
With wxhexeditor, I filled that area with FF
I saved and reflashed it again with CH341
I don't know if it was luck or persistence, but the tablet restarted as before, and now the USB ports are working!
Translated with DeepL.com (free version)
--------------------------------------------------------------------------
Hi Shann, missione compiuta ^_^
dump della rom con CH341
UEFIExtract https://github.com/LongSoft/UEFITool/releases
UEFIExtract mydump.bin
nella stessa cartella ho trovato il dump estratto con un file di nome mydump.bin.report.txt
aperto con leafpad (o qualsiasi editor a scelta) quel file mydump.bin.report.txt
nelle descrizioni si trova l'indicazione Type e Subtype in cui ho cercato la voce NVRAM
si vede che ha inizio e lunghezza occupata: nel mio caso di HEX 500000 e 40000
con wxhexeditor ho riempito quell'area con FF
salvato e riflashato sempre con il CH341
Fortuna o costanza non so ma, il tablet si è riavviato come prima, però le usb ora funzionano!
Offline
Thank you for sharing this detailed troubleshooting journey! It’s impressive how you carefully explored the BIOS settings, worked through the USB controller modes, and dug deep into the EFI and NVRAM areas. Your persistence in using tools like CH341 for dumping and flashing the ROM, combined with UEFIExtract and hex editing, really paid off. It’s great to hear that after all that effort, the USB ports are now working again! This kind of deep technical work is invaluable for anyone facing similar hardware or firmware issues. Thanks again for documenting the process so thoroughly—it’s a big help to the community.
Offline
Pages: 1
[ Generated in 0.020 seconds, 7 queries executed - Memory usage: 1.56 MiB (Peak: 1.77 MiB) ]
.