Bug 136953
Summary: | Fedora does not create HomePNA connection | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan-Petter Vainionpaa <javainio> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | barryn, javainio, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-10-27 15:37:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jan-Petter Vainionpaa
2004-10-23 22:13:08 UTC
Same problem occures with a new installation of Fedora Core 3 test 3, AMD PCNet HomePNA adapter is recognized correctly, but network connection fails. I just get the same notification as with Fedora Core 2, that is "Link is down, check the cable". I have a dual boot configuration on the machine, and the card works ok in windows XP. So far, only new installation of Fedora Core 2 without any updates worked correctly. Assuming the card is eth0, try adding either of these lines: options eth0 homepna=1 options pcnet32 homepna=1 to your /etc/modprobe.conf. (I would then run "depmod -a" and reboot. Maybe a "depmod -a; /etc/init.d/network restart" or a reboot alone would suffice, however.) Then see if you still have the problem. On an unrelated note, in the future please write (for example) "bug 111178", not "ID 111178", for bugs within this Bugzilla database. That way, Bugzilla can automatically turn it into a clickable link like the one in the previous sentence. Thanks! BTW, some more info on why this is happening: Previously, the connection to use on these cards (HomePNA or Ethernet) had to be selected at compile time by changing the pcnet32.c source code file. Recently, the driver was changed so that the type of connection could be specified using a kernel configuration option (so that, like any other Linux Ethernet driver, you could change the configuration without having to edit the source code). Finally, the driver was improved again, so that you can now choose at module load time rather than having to recompile the kernel. Hi Barry, I'm sorry for my answer being late, but I wasn't able to do the test before today. Your suggestition worked fine, many thanks for that!! I just added the options -line (options eth0 homepna=1) under the alias definition of eth0 and after updating module dependencies and booting the machine network worked just fine. This was clearly not a bug, and I should have looked the documentation of the driver before making bug report, I apologize of causing extra work to you all. br. JP |