Jump to content

qwijibo

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About qwijibo

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. GPU passthrough is broken with current BIOS versions on Ryzen.
  2. Still not working on an Asus Prime board with a 3000 or a 2000 series chip.
  3. I would hold off buying a 3000 series for now. I'm starting to regret buying one. I've had to turn PBO off to get stable temps and stop the chip from over-volting. The whole launch is starting to look like a bit of a mess. https://www.reddit.com/r/Amd/comments/cbls9g/the_final_word_on_idle_voltages_for_3rd_gen_ryzen/
  4. @mattz Just to add I did try the initial BIOS revision that was released for this board. I've also popped a 3700x onto the board which I purchased for my gaming PC and still cannot passthrough either an AMD or NVIDIA gpu. Tried different slots, ACS settings, BIOS settings, the works. This is definitely a board issue and not cpu related. https://www.youtube.com/watch?v=l-WHCCwgyDg
  5. Board is an Asus PRIME X570-PRO. I have tried all released BIOS revisions for the board. This board does let me downgrade. Currently on Version 7010 which is latest and a BETA apparently.
  6. Any suggestions for x570 boards yet? I just upgraded from a b350 due to a broken SATA port and still running a 2600 however I have lost the ability to passthrough any GPU to Win10. Obviously I can't downgrade the bios. VFIO support looks poor at this stage.
  7. I'm running an Asus Prime x570 with a 2600 and GPU passthrough no longer works. Was fine on the B350 it replaced. Obviously I can't roll back my bios so it's a waiting game name.
  8. I replaced the cable and swapped to a different SATA port and has been fine for the past 24 hours. I'm putting it down to a dud cable. Or port. Thanks for the replies.
  9. The only reason i'd suggest the drive is fine is because it was purchased 6 weeks ago and pre-cleared fine before use. I know drives can fail at any time but is it likely within 4 weeks of a pre-clear completing? Parity was done after the new array was set and came up with 0 errors.
  10. Hi all, I had an issue the other day where one of my drives became disabled overnight. Ran a full SMART check and the drive showed no issues, there were no writes being performed at the time so I put it down to a hardware error, changed the SATA cable and re-enabled the drive with the Trust My Array procedure. Runnings through the logs of the drive at the moment I keep seeing these errors. Jun 15 02:45:56 SERVER kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jun 15 02:45:56 SERVER kernel: ata10.00: configured for UDMA/133 Jun 15 02:45:56 SERVER kernel: ata10: EH complete Jun 15 02:45:56 SERVER kernel: ata10.00: sense data available but port frozen Jun 15 02:45:56 SERVER kernel: ata10: limiting SATA link speed to 1.5 Gbps Jun 15 02:45:56 SERVER kernel: ata10.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen Jun 15 02:45:56 SERVER kernel: ata10.00: irq_stat 0x48000001, interface fatal error Jun 15 02:45:56 SERVER kernel: ata10: SError: { UnrecovData 10B8B BadCRC } Jun 15 02:45:56 SERVER kernel: ata10.00: failed command: READ DMA EXT Jun 15 02:45:56 SERVER kernel: ata10.00: cmd 25/00:00:78:df:fa/00:01:2a:03:00/e0 tag 20 dma 131072 in Jun 15 02:45:56 SERVER kernel: ata10.00: status: { DRDY SENSE ERR } Jun 15 02:45:56 SERVER kernel: ata10.00: error: { ICRC ABRT } Jun 15 02:45:56 SERVER kernel: ata10: hard resetting link Jun 15 02:45:57 SERVER kernel: ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 15 02:45:57 SERVER kernel: ata10.00: configured for UDMA/133 Jun 15 02:45:57 SERVER kernel: ata10: EH complete Any ideas what is causing this? I'm confident the drive is fine. Should I be looking at changing the SATA port on my MB? Another dud cable perhaps? Looking through the SMART data I have a tonne of UDMA CRC error's. Cheers