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
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
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
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
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
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
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
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
, 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
