Jump to content

mossiemosforth

Members
 View Profile  See their activity

  • Posts

    81

  • Joined

  • Last visited

 Content Type 

Posts posted by mossiemosforth

    [unRAID 6 beta14+] Unassigned Devices [former Auto Mount USB]

    in Plugin Support

    Posted

    SNAP is incompatible with unraid V6.1 and will not work.

     

    Attached is a modified plugin I created to install the last version of unassigned devices that works for me.  Copy this file to your flash drive, then go to the Plugins->Install Plugin tab and select the 'unassigned.devices.plg' on your flash.  This will install the 2015.09.19 version and won't try to update to the later versions.

     

    I don't know what features the later versions offered.  I think gfjardim was rewriting some things and left them half done.

     

    This is the best I think we can do until gfjardim returns to update unassigned devices.  I am not interested in picking up yet another abandoned plugin, but if gfjardim does not return, I may move this version to my own github repository so users can at least have a version that works.  We'd have to see how it goes from there.

     

    you sir, are a true gent.

    That previous version has worked a treat for me.

     

    Now the hideous task of migrating my VMs and Docker to the new drive

     

    [unRAID 6 beta14+] Unassigned Devices [former Auto Mount USB]

    in Plugin Support

    Posted

    I've come looking as i am also having this very same issue.

    Installed an SSD to host my VMs and Docker, all seems to be good until i tried to mount the disk and the icon never goes green saying mounted.

    That being said it does actually mount the disk and shares it. Another weird one is for some reason the share name is in lowercase (ssd), whereas in all config files i have defined it in uppercase (SSD), anyone have any idea to fix that?

     

    Checked my logs and i also get the same php errors as you all (after reporting it is mounted correctly);

     

    Fri Jan 15 18:29:56 GMT 2016: Mounting '/dev/sdf1'

    Fri Jan 15 18:29:56 GMT 2016: Drive found with the following attributes: name='sdf1', device='/dev/sdf1', part='1', disk='/dev/sdf', label='SanDisk_SDSSDA240G_154608406660-part1', fstype='btrfs', mounted='', mountpoint='/mnt/dis$

    Fri Jan 15 18:29:56 GMT 2016: Adding disk  ...

    Fri Jan 15 18:29:56 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:29:56 GMT 2016: Mounting drive with command: mount -t btrfs -o auto,async,noatime,nodiratime '/dev/sdf1' '/mnt/disks/SSD'

    Fri Jan 15 18:29:56 GMT 2016: Successfully mounted '/dev/sdf1' on '/mnt/disks/SSD'

    Fri Jan 15 18:29:56 GMT 2016: Partition '/dev/sdf1' successfully mounted.

    Fri Jan 15 18:29:56 GMT 2016: Defining share 'SSD' on file '/SSD.conf'.

    Fri Jan 15 18:29:56 GMT 2016: Adding share 'SSD' to /boot/config/smb-extra.conf.

    Fri Jan 15 18:29:56 GMT 2016: Reloading Samba configuration.

    Fri Jan 15 18:29:56 GMT 2016: Directory '/mnt/disks/SSD' shared successfully.

    Fri Jan 15 18:29:56 GMT 2016: Command not available, skipping.

    Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:00 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:00 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:02 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:02 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:04 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:04 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:06 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:06 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:08 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:08 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:10 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:10 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

    Fri Jan 15 18:30:12 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428

     

    Would moving back to SNAP be an option do you think?

    GT610 Graphics Card Passthrough issue

    in VM Engine (KVM)

    Posted

    Thanks for the reply Jon, sounds like promising news.

     

    Sadly the VM dropped out on me while watching a TV Show last night, kind of lost my faith in it a little.

    Where can I find the logs, as to better find out what is going on with it?

     

    I've had to plug my raspberry pi back in for now, for stability, so waiting out for a new release should be too bad.

    On that note do you have a time frame for release? or an idea when Openelec v6.0.0 willl be an available template?

     

     

    GT610 Graphics Card Passthrough issue

    in VM Engine (KVM)

    Posted

    From what I have gathered in all my research so far, some GPUs just don't support this reset feature and there is no apparent way to "force" this to happen.  It's an issue with the GPU itself and not something we can solve from the unRAID side.

     

    Have you tried both SeaBIOS and OVMF for the BIOS type?  Any difference?  As far as passing a ROM file, this is documented in the wiki here:  http://lime-technology.com/wiki/index.php/UnRAID_6/VM_Management#Edit_XML_for_VM_to_supply_GPU_ROM_manually

     

    I figured that was the case, as the old AMD 3450 i had ran like a charm and was able to be reset (if it was HDMI i'd keep it)

    I have both bios types with no avail, shame as the card itself seems to perform well for a low end card.

     

    As for trying another rom, i have followed the wiki, but I have no idea what rom 'could' even work with this card. Anything in the region of this model i have tried failed miserably.

     

    Seems like buying another card is my best solution, current one that's caught my eye is a Radeon HD5450, I can currently get one for circa £20, should be good enough to run kodi and a few emulators, anyone have have one/know if they work?

    OpenELEC VM Template Support

    in VM Templates

    Posted

    scratch the above about an xbox 360 controller

    some googling on the lights found me the xboxdrv.sh driver that solves it all and the pad now works for both OE and the emulators

     

    for anyone else interested the helpful instruction i followed can be found here - http://openelec.tv/forum/128-addons/71535-guides-retroarch-friends?start=319

     

    still wouldn't mind hearing if anyone has a pulse eight adaptor working ;)

     

    I got the pulse-eight adaptor working by adding the address manually to the xml for the VM.

     

    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x2548'/>
        <product id='0x1002'/>
        <address bus='7' device='5'/>
      </source>
      <alias name='hostdev1'/>
    </hostdev>

     

    The above is the code specific to my installation but it might be of some use.

     

    Smashing Phil, thanks for the confirmation.

    Thanks for the code, did you have to manually add it? Just it seems to be the same entered when using the tick boxes on the 'edit VM' screen. Either way, useful non-the-less ;)

     

    I think i'll get one ordered once I've solved my graphics card issue.

    GT610 Graphics Card Passthrough issue

    in VM Engine (KVM)

    Posted

    Hi guys, a small issue I have and I'm after clarification/best solution.

     

    I have been running VMs for quite a while now, including a linux box with 2 passthrough NICs (firewall/DMZ into my home network) and have never had a issue. Also passed through singular USB and even one of my motherboards USB controllers to different VMs. My issue now lies with graphics pass through.

    I've achieved it before but never really had a use for it, until my wife saw me playing Super Mario and asked if it was possible on the living room TV so we can play together. I then came across the retroarch/advancedlauncher guide johnoden wrote and thought i'll give it a go.

     

    So i've ripped out the old AMD HD3450 card I had previously used (with no issue passing through) and put in a GT610 I 'borrowed' from my daughter machine as it has HDMI so I can send video and audio to the TV.

    Already a big fan of KODI and i run multiple instances around the house i figured i could use limetechs OpenELEC VM to make this all happen and replace the raspberry pi I currently use in the living room.

    I have indeed managed all the above (and may write this up at some point, UCD post maybe), including pass through of a USB keyboard and xbox360 wireless receiver, but i have an issue with the graphics card. Specifically if I reboot the OpenELEC VM I get no video once booted again. I can gain graphics again, but have to reboot the entire server to get it, which takes ages, along with this the VMs logs are full of this libusb: error [submit_bulk_transfer] submiturb failed error -1 errno=28 (i think this may be to do with the xbox receiver).

     

    From what I can gather the issue lies with the GT610 itself, it doesn't reset properly when the VM restarts, am I right?

    If so is there a way of forcing it to? I have also read about pointing VMs at a different ROM that would allow this (but that's outside my knowledge and if anyone could point me in the right direction i'd be much obliged)

     

    Failing all else I can also go out and get another card, but wanted to ask before i spend money unnecessarily. If this is my only option does anyone have a cheap recommendation (i'm in the UK and parts can be pricey).

     

    Last question (maybe have my fingers slapped for wrong forum), but any idea when limetech will release an OpenELEC v6.0.0 template. I'm a growing fan of it and theres a few addtions to v6 that i would make use of.

    OpenELEC VM Template Support

    in VM Templates

    Posted

    Can I ask how are you all controlling this VM?

     

    I have been trying to pass through a wireless xbox360 receiver but have had no joy whatsoever.

    I've only passed it through using device id (tick box on edit VM screen), obviously plugged in with the VM off.

    The controller doesn't even seem to sync with the receiver (all lights on the ring just flash).

    However same method with a wireless mini kb/touchpad combo usb dongle works fine (but the kb/touchpad is awful to use).

     

    The main reason I want to do this is I've installed RetroArch on it using johnoden's guide here - https://lime-technology.com/forum/index.php?topic=43836.0

    Currently its just plugged into my monitors 2nd input, but I plan on extending it into the living room and replace one of my pi's in there that's running openELEC.

     

    Also on that note, if I can get the controller working I'd want to look at getting a pulse eight cec adaptor in order to control it using my tv's remote. Anyone passed the usb part of that to the OE VM?

    I'd like to do this as the tv remote is what we currently use to control the pi, keeps things simple for the missus and kids (and 1 less remote on the coffee table).

     

    only other point to note is I plugged in the xbox receiver into my openelec pi and the ring doesn't flash (solid top left light) like its connected, it still doesn't control kodi though :(

     

    Any help appreciated guys ;)

    [SOLVED]Problem with mouse tracking/USB controller help

    in VM Engine (KVM)

    Posted

    so right after posting this i managed to fix it, typical isn't it. i can't take any credit, after hitting the 'post' button i noticed another thread asking about usb details in the xml, here - http://lime-technology.com/forum/index.php?topic=36424.0

     

    big thanks goes to JustinChase for giving a very simple way to fix my issue also. this was to add the require config lines but leave out the address line in the usb controller section and let the system write that part itself.

     

    so for completeness of this thread here is my working windows 10 xml, complete with passthrough of 2x pci nics and a mouse that now works accurately;

     

    <domain type='kvm' id='20' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>win10</name>
  <uuid>cc411d70-4463-4db7-bf36-d364c0cdaa9d</uuid>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>976563</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-2.1'>hvm</type>
    <boot dev='cdrom'/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough'>
  </cpu>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/disk/vertex/isos/win10.iso'/>
      <backingStore/>
      <target dev='sdc' bus='sata'/>
      <readonly/>
      <alias name='sata0-0-2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/disk/vertex/isos/virtio.iso'/>
      <backingStore/>
      <target dev='sdd' bus='sata'/>
      <readonly/>
      <alias name='sata0-0-3'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/mnt/disk/vertex/vms/win10.qcow2'/>
      <backingStore/>
      <target dev='vda' bus='virtio'/>
      <alias name='virtio-disk0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/>
    </disk>
    <controller type='sata' index='0'>
      <alias name='sata0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='dmi-to-pci-bridge'>
      <alias name='pci.1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
    </controller>
    <controller type='pci' index='2' model='pci-bridge'>
      <alias name='pci.2'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
    </controller>
    <controller type='usb' index='0'>
      <alias name='usb0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:fd:96:75'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
    </interface>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='cirrus' vram='9216' heads='1'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/>
    </memballoon>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=02:00.0,bus=pcie.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=06:00.0,bus=pcie.0'/>
  </qemu:commandline>
</domain>

     

    probably the quickest fix time in the history of kvm. more down to my inablity to find anything related to my issue before resorting to posting it in the first place. sorry about that, but hope my xml may be of use to someone else :D

    [SOLVED]Problem with mouse tracking/USB controller help

    in VM Engine (KVM)

    Posted

    Good evening guys, i've got a long way forward with kvm this weekend, however upon managing to get passthough of 2 pci nics i have managed to ruin my mouse input to the vm and am loosing my mind (and patience) with this issue.

     

    here is my current xml (mostly pulled from one of jonp's);

    <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>win10</name>
  <uuid>cc411d70-4463-4db7-bf36-d364c0cdaa9d</uuid>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>976563</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-2.1'>hvm</type>
    <boot dev='cdrom'/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough'>
  </cpu>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/disk/vertex/isos/win10.iso'/>
      <target dev='sdc' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/disk/vertex/isos/virtio.iso'/>
      <target dev='sdd' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/mnt/disk/vertex/vms/win10.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/>
    </disk>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='dmi-to-pci-bridge'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
    </controller>
    <controller type='pci' index='2' model='pci-bridge'>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
    </controller>
    <controller type='usb' index='0' model='none'/>
    <interface type='bridge'>
      <mac address='52:54:00:fd:96:75'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='cirrus' vram='9216' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/>
    </memballoon>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=02:00.0,bus=pcie.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=06:00.0,bus=pcie.0'/>
  </qemu:commandline>
</domain>

     

    i understand that my mouse problem in vnc is caused by not having a 'tablet' input type, this is corrected by the following code adding with the other input types;

     

    <input type='tablet' bus='usb'/>

     

    however for this to function the vm requires a usb controller which my current xml does not allow for. the following code is pulled from another vm that mouse tracking is not a problem on (created using vm manager);

     

    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>

     

    the above doesn't work on this vm, but i have gathered it's to do with the pci device of the host i'm referencing. i have changed the bus/slot/function numbers in differing combinations but still no joy. depending on the combination i get either of the following error messages when trying to apply the config in VM manager;

     

    Error changing domain definition: internal error: Bus 0 must be PCI for integrated PIIX3 USB or IDE controllers

     

    Error changing domain definition: XML error: PCI bus is not compatible with the device at 0000:00:01.3. Device requires a standard PCI slot, which is not provided by bus 0000:00

     

    below is an output of lspci (well from the extension page of the unraid gui);

     

    00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02)

    00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02)

    00:03.0 Communication controller: Intel Corporation 82Q35 Express MEI Controller (rev 02)

    00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02)

    00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02)

    00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02)

    00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02)

    00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)

    00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)

    00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02)

    00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 02)

    00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 02)

    00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 02)

    00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02)

    00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)

    00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)

    00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)

    00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)

    00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)

    00:1f.0 ISA bridge: Intel Corporation 82801IO (ICH9DO) LPC Interface Controller (rev 02)

    00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)

    00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)

    02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 02)

    03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6101/6102 single-port PATA133 interface (rev b2)

    06:00.0 Network controller: Atheros Communications Inc. AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn] (rev 01)

    06:03.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 70)

     

     

    if anyone can point out what i can do to rectify this small (but bloody annoying) problem i will be most grateful, i know i'm close but had to put my lighter down as theres no cigar yet.

     

    TIA guys ;)

×
×
  • Create New...