Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
11-26-2005, 10:18 AM
|
#1
|
LQ Newbie
Registered: Nov 2005
Posts: 14
Rep:
|
eth1 problem
hi
I have fedora core 2 install on my system. my internet connection i working fine on eth0. i add one more network card on this system but when try to activate this new card (i. e. eth1) i get error "rtl8129 device eth1 does not seem to be present, delaying initialization." can any body provide help
|
|
|
11-26-2005, 10:30 AM
|
#2
|
LQ Newbie
Registered: Nov 2005
Distribution: Slackware v10.2 (kernel 2.4.31)
Posts: 3
Rep:
|
Check to see if the device is listed on the computer. Linux has a device directory, called /dev. There are some steps to take. First, you can either enter:
ls -a /dev/et*
which should list all of them (the network ethernet devices (that's why there is 'eth')), or you can search specific:
ls -a /dev | egrep '/dev/eth1'
because you are looking to see if it is on your computer. I suspect that the device is no longer, or just not, on your computer. I am sorry I can not be of more help right now.
|
|
|
11-26-2005, 11:11 AM
|
#3
|
LQ Newbie
Registered: Nov 2005
Posts: 14
Original Poster
Rep:
|
hi Clwhite0
thanks for the reply, i have very strange news, my internet connection is working fine on eth0 as i mention early, this means that eth0 is working fine still when i give
----------------
[root@localhost dev]# ls -a /dev/et*
ls: /dev/et*: No such file or directory
--------
i dont know what is the problem
again when i give
---------
[root@localhost dev]# ls -a /dev/e*
/dev/egp /dev/enskip
-------------------
what is means ?
|
|
|
11-26-2005, 11:18 AM
|
#4
|
LQ Newbie
Registered: Nov 2005
Distribution: Slackware v10.2 (kernel 2.4.31)
Posts: 3
Rep:
|
At this point I am not sure what the matter is. I am sorry I could not be of more help.
|
|
|
11-26-2005, 01:52 PM
|
#5
|
LQ Newbie
Registered: Oct 2005
Location: Toronto
Distribution: Red Hat 8.0
Posts: 26
Rep:
|
could you please run:
lspci -v
and post the result here?
|
|
|
11-26-2005, 02:38 PM
|
#6
|
LQ Newbie
Registered: Nov 2005
Posts: 14
Original Poster
Rep:
|
hi wym
thanks for reply , u asked me for lspci -v output. pls see if u can help
--------------------------------------------------
root@localhost root]# lspci -v
00:00.0 Host bridge: VIA Technologies, Inc. P4M266 Host Bridge
Subsystem: VIA Technologies, Inc.: Unknown device 0000
Flags: bus master, 66Mhz, medium devsel, latency 8
Memory at e0000000 (32-bit, prefetchable)
Capabilities: [a0] AGP version 2.0
Capabilities: [c0] Power Management version 2
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: dfd00000-dfefffff
Prefetchable memory behind bridge: cfb00000-dfbfffff
Capabilities: [80] Power Management version 2
00:09.0 Ethernet controller: Unknown device 1904:2031 (rev 01)
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at dfffff00 (32-bit, non-prefetchable) [size=dffc0000]
I/O ports at ec00 [size=256]
Expansion ROM at 00020000 [disabled]
Capabilities: [50] Power Management version 2
Capabilities: [60] Vital Product Data
00:0b.0 Modem: PCTel Inc HSP MicroModem 56 (rev 02) (prog-if 04 [Hayes/16750])
Subsystem: PCTel Inc PCT789 adapter
Flags: medium devsel, IRQ 5
I/O ports at e800
Capabilities: [40] Power Management version 2
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at dc00 [size=32]
Capabilities: [80] Power Management version 2
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at e000 [size=32]
Capabilities: [80] Power Management version 2
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at e400 [size=32]
Capabilities: [80] Power Management version 2
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
Subsystem: VIA Technologies, Inc. USB 2.0
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at dffffe00 (32-bit, non-prefetchable)
Capabilities: [80] Power Management version 2
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
Subsystem: VIA Technologies, Inc.: Unknown device 0000
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
Flags: bus master, medium devsel, latency 32, IRQ 255
I/O ports at fc00 [size=16]
Capabilities: [c0] Power Management version 2
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
Subsystem: VIA Technologies, Inc.: Unknown device 4161
Flags: medium devsel, IRQ 5
I/O ports at d800
Capabilities: [c0] Power Management version 2
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235 Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at d400
Memory at dffffd00 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2
01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266] (prog-if 00 [VGA])
Subsystem: S3 Inc. VT8375 [ProSavage8 KM266/KL266]
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 11
Memory at dfe80000 (32-bit, non-prefetchable) [size=dfe70000]
Memory at d0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at 00010000 [disabled]
Capabilities: [dc] Power Management version 2
Capabilities: [80] AGP version 2.0
|
|
|
11-26-2005, 07:38 PM
|
#7
|
LQ Newbie
Registered: Oct 2005
Location: Toronto
Distribution: Red Hat 8.0
Posts: 26
Rep:
|
Quote:
Originally posted by abhishekgedam
00:09.0 Ethernet controller: Unknown device 1904:2031 (rev 01)
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at dfffff00 (32-bit, non-prefetchable) [size=dffc0000]
I/O ports at ec00 [size=256]
Expansion ROM at 00020000 [disabled]
Capabilities: [50] Power Management version 2
Capabilities: [60] Vital Product Data
|
This is the card that can not be detected. It shows an impossible memory size. I'd say there is probably something wrong in the card.
My suggestion:
1. re-install the card, make sure it is pluged in well
2. go into BIOS setting, disable PNP
3. try insmod -f 8129.o, I assume 8129.o is the driver name, it could be another name
4. if all these don't work, replace the card
Good Luck!
|
|
|
All times are GMT -5. The time now is 12:21 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|