Bug#59256: Inappropriate LAN configuration
At 05:54 PM 3/1/00 -0800, Karl M. Hegbloom wrote:
>>>>>> "Ross" == Ross Boylan <RossBoylan@stanfordalumni.org> writes:
>
> Ross> Package: boot-floppies
> Ross> Version: 2.2.7
>
> Ross> Though my only network connection is via modem, the installation
routines
> Ross> force me into an LAN/ethernet-oriented configuration. I do have an
> Ross> ethernet card in my system, and I suspect that is partly behind the
> Ross> problem. But the setup shouldn't force an ethernet config on a
system
> Ross> which lacks an ethernet connection (there is no cable in the
card) Should
> Ross> it?.
>
> Ross> At any rate, when I finish driver selection, I never get asked
"Is your
> Ross> system connected to a network?" Instead a dialog comes up (it
says it's
> Ross> "automatic" and refers to eth0) asking about DHCP, and it
continues on from
> Ross> there with a bunch of LAN type queries.
>
> It ought to have a look and see if any network interfaces exist. If
> several do, then it ought to offer a menu of them to configure, and
> allow you to configure more than one if you like. When you configure
> one that's already been configured, it ought to use the previous
> settings as defaults.
I didn't know this was checking drivers; I thought it was strictly user
driven. So maybe the problem is simple: ppp wouldn't load, so I get the
LAN queries? But I think ppp did load with earlier boot floppies (2.2.6?)
and I still had this problem.
>
> Ross> For completeness, here was my driver selection at earlier
stages, in the
> Ross> order I loaded them:
> Ross> nfs -- failed with warnings about unresolved symbols in (from?)
sunrpc.o
>
> I've seen similar problems. There's a text file in
> /lib/modules/$(uname -r)/pcmcia that causes the `depmod -a' to fail.
> That's what makes it print the can't read ELF header message. It
> doesn't finish generating the "modules.dep" file, so `modprobe' can't
> know what prerequisite modules need to be loaded with the one you
> choose, thus there are unresolved symbols, and it fails.
>
> Ross> ntfs, vfat, awe_wave--all fine
>
> Ok, and all without any arguments to the module? Am I right?
Yes, no arguments to anything. I haven't a clue what they'd be.
>
> Ross> joy_creative -- failed. Could be my hardware, or a conflict
with awe_wave
>
> Did you pass arguments to the `modprobe' (via the interface)? If you
Still no args.
> switch to vt2, `rm /lib/modules/$(uname -r)/pcmcia/.*', `depmod -a',
> then switch back to the `modconf' and try again, does it work? If
> not, does it work if you switch back to vt2 and `modprobe
> joy_creative ARGS' by hand? Please report on this if you can.
>
No time right now.
> Ross> ppp--fails. Many unresolved symbols
/lib/module/2.2.14/net/ppp.o. This is
> Ross> critical for me. (not the subject of this bug report)
>
> I think this is the `depmod -a' failing again.
>
> Yesterday I noticed that `modconf' does not seem to be passing the
> module arguments to the `modprobe' it ostensibly runs. I have not
> reported a bug on it yet, nor have I examined the code. This needs
> to be done if there's not already one for it in BTS. RC!
>
Reply to: