Search content
Sort by
Showing 5 of 5 results by sunpower_miner
Re: Official FutureBit Apollo LTC Image and Support thread
Well, as long as they are up with blinky leds, his units make a solid job.
Fun part begins once you've got problems and re-flashing your SD won't fix it anymore.
Honestly? I am really pissed. And nope, it's not about ROI because that's not what folks using futurebit devices are after I'd say.
It's about the couldn't care less mentality of a US based one man show, I thought it's worth backing.
My Apollo batch 2 with original PSU and SD card is now for sale! Drop me a PM it you're interested. You can read above about the problems this unit shows.
Fun part begins once you've got problems and re-flashing your SD won't fix it anymore.
Honestly? I am really pissed. And nope, it's not about ROI because that's not what folks using futurebit devices are after I'd say.
It's about the couldn't care less mentality of a US based one man show, I thought it's worth backing.
My Apollo batch 2 with original PSU and SD card is now for sale! Drop me a PM it you're interested. You can read above about the problems this unit shows.
Re: Official FutureBit Apollo LTC Image and Support thread
The furturebit apollo batch 2 has become a doorstopper worth $400 USD...
developer not interested in providing support, ignoring messages.
everbody be warned, learn from my mistake!
good catch HagssFIN , classic typo. thanks anyway.
developer not interested in providing support, ignoring messages.
everbody be warned, learn from my mistake!
@sunpower_miner
The first code field in your post shows the ip address 192.168.1.222 but the second code field shows ip address 192.168.1.122 . Was there maybe some simple typo error?
The first code field in your post shows the ip address 192.168.1.222 but the second code field shows ip address 192.168.1.122 . Was there maybe some simple typo error?
good catch HagssFIN , classic typo. thanks anyway.
Re: Official FutureBit Apollo LTC Image and Support thread
Do you still have the full node drive plugged in? Make sure you remove it to be sure thats not causing the issue. That loop also sounds like it cant detect the hashboard. Make sure the controller is properly seated in its socket on the backside.
usb drive is disconnected and hasboard sitting rock solid in it's socket.
still the same behaviour. orange light comes on 4 times together with the fan and that's it.
after like 20 times trying I was lucky and managed to establish a ssh connection.
the unit reset connection on it's own. afterwards froze again and I am not able to re-connect d/t connection timed out
Code:
C:\Users\admin>ssh futurebit@192.168.1.222
ssh: connect to host 192.168.1.222 port 22: Connection timed out
C:\Users\admin>ssh futurebit@192.168.1.222 -l futurebit
futurebit@192.168.1.222's password:
_____ _ ____ _ _ _ _ _
| ___| _| |_ _ _ _ __ ___| __ )(_) |_ / \ _ __ ___ | | | ___
| |_ | | | | __| | | | '__/ _ \ _ \| | __| / _ \ | '_ \ / _ \| | |/ _ \
| _|| |_| | |_| |_| | | | __/ |_) | | |_ / ___ \| |_) | (_) | | | (_) |
|_| \__,_|\__|\__,_|_| \___|____/|_|\__| /_/ \_\ .__/ \___/|_|_|\___/
|_|
Welcome to ARMBIAN 5.70 stable Ubuntu 16.04.5 LTS 4.19.13-sunxi
System load: 1.42 0.34 0.11 Up time: 0 min
Memory usage: 12 % of 493MB IP: 192.168.1.222
CPU temp: 47°C
Usage of /: 6% of 29G
Last login: Tue Jan 29 18:11:44 2019 from 192.168.0.102
Connection reset by 192.168.1.222 port 22
C:\Users\admin>ssh futurebit@192.168.1.222 -l futurebit
futurebit@192.168.1.222's password:
ssh: connect to host 192.168.1.222 port 22: Connection timed out
C:\Users\admin>ssh futurebit@192.168.1.222 -l futurebit
futurebit@192.168.1.222's password:
_____ _ ____ _ _ _ _ _
| ___| _| |_ _ _ _ __ ___| __ )(_) |_ / \ _ __ ___ | | | ___
| |_ | | | | __| | | | '__/ _ \ _ \| | __| / _ \ | '_ \ / _ \| | |/ _ \
| _|| |_| | |_| |_| | | | __/ |_) | | |_ / ___ \| |_) | (_) | | | (_) |
|_| \__,_|\__|\__,_|_| \___|____/|_|\__| /_/ \_\ .__/ \___/|_|_|\___/
|_|
Welcome to ARMBIAN 5.70 stable Ubuntu 16.04.5 LTS 4.19.13-sunxi
System load: 1.42 0.34 0.11 Up time: 0 min
Memory usage: 12 % of 493MB IP: 192.168.1.222
CPU temp: 47°C
Usage of /: 6% of 29G
Last login: Tue Jan 29 18:11:44 2019 from 192.168.0.102
Connection reset by 192.168.1.222 port 22
C:\Users\admin>ssh futurebit@192.168.1.222 -l futurebit
futurebit@192.168.1.222's password:
Code:
C:\Users\admin>ssh futurebit@192.168.1.122 -l futurebit
ssh: connect to host 192.168.1.122 port 22: Connection timed out
ssh: connect to host 192.168.1.122 port 22: Connection timed out
what else you suggest?
been quite a painful new year so far watching LTC performance with the apollo disconnected from litecoinpool...
thankful for any help
Re: Official FutureBit Apollo LTC Image and Support thread
happy new year, hope everyone is healthy!
After 2 days and one night of trying to fix it on my own I am here now...
Because I got a serious problem with my apollo batch 2 and hope you can help me
my unit is not booting anymore.
also ssh into is not working anymore.
sometimes I am fast enough when the putty connection window opens to type in the apollos login, but when it comes to the ssh password it gives me back a 'software caused a connection or network error'.
the unit shows periodically 4 times an orange light blinking an then fan comes on very slow and then nothing again.
after around 20 seconds again 4 times orange light blinking, little fan activity and so on... it feels to me like kind of caught in a boot-loop?
I already tried re-flashing 4 different 32 GB SD cards (2 of them were fresh out of amazon package, new) with same result, the unit is not booting.The original SD card that came with the unit also not working. For PSU I am using the futurebit original that came with the full package. Flashing an old image also not working, same problem.
it all started when I was using the new fullnode image that suddenly gave me a solid red light. it was the last time I was able to see the futurebit dashboard!
how can I fix my apollo? is there a workaround to connect the unit by usb or ethernet cable to a pc and somehow become it responsive again to reflash it? Rebooting router, using different cables, all was done and nothing helped.
Been reading through every single page of this thread and what I found were dozens of comments with just 'reflash your SD card'.
well, that solved it for pretty much the most of you but unfortunately not for me...
I would be more than happy to see my unit mining again. Seriously no more need for the node functionality, because this started all my problems!
Thanks for your help
After 2 days and one night of trying to fix it on my own I am here now...
Because I got a serious problem with my apollo batch 2 and hope you can help me
my unit is not booting anymore.
also ssh into is not working anymore.
sometimes I am fast enough when the putty connection window opens to type in the apollos login, but when it comes to the ssh password it gives me back a 'software caused a connection or network error'.
the unit shows periodically 4 times an orange light blinking an then fan comes on very slow and then nothing again.
after around 20 seconds again 4 times orange light blinking, little fan activity and so on... it feels to me like kind of caught in a boot-loop?
I already tried re-flashing 4 different 32 GB SD cards (2 of them were fresh out of amazon package, new) with same result, the unit is not booting.The original SD card that came with the unit also not working. For PSU I am using the futurebit original that came with the full package. Flashing an old image also not working, same problem.
it all started when I was using the new fullnode image that suddenly gave me a solid red light. it was the last time I was able to see the futurebit dashboard!
how can I fix my apollo? is there a workaround to connect the unit by usb or ethernet cable to a pc and somehow become it responsive again to reflash it? Rebooting router, using different cables, all was done and nothing helped.
Been reading through every single page of this thread and what I found were dozens of comments with just 'reflash your SD card'.
well, that solved it for pretty much the most of you but unfortunately not for me...
I would be more than happy to see my unit mining again. Seriously no more need for the node functionality, because this started all my problems!
Thanks for your help