Bitcoin Forum
November 30, 2021, 10:38:16 AM *
News: Latest Bitcoin Core release: 22.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 [78] 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 »
  Print  
Author Topic: Official FutureBit Moonlander 2 Driver and Support Thread  (Read 69170 times)
jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
April 25, 2018, 04:16:51 PM
 #1541

Code:
bfgminer.exe --scrypt -o stratum+tcp://eu.multipool.us:3351 -u Moonlander2.1 -p x,d=256  -S MLD:all --set MLD:clock=796
pause

Ok so i have it running on litecoinpool and on multipool. Works but i run into the same error. After a while it just stops hashing. If i restart bfg then it works like a champ again.
So can someone help me. Is there a way to set bfgminer up to auto restart after an hour. yea I know its not perfect but at this point i just want the dang thing to run nearly 24 hours. I hate waking up to find it pooped out after 30 minutes and sat idle 6 hours. Is there a way to add a piece to this scrypt that will make it auto restart after an hour? Since I have no clue why it keeps stopping. And before we trouble shoot again just assume its all running on the right stuff. yes powered hub. yes 100mbps connection which is stable. Yes way more than adequate cooling. This thing will run 30 minutes and stop or 32 hours and stop. No rhyme or reason i see. If there is a code to auto restart after an hour that would be gold.  Any help?

Any ideas?

This depends on whats going on with your setup. First are you running the latest bfgminer binaries I release that have auto-restart built into the miner? Sounds like your not since restarting bfgminer pretty much does what I already do in the new driver release automatically.

i have 5.4.2. isnt that the newest one? i see no restart timer


You should see 5.4.2-38 at the top if your running the latest version.

Project Apollo: A Pod Miner Designed for the Home https://bitcointalk.org/index.php?topic=4974036
FutureBit Moonlander 2 USB Scrypt Stick Miner: https://bitcointalk.org/index.php?topic=2125643.0
LTC:LX5vpxrQE4eLRLPobKwZhw2comkKFCh3p4 - BTC:14w9Lea6kdVzspJk8TQRe7qSYu9LhzJJsh
1638268696
Hero Member
*
Offline Offline

Posts: 1638268696

View Profile Personal Message (Offline)

Ignore
1638268696
Reply with quote  #2

1638268696
Report to moderator
1638268696
Hero Member
*
Offline Offline

Posts: 1638268696

View Profile Personal Message (Offline)

Ignore
1638268696
Reply with quote  #2

1638268696
Report to moderator
1638268696
Hero Member
*
Offline Offline

Posts: 1638268696

View Profile Personal Message (Offline)

Ignore
1638268696
Reply with quote  #2

1638268696
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1638268696
Hero Member
*
Offline Offline

Posts: 1638268696

View Profile Personal Message (Offline)

Ignore
1638268696
Reply with quote  #2

1638268696
Report to moderator
1638268696
Hero Member
*
Offline Offline

Posts: 1638268696

View Profile Personal Message (Offline)

Ignore
1638268696
Reply with quote  #2

1638268696
Report to moderator
jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
April 25, 2018, 04:22:22 PM
 #1542

I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!


Hmm thats not good. U2 is the memory voltage controller. Sounds like something shorted or overheated. Were you running higher clocks? If only the controller blew the repair would be relatively easy and its a 50 cent component if your good with removing/soldering SMDs. If your in the US and don't mind sending it in shoot me a PM...catastrophic failures like this are super rare so they are good dissecting cases.

Project Apollo: A Pod Miner Designed for the Home https://bitcointalk.org/index.php?topic=4974036
FutureBit Moonlander 2 USB Scrypt Stick Miner: https://bitcointalk.org/index.php?topic=2125643.0
LTC:LX5vpxrQE4eLRLPobKwZhw2comkKFCh3p4 - BTC:14w9Lea6kdVzspJk8TQRe7qSYu9LhzJJsh
Christocyr
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
April 25, 2018, 06:44:14 PM
 #1543

I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!


Hmm thats not good. U2 is the memory voltage controller. Sounds like something shorted or overheated. Were you running higher clocks? If only the controller blew the repair would be relatively easy and its a 50 cent component if your good with removing/soldering SMDs. If your in the US and don't mind sending it in shoot me a PM...catastrophic failures like this are super rare so they are good dissecting cases.

No, I was running straight defaults at 600 clock speed on litecoinpool.org with 128 difficulty. I am in the US, and will send you a PM. Thanks!

pyroandy
Newbie
*
Offline Offline

Activity: 88
Merit: 0


View Profile
April 26, 2018, 11:59:26 AM
 #1544

I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!


Hmm thats not good. U2 is the memory voltage controller. Sounds like something shorted or overheated. Were you running higher clocks? If only the controller blew the repair would be relatively easy and its a 50 cent component if your good with removing/soldering SMDs. If your in the US and don't mind sending it in shoot me a PM...catastrophic failures like this are super rare so they are good dissecting cases.

No, I was running straight defaults at 600 clock speed on litecoinpool.org with 128 difficulty. I am in the US, and will send you a PM. Thanks!



Is there something wroung with the USB port on your computer?
pyroandy
Newbie
*
Offline Offline

Activity: 88
Merit: 0


View Profile
April 26, 2018, 12:04:25 PM
 #1545

...

Nice looking setup. Personally, I would only run 5 off that hub so you can run them full speed. If you only have on one hub then you could plug you Pi and extra fans into the hub too because they don't need that much power.  Have you tried to get bfgminer to run at startup? I am new to pi and Linux in general and have not been able to get it to work.

Nah I dont really need to been using pi's for years and they seldom crash, I use ssh and tmux to control it. that theres my trusty old pi2 with a broken hdmi out  Grin

I'm sure you know what ssh is tmux may be a mystery to you it allows you to run a program through ssh and it'll keep running even after you disconnect. its similair to screen but a bit more advanced/configurable

Yes, I tried screen but it was not getting me anywhere. Besides I just want it to autostart every time the pi boots up.

make sure screen is installed (sudo apt install screen)

create a file in your home directory with nano like this:

Code:
nano startup.sh

inside this file put something like this

Code:
cd /home/YOUR_PI_ACCOUNT_NAME/YOUR_BFGMINER_FOLDER_NAME
screen -dmS miner bash -c './start_moonlander.sh; exec bash'

then turn startup script to executible

Code:
sudo chmod +x startup.sh

and add this to crontab

Code:
sudo crontab -e

go down after all the ## and add this line

Code:
@reboot /home/YOUR_PI_ACCOUNT_NAME/startup.sh

then

Code:
sudo reboot

once rebooted just do

Code:
sudo screen -dr

and you should see bfgminer running. Press control then A then D at the same time to exit screen without terminating process.

That should do it  Wink

Thanks for your time putting these instructions together. I finally had a chance to try it last night and the miner starts every time I power up the pi. One last question, is there a way to automate the last step (sudo screen -dr) so the terminal with bfgminer comes up on the connected HDMI screen every time?
pyroandy
Newbie
*
Offline Offline

Activity: 88
Merit: 0


View Profile
April 26, 2018, 11:33:58 PM
Last edit: April 27, 2018, 10:20:43 AM by pyroandy
 #1546

I'm looking to update my raspberry pi from 5.4.2-34 to 5.4.2-38 for the auto restart. Has the GitHub armv6 download link been updated to the newest version? It still installs ver. 5.4.2-34.

thanks!


Maybe that's why bfgminer on my pi will not auto restart. My bfgminer comes up with 5.4.2-34, not 5.4.2-38 when following the instructions from page 1
jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
April 30, 2018, 06:30:16 PM
 #1547

I'm looking to update my raspberry pi from 5.4.2-34 to 5.4.2-38 for the auto restart. Has the GitHub armv6 download link been updated to the newest version? It still installs ver. 5.4.2-34.

thanks!


Maybe that's why bfgminer on my pi will not auto restart. My bfgminer comes up with 5.4.2-34, not 5.4.2-38 when following the instructions from page 1

hmmm, the beta 2 link for armv6 shows build 34? Ill check it and update it. Ill be building new version with latest updates soon anyway.

Project Apollo: A Pod Miner Designed for the Home https://bitcointalk.org/index.php?topic=4974036
FutureBit Moonlander 2 USB Scrypt Stick Miner: https://bitcointalk.org/index.php?topic=2125643.0
LTC:LX5vpxrQE4eLRLPobKwZhw2comkKFCh3p4 - BTC:14w9Lea6kdVzspJk8TQRe7qSYu9LhzJJsh
pyroandy
Newbie
*
Offline Offline

Activity: 88
Merit: 0


View Profile
April 30, 2018, 08:50:27 PM
 #1548

I'm looking to update my raspberry pi from 5.4.2-34 to 5.4.2-38 for the auto restart. Has the GitHub armv6 download link been updated to the newest version? It still installs ver. 5.4.2-34.

thanks!


Maybe that's why bfgminer on my pi will not auto restart. My bfgminer comes up with 5.4.2-34, not 5.4.2-38 when following the instructions from page 1

hmmm, the beta 2 link for armv6 shows build 34? Ill check it and update it. Ill be building new version with latest updates soon anyway.

Thanks for looking into this. And just an FYI the instructions for the Pi install on page one still links to the old build.
Christocyr
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
May 01, 2018, 01:22:40 AM
 #1549

I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!


Hmm thats not good. U2 is the memory voltage controller. Sounds like something shorted or overheated. Were you running higher clocks? If only the controller blew the repair would be relatively easy and its a 50 cent component if your good with removing/soldering SMDs. If your in the US and don't mind sending it in shoot me a PM...catastrophic failures like this are super rare so they are good dissecting cases.

No, I was running straight defaults at 600 clock speed on litecoinpool.org with 128 difficulty. I am in the US, and will send you a PM. Thanks!



Is there something wroung with the USB port on your computer?

No, I have been running two other miners and no problem with that port. Only thing I can think of is that a surge took it out.  Are there any other components before the voltage controller from the initial usb connection on that circuit? Jstefanop, I sent you a PM a couple of days ago, but I am not sure if you got it. Thanks!
jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
May 03, 2018, 05:38:57 PM
 #1550

I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!


Hmm thats not good. U2 is the memory voltage controller. Sounds like something shorted or overheated. Were you running higher clocks? If only the controller blew the repair would be relatively easy and its a 50 cent component if your good with removing/soldering SMDs. If your in the US and don't mind sending it in shoot me a PM...catastrophic failures like this are super rare so they are good dissecting cases.

No, I was running straight defaults at 600 clock speed on litecoinpool.org with 128 difficulty. I am in the US, and will send you a PM. Thanks!



Is there something wroung with the USB port on your computer?

No, I have been running two other miners and no problem with that port. Only thing I can think of is that a surge took it out.  Are there any other components before the voltage controller from the initial usb connection on that circuit? Jstefanop, I sent you a PM a couple of days ago, but I am not sure if you got it. Thanks!

Sent you a PM.

Project Apollo: A Pod Miner Designed for the Home https://bitcointalk.org/index.php?topic=4974036
FutureBit Moonlander 2 USB Scrypt Stick Miner: https://bitcointalk.org/index.php?topic=2125643.0
LTC:LX5vpxrQE4eLRLPobKwZhw2comkKFCh3p4 - BTC:14w9Lea6kdVzspJk8TQRe7qSYu9LhzJJsh
pyroandy
Newbie
*
Offline Offline

Activity: 88
Merit: 0


View Profile
May 04, 2018, 11:51:47 AM
 #1551

I'm looking to update my raspberry pi from 5.4.2-34 to 5.4.2-38 for the auto restart. Has the GitHub armv6 download link been updated to the newest version? It still installs ver. 5.4.2-34.

thanks!


Maybe that's why bfgminer on my pi will not auto restart. My bfgminer comes up with 5.4.2-34, not 5.4.2-38 when following the instructions from page 1

hmmm, the beta 2 link for armv6 shows build 34? Ill check it and update it. Ill be building new version with latest updates soon anyway.

Any idea when the armv6 build might be updated? I have to restart my pi and moonlander about once a day do to internet dropouts.
Finless
Newbie
*
Offline Offline

Activity: 44
Merit: 0


View Profile
May 05, 2018, 05:00:46 PM
 #1552

I just installed the Windows 10 update 1803 and after install the Moonlander2 drivers did not work.
In device manager it listed the Moonlanders but had a triangle.
BFGMiner when run says "No devices found".
I tried reinstalling them, removing them and reinstalling but to no avail. The driver Preinstaller program fails with an error.
When I try to manually install the drivers, the error says INF file invalid.

I downloaded the v6.7.5 version from the driver page and they worked!
In device manager under COM ports it no longer lists them as Moonlander2 and instead lists them as Silicon Labs CP210x USB to UART Bridge (COMx).
BFGimner now sees them Smiley

Just a tip should you run into this.

Bob
jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
May 05, 2018, 06:55:56 PM
 #1553

I just installed the Windows 10 update 1803 and after install the Moonlander2 drivers did not work.
In device manager it listed the Moonlanders but had a triangle.
BFGMiner when run says "No devices found".
I tried reinstalling them, removing them and reinstalling but to no avail. The driver Preinstaller program fails with an error.
When I try to manually install the drivers, the error says INF file invalid.

I downloaded the v6.7.5 version from the driver page and they worked!
In device manager under COM ports it no longer lists them as Moonlander2 and instead lists them as Silicon Labs CP210x USB to UART Bridge (COMx).
BFGimner now sees them Smiley

Just a tip should you run into this.

Bob


Sounds like some driver signing issue with the new windows release. Im sure silicon labs will sort it out.

Project Apollo: A Pod Miner Designed for the Home https://bitcointalk.org/index.php?topic=4974036
FutureBit Moonlander 2 USB Scrypt Stick Miner: https://bitcointalk.org/index.php?topic=2125643.0
LTC:LX5vpxrQE4eLRLPobKwZhw2comkKFCh3p4 - BTC:14w9Lea6kdVzspJk8TQRe7qSYu9LhzJJsh
peeess
Newbie
*
Offline Offline

Activity: 38
Merit: 0


View Profile
May 06, 2018, 10:54:26 AM
 #1554

I have 4 of them, which no longer work thanks to the windows upgrade. I can get 1 with the 6.75 driver to work, but the rest have conflicts with COM ports on that version. Did anyone figure out a work-around yet for multiple Moonlanders?
doroboNeko
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
May 07, 2018, 03:52:26 AM
 #1555

Hi. I have downloaded the software specific to the miner and it run fine on a Debian machine. Then i moved the miner to another machine that has Gentoo and bfgminer ran fine for like a day or two and then does segmentation fault. It has happened very consistently so i ran it through dbg to get log. I don't know if there is another place where i can put this or if there is other way to get more debugging info.
Code:
Starting program: /home/user/bfgminer_5.4.2-futurebit2_linux_x86_64/bfgminer --scrypt -o stratum+tcp://hub.miningpoolhub.com:20523/\#skipcbcheck -u userName.minerName -p p -d 128 -S ALL --set MLD:clock=796
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff4ae2700 (LWP 2349)]
[New Thread 0x7ffff42e1700 (LWP 2350)]
[New Thread 0x7ffff3ae0700 (LWP 2351)]
[Thread 0x7ffff42e1700 (LWP 2350) exited]
[New Thread 0x7ffff32df700 (LWP 2352)]
[Thread 0x7ffff3ae0700 (LWP 2351) exited]
[New Thread 0x7ffff2ade700 (LWP 2353)]
[Thread 0x7ffff32df700 (LWP 2352) exited]
[New Thread 0x7ffff22dd700 (LWP 2354)]
[Thread 0x7ffff2ade700 (LWP 2353) exited]
[New Thread 0x7ffff1adc700 (LWP 2355)]
[Thread 0x7ffff22dd700 (LWP 2354) exited]
[New Thread 0x7ffff12db700 (LWP 2356)]
[Thread 0x7ffff1adc700 (LWP 2355) exited]
[New Thread 0x7ffff0ada700 (LWP 2357)]
[Thread 0x7ffff12db700 (LWP 2356) exited]
[Thread 0x7ffff0ada700 (LWP 2357) exited]
[New Thread 0x7ffff0ada700 (LWP 2360)]
[New Thread 0x7ffff12db700 (LWP 2361)]
[Thread 0x7ffff12db700 (LWP 2361) exited]
[New Thread 0x7ffff12db700 (LWP 2362)]
[Thread 0x7ffff0ada700 (LWP 2360) exited]
[New Thread 0x7ffff1adc700 (LWP 2364)]
[New Thread 0x7ffff22dd700 (LWP 2365)]
[New Thread 0x7ffff3cb8700 (LWP 2366)]
[New Thread 0x7ffff34b7700 (LWP 2367)]
[New Thread 0x7ffff2cb6700 (LWP 2368)]
[New Thread 0x7fffe3fff700 (LWP 2369)]
[Thread 0x7ffff2cb6700 (LWP 2368) exited]
[New Thread 0x7ffff2cb6700 (LWP 2370)]
[New Thread 0x7fffe37fe700 (LWP 9331)]
[Thread 0x7fffe37fe700 (LWP 9331) exited]

Thread 13 "stratum0" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff12db700 (LWP 2362)]
0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#0  0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#1  0x00007ffff757319c in curl_easy_recv () from /usr/lib64/libcurl-gnutls.so.4
#2  0x0000000000437acb in clear_sock (pool=pool@entry=0x6971e0) at util.c:1837
#3  0x000000000043c7c0 in recv_line (pool=pool@entry=0x6971e0) at util.c:1937
#4  0x000000000042ce13 in stratum_thread (userdata=0x6971e0) at miner.c:9657
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7ffff2cb6700 (LWP 2370)):
#0  0x00007ffff711facd in read () from /lib64/libpthread.so.0
#1  0x00007ffff6eecaaf in _nc_wgetch () from /usr/lib64/libncurses.so.5
#2  0x00007ffff6eed426 in wgetch () from /usr/lib64/libncurses.so.5
#3  0x00000000004117f3 in __real_getch () at ./miner.h:206
#4  my_cancellable_getch () at miner.c:3787
#5  0x00000000004328f5 in input_thread (userdata=<optimized out>) at miner.c:8895
#6  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#7  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7fffe3fff700 (LWP 2369)):
#0  0x00007ffff64cd2a3 in epoll_wait () from /lib64/libc.so.6
#1  0x00000000004172f9 in hotplug_thread (p=<optimized out>) at miner.c:13087
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7ffff34b7700 (LWP 2367)):
#0  0x00007ffff6497c6d in nanosleep () from /lib64/libc.so.6
#1  0x00007ffff6497baa in sleep () from /lib64/libc.so.6
#2  0x0000000000422bb2 in watchdog_thread (userdata=<optimized out>) at miner.c:11609
#3  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#4  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7ffff3cb8700 (LWP 2366)):
#0  0x00007ffff712019d in nanosleep () from /lib64/libpthread.so.0
#1  0x0000000000435f75 in _cgsleep_us_r_nanosleep (tv_start=<optimized out>, us=<optimized out>) at util.c:1474
#2  0x0000000000439cf3 in cgsleep_ms_r (ms=30000, tv_start=0x7ffff3cb6ea0) at util.c:1457
#3  cgsleep_ms (ms=ms@entry=30000) at util.c:1483
#4  0x000000000042b8c5 in watchpool_thread (userdata=<optimized out>) at miner.c:11461
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7ffff22dd700 (LWP 2365)):
#0  0x00007ffff64c3f63 in select () from /lib64/libc.so.6
#1  0x000000000042780a in submit_work_thread (userdata=<optimized out>) at miner.c:6976
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7ffff1adc700 (LWP 2364)):
#0  0x00007ffff711facd in read () from /lib64/libpthread.so.0
#1  0x0000000000451d8c in read (__nbytes=8, __buf=0x7ffff1ad9dd0, __fd=13) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  _serial_read (fd=fd@entry=13, buf=buf@entry=0x7ffff1ad9dd0 "<\020\377\032\t'V\024`\f", bufsiz=bufsiz@entry=8,
    eol=eol@entry=0x0) at lowl-vcom.c:1239
#3  0x0000000000455042 in futurebit_scanhash (thr=0x6bbc10, work=0x6bb330, max_nonce=<optimized out>) at driver-futurebit.c:650
#4  0x0000000000433d3f in minerloop_scanhash (mythr=0x6bbc10) at deviceapi.c:274
#5  0x0000000000434eb2 in miner_thread (userdata=0x6bbc10) at deviceapi.c:772
#6  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#7  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7ffff12db700 (LWP 2362)):
#0  0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#1  0x00007ffff757319c in curl_easy_recv () from /usr/lib64/libcurl-gnutls.so.4
#2  0x0000000000437acb in clear_sock (pool=pool@entry=0x6971e0) at util.c:1837
#3  0x000000000043c7c0 in recv_line (pool=pool@entry=0x6971e0) at util.c:1937
#4  0x000000000042ce13 in stratum_thread (userdata=0x6971e0) at miner.c:9657
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ffff4ae2700 (LWP 2349)):
#0  0x00007ffff64c18fd in poll () from /lib64/libc.so.6
#1  0x00007ffff7fb5fc1 in ?? () from /lib64/libusb-1.0.so.0
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ffff7f9ab40 (LWP 2345)):
#0  0x00007ffff711b7f6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x0000000000408a4e in main (argc=1, argv=<optimized out>) at miner.c:13859

jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
May 08, 2018, 12:22:05 AM
 #1556

Hi. I have downloaded the software specific to the miner and it run fine on a Debian machine. Then i moved the miner to another machine that has Gentoo and bfgminer ran fine for like a day or two and then does segmentation fault. It has happened very consistently so i ran it through dbg to get log. I don't know if there is another place where i can put this or if there is other way to get more debugging info.
Code:
Starting program: /home/user/bfgminer_5.4.2-futurebit2_linux_x86_64/bfgminer --scrypt -o stratum+tcp://hub.miningpoolhub.com:20523/\#skipcbcheck -u userName.minerName -p p -d 128 -S ALL --set MLD:clock=796
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff4ae2700 (LWP 2349)]
[New Thread 0x7ffff42e1700 (LWP 2350)]
[New Thread 0x7ffff3ae0700 (LWP 2351)]
[Thread 0x7ffff42e1700 (LWP 2350) exited]
[New Thread 0x7ffff32df700 (LWP 2352)]
[Thread 0x7ffff3ae0700 (LWP 2351) exited]
[New Thread 0x7ffff2ade700 (LWP 2353)]
[Thread 0x7ffff32df700 (LWP 2352) exited]
[New Thread 0x7ffff22dd700 (LWP 2354)]
[Thread 0x7ffff2ade700 (LWP 2353) exited]
[New Thread 0x7ffff1adc700 (LWP 2355)]
[Thread 0x7ffff22dd700 (LWP 2354) exited]
[New Thread 0x7ffff12db700 (LWP 2356)]
[Thread 0x7ffff1adc700 (LWP 2355) exited]
[New Thread 0x7ffff0ada700 (LWP 2357)]
[Thread 0x7ffff12db700 (LWP 2356) exited]
[Thread 0x7ffff0ada700 (LWP 2357) exited]
[New Thread 0x7ffff0ada700 (LWP 2360)]
[New Thread 0x7ffff12db700 (LWP 2361)]
[Thread 0x7ffff12db700 (LWP 2361) exited]
[New Thread 0x7ffff12db700 (LWP 2362)]
[Thread 0x7ffff0ada700 (LWP 2360) exited]
[New Thread 0x7ffff1adc700 (LWP 2364)]
[New Thread 0x7ffff22dd700 (LWP 2365)]
[New Thread 0x7ffff3cb8700 (LWP 2366)]
[New Thread 0x7ffff34b7700 (LWP 2367)]
[New Thread 0x7ffff2cb6700 (LWP 2368)]
[New Thread 0x7fffe3fff700 (LWP 2369)]
[Thread 0x7ffff2cb6700 (LWP 2368) exited]
[New Thread 0x7ffff2cb6700 (LWP 2370)]
[New Thread 0x7fffe37fe700 (LWP 9331)]
[Thread 0x7fffe37fe700 (LWP 9331) exited]

Thread 13 "stratum0" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff12db700 (LWP 2362)]
0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#0  0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#1  0x00007ffff757319c in curl_easy_recv () from /usr/lib64/libcurl-gnutls.so.4
#2  0x0000000000437acb in clear_sock (pool=pool@entry=0x6971e0) at util.c:1837
#3  0x000000000043c7c0 in recv_line (pool=pool@entry=0x6971e0) at util.c:1937
#4  0x000000000042ce13 in stratum_thread (userdata=0x6971e0) at miner.c:9657
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7ffff2cb6700 (LWP 2370)):
#0  0x00007ffff711facd in read () from /lib64/libpthread.so.0
#1  0x00007ffff6eecaaf in _nc_wgetch () from /usr/lib64/libncurses.so.5
#2  0x00007ffff6eed426 in wgetch () from /usr/lib64/libncurses.so.5
#3  0x00000000004117f3 in __real_getch () at ./miner.h:206
#4  my_cancellable_getch () at miner.c:3787
#5  0x00000000004328f5 in input_thread (userdata=<optimized out>) at miner.c:8895
#6  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#7  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7fffe3fff700 (LWP 2369)):
#0  0x00007ffff64cd2a3 in epoll_wait () from /lib64/libc.so.6
#1  0x00000000004172f9 in hotplug_thread (p=<optimized out>) at miner.c:13087
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7ffff34b7700 (LWP 2367)):
#0  0x00007ffff6497c6d in nanosleep () from /lib64/libc.so.6
#1  0x00007ffff6497baa in sleep () from /lib64/libc.so.6
#2  0x0000000000422bb2 in watchdog_thread (userdata=<optimized out>) at miner.c:11609
#3  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#4  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7ffff3cb8700 (LWP 2366)):
#0  0x00007ffff712019d in nanosleep () from /lib64/libpthread.so.0
#1  0x0000000000435f75 in _cgsleep_us_r_nanosleep (tv_start=<optimized out>, us=<optimized out>) at util.c:1474
#2  0x0000000000439cf3 in cgsleep_ms_r (ms=30000, tv_start=0x7ffff3cb6ea0) at util.c:1457
#3  cgsleep_ms (ms=ms@entry=30000) at util.c:1483
#4  0x000000000042b8c5 in watchpool_thread (userdata=<optimized out>) at miner.c:11461
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7ffff22dd700 (LWP 2365)):
#0  0x00007ffff64c3f63 in select () from /lib64/libc.so.6
#1  0x000000000042780a in submit_work_thread (userdata=<optimized out>) at miner.c:6976
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7ffff1adc700 (LWP 2364)):
#0  0x00007ffff711facd in read () from /lib64/libpthread.so.0
#1  0x0000000000451d8c in read (__nbytes=8, __buf=0x7ffff1ad9dd0, __fd=13) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  _serial_read (fd=fd@entry=13, buf=buf@entry=0x7ffff1ad9dd0 "<\020\377\032\t'V\024`\f", bufsiz=bufsiz@entry=8,
    eol=eol@entry=0x0) at lowl-vcom.c:1239
#3  0x0000000000455042 in futurebit_scanhash (thr=0x6bbc10, work=0x6bb330, max_nonce=<optimized out>) at driver-futurebit.c:650
#4  0x0000000000433d3f in minerloop_scanhash (mythr=0x6bbc10) at deviceapi.c:274
#5  0x0000000000434eb2 in miner_thread (userdata=0x6bbc10) at deviceapi.c:772
#6  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#7  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7ffff12db700 (LWP 2362)):
#0  0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#1  0x00007ffff757319c in curl_easy_recv () from /usr/lib64/libcurl-gnutls.so.4
#2  0x0000000000437acb in clear_sock (pool=pool@entry=0x6971e0) at util.c:1837
#3  0x000000000043c7c0 in recv_line (pool=pool@entry=0x6971e0) at util.c:1937
#4  0x000000000042ce13 in stratum_thread (userdata=0x6971e0) at miner.c:9657
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ffff4ae2700 (LWP 2349)):
#0  0x00007ffff64c18fd in poll () from /lib64/libc.so.6
#1  0x00007ffff7fb5fc1 in ?? () from /lib64/libusb-1.0.so.0
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ffff7f9ab40 (LWP 2345)):
#0  0x00007ffff711b7f6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x0000000000408a4e in main (argc=1, argv=<optimized out>) at miner.c:13859


Could be an issue with gentoo specific libraries that bfgminer relies on. Since this is a linux machine its easy to build the binaries...I would just do a custom compile on your system and see if that resolves the issue.

Project Apollo: A Pod Miner Designed for the Home https://bitcointalk.org/index.php?topic=4974036
FutureBit Moonlander 2 USB Scrypt Stick Miner: https://bitcointalk.org/index.php?topic=2125643.0
LTC:LX5vpxrQE4eLRLPobKwZhw2comkKFCh3p4 - BTC:14w9Lea6kdVzspJk8TQRe7qSYu9LhzJJsh
doroboNeko
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
May 08, 2018, 07:25:00 PM
 #1557

Hi. I have downloaded the software specific to the miner and it run fine on a Debian machine. Then i moved the miner to another machine that has Gentoo and bfgminer ran fine for like a day or two and then does segmentation fault. It has happened very consistently so i ran it through dbg to get log. I don't know if there is another place where i can put this or if there is other way to get more debugging info.
Code:
Starting program: /home/user/bfgminer_5.4.2-futurebit2_linux_x86_64/bfgminer --scrypt -o stratum+tcp://hub.miningpoolhub.com:20523/\#skipcbcheck -u userName.minerName -p p -d 128 -S ALL --set MLD:clock=796
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff4ae2700 (LWP 2349)]
[New Thread 0x7ffff42e1700 (LWP 2350)]
[New Thread 0x7ffff3ae0700 (LWP 2351)]
[Thread 0x7ffff42e1700 (LWP 2350) exited]
[New Thread 0x7ffff32df700 (LWP 2352)]
[Thread 0x7ffff3ae0700 (LWP 2351) exited]
[New Thread 0x7ffff2ade700 (LWP 2353)]
[Thread 0x7ffff32df700 (LWP 2352) exited]
[New Thread 0x7ffff22dd700 (LWP 2354)]
[Thread 0x7ffff2ade700 (LWP 2353) exited]
[New Thread 0x7ffff1adc700 (LWP 2355)]
[Thread 0x7ffff22dd700 (LWP 2354) exited]
[New Thread 0x7ffff12db700 (LWP 2356)]
[Thread 0x7ffff1adc700 (LWP 2355) exited]
[New Thread 0x7ffff0ada700 (LWP 2357)]
[Thread 0x7ffff12db700 (LWP 2356) exited]
[Thread 0x7ffff0ada700 (LWP 2357) exited]
[New Thread 0x7ffff0ada700 (LWP 2360)]
[New Thread 0x7ffff12db700 (LWP 2361)]
[Thread 0x7ffff12db700 (LWP 2361) exited]
[New Thread 0x7ffff12db700 (LWP 2362)]
[Thread 0x7ffff0ada700 (LWP 2360) exited]
[New Thread 0x7ffff1adc700 (LWP 2364)]
[New Thread 0x7ffff22dd700 (LWP 2365)]
[New Thread 0x7ffff3cb8700 (LWP 2366)]
[New Thread 0x7ffff34b7700 (LWP 2367)]
[New Thread 0x7ffff2cb6700 (LWP 2368)]
[New Thread 0x7fffe3fff700 (LWP 2369)]
[Thread 0x7ffff2cb6700 (LWP 2368) exited]
[New Thread 0x7ffff2cb6700 (LWP 2370)]
[New Thread 0x7fffe37fe700 (LWP 9331)]
[Thread 0x7fffe37fe700 (LWP 9331) exited]

Thread 13 "stratum0" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff12db700 (LWP 2362)]
0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#0  0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#1  0x00007ffff757319c in curl_easy_recv () from /usr/lib64/libcurl-gnutls.so.4
#2  0x0000000000437acb in clear_sock (pool=pool@entry=0x6971e0) at util.c:1837
#3  0x000000000043c7c0 in recv_line (pool=pool@entry=0x6971e0) at util.c:1937
#4  0x000000000042ce13 in stratum_thread (userdata=0x6971e0) at miner.c:9657
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7ffff2cb6700 (LWP 2370)):
#0  0x00007ffff711facd in read () from /lib64/libpthread.so.0
#1  0x00007ffff6eecaaf in _nc_wgetch () from /usr/lib64/libncurses.so.5
#2  0x00007ffff6eed426 in wgetch () from /usr/lib64/libncurses.so.5
#3  0x00000000004117f3 in __real_getch () at ./miner.h:206
#4  my_cancellable_getch () at miner.c:3787
#5  0x00000000004328f5 in input_thread (userdata=<optimized out>) at miner.c:8895
#6  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#7  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7fffe3fff700 (LWP 2369)):
#0  0x00007ffff64cd2a3 in epoll_wait () from /lib64/libc.so.6
#1  0x00000000004172f9 in hotplug_thread (p=<optimized out>) at miner.c:13087
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7ffff34b7700 (LWP 2367)):
#0  0x00007ffff6497c6d in nanosleep () from /lib64/libc.so.6
#1  0x00007ffff6497baa in sleep () from /lib64/libc.so.6
#2  0x0000000000422bb2 in watchdog_thread (userdata=<optimized out>) at miner.c:11609
#3  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#4  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7ffff3cb8700 (LWP 2366)):
#0  0x00007ffff712019d in nanosleep () from /lib64/libpthread.so.0
#1  0x0000000000435f75 in _cgsleep_us_r_nanosleep (tv_start=<optimized out>, us=<optimized out>) at util.c:1474
#2  0x0000000000439cf3 in cgsleep_ms_r (ms=30000, tv_start=0x7ffff3cb6ea0) at util.c:1457
#3  cgsleep_ms (ms=ms@entry=30000) at util.c:1483
#4  0x000000000042b8c5 in watchpool_thread (userdata=<optimized out>) at miner.c:11461
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7ffff22dd700 (LWP 2365)):
#0  0x00007ffff64c3f63 in select () from /lib64/libc.so.6
#1  0x000000000042780a in submit_work_thread (userdata=<optimized out>) at miner.c:6976
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7ffff1adc700 (LWP 2364)):
#0  0x00007ffff711facd in read () from /lib64/libpthread.so.0
#1  0x0000000000451d8c in read (__nbytes=8, __buf=0x7ffff1ad9dd0, __fd=13) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  _serial_read (fd=fd@entry=13, buf=buf@entry=0x7ffff1ad9dd0 "<\020\377\032\t'V\024`\f", bufsiz=bufsiz@entry=8,
    eol=eol@entry=0x0) at lowl-vcom.c:1239
#3  0x0000000000455042 in futurebit_scanhash (thr=0x6bbc10, work=0x6bb330, max_nonce=<optimized out>) at driver-futurebit.c:650
#4  0x0000000000433d3f in minerloop_scanhash (mythr=0x6bbc10) at deviceapi.c:274
#5  0x0000000000434eb2 in miner_thread (userdata=0x6bbc10) at deviceapi.c:772
#6  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#7  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7ffff12db700 (LWP 2362)):
#0  0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#1  0x00007ffff757319c in curl_easy_recv () from /usr/lib64/libcurl-gnutls.so.4
#2  0x0000000000437acb in clear_sock (pool=pool@entry=0x6971e0) at util.c:1837
#3  0x000000000043c7c0 in recv_line (pool=pool@entry=0x6971e0) at util.c:1937
#4  0x000000000042ce13 in stratum_thread (userdata=0x6971e0) at miner.c:9657
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ffff4ae2700 (LWP 2349)):
#0  0x00007ffff64c18fd in poll () from /lib64/libc.so.6
#1  0x00007ffff7fb5fc1 in ?? () from /lib64/libusb-1.0.so.0
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ffff7f9ab40 (LWP 2345)):
#0  0x00007ffff711b7f6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x0000000000408a4e in main (argc=1, argv=<optimized out>) at miner.c:13859


Could be an issue with gentoo specific libraries that bfgminer relies on. Since this is a linux machine its easy to build the binaries...I would just do a custom compile on your system and see if that resolves the issue.

Do i need to build with a specific config or do just clone your git and build with all options?
jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
May 08, 2018, 07:36:51 PM
 #1558

git clone https://github.com/jstefanop/bfgminer.git ./futurebit
cd futurebit
git checkout futurebit2_driver
./autogen.sh
./configure --disable-other-drivers --enable-scrypt --enable-futurebit
make


should do it if you have all the right dependencies installed(check the readme for those).

Project Apollo: A Pod Miner Designed for the Home https://bitcointalk.org/index.php?topic=4974036
FutureBit Moonlander 2 USB Scrypt Stick Miner: https://bitcointalk.org/index.php?topic=2125643.0
LTC:LX5vpxrQE4eLRLPobKwZhw2comkKFCh3p4 - BTC:14w9Lea6kdVzspJk8TQRe7qSYu9LhzJJsh
doroboNeko
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
May 08, 2018, 08:49:01 PM
 #1559

git clone https://github.com/jstefanop/bfgminer.git ./futurebit
cd futurebit
git checkout futurebit2_driver
./autogen.sh
./configure --disable-other-drivers --enable-scrypt --enable-futurebit
make


should do it if you have all the right dependencies installed(check the readme for those).

okay. just built and is running now although it got lots of warnings when building. i'll let you know if i have a problem in a day or two. Thanks for the help  Smiley
nuanicaj
Member
**
Offline Offline

Activity: 178
Merit: 12


View Profile
May 08, 2018, 09:16:00 PM
 #1560



You should see 5.4.2-38 at the top if your running the latest version.
[/quote]


I got 25 units running.. 

LXGUz...GMxGD
Pool
145M / 0.000%
105M / 0.000%
97.7M / 0.071%
87.9M / 0.193%
73.3M / 0.268%
34535.96202
Pages: « 1 ... 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 [78] 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!