Strangely, I had a similar problem early this week when diagnosing a problem between a FreeBSD installation and a USB / NIC (Realtek 2832 based chipset), I resolved the problem by replacing the USB device with a RAlink 2800 based USB / NIC (I would have used a PCI based wireless NIC but the computer did not have any free PCI slots).
I would suggest that if forced to use any type of USB device, confirm that the operating system supports it before trying to install said device (I have also had previous problems with installing certain USB / DAB / DVB devices on a Debian based installation).
Which NethServer release?
The drivers (kmod-ax88179_178a) are in elrepo but the ones for CentOS 7 complain about the kernel version.
You can report the problem to elrepo bug tracker to see if they can fix it.
Neither a linux expert, but if you need assistance or want me to report it on your behalf Iām open to that.
thank you for all your advices. So what I did:
Created new interface - bridged, because couldnāt change green to red. It was saying, cannot remove (or change, not sure) the red interface.
Iāve installed all updates + some packages like DHCP and DNS, basic firewall. Unfortunately now in Software centre it is not showing any package and says I should clear YUM cache because the install /update may have failed due to metadata caching issues. Clicked the button, couple times, but not working, it is still there.
As well, I went through all the links you provided and came to the conclusion, there are only 2 options (correct me if I am wrong):
download the drivers from elrepo - but in case these are not correct it might not work (I have System versionNethServer release 6.8 (Final), Kernel release2.6.32-642.4.2.el6.x86_64)
If I get it right, it might even happen, that sometimes in the future I upgrade NS, but the drivers wonāt be updated and then I am without network.
buy USB NIC that has support directly by CentOS/Redhat - any advices which it might be?
Donāt get me wrong, but I just donāt want to spend 300ā¬ for another miniPC having 2 internal NICs just for āhome useā. Therefore I would need to make this work somehow, or stay with Zentyal (donāt really like this option).
Thank you one more time for all your help and quick responses.
Unfortunately all that I read regard to USB to LAN adapter drivers for CentOS is related to the Kernel versions, and must be compiled from sources.
I didnāt found, on a quick search on Google, an USB to LAN adapter to work on CentOS 6 or 7. That didnāt mean that arenāt.
Curiously, there are a lot of USB to Wireless adapters that works.
As @Stefano_Zamboni said, if you compiled the drivers for the current kernel version, in case of an upgrade, couldnāt work anymore.
Finally, IMO, the best/only solution is to change the hardware.
To resume the available options to have it running:
New USB to LAN adapter supported by the kernel: usually you need to identify the chipset used by the device and find out if itās supported by the kernel.
Easier with popular chipsets (realtek, ralinkā¦), but the device manufacturer may not provide that info and you have to find it out by others means, as @GG_jr did (looking at the drivers page).
Install 3rd-party pre-compiled drivers (kernel module) for your device: luckily theyāre available at ELRepo and the ones for Centos 6 can be installed without complain (I tested them on the same kernel you have and with the previous one). ELRepo compiles them in a way to make them work, in most cases, even after kernel updates (but exceptions may arise).
Manually compile the drivers: more difficult than the other methods. Problems on kernel updates. Needs compiling tools not always desirable to have on an Enterprise distribution.
Install a main-line kernel: that is a kernel with more recent features (more supported devices). ELRepo has a repository for that. More experienced members will be able to give the pros and cons. I think your device is supported (at least) from kernel >=3.18.
great, thank you for the recap. I was googling around a bit and Iāve found this one, seems it has RTL8153 chip.
I tried to check on the Red Hat Customer Portal, but I havenāt found it there.
Would anyone be able to tell me if NS would work with that chip please?
But this one and the AX88179 you own are included on CentOS 7 (sorry, Iāve mistakenly tried the ELRepo driver without knowing the device was natively supported).
In the 2nd point of the previous message I forgot to say that IF the drivers stop working after a kernel update, I still believe the computer can be booted from the previous kernel, giving some time to look for a fix.
Sorry, I am a bit confused now ā¦ so if I get it right ā¦ I have NS 6.8 that runs on CentOS 6. That means these drivers are not included, I suppose.
Therefore should I install them from ELRepo? (if yes, how please?)
Or should I install CentOS7 and on that one install NS 6.8? (no idea how to do that and what to choose in the CentOS installation)
Or should I install the NS 7 alpha2? Is it running on CentOS 7? I suppose this is not a final version, so would I be able to run this (Linux noob) or does that require any special tweaking, tuning, ā¦?
IMO, it doesnāt matter how to install NS, or which version of NS (CentOS) do you intend to use.
The only problem are the drivers.
If you donāt have the proper drivers, you cannot use the USB to LAN adapter.
The best approach is to use a combination of hardware that match the OS base platform (in this case CentOS 6.xx for NS 6.xx, or CentOS 7.xx for NS 7.xx).
Itās a little bit more complicated than for Windows OS, because not all the hardware producers, or the chipset producers, build drivers also for Linux.
EDIT:
Also, the producers of the Linux distros have different approach regarding the proper environment where will be used their distro
Please review what @Stefano_Zamboni said in his posts.
Hi Gabriel,
OK, got it. So in that case would it be better to install the NS7 alpha2 version that (seems) includes the drivers?Can I use that as a stable version (so basically rely that it will work properly without issues)?
NS Alpha 2 is āveryā outdated. Cannot be used anymore.
The latest version is NS Beta 2 which is based on the same version of CentOS.
Iām not sure about the Kernel version.
If the drivers of your USB to LAN Adapter was available on Alpha 2 version, Iām pretty sure that are available also in the Beta 2 version.
I donāt know if the drivers are related to the Kernel version.
The NS Beta 2 version is the closest version to the final version.
You can try to install NS Beta 2 and see what is happened.
so I tried the Beta 2 version, but seems I am not able to boot it directly from DVD. So I decided to try to download the drivers from elrepo.
I logged in as root (directly in the device where the NS is installed, not via SSH) and wrote:
sudo rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
and it says:
curl: (6) Couldnāt resolve host 'www.elrepo.orgā
error: import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org: import read failed (2)
hmm ā¦ I tried to ping with www only, then with http as well as https and it says
ping: unknown host www.elrepo.org
when pinging first time, it says I have new mail in /var/spool/mail/root
btw. issue with the NS7 beta 2 was, that after downloading from SourceForge, I burned it to DVD and it is not recognised as booting CD/DVD. It is always asking to insert a bootable media.
It is not issue of the DVD drive, because when I try the same with NS 6.8 it works from the first restart.
I just begin the installation of the NS Beta 2 on a dedicated server from DVD-ISO (burned with Nero 10 Essentials, burning speed: safe mode, āQuick copy ā¦ā not checked), without issues.
Marcās reply solved the issue finally ā¦ Iāve installed the driver from Elrepo and ā¦ miracle ā¦ the adapter appeared and works. THANK YOU!
I have one more issue, not related to this at all, but I hope can āhi-jackā this thread for question ā¦ I have an external usb disk where I have data (hope they are still there). If I try to mount it to a folder it says mount: wrong fs type, bad option, bad superblock on /dev/sdb1, ā¦
doing e2fsck it says superblock cannot be read or does not describe a valid ā¦
so I did e2fsck -b 32768 and still the same error.
I am already desperate ā¦ I really would like to save the data (or at least as big part as possible) on that drive, however I have no idea what should I do.