LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 07-30-2007, 05:57 AM   #16
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198

ondipuli: thanks for trying to help ... however, you need to take more care about your posts. As it is a helpful (hopefully) post you want users to be able to read it easily - leaving little room for misunderstandings.

You have given numbered solutions, but it is unclear if you intend this to be a series of steps or a selection of different things to try. You have used frowned-upon abbreviations and you need to revise punctuation (the space goes after the comma/period, not before). Try to leave an empty line between paragraphs and give examples. Remember - these issues are confusing, so the response needs to be the opposite to be effective.

Otherwise: a solid summary of the standard approaches to the problem. Well done. I'll just see if I cannot tidy it up a bit in case some future answer-seeker needs a hand.

1.load the correct module with modprobe cmd

modprobe r8169

You can check the driver needed by examining the hardware specs in system > preferences > hardware information (news to me - how is this achieved? Or is this another KDE thing?)

r8169 is in the kernel tree.
If the information about the module in blank or says "unknown module" then you need to install the correct driver. So let us know.
(This event usually generates an entry in syslog - which is why I wanted that dmesg search).

2. Check to see that the module is loaded:

lsmod | grep r8169

(Remember that it may be a different module you need.)
If this is present and the issue remains, then you may have an irq conflict. You can check the irq ports with

lspci -v
(show us)

You can work around this by editing the modprobe.conf file as root:

# gedit /etc/modprobe.conf

alias eth0 r8169
options irq=<irq from lspci -v>


(The options line is just for good measure)

Then: ifup eth0, then ifconfig

(I would be surprised if this works as it requires eth0 to be assigned already - but I've been surprised before.)

To this I'd add my own:

3. You ethernet card may be asleep as a feature of the bios acpi - try adding "noacpi" to the kernel line in /boot/grub/grub.conf "irqpoll" or "noirqpoll" as well, can help irq conflicts.

4. If this in a PCI card rather than a builtin - you may just need to reseat the card (pull it out, plug it back - gently but firmly). Of course, you may have a fake card - these will pretend to be realtech but are net and use special software (only for windows) to cover up the difference.
 
Old 07-30-2007, 06:18 AM   #17
Peter John
LQ Newbie
 
Registered: Jan 2007
Posts: 29

Original Poster
Rep: Reputation: 15
Done, the module is r8169.ko present in the kernel.
I did changes in modules.conf and restarted the module with modprobe.
Then an ifup eth0 states "r8169 device does not seem to be present , delaying initialisation". Found some patches on web need to try them.

Thanks
John
 
Old 07-30-2007, 10:02 AM   #18
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198
"01:07.0 Ehternet Controller" (post #1)
... that lspci entry looks funny: is this a copy and paste or did you type it out by hand?

Verify the card is not broken.
Tell me if the card is built-in or pluggable PCI.
Gnome or KDE?


as root:

# gedit /boot/grub/grub.conf

add "noacpi noapic nolapic" to the kernel line. reboot.

Lets see that lspci -vv (the complete entry)
 
Old 07-31-2007, 12:41 AM   #19
Peter John
LQ Newbie
 
Registered: Jan 2007
Posts: 29

Original Poster
Rep: Reputation: 15
That was written by hand, since there was no network for the machine. We have four systems all of which are genuine HP from a HP Dealer, which has this in-built ethernet Adapter. All these four system are installed with Fedora core 6 and fail to recognise these cards. Tried adding these lines to grub.conf but no luck. Am using GNOME. Interestingly there is no entry in /proc/interrupts.

lspci -vv
=========
01:07.0 Ethernet Controller: Realtek Semiconductor Co., Ltd. RTL8169SC Gigabit Ethernet (rev 10)
Subsystem: Hewlett-Packard Company Unknown Device 3023
Control: I/O+ Mem+ BusMaster+ SpecCycle - MemINV - VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz+ UDF FastB2B+ ParErr- DEVSEL=medium >TAbort- <MAbort- >SERR- <PERR-
Latency: 32(8000ns min, 16000ns max) Cache Line Size: 64 Bytes
Interrupt: pin A routed to IRQ 10
Region 0: I/O Ports at ee00 [size=256]
Region 1: Memory at fdcff000 (32-Bit, non-prefetchable] [size=256]

Rest may be irrelavent

Thanks
John
 
Old 07-31-2007, 04:06 AM   #20
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198
I've asked around and got a suggestion: try the previous suggestions but with the following drivers:

skge
sklin98

<reads previous post>
good ... as this was a package, does the package have a brand name? How about the Mobo? (If others have had trouble with the mobo or box, I can find out that way.)

But here's another suggestion - go into bios and see what the irq table is like - see if you can reassign the nic to irq 19. (Just a hunch).
 
Old 07-31-2007, 04:50 AM   #21
Peter John
LQ Newbie
 
Registered: Jan 2007
Posts: 29

Original Poster
Rep: Reputation: 15
Hi ALL,

I have downloaded the latest driver sources, and build them using kernel source tree. The problems have been solved. ( Though i could not identify the exact patch for this )

Thanks for your valuable time and suggestions.

John
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem with ethernet card [Marvel Yukon Ethernet controller] in Fedora 4 me4linux Linux - Hardware 3 03-28-2007 03:39 PM
SuSE not auto-recognising ethernet adaptor at boot VimFuego SUSE / openSUSE 3 08-27-2006 01:39 AM
Games not recognising 3D card duncnz SUSE / openSUSE 9 08-10-2006 07:56 PM
Ethernet card on laptop: I installed my D-Link ethernet card into Redhat 9, not detec brighamr Linux - Hardware 0 05-18-2004 01:33 AM
Not Recognising Wireless pci card MattLaw Linux - Hardware 0 09-03-2003 05:03 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 12:40 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration