Hey Steve,
Is it possible that if I upgrade a kernel and reboot, but do not unplug
the FET, that the FET could retain a state that allows it to work with
the 'broken' Ubuntu kernel module? It kind of seems like this may be
what I'm experiencing.
I upgraded the kernel again today to the 2.6.24-19.34 version just
released. Upon update and reboot the FET was still working, but while
playing around with an EZ430 I was plugging/unplugging the EZ430 and the
FET and the FET stopped working and would not register the udev device.
After loading your kernel module it worked again.
Maybe this explains the mixed success I've had with the various Ubuntu
kernels and having to apply or not apply your kernel module. I rarely
turn off my computer and often reboot without power cycle(or unplugging
the FET) when updating the kernel.
Normally I wouldn't obsess over the kernel updates, but I've been
curious about what I've seen with the FET driver, so I've been updating
with every release to see what happens.
Dave L.
Stephen Glow wrote:
Odd indeed. It seems to only work in odd versions of the Ubuntu
kernel! :-)
Steve
David E. Lotton wrote:
I posted another reply which has not shown up on the list...
1) I had to apply Stephen Glow's kernel module to get the FET driver to
work in the Ubuntu 8.04 2.6.24-16 kernel.
2) I later upgraded to the 2.6.24-17 kernel the FET driver worked
without applying Stephen's driver.
3) After upgrading to the 2.6.24-18 kernel I had to apply Stephen's
driver to make it work.
4) After upgrading to the 2.6.24-19 kernel it works again without
applying Stephen's driver.
I've checked the md5sum of the working Ubuntu drivers against Stephen's
driver to verify that they are different, and they are.
Odd.
Dave L.
David E. Lotton wrote:
FYI,
I just installed the Ubuntu 8.04 kernel 2.6.24-17 upgrade package and
the issue seems to be resolved.
DL
