Err0r

Members
  • Content count

    23
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Err0r

  • Rank
    Junior Member
  1. Your Welcome! Now to find out how to add drivers to the kernel configuration etc..
  2. I give up! Will buy another controller! Thanks for your time!
  3. Im at work now so i cant check it.. This output is just when i ssh in to my xpenology box.. im root: root@DiskStation:~# lspci 0000:00:00.0 Class 0600: Device 8086:0c00 (rev 06) 0000:00:01.0 Class 0604: Device 8086:0c01 (rev 06) 0000:00:02.0 Class 0300: Device 8086:0412 (rev 06) 0000:00:03.0 Class 0403: Device 8086:0c0c (rev 06) 0000:00:14.0 Class 0c03: Device 8086:8cb1 0000:00:16.0 Class 0780: Device 8086:8cba 0000:00:19.0 Class 0200: Device 8086:15a1 0000:00:1a.0 Class 0c03: Device 8086:8cad 0000:00:1b.0 Class 0403: Device 8086:8ca0 0000:00:1c.0 Class 0604: Device 8086:8c90 (rev d0) 0000:00:1c.3 Class 0604: Device 8086:244e (rev d0) 0000:00:1c.4 Class 0604: Device 8086:8c98 (rev d0) 0000:00:1d.0 Class 0c03: Device 8086:8ca6 0000:00:1f.0 Class 0601: Device 8086:8cc6 0000:00:1f.2 Class 0106: Device 8086:8c82 0000:00:1f.3 Class 0c05: Device 8086:8ca2 0000:03:00.0 Class 0604: Device 1b21:1080 (rev 04) 0000:05:00.0 Class 0200: Device 8086:10b9 (rev 06) 0001:07:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:09:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:0a:00.0 Class 0000: Device 1b4b:9235 (rev ff) When i start chroot i get this output: root@DiskStation:/# lspci pcilib: Cannot open /proc/bus/pci 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller 00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V 00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0) 00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d0) 00:1c.4 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 5 (rev d0) 00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family H97 Controller 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] 00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller 03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 04) 05:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06) here is my dmesg: https://justpaste.it/17bn4
  4. @bmwfreak8 Its not gonna work, the hp machines are just crap!! Just buy a hd bay 2.5 inch and test it out.. No need for extra power chord and its about 8 bucks. Put it an old harddisk and boot from it. When it doesn't work just return the bay.
  5. so, i made a mistake! the achi.ko is working fine! But the controller is still not detected
  6. DSM 6.1 on Nutanix Community Edition (KVM)

    yes, you need an scsi controller or it wont work!
  7. most of the intel/realtek cards are working out of the box
  8. Hi, Thanks to Aigor and IG-88 i managed to compile drivers in Bash for windows. I used snippets from both users to make this tutorial! Thanks for that! Follow the tutor here: http://xpenology.club/compile-drivers-x ... d-in-bash/
  9. No sickbeard on dsm 6.0

    EDIT: Sorry, i misread you.. anyways, why would u want an old package? Sickrage is developed actively! and much much better! no need, i got sickrage (much better then sickbeard) running on dsm 6. Add custom sickbeard and paste the git url.. https://github.com/SickRage/SickRage.git I had to edit the start stop script to run as root: edit this file: /var/packages/sickbeard-custom/scripts/start-stop-status and replace the user with root USER="root"
  10. Im sorry, i made a typo.. its ASUS U3S6 Its this controller: https://www.everythingusb.com/asus-u3s6 ... 18307.html On my box i type lspci and i see this output.. 0001:07:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:09:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:0a:00.0 Class 0000: Device 1b4b:9235 (rev ff) Looking for the id on this site: https://pci-ids.ucw.cz/read/PC/1b4b/9235 and that gave me the chipset.. Im not sure if its got a SE9235 or a SE9123. Im on DSM 6.1-15047 This is my hardware: root@DiskStation:/# lspci pcilib: Cannot open /proc/bus/pci/0000:0a/00.0 lspci: Unable to read the standard configuration space header of device 0000:0a:00.0 pcilib: Cannot open /proc/bus/pci/0000:09/00.0 lspci: Unable to read the standard configuration space header of device 0000:09:00.0 pcilib: Cannot open /proc/bus/pci/0000:08/00.0 lspci: Unable to read the standard configuration space header of device 0000:08:00.0 pcilib: Cannot open /proc/bus/pci/0000:07/00.0 lspci: Unable to read the standard configuration space header of device 0000:07:00.0 Above output it prolly the controller 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller 00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V 00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0) 00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d0) 00:1c.4 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 5 (rev d0) 00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family H97 Controller 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] 00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller 03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 04) 05:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
  11. So, i followed your tutorials and i got compiling working.. (giving me shit about usb drivers, so i disabled them.) But i have a couple of qstions.. Where can i enable U36S drivers? lspci gives me https://pci-ids.ucw.cz/read/PC/1b4b/9235 I believe its a Marvel 88SE9123 controller and google told me it's already in the achi.ko but whenever i compile that and replace the lmza.extra i cant find my box on the network. When i insmod that ko file its giving me shit about symbols.. do you guys have any idea how to solve this?
  12. There is no vid/pid for hard drives. vid/pid are only identification numbers for USB devices. That's not true.. The USB bay has an controller and that controller got a pid and vid. @ bmwfreak8 Not in your computer but use a HD bay 2.5 inch and put in some old laptop disk.. like this one: http://www.ebay.com/itm/12-5mm-IDE-2-5- ... 0506103629 btw, do not buy a usb 3.0 bay but a 2.0
  13. Maybe you can buy a 2.5 inch HD bay and put a old drive in it.. Then burn the img to the drive.. do not forget the pid/vid
  14. I now used an old 512 MB stick. Same problem. Booting 5.2 is okay with this. So I think the grub is the problem. Question again: can i start the new loader with syslinux instead of grub somehow? mm can you make an iso http://xpenology.club/convert-img-to-iso-on-windows/ from the image file and then use rufus to create a usb stick? In rufus, checkbox the bootable option and then choose the iso you converted.. No idea if this works but its worth a try!
  15. re-image your stick again: write the syno image on the usb for a second time