[Drivers requests for DSM 5.2]

I'm also interested in knowing how I can patch XPEnoboot with a new driver. I know my way around building stuff on Linux but I need the source and at least some brief description of how to build the image.

 

See description of my problem: viewtopic.php?f=2&t=5790

[Fails to boot XPEnoboot 5.1-5022.3 on Shuttle XS35 v2]

Okay, I'm slowly becoming more convinced that it indeed is the ethernet adapter that is the problem as I am able to make it run on two other computers here at home.

 

So, the question remains, how can I create a custom image including my driver?

[Fails to boot XPEnoboot 5.1-5022.3 on Shuttle XS35 v2]

I should maybe add that the final thing that happens is that I get a Login prompt. If I knew the login name and password I would be able to troubleshoot this much more efficiently. What are they?

[Fails to boot XPEnoboot 5.1-5022.3 on Shuttle XS35 v2]

When trying to boot XPEnoboot 5.1-5022.3 on my Shuttle xs35 v2, I get various errors. I have downloaded the img file from the dropbox link. See below for details.

 

I suspect that the reason is that the network adapter is not supported. I have two questions:

 

1. Is this correct, or is there a different cause?

2. Is there anything I can do about it? I know my way around configuring Linux and build stuff so I might be able to contribute. The system runs Linux perfectly well so drivers should not be a problem. Is there a repository / build instructions somewhere?

 

Thanks!

 

System

 

Model: Shuttle xs35 v2

Processor: Intel Dual Core Atom processor D525 (Codename: Pineview-D)

Chipset: Intel® NM10 Express Chipset

 

Summary of errors in startup log

 

The output ends with

 

Excution Error

 

Before that, I see the following strange things (in reverse order):

 

Problem with SSDPD

Running /usr/syno/etc/rc.d/J03ssdps.sh...
/usr/syno/sbin/minissdpd
Usage: /usr/syno/sbin/minissdpd [-d] [-6] [-s socket] -[p pidfile] -i  [-i ] ...

is either an IPv4 address such as 192.168.1.42, or an
interface name such as eth0.

By default, socket will be open as /var/run/minissdpd.sock
and pid written to file /var/run/minissdpd.pid
start SSDPD failed.

 

AWK problem

/etc.defaults/rc.volume: line 250: awk: not found

 

ADT problem

:: Loading module adt7475                                                   [  OK  ]
Can not detect ADT device, Retry: 1...
:: Unloading module adt7475                                                 [  OK  ]
:: Unloading module i2c-i801                                                [  OK  ]
:: Loading module i2c-i801                                                  [  OK  ]
:: Loading module adt7475                                                   [  OK  ]

 

swap / disk problem

:: Checking new disks ...
No new disk. Do nothing.
mdadm: stopped /dev/md1
rc: Use all internal disk as swap.
/etc/rc: line 178: sed: not found
rc: No assigned swap disk (sda2) can be assembled, use all instead.
rc: Use all internal disk as swap.
/etc/rc: line 178: sed: not found
rc: No disk (sda2) can be assembled.
swapon: /dev/md1: Invalid argument

 

mount problems

:: Starting /usr/syno/bin/synocfgen...                      [  OK  ]
/usr/synobin/synocfgen returns 0
Partition Version=0
Partitoin layout is not DiskStation style.
NOT EXECUTE /sbin/e2fsck.
mounting /dev/md0 /tmpRoot
mount: lseek failed, msg:Invalid argument
mount: mounting /dev/md0 on /mptRoot failed: No such device
:: mount /dev/md0 fail, returns                                 [FAILED]

 

copy problems

:: Copy default /etc                                 [  OK  ]
cp: can't stat '/tmpRoot/etc.defaults': No such file or directory
:: Copy default /usr/syno/etc                                 [  OK  ]
cp: can't stat '/tmpRoot/usr/syno/etc.defaults': No such file or directory
:: Copy default /var                                 [  OK  ]
cp: can't stat '/tmpRoot/var.defaults': No such file or directory
Exit on error [3] no init exists...
Thr Apr 30 -8:49:33 UTC 2015
linuxrc.syno failed on 3