I did miss those git steps in the install.  I've run them now (added my user account to the plugdev group) and copied the rules file and copy/pasted the cgminer.conf file from the tutorial (minus the pool info).

Still nothing.  It hashes, but no shares.


I even tried using the newest version of the rules file directly from the repo.
Then I reran
Still nothing.



There's got to be something obvious that I'm missing.

I've been racking my brain trying to figure out why this isn't working.

My install procedures:


My cgminer.conf is only my pool info.

I run cgminer with:
It runs and detects the two block erupters and begins hashing, but submits no shares.  This is a screenshot after ~10 minutes:




I've also tried cgminer versions 3.2.2 (it ends up disconnecting the USB devices from /dev/) and 3.3.1 (it detects them, but no hashing at all) to no avail.
If I connect the erupter to my desktop computer running Windows 7 + cgminer 3.1.1, it works just fine.

Any help would be greatly appreciated.

---

edit: The erupter is connected to a powered USB hub supplied with 5v 1000mA power, so that shouldn't be an issue.

Ok, so I've been participating in Bitcoin mining for almost a month now and it's been going smoothly on my desktop rig (NVidia Card).

(Edit: Question one removed and title changed.  Turns out that I was misreading GUIMiner's status screen.  Now I feel like a doof.)

So I've been running Bitcoin solo mining on my old desktop for a few weeks now and it works absolutely fine running Bitcoin 3.21.  My new rig that I built (dual 5830s OC'd to 900Mhz) works fine connecting to mining pools and to my other desktop.  The issue I'm having is that whenever I try to connect to a locally running Bitcoin server (version 3.23), the Bitcoin application CPU usage spikes to consume a whole core and doesn't respond to mining clients.  I copied over my desktop's 3.21 version and it works fine.  What could be causing this and what can I do to fix it?
TLDR: New rig runs Bitcoin 3.21 as a server fine, but on client connect with Bitcoin 3.23, process CPU usage maxes out and server goes unresponsive.

If you need any details on my system setup, please feel free to ask.

Any advice or help is appreciated.  I'm a fairly technical person, so feel free to get nitty gritty.

Thanks in advance!

Ugh, I feel terrible about doing this, but I haven't seen any rules against it... so... well... bump?

I really wish this could get scooted to the appropriate forum.

I think I might be a latecomer to this "get out of newb free" party, but I'd like to submit my application.

I'm not necessarily new to Bitcoin and I consider myself a highly technical person (I actually work in the industry), so I'd be much obliged to be alleviated of my "Newbie" status.

If not... well... I've got another few posts and a few hours of waiting to do.

Oh, did I mention that I know how to use BBS tags?
Oh, and that I know how to use punctuation and grammar?
I hope those count for something. 

There's quite a few problems with this.
Unless a person is running a client configured to act like a server and somehow removes a username/password requirement along with allowing any IP, then sure, someone could just tell the client to send out the coins in their wallet.

Secondly, assuming that the client is configured properly and that it's a buffer overflow (or something similar) via network communication... well... the source code for the bitcoin client is publicly available and there haven't been any exploits so far.  That's not to say that there's no chance that there's a potential exploit, but for the most part, bitcoin has well defined protocol standards and uses JSON formatting to send data.

Lastly, if you're talking a local malicious action (where a user has access to a computer directly), then there's nothing bitcoin could do to stop it because that's a system wide unauthorized access.  Anything a user could do an attacker would do.


So long story short, I wouldn't sweat it.  Bitcoin uses well defined standards so unless there happens to be a massive gaping hole in open source software that nobody's managed to spot (and the exploitation of it thus far has impossibly managed to stay invisible), then there really isn't a need to worry.

Ok, so I've been participating in Bitcoin mining for almost a month now and it's been going smoothly on my desktop rig (NVidia Card).

I had a new rig come in recently (Windows 7 x64, Radeon 5830 x2 OC to 900Mhz, Phenom II dual) so I decided to run a server on my desktop and have my new rig connect to it.
All seems to be going well - the hash speeds are as expected, temp is fine, no connection issues - but after a few days of running I noticed that guiminer reported that of the ~5k shares that each video card had submitted, only about 200 from each were accepted.  I reset the numbers and only ran one instance of a miner (just using one card) and after 500+ shares, all of them were accepted.
TLDR (issue #1): Using two video cards on one rig to connect to my desktop rejects over 80% of the shares from each card.


The second issue is setting up a Bitcoin server on my new rig so that it can connect to itself instead of across the network.  My older desktop is running Bitcoin 3.21 and the server mode works fine.  My new rig running 3.23 gives me "Connection error" warnings in guiminer.  Worse still is that as soon as a client tries to connect to the 3.23 server, the bitcoin.exe process spikes to full load and no amount of waiting fixes it.
TLDR (issue #2): New rig runs Bitcoin 3.21 as a server fine, but on client connect with Bitcoin 3.23, process CPU usage maxes out and goes unresponsive.


Any advice or help is appreciated.  I'm a fairly technical person, so feel free to get nitty gritty.
Also, I apologize for gluing two issues in one thread (and in the Newbie board at that!) but I don't have access to the appropriate forum.

Thanks in advance!