Re: Please keep the old IDE chipset drivers so that external CD writers can work

2008-04-11 Thread Rick Knight
Wenzhuo Zhang wrote:
 Rick Knight wrote:

   
   $ wget
 http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-image-2.6.24-15-386_2.6.24-15.27_i386.deb

   $ sudo dpkg -i linux-image-2.6.24-15-386_2.6.24-15.27_i386.deb

   
   
 I tried this tonight. I ran into dependency problems.
 linux-image-2.6.24-15-386_2.6.24-15.27_i386.deb depends on
 module-init-tools_3.3-pre11-4ubuntu5_i386.deb which depends on
 libc6_2.7-10ubuntu3_i386.deb. I don't mind replacing module_init_tools,
 but libc6 scares me a little. Is it safe to replace the Gutsy libc6 with
 the Hardy libc6? It will probably lead to more dependency problems.

 

 Try:

 $ sudo dpkg --ignore-depends=module-init-tools -i 
 linux-image-2.6.24-15-386_2.6.24-15.27_i386.deb


 Wenzhuo
   
Wenzhuo,

I've found a fix (or work-around) for this issue. I found this kernel 
parameter all_generic_ide mentioned as a possible fix for a problem 
with Seagate drives. I tried using it with my default, un-modified Gutsy 
kernel but it didn't solve the problem. I tried it with the custom Gutsy 
kernel I built with the pata_via module enabled and that worked. I don't 
know why, but the combination of the pata_via module and 
all_generic_ide allows my system to boot and run the Gutsy kernel. Now 
I'll be ready to upgrade to Hardy after it's had a week or to to stabilize.

On another note, Brian Murray (ubuntu developer?) has marked my bug 
(212042) as won't fix because it doesn't meet the criteria for a stable 
release update. What does this mean?

Thanks,
Rick Knight

P.S. Where is your petition to keep the old IDE drivesr?

 

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Please keep the old IDE chipset drivers so that external CD writers can work

2008-04-09 Thread Rick Knight
Wenzhuo Zhang wrote:
 Rick Knight wrote:

   
   $ wget
 http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-image-2.6.24-15-386_2.6.24-15.27_i386.deb

   $ sudo dpkg -i linux-image-2.6.24-15-386_2.6.24-15.27_i386.deb

   
   
 I tried this tonight. I ran into dependency problems.
 linux-image-2.6.24-15-386_2.6.24-15.27_i386.deb depends on
 module-init-tools_3.3-pre11-4ubuntu5_i386.deb which depends on
 libc6_2.7-10ubuntu3_i386.deb. I don't mind replacing module_init_tools,
 but libc6 scares me a little. Is it safe to replace the Gutsy libc6 with
 the Hardy libc6? It will probably lead to more dependency problems.

 

 Try:

 $ sudo dpkg --ignore-depends=module-init-tools -i 
 linux-image-2.6.24-15-386_2.6.24-15.27_i386.deb


 Wenzhuo
   
Wenzhuo,

This worked. I was able to install the Hardy kernel and then boot using 
it. My drives show up as SCSI devices (/dev/sdxn) instead of IDE devices 
and the pata_via module is being loaded. The IDE modules are not 
loading. Whatever was broken in Gutsy seems fixed in Hardy. There a 
couple of problems, that will go away when I upgrade to Hardy. I get a 
Cups backend error and the VBox modules won't load. Other than that, 
things look good.

Thanks,
Rick


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Please keep the old IDE chipset drivers so that external CD writers can work

2008-04-08 Thread Rick Knight
Wenzhuo Zhang wrote:
 Rick Knight wrote:

   
 I'm not sure I follow you here. Are you suggesting I upgrade to the
 Hardy beta, or just set my repositories to Hardy and update. Won't that
 be an upgrade? How stable is Hardy. I know the code freeze is this week,
 but is it safe to upgrade to Hardy?
 

 I am suggesting you try the libata pata_via module, because the old
 via82cxxx ide driver has been disabled in favor of pata_via since
 2.6.24-13.23; and if it does not support your controller, report a bug
 as soon as possible so that it has a chance to get fixed before hardy
 release.

   
 Also, I rebuilt the Gutsy kernel to add support for the pata_via module,
 but that didn't help, I still can't boot into the Gutsy kernel.
 

 You can try downloading the latest hardy kernel and install in your 
 7.10(gutsy)
 installation. Again, remove the IDE modules from /etc/initramfs-tools/modules
 first before proceeding:

   $ wget 
 http://mirrors.kernel.org/ubuntu/pool/main/l/linux/linux-image-2.6.24-15-386_2.6.24-15.27_i386.deb
   $ sudo dpkg -i linux-image-2.6.24-15-386_2.6.24-15.27_i386.deb
   
I tried this tonight. I ran into dependency problems. 
linux-image-2.6.24-15-386_2.6.24-15.27_i386.deb depends on 
module-init-tools_3.3-pre11-4ubuntu5_i386.deb which depends on 
libc6_2.7-10ubuntu3_i386.deb. I don't mind replacing module_init_tools, 
but libc6 scares me a little. Is it safe to replace the Gutsy libc6 with 
the Hardy libc6? It will probably lead to more dependency problems.

Thanks,
Ric
 If you have empty space in your hard drive, you can try install hardy
 in a separate partition. I have been using it on a daily basis for one
 month. I've seen no major breakage. It's still not recommended for
 production usage though.

 Wenzhuo
   


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Please keep the old IDE chipset drivers so that external CD writers can work

2008-04-07 Thread Rick Knight
Wenzhuo Zhang wrote:
 Rick Knight wrote:

   
 I downloaded the Kubuntu 8.04 Desktop CD ISO, burned the ISO and booted.
 It DOES install my hard drives as /dev/hd devices, not /dev/sd and I can
 access them without any problem, so whatever is causing my problem with
 Gutsy, has been fixed in Hardy. Also, I think tells me my Via controller
 is not compatible with libata.
 

 In Feisty and Gutsy kernels, the IDE driver via82cxxx is the only driver
 that supports VIA_82C586_1(1106:0571), and the new libata based driver
 pata_via is not enabled. So the Gutsy problem you experienced is probably
 a regression of via82cxxx driver introduced in linux-image-2.6.22.

 Starting from linux-image-2.6.24-13.23, via82cxxx is disabled in favor
 of pata_via. Kubuntu 8.04 beta CD ships with 2.6.24-12, which includes
 both via82cxxx and pata_via. Judging from the fact your drives are
 recognized as /dev/hd?, via82cxxx is loaded first, which means the
 via82cxxx issue has been fixed in 2.6.24-12.

 You may want to download and install all the hardy updates up-to-date
 using Update Manager. linux-image-2.6.25-15-generic will be installed
 in the update process. Be sure to remove the IDE drivers you added to
 /etc/initramfs-tools/modules before starting to update. You'll then find
 out whether pata_via is working properly for VIA_82C586_1. If it does
 not work for you, you can file another bug report.

 Wenzhuo
   
Wenzhuo,

I'm not sure I follow you here. Are you suggesting I upgrade to the 
Hardy beta, or just set my repositories to Hardy and update. Won't that 
be an upgrade? How stable is Hardy. I know the code freeze is this week, 
but is it safe to upgrade to Hardy?

Also, I rebuilt the Gutsy kernel to add support for the pata_via module, 
but that didn't help, I still can't boot into the Gutsy kernel.

Thanks,
Rick

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Please keep the old IDE chipset drivers so that external CD writers can work

2008-04-04 Thread Rick Knight
Wenzhuo Zhang wrote:
 Rick Knight wrote:

   
 I've removed/commented everything from /etc/initramfs-tools/modules except

 via82cxxx
 ide_generic
 ide_disk
 ide_cd

 And I've run

 $update-initramfs -c -k 2.6.22-14-generic.

 I still can't boot the 2.6.22-14-generic kernel but now I can see my
 CDrom and DVD drives. They were not loading before, but are now, so I
 think we're on the right track. It seems like there is still a module or
 driver missing. Any other ideas?
 

 It's becoming difficult to track your problem. You may want to file a
 separate bug report at https://bugs.launchpad.net/, and attach the
 dmesg, lspci -vvn and lshw output to it when running the feisty
 kernel.

 For the Gutsy boot messages, you can boot into single-user mode,
 and take a screenshot of the failure messages using a digital camera,
 and then attach it to the bug report as well. Do it twice with and
 without preloading ide drivers in initramfs.

   
 I do plan on downloading the 8.04 live CD this weekend as you suggested.
 

 Wenzhuo
   
Wenzhou, thanks for your help. As you suggested, I have just submitted a 
bug report to  launchpad / ubuntu with the output of dmesg, lspci -vvn 
and lshw attached along with a second comment with the screen shot 
attached. It is bug report number 212042 
(https://bugs.launchpad.net/ubuntu/+bug/212042).

Thanks, Rick Knight

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Please keep the old IDE chipset drivers so that external CD writers can work

2008-04-04 Thread Rick Knight
Wenzhuo Zhang wrote:
 Rick Knight wrote:

   
 I've removed/commented everything from /etc/initramfs-tools/modules except

 via82cxxx
 ide_generic
 ide_disk
 ide_cd

 And I've run

 $update-initramfs -c -k 2.6.22-14-generic.

 I still can't boot the 2.6.22-14-generic kernel but now I can see my
 CDrom and DVD drives. They were not loading before, but are now, so I
 think we're on the right track. It seems like there is still a module or
 driver missing. Any other ideas?
 

 It's becoming difficult to track your problem. You may want to file a
 separate bug report at https://bugs.launchpad.net/, and attach the
 dmesg, lspci -vvn and lshw output to it when running the feisty
 kernel.

 For the Gutsy boot messages, you can boot into single-user mode,
 and take a screenshot of the failure messages using a digital camera,
 and then attach it to the bug report as well. Do it twice with and
 without preloading ide drivers in initramfs.

   
 I do plan on downloading the 8.04 live CD this weekend as you suggested.
 

 Wenzhuo
   
Wenzhuo,

I downloaded the Kubuntu 8.04 Desktop CD ISO, burned the ISO and booted.
It DOES install my hard drives as /dev/hd devices, not /dev/sd and I can
access them without any problem, so whatever is causing my problem with
Gutsy, has been fixed in Hardy. Also, I think tells me my Via controller
is not compatible with libata.

Thanks,
Rick


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Please keep the old IDE chipset drivers so that external CD writers can work

2008-04-03 Thread Rick Knight
Wenzhuo Zhang wrote:
 Rick Knight wrote:

   
 boot the 2.6.22.14-generic kernel? I have a 4 year old Soyo motherboard 
 with Via chipset. Can I rebuild the kernel to get this older IDE 
 support? I can still boot into my Feisty kernel.
 


 If your chipset is not supported by libata, and you want rebuild the kernel
 to add the old drivers back, following the instructions on this web page:

 https://help.ubuntu.com/community/Kernel/Compile

 Wenzhuo


   
After doing a lot of comparing between my desktop at work, my notebook 
and my desktop at home, I'm beginning to think that the problem is the 
chipset in my desktop at home is not supported by libata. The 
motherboard in the PC is about 4 years old and has a Via VT82C568A/B, 
VT82C686A/B, VT823x/A/C chipset. When I boot the Feisty kernel, libata 
and ata_generic are being loaded but are not being used...

$ lsmod | grep ata
ata_generic9902   0
libata 125720 ata_generic
scsi_mod142348 libata,sg,st,aic7xxx,scsi_transport_spi

This tells me that libata is being using by ata_generic, but ata_generic 
isn't being used.

Also, lsmod shows that ide_disk is being used...

$ lsmod | grep ide
ide_cd   32672  0
cdrom   37664  1 ide_cd
ide_disk17024  5

I think this tells me that this kernel is using IDE_DISK and not 
ATA_GENERIC. Neither my desktop PC at work nor my notebook PC load the 
IDE_DISK. They both use ATA_PIIX. I've looked for a Via ATA module in 
the kernel source, but all I can find is SATA_VIA and this module is 
installed but doesn't seem to work  (I don't have serial ata drives).

Am I correct in this? If I am correct, how can I fix this problem? Is 
there a Via ata driver I'm not seeing?

Thanks,
Rick


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: Please keep the old IDE chipset drivers so that external CD writers can work

2008-04-03 Thread Rick Knight
Wenzhuo Zhang wrote:
 Rick Knight wrote:
   
 I'll file the bug report as you, suggest, tonight or this weekend. But
 until I hear a respones to the bug report, is there anyway to force the
 newer kernel to setup drives by path with hdxn instead of sdxn? Also, if
 I do rebuild the kernel, which module(s) do I need to activate?
 

 It seems to me that VIA82Cxxx chipset support is included in the Gutsy
 kernel image. BLK_DEV_VIA82CXXX is enabled as a module in
 /boot/config-2.6.22-14-generic.

 Try adding the following lines to /etc/initramfs-tools/modules:

 via82cxxx
 ide-disk
 ide-cd
 ide-generic

 and then type:

 $ sudo update-initramfs -u -k 2.6.22-14-generic

 After that, reboot into the Gutsy kernel. If you can now successfully
 boot the Gutsy kernel, libata is to blame. ;)

 Wenzhuo
   
Wenzhuo,

That's almost done it. I can see my two CD drives, /dev/hdc and 
/dev/hdd. It seems that something else is still missing, or maybe I need 
to take something out. Would anything else be effected by taking out libata?

Thanks again,
Rick Knight

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Help with Gutsy Upgrade

2008-04-01 Thread Rick Knight
Ubuntu developers. I know this is not the place for the usual requests 
for help with Ubuntu, but I don't know where else to look. I've posted 
to the Ubuntu-users list, the Ubuntu and Kubuntu forums and I've be 
visited both #ubuntu and #kubuntu on IRC. I've even added my comment to 
a Launchpad bug report, #190588. I've gotten several suggestions to fix 
my problem, but so far none of them have made a difference. I've also 
tried to post to ubuntu-devel, but the moderator refused the post and 
recommended I post here instead.

About 2 weeks ago I tried to upgrade my PC using the instructions found 
here http://www.kubuntu.org/announcements/7.10-release.php. The upgrade 
froze at Installing packages 2%. After a couple of hours I stopped the 
upgrade process and tried again. This time the upgrade finished 
successfully. I rebooted the PC expecting to get a new Gutsy desktop, 
but instead got the Busy Box initramfs prompt and this message...

Check root= bootarg cat /proc/cmdline or missing modules, devices: cat 
/proc/modules ls /dev

ALERT! /dev/disk/by-uuid/(my boot disk uuid) does not exist. Dropping to 
a shell.

All modules seem to be present and loaded but ls /dev/disk/by-uuid 
shows I have no hard drives (I actually have 2 hard drives, both EIDE 
devices, not SATA).

I can boot using the prior Feisty 2.6.20-16-generic kernel and am able 
to trouble shoot using the older kernel. As I said above, I have tried 
several suggestions to fix this problem, but so far none have had any 
effect.

I've tried re-installing the 2.6.22-14-generic kernel.
I've tried modifying initramfs.
I've re-installed and updated GRUB.
I've modified GRUB's menu.lst to use /dev/sd and /dev/hd drive identifiers.
I've tried to re-run the upgrade, both form the internet and from the 
alternate CD, but both methods say my system is up to date and can't be 
upgraded.

I don't know if this may be important information, but when I upgraded 
from Dapper to Feisty my system refused to recognize the new /dev/sd 
drive identifiers and I had to modify GRUB and /etc/fstab to use /dev/hd 
instead, but that didn't work this time.

While this may not be a common problem with the Feisty / Gutsy upgrade, 
a Google search shows the several are have the same or similar upgrade 
errors.

Can someone here please give me some suggestions to fix this problem?

Thanks,
Rick Knight




-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss