Re: Fatal Exception on device when Hotsyncing Palm in linux

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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, 2015 at 10:20 PM, Dan Williams <dcbw@xxxxxxxxxx> wrote:
> 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 need to compile your own kernel (e.g. test an old kernel
>> on your recent userspace) if you really want to rule out that this is
>> kernel related (which it doesn't seem to be).
>>
>> > 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 hotsyncing. Does anyone know which, if at all,
>> > user-space program is auto-started in 10.04 after a Palm is detected?
>> > Do I need to check udev rules?
>>
>> No idea, sorry. Perhaps you should file a bug report with your distro.
>
> It might be ModemManager; try moving /usr/sbin/ModemManager out of the
> way.  If so, we'll update the USB device blacklist for various Palm
> devices upstream, so that it ignores them.
>
> Dan
>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux