We should make sure that the Wiki has the correct information / instructions, and then point the users to it;
Wiki - Pinebook Pro - Trackpad
As usual, feel free to correct, improve or comment, (good or politely bad).
--
Arwen Evenstar
Princess of Rivendale
Anyone with an ANSI unit willing to help test the ANSI FW PM me please
(01-08-2020, 07:36 PM)bcnaz Wrote: (01-08-2020, 06:09 AM)Arwen Wrote: We should make sure that the Wiki has the correct information / instructions, and then point the users to it;
Wiki - Pinebook Pro - Trackpad
As usual, feel free to correct, improve or comment, (good or politely bad).
( Is this a dumb Question ? )
Could downloading the firmware be called "step one" ?
Then step one would be called step two ?
And step two would become step three ?
Or am I not understanding something in this process ?
Also when Luke first posted this firmware 'update' he mentioned "needing a 'usb keyboard' "
While the Wiki says a 'usb mouse' is needed ?
Thanks for Clarifying this, BC
Or maybe word the the Wiki to say "first download the firmware" then proceed with step one, then step two ?
Mis-installed firmware is a bit harder to correct than mis-installed software ?
I'll take a look at clarifying the Wiki trackpad firmware update instructions, when I do the update on my ISO model, (not done yet). That might be this weekend.
--
Arwen Evenstar
Princess of Rivendale
So I'm getting 'command not found' errors at step 1
rock@Debian-Desktop:~/pinebook-pro-keyboard-updater$ sudo ./updater step-1 ansi
[sudo] password for rock:
sudo: ./updater: command not found
I just received my Pinebook Pro ANSI today. After seeing this thread, I immediately updated the firmware following the instructions in the original post.
I wanted to note that after running the step-1 script, my keymap changed and I could not run the reboot command. I tried fumbling my way thought the keys to figure out the new keymap and I eventually gave up and used the power button. On reboot, the wrong keymap was still active so I couldn't log in. Luckily I had a USB keyboard I could plug in and login and run setp-2. After step-2 I was able to reboot and on boot up, the keymap was back to normal.
You may want to post a warning about this as someone without a USB keyboard may not have been able to easily workaround it.