BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools

[TheHarbinger]

Unfortunatelly, BAMT not support wireless network

I've had no problem in running bamt over a wireless network.

Well, you are one of the few. 

I have 3 USB adapters, 2 RaLink and a Broadcomm,  all listed as supported for debian sqeeze.  1 RaLink doesn't even show up when attached, the other and the Broadcomm chip show up, but refuse to connect to the network.  I got a old "g" adapter to connect, once, it stayed connected for about 2 hours, disconnected, then refused to be recognized after that.

In fact, it has been stated that by the author that wireless is not supported.

[1714134974]

1714134974

[1714134974]

1714134974

[lodcrappo]

Unfortunatelly, BAMT not support wireless network

what?

[lodcrappo]

Unfortunatelly, BAMT not support wireless network

I've had no problem in running bamt over a wireless network.

Well, you are one of the few.  

I have 3 USB adapters, 2 RaLink and a Broadcomm,  all listed as supported for debian sqeeze.  1 RaLink doesn't even show up when attached, the other and the Broadcomm chip show up, but refuse to connect to the network.  I got a old "g" adapter to connect, once, it stayed connected for about 2 hours, disconnected, then refused to be recognized after that.

In fact, it has been stated that by the author that wireless is not supported.

It was not supported in 0.4,  but as of the 0.5 image it should work fine.  Does for me at least.  I have only a few adapters to test with, but they all "just work".  this is first i've heard of trouble since 0.5.

[TheHarbinger]

Unfortunatelly, BAMT not support wireless network

I've had no problem in running bamt over a wireless network.

Well, you are one of the few.  

I have 3 USB adapters, 2 RaLink and a Broadcomm,  all listed as supported for debian sqeeze.  1 RaLink doesn't even show up when attached, the other and the Broadcomm chip show up, but refuse to connect to the network.  I got a old "g" adapter to connect, once, it stayed connected for about 2 hours, disconnected, then refused to be recognized after that.

In fact, it has been stated that by the author that wireless is not supported.

It was not supported in 0.4,  but as of the 0.5 image it should work fine.  Does for me at least.  I have only a few adapters to test with, but they all "just work".  this is first i've heard of trouble since 0.5.

Don't know what to tell you.  Simply doesn't work for me with four different adapters and chipsets.  Are you using encryption?  WES?  WPA?  WPA2?   Using WPA2 with AES here.  wpasupplicant loaded via aptitude install.

[jme621]

it didnt pick up my adapter either, i use this one http://www.meritline.com/airlink101-awll5088-wireless-n-ultra-mini-usb-adapter---p-45923.aspx

[lodcrappo]

Unfortunatelly, BAMT not support wireless network

I've had no problem in running bamt over a wireless network.

Well, you are one of the few.  

I have 3 USB adapters, 2 RaLink and a Broadcomm,  all listed as supported for debian sqeeze.  1 RaLink doesn't even show up when attached, the other and the Broadcomm chip show up, but refuse to connect to the network.  I got a old "g" adapter to connect, once, it stayed connected for about 2 hours, disconnected, then refused to be recognized after that.

In fact, it has been stated that by the author that wireless is not supported.

It was not supported in 0.4,  but as of the 0.5 image it should work fine.  Does for me at least.  I have only a few adapters to test with, but they all "just work".  this is first i've heard of trouble since 0.5.

Don't know what to tell you.  Simply doesn't work for me with four different adapters and chipsets.  Are you using encryption?  WES?  WPA?  WPA2?   Using WPA2 with AES here.  wpasupplicant loaded via aptitude install.

hmm.  dunno.  as always, I will try to make any hardware you send to me work.  otherwise, I think you (or someone) will have to sort that out and let me know what needs to be changed.  I don't have any wireless hardware that doesn't work here.

[lodcrappo]

Don't know what to tell you.  Simply doesn't work for me with four different adapters and chipsets.  Are you using encryption?  WES?  WPA?  WPA2?   Using WPA2 with AES here.  wpasupplicant loaded via aptitude install.

wpasupplicant comes preinstalled in 0.5.  you should not have been able to install it again.  are you sure you are using 0.5?

[boozer]

My wireless usb devices are pretty old, but I had better luck with wireless using WICD instead of network manager:
http://wicd.sourceforge.net/moinmoin/Wicd%20on%20Ubuntu

I also had to modify the device ID as suggested in this thread, but its specific to the Linksys WUSB100... just mentioning it in case its some sort of driver id issue in your case as well.
http://ubuntuforums.org/showthread.php?p=8086015#post8086015

[jamesg]

Just want to say thanks for the awesome software. Had trouble booting any other OS of a usb, but BAMT worked first time. Easy to use and setup, and it isn't full of other useless shit, just plug and mine.

Please show your appreciation by donating. 

[lodcrappo]

Just want to say thanks for the awesome software. Had trouble booting any other OS off a usb, but BAMT worked first time. Easy to use and setup, and it isn't full of other useless shit, just plug and mine.

glad to hear it.  always nice when it works for somebody.  based on # of download vs number of complaints, I have to assume it does work for most people, but sometimes seems like I only hear from the folks who have problems.

[asdlsd]

One of my machines keeps losing it's IP address.  It's like the lease expires, but never renews.  Only happens on one machine... is there a way to assign a static IP permanently to the machine that will survive a reboot?

I delete network-manager and problem is gone.

Many complain about it in internet...

[Inaba]

Well, after solving the IP addressing issue (assigned a static IP and all is well) ... I have another machine that seems to be having an issue.  This machine seems to lock up with I have the --api-listen line in cgminer_opts.  If I remove that, the machine is stable.

Anyone got any ideas why that might cause just this one machine to become unstable?

[Isokivi]

Well, after solving the IP addressing issue (assigned a static IP and all is well) ... I have another machine that seems to be having an issue.  This machine seems to lock up with I have the --api-listen line in cgminer_opts.  If I remove that, the machine is stable.

Anyone got any ideas why that might cause just this one machine to become unstable?

Your mining at gpumax ? I had some similiar like issues and had to abondin it for now myself.

[cmg5461]

Just wondering, is there a way to have a bash script run at start up?

[Inaba]

Your mining at gpumax ? I had some similiar like issues and had to abondin it for now myself.

Nope.. and besides the system will barely get that far before it locks up.

[Red Emerald]

Just wondering, is there a way to have a bash script run at start up?

Same way you run a bash script at start up on any other linux machine.  BAMT is just debian with the mining stuff installed.  Write an init script or just add a line to /etc/rc.local

[Isokivi]

Could someone mining in P2pool confirm the new difficulty changing working in bamt, im fairly sure it does not, but I'd like a second oppinnion.
To do it you need to edit pools.conf: Minername/sharedifficulty+localdifficulty

So for example:

Miner/1500+1

When I did this and restarted mining the rig never got areound to mining, saw 0mhs flowin on gpumon, if theres an issue I guess it is with either / or + sign in the adress.

[DeathAndTaxes]

It works using cgminer.conf & cgminer.  I have never used phoenix and pool.conf file.

Code:

"pools" : [
	{
		"url" : "192.168.0.189:9332",
		"user" : "user/1000+1",
		"pass" : "pass"
	}
...

[minero1]

hi loadcrappo, great work with BAMT, i've been using it since yesterday and i think i'm in love with it, the simplicity rocks! and this is coming from someone who had never experienced linux before  

Anyhow, i'm having a lot of rejects reported locally but when i check the pool stats (gpumax) they are not reflected there. its like phoenix thinks the pool is rejecting shares when its actually not. when directing shares from gpumax to abcpool it shows like 4% rejects but when i point them to bonuspool (clipse's pool) it shows like 40% rejects and according to the pool stats everything is in order with like 1% rejects.

what could be causing this?

EDIT: oh no the rejects are real, overnight accumulated over 4k rejected shares on GPUMAX, what could possibly go that wrong as to give me 20% reject rate?

EDIT 2: finally changed to cgminer and everything is going smooth now, thanks gigavps

[BitMinerN8]

What is the best way to troubleshoot mgpumon not running? It had been running for weeks in a putty console on my win 7 workstation/gaming system, I needed to reboot so I hit q to exit mgpumon, then typed exit to close the session. I rebooting my Win 7 system and when I connected via putty, gpumon works fine, but mgpumon (mgpumon /etc/bamt/mgpumon.conf) just clears the term window and goes back to the prompt. It wigs out the console too, like you can't see what you type anymore. Very strange. I did try restarting that rig, but it still will not run even after power cycle. I went to the console on the rig itself and try to run it from the GUI, but when you try to start it from the menu, it just pops the console window and closes. I tried looking in /var/log/bamt.log but no errors if you tail it and try to launch it from another term window.

Just to rule out a going bad USB stick, I also wrote a fresh image on a new USB stick, copied over my config files, still does not run. I think the only thing that changed was adding in the bamtpro_id: and do_submitter: a week or so ago when I became a BAMT Pro Member. Commenting out those lines does not fix it either.

Puzzled...