Good call. I found it in the initrd.img file. So I removed that
module, saved, and it booted just fine with network. I am getting some
errors on the TX side according to ifconfig BUT everything appears to be
working fine on this box. The stats below are lying as the network
interface is sending and receiving (did 1 byte pings for a couple
seconds) and it but no traffic is being logged. I assume this is a
driver issue and not really anything to do with the hardware but if you
have any ideas of how to fix or if it's even important, please let me
know.
Anyway, it's working now so I'll start to play with the machines.
Thanks for the help and I'm sure that I'll ask for more later
debian:~# ifconfig
eth1 Link encap:Ethernet HWaddr 00:03:BA:0C:38:D5
inet addr:10.0.16.113 Bcast:10.0.16.255 Mask:255.255.255.0
inet6 addr: fe80::203:baff:fe0c:38d5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:164 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:112 dropped:0 overruns:0 carrier:112
collisions:0 txqueuelen:1000
RX bytes:61864 (60.4 KiB) TX bytes:0 (0.0 b)
Interrupt:9
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
> -Original Message-
> From: Richard Mortimer [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 02, 2008 4:07 PM
> To: Gary W. Smith
> Cc: Steve Haavik; Martin Habets; debian-sparc@lists.debian.org
> Subject: RE: Netra X1 install problem/oddity
>
> Hello,
>
> I'm working from memory here but I vaguely remember having a similar
> problem some time ago. I seem to remember that the kernel module and
> blacklist files are built into the initrd/initramfs files. I think
that
> you need to regenerate that to get the changes to work during boot.
>
> I cannot easily get access to my X1 at the moment so I cannot check
> myself - sorry.
>
> Richard
>
> On Mon, 2008-06-02 at 07:53 -0700, Gary W. Smith wrote:
> > Steve,
> >
> > Thanks for the follow up on this. I did the echo trick but it still
> > didn't work. I also did remove dmfe.ko and then issue depmod -a to
> > rebuild the catalog but it still loads the module. It seems like
> this
> > module is in the kernel or something. Anyway, I'll play around with
> > it a little more. In a worse case scenario, I'll script something
on
> > startup.
> >
> > Gary
> >
> >
> >
> __
> > From: Steve Haavik [mailto:[EMAIL PROTECTED]
> > Sent: Mon 6/2/2008 4:25 AM
> > To: Gary W. Smith
> > Cc: Martin Habets; debian-sparc@lists.debian.org
> > Subject: RE: Netra X1 install problem/oddity
> >
> >
> > I've still got a few Netra X1's running.
> > From my notes:
> >
> > First thing after booting the tftpimage jump to a shell and:
> >
> > modprobe -r dmfe
> > modprobe -r tulip
> > modprobe tulip
> >
> > Then you can continue the install.
> >
> > After it reboots to the new system:
> >
> > echo 'blacklist dmfe' > /etc/modprobe.d/dmfe-blacklist
> >
> > If all else fails you could track down and delete dmfe.ko but you'd
> > have
> > to remember to do that after every kernel upgrade. The above method
> > worked
> > fine on my production boxes.
> >
> >
> >
> --
> Richard Mortimer <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]