FC6 not connecting -- amplification

[Beartooth]

On Thu, 01 Feb 2007 11:52:30 -0800, Rick Stevens wrote:

> On Thu, 2007-02-01 at 19:16 +0000, Beartooth wrote:
[...] 
>> I think I must have retyped that correctly, because bash turned the uname
>> part into "2.6.19-1.2895.fc6" and left the rest. But I also think I do not
>> have it, because bash then added ":No such file or directory"
> 
> Hmmm.  Let me try:
> 
> [root at prophead ~]# ls /lib/modules/`uname -r`/kernel/drivers/net/e100.ko
> /lib/modules/2.6.18-1.2869.fc6/kernel/drivers/net/e100.ko
> 
Odd : you appear to be running an older kernel than I got off my CD ...
>> 
>> Anybody know a straightforward way to get it from the CDs?
> 
> It's part of the kernel RPM.  If you've installed the kernel, you've got
> it.
> 
> So, here's what to do:
> 
> 1. Run "su -" and become root
> 2. Run "ls /lib/modules/`uname -r`/kernel/drivers/net/e100.ko" and
>    verify you have the file.

Aargh. It says "ls: /lib/modules/`uname -r`/kernel/drivers/net/e100.ko: no
such file or directory"

> 3. Delete the "/etc/sysconfig/hwconf" file and run kudzu to rediscover
>    your hardware:
> 
> 	rm /etc/sysconfig/hwconf
> 	kudzu

I did that slightly differently, just to be sure : "cd /etc/sysconfig"
followed by "ls | grep hw" -- which did give me hwconf -- then deleted it
and ran kudzu (which gave me my prompt back, with no report).

 
> 4. Run "modprobe e100" to load the driver 5. 

That gave 

"FATAL: Could not load /lib/modules/2.6.19-1.2895.fc6/modules.dep: No such
file or directory."

So I did cd / (just to be sure), then cd /lib, then ls; sure enough,
there's a subdirectory called modules. So I tried cd modules, then ls --
and all it contains is a subdirectory, called *not* 2.6.19-[and so on], as
we got from `uname -r` -- but 2.6.18-1.2798.fc6

I looked in that. It contains build, extra, kernel, source, updates,
weak-updates, and eleven things of the form modules.*

Here I stop for now -- have we discovered something?

> Run "ifconfig" and verify
> you have device eth0. 6. Try to configure eth0 using the command line:
> 
> 	ifconfig eth0 192.168.0.254 netmask 255.255.255.0
> 
> 7. Try "ifconfig" again.  You should see something like:
> 
> [root at prophead ~]# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:0F:FE:02:16:38
> 	  inet addr:192.168.0.254  Bcast:192.168.0.255
> 		Mask:255.255.255.0
>           inet6 addr: fe80::20f:feff:fe02:1638/64 Scope:Link UP
>           BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 RX
>           packets:33007499 errors:0 dropped:0 overruns:0 frame:0 TX
>           packets:15837216 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:2322911622 (2.1 GiB)  TX bytes:616269113 (587.7 MiB)
>           Interrupt:193
> 
> The "HWaddr", "inet6 addr:", "Interrupt" and traffic info (RX/TX bytes)
> will differ from what I show above, but you get the idea.
> 
> 8. If you see that stuff, great!  Edit the /etc/modprobe.conf file and
> add a line that reads:
> 
> 	alias eth0 e100
> 
> 9. Run your normal configuration.  Delete all existing configs and put
> in the new stuff you want.
> 
> That should handle it.


-- 
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Remember I know precious little of what I am talking about.