Hi !
I installed the new OMV 1.0 on my SSD, then installed the backports Kernel 3.14 and all updates.
Then i put the SSD into my server which has an Asrock Board with the Qualcomm network adapter, but it looks like the backports kernel does not include the right drivers.
Can anyone help me ?
Thank you.
Greets Karl
What is the output of: lsmod | grep alx
there is no output ...
Try: modprobe alx
the same ... maybe it helps ... i put the SSD back to my other computer at the moment to do this.
Does this have an influence ?
now i put the SSD back to the server
lsmod | grep alx
alx 36121 0
mdio 12599 1 alx
I wanted to see if it gave you an error. No output was good. Did you do the lsmod | grep alx after the modprobe command?
after putting the SSD back to the server i first tried modprobe (no output), then i tried lsmod (output see above).
Putting the SSD in my other computer gave no output with both commands.
after putting the SSD back to the server i first tried modprobe (no output)
Linux for Dummies: If something works like it is supposed to do, it does not bother you with a success message.
Greetings
David
how can i make my network card work? Before the OMV 1.0 i had ubuntu (13.10 and 14.04) on the server, worked out of the box, so i thought here it would be the same.
doesn't it work ootb, if the drivers are added?
which drivers do you mean ?
i first installed OMV (with the ISO on USB stick), then i added OMV extras and activated the backports kernel (is working), then i updated all packages and rebootet.
After this i put the SSD to my server with the atheros chip, but the network (Eth0) does not work.
Any ideas ?
Or did i make s.th. wrong ?
how do i add drivers manually?
while booting it says "cannot find device eth0"
when i put in modinfo alx it shows, that it finds the driver .... somehow strange.
Does anybody have an idea ?
When i boot the kernel 3.2 the modinfo alx does not show this infos.
If the driver loads and works, it should show an eth0 driver or possibly different letters in the output of: ifconfig -a
it shows me an "eth1"
Why did this happen?
How can i correct that ?
Just adapt the "interfaces" file ?
Just execute: omv-firstaid Don't mess with the interfaces file. It will be overwritten by OMV web interface.
Also: echo "alx" > /etc/modules
That should make the alx module load at boot since it doesn't seem to want.
nano /etc/udev/rules.d/70-persistent-net.rules
delete the line with eth1
Ctrl+O to save
Ctrl+X to exit
reboot
i tried to fix it with the interfaces file ... just changed to eth1 (i read your post too late) ... and now it works.
I think i can correct that later.
omv-firstaid will fix the udev file Solo refers too and rewrite the interfaces file.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
