[Bug 252033] Re: [NV25] Can't get over 800x600 resolution
mattismyname has indicated this is no longer an issue for him because he installed the beta drivers. I indicated that these are available in the repository. Looks like this issue was related to the 96 series nVidia drivers broken by the Intrepid changes to Xorg. ** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Status: Confirmed => Fix Released -- [NV25] Can't get over 800x600 resolution https://bugs.launchpad.net/bugs/252033 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 325263] [NEW] KQ package very out of date.
Public bug reported: Binary package hint: kq kq (and kq-data) packages are severely out of date. Official web page: http://kqlives.sourceforge.net/ Download page: http://sourceforge.net/project/showfiles.php?group_id=61344&package_id=130221 Download page shows that the last stable update is from Feb 2, 2008. Yet, the last update in the repositories is from March of 2007. Please package the latest version of this game. ** Affects: kq (Ubuntu) Importance: Undecided Status: New -- KQ package very out of date. https://bugs.launchpad.net/bugs/325263 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 317455] Re: package nvidia-glx-96 None failed to install/upgrade: subprocess pre-installation script returned error exit status 2
I changed the status to Invalid as this is an issue with compatability between the script made by nVidia and Ubuntu, rather than an issue with the Ubuntu-supported packages. ** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Status: Confirmed => Invalid -- package nvidia-glx-96 None failed to install/upgrade: subprocess pre-installation script returned error exit status 2 https://bugs.launchpad.net/bugs/317455 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 317455] Re: package nvidia-glx-96 None failed to install/upgrade: subprocess pre-installation script returned error exit status 2
This is not a problem with the nvidia graphics drivers packages in Ubuntu. I see that you downloaded the script from nVidia, instead of installing the package from intrepid-updates. First, check your software sources. You can do this in Gnome from ... System --> Administration --> Software Sources or in Synaptic from Settings --> Repositories Go to the updates tab and check that Recommended Updates (intrepid- updates) is checked. Make sure that you somehow reload the package list. (The "Reload" button in Synaptic will do this) You'll want to remove the effects of the nVidia script (honestly, been awhile since I used the nVidia script, but I believe they send removal instructions with the script). Unfortunately, I remember seeing indications in the forums that the nVidia script can mess things up, but I'm not certain what all you need to do to strip it back off. Perhaps others can contribute here? Once the nVidia version is gone (use the nv or vesa driver in the meantime), go to your favorite package manager and make sure either jockey-gtk (for gnome, xubuntu, etc) or jockey-kde (for kubuntu) is installed. Also, make sure dkms is installed. Exit your package manager and go to... System --> Administration --> Hardware Drivers Choose the appropriate driver for your system and select activate. Once everything gets finished, go back into your package manager and make sure you have the latest version of nvidia-glx-96 (or whichever version you installed in Hardware Drivers). Then you should be ready for restart. -- package nvidia-glx-96 None failed to install/upgrade: subprocess pre-installation script returned error exit status 2 https://bugs.launchpad.net/bugs/317455 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 214413] Re: after upgrading from 7.10 to 8.04 cdrom won't mount
Guess I'm finally getting around to joining this discussion. If anyone has this now working on their system, could you please share what you have in /etc/fstab in relation to your cd-rom(s)? I am getting error like this in both Intrepid and Jaunty. (This taken from the Intrepid dmesg log) [ 21.267641] sr0: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00 [ 21.268843] sr: Sense Key : Hardware Error [current] [ 21.268850] sr: Add. Sense: Logical unit communication CRC error (Ultra-DMA/32) [ 21.373663] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input7 [ 23.205086] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [ 23.205103] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current] [ 23.205114] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32) [ 23.205128] end_request: I/O error, dev sr0, sector 40 [ 23.205650] Buffer I/O error on device sr0, logical block 5 [ 23.206172] Buffer I/O error on device sr0, logical block 6 [ 23.206690] Buffer I/O error on device sr0, logical block 7 [ 23.207208] Buffer I/O error on device sr0, logical block 8 [ 23.207726] Buffer I/O error on device sr0, logical block 9 [ 23.208298] Buffer I/O error on device sr0, logical block 10 [ 23.208825] Buffer I/O error on device sr0, logical block 11 [ 23.588700] gameport: CS46xx Gameport is pci:00:09.0/gameport0, speed 1704kHz [ 23.718183] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [ 23.718200] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current] [ 23.718211] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32) [ 23.718225] end_request: I/O error, dev sr0, sector 96 [ 23.718752] Buffer I/O error on device sr0, logical block 12 [ 23.721423] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [ 23.721441] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current] [ 23.721451] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32) [ 23.721464] end_request: I/O error, dev sr0, sector 104 [ 23.721993] Buffer I/O error on device sr0, logical block 13 [ 23.722525] Buffer I/O error on device sr0, logical block 14 Here's the cdrom lines from my fstab: /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/scd1 /media/cdrom1 udf,iso9660 user,noauto 0 0 Any suggestions are appreciated. -- after upgrading from 7.10 to 8.04 cdrom won't mount https://bugs.launchpad.net/bugs/214413 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 316617] Re: GDM Language Selection not listed properly
Filed. http://bugzilla.gnome.org/show_bug.cgi?id=567703 -- GDM Language Selection not listed properly https://bugs.launchpad.net/bugs/316617 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 316617] [NEW] GDM Language Selection not listed properly
Public bug reported: Binary package hint: gdm Using Intrepid Ibex, but I would guess this bug is common to all flavors of Ubuntu. gdm (2.20.8-0ubuntu3) does not properly localize its language selections. Established world example: Next time you use an ATM or point-of-sale credit card reader that allows for multiple languages, take a look at how the language options are listed. Here in the USA, we often see support for both English and Spanish. But we don't see the options as English and Spanish, or as Ingles and Espanol. We see them as English and Espanol (apologies if I'm leaving out critical pronunciation marks). My point is, if you want your user to understand you, you need to print in the language that they understand. If you want your interface to be accessible to Spanish speaking users, you list Espanol, not Spanish as the language. For those of us who speak English, its not Ingles to us. So, this needs to apply in our login screens also. I'm currently setting up a PC capable of working in either Spanish or English. But the bug is, if GDM is currently in English mode, then the language selector shows Spanish and English options, but if its currently in Spanish mode, it shows English, Ingles, Spanish, and Espanol options (not sure why it can't decide how to spell the languages). In reality, each language should be listed in the native tongue of whoever would speak the language. So, regardless of what language mode GDM is currently in, all Spanish language options should be listed as Espanol, with the appropriate name of the country as its known to the natives of that country. Similarly, English should always be listed as English, with the country names being the names as they would be known to the locals. Once I make my language selection, a message screen pops up asking whether I want to make this the default, or just use the language for this one session. Again, this is a throw-back to the language mode that GDM is currently in. If GDM is in Spanish mode, and I just chose an English language option, the verification message still shows in Spanish. That should not be. I've just indicated the strong possibility that I don't understand the current language mode. So, once I've chosen a new language, the verification text needs to come up in the language that I've just chosen, making sure that the cancel button also includes the established Linux symbol for cancel -- so I know which one to pick if I can't read the message that popped up. This is how the world already works, this is how Linux needs to "just work" in order to be multi-lingual. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- GDM Language Selection not listed properly https://bugs.launchpad.net/bugs/316617 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 252033] Re: [NV25] Can't get over 800x600 resolution
Eh. Don't go through all that work. Fire up Synaptic, bring up the repositories (sorry, I'm not at my Linux PC, so I'm not sure all the right menu names), and make sure that the "Proposed" repository is turned on. Reload your repositories, and bring on the latest nvidia updates. I believe that 96.43.09 was the first version that worked, so make sure that the drivers you install show that update or later. Make sure you also install the latest jockey from proposed, since jockey in the main repositories has these drivers blacklisted. One caveat. Some have noted (and I have confirmed) that certain programs run under Wine have messed up fonts. I have not noticed any issues with native Linux stuff yet. -- [NV25] Can't get over 800x600 resolution https://bugs.launchpad.net/bugs/252033 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 64615] Re: apt-get broken after upgrade to edgy eft (courier-authdaemon package)
As noted, this bug is specific to upgrading from Dapper to Edgy. As Edgy has reached end of life, I am closing this bug. ** Changed in: courier-authlib (Ubuntu) Status: New => Fix Released -- apt-get broken after upgrade to edgy eft (courier-authdaemon package) https://bugs.launchpad.net/bugs/64615 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 273929] Re: gnome-desktop-environment (intrepid) not installable
I agree. This one is fixed. Is there anything more I need to do to close this bug? -- gnome-desktop-environment (intrepid) not installable https://bugs.launchpad.net/bugs/273929 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 268495] Re: [Intrepid] gnome-office cannot be installed
(Note: I have "fixed" my own installation by pulling several abiword related packages from Debian. So, the abiword piece *is* fixed in Debian. Now, we just need that pulled back to Intrepid.) ** Changed in: meta-gnome2 (Ubuntu) Status: Fix Released => In Progress -- [Intrepid] gnome-office cannot be installed https://bugs.launchpad.net/bugs/268495 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 268495] Re: [Intrepid] gnome-office cannot be installed
Fixed? I don't agree. The need for abiword-gnome was taken out and replaced with a need for abiword-plugin-goffice. But since abiword-plugin-goffice is *not* available in intrepid either, this hasn't fixed anything. So, the breakage has been changed, but not fixed yet. -- [Intrepid] gnome-office cannot be installed https://bugs.launchpad.net/bugs/268495 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 273929] [NEW] gnome-desktop-environment (intrepid) not installable
Public bug reported: Binary package hint: gnome-desktop-environment Latest update of gnome-desktop-environment (2.22.2-4ubuntu1) was posted without all of its requirements. It depends on gnome-user-guide 2.22.1, but that version of the guide is not available in the repositories. The latest version of the gnome-user-guide is 2.22.0+svn20080407ubuntu1. ** Affects: meta-gnome2 (Ubuntu) Importance: Undecided Status: New -- gnome-desktop-environment (intrepid) not installable https://bugs.launchpad.net/bugs/273929 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 220030] Re: Kubuntu Alternate Install CD - Stop making coasters!
** Changed in: ubuntu Status: New => Invalid -- Kubuntu Alternate Install CD - Stop making coasters! https://bugs.launchpad.net/bugs/220030 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 268495] [NEW] [Intrepid] gnome-office cannot be installed
Public bug reported: Intrepid Ibex issue. Meta-package gnome-office depends on abiword-gnome which does not exist. Either abiword-gnome needs to be created, or this dependency needs to change to just abiword. ** Affects: meta-gnome2 (Ubuntu) Importance: Undecided Status: New -- [Intrepid] gnome-office cannot be installed https://bugs.launchpad.net/bugs/268495 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 220030] Re: Kubuntu Alternate Install CD - Stop making coasters!
Couple things here. 1) Come to think of it, I'm not certain that I have successfully burned any ISO's from Gutsy. I have done it with other versions of Ubuntu (including Hardy -- yes I had Hardy installed once, but had to abandon it when certain upgrades crashed the system). which makes me start to suspect things like k3b in Gutsy. 2) This is not a problem with just the Kubuntu CD's. I tried the Xubuntu CD with similar results. Which again makes me suspect that it *may* be a software problem. When I get another chance -- I'll see if I can find any Windows-based burning tools on my other system that might be able to create these disks. At least its worth a shot. -- Kubuntu Alternate Install CD - Stop making coasters! https://bugs.launchpad.net/bugs/220030 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 220030] Re: Kubuntu Alternate Install CD - Stop making coasters!
Actually -- What I see here (http://iso.qa.ubuntu.com/qatracker/build/kubuntu/all) is flawed testing situations. Under "download info Kubuntu Alternate i386 (20080417.1)" >From Install (Auto-Resize): Summary Install from the Alternate CD using one of 3 partitioning methods, OEM, expert or rescue mode. Procedure 1. Boot using the desktop CD In fact, for all but one of the test cases for the i386 Alternate install, it either does not specify which disk to use, or specifically indicates the *Desktop* CD, instead of the Alternate CD. Same thing for the KDE4 version. So, assuming the testers did not follow the written instructions, but actually followed what the instructions *should* read... There are a total of three people that have responded back that they tried the alternate install CD. Did any of them actually have system requirements low enough that they needed the alternate CD? Or an older computer? Nothing is indicated as far as that goes. I haven't had problems in the past burning disks from this computer. And I have trouble convincing myself enough to say Memorex screwed up their disks... -- Kubuntu Alternate Install CD - Stop making coasters! https://bugs.launchpad.net/bugs/220030 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 220030] [NEW] Kubuntu Alternate Install CD - Stop making coasters!
Public bug reported: I download the Kubuntu Alternate release candidate CD for i386 -- kubuntu-8.04-rc-alternate-i386.iso.In gutsy, I burn this (through k3b) to a new CD-R medium, first verifying the MD5 sum (its fine). I then reboot my computer (Authentic AMD Athlon Processor CPU family 6, model 4, 1.2 Mhz. Total physical memory - 256Mb) and ask to "Check CD for defects". It passes some of the verification levels, before finally crashing with this message: The ./insall/netboot/ubuntu-installer/i386/initrd.gz file failed the MD5 checksum verification. Your CD-ROM or this file may have been corrupted. Note: I apologize for waiting so long to report this. I had noted it on the Kubuntu install feedback wiki previously, but had not filed an official bug. I've made a few CD-ROM coasters because of this continuing error. Please validate the CD's before posting them on the web. The Alternate CD's are not passing their own internal validation. Cheers! ** Affects: ubuntu Importance: Undecided Status: New -- Kubuntu Alternate Install CD - Stop making coasters! https://bugs.launchpad.net/bugs/220030 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 126337] Re: IDE drivers not loaded at boot with powerpc
Going back to the original poster's messages, I see that something in his computer is referencing /dev/hda3. Partially with Gutsy, and more completely with Hardy, we have migrated over to a different way of referencing drives. The most reliable way to reference all drives in Hardy, Gutsy, or even Feisty, is to use UUID's. Although it appears that Michael's /etc/fstab correctly uses UUID's, I would hazard a guess that his /boot/grub/menu.lst still uses the /dev paths to reference drives. Please see the following material: https://help.ubuntu.com/community/UsingUUID Cheers! -- IDE drivers not loaded at boot with powerpc https://bugs.launchpad.net/bugs/126337 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 152820] Re: Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
For those who have *some* method of booting into their system... It should be noted that there were a number of issues related to booting as a result of what was done in Gutsy. See bug 133666 for one prominent example. This documents an issue that had a known fix that will not be put into Gutsy simply because this show-stopping bug was found only after the release of Gutsy when people actually started using the distribution. This is actually an upstream thing -- the Linux kernel had the bug in 2.6.22, but it had been fixed in 2.6.23 and beyond. As I understand the situation, Linux is trying to alter how drives are accessed. For many of us, that means that instead of /dev/hd*, we now have /dev/sd*. UUID's do not change between the two access methods, but there were some kernel bugs that were not identified until after Gutsy. There is no intention to pull these bugs out of Gutsy. Instead, they are asking that people test out the Hardy kernels to make sure that these issues are truly fixed in Hardy. I'm of the understanding that this is done by temporarily altering the /etc/apt/sources.list in order to include the Hardy main and restricted repositories. Once you have retrieved the Hardy kernels, and installed them on your system, you can change /etc/apt/sources.list back to just Gutsy repositories. Unless you actually want to test Hardy, it is advised that you do not do any upgrades while you are using the altered sources.list. At this point, the primary concern is if these issues are not fixed in the Hardy kernels. If there are still issues in the 2.6.24 kernels, please document the bugs appropriately. -- Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable https://bugs.launchpad.net/bugs/152820 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 96207] Re: Feisty package pciutils depends on "obsolete" package
Reviewed in Hardy. I have pciutils installed, and I was able to remove libpci2. This is no longer an issue as of the hardy release. ** Changed in: pciutils (Ubuntu) Status: Confirmed => Fix Released -- Feisty package pciutils depends on "obsolete" package https://bugs.launchpad.net/bugs/96207 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 152820] Re: Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
It appears that the *intent* with Gutsy was to switch the drives over to /dev/sd* completely. That did not happen for SiS 5513 IDE controllers. According to my personal experience, these changes allowed me to use the stock Ubuntu kernels: Feisty: No changes from previous installs. Feisty kernels were working fine with SiS 5513. Gutsy: Some report fresh install with Gutsy works fine. An upgrade is another matter. Change the /etc/fstab file for the / (root) partition only to /dev/sd* instead of /dev/hd*. Hardy: Change the /etc/fstab file for all partitions to use /dev/sd* instead of /dev/hd*. Also, if you specify the boot directory by /dev (instead of UUID) in /boot/grub/menu.lst, change to /dev/sd* there also. These kind of changes need to be noted in the distribution notes for upgrading. Cheers! -- Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable https://bugs.launchpad.net/bugs/152820 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 164722] Re: kernel 2.6.22 crash on toshiba m30x-127
See Bug 152820. Another SiS 5513 user there tried both upgrading and a fresh install. For him, the upgrade caused boot issues, but the install worked fine. I have made a few tweaks to my /etc/fstab file and am now using the stock Gutsy kernels. My changes are noted in the other bug. the original contributer here indicates that his issue includes problems even from the live CD. So, I don't think this is the same issue. Cheers! -- kernel 2.6.22 crash on toshiba m30x-127 https://bugs.launchpad.net/bugs/164722 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 155702] Re: pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available!
Just a note of clarification. My particular problem was related to an upgrade from Feisty to Gutsy. See Bug 152820. I had to make some tweaks to /etc/fstab as indicated in the other bug. Cheers! -- pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available! https://bugs.launchpad.net/bugs/155702 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
*** This bug is a duplicate of bug 133666 *** https://bugs.launchpad.net/bugs/133666 Please note: this is related to upgrade. Please also see bug 152820. There are issues with the upgrade that do not exist with a fresh install. I had to make additional updates to /etc/fstab. These updates should have been identified in the upgrade notes, but they were not. So, after the changes I indicated in 152820, I am now working -- with the stock Gutsy kernels. Cheers! -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 133666] Re: please patch linux-source-2.6.22 to fix ata_piix bug
Clarification: after reviewing bug 152820, I found that my issue was directly related to upgrading from Feisty to Gutsy, and some missing related upgrade notes. Feel free to review that bug to see how I fixed my problem. (Had to change the root partition specification in /etc/fstab) That being said, I fear that we may have deviated from the original intent of this bug. This bug originally indicated a patch that is supposed to be fixed in 2.6.23 and beyond. Since my Gutsy system is now working with the stock kernel (after some /etc/fstab tweaks), I can't speak to whether the original issue is still a problem. That being said -- I'm working, so I'm now content. Cheers! -- please patch linux-source-2.6.22 to fix ata_piix bug https://bugs.launchpad.net/bugs/133666 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 131945] Re: Bad recognition of DD by ata_piix
Note: I found that my issue was related to an upgrade as opposed to a fresh install. Please disregard my comments. For those experiencing upgrade issues, please see bug 152820 for further details of the problem. -- Bad recognition of DD by ata_piix https://bugs.launchpad.net/bugs/131945 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 152820] Re: Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
Here's a quick rundown of my Gutsy kernel issue. Feisty was working fine with my computer. An upgrade to Gutsy worked -- with the exception of needing to either use the Feisty kernel, or compile my own with the SiS 5513 module compiled (it was removed by the Ubuntu folks). Then I finally read through this bug. There is critical information hidden away here that really needs to be documented better. I tried to switch everything in /etc/fstab from '/dev/hd*' to /dev/sd*'. That got me further, but failed to completely work. I was finally able to get to a console prompt, though. I determined that it was now finding my root directory, but directories that were on other partitions were no longer found. End result: /etc/fstab needs to have the '/' (root) directory set as /dev/sd*, but all other partitions need to be set as /dev/hd*. Kinda weird, but it works. I am finally using the stock Gutsy Ubuntu kernels -- and they work! (no -- my system did not have any of the evms packages installed) Could someone from the kernel team please review what all needed to change in setup for those of us that use IDE drives? I'm guessing that a number of issues could be resolved just by properly documenting the necessary changes when upgrading from Feisty to Gutsy. /etc/fstab clearly needs to change for those that use IDE drives. What else needs to change? These change notes need to be added to the upgrade notes (http://www.ubuntu.com/getubuntu/upgrading). As requested, I am including my kern.log. The latest boot messages would be from the 2.6.22-14 kernel. ** Attachment added: "kern.log.txt" http://launchpadlibrarian.net/10985196/kern.log.txt -- Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable https://bugs.launchpad.net/bugs/152820 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 152820] Re: Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
I would disagree that this issue is *fixed*. Bolek indicated that an *upgrade* from Feisty to Gutsy on a certain architecture (including a SiS 5513 IDE driver) will cause the computer to be unbootable, while a fresh install on the same computer will have it working like a charm. There is some discussion as to possibly some changes needed in /etc/fstab in order to get everything working again. Perhaps this is all it takes, in my experience of trying this fix, it did not work. At this point, it sounds like this could very well be an issue that could be fixed with proper documentation. Things are different between Feisty and Gutsy, and evidently a straight update as documented in the release notes is not working. It should be documented in the release notes how to switch a Feisty system over to a Gutsy system. I'm at the point of having a broken system after a straight update. And just changing /etc/fstab did not do the trick for me. What else might I need to change? -- Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable https://bugs.launchpad.net/bugs/152820 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
Sorry -- I neglected to change the 'Baltix' default. ** Changed in: linux-source-2.6.24 (Baltix) Status: New => Invalid -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
Major regression issue still in Gutsy for all SiS 5513 controllers, and some Intel 82801 controllers. For Gutsy, we are still requesting that the old patch be put back into the kernel -- that is: restore the availability of the sis5513 module. If there is something we are attempting to fix by removing the sis5513 module -- we failed. And the current 2.6.24 kernels in Hardy do not fix the issue either. Please review what the sis5513 module is doing because I have recompiled the 2.6.24 kerne for my Hardy kernell -- and the module works fine for those of us with SiS 5513 controllers. But removing the module makes such a system unbootable. Cheers! ** Also affects: linux-source-2.6.24 (Ubuntu) Importance: Undecided Status: New -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
** Also affects: linux-source-2.6.24 (Baltix) Importance: Undecided Status: New -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 133666] Re: please patch linux-source-2.6.22 to fix ata_piix bug
Tested recompile of 2.6.24. The SiS 5513 module as originally supplied by the kernel.org folks is still working. The 2.6.22 and 24 kernels with this module removed in Gutsy and Hardy are not working. If there's some reason that we do not want this module -- then we still have not fixed the kernel to correctly support this hardware and we need to review our fix in Hardy. With Gutsy being a stable system, I would not suggest any new kernel patches. But, because this has caused major regression for anyone with a SiS 5513-related controller (including certain Intel 82801 controllers), I would request that we restore the old fix so that Gutsy can actually be a working system. So, where Hardy may need to have new code to replace the module, Gutsy should just have the existing module compiled and made available to the kernel. Cheers! -- please patch linux-source-2.6.22 to fix ata_piix bug https://bugs.launchpad.net/bugs/133666 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 123789] Re: Kernel 2.6.22-x will not boot on laptop
Sorry to have further muddied the waters. Note: DaveW, the contributor who originally posted this issue, has not responded back with his computer specifications. But the next three contributors (Johan, Necromancer, and Fabio Marzocca) all showed that they use this IDE controller: nVidia Corporation MCP51 IDE. (Search their lspci reports for 'IDE' and you'll see what I mean) I would suggest using this issue to deal with problems specifically related to this IDE controller. I again apologize for adding to the confusion with my previous post. -- Kernel 2.6.22-x will not boot on laptop https://bugs.launchpad.net/bugs/123789 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 133666] Re: please patch linux-source-2.6.22 to fix ata_piix bug
I have an Athlon Classic 1200 with a SiS 5513 IDE driver. The 2.6.22 kernels in Gutsy and Hardy, and the 2.6.24 kernel in Hardy all show this problem by not recognizing my hard drive partitions on bootup -- causing a complete lock up early in the boot process. I have proven this is fixable in the 2.6.22 and 2.6.23 kernels by simply building the sis5513 module when recompiling the kernel. Perhaps there is some other more generally applicable code fix, but so far, none of the final release kernels for Gutsy have any such fix, and neither do the early versions of the Hardy kernels. I have been able to do a partial fix by adding 'ide-generic' and 'ide- disk' to /etc/initramfs-tools/modules and running update-initramfs. This has "worked" in both Gutsy and Hardy kernels -- but it has its problems. Most importantly, ide-generic completely cancels dma on all drives. So, while this will allow me to use xorg and KDE, it is not a true final solution. I have an active Gutsy partition, and now a Hardy partition (upgraded from Feisty this week). I would like to see this bug actively worked in Hardy to a point where I can actually use my hard drives *with* dma turned on. We've now chosen to leave Gutsy with a known major failure for everyone with SiS 5513 and Intel 82801 EB/ER IDE drivers. Can we please get this failure fixed in Hardy? (Hint: The sis5513 module still works -- but it has been marked as not to be compiled for the Gutsy and Hardy kernels. So, if we are mandating that the module cannot be allowed in the kernel, we need to look at what its doing in order to support these drivers.) Please keep us posted as new changes are put in place for this driver. Cheers! -- please patch linux-source-2.6.22 to fix ata_piix bug https://bugs.launchpad.net/bugs/133666 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 133666] Re: please patch linux-source-2.6.22 to fix ata_piix bug
** Also affects: linux-source-2.6.24 (Ubuntu) Importance: Undecided Status: New -- please patch linux-source-2.6.22 to fix ata_piix bug https://bugs.launchpad.net/bugs/133666 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
RE: [Bug 133666] Re: please patch linux-source-2.6.22 to fix ata_piix bug
I tried. The latest 2.6.22 and 2.6.24 Ubuntu kernels both prevent my SiS 5513 driver from seeing my hard drives. They lock up very quickly after starting the kernel. Can you please at least explain what the SIS5513 module is trying to do and why we're adamant that it must be removed from Ubuntu? I'm assuming that something has been coded that is supposed to take the place of the SIS5513 module. However, that "something" is evidently not working. It's not working in Gutsy, and its not working yet in Hardy. Any chance we could create a kernel *with* the module compiled and ready for use in either Gutsy or Hardy? David > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Date: Mon, 3 Dec 2007 20:04:19 + > Subject: [Bug 133666] Re: please patch linux-source-2.6.22 to fix ata_piix bug > > Hi Edward, > > The Hardy Heron 2.6.24 kernel is out for testing. Care to try > installing and report back your results. Thanks! > > ** Also affects: linux (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: linux (Ubuntu) >Status: New => Incomplete > > -- > please patch linux-source-2.6.22 to fix ata_piix bug > https://bugs.launchpad.net/bugs/133666 > You received this bug notification because you are a direct subscriber > of the bug. _ Your smile counts. The more smiles you share, the more we donate. Join in. www.windowslive.com/smile?ocid=TXT_TAGLM_Wave2_oprsmilewlhmtagline -- please patch linux-source-2.6.22 to fix ata_piix bug https://bugs.launchpad.net/bugs/133666 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
RE: [Bug 133666] Re: please patch linux-source-2.6.22 to fix ata_piix bug
I tried. The latest 2.6.22 and 2.6.24 Ubuntu kernels both prevent my SiS 5513 driver from seeing my hard drives. They lock up very quickly after starting the kernel. Can you please at least explain what the SIS5513 module is trying to do and why we're adamant that it must be removed from Ubuntu? I'm assuming that something has been coded that is supposed to take the place of the SIS5513 module. However, that "something" is evidently not working. It's not working in Gutsy, and its not working yet in Hardy. Any chance we could create a kernel *with* the module compiled and ready for use in either Gutsy or Hardy? David > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Date: Mon, 3 Dec 2007 20:04:19 + > Subject: [Bug 133666] Re: please patch linux-source-2.6.22 to fix ata_piix bug > > Hi Edward, > > The Hardy Heron 2.6.24 kernel is out for testing. Care to try > installing and report back your results. Thanks! > > ** Also affects: linux (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: linux (Ubuntu) >Status: New => Incomplete > > -- > please patch linux-source-2.6.22 to fix ata_piix bug > https://bugs.launchpad.net/bugs/133666 > You received this bug notification because you are a direct subscriber > of the bug. _ Share life as it happens with the new Windows Live.Download today it's FREE! http://www.windowslive.com/share.html?ocid=TXT_TAGLM_Wave2_sharelife_112007 -- please patch linux-source-2.6.22 to fix ata_piix bug https://bugs.launchpad.net/bugs/133666 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
One line of changes in the .config file -- which would only impact those that actually utilize the module -- could sure fix a lot of problems. Here's a partial listing of what appear to be issues directly related to this missing module: >From the forums: http://ubuntuforums.org/showthread.php?t=586894 Bug 123789, Kernel 2.6.22-x will not boot on laptop Bug 131945, Bad recognition of DD by ata_piix Bug 133666, please patch linux-source-2.6.22 to fix ata_piix bug Bug 152820, Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable Bug 155702, pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available! Bug 163753, Strange ATA HD configuration Bug 164722, kernel 2.6.22 crash on toshiba m30x-127 -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 123789] Re: Kernel 2.6.22-x will not boot on laptop
I see that some people reporting this issue have an nVidia IDE controller, while others have an Intel 82801 controller, and there may even be other controllers represented here. I do not have personal experience with the Intel 82801 controller, but I have seen reports from other users that indicate that the 82801 uses the sis5513 module in older kernels (for instance, Feisty's 2.6.20 series). Any of you that still have working kernels may want to check for the presence of this module in your lsmod reports. For some reason, the sis5513 module has been disabled in the more recent Gutsy kernels (by the time I first switched to Gutsy, they were already up to 2.6.22.13, so I can't vouch for earlier Gutsy kernels). The module is still in the code, but its been completely shut off so the module is not available. I know from personal experience, including kernel recompiles, that the kernel code is not yet ready to shut off the sis5513 module. Without this module, my own computer (which has an official SiS 5513 IDE controller) will not boot from either a 2.6.22 or 2.6.23 kernel without the SiS 5513 module -- the computer simply does not recognize my hard drives. But simply enabling this one module brings me back to a working computer. Cheers! -- Kernel 2.6.22-x will not boot on laptop https://bugs.launchpad.net/bugs/123789 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 164722] Re: kernel 2.6.22 crash on toshiba m30x-127
Hmm. I've a theory -- based on what others are reporting about the Intel 82801 IDE controllers. When you boot into the 2.6.20 kernel and run 'lsmod', do you have the 'sis5513' module listed amongst the list? If so, that could be the problem. The Ubuntu kernel folk chose to disable the sis5513 module for the 2.6.22 kernels. No explanation given, and its causing quite a bit of grief to those that use hardware supported by this module. Cheers! -- kernel 2.6.22 crash on toshiba m30x-127 https://bugs.launchpad.net/bugs/164722 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 131945] Re: Bad recognition of DD by ata_piix
FYI -- see forum topic http://ubuntuforums.org/showthread.php?t=586894 The original poster of the topic also had an Intel 82801 EB/ER driver, but his lsmod from Etch included the sis5513 module. For whatever reason, the Ubuntu kernel folk has chosen to compile the kernel with the use of this module completely disabled. The module is still this in the code, but they've chosen to not even compile the module. If you're comfortable with this -- try recompiling your kernel with the sis5513 module enabled. Instead of this, as found in the stock Gutsy .config file # CONFIG_BLK_DEV_SIS5513 is not set Use this, as found in the stock Feisty .config file CONFIG_BLK_DEV_SIS5513=m Cheers! -- Bad recognition of DD by ata_piix https://bugs.launchpad.net/bugs/131945 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
mfajer, original poster of this thread: http://ubuntuforums.org/showthread.php?t=586894 has an Intel 82801 EB/ER IDE controller, but his lsmod report from Etch shows that this also uses the SIS5513 module. So, it appears that the Intel 82801 EB/ER driver is also broken by dropping this module. -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 155702] Re: pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available!
I tried recompiling the latest stable kernel from the official kernel archives -- 2.6.23.8 -- by taking the stock Ubuntu .config file and a make oldconfig. By using Ubuntu's .config file, the SiS 5513 module was *not* included in the kernel. For that test, I had the same results as I have with the provided Gutsy kernel -- my computer would not boot because it could not find the hard drives. But the simple task of enabling the SiS 5513 module to be built got my computer up and running. So, I currently have a Gutsy computer with a 2.6.23.8 kernel and, with the help of "envy", the latest nvidia drivers. This is all that needs to change. In the .config file, instead of this: # CONFIG_BLK_DEV_SIS5513 is not set Use this: CONFIG_BLK_DEV_SIS5513=m I've been hearing that we're somehow trying to move away from whatever the SIS5513 module is trying to accomplish. That may be, but we didn't accomplish it for Gutsy -- and now we've broken everyone that uses this kind of interface (including SiS 5513 and Intel 82801 EB/ER IDE controllers, and any other controllers that use this module). Evidently the Ubuntu kernel folk canceled this hardware-specific kernel fix, then forgot to actually test it on the related hardware. And now that this is in the "stable" distribution, we're having a hard time convincing them that they've dropped support for these specific IDE controllers. Cheers! -- pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available! https://bugs.launchpad.net/bugs/155702 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 133666] Re: please patch linux-source-2.6.22 to fix ata_piix bug
A careful look at this forum topic: http://ubuntuforums.org/showthread.php?t=586894 will show that the original poster (mfajer) has an Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller, yet his Etch lsmod report includes the SIS5513 module. So, looks like people with the Intel 82801 controllers are also messed up by the removal of this module. -- please patch linux-source-2.6.22 to fix ata_piix bug https://bugs.launchpad.net/bugs/133666 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
I don't understand how this does not meet the criteria. I see this in the criteria: * Bugs which represent severe regressions from the previous release of Ubuntu Now, this may not be a "severe regression" for everyone. But for many that own a computer with a SIS5513 IDE controller, going from a Feisty install where everything works, to a Gutsy install, where the system can't even boot because the IDE controller cannot recognize the hard drives -- that's a very severe regression! No solution has been presented that allows me to boot my computer with its SiS 5513 IDE controller without recompiling the kernel to include the necessary IDE module. So, here's what I know in regard to the requested documentation: 1) Impact of the bug: Computers with SiS 5513 IDE controllers have reported everything from complete inability to boot, to very flaky disk access, even locking up the system. One proposed work-around was to force the ide_generic and ide_disk modules -- a "solution" that prevents the use of DMA in CD- / DVD-ROM drives connected to the computer. Thus, an unacceptable solution. That from my personal experience coupled with reports seen on the web forums. 2) I don't know of the bug being addressed in the "development" branch. But I can look back to former stable branches!!! >From the Feisty stock .config file: CONFIG_BLK_DEV_SIS5513=m >From the Gutsy stock .config file: # CONFIG_BLK_DEV_SIS5513 is not set 3) The patch: well, just correct the one line in the .config file in the kernel. That's it. Basically -- the module that the kernel folk have written for the SiS 5513 IDE controller should be allowed to be used by those of us with such a controller. Since this is built as a module, I would expect it to only be used by computers with the appropriate hardware. (Note: I tested with the ubuntu .config file, but with the latest 2.6.22 official Linux kernel -- if any Ubuntu-specific changes have been made to this module, there may be problems I am not aware of) 4) Reproducing the bug. I migrated my computer up from a Feisty install, so this *might* be a problem specific to migration, rather than new installs, but I doubt it. First: get a computer with a SiS 5513 IDE controller, as the error is specific to this hardware. Then try a) a fresh install with Gutsy, and b) a fresh install with Feisty, followed by a migration to Gutsy. I would expect both to cause problems. (I remember trying the new install. My computer crashed during the install, though I don't recall the specifics of where) If you're able to reboot successfully off of such a computer, and hdparm reports that DMA is settable for any CD- / DVD drives on the IDE controller, then something else is the problem. But I think you're going to find issues. 5) Regression potential: If you have a computer with a SiS 5513 IDE controller, migrating to Gutsy can bring your computer to a complete halt. If you can *somehow* tweak your computer to boot, even with this controller, than you'll probably find that the drives are not all working as they optimally should. This should only affect the users of this particular style of IDE controller, but the probalem for computers using this controller is widespread, if not all-encompassing. According to my personal experience, SiS 5513 drivers were working fine from Hoary through Feisty, but the install of Gutsy has been problematic for this controller. Recompiling the kernel with this one extra module enabled brought my computer back to its pre-Gutsy working state. I personally would be eager to test any proposed version of the kernel for usability on a computer with a SiS 5513 controller. David Wynn -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 155702] Re: pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available!
BTW -- I can't vouch for effectiveness of this fix. I recompiled the 2.6.23 (which already has this "fix" coded in) and my computer failed to boot -- got the 1 millimeter of progress hang. But recompiling the 2.6.23 kernel *with* the SIS5513 module fixed my problem. But then 2.6.22 worked fine for me also once the SIS5513 module was included. So, from my experience, SIS5513 issues continue to stem from the absence of the module in the Ubuntu kernel. (If there is supposed to be code the replaces the SIS5513 module, that code has not been installed in the kernel's for 2.6.22 or 2.6.23) I have, however, removed the duplicate tag from this bug. -- pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available! https://bugs.launchpad.net/bugs/155702 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 155702] Re: pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available!
** This bug is no longer a duplicate of bug 150693 stock 2.6.22 kernels don't detect both IDE HDDs anymore -- pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available! https://bugs.launchpad.net/bugs/155702 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 150011] Re: Crashes on startup on Dell Inspiron 1501
If you still have the 2.6.22-15 kernel available, please start with that kernel and provide the information requested at https://wiki.ubuntu.com/KernelTeamBugPolicies. -- Crashes on startup on Dell Inspiron 1501 https://bugs.launchpad.net/bugs/150011 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 155702] Re: pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available!
*** This bug is a duplicate of bug 150693 *** https://bugs.launchpad.net/bugs/150693 Marked as a duplicate of 150693. Both are dealing with the SiS 5513 driver. My own experience with the SiS 5513 driver showed that enabling the kernel module for SiS 5513 fixed my computer. Module was enabled in Feisty, but disabled in Gutsy for some reason. ** This bug has been marked a duplicate of bug 150693 stock 2.6.22 kernels don't detect both IDE HDDs anymore -- pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available! https://bugs.launchpad.net/bugs/155702 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
** Changed in: linux-source-2.6.22 (Ubuntu) Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Ubuntu Kernel Storage Team (ubuntu-kernel-storage) -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team) ** Changed in: linux-source-2.6.22 (Ubuntu) Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team) ** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => (unassigned) -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
I will admit, I haven't confirmed this in *exactly* a Ubuntu way -- but I have confirmed the issue, and the fix is very simple -- at least in my case, it was much easier than the diff shown. The key is right here in the diff: -# CONFIG_BLK_DEV_SIS5513 is not set +CONFIG_BLK_DEV_SIS5513=m Looking back at my own system, triple boot: Windows ME (got tired of paying the tax); Feisty; Gutsy. >From /boot/config-2.6.20-16-generic (feisty) CONFIG_BLK_DEV_SIS5513=m >From /boot/config-2.6.22-14-generic (gutsy) # CONFIG_BLK_DEV_SIS5513 is not set I took the absolute last version of the 2.6.22 kernels from the official linux kernel archives (as opposed to the Ubuntu source). I then took my config-2.6.22-14-generic and allowed for the SIS5513 module to be built. I rebuilt the kernel and headers and installed them. I then rebooted my computer. With the Ubuntu 2.6.22-14, my computer always hangs very quickly -- the progress bar shows a couple millimeters before the crash. Then it just takes several minutes to finally drop to a command line. With my newly compiled kernel with the SiS 5513 module available, the computer boots all the way to a normal command line (I'd probably have X, but I don't have the restricted drivers yet for the new kernel). I am convinced that the solution here, and for everyone else dealing with SiS 5513 controllers is that the current compile of the kernel does not make the needed module available to us. -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
** Changed in: linux-source-2.6.22 (Ubuntu) Status: New => Confirmed -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 133666] Re: please patch linux-source-2.6.22 to fix ata_piix bug
FYI -- the absence of the SIS5513 module seems to be breaking those of us with SiS 5513 IDE controllers. I went a little outside the purely Ubuntu way of doing things, but not too far. I downloaded the latest 2.6.22.12 version from the linux kernel archives. Then I took my Ubuntu config file, and mostly updated just the one line (also updated the kernel version tag, but nothing else). Then I recompiled the kernel. My system now boots directly. The original poster does not list his IDE controller, so I cannot tell if this is the same problem -- but seems to fix SiS 5513 controllers. Cheers! -- please patch linux-source-2.6.22 to fix ata_piix bug https://bugs.launchpad.net/bugs/133666 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 133666] Re: please patch linux-source-2.6.22 to fix ata_piix bug
FYI -- I also had no problems in Feisty, but have been having *serious* issues in Gutsy with booting. I update /etc/intiramfs-tools/modules to include ide-generic, but that means -- no DMA. I also have a SIS5513 IDE controller. I was thinking of recompiling my own kernel, when I found this: >From /boot/config-2.6.20-16-generic (feisty) CONFIG_BLK_DEV_SIS5513=m >From /boot/config-2.6.22-14-generic (gutsy) # CONFIG_BLK_DEV_SIS5513 is not set Why was this module turned off for Gutsy? Please allow this as a module again. As a module, it can do no harm to folks with other IDE drivers, but I'm guessing it could sure relieve some grief for those of us with this particular driver! -- please patch linux-source-2.6.22 to fix ata_piix bug https://bugs.launchpad.net/bugs/133666 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 155702] Re: pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available!
Worthy of noting. I have no problems with SiS5513 IDE in my Feisty distribution, but cannot get it loaded without some initramfs-tools overrides in my Gutsy distribution. I would guess this is the reason: >From /boot/config-2.6.20-16-generic (feisty) CONFIG_BLK_DEV_SIS5513=m >From /boot/config-2.6.22-14-generic (gutsy) # CONFIG_BLK_DEV_SIS5513 is not set I notice that there are other similar options that were enabled in feisty that, for some reason, have been disabled in gutsy. I would guess this is the reason for the slew of issues with bad boots. Please allow for this module in the kernel again. Thanks. -- pata_sis fails to enable udma100, which causes a long (~1min) delay at boot. Patch available! https://bugs.launchpad.net/bugs/155702 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 155231] Re: NV20 [GeForce3] nvidia not supported by nvidia-glx in gutsy
The error message you listed indicates that you're using nvidia-glx-new. That one is not intended for use with a GeForce 3. The nvidia-glx is, although you may need to do some tweaking under nvidia-xconfig. For the record, there are now two generations of legacy drivers. That's why there's now three different versions of nvidia-glx. According to nvidia, these cards are supported by the nvidia-glx-new driver: http://www.nvidia.com/object/IO_18897.html Cards supported by the two legacy drivers are here. nvidia-glx cards first, then nvidia-glx-legacy cards: http://www.nvidia.com/object/IO_32667.html -- NV20 [GeForce3] nvidia not supported by nvidia-glx in gutsy https://bugs.launchpad.net/bugs/155231 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 151013] Re: can't boot linux-image-2.6.22 ppc
Stefan, thank you for pointing me in the right direction. On my Athlon Classic, I added the ide-generic and ide-disk modules to the /etc /initramfs-tools/modules. (I couldn't find an ide-core module) I then ran the command indicated in your message. That fixed my kernel. I still wonder if the kernel patch indicated in Bug 133666 would have prevented the need for these overrides. -- can't boot linux-image-2.6.22 ppc https://bugs.launchpad.net/bugs/151013 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 155703] Re: Restricted Manager installs wrong nvidia driver
My apologies. Thank you for the correction. For reference purposes, I found these two links that should cover the difference between the various Linux drivers: Cards that are supported by nvidia-glx-new are here: http://www.nvidia.com/object/IO_18897.html Cards supported by the two legacy drivers are here. nvidia-glx cards first, then nvidia-glx-legacy cards: http://www.nvidia.com/object/IO_32667.html And the GeForce2 MX is listed on these pages as being supported under nvidia-glx. That being said, as long as a card existed before one of the older drivers, it should be possible to use your card with the older driver. So, even if the GeForce2 MX is supported by the nvidia-glx drivers, because it was around when the older drivers were built, it would also work with the nvidia-glx-legacy drivers. I will also point out that there is an application called nvidia- xconfig. Check "man nvidia-xconfig" for the various options that may need to be tweaked to get a card running with any of these drivers. -- Restricted Manager installs wrong nvidia driver https://bugs.launchpad.net/bugs/155703 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 155719] Re: nvidia-glx-legacy driver upgrades to nvidia-glx (gutsy)
Found this yesterday: http://kubuntuforums.net/forums/index.php?topic=3087867.0 Try 'man nvidia-xconfig'. There are a lot of options here, and what works for one, may not work for all. Try to think back as to whether there was anything you needed to tweak for your card in Feisty.. Personally, in Feisty, I had to add this to the "Screen" section of xorg.conf to keep my screen from locking up: Option "NvAGP" "0" In Gutsy, this is accomplished by "sudo nvidia-xconfig --nvagp=0". If you still have it available, look back at your Feisty xorg.conf for hints that may determine what you need to add. For reference purposes, according to nvidia, these cards are supported by the nvidia-glx-new driver: http://www.nvidia.com/object/IO_18897.html Cards supported by the two legacy drivers are here. nvidia-glx cards first, then nvidia-glx-legacy cards: http://www.nvidia.com/object/IO_32667.html -- nvidia-glx-legacy driver upgrades to nvidia-glx (gutsy) https://bugs.launchpad.net/bugs/155719 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 155231] Re: NV20 [GeForce3] nvidia not supported by nvidia-glx in gutsy
Sorry, that link should be: http://kubuntuforums.net/forums/index.php?topic=3087867.0 -- NV20 [GeForce3] nvidia not supported by nvidia-glx in gutsy https://bugs.launchpad.net/bugs/155231 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 155231] Re: NV20 [GeForce3] nvidia not supported by nvidia-glx in gutsy
Found this yesterday: http://kubuntuforums.net/forums/inde...opic=3087867.0 Try 'man nvidia-xconfig'. There are a lot of options here, and what works for one, may not work for all. Try to think back as to whether there was anything you needed to tweak for your card in Feisty.. Personally, in Feisty, I had to add this to the "Screen" section of xorg.conf to keep my screen from locking up: Option "NvAGP" "0" In Gutsy, this is accomplished by "sudo nvidia-xconfig --nvagp=0". If you still have it available, look back at your Feisty xorg.conf for hints that may determine what you need to add. -- NV20 [GeForce3] nvidia not supported by nvidia-glx in gutsy https://bugs.launchpad.net/bugs/155231 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 155231] Re: NV20 [GeForce3] nvidia not supported by nvidia-glx in gutsy
I use Kubuntu, so can't help on the Gnome front. There may be something with your computer trying to run Compiz Fusion -- which is supposed to be installed by default in Gutsy for machines that can handle it. That being said, according to nvidia, the GeForce 3 should be supported by the later drivers included in nvidia-glx. There are issues with the nvidia-glx driver in Gutsy that were not present in Feisty. nvidia-glx worked find in Feisty for my GeForce FX 5700 LE. In Gutsy, I get basic KDE functionality, but anything that requires glx is broken. As an example, under Gutsy, when I run glxgears, the window that *should* show a set of moving gears is just blank. Meanwhile, in the console screen where I ran the glxgears command, its showing appalling performance calculations around 1.0 fps or less, until it finally crashes. I don't think that the issue is a matter of your card not being supported as much as it seems to be an issue of nvidia-glx not working correctly. -- NV20 [GeForce3] nvidia not supported by nvidia-glx in gutsy https://bugs.launchpad.net/bugs/155231 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 155703] Re: Restricted Manager installs wrong nvidia driver
See this link: http://nvidia.custhelp.com/cgi- bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=276&p_created=1119630054&p_sid=UlOouZOi&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPSZwX3NvcnRfYnk9JnBfZ3JpZHNvcnQ9JnBfcm93X2NudD01MDcmcF9wcm9kcz0mcF9jYXRzPSZwX3B2PSZwX2N2PSZwX3NlYXJjaF90eXBlPWFuc3dlcnMuc2VhcmNoX25sJnBfcGFnZT0y&p_li=&p_topview=1 According to nvidia -- GeForce2 MX *is* supported by the later drivers included in nvidia-glx. However, its about the earliest card that is still supported. -- Restricted Manager installs wrong nvidia driver https://bugs.launchpad.net/bugs/155703 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 155719] Re: nvidia-glx-legacy driver upgrades to nvidia-glx (gutsy)
Although the nvidia-glx-legacy should *not* have updated to nvidia-glx, the nvidia-glx is the correct drivier for your card (unless its an FX Go for laptops). Here's a link giving the specifics as to which cards should be using nvidia-glx and which should be using nvidia-glx-legacy: http://nvidia.custhelp.com/cgi- bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=276&p_created=1119630054&p_sid=UlOouZOi&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPSZwX3NvcnRfYnk9JnBfZ3JpZHNvcnQ9JnBfcm93X2NudD01MDcmcF9wcm9kcz0mcF9jYXRzPSZwX3B2PSZwX2N2PSZwX3NlYXJjaF90eXBlPWFuc3dlcnMuc2VhcmNoX25sJnBfcGFnZT0y&p_li=&p_topview=1 Having said that, there *are* issues currently with the nvidia-glx driver. I use a GeForce FX 5700 LE and can get basic functionality wiorking. But anything glx-related is broken in Gutsy. The nvidia-glx driver in Feisty was working just fine with my card. -- nvidia-glx-legacy driver upgrades to nvidia-glx (gutsy) https://bugs.launchpad.net/bugs/155719 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 146287] Re: kernel 2.6.22 fails to mount hard drives, drops to busybox
This could be related to Bug 133666 which indicates problems with recognizing ATA / IDE hard drives. There is a patch listed in that bug, but the patch has not been applied to Ubuntu yet. -- kernel 2.6.22 fails to mount hard drives, drops to busybox https://bugs.launchpad.net/bugs/146287 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 150693] Re: stock 2.6.22 kernels don't detect both IDE HDDs anymore
Perhaps related to Bug 133666, which documents a known issue with ATA / IDE drive detection. That bug also lists a patch, but the patch has not been applied to Ubuntu yet. -- stock 2.6.22 kernels don't detect both IDE HDDs anymore https://bugs.launchpad.net/bugs/150693 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 151013] Re: can't boot linux-image-2.6.22 ppc
Perhaps related to Bug 133666, which speaks of issues with ATA / IDE hard-drive detection. The other bug lists a patch, but that patch has not been applied to Ubuntu yet. -- can't boot linux-image-2.6.22 ppc https://bugs.launchpad.net/bugs/151013 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 131937] Re: Gutsy installation fails on HP 6510b
May be related to Bug 133666 which deals with a known issue with recognizing ATA / IDE drives. A patch is supplied in the other bug, but that patch has not been applied to Ubuntu yet. -- Gutsy installation fails on HP 6510b https://bugs.launchpad.net/bugs/131937 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 135154] Re: gutsy tribe 5 hangs after reboot
Possibly linked to issue 133666. That issue indicates a recognized issue with ATA / IDE detection. As indicated in the other issue, a patch has been created, but not yet applied in Ubuntu. -- gutsy tribe 5 hangs after reboot https://bugs.launchpad.net/bugs/135154 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 73082] Re: xbase-clients and xutils package description is inaccurate
As these are updated, please make sure that the description of xbase- clients and xutisl no longer includes any reference to them being "transitional" packages. They are currently used as meta-packages, not transitional packages. This issue is still occurring in Feisty and Gutsy. ** Tags added: edgy feisty gutsy -- xbase-clients and xutils package description is inaccurate https://bugs.launchpad.net/bugs/73082 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 151601] [gutsy] ichthux-desktop depends on transitional package
Public bug reported: Ichthux-desktop currently requires xkeyboard-config which is a transitional package, and thus no longer needed. Please remove xkeyboard-config from the requirements for ichthux-desktop. ** Affects: ichthux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: gutsy ** Tags added: gutsy -- [gutsy] ichthux-desktop depends on transitional package https://bugs.launchpad.net/bugs/151601 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 96207] Re: Feisty package pciutils depends on "obsolete" package
Problem still exists in gutsy. ** Tags added: feisty gutsy -- Feisty package pciutils depends on "obsolete" package https://bugs.launchpad.net/bugs/96207 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 64616] Re: Ubuntu-Desktop (et al) still depends on xkeyboard-config
I no longer use edgy. I see that this has been fixed in feisty for ubuntu-desktop, kubuntu-desktop, edubuntu-desktop, xubuntu-desktop. -- Ubuntu-Desktop (et al) still depends on xkeyboard-config https://launchpad.net/bugs/64616 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96207] Feisty package pciutils depends on "obsolete" package
Public bug reported: Binary package hint: pciutils Package pciutils depends on package libpci2. Package libpci2 describes itself as an obsolete package. This dependency needs to be reviewed. If libpci2 is still needed, then the description for that package needs to be changed, (if pciutils needs libpci2, then libpci2 is not obsolete). If the libpci2 dependency can be removed from pciutils, please do so. ** Affects: pciutils (Ubuntu) Importance: Undecided Status: Unconfirmed -- Feisty package pciutils depends on "obsolete" package https://launchpad.net/bugs/96207 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96199] Feisty libxklavier11 requires obsolete package
Public bug reported: Binary package hint: libxklavier11 Feisty package libxklavier11 requires package xkeyboard-config. Package xkeyboard-config is a transitional package that depends on xkb-data, but has no files of its own. The dependency needs to be changed from xkeyboard-config to xkb-data ** Affects: libxklavier (Ubuntu) Importance: Undecided Status: Unconfirmed -- Feisty libxklavier11 requires obsolete package https://launchpad.net/bugs/96199 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96193] xfburn includes dependency on obsolete package mkisofs
Public bug reported: Binary package hint: xfburn Package xfburn includes a dependency on package mkisofs. Package mkisofs includes two symlinks for mkhybrid and mkisofs. Both are symlinks for program genisoimage. Package xfburn needs to be updated, replacing all calls to these two program to genisoimage calls. The dependency needs to change from mkisofs to genisoimage. ** Affects: xfburn (Ubuntu) Importance: Undecided Status: Unconfirmed -- xfburn includes dependency on obsolete package mkisofs https://launchpad.net/bugs/96193 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96190] xfburn includes dependency on obsolete binary cdrecord
Public bug reported: Binary package hint: xfburn Feisty xfburn depends on package cdrecord. In Feisty, cdrecord is a transitional package containing just a symlink to package wodim. xfburn needs to be updated, changing all cdrecord calls to wodim calls. The cdrecord dependency needs to be changed to a wodim dependency. ** Affects: xfburn (Ubuntu) Importance: Undecided Status: Unconfirmed -- xfburn includes dependency on obsolete binary cdrecord https://launchpad.net/bugs/96190 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 29833] Re: Breezy Denemo does not allow note entry
I have confirmed that this has been fixed in both Dapper and Edgy. ** Changed in: denemo (Ubuntu) Status: Needs Info => Fix Released -- Breezy Denemo does not allow note entry https://launchpad.net/bugs/29833 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64616] Ubuntu-Desktop (et al) still depends on xkeyboard-config
Public bug reported: Binary package hint: ubuntu-desktop This is a problem in edgy ubuntu-desktop and all edgy variants (kubuntu- desktop, edubuntu-desktop, etc). These packages still depend on xkeyboard-config. But, xkeyboard-config has no real files and only depends on one package (xkb-data). All of these desktop packages need to be changed to depend on xkb-data. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Unconfirmed -- Ubuntu-Desktop (et al) still depends on xkeyboard-config https://launchpad.net/bugs/64616 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
