[gentoo-user] modprobe looks in wrong dir
maxim wexler
This should be an easy fix -- if you already know!
The reason many of my modules are not loading is
because modprobe is looking in /lib/modules/2.6.12-r6
and not /lib/modules/2.6.16-r3 which was filled when I
ran make modules_install.
The link to the newer kernel is OK.
Yes, I ran modules-update.
Also, module loading and unloading options are set=y
in kernel.
Not a clue as to why some modules load, sound, usb;
and some, firewire, ppp, forcedeth don't.
dmesg is filled with lines like:
Unknown symbol < >...disagrees about version of
symbol< > ...
At the end of the boot console it says:
/usr/sbin/pppd/: Couldn't stat /dev/ttyS0: Too many
levels of symbolic links.
But according to emerge -pv udev I have the latest
ver. Which I set up according to the gentoo
udev-guide.
Attempts to specify the proper dir to modprobe result
in no-such-file errors.
-mw
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
gento...@gentoo.org mailing list
Francesco Talamona
> Hi group,
>
> This should be an easy fix -- if you already know!
>
> The reason many of my modules are not loading is
> because modprobe is looking in /lib/modules/2.6.12-r6
> and not /lib/modules/2.6.16-r3 which was filled when I
> ran make modules_install.
>
> The link to the newer kernel is OK.
>
> Yes, I ran modules-update.
It seems like you compiled your kernel but forgot to execute
"make modules_install" step.
ciao
Francesco
--
Linux Version 2.6.16-gentoo-r4, Compiled #1 PREEMPT Wed Apr 26 06:59:58
CEST 2006
One 1GHz AMD Athlon 64 Processor, 2GB RAM, 2007.31 Bogomips Total
aemaeth
--
gento...@gentoo.org mailing list
Brett I. Holcomb
nvidia, alsa require you rerun their installation process.
--
Brett I. Holcomb
--
gento...@gentoo.org mailing list
Maurice E Johnson
maxim wexler
> > ran make modules_install.
> It seems like you compiled your kernel but forgot to
> execute
> "make modules_install" step.
>
> ciao
> Francesco
>
> --
> Linux Version 2.6.16-gentoo-r4, Compiled #1 PREEMPT
> Wed Apr 26 06:59:58
> CEST 2006
> One 1GHz AMD Athlon 64 Processor, 2GB RAM, 2007.31
> Bogomips Total
> aemaeth
> --
> gento...@gentoo.org mailing list
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
gento...@gentoo.org mailing list
maxim wexler
--- Maurice E Johnson <maurice....@gmail.com>
wrote:
> modules-update only updates for the running version.
> In order to update
> the new version, you could simply reboot to the new
> version.
Ok, here's where it gets weird, at least to me:
The symlink points to the new sources. When I cd
/usr/src/linux that's where I end up. I run make
menuconfig, then make && make modules_install. Then I
copy bzImage to /boot/vmlinuz as always; take a quick
look around; check that the new /lib/modules dir(there
are now two, natch) is full of modular goodness, and
reboot.
At the grub prompt I run >root, >kernel /vmlinuz #the
*new* kernel and >boot as I always do.
CERTAIN modules load. CERTAIN modules don't,
predominantly having to do with communications
hardware.
The thing makes it to the prompt. I log in. Run uname.
Yikes! It *is* _running_ the old kernel.
BUT, it's _booting_ from the new! I checked!
Puh-leeeeeeeze! Chew me out! Deny my competency! Flame
me like you've never flamed the rankest wannabe!But
tell me how to fix this thing!
-Your humble servant etc etc
-Maxim
Francesco Talamona
> > when I
> >
> > > ran make modules_install.
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^!
ooops. Sorry
FT
Francesco Talamona
> make
> menuconfig, then make && make modules_install
You missed a step:
make && make modules && make modules_install
Ciao
Francesco
--
Linux Version 2.6.16-gentoo-r4, Compiled #1 PREEMPT Wed Apr 26 06:59:58
CEST 2006
One 1.8GHz AMD Athlon 64 Processor, 2GB RAM, 3613.16 Bogomips Total
Toby Cubitt
> On Monday 01 May 2006 22:05, maxim wexler wrote:
> > make menuconfig, then make && make modules_install
>
> You missed a step:
> make && make modules && make modules_install
Actually, he didn't. The 2.6 series kernels don't require the "make
modules" step.
Toby
--
PhD Student
Quantum Information Theory group
Max Planck Institute for Quantum Optics
Garching, Germany
email: to...@dr-qubit.org
web: www.dr-qubit.org
--
gento...@gentoo.org mailing list
Jacques Montier
> You missed a step:
> make && make modules && make modules_install
>
> Ciao
>
>
I don't think so,
when you run make, your compile kernel and modules.
Then, you just have to run make modules_install.
So make && make modules_install is ok.
But, I don't help maxim very much :-(
regards
--- Jacques --
^
^^^
^^^^^
( 0 0 )
\/
-----0000----------0000-----
--
gento...@gentoo.org mailing list
Francesco Talamona
> Actually, he didn't. The 2.6 series kernels don't require the "make
> modules" step.
Ok, good to know. An old school leftover :-)
Ciao
Francesco
--
Linux Version 2.6.16-gentoo-r4, Compiled #1 PREEMPT Wed Apr 26 06:59:58
CEST 2006
One 2.2GHz AMD Athlon 64 Processor, 2GB RAM, 4416.08 Bogomips Total
Mick
On Monday 01 May 2006 21:05, maxim wexler wrote:
> Ok, here's where it gets weird, at least to me:
>
> The symlink points to the new sources. When I cd
> /usr/src/linux that's where I end up.
I assume that you first check:
# ls -la /usr/src
where the symlink points to, because after you cd into it you can't readily
see what directory you've descended into.
> I run make
> menuconfig, then make && make modules_install. Then I
> copy bzImage to /boot/vmlinuz as always; take a quick
> look around; check that the new /lib/modules dir(there
> are now two, natch) is full of modular goodness, and
> reboot.
I don't use make install, because my set up (on the laptop is rather
complicated) and so I always manually copy the kernel image. I use cp -i -v
to get some feedback on what's happening and make sure that I overwrite only
the files I choose to. Also, my modules have to be manually entered
in /etc/modules.autoload.d/kernel-2.6, at least these modules which I always
want installed automatically at boot.
I first modprobe -v <module_name> one at a time to make sure that they do load
without errors. Then enter their name in /etc/modules.autoload.d/kernel-2.6
and finally run modules-update.
> At the grub prompt I run >root, >kernel /vmlinuz #the
> *new* kernel and >boot as I always do.
Don't you have a menu.lst or grub.conf to set up your grub menu so that you
don't have to make manual entries at boot time?
> CERTAIN modules load. CERTAIN modules don't,
> predominantly having to do with communications
> hardware.
Anything in /etc/modules.autoload.d/kernel-2.6 should load automatically or
print an error. Latest changes in udev slightly complicate matters - see
other concurrent thread on this topic.
> The thing makes it to the prompt. I log in. Run uname.
> Yikes! It *is* _running_ the old kernel.
>
> BUT, it's _booting_ from the new! I checked!
There's a bit of a contradiction in terms here! I suggest that you are
inadvertently booting the old kernel image and that's what's shown.
If you check the /usr/src/linux symlink after reboot where does it lead you?
HTH.
--
Regards,
Mick
Richard Fish
> The thing makes it to the prompt. I log in. Run uname.
> Yikes! It *is* _running_ the old kernel.
>
> BUT, it's _booting_ from the new! I checked!
I don't see how this is possible. How did you check that it is
booting the new kernel? Checking dmesg output would be the best way
to verify...
Possibly a stupid question, but are you sure that /boot is actually
mounted (if it is a separate filesystem) when you copy the new kernel
to it?
-Richard
--
gento...@gentoo.org mailing list