Then my pc locked up and my fan speeds increased. I shut down and on reboot would post. Shutdown again and it booted properly.
The modules did load and the program did execute but the lockup happened.
lsmod | grep "i2c"
i2c_dev 13057 0
i2c_i801 16965 0
i2c_core 50152 4 drm,i2c_i801,i2c_dev,nvidia
Last edit: Fryndr 2014-10-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x69, mode smbus block
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: ff ff ff 00 ff 00 19 ......?
Very good. I'm busy right now.
The next few days I will make changes to the code.
Left quite a bit part.
Can you confirm right FSB calculation ?
Is this true 133 MHz FSB ?
Please post output of
cat /proc/cpuinfo
Last edit: Andrey Zhornyak 2014-10-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Build new version from git.
Try to overclock:
lfsb ics932s421b 133
Try 133 first, then add some more value.
Be careful with hi fsb values. It can be dangerous for the equipment.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please check git version. Make it with debug option.
Check http://sourceforge.net/p/lfsb/wiki/i2c-SMbus%20availability/
DO NOT REALY OVERCLOCK !
Just post output from command
lfsb ics932s421b
right here.
cpufreq-set failed
CPU frequency : 2659.98 MHz (estimated)
PLL ics932s421b is supported (untested)
Run as root?
Is module i2c_dev loaded?
Is i2c module for your chipset loaded?
Is i2c support enabled in kernel?
Run as root?
Is module i2c_dev loaded?
Is i2c module for your chipset loaded?
Is i2c support enabled in kernel?
cpufreq-set failed
Please read wiki section related to the git version of lfsb :
http://sourceforge.net/p/lfsb/wiki/How%20to%20build%20from%20git/
cpufreq-set failed
Then my pc locked up and my fan speeds increased. I shut down and on reboot would post. Shutdown again and it booted properly.
The modules did load and the program did execute but the lockup happened.
lsmod | grep "i2c"
i2c_dev 13057 0
i2c_i801 16965 0
i2c_core 50152 4 drm,i2c_i801,i2c_dev,nvidia
Last edit: Fryndr 2014-10-07
Ok, post the output of
i2cdetect -l
bash: i2c-detect: command not found
I don't understand why it isn't found.
Here is a locate of i2c:
/home/fryndr/code/src/i2c.c
---------cut----------
Last edit: Andrey Zhornyak 2014-10-09
i2cdetect -l not i2c-detect -l
bash: i2cdetect: command not found
Last edit: Fryndr 2014-10-07
You have to install i2c-tools.
If it debian like try (with root privileges)
apt-get install i2c-tools
Ok, sorry for the back and forth.
Output:
i2c-0 unknown SMBus I801 adapter at ece0 N/A
i2c-1 unknown NVIDIA i2c adapter 0 at 3:00.0 N/A
i2c-2 unknown NVIDIA i2c adapter 6 at 3:00.0 N/A
i2c-3 unknown NVIDIA i2c adapter 8 at 3:00.0 N/A
i2c-4 unknown NVIDIA i2c adapter 10 at 3:00.0 N/A
Ok, now try
i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- 08 -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- 44 -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- 6e --
70: -- -- -- -- -- -- -- --
I added a screenshot since the post isn't picking up the extra spaces.
Last edit: Fryndr 2014-10-08
Looks good. Now try block read from chip :
i2cdump 0 0x69 s
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x69, mode smbus block
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: ff ff ff 00 ff 00 19 ......?
Try new version on git. Build it with debug:
make debug
[fryndr@snowmantle:code|master %]$ sudo lfsb ics932s421b
cpufreq-set failed
CPU frequency : 2660.01 MHz (estimated)
PLL ics932s421b is supported (untested)
DEBUG: Using device '/dev/i2c-0'
unhide DEBUG: 7 bytes read : FF FF FF 00 FF 00 19
unhide DEBUG: 7 bytes written : FF FF FF 00 FF 00 19
unhide DEBUG: 7 bytes read : FF FF FF 00 FF 00 19
CheckTME DEBUG: 7 bytes read : FF FF FF 00 FF 00 19
Trusted Mode Disabled.
Overclocking is possible.
DEBUG: Using device '/dev/i2c-0'
unhide DEBUG: 7 bytes read : FF FF FF 00 FF 00 19
unhide DEBUG: 7 bytes written : FF FF FF 00 FF 00 19
unhide DEBUG: 7 bytes read : FF FF FF 00 FF 00 19
GetFSB DEBUG: 7 bytes read : FF FF FF 00 FF 00 19
GetFSB DEBUG: n=736, m=28, dt=0
FSB=177 MHz
cpufreq-set failed
Ok. Try git version again.
cpufreq-set failed
CPU frequency : 2660.04 MHz (estimated)
PLL ics932s421b is supported (untested)
DEBUG: Using device '/dev/i2c-0'
unhide DEBUG: 7 bytes read : FF FF FF 00 FF 00 19
unhide DEBUG: 9 bytes written : FF FF FF 00 FF 00 19 00 15
unhide DEBUG: 21 bytes read : FF FF FF 00 FF 00 19 11 15 2B 43 CD 3C E9 2F CD 3C E9 2F 59 D8
CheckTME DEBUG: 21 bytes read : FF FF FF 00 FF 00 19 11 15 2B 43 CD 3C E9 2F CD 3C E9 2F 59 D8
Trusted Mode Disabled.
Overclocking is possible.
DEBUG: Using device '/dev/i2c-0'
unhide DEBUG: 21 bytes read : FF FF FF 00 FF 00 19 11 15 2B 43 CD 3C E9 2F CD 3C E9 2F 59 D8
GetFSB DEBUG: 21 bytes read : FF FF FF 00 FF 00 19 11 15 2B 43 CD 3C E9 2F CD 3C E9 2F 59 D8
GetFSB DEBUG: n=828, m=13, dt=5
FSB=132 MHz
cpufreq-set failed
Last edit: Fryndr 2014-10-10
Very good. I'm busy right now.
The next few days I will make changes to the code.
Left quite a bit part.
Can you confirm right FSB calculation ?
Is this true 133 MHz FSB ?
Please post output of
cat /proc/cpuinfo
Last edit: Andrey Zhornyak 2014-10-10
I can confirm. Yes 133mhz is correct for FSB. I have 24 cores so I put cpuinfo in an attachment.
Build new version from git.
Try to overclock:
lfsb ics932s421b 133
Try 133 first, then add some more value.
Be careful with hi fsb values. It can be dangerous for the equipment.
I tried it 3 times to be sure. It locks up the PC as soon as I hit yes.
[fryndr@snowmantle:~]$ sudo modprobe i2c-dev
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
[sudo] password for fryndr:
[fryndr@snowmantle:~]$ sudo lfsb ics932s421b 133
cpufreq-set failed
CPU frequency : 2660.04 MHz (estimated)
PLL ics932s421b is supported (testing)
Trusted Mode Disabled.
Overclocking is possible.
FSB=132 MHz
Changing to:
FSB=133 MHz
WARNING: Too high FSB/PCI/AGP speed can DAMAGE your hardware!
Continue [y/N]:
Ok, I'll check where the problem.
Thank you. Let me know if I need to give more info.