starting another one on different port:
reproducible with other port combinations and on both win 7 and 8
what am i doing wrong?
not an issue with prior to 3.9.0 versions of bfgminer.
Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 73. (Read 1193218 times)
January 03, 2014, 03:43:45 PM
I have an instance of bfgminer proxy running on port 8332.
starting another one on different port:
reproducible with other port combinations and on both win 7 and 8
what am i doing wrong?
not an issue with prior to 3.9.0 versions of bfgminer.
starting another one on different port:
reproducible with other port combinations and on both win 7 and 8
what am i doing wrong?
not an issue with prior to 3.9.0 versions of bfgminer.
January 03, 2014, 07:56:52 AM
My Antminers are here.
Hashing on a rPi but only at 500Mh/s
Hashing on a rPi but only at 500Mh/s
I am getting 2 gh with windows 7 and the custom cgminer build.. waiting on luke to get ant miners set for bfgminer.
At luke-jr how is you new home? nice a new home and a new year wrapped into one. good luck with it.
Ps I sent a small amount of BTC for a house warming gift.
January 03, 2014, 07:20:39 AM
My Antminers are here.
Hashing on a rPi but only at 500Mh/s
Hashing on a rPi but only at 500Mh/s
January 03, 2014, 05:12:06 AM
On the BBB one of my IceFurys (NFY0) gives lots of 'dropped nonces' errors on startup, the other (NFY1) is perfect. NFY0 eventually stabilises after about a minute and runs fine. I have nowhere near the errors listed by Nate.
As I said, I'm running Debian on the BBB with bfg compiled from source.
As I said, I'm running Debian on the BBB with bfg compiled from source.
January 03, 2014, 04:14:35 AM
Any chance bfgminer will have built-in Antminer U1 support anytime soon?
He's a working on it. Ljr just moved into a new house. So give em a few 
January 03, 2014, 12:18:27 AM
Any chance bfgminer will have built-in Antminer U1 support anytime soon?
January 02, 2014, 09:56:52 PM
Can you post backtraces for those crashes?
No worries, I will just reload/recompile "-g" on the CubeBoard2 and get back to you. It seems to have the most 'intresting' results.
Neil
January 02, 2014, 09:54:20 PM
Occasionally I get a few accepted shares first.
Very similar to what I get, I have not noticed any shares though (I have not really been looking though).
The Pi is defiantly most effected of the ARM systems, a bit understandable it being ARMv6 with a dodgy USB controller. I just tried Pidora (a Fedora Remix) with the same results as Arch and Rasperian.
Neil
January 02, 2014, 09:50:01 PM
Update on my investigations on ARM and NFY;-
Arch Linux on x86/64 bfgminer 3.9.0 = No problems, works as expected.
Arch Linux on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.
Rasberian on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.
Arch Linux on CubieBoard2 (ARMv7) bfgminer 3.9.0 = Detects, initializes, bfgminer often has to reset the NFY's because the hashrate falls below 50%, often segfaults and core dumps.
Arch Linux on BeagleBone Black (ARMv7) bfgminer 3.9.0 = Detects, initializes, occasionally segfaults and core dumps. Does not handle unplug events and a restart (of bfgminer or the ARM device) will often leave the NFY's locked.
Curious you have trouble on non-RPI platforms too...Arch Linux on x86/64 bfgminer 3.9.0 = No problems, works as expected.
Arch Linux on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.
Rasberian on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.
Arch Linux on CubieBoard2 (ARMv7) bfgminer 3.9.0 = Detects, initializes, bfgminer often has to reset the NFY's because the hashrate falls below 50%, often segfaults and core dumps.
Arch Linux on BeagleBone Black (ARMv7) bfgminer 3.9.0 = Detects, initializes, occasionally segfaults and core dumps. Does not handle unplug events and a restart (of bfgminer or the ARM device) will often leave the NFY's locked.
Can you post backtraces for those crashes?
January 02, 2014, 09:43:31 PM
Arch Linux on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.
...
Is anyone experiencing anything different? If so, can I possibly grab an image of the OS from you so I can compare/see what is different.
...
Is anyone experiencing anything different? If so, can I possibly grab an image of the OS from you so I can compare/see what is different.
This is what I get with Ice Fury along with MinePeon compiled with NanoFury support:
Code:
[2014-01-03 02:41:42] Started bfgminer 3.9.0
[2014-01-03 02:41:43] Probing for an alive pool
[2014-01-03 02:41:43] Pool 0 http://192.168.0.15:3333 alive
[2014-01-03 02:41:43] Network difficulty changed to 1.42G (10.15Ph/s)
[2014-01-03 02:41:43] Stratum from pool 0 detected new block
[2014-01-03 02:41:43] Pool 0 is hiding block contents from us
[2014-01-03 02:41:45] NFY 0: Previous nonce mismatch (4th try), recalibrating
[2014-01-03 02:41:45] mcp2210_spi_transfer: Failed to continue SPI transfer (1 bytes remaining)
[2014-01-03 02:41:47] mcp2210_spi_transfer: Failed to continue SPI transfer (59 bytes remaining)
[2014-01-03 02:41:47] NFY 0 failure, attempting to reinitialize
[2014-01-03 02:41:47] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:41:47] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:41:48] NFY 0 failure, disabling!
[2014-01-03 02:41:49] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:49] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:50] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:50] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:51] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:52] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:52] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:56] mcp2210_spi_transfer: Failed to continue SPI transfer (59 bytes remaining)
[2014-01-03 02:41:56] NFY 0 failure, disabling!
[2014-01-03 02:41:56] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:41:56] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:41:56] NFY 0 failure, disabling!
[2014-01-03 02:41:56] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:56] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:57] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:58] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:58] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:59] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:59] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:00] mcp2210_set_cfg_spi: Failed to set current SPI config
[2014-01-03 02:42:02] mcp2210_spi_transfer: Failed to continue SPI transfer (59 bytes remaining)
[2014-01-03 02:42:02] NFY 0 failure, disabling!
[2014-01-03 02:42:02] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:42:02] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:42:02] NFY 0 failure, disabling!
[2014-01-03 02:42:02] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:02] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:03] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:04] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:04] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:05] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:05] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:06] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:43] Probing for an alive pool
[2014-01-03 02:41:43] Pool 0 http://192.168.0.15:3333 alive
[2014-01-03 02:41:43] Network difficulty changed to 1.42G (10.15Ph/s)
[2014-01-03 02:41:43] Stratum from pool 0 detected new block
[2014-01-03 02:41:43] Pool 0 is hiding block contents from us
[2014-01-03 02:41:45] NFY 0: Previous nonce mismatch (4th try), recalibrating
[2014-01-03 02:41:45] mcp2210_spi_transfer: Failed to continue SPI transfer (1 bytes remaining)
[2014-01-03 02:41:47] mcp2210_spi_transfer: Failed to continue SPI transfer (59 bytes remaining)
[2014-01-03 02:41:47] NFY 0 failure, attempting to reinitialize
[2014-01-03 02:41:47] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:41:47] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:41:48] NFY 0 failure, disabling!
[2014-01-03 02:41:49] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:49] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:50] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:50] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:51] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:52] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:52] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:56] mcp2210_spi_transfer: Failed to continue SPI transfer (59 bytes remaining)
[2014-01-03 02:41:56] NFY 0 failure, disabling!
[2014-01-03 02:41:56] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:41:56] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:41:56] NFY 0 failure, disabling!
[2014-01-03 02:41:56] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:56] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:57] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:58] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:58] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:59] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:41:59] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:00] mcp2210_set_cfg_spi: Failed to set current SPI config
[2014-01-03 02:42:02] mcp2210_spi_transfer: Failed to continue SPI transfer (59 bytes remaining)
[2014-01-03 02:42:02] NFY 0 failure, disabling!
[2014-01-03 02:42:02] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:42:02] mcp2210_set_cfg_spi: Error setting current SPI config (248)
[2014-01-03 02:42:02] NFY 0 failure, disabling!
[2014-01-03 02:42:02] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:02] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:03] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:04] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:04] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:05] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:05] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-03 02:42:06] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
Occasionally I get a few accepted shares first.
January 02, 2014, 08:47:23 PM
Update on my investigations on ARM and NFY;-
Arch Linux on x86/64 bfgminer 3.9.0 = No problems, works as expected.
Arch Linux on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.
Rasberian on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.
Arch Linux on CubieBoard2 (ARMv7) bfgminer 3.9.0 = Detects, initializes, bfgminer often has to reset the NFY's because the hashrate falls below 50%, often segfaults and core dumps.
Arch Linux on BeagleBone Black (ARMv7) bfgminer 3.9.0 = Detects, initializes, occasionally segfaults and core dumps. Does not handle unplug events and a restart (of bfgminer or the ARM device) will often leave the NFY's locked.
As a note, all other hardware drivers that I can test (BFL, ICA, BPM, ZTX) work fine on all platforms.
My build scripts are;-
hidapi (the necessary library)
bfgminer
Is anyone experiencing anything different? If so, can I possibly grab an image of the OS from you so I can compare/see what is different.
Neil
Arch Linux on x86/64 bfgminer 3.9.0 = No problems, works as expected.
Arch Linux on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.
Rasberian on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.
Arch Linux on CubieBoard2 (ARMv7) bfgminer 3.9.0 = Detects, initializes, bfgminer often has to reset the NFY's because the hashrate falls below 50%, often segfaults and core dumps.
Arch Linux on BeagleBone Black (ARMv7) bfgminer 3.9.0 = Detects, initializes, occasionally segfaults and core dumps. Does not handle unplug events and a restart (of bfgminer or the ARM device) will often leave the NFY's locked.
As a note, all other hardware drivers that I can test (BFL, ICA, BPM, ZTX) work fine on all platforms.
My build scripts are;-
hidapi (the necessary library)
Code:
git clone https://github.com/signal11/hidapi
cd hidapi
./bootstrap
./configure --prefix=/
make
make install
cd ..
cd hidapi
./bootstrap
./configure --prefix=/
make
make install
cd ..
bfgminer
Code:
git clone https://github.com/luke-jr/bfgminer.git
cd bfgminer
./autogen.sh
./configure
make
make install
cd bfgminer
./autogen.sh
./configure
make
make install
Is anyone experiencing anything different? If so, can I possibly grab an image of the OS from you so I can compare/see what is different.
Neil
January 02, 2014, 04:49:01 PM
Build with;-
git clone https://github.com/signal11/hidapi
cd hidapi
./bootstrap
./configure --prefix=/
make
make install
And bfgminer will pick it up without any options, and I can confirm, the BBB will run the NFY devices fine.
Neil
I didn't even need to use the --prefix=/ part, and it all worked.
January 02, 2014, 04:40:55 PM
Finally got BFGMiner running on Debian on my BeagleBone Black. It's MUCH faster than the RaspberryPi. I'm running getwork proxy for 65GH and it's running at less than 10% CPU at full speed. The Pi can't do that for shit.
Trying USB miners later (I think I got hidapi running).
Still looking forward to getting LongPoll support.
Trying USB miners later (I think I got hidapi running).
Still looking forward to getting LongPoll support.
I've got hidalgo working on bbb with a few NFY. I remember having to compile libhidapi with --prefix=#####
Can't remember the exact location. Will check make file when I get home
Build with;-
git clone https://github.com/signal11/hidapi
cd hidapi
./bootstrap
./configure --prefix=/
make
make install
And bfgminer will pick it up without any options, and I can confirm, the BBB will run the NFY devices fine.
Neil
January 02, 2014, 04:30:18 PM
Finally got BFGMiner running on Debian on my BeagleBone Black. It's MUCH faster than the RaspberryPi. I'm running getwork proxy for 65GH and it's running at less than 10% CPU at full speed. The Pi can't do that for shit.
Trying USB miners later (I think I got hidapi running).
Still looking forward to getting LongPoll support.
Trying USB miners later (I think I got hidapi running).
Still looking forward to getting LongPoll support.
I've got hidalgo working on bbb with a few NFY. I remember having to compile libhidapi with --prefix=#####
Can't remember the exact location. Will check make file when I get home
I had no issues, hidapi installed no problems. The IceFurys are mining perfectly. I've got approx 90GH going through the BBB between proxies and USB miners. Less than 20% CPU.
Stats at http://847pool.no-ip.biz:7544/miner.php
January 02, 2014, 03:59:08 PM
Finally got BFGMiner running on Debian on my BeagleBone Black. It's MUCH faster than the RaspberryPi. I'm running getwork proxy for 65GH and it's running at less than 10% CPU at full speed. The Pi can't do that for shit.
Trying USB miners later (I think I got hidapi running).
Still looking forward to getting LongPoll support.
Trying USB miners later (I think I got hidapi running).
Still looking forward to getting LongPoll support.
I've got hidalgo working on bbb with a few NFY. I remember having to compile libhidapi with --prefix=#####
Can't remember the exact location. Will check make file when I get home
January 02, 2014, 03:14:29 PM
Finally got BFGMiner running on Debian on my BeagleBone Black. It's MUCH faster than the RaspberryPi. I'm running getwork proxy for 65GH and it's running at less than 10% CPU at full speed. The Pi can't do that for shit.
Trying USB miners later (I think I got hidapi running).
Still looking forward to getting LongPoll support.
Trying USB miners later (I think I got hidapi running).
Still looking forward to getting LongPoll support.
January 02, 2014, 01:49:54 PM
luke will you be making an ant miner firmware for your bfgminer ?
Wow....on the previous page...
How soon for antminer usb sticks? [/list]
Did you even look at the thread before posting? No? Thought not.
If you'd bothered to read the thread, you'd have seen this post less than 10 posts above yours: https://bitcointalksearch.org/topic/m.4208318
January 02, 2014, 12:41:37 PM
luke will you be making an ant miner firmware for your bfgminer ?
January 01, 2014, 08:40:17 PM
Hi Luke,
Hope the holiday session is going well.
I am struggling and need a hand with NFY devices on the Raspberry PI.
It's the usual "Raspberry Pi has broken USB" problem... workaround seems to be to set it to USB 1.1 mode (dwg_otc.speed=1 in cmdline.txt).Hope the holiday session is going well.
I am struggling and need a hand with NFY devices on the Raspberry PI.
Thanks for getting back to me, unfortunately that is with "dwg_otc.speed=1" enabled (I tried it without as well to see if that made a difference).
I however have noticed something odd, it does not always seg fault and dump. It will sometimes have a go at initilizing the device before it gives up like this;-
Code:
bfgminer version 3.9.0 - Started: [2014-01-01 18:31:59] - [ 0 days 00:00:10]
[M]anage devices [P]ool management [S]ettings [D]isplay options [H]elp [Q]uit
Connected to stratum.bitcoin.cz diff 3 with stratum as user NRF.MP3
Block: ...25104ab0 #278212 Diff:1.42G (10.15Ph/s) Started: [18:31:58]
ST:2 F:0 NB:1 AS:0 BW:[ 12/ 0kB/s] E:0.00 I: 0.00 BTC/hr BS:0
0 | 0.0/ 0.0/ 0.0 h/s | A:0 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
NFY 0: | OFF / 0.0/ 0.0 h/s | A:0 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
[2014-01-01 18:31:56] Loaded configuration file /opt/minepeon/etc/miner.conf
[2014-01-01 18:31:57] Probing for an alive pool
[2014-01-01 18:31:58] Network difficulty changed to 1.42G (10.15Ph/s)
[2014-01-01 18:31:58] Switching to pool 1 http://us1.eclipsemc.com:8337 - first alive pool
[2014-01-01 18:31:58] Long-polling activated for http://us1.eclipsemc.com:8337 (getblocktemplate)
[2014-01-01 18:31:59] API running in IP access mode on port 4028
[2014-01-01 18:31:59] Longpoll from pool 1 requested work update
[2014-01-01 18:31:59] mcp2210_set_cfg_gpio: Failed to set current GPIO config
[2014-01-01 18:31:59] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2014-01-01 18:31:59] NFY 0 failure, attempting to reinitialize
[2014-01-01 18:31:59] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2014-01-01 18:31:59] NFY 0 failure, disabling!
[2014-01-01 18:31:59] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2014-01-01 18:31:59] NFY 0 failure, disabling!
[2014-01-01 18:31:59] mcp2210_set_cfg_gpio: Failed to set current GPIO config
[2014-01-01 18:31:59] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2014-01-01 18:31:59] NFY 0 failure, disabling!
[2014-01-01 18:31:59] mcp2210_set_cfg_spi: Failed to set current SPI config
[2014-01-01 18:31:59] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2014-01-01 18:31:59] mcp2210_set_cfg_gpio: Failed to set current GPIO config
[2014-01-01 18:31:59] NFY 0 failure, disabling!
[2014-01-01 18:31:59] Pool 0 http://stratum.bitcoin.cz:3333 alive
[2014-01-01 18:31:59] Switching to pool 0 http://stratum.bitcoin.cz:3333
[2014-01-01 18:31:59] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2014-01-01 18:31:59] NFY 0 failure, disabling!
[2014-01-01 18:31:59] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2014-01-01 18:32:00] Stratum from pool 0 requested work update
[2014-01-01 18:32:00] Pool 0 is hiding block contents from us
[2014-01-01 18:32:00] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2014-01-01 18:32:00] mcp2210_get_gpio_input: Failed to get current GPIO input values
[2014-01-01 18:32:00] NFY 0 failure, disabling!
[2014-01-01 18:32:00] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
Does that mean anything to you?
Thanks for your help.
Neil
January 01, 2014, 04:10:46 PM
Hi Luke,
Hope the holiday session is going well.
I am struggling and need a hand with NFY devices on the Raspberry PI.
It's the usual "Raspberry Pi has broken USB" problem... workaround seems to be to set it to USB 1.1 mode (dwg_otc.speed=1 in cmdline.txt). Hope the holiday session is going well.
I am struggling and need a hand with NFY devices on the Raspberry PI.
Jump to: