Jump to content

johnodon

Community Developer
  • Posts

    1,879
  • Joined

  • Last visited

Everything posted by johnodon

  1. Do you mean an external USB hub plugged into a USB port? My understanding was that if you passthrough a USB hub you will not be able to see the devices attached to it to pass those through. Anyway, wouldn't I be in the same situation with the hub being assigned a different device ID at random? I haven't tried...just what I read. Or are you talking about an internal USB controller? John
  2. So, this whole issue with randomly changing USB device IDs...is this a Linux issue? A KVM issue? Just wondering why I never saw this problem in ESXi? Does ESXi do some of it's own funky remapping to keep consistent IDs? John
  3. Sigh...now KVM is taking it upon itself to inject the USB device address into my XML. I went back to using vendor and product IDs: <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x20a0'/> <product id='0x0001'/> </source> </hostdev> I then started the VM and noticed this when I viewed the XML...
  4. Well, it was too good to be true. While the above works, USB ports have a nasty habit of changing their device IDs on the fly (or whenever a VM is stopped, started, restart). So, still investigating. John
  5. For anyone who cares, here is my final working XML for XBMCBuntu Gotham with GPU and USB passthrough (by bus/device IDs...not vendor/product IDs):
  6. W00t! USB Passthrough using bus/device IDs: <hostdev mode='subsystem' type='usb' managed='no'> <source> <address bus='6' device='3'/> </source> </hostdev> Works like a friggin champ!
  7. I think this may have worked (or at least it didn't yell at me). I won't know until I get the OS installed. <hostdev mode='subsystem' type='usb' managed='no'> <source> <address bus='8' device='2'/> </source> root@unRAID:~# lsusb Bus 002 Device 003: ID 0951:1625 Kingston Technology DataTraveler 101 II Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 002: ID 20a0:0001 Clay Logic Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 002: ID 20a0:0001 Clay Logic Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  8. This is possible, but we have to pass additional attributes to indicate the specific flirc by device id. I'll test this out today and see if I can get you some XML to try out. Thanks Jon. Found some info here: https://bbs.archlinux.org/viewtopic.php?id=167074 According to the above, should I change the USB passthrough section to look like this: <hostdev mode='subsystem' type='usb' managed='no'> <source> <host:001.002/> </source> </hostdev> I'm guessing it isn't this simple. John
  9. From what I have read, the code to passthrough a USB device (flirc in my case) is as follows: <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x20a0'/> <product id='0x0001'/> </source> </hostdev> My question is what if you have multiple "like" USB devices to passthrough to multiple VMs. For example, I have 2 flircs and each is passed through to separate WIN8 VMs. The code above is not USB port specific (only vendor/product) so how can this be accomplished? John
  10. Hi Tom, should you add code to block access to IE7 and below? for example a windows that says IE8.0 or greater etc... -- Sideband Samurai IE users can just use chrome frame, you dont even need admin rights. Sadly though its being retired on Jan 2014. Anyways, rather than forcing that as short term solution we might just be better off doing something like showing a message to IE7 and older peeps: <!--[if lt IE 7]> <p class="browsehappy">You are using an <strong>outdated</strong> browser. Please <a href="http://browsehappy.com/">upgrade your browser</a> to improve your experience.</p> <![endif]--> +1 Great Idea! Can't this enhancement be suggested on github directly and Tom can choose to incorporate? John
  11. As stated before... unRAID™ webGui © Lime Technology | page author: limetech | page version: r3
  12. Any concerns with these messages: Aug 21 13:03:15 unRAID emhttp: returnFile: sendfile /usr/local/emhttp/plugins/webGui/js/jquery.jgrowl.js: Broken pipe Aug 21 13:03:15 unRAID emhttp: returnFile: sendfile /usr/local/emhttp/plugins/webGui/js/jquery.js: Broken pipe
  13. There is an updated VMWare Tools plugin for the new WebGUI. Yep...that's the one I am using.
  14. I am going to remove the new webgui and go back to stock to see if the issue persists. EDIT: Before I remove the new webgui, I am going to try and remove the VMWare Tools plugin. I went back to using that around the same time so there is a chance that may be the culprit. Other than that, the only other things I am doing that are "non-standard" are: 1. running unRAID in a VM and 2. PXE booting unRAID. Does anyone see any issue with either (especially #2)? John
  15. Well, I resorted to hardbooting my unraid VM and less than 12 hours later the webgui has gone unrespoinsive again. John
  16. 4 days after upgrading the webgui (R3) has gone unresponsive on me. I have tried to connect from 3 different machines (all IE). Anyone else having this issue? I tried the following and it produced a segfault... John
  17. Would this thread be the proper place for feature requests/suggestions specific to the webgui? John
  18. I'll take this into a different thread to avoid highlacking. Stay tuned... John Can't wait to see your write up! http://lime-technology.com/forum/index.php?topic=27768.0 Again, not a true technical write-up on how to setup a PXE server but it should explain most of the required pieces. John
  19. I'll take this into a different thread to avoid highlacking. Stay tuned... John
  20. As much as I liked using a VMDK to boot unRAID, you guys should look into PXE booting. I am LOVING IT!!! Whenever an new version is released, all I have to do is replace the bzroot and bzimage files in my unraid TFTP folder and restart (much like updating your flash dive). Doesn't get any easier. If something barfs...just put the old files back. Granted...it is not nearly as fast as booting from a VMDK (especially on an SSD as I was) but it is also very acceptable. John
  21. HAHA...I found the thread he referenced 2 mins after posting. Thx BQ. I'm so tempted to try but I am at work right now. If it blows up I'm screwed...although that usually does not stop me. John
  22. QQ about flashing the MB BIOS... Is it possible to do it over IPMI via Virtual Media? Been trying to find an answer and have struck out. I'm afraid that once the upgrade process starts it will kill the IPMI connection. John
  23. I was finally able to flash the Dell H310 with an IT Firmware! I basically follwed the guide here: http://forums.overclockers.com.au/showthread.php?t=1045376 But the first thing I had to do was wipe the card completely otherwise sas2flsh would not recognize it as an LSI card. So, I did: megarec -writesbr 0 sbrempty.bin megarec -cleanflash 0 and then flashed it with the firmware found here: http://www.dell.com/support/drivers/us/en/19/DriverDetails/Product/poweredge-r610?DriverId=6M53D&FileId=2731103519&DriverName=Dell%206Gbps%20SAS%20HBA%2C%20v.07.03.05.00%2C%20A08&urlProductCode=False Funny that Dell actually provides this firmware but in the same breath will tell you that the H310 cannot be flashed with an IT firmware. sas2flsh -o -f 6gbpsas.fw Then flash with the mptsas2.rom. sas2flsh -o -b mptsas2.rom Lastly, add the SAS Address back to teh card: sas2flsh -o -sasadd 500605bxxxxxxxxx That's it. I now have an H310 that I can passthrough in ESXi. John
  24. All of my attempts to flash my Dell Perc H310 with an LSI IT firmware thus far have failed...but I am not ready to give up. I was wondering if: 1. Could the people in-the-know tell me if this card is even able to be flashed with an LSI IT firmware? The spec sheet can be found here although it really doesn't offer much info other than it is an LSISAS2008 chipset. http://i.dell.com/sites/doccontent/shared-content/data-sheets/Documents/dell-perc-h310-spec-sheet.pdf 2. If the card is able to be flashed, which package (zip) should I use. I did find one thread that seems to indicate that these cards have the 9211 version of the chip: http://openindiana.org/pipermail/openindiana-discuss/2013-January/011190.html If there are any utilities that you would like me to run on the card itself, just let me know and I will do that. TIA! John
  25. This is a good idea but would nuke my suggestion above for people who are using the free version (no USB key required). they would lose their settings after every reboot. Maybe there should be two flavors...persistent and non-persistent. John
×
×
  • Create New...