On Mon, Jan 19, 2015 at 05:08:07PM +0100, Henri Manson wrote:
Apparently on 9.04 USB communications happen after invoking pilot-link
while in 10.04 it happens directly when Hotsync is activated on the
device. Enclosed the 9.04 syslog file and MenuExample.prc which is
sent using:
pilot-xfer
Hello,
I performed the test using VirtualBox and live cd iso images, so
mixing different version of kernel and user-space programs does not
happen. In 9.04 there is no usb communication until pilot-xfer is
started (a user-space program), in 10.04 usb communication happens
directly after
On Mon, Jan 26, 2015 at 04:00:26PM +0100, Henri Manson wrote:
Hello,
I performed the test using VirtualBox and live cd iso images, so
mixing different version of kernel and user-space programs does not
happen.
You'd probably need to compile your own kernel (e.g. test an old kernel
on your
On Mon, 2015-01-26 at 19:17 +0100, Johan Hovold wrote:
On Mon, Jan 26, 2015 at 04:00:26PM +0100, Henri Manson wrote:
Hello,
I performed the test using VirtualBox and live cd iso images, so
mixing different version of kernel and user-space programs does not
happen.
You'd probably
Indeed /usr/sbin/ModemManager (Ubuntu 14.04) or
/usr/sbin/modem-manager (Ubuntu 10.04) is the program that is started
when a Palm is connected and is causing the 'Fatal Exception' on the
Palm m505. Moving it out of the way is the solution. How can I update
the blacklist myself?
On Mon, Jan 26,
On Mon, 2015-01-26 at 22:49 +0100, Henri Manson wrote:
Indeed /usr/sbin/ModemManager (Ubuntu 14.04) or
/usr/sbin/modem-manager (Ubuntu 10.04) is the program that is started
when a Palm is connected and is causing the 'Fatal Exception' on the
Palm m505. Moving it out of the way is the solution.
From lsusb:
Bus 008 Device 013: ID 0830:0002 Palm, Inc. m505
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, 2015-01-26 at 23:33 +0100, Henri Manson wrote:
From lsusb:
Bus 008 Device 013: ID 0830:0002 Palm, Inc. m505
I've blacklisted anything driven by 'visor' upstream in ModemManager,
since most of those appear to be non-phone devices. Yes, 3 are phones
(Samsung and Acer) but they are so
[ Please try not to top-post. ]
On Mon, Jan 19, 2015 at 12:37:00PM +0100, Henri Manson wrote:
Enclosed the dmesg outputs from 9.04 and 10.04.4. I booted both
kernels with usbserial.debug=1 and loaded module visor.ko with
parameter debug=1
out-crash: debug output form Ubuntu 14.04.1 which
On Fri, Jan 16, 2015 at 10:10:52AM +0100, Oliver Neukum wrote:
On Thu, 2015-01-15 at 18:34 +0100, Henri Manson wrote:
Hello Greg,
Nothing goes wrong at the linux host, my Palm m505 shows as dialog box
'Fatal Exception' and hangs when the visor.ko module is loaded and
hotsync activated
Dear Johan,
Enclosed the dmesg outputs from 9.04 and 10.04.4. I booted both
kernels with usbserial.debug=1 and loaded module visor.ko with
parameter debug=1
Kind regards,
Henri
On Mon, Jan 19, 2015 at 11:56 AM, Johan Hovold jo...@kernel.org wrote:
On Sat, Jan 17, 2015 at 12:06:59AM +0100,
On Sat, Jan 17, 2015 at 12:06:59AM +0100, Henri Manson wrote:
I figured out how to get debug output, enclosed the results. How can I
get usbserial debug output on Ubuntu 9.04? It appears it wasn't a
module yet back then.
Try passing usbserial.debug=1 as a kernel parameter from the bootloader.
Ubuntu 9.04:
Linux ubuntu 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC
2009 i686 GNU/Linux
Ubuntu 10.04.4:
Linux ubuntu 2.6.32-38-generic #83-Ubuntu SMP Wed Jan 4 11:13:04 UTC
2012 i686 GNU/Linux
On Fri, Jan 16, 2015 at 12:24 PM, Johan Hovold jo...@kernel.org wrote:
On Thu, Jan 15,
On Sat, 2015-01-17 at 00:06 +0100, Henri Manson wrote:
I figured out how to get debug output, enclosed the results. How can I
get usbserial debug output on Ubuntu 9.04? It appears it wasn't a
module yet back then.
out-crash: debug output form Ubuntu 14.04.1 which causes the Palm m505 to
On Thu, 2015-01-15 at 18:34 +0100, Henri Manson wrote:
Hello Greg,
Nothing goes wrong at the linux host, my Palm m505 shows as dialog box
'Fatal Exception' and hangs when the visor.ko module is loaded and
hotsync activated on the Palm. There are some suggestions on the web
about draining
On Thu, Jan 15, 2015 at 12:00:28AM +0100, Henri Manson wrote:
I own a Palm m505 and a while ago a developed programs using SuperWaba
and uploaded them using pilot-xfer. Using Ubuntu 14.04 I tried
Hotsyncing on the device but now the devices shows a dialog box
containing 'Fatal Exception' and
I figured out how to get debug output, enclosed the results. How can I
get usbserial debug output on Ubuntu 9.04? It appears it wasn't a
module yet back then.
out-crash: debug output form Ubuntu 14.04.1 which causes the Palm m505 to crash
out: debug output form Ubuntu 9.04 which works fine
probe
Hello Greg,
Nothing goes wrong at the linux host, my Palm m505 shows as dialog box
'Fatal Exception' and hangs when the visor.ko module is loaded and
hotsync activated on the Palm. There are some suggestions on the web
about draining the palm battery but it seems to be a software problem
(visor
I own a Palm m505 and a while ago a developed programs using SuperWaba
and uploaded them using pilot-xfer. Using Ubuntu 14.04 I tried
Hotsyncing on the device but now the devices shows a dialog box
containing 'Fatal Exception' and then hangs.
I figured out using VirtualBox and old Ubuntu ISO
On Thu, Jan 15, 2015 at 12:00:28AM +0100, Henri Manson wrote:
I own a Palm m505 and a while ago a developed programs using SuperWaba
and uploaded them using pilot-xfer. Using Ubuntu 14.04 I tried
Hotsyncing on the device but now the devices shows a dialog box
containing 'Fatal Exception' and
20 matches
Mail list logo
