AndyT86

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

2 Neutral

About AndyT86

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Your commands: wget http://slackware.cs.utah.edu/pub/slackware/slackware64-current/slackware64/l/json-c-0.15_20200726-x86_64-1.txz upgradepkg --install-new json-c-0.15_20200726-x86_64-1.txz work perfectly. But nerdpack is not working at all for JSON-C. I tried many many times to get nerdpack to work correctly. "Host" has dependencies in kbd, json-c and libgssi-kbd (and perhaps more I had already) I could not get past json-c dependency. I was not sure if you were saying you updated NERD pack recently to the new version, but it does not appear to work.
  2. Did you ever solve this. I am having a similar issue. I have 2 cards, a LSI 9207-8e and an LSI 9207-8i (SAS2308). I can get 1 drive to show on one card, and none on the other. Even in bios option rom, all three of my LSI SAS cards are showing. One is working correctly (the old 2008) but neither of the two new ones. I have a bunch of cables to try. They have all been tried, with no success. I have 6 or 8. Everyone always seems to just throw out the "its a reverse cable" claim. But why does *everyone* have a reverse cable and what would you do with
  3. In our unknown device: Address is 001F0003 And BIOS name is: \_SB.PCI0.SMB0 Further- if we go to Linux and run lspci: At that address (00:1f.3) we have SMBus: Intel 8280I ICH9 Family SMBus Controller. HOWEVER, installing the Intel SMBus Controller Driver does NOT help. There is in fact already a SMBus Device installed Going to the VirtIO cd, there is in fact a folder named SMBus. However both drivers do NOT work, and its only "2k8\[x86 or x64]" There is no Windows 10 folder.
  4. In addition: ACPI Proc Container Device has a different Hardware ID - most notably DEV_0010. We can get some more info: Last known parent is ACPI\PNP0A08\1 The Parent of ACPI Processor Container Device is ACPI_HAL\PNP0C08\0 Further the SIBLING of ACPI Processor Container Device is ACPI\PNP0A08\1 which means we have ControllerRoot | - ACPI Processor Container Device (ACPI\ACPI0010\2&DABA3FF&0) and othernames | -ACPI\PNP0A08\1 | |- Our mystery device | |- ACPI\PBP0A06\CP
  5. searching for the device ID only returns a handful of hits, all but two are unraid (this thread) etc. Another is https://seandheath.com/windows-acpi-driver/ which just says the above: and So no help. It's interesting others list this as working, but others of us its not. It also appears UNRAID specific, as if were more generally a Windows or QEMU or OVMF related issue, there would be many more hits and not all of them would be UNRAID. So its unclear what this is and what the issue is.
  6. I found the Driver he's talking about Browse My Computer Let me pick from list System Devices *then the missing step above* On left do (Standard System Devices), Then on the right "ACPI Processor Container Device" This gets me to AntaresUK's solution, of selecting the driver he specifies that people couldnt find. HOWEVER, I still get the different icon, but still "Unknown Device" shown by DrJake. So its not a true resolution.
  7. Also. since I spent 15 minutes hinting for it. in every possible menu. "Advanced View," its the little button, top right, in the Docker Menu. It says "Basic View" by default until you click it. Theres two types of people here, the people who know all this that cant explain for shit because its obvious to them and the people who have no clue so they are on the message board looking for answers. We need to work on connecting those two. (looking at you Squid, you clearly know this stuff inside and out, but your answers leave a lot to be desired- especially linking to vaguely related pos
  8. Thank you. Good lord people. How f-ing hard was it to answer this question. It only took 3 threads with >10 posts each. So unclear, by default there is absolutley no hint of "slave" or anyway to change some option. It reminds me of the 'how many people does it take' joke.
  9. You can install any python app with pip3, setuptools and python3 Not so much I wrote out this long explination including the errors and how I fixed it, but then I accidentally hit back on my mouse and lost it all. I am not going to do it over. It will eventually install. There are several pre-reqs that are difficult to fill. bpytop - depends on psutil - requires python3, setuptools, pip, *wheel (pip install wheel) psutil requires libffi (nerd pack) the remainder are devpack. also requires gcc and gccplus. Then you get an annoying and un
  10. I want to point out again, that it seems like the edits to /etc/hosts and /etc/exports and also some changes I had to make to Routes and ifconfig are NOT persistent. So these are bodges at best. Rebooting is a pain. Maybe someone can help me make things persistent.
  11. Ok! I found my problem. I tried lots of things, so I am not sure what worked. I switched from SAMBA to NFS. Following this link someone linked: https://graspingtech.com/mount-nfs-share-windows-10/ Though the bigger issues were this: The exports are NOT //SERVER/share_name (though confusingly this did work sometimes...) Instead they are //SERVER/mnt/user/share_name ! This may be a difference in SAMBA vs. NFS. And it also differs for all my other experience sharing things across the network. Admittedly, this is mostly SAMBA related. I wonder
  12. Thanks, I did figure it out. I am not sure what worked. But restarting the Client PC seemed to bag them all. FWIW there were no visible tabs open than the one. But there must have been something lingering.
  13. Actually, I have been thinking the exact same for a while. I couldn't figure out why all my drives were in "pre-fail" state or old, even brand new ones. This is a dead topic, but I am resurrecting it to suggest maybe a slight change in wording. Maybe the header could say "Metric of:" My biggest complaint of Unraid is that in the GUI the available options are often cryptic and un-intuitive. "Cache: Prefer" has a totally different behavior than expected. Shares are "Private" or "Secure" which has little to do with 'Private' and I think its more 'Secure' tha
  14. and... its down again... Also, fairly sure its an unraid problem not a Windows problem. For one, I have several linux Samba shares in my house, all work without a problem. For the second, executing `/etc/rc.d/rc.samba restart` on unraid, immedietly clears all the problems on both machines- although interrupting any transfers I have in progress. So far, I am failing to see the benefit of unraid over say, standard ubuntu linux, where at least I know the commands (wtf is rc.d?).
  15. Removing bonding seems to have solved this- for the moment at least. This is odd as someone above says dont mix from different mfg's but these were all the same mfg. All the same card. One card with 4 1gb ports and one card with 2 10gb ports. Only the 1gb ones were bonded. The error I was getting was repeatedly Nov 2 22:30:17 Unraid rpc.mountd[20170]: refused mount request from 169.254.0.1 for /rA/S (/): not exported Nov 2 22:30:17 Unraid rpc.mountd[20170]: refused mount request from 169.254.0.1 for /rA (/): not exported Nov 2 22:30:17 Unraid rpc.mountd[201