Discussion forums for Arch Linux, a simple, lightweight linux distribution.
You are not logged in.
Hi guys,
i'm following this page to porting my system to x86_64.
I'm stucking after the first boot with the kernel26 for x86_64: it hangs when it tries to discover the sata hds.
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata3.00: qc timeout (cmd 0xec) ata3.00: failed to IDENTIFY (I/O error, err_mask=0x104)
It tries 5 times to initialize and then hangs up.
I've tried to use the livecd (2009.08 64bit) and it works flawless.
Now, the differences between the livecd and my system are:
1) version of the kernel (2.6.30 vs. 2.6.31.6)
2) generation of the kernel (mkinitcpio.conf ??? (on my system i've got the default settings))
.
.
.
anything else?
If i could use the livecd kernel on my system i guess i could solve it. Of course, i've to understand what are the differences.
Thanks in advance
Roberto
Last edited by Cagnulein (2009-11-08 14:46:32)
Offline
Did you already try pci=nomsi?
Last edited by daneel971 (2009-11-08 12:39:47)
Offline
Long shot: check in the bios the settings for your sata controller - if ahci mode is enabled, disable it and if it is disabled try enabling it...
I'm not sure, but I'm afraid this means reinstall from scratch and if you have another installation on that disk, maybe you won't be able to access it anymore.
Offline
my motherboard (GigaByte GA-MA69VM-S2) allows me to set these setting for sata controller:
- native ide
- raid
- legacy ide
- sata -> ahci
i've installed arch x86_64 with native ide.
i've tried native ide, legacy ide, sata->ahci with/without pci=nomsi but no one of these combinations works.
i can mount my partition changing this parameter, is it correct for you?
Offline
If you have 4GB ram try with less.
This may be your issue (the onboard SATA controller) even though it is from an old kernel. These kind of problems tend to get reintroduced from time to time.
https://bugzilla.redhat.com/show_bug.cgi?id=242969#c5
https://bugzilla.redhat.com/show_bug.cgi?id=242969#c17
Otherwise, try plugging the drive into another channel.
Edit: Looks like another option is adding mem=3G to kernel parameters.
Last edited by fphillips (2009-11-08 14:18:26)
Offline
i've found this http://www.tomshardware.co.uk/forum/pag … _12_0.html
it seeems very interesting! i'll update the bios and i'll let you know
Offline
The live cd had 2.6.30 kernel, which disabled 64bit DMA on SB600 boards.
Then this patch went in after 2.6.30 was released:
http://git.kernel.org/?p=linux/kernel/g … efbb28b561
With the buggy BIOS, your board couldn't do 64bit DMA with a newer kernel (2.6.31.5).
So, Tejun made a patch to revert that patch and keep all SB600 boards doing 32bit DMA:
http://bugzilla.kernel.org/show_bug.cgi?id=14275#c2
And Greg KH posted a version for review which should be in 2.6.31.6 on kernel .org in a day or two:
http://lkml.org/lkml/2009/11/6/388
How's that for an explanation? ![]()
Good news is with the new BIOS you won't have the problem again.
The stuff about ram was just a workaround.
Offline