Re: Compaq Proliant 2500 - freebsd 5.1 install problems
Sounds very similar to a problem that I have with FreeBSD 5.1. As soon as /stand/sysinstall is started, the display adaptor turns off! This is on a Dell Poweredge 6350 with 4xXeon 550s. I never did get FreeBSD 5.x working on any of the 6350s that I have, but 4.8 works perfectly. Tom On Thu, 6 Nov 2003, Christer Solskogen wrote: I`m trying to get FreeBSD 5.1 installed, but sysinstall never shows. The last info I get is /stand/sysinstall running as init on vty0 and it stops. It dont do anything more. FreeBSD 4.8(and 4.9 i guess, havent tried yet) works. Any sollution? Btw, I have set the OS to be 'Other' in BIOS. -- Med vennlig hilsen / Best regards Christer Solskogen http://dtz.cjb.net - http://carebears.mine.nu Cheap, but not as cheap as your girlfriend! -Spider Jerusalem ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Compaq Proliant 2500 - freebsd 5.1 install problems
I`m trying to get FreeBSD 5.1 installed, but sysinstall never shows. The last info I get is /stand/sysinstall running as init on vty0 and it stops. It dont do anything more. FreeBSD 4.8(and 4.9 i guess, havent tried yet) works. Any sollution? Btw, I have set the OS to be 'Other' in BIOS. -- Med vennlig hilsen / Best regards Christer Solskogen http://dtz.cjb.net - http://carebears.mine.nu Cheap, but not as cheap as your girlfriend! -Spider Jerusalem ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ATAng errors on compaq proliant 330e
hi this verbosed dmesg is from my box maybe it help you have a nice day -- Archeologists near mount Sinai have discovered what is believed to be a missing page from the Bible. The page is currently being carbon dated in Bonn. If genuine it belongs at the beginning of the Bible and is believed to read To my darling Candy. All characters portrayed within this book are fictitous and any resemblance to persons living or dead is purely coincidental. The page has been universally condemned by church leaders. RED DWARF Series II Episode 2, Better Than Life - R 52D 0x15 3 4 5 7 10 11 14 15 slot 2 51A 0x10 3 4 5 7 10 11 14 15 slot 2 51B 0x11 3 4 5 7 10 11 14 15 slot 2 51C 0x12 3 4 5 7 10 11 14 15 slot 2 51D 0x12 3 4 5 7 10 11 14 15 slot 3 01A 0x16 3 4 5 7 10 11 14 15 slot 3 01B 0x17 3 4 5 7 10 11 14 15 slot 3 01C 0x18 3 4 5 7 10 11 14 15 slot 3 01D 0x19 3 4 5 7 10 11 14 15 slot 4 02A 0x1a 3 4 5 7 10 11 14 15 slot 4 02B 0x1b 3 4 5 7 10 11 14 15 slot 4 02C 0x1a 3 4 5 7 10 11 14 15 slot 4 02D 0x1b 3 4 5 7 10 11 14 15 slot 5 03A 0x1c 3 4 5 7 10 11 14 15 slot 5 03B 0x1d 3 4 5 7 10 11 14 15 slot 5 03C 0x1c 3 4 5 7 10 11 14 15 slot 5 03D 0x1d 3 4 5 7 10 11 14 15 slot 6 04A 0x1e 3 4 5 7 10 11 14 15 slot 6 04B 0x1f 3 4 5 7 10 11 14 15 slot 6 04C 0x1e 3 4 5 7 10 11 14 15 slot 6 04D 0x1f 3 4 5 7 10 11 14 15 AcpiOsDerivePciId: bus 0 dev 0 func 0 AcpiOsDerivePciId: bus 0 dev 0 func 1 unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported unknown: I/O range not supported ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.IBRG.SMIC] in namespace, AE_NOT_FOUND SearchNode 0xc2d39a40 StartNode 0xc2d39a40 ReturnNode 0 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.IBRG.KBD_._STA] (Node 0xc2d39a40), AE_NOT_FOUND ACPI-0438: *** Error: Looking up [\\_SB_.PCI0.IBRG.SMIC] in namespace, AE_NOT_FOUND SearchNode 0xc2d39980 StartNode 0xc2d39980 ReturnNode 0 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.IBRG.PS2M._STA] (Node 0xc2d39980), AE_NOT_FOUND acpi_timer0: 32-bit timer at 3.579545MHz port 0xf808-0xf80b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 initial configuration \\_SB_.LNK6 irq 10: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.1.0 \\_SB_.LNK7 irq 11: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.1.1 \\_SB_.LNK8 irq 5: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.1.2 \\_SB_.LNK9 irq 5: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.1.3 \\_SB_.LNKA irq 0: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.2.0 \\_SB_.LNKB irq 0: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.2.1 \\_SB_.LNKA irq 0: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.2.2 \\_SB_.LNKB irq 0: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.2.3 \\_SB_.LNKC irq 0: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.3.0 \\_SB_.LNKD irq 0: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.3.1 \\_SB_.LNKC irq 0: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.3.2 \\_SB_.LNKD irq 0: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.3.3 \\_SB_.LNKE irq 11: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.4.0 \\_SB_.LNKF irq 0: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.4.1 \\_SB_.LNKE irq 11: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.4.2 \\_SB_.LNKF irq 0: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.4.3 \\_SB_.LNKG irq 5: [ 3 4 5 7 10 11 14 15] low,level,sharable 0.15.0 before setting priority for links \\_SB_.LNKA: interrupts: 3 4 5 710111415 penalty: 2100 2100 1400 2100 1200 1400 11100 11100 references: 2 priority: 0 \\_SB_.LNKB: interrupts: 3 4 5 710111415 penalty: 2100 2100 1400 2100 1200 1400 11100 11100 references: 2 priority: 0 \\_SB_.LNKC: interrupts: 3 4 5 710111415
Re: ATAng errors on compaq proliant 330e
It seems Radko Keves wrote: hi this verbosed dmesg is from my box maybe it help you Uhm, and what exactly is the problem ? -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
compaq proliant dl360 G3 nic driver
hi, I have installed FreeBSD 4.7R on a compaq proliant dl360 G3 to find out that the nics are not being recognized.. has this been dealt with in current ? -- Does artificial plants need artificial water ? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: compaq proliant dl360 G3 nic driver
use the latest RELENG_4 L. Jankok ([EMAIL PROTECTED]) wrote: hi, I have installed FreeBSD 4.7R on a compaq proliant dl360 G3 to find out that the nics are not being recognized.. has this been dealt with in current ? -- Does artificial plants need artificial water ? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Paul Saab Technical Yahoo [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SMP hang at boot on Compaq Proliant ML370
Peter Wemm [EMAIL PROTECTED] writes: I have a brutal workaround (use a single 8254 clock and simulate the RTC clock), but it breaks some things (eg: high res profiling). I really dont like it, and I'm working on a different possibility as well (keep the 8259 PIC alive and use it in ExtInt mode directly on LINT0 on the BSP, but this is nastier than it sounds). I'd really like to know if Linux can generate RTC PIE interrupts via the IO APIC on this hardware. I'm 99.% sure that it wont work either. I should try it, it would be nice to know for sure if it was a hardware/firmware bug. If this can help, I have put the boot log file for Linux 2.4.18 with SMP enabled at this URL : http://www-verimag.imag.fr/~kowalski/rochail.log Maybe can I help for other things ? -- Nicolas To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
SMP hang at boot on Compaq Proliant ML370
Hello. On a brand new Compaq Proliant ML370, I installed FreeBSD 5.0RC2, without any problems. It works very well when using only one CPU. To take advantage of the two available CPUs, I compiled a new kernel with the two necessary SMP options, installed it, then restarted the server, but it hangs when booting the new kernel, just after the following line has been displayed : APIC_IO: testing 8254 interrupt delivery. Reading some archives tells me this message appears just before the others CPUs are started, so I suppose this is the problem. The server is configured for Unixware7, as told in the archives. Has anybody an idea ? Thanks. -- Nicolas To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SMP hang at boot on Compaq Proliant ML370
On Wed, Jan 15, 2003 at 11:09:09AM +0100, Nicolas Kowalski wrote: The server is configured for Unixware7, as told in the archives. our Compaq worked when configured for linux -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SMP hang at boot on Compaq Proliant ML370
Fritz Heinrichmeyer [EMAIL PROTECTED] writes: On Wed, Jan 15, 2003 at 11:09:09AM +0100, Nicolas Kowalski wrote: The server is configured for Unixware7, as told in the archives. our Compaq worked when configured for linux Nope :-(. I just tried this option, and the server still hangs at the same point. Any idea ? Thanks. -- Nicolas To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SMP hang at boot on Compaq Proliant ML370
In message [EMAIL PROTECTED], Nicolas Kowalski writes: Fritz Heinrichmeyer [EMAIL PROTECTED] writes: On Wed, Jan 15, 2003 at 11:09:09AM +0100, Nicolas Kowalski wrote: The server is configured for Unixware7, as told in the archives. our Compaq worked when configured for linux Nope :-(. I just tried this option, and the server still hangs at the same point. I had a Compaq visit my lab recently. Unless the aic driver were removed from the kernel (disabling it might have worked too) it would screw up the floppy driver. This sounds like black magic, but the explanation is that the aic driver has a very intrusive probe routine which sticks random bytes into whatever I/O locations it feels like and this appearantly is not liked by certain machines. Compaqs with all their bells and whistles could be particular sensitive to this, so try to disable the aic driver and see if it helps. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SMP hang at boot on Compaq Proliant ML370
On 15-Jan-2003 Nicolas Kowalski wrote: [EMAIL PROTECTED] writes: I had a Compaq visit my lab recently. Unless the aic driver were removed from the kernel (disabling it might have worked too) it would screw up the floppy driver. This sounds like black magic, but the explanation is that the aic driver has a very intrusive probe routine which sticks random bytes into whatever I/O locations it feels like and this appearantly is not liked by certain machines. Compaqs with all their bells and whistles could be particular sensitive to this, so try to disable the aic driver and see if it helps. I tried this. Now there is only the ahc driver (the only one needed) compiled in the kernel but this does not help, the server still hangs. I also removed the ata driver, without success. :-( Is the ML370 a new box? I've heard rumors recently that one of the recent Compaq boxes effectively doesn't generate clock interrupts in SMP mode and there isn't a workaround for that at the moment. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SMP hang at boot on Compaq Proliant ML370
John Baldwin [EMAIL PROTECTED] writes: [...] Is the ML370 a new box? I've heard rumors recently that one of the recent Compaq boxes effectively doesn't generate clock interrupts in SMP mode and there isn't a workaround for that at the moment. Yes. I received it last Friday. I think these rumors are true...:-( -- Nicolas To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: SMP hang at boot on Compaq Proliant ML370
That's a vicious rumor -- no operating system could work without clock interrupts in SMP mode... Could it? Which generation of the ML370 is having this problem? I had a similar problem on another box that was corrected with a newer BIOS version. Thanks, John -Original Message- From: John Baldwin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 10:55 AM To: Nicolas Kowalski Cc: [EMAIL PROTECTED] Subject: Re: SMP hang at boot on Compaq Proliant ML370 On 15-Jan-2003 Nicolas Kowalski wrote: [EMAIL PROTECTED] writes: I had a Compaq visit my lab recently. Unless the aic driver were removed from the kernel (disabling it might have worked too) it would screw up the floppy driver. This sounds like black magic, but the explanation is that the aic driver has a very intrusive probe routine which sticks random bytes into whatever I/O locations it feels like and this appearantly is not liked by certain machines. Compaqs with all their bells and whistles could be particular sensitive to this, so try to disable the aic driver and see if it helps. I tried this. Now there is only the ahc driver (the only one needed) compiled in the kernel but this does not help, the server still hangs. I also removed the ata driver, without success. :-( Is the ML370 a new box? I've heard rumors recently that one of the recent Compaq boxes effectively doesn't generate clock interrupts in SMP mode and there isn't a workaround for that at the moment. -- John Baldwin [EMAIL PROTECTED] http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SMP hang at boot on Compaq Proliant ML370
Cagle, John (ISS-Houston) [EMAIL PROTECTED] writes: That's a vicious rumor -- no operating system could work without clock interrupts in SMP mode... Could it? Which generation of the ML370 is having this problem? I had a similar problem on another box that was corrected with a newer BIOS version. This server is of generation 3. -- Nicolas To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: SMP hang at boot on Compaq Proliant ML370
On 15-Jan-2003 Cagle, John (ISS-Houston) wrote: That's a vicious rumor -- no operating system could work without clock interrupts in SMP mode... Could it? I think it had something to do more with the RTC interrupt not being routed to the I/O APIC and FreeBSD currently can only handle the ISA timer interrupt being only rounted to the 8259A PICs. Thus, FreeBSD hangs because it doesn't get any interrupts from the RTC via the I/O APIC. I couldn't remmeber the exact details earlier hence the vagueness of my message. Which generation of the ML370 is having this problem? I had a similar problem on another box that was corrected with a newer BIOS version. Thanks, John -Original Message- From: John Baldwin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 10:55 AM To: Nicolas Kowalski Cc: [EMAIL PROTECTED] Subject: Re: SMP hang at boot on Compaq Proliant ML370 On 15-Jan-2003 Nicolas Kowalski wrote: [EMAIL PROTECTED] writes: I had a Compaq visit my lab recently. Unless the aic driver were removed from the kernel (disabling it might have worked too) it would screw up the floppy driver. This sounds like black magic, but the explanation is that the aic driver has a very intrusive probe routine which sticks random bytes into whatever I/O locations it feels like and this appearantly is not liked by certain machines. Compaqs with all their bells and whistles could be particular sensitive to this, so try to disable the aic driver and see if it helps. I tried this. Now there is only the ahc driver (the only one needed) compiled in the kernel but this does not help, the server still hangs. I also removed the ata driver, without success. :-( Is the ML370 a new box? I've heard rumors recently that one of the recent Compaq boxes effectively doesn't generate clock interrupts in SMP mode and there isn't a workaround for that at the moment. -- John Baldwin [EMAIL PROTECTED] http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SMP hang at boot on Compaq Proliant ML370
John Baldwin wrote: On 15-Jan-2003 Cagle, John (ISS-Houston) wrote: That's a vicious rumor -- no operating system could work without clock interrupts in SMP mode... Could it? I think it had something to do more with the RTC interrupt not being routed to the I/O APIC and FreeBSD currently can only handle the ISA timer interrupt being only rounted to the 8259A PICs. Thus, FreeBSD hangs because it doesn't get any interrupts from the RTC via the I/O APIC. I couldn't remmeber the exact details earlier hence the vagueness of my message. The same problem happens with a newer DL380 that we have here. G3 I think, but I can never keep track of all the new toys. :-) Backgrounder: There are two sources of clock in i386 systems. The 8254 timer and the RTC (real time clock). FreeBSD uses both. Linux and Windows use the 8254 primarily, but Linux can be configured to use the RTC as well via the /dev/ rtc device and a couple of ioctl() calls. Linux normally wouldn't notice if the RTC device wasn't generating interrupts. vmware might though as it uses /dev/rtc. In uniprocessor mode, both of these are used via the 8259 interrupt controller (PIC). But in SMP mode, neither the 8254 or RTC originated interrupts show up on the APIC on their designated interrupt inputs. I really do not know why. From what I have seen of the chipset specs (Serverworks CSB5 - Champion South Bridge 5), the RTC interrupts are delivered to a single piece of silicon via serial interrupt protocol along with the floppy controller and COM ports etc. It is supposedly an all-or-nothing deal. Meanwhile the 8254, 8259 and IO APIC are all on the same silicon. There shouldn't be anything that can't be connected. So all I can think of is a hardware quirk in the CSB5 (Older rev 1.x in the system I was playing with that isn't working, not CSB5 v2.0), a BIOS programming issue (not setting up the interrupt routing correctly), or a bug in FreeBSD. I'm 99.9% convinced that it is not the latter. I've looked at register dumps of the CSB5 and I can't see anything obvious that is wrong there. :-( I have a brutal workaround (use a single 8254 clock and simulate the RTC clock), but it breaks some things (eg: high res profiling). I really dont like it, and I'm working on a different possibility as well (keep the 8259 PIC alive and use it in ExtInt mode directly on LINT0 on the BSP, but this is nastier than it sounds). I'd really like to know if Linux can generate RTC PIE interrupts via the IO APIC on this hardware. I'm 99.% sure that it wont work either. I should try it, it would be nice to know for sure if it was a hardware/firmware bug. Which generation of the ML370 is having this problem? I had a similar problem on another box that was corrected with a newer BIOS version. Thanks, John -Original Message- From: John Baldwin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 10:55 AM To: Nicolas Kowalski Cc: [EMAIL PROTECTED] Subject: Re: SMP hang at boot on Compaq Proliant ML370 On 15-Jan-2003 Nicolas Kowalski wrote: [EMAIL PROTECTED] writes: I had a Compaq visit my lab recently. Unless the aic driver were removed from the kernel (disabling it might have worked too) it would screw up the floppy driver. This sounds like black magic, but the explanation is that the aic driver has a very intrusive probe routine which sticks random bytes into whatever I/O locations it feels like and this appearantly is not liked by certain machines. Compaqs with all their bells and whistles could be particular sensitive to this, so try to disable the aic driver and see if it helps. I tried this. Now there is only the ahc driver (the only one needed) compiled in the kernel but this does not help, the server still hangs. I also removed the ata driver, without success. :-( Is the ML370 a new box? I've heard rumors recently that one of the recent Compaq boxes effectively doesn't generate clock interrupts in SMP mode and there isn't a workaround for that at the moment. -- John Baldwin [EMAIL PROTECTED] http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: SMP hang at boot on Compaq Proliant ML370
Thanks for the info. I've found a ML370 G3 and will look into this today or tommorrow. I'll be in touch. Thanks, John -Original Message- From: Peter Wemm [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 11:32 AM To: John Baldwin Cc: Cagle, John (ISS-Houston); [EMAIL PROTECTED] Subject: Re: SMP hang at boot on Compaq Proliant ML370 John Baldwin wrote: On 15-Jan-2003 Cagle, John (ISS-Houston) wrote: That's a vicious rumor -- no operating system could work without clock interrupts in SMP mode... Could it? I think it had something to do more with the RTC interrupt not being routed to the I/O APIC and FreeBSD currently can only handle the ISA timer interrupt being only rounted to the 8259A PICs. Thus, FreeBSD hangs because it doesn't get any interrupts from the RTC via the I/O APIC. I couldn't remmeber the exact details earlier hence the vagueness of my message. The same problem happens with a newer DL380 that we have here. G3 I think, but I can never keep track of all the new toys. :-) snip To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: compaq proliant
On 21 Aug 2000, at 21:04, [EMAIL PROTECTED] wrote: has anyone gotten freebsd (current or other) running on one of these? Which Proliant model are you talking about? i've tried 4.0, 4.1, and -current, and the kernel panics on me with the following: sym0: 895a port 0x1000=0x10ff mem 0xb110-0xb1101fff,0xb140-0xb14003ff irq 11 at device 4.0 on pci1 sym0: failed to allocate RAM resources We're running 3.4-STABLE on a Proliant 3000 here, and it's working great. Mind you, this has a Symbios 875 based controller, not 895a as in your case. Proliant 3000 with 4.1-STABLE here, working great too. -- .. David Touitouhttp://dites-le.com SysAdmin and co Solexine To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: compaq proliant
sym0: 895a port 0x1000=0x10ff mem 0xb110-0xb1101fff,0xb140-0xb14003ff irq 11 at device 4.0 on pci1 sym0: failed to allocate RAM resources We're running 3.4-STABLE on a Proliant 3000 here, and it's working great. Mind you, this has a Symbios 875 based controller, not 895a as in your case. Proliant 3000 with 4.1-STABLE here, working great too. it's a ML330. recompiling the kernel without sym support seems to make it boot (i wasnt using the scsi controller anyway). which is an interesting data point, actually: there were no scsi devices plugged into the controller. in any event, im up and running. this may now serve as a data point for whomever is maintaining the sym driver... - j Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
compaq proliant
has anyone gotten freebsd (current or other) running on one of these? i've tried 4.0, 4.1, and -current, and the kernel panics on me with the following: sym0: 895a port 0x1000=0x10ff mem 0xb110-0xb1101fff,0xb140-0xb14003ff irq 11 at device 4.0 on pci1 sym0: failed to allocate RAM resources any ideas? - j Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: compaq proliant
has anyone gotten freebsd (current or other) running on one of these? Which Proliant model are you talking about? i've tried 4.0, 4.1, and -current, and the kernel panics on me with the following: sym0: 895a port 0x1000=0x10ff mem 0xb110-0xb1101fff,0xb140-0xb14003ff irq 11 at device 4.0 on pci1 sym0: failed to allocate RAM resources We're running 3.4-STABLE on a Proliant 3000 here, and it's working great. Mind you, this has a Symbios 875 based controller, not 895a as in your case. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] -- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-2124-STABLE #0: Sat Feb 19 23:14:12 CET 2000 [EMAIL PROTECTED]:/local/freebsd/src/sys/compile/NEWSFEED1_SYM Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 603979776 (589824K bytes) avail memory = 584105984 (570416K bytes) Programming 28 pins in IOAPIC #0 EISA INTCONTROL = 0620 IOAPIC #0 intpint 24 - irq 5 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 8, version: 0x001b0011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc02d6000. Pentium Pro MTRR support enabled eisa0: CPQ561 (System Board) Probing for devices on the EISA bus Probing for devices on PCI bus 0: chip0: Ross (?) host to PCI bridge rev 0x03 on pci0.0.0 vga0: Cirrus Logic GD5430 SVGA controller rev 0x22 int a irq 255 on pci0.6.0 chip1: PCI to EISA bridge (vendor=0e11 device=0001) rev 0x07 on pci0.15.0 chip2: Ross (?) host to PCI bridge rev 0x03 on pci0.17.0 Probing for devices on PCI bus 1: sym0: 875 rev 0x14 int a irq 19 on pci1.4.0 sym0: No NVRAM, ID 7, Fast-20, parity checking sym1: 875 rev 0x14 int b irq 18 on pci1.4.1 sym1: No NVRAM, ID 7, Fast-20, parity checking fxp0: Intel EtherExpress Pro 10/100B Ethernet rev 0x05 int a irq 18 on pci1.7.0 fxp0: Ethernet address 00:90:27:13:f6:21 tl0: Compaq Netelligent 10/100 rev 0x10 int a irq 17 on pci1.8.0 tl0: Ethernet address: 00:08:c7:1e:a7:35 tl0: autoneg complete, link status good (full-duplex, 100Mbps) Probing for devices on PCI bus 2: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0: failed to get data. psm0 irq 12 on isa psm0: model IntelliMouse, device ID 3 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): CD-ROM CDU571-Q/1.1a, removable, accel, dma, iordis acd0: drive speed 1378KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2 APIC_IO: routing 8254 via 8259 on pin 0 ccd0-3: Concatenated disk drivers Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da0 at sym0 bus 0 target 0 lun 0 da0: COMPAQ HD0093172C 3207 Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da2 at sym0 bus 0 target 4 lun 0 da2: COMPAQ HD0093172C 3207 Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da3 at sym0 bus 0 target 5 lun 0 da3: COMPAQ HD0093172C 3207 Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da1 at sym0 bus 0 target 1 lun 0 da1: COMPAQ HD0093172C 3207 Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
