Pages:
Author

Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 73. (Read 1193358 times)

legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
My Antminers are here.

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.
hero member
Activity: 868
Merit: 1000
My Antminers are here.

Hashing on a rPi but only at 500Mh/s

hero member
Activity: 1246
Merit: 501
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.
hero member
Activity: 658
Merit: 500
CCNA: There i fixed the internet.
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 Smiley
legendary
Activity: 1190
Merit: 1001
Any chance bfgminer will have built-in Antminer U1 support anytime soon?
legendary
Activity: 896
Merit: 1000
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
legendary
Activity: 896
Merit: 1000
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
legendary
Activity: 2576
Merit: 1186
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...
Can you post backtraces for those crashes?
hero member
Activity: 840
Merit: 1002
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.

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

Occasionally I get a few accepted shares first.
legendary
Activity: 896
Merit: 1000
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)
Code:
git clone https://github.com/signal11/hidapi
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

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
hero member
Activity: 1246
Merit: 501

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. Smiley
legendary
Activity: 896
Merit: 1000
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. Smiley

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
hero member
Activity: 1246
Merit: 501
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. Smiley

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
hero member
Activity: 658
Merit: 500
CCNA: There i fixed the internet.
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. Smiley

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
hero member
Activity: 1246
Merit: 501
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. Smiley
hero member
Activity: 1246
Merit: 501
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

     Roll Eyes
    legendary
    Activity: 1820
    Merit: 1001
    luke will you be making  an ant miner firmware for your bfgminer ?
    legendary
    Activity: 896
    Merit: 1000
    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).

    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
    legendary
    Activity: 2576
    Merit: 1186
    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).
    legendary
    Activity: 896
    Merit: 1000
    Hi Luke,

    Hope the holiday session is going well.

    I am struggling and need a hand with NFY devices on the Raspberry PI.  I finally got one and managed to compile hidapi correctly (I think) and bfgminer

    finds the devices correctly;-

    Code:
    bfgminer -D -T -d?
     [2014-01-01 11:52:55] setrlimit: Soft fd limit not being changed from 1024 (FD_SETSIZE=1024; hard limit=4096)
     [2014-01-01 11:52:55] Started bfgminer 3.9.0
     [2014-01-01 11:52:55] hidapi_try_lib: Couldn't load libhidapi.so: libhidapi.so: cannot open shared object file: No such file or directory
     [2014-01-01 11:52:55] hidapi_try_lib: Couldn't load libhidapi-0.so: libhidapi-0.so: cannot open shared object file: No such file or directory
     [2014-01-01 11:52:55] hidapi_try_lib: Successfully loaded libhidapi-hidraw.so
     [2014-01-01 11:52:55] hid_devinfo_scan: Found "NanoFury NF1 v0.6" serial "0000023445"
     [2014-01-01 11:52:56] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=1d6b, pid=0002, manuf=Linux 3.10.25-1-ARCH dwc_otg_hcd, prod=DWC

    OTG Controller, serial=bcm2708_usb)
     [2014-01-01 11:52:56] lowlevel_scan: Found usb device at usb:001:002 (path=(null), vid=0424, pid=9512, manuf=(null), prod=(null), serial=(null))
     [2014-01-01 11:52:56] lowlevel_scan: Found usb device at usb:001:003 (path=(null), vid=0424, pid=ec00, manuf=(null), prod=(null), serial=(null))
     [2014-01-01 11:52:56] lowlevel_scan: Found usb device at usb:001:004 (path=(null), vid=1a40, pid=0201, manuf=(null), prod=USB 2.0 Hub [MTT], serial=

    (null))
     [2014-01-01 11:52:56] lowlevel_scan: Found usb device at usb:001:006 (path=(null), vid=1a40, pid=0101, manuf=(null), prod=USB 2.0 Hub [MTT], serial=

    (null))
     [2014-01-01 11:52:56] lowlevel_scan: Found usb device at usb:001:005 (path=(null), vid=3322, pid=5544, manuf=(null), prod=USB 2.0 Hub [MTT], serial=

    (null))
     [2014-01-01 11:52:56] lowlevel_scan: Found usb device at usb:001:007 (path=(null), vid=1a40, pid=0101, manuf=(null), prod=USB 2.0 Hub [MTT], serial=

    (null))
     [2014-01-01 11:52:56] lowlevel_scan: Found usb device at usb:001:008 (path=(null), vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury

    NF1 v0.6, serial=0000023445)
     [2014-01-01 11:52:56] lowlevel_scan: Found hid device at hid:/dev/hidraw0 (path=/dev/hidraw0, vid=04d8, pid=00de, manuf=Microchip Technology Inc.,

    prod=NanoFury NF1 v0.6, serial=0000023445)
     [2014-01-01 11:52:56] lowlevel_scan: Found mcp2210 device at hid:/dev/hidraw0 (path=/dev/hidraw0, vid=04d8, pid=00de, manuf=Microchip Technology Inc.,

    prod=NanoFury NF1 v0.6, serial=0000023445)
     [2014-01-01 11:52:56] Devices detected:
     [2014-01-01 11:52:56]  NanoFury NF1 v0.6 by Microchip Technology Inc. (driver=nanofury; procs=1; serial=0000023445; path=/dev/hidraw0)
     [2014-01-01 11:52:56] Timers: Using clock_gettime(CLOCK_MONOTONIC_RAW)

    Unfortunatly when I start bfgminer

    ./bfgminer -S NFY:/dev/hiddev0 -c /opt/minepeon/etc/miner.conf

    It will seg fault and core dump;-

    Code:
    [2014-01-01 12:02:07] Loaded configuration file /opt/minepeon/etc/miner.conf
     [2014-01-01 12:02:07] Probing for an alive pool
     [2014-01-01 12:02:09] Network difficulty changed to 1.18G ( 8.45Ph/s)
     [2014-01-01 12:02:09] Switching to pool 1 http://us1.eclipsemc.com:8337 - first alive pool
     [2014-01-01 12:02:09] Long-polling activated for http://us1.eclipsemc.com:8337 (getblocktemplate)
     [2014-01-01 12:02:10] API running in IP access mode on port 4028
     [2014-01-01 12:02:10] mcp2210_set_cfg_gpio: Failed to set current GPIO config
     [2014-01-01 12:02:10] NFY 0: checkport failed
     [2014-01-01 12:02:10] NFY 0 failure, exiting
     [2014-01-01 12:02:10] Pool 0 http://stratum.bitcoin.cz:3333 alive
     [2014-01-01 12:02:10] Switching to pool 0 http://stratum.bitcoin.cz:3333Segmentation fault (core dumped)

    I really don't do much with coding (being an OS guy) but I compiled -g and here is the backtrace;-

    Code:
    gdb /home/minepeon/bfgminer/bfgminer core.22907
    GNU gdb (GDB) 7.6.2
    Copyright (C) 2013 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
    and "show warranty" for details.
    This GDB was configured as "armv6l-unknown-linux-gnueabihf".
    For bug reporting instructions, please see:
    ...
    Reading symbols from /home/minepeon/bfgminer/bfgminer...done.
    [New LWP 22930]
    [New LWP 22931]
    [New LWP 22932]
    [New LWP 22933]
    [New LWP 22934]
    [New LWP 22935]
    [New LWP 22936]
    [New LWP 22908]
    [New LWP 22927]
    [New LWP 22907]
    [New LWP 22918]
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/usr/lib/libthread_db.so.1".
    Core was generated by `/home/minepeon/bfgminer/bfgminer -S NFY:/dev/hiddev0 -c /opt/minepeon/etc/miner'.
    Program terminated with signal 11, Segmentation fault.
    #0  0x000af24c in nanofury_shutdown (thr=0x1bb3f78) at driver-nanofury.c:369
    369             struct mcp2210_device * const mcp = state->mcp;
    (gdb) bt
    #0  0x000af24c in nanofury_shutdown (thr=0x1bb3f78) at driver-nanofury.c:369
    #1  0x000474fc in miner_thread (userdata=0x1bb3f78) at deviceapi.c:732
    #2  0xb6eb8d2c in start_thread () from /usr/lib/libpthread.so.0
    #3  0xb6cbbad8 in ?? () from /usr/lib/libc.so.6
    #4  0xb6cbbad8 in ?? () from /usr/lib/libc.so.6
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)

    I am running as root as you say in the README and have modprobed everything you required;-

    Code:
    leds_gpio               2091  0
    led_class               3712  1 leds_gpio
    spi_bcm2708             4755  0
    i2c_dev                 5573  0
    i2c_bcm2708             3949  0
    snd_bcm2835            16222  0
    snd_pcm                81485  1 snd_bcm2835
    snd_page_alloc          5188  1 snd_pcm
    snd_timer              19925  1 snd_pcm
    snd                    58851  3 snd_bcm2835,snd_timer,snd_pcm
    bcm2708_rng             1032  0
    rng_core                4190  1 bcm2708_rng
    ipv6                  303991  0

    Thanks for any help you can provide.

    Neil
    Pages:
    Jump to: