[haiku-bugs] Re: [Haiku] #8241: Can't boot on Sandy Bridge PC.
- From: "diver" <trac@xxxxxxxxxxxx>
- Date: Sat, 31 Mar 2012 13:23:41 -0000
#8241: Can't boot on Sandy Bridge PC.
-----------------------------+------------------------------------------
Reporter: xeon3d | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: System/Kernel | Version: R1/Development
Resolution: | Keywords: sandy bridge,core,boot,stall
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
-----------------------------+------------------------------------------
Changes (by diver):
* version: R1/alpha3 => R1/Development
Old description:
> Hi.
>
> I've been trying to boot Haiku on my main machine with no success.
> The build I've tried is rev. 43475 GCC2H off of haiku-files.org burned to
> a DVD.
>
> Specs of the computer:
> Core i7-2700k (Sandy Bridge)
> Gigabyte GA-Z68X-UD4-B3
> 16 GB DDR3 RAM
> GeForce GT210 VGA (PCI-Ex) with 512 MB
> OCZ Vertex 3 SSD
>
> Symptom:
> When booting normally, no boot icon lights up. I've tried booting with
> preety much every combination of safe mode flags to no availability.
> While booting verbose, the last lines it outputs before stalling (No KDL,
> nothing) are 7 lines similar to the ones that start with "PCI: dom 0, bus
> 0" in this photo:
> http://dev.haiku-os.org/attachment/ticket/8111/1.JPG
>
> Extra Info:
> Due to my wanderings with booting multiple OSes, I've found a similar
> behaviour with OS X where it also stalls at "PCI Configuration". There
> was a fix provided by the developers which was to add a parameter to the
> bootloader, namely "npci=0x2000".
>
> All the info I could find about that parameter is this tidbit
>
> "0x2000 is the kIOPCIConfiguratorPFM64 flag, as seen in the IOPCIFamily
> source code. (PFM64 probably stands for prefetch memory 64 bit).
>
> npci=0x2000 turns off this flag, as npci negates whatever flag bits you
> specify.
> With this flag turned off, the logic that sets fConsoleRange is disabled,
> and so the new graphics console relocation code is not triggered.
> However, the rest of the other new relocation code is still executed, and
> therein probably lies a problem for some, depending upon your PCI memory
> config."
>
> Source: http://tonymacx86.com/viewtopic.php?p=222908#p222908
>
> I've attached some logs from Linux (lspci, lsusb & lshw) since I was
> unable to get into KDL and not having a camera also didn't help regarding
> taking a picture of where it stalled.
>
> Also, according to Disreali, this might be similar to the bug #8111 but
> since that one does go into KDL and mine doesn't (also, the user there is
> an AMD user and this is an Intel CPU) I thought it'd be better to create
> a new bug report.
New description:
Hi.
I've been trying to boot Haiku on my main machine with no success.
The build I've tried is hrev43475 GCC2H off of haiku-files.org burned to a
DVD.
Specs of the computer:
Core i7-2700k (Sandy Bridge)
Gigabyte GA-Z68X-UD4-B3
16 GB DDR3 RAM
GeForce GT210 VGA (PCI-Ex) with 512 MB
OCZ Vertex 3 SSD
Symptom:
When booting normally, no boot icon lights up. I've tried booting with
preety much every combination of safe mode flags to no availability. While
booting verbose, the last lines it outputs before stalling (No KDL,
nothing) are 7 lines similar to the ones that start with "PCI: dom 0, bus
0" in this photo:
http://dev.haiku-os.org/attachment/ticket/8111/1.JPG
Extra Info:
Due to my wanderings with booting multiple OSes, I've found a similar
behaviour with OS X where it also stalls at "PCI Configuration". There was
a fix provided by the developers which was to add a parameter to the
bootloader, namely "npci=0x2000".
All the info I could find about that parameter is this tidbit
"0x2000 is the kIOPCIConfiguratorPFM64 flag, as seen in the IOPCIFamily
source code. (PFM64 probably stands for prefetch memory 64 bit).
npci=0x2000 turns off this flag, as npci negates whatever flag bits you
specify.
With this flag turned off, the logic that sets fConsoleRange is disabled,
and so the new graphics console relocation code is not triggered.
However, the rest of the other new relocation code is still executed, and
therein probably lies a problem for some, depending upon your PCI memory
config."
Source: http://tonymacx86.com/viewtopic.php?p=222908#p222908
I've attached some logs from Linux (lspci, lsusb & lshw) since I was
unable to get into KDL and not having a camera also didn't help regarding
taking a picture of where it stalled.
Also, according to Disreali, this might be similar to the bug #8111 but
since that one does go into KDL and mine doesn't (also, the user there is
an AMD user and this is an Intel CPU) I thought it'd be better to create a
new bug report.
--
--
Ticket URL: <http://dev.haiku-os.org/ticket/8241#comment:9>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
