| 1 |
Roy~ |
| 2 |
I've been leaning toward building the kernel myself; maybe this is a good |
| 3 |
time to jump in... |
| 4 |
|
| 5 |
I know from lspci that, in addition to the nvidia kernel (which |
| 6 |
module-rebuild correctly identifies), that ipw2100 (wireless) is a module |
| 7 |
that I had to emerge in order to be functional on my laptop. I also know |
| 8 |
that I emerged alsa sound to get all the functionality I wanted there. And, |
| 9 |
from going through menuconfig, it appears that the sound/modem controller |
| 10 |
(Intel AC97) and the Firewire (IEEE1394) is selectable within the kernel |
| 11 |
config. |
| 12 |
So, my question would be - why doesn't module-rebuild see the ipw2100 (at |
| 13 |
least), and the alsa drivers (at most)? |
| 14 |
|
| 15 |
I'm still reading through the docs and re-reading the handbook on kernel |
| 16 |
generation so I'll be trying this out later today. I know that I had a |
| 17 |
lengthy discourse with Holly regarding splash, which was never really |
| 18 |
resolved for me regardless of the kernel generation method chosen. |
| 19 |
|
| 20 |
JD |
| 21 |
|
| 22 |
-----Original Message----- |
| 23 |
From: Roy Wright [mailto:royw@×××××.com] |
| 24 |
Sent: Sunday, October 30, 2005 11:16 PM |
| 25 |
To: gentoo-user@l.g.o |
| 26 |
Subject: Re: [gentoo-user] updates |
| 27 |
|
| 28 |
John Dangler wrote: |
| 29 |
|
| 30 |
>Roy~ |
| 31 |
>Thanks for the reply. I actually used genkernel to make the kernel. I |
| 32 |
used |
| 33 |
>'genkernel all'. That's why I'm a little confused as to why this didn't |
| 34 |
>take effect. The previous kernel was also built with genkernel and didn't |
| 35 |
>have any problems. |
| 36 |
> |
| 37 |
>Regards, |
| 38 |
> |
| 39 |
>JD |
| 40 |
> |
| 41 |
> |
| 42 |
I'm about out of my league with this. Just a couple of days experience |
| 43 |
with genkernel before switching to menuconfig... |
| 44 |
|
| 45 |
Just a few things to check. |
| 46 |
|
| 47 |
dmesg |
| 48 |
|
| 49 |
recent logs in /var/log |
| 50 |
|
| 51 |
Look in /lib/modules. You should see some kernel directories. Ex: |
| 52 |
|
| 53 |
royw-gentoo etc # ls /lib/modules/ |
| 54 |
2.4.28 2.6.11-gentoo-r11 2.6.11-gentoo-r4 2.6.11-gentoo-r9 |
| 55 |
2.6.12-gentoo-r10 2.6.13-gentoo-r3 |
| 56 |
|
| 57 |
Then look in the problem kernel's directory. Ex: |
| 58 |
|
| 59 |
royw-gentoo etc # ls /lib/modules/2.6.12-gentoo-r10/ |
| 60 |
CiscoVPN kernel modules.alias modules.dep |
| 61 |
modules.inputmap modules.pcimap modules.usbmap video |
| 62 |
build misc modules.ccwmap modules.ieee1394map |
| 63 |
modules.isapnpmap modules.symbols source |
| 64 |
|
| 65 |
Then you can dig down into kernel/* looking for *.ko files. Ex: |
| 66 |
|
| 67 |
royw-gentoo etc # find /lib/modules/2.6.12-gentoo-r10/kernel -name |
| 68 |
"*.ko" -print |
| 69 |
/lib/modules/2.6.12-gentoo-r10/kernel/drivers/acpi/video.ko |
| 70 |
/lib/modules/2.6.12-gentoo-r10/kernel/drivers/base/firmware_class.ko |
| 71 |
/lib/modules/2.6.12-gentoo-r10/kernel/drivers/block/pktcdvd.ko |
| 72 |
... |
| 73 |
|
| 74 |
This should give you a warm fuzzy that the modules were built... |
| 75 |
|
| 76 |
If all that's there, then look at the modules configs in /etc. Ex: |
| 77 |
|
| 78 |
royw-gentoo etc # ls -d /etc/modules* |
| 79 |
/etc/modules.autoload.d /etc/modules.conf /etc/modules.conf.old |
| 80 |
/etc/modules.d /etc/modules.devfs |
| 81 |
|
| 82 |
/etc/modules.d contains individual module config files. modules-update |
| 83 |
will merge these into |
| 84 |
/etc/modules.conf. |
| 85 |
|
| 86 |
That's about the sum of my knowledge here... |
| 87 |
|
| 88 |
HTH, |
| 89 |
Roy |
| 90 |
-- |
| 91 |
gentoo-user@g.o mailing list |
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
-- |
| 98 |
gentoo-user@g.o mailing list |
Archives