List Archive: gentoo-amd64
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
Okay, Got 3 Neo3 Platinum boxes on BIOS 1.B.
The two 64 bit Gentoo boxes are running clean with
2.6.9-r9 gentoo sources. One has the dual core
upgrade and its very very nice! Played with lots of
different kernels including gentoo-sources 2.6.14 and
vanilla-sources 2.6.14 on the single core box and they
all hang like the 2.6.12 and 2.6.13 kernels.
If I can find about 8 hours, I can probably isolate
the kernel code change(s) that causes the freeze on
this MBoard and float a patch into 2.6.14 and see if
some kernel guys can study it.
The third box is a windoze XP and it occasionally
needs the keyboard unplugged and replugged after the
BIOS starts. This looks like a hardware issue because
it happens with BIOS 1.3, 1.8 and 1.B and occurs far
before the bootloader gets going.
I'm off to Frys because the dual core box has a stuck
chipset fan. Might as well buy 3 replacements, one
for each board.
--- Nuitari <nuitari@...> wrote:
> > So, the old BIOS works with all versions of the
> > going back a year. The new BIOS doesn't work with
> > kernel 2.6.11 and 2.6.12.
> > Anyone familiar with the recent changes to libata
> > nv_sata drivers?
> No, but I know that there are fixes related to
> nv_sata in 2.6.14, so it
> might work again.
> "sata_nv: Fixed bug introduced by 0.08's MCP51 and
> MCP55 support"
> (the bug seems to have been introduced earlier in
> 2.6.14 development.
> "[PATCH] Add NVIDIA device ID in sata_nv"
> There is also a fix atapi_packet_task vs intr race
> (take 2) which is way
> too technical for me to understand before getting a
> good night of sleep.
> firstname.lastname@example.org mailing list
Yahoo! Mail - PC Magazine Editors' Choice 2005
email@example.com mailing list