(2x1GB DDR2-667 and a E2160 (FSB200, 9x); heatsink is asus v60 and gfx is geforce 7800gs AGP)
On the other front (overclocking), by enabling the ram tolerance mode or whatever it's called, I've managed to push it to a maximum of 266 (which is a 33% overclock already; I'm quite satisfied) in a stable way (compiled some reasonably big stuff without problems).
I've done tests where I got the motherboard _crazy_, at >=273 or so it would somehow change its clocks math, making the cpu run at 1.80. Worst of it was that lowering it or setting it to auto would not fix a thing (getting 1.5GHz?!), and also it would show "175" when in auto mode instead of "200". I believe it's the same problem somebody talked about already a page or two ago. Do newer BIOSes fix it? Again, I'm still with 1.5, and will be until I install some version of Windows (I'm lazy, but I'll prolly go for XP Pro 64). To get things back into sanity, I had to try again pushing things really hard (300) and it somehow sometimes reverted back to sanity the confortable way (math is right again all of a sudden) or the CMOS was corrupted and I had to re-setup everything (still better than having to open the case and placing the jumper... there are a lot of cables which make that a hell).
So far, as we know, the point of this board is that it supports SATA 3Gb/s transfer mode (hence the name). The Seagate I got (ST3500320AS) had a jumper preset in to force compat. mode (and get just 1.5Gb) instead of autonegotiation, but removing it does not help; it runs in the slow mode. This is the relevant part of dmesg, the kernel is 2.6.24-rc6:Originally posted by: brokencase
ayumu, I also plan to run linux on this board. I did read that there were some compatability issues with the VIA chip set. Something about the SATA not seen correctly.
Did you run into any problems? Were you able to get the on board audio to work?
About the onboard audio; yes, it does work (alsa, pci, intel hda), but without hardware mixing (as with most integrated audio chipsets) and without controls for bass/tremble. Luckily, I have my trusty emu10k1 (sblive!, pci) from ages ago, which works like a charm on Linux, with hardware mixing and bass/tremble.[ 24.044152] sata_via 0000:00:0f.0: version 2.3
[ 24.044175] ACPI: PCI Interrupt 0000:00:0f.0(B) -> GSI 21 (level, low) -> IRQ 21
[ 24.044332] sata_via 0000:00:0f.0: routed to hard irq line 5
[ 24.044462] scsi0 : sata_via
[ 24.044573] scsi1 : sata_via
[ 24.045903] ata1: SATA max UDMA/133 cmd 0xdc00 ctl 0xd880 bmdma 0xd400 irq 21
[ 24.045973] ata2: SATA max UDMA/133 cmd 0xd800 ctl 0xd480 bmdma 0xd408 irq 21
[ 24.246084] ata1: SATA link up 1.5 Gbps (SStatus 123 SControl 300)
[ 24.266993] Switched to high resolution mode on CPU 1
[ 24.267044] Switched to high resolution mode on CPU 0
[ 24.399420] ata1.00: ATA-7: ST3500320AS, SD04, max UDMA/133
[ 24.399487] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 24.405403] ata1.00: configured for UDMA/133
[ 24.605488] ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
[ 24.616371] scsi 0:0:0:0: Direct-Access ATA ST3500320AS SD04 PQ: 0 ANSI: 5
[ 24.616537] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
[ 24.616612] sd 0:0:0:0: [sda] Write Protect is off
[ 24.616678] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 24.616690] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 24.616808] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
[ 24.616882] sd 0:0:0:0: [sda] Write Protect is off
[ 24.616948] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 24.616959] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 24.617038] sda: sda1 sda2
[ 24.622692] sd 0:0:0:0: [sda] Attached SCSI disk
On the other front (overclocking), by enabling the ram tolerance mode or whatever it's called, I've managed to push it to a maximum of 266 (which is a 33% overclock already; I'm quite satisfied) in a stable way (compiled some reasonably big stuff without problems).
I've done tests where I got the motherboard _crazy_, at >=273 or so it would somehow change its clocks math, making the cpu run at 1.80. Worst of it was that lowering it or setting it to auto would not fix a thing (getting 1.5GHz?!), and also it would show "175" when in auto mode instead of "200". I believe it's the same problem somebody talked about already a page or two ago. Do newer BIOSes fix it? Again, I'm still with 1.5, and will be until I install some version of Windows (I'm lazy, but I'll prolly go for XP Pro 64). To get things back into sanity, I had to try again pushing things really hard (300) and it somehow sometimes reverted back to sanity the confortable way (math is right again all of a sudden) or the CMOS was corrupted and I had to re-setup everything (still better than having to open the case and placing the jumper... there are a lot of cables which make that a hell).