ref: eb07ec1213e2552c1bcf79a9615fc7e646ba82a7
dir: /changeblog/1608028434.ms/
.HTML 9front on Lenovo Thinkpad Twist
.TL
9front on Lenovo Thinkpad Twist
.LP
A few weeks ago I removed archlinux from my remaining machine.
I noticed how the new lenovo keyboards aren't good and the trackpoint is crap.
That's why I still prefer the Thinkpad T61, even without battery.
.PP
Anyways, I'll try to describe the process of the installation.
The installation itself went according to the FQA, I'll just add some notes.
.SH
Process
.PP
First I had to disable UEFI completely and switch to legacy BIOS.
I know 9front can handle UEFI somehow, but I never got it working on any machine.
To make 9front work with legacy BIOS I had to change the SSD layout from GPT to MBR.
This was possible, just remove all partitions and use the command line to create DOS partitions.
Then the SSD was detected as MBR/non-GPT and I could proceed with default installation.
.PP
After installation I needed to get WIFI working.
Thanks to 9front developers I was able to use BSD drivers as documented in the FQA.
In my case I just grabbed the
.CW iwn-2030
drivers, placed them in
.CW /lib/firmware
and built the kernel from scratch.
.PP
Enabling ACPI in the
.CW plan9.ini
and starting
.CW aux/acpi
went without errors, only
.CW "bad opcode"
warnings showed up.
Still, everything works as expected, so I didn't investigate further.
.SH
Issues and Troubleshooting
.LP
I had exactly
.B two
issues.
The first is the
.CW "bad opcode"
as described earlier.
.PP
The second is a big surprise.
Backlight controls work out of the box!
I know older machines handle this directly without using the operating system, but this was a modern machine.
Still it worked with only one tradeoff:
.PP
It always prints
.I lapicerrors
on the console.
I didn't find a good way to disable them, so I just added a hidden window in my riostart that just
.CW cat /dev/kprint
so the errors don't fill the screen.
.SH
Bonus: conntosrv
.LP
As a bonus I have a small script that saves me lots of installation time.
I have a server with my $home directory, including some configuration in my
.CW lib/profile .
On my terminals (laptops) I just work in my $home like it was right there on my machine.
.PP
To make this happen I placed the little script in my terminal's
.CW /cfg/$sysname/conntosrv
and called in the
.CW /cfg/$sysname/termrc .
.PP
The script contains:
.P1
#!/bin/rc
echo -n 'connect to server: '
server=`{read}
if(~ $#server 0){
echo not connecting to services >[1=2]
exit
}
if(! test -e /net/dns)
ndb/dns -r
auth/factotum
for(i in $server){
rimport -Cc $i /n/$i
}
bind -c '/n/'^$server(1)^'/usr/'^$user /usr/$user
.P2
.PP
As you can see, the scrips connects to all servers you input at the prompt.
It takes the first to be your $home, all others are imported to
.CW /n .