On Friday, September 22, 2000 Mike Rambo wrote:
#
# Rachel Collins wrote in part:
# >
# > # --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.
I added 'alias eth0 pcnet_cs' to my conf.modules file, but it didn't seem to
have any affect.
# > # --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.
Do you know of any way to set the negotiation manually so that it forces it
to start at 10 or 100, or at full or half duplex? The computer is dual
booting to Win2k so I know the card is functional, and I can't find any
utilities on the driver disk that appear useful.
# > # '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.
Yes, I have that file and 'NETWORKING=yes'. I also tried setting my IP
manually (to a generic 192.168.0.50) and it behaves like it's starting ok
now, but my lights are still flashing and I, of course, still can't access
anything outside of my pc (although I can ping my pc). It also still says
'trigger_send() called with the transmitter busy' and 'found link beat' and
'lost link beat' whenever I try to ping something.
# > # 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.
#
I tried changing S45pcmcia to S09pcmcia so that it would start first - it
made it think a lot harder about initializing the card, and it now
consistently says 'lost link beat' right after 'found link beat', but no
other changes. What does 'found/lost link beat' mean? What does
'trigger_send() called with the transmitter busy' mean?
Is there another card you'd recommend I buy? ;)
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
