armbrust

Members
  • Content Count

    56
  • Joined

  • Last visited

Community Reputation

0 Neutral

About armbrust

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Thanks Warrentheo for the ideas.. removing xvga='yes' prevents it from crashing, but also prevents the VM from booting in either 6.7.2 or 6.6.1. I did dump the rom from this card, but I'll try to do it again - the problem is according to space invaders video you need to run it in a VM first.. I do have another GPU in the system.. perhaps I can somehow make it the primary.. Creating a new VM using the same image has the same results as the existing VM.
  2. A couple other things I tried without success: Bind the GPU to the vfio driver: apped vfio-pci.ids=10de:1d01,10de:0fb8 Append pcie_aspm=off video=vesafb:off,efifb:off in syslinux config
  3. Thanks for the comment, I appreciate the time. Agreed that this is old hardware. But pass through has been working well for me prior to 6.7.x. Something has changed from 6.x.x -> 6.7.x. Unfortunately I do have the latest BIOS. I'm hoping there is a work around for 6.7.x as I don't want to get left behind in versions, and don't want to buy new hardware.
  4. Moving from 6.6.7 to either 6.7.0, 6.7.1 6.7.2 all have the same issue. Everything works correctly, except starting a VM that has a GPU passed through. When starting this VM the system crashes. I've attached diagnostics from both versions (6.6.7 and 6.7.2), just before starting the VM. Nothing was changed in the configuration between runs. There is another VM running fine in both cases. It has nothing passed through. Also attached is the xml config of the problem VM. I tailed the syslog in both versions when starting the VM, and they look the same
  5. Thanks for the reply, unfortunately no luck. This is the syslog at the time of VM start. Jun 25 21:44:17 Tower kernel: vfio-pci 0000:0a:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Jun 25 21:44:17 Tower kernel: br0: port 3(vnet2) entered blocking state Jun 25 21:44:17 Tower kernel: br0: port 3(vnet2) entered disabled state Jun 25 21:44:17 Tower kernel: device vnet2 entered promiscuous mode Jun 25 21:44:17 Tower kernel: br0: port 3(vnet2) entered blocking state Jun 25 21:44:17 Tower kernel: br0: port 3(vnet2) entered forwarding state Jun 25 21:44:18 Towe
  6. Hi, I tried upgrading from 6.6.7, and experiance a hard crash, when the VMs were started. For a few seconds, The GUI was available, but then the system rebooted, and came back with the VM manger disabled. When I enabled the VM manger, the system crashed (no web GUI didn't respond to pings), and didn't come back. I rebooted into safe mode, captured a diagnostic file, and reverted to 6.6.7. Back to 6.6.7 and all is well. The same thing happened when trying to upgrade to 6.7.0 from 6.6.7. The attached diagnostic file was captured in 6.7.1 safe mode.
  7. Thanks, figure it out. Had to manually create the "docker" sub folder on the cache drive. The tab shows up now, so I assume I'm good to go. Thanks again
  8. Thanks for the reply. Yes, I do have a cache drive. Should I see a docker tab in the ui?
  9. Has something changed since when the guide was written? i don't have a main docker tab, only a docker option under settings. I change enable to yes, and hit apply, but nothing seems to happen.
  10. Update: After the last rebuild, the drive *seems* to be stable - hasn't dropped out yet. These were the changes I made: -Put the tunables back to default -Added acpi=off libata.force=noncq to syslinux.cfg
  11. Uraid 4.7 I have a segate BARRACUDA GREEN Model Number: ST2000DL003 drive that has started acting up. It is my parity drive. What happens is that it just dissapears from the system, parity is invalidated. I can restart the system (hard turn off power) and it returns. In the smart test everything appears normal. Also, I've tried different power and sata cables and sata ports. The last time this happened I restarted, and did a parity rebuild. It finished fine, but shortly after the drive dropped off. Here is a section of the system log after the partiy rebuild fini
  12. Thanks for taking the time to comment. Will do. Now, buy a replacement drive, or move stuff off temporarily. Pondering...
  13. I have the same stituation/question -- And I guessing the same answer - RMA. I did a short test on the Drive. Here is the smartctl output after the short test. I'm running a long test now. Any comments appreciated. Thanks SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 194 194 051 Pre-fail Always - 12786 3 Spin_Up_Time 0x0027 186 163 021 Pre-fail
  14. armbrust

    Tablet...

    2nd the transformer. Has an micro SD slot, plays most everything - use plex and a plex server and you can have access to all your online media. Much better deal then the ipad IMO.