Fixing Ubuntu 7.04 Fiesty Fawn Mouse under Virtual PC 2007

Update: October 18, 2007 – Ubuntu 7.10 was released today, and I’ve now posted step by step instructions for installing it. If you haven’t yet installed Ubuntu, you may prefer to start with the instructions on 7.10, found here:

OK, one of my readers “John” (thanks John!) shared a link to an unsupported patch that fixed the Ubuntu 7.04’s mouse under Virtual PC. Let me give you the quick summary of what I did:

  1. Fired up a new VirtualPC with the Fiesty Fawn “Live CD” in the drive. Booted up in safe graphics mode.
  2. Once up, I activated the keyboard mouse using the fix I described in my post “Ubuntu 7.04 and Virtual PC 2007 – Mouse Issue Workaround (sort of)” at
  3. I then installed Ubuntu, it was pretty straightforward although a bit annoying using the numeric keypad as a mouse. One hint, sometimes it didn’t recognize my mouse click until I moved the mouse off a button then back on.
  4. After the install I rebooted, then in my new install repeated step 2 to activate the keyboard mouse in my new install. Setting this in the Live CD didn’t carry over to the new install.
  5. I then opened firefox and went to the link John provided, Since that’s a lot of typing, I shrinksterized it to make it very easy to type,
  6. Joe Soroka has posted a script, I downloaded it using the “shell script” link at the very top of the message and saved it to my home folder.
  7. I opened my File Browser (use Left Alt+F1 select Places, Home Folder). I moved the mouse (again using the numeric keypad) and clicked once on the sh file I’d saved.
  8. Now in the browser, with the file highlighted, hit left alt+enter or select File, Properties on the File Browser menu.
  9. In the dialog that appears, move to the Permissions tab, and check on the box that says “Allow executing file as program”. Click the close button to close the dialog.
  10. Now double click the sh file or press enter. You should see a dialog appear that asks if you want to open in a text editor or run the script. Select the “run in terminal” option. (Update, added “in terminal” based on feedback.)
  11. While the script executes it will ask for your admin password, give it.
  12. At one point it will also stop to ask if you want to skip or configure grub manually, or let it do it for you. I pressed enter to let the script do it for me.
  13. That ended the app, when the terminal window closed I rebooted (still using the numeric keypad as my mouse).
  14. When Ubuntu came back up, it flashed a quick message from the grub asking which kernel I wanted to load, I just took the default.
  15. I logged in and what do you know, my mouse worked!

Just FYI, I’m running Virutal PC 2007 under Vista, using the standard desktop version of Ubuntu 7.04.

The real hero here is Joe Soroka for posting such a simple fix. I encourage you to give it a try. If you are concerned about messing up your Ubuntu install, simply copy the VHD/VPC files to a backup location before running the fix.

A big thanks to Joe Soroka, and to “John” for posting the link. Now I can actually start playing with Ubuntu 7.04.


63 thoughts on “Fixing Ubuntu 7.04 Fiesty Fawn Mouse under Virtual PC 2007

  1. (the above is just useful for copying the link – and great fun to watch virtual pc’s method of pasting)

    > Step 10 should say to select the Run In Terminal option as Run does not seem to do anything
    > Also, as an alternative to parts of steps 6 and 7, it is probaly easier to save to the desktop so you don’t have to open a seperate file browser

  2. I worked fine for me, with VPC2007 on Vista32. Only problem was, because I got sick of using the keypad as a mouse really quick, I had no patience to figure out why my network wasn’t up. I used the trick to paste from the host. You have to wait for VPC to enter the entire script, one character at a time. That takes several minutes. Then you will probably have to enter your own carriage returns and tabs to make the script identical to the one displayed on the page from which you download the script. Once again though, it worked fine the first time! Oh yeah, and do select the “Run in Terminal” option for step 10, because the “Run” button does nothing at all.

  3. Thanks for the feedback, I updated the instructions with the “in terminal” text. Glad it worked for you.

    On the network issue, I had some as well when I was at work, although not at home. To fix while at work I set VPC to use “Shared Networking (NAT)” option under Networking.

    I then clicked on the network icon in the upper right area of the bar (near the clock) and picked “wired”. Ubuntu refreshed itself and connected to the internet.

    You may or may not have to do this, as I said when I got home that night Ubuntu connected to the internet with no problems, so I guess it’s something in the way the connections are setup externally to VPC/Ubuntu.


  4. Thanks for the guide, I was installing Xbuntu so not all of the steps worked but I often another way of installing it which maybe easier. I think it should also work for Ubuntu.

    1. Hit control-alt-F1
    2. Login
    3. sudo bash
    4. apt-get install lynx
    5. lynx
    6. hit ‘d’ on the “shell script” link and save it
    7. chmod +x
    8. ./
    9. reboot

    Worked for me

  5. Sorry steps 7 and 8 are missing the name of the shell script.

    7. chmod +x
    8. ./

  6. paperino’s simple approach worked like a charm. Only change is in step 4. Be sure to add the .sh to the end of the filename.

  7. Wow! That was easy! Just to summarize what I did using paprino’s easy script adding the .sh per dax to the file name. And using the Right ALT + V per Russ:

    Use the RIGHT ALT + V to paste the below lines into Ubuntu. Much easier than typing it out.

    1. reboot in recovery mode by pressing ESC on the GRUB screen
    2. wget
    3. chmod +x
    4. ./
    5. reboot

  8. I tried the script but it failed becasue I used the server CD insted of the desktop. Any suggestions?

  9. John again. This morning my Ubuntu upgraded itself to 2.6.20-16, which killed the mouse. I had to reboot to the 2.6.20-15 patched version. I do not know linux well enough to know where to patch -16, although it would be nice of somebody to fix the source.

    Anyway, just a heads up.


  10. Would love to see an updated source or instructions on how to make this work when the kernel is updated to 2.6.20-16

  11. As John reported above upgrading to 2.6.20-16 breaks the mouse again – does anyone have a fix for this yet? Is this likely to be fixed properly any time soon or have PS/2 mice been written off as unsupported?

  12. Actually Indianabeck’s solution of adding i8042.noloop to the kernel parameters works just fine with 2.6.20-16.

  13. Thank you Indianabeck, i8040.noloop fixed the problem. Now I need to figure out why I have to tell Ubuntu that it has a wired network everytime I reboot.

  14. Thank you for the mouse fix. I had been using Hoary hedgehog in Virtual PC, finally decided to upgrade, didn’t know about this mouse issue. Awesome that you have this not-too-difficult fix for us! I hope the ubuntu folks are paying attention and stick this into the next build(s).

    Thanks a lot!

  15. I should have mentioned that Hoary is v 5.04, and installed very easy, and everything (network, mouse, etc.) just worked without problem in Virtual PC. So I expected the same for 7.04. Both network and mouse took some effort to get going, but now it is working fine. Thanks again.

  16. This worked great for me until Ubuntu installed several updates, and when I rebooted the mouse died again. I tried the script again but it didn’t work that time. Any ideas?

    (Also, I am a brand-new Linux user, so I’m afraid I can’t give much technical information…)

  17. For an easy fix, do this:

    At boot option screen, press F6 and erase “splash”. Put in “i8042.noloop” (w/o quotes). This should fix it, but you’ll have to type it in every time 🙂

  18. hi guys i test it this solutions but it does not working i got the server version

    i get the msg:
    md5sum: /boot/vmlinuz-2.6.20-15-generic: No such file or directory unexpected version of /boot/vmlinuz-2.7.20-15-generic

    sombody have solution for my problem?

  19. To fix mouse you simply start vpc 2007 then when you have option to do safe graphics go to that do not click it press F6 and type at the end i8042.noloop Then press enter The mouse will work!!!

  20. É isso ae o meu funcionou perfeitamente estou usando o Windows Vista com Virtual PC 2007 e Ubuntu 7.04

  21. Kbunutu 7.10 on Virtual PC 2003

    Tested i8042.noloop in grub boot, mouse works 🙂

    In /boot/grub/menu.lst
    kernel …… splash
    kernel …… i8042.noloop

    boots fine with mouse enabled…. now onwards to get my eth0 working and install some packages, but first bed!


  22. Russell, that worked like a charm. One question is do I have to make that change each time? It didn’t save it once I shut down and restarted.

  23. Dean, I just posted instructions on how to install Ubuntu 7.10. (See my post for October 18 2007). The last few steps on editing the menu.lst should also work under 7.04.

    By the way I said it in the October 18 post, and I’ll say it again here, thanks to all the wonderful folks who added comments here, made the install for 7.10 much easier.


  24. Hi all.. i’m running Ubuntu 7.04 in Ms Virtual server and have same mouse problem. But, if I connect using VNC, my mouse work perfectly fine. I hope this help you in using the mouse to fix the mouse issue 😉

    Currently upgrading to 7.10. willl try the patch later . should work. Only issue I observed is the CPU utilizaton goes higher. Not an issue if you have a fast one like Intel core2duo e6750.

  25. Ooops.. btw mine was a working linux migrated to virtual server…and remote desktop was enabled. In case of installing a new one, the remote desktop will be still disabled. so..not pretty useful. I have tried editing grub. Will let you know once I restart.

  26. Bailey said:
    At boot option screen, press F6 and erase “splash”. Put in “i8042.noloop” (w/o quotes).

    This worked for me and it also cured my graphics problem. In normal mode graphics were corrupt, in safe mode everything was too big so I couldn’t see the whole screen.
    This is in MS VPC2007 under a Vista x64 host.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s