[Bug 898110] Re: please remove the Previous Linux versions sub-menu and display all kernels again
Agreed, that menu is not good. You don't know what kernel you are booting, and if you press Enter to see that, it is not obvious if this keypress could change the kernel which is going to be booted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/898110 Title: please remove the Previous Linux versions sub-menu and display all kernels again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/898110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871847] Re: Bad port '0' upon connect qemu+ssh
** Attachment added: fix for bad port 0.patch https://bugs.launchpad.net/bugs/871847/+attachment/2535037/+files/fix%20for%20bad%20port%200.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871847 Title: Bad port '0' upon connect qemu+ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-viewer/+bug/871847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871847] [NEW] Bad port '0' upon connect qemu+ssh
Public bug reported: Hi there, it's not possible to use virt-viewer --connect qemu+ssh:. anymore in Oneiric Ocelot (virt-viewer 0.4.1-1ubuntu1) because of a bug. It returns the following error during connect: Bad port '0' This is due to a bug in the C code, which I have traced. Please apply the patch in attachment to the Oneiric Ocelot virt-viewer 0.4.1-1ubuntu1 sources. ** Affects: virt-viewer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871847 Title: Bad port '0' upon connect qemu+ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-viewer/+bug/871847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 642071] Re: kexec --load does not work in maverick amd64
Ok and when is 1:2.0.1-2ubuntu2.1 expected to be uploaded in the repositories? With an apt-get update I still see the broken 1:2.0.1-2ubuntu2 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/642071 Title: kexec --load does not work in maverick amd64 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 316861] Re: Virtio not working in Hardy 64bit
Hi there, even removing -smp option wouldn't fix the problem in kvm/hardy, as I mentioned in my first post. I have not tried KVM from jaunty, I don't have a jaunty machine. I have tried kvm-84 compiled from source and it does not exhibit the problem, same as kvm-83 from source. Thanks -- Virtio not working in Hardy 64bit https://bugs.launchpad.net/bugs/316861 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 316861] Re: Virtio not working in Hardy 64bit
I have finally narrowed this problem. The key thing is the memory given to the virtual guest. The problem seems to be in Ubuntu's kvm. Please follow these instructions to reproduce: (might not be the shortest instructions to achieve the bug, sorry for that) Hardware with intel CPU and at least 4GB physical memory Host with ubuntu 8.04 64bit and Ubuntu's native KVM Make guest HD image like this: dd if=/dev/zero of=vmhd.raw count=0 seek=2 Download ubuntu-8.04.2-desktop-amd64.iso from ubuntu website on the host Configure bridge and tap0 interface, enslave tap0 to the bridge First boot is like this: kvm -m 2000 -boot d -drive file=vmhd.raw,index=0,media=disk -cdrom ubuntu-8.04.2-desktop-amd64.iso -net nic,macaddr=52:54:00:94:91:31 -net tap,ifname=tap0,script=no This will boot the VM with the ubuntu live CD open bash sudo su gparted make two ext3 partitions: 1) one for /boot filesystem, 1000MB aligned to cylinders, 2) another ext3 partition filling the rest of the disk for the / filesystem format and exit doubleclick on the installer, follow the steps, manual partitioning, assign /boot and / filesystems to the partitions. Assign machine name, login, password etc. Install everything then shutdown the VM. Now your test VM is installed. The next steps are: Boot the VM with this line: (I suggest to boot the recovery mode ubuntu kernel or anyway remove the quiet splash so to see the messages) kvm -m 2000 -boot d -drive file=vmhd.raw,index=0,media=disk,if=virtio,boot=on -net nic,macaddr=52:54:00:94:91:31,model=virtio -net tap,ifname=tap0,script=no Everything works, right? Now reboot changing the memory amount (-m option), the results should be like this: -m = 3590: everything works -m 3592--3690: kvm crashes at boot, error message: kvm: Guest sent invalid pointer -m =3691: hangs at boot because it cant find disks vda1 and vda2. If you remove virtio from the disk commandline and leave it only on the network, it will boot if memory is higher than approx 4000 (I didn't investigate for the exact number, anyway it is higher than 3691) but once booted networking will not work, no ping, nothing. kvm-83 compiled from source does not appear to have these problems. -- Virtio not working in Hardy 64bit https://bugs.launchpad.net/bugs/316861 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 316861] [NEW] Virtio not working in Hardy 64bit
Public bug reported: Binary package hint: kvm Hi there I am having problems with KVM in Ubuntu Hardy 8.04 64-bit (both host and guest) with virtio. Virtio currently does not work either as disk or as net. Hardware is HP xw6600 10GB ram, 2 x E5420 Kernel image is 2.6.24-23-server both on host and on guest (also tried -19-generic) kvm is kvm-62 1:62+dfsg-0ubuntu8 I made a bridge br0 for eth0 and tap0 I made a 170GB file as hard disk image (raw) I installed Ubuntu with kvm non-virtio (network was 1000e) because it seemed not recognizing virtio devices at install time. Everything was working without virtio. In the next boots I tried to introduce virtio but it would not work. Here is the command line: kvm -m 9000 -boot c -drive file=login_server,index=0,media=disk -net nic,macaddr=52:54:00:94:91:31,model=e1000 -net tap,ifname=tap0 -smp 8 This one works. If I put model=virtio for network, it stops working. Nothing passes, not even ping, arping, ssh, nothing. Tried even with user mode instead of tap. Virtio modules are loaded correctly in the guest. Tried unloading and reloading virtio modules, no good. Tried removing -smp option, no good. If I make two nics, one with e1000 and one with virtio with different MACs, NONE of the two works. Now if I unload the virtio modules, the virtio ethX interface correctly disappears, but the other one STILL does not work. No errors are shown in the dmesg. If I use only one e1000, that works. For the disk: virtio prevents boot. No /dev/vda appears nor /dev/disk/by-uuid. The directory /sys/block/dev/vda exists though, but I'm not sure how to use it and I don't seem to be able to mount to /root any of the entries. The root filesystem cannot be found because the by-uuid directory does not exist. I am positive that the virtio_blk, virtio_pci and virtio modules are loaded when I am dropped to the shell. I also tried rootdelay=10, no good. Only one message regarding the disk appears in the boot messages, probably meaningless: vda:4Driver 'sr' needs updating - please use bus_type methods Any idea? Thank you PS: I am not sure if the correct package for the bug is kvm or linux... ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- Virtio not working in Hardy 64bit https://bugs.launchpad.net/bugs/316861 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238327] Re: Hardy 64bit - 82801H IC8H sound stopped working at 2.6.24-17
I'm so sorry, please ignore the bug report. I hadn't installed the linux-ubuntu-modules for the new kernel, that's why it wasn't working. There is probably a bug in the dependencies though, how come the linux- image- does not depend on its modules package (and vice versa)? Thanks -- Hardy 64bit - 82801H IC8H sound stopped working at 2.6.24-17 https://bugs.launchpad.net/bugs/238327 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238327] [NEW] Hardy 64bit - 82801H IC8H sound stopped working at 2.6.24-17
Public bug reported: Subject says it all. Audio from 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) was working in hardy 64bit in kernel 2.6.24-16-anything but stopped working in 2.6.24-17-anything and 2.6.24-18-anything Computer is Dell Latitude D830. Sound card does not get detected by the driver in the newest kernels mentioned. Regarding the attachment: Instead of giving you the information (as per DebuggingSoundProblems) at the time the audio card doesn't work, I think it is more productive to run the debug stuff when the audio card WORKS, so you see exactly which model is the audio card that stopped working. (ok ok if you also need to see it when it doesn't work, tell me) The following was launched with: 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux Please note that I'm not changing ANY configuration to make it work/not work, I am just booting with different kernels. ** Affects: ubuntu Importance: Undecided Status: New -- Hardy 64bit - 82801H IC8H sound stopped working at 2.6.24-17 https://bugs.launchpad.net/bugs/238327 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238327] Re: Hardy 64bit - 82801H IC8H sound stopped working at 2.6.24-17
** Attachment added: audiodebug_works.txt http://launchpadlibrarian.net/15123972/audiodebug_works.txt -- Hardy 64bit - 82801H IC8H sound stopped working at 2.6.24-17 https://bugs.launchpad.net/bugs/238327 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146191] Re: iwl4965 does not work after resume
It might be this bug: (symptoms are similar though not exactly identical) http://bughost.org/bugzilla/show_bug.cgi?id=1539 which has just been fixed with a patch as you can see from the discussion there. You can apply the patch to the iwlwifi-1.2.22.tgz sources then compile and install. Please see the following thread suggested by Tim Gardner which has more detailed instruction for recompiling the intellinuxwireless https://bugs.edge.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/144621 I will add my comment also there This bugfix should really be included in the modules update due at the end of the year please. -- iwl4965 does not work after resume https://bugs.launchpad.net/bugs/146191 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 144621] Re: iwl4965 drops out from time to time (Santa Rosa)
I have the bug described, and also this other one probably more serious: https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/146191 which is probably the same as this http://bughost.org/bugzilla/show_bug.cgi?id=1539 and has a patch as you can see. PLEASE include the patch in the gutsy-updates. Please note that it is very recent and has not made it into the 1.2.22 intellinuxdrivers sources, it has to be applied over it. For now you can have the fixed drivers with the following steps (not as difficult as others have suggested, in my case at least): Download intellinuxdrivers package 1.2.22 sources: wget http://www.intellinuxwireless.org/iwlwifi/downloads/iwlwifi-1.2.22.tgz download the patch near to it wget http://bughost.org/bugzilla/attachment.cgi?id=1264 rename it to something more sensible mv attachment.cgi?id=1264 iwldrivers.patch unpack the driver and apply the patch tar -zxvf iwlwifi-1.2.22.tgz cd iwlwifi-1.2.22/origin patch ../../iwldrivers.patch Now download kernel 2.6.22 sources, these are needed to compile the driver. The kernel headers, as others have noticed, are not enough. I think: apt-get linux-source-2.6.22 this goes in /usr/src/linux-source-2.6.22 unpack the sources if they are compressed (I don't remember) Now as root, go back to the directory iwlwifi-1.2.22 export KSRC=/usr/src/linux-source-2.6.22 make install depmod now you should have the new drivers, installed in parallel with the ubuntu ones, that is in a separate directory, probably in /lib/modules/2.6.22-14-generic/kernel/drivers/net/wireless/ while the ubuntu older ones are probably in /lib/modules/2.6.22-14-generic/ubuntu/wireless/iwlwifi/iwlwifi/origin/ Make sure modprobe iwl4965 really loads the new drivers and not the old ones. Maybe rename the old ones. -- iwl4965 drops out from time to time (Santa Rosa) https://bugs.launchpad.net/bugs/144621 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
