[LEDE-DEV] mvebu:clearfog pro: Problems of ath10k driver and urandom

[Xue Liu]

Hello everyone,

Recently I update my lede repo to HEAD r1659 and found two problems in 
the firmware for clearfog pro board.

The first problem is about random. I got message below:

[    1.455149] init: Console is alive
[    1.458621] init: - watchdog -
[    1.662992] init: - preinit -
[    1.765184] random: jshn: uninitialized urandom read (4 bytes read, 7 
bits of entropy available)
[    1.785144] random: jshn: uninitialized urandom read (4 bytes read, 7 
bits of entropy available)
[    1.801371] random: jshn: uninitialized urandom read (4 bytes read, 7 
bits of entropy available)
[    1.821036] random: jshn: uninitialized urandom read (4 bytes read, 7 
bits of entropy available)
[    1.836021] random: jshn: uninitialized urandom read (4 bytes read, 7 
bits of entropy available)
[    1.852425] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[    3.851416] mvneta f1030000.ethernet eth0: Link is Up - 1Gbps/Full - 
flow control off
[    3.859279] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    4.901827] mount_root: mounting /dev/root
[    4.906144] EXT4-fs (mmcblk0p2): warning: mounting unchecked fs, 
running e2fsck is recommended
[    4.918122] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    4.927956] urandom-seed: Seed file not found (/etc/urandom.seed)
[    4.957518] procd: - early -
[    4.960430] procd: - watchdog -
[    5.541489] procd: - ubus -
[    5.598030] random: ubusd: uninitialized urandom read (4 bytes read, 
9 bits of entropy available)
[    5.607015] random: ubusd: uninitialized urandom read (4 bytes read, 
9 bits of entropy available)
[    5.615933] random: ubusd: uninitialized urandom read (4 bytes read, 
9 bits of entropy available)
[    5.624909] random: ubusd: uninitialized urandom read (4 bytes read, 
9 bits of entropy available)
[    5.633824] random: ubusd: uninitialized urandom read (4 bytes read, 
9 bits of entropy available)
[    5.642880] procd: - init -
Please press Enter to activate this console.

Should I enable other packages ?

The other problem is that my QCA9880 WiFi cards can not work any more. 
Neither ath10k nor ath10k-ct driver can not work properly and give me 
almost the same message:

[    6.217867] ath10k_pci 0000:01:00.0: Direct firmware load for 
ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
[    6.228604] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.240597] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: 
firmware_loading_store: map pages failed
[    6.249693] ath10k_pci 0000:01:00.0: Direct firmware load for 
ath10k/cal-pci-0000:01:00.0.bin failed with error -2
[    6.260083] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.269688] firmware ath10k!cal-pci-0000:01:00.0.bin: 
firmware_loading_store: map pages failed
[    6.278408] ath10k_pci 0000:01:00.0: Direct firmware load for 
ath10k/fwcfg-pci-0000:01:00.0.txt failed with error -2
[    6.288971] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.298511] firmware ath10k!fwcfg-pci-0000:01:00.0.txt: 
firmware_loading_store: map pages failed
[    6.311374] ath10k_pci 0000:01:00.0: Direct firmware load for 
ath10k/QCA988X/hw2.0/firmware-5.bin failed with error -2
[    6.322114] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.331684] firmware ath10k!QCA988X!hw2.0!firmware-5.bin: 
firmware_loading_store: map pages failed
[    6.340715] ath10k_pci 0000:01:00.0: could not fetch firmware file 
'ath10k/QCA988X/hw2.0/firmware-5.bin': -11
[    6.350694] ath10k_pci 0000:01:00.0: Direct firmware load for 
ath10k/QCA988X/hw2.0/firmware-4.bin failed with error -2
[    6.361426] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.371006] firmware ath10k!QCA988X!hw2.0!firmware-4.bin: 
firmware_loading_store: map pages failed
[    6.380047] ath10k_pci 0000:01:00.0: could not fetch firmware file 
'ath10k/QCA988X/hw2.0/firmware-4.bin': -11
[    6.390029] ath10k_pci 0000:01:00.0: Direct firmware load for 
ath10k/QCA988X/hw2.0/firmware-3.bin failed with error -2
[    6.400756] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.410195] firmware ath10k!QCA988X!hw2.0!firmware-3.bin: 
firmware_loading_store: map pages failed
[    6.419249] ath10k_pci 0000:01:00.0: could not fetch firmware file 
'ath10k/QCA988X/hw2.0/firmware-3.bin': -11
[    6.442274] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c 
chip_id 0x043202ff sub 0000:0000
[    6.451542] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 
tracing 0 dfs 0 testmode 0
[    6.461013] ath10k_pci 0000:01:00.0: firmware ver 
10.1.467-ct-_fW-016-0c89552 api 2 features 
wmi-10.x,has-wmi-mgmt-tx,txstatus-noac5
[    6.503048] ath10k_pci 0000:01:00.0: Direct firmware load for 
ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[    6.513516] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.523298] firmware ath10k!QCA988X!hw2.0!board-2.bin: 
firmware_loading_store: map pages failed
[    6.534482] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A 
crc32 bebc7c08
[    7.798787] device eth0 entered promiscuous mode
[    7.804312] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[    7.818207] device eth1 entered promiscuous mode
[    7.822957] br-lan: port 2(eth1) entered forwarding state
[    7.828393] br-lan: port 2(eth1) entered forwarding state
[    7.833871] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[    7.847342] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[    8.381410] ath10k_pci 0000:01:00.0: failed to receive control 
response completion, polling..
[    8.801423] br-lan: port 2(eth1) entered disabled state
[    9.381405] ath10k_pci 0000:01:00.0: Service connect timeout
[    9.387081] ath10k_pci 0000:01:00.0: failed to connect htt (-110)
[    9.472285] ath10k_pci 0000:01:00.0: could not init core (-110)
[    9.478259] ath10k_pci 0000:01:00.0: could not probe fw (-110)
[    9.791414] mvneta f1030000.ethernet eth0: Link is Up - 1Gbps/Full - 
flow control off

Can anyone give me some advices ?

In the attachment you can find the whole boot message.

Regards,

Xue Liu

-------------- next part --------------
A non-text attachment was scrubbed...
Name: lede-r1659-clearfog-bootlog.log
Type: text/x-log
Size: 22746 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/lede-dev/attachments/20160926/814287db/attachment-0001.bin>