|
evlew (OP)
|
 |
December 23, 2013, 11:57:49 PM |
|
I am trying to run a single 7950 on a 990FXA-GD80 based miner.
I can boot into SMOS linux just fine but the network is intermittent.
Running a simple ping of google.com or 8.8.8.8 shows that the network works fine for a little while and then stops working. It then resumes working and then stops working. repeatedly.
I would love any insight into what could be causing this issue. Is it likely to be a motherboard firmware issue?
|
|
|
|
|
|
|
|
|
|
|
|
The trust scores you see are subjective; they will change depending on who you have in your trust list. |
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
cp1
|
|
December 24, 2013, 12:08:50 AM |
|
What's your network configuration?
|
|
|
|
|
evlew (OP)
|
|
December 24, 2013, 12:17:58 AM |
|
DHCP on DD-WRT Netgear router.
I suppose trying static would be a place to start.
|
|
|
|
|
|
cp1
|
|
December 24, 2013, 12:30:18 AM |
|
Wireless? Are you sure it's just not a bad network card/router?
|
|
|
|
|
evlew (OP)
|
|
December 24, 2013, 04:46:37 AM |
|
No wireless. This is my home/gaming PC. So ya, everything works fine from Windows. I realized I'm getting a kernel panic. I've linked the output of the error message. I tried static IP and the problems still exists. I am going to try disabling the overclock and see if that does anything. Error details: http://pastebin.com/6rcPVkHNThanks for looking and trying to help. |
|
|
|
|
|
cp1
|
|
December 24, 2013, 05:38:28 AM |
|
Can you find linux drivers for your NIC online?
|
|
|
|
|
evlew (OP)
|
|
December 24, 2013, 05:51:30 AM |
|
sure enough. turned off the overclock "genie" setting and voila! All is working now.
Guess the overclock was unstable for linux. weird.
Thanks for your responses tho.
|
|
|
|
|
|
evlew (OP)
|
|
December 24, 2013, 06:44:32 AM |
|
scratch that. still not working. guess i jumped the gun. it seemed more stable at first, but now it seems as unstable as before. I got the kernel panic again as well. frickin annoying... I wanna mine and every other old motherboard has never given me grief, but this one.... i'm about to throw it out the window.
google didn't yield much when i searched for linux drivers for this board. maybe i'll try a new adapter or something.
|
|
|
|
|
|
cp1
|
|
December 24, 2013, 07:26:55 AM |
|
What make/model is the NIC?
|
|
|
|
|
evlew (OP)
|
|
March 07, 2014, 01:03:03 AM |
|
bump. still battling this issue with this motherboard
|
|
|
|
|
|
nybbler905
|
|
March 07, 2014, 05:03:44 AM |
|
one work around is to physically install a new nic and bios disable the built in. Take the time to check ahead of time that the card is supported. I have an old dual Coppermine motherboard ( great for USB mining, no way can it GPU mine since it's AGP ) and it's Intel Inside still does not have Linux drivers, but the old Pci card does ( thank you NetGear! ).
it's an option....
|
Always looking for donations even as low as 1uBTC
14XfpYPdtYiGoEiDcKrSzuvBM3ukhwANUh - BTC
LS7FEfu9ajp3NQcDjui9TSKscwQesj9i8k - LTC
LHe9g5ixMyfdtqAEHU5vErG1eQrDshBFRW -Luckycoin
|
|
|
|
repairguy
|
|
March 07, 2014, 07:04:01 AM |
|
I know that it isnt a solution as much as a workaround, but I use the 990fxa and mine like crazy with windows 7 and ubuntu both. Have you tried using one of those?
|
|
|
|
|
|
davecoin
|
|
March 07, 2014, 07:21:32 PM |
|
Have you tried using wicd instead of the network manager that comes on smos? That helped with my network issues. Also, here's the link to the smos nic driver page: http://www.smos-linux.org/tips/ |
|
|
|
|
|
evlew (OP)
|
|
March 07, 2014, 10:57:14 PM |
|
I tried a new NIC. The only one I could find which was PCI. It worked for a while and then seemed to cause stability issues with the motherboard. The thing is literally ancient so no surprise there. It did work well for the time though which leads me to believe that it's just a compability issue with the built in NIC. I can mine in windows 7 fine. Haven't tried other linux distros yet because I like the simplicity of smos and the historical charts it gives.
thanks for the link I haven't gone through those troubleshooting steps yet and have something to try when I get home tonight!
|
|
|
|
|
|
repairguy
|
|
March 08, 2014, 04:31:48 AM |
|
I tried a new NIC. The only one I could find which was PCI. It worked for a while and then seemed to cause stability issues with the motherboard. The thing is literally ancient so no surprise there. It did work well for the time though which leads me to believe that it's just a compability issue with the built in NIC. I can mine in windows 7 fine. Haven't tried other linux distros yet because I like the simplicity of smos and the historical charts it gives.
thanks for the link I haven't gone through those troubleshooting steps yet and have something to try when I get home tonight!
If you can mine in windows, you are correct about the compatibility. I am not really familiar with smos. That board uses a realtek 8111 nic. The driver page is http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=falseYou might try updating the linux driver. Also, Mine will kernel panic with bamt on ocassion, I just use ubuntu, and watch stats from the pool. I am sure with a little research you could install the monitor package on ubuntu. |
|
|
|
|
|
evlew (OP)
|
|
March 08, 2014, 07:05:19 AM |
|
That is exactly what I ended up doing after digging a little deeper. The correct package on that page (for anyone who might need this in the future) is LINUX driver for kernel 3.x and 2.6.x and 2.4.x I'm running bamt 1.3 but first you must do this... you need to blacklist the old module. try this:
Code: [Select]
echo "blacklist r8169" | sudo tee -a /etc/modprobe.d/blacklist.conf taken from https://litecointalk.org/index.php?topic=2924.msg75706#msg75706works like a charm now. for some reason windows would become unstable with my second card and smos has been pretty good to me so far. (great now I have to register there just to say thanks)  |
|
|
|
|
|
repairguy
|
|
March 08, 2014, 07:31:48 AM |
|
That is exactly what I ended up doing after digging a little deeper. The correct package on that page (for anyone who might need this in the future) is LINUX driver for kernel 3.x and 2.6.x and 2.4.x I'm running bamt 1.3 but first you must do this... you need to blacklist the old module. try this:
Code: [Select]
echo "blacklist r8169" | sudo tee -a /etc/modprobe.d/blacklist.conf taken from https://litecointalk.org/index.php?topic=2924.msg75706#msg75706works like a charm now. for some reason windows would become unstable with my second card and smos has been pretty good to me so far. (great now I have to register there just to say thanks) That is surprisingly backwards of my experience. The first machine I build ran 6x gpus on windows like a dream. I tried to switch to bamt to reduce overhead. Didn't work. Ubuntu runs great but I am not sure if I really gained anything. |
|
|
|
|
|
evlew (OP)
|
|
March 08, 2014, 08:32:35 AM |
|
right now if i boot into window with a 290 and a 280x the 280x shows up as a generic vga in device manager
i manually install driver and it says successfully updated to r9 200 series
i got to device manager and it shows r9 200 series (my 290 which works great)
and the 280x shows up as a hd 7900 series and causes all sorts of crashes
i think i might need a fresh install of windows. will try tomorrow
|
|
|
|
|
|
repairguy
|
|
March 08, 2014, 08:38:18 AM |
|
right now if i boot into window with a 290 and a 280x the 280x shows up as a generic vga in device manager
i manually install driver and it says successfully updated to r9 200 series
i got to device manager and it shows r9 200 series (my 290 which works great)
and the 280x shows up as a hd 7900 series and causes all sorts of crashes
i think i might need a fresh install of windows. will try tomorrow
Fresh install is alot easier that screwing around trying to remove drivers. If you plan on installing more than 4 cards at a later time use the modded driver. and then mod your catalyst installer, then install the catalyst. (some people say that you can just use an older sdk rather than modding and installing catalyst installer, but I did it just the way I described and it worked perfectly) |
|
|
|
|
|
