Skip to main content

Upgrading from Intrepid (8.10) to Jaunty (9.04)

This is kind of funny. I decided to let my machine upgrade from Intrepid Ibex (8.10) to Jaunty Jackalope (9.04) while I was in meetings all morning on Thursday. Great idea, I thought - let my machine toil away while I was away. And I was right (for the most part). I came back to a fresh, shiny new OS with better support for my machine than previously.

At work, it was an awesome new user experience with all kinds of improvements over Intrepid and since I've only been using Intrepid for a couple of weeks, THOUSANDS of improvements over my previous installation of Windows XP.

However, I had driven to work yesterday and hadn't had the normal 2 hours of bus riding to test out all the multimedia stuff. Today I did and ran into a serious problem. No support for playing back mkv, avi, mp4 or other video formats in Totem or VLC! When I went to launch the video, the program would crash with something similar to this error (reposted from another user with the same issue since I've resolved it on mine and can't reproduce the exact error):
Binary package hint: xserver-xorg-video-intel

xine, mplayer, or totem all crash when attempting to play any video file with an error like this one from xine:
This is xine (X11 gui) - a free video player v0.99.6cvs.
(c) 2000-2007 The xine Team.
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 132 (XVideo)
Minor opcode of failed request: 19 ()
Serial number of failed request: 4731
Current serial number in output stream: 4732

This worked in Intrepid and does not work since updating to the Jaunty
As he said, this worked perfectly in Intrepid and stopped working in the newly released Jaunty. I did a bit more digging on why this was and found that they had upgraded some things such that DRI2 no longer worked with the newer version of the Intel graphics driver needed for the D430 (specifically, the Intel 945).

DOH! Now I was certain I'd either have to switch my virtual desktop size down to only allow monitor mirroring in order to get videos to work, or I'd have to downgrade to Intrepid again. Big doh. I haven't done a downgrade in Linux before and I wasn't sure what, if anything could go wrong... Then I stumbled across a possible solution. Downgrade the graphics driver to an older version than ships with Jaunty. 3D effects on the desktop would likely not work very well, if at all, but they never did (let's face it, the D430 isn't exactly a gaming machine!). Worth a shot, especially if I was considering downgrading anyway.

After following the instructions here, I rebooted and found that I could now set my virtual desktop back to normal size AND still watch my videos! Sweet success...

For anyone else out there wondering if they should upgrade their D430 or any laptop with an Intel 945 graphics card, fear not. There is a viable solution that doesn't severly hamper your experience. Why they shipped with this craptastic driver is beyond me. But they did. And because it's Linux, we can deal with it anyway. :)

Please post if a patch comes out for this. Thanks muchly!

UPDATE: With the old driver, I am noticing some lag when scrolling large pages such as full-screen Firefox... It looks like there are some issues even with this driver. :(

UPDATE2: I've leapfrogged to the xserver-xorg-video-intel 2.7.1 version driver. It seems to be working as good as 2.4 but there is still a noticable lag when scrolling pages of text (Firefox). :(

Comments

Popular posts from this blog

Black Cursors on Win7/2008 R2 Using rdesktop for Ubuntu 10.04

I recently setup a Win 2008 R2 VM and proceeded to remote connect to it from Ubuntu 10.04. Everything worked perfectly except the mouse cursors were black (and some were corrupt). Solution? Use a newer version of rdesktop that doesn't ship with Ubuntu. There is a handy PPA that can be added using the following command: sudo apt-add-repository ppa:ricolai/ppa sudo apt-get update sudo apt-get install rdesktop [UPDATE] It appears ricolai may have removed the package from his PPA. To remedy the situation, I've uploaded the working binaries for x64. Sorry, I don't have the x86 any longer. More information on the bug can be found here: https://bugs.launchpad.net/ubuntu/+source/rdesktop/+bug/385974?comments=all

Getting the Hauppauge WinTV-HVR-2250 to work in Ubuntu 10.04

Really just posting this for my own reference later, but here's the link and the details: Enter this into your Terminal it is the code for the firmware and to install it Code: wget http://www.steventoth.net/linux/hvr22xx/22xxdrv_27086.zip wget http://www.steventoth.net/linux/hvr22xx/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip wget http://www.steventoth.net/linux/hvr22xx/extract.sh Code: sh extract.sh;sudo cp *fw /lib/firmware you need to install mercurial and build essential for the next steps Code: sudo apt-get install mercurial libncurses5-dev then we need the driver using this command to fetch Code: hg clone http://kernellabs.com/hg/saa7164-stable/ now change to the directory Code: cd saa7164-stable then run make Code: make CONFIG_DVB_FIREDTV:=n that will take some time, go grab a drink and wait it out, when it completes run this command Code: sudo make install wait for that to complete and reboot from the command line Code: sudo reboot Note that an application like TVtime will not

Mounting VMware VMDK Disks in Ubuntu (Linux)

Took me a while to find the info on this, but it's fairly simple once you piece together all the information out there. First off, I'm not converting this to VirtualBox. I'm simply accessing the HD as though it were mounted on my local file system (Ubuntu). The VMDK image is for a WinXP virtual machine. First off, verify you have vmware-mount on your system. Drop to terminal, type "vmware-mount". You should get info regarding usage. If not, you need to install VMware Server or VMware Workstation (it's bundled with them). When prompted during the install, say 'Yes' to installing the additional tools packages. Not sure which one it's in, but it's there. Sorry, perhaps someone else can clarify this point. Next, navigate to the location of your VMDK and type "vmware-mount -p .vmdk". This will show you a list of mount points within the file (first column). Create /mnt/ using "mkdir /mnt/ " Next, type "sudo vmware-m