[Bug 50385] Re: samba can't be launched by a normal user (qemu related)
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 see if that helps. -- samba can't be launched by a normal user (qemu related) https://bugs.launchpad.net/bugs/50385 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87262] Re: 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... Then I found, inside the vmlinux, the 'easily searchable' number from above, I disassembled the bytes around it and figured out which ones matched with which source lines... and, well, there ya go. Not exactly easily repeatable. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87262] Re: Virtual PC and feisty fawn
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) {
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87262] Re: Virtual PC and feisty fawn
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 received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 108382] Re: ps2 mouse does not work in Feisty FINAL VERSION
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/108382 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87262] real patch available?
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.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips-fix.patch -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 108382] Re: ps2 mouse does not work in Feisty FINAL VERSION
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/people/akpm/patches/2.6/2.6.21/2.6.21-mm1/broken-out/input-fix-aux-port-detection-with-some-i8042-chips-fix.patch -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87262] a two byte patch
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, from "85
c0 test eax, eax" to "40 40 inc eax inc eax". It's based very loosely
on the discussion at http://www.cpqlinux.com/binary-kernel.html which is
somewhat out of date, and doesn't work.
Anyway, I'm posting this here because Virtual PC users can stand the
pain of a binary kernel patch. If it doesn't work or borks things up,
you just chuck out your 'undo' disk. It would probably work for the
people waiting on https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/108382 as well, but it's a little more risky for
them.
Having said that, it doesn't change much. It leaves the old kernel in
place, and comes with an uninstaller script, so it might be worth a try
for them too.
Security-wise, your on your own. Running a shell script that requires
sudo, which then patches your kernel in obscure ways is not something to
be taken lightly. Have a good look through the script before you run
it.
Basically all it does is change the bytes corresponding to line 631, from
msecs_to_jiffies(250)) == 0) {
to
msecs_to_jiffies(250)) + 2) {
** Attachment added: "shell script"
http://librarian.launchpad.net/7583925/unsupported-patch-for-87262.sh
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 108382] a stop-gap patch script for the adventurous
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 108382] kinda solved for virtualpc
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89295] Re: no carrier detection for ethernet
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 up, switch to a text console and change DefaultDepth 24 to DefaultDepth 16, then switch back and ctrl-alt-backspace it) - AMIBI0S(C)2001 American Megatrends, Inc. BI0S Date: 02/22/06 20:54:49 Ver: 08.00.02 Press DEL to run Setup Checking NVRAM.. 512MB 0K Auto-Detecting Pri Channel (0)...IDE Hard Disk Auto-Detecting Pri Channel (1)...Not Detected Auto-Detecting Sec Channel (0)...CDR0M Auto-Detecting Sec Channel (1)...Not Detected Pri Channel (0): 1. 1 Virtual HD Starting up ... [ 19.281252] isapnp: checksum for device 1 is not valid (0x89) [ 19.289884] isapnp: checksum for device 2 is not valid (0xbe) Loading, please wait... kinit: name_to_dev_t(/dev/disk/by-uuid/----0fff) = h da5(3,5) kinit: trying to resume from /dev/disk/by-uuid/----0 ac1 kinit: No resume image, doing normal boot... Ubuntu 7.04 feisty tty1 feisty login: root Password: Last login: Fri May 4 00:22:21 2007 on tty1 Linux feisty 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 The programs included with the Ubuntu system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Ubuntu comes with ABS0LUTELY N0 WARRANTY, to the extent permitted by applicable law. [EMAIL PROTECTED]:~# dpkg -l network-manager Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii network-manage 0.6.4-6ubuntu7 network management framework daemon [EMAIL PROTECTED]:~# grep carrier /var/log/syslog May 4 08:21:40 feisty NetworkManager: ^Ieth0: Driver 'tulip' does not support carrier detection. ^IYou must switch to it manually. [EMAIL PROTECTED]:~# dmesg |grep 'eth.*link' [EMAIL PROTECTED]:~# cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet dhcp
[Bug 87262] semi-solved?
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 distros too, so this might not
be the right place, but here goes.
See line 630 of /usr/src/linux-source-2.6.20/drivers/input/serio/i8042.c:
-
if (wait_for_completion_timeout(&i8042_aux_irq_delivered,
msecs_to_jiffies(250)) == 0) {
/*
* AUX IRQ was never delivered so we need to flush the controller to
* get rid of the byte we put there; otherwise keyboard may not work.
*/
i8042_flush();
retval = -1;
}
-
Commenting out the i8042_flush(); and retval = -1; lines 'fixes' the problem.
before:
$ dmesg | grep "i8042 AUX" || echo nothing
nothing
after:
$ dmesg | grep "i8042 AUX" || echo nothing
[ 69.766263] serio: i8042 AUX port at 0x60,0x64 irq 12
BTW I increased the timeout from 250ms to 20 seconds, and it didn't make
a difference, so that's not it. It's just not responding at all.
This bug is marked as being of 'Undecided' importance and 'Needs Info',
perhaps due to its "eau de M$", but the aforementioned probable dupes
are marked as 'High' importance and 'Confirmed' status. I hope this
'Info' can expedite the help for all those other people suddenly without
a mouse on their primary, non-virtual, machines.
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
