As requested by Leann Ogasawara:
I have confirmed this to an issue in Ubuntu 8.04.1 (Hardy) with kernel
2.6.24-19-386.
This problem also affects the lastest linux kernel and at the time I
wrote this it was, 2.6.25.6.
Adding i8042.noloop to the kernel parameters fixes the problem in hardy
as
I'm just curious why this report is also targeted against the Hardy
kernel but there are no comments here regarding this being in issue with
Hardy. I'm marking this Invalid against the Hardy kernel for now until
we receive further information.
Also, I'm reassigning the Ubuntu Hardy kernel source
** Also affects: linux-source-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
** Changed in: linux-source-2.6.20 (Baltix)
Status: New = Fix Released
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Incomplete = Fix Released
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: linux-source-2.6.20 (Baltix)
Importance: Undecided
Status: New
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Phillip's kernel parameter fixes the no mouse issue for 7.10 in VirtualPC 2007.
Thanks!
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Yeah! the fix is already work on gutsy with kernel 2.6.22 thx!
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Sorry to be so Unix stupid but I downloaded the Joe Soroka two byte
patch script but don't know how to run it. Could someone help me out?
Dab
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is
indianabeck: the two byte patch will only work on 2.6.20-15.27 (not the
latest 2.6.20-16.28). Adding the kernel parameter i8042.noloop is a
better way, this is effectively what the two byte patch achieves, and it
is kernel version independent.
--
Virtual PC and feisty fawn
To: David A. Beck
Subject: [Bug 87262] Re: Virtual PC and feisty fawn
indianabeck: the two byte patch will only work on 2.6.20-15.27 (not the
latest 2.6.20-16.28). Adding the kernel parameter i8042.noloop is a
better way, this is effectively what the two byte patch achieves, and it
is kernel version
On 5/31/07, David A. Beck [EMAIL PROTECTED] wrote:
Philip,
Thanks. Can you tell me how I would add the kernel parameter? Do I edit
a file like I did when I added the tulip network driver?
This is probably covered in a FAQ somewhere. A google brings this up,
which is a good description of
Hot Zig! Phillip This fixed 7.04 for me on Virtual PC 2007. :)
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=223606
There appears to be a less invasive workaround at the bottom of this bug report.
Add the kernel parameter i8042.noloop (without the quotes). This cause
Virtual PC 2007 to behave as expected for me.
--
Virtual PC and feisty fawn
How did you calculate the offset to the patched code in the patch script above?
I want to apply the same patch to the new security update kernel 2.6.20-16.28
which has been published. I can see how to update the script apart from
calculating the offset.
Bill
--
Virtual PC and feisty fawn
I don't remember precisely how I got the offset. Basically, I went to
build the kernel the normal ubuntu way, but I changed the 250ms to
something else, which ended up being easily searchable. Then also,
somehow, due to some bug in the build process, I ended up with an
uncompressed vmlinux...
** Attachment added: Edgy dmesg
http://librarian.launchpad.net/7779687/dmesg.log
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: Edgy lspci -vvvnn
http://librarian.launchpad.net/7779690/lspci.log
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Another dmesg from Virtual PC 2007.
** Attachment added: dmesg virtual pc 2007
http://librarian.launchpad.net/7729521/C%3A%5CUsers%5Cmandrews%5CDesktop%5Cdmesg.txt
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a
The attached is the lspci -vvvnn output from feisty under vpc 2007, like
the previous dmesg.
** Attachment added: lspci.txt
http://librarian.launchpad.net/7732873/lspci.txt
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are
Regarding the diffs in the patch queue that I mentioned above... I just
tried building a kernel with them, and it didn't help. I even increased
the timeout from 100*50us to 1*50us and it didn't make a difference.
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You
Also, I said in my description above that:
Basically all it does is change the bytes corresponding to line 631, from
msecs_to_jiffies(250)) == 0) {
to
msecs_to_jiffies(250)) + 2) {
That's just not true... It does the opposite. It's more like
msecs_to_jiffies(250)) == -2) {
--
I just tried the script from the previous post and it is working for me.
VPC now correctly captures the mouse when I click in the VPC window and
I can navigate with it normally. Thank you for working on this problem.
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You
I would also like to confirm that the patch supplied worked just fine.
A very elegant patch, did a good job of making backups.
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I third that confirmation. Upgraded from 6.10 to 7.04 on VPC-2007 and lost
mouse capture. The patch worked great.
Thank you.
--
Virtual PC and feisty fawn
https://bugs.launchpad.net/bugs/87262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
No, the idea is that once you enter a working VM, mouse and keyboard are
captured by the virtual machine and the host machine cannot see them.
You press a key, usually Right Alt (but this is user configurable), to
tell the VM to let go and allow you to do other things on the host
machine (answer
I confirm that I have the same problem. My virtual Edgy install worked
OK, but I upgraded to Feisty via the Update Manager and now the mouse
does not work.
The Virtual PC software does not appear to 'capture' the mouse pointer
when you click on the virtual machine. Normally the windows pointer
Looks like the issue might be in the 2.6.19 kernel and later.
Other distros are reporting the same problem:
http://www.linuxquestions.org/questions/showthread.php?t=521011
http://www.linuxquestions.org/questions/showthread.php?t=510698
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=223606
Normally the windows pointer
disappears and the virtual machine pointer starts to move (but is
trapped inside the virtual machine). You must release the pointer by
pressing a magic key.
Hi! Thanks for the input! Perhaps I am misunderstanding but does that
last sentence imply the mouse can be
Same problem here. Installing Feisty Fawn under Virtual PC and the mouse
is frozen in the center of the screen. The keyboard APPEARS to work
because I can change virtual terminals. But I cannot access any desktop
items via any keyboard hot keys or shortcuts. Anyone have any idea how I
can get the
Well, if you really cannot wait for a fix, there is a very bad alternative:
the accessibility options. Use alt-F1 to access the menu options, and
use the keyboard to move over to preferences - keyboard. You can
use the tab key to move among the options, and go down to accessibility.
You can then
Well, if you really cannot wait for a fix, there is a very bad alternative:
the accessibility options. Use alt-F1 to access the menu options
Todd, thanks a ton! I'm a newbie and just excited to try it out.
That'll get me going! I appreciate your taking the time to write. Take
care!
Matthew
--
I'm experiencing this also - here is some more information that might be useful.
Under 6.10, /proc/bus/input/devices has this in it for the mouse:
I: Bus=0011 Vendor=0002 Product =000a Version=
N: Name=TPPS/2 IBM TrackPoint
P: Phys=isaa0060/serio1/input0
S: Sysfs=/class/input/input2
H:
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) = Kyle McMartin
--
Virtual PC and feisty fawn
https://launchpad.net/bugs/87262
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
On feisty is possible to boot to X but mouse pointer is still freeze on
center screen and not possibile to move with mouse!
I have posted the output the dmesg of feisty and edgy (on virtual pc) to
phpfi.com:
http://phpfi.com/217921 (feisty)
http://phpfi.com/ 217924 (edgy)
On feisty have
Thanks for your report, can you please attach the output of dmesg from
when it works on edgy, and if you not boot to X in feisty, please attach
a dmesg from there as well. Without this, it's impossible to fix your
bug.
Thanks,
Kyle
** Changed in: linux-source-2.6.20 (Ubuntu)
Status:
** Changed in: Ubuntu
Sourcepackagename: None = linux-source-2.6.20
--
Virtual PC and feisty fawn
https://launchpad.net/bugs/87262
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
37 matches
Mail list logo
