Looks to me like your serial port isn't working in your new kernel, more a
kernel issue than a digitemp issue.
Can you confirm you still have a working serial port and you can get minicom
to talk to things plugged into it? If not, you'll have to solve that first.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
DS9097U is a serial interface, but indeed it's possible to use it behind a
USB to serial converter.
It may be that the usb support changed slightly in a way that the serial
converter is working quite like it did before?
Now that you mention it, I hadn't realized that it doesn't work for me
on 2.6.34.1 either:
digitemp_DS9097 -s /dev/ttyS1 -w
DigiTemp v3.5.0 Copyright 1996-2007 by Brian C. Lane
GNU Public License v2.0 - http://www.digitemp.com
Turning off all DS2409 Couplers
Devices on the Main LAN
(nothing)
I just didn't realize since I switched to owfs a while ago since I have ow
devices that only owfs supports.
It's surprising that a kernel change would break just digitemp though.
Was digitemp maybe doing something wrong with the serial port but it just
happened to work until now?
> I have never dealt with the Linux kernel before - is there a change
> log somewhere?
Yes, and it's very long :)
On Fri, Oct 01, 2010 at 06:38:16PM -0700, kastrolis wrote:
> it is not usb problem, as I reported problem persists in both cases.
> k.
>
> p.s. googlegroups sux, I can post only thru web interface :(
What's the problem? Your posting address doesn't match your subscription
address?
To be honest, I'm not the right person, I don't use digitemp anymore since
as I explained it did not support my devices properly, so I switched to
owfs.
I guess I should unsubscribe from this list :)
Reverting it, then rebuilding the kernel where I first noticed the
problem, made it possible for digitemp to talk to the device again.
The problem was the kernel change. It has already been reverted in the mainline.
As for when ubuntu get around to fixing it, I don't know.
The bug is ranked about 5700 out of about 6500 bugs against the 'linux' package
so it may take a few weeks to get some attention.
Once it gets triaged it should progress quickly, since we've provided the fix.
Meanwhile you could build your own kernel, just edit ftdi_sio.c and
rebuild following:
https://help.ubuntu.com/community/Kernel/Compile
> I don't understand why they'd go making changes to how serial devices
> work now since most are for legacy hardware and applications and
> haven't changed since the early 1990's!
It's a puzzle, indeed. This is the "joy" of Linux.
I would be very interested to see if it continues to run over a long
period of time, for you.
I have had one failure (could not read anything back from the device)
18h after boot that got fixed by pulling and reinserting the usb
device. This has not yet recurred but I think a patch or two more may
be required to really fix this.
Details at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/690798.