v210 installation [was Re: tg3 driver fails]
- To: email@example.com
- Cc: firstname.lastname@example.org
- Subject: v210 installation [was Re: tg3 driver fails]
- From: Dave Love <email@example.com>
- Date: Wed, 06 Jul 2005 18:02:40 +0100
- Message-id: <rzqr7eb3m1b.fsf_-_@loveshack>
- In-reply-to: <Pine.LNX.4.61.0507061051020.2607@bobcat> (Jurij Smakov's message of "Wed, 6 Jul 2005 11:09:55 -0400 (EDT)")
- References: <rzq1x6c3tc4.fsf@loveshack> <Pine.LNX.4.61.0507061051020.2607@bobcat>
Jurij Smakov <firstname.lastname@example.org> writes:
> Yes, this is a known problem.
Is there any possibility of documenting it, then? I think it would be
better to leave the driver out rather than (on a 2.6 kernel) appear to
have set it up and leave you wondering what's wrong with the network.
> I am afraid that the only feasible solution for Sarge kernels is to
> rebuild your kernel (or, at least, the tg3 module) using the
> pristine kernel source from kernel.org.
If I did that, how would I install it? Anyway, is there any
indication it will work in view of the below?
Meanwhile, I've found a card with an hme interface and done an install
with that. On the reboot after the initial install on a disk with
Solaris on for dual boot, it boots Solaris, not silo, which then
reports that the disk label is screwed.
Starting again with a freshly-partitioned disk, sigh, the reboot fails
VFS: Disk quotas vdquot_6.5.1
Fatal Error Reset
CPU 0000.0000.0000.0000 AFSR 0210.9000.0000.0000 JETO PRIV OM TO
With either a 2.4 or 2.6 kernel.
It looks about time to give up on this.