Fixed a friend’s laptop today

Toshiba T130, wireless decided not to play any more. I first thought it was the terrible Toshiba software which for some reason is used to enable and disable the hardware devices themselves. I guess it’s from ~2009 when wireless devices like Bluetooth and 802.11N took a lot of power, but really? Why not just utilise the OS?

I found there was a couple of possible issues with it.

Hardware

The issue we were having with this laptop was that the wireless adaptor was periodically not showing up, then it disappeared entirely (even after reboots, and a variety of things)

I followed this great Toshiba T130 disassembly guide and pulled it apart on the bench.

The wireless card is down to the left of the touch pad, with a lot of space around it. I pulled it out and checked the model number (in case I had to replace it) and it’s a Realtek RTL8191SE which is 802.11b/g/n MIMO controller in a half-size Mini PCI-E connector.

It all looked good, other than some slight tarnishing to the pins so I gave it a good clean and test-reassembled it.

This slideshow requires JavaScript.

Registry

It seems the service on the machine has a known issue where if it’s set to Manual, bad things happen.

To summarise:

  1. Open Regedit
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Ndisuio
  3. Edit the key called “Start” and set the value to 2
  4. Reboot your computer

The value’s likely to be 4 (disabled) or 3 (manual) which will either stop the automatic wireless association, or severely limit its ability to work right.

 

So far it’s all working, hopefully it’ll stay that way. :)

Boot into the GUI after changing default user in raspbian

As usual, when I go looking for something and it takes a while to find, I like to document it here as well. I found some information in this thread “Boot into the GUI after changing default user” in the Raspberry Pi StackExchange, but I had to modify it quite a lot (including the original post) to reflect the full changes required.

You can manually modify the raspi-config script as follows. Let’s presume we’re using the username “bob”.

sudo vi /usr/bin/raspi-config

Search for the function:

do_boot_behaviour() {…}

Under that, there’s a line where we will replace the “-u pi” with “-u bob”, leaving the rest of the line unchanged:

if id -u pi > /dev/null 2>&1; then

Next edit the line:

sed /etc/lightdm/lightdm.conf -i -e “s/^#autologin-user=.*/autologin-user=pi/”

By changing autologin-user=pi to be autologin-user=bob

If you want a pretty menu and also error when it occurs, edit these lines:

whiptail –msgbox “The pi user has been removed, can’t set up boot to desktop” 20 60 2

and

“Desktop” “Log in as user ‘pi’ at the graphical desktop” \

Again, replacing “pi” with “bob”, or your username of choice.