On Wednesday, February 13, 2013 6:56:06 pm CeDeROM wrote:
> On Wed, Feb 13, 2013 at 4:48 PM, John Baldwin wrote:
> >> The simple answer that I have deduced is that APIC is MANDATORY for
> >> AMD64 machines and they won't run otherwise? This is why generic AMD64
> >> install fails when no APIC is e
On Wed, Feb 13, 2013 at 4:48 PM, John Baldwin wrote:
>> The simple answer that I have deduced is that APIC is MANDATORY for
>> AMD64 machines and they won't run otherwise? This is why generic AMD64
>> install fails when no APIC is enabled in the VBox?
>
> No, it is not quite like that. x86 machin
On Monday, February 11, 2013 4:34:37 pm CeDeROM wrote:
> On Mon, Feb 11, 2013 at 10:06 PM, John Baldwin wrote:
> > On Sunday, February 10, 2013 1:16:16 pm CeDeROM wrote:
> >> Hey :-) I have just noticed that booting installation media for
> >> FreeBSD 9.1-RELEASE AMD64 from ISO bootonly under Virt
On Tue, Feb 12, 2013 at 12:53 AM, Jakub Lach wrote:
> As far as I remember, there is no apic option in amd64 kernel,
> because it's always included.
Yup, I guess that note in the handbook should be updated :-)
CPU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (2394.03-MHz K8-class CPU)
Ori
As far as I remember, there is no apic option in amd64 kernel,
because it's always included.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-RELEASE-AMD64-crash-under-VBox-4-2-6-when-IO-APIC-is-disabled-tp5785747p5786129.html
Sent from the freebsd-stable mailing list
On Mon, Feb 11, 2013 at 10:06 PM, John Baldwin wrote:
> On Sunday, February 10, 2013 1:16:16 pm CeDeROM wrote:
>> Hey :-) I have just noticed that booting installation media for
>> FreeBSD 9.1-RELEASE AMD64 from ISO bootonly under VirtualBox 4.2.6
>> results in a kernel panic both when ACPI is ena
On Sunday, February 10, 2013 1:16:16 pm CeDeROM wrote:
> Hey :-) I have just noticed that booting installation media for
> FreeBSD 9.1-RELEASE AMD64 from ISO bootonly under VirtualBox 4.2.6
> results in a kernel panic both when ACPI is enabled and disabled in
> the boot dialog screen (seems differe
On 11/26/12 23:48, Bas Smeelen wrote:
On 11/26/12 23:36, Rick Miller wrote:
On Mon, Nov 26, 2012 at 5:25 PM, Bas Smeelen wrote:
Hi
Just modify newvers.sh to 9.1-RELEASE recompile and your on RELEASE :)
Who has a no non-release policy, management?
It's not just management,
Just to sum it up
On 11/26/12 23:36, Rick Miller wrote:
On Mon, Nov 26, 2012 at 5:25 PM, Bas Smeelen wrote:
Hi
Just modify newvers.sh to 9.1-RELEASE recompile and your on RELEASE :)
Who has a no non-release policy, management?
It's not just management,
checked, they don't have a clue, that's what we're here f
On Mon, Nov 26, 2012 at 5:25 PM, Bas Smeelen wrote:
> Hi
> Just modify newvers.sh to 9.1-RELEASE recompile and your on RELEASE :)
> Who has a no non-release policy, management?
It's not just management, but also software engineers, architects, and
business folks. When a company runs a service wh
On 11/26/12 22:42, mat...@hush.ai wrote:
Hi. With the recent delays from the security incident and the three SAs out of
the way, what now are we waiting for? I think we should just get rid of the
release schedule on FreeBSD.org if we aren't even going to be close to the set
dates.
RC3 has been
11 matches
Mail list logo
