Hi, Attached are dmidecode and lspci -t/n/v output for my system, which has the same MB as Adrian's. Since he has the tools, can anyone provide tips on how to get started? Regards, David M. Barr
On 19/03/2007 12:06:43 am, Adrian-Ken Rueegsegger wrote:
Hi David,
Thanks for the info! I did find out that all chipsets are supported. I bought myself a Bios saviour and I have all the other hardware one needs. I just had little time playing around with it the last two weeks but I want to start looking into it again, that's why I wanted to ask if you had made some progress.
I am not quite sure where to start but I found a motherboard [1] that is quite "similar" to ours: Sun Ultra40. It has the same North- and Southbridge; SuperIO is different though. Would you know where to go from here?
Cheers, Adrian
On Sat, Mar 24, 2007 at 03:51:58PM +1100, David M Barr wrote:
Hi, Attached are dmidecode and lspci -t/n/v output for my system, which has the same MB as Adrian's. Since he has the tools, can anyone provide tips on how to get started? Regards, David M. Barr
On 19/03/2007 12:06:43 am, Adrian-Ken Rueegsegger wrote:
Hi David,
Thanks for the info! I did find out that all chipsets are supported. I bought myself a Bios saviour and I have all the other hardware one needs. I just had little time playing around with it the last two weeks but I want to start looking into it again, that's why I wanted to ask if you had made some progress.
I am not quite sure where to start but I found a motherboard [1] that is quite "similar" to ours: Sun Ultra40. It has the same North- and Southbridge; SuperIO is different though. Would you know where to go from here?
I suggest you checkout LinuxBIOSv2, then patch the Sun Ultra40 target directly until you get it to work (it's easy to see what you changed that way -- just do 'svn diff').
Then we can create a new mainboard directory and target etc...
What's the Super I/O? That should be the first thing to add. You need it for serial output.
Edit src/mainboards/sunw/ultra40/auto.c and change the Super I/O which is used there.
You also might need to change targets/sunw/ultra40/Config.lb to match the size of your ROM chip and the payload etc. etc. There are other things you'll probably need to change.
Start with the Super I/O, then report back to the mailing list and we'll try to help...
Uwe.
Uwe Hermann wrote:
What's the Super I/O? That should be the first thing to add. You need it for serial output.
ite it8712(f?).
In auto.c, change the #include "superio/xxx" to "superio/ite/it8712f". Then, in main(), change the line xxx_enable_serial() to it8712f_enable_serial(). Compile it and see if you get serial output!
-Corey
Hello everyone,
I started to try and get linuxbios running on my Asus A8N-SLI board. I got serial output working by using the sunw/ultra40 source and the appropriate superio (IT8712F). So far so good :)
After getting the message "Unbuffered Dimms not supported on Opteron" I simply disabled the check (src/northbridge/amd/k8/raminit.c,line 1198) since my processor is an AMD64 X2 4400+. Sidequestion: how could the "is_opteron()"-function in src/northbridge/amd/k8/raminit.c,line 606 be improved so it would not wrongly identify my kind of processor as an opteron?
Now there seems to be a problem with setting up the memory since SOFT_RESET is being issued several times before the boot process stops with "Jumping to LinuxBIOS.". I would be gratefull if somebody could take a look at the attached debug output and give me a hint on where to go from here.
Thanks!
Adrian
Corey Osgood wrote:
Uwe Hermann wrote:
What's the Super I/O? That should be the first thing to add. You need it for serial output.
ite it8712(f?).
In auto.c, change the #include "superio/xxx" to "superio/ite/it8712f". Then, in main(), change the line xxx_enable_serial() to it8712f_enable_serial(). Compile it and see if you get serial output!
-Corey
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 22:23:05 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
It means the RAM is not initialized properly.
It seems that for Rev E X2, current mem code in LinuxBIOS public tree only support one DIMM, if my memory is right.
So please try one dimm only.
YH
That was indeed the problem. Thanks! It got a bit further in the bootup process. I attached the latest debug log.
By the way, why are there several "SOFT_RESET"'s before it goes on?
Thanks again,
Adrian
Lu, Yinghai wrote:
It means the RAM is not initialized properly.
It seems that for Rev E X2, current mem code in LinuxBIOS public tree only support one DIMM, if my memory is right.
So please try one dimm only.
YH
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS.
INIT detected from ---- {APICID = 00 NODEID = 00 COREID = 00} ---
Issuing SOFT_RESET...
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 ht reset -
LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 starting... 01 nodes initialized. core0 started: started ap apicid: 11 SBLink=00 NC node|link=00 SMBus controller enabled Ram1.00 Ram2.00 Ram3 Initializing memory: done Ram4 v_esp=000cfce8 testx = 5a5a5a5a Copying data from cache to RAM -- switching to use RAM as stack... Done testx = 5a5a5a5a Disabling cache as ram now Clearing initial memory region: Done Copying LinuxBIOS to RAM. src=fffe0000 dst=00004000 linxbios_ram.nrv2b length = 0000d987 linxbios_ram.bin length = 00025e90 Jumping to LinuxBIOS. LinuxBIOS-2.0.0_ultra40_Fallback Mon Apr 2 23:40:29 CEST 2007 booting... Enumerating buses... APIC_CLUSTER: 0 enabled PCI_DOMAIN: 0000 enabled PCI: 00:18.3 siblings=1 CPU: APIC: 00 enabled CPU: APIC: 11 enabled PCI: pci_scan_bus for bus 00 PCI: 00:18.0 [1022/1100] enabled PCI: 00:18.1 [1022/1101] enabled PCI: 00:18.2 [1022/1102] enabled PCI: 00:18.3 [1022/1103] enabled Disabling static device: PCI: 00:19.0 Disabling static device: PCI: 00:19.1 Disabling static device: PCI: 00:19.2 Disabling static device: PCI: 00:19.3 PCI: 00:00.0 [10de/005e] enabled PCI: 00:00.0 [10de/005e] enabled next_unitid: 000f PCI: pci_scan_bus for bus 00 PCI: 00:00.0 [10de/005e] enabled PCI: 00:01.0 [10de/0050] enabled PCI: 00:01.1 [10de/0052] enabled PCI: 00:01.2 [10de/005f] enabled PCI: 00:02.0 [10de/005a] enabled PCI: 00:02.1 [10de/005b] enabled PCI: 00:04.0 [10de/0059] enabled PCI: 00:04.1 [10de/0058] enabled PCI: 00:06.0 [10de/0053] enabled PCI: 00:07.0 [10de/0054] enabled PCI: 00:08.0 [10de/0055] enabled PCI: 00:09.0 [10de/005c] enabled PCI: 00:0a.0 [10de/0057] enabled PCI: 00:0b.0 [10de/005d] enabled PCI: 00:0c.0 [10de/005d] enabled PCI: 00:0d.0 [10de/005d] enabled PCI: 00:0e.0 [10de/005d] enabled PCI: pci_scan_bus for bus 01 PCI: 01:06.0 [1102/0005] enabled PCI: 01:0b.0 [104c/8023] enabled PCI: pci_scan_bus returning with max=001 PCI: pci_scan_bus for bus 02 PCI: pci_scan_bus returning with max=002 PCI: pci_scan_bus for bus 03 PCI: pci_scan_bus returning with max=003 PCI: pci_scan_bus for bus 04 PCI: pci_scan_bus returning with max=004 PCI: pci_scan_bus for bus 05 PCI: pci_scan_bus returning with max=005 PCI: pci_scan_bus returning with max=005 PCI: pci_scan_bus returning with max=005 done Allocating resources... Reading resources... PCI: 00:09.0 24 <- [0x00fff00000 - 0x00ffefffff] bus 01 prefmem PCI: 00:0b.0 1c <- [0x00fffff000 - 0x00ffffefff] bus 02 io PCI: 00:0b.0 24 <- [0xfffffffffff00000 - 0xffffffffffefffff] bus 02 prefmem PCI: 00:0b.0 20 <- [0x00fff00000 - 0x00ffefffff] bus 02 mem PCI: 00:0c.0 1c <- [0x00fffff000 - 0x00ffffefff] bus 03 io PCI: 00:0c.0 24 <- [0xfffffffffff00000 - 0xffffffffffefffff] bus 03 prefmem PCI: 00:0c.0 20 <- [0x00fff00000 - 0x00ffefffff] bus 03 mem PCI: 00:0d.0 1c <- [0x00fffff000 - 0x00ffffefff] bus 04 io PCI: 00:0d.0 24 <- [0xfffffffffff00000 - 0xffffffffffefffff] bus 04 prefmem PCI: 00:0d.0 20 <- [0x00fff00000 - 0x00ffefffff] bus 04 mem PCI: 00:0e.0 1c <- [0x00fffff000 - 0x00ffffefff] bus 05 io PCI: 00:0e.0 24 <- [0xfffffffffff00000 - 0xffffffffffefffff] bus 05 prefmem PCI: 00:0e.0 20 <- [0x00fff00000 - 0x00ffefffff] bus 05 mem PCI: 00:00.0 missing read_resources PCI: 00:01.0 missing read_resources PCI: 00:01.1 missing read_resources PCI: 00:02.0 missing read_resources PCI: 00:02.1 missing read_resources PCI: 00:04.0 missing read_resources PCI: 00:06.0 missing read_resources PCI: 00:07.0 missing read_resources PCI: 00:08.0 missing read_resources PCI: 00:09.0 missing read_resources PCI: 00:0a.0 missing read_resources PCI: 00:0e.0 missing read_resources PCI: 00:00.0 missing read_resources PCI: 00:01.0 missing read_resources PCI: 00:01.1 missing read_resources PCI: 00:02.0 missing read_resources PCI: 00:02.1 missing read_resources PCI: 00:04.0 missing read_resources PCI: 00:06.0 missing read_resources PCI: 00:07.0 missing read_resources PCI: 00:08.0 missing read_resources PCI: 00:09.0 missing read_resources PCI: 00:0a.0 missing read_resources PCI: 00:0e.0 missing read_resources PCI: 00:00.0 missing read_resources PCI: 00:01.0 missing read_resources PCI: 00:01.1 missing read_resources PCI: 00:02.0 missing read_resources PCI: 00:02.1 missing read_resources PCI: 00:04.0 missing read_resources PCI: 00:06.0 missing read_resources PCI: 00:07.0 missing read_resources PCI: 00:08.0 missing read_resources PCI: 00:09.0 missing read_resources PCI: 00:0a.0 missing read_resources PCI: 00:0e.0 missing read_resources Done reading resources. Setting resources... PCI: 00:18.0 1c0 <- [0x0000001000 - 0x0000003fff] io <node 0 link 0> PCI: 00:18.0 1b8 <- [0x00fc600000 - 0x00fc5fffff] prefmem <node 0 link 0> PCI: 00:18.0 1b0 <- [0x00fc000000 - 0x00fc5fffff] mem <node 0 link 0> PCI: 00:00.0 missing read_resources PCI: 00:01.0 missing read_resources PCI: 00:01.1 missing read_resources PCI: 00:02.0 missing read_resources PCI: 00:02.1 missing read_resources PCI: 00:04.0 missing read_resources PCI: 00:06.0 missing read_resources PCI: 00:07.0 missing read_resources PCI: 00:08.0 missing read_resources PCI: 00:09.0 missing read_resources PCI: 00:0a.0 missing read_resources PCI: 00:0e.0 missing read_resources PCI: 00:18.0 1d9 <- [0x0000004000 - 0x0000003fff] io <node 0 link 1> PCI: 00:00.0 missing read_resources PCI: 00:01.0 missing read_resources PCI: 00:01.1 missing read_resources PCI: 00:02.0 missing read_resources PCI: 00:02.1 missing read_resources PCI: 00:04.0 missing read_resources PCI: 00:06.0 missing read_resources PCI: 00:07.0 missing read_resources PCI: 00:08.0 missing read_resources PCI: 00:09.0 missing read_resources PCI: 00:0a.0 missing read_resources PCI: 00:0e.0 missing read_resources PCI: 00:18.0 1a9 <- [0x00fc600000 - 0x00fc5fffff] prefmem <node 0 link 1> PCI: 00:00.0 missing read_resources PCI: 00:01.0 missing read_resources PCI: 00:01.1 missing read_resources PCI: 00:02.0 missing read_resources PCI: 00:02.1 missing read_resources PCI: 00:04.0 missing read_resources PCI: 00:06.0 missing read_resources PCI: 00:07.0 missing read_resources PCI: 00:08.0 missing read_resources PCI: 00:09.0 missing read_resources PCI: 00:0a.0 missing read_resources PCI: 00:0e.0 missing read_resources PCI: 00:18.0 1a1 <- [0x00fc600000 - 0x00fc5fffff] mem <node 0 link 1> PCI: 00:01.0 60 <- [0x0000002000 - 0x00000020ff] io PCI: 00:01.0 64 <- [0x0000002400 - 0x00000024ff] io PCI: 00:01.0 68 <- [0x0000002800 - 0x00000028ff] io PCI: 00:01.1 10 <- [0x0000003c00 - 0x0000003c1f] io PCI: 00:01.1 20 <- [0x0000003880 - 0x00000038bf] io PCI: 00:01.1 24 <- [0x00000038c0 - 0x00000038ff] io PCI: 00:02.0 10 <- [0x00fc500000 - 0x00fc500fff] mem PCI: 00:02.1 10 <- [0x00fc506000 - 0x00fc5060ff] mem PCI: 00:04.0 10 <- [0x0000002c00 - 0x0000002cff] io PCI: 00:04.0 14 <- [0x0000003000 - 0x00000030ff] io PCI: 00:04.0 18 <- [0x00fc501000 - 0x00fc501fff] mem PCI: 00:04.1 10 <- [0x0000003400 - 0x00000034ff] io PCI: 00:04.1 14 <- [0x0000003800 - 0x000000387f] io PCI: 00:04.1 18 <- [0x00fc502000 - 0x00fc502fff] mem PCI: 00:06.0 20 <- [0x0000003c20 - 0x0000003c2f] io PCI: 00:07.0 10 <- [0x0000003c50 - 0x0000003c57] io PCI: 00:07.0 14 <- [0x0000003ca0 - 0x0000003ca3] io PCI: 00:07.0 18 <- [0x0000003c60 - 0x0000003c67] io PCI: 00:07.0 1c <- [0x0000003cb0 - 0x0000003cb3] io PCI: 00:07.0 20 <- [0x0000003c30 - 0x0000003c3f] io PCI: 00:07.0 24 <- [0x00fc503000 - 0x00fc503fff] mem PCI: 00:08.0 10 <- [0x0000003c70 - 0x0000003c77] io PCI: 00:08.0 14 <- [0x0000003cc0 - 0x0000003cc3] io PCI: 00:08.0 18 <- [0x0000003c80 - 0x0000003c87] io PCI: 00:08.0 1c <- [0x0000003cd0 - 0x0000003cd3] io PCI: 00:08.0 20 <- [0x0000003c40 - 0x0000003c4f] io PCI: 00:08.0 24 <- [0x00fc504000 - 0x00fc504fff] mem PCI: 00:09.0 1c <- [0x0000001000 - 0x0000001fff] bus 01 io PCI: 00:09.0 20 <- [0x00fc000000 - 0x00fc4fffff] bus 01 mem PCI: 01:06.0 10 <- [0x0000001000 - 0x000000101f] io PCI: 01:06.0 14 <- [0x00fc000000 - 0x00fc1fffff] mem64 PCI: 01:06.0 1c <- [0x00fc200000 - 0x00fc3fffff] mem64 PCI: 01:0b.0 10 <- [0x00fc404000 - 0x00fc4047ff] mem PCI: 01:0b.0 14 <- [0x00fc400000 - 0x00fc403fff] mem PCI: 00:0a.0 10 <- [0x00fc505000 - 0x00fc505fff] mem PCI: 00:0a.0 14 <- [0x0000003c90 - 0x0000003c97] io PCI: 00:18.3 94 <- [0x00f8000000 - 0x00fbffffff] mem <gart> Done setting resources. Done allocating resources. Enabling resources... PCI: 00:18.0 cmd <- 140 PCI: 00:00.0 cmd <- 146 PCI: 00:01.0 cmd <- 14f PCI: 00:01.1 cmd <- 141 PCI: 00:01.2 cmd <- 540 PCI: 00:02.0 cmd <- 142 PCI: 00:02.1 cmd <- 142 PCI: 00:04.0 cmd <- 143 PCI: 00:04.1 cmd <- 143 PCI: 00:06.0 cmd <- 141 PCI: 00:07.0 cmd <- 143 PCI: 00:08.0 cmd <- 143 PCI: 00:09.0 bridge ctrl <- 0003 PCI: 00:09.0 cmd <- 147 PCI: 01:06.0 cmd <- 143 PCI: 01:0b.0 cmd <- 142 PCI: 00:0a.0 cmd <- 143 PCI: 00:0b.0 bridge ctrl <- 0003 PCI: 00:0b.0 cmd <- 140 PCI: 00:0c.0 bridge ctrl <- 0003 PCI: 00:0c.0 cmd <- 140 PCI: 00:0d.0 bridge ctrl <- 0003 PCI: 00:0d.0 cmd <- 140 PCI: 00:0e.0 bridge ctrl <- 0003 PCI: 00:0e.0 cmd <- 140 PCI: 00:00.0 missing enable_resources PCI: 00:01.0 missing enable_resources PCI: 00:01.1 missing enable_resources PCI: 00:02.0 missing enable_resources PCI: 00:02.1 missing enable_resources PCI: 00:04.0 missing enable_resources PCI: 00:06.0 missing enable_resources PCI: 00:07.0 missing enable_resources PCI: 00:08.0 missing enable_resources PCI: 00:09.0 missing enable_resources PCI: 00:0a.0 missing enable_resources PCI: 00:0e.0 missing enable_resources PCI: 00:18.1 subsystem <- 108e/40 PCI: 00:18.1 cmd <- 140 PCI: 00:18.2 subsystem <- 108e/40 PCI: 00:18.2 cmd <- 140 PCI: 00:18.3 cmd <- 140 done. Initializing devices... Root Device init APIC_CLUSTER: 0 init Initializing CPU #0 CPU: vendor AMD device 20f32 CPU: family 0f, model 23, stepping 02 Enabling cache
Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) Type: WB, RdMEM, WrMEM Setting fixed MTRRs(24-88) Type: WB, RdMEM, WrMEM DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 512MB, type WB DONE variable MTRRs Clear out the extra MTRR's
MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled
microcode: equivalent processor rev id = 0x0210, patch id = 0x00000000 microcode: patch id that want to apply= 0x0000004d microcode: updated to patch id = 0x0000004d success CPU model AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ Setting up local apic... apic_id: 0x00 done. ECC Disabled CPU #0 Initialized Initializing CPU #1 Waiting for 1 CPUS to stop CPU: vendor AMD device 20f32 CPU: family 0f, model 23, stepping 02 Enabling cache
Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) Type: WB, RdMEM, WrMEM Setting fixed MTRRs(24-88) Type: WB, RdMEM, WrMEM DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 512MB, type WB DONE variable MTRRs Clear out the extra MTRR's
MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled
microcode: equivalent processor rev id = 0x0210, patch id = 0x00000000 microcode: patch id that want to apply= 0x0000004d microcode: updated to patch id = 0x0000004d success CPU model AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ Setting up local apic... apic_id: 0x11 done. CPU #1 Initialized All AP CPUs stopped PCI: 00:18.0 init PCI: 00:18.1 init PCI: 00:18.2 init PCI: 00:18.3 init NB: Function 3 Misc Control.. done. PCI: 00:01.0 init set power on after power fail RTC Init RTC: Checksum invalid zeroing cmos Invalid CMOS LB checksum PCI: 00:01.2 init PCI: 00:02.0 init PCI: 00:02.1 init PCI: 00:06.0 init IDE1 IDE0 PCI: 00:07.0 init SATA S SATA P PCI: 00:08.0 init SATA S SATA P PCI: 00:09.0 init dev_root mem base = 0x00f8000000 [0x50] <-- 0xf8000000 PCI: 00:0a.0 init PCI: 00:0b.0 init PCI: 00:0c.0 init PCI: 00:0d.0 init PCI: 00:0e.0 init PCI: 01:06.0 init PCI: 01:0b.0 init Devices initialized Writing IRQ routing tables to 0xf0000...done. PCI: 00:01.0 missing resource: 14
Your ck804 is under K8 link0, so move
The
device pci 18.0 on end
in your MB Config.lb to
before device pci 18.1 on end.
I guess after updating ODC and Timing, all dimm could work, and there will be "SOFT_RESET"
YH
-----Original Message----- From: Adrian-Ken Rueegsegger [mailto:ken@gmx.ch] Sent: Monday, April 02, 2007 4:23 PM To: Lu, Yinghai Cc: Corey Osgood; David M Barr; linuxbios@linuxbios.org Subject: Re: [LinuxBIOS] ASUS A8N-SLI Premium (K8, CK804, IT8712)
That was indeed the problem. Thanks! It got a bit further in the bootup process. I attached the latest debug log.
By the way, why are there several "SOFT_RESET"'s before it goes on?
Thanks again,
Adrian
Lu, Yinghai wrote:
It means the RAM is not initialized properly.
It seems that for Rev E X2, current mem code in LinuxBIOS public tree only support one DIMM, if my memory is right.
So please try one dimm only.
YH
* Lu, Yinghai yinghai.lu@amd.com [070403 01:27]:
I guess after updating ODC and Timing, all dimm could work, and there will be "SOFT_RESET"
ODC?
Check the ODC in raminit_f.c
YH
-----Original Message----- From: Stefan Reinauer [mailto:stepan@coresystems.de] Sent: Monday, April 02, 2007 4:47 PM To: Lu, Yinghai Cc: Adrian-Ken Rueegsegger; David M Barr; linuxbios@linuxbios.org Subject: Re: [LinuxBIOS] ASUS A8N-SLI Premium (K8, CK804, IT8712)
* Lu, Yinghai yinghai.lu@amd.com [070403 01:27]:
I guess after updating ODC and Timing, all dimm could work, and there will be "SOFT_RESET"
ODC?
What does this mean? Is there a bug in raminit_f.c?
* Lu, Yinghai yinghai.lu@amd.com [070403 02:16]:
Check the ODC in raminit_f.c
YH
-----Original Message----- From: Stefan Reinauer [mailto:stepan@coresystems.de] Sent: Monday, April 02, 2007 4:47 PM To: Lu, Yinghai Cc: Adrian-Ken Rueegsegger; David M Barr; linuxbios@linuxbios.org Subject: Re: [LinuxBIOS] ASUS A8N-SLI Premium (K8, CK804, IT8712)
- Lu, Yinghai yinghai.lu@amd.com [070403 01:27]:
I guess after updating ODC and Timing, all dimm could work, and there will be "SOFT_RESET"
ODC?
-- coresystems GmbH * Brahmsstr. 16 * D-79104 Freiburg i. Br. Tel.: +49 761 7668825 * Fax: +49 761 7664613 Email: info@coresystems.de * http://www.coresystems.de/
Any progress on the ASUS A8N-SLI Premium port?
On Sat, 7 Apr 2007 04:38:35 am Stefan Reinauer wrote:
What does this mean? Is there a bug in raminit_f.c?
Hi
I realized some guys on this list were talking about porting ASUS A8N-SLI.
I started porting LinuxBIOS to ASUS A8N-E [1]. The boards seem to share some similarities so maybe my code is of any use for A8N-SLI port.
At the moment I'am able to fully boot an open SuSE 10.0 using the standard SuSE SMP kernel.
Network, sata, ide, usb and vga are working fine.
Unfortunately I still have some issues with IT8712F superio. Keyboard and mouse are not working (have to use usb counterparts). I finally ended up writing a little tool that dumps the register values of IT8712F (see attachement). As of writing this I'am pretty sure it is no issue of IT8712F alone. It seems to be an interrupt problem. Maybe some extra interrupt settings of ck804 are needed?? Unfortunately I don't have any mb schematics nor any ck804 data sheets that would help me further here :(.
I would be perfectly happy to provide a svn diff if it is of interest for you guys.
phil
------------------------------------- [1] http://www.asus.com/products.aspx?l1=3&l2=15&l3=171&l4=0&mod...
On Thu, May 17, 2007 at 07:30:41PM +0200, Philipp Degler wrote:
I realized some guys on this list were talking about porting ASUS A8N-SLI.
I started porting LinuxBIOS to ASUS A8N-E [1]. The boards seem to share some similarities so maybe my code is of any use for A8N-SLI port.
At the moment I'am able to fully boot an open SuSE 10.0 using the standard SuSE SMP kernel.
Network, sata, ide, usb and vga are working fine.
Unfortunately I still have some issues with IT8712F superio. Keyboard and mouse are not working (have to use usb counterparts). I finally ended up writing a little tool that dumps the register values of IT8712F (see attachement). As of writing this I'am pretty sure it is no issue of IT8712F alone. It seems to be an interrupt problem. Maybe some extra interrupt settings of ck804 are needed?? Unfortunately I don't have any mb schematics nor any ck804 data sheets that would help me further here :(.
I would be perfectly happy to provide a svn diff if it is of interest for you guys.
Yes, definately! Please post a (signed-off) patch to add the mainboard as a new target. If it already boots we should definately add it to the repository. Fixing the remaining issues can be done later...
Uwe.
On Thu, 2007-05-17 at 19:30 +0200, Philipp Degler wrote:
Hi
I realized some guys on this list were talking about porting ASUS A8N-SLI.
I started porting LinuxBIOS to ASUS A8N-E [1]. The boards seem to share some similarities so maybe my code is of any use for A8N-SLI port.
At the moment I'am able to fully boot an open SuSE 10.0 using the standard SuSE SMP kernel.
Network, sata, ide, usb and vga are working fine.
When you say SATA is working, do you mean all 4 ports?
Regards,
Jeremy
Hi,
Wondering if you can test all 4 SATA ports, i don't think anyone has more than 2 of 4 working.
I'm working on a Tyan S2865 board, similar except the SuperIO chip. I'm having trouble with only one of four PCI slots generating interrupts. I wonder if you can try a PCI network card or something and post your status?
Thanks,
Jeremy
On Thu, 2007-05-17 at 19:30 +0200, Philipp Degler wrote:
At the moment I'am able to fully boot an open SuSE 10.0 using the standard SuSE SMP kernel.
Network, sata, ide, usb and vga are working fine.
On Wednesday 23 May 2007 01:59:01 Jeremy Jackson wrote:
Hi,
Wondering if you can test all 4 SATA ports, i don't think anyone has more than 2 of 4 working.
yes same thing here. Tested all for ports but only the first 2 of em work.
I'm working on a Tyan S2865 board, similar except the SuperIO chip. I'm having trouble with only one of four PCI slots generating interrupts. I wonder if you can try a PCI network card or something and post your status?
actually the asus board has 3 pci slots. I plugged in a 3com network card. The device was found and the module loaded but the assignment of an interrupt failed. I would assume this is an mptable issue.
http://people.redhat.com/zaitcev/linux/ On this page you will find a tool called mptable that might help generating a valid mptable.c I already tried to get it right but no success so far :(. The mptable of asus a8n-e commercial bios seems to buggy though.
---- phil
* Philipp Degler pdegler@rumms.uni-mannheim.de [070523 14:46]:
http://people.redhat.com/zaitcev/linux/ On this page you will find a tool called mptable that might help generating a valid mptable.c I already tried to get it right but no success so far :(. The mptable of asus a8n-e commercial bios seems to buggy though.
BTW, this tool is also available in LinuxBIOSv2/util/mptable since many years.
Vendor bioses do not feature maintained mptables/pirq tables anymore. If you want a correct hardware description, look at their ACPI tables
What I found is that with a correct mptable.c, I get 1 slot working. I can verify the physical wiring of the INT[A-D] pins of the other 3 slots, and make correct mptable entries for those, but they are unable to generate interrupts.
Maybe when you have your mptable working you can try out all 3 slots and post the results,
Thanks,
Jeremy
On Wed, 2007-05-23 at 14:46 +0200, Philipp Degler wrote:
actually the asus board has 3 pci slots. I plugged in a 3com network card. The device was found and the module loaded but the assignment of an interrupt failed. I would assume this is an mptable issue.
http://people.redhat.com/zaitcev/linux/ On this page you will find a tool called mptable that might help generating a valid mptable.c I already tried to get it right but no success so far :(. The mptable of asus a8n-e commercial bios seems to buggy though.
On Wed, May 23, 2007 at 02:46:53PM +0200, Philipp Degler wrote:
On Wednesday 23 May 2007 01:59:01 Jeremy Jackson wrote:
Hi,
Wondering if you can test all 4 SATA ports, i don't think anyone has more than 2 of 4 working.
yes same thing here. Tested all for ports but only the first 2 of em work.
I'm working on a Tyan S2865 board, similar except the SuperIO chip. I'm having trouble with only one of four PCI slots generating interrupts. I wonder if you can try a PCI network card or something and post your status?
actually the asus board has 3 pci slots. I plugged in a 3com network card. The device was found and the module loaded but the assignment of an interrupt failed. I would assume this is an mptable issue.
Does the "irqpoll" kernel command line option help?
Jürgen Beisert has written a really nice HOWTO which may be useful, see http://linuxbios.org/Some_help_to_reverse_engineer_a_valid_interrupt_routing...
Uwe.
* Uwe Hermann uwe@hermann-uwe.de [070526 15:35]:
Jürgen Beisert has written a really nice HOWTO which may be useful, see http://linuxbios.org/Some_help_to_reverse_engineer_a_valid_interrupt_routing...
How about we rename the page to something that fits in 80 characters? Reverse_Engineering_IRQ_Tables or so?
On Sat, May 26, 2007 at 05:54:13PM +0200, Stefan Reinauer wrote:
- Uwe Hermann uwe@hermann-uwe.de [070526 15:35]:
Jürgen Beisert has written a really nice HOWTO which may be useful, see http://linuxbios.org/Some_help_to_reverse_engineer_a_valid_interrupt_routing...
How about we rename the page to something that fits in 80 characters? Reverse_Engineering_IRQ_Tables or so?
Good point, renamed to "Creating Valid IRQ Tables". I dropped the rev.eng. as it has a bad taste to it and doesn't really apply here. This is more like educated guessing ;-)
Uwe.
On Sat, 2007-05-26 at 15:35 +0200, Uwe Hermann wrote:
On Wed, May 23, 2007 at 02:46:53PM +0200, Philipp Degler wrote:
On Wednesday 23 May 2007 01:59:01 Jeremy Jackson wrote:
I'm working on a Tyan S2865 board, similar except the SuperIO chip. I'm having trouble with only one of four PCI slots generating interrupts. I wonder if you can try a PCI network card or something and post your status?
actually the asus board has 3 pci slots. I plugged in a 3com network card. The device was found and the module loaded but the assignment of an interrupt failed. I would assume this is an mptable issue.
Does the "irqpoll" kernel command line option help?
unfortunately not. I'm convinced the mptable is correct, as I have verified the physical wiring of the PCI slots with a multimeter. Based on the slot that has all 4 PIRQ[A-D] working, these should work.
If interrupts were being generated, but mptable was wrong, wouldn't the kernel complain about a spurious interrupt (and hence work with irqpoll)?
I think my next step will be to attach a counter/timer to the PIRQ lines and see what's going on.
As for the HOWTO, that's basically what I've done, and the IRQ steering can't be related because of the zero ohm connection between the PIRQ pins of all 4 slots.
What would be really helpful is to hear a report of someone with a CK804 that has more than 1 working PCI slot.
Also I'm looking for a PCI card that I can easily check interrupt pending status from a register, PC parallel printer port comes to mind, I'll have to look at the Linux kernel driver source.
Regards,
Jeremy
Jürgen Beisert has written a really nice HOWTO which may be useful, see http://linuxbios.org/Some_help_to_reverse_engineer_a_valid_interrupt_routing...
-
Adrian-Ken Rueegsegger -
Corey Osgood -
David M Barr -
David M. Barr
-
Jeremy Jackson -
Lu, Yinghai -
Philipp Degler -
Stefan Reinauer -
Uwe Hermann