- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Proliant 1850r Suse 8.2 Pro not using 2nd proc...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2003 09:01 PM
тАО10-09-2003 09:01 PM
Any one know to get SuSE 8.2 Pro to start using the second processor on a Proliant 1850r? If so, please try to be as thorough and complete and accurate as possible in your reply, as I dont want to torch this build of it (which was a tiny bit of a struggle).
Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2003 09:13 PM
тАО10-09-2003 09:13 PM
Re: Proliant 1850r Suse 8.2 Pro not using 2nd processor
If you really are running UP then you need to configure the kernel to as a multi processor kernel. It's a long time since I ran SuSe but they used to supply a multiprocessor enabled kernel as well as a uniprocessor one and it may be just a case of getting it and alter /etc/lilo.conf to point to it.
However, in the general case, you will need to build a new kernel with SMP support. I hesitate to give you the steps to do this because SuSe run with modified kernels and doing this might stop something else working. So, if you want to build your own kernel and still keep the old one around just in case, follow these steps.
Backup
become root
# export DISPLAY=:0
# cd /usr/src/linux (or where ever it is in Suse these days)
# make xconfig
Navigate around until you find the SMP option, I think it's one of the first options you are able to change.
change it to "y"
save and exit
# make dep
# make bzImage
# make modules
# make modules_install
# cp /boot/System.map /boot/system.map.prev
# cp /boot/vmlinuz /boot/vmlinuz.prev
# cp arch/i386/boot/bzImage /boot/vmlinuz
# cp System.map /boot/System.map
edit /etc/lilo.conf or grub.conf to include a n entry for your backup kernel image (vmlinuz.prev) or forget this if you like living dangerously
run either "lilo" or "grub" as required
# cross fingers
# re-boot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2003 03:01 AM
тАО10-10-2003 03:01 AM
Re: Proliant 1850r Suse 8.2 Pro not using 2nd processor
ftp://ftp.suse.com/pub/suse/i386/8.2/suse/i586/
(or i686 depending on your CPUs) and look for
k_smp-2.4.20-62.i586.rpm
This should be a precompiled SMP kernel.
If you are using Lilo as the boot manager you should have a "failsafe" option by default (although it never hurts to have a backup kernel as suggested before ;-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2003 07:18 AM
тАО10-13-2003 07:18 AM
Re: Proliant 1850r Suse 8.2 Pro not using 2nd processor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2003 07:53 AM
тАО10-14-2003 07:53 AM
Re: Proliant 1850r Suse 8.2 Pro not using 2nd processor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2003 09:38 AM
тАО10-14-2003 09:38 AM
Re: Proliant 1850r Suse 8.2 Pro not using 2nd processor
quoting complete and undistorted error messages (preferably the first you receive) will greatly enhance your chances of getting good help.
As for the CD-Rom issue, can you boot directly from CD?
Greetings, Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2003 09:42 AM
тАО10-14-2003 09:42 AM
SolutionAny chance you can start over and do the install again off the original install cd's? at that point all the necessary components required by the smp kernel will be installed.
The smp kernel is the only one thats going to use both processors, so you need to get it and all pre-requisites installed.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2003 04:50 PM
тАО10-28-2003 04:50 PM
Re: Proliant 1850r Suse 8.2 Pro not using 2nd processor
The last answer was the way I ended up going. Funny, I lost track of this thread, and came on this solution on my own, then I came back here to close this out, and, sure enough, the last suggestion was the way to go.
What I ended up doign was botting of CD #1, choosing install, then "upgrade", while making sure I chose "k_smp" (instead of default kernel (ie: "k_dftl")). It went through, and literaly, three minutes later I was up and running again, perfectly, on both CPU's. I then ran YaST to patch to the most recent kernel, that went straight through, and all is well.
Thanks again.