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 resou
> 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 1
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 0x
> > > 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 contr
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
bel
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&qu
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 an
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.
--
M
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 ar
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,
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
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: s
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
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
>
>
[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 pr
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
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 the
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 PR
"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 newe
s 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. Unles
>
> >> -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
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
>
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 ExtI
23 matches
Mail list logo
