| 1 |
sean wrote: |
| 2 |
> Daniel Iliev wrote: |
| 3 |
>> sean wrote: |
| 4 |
>>> Here is where things stand. |
| 5 |
>>> |
| 6 |
>>> On boot, dmesg showed the modules did not load. |
| 7 |
>> |
| 8 |
>> Did you replace the old "System.map" file with the new one? |
| 9 |
>> "cp /usr/src/linux/System.map /boot/System.map" |
| 10 |
>> or |
| 11 |
>> "/usr/src/linux/System.map /System.map" |
| 12 |
>> |
| 13 |
> |
| 14 |
> Well your recommendations did the trick, the boot message failures of |
| 15 |
> the modules is gone. |
| 16 |
> |
| 17 |
> I do not recall in the Gentoo instructions on the System.map copy you |
| 18 |
> mentioned above. |
| 19 |
> |
| 20 |
> Thanks |
| 21 |
> Sean |
| 22 |
|
| 23 |
Actually if you use "make install" it would take care for the System.map |
| 24 |
file and put it in "/boot". |
| 25 |
There is a private case when /boot is a mount point for a different |
| 26 |
partition and it happens that the kernel seeks /boot/System.map before |
| 27 |
the partition is mounted. If it can't find that file it seeks for |
| 28 |
/System.map (in the root partition). If not there it seeks for |
| 29 |
/usr/src/linux/System.map. If the kernel finds a wrong version of |
| 30 |
System.map or can't find it at all it is expected to be a minor problem |
| 31 |
and the system should work properly. |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Best regards, |
| 36 |
Daniel |
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-amd64@g.o mailing list |
Archives