Hello all,
I just got four words for you: It boots now yeah!
Yes it boots my standard Linux kernel (2.6.22) SATA/IDE/USB/soundcard/gigabiteth and my Radeon seems to work. My MB is Asus A8V-E SE. Which might be compatible with A8V-E Duluxe... So someone wants to play too?
However there are some problems left:
1) dualchannel on K8 with unbuffered dimms
Has someone in plan to fix this?
2) something wrong with PCI/RAM resources
LinuxBIOS is telling FILO and FILO tells linux this memmap:
00001000-0009ffff : System RAM 000c0000-000effff : System RAM 00100000-1fffffff : System RAM
But if I use my K8 resource dumper:
MMIO map: #0 0x0000000000 - 0x000000ffff Access: / Dstnode:0 DstLink 0 MMIO map: #1 0x0000000000 - 0x000000ffff Access: / Dstnode:0 DstLink 0 MMIO map: #2 0x0000000000 - 0x000000ffff Access: / Dstnode:0 DstLink 0 MMIO map: #3 0x0000000000 - 0x000000ffff Access: / Dstnode:0 DstLink 0 MMIO map: #4 0x0000000000 - 0x000000ffff Access: / Dstnode:0 DstLink 0 MMIO map: #5 0x00000a0000 - 0x00000cffff Access: R/W Dstnode:0 DstLink 0 MMIO map: #6 0x00fc000000 - 0x00fc2fffff Access: R/W Dstnode:0 DstLink 0 MMIO map: #7 0x00e0000000 - 0x00f7ffffff Access: R/W Dstnode:0 DstLink 0
There is MMIO region up to cffff.
I could not long time catch this bug - the system hung disk IO when the disk buffers hit this region. I thought there is something wrong with V-Link or PCI master. But once I spot this I solved it by passing my own memmap to Linux Kernel.
Question is: any idea why this happened? I'm using default resource map and reasonably old SVN. This seems to be completely undocumented in K8 code...
Perhaps there is something wrong my my memory resource??
3) ROM strapping of some registers does not work properly
I will try to solve it.
4) Fine tuning of some VIA registers.
I will try to solve it.
5) ACPI off, GPIO in SIO, Reset button does not work. PCIe regs tune.
Thanks, Rudolf