[ltp] t42p ata_piix [SOLVED]

[Carlos Moffat]

On Fri, 2008-01-11 at 08:44 -0500, Carlos Moffat wrote:
> On Fri, 2008-01-11 at 11:35 -0200, Henrique de Moraes Holschuh wrote:
> > On Fri, 11 Jan 2008, Carlos Moffat wrote:
> > > On Fri, 2008-01-11 at 06:22 +0100, Joerg Platte wrote:
> > > > Am Donnerstag, 10. Januar 2008 schrieb Carlos Moffat:
> > > > 
> > > > > Argh. Ok. Thanks, I'll give it a try. Please let me know if you remember
> > > > > anything about this, as I've been trying this switch for a while now.
> > > > 
> > > > Does your dmesg log indicate that the ide chipset has been found? If yes, 
> > > > please post the message. Maybe there is still some IDE part active that 
> > > > occupies the hardware first.
> > > > 
> > > 
> > > I couldn't figure out how to save the dmesg output from the BusyBox
> > > shell, but using Ulrich's config I noticed this:
> > > 
> > > Uniform Multi-Platform E-IDE driver revision 7.00alpha2
> > > ide: assuming 33MHz system bus speed for PIO modes: override with
> > > idebus=xx
> > > 
> > > I need to check again with a kernel without the IDE stuff at all to see
> > > if this shows up.
> > 
> > It doesn't.  Get rid of CONFIG_IDE, you don't want it on any T4x with a new
> > enough (2.6.2x) kernel.
> > 
> 
> You're right, Henrique. Withouth CONFIG_IDE I don't get any of those
> messages, although I still get stuck in 'waiting for root filesystem' or
> something like that.
> 
> Damn.
> 

After everything else failed, I decided to get a vanilla kernel
(2.6.23.13) from kernel.org, used my old configuration (which hadn't
work at all with the 2.6.23-2 available in Debian Sid), and presto! it
worked.

I'm not sure if this is due to some patch applied to the debian kernel
or something that was fixed recently upstream. I could only find this in
recent changelogs in kernel.org, but not sure if it is related:

http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.23.y.git;a=commit;h=9ee303ef4e582f2f8b4f08e58ced6ba44debfb64

I should have probably said (I didn't think of mentioning it) that I put
a WD hard drive (250GB - WDC WD2500BEVE-00WZT0). This might have been
the problem.

Anyways, thanks everybody for your help. I'm sure I'll be back soon
enough.

Best Regards,
Carlos






> Carlos
>