Hi Blissz,

I think there is a bug in your latest firmware 08/12 v1.11. On the Miner Status page, the chains are numbered 2, 3, 4, but on the Miner Advanced Configuration page, they are numbered 1, 2, 3. Any changes made to chain 2 on the Miner Configuration page will be applied to chain 3 on the Miner Status page, and any changes to chain 3 will be applied to chain 3 and 4. Changes to chain 1 on the Miner Configuration page doesn't seem to affect anything.

As an experiment, I set the global frequency at 450M, chain 1 at 444M, chain 2 at 438M and chain 3 at 425M. Below is an excerpt from kernel log:

Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 444
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 438
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 425
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 425
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: software_set_address: chain 0 has 0 ASIC, and addrInterval is 1
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: software_set_address: chain 1 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: Now Set [1] Chain Address
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: software_set_address: chain 2 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: Now Set [2] Chain Address
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: software_set_address: chain 3 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: Now Set [3] Chain Address

On the Miner Status page, it shows that the frequency of chain 2, 3, and 4 are 438M, 425M, and 425M respectively.