As I mentioned I have a controller and 3 standards running (one on each rack) however I moved one around and I still have the hashboard listed as inactive under it.
Any ideas?
Thanks in advance.
EDIT:
Disregard it appears to have resolved itself!
Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 63. (Read 48695 times)
June 20, 2022, 09:38:26 AM
Does anyone know how to remove one of the hashboards from the GUI?
As I mentioned I have a controller and 3 standards running (one on each rack) however I moved one around and I still have the hashboard listed as inactive under it.
Any ideas?
Thanks in advance.
EDIT:
Disregard it appears to have resolved itself!
As I mentioned I have a controller and 3 standards running (one on each rack) however I moved one around and I still have the hashboard listed as inactive under it.
Any ideas?
Thanks in advance.
EDIT:
Disregard it appears to have resolved itself!
June 18, 2022, 07:39:15 PM
Since Batch 4 is being released, is there going to be an updated firmware and will lightning node be added?
I'm working on a 'community OS' for this device which has Lightning and everything you'd want in a full node, there's a guide right here. However I have build issues with latest nodejs for the web GUI. If that's not important for you, you can follow the guide; it even keeps the blockchain download. If you install it on a secondary microSD, you can even switch back to the one Futurebit provided you if there are any issues.This is awesome; following it with interest! Thank you
Thank you very much in advance for doing that, I think a lot of us would appreciate it.
When will be able to run a lightning node and how would i connect my storage wallet to my node?
FYI; the guide is online and I walked through it a second time, following line by line & it works except of the web GUI install. I will take another look at it, but right now discourage installing it as it requires an outdated version of nodeJS.
June 14, 2022, 09:52:24 PM
Finally have all 16 online! 
Each "workername" has a "Full" version with 3 Standards attached!
85% power and 60 Frequency!
"workername": "x.ApolloBTC1",
"hashrate1m": "13T",
"hashrate5m": "13T",
"hashrate1hr": "13T",
"hashrate1d": "12.9T",
"hashrate7d": "6.08T",
"lastshare": 1655261006,
"shares": 1150554964,
"bestshare": 1067318666.263625,
"bestever": 1067318666
},
{
"workername": "x.ApolloBTC2",
"hashrate1m": "13.1T",
"hashrate5m": "13.8T",
"hashrate1hr": "13.2T",
"hashrate1d": "13.1T",
"hashrate7d": "6.13T",
"lastshare": 1655261008,
"shares": 1160196367,
"bestshare": 5705086819.772847,
"bestever": 5705086819
},
{
"workername": "x.ApolloBTC3",
"hashrate1m": "15T",
"hashrate5m": "13.9T",
"hashrate1hr": "13.2T",
"hashrate1d": "13T",
"hashrate7d": "6.09T",
"lastshare": 1655261007,
"shares": 1149377795,
"bestshare": 1561958236.972086,
"bestever": 1561958236
},
{
"workername": "x.ApolloBTC4",
"hashrate1m": "14T",
"hashrate5m": "13.2T",
"hashrate1hr": "12.3T",
"hashrate1d": "6.96T",
"hashrate7d": "3.09T",
"lastshare": 1655261008,
"shares": 581432584,
"bestshare": 2545683025.957528,
"bestever": 2545683025
Each "workername" has a "Full" version with 3 Standards attached!
85% power and 60 Frequency!
"workername": "x.ApolloBTC1",
"hashrate1m": "13T",
"hashrate5m": "13T",
"hashrate1hr": "13T",
"hashrate1d": "12.9T",
"hashrate7d": "6.08T",
"lastshare": 1655261006,
"shares": 1150554964,
"bestshare": 1067318666.263625,
"bestever": 1067318666
},
{
"workername": "x.ApolloBTC2",
"hashrate1m": "13.1T",
"hashrate5m": "13.8T",
"hashrate1hr": "13.2T",
"hashrate1d": "13.1T",
"hashrate7d": "6.13T",
"lastshare": 1655261008,
"shares": 1160196367,
"bestshare": 5705086819.772847,
"bestever": 5705086819
},
{
"workername": "x.ApolloBTC3",
"hashrate1m": "15T",
"hashrate5m": "13.9T",
"hashrate1hr": "13.2T",
"hashrate1d": "13T",
"hashrate7d": "6.09T",
"lastshare": 1655261007,
"shares": 1149377795,
"bestshare": 1561958236.972086,
"bestever": 1561958236
},
{
"workername": "x.ApolloBTC4",
"hashrate1m": "14T",
"hashrate5m": "13.2T",
"hashrate1hr": "12.3T",
"hashrate1d": "6.96T",
"hashrate7d": "3.09T",
"lastshare": 1655261008,
"shares": 581432584,
"bestshare": 2545683025.957528,
"bestever": 2545683025
June 13, 2022, 07:00:34 PM
~snip~
Nothing is working, though all lights seem to be on whenpowered. not even hooking up orange pi as if i wanted to use it with ubuntu. I fear its the controller. Looking for options?
Can I send it in for service?
Nothing is working, though all lights seem to be on whenpowered. not even hooking up orange pi as if i wanted to use it with ubuntu. I fear its the controller. Looking for options?
Can I send it in for service?
You will probably save time and money if you make sure the miner itself is working by connecting it with a USB cable to any PC or a Raspberry Pi. Then just execute the binary with your settings and see if it works.
If the miner doesn't work then yeah, you might need to send it all back. But if the miner works, then the rest can probably be solved with a new image, or just some remote troubleshooting. Or you can just use your PC anyway.
Hooking up via usb cable to a pc computer/ Linux too, works with binaries. Prefer the controller setup. Orange Pi is bad
......the end............
June 13, 2022, 06:04:28 PM
As long as Bitcoin Core is stopped entirely (the systemd service), you can just copy the /mount/nvme/Bitcoin folder with something like rsync. Then modify the service / Bitcoin config file to point to the new drive and start the service back up.
This may be more accessible / more practical than a whole drive clone (e.g. in case you don't want certain other data that was also on the drive or something like that).
It's just important that Bitcoin Core isn't running when you start the copy, because if there's a single 'unsaved change' it will reindex the whole drive (been there, done that).
This may be more accessible / more practical than a whole drive clone (e.g. in case you don't want certain other data that was also on the drive or something like that).
It's just important that Bitcoin Core isn't running when you start the copy, because if there's a single 'unsaved change' it will reindex the whole drive (been there, done that).
June 13, 2022, 04:03:02 PM
I have the complete controller with a 512 GB memory. Can I just swap that out with a 1TB card without any problems? Can someone suggest which one/type to use?
Thanks in advance!
Thanks in advance!
I did it and is was not that easy. I cloned it then the 1tb was cut off at 512gb so I expanded the partition to 900gb leaving 100gb empty , It should be good for at least 3 -4 years
I used a crucial since my gear came with a crucial.
https://www.amazon.com/Crucial-NAND-NVMe-PCIe-2400MB/dp/B089DNM8LR/ref=sxts_rp_s_1_0?
$85 at amazon
or 2tb for 170
https://www.amazon.com/Crucial-NAND-NVMe-PCIe-2400MB/dp/B08GVDNTGJ/ref=sxts_rp_s_1_0?th=1
You dont need to clone it. Just swap out the SSD then press the format button in settings section of the UI.
I had already downloaded entire block chain took 3 days. So I did not want to start from scratch cloning was under 2 hours time.
gear has worked great since late may of 2021
June 13, 2022, 03:27:50 PM
I have the complete controller with a 512 GB memory. Can I just swap that out with a 1TB card without any problems? Can someone suggest which one/type to use?
Thanks in advance!
Thanks in advance!
I did it and is was not that easy. I cloned it then the 1tb was cut off at 512gb so I expanded the partition to 900gb leaving 100gb empty , It should be good for at least 3 -4 years
I used a crucial since my gear came with a crucial.
https://www.amazon.com/Crucial-NAND-NVMe-PCIe-2400MB/dp/B089DNM8LR/ref=sxts_rp_s_1_0?
$85 at amazon
or 2tb for 170
https://www.amazon.com/Crucial-NAND-NVMe-PCIe-2400MB/dp/B08GVDNTGJ/ref=sxts_rp_s_1_0?th=1
You dont need to clone it. Just swap out the SSD then press the format button in settings section of the UI.
June 13, 2022, 10:46:15 AM
I have the complete controller with a 512 GB memory. Can I just swap that out with a 1TB card without any problems? Can someone suggest which one/type to use?
Thanks in advance!
Thanks in advance!
I did it and is was not that easy. I cloned it then the 1tb was cut off at 512gb so I expanded the partition to 900gb leaving 100gb empty , It should be good for at least 3 -4 years
I used a crucial since my gear came with a crucial.
https://www.amazon.com/Crucial-NAND-NVMe-PCIe-2400MB/dp/B089DNM8LR/ref=sxts_rp_s_1_0?
$85 at amazon
or 2tb for 170
https://www.amazon.com/Crucial-NAND-NVMe-PCIe-2400MB/dp/B08GVDNTGJ/ref=sxts_rp_s_1_0?th=1
June 13, 2022, 09:44:01 AM
I have the complete controller with a 512 GB memory. Can I just swap that out with a 1TB card without any problems? Can someone suggest which one/type to use?
Thanks in advance!
Thanks in advance!
June 13, 2022, 03:00:42 AM
Since Batch 4 is being released, is there going to be an updated firmware and will lightning node be added?
I'm working on a 'community OS' for this device which has Lightning and everything you'd want in a full node, there's a guide right here. However I have build issues with latest nodejs for the web GUI. If that's not important for you, you can follow the guide; it even keeps the blockchain download. If you install it on a secondary microSD, you can even switch back to the one Futurebit provided you if there are any issues.This is awesome; following it with interest! Thank you
June 12, 2022, 07:35:32 PM
Since Batch 4 is being released, is there going to be an updated firmware and will lightning node be added?
I'm working on a 'community OS' for this device which has Lightning and everything you'd want in a full node, there's a guide right here. However I have build issues with latest nodejs for the web GUI. If that's not important for you, you can follow the guide; it even keeps the blockchain download. If you install it on a secondary microSD, you can even switch back to the one Futurebit provided you if there are any issues. June 12, 2022, 01:44:46 PM
I think I need to repeat my question at the moment my units run with Raspberry PI4 and I don't like it because of more cables flying around.
Can I replace Orange Pi4 with Orange PI4 LTS and flash it with publicly available Apollo BTC image? Will it work?
Nope, it won't work. It's compiled for a different chip. at the moment my units run with Raspberry PI4 and I don't like it because of more cables flying around.Can I replace Orange Pi4 with Orange PI4 LTS and flash it with publicly available Apollo BTC image? Will it work?
What kind of PI board is installed in last batch of full units? Orange PI4 seems to be not available anymore.
Orange Pi 4. At least in batch 3, since that's what I have. I also don't think they changed it in batch 4, otherwise there would be binaries available for a new SBC in the mega folder.Apollo BTC SD Card Image/OS Download and Install
Folder for all Apollo BTC Image Releases: https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_Q
[...]
Folder for all Apollo BTC Image Releases: https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_Q
[...]
Batch 4 will use our custom version of the LTS board, so we will be providing an image that should also work with the generic LTS board as well.
June 10, 2022, 10:38:51 PM
I think I need to repeat my question at the moment my units run with Raspberry PI4 and I don't like it because of more cables flying around.
Can I replace Orange Pi4 with Orange PI4 LTS and flash it with publicly available Apollo BTC image? Will it work?
Nope, it won't work. It's compiled for a different chip. at the moment my units run with Raspberry PI4 and I don't like it because of more cables flying around.Can I replace Orange Pi4 with Orange PI4 LTS and flash it with publicly available Apollo BTC image? Will it work?
What kind of PI board is installed in last batch of full units? Orange PI4 seems to be not available anymore.
Orange Pi 4. At least in batch 3, since that's what I have. I also don't think they changed it in batch 4, otherwise there would be binaries available for a new SBC in the mega folder.Apollo BTC SD Card Image/OS Download and Install
Folder for all Apollo BTC Image Releases: https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_Q
[...]
Folder for all Apollo BTC Image Releases: https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_Q
[...]
Batch 4 will use our custom version of the LTS board, so we will be providing an image that should also work with the generic LTS board as well.
June 08, 2022, 06:53:35 PM
I think I need to repeat my question at the moment my units run with Raspberry PI4 and I don't like it because of more cables flying around.
Can I replace Orange Pi4 with Orange PI4 LTS and flash it with publicly available Apollo BTC image? Will it work?
Nope, it won't work. It's compiled for a different chip. at the moment my units run with Raspberry PI4 and I don't like it because of more cables flying around.Can I replace Orange Pi4 with Orange PI4 LTS and flash it with publicly available Apollo BTC image? Will it work?
What kind of PI board is installed in last batch of full units? Orange PI4 seems to be not available anymore.
Orange Pi 4. At least in batch 3, since that's what I have. I also don't think they changed it in batch 4, otherwise there would be binaries available for a new SBC in the mega folder.Apollo BTC SD Card Image/OS Download and Install
Folder for all Apollo BTC Image Releases: https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_Q
[...]
Folder for all Apollo BTC Image Releases: https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_Q
[...]
June 08, 2022, 12:23:12 PM
I think I need to repeat my question at the moment my units run with Raspberry PI4 and I don't like it because of more cables flying around.
Can I replace Orange Pi4 with Orange PI4 LTS and flash it with publicly available Apollo BTC image? Will it work?
What kind of PI board is installed in last batch of full units? Orange PI4 seems to be not available anymore.
at the moment my units run with Raspberry PI4 and I don't like it because of more cables flying around.Can I replace Orange Pi4 with Orange PI4 LTS and flash it with publicly available Apollo BTC image? Will it work?
What kind of PI board is installed in last batch of full units? Orange PI4 seems to be not available anymore.
June 07, 2022, 12:23:28 PM
It would be great if you could point out what changed between stock DTS and your DTS; I can't yet figure it out.
Decompile the two DTS and do a compare if you really want to know
June 07, 2022, 12:15:41 PM
Do you mean changing the port number in the binary? Or just in the command-line argument?
Just change the port number in the command line argument.
It would be great if you could point out what changed between stock DTS and your DTS; I can't yet figure it out.
Decompile the two DTS and do a compare if you really want to know
June 07, 2022, 11:18:52 AM
You have to use our custom DTS, the UART port we use is not activated by default on Armbian.
Thanks a lot; in fact, I just tried it and it works. I'd prefer to activate it myself, but had no success with that.If your doing custom stuff you can easily use any active UART port on any board/sbc. All you have to do is change the /dev/ttySx port number the app uses to start the hashboard via internal UART (its in /opt/apolloapi/backend/apollo-miner files).
Do you mean changing the port number in the binary? Or just in the command-line argument?FYI below is the board pinout for anyone that wants to tinker with rpi or any other SBC (Pin #1 is towards the bottom of the board). You can ignore the BOOT pin, all you have to do is reset the board using the RES pin (low then high), and start the miner program. The 5v pin can provide up to 15 watts of power so it can power most SBCs boards internally.
Great, that's very helpful thank you!It would be great if you could point out what changed between stock DTS and your DTS; I can't yet figure it out.
June 07, 2022, 11:16:15 AM
Hey @jstefanop and @crypto_curious, I'm trying to mount the NVMe from a custom Linux install on another microSD card and it just doesn't show up in lsblk or elsewhere.
Does the 'Futurebit OS' have a special driver included or anything like that to recognize the small daughterboard which connects the NVMe SSD to the SBC?
Edit: It seems an OpenSUSE / JeOS specific issue. With ARMbian for Orange Pi 4 it works nicely.
But if there's any information you can share about accessing the hashboard through the internal connection, I'd really appreciate it!
I can see on 'Futurebit OS', it's activated, while on my Armbian SD card it's not.
I need stock Armbian to recognize ttyS1...
Edit 2: I changed a few things as I noticed you swapped uart1 and uart2 in your Futurebit OS.
Does the 'Futurebit OS' have a special driver included or anything like that to recognize the small daughterboard which connects the NVMe SSD to the SBC?
Edit: It seems an OpenSUSE / JeOS specific issue. With ARMbian for Orange Pi 4 it works nicely.
But if there's any information you can share about accessing the hashboard through the internal connection, I'd really appreciate it!
Yea you could technically run the whole UI off a rasberry pi (or any ARM SBC with a UART port for that matter), or simply run it off the USB port if you dont want to deal with setting up the internal UART. I should probably post the board connector pinout for anyone that wants to do this. Will probably release a pi image at some point as well (or at least update the installer so its a one step RPI installation).
Oh, it's internal UART, alright. Would it be possible to know how to 'activate' it?I can see on 'Futurebit OS', it's activated, while on my Armbian SD card it's not.
Code:
root@futurebit-btc:/boot/dtb/rockchip/overlay# dmesg | grep tty
[ 0.000000] Kernel command line: root=UUID=98eceb4e-f6db-4229-bee6-b02137879d0c rootwait rootfstype=ext4 bootsplash.bootfile=bootsplash.armbian console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=37857158-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 0.001497] printk: console [tty1] enabled
[ 2.729455] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 47, base_baud = 1500000) is a 16550A
[ 2.729630] serial serial0: tty port ttyS0 registered
[ 2.730549] ff1a0000.serial: ttyS1 at MMIO 0xff1a0000 (irq = 48, base_baud = 1500000) is a 16550A
[ 2.731757] ff370000.serial: ttyS4 at MMIO 0xff370000 (irq = 50, base_baud = 1500000) is a 16550A
[ 0.000000] Kernel command line: root=UUID=98eceb4e-f6db-4229-bee6-b02137879d0c rootwait rootfstype=ext4 bootsplash.bootfile=bootsplash.armbian console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=37857158-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 0.001497] printk: console [tty1] enabled
[ 2.729455] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 47, base_baud = 1500000) is a 16550A
[ 2.729630] serial serial0: tty port ttyS0 registered
[ 2.730549] ff1a0000.serial: ttyS1 at MMIO 0xff1a0000 (irq = 48, base_baud = 1500000) is a 16550A
[ 2.731757] ff370000.serial: ttyS4 at MMIO 0xff370000 (irq = 50, base_baud = 1500000) is a 16550A
I need stock Armbian to recognize ttyS1...
Edit 2: I changed a few things as I noticed you swapped uart1 and uart2 in your Futurebit OS.
Code:
sudo dtc -I dtb -O dts /boot/dtb/rockchip/rk3399-orangepi-4.dtb -o /boot/dtb/rockchip/rk3399-orangepi-4.dts
sudo vim /boot/dtb/rockchip/rk3399-orangepi-4.dts
sudo dtc -I dts -O dtb /boot/dtb/rockchip/rk3399-orangepi-4.dts -o /boot/dtb/rockchip/rk3399-orangepi-4.dtb
Now, a ttyS1 device shows up, but I'm not sure everything's correct. The miner binary doesn't recognize it yet. The IRQ is probably wrong (wrong pin).sudo vim /boot/dtb/rockchip/rk3399-orangepi-4.dts
sudo dtc -I dts -O dtb /boot/dtb/rockchip/rk3399-orangepi-4.dts -o /boot/dtb/rockchip/rk3399-orangepi-4.dtb
Code:
:% dmesg | grep tty
[ 0.000000] Kernel command line: root=UUID=3398764f-7f34-4184-b0c2-c76e0b416579 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=c257b905-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 0.002018] printk: console [tty1] enabled
[ 1.530133] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 44, base_baud = 1500000) is a 16550A
[ 1.530315] serial serial0: tty port ttyS0 registered
[ 1.531269] ff1a0000.serial: ttyS1 at MMIO 0xff1a0000 (irq = 45, base_baud = 1500000) is a 16550A
[ 6.630819] systemd[1]: Created slice system-getty.slice.
[ 6.635376] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 8.463791] systemd[1]: Found device /dev/ttyS2.
[ 0.000000] Kernel command line: root=UUID=3398764f-7f34-4184-b0c2-c76e0b416579 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=c257b905-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 0.002018] printk: console [tty1] enabled
[ 1.530133] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 44, base_baud = 1500000) is a 16550A
[ 1.530315] serial serial0: tty port ttyS0 registered
[ 1.531269] ff1a0000.serial: ttyS1 at MMIO 0xff1a0000 (irq = 45, base_baud = 1500000) is a 16550A
[ 6.630819] systemd[1]: Created slice system-getty.slice.
[ 6.635376] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 8.463791] systemd[1]: Found device /dev/ttyS2.
You have to use our custom DTS, the UART port we use is not activated by default on Armbian.
If your doing custom stuff you can easily use any active UART port on any board/sbc. All you have to do is change the /dev/ttySx port number the app uses to start the hashboard via internal UART (its in /opt/apolloapi/backend/apollo-miner files).
FYI below is the board pinout for anyone that wants to tinker with rpi or any other SBC (Pin #1 is towards the bottom of the board). You can ignore the BOOT pin, all you have to do is reset the board using the RES pin (low then high), and start the miner program. The 5v pin can provide up to 15 watts of power so it can power most SBCs boards internally.
June 06, 2022, 11:35:27 AM
Hey @jstefanop and @crypto_curious, I'm trying to mount the NVMe from a custom Linux install on another microSD card and it just doesn't show up in lsblk or elsewhere.
Does the 'Futurebit OS' have a special driver included or anything like that to recognize the small daughterboard which connects the NVMe SSD to the SBC?
Edit: It seems an OpenSUSE / JeOS specific issue. With ARMbian for Orange Pi 4 it works nicely.
But if there's any information you can share about accessing the hashboard through the internal connection, I'd really appreciate it!
I can see on 'Futurebit OS', it's activated, while on my Armbian SD card it's not.
I need stock Armbian to recognize ttyS1...
Edit 2: I changed a few things as I noticed you swapped uart1 and uart2 in your Futurebit OS.
Does the 'Futurebit OS' have a special driver included or anything like that to recognize the small daughterboard which connects the NVMe SSD to the SBC?
Edit: It seems an OpenSUSE / JeOS specific issue. With ARMbian for Orange Pi 4 it works nicely.
But if there's any information you can share about accessing the hashboard through the internal connection, I'd really appreciate it!
Yea you could technically run the whole UI off a rasberry pi (or any ARM SBC with a UART port for that matter), or simply run it off the USB port if you dont want to deal with setting up the internal UART. I should probably post the board connector pinout for anyone that wants to do this. Will probably release a pi image at some point as well (or at least update the installer so its a one step RPI installation).
Oh, it's internal UART, alright. Would it be possible to know how to 'activate' it?I can see on 'Futurebit OS', it's activated, while on my Armbian SD card it's not.
Code:
root@futurebit-btc:/boot/dtb/rockchip/overlay# dmesg | grep tty
[ 0.000000] Kernel command line: root=UUID=98eceb4e-f6db-4229-bee6-b02137879d0c rootwait rootfstype=ext4 bootsplash.bootfile=bootsplash.armbian console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=37857158-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 0.001497] printk: console [tty1] enabled
[ 2.729455] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 47, base_baud = 1500000) is a 16550A
[ 2.729630] serial serial0: tty port ttyS0 registered
[ 2.730549] ff1a0000.serial: ttyS1 at MMIO 0xff1a0000 (irq = 48, base_baud = 1500000) is a 16550A
[ 2.731757] ff370000.serial: ttyS4 at MMIO 0xff370000 (irq = 50, base_baud = 1500000) is a 16550A
[ 0.000000] Kernel command line: root=UUID=98eceb4e-f6db-4229-bee6-b02137879d0c rootwait rootfstype=ext4 bootsplash.bootfile=bootsplash.armbian console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=37857158-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 0.001497] printk: console [tty1] enabled
[ 2.729455] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 47, base_baud = 1500000) is a 16550A
[ 2.729630] serial serial0: tty port ttyS0 registered
[ 2.730549] ff1a0000.serial: ttyS1 at MMIO 0xff1a0000 (irq = 48, base_baud = 1500000) is a 16550A
[ 2.731757] ff370000.serial: ttyS4 at MMIO 0xff370000 (irq = 50, base_baud = 1500000) is a 16550A
I need stock Armbian to recognize ttyS1...
Edit 2: I changed a few things as I noticed you swapped uart1 and uart2 in your Futurebit OS.
Code:
sudo dtc -I dtb -O dts /boot/dtb/rockchip/rk3399-orangepi-4.dtb -o /boot/dtb/rockchip/rk3399-orangepi-4.dts
sudo vim /boot/dtb/rockchip/rk3399-orangepi-4.dts
sudo dtc -I dts -O dtb /boot/dtb/rockchip/rk3399-orangepi-4.dts -o /boot/dtb/rockchip/rk3399-orangepi-4.dtb
Now, a ttyS1 device shows up, but I'm not sure everything's correct. The miner binary doesn't recognize it yet. The IRQ is probably wrong (wrong pin).sudo vim /boot/dtb/rockchip/rk3399-orangepi-4.dts
sudo dtc -I dts -O dtb /boot/dtb/rockchip/rk3399-orangepi-4.dts -o /boot/dtb/rockchip/rk3399-orangepi-4.dtb
Code:
:% dmesg | grep tty
[ 0.000000] Kernel command line: root=UUID=3398764f-7f34-4184-b0c2-c76e0b416579 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=c257b905-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 0.002018] printk: console [tty1] enabled
[ 1.530133] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 44, base_baud = 1500000) is a 16550A
[ 1.530315] serial serial0: tty port ttyS0 registered
[ 1.531269] ff1a0000.serial: ttyS1 at MMIO 0xff1a0000 (irq = 45, base_baud = 1500000) is a 16550A
[ 6.630819] systemd[1]: Created slice system-getty.slice.
[ 6.635376] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 8.463791] systemd[1]: Found device /dev/ttyS2.
[ 0.000000] Kernel command line: root=UUID=3398764f-7f34-4184-b0c2-c76e0b416579 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=c257b905-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 0.002018] printk: console [tty1] enabled
[ 1.530133] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 44, base_baud = 1500000) is a 16550A
[ 1.530315] serial serial0: tty port ttyS0 registered
[ 1.531269] ff1a0000.serial: ttyS1 at MMIO 0xff1a0000 (irq = 45, base_baud = 1500000) is a 16550A
[ 6.630819] systemd[1]: Created slice system-getty.slice.
[ 6.635376] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 8.463791] systemd[1]: Found device /dev/ttyS2.
Jump to: