>Reply from support: >rats. >Try putting a printk() in w83781d_write_value() to identify >which write is the problem??? >If you figure it out email us and reference your ticket number. >MDS 12/19/01 hi! by the way...what do you mean with "rats" ?!? *hmmm* so: i put lots of printk()'s into the w83781d.c file and set init to value "0"... but still no success. :( let me explain, when using the attached file i tried a "modprobe w83781d" and /var/log/messages told me "Dec 20 13:14:42 kernel: i2c-core.o: i2c core module" "Dec 20 13:14:42 kernel: i2c-proc.o version 2.6.1 (20010825)" "Dec 20 13:14:42 kernel: init_module called." "Dec 20 13:14:42 kernel: w83781d.o version 2.6.2 (20011118)" "Dec 20 13:14:42 kernel: i2c-core.o: driver W83781D sensor driver registered." the printk with "init_module called" was printed out. obviously no other printk was called... *hmmm* is this ok? then i unloaded w83781d "Dec 20 13:26:09 kernel: i2c-core.o: driver unregistered: W83781D sensor driver" and loaded i2c-piix4 "Dec 20 13:26:37 kernel: i2c-piix4.o version 2.6.2 (20011118)" "Dec 20 13:26:37 kernel: i2c-piix4.o: Found CSB5 device" "Dec 20 13:26:37 kernel: i2c-core.o: adapter SMBus PIIX4 adapter at 0580 registered as adapter 0." "Dec 20 13:26:37 kernel: i2c-piix4.o: SMBus detected and initialized" "Dec 20 14:25:05 syslogd 1.4.1: restart." and there is no printk output. maybe writing to /var/log/messages isn?t "fast" enough, and the system freezes before write completes..? is there a way to print debugging info to the console? thx MK -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: w83781d.c Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20011220/5e98b27f/attachment.c
