AHCI IDENTIFY problem only on x86_64

AHCI IDENTIFY problem only on x86_64

[Maarten Vanraes]

I would like to be CC'ed as i'm not on the list.

kernel 2.16.17.13: in 32bit the disk is detected everything ok, in
x86_64, it gives a Failed to IDENTIFY for both drives, it does not
give a FAILED to IDENTIFY on the ones where the link is down.

any idea what the problem is?

tia,
-- 
Alien is my name and head-biting is my game

Re: AHCI IDENTIFY problem only on x86_64

[Jeff Garzik]

Maarten Vanraes wrote:
> I would like to be CC'ed as i'm not on the list.
> 
> kernel 2.16.17.13: in 32bit the disk is detected everything ok, in
> x86_64, it gives a Failed to IDENTIFY for both drives, it does not
> give a FAILED to IDENTIFY on the ones where the link is down.
> 
> any idea what the problem is?

May we presume that 2.6.20-rc4 works?

	Jeff

Re: AHCI IDENTIFY problem only on x86_64

[Maarten Vanraes]

i don't think so, but i cannot test it... i don't have an x86_64
system, and i cannot install on my disk, cause it's not detected.
unless i can install an x86_64 kernel on a i586 system, i donno how to
further test this.

2007/1/9, Jeff Garzik <jeff@garzik.org>:
> Maarten Vanraes wrote:
> > I would like to be CC'ed as i'm not on the list.
> >
> > kernel 2.16.17.13: in 32bit the disk is detected everything ok, in
> > x86_64, it gives a Failed to IDENTIFY for both drives, it does not
> > give a FAILED to IDENTIFY on the ones where the link is down.
> >
> > any idea what the problem is?
>
> May we presume that 2.6.20-rc4 works?
>
>         Jeff
>
>
>
>


-- 
Alien is my name and head-biting is my game

Re: AHCI IDENTIFY problem only on x86_64

[Jeff Garzik]

Maarten Vanraes wrote:
> i don't think so, but i cannot test it... i don't have an x86_64
> system, and i cannot install on my disk, cause it's not detected.
> unless i can install an x86_64 kernel on a i586 system, i donno how to
> further test this.

If you are stopped at the initial install, just grab a distro that 
already works on this hardware, like Fedora Core 6 (x86-64).

	Jeff

Re: AHCI IDENTIFY problem only on x86_64

[Maarten Vanraes]

so, the problem is already solved then? at what minimal kernel version
was that problem solved?

i didn't see it in the changelogs, but i may not have seen them all...

If i know the version, i can submit the info to them...

2007/1/9, Jeff Garzik <jeff@garzik.org>:
> Maarten Vanraes wrote:
> > i don't think so, but i cannot test it... i don't have an x86_64
> > system, and i cannot install on my disk, cause it's not detected.
> > unless i can install an x86_64 kernel on a i586 system, i donno how to
> > further test this.
>
> If you are stopped at the initial install, just grab a distro that
> already works on this hardware, like Fedora Core 6 (x86-64).
>
>         Jeff
>
>
>
>


-- 
Alien is my name and head-biting is my game

Re: AHCI IDENTIFY problem only on x86_64

[Jeff Garzik]

Maarten Vanraes wrote:
> so, the problem is already solved then? at what minimal kernel version
> was that problem solved?
> 
> i didn't see it in the changelogs, but i may not have seen them all...
> 
> If i know the version, i can submit the info to them...

The SATA drivers have seen /hundreds/ of changes since your kernel was 
released, and the problem you describe is a symptom of /multiple/ 
problems that were fixed in the following kernels.

It's unfortunately your task, and the task of the 2.6.16.* maintainer, 
to track this down further if you care.  Most developers concentrate on 
the current kernel, otherwise we wind up fixing the same bugs over and 
over again.

That's what distros pay people to do, care about older kernels...

	Jeff

Re: AHCI IDENTIFY problem only on x86_64

[Maarten Vanraes]

ok, fine, but it is fixed, you are sure?

i'll mention it to the people then.

thanks

2007/1/9, Jeff Garzik <jeff@garzik.org>:
> Maarten Vanraes wrote:
> > so, the problem is already solved then? at what minimal kernel version
> > was that problem solved?
> >
> > i didn't see it in the changelogs, but i may not have seen them all...
> >
> > If i know the version, i can submit the info to them...
>
> The SATA drivers have seen /hundreds/ of changes since your kernel was
> released, and the problem you describe is a symptom of /multiple/
> problems that were fixed in the following kernels.
>
> It's unfortunately your task, and the task of the 2.6.16.* maintainer,
> to track this down further if you care.  Most developers concentrate on
> the current kernel, otherwise we wind up fixing the same bugs over and
> over again.
>
> That's what distros pay people to do, care about older kernels...
>
>         Jeff
>
>
>
>


-- 
Alien is my name and head-biting is my game