Jerrino

Ok grazie

Mi riattacco a questo post. Per raffreddare al meglio il (futuro) WB della vga, avevo pensato di collegare direttamente al connettore della ventola originale la ventola che andrà a raffreddare il rad da 120 della vga. Non riesco però a trovare le specifiche della ventola stock (12V? 5V?) e soprattutto capire quanto assorbimento in Ampére sopporta la scheda, visto che vorrei metterci 2 ventole in configurazione push/pull. Posso quindi collegare due ventole da 12V in parallelo al connettore della vga?. Tutte queste domande perchè le ventole verranno gestite dalla scheda madre tramite la ROG base

Ecco.. come puoi notare, con una m-atx (lunga 244mm) mi avanzano 7-8 cm nei quali muovermi un po' meglio. Una atx invece coprirebbe tutto.

Il case già ce l'ho, dammi qualche minuto che faccio delle foto Inviato con il mio piccione viaggiatore usando Tapatalk

Compucase 7106B-UG . E sì, è piuttosto angusto. Il problema è che una mb atx ci sta precisa, quindi l'ho sostituita con una microatx, riuscendo a recuperare 6cm, precisi per i radiatori più fini. Visto che devo quindi cambiare, mi chiedevo se fosse migliore la versione 1 rad o 2rad, ora che metto anche la vga sotto liquido Inviato con il mio piccione viaggiatore usando Tapatalk

Questo.. Il problema è che mentre avrei spazio per pompa e vaschetta, non riesco a trovare posto per il rad, che con 10 cm vi va abbondantemente sopra la MB e non riesco a trovare un modo per attaccarlo.

Salve a tutti, sto aggiornando il mio PC aggiungendo alcune parti al mio circuito di cooling EKWB. Metterò sotto liquido anche la VGA (una 780TI che finora stava con il suo dissi stock) e sposterò tutto in un case ATX orizzontale. Ora, visto che nel case dovrei mettere il mio radiatore EKWB da 240mm spesso però 68mm, e non riesco proprio ad infilarcelo (con le ventole diventa quasi 10 cm), avrei optato per la sostituzione con un nuovo radiatore di quelli più sottili, tipo il XSPC EX240 spesso solo 35mm. Ora però mi sorgono dei dubbi: 1- Meglio un rad da 240 con percorso RAD-CPU-VGA, oppure due rad da 120 (tipo il BlackIce GTS 120 Lite da 30mm) con percorso RAD1-CPU-RAD2-VGA???? 2- Attualmente sto usando come refrigerante acqua distillata. Posso (devo???) aggiungere qualche additivo per abbassare ancora di più la temperatura? Grazie a tutti coloro che sapranno rispondermi

Rianimo il post. limata a 150€

Ah è sistemato sì!! Grazie del consiglio fedemini, anche io la penso così

Salve a tutti, un amico mi ha chiesto un consiglio per assemblare un nuovo pc. Premetto che siamo già orientati su un 5820k, vorrei un suggerimento riguardo la scheda video. Meglio una 980 o uno SLI di 960/970? Caratteristica essenziale , 60fps stabili a 1080p dettagli superultramega (al momento non è previsto l'acquisto di un 4k o di un g-sync). Grazie

up

Salve a tutti, come da titolo vendo la mia Asus Maximus VI formula, acquistata a febbraio 2014, ancora in garanzia (fattura disponibile). Vendo causa passaggio ad un fattore di forma diverso (mi serve una m-atx) http://www.asus.com/Motherboards/MAXIMUS_VI_FORMULA/ La scheda è perfetta, ha lavorato attaccata al mio impianto a liquido. Vendo € 190 spedita. Pagamento Postepay o Paypal (con spese a carico di chi compra) Grazie a tutti, ciao

Ciao Kitsune e scusa per il ritardo nella risposta. Allora, le scansioni non potevo farle perchè il disco non veniva inizializzato, in Linux non veniva neanche assegnato un /dev. Ho però (spero) risolto: guardando il disco (un WD Enterprise edition da 1.5TB) ho notato i dati di targa, in particolare l'amperaggio richiesto, 0.5/0.6A. Io invece avevo collegato il disco ad un alimentatore esterno da 2A, con un adattatore plug/molex che non credo filtrasse gli ampere forniti. In pratica ho sovralimentato il disco. Ora, per un po' ha funzionato, poi si è bloccato. Ho quindi recuperato qualche cavetto qua e là e, armato di saldatore, ho realizzato un cavetto per collegare il disco alla UDOO sia tramite l'uscita dedicata la disco (che però dà solo i 5V) che ai connettori GPIO (che invece forniscono i 12V). Adesso il disco è diventato nuovamente accessibile, ho fatto qualche test e sembra tutto a posto. Speriamo che duri!!!

Ciao a tutti, ho un problema (credo a questo punto hardware) con un HDD. Dunque, ho attualmente una board UDOO con la quale ho realizzato un media server domestico. La macchina gira un demone Deluge, Samba, ha un webserver con installato un piccolo sito per le prove, e altri servizi in esecuzione. Ora, qualche tempo fa ho notato che all'avvio il dmesg registra degli errori sull'interfaccia SATA alla quale è collegato l'HDD (alimentato da un alimentatore esterno) questi errori: Jan 1 00:00:16 GameRig kernel: [ 11.226976] ata1: irq_stat 0x00400000, PHY RDY changed Jan 1 00:00:16 GameRig kernel: [ 11.232125] ata1: SError: { Persist PHYRdyChg } Jan 1 00:00:16 GameRig kernel: [ 11.236694] ata1: hard resetting link Jan 1 00:00:16 GameRig kernel: [ 12.503128] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx Jan 1 00:00:16 GameRig kernel: [ 12.503179] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jan 1 00:00:18 GameRig kernel: [ 18.366347] random: nonblocking pool is initialized Jan 1 00:00:21 GameRig kernel: [ 21.242619] ata1: softreset failed (device not ready) Jan 1 00:00:21 GameRig kernel: [ 21.247685] ata1: hard resetting link Jan 1 00:00:31 GameRig kernel: [ 31.282617] ata1: softreset failed (device not ready) Jan 1 00:00:31 GameRig kernel: [ 31.287683] ata1: hard resetting link Jan 1 00:00:42 GameRig kernel: [ 42.312616] ata1: link is slow to respond, please be patient (ready=0) Jan 1 00:01:00 GameRig kernel: [ 60.432629] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 1 00:01:00 GameRig kernel: [ 60.454511] ata1.00: configured for UDMA/133 Jan 1 00:01:00 GameRig kernel: [ 60.454530] ata1: EH complete Jan 1 00:01:02 GameRig kernel: [ 62.507137] ata1: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen Jan 1 00:01:02 GameRig kernel: [ 62.514394] ata1: irq_stat 0x00400000, PHY RDY changed Jan 1 00:01:02 GameRig kernel: [ 62.519540] ata1: SError: { Persist PHYRdyChg } Jan 1 00:01:02 GameRig kernel: [ 62.524115] ata1: hard resetting link Jan 1 00:01:12 GameRig kernel: [ 72.532614] ata1: softreset failed (device not ready) Jan 1 00:01:12 GameRig kernel: [ 72.537675] ata1: hard resetting link Jan 1 00:01:22 GameRig kernel: [ 82.542613] ata1: softreset failed (device not ready) Jan 1 00:01:22 GameRig kernel: [ 82.547674] ata1: hard resetting link Jan 1 00:01:29 GameRig kernel: [ 89.932621] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 1 00:01:29 GameRig kernel: [ 89.949408] ata1.00: configured for UDMA/133 Jan 1 00:01:29 GameRig kernel: [ 89.949423] ata1: EH complete Jan 1 00:01:41 GameRig kernel: [ 101.097910] ata1: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen Jan 1 00:01:41 GameRig kernel: [ 101.105179] ata1: irq_stat 0x00400000, PHY RDY changed Jan 1 00:01:41 GameRig kernel: [ 101.110326] ata1: SError: { Persist PHYRdyChg } Jan 1 00:01:41 GameRig kernel: [ 101.114904] ata1: hard resetting link Jan 1 00:01:51 GameRig kernel: [ 111.122615] ata1: softreset failed (device not ready) Jan 1 00:01:51 GameRig kernel: [ 111.127677] ata1: hard resetting link Jan 1 00:01:55 GameRig kernel: [ 115.732628] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 1 00:01:55 GameRig kernel: [ 115.741262] ata1.00: configured for UDMA/133 Jan 1 00:01:55 GameRig kernel: [ 115.741279] ata1: EH complete Jan 1 00:02:33 GameRig kernel: [ 153.772702] ata1: limiting SATA link speed to 1.5 Gbps Jan 1 00:02:33 GameRig kernel: [ 153.772723] ata1.00: exception Emask 0x10 SAct 0x7fffffc3 SErr 0x10300 action 0xe frozen Jan 1 00:02:33 GameRig kernel: [ 153.780822] ata1.00: irq_stat 0x08400000, interface fatal error, PHY RDY changed Jan 1 00:02:33 GameRig kernel: [ 153.788274] ata1: SError: { UnrecovData Persist PHYRdyChg } Jan 1 00:02:33 GameRig kernel: [ 153.793880] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:33 GameRig kernel: [ 153.799121] ata1.00: cmd 61/00:00:00:98:00/04:00:00:00:00/40 tag 0 ncq 524288 out Jan 1 00:02:33 GameRig kernel: [ 153.799121] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:33 GameRig kernel: [ 153.814611] ata1.00: status: { DRDY } Jan 1 00:02:33 GameRig kernel: [ 153.818279] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:33 GameRig kernel: [ 153.823532] ata1.00: cmd 61/00:08:00:9c:00/04:00:00:00:00/40 tag 1 ncq 524288 out Jan 1 00:02:33 GameRig kernel: [ 153.823532] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:33 GameRig kernel: [ 153.839024] ata1.00: status: { DRDY } Jan 1 00:02:33 GameRig kernel: [ 153.842705] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:33 GameRig kernel: [ 153.847942] ata1.00: cmd 61/00:30:00:38:00/04:00:00:00:00/40 tag 6 ncq 524288 out Jan 1 00:02:33 GameRig kernel: [ 153.847942] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:33 GameRig kernel: [ 153.863429] ata1.00: status: { DRDY } Jan 1 00:02:33 GameRig kernel: [ 153.867097] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:33 GameRig kernel: [ 153.872334] ata1.00: cmd 61/00:38:00:3c:00/04:00:00:00:00/40 tag 7 ncq 524288 out Jan 1 00:02:33 GameRig kernel: [ 153.872334] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:33 GameRig kernel: [ 153.887823] ata1.00: status: { DRDY } Jan 1 00:02:33 GameRig kernel: [ 153.891492] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:33 GameRig kernel: [ 153.896745] ata1.00: cmd 61/00:40:00:10:00/04:00:00:00:00/40 tag 8 ncq 524288 out Jan 1 00:02:33 GameRig kernel: [ 153.896745] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:33 GameRig kernel: [ 153.912239] ata1.00: status: { DRDY } Jan 1 00:02:33 GameRig kernel: [ 153.915921] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:33 GameRig kernel: [ 153.921158] ata1.00: cmd 61/00:48:00:40:00/04:00:00:00:00/40 tag 9 ncq 524288 out Jan 1 00:02:33 GameRig kernel: [ 153.921158] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:33 GameRig kernel: [ 153.936644] ata1.00: status: { DRDY } Jan 1 00:02:33 GameRig kernel: [ 153.940314] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:33 GameRig kernel: [ 153.945568] ata1.00: cmd 61/00:50:00:44:00/04:00:00:00:00/40 tag 10 ncq 524288 out Jan 1 00:02:33 GameRig kernel: [ 153.945568] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:33 GameRig kernel: [ 153.961148] ata1.00: status: { DRDY } Jan 1 00:02:33 GameRig kernel: [ 153.964828] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:33 GameRig kernel: [ 153.970065] ata1.00: cmd 61/00:58:00:48:00/04:00:00:00:00/40 tag 11 ncq 524288 out Jan 1 00:02:33 GameRig kernel: [ 153.970065] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:33 GameRig kernel: [ 153.985639] ata1.00: status: { DRDY } Jan 1 00:02:33 GameRig kernel: [ 153.989306] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:33 GameRig kernel: [ 153.994557] ata1.00: cmd 61/00:60:00:4c:00/04:00:00:00:00/40 tag 12 ncq 524288 out Jan 1 00:02:33 GameRig kernel: [ 153.994557] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:33 GameRig kernel: [ 154.010138] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.013831] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.019071] ata1.00: cmd 61/00:68:00:50:00/04:00:00:00:00/40 tag 13 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.019071] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.034668] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.038339] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.043595] ata1.00: cmd 61/00:70:00:54:00/04:00:00:00:00/40 tag 14 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.043595] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.059180] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.062866] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.068104] ata1.00: cmd 61/00:78:00:58:00/04:00:00:00:00/40 tag 15 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.068104] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.083684] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.087358] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.092614] ata1.00: cmd 61/00:80:00:5c:00/04:00:00:00:00/40 tag 16 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.092614] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.108192] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.111861] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.117117] ata1.00: cmd 61/00:88:00:60:00/04:00:00:00:00/40 tag 17 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.117117] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.132699] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.136368] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.141605] ata1.00: cmd 61/00:90:00:64:00/04:00:00:00:00/40 tag 18 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.141605] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.157179] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.160847] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.166100] ata1.00: cmd 61/00:98:00:68:00/04:00:00:00:00/40 tag 19 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.166100] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.181680] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.185367] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.190604] ata1.00: cmd 61/00:a0:00:6c:00/04:00:00:00:00/40 tag 20 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.190604] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.206180] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.209846] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.215098] ata1.00: cmd 61/00:a8:00:70:00/04:00:00:00:00/40 tag 21 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.215098] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.230679] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.234362] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.239598] ata1.00: cmd 61/00:b0:00:74:00/04:00:00:00:00/40 tag 22 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.239598] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.255173] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.258841] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.264093] ata1.00: cmd 61/00:b8:00:78:00/04:00:00:00:00/40 tag 23 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.264093] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.279674] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.283359] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.288597] ata1.00: cmd 61/00:c0:00:7c:00/04:00:00:00:00/40 tag 24 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.288597] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.304181] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.307857] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.313113] ata1.00: cmd 61/00:c8:00:80:00/04:00:00:00:00/40 tag 25 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.313113] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.328694] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.332364] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.337617] ata1.00: cmd 61/00:d0:00:84:00/04:00:00:00:00/40 tag 26 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.337617] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.353199] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.356867] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.362104] ata1.00: cmd 61/00:d8:00:88:00/04:00:00:00:00/40 tag 27 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.362104] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.377679] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.381347] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.386602] ata1.00: cmd 61/00:e0:00:8c:00/04:00:00:00:00/40 tag 28 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.386602] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.402184] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.405867] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.411104] ata1.00: cmd 61/00:e8:00:90:00/04:00:00:00:00/40 tag 29 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.411104] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.426679] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.430348] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:02:34 GameRig kernel: [ 154.435602] ata1.00: cmd 61/00:f0:00:94:00/04:00:00:00:00/40 tag 30 ncq 524288 out Jan 1 00:02:34 GameRig kernel: [ 154.435602] res 40/00:cc:00:80:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:02:34 GameRig kernel: [ 154.451184] ata1.00: status: { DRDY } Jan 1 00:02:34 GameRig kernel: [ 154.454876] ata1: hard resetting link Jan 1 00:02:44 GameRig kernel: [ 164.462613] ata1: softreset failed (device not ready) Jan 1 00:02:44 GameRig kernel: [ 164.467678] ata1: hard resetting link Jan 1 00:02:54 GameRig kernel: [ 174.472618] ata1: softreset failed (device not ready) Jan 1 00:02:54 GameRig kernel: [ 174.477680] ata1: hard resetting link Jan 1 00:03:01 GameRig kernel: [ 181.662628] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 1 00:03:01 GameRig kernel: [ 181.679619] ata1.00: configured for UDMA/133 Jan 1 00:03:01 GameRig kernel: [ 181.679742] ata1: EH complete Jan 1 00:03:02 GameRig kernel: [ 182.100672] ata1: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen Jan 1 00:03:02 GameRig kernel: [ 182.107944] ata1: irq_stat 0x00400000, PHY RDY changed Jan 1 00:03:02 GameRig kernel: [ 182.113116] ata1: SError: { Persist PHYRdyChg } Jan 1 00:03:02 GameRig kernel: [ 182.117663] ata1: hard resetting link Jan 1 00:03:12 GameRig kernel: [ 192.122617] ata1: softreset failed (device not ready) Jan 1 00:03:12 GameRig kernel: [ 192.127681] ata1: hard resetting link Jan 1 00:03:16 GameRig kernel: [ 196.072638] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 1 00:03:16 GameRig kernel: [ 196.082287] ata1.00: configured for UDMA/133 Jan 1 00:03:16 GameRig kernel: [ 196.082304] ata1: EH complete Jan 1 00:03:18 GameRig kernel: [ 198.123164] ata1: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen Jan 1 00:03:18 GameRig kernel: [ 198.130393] ata1: irq_stat 0x00400000, PHY RDY changed Jan 1 00:03:18 GameRig kernel: [ 198.135578] ata1: SError: { Persist PHYRdyChg } Jan 1 00:03:18 GameRig kernel: [ 198.140124] ata1: hard resetting link Jan 1 00:03:28 GameRig kernel: [ 208.142613] ata1: softreset failed (device not ready) Jan 1 00:03:28 GameRig kernel: [ 208.147674] ata1: hard resetting link Jan 1 00:03:38 GameRig kernel: [ 218.152614] ata1: softreset failed (device not ready) Jan 1 00:03:38 GameRig kernel: [ 218.157673] ata1: hard resetting link Jan 1 00:03:49 GameRig kernel: [ 229.182616] ata1: link is slow to respond, please be patient (ready=0) Jan 1 00:04:13 GameRig kernel: [ 253.182619] ata1: softreset failed (device not ready) Jan 1 00:04:13 GameRig kernel: [ 253.187682] ata1: hard resetting link Jan 1 00:04:18 GameRig kernel: [ 258.372615] ata1: softreset failed (device not ready) Jan 1 00:04:18 GameRig kernel: [ 258.377677] ata1: reset failed, giving up Jan 1 00:04:18 GameRig kernel: [ 258.381692] ata1.00: disabled Jan 1 00:04:18 GameRig kernel: [ 258.381715] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4050202 action 0xe frozen t4 Jan 1 00:04:18 GameRig kernel: [ 258.389409] ata1: irq_stat 0x00400040, connection status changed Jan 1 00:04:18 GameRig kernel: [ 258.395452] ata1: SError: { RecovComm Persist PHYRdyChg CommWake DevExch } Jan 1 00:04:18 GameRig kernel: [ 258.402344] ata1: hard resetting link Jan 1 00:04:28 GameRig kernel: [ 268.402615] ata1: softreset failed (device not ready) Jan 1 00:04:28 GameRig kernel: [ 268.407676] ata1: hard resetting link Jan 1 00:04:38 GameRig kernel: [ 278.412621] ata1: softreset failed (device not ready) Jan 1 00:04:38 GameRig kernel: [ 278.417681] ata1: hard resetting link Jan 1 00:04:49 GameRig kernel: [ 289.322625] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 1 00:04:49 GameRig kernel: [ 289.329451] ata1.00: ATA-8: WDC WD1502FYPS-02W3B0, 04.01G01, max UDMA/133 Jan 1 00:04:49 GameRig kernel: [ 289.329463] ata1.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32) Jan 1 00:04:49 GameRig kernel: [ 289.332363] ata1.00: configured for UDMA/133 Jan 1 00:04:49 GameRig kernel: [ 289.332386] ata1: EH complete Jan 1 00:04:49 GameRig kernel: [ 289.332415] ata1.00: detaching (SCSI 0:0:0:0) Jan 1 00:04:49 GameRig kernel: [ 289.343995] sd 0:0:0:0: [sda] Synchronizing SCSI cache Jan 1 00:04:49 GameRig kernel: [ 289.344158] sd 0:0:0:0: [sda] Stopping disk Jan 1 00:04:49 GameRig kernel: [ 289.422691] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen Jan 1 00:04:49 GameRig kernel: [ 289.430186] ata1.00: irq_stat 0x00400000, PHY RDY changed Jan 1 00:04:49 GameRig kernel: [ 289.435628] ata1: SError: { Persist PHYRdyChg } Jan 1 00:04:49 GameRig kernel: [ 289.440175] ata1.00: failed command: STANDBY IMMEDIATE Jan 1 00:04:49 GameRig kernel: [ 289.445347] ata1.00: cmd e0/00:00:00:00:00/00:00:00:00:00/a0 tag 21 Jan 1 00:04:49 GameRig kernel: [ 289.445347] res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error) Jan 1 00:04:49 GameRig kernel: [ 289.459633] ata1.00: status: { DRDY } Jan 1 00:04:49 GameRig kernel: [ 289.463325] ata1: hard resetting link Jan 1 00:04:59 GameRig kernel: [ 299.472624] ata1: softreset failed (device not ready) Jan 1 00:04:59 GameRig kernel: [ 299.477689] ata1: hard resetting link Jan 1 00:05:03 GameRig kernel: [ 303.422625] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 1 00:05:03 GameRig kernel: [ 303.434857] ata1.00: configured for UDMA/133 Jan 1 00:05:03 GameRig kernel: [ 303.434876] ata1.00: device reported invalid CHS sector 0 Jan 1 00:05:03 GameRig kernel: [ 303.434908] ata1: EH complete Jan 1 00:05:03 GameRig kernel: [ 303.434935] sd 0:0:0:0: [sda] START_STOP FAILED Jan 1 00:05:03 GameRig kernel: [ 303.434948] sd 0:0:0:0: [sda] Jan 1 00:05:03 GameRig kernel: [ 303.434956] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Jan 1 00:05:03 GameRig kernel: [ 303.434965] sd 0:0:0:0: [sda] Jan 1 00:05:03 GameRig kernel: [ 303.434971] Sense Key : Aborted Command [current] [descriptor] Jan 1 00:05:03 GameRig kernel: [ 303.434984] sd 0:0:0:0: [sda] Jan 1 00:05:03 GameRig kernel: [ 303.434991] Add. Sense: No additional sense information Jan 1 00:05:03 GameRig kernel: [ 303.562960] scsi 0:0:0:0: Direct-Access ATA WDC WD1502FYPS-0 1G01 PQ: 0 ANSI: 5 Jan 1 00:05:03 GameRig kernel: [ 303.563986] sd 0:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) Jan 1 00:05:03 GameRig kernel: [ 303.564234] sd 0:0:0:0: [sda] Write Protect is off Jan 1 00:05:03 GameRig kernel: [ 303.564247] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Jan 1 00:05:03 GameRig kernel: [ 303.564354] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 1 00:05:03 GameRig kernel: [ 303.565347] sd 0:0:0:0: Attached scsi generic sg0 type 0 Jan 1 00:05:03 GameRig kernel: [ 303.571179] sda: unknown partition table Jan 1 00:05:03 GameRig kernel: [ 303.572209] sd 0:0:0:0: [sda] Attached SCSI disk Jan 1 00:05:05 GameRig kernel: [ 305.675775] ata1: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen Jan 1 00:05:05 GameRig kernel: [ 305.683047] ata1: irq_stat 0x00400000, PHY RDY changed Jan 1 00:05:05 GameRig kernel: [ 305.688193] ata1: SError: { Persist PHYRdyChg } Jan 1 00:05:05 GameRig kernel: [ 305.692777] ata1: hard resetting link Jan 1 00:05:15 GameRig kernel: [ 315.702621] ata1: softreset failed (device not ready) Jan 1 00:05:15 GameRig kernel: [ 315.707685] ata1: hard resetting link Jan 1 00:05:25 GameRig kernel: [ 325.712626] ata1: softreset failed (device not ready) Jan 1 00:05:25 GameRig kernel: [ 325.717697] ata1: hard resetting link Jan 1 00:05:36 GameRig kernel: [ 336.742620] ata1: link is slow to respond, please be patient (ready=0) Jan 1 00:06:00 GameRig kernel: [ 360.262643] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 1 00:06:00 GameRig kernel: [ 360.282998] ata1.00: configured for UDMA/133 Jan 1 00:06:00 GameRig kernel: [ 360.283014] ata1: EH complete Jan 1 00:06:00 GameRig kernel: [ 360.492673] ata1.00: exception Emask 0x10 SAct 0x7f0000 SErr 0x10300 action 0xe frozen Jan 1 00:06:00 GameRig kernel: [ 360.500604] ata1.00: irq_stat 0x08400000, interface fatal error, PHY RDY changed Jan 1 00:06:00 GameRig kernel: [ 360.508059] ata1: SError: { UnrecovData Persist PHYRdyChg } Jan 1 00:06:00 GameRig kernel: [ 360.513674] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:06:00 GameRig kernel: [ 360.518914] ata1.00: cmd 61/00:80:00:84:00/04:00:00:00:00/40 tag 16 ncq 524288 out Jan 1 00:06:00 GameRig kernel: [ 360.518914] res 40/00:b4:00:88:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:06:00 GameRig kernel: [ 360.534495] ata1.00: status: { DRDY } Jan 1 00:06:00 GameRig kernel: [ 360.538163] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:06:00 GameRig kernel: [ 360.543425] ata1.00: cmd 61/00:88:00:8c:00/04:00:00:00:00/40 tag 17 ncq 524288 out Jan 1 00:06:00 GameRig kernel: [ 360.543425] res 40/00:b4:00:88:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:06:00 GameRig kernel: [ 360.559006] ata1.00: status: { DRDY } Jan 1 00:06:00 GameRig kernel: [ 360.562693] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:06:00 GameRig kernel: [ 360.567931] ata1.00: cmd 61/00:90:00:90:00/04:00:00:00:00/40 tag 18 ncq 524288 out Jan 1 00:06:00 GameRig kernel: [ 360.567931] res 40/00:b4:00:88:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:06:00 GameRig kernel: [ 360.583510] ata1.00: status: { DRDY } Jan 1 00:06:00 GameRig kernel: [ 360.587178] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:06:00 GameRig kernel: [ 360.592414] ata1.00: cmd 61/00:98:00:94:00/04:00:00:00:00/40 tag 19 ncq 524288 out Jan 1 00:06:00 GameRig kernel: [ 360.592414] res 40/00:b4:00:88:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:06:00 GameRig kernel: [ 360.607992] ata1.00: status: { DRDY } Jan 1 00:06:00 GameRig kernel: [ 360.611660] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:06:00 GameRig kernel: [ 360.616915] ata1.00: cmd 61/00:a0:00:98:00/04:00:00:00:00/40 tag 20 ncq 524288 out Jan 1 00:06:00 GameRig kernel: [ 360.616915] res 40/00:b4:00:88:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:06:00 GameRig kernel: [ 360.632493] ata1.00: status: { DRDY } Jan 1 00:06:00 GameRig kernel: [ 360.636177] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:06:00 GameRig kernel: [ 360.641415] ata1.00: cmd 61/00:a8:00:9c:00/04:00:00:00:00/40 tag 21 ncq 524288 out Jan 1 00:06:00 GameRig kernel: [ 360.641415] res 40/00:b4:00:88:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:06:00 GameRig kernel: [ 360.656994] ata1.00: status: { DRDY } Jan 1 00:06:00 GameRig kernel: [ 360.660662] ata1.00: failed command: WRITE FPDMA QUEUED Jan 1 00:06:00 GameRig kernel: [ 360.665918] ata1.00: cmd 61/00:b0:00:88:00/04:00:00:00:00/40 tag 22 ncq 524288 out Jan 1 00:06:00 GameRig kernel: [ 360.665918] res 40/00:b4:00:88:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 1 00:06:00 GameRig kernel: [ 360.681504] ata1.00: status: { DRDY } Jan 1 00:06:00 GameRig kernel: [ 360.685198] ata1: hard resetting link Gli errori "ata1.00: failed command: WRITE FPDMA QUEUED" sono comparsi dopo il classico comando dd if=/dev/zero of=/dev/sda Comunque, ho staccato il disco dalla board e l'ho collegato al mio pc (con Mint17) e dmesg registra questo output: [ 36.906578] ata7.00: qc timeout (cmd 0xec) [ 37.115241] ata7.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 37.115243] ata7.00: revalidation failed (errno=-5) [ 37.115246] ata7: hard resetting link [ 37.608622] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 38.827131] ata8: limiting SATA link speed to 1.5 Gbps [ 38.827133] ata8: hard resetting link [ 38.987029] ata7.00: configured for UDMA/133 [ 38.987034] ata7: EH complete [ 39.995118] ata8: link resume succeeded after 3 retries [ 42.050065] ata8: COMRESET failed (errno=-32) [ 42.149654] ata8: reset failed (errno=-32), retrying in 7 secs [ 48.885038] ata8: hard resetting link [ 50.330485] ata8: failed to resume link (SControl FFFFFFFF) [ 50.331834] ata8: SATA link down (SStatus 0 SControl 3F0) [ 50.332453] ata8: EH complete [ 55.337488] ata7.00: qc timeout (cmd 0x2f) [ 55.338068] ata7: failed to read log page 10h (errno=-5) [ 55.338071] ata7.00: exception Emask 0x1 SAct 0x1 SErr 0x0 action 0x6 frozen [ 55.338072] ata7.00: irq_stat 0x40000008 [ 55.338073] ata7.00: failed command: READ FPDMA QUEUED [ 55.338076] ata7.00: cmd 60/08:00:18:00:00/00:00:00:00:00/40 tag 0 ncq 4096 in [ 55.338076] res 40/00:04:18:00:00/00:00:00:00:00/40 Emask 0x1 (device error) [ 55.338077] ata7.00: status: { DRDY } [ 55.338079] ata7: hard resetting link [ 56.052643] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 56.052994] ata7.00: link online but device misclassified [ 61.061845] ata7.00: qc timeout (cmd 0xec) [ 61.274553] ata7.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 61.274555] ata7.00: revalidation failed (errno=-5) [ 61.274556] ata7: hard resetting link [ 61.767653] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) La parte che mi interessa è quella riguardante ata7. Il problema è che non riesco ad operare sul disco in quanto neanche fdisk "vede" il disco, ma soprattutto dopo pochissimi minuti il PC va in freeze e sono costretto a riavviarlo a mano. Devo buttare il disco o ho qualche speranza di recuperarlo? Grazie per l'attenzione PS. Ho provato anche con Windows ma si blocca anche lì (ma questo non è strano no?? ) EDIT: ho recuperato l'ultimo log della UDOO

Enermax T.B. SILENCE Fan UCTB12 - 120mm

Allora breve aggiornamento: le ventole non sono riconosciute da speedfan perché sembra (leggendo in giro) che il programma non vada molto è'accordo con le schede Asus più recenti. Va beh.. Poi, le ventole non salgono oltre i 900 giri perché.. è la loro velocità massima!!!! Sono delle Enermax serie Silent. Io pensavo che il silentq fosse riferito alla particolare forma delle pale che smorza il rumore prodotto, invece, semplicemente, girano piano! Mah.. Ora comunque ho montato le ventole originali EKWB che hanno una rotazione massima di 1600 giri, e infatti subito la velocità di rotazione in idle è salita a 1200 giri. Peccato che fischiano come una locomotiva. Devo sostituirle.. accetto suggerimenti! Ora provo qualche test e vediamo l'effetto che fa.

Ecco una cosa carina.. Speedfan non vede le ventole!!! [ATTACH=CONFIG]4821[/ATTACH]

Ciao Le085, si la pompa gira, le ventole girano e il loop dovrebbe essere a posto (pompa-rad-cpu-nb-vaschetta) ma le ventole proprio non si muovono dai 900 giri. Come ho già detto, sia disabilitando q-fan (e così la ai suite neanche riconosce la ventola cpu) né con q-fan in advanced mode. Nel bios ho messo che a 70 gradi la ventola deve girare al 100%, ma durante i test arriva a 80 gradi e le ventole non salgono.

Ciao a tutti, scusate il titolo ma sto avendo problemi con la corretta configurazione delle ventole per il mio setup. Premessa: ho notato durante alcuni giochi (Skyrim in particolare) frequenti crash con scene piuttosto impegnative. Pensando che fossero le numerose mod installate, ho reinstallato il gioco "liscio", ma con mio stupore il gioco continuava a crashare sempre all'incirca negli stessi punti. Allora ho pensato ad un problema di temperature. E qui è iniziata l'avventura. Passando vari tools come OCCT e realtemp, sia disabilitando il Q-Fan della mia mobo Asus, che abilitandolo in Advanced Mode (come suggerito per ventole a 3 pin come le mie), la velocità di rotazione resta fissa intorno ai 900 giri, come riportato dalla AI Suite III. con la CPU che arriva a sfiorare gli 80°. Usando il tool di configurazione della stessa suite, in teoria se clicco sopra il pulsante "Turbo Mode", le ventole dovrebbero iniziare a girare all'impazzata, ma purtroppo non è così. Mi aiutate a capire se ho sbagliato qualche connessione? Questo è il mio sistema: Pompa EKWB collegata direttamente all'alimentatore; Ventole (a 3 pin, quelle fornite con il kit EKWB) del rad da 240 collegate una al connettore CPU_FAN, una al CPU_OPT, ventola in estrazione per lo chassis collegata su CHA_FAN1

Ok, valuterò le cose. Comunque dei minidissipatori passivi sarebbero l'ideale, giusto?

Allora, ho preso due misure, e dal retro della scheda al bordo inferiore della RAM ci sono 18 mm, molti di meno dei circa 23 che ne servirebbero. Avrei quindi due possibilità: 1 - Spostare la scheda dallo slot PCI-E 1 allo slot PCI-E 3, ma in questo modo avrei la scheda sul bus a 8 linee e non su quello a 16, giusto? 2 - Grattare via mezzo centimetro di alette a colpi di Dremel e farcelo entrare per forza. Cè però un punto che mi perplime non poco: i chip VRM con questo sistema restano scoperti, giusto? Non potrebbe diventare un problema? Volevo usare questo sistema perchè più economico di un waterblock da aggiungere al mio circuito. Per essere efficace dovrei aggiungere anche un ulteriore radiatore tra l'uscita dalla CPU e l'entrata nella VGA. Esistono quindi delle alternative all'accelero, oltre all'accoppiata NZXT G10+x40?

Ciao a tutti, ho un dubbione che mi assale: vorrei acquistare il suddetto, ma mi chiedo se entra in una mobo con chipset Z87. Nella mia Maximus VI Formula ho come l'impressione che l'heatsink posteriore vada a sbattere conto i banchi di RAM. C'è qualcuno che ha provato?

Ho provato, ma se possibile è anche peggio, non so come mai.. ho provato a "spingere" un po' di più la scheda, ma a parte la ventola all'80% non ho ottenuto risultati apprezzabili..

Yes, 1.03

Ciao a tutti, pongo una semplice domanda: è possibile secondo voi che il gioco in oggetto ogni tanto cali sensibilmente le prestazioni con un hardware come in firma? Mi spiego: ho settato tutto al massimo (anche il GeForce experience mi setta tutto al massimo), e generalmente riesco a giocare in maniera piuttosto fluida a 60 fps stabili con vsync attivato. Però durante qualche scena un po' più concitata, o addirittura durante i filmati, gli FPS calano talvolta anche sotto i 30. C'è qualcosa che posso fare o la mia unica possibilità è diminuire i livelli di dettaglio (cosa che non vorrei)? Grazie