Olaf Hering wrote:
These drivers are not neccessary ready for non-i386.
Did you try 2.4.2? It has natsemi.o
Thanks, yes I will try this ultimately. But, call me stubborn, I'm still
attempting to get that card to work with 2.2.16. If Don Becker's driver
(a 40kB download) could save me the download of 2.4.2 (9.3MB)...
I've made progress... after pulling the Netgear FA311 card out of
its PCI slot and putting it back in. (Don't ask why.)
Now the hub's LED lights up, my Power Mac 7300 loads the natsemi
kernel module, and the card gets recognized as eth1 (in addition
to the built-in eth0). Also it gets recognized at bootup, after
changing a line in modules.conf to: alias eth1 natsemi
HOWEVER: While I can telnet, ftp and http into the box from my
iMac using eth0 (192.168.0.99), nothing happens if instead I use
eth1 (192.168.0.100).
See relevant info below. What am I doing wrong?
hysterion
==============
Boot messages:
(...)
Setting up network device eth0 done
Setting up network device eth1 done
Setting up routing (using /etc/route.conf) done
Starting RPC portmap daemon done
(...)
Starting service httpd done
(...)
Starting INET services (inetd) done
(...)
==============
$ dmesg
(...)
natsemi.c:v1.07 1/9/2001 Written by Donald Becker
http://www.scyld.com/network/natsemi.html
The PCI BIOS has not enabled the device at 0/104! Updating PCI
command 0004->0006.
eth1: NatSemi DP83815 at 0xc481e000, 00:02:e3:05:93:ed, IRQ 23.
eth1: Transceiver status 0x7869 advertising 0000.
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
eth1: no IPv6 routers present
eth1: no IPv6 routers present
eth0: no IPv6 routers present
eth0: no IPv6 routers present
==============
$ lspci -tv
-[00]-+-0b.0 Apple Computer Inc. Bandit PowerPC host bridge
+-0d.0 National Semiconductor Corporation: Unknown device 0020
\-10.0 Apple Computer Inc. Grand Central I/O
==============
$ lsmod
Module Size Used by
ipv6 121832 -1 (autoclean)
natsemi 11332 1 (autoclean)
pci-scan 3424 0 (autoclean) [natsemi]
memstat 1960 0 (unused)
==============
$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:05:02:A8:78:12
inet addr:192.168.0.99 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::5:2a8:7812/10 Scope:Link
inet6 addr: fe80::205:2ff:fea8:7812/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:48 dropped:0 overruns:0 carrier:96
collisions:0
eth1 Link encap:Ethernet HWaddr 00:02:E3:05:93:ED
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2:e305:93ed/10 Scope:Link
inet6 addr: fe80::202:e3ff:fe05:93ed/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:32 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
==============
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
loopback * 255.0.0.0 U 0 0 0 lo
==============
P.S.: If really I must upgrade to kernel 2.4.2
1) Will k_deflt-2.4.2-11.ppc.rpm contain all I need?
Looking at http://lxr.linux.no/source/Documentation/Changes?a=ppc#L38
("Current Minimal Requirements"), I guess not all 10 items are relevant
to me, but I'm worried about
o util-linux 2.10o (my SuSE 7.0 has 2.10m)
o modutils 2.4.2 (don't seem to have this)
o e2fsprogs 1.19 (I have 1.18)
2) If yes, will the following procedure be about right?
(I'm going by http://sdb.suse.de/en/sdb/html/ftpkernel.html and
http://sdb.suse.de/en/sdb/html/olh_ppc_64_kernel_update.html):
1. Download the package to your hard disk
2. Save your old kernel and if necessary also your old initrd.
cp /boot/vmlinux /boot/vmlinux.old
3. Install the new package by issuing the following command:
rpm -Uhv k_deflt.rpm
4. copy the kernel from Linux to the MacOS side:
o open a root shell with the command " su - "
o mount the MacOS partition with " hmount /dev/macospartitionN "
o copy the file /boot/vmlinux onto the Mac partition:
hcopy /boot/vmlinux :
o unmount the MacOS partition with " humount /dev/macospartitionN"
o Boot into MacOS and copy the file to the correct place, e.g.
your System folder. Make sure that you boot that new kernel,
it must be active in the BootX window.