Topic: NIC problem

[hsm]

installed 8.0 on a new shuttle xs36v: I get not network connections at all. configured as server only and given ip on lan. router does not see server, cannot ping server, cannot log in over network...
Tested the shuttle with knoppix and network works perfectly: Is it possible that sme 8.0 has problems with my particular NIC? I also tried sme 7.6 with same result...

[janet]

hsm

installed 8.0 on a new shuttle xs36v .... Is it possible that sme 8.0 has problems with my particular NIC?

Check hardware compatibility lists (HCL) for CentOS5.8 on which sme8.0 is based on.
You can also try to install CentOS 5.8 to see if that runs & detects your NIC.
If 5.8 fails, then you could also try CentOS 6.x to check if a more recent OS detects your hardware.

Before purchasing ANY hardware, you should always check compatibility with the operating system you plan to install.

[hsm]

CentOS 5.8 does not work but CentOS 6.3 does work: Now what?????

in sme startup log:

Bringing up interface eth0: awk: /NA/NA/ {print $2}
awk: ^syntax error
Device eth0 has different MAC address than expected
ignoring: [FAILED]

[janet]

hsm

So that indicates your NIC is not supported in older kernels/operating systems and therefore not likely to be detected by sme 8.0.

Usually you would disable the incompatible NIC in the BIOS, and then plug in a compatible NIC (card) into the server. I'm not sure if that server has any expansion slots for cards.
Alternatively you would have to compile and/or install suitable drivers for the onboard NIC (if available), but this is possibly something you would have to do for each kernel upgrade.
Maybe check with Intel about the NIC.

[guest22]

hsm,

next to the suggestion of Mary, please try the following on the console as root:

(assuming eth0 is your Internal NIC)

config show InternalInterface
copy the line: HWAddress=xx.xx.xx.xx.xx.xx (and save off console)

config delprop InternalInterface HWAddress
signal-event post-upgrade; signal-event reboot

this will regenerate the (correct) HWAddress (check with 'config show InternalInterface')

Can you let us know the results please?

TIA
guest

[hsm]

ok: for this I need some help, this is a little beyond my pay-grade: How do you do the configuring? I also have a friend who could help me with this: So, just stand by, this might take a while...

I know the HWAdress but how do I configure the config delprop InternalInterface HWAddress
signal-event post-upgrade; signal-event reboot?

[guest22]

Simply enter the commands on the console as root

config delprop InternalInterface HWAddress
signal-event post-upgrade; signal-event reboot

[hsm]

does not work

[janet]

hsm

Please enter this command at the root prompt and show us the output
config show InternalInterface

Does the server have a slot for an additional card ?
If so the simplest solution is to buy a compatible NIC and insert it and allow sme to detect the card, having also disabled the onboard NIC in the BIOS.
I saw the server uses an Intel Nxxx (forgot type model now) so you should contact Intel to see if they have a driver for CentOS 5.8.
Alternatively you could try logging in as admin & run Configure this server option, and then manually select a NIC driver eg e1000 re e100 (Intel) and see if that works by chance.

[hsm]

thank you for all your help: the server is a mini form-factor and has not slots: I have installed clearOS which is based on CentOS 6.x and that is up and running now...

[purvis]

http://www.shuttle.eu/support/faq/software/linux/
says

Currently, Shuttle provides Linux support for some XPCs by including Linux driver CD along with the systems. However, not all XPCs and motherboards come with a Linux driver CD. Since Linux is an “open source” operating system; most drivers are written/provided by 3rd parties. We strongly encourage our users to search the Internet or visit the chipset vendors’ web sites for any new available drivers.

As we continue our efforts to have every latest models tested for Linux compatibility; please keep in mind that not all features/functions/drivers are supported at this time. Thank you for your understanding as we continue to push for better Linux implementation and support in the future.