[Bug 529363] Re: HPT370 infinite reboot loop as GRUB loads
Here is an lspci dump when the boot CD has started up. It shows that the highpoint controller has been detected. ** Attachment added: "lspci_output_cdrom_boot" http://launchpadlibrarian.net/43099566/lspci_output_cdrom_boot -- HPT370 infinite reboot loop as GRUB loads https://bugs.launchpad.net/bugs/529363 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 529363] Re: HPT370 infinite reboot loop as GRUB loads
Here is the generated grub.cfg after installation. ** Attachment added: "grub.cfg" http://launchpadlibrarian.net/43099243/grub.cfg -- HPT370 infinite reboot loop as GRUB loads https://bugs.launchpad.net/bugs/529363 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 529363] Re: HPT370 infinite reboot loop as GRUB loads
Hi I can reproduce this bug again with the following setup. Ubuntu Karmic 09-10 stock 32 bit installation disk. Mainboard: Abit KR7A - Raid CPU AMD Athlon 1900+ Highpoint HPT 370/372 external ATA controller. Via VT8366A southbridge Hard disk setup Primary master: DVD rom drive. Secondary Master: DVD Rewriter. External highpoint HPT 370 controller: hard disk. Start situation: PC did boot to windows XP normally before Kubuntu Installation. Installation of Kubuntu Karmic 09-10 went normally. After reboot PC gets in infinite reboot loop as described in parent post. No grub errors visible on console. -- HPT370 infinite reboot loop as GRUB loads https://bugs.launchpad.net/bugs/529363 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 279983] Re: kblueplugd crashed with DBusException in call_blocking()
Problem happened with an on-line upgrade from 08.04 to 08.10 as well. Laptop specs. Intel core 2 duo processor 2gb ram intel GMA950. Fujitsu Siemens Amilo series. -- kblueplugd crashed with DBusException in call_blocking() https://bugs.launchpad.net/bugs/279983 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 88431] Re: 'Monitor & Display' module in System Settings is not working.
During the a fresh install of the Hardy heron alpha 3 this bug surfaces again on my system. CPU AMD athlon 64 3200 + ATI X800 pro. 2 GB RAM. Error message supplied by "display properties" in Kubuntu. The module monitor and display could not be loaded. The diagnostics is: Library files for libpython2.5.so not found in paths Possible reasons: - An error occurred during your last KDE upgrade leaving an orphaned control module. - You have old third party modules lying around. Output of kcmshell diaplayconfig [EMAIL PROTECTED]:~$ kcmshell displayconfig Pythonize constructor -- pid = 7492 Python interpreter initialized! Pythonize constructor -- pid = 7492 Traceback (most recent call last): File "/var/lib/python-support/python2.5/displayconfig.py", line 19, in from qt import * ImportError: /usr/lib/python2.5/site-packages/qt.so: undefined symbol: PyUnicode_Type Error in sys.excepthook: Traceback (most recent call last): File "/var/lib/python-support/python2.5/apport_python_hook.py", line 36, in apport_excepthook from cStringIO import StringIO ImportError: /usr/lib/python2.5/lib-dynload/cStringIO.so: undefined symbol: _Py_ZeroStruct Original exception was: Traceback (most recent call last): File "/var/lib/python-support/python2.5/displayconfig.py", line 19, in from qt import * ImportError: /usr/lib/python2.5/site-packages/qt.so: undefined symbol: PyUnicode_Type error: ***failed to import module kdecore (KProcess): WARNING: _attachPty() 12 X Error: BadValue (integer parameter out of range for operation) 2 Major opcode: 113 Minor opcode: 0 Resource id: 0x3c7 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 10 Minor opcode: 0 Resource id: 0x3c7 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 Minor opcode: 0 Resource id: 0x3c7 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 6 Minor opcode: 0 Resource id: 0x3c7 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 25 Minor opcode: 0 Resource id: 0x3c7 -- 'Monitor & Display' module in System Settings is not working. https://bugs.launchpad.net/bugs/88431 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kde-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 150717] Gutsy install hangs during download of Dutch localisation files.
Public bug reported: During the installation of the Gutsy Beta , the following error was observerved. Installation hangs at the moment where dutch localization files (NL) are downloaded. The user is not informed about anything, so the progress bars, just hangs at 87%. The error occurs when dutch (NL) is chosen as the language of the installed ubuntu system. When the installation is aborted, the system does not boot, since GRUB is not installed and the windows bootsector still is active. Installation of the Gutsy beta by selecting English as a language succeeds, and the GRUB bootloader loads with the option to select Ubuntu and Windows XP. ** Affects: ubuntu Importance: Undecided Status: New -- Gutsy install hangs during download of Dutch localisation files. https://bugs.launchpad.net/bugs/150717 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 150717] Re: Gutsy install hangs during download of Dutch localisation files.
** Attachment added: "Screenshot.png" http://launchpadlibrarian.net/9888431/Screenshot.png -- Gutsy install hangs during download of Dutch localisation files. https://bugs.launchpad.net/bugs/150717 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 67487] Re: [regression][rv280] black screen and console freeze when X starts - drm lockup
I have a similar bug on my ubuntu test box with the following specs. Specificiations Ubuntu Feisty 7.04 RevisMion history / Initial install Dapper Drake, Upgraded From Dapper To Edgy and from Edgy to Feisty. CPU AMD athlon 64 3200 + Video card Ati Radeon X800 pro. Installed FGLRX driver. Monitor Samsung 940BF tft screen connected via a DVI cable. Installed dapper without problems, and was able to perform the upgrades during one year. During my Linux use i tried to tame X but I encountered some problems. 1. When my monitor is auto detected as "Plug and play" in the options, the black screen of death appears and only single user mode enables me to restore xorg.conf 2. Manually defining my monitor as a 1280X1024 monitor with a 74 hz refresh rate solves my problem. 3 Defining my monitor as a generic TFT screen with a resolution of 1280X1024 leads to image corruption and a non-working mouse. But the tricky part was, that I wanted to reinstall feisty from CD, to start anew to solve some other problems, the black screen appears again when booting from the installer CD. And of course X dies a horrible death. But at least I encounter a similar prolem with a functional X system, so here are some xorg.0.log entries from a "black screen situation". First Xorg.0.log from my working system (note, it already contains errors). Xorg.0.log from working system [EMAIL PROTECTED]:/var/log$ cat Xorg.0.log.old | grep EE (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (II) Loading extension MIT-SCREEN-SAVER (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): === [swlDalHelperAddCustomizeMode] === CWDDEDI_DisplayGetSetModeTimingOverride failed: 7 (EE) fglrx(0): GART is not initialized, disabling DRI (EE) AIGLX: Screen 0 is not DRI capable (EE) xf86OpenSerial: Cannot open device /dev/wacom (EE) xf86OpenSerial: Cannot open device /dev/wacom (EE) xf86OpenSerial: Cannot open device /dev/wacom (EE) AIGLX: Screen 0 is not DRI capable (EE) xf86OpenSerial: Cannot open device /dev/wacom (EE) xf86OpenSerial: Cannot open device /dev/wacom (EE) xf86OpenSerial: Cannot open device /dev/wacom [EMAIL PROTECTED]:/var/log$ Xorg.0.log from " Black screen of death" situation (II) Loading extension MIT-SCREEN-SAVER (EE) fglrx(0): GART is not initialized, disabling DRI (EE) AIGLX: Screen 0 is not DRI capable (EE) xf86OpenSerial: Cannot open device /dev/wacom (EE) xf86OpenSerial: Cannot open device /dev/wacom (EE) xf86OpenSerial: Cannot open device /dev/wacom (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) The directory "/usr/share/X11/fonts/cyrillic" does not exist. (WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found (WW) fglrx(0): GetVBEMode failed (WW) fglrx(0): Failed to open DRM connection (WW) fglrx(0): No DRM connection for driver fglrx. (WW) fglrx(0): *** (WW) fglrx(0): * DRI initialization failed! * (WW) fglrx(0): * (maybe driver kernel module missing or bad) * (WW) fglrx(0): * 2D acceleraton available (MMIO) * (WW) fglrx(0): * no 3D acceleration available* (WW) fglrx(0): * * I tried a fresh install and the Feisty installer locks up with the reported black screen of death. I assume this bug may be caused by the default selection of plug and play for a monitor. -- [regression][rv280] black screen and console freeze when X starts - drm lockup https://bugs.launchpad.net/bugs/67487 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.co
Re: [Bug 61247] Re: Instalation CD kubuntu edgy knot-3 problem
Hi Jonathan I looked at the listed bug report 61247, but I did not send it. Guess it was another person intended for this mail. Niels Jonathan Jesse schreef: > Good afternoon, > > I noticed this bug is reported against Edgy Knot-3 and I am wondering if you > were able to install Edgy in the final release version correctly? > Can you please update this bug to reflect its current status? > Thanks, > > Jonathan > > ** Changed in: Ubuntu > Assignee: (unassigned) => Jonathan Jesse >Status: Unconfirmed => Needs Info > > -- Instalation CD kubuntu edgy knot-3 problem https://launchpad.net/bugs/61247 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63209] Re: [Edgy Regression] Dhclient error on Realtek 8169/8110: send_packet: Message too long
Hi Thanks for the workaround, this was a nasty one since I did not have a clue that it was a bothed DHCP config. It works and I am now upgrading my box to stay current. -- [Edgy Regression] Dhclient error on Realtek 8169/8110: send_packet: Message too long https://launchpad.net/bugs/63209 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63209] Re: Install edgy eft breaks compatibility Realtek 8169/8110 NIC
Here is some output from ifconfig and and the dhcp deamon. It looks like kubuntu can not contact my router to obtain a dhcp lease. Note when I boot my PC in windows it works without problems. [EMAIL PROTECTED]:~$ ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0C:76:E7:80:41 UP BROADCAST RUNNING MULTICAST MTU:64 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2480 (2.4 KiB) TX bytes:1368 (1.3 KiB) Interrupt:201 Base address:0x2f00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) [EMAIL PROTECTED]:~$ sudo dhclient eth0 Password: Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:0c:76:e7:80:41 Sending on LPF/eth0/00:0c:76:e7:80:41 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 send_packet: Message too long DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 send_packet: Message too long -- Install edgy eft breaks compatibility Realtek 8169/8110 NIC https://launchpad.net/bugs/63209 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63209] Re: Install edgy eft breaks compatibility Realtek 8169/8110 NIC
Here is some update. Eth0 (my network card) is still having problems. When is is configured with a static ip, the card shows up in the KDE system information and I can ping my router and my ISP dns server. When I configure eth0 with a dynamic ip using the control panel, eth0 could not obtain a DHCP lease, this did not happen with dapper. -- Install edgy eft breaks compatibility Realtek 8169/8110 NIC https://launchpad.net/bugs/63209 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63209] Install edgy eft breaks compatibility Realtek 8169/8110 NIC
Public bug reported: When I installed the edgy eft distribution from the CD with the default kerne, my network card was not recognized anymore. I did work out of the box with the dapper drake distribution, which installed successfully on my box. I could configyure the NIC and I could have had access to the internet. I have an onboard Realtek 8169/8110 gigabit ethernet card. After installation I cannot connect to the internet and my NIC could not be configured by using the control panel. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Install edgy eft breaks compatibility Realtek 8169/8110 NIC https://launchpad.net/bugs/63209 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63053] Re: Upgrade from dapper drake to edgy beta breaks X
*** This bug is a duplicate of bug 61247 *** I got X up and running, it seemed that the xorg.conf reverted back to the "ati" driver instead of the "fglrx" driver. I commentented out the "dri" line. This is what I think is the root cause for the X issue. I advise to check for fglrx dependency during the upgrade process or more users will have a nasty suprise when they upgrade. -- Upgrade from dapper drake to edgy beta breaks X https://launchpad.net/bugs/63053 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63053] Re: Upgrade from dapper drake to edgy beta breaks X
*** This bug is a duplicate of bug 61247 *** Hi I tried reconfiguring X by using the command sudo dpkg-reconfigure xserver-xorg But still the same probs an no X. Here is a new logfile. Maybe this information will help, since I know X does not like dual head video cards. Video card X800 pro TFT screen 19 inch max resolution 75 hz. Screen is connected via DVI connection. ** Attachment added: "Xorg.0.log" http://librarian.launchpad.net/4554143/H%3A%5CLogs%5CXorg.0.log -- Upgrade from dapper drake to edgy beta breaks X https://launchpad.net/bugs/63053 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63053] Re: Upgrade from dapper drake to edgy beta breaks X
*** This bug is a duplicate of bug 61247 *** Her is the Xorg.0.log output It is a large one so I have attached it as a file. It looks like the x init process fails. ** Attachment added: "Xorg.0.log file" http://librarian.launchpad.net/4554011/Xorg.0.log -- Upgrade from dapper drake to edgy beta breaks X https://launchpad.net/bugs/63053 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63053] Upgrade from dapper drake to edgy beta breaks X
*** This bug is a duplicate of bug 61247 *** Public bug reported: When I upgraded from Kubuntu Dapper drake to te Edgy Eft beta by using the dist upgrade commands, X does not work after the reboot. The screen stays blank and after a while the text based login screen opens. Both the 2.6.17.x series kernel and the 2.6.15.27 kernel from dapper did not work as well. Hardware configuration. Ati Radeon X800 pro video card. ATI fglrx driver. Only text based login is possible. ** Affects: kubuntu-default-settings (Ubuntu) Importance: Undecided Status: Unconfirmed -- Upgrade from dapper drake to edgy beta breaks X https://launchpad.net/bugs/63053 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
