Tulip PHY problems on c200 [WAS: tulip module...a500]
On 10/12/05, Grant Grundler <grundler@parisc-linux.org> wrote:
> On Tue, Oct 11, 2005 at 10:31:27PM -0500, David H. Barr wrote:
> > It -is- worth noting that the addin NIC won't come up off a hard
> > boot. I have to hardboot, login over ttyS0, and issue a soft
> > reboot.
>
> This is weird too. Which firmware version does this C200 have?
> The parisc-linux FAQ explains where to find newer revs.
Will make a firmware upgrade tomorrow's first job. If I brick one of
my machines, I can always work on the other one. Thanks for pointing out
what should have been obvious... I never thought to check the firmware.
> > > (c) built-in NIC should work fine. No idea what's going on here.
> > > I'm not aware of any code changes that might break this.
> >
> > Tried a fresh net install with -no- additional cards in (just the naked
> > c200 + drives) and I can of course get a basic system, but none of
> > the things mentioned so far in this thread can bring up the onboard tulip.
>
> Ok. I can't explain this. And TBH, I'm really not interested in chasing
> this on the 2.6.8.x kernel. If you can try either the 2.6.12 kernel
> in unstable or test 2.6.14-rc2-pa2 kernel from
> cvs.parisc-linux.org/download/linux-2.6
Fair enough. Just to make sure I've got the basic steps for switching
precompiled kernels correctly:
* add
deb http://cvs.parisc-linux.org/download/linux-2.6/autobuild/712_defconfig/ ./
to the end of "/etc/sources.list"
* issue "apt-get update" to synchronize apt-cache with new source
* issue "apt-get install palinux-712-defconfig-2.6.14-rc2-pa2"
* change "/etc/palo.conf" from:
"--commandline=2/vmlinux-2.6.8-2-32-smp"
to
"--commandline=2/vmlinux-2.6.12-pa2-712_defconfig"
* issue "palo" to apply changes made in palo.conf
* issue "reboot" to give it a whirl
Since both my kernel faults said something to the effect of
" IAOQ[0]: lasi700_probe+0x190/0x1d0
IAOQ[1]: lasi700_probe+0x194/0x1d0
RP(r2): lasi700_probe+0x58/0x1d0
Kernel panic - not syncing: Kernel Fault"
I'm guessing there must be more to it than just switching out the kernel; that
must be the "Adjust for the configuration(s) you use" step, right? <grin>
If it's going to require complete kernel rebuilds on my part, I think I'll
stick with a firmware upgrade and live with two boots (one cold, one warm)
to bring up that addin NIC, at least until I've whetted my skills a bit more.
Sorry to bother with this basic question stuff. I =am= slowly working through
the Kernel Rebuild HOWTO on TLDP. If only they'd had a couple of SUNs or
ALPHAs at that University auction instead of these HPPAs, I'd be someone
else's problem child <grin>
Thanks again,
-dhbarr.
Reply to: