Feisty Fawn beta doesn't install on Toshiba Tecra S3

The attached lspci on the Toshiba Tecra S3

I confirm this behaviour on my Tecra S3. It was OK with 6.10
m

As if it was needed, I also confirm the behavior: none of the Ubuntu Feisty beta CDs (desktop and alternate install) are usable on a Toshiba S3.

Based on comments found elsewhere about the conflict between ata_piix and ahci, I elaborated the following work around strategy:
- install edgy (which is known to be working on the S3)
- dist-upgrade to feisty
After this installation, the system is not bootable with any of the kernels (even the one from edgy - don't know why ?!?)
- boot with the edgy alternate install CD in rescue mode
- from the rescue installer, start a shell on the root partition
- mount all necessary partitions manually (if not using a single partition setup)
- create /etc/modprobe.d/blacklist-ata_piix containing:
    blacklist ata_piix
- dpkg-reconfigure linux-image-2.6.20-15-generic
- dpkg-reconfigure linux-image-2.6.17-10-generic (from edgy)

Result: the ata_piix is now blacklisted in the initrd (thanks to dpkg-reconfigure) and the ahci is used to handle the SATA HDD.

I confirm this behaviour on my Tecra S3. It was OK with 6.10

I think it is an upstream-problem, as recent Fedora have the same problems.

romal

I had the same problem in my tecra s3 trying to install 5.10, then everything was ok with 6.10 and I've had the same problem again with Feist. Now I have gone back to 6.10 and everything was ok. But I'm afraid I'm not expert enough to try what Osmeest suggests. If anyony could detail all the steps to be taken I'm afraid I won't be able to upgrade.
Thank you.

Hi,

The procedure I described was quite detailed.

If you want, give me the result of the "mount" command and I'll try to
give you more detail.

Best regards,

Olivier

2007/4/20, mibane <email address hidden>:
> I had the same problem in my tecra s3 trying to install 5.10, then everything was ok with 6.10 and I've had the same problem again with Feist. Now I have gone back to 6.10 and everything was ok. But I'm afraid I'm not expert enough to try what Osmeest suggests. If anyony could detail all the steps to be taken I'm afraid I won't be able to upgrade.
> Thank you.
>
> --
> 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.
>

Thank you in advance.
Mu problem is that I'm quite new at Linux so I get lost because I don't know how to mount all partitions manually. I think I should read the HOWTO manual and that will not be a proble but what I don't know how to do is the rest:
create /etc/modprobe.d/blacklist-ata_piix containing:
    blacklist ata_piix
How do I do that?

- dpkg-reconfigure linux-image-2.6.20-15-generic
- dpkg-reconfigure linux-image-2.6.17-10-generic (from edgy)

thank you again.
pd. I'm going to read the manual right now

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.

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 address hidden>:
>
> 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.
>

everything is ok
I made a mistake I created the file containing 'blacklist-ata_piix' instead of 'blacklist ata_piix' I changed that and now everything works ok.
Thank you very much.

Hi,

I get ubuntu to start, but now my cd player isnt working anymore.

Indeed, you lose the access to the CDROM if you don't load ata_piix.
The important thing here is to load ata_piix after ahci (that's why ata_piix
is blacklisted).

I tried sudo modprobe ata_piix --> get back access to CD
Would be worth to try putting "ahci" and "ata_piix" in the /etc/modules (and
maybe removing the blacklist-ata_piix file).
(I don't have the time to test this right now.)

2007/4/23, toetie <email address hidden>:
>
> Hi,
>
> I get ubuntu to start, but now my cd player isnt working anymore.
>
> --
> 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.
>

I've tested the setup without blacklist and with ahci and ata_piix in /etc/modules ( in that order )

IT WORKS!! :-) I can boot ans I'm able to access cd without a manual modprobe ata_piix
thanks for the tip.

Yes it works. I think there must be an option to do this from the alternate cd pressing f6 and load ahci before ata_piix but I don't know how

mmm still problems

I had probs mount an usb harddrive and decide to reboot ----> boot failed again
I'm blacklisting ata_piix again

Can you reproduce this bug with the Ubuntu 7.10 beta release?

Yes.

See http://bugzilla.kernel.org/show_bug.cgi?id=8933

Yes
m

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Intrepid installs on my tecra S3 without problems now.
Thanks!
Milos

Hi. Fixed in 2.6.26

http://bugzilla.kernel.org/show_bug.cgi?id=9491

cu romal

Intrepid Live CD is fully functionnal (as far as HDD/CDROM are concerned).
Thanks

OSmeest

Thanks for the updates everyone. I'm marking this Fix Released for Intrepid per the last few comments. Thanks.