| View previous topic :: View next topic |
| Author |
Message |
Stalione
Guru
Joined: 21 Apr 2002
Posts: 335
|
 Posted: Sun Dec 29, 2002 7:22 pm Post subject: Upgrading from Athlon K6 to Athlon MP's |
 |
|
I was running my gentoo install on a Athlon K6 machine. Now I have recently built a athlon MP (dual proc) system and I just moved the hard drivers over from the old system. Im not only having trouble recompiling the kernel with SMP support, but also not sure what CFLAGS to set in /etc/make.conf. Yes I am quite aware that those two issues are completely unrelated. Should my CFLAGS in /etc/make.conf be set to | Code: | | CFLAGS="-mcpu=athlon-mp -O3 -pipe" |
(notice the mp not xp) Cuase in the comments I noticed they mention CFLAGS="-mcpu=athlon-xp -O3 -pipe" which is for XP's. No mentop on there for MP's. i did do a search on the forum for keywords Athlon MP and didn't get any results. As for my kernel issue this is the error im getting (during make modules_install stage):
| Code: |
depmod: i2c_detect_R3gig_12fb8fa2
depmod: i2c_del_driver_R3gig_e1de2769
depmod: i2c_add_driver_R3gig_d0e7daf2
depmod: i2c_attach_client_R3gig_907d1bef
depmod: *** Unresolved symbols in /lib/modules/2.4.19-gentoo-r10/misc/pcf8591.o
depmod: i2c_smbus_read_byte_R3gig_ec07fbca
depmod: i2c_sysctl_real_R3gig_de7b1f58
depmod: i2c_register_entry_R3gig_e7051574
depmod: i2c_deregister_entry_R3gig_ec85ba8b
depmod: i2c_proc_real_R3gig_1680fb1c
depmod: i2c_detach_client_R3gig_55410d17
depmod: i2c_check_functionality_R3gig_51494ff7
depmod: i2c_smbus_write_byte_R3gig_ae1d90f4
depmod: i2c_detect_R3gig_12fb8fa2
depmod: i2c_del_driver_R3gig_e1de2769
depmod: i2c_smbus_write_byte_data_R3gig_112fd2f4
depmod: i2c_add_driver_R3gig_d0e7daf2
depmod: i2c_attach_client_R3gig_907d1bef
depmod: *** Unresolved symbols in /lib/modules/2.4.19-gentoo-r10/misc/sis5595.o
depmod: i2c_sysctl_real_R3gig_de7b1f58
depmod: i2c_register_entry_R3gig_e7051574
depmod: i2c_deregister_entry_R3gig_ec85ba8b
depmod: i2c_proc_real_R3gig_1680fb1c
depmod: i2c_detach_client_R3gig_55410d17
depmod: i2c_detect_R3gig_12fb8fa2
depmod: i2c_del_driver_R3gig_e1de2769
depmod: i2c_add_driver_R3gig_d0e7daf2
depmod: i2c_attach_client_R3gig_907d1bef
depmod: *** Unresolved symbols in /lib/modules/2.4.19-gentoo-r10/misc/smbus-arp.o
depmod: i2c_sysctl_real_R3gig_de7b1f58
depmod: i2c_register_entry_R3gig_e7051574
depmod: i2c_deregister_entry_R3gig_ec85ba8b
depmod: i2c_proc_real_R3gig_1680fb1c
depmod: i2c_smbus_write_block_data_R3gig_460334c4
depmod: i2c_detach_client_R3gig_55410d17
depmod: i2c_check_functionality_R3gig_51494ff7
depmod: i2c_detect_R3gig_12fb8fa2
depmod: i2c_del_driver_R3gig_e1de2769
depmod: i2c_add_driver_R3gig_d0e7daf2
depmod: i2c_attach_client_R3gig_907d1bef
depmod: *** Unresolved symbols in /lib/modules/2.4.19-gentoo-r10/misc/smsc47m1.o
depmod: i2c_sysctl_real_R3gig_de7b1f58
depmod: i2c_register_entry_R3gig_e7051574
depmod: i2c_deregister_entry_R3gig_ec85ba8b
depmod: i2c_proc_real_R3gig_1680fb1c
depmod: i2c_detach_client_R3gig_55410d17
depmod: i2c_detect_R3gig_12fb8fa2
depmod: i2c_del_driver_R3gig_e1de2769
depmod: i2c_add_driver_R3gig_d0e7daf2
depmod: i2c_attach_client_R3gig_907d1bef
depmod: *** Unresolved symbols in /lib/modules/2.4.19-gentoo-r10/misc/thmc50.o
depmod: i2c_sysctl_real_R3gig_de7b1f58
depmod: i2c_register_entry_R3gig_e7051574
depmod: i2c_deregister_entry_R3gig_ec85ba8b
depmod: i2c_proc_real_R3gig_1680fb1c
depmod: i2c_detach_client_R3gig_55410d17
depmod: i2c_check_functionality_R3gig_51494ff7
depmod: i2c_smbus_read_byte_data_R3gig_043d576a
depmod: i2c_detect_R3gig_12fb8fa2
depmod: i2c_del_driver_R3gig_e1de2769
depmod: i2c_smbus_write_byte_data_R3gig_112fd2f4
depmod: i2c_add_driver_R3gig_d0e7daf2
depmod: i2c_attach_client_R3gig_907d1bef
depmod: *** Unresolved symbols in /lib/modules/2.4.19-gentoo-r10/misc/via686a.odepmod: i2c_sysctl_real_R3gig_de7b1f58
depmod: i2c_register_entry_R3gig_e7051574
depmod: i2c_deregister_entry_R3gig_ec85ba8b
depmod: i2c_proc_real_R3gig_1680fb1c
depmod: i2c_detach_client_R3gig_55410d17
depmod: i2c_detect_R3gig_12fb8fa2
depmod: i2c_del_driver_R3gig_e1de2769
depmod: i2c_add_driver_R3gig_d0e7daf2
depmod: i2c_attach_client_R3gig_907d1bef
depmod: *** Unresolved symbols in /lib/modules/2.4.19-gentoo-r10/misc/vt1211.o
depmod: i2c_sysctl_real_R3gig_de7b1f58
depmod: i2c_register_entry_R3gig_e7051574
depmod: i2c_deregister_entry_R3gig_ec85ba8b
depmod: i2c_proc_real_R3gig_1680fb1c
depmod: i2c_detach_client_R3gig_55410d17
depmod: i2c_detect_R3gig_12fb8fa2
depmod: i2c_del_driver_R3gig_e1de2769
depmod: i2c_add_driver_R3gig_d0e7daf2
depmod: i2c_attach_client_R3gig_907d1bef
depmod: *** Unresolved symbols in /lib/modules/2.4.19-gentoo-r10/misc/w83781d.o
depmod: i2c_sysctl_real_R3gig_de7b1f58
depmod: i2c_register_entry_R3gig_e7051574
depmod: i2c_deregister_entry_R3gig_ec85ba8b
depmod: i2c_smbus_write_word_data_R3gig_4b74825d
depmod: i2c_proc_real_R3gig_1680fb1c
depmod: i2c_smbus_read_word_data_R3gig_c04d3d1e
depmod: i2c_adapter_id_R3gig_5b8676a6
depmod: i2c_detach_client_R3gig_55410d17
depmod: i2c_check_functionality_R3gig_51494ff7
depmod: i2c_smbus_read_byte_data_R3gig_043d576a
depmod: i2c_detect_R3gig_12fb8fa2
depmod: i2c_del_driver_R3gig_e1de2769
depmod: i2c_smbus_write_byte_data_R3gig_112fd2f4
depmod: i2c_add_driver_R3gig_d0e7daf2
depmod: i2c_attach_client_R3gig_907d1bef
|
A google search only resulted in one English thread which did not really make much sense to me. Here it is anyways. I am using kernel linux-2.4.19-gentoo-r10 |
|
| Back to top |
|
 |
Stalione
Guru
Joined: 21 Apr 2002
Posts: 335
|
| Posted: Sun Dec 29, 2002 8:08 pm Post subject: |
|
|
| I found a solution to my kernel problem. For some strange linking issues my /lib/modules/2.4.19-gentoo-r10 directory was screwed up. I just moved it to /lib/modules/2.4.19-gentoo-r10_old and did make modules_install and it worked just fine. Now I have SMP working perfectly. |
|
| Back to top |
|
|
AlterEgo
Veteran
Joined: 25 Apr 2002
Posts: 1619
|
| Posted: Sun Dec 29, 2002 9:09 pm Post subject: |
|
|
Good for you 
Still: CFLAGS="-mcpu=athlon-mp -O3 -pipe" is not 100% correct.
CFLAGS="-march=athlon-mp -O3 -pipe" is the better syntax.
The depmod errors can probably be avoided by starting the kernel build process with" make mrproper" before anything else. Make sure to back up your .config first! |
|
| Back to top |
|
|
Stalione
Guru
Joined: 21 Apr 2002
Posts: 335
|
| Posted: Sun Dec 29, 2002 11:27 pm Post subject: |
|
|
You were absoltely right. I removed all the directories in /lib/modules/ and then I did the following:
| Code: |
cd /usr/src/linux
make mrproper
make distclean
make clean
make menuconfig
make dep && make clean bzImage modules modules_install
|
After a reboot I typed modules-update and it updated all the modules without any errors. The only strangeness im experiencing is that my SB live soundcard works just fine but when alsa is starting up it says it can't load snd-module snd-emu10k1. Ill keep working on this and post the solution if I find it. |
|
| Back to top |
|
|
Stalione
Guru
Joined: 21 Apr 2002
Posts: 335
|
| Posted: Sun Dec 29, 2002 11:44 pm Post subject: |
|
|
as for my alsa probs....its simple. It skipped my mind that when you emerge alsa-diver , it puts modules in the sound directory. Because I deleted the directory under /lib/modules/<kernel> that modules put in by alsa are also gone ...DOH! hehehe...just emerge alsa-driver and your good to go.  |
|
| Back to top |
|
|
keratos68
Guru
Joined: 27 Dec 2002
Posts: 561
Location: Blackpool, Lancashire, UK.
|
| Posted: Sun Dec 29, 2002 11:49 pm Post subject: |
|
|
When you perform a kernel rebuild, the ALSA drivers need to be rebuilt. Try:
emerge -p alsa
emerge alsa
You will also need to edit your /etc/modules.d/alsa file to correctly insert your sound card. Read the GENTOO LINUX ALSA GUIDE on the web home. Take a backup of the /etc/modules.d/alsa for next time you krecompile!
Finally, run update-modules again.
I think that should sort you out.
 |
|
| Back to top |
|
|
keratos68
Guru
Joined: 27 Dec 2002
Posts: 561
Location: Blackpool, Lancashire, UK.
|
| Posted: Sun Dec 29, 2002 11:54 pm Post subject: |
|
|
SORRY!!! I meant "emerge alsa-driver" and not "emerge alsa".
"emerge alsa" will build the class, i.e. the whole lot again, you only need rebuld the drivers! |
|
| Back to top |
|
|
Stalione
Guru
Joined: 21 Apr 2002
Posts: 335
|
| Posted: Mon Dec 30, 2002 1:43 am Post subject: |
|
|
| hehe thanks but i guess you did not read my response..thats exactly what i suggested as the solution. Looks like you might have been posting same time I was. |
|
| Back to top |
|
|
puddpunk
l33t
Joined: 20 Jul 2002
Posts: 681
Location: New Zealand
|
| Posted: Mon Dec 30, 2002 6:54 am Post subject: |
|
|
| AlterEgo wrote: | Good for you
Still: CFLAGS="-mcpu=athlon-mp -O3 -pipe" is not 100% correct.
CFLAGS="-march=athlon-mp -O3 -pipe" is the better syntax. |
| Code: | | CFLAGS="-mcpu=athlon-mp -O3 -pipe" |
is 100% correct, if you want it optimised for athlon MP's, and you want the generated binary to run on other machines as well.
-mcpu WILL optimise for the specified architecture, and is a perfectly legal GCC flag. -march optimises more aggressively, and uses all the nooks and crannies of the architecture, and will not run on other processors (as a rule of thumb) |
|
| Back to top |
|
|
Stalione
Guru
Joined: 21 Apr 2002
Posts: 335
|
| Posted: Mon Dec 30, 2002 9:18 am Post subject: |
|
|
I just moved my drives from a Athlon K6 box to a new Athlon MP box. Currently my /etc/make.con says the following:
| Quote: |
#+++
# automagicaly added by build process
#
CHOST='i586-pc-linux-gnu'
CFLAGS='-march=k6-3 -mcpu=k6-3 -O3 -pipe'
CXXFLAGS='-march=k6-3 -mcpu=k6-3 -O3 -pipe'
#---
|
Obviously these no longer apply but will work. I know what to put for CFLAGS (CFLAGS="-mcpu=athlon-mp -O3 -pipe") but I dunno what to put for CHOST and CXXFLAGS. Can someone please help. |
|
| Back to top |
|
|
fuxored
n00b
Joined: 29 May 2002
Posts: 71
|
| Posted: Mon Dec 30, 2002 9:32 pm Post subject: |
|
|
Heres how mine is setup, also using dual athlons.
| Code: |
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon-mp -O3 -pipe -fomit-frame-pointer"
CXXFLAGS="${CFLAGS}"
|
|
|
| Back to top |
|
|
Stalione
Guru
Joined: 21 Apr 2002
Posts: 335
|
| Posted: Tue Dec 31, 2002 2:40 am Post subject: |
|
|
| Thanks a lot. Just what I needed. I was fairly sure I had it right but its just reassuring to see it from someone else =) Does anyone know of a good document that might explain these CFLAGS in an understandable way? |
|
| Back to top |
|
|
scoobydu
Veteran
Joined: 16 Feb 2003
Posts: 1076
Location: 'Mind the Gap'
|
| Posted: Tue Feb 18, 2003 9:28 pm Post subject: |
|
|
Thx for the info Stalione, I'm running a couple of Athlon 2100+MP's with the mcpu settings listed in the make.conf file.
Everything is working great , but it sounds like I haven't really got it tuned to its full potential yet.
What settings did you end up with?
cheers
scoob |
|
| Back to top |
|
|
abhishek
Retired Dev
Joined: 28 Jun 2002
Posts: 393
Location: Los Angeles, CA
|
| Posted: Wed Feb 19, 2003 12:12 am Post subject: |
|
|
| Stalione wrote: | | Thanks a lot. Just what I needed. I was fairly sure I had it right but its just reassuring to see it from someone else =) Does anyone know of a good document that might explain these CFLAGS in an understandable way? |
Try this, this. and this. |
|
| Back to top |
|
|
|
Portage & Programming
