Re: installing 6.1 on Compaq Proliant 5000
- Original Message - From: Lee Shackelford [EMAIL PROTECTED] To: Ted Mittelstaedt [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Monday, September 11, 2006 9:23 AM Subject: Re: installing 6.1 on Compaq Proliant 5000 Good morning, Mr. Mittelstaedt. Again, many thanks for your response to my question. My original purpose in purchasing the computer was to install multiple operating systems for hobbyist purpose. The computer's major selling point was that it has five hard drives. My original idea was to install a different operating system on each one. When I discovered that it had the rather sophisticated RAID-5 system implemented in hardware, I discarded that idea in favor of partitioning the hard drive to install the operating systems. The next operating system that I wanted after Windows Server 2000, with which it came equipped was FreeBSD. This project has become painfully involved, first of all, because I did not understand the fact, documented nowhere, that the BIOS of a computer intended to be a server is totally different from the BIOS of a computer intended to be a workstation. With experience, and with information eventually traded across the internet from other computer enthusiasts trying to do the same thing, I have eventually gained enough understanding of the BIOS to proceed. OK, you bought the computer to install operating systems on to do - what? Seems to me you wanted to install them to LEARN. Well, a computer OS is an integral part of the computer - like ying and yang, each requires the other. How exactly did you think that you were going to be able to learn anything whatsoever of value about an operating system by completely ignoring the hardware it was running on? Seems to me your money has been well spent on training. I'm sorry if the training isn't teaching you things that you think you thought you needed to know. But guess what, life is like that. Let me put it another way. If I needed to hire someone to install a Windows server, which would be a better choice? Someone who actually knows that server BIOS's are somewhat different than Workstation BIOSES? Someone who has actually installed a server OS and solved problems with getting it to work on hardware they are unfamiliar with? Or, some newly-minted MSCSE who has only installed Windows on his desktop computer, but by golly, knows all the definitions in the Microsoft literature? Think about it. The process has also been stymied by the fact that the developers of the boot program for sysinstall have failed, even in its latest edition, to install in BOOT the necessary features to read the output of a Compaq server BIOS, in particular the ability to correctly interpret the size of memory. The developers know all about the Compaq issues. Those are first of all solved in the latest Compaq BIOSES that ship with the current HP/Compaq servers. Secondly, there's workarounds. Thirdly, Compaq did it wrong back then. What good reason do we want to break sysinstall to have it do things the wrong way, so that it can work with old Compaq gear? Thanks to you, other respondents, and experience, I feel that I now have a grip of that issue. My latest problem stems from the fact that I had intended to install a portion of the BSD operating system in a primary Windows partition (BSD slice) below the 1024 cylinder limit, and the rest of it in a larger Windows logical partition within the extended partition, above 1024 cylinders. You need to throw most of this cylinder nonsense out the window it is meaningless to any OS that will run on that hardware, with the exception of DOS. Even though the handbook, as well as several other documents, clearly states that the operating system cannot be loaded into a logical partition, the implication of that statement did not register in my brain until I tried to do it. More learning that a lot of more advanced techs than you still don't understand. I wonder if system designers realize the extent to which the requirements that the entire system, or at least the boot BSD partition be loaded below 1024 cylinders, and the requirement that the operating system not be loaded into the extended Windows partition are in conflict in a multiple operating system environment. They do. They don't care. Multiple boot systems are for the birds. Mostly what happens is that people load multiple OS's on a system, intending to use all of them, then discover 3-4 months into it that it's too much of a PIA to keep rebooting all the time to get into a different system, and end up spending all their time in one system. If you really want multiple OS, buy multiple computers and plug them into a single console with a KVM switch. Much more practical. But, by all means, do it anyway, you probably won't really understand what I mean when I say they are for the birds until you have experienced a multiboot system. One again, more learning. Some
Re: installing 6.1 on Compaq Proliant 5000
Good morning, Mr. Mittelstaedt. Again, many thanks for your response to my question. My original purpose in purchasing the computer was to install multiple operating systems for hobbyist purpose. The computer's major selling point was that it has five hard drives. My original idea was to install a different operating system on each one. When I discovered that it had the rather sophisticated RAID-5 system implemented in hardware, I discarded that idea in favor of partitioning the hard drive to install the operating systems. The next operating system that I wanted after Windows Server 2000, with which it came equipped was FreeBSD. This project has become painfully involved, first of all, because I did not understand the fact, documented nowhere, that the BIOS of a computer intended to be a server is totally different from the BIOS of a computer intended to be a workstation. With experience, and with information eventually traded across the internet from other computer enthusiasts trying to do the same thing, I have eventually gained enough understanding of the BIOS to proceed. The process has also been stymied by the fact that the developers of the boot program for sysinstall have failed, even in its latest edition, to install in BOOT the necessary features to read the output of a Compaq server BIOS, in particular the ability to correctly interpret the size of memory. Thanks to you, other respondents, and experience, I feel that I now have a grip of that issue. My latest problem stems from the fact that I had intended to install a portion of the BSD operating system in a primary Windows partition (BSD slice) below the 1024 cylinder limit, and the rest of it in a larger Windows logical partition within the extended partition, above 1024 cylinders. Even though the handbook, as well as several other documents, clearly states that the operating system cannot be loaded into a logical partition, the implication of that statement did not register in my brain until I tried to do it. I wonder if system designers realize the extent to which the requirements that the entire system, or at least the boot BSD partition be loaded below 1024 cylinders, and the requirement that the operating system not be loaded into the extended Windows partition are in conflict in a multiple operating system environment. Some documentation says that the 1024 cylinder limit does not apply in many cases, but it never says when it applies and when it does not apply. I feel, that to make this system work, I will have to use some type of exotic partition manager such as Ranish or XOSL that can create a large number of primary partitions. I had originally wished to stick with GNU tools such as parted and grub. I realize my explanation is a bit long winded, but I hope it clarifies my goals. Yours truly, Lee Shackelford Ted Mittelstaedt [EMAIL PROTECTED] To o.comfreebsd-questions@freebsd.org, Lee Shackelford 09/06/2006 11:07 [EMAIL PROTECTED] PM cc Subject Re: installing 6.1 on Compaq Proliant 5000 This isn't unusual, it happens with certain array cards. If the disk drivers of each different operating system don't agree in how the disk is laid out that the intelligent driver array controller presents to them, then your screwed - you cannot use the array card for a multi-boot system. Sometimes you can get away with it by installing FreeBSD on part of the disk, and a subsequent disk driver will see the FreeBSD partition and understand not to overwrite it. But, sometimes not. It strikes me that Win 2003 Server is going to run dogpile slow, I simply cannot fathom why you want to multiboot this system in the first place. The only OS's that are going to run worth a damn on it are Linux and FreeBSD, and you just need to pick one or the other. Ted PS: You do understand
Re: installing 6.1 on Compaq Proliant 5000
This isn't unusual, it happens with certain array cards. If the disk drivers of each different operating system don't agree in how the disk is laid out that the intelligent driver array controller presents to them, then your screwed - you cannot use the array card for a multi-boot system. Sometimes you can get away with it by installing FreeBSD on part of the disk, and a subsequent disk driver will see the FreeBSD partition and understand not to overwrite it. But, sometimes not. It strikes me that Win 2003 Server is going to run dogpile slow, I simply cannot fathom why you want to multiboot this system in the first place. The only OS's that are going to run worth a damn on it are Linux and FreeBSD, and you just need to pick one or the other. Ted PS: You do understand the difference between FreeBSD slices, FreeBSD partitions, and IBM/BIOS partitions don't you? That is your not doing something incorrect like trying to install another OS within a FreeBSD logical slice - Original Message - From: Lee Shackelford [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Wednesday, September 06, 2006 10:00 AM Subject: installing 6.1 on Compaq Proliant 5000 Initial message posted on 8/24/2006: Good morning dear FreeBSD enthusiasts. I am attempting to install FreeBSD 6.1 on a Compaq Proliant 5000. The computer is equipped with four Pentium Pro processors clocked at 200 mhz and with a Smart 2/P hardware-RAID array. The BIOS indicates that the first two processors have failed. They are actually okay, but there is something wrong with their socket on the motherboard... Current message: Thank you to the two people who responded to my original message. With their help, I have progressed to the point of specifying the slice into which I want the system installed. There are three primary slices on this computer, plus one extended slice. The three primary slices all end within the 1024 cylinder limit. The two primary slices that do not contain FreeBSD are reserved for the installation of other operating systems. I wish to place the swap slice/partition in the extended slice. The fdisk program supplied with FreeBSD sees all of the extended slice as one slice, and does not seem to be able to see the logical slices within it. Most of my 15 gb. drive is in the extended slice. Does anyone know how to solve this problem? All suggestions are appreciated. Yours truly, Lee Shackelford ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
installing 6.1 on Compaq Proliant 5000
Initial message posted on 8/24/2006: Good morning dear FreeBSD enthusiasts. I am attempting to install FreeBSD 6.1 on a Compaq Proliant 5000. The computer is equipped with four Pentium Pro processors clocked at 200 mhz and with a Smart 2/P hardware-RAID array. The BIOS indicates that the first two processors have failed. They are actually okay, but there is something wrong with their socket on the motherboard... Current message: Thank you to the two people who responded to my original message. With their help, I have progressed to the point of specifying the slice into which I want the system installed. There are three primary slices on this computer, plus one extended slice. The three primary slices all end within the 1024 cylinder limit. The two primary slices that do not contain FreeBSD are reserved for the installation of other operating systems. I wish to place the swap slice/partition in the extended slice. The fdisk program supplied with FreeBSD sees all of the extended slice as one slice, and does not seem to be able to see the logical slices within it. Most of my 15 gb. drive is in the extended slice. Does anyone know how to solve this problem? All suggestions are appreciated. Yours truly, Lee Shackelford ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installing 6.1 on Compaq Proliant 5000
Give it up. First, you need to set Windows or DOS in the BIOS setting not SCO. SCO sets up the SMP table all wrong. that should also fix the mem reporting problem. But the big problem is that the ida driver crapped up support for EISA cards some time ago. I keep meaning to setup a test Proliant and bug the ida driver author to fix it, but I have never got round tuit. If you can find a PCI compaq raid card you might get somewhere. Ted - Original Message - From: Lee Shackelford [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Thursday, August 24, 2006 10:27 AM Subject: installing 6.1 on Compaq Proliant 5000 Good morning dear FreeBSD enthusiasts. I am attempting to install FreeBSD 6.1 on a Compaq Proliant 5000. The computer is equipped with four Pentium Pro processors clocked at 200 mhz and with a Smart 2/P hardware-RAID array. The BIOS indicates that the first two processors have failed. They are actually okay, but there is something wrong with their socket on the motherboard. The following sequence is being quoted from human memory. I ran SmartStart with the request to install S.C.O. OpenUnix. Of the operating systems supported by SmartStart, this one sounded the most similar to FreeBSD. Then I rebooted with the CD containing FreeBSD 6.1 in the SCSI CD-ROM reader. To my surprise, the computer booted off of the CD-ROM. Initially, the screen displayed in black-and-white. When a list box appeared, I entered the request for a command prompt. The monitor immediately displayed a command prompt. I entered the following commands: load ida load sym set Hint.acpi.0.disabled=1 set Hw.physmem=1048576K boot The fourth command was entered because the boot program does not correctly interpret the memory size from the information transferred to it from the BIOS. Then a lengthy list of device drivers either installed, or failed-to-install, scrolled down the face of the monitor, still in black-and-white. Then the screen displayed a blue background, and a colored message appeared saying probing for devices. Then it displayed a message to choose a country code. The display delayed response to keyboard entries by two minutes or more for each keystroke. I selected United States. Several minutes later, the list box disappeared, and screen became blank blue. One-half hour later, another list box displayed which gave the user choices of the type of install desired. There was absolutely no response on the screen to any keyboard entry. What am I doing wrong? Any and all suggestions will be appreciated. Yours truly, Lee ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
installing 6.1 on Compaq Proliant 5000
Good morning dear FreeBSD enthusiasts. I am attempting to install FreeBSD 6.1 on a Compaq Proliant 5000. The computer is equipped with four Pentium Pro processors clocked at 200 mhz and with a Smart 2/P hardware-RAID array. The BIOS indicates that the first two processors have failed. They are actually okay, but there is something wrong with their socket on the motherboard. The following sequence is being quoted from human memory. I ran SmartStart with the request to install S.C.O. OpenUnix. Of the operating systems supported by SmartStart, this one sounded the most similar to FreeBSD. Then I rebooted with the CD containing FreeBSD 6.1 in the SCSI CD-ROM reader. To my surprise, the computer booted off of the CD-ROM. Initially, the screen displayed in black-and-white. When a list box appeared, I entered the request for a command prompt. The monitor immediately displayed a command prompt. I entered the following commands: load ida load sym set Hint.acpi.0.disabled=1 set Hw.physmem=1048576K boot The fourth command was entered because the boot program does not correctly interpret the memory size from the information transferred to it from the BIOS. Then a lengthy list of device drivers either installed, or failed-to-install, scrolled down the face of the monitor, still in black-and-white. Then the screen displayed a blue background, and a colored message appeared saying probing for devices. Then it displayed a message to choose a country code. The display delayed response to keyboard entries by two minutes or more for each keystroke. I selected United States. Several minutes later, the list box disappeared, and screen became blank blue. One-half hour later, another list box displayed which gave the user choices of the type of install desired. There was absolutely no response on the screen to any keyboard entry. What am I doing wrong? Any and all suggestions will be appreciated. Yours truly, Lee ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem RESOLVED
On Wed, 2005-08-31 at 17:26, Robert Slade wrote: On Wed, 2005-08-31 at 00:21, Vizion wrote: On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: On Tue, 2005-08-30 at 21:20, Vizion wrote: On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: On Tue, 2005-08-30 at 20:10, Vizion wrote: On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to the dialogue on- Proliant 5000 sever Fbsd 5.4 (re)boot problem: Hiya, I've been working on this beasty on and off for some time. It's a Quad processor 1 Gbyte of memory and 5 scsi drives using the 2p raid controller setup as 2 raid arrays + 1 spare. The machine works fine with 5.4 release #0 with the supplied generic kernel. The problem(s) I have been having are: 1. When I recompiled the Kernel with SMP support, I get random reboots. It also fails to boot sometimes failing at the point after waiting for the scsi drives to settle. I get some error codes and Fbsd fails to find the boot device. 2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP support. This does to boot at all. It gets as far as the waiting 15s for scsi devices to settle, then (appears to) reset the scsi controller and immediately tries to access the drives (does not wait). I have tried recompiling with scsi_delay set to 3 (30s) with no change. I have checked dmesg and message logs but there is nothing related to the problem(s) there. I have gone back to the 5.4 release #0 single processor kernel for now which is a shame as the machine is slow without the multi processor support. The only thing out of the ordinary I have noted is a tx underunn -- increasing threshold to 512 bytes message which appears related to running kde remotely via vncserver and tinync. Any ideas, I can send conf files etc if needed. Thanks Rob What are your bios setting? My guess is that you have not made the right setting using the siftware and configuration utilities david David, Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk geometry) and the machine passes all the diagnostics. Rob I cannot remember - but I have sneaking notion that you need to set it as linux Tried that too :-). I think that the problem is that with 5.4 release #2 it is trying to access that scsi drives immediately then inducing the kernel panic for 15s. Rather than inducing the panic 1st. Rob Did you follow my suggestion and search the HP resources with freebsd and your model. I have had the same problem myself I am pretty certain it was fixed by changes using the Proliant Essrntial Foundation Pack.. but my memory may not be accurate. david David, I did update the system and controller ROMs whne the machine was running windows. I have been on the HP site and as far as I can tell I have the latest. Rob For the record, lucking under SCO Unix is an update to the Raid Controller firmware which fixes the problem. You do need Dos or Windows to create the self booting disks. Only disk 1 is needed for the SMART 2P controller. The update appears to be only listed under SC Unix though. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Proliant 5000 sever Fbsd 5.4 (re)boot problem
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Vizion Sent: Tuesday, August 30, 2005 4:21 PM To: freebsd-questions@freebsd.org Cc: Robert Slade Subject: Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem Did you follow my suggestion and search the HP resources with freebsd and your model. I have had the same problem myself I am pretty certain it was fixed by changes using the Proliant Essrntial Foundation Pack.. but my memory may not be accurate. Yeah, what a awful design! You have to load an entire full-blown Windows install just to update the microcode in the SCSI raid controller. I saw they had done this the last time I setup a Compaq server and nearly barfed. You can still firmware update the machines' BIOS with a bootable floppy but that's it. To get anything else, helo Windows! At least you get the satisfaction of scratching it off once you've done the update. Ted -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.10.17/85 - Release Date: 8/30/2005 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Wed, 2005-08-31 at 07:01, Ted Mittelstaedt wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Vizion Sent: Tuesday, August 30, 2005 4:21 PM To: freebsd-questions@freebsd.org Cc: Robert Slade Subject: Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem Did you follow my suggestion and search the HP resources with freebsd and your model. I have had the same problem myself I am pretty certain it was fixed by changes using the Proliant Essrntial Foundation Pack.. but my memory may not be accurate. Yeah, what a awful design! You have to load an entire full-blown Windows install just to update the microcode in the SCSI raid controller. I saw they had done this the last time I setup a Compaq server and nearly barfed. You can still firmware update the machines' BIOS with a bootable floppy but that's it. To get anything else, helo Windows! At least you get the satisfaction of scratching it off once you've done the update. Ted -- Thanks Ted David, The HP site does not turn up anything about FreeBSD and the Proliant. However I have found out that the Smart-2 family controllers do have an update. There is a Linux version of the flash utility so I'll try that first. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Wed, 2005-08-31 at 00:21, Vizion wrote: On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: On Tue, 2005-08-30 at 21:20, Vizion wrote: On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: On Tue, 2005-08-30 at 20:10, Vizion wrote: On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to the dialogue on- Proliant 5000 sever Fbsd 5.4 (re)boot problem: Hiya, I've been working on this beasty on and off for some time. It's a Quad processor 1 Gbyte of memory and 5 scsi drives using the 2p raid controller setup as 2 raid arrays + 1 spare. The machine works fine with 5.4 release #0 with the supplied generic kernel. The problem(s) I have been having are: 1. When I recompiled the Kernel with SMP support, I get random reboots. It also fails to boot sometimes failing at the point after waiting for the scsi drives to settle. I get some error codes and Fbsd fails to find the boot device. 2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP support. This does to boot at all. It gets as far as the waiting 15s for scsi devices to settle, then (appears to) reset the scsi controller and immediately tries to access the drives (does not wait). I have tried recompiling with scsi_delay set to 3 (30s) with no change. I have checked dmesg and message logs but there is nothing related to the problem(s) there. I have gone back to the 5.4 release #0 single processor kernel for now which is a shame as the machine is slow without the multi processor support. The only thing out of the ordinary I have noted is a tx underunn -- increasing threshold to 512 bytes message which appears related to running kde remotely via vncserver and tinync. Any ideas, I can send conf files etc if needed. Thanks Rob What are your bios setting? My guess is that you have not made the right setting using the siftware and configuration utilities david David, Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk geometry) and the machine passes all the diagnostics. Rob I cannot remember - but I have sneaking notion that you need to set it as linux Tried that too :-). I think that the problem is that with 5.4 release #2 it is trying to access that scsi drives immediately then inducing the kernel panic for 15s. Rather than inducing the panic 1st. Rob Did you follow my suggestion and search the HP resources with freebsd and your model. I have had the same problem myself I am pretty certain it was fixed by changes using the Proliant Essrntial Foundation Pack.. but my memory may not be accurate. david David, I did update the system and controller ROMs whne the machine was running windows. I have been on the HP site and as far as I can tell I have the latest. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Proliant 5000 sever Fbsd 5.4 (re)boot problem
Hiya, I've been working on this beasty on and off for some time. It's a Quad processor 1 Gbyte of memory and 5 scsi drives using the 2p raid controller setup as 2 raid arrays + 1 spare. The machine works fine with 5.4 release #0 with the supplied generic kernel. The problem(s) I have been having are: 1. When I recompiled the Kernel with SMP support, I get random reboots. It also fails to boot sometimes failing at the point after waiting for the scsi drives to settle. I get some error codes and Fbsd fails to find the boot device. 2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP support. This does to boot at all. It gets as far as the waiting 15s for scsi devices to settle, then (appears to) reset the scsi controller and immediately tries to access the drives (does not wait). I have tried recompiling with scsi_delay set to 3 (30s) with no change. I have checked dmesg and message logs but there is nothing related to the problem(s) there. I have gone back to the 5.4 release #0 single processor kernel for now which is a shame as the machine is slow without the multi processor support. The only thing out of the ordinary I have noted is a tx underunn -- increasing threshold to 512 bytes message which appears related to running kde remotely via vncserver and tinync. Any ideas, I can send conf files etc if needed. Thanks Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to the dialogue on- Proliant 5000 sever Fbsd 5.4 (re)boot problem: Hiya, I've been working on this beasty on and off for some time. It's a Quad processor 1 Gbyte of memory and 5 scsi drives using the 2p raid controller setup as 2 raid arrays + 1 spare. The machine works fine with 5.4 release #0 with the supplied generic kernel. The problem(s) I have been having are: 1. When I recompiled the Kernel with SMP support, I get random reboots. It also fails to boot sometimes failing at the point after waiting for the scsi drives to settle. I get some error codes and Fbsd fails to find the boot device. 2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP support. This does to boot at all. It gets as far as the waiting 15s for scsi devices to settle, then (appears to) reset the scsi controller and immediately tries to access the drives (does not wait). I have tried recompiling with scsi_delay set to 3 (30s) with no change. I have checked dmesg and message logs but there is nothing related to the problem(s) there. I have gone back to the 5.4 release #0 single processor kernel for now which is a shame as the machine is slow without the multi processor support. The only thing out of the ordinary I have noted is a tx underunn -- increasing threshold to 512 bytes message which appears related to running kde remotely via vncserver and tinync. Any ideas, I can send conf files etc if needed. Thanks Rob What are your bios setting? My guess is that you have not made the right setting using the siftware and configuration utilities david -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tue, 2005-08-30 at 20:10, Vizion wrote: On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to the dialogue on- Proliant 5000 sever Fbsd 5.4 (re)boot problem: Hiya, I've been working on this beasty on and off for some time. It's a Quad processor 1 Gbyte of memory and 5 scsi drives using the 2p raid controller setup as 2 raid arrays + 1 spare. The machine works fine with 5.4 release #0 with the supplied generic kernel. The problem(s) I have been having are: 1. When I recompiled the Kernel with SMP support, I get random reboots. It also fails to boot sometimes failing at the point after waiting for the scsi drives to settle. I get some error codes and Fbsd fails to find the boot device. 2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP support. This does to boot at all. It gets as far as the waiting 15s for scsi devices to settle, then (appears to) reset the scsi controller and immediately tries to access the drives (does not wait). I have tried recompiling with scsi_delay set to 3 (30s) with no change. I have checked dmesg and message logs but there is nothing related to the problem(s) there. I have gone back to the 5.4 release #0 single processor kernel for now which is a shame as the machine is slow without the multi processor support. The only thing out of the ordinary I have noted is a tx underunn -- increasing threshold to 512 bytes message which appears related to running kde remotely via vncserver and tinync. Any ideas, I can send conf files etc if needed. Thanks Rob What are your bios setting? My guess is that you have not made the right setting using the siftware and configuration utilities david David, Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk geometry) and the machine passes all the diagnostics. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tue, 2005-08-30 at 21:20, Vizion wrote: On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: On Tue, 2005-08-30 at 20:10, Vizion wrote: On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to the dialogue on- Proliant 5000 sever Fbsd 5.4 (re)boot problem: Hiya, I've been working on this beasty on and off for some time. It's a Quad processor 1 Gbyte of memory and 5 scsi drives using the 2p raid controller setup as 2 raid arrays + 1 spare. The machine works fine with 5.4 release #0 with the supplied generic kernel. The problem(s) I have been having are: 1. When I recompiled the Kernel with SMP support, I get random reboots. It also fails to boot sometimes failing at the point after waiting for the scsi drives to settle. I get some error codes and Fbsd fails to find the boot device. 2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP support. This does to boot at all. It gets as far as the waiting 15s for scsi devices to settle, then (appears to) reset the scsi controller and immediately tries to access the drives (does not wait). I have tried recompiling with scsi_delay set to 3 (30s) with no change. I have checked dmesg and message logs but there is nothing related to the problem(s) there. I have gone back to the 5.4 release #0 single processor kernel for now which is a shame as the machine is slow without the multi processor support. The only thing out of the ordinary I have noted is a tx underunn -- increasing threshold to 512 bytes message which appears related to running kde remotely via vncserver and tinync. Any ideas, I can send conf files etc if needed. Thanks Rob What are your bios setting? My guess is that you have not made the right setting using the siftware and configuration utilities david David, Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk geometry) and the machine passes all the diagnostics. Rob I cannot remember - but I have sneaking notion that you need to set it as linux Tried that too :-). I think that the problem is that with 5.4 release #2 it is trying to access that scsi drives immediately then inducing the kernel panic for 15s. Rather than inducing the panic 1st. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: On Tue, 2005-08-30 at 21:20, Vizion wrote: On Tuesday 30 August 2005 13:22, the author Robert Slade contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: On Tue, 2005-08-30 at 20:10, Vizion wrote: On Tuesday 30 August 2005 12:05, the author Robert Slade contributed to the dialogue on- Proliant 5000 sever Fbsd 5.4 (re)boot problem: Hiya, I've been working on this beasty on and off for some time. It's a Quad processor 1 Gbyte of memory and 5 scsi drives using the 2p raid controller setup as 2 raid arrays + 1 spare. The machine works fine with 5.4 release #0 with the supplied generic kernel. The problem(s) I have been having are: 1. When I recompiled the Kernel with SMP support, I get random reboots. It also fails to boot sometimes failing at the point after waiting for the scsi drives to settle. I get some error codes and Fbsd fails to find the boot device. 2. I CVSuped to 5.4 release #2 and recompiled the Kernel with SMP support. This does to boot at all. It gets as far as the waiting 15s for scsi devices to settle, then (appears to) reset the scsi controller and immediately tries to access the drives (does not wait). I have tried recompiling with scsi_delay set to 3 (30s) with no change. I have checked dmesg and message logs but there is nothing related to the problem(s) there. I have gone back to the 5.4 release #0 single processor kernel for now which is a shame as the machine is slow without the multi processor support. The only thing out of the ordinary I have noted is a tx underunn -- increasing threshold to 512 bytes message which appears related to running kde remotely via vncserver and tinync. Any ideas, I can send conf files etc if needed. Thanks Rob What are your bios setting? My guess is that you have not made the right setting using the siftware and configuration utilities david David, Thanks. The BIOS setting appear ok - OS type is set as UNIX (Small disk geometry) and the machine passes all the diagnostics. Rob I cannot remember - but I have sneaking notion that you need to set it as linux Tried that too :-). I think that the problem is that with 5.4 release #2 it is trying to access that scsi drives immediately then inducing the kernel panic for 15s. Rather than inducing the panic 1st. Rob Did you follow my suggestion and search the HP resources with freebsd and your model. I have had the same problem myself I am pretty certain it was fixed by changes using the Proliant Essrntial Foundation Pack.. but my memory may not be accurate. david ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem
On Tuesday 30 August 2005 16:21, the author Vizion contributed to the dialogue on- Re: Proliant 5000 sever Fbsd 5.4 (re)boot problem: On Tuesday 30 August 2005 13:31, the author Robert Slade contributed to the dialogue on- Is this any use: http://ezine.daemonnews.org/23/cpqraid.html -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Proliant 5000
-Original Message- From: Greg 'groggy' Lehey [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 10:09 PM To: Ted Mittelstaedt Cc: Brad; Lowell Gilbert; freebsd-questions@FreeBSD.org Subject: Re: Proliant 5000 4 X 200MHz processors. 512Mb RAM Scsi hardware raid controller. That may be your problem. Depends on the RAID controller. Both my machines have RAID controllers (2DH). See http://www.lemis.com/grog/diary-dec2004.html#10: it seems that 5.1 panicked. I'm pretty sure I had no trouble with 5.3, though. If the system has an EISA raid array card you cannot install FreeBSD on it. There is a bug in the compaq raid driver it won't work on eisa. I don't think these machines are *that* old. Greg, yes they are. Here's a writeup on the 5000: http://www.winnetmag.com/Windows/Article/ArticleID/159/159.html Brand new these were $60K according to the article. It's pretty good example of hardware depreciation that something that currently sells for $50 on the used market: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemcategory=56106item=5747562 471rd=1 once cost $60K. Incidentally, if you have a copy of Solaris 2.5.1 x86 around, these still make nice little servers - if you are willing to spend the 20+ hours or so needed to install Solaris+patches+gcc+whateveryouwanttorun. If he has an EISA raid card in there he can replace it with one of these: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemcategory=56091item=5747208 198rd=1 which will probably boot FreeBSD just fine. Brad, incidentally, I understand that the Linux driver for the Compaq smart array card does speak to the EISA cards, so if you just absolutely don't want to put any more money into this, you can try Linux on it. I don't mean to send you away, that auction lists $4 for the raid card that should work. But I do understand that there are folks who wouldn't even spend the $4. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 5000
[Format recovered--see http://www.lemis.com/email/email-format.html] On Tuesday, 1 February 2005 at 21:54:18 -0800, Ted Mittelstaedt wrote: 4 X 200MHz processors. 512Mb RAM Scsi hardware raid controller. That may be your problem. Depends on the RAID controller. Both my machines have RAID controllers (2DH). See http://www.lemis.com/grog/diary-dec2004.html#10: it seems that 5.1 panicked. I'm pretty sure I had no trouble with 5.3, though. If the system has an EISA raid array card you cannot install FreeBSD on it. There is a bug in the compaq raid driver it won't work on eisa. I don't think these machines are *that* old. Greg, yes they are. Here's a writeup on the 5000: http://www.winnetmag.com/Windows/Article/ArticleID/159/159.html Yes, this is about the age I was expecting. The specs are pretty close to my 6500. I didn't realize, that the older RAID cards were EISA, but it's not clear from the article whether they were shipped with the 5000. If he has an EISA raid card in there he can replace it with one of these: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemcategory=56091item=5747208198rd=1 which will probably boot FreeBSD just fine. Definitely. This is the 2DH I'm referring to above. I don't mean to send you away, that auction lists $4 for the raid card that should work. But I do understand that there are folks who wouldn't even spend the $4. Look at the shipping costs. That's another $13 before you get started. Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html See complete headers for address and phone numbers. pgpYKHMasL7rE.pgp Description: PGP signature
RE: Proliant 5000
Greg 'groggy' Lehey wrote: http://www.winnetmag.com/Windows/Article/ArticleID/159/159.html Yes, this is about the age I was expecting. The specs are pretty close to my 6500. I didn't realize, that the older RAID cards were EISA, but it's not clear from the article whether they were shipped with the 5000. No it isn't clear - thing is though that most of those servers were sold by VARS (the sister company of the ISP I work at used to be a Compaq VAR and now is an HP VAR) and there was no default factory configuration because the VAR was supposed to analyze the customer's network and quote the appropriate parts. Unfortunately however as you might have guessed the PCI cards were at least a grand more than the EISA cards and so customers being customers, far too many of these were quoted and built with the cheaper EISA card. Many also were upgrade sales of older Compaq 4500's and they just sold the chassis and cpu's and ram, and moved the disks and raid card wholesale from one to the other. If he has an EISA raid card in there he can replace it with one of these: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemcategory=56091it em=5747208198rd=1 Look at the shipping costs. That's another $13 before you get started. Damn, there goes the pizza money... :-) And to think I actually bought a CGI card back in 1985 for $50!!! Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Proliant 5000
-Original Message- From: Ted Mittelstaedt [mailto:[EMAIL PROTECTED] Sent: February 2, 2005 12:37 AM To: Greg 'groggy' Lehey Cc: Brad; Lowell Gilbert; freebsd-questions@FreeBSD.org Subject: RE: Proliant 5000 Greg 'groggy' Lehey wrote: http://www.winnetmag.com/Windows/Article/ArticleID/159/159.html Yes, this is about the age I was expecting. The specs are pretty close to my 6500. I didn't realize, that the older RAID cards were EISA, but it's not clear from the article whether they were shipped with the 5000. No it isn't clear - thing is though that most of those servers were sold by VARS (the sister company of the ISP I work at used to be a Compaq VAR and now is an HP VAR) and there was no default factory configuration because the VAR was supposed to analyze the customer's network and quote the appropriate parts. Unfortunately however as you might have guessed the PCI cards were at least a grand more than the EISA cards and so customers being customers, far too many of these were quoted and built with the cheaper EISA card. Many also were upgrade sales of older Compaq 4500's and they just sold the chassis and cpu's and ram, and moved the disks and raid card wholesale from one to the other. If he has an EISA raid card in there he can replace it with one of these: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemcategory=56091it em=5747208198rd=1 Look at the shipping costs. That's another $13 before you get started. Damn, there goes the pizza money... :-) And to think I actually bought a CGI card back in 1985 for $50!!! Ted Hi, sorry for being out of touch for the day (or so...) The computer has a Smart Array 2DH card. It is in fact PCI based so now I don't know what to do. First however, I think I will try a different slot And see if that does something. Then I do have a different array controller And will try that one. Thanks for the great info and of course, if anyone has an idea, please give me An e-mail. Brad ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 5000
[Format recovered--see http://www.lemis.com/email/email-format.html] I'm really puzzled how the quotation levels got the way they were. On Wednesday, 2 February 2005 at 1:00:20 -0600, Brad wrote: On February 2, 2005 12:37 AM, Ted Mittelstaedt wrote: Greg 'groggy' Lehey wrote: http://www.winnetmag.com/Windows/Article/ArticleID/159/159.html Yes, this is about the age I was expecting. The specs are pretty close to my 6500. I didn't realize, that the older RAID cards were EISA, but it's not clear from the article whether they were shipped with the 5000. No it isn't clear - thing is though that most of those servers were sold by VARS (the sister company of the ISP I work at used to be a Compaq VAR and now is an HP VAR) and there was no default factory configuration because the VAR was supposed to analyze the customer's network and quote the appropriate parts. Unfortunately however as you might have guessed the PCI cards were at least a grand more than the EISA cards and so customers being customers, far too many of these were quoted and built with the cheaper EISA card. Many also were upgrade sales of older Compaq 4500's and they just sold the chassis and cpu's and ram, and moved the disks and raid card wholesale from one to the other. If he has an EISA raid card in there he can replace it with one of these: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemcategory=56091item=5747208198rd=1 Look at the shipping costs. That's another $13 before you get started. Damn, there goes the pizza money... :-) Hi, sorry for being out of touch for the day (or so...) The computer has a Smart Array 2DH card. As I mentioned a couple of times, this is the card I'm using. It's also the one in the (repeatedly broken) URL above. It is in fact PCI based so now I don't know what to do. First however, I think I will try a different slot And see if that does something. Then I do have a different array controller And will try that one. Do you have a 4.10 CD available? That's what I used for installation. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpCep9z8JIDA.pgp Description: PGP signature
Re: Proliant 5000
Brad [EMAIL PROTECTED] writes: Hi, I have recently acquired a Proliant 800 and a Proliant 5000 server. The 800 installed quite cleanly and is currently running FreeBSD 5.3 The 800 is a dual processor machine. When I try to install FreeBSD 5.3 on the 5000 (it's a quad processor machine ) it panic's saying, panic: pmtimer_indentify Has anyone seen this before. As near as I can tell it involves the power management of the computer. Only there isn't any in the bios. Doing a verbose logging on the system I noticed that it has just finished scanning the ISA bus and found nothing. Then it panic's. I would appreciate any thoughts that the community might have. Have you tried turning off ACPI in the install? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 5000
[Format recovered--see http://www.lemis.com/email/email-format.html] Gratuitous line breaks removed. On Sunday, 30 January 2005 at 19:36:32 -0600, Brad wrote: Hi, I have recently acquired a Proliant 800 and a Proliant 5000 server. The 800 installed quite cleanly and is currently running FreeBSD 5.3 The 800 is a dual processor machine. When I try to install FreeBSD 5.3 on the 5000 (it's a quad processor machine ) it panic's saying, panic: pmtimer_indentify Has anyone seen this before. No. I've installed on a ProLiant 850 (dual processor) and 6500 (quad processor) with spectacular lack of problems. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgphRqRhZlpQF.pgp Description: PGP signature
RE: Proliant 5000
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lowell Gilbert Sent: January 31, 2005 8:13 AM To: Brad Cc: freebsd-questions@freebsd.org Subject: Re: Proliant 5000 Brad [EMAIL PROTECTED] writes: Hi, I have recently acquired a Proliant 800 and a Proliant 5000 server. The 800 installed quite cleanly and is currently running FreeBSD 5.3 The 800 is a dual processor machine. When I try to install FreeBSD 5.3 on the 5000 (it's a quad processor machine ) it panic's saying, panic: pmtimer_indentify Has anyone seen this before. As near as I can tell it involves the power management of the computer. Only there isn't any in the bios. Doing a verbose logging on the system I noticed that it has just finished scanning the ISA bus and found nothing. Then it panic's. I would appreciate any thoughts that the community might have. Have you tried turning off ACPI in the install? Ok, when I boot the menu has default and then the second choice is to install with ACPI turned on... Tried that one and it progresses just a tad further. It reports: Orm0: ISA Option ROMs at iomem 0xe8000-0xedfff,0xc8000-0xcbfff,0xc-0xc7fff on isa0 Pmtimer0 on isa0 Then the computer freezes at that point. What else could I tell you about this machine? 4 X 200MHz processors. 512Mb RAM Scsi hardware raid controller. 4 drives 2 x 9Gb and 2 X 4 Gb Safe mode just hung on the orm0: line. Starting to wonder if I have MB issues. The 4th menu item is to boot single user mode. This one hangs just as the default one does. Other interesting things I just noticed. Eisab0: PCI-EISA bridge at device 15.0 on pci0 Eisa0: EISA bus on eisab0 Isa0: ISA bus on eisab0 Pci0: memory, RAM at device 20.0 (no driver attached) Guess I am back to requesting thoughts again. Thank you to the people that have responded so far. Brad ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Proliant 5000
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brad Sent: Monday, January 31, 2005 5:30 PM To: 'Lowell Gilbert' Cc: freebsd-questions@freebsd.org Subject: RE: Proliant 5000 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lowell Gilbert Sent: January 31, 2005 8:13 AM To: Brad Cc: freebsd-questions@freebsd.org Subject: Re: Proliant 5000 Brad [EMAIL PROTECTED] writes: Hi, I have recently acquired a Proliant 800 and a Proliant 5000 server. The 800 installed quite cleanly and is currently running FreeBSD 5.3 The 800 is a dual processor machine. When I try to install FreeBSD 5.3 on the 5000 (it's a quad processor machine ) it panic's saying, panic: pmtimer_indentify Has anyone seen this before. As near as I can tell it involves the power management of the computer. Only there isn't any in the bios. Doing a verbose logging on the system I noticed that it has just finished scanning the ISA bus and found nothing. Then it panic's. I would appreciate any thoughts that the community might have. Have you tried turning off ACPI in the install? Ok, when I boot the menu has default and then the second choice is to install with ACPI turned on... Tried that one and it progresses just a tad further. It reports: Orm0: ISA Option ROMs at iomem 0xe8000-0xedfff,0xc8000-0xcbfff,0xc-0xc7fff on isa0 Pmtimer0 on isa0 Then the computer freezes at that point. What else could I tell you about this machine? 4 X 200MHz processors. 512Mb RAM Scsi hardware raid controller. That may be your problem. If the system has an EISA raid array card you cannot install FreeBSD on it. There is a bug in the compaq raid driver it won't work on eisa. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 5000
[Format recovered--see http://www.lemis.com/email/email-format.html] Quote indentation corrected. Trimmed. On Monday, 31 January 2005 at 21:16:03 -0800, Ted Mittelstaedt wrote: On Monday, January 31, 2005 5:30 PM, Brad wrote: On January 31, 2005 8:13 AM, Lowell Gilbert wrote: Brad [EMAIL PROTECTED] writes: Hi, I have recently acquired a Proliant 800 and a Proliant 5000 server. The 800 installed quite cleanly and is currently running FreeBSD 5.3 The 800 is a dual processor machine. When I try to install FreeBSD 5.3 on the 5000 (it's a quad processor machine ) it panic's saying, panic: pmtimer_indentify Has anyone seen this before. As near as I can tell it involves the power management of the computer. Only there isn't any in the bios. Doing a verbose logging on the system I noticed that it has just finished scanning the ISA bus and found nothing. Then it panic's. I would appreciate any thoughts that the community might have. Have you tried turning off ACPI in the install? Ok, when I boot the menu has default and then the second choice is to install with ACPI turned on... Tried that one and it progresses just a tad further. It reports: Orm0: ISA Option ROMs at iomem 0xe8000-0xedfff,0xc8000-0xcbfff,0xc-0xc7fff on isa0 Pmtimer0 on isa0 Then the computer freezes at that point. What else could I tell you about this machine? 4 X 200MHz processors. 512Mb RAM Scsi hardware raid controller. That may be your problem. Depends on the RAID controller. Both my machines have RAID controllers (2DH). See http://www.lemis.com/grog/diary-dec2004.html#10: it seems that 5.1 panicked. I'm pretty sure I had no trouble with 5.3, though. If the system has an EISA raid array card you cannot install FreeBSD on it. There is a bug in the compaq raid driver it won't work on eisa. I don't think these machines are *that* old. Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html See complete headers for address and phone numbers. pgpfDd6wZSe2S.pgp Description: PGP signature
Proliant 5000
Hi, I have recently acquired a Proliant 800 and a Proliant 5000 server. The 800 installed quite cleanly and is currently running FreeBSD 5.3 The 800 is a dual processor machine. When I try to install FreeBSD 5.3 on the 5000 (it's a quad processor machine ) it panic's saying, panic: pmtimer_indentify Has anyone seen this before. As near as I can tell it involves the power management of the computer. Only there isn't any in the bios. Doing a verbose logging on the system I noticed that it has just finished scanning the ISA bus and found nothing. Then it panic's. I would appreciate any thoughts that the community might have. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
