Re: hosers-talk: SuXE

["Jon Stewart" <stew1@xxxxxxxxxxx>]

> Looking in /lib/modules, there's a 2.2.18 directory filled with 
> subdirectories and module libraries. There's no 2.4.2 library.
							^^^^^^^

That is, "directory".


> Although a complete linux dummy, I am guessing that since I'm getting 
> these modprobe errors and since /proc/modules is empty (I'm guessing it 
> would list loaded modules), none of my modules are loading -- including my 
> ethernet drivers -- because somewhere modprobe is being told to look in 
> /lib/modules/2.4.2/, not /lib/modules/2.2.18.
> 
> I'm kind of amazed, though, that I can get a running system with no 
> modules loaded. 
> 
> Rather than fix the root cause of this problem (that is, why modprobe 
> thinks I'm running 2.4.2), I was thinking about creating a symlink:
> 
> /lib/modules/2.4.2 -> /lib/modules/2.2.18
> 
> 
> Is this an incredibly stupid thing to do?
> 
> If so, do you have any advice as to how I can get my ethernet back up?


If my kernel is looking for modules in the non-existent 
/lib/modules/2.4.2/, why did eth0 come up the first boot last night?

Why can't this shit just fucking work? I don't mind configuring Apache and
MySQL and Slash, but, jebus, ya' think that for the $70 I plunked down, I
could get a working installation (unfortunately, my support has long since
run out).



Jon
who just saw one of his fine neighbors wearing a "low rider" shirt. <sigh>
-- 
Jon Stewart
stew1@xxxxxxxxxxx

"and dropping a barbell, he points to the sky, saying 'the sun's not 
yellow, it's chicken.'"

			-- Bob Dylan