--- "David A. Bandel" <[EMAIL PROTECTED]> wrote: > On Thu, 7 Mar 2002 18:38:11 -0800 (PST) > begin Net Llama <[EMAIL PROTECTED]> spewed forth: > > I just built 2.4.18 on a HP Omnibook XE2 laptop running Redhat-7.2. > > Everything is working perfectly using the Redhat supplied kernel. > > > > Networking is severely horked using the 2.4.18 kernel that i built > (this > > is the first kernel that i've built on this laptop, so i'm not > ruling > > out the possibility of my unfamiliarity with the hardware). Here's > an > > assortment of errors that i'm seeing at bootup: > > > > ifup: arping: socket: Address family not supported by protocol > > you don't have af_packet, either built-in or as a module (Networking > options)
Yea, i compiled it in on the next run through, and it resolved this error. What i don't understand is that I don't normally compile any support for it in the other 2.4.x kernels i've built, and never saw this error before. > > ifup: Error, some other host already uses address 127.0.0.1 > > lo has come up, so can't again. But is it localhost or did you by > chance > give 127.0.0.1 a name other than localhost in your /etc/hosts file > (not a > good idea, BTW). Nope. I've not bound 127.0.0.1 to anything other than lo. This error also disapeared once i compiled af_packet support into the kernel. > > network: bringing up interface lo: failed > > RTNETLINK answers: Cannot assign requested address > > > > What is even more strange is that the loopback comes up anyway (it > > appears in the output from ifconfig). I'll also note that support > for > > the PCMCIA Xircom RealPort Cardbus Ethernet 10/100+ Modem 56 card no > > longer seems to exist, as pcmcia-cs fails to recognize it, even when > i > > manually load the module that supports it. > > what does /var/lib/pcmcia/stab say? Its identical under both the 'good RH' and 'bad 2.4.18' kernel: Socket 0: CardBus hotplug device Socket 1: empty > > After trolling through messages a bit, I see some references to a > > failure to locate module net-pf-17 when cardmgr tries to support the > > card. What I don't understand is why its looking for the packet > socket > > module, when i have no call for it in modules.conf. > > because it might be needed (I noticed arping above) Yea, it seems this way. I'm wondering if this is something new for 2.4.18, because on my SONY VAIO that also has a PCMCIA NIC (not a Xircom though), i haven't compiled any af_packet support into the 2.4.17 kernel it uses, and everything works just fine. > Yep, you blew this one. > > Sure you have the cardbus module the Xircom requires? Hrmmm...it appears that I am missing a few under 2.4.18, namely: yenta_socket pcmcia_core However, i'm fairly certain that I compiled them into the kernel, rather than making them modular. Actually, if I restart the network service, eth0 comes up, and i can ping out. So, i'm guessing I need to add an alias entry into modules.conf for xircom_cb so that it will get loaded on bootup. So, i guess the only remaining mystery here is why does eth0 come up on its own when booting into the RH kernel, but not mine? Thanks for you help, David, i appreciate it. ===== ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J. Friedman [EMAIL PROTECTED] Linux Step-by-step help: http://netllama.ipfox.com . __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ _______________________________________________ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
