Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Mini ITX Desktop Board D201GLY2 Network Problems

Featured Replies

I have been running 2 unraid systems for quite some time now. Thought I

would try this new mini itx board. The problem seems to be the built in nic.

It judt will not see it.

It's a SIS 900 Network adapter The board has the SiS chipset with a

Intel processor. It's a beautiful little board and I would really like to get it

running to set up some small 5 and 6 disk systems.

 

Any help would be greatly appreciated

Bill

  • Author

Well I guess thier not interested in supporting the mini itx..

Really to bad because these newer boards are really catching on.

Thanks for your input though...

Bill

Tom has not logged onto the forum since Feb 9th.  He has probably not seen your request for support for the Mini-ITX board's chipset.

 

If there is a loadable module for your LAN chipset you can put it into place on the flash drive, add a couple of lines to the "go" script to copy it into place, and then install it as a loadable module before starting "emhttp"  (since unRaid is built on Slackware, look in their LIVE release for an appropriate module)

 

Tom does not supply loadable modules for every network board chipset since there are so many and it would bloat the size of his distribution.  If it is a chipset used by one of his customers he has regularly added the kernel module to his release.

 

Hopefully Tom will log in and see this.  Perhaps a known folder on the flash drive might be created to put loadable modules and then included in the PATH searched for modules.  Or modules in that folder copied to the ram file-system when "go" is executed.  Either way would allow easier support of chipsets less frequently found on boards otherwise.

 

Joe L.

 

 

I'm sure if enough people ask it will be included.

 

The driver is already in the kernel.

 

It just needs to be compiled and put on the distribution.

 

I'm also looking at some other PCI network adapters that have an embedded switch.

This would make the unRaid server a good hub system for a small network.

 

Might be worthwhile to compile all the network drivers and just have them available as object modules for people who request them.

 

By adding an itx unRaid server with a mobile processor and the pci switch, I can eliminate an external switch and save a few watts.

 

 

 

 

 

 

 

 

 

 

If there is a loadable module for your LAN chipset you can put it into place on the flash drive, add a couple of lines to the "go" script to copy it into place, and then install it as a loadable module before starting "emhttp"  (since unRaid is built on Slackware, look in their LIVE release for an appropriate module)

 

OK, Can you provide a lil pointing here..(please)

I had downloaded Slackware 12, installed it on an internal drive, pulled out the loadable module and it would not load.

Perhaps I grabbed the wrong DVD. I did notice the kernel's were different.

 

Perhaps this can be wrapped up easily.....

 

Also, if I could get a .config file to start with,

I could update the kernel with CPUSPEED support. a larger memory footprint (I have 4GB available to me) and SMP support.

 

Anyone have a base to start with?

 

If there is a loadable module for your LAN chipset you can put it into place on the flash drive, add a couple of lines to the "go" script to copy it into place, and then install it as a loadable module before starting "emhttp"  (since unRaid is built on Slackware, look in their LIVE release for an appropriate module)

 

OK, Can you provide a lil pointing here..(please)

I had downloaded Slackware 12, installed it on an internal drive, pulled out the loadable module and it would not load.

Perhaps I grabbed the wrong DVD. I did notice the kernel's were different.

I think the kernel would need to be the same...

Perhaps this can be wrapped up easily.....

 

Also, if I could get a .config file to start with,

Tom said it would be included in the next release and its omission was an oversight.

I could update the kernel with CPUSPEED support. a larger memory footprint (I have 4GB available to me) and SMP support.

cool.

Anyone have a base to start with?

I do not... I've not set up a development environment or tried to compile the "md" module.  Others have... perhaps one of them will respond.

 

Joe L.

  • Author

I have been running 2 unraid systems for quite some time now. Thought I

would try this new mini itx board. The problem seems to be the built in nic.

It judt will not see it.

It's a SIS 900 Network adapter The board has the SiS chipset with a

Intel processor. It's a beautiful little board and I would really like to get it

running to set up some small 5 and 6 disk systems.

 

Any help would be greatly appreciated

Bill

 

 

I don't understand. I have loaded many Linux distros with the above board and without

exception they all supported the onboard SIS 900 nic. (except UnRaid)..

Don't misunderstand me, if unraid can't or won't thats ok.

But I think someone could let us know one way or the other and not leave us

hanging with no answer at all.

Bill

To keep the size of the unRaid distribution reasonable Tom has only put a subset of the network card driver modules that are available under Linux in his distribution.  For the most part, if a 1Gig card / chipset is identified where he has not yet included a driver module he will include it in a subsequent release.

 

So, if you have an SIS 900 chipset and can locate a loadable driver module for the current Slackware release you can install it on the flash drive, add a few lines to copy it into place when re-booting, and install it using modprobe before the emhttp management utility is invoked. (unRaid is built on Slackware as a base, with many things removed to make the distribution fit the smaller flash drives)

 

Joe L.

 

 

So, if you have an SIS 900 chipset and can locate a loadable driver module for the current Slackware release you can install it on the flash drive, add a few lines to copy it into place when re-booting, and install it using modprobe before the emhttp management utility is invoked.

 

I do not believe this will work.

Because the unraid kernel is customized, you cannot load an object module from another version as easy as copying it.

From what I recall, you have to compile the kernel with the options you need.

 

I think if enough people request this driver then Tom will put it in.

There are a number of these ITX boards available at Rock bottom prices.

 

If a .config file were posted, I would do the recompile myself.

 

Frankly, adding this driver is needed for these ITX machines because they have limited slots.

 

The boards WITH CPU are available pretty cheaply.

 

At the very least the driver could be compiled and just left outside the initrd Distribution for those who need it.

Then we can update our own initrd image with the "properly compiled" module.

 

 

 

 

 

 

  • Author

Hi WeeboTech,

 

I started this topic, and I thank you for your input and support.

I need all the help I can get. You are right these boards are great

and fast becoming very popular.

I'm using 2 of them with freenas and they work very well, but I am

also using unraid for my large server. I do like freenas, but I think

unraid is better. So I really want to get my little boards going

with unraid.

Bill

 

If I could get a .confg to start with I could recompile the kernel and make a new bzroot.

I just dread going through all those questions in the kernel configuration.

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.