log in | register | forums
Show:
Go:
Forums
Username:

Password:

User accounts
Register new account
Forgot password
Forum stats
List of members
Search the forums

Advanced search
Recent discussions
- R-Comp releases Genealogy v2 (News:)
- Will we see 5.30 released at Wakefield show? (News:1)
- Sine Nomine updates RiscOSM and Impact (News:)
- Netfetch version 5.55 released (News:)
- Prizes for Wakefield Show announced (News:)
- Heretic update from R-Comp (News:)
- Wakefield Show 2024 is next Saturday (News:)
- Git client updated to 0.07 (News:2)
- Archive Edition 27:1 reviewed (News:)
- Rougol April 2024 meeting on monday is Anniversary time (News:1)
Latest postings RSS Feeds
RSS 2.0 | 1.0 | 0.9
Atom 0.3
Misc RDF | CDF
 
View on Mastodon
@www.iconbar.com@rss-parrot.net
Site Search
 
Article archives
The Icon Bar: General: Iyonic motherboard NIC refuses to come up
 
  Iyonic motherboard NIC refuses to come up
  sirbod (10:52 8/9/2013)
  krisa (17:52 9/9/2013)
    sirbod (18:08 9/9/2013)
  ksattic (19:50 10/9/2013)
    sirbod (16:20 11/9/2013)
 
Jon Abbott Message #122646, posted by sirbod at 10:52, 8/9/2013
Member
Posts: 563
This seems to be a common issue from doing a Google search, but I've not found any solutions.

The onboard Intel Pro/1000 is visible in pcidevices and ekinfo list is as ek0 and it appears to be initialised.

ifconfig ek0 up does nothing and there's no link or negotiation with the switch.

ektest reports passed, except for Link test, which obviously reports NO link.

It looks very much like a software issue to me, I know from my network design days that Intel cards can fail in this way if they're configured to use Flow control. After some digging I found that Flow control is forced on by default and is controlled via the EKFlowControl config entry, however *Configure EKFlowControl 0 none reports a syntax error, in fact any setting reports a syntax error so that looks like a bug in EtherK (this issue exists in both RO5.16 and RO5.20)

Anyone know how to change the flow control in the CMOS - I'm guessing that's where it's stored?

[Edited by sirbod at 10:53, 8/9/2013]
  ^[ Log in to reply ]
 
Kris Adcock Message #122648, posted by krisa at 17:52, 9/9/2013, in reply to message #122646
Member
Posts: 62
How old is the PSU? The voltage deteriorates over time, and some mobo components are more sensitive to it than others.

A quick test of the +5v and +12v rails with a multimeter might be in order ... or a swapout, if you happen to have a spare PSU knocking about.
  ^[ Log in to reply ]
 
Jon Abbott Message #122649, posted by sirbod at 18:08, 9/9/2013, in reply to message #122648
Member
Posts: 563
Both within 3%. The PSU doesn't show the tolerances, so I'm not certain if 3% is acceptable. There's no manufacture date on it either.

I did try swapping the PSU over this morning, unfortunately all my PSU's are PC ones that need pin 14 grounding to power on. Without seeing a schematic I didn't want to risk grounding it when plugged into the motherboard.

[Edited by sirbod at 18:10, 9/9/2013]
  ^[ Log in to reply ]
 
Simon Wilson Message #122650, posted by ksattic at 19:50, 10/9/2013, in reply to message #122646
ksattic
Finally, an avatar!

Posts: 1291
A number of people have had this problem with their Iyonix and in some cases it was the power supply. In one case, a simple *rmreinit etherk after boot would kick it back into life. Does that help?

I seem to remember that I had a problem with this many years ago and I sent away my motherboard to have a new ethernet controller soldered on.
  ^[ Log in to reply ]
 
Jon Abbott Message #122653, posted by sirbod at 16:20, 11/9/2013, in reply to message #122650
Member
Posts: 563
No, RMReInit does nothing.

I believe the onboard NIC is faulty so I'll order another - they're less than £5.
  ^[ Log in to reply ]
 

The Icon Bar: General: Iyonic motherboard NIC refuses to come up