.
Will try to find out further details or give up and buy another GPIO
board...
Thanks a lot for your responses!
Best regards,
Florian
On Sun, 9 Sep 2012, Florian Wöhrl wrote:
Clearly the device doesn't like your RPi system. There's some sort of
hardware-level incompatibility; it may even
Am 10.09.2012 04:55, schrieb Oliver Neukum:
On Monday 10 September 2012 10:51:32 Bjørn Mork wrote:
Oliver Neukum oneu...@suse.de writes:
On Monday 10 September 2012 10:11:15 Bjørn Mork wrote:
And I do not think ftdi_sio should be loaded for this device
since it is really not an FTDI device
Hi Alan,
Can you provide a comparable usbmon trace from a kernel where the
device works?
Also, to make sure that nothing important has been omitted, please
resend the earlier trace without any grep filtering. And do the same
with the new trace.
Now I have a trace from my Ubuntu 10.04 system
Hi Alan,
Am 09.09.2012 15:00, schrieb Alan Stern:
But it now still works when afterwards plugging it into the 12.04 desktop.
Any clue? I'm not that into driver development...
Is this a firmware thing? The device is powered by USB only. Why does it
work on Ubuntu 12.04 after plugging it in once
Hi Alan,
I don't think, that it was the RPi - because now it even works on the
RPi. Furthermore I had the problems before RPi with Ubuntu 12.04 on the
same desktop machine I used to run with 10.04.
In order words, the device now works with the same computer and OS that
it used to fail with
Hello everybody,
I am trying to get a USB IO Board running with Debian on Raspberry PI
and other 2.6.+ distributions (e.g. Ubuntu 12.04).
The board used to run fine with kernel 2.4.+ (e.g. Ubuntu 10.04) - a
Device /dev/ttyACM0 was created and usable.
But with newer kernels no device is
Hi Alan,
first I have to apologize - it's not kernel version 2.6.+ that's the
begin of the problems, it's 3.2.+ - included in Debian wheezy and Ubuntu
12.04.
Up to kernel 2.6. it is currently working correct.
I first thought it might be the change in the driver - because in the
past
Hi Alan, Oliver,
Am 08.09.2012 18:04, schrieb Alan Stern:
If you're certain that the problem is associated with the kernel
version, you could try using git bisect to pinpoint exactly what
change to the kernel caused the problem to start.
Never used git bisect before, but will give it a try.
