Jump to content
XPEnology Community

Drivers requests for DSM 5.2


Recommended Posts

is the fix for the scsi/hba near?

 

Not my priority for now. We must investigate further to find out why DSM do not detect drives attached to scsi/sas controller at boot and prevent us to install DSM on them

 

Please help. in 4.3 don't work my lan card TP-LINK TG-3269, 4.2 yes. Y?

I need driver for wifi TP-LINK TL-WDN4800.

 

For your network card based on a realtek chip, I modified the embedded r8169 driver (remove r8168 support from it to prevent conflict with the included r8168) : http://xpenology.trantor.be/beta/r8169.ko

Copy it to modules folder, insmod it, and type : ifconfig ethX up (where X is the network card number, ie ; eth0, eth1 ...)

 

I run XPEnology in a KVM virtual machine managed through virt-manager, but I noticed that some things are not working.

 

I will add more drivers for KVM / virtio / virtualization support

 

Sorry...

Link to comment
Share on other sites

Today I test XPEnology on an "old" DELL Optiplex 745 which have the press stop button warning issue (solved by k3dt with new synobios.ko).

On this computer I put my fuck*ng DLINK DGE-528T which is not working on my test computer (ASUS P5KPL-AM SE, IRQ issues :mad: ).

 

insmod my brand new r8169.ko module (link fews post above) and voila :smile:

No conflict between r8168 and r8169.

 

All network cards based on realtek chip which are not working with the r8168 driver will work with this one.

This will of course be included in v1.1.

Link to comment
Share on other sites

Cadre,

 

Can you share steps on how you got pata_legacy working on your intel ss4200. I've got one running with DSM 4.2 on USB but if I could do it on PATA interface that would be stop me from pressing reset button for every reboot.

 

The steps are exactly the same, except instead of the USB drive for the synoboot image, I'm using an 8gb DOM in the PATA port, along with a minimum of two sata disks of course.

 

My primary workstation is windows, so using an older computer I simply connected the IDE DOM to a controller and wrote the synoboot image with http://m0n0.ch/wall/downloads/physdiskwrite-0.5.2-PhysGUI-bundle.zip. And most importantly use Trantor's latest version of http://xpenology.trantor.be/beta/synoboot-3810-pre-v1.1_v2.7z that includes the pata_legacy module in the boot image.

 

Write the image to the DOM, remove and place in the Intel ss4200, make sure the PATA hard drive is the first boot device in the bios (which should be default with this system anyway) and power it on, and you should be golden; many thanks to Trantor.

Link to comment
Share on other sites

Thank you

 

Do you have any instruction how to add the r8169.ko to the modules directory.

 

I am not god in linux.

 

My DSM installed on PC (with USB loader)

 

I manage to copy the file to the usb stick (using the DSM gui), then went to the console and tried to copy from /volumeUSB2/usbshare/ to /lib/modules/, but got permission denied error.

 

Update:

managed to copy the .ko file to modules directory (using winscp). whats next?

 

Update 2:

OK, got it, install it and its working

 

-Roei

Link to comment
Share on other sites

Thank you

 

Do you have any instruction how to add the r8169.ko to the modules directory.

 

I am not god in linux.

 

My DSM installed on PC (with USB loader)

 

I manage to copy the file to the usb stick (using the DSM gui), then went to the console and tried to copy from /volumeUSB2/usbshare/ to /lib/modules/, but got permission denied error.

 

Update:

managed to copy the .ko file to modules directory (using winscp). whats next?

 

Update 2:

OK, got it, install it and its working

 

-Roei

 

Perfect :grin:

Thank you for the feedback

Link to comment
Share on other sites

With the sas/SCSI issue.

 

Does xpenology put its OS partition on every drive? Or only the 1st few?

 

Eg if I have the following

 

4 sata drives

15 sas drives

 

If I 1st install and set it up say with just the 4 sata....

Then attach the external 15 sas drives later.

 

Config like

 

4 sata one volume

15 sas 2nd volume

 

Will it be fine over reboots?.... Or will it still complain ?

 

Thanks

 

.

Link to comment
Share on other sites

With the sas/SCSI issue.

 

Does xpenology put its OS partition on every drive? Or only the 1st few?

 

Eg if I have the following

 

4 sata drives

15 sas drives

 

If I 1st install and set it up say with just the 4 sata....

Then attach the external 15 sas drives later.

 

Config like

 

4 sata one volume

15 sas 2nd volume

 

Will it be fine over reboots?.... Or will it still complain ?

 

Thanks

 

.

 

Yes, it installs system partition on every drive, so yes it will complain after reboot :smile:

Link to comment
Share on other sites

Hello !

Thanks for your work !

I'd need driver for Highpoint Oocket 2720GSL sata controler (not the RAID one)

The chip is a Marvell 88SE9480

Drivers source code can be found hear : http://www.highpoint-tech.com/BIOS_Driv ... source.tgz

 

I Have a package with an impressive list of drivers for Red Hat, Gentoo, SUSE but don't know what to do with (seems to be used with distib's installer...)

 

Is it possible to have more informations on what is needed to do it by myself ?

I saw the modules for e1000 is loaded but don't find it in lib/module , just need to know how to build my module with the source code I have (does it need the associate kernel source 3.2.30 ? ...)

Is it possible to built it on the syno or on a separate machine ?

 

Thank you !

 

Edit :

I managed to compile the driver,but some warnings appeared

 

root@debian:/home/temp/driver_hpt/partial# make
make ARCH=x86_64 CC=cc LD=ld CROSS_COMPILE= V= -C /lib/modules/3.2.0-4-amd64/build SUBDIRS=`pwd` modules
make[1]: entrant dans le répertoire « /usr/src/linux-headers-3.2.0-4-amd64 »
make -C /usr/src/linux-headers-3.2.0-4-amd64 \
   KBUILD_SRC=/usr/src/linux-headers-3.2.0-4-common \
   KBUILD_EXTMOD="/home/temp/driver_hpt/partial" -f /usr/src/linux-headers-3.2.0-4-common/Makefile \
   modules
 CC [M]  /home/temp/driver_hpt/partial/linux_main.o
/home/temp/driver_hpt/partial/linux_main.c: In function ‘scsi_cmd_to_req_conv’:
/home/temp/driver_hpt/partial/linux_main.c:909:24: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
/home/temp/driver_hpt/partial/linux_main.c: In function ‘mv_scsi_slave_alloc’:
/home/temp/driver_hpt/partial/linux_main.c:1573:19: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
/home/temp/driver_hpt/partial/linux_main.c: At top level:
/home/temp/driver_hpt/partial/linux_main.c:1805:2: warning: initialization from incompatible pointer type [enabled by default]
/home/temp/driver_hpt/partial/linux_main.c:1805:2: warning: (near initialization for ‘mv_driver_template.change_queue_depth’) [enabled by default]
 CC [M]  /home/temp/driver_hpt/partial/hba_exp.o
 CC [M]  /home/temp/driver_hpt/partial/hba_mod.o
 CC [M]  /home/temp/driver_hpt/partial/hba_timer.o
 CC [M]  /home/temp/driver_hpt/partial/mv_os.o
 CC [M]  /home/temp/driver_hpt/partial/linux_iface.o
 LD [M]  /home/temp/driver_hpt/partial/mv94xx.o
 Building modules, stage 2.
 MODPOST 1 modules
WARNING: could not find /home/temp/driver_hpt/partial/lib/.libmv_nonraid_64.obj.cmd for /home/temp/driver_hpt/partial/lib/libmv_nonraid_64.obj
 CC      /home/temp/driver_hpt/partial/mv94xx.mod.o
 LD [M]  /home/temp/driver_hpt/partial/mv94xx.ko
make[1]: quittant le répertoire « /usr/src/linux-headers-3.2.0-4-amd64 »
root@debian:/home/temp/driver_hpt/partial#

I modified source code to meet kernel 3.2 : replace

#   include 

with

#   include 

in mv_os.h

And replace all DMA_64BIT_MASK macro with DMA_BIT_MASK(64) and DMA_32BIT_MASK macro with DMA_BIT_MASK(32) in linux_main.c

 

Will there any trouble with this ?

I successfully get a mv94xx.ko module.

Link to comment
Share on other sites

This is an updated synoobot file which include several updates/fixes.

 

Link : http://xpenology.trantor.be/beta/

 

Known issues:

- You can't install DSM on a drive connected to a SCSI/SAS controller (configuration lost on reboot)

- Volume containing drives attached to SCSI/SAS controller is "broken" on each reboot, you must click repair.

 

Changelog:

v3 (21/12/2013)

- Add more drivers for KVM / virtio / virtualization support
- Add patched r8169 driver (realtek chips which are not working with the r8168 driver will work with this one)
- Add latest version of sk98lin driver (Marvell Yukon / SysKonnect SK-98xx/SK-95xx support)
- Update Broadcom bnx2 driver to latest version


v2 (05/12/2013)

- AX88179 Gigabit Ethernet USB 3.0
- Latest driver version for RocketRAID 3xxx/4xxx Controller
- Latest (aacraid) driver version for Adaptec
- Support XFS filesystem (no idea if DSM will automount this)


v1

- Update synobios.ko (by k3dt ; fix "buzzer stop button pressed" warning)


SCSI
----

Highpoint Rocketraid 2720SGL
LSI mpt2sas v17
Adaptec aacraid
Intel C600 Series Chipset SAS


NETWORK
-------

3Com 3c590/3c900, 3cr990
Alteon AceNIC/3Com 3C985/NetGear GA620
QLogic QLA3XXX
SiS 900/7016 SiS190/SiS191


USB
---

USB to serial / Prolific 2303 driver


PATA
----

ATI PATA (PATA_ATIIXP)
AMD/NVidia PATA (PATA_AMD)
CMD64x PATA (PATA_CMD64X)
JMicron PATA (PATA_JMICRON)
Marvell PATA (PATA_MARVELL)
Promise PATA 2027x (PATA_PDC2027X)
Intel SCH PATA (PATA_SCH)
CMD / Silicon Image 680 PATA (PATA_SIL680)
SiS PATA (PATA_SIS)
VIA PATA (PATA_VIA)
Winbond SL82C105 PATA (PATA_WINBOND)
Legacy PATA support (PATA_LEGACY)

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...