andrew's picture

im currently tring to install mineos. i have managed to get a server working in the past but it was amd build and now im working with intel the network card is nc382i. i tried to find debian drivers, no luck. as of right now, the server gets to the network confi page and wont connect. i believe this to be a driver issue. i know last time a fresh install of debian worked. but it came with a bunch more stuff and configs that didnt work right. if possible i would just like to add the drivers into the current install.

also im still pretty new to linux, i dont know how to add them once i do.

i thought about adding the drivers from the debian install into mineos install, but cant find my way around.

Jeremy Davis's picture

I did a quick google and it appears that the NC382i NIC uses a Broadcom NetXtremeII chip. So my googling suggests that the "non-free" (still free as in beer, just not open source) package that you need is firmware-bnx2.

The link that I posted above is for Debian Buster - i.e. what v16.x is based on. Whilst MineOS is based on TurnKey, we don't produce it, so I'm not sure if there is a v16.x based release. So you may need to download the package for an earlier release (v15.x was based on "Stretch").

andrew's picture

so i mananged to install the stretch drivers and was able to use eth0

however eth1 just errors out still.

also was a bit weird, worked first restart, then when i restarted again, it made me set up the network again. im not sure if its booting the network driver that i installed first or if its booting the broken mineos network setup first

Jeremy Davis's picture

So it may be best for you to try manually configuring your network directly via /etc/network/interfaces?!

FWIW by default Confconsole will only configure one interface (generally eth0 by default). So unless you are happy with the default, you'll need to manually configure that anyway.

TBH, I'm totally unfamiliar with that hardware and it seems that a single chip provides 2 Ethernet ports. I've never personally used hardware like that (all the multi-NIC hardware I've used has either "just worked" or has had separate chips).

So as per above, from what I gather, both eth0 & eth1 are provided via a single chip. That would suggest to me that the driver should work for both. It would also suggest that it's the eth1 config that is the issue, rather than a driver problem. Although TBH, I'm pretty much just stabbing in the dark... If you keep in mind that under the hood, TurnKey is Debian, you may be able to find more info online about getting your hardware working?

andrew's picture

so that fixed eth0 and 1, by adding in 1 to the /etc/network/interfaces. however, everytimg the server restarts it makes me reconfigure network. its like its not saving the config to file. any ideas where that might be set up at

Jeremy Davis's picture

I just realised that I hadn't replied to this post. Sorry about that...

My suggestion would be to manually configure it how you want it via the /etc/network/interfaces file. Then be sure to remove the top line. I.e. remove the line that says "# UNCONFIGURED INTERFACES" (as per the instructions on the line below that - you can remove that line too if you want).

andrew's picture

i tried to set it to static and remove the line, it then just gets stuck in unconfigured network screen and doesnt work, then i have to add the "# UNCONFIGURED INTERFACES" back in and reboot and it at least will let me connect again

Jeremy Davis's picture

That sounds a bit strange and doesn't make sense to me... Could you please tell me which TurnKey version this is. If you're unsure, try this:


Also, it might also be worth double checking the Debian version:

lsb_release -a
andrew's picture


tho idk why it says amd64 when im on intel

Welcome to Mineos-tkldev, TurnKey GNU/Linux 14.0 / TurnKey 9.13 Stretch

is what it says when i loginto root

Jeremy Davis's picture

AMD64 (aka x86_64) is just the name for the 64bit version of the x86 CPU instruction set, regardless of CPU manufacturer. It is sometimes called "Intel 64" when specifically referring to Intel CPUs but TurnKey follows Debian's lead and uses amd64 to denote a CPU manufacturer agnostic x84 64 bit OS. It's often referred to as amd64 regardless of CPU manufacturer because the specification was originally developed by AMD and the first CPU to be released with it was by AMD.

For what it's worth, it looks like it's based on our old v14.0 release, but updated to Debian 9/Stretch (v14.x was based on Debian 8/Jessie). Our latest release is v16.x (based on Debian 10/Buster) and we did a lot of work on the components that are causing you trouble. Having said that, TBH I'm not sure if this issue that you are hitting would be any better with the newer versions.

Perhaps you might just be better off to just follow my suggestions re the interfaces file and disable the Confconsole (the bit that I'm pretty sure is complaining about unconfigured interfaces)? To disable Confconsole's auto starting at boot, try this:

update-rc.d confconsole disable
andrew's picture

when i set the file manually i was unable to connect to it, so i know the network was down. if i disable the config console i just wont be able to see it. i need to force the network to start up sooner i think.

andrew's picture

so what ever is setup to reset the network config file is persistant. but i found a work arround, i set up my ip address, with dhcp, copied that over to static, edited the interfaces file to no longer have modification permissions, it can still be executed and read, but now it cant be reset. i do get an error screen saying it cant bring up network devices, but it is bringing up my ethernet and is working with a reboot

Jeremy Davis's picture

Ok great. TBH, I'm still not sure why it's been such a pain, but it sounds like you have found a way to force it to work! So nice one! :)

Add new comment