menu.

I’ve posted twice recently about my problems following an upgrade of Ubuntu Netbook Remix to Lucid Lynx (10.04).  In short, I upgraded both the BIOS of the netbook (an Asus Eee PC 1008HA) and upgraded Ubuntu from 9.10 (Karmic Koala) to 10.04 (Lucid Lynx).  Once I did this the sound would disappear after the first time I logged in following each boot, and only work properly if I logged out and in again.

One kind commenter (thank you “ThrasherC”) suggested a solution to a similar problem.  I haven’t followed the story of the bug report and probably don’t know enough about Linux to understand it so I’m not taking responsibility for anyone else doing this. This is a statement of what I did, not advice

1. Open a new terminal
2. Issue command “sudo gedit /etc/pulse/default.pa”
3. Find the line that says “load-module module-device-restore” and creplaceomment it out by adding a hash at the start so it reads “#load-module module-device-restore”
4. Restart

Hope this helps someone – be that you, or me in the future.

Right, at the weekend I upgraded my Asus Eee PC (1008HA for those of you interested) to Ubuntu 10.04 LTS – Lucid Lynx from the previous version, 9.10.  Everything seemed fine (I think).

Update: The problem described in this post has subsequently been investigated and solved.

On Monday or Tuesday night I then upgraded the BIOS to see if it would fix the fact that the wireless was shite when I was using Ubuntu.  (Incidentially either the BIOS or OS upgrade seems to have fixed the probelms I had connecting to one specific router)

I didn’t notice a problem at the time because I’m dual booting Windows XP and was using that, but when I booted into Ubuntu again on Thursday night, the audio didn’t seem to be working.  I quickly discovered that the sound did indeed work at the login screen, but once I logged in there was nothing (including no welcome sound).  The audio/volume functions on the Fn keys also now do nothing (though brightness ones still work!)

I think the sound was fine following the Ubuntu upgrade, but I’m not sure, so I think the BIOS upgrade has ballsed it up.  Which is a pain.  It looks like I’ll have to try reverting the BIOS and/or Ubuntu to a previous version.  Watch this space…

Had a bitch of a day today in work, with an application I was playing with refusing to play with Active Directory (largely because I’ve never used LDAP before and couldn’t figure out the weird bloody syntax).

So I’d really like to offer a quick thank you to Jarek Gawor for developing (and releasing) his LDAP Browser/Editor which let me double check that I was connecting to the right server/port and play with the settings enough that I eventually got it sussed. Great wee Java tool.

I have my Acer Aspire laptop dual booting Ubuntu Linux with Windows XP but, despite being sympathetic to Linux and interested in learning more about it, I don’t use Ubuntu very often.  One major reason for this was the amount of time it takes to boot up.  Over time I noticed an error message and looking at it began to suspect that this error was partially responsible for the long load times.

There are differences between boot sector and its backup
… [sequences of numbers]…
Not automatically fixing this

According to this forum thread, it seems like this error may have been let loose when I changed the grub configuration to make the OS names a bit more user-friendly and have the system stop booting into Ubuntu by default (the girlfriend isn’t converted yet and even I preferred Windows for regular use). This seems to affect the MBR, which doesn’t overwrite the backup and therefore causes the above problem.

SimonU at UbuntuForums had the same problem on his Ubuntu laptop and posted a solution which I decided to borrow.

sudo cp /etc/init.d/checkfs.sh /etc/init.d/checkfsbackup.sh
sudo rm /etc/init.d/checkfs.sh

I had already hit the button to restart my PC when I thought to myself “I really should have looked at what it was doing  and made sure it was doing it to the right hard drive for my system” and started worrying that I may have just made my machine unbootable. Luckily all was ok and my laptop now boots into Ubuntu in a fraction of the time it had taken before. If I could only figure out how to stop Ubuntu overheating the laptop so much and causing the fan to run at full pelt, I’d maybe use it on a regular basis.

If that doesn’t work for you another thread talks about skipping the file system check (fsck) on FAT32 drives as an alternative solution.