Carl-Daniel Hailfinger wrote:
On 10.12.2007 21:56, Marc Jones wrote:
A devices needs to be listed in the config.lb if it requires more setup
than standard PCI initialization (resource allocation). Usually that
means the CPU, northbridge, southbridge, and SIO. Those devices are
usually
On Mon, Dec 17, 2007 at 03:10:52PM -0700, Marc Jones wrote:
Carl-Daniel Hailfinger wrote:
On 10.12.2007 21:56, Marc Jones wrote:
A devices needs to be listed in the config.lb if it requires more setup
than standard PCI initialization (resource allocation). Usually that
means the CPU,
On 17.12.2007 23:10, Marc Jones wrote:
Carl-Daniel Hailfinger wrote:
On 10.12.2007 21:56, Marc Jones wrote:
A devices needs to be listed in the config.lb if it requires more
setup than standard PCI initialization (resource allocation).
Usually that means the CPU, northbridge, southbridge,
On 10.12.2007 21:56, Marc Jones wrote:
A devices needs to be listed in the config.lb if it requires more setup
than standard PCI initialization (resource allocation). Usually that
means the CPU, northbridge, southbridge, and SIO. Those devices are
usually needed to indicate the system bus
On Mon, 2007-12-10 at 17:32 -0700, Marc Jones wrote:
When I have seen a soft reset at this point it has been due to a memory
problem. Try simpler configurations and try putting some basic memory
test just before CAR is disabled. I would try on the interesting
boundaries. For example,
On Dec 12, 2007 11:05 AM, Steve Isaacs [EMAIL PROTECTED] wrote:
btw: based upon this information I've deduced that if a device is listed
in the Config.lb but does not appear in the bus scan it is identified as
a Left over device. Is this correct?
yes.
I'm thinking that an experiment which
ron minnich wrote:
On Dec 12, 2007 11:05 AM, Steve Isaacs [EMAIL PROTECTED] wrote:
I'm thinking that an experiment which might prove interesting is to
temporarily change pci_scan_bus to not die when this device is Left
over... and see where that gets me.
sure, it can't hurt ...
Should it
On Dec 12, 2007 11:19 AM, Marc Jones [EMAIL PROTECTED] wrote:
Should it die if a a device isn't found? Seems like that would be a
warning. I can imagine some cases where a device might or might not be
installed on a mainboard that could be supported by a single ROM image.
I thought the same
On Sun, 2007-12-09 at 10:15 -0800, ron minnich wrote:
On Dec 9, 2007 10:12 AM, Uwe Hermann [EMAIL PROTECTED] wrote:
You don't have the 19.* devices from lspci listed here; not sure what
those devices are, but I guess they must be listed.
They're cpu 1 northbridge I believe.
You're
On Dec 10, 2007 7:51 AM, Steve Isaacs [EMAIL PROTECTED] wrote:
That's something I don't understand. What is essential and what is not?
Essential is needed to configure machine to load Linux. Which really
means that devices for it exist in the device tree, and those devices
need to run some
On Sun, 2007-12-09 at 19:12 +0100, Uwe Hermann wrote:
On Wed, Dec 05, 2007 at 12:00:59PM -0800, Steve Isaacs wrote:
Is there anything that describes how to make a configuration in detail?
I'd rather learn the rules than have someone figure it out for me.
There's a PDF which describes some
On Sun, 2007-12-09 at 15:56 -0500, Tom Sylla wrote:
Steve Isaacs wrote:
chip southbridge/broadcom/bcm21000
device pci 0.0 on
end
device pci 1.0 off
end
device pci 2.0 on
end
device pci 3.0 off
On Sun, 2007-12-09 at 12:26 -0800, yhlu wrote:
whole boot log and your Options.lb in your MB dir ?
I just now realized that this might be what you wanted. This is the
output sent to the serial port during boot.
Steve
-
LinuxBIOS-2.0.0._apollo_Fallback OBJ--XX Mon Dec 10 11:19:06
On Mon, Dec 10, 2007 at 10:08:30AM -0800, Steve Isaacs wrote:
For the PCI parts, LinuxBIOS sets up the static/onboard devices and scans
for other devices dynamically, if I'm not mistaken.
This means you do not specify PCI/AGP/PCIe extention cards in Config.lb,
they're rather detected at
On Mon, 2007-12-10 at 09:05 -0800, ron minnich wrote:
On Dec 10, 2007 7:51 AM, Steve Isaacs [EMAIL PROTECTED] wrote:
That's something I don't understand. What is essential and what is not?
Essential is needed to configure machine to load Linux. Which really
means that devices for it
On Mon, 2007-12-10 at 21:25 +0100, Uwe Hermann wrote:
On Mon, Dec 10, 2007 at 10:08:30AM -0800, Steve Isaacs wrote:
One thing that keeps tripping me is it appears that some device numbers
are 0 based and others are 1 based. For example 18.0 agrees with a PCI
bus scan as well as 19.0 but 6.0
Steve Isaacs wrote:
On Mon, 2007-12-10 at 09:05 -0800, ron minnich wrote:
e.g. Can I leave out the 18.x as well and LB will auto-detect like it
did for node 1 (19.x)?
Those are northbridge register on k8 and on a 2-cpu system you need
them. But do you need them in Config.lb? You know, I
On Dec 10, 2007 10:08 AM, Steve Isaacs [EMAIL PROTECTED] wrote:
This is part of my confusion. I installed a Phoenix BIOS to boot Linux
and be able to run lspci. I have no visibility into what it's (Phoenix
BIOS) design is for this board. I suspect there are several devices it
hides (a feature
On Dec 10, 2007 1:39 PM, yhlu [EMAIL PROTECTED] wrote:
No, you don't need that. I have made it automatically detect that. So
you only need the chain that down to superio.
if my memory is right, the auto detect is in northbridge.c
oops, forgot you had done that!
So, what should his Config
On Dec 10, 2007 1:19 PM, ron minnich [EMAIL PROTECTED] wrote:
On Dec 10, 2007 10:08 AM, Steve Isaacs [EMAIL PROTECTED] wrote:
This is part of my confusion. I installed a Phoenix BIOS to boot Linux
and be able to run lspci. I have no visibility into what it's (Phoenix
BIOS) design is for
On Dec 10, 2007 1:51 PM, ron minnich [EMAIL PROTECTED] wrote:
On Dec 10, 2007 1:39 PM, yhlu [EMAIL PROTECTED] wrote:
No, you don't need that. I have made it automatically detect that. So
you only need the chain that down to superio.
if my memory is right, the auto detect is in
On Dec 10, 2007 2:52 PM, yhlu [EMAIL PROTECTED] wrote:
On Dec 10, 2007 1:51 PM, ron minnich [EMAIL PROTECTED] wrote:
On Dec 10, 2007 1:39 PM, yhlu [EMAIL PROTECTED] wrote:
No, you don't need that. I have made it automatically detect that. So
you only need the chain that down to
On Mon, 2007-12-10 at 13:19 -0800, ron minnich wrote:
Your board is not working, and the best thing you can do is shrink
down Config.lb until it works.
I performed a series of experiments stripping the Config.lb none of
which fixed my issue. The process I followed was to comment out devices
I tried this config and it got this far (hangs after second SOFT_RESET):
LinuxBIOS-2.0.0._apollo_Fallback OBJ--XX Mon Dec 10 15:21:11 PST
2007 starting...
(0,1) link=01
(1,0) link=01
02 nodes initialized.
core0 started: 01
01 02 03SBLink=00
NC node|link=00
SMBus controller enabled
INIT
Steve Isaacs wrote:
I tried this config and it got this far (hangs after second SOFT_RESET):
LinuxBIOS-2.0.0._apollo_Fallback OBJ--XX Mon Dec 10 15:21:11 PST
2007 starting...
...
Ram1.00
Ram1.01
Ram2.00
Registered
333Mhz
Interleaved
RAM: 0x0040 KB
Ram2.01
Registered
333Mhz
On Dec 10, 2007 3:03 PM, ron minnich [EMAIL PROTECTED] wrote:
On Dec 10, 2007 2:52 PM, yhlu [EMAIL PROTECTED] wrote:
On Dec 10, 2007 1:51 PM, ron minnich [EMAIL PROTECTED] wrote:
On Dec 10, 2007 1:39 PM, yhlu [EMAIL PROTECTED] wrote:
No, you don't need that. I have made it
On Wed, Dec 05, 2007 at 12:00:59PM -0800, Steve Isaacs wrote:
On Wed, 2007-12-05 at 12:30 +0100, Uwe Hermann wrote:
Please post your Config.lb and 'lspci -tvnn' output.
You're likely listing PCI devices in Config.lb which are not on the
board, or you use the wrong nesting or order (?)
On Dec 9, 2007 10:12 AM, Uwe Hermann [EMAIL PROTECTED] wrote:
You don't have the 19.* devices from lspci listed here; not sure what
those devices are, but I guess they must be listed.
They're cpu 1 northbridge I believe.
The rule is, unless you really MUST list a device in Config.lb, don't
whole boot log and your Options.lb in your MB dir ?
YH
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
Steve Isaacs wrote:
chip southbridge/broadcom/bcm21000
device pci 0.0 on
end
device pci 1.0 off
end
device pci 2.0 on
end
device pci 3.0 off
end
device pci 4.0 off
end
On Wed, 2007-12-05 at 12:30 +0100, Uwe Hermann wrote:
Please post your Config.lb and 'lspci -tvnn' output.
You're likely listing PCI devices in Config.lb which are not on the
board, or you use the wrong nesting or order (?)
Thanks, see below.
I have been in a very uncomfortable position
On Tue, Dec 04, 2007 at 04:08:47PM -0800, Steve Isaacs wrote:
I'm seeing this message during boot and have made several attempts and
modifying the Config.lb as the message suggests. Here's the tail of the
messages:
PCI: 00:09.0 [1166/0142] disabled
PCI: 00:0a.0 subbordinate bus PCI Express
I'm seeing this message during boot and have made several attempts and
modifying the Config.lb as the message suggests. Here's the tail of the
messages:
PCI: 00:09.0 [1166/0142] disabled
PCI: 00:0a.0 subbordinate bus PCI Express
PCI: 00:0a.0 [1166/0144] enabled
PCI: 00:0b.0 subbordinate bus PCI
33 matches
Mail list logo
