Bug 49842
| Summary: | pcmcia network interface doesn't start | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Chris Ricker <chris.ricker> |
| Component: | initscripts | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.3 | CC: | 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: | 2001-08-06 19:01:28 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
Chris Ricker
2001-07-24 15:08:46 UTC
Please see the twenty-five other times this has been reported. PCMCIA cardbus interfaces should be set up as ONBOOT=no. This causes no messages to be sent. They will then be brought up by the PCMCIA package. See bug # 49779 Either init scripts need to be re-ordered, or the text installer needs to be fixed to correctly configure pcmcia devices. ONBOOT=no I'm *still* getting lots of spewage, kudzu complaining, etc. The other issue, of course, is that I actually *do* want my NIC enabled at boot. If I use ONBOOT=no, I get error messages and no NIC enabled (I have to manually run ifup eth0 to get the DHCP lease). If I use ONBOOT=yes, I get error messages. This is regression from 7.1, in which I had error-less DHCP configuration of my CardBus NIC at boot-time. Still true with beta 3, still major regression from 7.1 the script ordering is irrelevant. something else is wrong. Remove the check_link_down call from ifup (or install 6.11-1) - does that help? Ignore the re-ordering suggestion; it was just my stab in the dark at an attempt to fix the problem. Here's what I see with stock beta3: ONBOOT=yes: kudzu yells during boot, card is initialized but doesn't get a dhcp lease ONBOOT=no: kudzu yells during boot, card is initialized but doesn't get a dhcp lease with the if check_link_down block commented out and beta 3: ONBOOT=yes: kudzu yells during boot, card gets a dhcp lease automatically ONBOOT=no: kudzu yells during boot, card gets a dhcp lease automatically So, basically ONBOOT= seems to be ignored. kudzu always complains (because it's trying to load tulip.o before loading cardbus support?), and automatic configuration of the card on bootup is broken with the stock ifup script. I'm going to now blow away the card entirely and see if it'll then work when I reconfigure it. Okay, latest results. I removed the card entirely from the kudzu database. After that, with the stock beta3 ifup, I get no automatic dhcp lease on the card on bootup. With the modified ifup, I get ONBOOT=yes: error message after configuring lo0, but then card gets dhcp lease automatically anyway ONBOOT=no: no error messages, card automatically gets an IP lease. So, it looks like with the new ifup, ONBOOT=no will do the right thing. One bug still exists, however. A bogus entry is being created in the kudzu database during install (pcmcia devices get dumped into kudzu by anaconda, I guess, but shouldn't be there because kudzu gets run before pcmcia support gets loaded). I'm not sure if that's a bug in kudzu, init scripts, or anaconda.... kudzu message squashed in 0.99.12-1. That's been broken for way too long. :( Other stuff should be taken care of with initscripts-6.12-1. |