On Tue, 9 Oct 2012, [ISO-8859-1] Florian W�hrl wrote:
> Dear Alan, Oliver,
>
> short follow-up on my Microchip Test board with PIQ18F24J50 chip:
>
> pySerial worked quiet well, got some html server component up and running.
>
> Nevertheless the device again failed to work on machines (that mean
Dear Alan, Oliver,
short follow-up on my Microchip Test board with PIQ18F24J50 chip:
pySerial worked quiet well, got some html server component up and running.
Nevertheless the device again failed to work on machines (that meanwhile
worked) after having it plugged-off (from USB) for 2 days. It
On Mon, Sep 10, 2012 at 9:35 PM, Xiaofan Chen wrote:
> On Mon, Sep 10, 2012 at 8:48 PM, Oliver Neukum wrote:
>> On Monday 10 September 2012 08:37:55 Florian Wöhrl wrote:
>>> it seems like cdc_acm was altered, too - am I right? modinfo doesn't
>>> mention 04d8:000A. It just tells 04d8:000B. Did yo
On Mon, Sep 10, 2012 at 8:48 PM, Oliver Neukum wrote:
> On Monday 10 September 2012 08:37:55 Florian Wöhrl wrote:
>> it seems like cdc_acm was altered, too - am I right? modinfo doesn't
>> mention 04d8:000A. It just tells 04d8:000B. Did you make that patch?
>
> Doesn't the device show the proper c
On Mon, Sep 10, 2012 at 8:37 PM, Florian Wöhrl wrote:
> it seems like cdc_acm was altered, too - am I right? modinfo doesn't mention
> 04d8:000A. It just tells 04d8:000B. Did you make that patch?
That is bad.
1634/* Support for Droids MuIn LCD */
1635{ USB_DEVICE(0x04d8, 0x000b),
On Monday 10 September 2012 08:37:55 Florian Wöhrl wrote:
> Am 10.09.2012 04:55, schrieb Oliver Neukum:
> > On Monday 10 September 2012 10:51:32 Bjørn Mork wrote:
> >> Oliver Neukum writes:
> >>
> >>> On Monday 10 September 2012 10:11:15 Bjørn Mork wrote:
> > And I do not think ftdi_sio should
Am 10.09.2012 04:55, schrieb Oliver Neukum:
On Monday 10 September 2012 10:51:32 Bjørn Mork wrote:
Oliver Neukum 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 after all. 04d8:0
On Monday 10 September 2012 10:51:32 Bjørn Mork wrote:
> Oliver Neukum 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 after all. 04d8:000a is
> >> > a CDC-ACM dem
Oliver Neukum 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 after all. 04d8:000a is
>> > a CDC-ACM demo device from Microchip's USB Firmware
>> > Framework.
>>
>> Yes,
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 after all. 04d8:000a is
> > a CDC-ACM demo device from Microchip's USB Firmware
> > Framework.
>
> Yes, that is cleary an error which sh
Xiaofan Chen writes:
> On Sun, Sep 9, 2012 at 6:04 AM, Alan Stern wrote:
>> On Sat, 8 Sep 2012, Florian Wöhrl wrote:
>>> I first thought it might be the change in the driver - because in the
>>> past 04d8:000a was handled by cdc_acm, now the modalias shows ftdi_sio.
>>
>> No, that can't be the re
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 befo
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 be a question of available
> > power as Greg suggested. You should try adding a powered hub between
> > the computer and the device,
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
On Sun, 9 Sep 2012, Florian Wöhrl wrote:
> Now I have a trace from my Ubuntu 10.04 system (running on a Sony Vaio FW):
>
> # uname -a
> Linux xxx 2.6.32-33-generic #72-Ubuntu SMP Fri Jul 29 21:07:13 UTC
> 2011 x86_64 GNU/Linux
>
> # dmesg
> Sep 9 15:30:15 xxx kernel: [ 502.821293] usb
Am 09.09.2012 10:33, schrieb Alan Stern:
# uname -a
Linux desktop01 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
# dmesg
[20012.271332] usb 1-1.2: new full-speed USB device number 3 using ehci_hcd
[20017.357551] usb 1-1.2: unable to read config inde
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
On Sun, 9 Sep 2012, Florian Wöhrl wrote:
> 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
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. Th
On Sun, Sep 9, 2012 at 6:04 AM, Alan Stern wrote:
> On Sat, 8 Sep 2012, Florian Wöhrl wrote:
>> I first thought it might be the change in the driver - because in the
>> past 04d8:000a was handled by cdc_acm, now the modalias shows ftdi_sio.
>
> No, that can't be the reason. The problem occurs bef
On Sat, 8 Sep 2012, Florian Wöhrl wrote:
> 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
On Saturday 08 September 2012 15:56:42 Florian Wöhrl wrote:
> 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.
It would be go
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 04d8:000
On Sat, 8 Sep 2012, Greg KH wrote:
> On Sat, Sep 08, 2012 at 02:06:19PM -0400, Florian W�hrl wrote:
> >
> > 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 wi
On Sat, 8 Sep 2012, [ISO-8859-1] Florian W�hrl wrote:
>
> 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/ttyA
On Sat, Sep 08, 2012 at 02:06:19PM -0400, Florian Wöhrl wrote:
>
> 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 /de
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 crea
27 matches
Mail list logo
