Hi,

To see the list of devices that are mounted, you need to type "mount". You
will see something like:
/dev/sda8 on / type ext3 (rw,errors=remount-ro)
/dev/sda7 on /boot type ext2 (rw)
/dev/sda9 on /home type ext3 (rw)

In the rescue shell (where you choose shell on the root filesystem), you
need to mount /home and /boot in this case, using the commands:
mount /dev/sda7 /boot
mount /dev/sda9 /home

What's really important is to mount /, /usr (sometimes separate) and /boot
(often separate).

To create the blacklist file, the easiest is (from the same shell):
echo blacklist ata_piix > /etc/modprobe.d/blacklist-ata_piix

I've the feeling that your dpkg-reconfigure failed for 2.6.20 .

As you still have a kernel that can boot on your harddisk, I don't think you
really need to boot the rescue CD.
You can simply open a terminal, sudo -s (to get root access) and run the
dpkg-reconfigure commands.

Hope this helps,


Olivier


2007/4/22, mibane <[EMAIL PROTECTED]>:
>
> Hello again from feist :).
> I upgraded to feist and then I run the alternate cd (edgy) in 'rescue a
> broken system'. It already mounted the root partition and I mounted /home.
> Then I created "/etc/modprobe.d/blacklist-ata_piix containing:  blacklist
> ata_piix" and run "dpkg-reconfigure linux-image-2.6.20-15-generic" but not
> the edgy image.
> Then I rebooted and it failed booting from 2.6.20-15, also -11 but I could
> boot from 2.6.17-10-386.
> My question is Will I have any problems if I always boot in 2.6.17-10?
> What should I do to boot from 2.6.20-15?
> Thank you very much.
>
> --
> Feisty Fawn beta doesn't install on Toshiba Tecra S3
> https://bugs.launchpad.net/bugs/96311
> You received this bug notification because you are a direct subscriber
> of the bug.
>

-- 
Feisty Fawn beta doesn't install on Toshiba Tecra S3
https://bugs.launchpad.net/bugs/96311
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

Reply via email to