My BAMT machine keeps losing the network connection, and killing the miner.
I thought it was just my setup, but I guess not.
Topic: BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools - page 55. (Read 324169 times)
April 02, 2012, 04:43:28 PM
I think I'm having a similar issue.
My BAMT machine keeps losing the network connection, and killing the miner.
I thought it was just my setup, but I guess not.
My BAMT machine keeps losing the network connection, and killing the miner.
I thought it was just my setup, but I guess not.
April 02, 2012, 03:35:24 PM
Inaba,
Yeah, same problem here. Something is broken in BAMT, but I have as yet to figure out what it is. Rigs work fine in other distro's, so I know it's not the hardware.
What do you see when you connect keyboard and mouse? Mine are all up, but network seems to be down...
Quote
I finally just assigned a static IP to my rig that had this problem (network disconnecting even though lease had not expired) and that fixed it. I have four identical motherboards... 3 run fine with dhcp reservations, but I had to assign static on this one board for whatever reason for the network to remain connected.
Yeah, same problem here. Something is broken in BAMT, but I have as yet to figure out what it is. Rigs work fine in other distro's, so I know it's not the hardware.
What do you see when you connect keyboard and mouse? Mine are all up, but network seems to be down...
April 02, 2012, 03:32:11 PM
Quote
I finally just assigned a static IP to my rig that had this problem (network disconnecting even though lease had not expired) and that fixed it. I have four identical motherboards... 3 run fine with dhcp reservations, but I had to assign static on this one board for whatever reason for the network to remain connected.
Yeah, same problem here. Something is broken in BAMT, but I have as yet to figure out what it is. I brought up the issue several pages back, but was told it was my hardware or router. Rigs work fine in other distro's, so I know it's not the hardware or the router.
April 02, 2012, 03:19:36 PM
I fix that. Just make an own linux usb pen drive os with more recent software and now everything is working fine 
If you didnt know that:
BAMT use a Kernel (all drivers for network, usb, cpu, everytghing) from 2009 and a networking software from 2010...
If you didnt know that:
BAMT use a Kernel (all drivers for network, usb, cpu, everytghing) from 2009 and a networking software from 2010...
I finally just assigned a static IP to my rig that had this problem (network disconnecting even though lease had not expired) and that fixed it. I have four identical motherboards... 3 run fine with dhcp reservations, but I had to assign static on this one board for whatever reason for the network to remain connected.
April 02, 2012, 02:45:15 PM
lodcrappo,
Is there any specific reason you choose Debian stable instead of Ubuntu?
Is there any specific reason you choose Debian stable instead of Ubuntu?
April 02, 2012, 09:22:16 AM
I have no idea what that means! I'm using a Buffalo G router running DD-WRT as the extender, set as 192.168.1.1.
My primary router is a Buffalo N, also running DD-WRT, set as 192.168.11.1.
How would I go about creating a route between the routers?
How about the tracert?
Go to http://192.168.11.1 enter username and password.
Click Internet...then choose route
add route to 192.168.1.0 (and 255.255.255.0 if subnet mask is needed) and select 192.168.1.1 as the next hop and leave the metric as default.
Something like that depending on your router should give your clients access to/ from the remote subnet.
Tracert is a command line tool you can run from windows to see the path your request is making. Its done like this from the command line:
tracert 192.168.1.1
It will tell you all the hops from the client your are running to the destination and the response from the routers at each hop. You can use that to see where the path is ending or looping for debugging a routing issue.
That's excellent info, thanks!
I'll try it and report back.
April 02, 2012, 01:39:35 AM
After about an hour of reading support forums and a little of this and that, I finally got my wireless adapter to work, yeah for jme!!!
April 02, 2012, 12:02:10 AM
I have no idea what that means! I'm using a Buffalo G router running DD-WRT as the extender, set as 192.168.1.1.
My primary router is a Buffalo N, also running DD-WRT, set as 192.168.11.1.
How would I go about creating a route between the routers?
How about the tracert?
Go to http://192.168.11.1 enter username and password.
Click Internet...then choose route
add route to 192.168.1.0 (and 255.255.255.0 if subnet mask is needed) and select 192.168.1.1 as the next hop and leave the metric as default.
Something like that depending on your router should give your clients access to/ from the remote subnet.
Tracert is a command line tool you can run from windows to see the path your request is making. Its done like this from the command line:
tracert 192.168.1.1
It will tell you all the hops from the client your are running to the destination and the response from the routers at each hop. You can use that to see where the path is ending or looping for debugging a routing issue.
April 01, 2012, 01:50:58 PM
Anyone got an idea as to why I can't connect to my BAMT machine via the web gui?
BAMT is on a PC in my shop, connecting over wifi through a range extender, with a static IP.
Everything seems to be working fine, except I can't get to it via the web gui (192.168.1.105) or remote desktop connection.
Both worked fine before I moved the machine out to the new location.
Could it be because the BAMT machine is on a different subnet than the rest of my network?
My primary network is 192.168.11.x, BAMT is on 192.168.1.x.
I can't move it back to the primary network, because the wifi won't quite reach that far without the repeater.
Thoughts?
BAMT is on a PC in my shop, connecting over wifi through a range extender, with a static IP.
Everything seems to be working fine, except I can't get to it via the web gui (192.168.1.105) or remote desktop connection.
Both worked fine before I moved the machine out to the new location.
Could it be because the BAMT machine is on a different subnet than the rest of my network?
My primary network is 192.168.11.x, BAMT is on 192.168.1.x.
I can't move it back to the primary network, because the wifi won't quite reach that far without the repeater.
Thoughts?
You probably need a route to the 192.168.1.0 subnet on your main router to the AP. Do a tracert from a 192.168.11.0 client to 192.168.1.1 (if your AP is 192.168.1.1) to check.
I have no idea what that means! I'm using a Buffalo G router running DD-WRT as the extender, set as 192.168.1.1.
My primary router is a Buffalo N, also running DD-WRT, set as 192.168.11.1.
How would I go about creating a route between the routers?
How about the tracert?
April 01, 2012, 01:17:30 PM
I fix that. Just make an own linux usb pen drive os with more recent software and now everything is working fine
If you didnt know that:
BAMT use a Kernel (all drivers for network, usb, cpu, everytghing) from 2009 and a networking software from 2010...
If you didnt know that:
BAMT use a Kernel (all drivers for network, usb, cpu, everytghing) from 2009 and a networking software from 2010...
And did you integrate all BAMT tools? I like BAMT for the web interface...
Btw, which OS did you take?
April 01, 2012, 08:11:12 AM
I still have problems that bamt looses network connection after some time. The lease time is not over. Also i have set up the ip adress to the mac in the dhcp server.
Anyone an idea? I have tested many different router and problem is still there.
Anyone an idea? I have tested many different router and problem is still there.
Different network card?
Mine are onboard.
I mean you could try using a different (PCI or PCIe) network card and see if it helps. If you have time you can try if the same problem happens on windows.
April 01, 2012, 07:57:58 AM
I still have problems that bamt looses network connection after some time. The lease time is not over. Also i have set up the ip adress to the mac in the dhcp server.
Anyone an idea? I have tested many different router and problem is still there.
Anyone an idea? I have tested many different router and problem is still there.
Different network card?
Mine are onboard.
April 01, 2012, 07:57:36 AM
I still have problems that bamt looses network connection after some time. The lease time is not over. Also i have set up the ip adress to the mac in the dhcp server.
Anyone an idea? I have tested many different router and problem is still there.
Anyone an idea? I have tested many different router and problem is still there.
I just noticed I have the same problem... Network connection fails, but lease has not expired. When I attach a monitor and keyboard to my rigs, they are still up, but no connection...
April 01, 2012, 07:53:59 AM
I still have problems that bamt looses network connection after some time. The lease time is not over. Also i have set up the ip adress to the mac in the dhcp server.
Anyone an idea? I have tested many different router and problem is still there.
Anyone an idea? I have tested many different router and problem is still there.
Different network card?
April 01, 2012, 12:39:22 AM
Anyone got an idea as to why I can't connect to my BAMT machine via the web gui?
BAMT is on a PC in my shop, connecting over wifi through a range extender, with a static IP.
Everything seems to be working fine, except I can't get to it via the web gui (192.168.1.105) or remote desktop connection.
Both worked fine before I moved the machine out to the new location.
Could it be because the BAMT machine is on a different subnet than the rest of my network?
My primary network is 192.168.11.x, BAMT is on 192.168.1.x.
I can't move it back to the primary network, because the wifi won't quite reach that far without the repeater.
Thoughts?
BAMT is on a PC in my shop, connecting over wifi through a range extender, with a static IP.
Everything seems to be working fine, except I can't get to it via the web gui (192.168.1.105) or remote desktop connection.
Both worked fine before I moved the machine out to the new location.
Could it be because the BAMT machine is on a different subnet than the rest of my network?
My primary network is 192.168.11.x, BAMT is on 192.168.1.x.
I can't move it back to the primary network, because the wifi won't quite reach that far without the repeater.
Thoughts?
You probably need a route to the 192.168.1.0 subnet on your main router to the AP. Do a tracert from a 192.168.11.0 client to 192.168.1.1 (if your AP is 192.168.1.1) to check.
April 01, 2012, 12:08:47 AM
I'm having an odd memory underclocking issue.
I have a 6990 where I have flashed the BIOS to allow for a 150MHz memory clock. With cgminer 2.3.1-2 on Ubuntu x64 I can set the memory clocks to 150MHz and there are no issues. Also can use it just fine with atitweak and phoenix miner.
With BAMT, if I put in the profile (P2) that memory should be 150MHz, it freaks out. On one machine it just halts. On another machine it ignores it and runs the memory at 1250MHz. It also ran at 150Mhz for a little while then went to 1250MHz.
I suspect something is conflicting with something else within BAMT. Any ideas?
I have a 6990 where I have flashed the BIOS to allow for a 150MHz memory clock. With cgminer 2.3.1-2 on Ubuntu x64 I can set the memory clocks to 150MHz and there are no issues. Also can use it just fine with atitweak and phoenix miner.
With BAMT, if I put in the profile (P2) that memory should be 150MHz, it freaks out. On one machine it just halts. On another machine it ignores it and runs the memory at 1250MHz. It also ran at 150Mhz for a little while then went to 1250MHz.
I suspect something is conflicting with something else within BAMT. Any ideas?
March 31, 2012, 08:02:42 PM
Anyone got an idea as to why I can't connect to my BAMT machine via the web gui?
BAMT is on a PC in my shop, connecting over wifi through a range extender, with a static IP.
Everything seems to be working fine, except I can't get to it via the web gui (192.168.1.105) or remote desktop connection.
Both worked fine before I moved the machine out to the new location.
Could it be because the BAMT machine is on a different subnet than the rest of my network?
My primary network is 192.168.11.x, BAMT is on 192.168.1.x.
I can't move it back to the primary network, because the wifi won't quite reach that far without the repeater.
Thoughts?
BAMT is on a PC in my shop, connecting over wifi through a range extender, with a static IP.
Everything seems to be working fine, except I can't get to it via the web gui (192.168.1.105) or remote desktop connection.
Both worked fine before I moved the machine out to the new location.
Could it be because the BAMT machine is on a different subnet than the rest of my network?
My primary network is 192.168.11.x, BAMT is on 192.168.1.x.
I can't move it back to the primary network, because the wifi won't quite reach that far without the repeater.
Thoughts?
March 31, 2012, 06:25:51 PM
overvolting in linux is more limited than windows. probably just cannot be done.
Well that sucks. Was hoping I could hit a crazy clock like 1040 and get 340MH/s if I up'd the voltage.At current difficulty and exchange rate, you're talking about less than $1 per MH per year.
315-320 stable is easy. how much time are you going to spend chasing that extra $20 per year you'd get with 340? And how much mining time will you lose due to lockups in the pursuit? In the end, will all the time spent overclocking actually end up costing you money? It's a very real possibility.
March 31, 2012, 05:35:06 PM
overvolting in linux is more limited than windows. probably just cannot be done.
Well that sucks. Was hoping I could hit a crazy clock like 1040 and get 340MH/s if I up'd the voltage.At current difficulty and exchange rate, you're talking about less than $1 per MH per year.
315-320 stable is easy. how much time are you going to spend chasing that extra $20 per year you'd get with 340? And how much mining time will you lose due to lockups in the pursuit? In the end, will all the time spent overclocking actually end up costing you money? It's a very real possibility.
March 31, 2012, 05:30:33 PM
overvolting in linux is more limited than windows. probably just cannot be done.
Well that sucks. Was hoping I could hit a crazy clock like 1040 and get 340MH/s if I up'd the voltage. Jump to: