Rachel Collins wrote in part:
>
> I haven't received any replies to my request for assistance, so I tried
> taking the NIC out, waving a dead chicken over it, and clicking my heels
> together three times while chanting "There's no OS like Linux", but it just
> locked my computer... Should I maybe have tried a live chicken?
>
> I'm a newbie, so ANY advise on this problem is VERY VERY much appreciated...
>
> On Wednesday, September 20, 2000 Rachel Collins begged for help thusly:
> # I recently purchased a Sony PCG-SR7K Laptop and a D-Link
> # DFE-650 Network
> # card. I've managed to get all the basic stuff working, with
> # the exception of
> # the network card. Can anyone point me to the right how-to or offer a
> # suggestion? Details are as follows:
> #
> #
> # System:
> # Laptop: Sony PCG-SR7K
> # Network card: D-Link DFE-650
> # Linux kernel version: 2.2.16-3
> # Redhat version: 6.2
> #
> #
> # Questions:
> # --I don't have anything in my /etc/conf.modules file about my
> # ethernet card.
> # Should I?
I have always found it necessary to have a statement 'alias eth0
driver_name' in conf.modules. However I've never tried with a laptop
before either. If you alter conf.modules be sure to 'depmod -a' when
you're done.
> # --The network dongle (you know, the adapter thingie that
> # connects the card
> # to the network cable) has three lights on it (10/100,
> # Half/Full, Ln/Act).
> # When I plug into a 10 Mb hub, the appropriate lights come on
> # (still doesn't
> # work), but when I plug into a 100 Mb hub, they all just flash. Is it
> # possible that it is failing because it can't detect whether
> # the card is 10
> # or 100?
Token ring will do this but this would be the first time I've ever heard
of an ethernet card failing to start cuz it wasn't plugged in right or
something.
> # --I don't think protocol is my problem, but I noticed in the
> # course of my
> # travels that there's an IPv6, and I appear to have IPv4.
> # Should I get the
> # newer version?
> #
IPV4 is the current version of the IP addressing scheme currently in
use. IPV6 is the new standard in consideration but not in common use
yet.
> #
> # 'ifconfig' only shows the local loopback, but 'ifconfig eth0' shows:
> # eth0 Link encap:Ethernet HWaddr 00:50:BA:73:89:A7
> # BROADCAST MTU:1500 Metric:1
> # RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> # TX packets:0 errors:2 dropped:0 overruns:0 carrier:0
> # collisions:0 txqueuelen:100
> # Interrupt:10 Base address:0x300
> #
You _do_ have an /etc/sysconfig/network-scripts/ifcfg-eth0 file don't
you. Make sure 'NETWORKING=yes' is in /etc/sysconfig/network too.
Seems unlikely these would be a problem but it's something you can look
for.
> #
> # Everything that sounds network related in my /var/logs/messages file
> # (hopefully without too much other stuff mixed in):
> #
> # sysctl: net.ipv4.ip_forward = 0
> # sysctl: net.ipv4.conf.all.rp_filter = 1
> # sysctl: net.ipv4.ip_always_defrag = 0
> # sysctl: kernel.sysrq = 0
> # network: Setting network parameters succeeded
> # network: Bringing up interface lo succeeded
> # ifup: Delaying eth0 initialization.
> # network: Bringing up interface eth0 failed
> #
> # more other stuff...
> #
> # pcmcia: Starting PCMCIA services:
> # pcmcia: modules
> # kernel: Linux PCMCIA Card Services 3.1.8
> # kernel: kernel build: 2.2.16-3 #1 Mon Jun 19 19:11:44 EDT 2000
> # kernel: options: [pci] [cardbus] [apm]
> # kernel: Intel PCIC probe:
> # kernel: Ricoh RL5C475 PCI-to-CardBus at bus 0 slot 12, mem
> # 0x68000000, 1
> # socket
> # kernel: host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1]
> # [no pci irq]
> # [lat 168/176] [bus 32/34]
> # kernel: ISA irqs (default) = 3,4,5,7,10,11,12,15 polling
> # interval = 1000
> # ms
> # pcmcia: cardmgr.
> # rc: Starting pcmcia succeeded
> # cardmgr[479]: starting, version is 3.1.8
> # inetd: inetd startup succeeded
> # cardmgr[479]: watching 1 sockets
> # kernel: cs: IO port probe 0x1000-0x17ff: excluding 0x1040-0x104f
> # kernel: cs: IO port probe 0x0100-0x04ff: excluding
> # 0x170-0x177 0x330-0x337
> # 0x370-0x377 0x4d0-0x4d7
> # kernel: cs: IO port probe 0x0a00-0x0aff: clean.
> # cardmgr[479]: initializing socket 0
> # kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
> # cardmgr[479]: socket 0: D-Link DFE-650 Ethernet
> # cardmgr[479]: executing: 'insmod /lib/modules/2.2.16-3/net/8390.o'
> # cardmgr[479]: executing: 'insmod
> # /lib/modules/2.2.16-3/pcmcia/pcnet_cs.o
> # irq_list=10'
> # kernel: eth0: NE2000 Compatible: io 0x300, irq 10, hw_addr
> # 00:50:BA:73:89:A7
> # cardmgr[479]: executing: './network start eth0'
I see there appears to be a line here to start eth0 but I still wonder
if the problem might be related to when card services are started
compared to when the system originally tries to start eth0 above. I'm
not sure, but you might be able to adjust this with the scripts in
/etc/rc.d/rc5.d. The lower the number the sooner it's started. S10
starts sooner than S20 and K10 kills sooner than K20 etc. If you're
starting in console mode as opposed to X you'll want to adjust rc3.d
instead of rc5.d.
Not sure if any of this will help but it's my attempt :-).
Good Luck.
--
Mike Rambo
[EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
