View previous topic :: View next topic |
Author |
Message |
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Mon Jun 29, 2009 7:25 pm Post subject: |
|
|
If running 32 bit, your best bet is to pick the Pentium M, as it is closest to all that processor's settings (sse, sse2, mmx). Picking the older Xeon would most likely call for ssse3, which as you can see, your processor doesn't have. Under x86_64, choose the Intel P4 / older netburst Xeon. Once again, it is closest without going over.
Blessed be!
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Tue Jun 30, 2009 5:34 am Post subject: |
|
|
You're most welcome, as always.
Blessed be!
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54312 Location: 56N 3W
|
Posted: Thu Jul 02, 2009 9:20 pm Post subject: |
|
|
audiodef,
The menuconfig search also shows what your module depends on. Check that those settings are correct or the one you want may be hidden. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Thu Jul 02, 2009 9:39 pm Post subject: |
|
|
Also make sure you have
│ │ --- Wireless │ │
│ │ -*- Improved wireless configuration API │ │
│ │ [ ] cfg80211 regulatory debugging │ │
│ │ [*] nl80211 new netlink interface support │ │
│ │ [ ] Old wireless static regulatory definitions │ │
│ │ -*- Wireless extensions │ │
│ │ [*] Wireless extensions sysfs files │ │
│ │ < > Common routines for IEEE802.11 drivers │ │
│ │ <*> Generic IEEE 802.11 Networking Stack (mac80211) │ │
turned on, or it is for naught.
Blessed be!
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
Posted: Thu Jul 02, 2009 10:05 pm Post subject: |
|
|
The nl80211 option wasn't there, but after enabling everything else, the iwl4965 option appeared.
They should make these things more intuitive, or provide more "how to enable this option" info.
Thanks!
pappy_mcfae wrote: | Also make sure you have
│ │ --- Wireless │ │
│ │ -*- Improved wireless configuration API │ │
│ │ [ ] cfg80211 regulatory debugging │ │
│ │ [*] nl80211 new netlink interface support │ │
│ │ [ ] Old wireless static regulatory definitions │ │
│ │ -*- Wireless extensions │ │
│ │ [*] Wireless extensions sysfs files │ │
│ │ < > Common routines for IEEE802.11 drivers │ │
│ │ <*> Generic IEEE 802.11 Networking Stack (mac80211) │ │
turned on, or it is for naught.
Blessed be!
Pappy |
_________________ decibel Linux: https://decibellinux.org
Github: https://github.com/Gentoo-Music-and-Audio-Technology
Facebook: https://www.facebook.com/decibellinux
Discord: https://discord.gg/73XV24dNPN |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Fri Jul 03, 2009 5:27 am Post subject: |
|
|
Sorry I wasn't here to help. On the other hand, you figured it out, so...I didn't have to be. Cool!
Blessed be!
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Sat Jul 04, 2009 9:25 am Post subject: |
|
|
A happy Fourth of July to my fellow Yankees out there! In celebration, I have uploaded .configs for 2.6.27.26, 2.6.29.6, 2.6.30.1 and 2.6.30-gentoo-r2 in both x86 and x86_64 flavors. I also fixed some minor errors in the .30 configurations, and reposted them as well. Let the fireworks begin!
Blessed be!
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
Posted: Sat Jul 04, 2009 5:06 pm Post subject: |
|
|
Coming back to this, I noticed in the BIOS that my processor is "EM64T". 64-bit? Should I change my options accordingly?
pappy_mcfae wrote: | If running 32 bit, your best bet is to pick the Pentium M, as it is closest to all that processor's settings (sse, sse2, mmx). Picking the older Xeon would most likely call for ssse3, which as you can see, your processor doesn't have. Under x86_64, choose the Intel P4 / older netburst Xeon. Once again, it is closest without going over.
Blessed be!
Pappy |
_________________ decibel Linux: https://decibellinux.org
Github: https://github.com/Gentoo-Music-and-Audio-Technology
Facebook: https://www.facebook.com/decibellinux
Discord: https://discord.gg/73XV24dNPN |
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Sun Jul 05, 2009 5:07 am Post subject: |
|
|
To find out if you can use 64 bit, get a SysRescueCD and enter rescue64 at boot. If it starts, then it is a 64 bit processor, and in that case, it would probably be best to choose Intel P4 / older Netburst based Xeon. Either that or generic -x86-64.
Blessed be!
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54312 Location: 56N 3W
|
Posted: Sun Jul 05, 2009 3:42 pm Post subject: |
|
|
pappy_mcfae,
Code: | grep lm /proc/cpuinfo | works on any distro. If you have that flag, its 64 bit capable. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Mon Jul 06, 2009 6:04 am Post subject: |
|
|
NeddySeagoon,
Thanks for the tip. I only have lm showing up in the /proc/cpuinfo of one machine...the 64 bit machine. Cool.
Blessed be!
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54312 Location: 56N 3W
|
Posted: Mon Jul 06, 2009 6:09 pm Post subject: |
|
|
audiodef,
lm stands for Long Machine, meaning the 64 bit register set.
You don't loose half the data bus. The CPU still uses it all.
Do do only use the bottom half of your 64 bit registers and you do not use any instructions the operate of 64 bit quantities directly.
You also force the kernel to use Himem routines to access RAM over 2G and PAE for RAM over 4G.
In 64 bit mode the address space is linear up to 2^64. However. not all the address bits are made available. I don't recall the physical address bus width, its either 42 or 46 bits. 43 bits is 4Tb, which is more RAM that anyone could reasonably want attached to a single CPU for a few years yet. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
Posted: Mon Jul 06, 2009 10:55 pm Post subject: |
|
|
4Tb... party time. Thanks for 'splaining.
Pappy, have you ever come across any issues with a 64-bit system and tuxonice-sources? I'm seeing a bunch of packages fail to emerge on a 64-bit system with tuxonice when they did not when I installed Gentoo as 32-bit with gentoo-sources. I'm compiling gentoo-sources now to see what happens, but I thought I'd ask as well.
edit:
What prompted this question is lvm2 and openrc on ~amd64, synced as of today, just will not compile with the 64-bit system I set up and tuxonice-sources.
I just chrooted into this system and I can say it's not tuxonice, as openrc still will not compile. I'm-a go have dinner and check in here later and see if you have any advice. Maybe I just can't set up this laptop with 64-bit even though it's a 64-bit machine. _________________ decibel Linux: https://decibellinux.org
Github: https://github.com/Gentoo-Music-and-Audio-Technology
Facebook: https://www.facebook.com/decibellinux
Discord: https://discord.gg/73XV24dNPN |
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Tue Jul 07, 2009 4:18 am Post subject: |
|
|
No, I haven't heard of tuxonice issues with 64 bit machines. I did set up and test a tuxonice kernel for my 64 bit system, and it worked ok. I didn't set up the hibernation stuff, so I am guessing I missed out on possible issues there.
It might not be a bad idea to take a look at bugzilla. Look for tuxonice issues, and issues directly related to what you're experiencing. The intuitive part of me says there's something else going on.
Blessed be!
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
Posted: Tue Jul 07, 2009 12:40 pm Post subject: |
|
|
Intuition, as it usually does most of us, has served you well. I found out about this:
https://bugs.gentoo.org/show_bug.cgi?id=276715
and put linux-headers in package.mask, keeping it down to version 29, and openrc on my other 64-bit machine compiled fine.
pappy_mcfae wrote: | No, I haven't heard of tuxonice issues with 64 bit machines. I did set up and test a tuxonice kernel for my 64 bit system, and it worked ok. I didn't set up the hibernation stuff, so I am guessing I missed out on possible issues there.
It might not be a bad idea to take a look at bugzilla. Look for tuxonice issues, and issues directly related to what you're experiencing. The intuitive part of me says there's something else going on.
Blessed be!
Pappy |
_________________ decibel Linux: https://decibellinux.org
Github: https://github.com/Gentoo-Music-and-Audio-Technology
Facebook: https://www.facebook.com/decibellinux
Discord: https://discord.gg/73XV24dNPN |
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Tue Jul 07, 2009 7:34 pm Post subject: |
|
|
Awesome. I'll have to keep that in mind if I come upon weird compilation issues.
Blessed be!
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Thu Jul 09, 2009 5:31 am Post subject: |
|
|
To know for sure, stop kdm/xdm/gdm from starting. Enter a CLI, then enter startx. See what happens at that point.
Blessed be!
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
|