https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082009-12-13T02:53:27ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #1624: BTX Halted on X86_64 masterhttps://bugs.dragonflybsd.org/issues/1624?journal_id=79022009-12-13T02:53:27Zjgordeev
<ul></ul><p>Please, give more information.<br />Have you ever booted x86_64 DragonFly on your laptop successfully? Is <br />your laptop 64-bit capable? Does FreeBSD/amd64 boot on it?<br />Does the BTX Halted message appear just when the menu is being shown or <br />just when the countdown reaches zero/you press enter and the kernel is <br />supposed to be loading?</p> DragonFlyBSD - Bug #1624: BTX Halted on X86_64 masterhttps://bugs.dragonflybsd.org/issues/1624?journal_id=79032009-12-13T04:41:41Zelekktretterr
<ul></ul><p>Well this is rather embarassing. This aint a 64bit processor. I bought<br />this thing like half a year after I bought my AMD64 workstation and I had<br />assumed (Core Duo) would be 64 bit.</p>
<p>Sorry.....</p> DragonFlyBSD - Bug #1624: BTX Halted on X86_64 masterhttps://bugs.dragonflybsd.org/issues/1624?journal_id=79042009-12-13T04:51:23Zjgordeev
<ul></ul><p>There's a change in FreeBSD's loader that detects processors that are <br />not 64-bit capable and prints an error message, instead of "BTX Halted".</p> DragonFlyBSD - Bug #1624: BTX Halted on X86_64 masterhttps://bugs.dragonflybsd.org/issues/1624?journal_id=79112009-12-13T23:12:39Zwbh
<ul></ul><p><a class="email" href="mailto:elekktretterr@exemail.com.au">elekktretterr@exemail.com.au</a> wrote:</p>
<blockquote>
<p>Well this is rather embarassing. This aint a 64bit processor. I bought<br />this thing like half a year after I bought my AMD64 workstation and I had<br />assumed (Core Duo) would be 64 bit.</p>
<p>Sorry.....</p>
</blockquote>
<p>Odd, that. Just which specific CPU do you have? Mobility-something, perchance?</p>
<p>Not only the Core-2, but the earlier Core-D had Intel's '64-bit extensions' <br />(mostly) cross-licensed from AMD.</p>
<p>My Core-D happily ran FreeBSD ADM64 (6.2 beta onward).</p>
<p>Is DFLY that different?</p>
<p>Bill</p> DragonFlyBSD - Bug #1624: BTX Halted on X86_64 masterhttps://bugs.dragonflybsd.org/issues/1624?journal_id=79122009-12-14T02:02:43ZTGEN
<ul></ul><p>Bill Hacker wrote:</p>
<blockquote>
<p><a class="email" href="mailto:elekktretterr@exemail.com.au">elekktretterr@exemail.com.au</a> wrote:</p>
<blockquote>
<p>Well this is rather embarassing. This aint a 64bit processor. I bought<br />this thing like half a year after I bought my AMD64 workstation and I had<br />assumed (Core Duo) would be 64 bit.</p>
<p>Sorry.....</p>
</blockquote>
<p>Odd, that. Just which specific CPU do you have? Mobility-something,<br />perchance?</p>
<p>Not only the Core-2, but the earlier Core-D had Intel's '64-bit<br />extensions' (mostly) cross-licensed from AMD.</p>
<p>My Core-D happily ran FreeBSD ADM64 (6.2 beta onward).</p>
<p>Is DFLY that different?</p>
<p>Bill</p>
</blockquote>
<p>None of the Core Duo chips support EM64T. Are you perhaps confusing the<br />Pentium D with the Core Duo? Also, all Core Duo chips were mobile ones,<br />save for the Xeon ULV ("Sossaman"), which was for dual-socket servers<br />(short-lived though, as a couple of months later Woodcrest and friends<br />(Core 2-based) were released).<br />-- <br /> Thomas E. Spanjaard<br /> <a class="email" href="mailto:tgen@netphreax.net">tgen@netphreax.net</a><br /> <a class="email" href="mailto:tgen@deepbone.net">tgen@deepbone.net</a></p> DragonFlyBSD - Bug #1624: BTX Halted on X86_64 masterhttps://bugs.dragonflybsd.org/issues/1624?journal_id=79132009-12-14T07:43:44Zwbh
<ul></ul><p>Thomas E. Spanjaard wrote:</p>
<blockquote>
<p>Bill Hacker wrote:</p>
<blockquote>
<p><a class="email" href="mailto:elekktretterr@exemail.com.au">elekktretterr@exemail.com.au</a> wrote:</p>
<blockquote>
<p>Well this is rather embarassing. This aint a 64bit processor. I bought<br />this thing like half a year after I bought my AMD64 workstation and I had<br />assumed (Core Duo) would be 64 bit.</p>
<p>Sorry.....</p>
</blockquote>
<p>Odd, that. Just which specific CPU do you have? Mobility-something,<br />perchance?</p>
<p>Not only the Core-2, but the earlier Core-D had Intel's '64-bit<br />extensions' (mostly) cross-licensed from AMD.</p>
<p>My Core-D happily ran FreeBSD ADM64 (6.2 beta onward).</p>
<p>Is DFLY that different?</p>
<p>Bill</p>
</blockquote>
<p>None of the Core Duo chips support EM64T. Are you perhaps confusing the<br />Pentium D with the Core Duo? Also, all Core Duo chips were mobile ones,<br />save for the Xeon ULV ("Sossaman"), which was for dual-socket servers<br />(short-lived though, as a couple of months later Woodcrest and friends<br />(Core 2-based) were released).</p>
</blockquote>
<p>ACK 'marketing Nomenclature' - (the 'Core-D' / Pentium D eg - pre 'Core 2' <br />having been presented as meaning 'Core Duo')</p>
<p>.. which is why I asked about the <strong>number</strong>. Though of course a dmesg would show <br />that ... so long as the booting stage got that far:</p>
<p>(aged Tyan
====<br />CPU: Intel(R) Pentium(R) D CPU 3.00GHz (3000.14-MHz K8-class CPU)<br /> Origin = "GenuineIntel" Id = 0xf62 Stepping = 2</p>
<p>Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE><br /> Features2=0xe43d<SSE3,RSVD2,MON,DS_CPL,VMX,CNXT-ID,CX16,xTPR,PDCM><br /> AMD Features=0x20100800<SYSCALL,NX,LM><br /> AMD Features2=0x1<LAHF><br /> Cores per package: 2
====</p>
<p>Perhaps we should boot with an i32 image, detect what's there, throw a flag - <br />much as an OpenBSD insall selects an MP kernel (or not), and logs that action.<br />Doesn't need a lot of extra CD/DVD space ... or code.</p>
<p>I'll worry about all that when VIA Nano dualcore become common or ARM gets faster.</p>
<p>Meanwhile, after half a century of listening to fan noise, I'm chasing lower <br />power instead of raw speed and have come to rather enjoy what Simon & Garfunkel <br />called 'the sounds of silence'.</p>
<p>;-)</p>
<p>Bill</p> DragonFlyBSD - Bug #1624: BTX Halted on X86_64 masterhttps://bugs.dragonflybsd.org/issues/1624?journal_id=79152009-12-14T09:23:41Zdillon
<ul></ul><p>Heh. As Jordan indicated, this is where improving the failure message<br /> reduces the confusion.</p>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre> DragonFlyBSD - Bug #1624: BTX Halted on X86_64 masterhttps://bugs.dragonflybsd.org/issues/1624?journal_id=79192009-12-14T15:19:42Zalexh
<ul></ul><p>For reference: <a class="external" href="http://svn.freebsd.org/viewvc/base">http://svn.freebsd.org/viewvc/base</a>?<br />view=revision&revision=183667 .<br />That's the commit that introduces the failure message about trying to run on <br />x86.</p>
<p>Cheers,<br />Alex Hornung</p> DragonFlyBSD - Bug #1624: BTX Halted on X86_64 masterhttps://bugs.dragonflybsd.org/issues/1624?journal_id=79212009-12-14T16:59:58ZTGEN
<ul></ul><p>Bill Hacker wrote:</p>
<blockquote>
<p>Thomas E. Spanjaard wrote:</p>
<blockquote>
<p>Bill Hacker wrote:</p>
<blockquote>
<p><a class="email" href="mailto:elekktretterr@exemail.com.au">elekktretterr@exemail.com.au</a> wrote:</p>
<blockquote>
<p>Well this is rather embarassing. This aint a 64bit processor. I bought<br />this thing like half a year after I bought my AMD64 workstation and<br />I had<br />assumed (Core Duo) would be 64 bit.</p>
<p>Sorry.....</p>
</blockquote>
<p>Odd, that. Just which specific CPU do you have? Mobility-something,<br />perchance?</p>
<p>Not only the Core-2, but the earlier Core-D had Intel's '64-bit<br />extensions' (mostly) cross-licensed from AMD.</p>
<p>My Core-D happily ran FreeBSD ADM64 (6.2 beta onward).</p>
<p>Is DFLY that different?</p>
<p>Bill</p>
</blockquote>
<p>None of the Core Duo chips support EM64T. Are you perhaps confusing the<br />Pentium D with the Core Duo? Also, all Core Duo chips were mobile ones,<br />save for the Xeon ULV ("Sossaman"), which was for dual-socket servers<br />(short-lived though, as a couple of months later Woodcrest and friends<br />(Core 2-based) were released).</p>
</blockquote>
<p>ACK 'marketing Nomenclature' - (the 'Core-D' / Pentium D eg - pre 'Core<br />2' having been presented as meaning 'Core Duo')</p>
</blockquote>
<p>I've never seen the Pentium D marketed as "Core-D" around here though,<br />that'd have been awful :).</p>
<blockquote>
<p>I'll worry about all that when VIA Nano dualcore become common or ARM<br />gets faster.</p>
</blockquote>
<p>Haven't seen those Nano chips in the wild yet, unfortunately.</p>
<blockquote>
<p>Meanwhile, after half a century of listening to fan noise, I'm chasing<br />lower power instead of raw speed and have come to rather enjoy what<br />Simon & Garfunkel called 'the sounds of silence'.</p>
</blockquote>
<p>What about a blindingly fast system, but running in another<br />(sound-proofed) room? :P</p>
<p>Btw, your e-mail address bounces.<br />-- <br /> Thomas E. Spanjaard<br /> <a class="email" href="mailto:tgen@netphreax.net">tgen@netphreax.net</a><br /> <a class="email" href="mailto:tgen@deepbone.net">tgen@deepbone.net</a></p> DragonFlyBSD - Bug #1624: BTX Halted on X86_64 masterhttps://bugs.dragonflybsd.org/issues/1624?journal_id=79552009-12-21T06:48:00Zwbh
<ul></ul><p>Thomas E. Spanjaard wrote:</p>
<blockquote>
<p>Bill Hacker wrote:</p>
</blockquote>
<blockquote><blockquote>
<p>ACK 'marketing Nomenclature' - (the 'Core-D' / Pentium D eg - pre 'Core<br />2' having been presented as meaning 'Core Duo')</p>
</blockquote>
<p>I've never seen the Pentium D marketed as "Core-D" around here though,<br />that'd have been awful :).</p>
</blockquote>
<p>T'was ever thus in Asia anyway..</p>
<p>Core-D (faster clock, 'fatter' lithography, hungry, slower FSB/RAM</p>
<p>is NE to</p>
<p>Core-2 (the reverse on all of the above)</p>
<blockquote><blockquote>
<p>I'll worry about all that when VIA Nano dualcore become common or ARM<br />gets faster.</p>
</blockquote>
<p>Haven't seen those Nano chips in the wild yet, unfortunately.</p>
</blockquote>
<p>Dual-core, no. AFAIK, still a demo, if not 'lab' item.</p>
<p>Plenty of the solo's around in Netbooks and STB's though.</p>
<p>Wot the Hey - even the lowly C7 is a surprisingly good performer as a desktop.</p>
<p>All down to the hardware encryption engine and OpenSSL/SSH support for it. So <br />very much of what one does on a desktop uses encryption (ssh, scp, sftp, https, <br />esmtps(a), imaps, WiFi, rsync, VNC, remote X, remote desktop, distributed fs'en <br /> .... etc) that the hardware crypto engine very handily offsets the <br />generally-slower-than-CHEAP Intel CPU.</p>
<p>OTOH - as a compiler box? ... NFW!</p>
<blockquote><blockquote>
<p>Meanwhile, after half a century of listening to fan noise, I'm chasing<br />lower power instead of raw speed and have come to rather enjoy what<br />Simon & Garfunkel called 'the sounds of silence'.</p>
</blockquote>
<p>What about a blindingly fast system, but running in another<br />(sound-proofed) room? :P</p>
</blockquote>
<p>BT,DT,GTTS. 'Challenging' with the pair of laptops I now Globetrot with, and - <br />limited by the uplinks - the speed is no longer of much consequence, as anything <br />at 1 GHz (G4) to 1.5 GHz (x86) is seldom loaded up.</p>
<blockquote>
<p>Btw, your e-mail address bounces.</p>
</blockquote>
<p>Looking into that. Taking the headers from your post here, and ass-u-me-ing you <br />came off the same 'net from which you post to crater, I don't find any of the <br />three 'possible suspects' in my Exim logs as even attempting to attach recently.</p>
<pre><code>From which IP did you originate the last leg toward conducive.net?</code></pre>
<p>BTW - Sorry for the delay in responding - was enroute HKG USA on the 15th, then <br />distracted on arrival by need to deal with a water main leak and a snowstorm.</p> DragonFlyBSD - Bug #1624: BTX Halted on X86_64 masterhttps://bugs.dragonflybsd.org/issues/1624?journal_id=106892012-02-29T15:51:27Zalexh
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/10689/diff?detail_id=436">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Assignee</strong> deleted (<del><i>0</i></del>)</li></ul><p>committed freebsd's work in the area in 71920ddbfafa6ebd2812dc32ea61f7d69c05175b</p>