[Bug 407202] [NEW] Ondemand CPU Frequency Causes Crash on MSI MS-7093 Motherboard
Public bug reported: The MSI MS-7093 motherboard using a Phoenix BIOS, has a known issue where CPU frequency scaling does not work. Ubuntu 9.10 Alpha 3 attempts to use the 'ondemand' CPU frequency scaler by default. The result is a white screen of death where the entire screen turns white and the system is unresponsive. This happens shortly after boot. Workaround: 1. sudo apt-get install rcconf 2. sudo rcconf 3. Scroll down to 'ondemand' and disable it. Then restart. Preferred Solution: Ubuntu scans for this motherboard and automatically disables ondemand if it finds it. lshw output: *-core description: Motherboard product: MS-7093 physical id: 0 *-firmware description: BIOS vendor: Phoenix Technologies, LTD physical id: 0 version: 6.00 PG (03/02/2005) size: 128KiB capacity: 448KiB capabilities: isa pci pnp apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp ls120boot zipboot biosbootspecification ** Affects: ubuntu Importance: Undecided Status: New -- Ondemand CPU Frequency Causes Crash on MSI MS-7093 Motherboard https://bugs.launchpad.net/bugs/407202 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 134180] Re: X does not start after 8/22 fglrx update
I too experience this bug. I have an ATI Radeon xpress 200 (RS480), and when I enable fglrx through the restricted drivers manager, and restart X, the screen will flicker for several moments and then dump me into failsafe mode. I copied my xorg.conf file over from my working Feisty install, and it works as expected. -- X does not start after 8/22 fglrx update https://bugs.launchpad.net/bugs/134180 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 133502] Re: [gutsy] PlaneShift segmentation fault on Gutsy
** Changed in: ubuntu Status: New = Invalid -- [gutsy] PlaneShift segmentation fault on Gutsy https://bugs.launchpad.net/bugs/133502 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 141315] Re: Desktop CD fails to boot because of 8139cp driver
Upon further investigation I have found that the problem does not like in the 8139cp driver. By default, Ubuntu simply does not display all kernel messages (boots quiet) and this was the last message that was displayed in quiet mode, but was not the actual cause of the hanging at boot. ** Changed in: linux-source-2.6.22 (Ubuntu) Status: New = Invalid -- Desktop CD fails to boot because of 8139cp driver https://bugs.launchpad.net/bugs/141315 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 133502] Re: [gutsy] PlaneShift segmentation fault on Gutsy
This is not a bug in Ubuntu. When a segmentation fault occurs, it is an error in the program that is running, and Planeshift isn't an application that is supported by Ubuntu. You'll need to forward this bug report on to them. -- [gutsy] PlaneShift segmentation fault on Gutsy https://bugs.launchpad.net/bugs/133502 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 141315] Desktop CD fails to boot because of 8139cp driver
Public bug reported: Binary package hint: linux-source-2.6.22 Distribution: Ubuntu Gutsy Gibbon - Tribe 5 Architecture: Occurs on both x86 and AMD64 CDs Disk Type: Desktop / LiveCD Package: Linux 2.6.22 Hardware: Realtek 8139 (0x8139) Description: Upon booting the Desktop CD an error occurs when the kernel attempts to load the 8139cp driver. This error occurs on the default boot parameters and with noapic nolapic. Disabling ACPI appears to bypass this issue, although on my particular machine, it hung at a later point in the boot procedure, so I cannot confirm whether disabling ACPI is a valid solution. Error: 8139cp is not an 8139C+ compatible chip Try 8139too driver instead ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New -- Desktop CD fails to boot because of 8139cp driver https://bugs.launchpad.net/bugs/141315 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 141355] Re: Atheros AR511 not connecting to networks
If you read the dmesg output, you will see that it says If a device doesn't work, try pci=routeirq. When you load GRUB, highlight your kernel, then hit 'e'. Move to the second line and hit 'e' again. Then add pci=routeirq (without quotes) to the end of the string. Don't delete anything that is already there. See if this makes any difference. -- Atheros AR511 not connecting to networks https://bugs.launchpad.net/bugs/141355 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 141315] Re: Desktop CD fails to boot because of 8139cp driver
** Description changed: Binary package hint: linux-source-2.6.22 Distribution: Ubuntu Gutsy Gibbon - Tribe 5 Architecture: Occurs on both x86 and AMD64 CDs Disk Type: Desktop / LiveCD Package: Linux 2.6.22 Hardware: Realtek 8139 (0x8139) Description: Upon booting the Desktop CD an error occurs when the kernel attempts to load the 8139cp driver. This error occurs on the default boot parameters and with noapic nolapic. Disabling ACPI appears to bypass this issue, although on my particular machine, it hung at a later point in the boot procedure, so I cannot confirm whether disabling ACPI is a - valid solution. + valid solution. Everything works fine in Feisty with noapic nolapic + and nothing more. Error: 8139cp is not an 8139C+ compatible chip Try 8139too driver instead -- Desktop CD fails to boot because of 8139cp driver https://bugs.launchpad.net/bugs/141315 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 97681] Re: bochs CRASHES!!!
I had problems with this too. The bochs package in Ubuntu 7.04 (Feisty Fawn) is missing a couple of things. I'll start from scratch on how to install it. You must have the universe repository enabled. 1. sudo apt-get install bochs bochs-x bochs-sdl bochs-svga bochsbios bximage vgabios 2. Download the following file... http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/vgabios/vgabios/VGABIOS-lgpl-latest.bin?rev=HEAD 3. Save the file as /usr/share/bochs/VGABIOS-lgpl-latest. Notice I removed the .bin part. 4. Download and test a disk image from http://bochs.sourceforge.net/diskimages.html 5. cd into the images directory and run bochs. Everything should work. Note: Depending on your system and the disk image you download, you may need to adjust your IPS and VGA_UPDATE_INTERVAL or it will lag to death. See the Bochs documentation for more information at http://bochs.sourceforge.net/cgi- bin/topper.pl?name=New+Bochs+Documentationurl=http://bochs.sourceforge.net/doc/docbook -- bochs CRASHES!!! https://bugs.launchpad.net/bugs/97681 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 63531] Re: complete freeze of computer
I too have the same issue with an Athlon64 processor in Ubuntu 7.04 (Feisty Fawn) x86-32. The only way to avoid system crashes was to disable ACPI (acpi=off) or to uninstall powernowd. Since I have uninstalled powernowd, everything has been operating smoothly. No crashes, X no longer freezes when I attempt to logout, and I am able to properly put my computer into sleep mode and awaken it. I looked through the log files and could not find anything out of the usual. They just show my computer rebooting with no error reports before that. The entire system was locked up (ctrl-alt-backspace didn't work, nor did ctrl-F1) but my keyboard's lights didn't flash to indicate any kind of a kernel panic. -- complete freeze of computer https://bugs.launchpad.net/bugs/63531 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 19247] Re: Hang on connection to FTP, with cancel
I'm using the latest version of feisty and I am having this problem as well. It sometimes happens even when transferring small files (less than 5kb). It would appear as though there is no timeout for FTP connections. I don't even have to click cancel though. I just have to be transferring items via FTP and if the connection somehow drops, it will hang. -- Hang on connection to FTP, with cancel https://launchpad.net/bugs/19247 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86351] Re: NetworkManager crashes when configuring zd1211 wireless device
Fixed in Herd 4 ** Changed in: network-manager (Ubuntu) Status: Unconfirmed = Fix Released -- NetworkManager crashes when configuring zd1211 wireless device https://launchpad.net/bugs/86351 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86351] Re: NetworkManager crashes when configuring zd1211 wireless device
** Description changed: Binary package hint: network-manager Distribution: Ubuntu 7.04 Feisty Fawn - Herd 3 Hardware: Zonet ZEW2501 Chipset: zd1211b Driver: zd1211rw Description: - Upon attempting to configure this wireless device with NetworkManager, the window disappears and NetworkManager returns to the system tray. I am unable to configure this device because the window goes away in what appears to be a crash although it is still active in the tray and can be reopened. 'ifconfig' and 'iwconfig' both show the device and report not conflicts. The system logs appear normal and I didn't find any unusual behavior. + Upon attempting to configure this wireless device with NetworkManager, the window disappears and NetworkManager returns to the system tray. I am unable to configure this device because the window goes away in what appears to be a crash although it is still active in the tray and can be reopened. 'ifconfig' and 'iwconfig' both show the device and report no conflicts. The system logs appear normal and I didn't find any unusual behavior. Attempted Solutions: Believing it was a hardware conflict I have tried booting Ubuntu with the following additional parameters... noapic nolapic noapic nolapic pci=noacpi - disables IRQ11 used by the device and causes it to not appear noapic nolapic pci=noacpi irqpoll acpi=off - disables the device when used with any of the above parameters Steps to Reproduce: 1.) Boot with Zonet ZEW2501 (zd1211b) in Feisty Fawn Herd 3 2.) Click the NetworkManager icon in the top right 3.) Select the wireless device from the list 4.) Click 'Properties' 5.) The properties dialog may appear briefly for a few seconds before all NetworkManager windows disappear. Both the properties and the nm window vanish, but NetworkManager is still running in the system tray on the top right. -- NetworkManager crashes when configuring zd1211 wireless device https://launchpad.net/bugs/86351 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86351] NetworkManager crashes when configuring zd1211 wireless device
Public bug reported: Binary package hint: network-manager Distribution: Ubuntu 7.04 Feisty Fawn - Herd 3 Hardware: Zonet ZEW2501 Chipset: zd1211b Driver: zd1211rw Description: Upon attempting to configure this wireless device with NetworkManager, the window disappears and NetworkManager returns to the system tray. I am unable to configure this device because the window goes away in what appears to be a crash although it is still active in the tray and can be reopened. 'ifconfig' and 'iwconfig' both show the device and report not conflicts. The system logs appear normal and I didn't find any unusual behavior. Attempted Solutions: Believing it was a hardware conflict I have tried booting Ubuntu with the following additional parameters... noapic nolapic noapic nolapic pci=noacpi - disables IRQ11 used by the device and causes it to not appear noapic nolapic pci=noacpi irqpoll acpi=off - disables the device when used with any of the above parameters Steps to Reproduce: 1.) Boot with Zonet ZEW2501 (zd1211b) in Feisty Fawn Herd 3 2.) Click the NetworkManager icon in the top right 3.) Select the wireless device from the list 4.) Click 'Properties' 5.) The properties dialog may appear briefly for a few seconds before all NetworkManager windows disappear. Both the properties and the nm window vanish, but NetworkManager is still running in the system tray on the top right. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Unconfirmed -- NetworkManager crashes when configuring zd1211 wireless device https://launchpad.net/bugs/86351 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38263] Re: freeze at startup
I too have a motherboard with the ATI xpress 200 chipset. I attempted lasercat's settings and tried acpi=off irqpoll with no success on Edgy Eft which uses the 2.6.17 kernel. As of 2.6.16, there are some fixes with IRQ issues being resolved but the problem as a whole still exists with ACPI. Ubuntu Edgy Eft Knot 1: acpi=off irqpoll MP-BIOS bug: 8254 timer not connected to IO-APIC PCI Cannot allocate resource region 3 of device -- freeze at startup https://launchpad.net/bugs/38263 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
