Gigabyte GA-N680SLI-DQ6 ?

RosenSama · Tux's lil' helper Joined: 28 Apr 2003 Posts: 99

mm-sources 2.6.22_rc4-mm2 is a no go. I get "failed to set xfermode" from sata_nv devices before the kernel boot hangs. There are messages to this effect on lkml, so too bleeding edge for me.

gentoo-sources 2.6.21-r3 has the same behavior as 2.6.20-r8

If it's a hardware problem, it's the motherboard and I think it's unlikely that both ports on both jmicron SATA controllers would fail identically.

If I do an fdisk -l after booting with these errors, I see the activity lights flicker on the failed drives.

I think I'll try booting some other OS with AHCI support to see how it recognizes things.

RosenSama · Tux's lil' helper Joined: 28 Apr 2003 Posts: 99

FreeBSD 6.2 install CD also has trouble with any drives attached to the JMicron controllers. Maybe a bum mobo?

RosenSama · Tux's lil' helper Joined: 28 Apr 2003 Posts: 99

Any owners of the board using the JMicron SATA ports successfully?

sp0rk · n00b Joined: 05 Apr 2005 Posts: 10

hi,

I got this mobo in my pc since 3 months ago and I've always run a windows vista on this system since I didnt find the time to fix my linux....Now that I've got some time I'd like to fix it....

Anyhow I'm also expierncing problems with the marvell NIC's...

the livecd recognises the NIC's and they all work fine, but in the 2.6.22 kernel I've selected the build-in Marvell NIC driver but after the reboot...it just doesnt recognize eth0

I haven't got any problems yet with the sata drivers but hey....i'm still trying to get my system up and running

_________________
Do not morn about your unborn beauty

"I was brought up Catholic. Then I had a joint and looked at the world differently."
--Liam Gallagher

RosenSama · Tux's lil' helper Joined: 28 Apr 2003 Posts: 99

I'm pretty sure my SATA issues are due to too long of a cable run to an external exclosure. Specifically, I think the standard internal cables in the enclosure and host are too long combined with the infiniband cable.

I think you need the sky2 driver for the NICs. You may need forcedeth for the other two.

sp0rk · n00b Joined: 05 Apr 2005 Posts: 10

ok, so i've tried to use the sky2 driver but still i get no connection....now i'll try that other one

thx though ^^

and sata cables that are too long ? u didnt use the ones that gigabyte provided with the motherboard.?

EDIT:
network driver fixed
_________________
Do not morn about your unborn beauty

"I was brought up Catholic. Then I had a joint and looked at the world differently."
--Liam Gallagher

sp0rk · n00b Joined: 05 Apr 2005 Posts: 10

did you managed to fix your alsa ? can you pls tell me how ? cuz i cant (
_________________
Do not morn about your unborn beauty

"I was brought up Catholic. Then I had a joint and looked at the world differently."
--Liam Gallagher

sp0rk · n00b Joined: 05 Apr 2005 Posts: 10

did u manage to fix ur alsa? not able to do that either lol

well its working but not giving sound

_________________
Do not morn about your unborn beauty

"I was brought up Catholic. Then I had a joint and looked at the world differently."
--Liam Gallagher

niuck · n00b Joined: 16 Mar 2005 Posts: 60

tnt · Veteran Joined: 27 Feb 2004 Posts: 1227

gentoo-sources 2.6.22-r6

GA-P35-DS3R works without a problem (uptime >20 days without idling)

all controlers are set to AHCI in BIOS and AHCI driver is used in kernel:

niuck · n00b Joined: 16 Mar 2005 Posts: 60

I solved it by moving the Maxtor 200 sata from the gigabyte sata2-chip to the ICH9R.
And before when i was trying to boot windows (shame on me) i had to wait for a minute or so until it finally began to start. But all good now.

edit: hmm, looks like the errors are back. doh!