Jump to content
XPEnology Community

totalnas

Member
 View Profile  See their activity

  • Posts

    49

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by totalnas

    Drivers requests for DSM 5.2

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hi,

    Simple suggestion: Please, add all drivers related to virtualization. Several of them are included in the source of the Linux kernel. This will facilitate the deployment inside VMware, Hyper-V and Virtualbox.

    Best!

     

    Can you make a list of required options to build ? :oops:

    I read in the hyper-v that the built-in drivers are staging are very buggy...

     

    Not the full list, only a few:

     

    * For VMWARE:

    - PVSCSI: vmw_pvscsi.ko

    - VMXNET3: vmxnet3.ko

    - VMCI: vmw_vmci.ko & vmw_vsock_vmci_transport.ko

    - Ballon: vmw_balloon.ko

     

    * For Hyper-V:

    - Device Drivers --> Network device support --> "Microsoft Hyper-V Virtual Network Support"

    - Device Drivers --> Microsoft Hyper-V guest support --> "Microsoft Hyper-V utilities driver" & "Microsoft Hyper-V Ballon driver"

    - Device Drivers --> HID Support --> Special HID Drivers --> "Microsoft Hyper-V mouse driver"

     

    * For VirtualBox:

    - vboxguest.ko

    - vboxsf.ko

    - vboxvideo.ko

     

    * for KVM support:

    - CONFIG_VIRTIO_PCI=y (Virtualization -> PCI driver for virtio devices)

    - CONFIG_VIRTIO_BALLOON=y (Virtualization -> Virtio balloon driver)

    - CONFIG_VIRTIO_BLK=y (Device Drivers -> Block -> Virtio block driver)

    - CONFIG_VIRTIO_NET=y (Device Drivers -> Network device support -> Virtio network driver)

    - CONFIG_VIRTIO=y (automatically selected)

    - CONFIG_VIRTIO_RING=y (automatically selected)

     

    After a kernel with all modules enabled will be more easy to add a "tools" package for guest shutdown and other commands.

    Futhermore, the performance improvement with paravirtualization it's a must have!

     

    :grin:

    Kernel HIJACK

    in Developer Discussion Room

    Posted

    I've just found 2 images in my downloads and think I've possibly installed "DS3612xs_4.2-3211_x64_Microserver-20130612.img" instead of the 1.2 repack sitting next to it, is there anyway to check this? If it turns out I haven't installed the 1.2 version is there a way to update to this version or should I follow your instructions for OHCI support you posted towards the start of this thread?

    Hi,

     

    Change the USB pendrive for another one. Install in the new pendrive the 1.2 repack. After boot, you have the new version with OHCI support.

    Kernel HIJACK

    in Developer Discussion Room

    Posted

    I was just wondering if these modifications, specifically number 4, would work on the latest release of DSM (4.2 3211 v1.2) on a HP micro server. I'm guessing this a silly question however I wanted make sure before making any changes.

     

    Also thanks to everyone who's contributed in this thread especially totalnas, hopefully I will finally be able to get my UPS detection problem resolved.

    Hi Ollie,

     

    OHCI USB support is already included in the repack 4.2 v1.2

     

    Regards!

    DSM 4.3 Beta

    in Archives

    Posted

    Does this mean, that the source of 4.2 is available for compilation ???

    No, this means that the next version (4.3) is on road. Now at BETA stage.

     

    TN.

    Tuto pour compiler dsm 4.2

    in Archives

    Posted

    Si je ne dit pas de bétise, les modules compilés sont en version 3.2.11 au lieu de 3.2.30 ?

    Il me semble que dans les début j'ai testé, le kernel compil bien mais impossible de faire une build 4.2 complète à cause des modules incompatibles (surtout le synobios.ko qui fait tout planter). Ca s'installait bien mais reboot/shutdown au bout de quelques minutes.

    Je pense que vouz pouvez utiliser directement le fichier binaire de la version 4.2. Elle est différente de la version publique à le repositorie.

    Les toolchain sont le même, et il faut compiler avec le kernel 3.2.30.

     

    Dans la mesure ou la béta du DSM 4.3 est dispo sur le diste de syno, les sources ne vont plus tarder

    On pense la même chose! :wink:

    works xpenology with ide controller

    in Archives

    Posted

    @Trantor: have you an answere of my question ?

    -> can the xpenology shutdown completely (poweroff) via task and also going on to a specified time ? like the normaly synology?

    Hi,

     

    I feel that the answer is NO!

     

    I explain: You can schedule by software a shutdown on a specific time. You can configure your BIOS to boot at specific time. But, you need to create a software that changes your bios values to set the new boot time. This is a hard work!

     

    Workaround: Configure your XPEnology to Wake-On-Lan, and use your router (with OpenWRT or another custom distribution) to wakeup your XPEnology at specific time.

     

    TN.

    works xpenology with ide controller

    in Archives

    Posted

    Hi Trantor,

     

    I feel that you need to also enable:

     

    PATA_LEGACY

    PATA_CMD640

    PATA_VIA

    PATA_WINBOND

    PATA_SIL680

    PATA_RDC

    PATA_PDC2027X

    PATA_MARVELL

    PATA_JMICRON

    PATA_CMD64X

     

    I think that this include 99% of current systems. Or you can enable as a module all of current Linux-3.x PATA drivers.

     

    TN

    Kernel HIJACK

    in Developer Discussion Room

    Posted

    #4: OHCI support

     

    Here the solution: Add support for OHCI driver.

    You only need to modify the config file in the kernel with:

     

    CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_OHCI_HCD_SSB=y

     

    After recompiling this module the module "usbcore.ko" is different. If you try to load the "ohci-hcd.ko" in a system with the original "usbcore.ko" module already loaded you receive a kernel fault. You need to replace also the "usbcore.ko" module!!! :eek:

     

    Hi,

     

    Related to this post, when I insert a USB 3.0 host card, the system generates a kernel panic when the driver xhci is loaded. I feel that the the new "usbcore.ko" can be incompatible with the original one. To other developers: Can you try to enable the ohci driver and test USB 1.1 / 2.0 / 3.0 hardware?

     

    Thank you!

    [SOLVED] AX88179 driver for DSM 3.2 and up

    in Archives

    Posted

    i have a small issue. When entering insmod: 
    /lib/modules/usbnet.ko

    i get: 

    insmod: can't insert '/lib/modules/usbnet.ko': unknown symbol in module, or unknown parameter

    Any suggestions or sharing the right usbnet.ko for me?

    Sure, you need to update the version of the "usbcore.ko" module

    See: http://xpenology.com/forum/viewtopic.php?f=2&t=915#p4292

     

    In my system the driver is working (connected to an USB 2.0 port). You need to configure the new ethX manually.

     

    :grin:

    [SOLVED] AX88179 driver for DSM 3.2 and up

    in Archives

    Posted

    How to compile the driver for new releases:

     

    • 1) Setup the environment to compile the XPEnology kernel/modules (I don't explain this).
      2) Download the driver sources for Linux from
    http://www.asix.com.tw/download.php?sub=driverdetail&PItemID=131
    3) Go to "x86_64-linux-gnu/source/linux-3.x/drivers/net/usb/" and copy these source files from the package: "asix.h" and "ax88179a.c"
    4) Edit file "x86_64-linux-gnu/source/linux-3.x/drivers/net/usb/Makefile" and add this line "obj-$(CONFIG_USB_NET_AX88179) += ax88179_178a.o"
    5) Edit file "x86_64-linux-gnu/source/linux-3.x/drivers/net/usb/Kconfig" and add this code:
    config USB_NET_AX88179
       tristate "ASIX AX88179_178A Based USB 3.0/2.0 Gigabit Ethernet Adapters"
       depends on USB_USBNET
       select CRC32
       default y
       help
         This option adds support for ASIX AX88179_178A based USB 3.0/2.0
         10/100/1000 Ethernet adapters.

         This driver should work with at least the following devices:
           * ASIX AX88179

         This driver creates an interface named "ethX", where X depends on
         what other networking devices you have in use.


    6) As usual, configure and compile from the path "x86_64-linux-gnu/source/linux-3.x/". You found the new driver in the menuconfig, already enabled as a module.

    Best! :razz:

×
×
  • Create New...