Another thing to watch out for is that qemu only listens on 10.0.2.4
port 139. I just tried smbclient on feisty and it seems to try port 445
first, by default, and that ends up going straight to the host smbd
rather than the qemu-controlled phony one. Try "smbclient -p 139
//10.0.2.4/qemu" and se
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... The
see https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
You might not want to go through the trouble of building your own
kernel, especially in light of https://bugs.launchpad.net/ubuntu/+source
/kernel-package/+bug/90283
In that case, you can try out the patch that I am attaching. It goes
through alot of effort just to change two bytes in the kernel,
Real patch available now. Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel
Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.
Loki-uk, if you're desperate, you might want to try out this patch:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
I'm curious to know if it works outside of Virtual PC.
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108
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 receive
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) {
--
V
This is probably a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/91330
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108221
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108382
...and it's clearly affecting all other dist
I have the same bug running a pristine feisty install straight off the desktop
cd. This is on the free-as-in-beer Microsoft VirtualPC 2007, which uses the
tulip driver. (You'll have to do a tiny bit of xorg.conf editing to get feisty
to install on VPC2K7. When the borked install screen comes
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/12
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
Another thing to watch out for is that qemu only listens on 10.0.2.4
port 139. I just tried smbclient on feisty and it seems to try port 445
first, by default, and that ends up going straight to the host smbd
rather than the qemu-controlled phony one. Try "smbclient -p 139
//10.0.2.4/qemu" and se
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... The
This is probably a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/91330
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108221
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108382
...and it's clearly affecting all other dist
I have the same bug running a pristine feisty install straight off the desktop
cd. This is on the free-as-in-beer Microsoft VirtualPC 2007, which uses the
tulip driver. (You'll have to do a tiny bit of xorg.conf editing to get feisty
to install on VPC2K7. When the borked install screen comes
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/12
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
see https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
You might not want to go through the trouble of building your own
kernel, especially in light of https://bugs.launchpad.net/ubuntu/+source
/kernel-package/+bug/90283
In that case, you can try out the patch that I am attaching. It goes
through alot of effort just to change two bytes in the kernel,
Real patch available now. Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel
Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.
Loki-uk, if you're desperate, you might want to try out this patch:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
I'm curious to know if it works outside of Virtual PC.
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108
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 receive
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) {
--
V
Another thing to watch out for is that qemu only listens on 10.0.2.4
port 139. I just tried smbclient on feisty and it seems to try port 445
first, by default, and that ends up going straight to the host smbd
rather than the qemu-controlled phony one. Try "smbclient -p 139
//10.0.2.4/qemu" and se
This is probably a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/91330
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108221
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108382
...and it's clearly affecting all other dist
I have the same bug running a pristine feisty install straight off the desktop
cd. This is on the free-as-in-beer Microsoft VirtualPC 2007, which uses the
tulip driver. (You'll have to do a tiny bit of xorg.conf editing to get feisty
to install on VPC2K7. When the borked install screen comes
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/12
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
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... The
see https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
You might not want to go through the trouble of building your own
kernel, especially in light of https://bugs.launchpad.net/ubuntu/+source
/kernel-package/+bug/90283
In that case, you can try out the patch that I am attaching. It goes
through alot of effort just to change two bytes in the kernel,
Real patch available now. Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel
Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.
Loki-uk, if you're desperate, you might want to try out this patch:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
I'm curious to know if it works outside of Virtual PC.
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108
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 receive
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) {
--
V
Another thing to watch out for is that qemu only listens on 10.0.2.4
port 139. I just tried smbclient on feisty and it seems to try port 445
first, by default, and that ends up going straight to the host smbd
rather than the qemu-controlled phony one. Try "smbclient -p 139
//10.0.2.4/qemu" and se
Another thing to watch out for is that qemu only listens on 10.0.2.4
port 139. I just tried smbclient on feisty and it seems to try port 445
first, by default, and that ends up going straight to the host smbd
rather than the qemu-controlled phony one. Try "smbclient -p 139
//10.0.2.4/qemu" and se
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... The
see https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
You might not want to go through the trouble of building your own
kernel, especially in light of https://bugs.launchpad.net/ubuntu/+source
/kernel-package/+bug/90283
In that case, you can try out the patch that I am attaching. It goes
through alot of effort just to change two bytes in the kernel,
Real patch available now. Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel
Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.
Loki-uk, if you're desperate, you might want to try out this patch:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
I'm curious to know if it works outside of Virtual PC.
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108
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 receive
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) {
--
V
This is probably a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/91330
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108221
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108382
...and it's clearly affecting all other dist
I have the same bug running a pristine feisty install straight off the desktop
cd. This is on the free-as-in-beer Microsoft VirtualPC 2007, which uses the
tulip driver. (You'll have to do a tiny bit of xorg.conf editing to get feisty
to install on VPC2K7. When the borked install screen comes
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/12
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
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... The
see https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
You might not want to go through the trouble of building your own
kernel, especially in light of https://bugs.launchpad.net/ubuntu/+source
/kernel-package/+bug/90283
In that case, you can try out the patch that I am attaching. It goes
through alot of effort just to change two bytes in the kernel,
Real patch available now. Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel
Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.
Loki-uk, if you're desperate, you might want to try out this patch:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
I'm curious to know if it works outside of Virtual PC.
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108
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 receive
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) {
--
V
Another thing to watch out for is that qemu only listens on 10.0.2.4
port 139. I just tried smbclient on feisty and it seems to try port 445
first, by default, and that ends up going straight to the host smbd
rather than the qemu-controlled phony one. Try "smbclient -p 139
//10.0.2.4/qemu" and se
This is probably a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/91330
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108221
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108382
...and it's clearly affecting all other dist
I have the same bug running a pristine feisty install straight off the desktop
cd. This is on the free-as-in-beer Microsoft VirtualPC 2007, which uses the
tulip driver. (You'll have to do a tiny bit of xorg.conf editing to get feisty
to install on VPC2K7. When the borked install screen comes
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/12
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
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... The
see https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
You might not want to go through the trouble of building your own
kernel, especially in light of https://bugs.launchpad.net/ubuntu/+source
/kernel-package/+bug/90283
In that case, you can try out the patch that I am attaching. It goes
through alot of effort just to change two bytes in the kernel,
Real patch available now. Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel
Haven't tried it - just saw it in the patch queue:
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips.patch
http://ring.aist.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.
Loki-uk, if you're desperate, you might want to try out this patch:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/13
I'm curious to know if it works outside of Virtual PC.
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108
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 receive
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) {
--
V
This is probably a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/91330
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108221
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/108382
...and it's clearly affecting all other dist
I have the same bug running a pristine feisty install straight off the desktop
cd. This is on the free-as-in-beer Microsoft VirtualPC 2007, which uses the
tulip driver. (You'll have to do a tiny bit of xorg.conf editing to get feisty
to install on VPC2K7. When the borked install screen comes
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/87262/comments/12
--
ps2 mouse does not work in Feisty FINAL VERSION
https://bugs.launchpad.net/bugs/108382
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
72 matches
Mail list logo
