As I already wrote, I'm now able to Hotsync. However, I'm still interested in
answers to the following Bluetooth questions. BTW - as I understand it,
Bluetooth would also be useful for Internet connection and e-mail.
On Saturday 09 July 2005 21:31, Shlomo Solomon wrote:
Bluetooth might be a
On Sat, Jul 09, 2005 at 09:31:53PM +0300, Shlomo Solomon wrote:
(Snipped Bluetooth question - I never used Bluetooth)
I already read your later message about 95% success. So :-).
am also pretty sure it's a (partly) physical problem of the connection,
not (only) a software one.
I doubt that.
On Saturday 09 July 2005 21:31, Shlomo Solomon wrote:
Before I answer Yedidyah's latest post on this subject, I'd like to ask if
Bluetooth might be a solution to my Hotsync problem. The Zire 72 has
built-in Bluetooth and I know MDK10.1 supports Bluetooth. I've Googled and
found that connecting
I sent this over 2 hours ago and it didn't reach the list.
On Saturday 09 July 2005 21:31, Shlomo Solomon wrote:
Before I answer Yedidyah's latest post on this subject, I'd like to ask if
Bluetooth might be a solution to my Hotsync problem. The Zire 72 has
built-in Bluetooth and I know MDK10.1
Before I answer Yedidyah's latest post on this subject, I'd like to ask if
Bluetooth might be a solution to my Hotsync problem. The Zire 72 has built-in
Bluetooth and I know MDK10.1 supports Bluetooth. I've Googled and found that
connecting Palm to Linux via Bluetooth is do-able. My questions:
On Friday 08 July 2005 05:37, Shlomo Solomon wrote:
On Friday 08 July 2005 00:38, Yedidyah Bar-David wrote:
Can you at least rmmod visor and usb_serial (and modprobe them if
needed), then repeat the tests?
I've made some progress, so I'm on the right track, but .
1 - I figured out why I
On Fri, 8 Jul 2005, Shlomo Solomon wrote:
3 - I did alot of experimenting (including connecting to different USB plug
both with and without a hub). For some reason, out of abot 20 experiments I
did in the past hour, most of the timed out on the Palm, but in 2 cases I got
a dta error message
On Friday 08 July 2005 10:05, Shlomo Solomon wrote:
I now intend to clean everything up and make a few more tries. I'll try to
keep acurate records of what I do and see if the log entries can be of any
help.
OK - I did several experiments. Unfortunately, I was unable to reproduce the
On Friday 08 July 2005 13:00, Matan Ziv-Av wrote:
On Fri, 8 Jul 2005, Shlomo Solomon wrote:
3 - I did alot of experimenting (including connecting to different USB
plug both with and without a hub). For some reason, out of abot 20
experiments I did in the past hour, most of the timed out on
On Fri, Jul 08, 2005 at 02:36:59PM +0300, Shlomo Solomon wrote:
On Friday 08 July 2005 10:05, Shlomo Solomon wrote:
I now intend to clean everything up and make a few more tries. I'll try to
keep acurate records of what I do and see if the log entries can be of any
help.
OK - I did
Yedidyah Bar-David wrote:
There is no point in doing Ctrl-Z. If you want to shoot - shoot, don't
talk. Ctrl-C.
and if this does not work, you can also try Crtl-\ (backslash)
(sometimes progs stop responding to SIGINT, but they still respond to
this - it sends SIGQUIT)
I forgot to mention, in my previous message, that I did check the Palm on my
kids' Win98 computer and was able to hotsync - so this is not a problem with
the Palm.
Also, since my LINUX box has no problem communicating with several other USB
devices (scanner, printer, camera, mouse,
strange - I sent 2 messages to the list, but only the 2nd one got througt - so
here's the 1st one again.
On Tuesday 05 July 2005 22:59, Shlomo Solomon wrote:
On Tuesday 05 July 2005 19:52, Yedidyah Bar-David wrote:
OK. Let's start from the very beginning.
First, start from a clean known
On Tuesday 05 July 2005 22:59, Shlomo Solomon wrote:
On Tuesday 05 July 2005 19:52, Yedidyah Bar-David wrote:
OK. Let's start from the very beginning.
First, start from a clean known state. Either after a reboot, or try to
For completely unrelated reasons, re-booting is not an option today.
On Fri, Jul 08, 2005 at 12:02:12AM +0300, Shlomo Solomon wrote:
strange - I sent 2 messages to the list, but only the 2nd one got througt -
so
here's the 1st one again.
On Tuesday 05 July 2005 22:59, Shlomo Solomon wrote:
On Tuesday 05 July 2005 19:52, Yedidyah Bar-David wrote:
OK.
On Friday 08 July 2005 00:38, Yedidyah Bar-David wrote:
Can you at least rmmod visor and usb_serial (and modprobe them if
needed), then repeat the tests?
Sorry, I forgot to write that I tried that and was not able to remove the
modules. I didn't try --force because the man page says this is
On Tuesday 05 July 2005 02:31, Yedidyah Bar-David wrote:
But, as I said, some are actually accessible from ttyUSB0 and some from
ttyUSB1. I wanted to find out automatically which one, which wasn't
easy (found no real info on google). So I simply tried, and at least for
the first 3, I use the
On Tuesday 05 July 2005 02:31, Yedidyah Bar-David wrote:
But, as I said, some are actually accessible from ttyUSB0 and some from
ttyUSB1. I wanted to find out automatically which one, which wasn't
easy (found no real info on google). So I simply tried, and at least for
the first 3, I use the
On Tue, Jul 05, 2005 at 06:23:30PM +0300, Shlomo Solomon wrote:
[snip]
I still think it's strange that plugging in the USB cable causes the Kpilot
icon to pop up, so something is, at least partly, set up properly.
Not necessarily. Something is set up to respond to USB hotplug events.
Maybe not
On Tuesday 05 July 2005 19:52, Yedidyah Bar-David wrote:
OK. Let's start from the very beginning.
First, start from a clean known state. Either after a reboot, or try to
For completely unrelated reasons, re-booting is not an option today. I hope
I'll be able to do the tests you recommended in
This should be easy, but for some reason, I can't seem to sync my new USB
Palm. My previous Palm was a serial one and pilot-xfer -p/dev/ttyS1 worked
fine.
When I plugged in the USB cable on my new Zire 72, a KPILOT icon popped up on
the KDE desktop so I thought - wow, this is going to be
why not to link from /dev/pilot to /dev/usb ? (or whatever the device is
called on your system).
Shlomo Solomon wrote:
This should be easy, but for some reason, I can't seem to sync my new USB
Palm. My previous Palm was a serial one and pilot-xfer -p/dev/ttyS1 worked
fine.
When I plugged
On Mon, Jul 04, 2005 at 09:07:02PM +0300, Shlomo Solomon wrote:
This should be easy, but for some reason, I can't seem to sync my new USB
Palm. My previous Palm was a serial one and pilot-xfer -p/dev/ttyS1 worked
fine.
When I plugged in the USB cable on my new Zire 72, a KPILOT icon
On Mon, 4 Jul 2005, Shlomo Solomon wrote:
When I plugged in the USB cable on my new Zire 72, a KPILOT icon popped up on
the KDE desktop so I thought - wow, this is going to be easy. But, although
the icon popped up (and usbview also recognizes the Palm), it doesn't work. I
tried autodetection
On Monday 04 July 2005 21:43, Lior Kaplan wrote:
why not to link from /dev/pilot to /dev/usb ? (or whatever the device is
called on your system).
as I wrote before, I didn't find any new device in /dev - maybe I'm not
looking in the right place.
On Monday 04 July 2005 21:46, Yedidyah Bar-David
On Mon, Jul 04, 2005 at 10:56:55PM +0300, Shlomo Solomon wrote:
On Monday 04 July 2005 21:46, Yedidyah Bar-David wrote:
USB Palms use either /dev/ttyUSB0 or /dev/ttyUSB1, depending on model.
Use e.g. something like 'dlpsh -p /dev/ttyUSB0' (from pilot-link) to
find out which one, and make
On Mon, 4 Jul 2005, Shlomo Solomon wrote:
On my Fedora system, this is the content of
/etc/udev/rules.d/10-visor.rules:
BUS=usb, SYSFS{product}=Palm Handheld*, KERNEL=ttyUSB*,
SYMLINK=pilot
If you are using another system based on udev, it might be similar. If
you don't use udev, just create
On Monday 04 July 2005 23:43, Yedidyah Bar-David wrote:
If not, maybe you need to manually load the module - I don't know if
hotplug does that automatically (and you did not say if you use hotplug
but I guess you do).
# modprobe visor
not necessary - the module is loaded:
[EMAIL PROTECTED]
On Tue, Jul 05, 2005 at 01:32:33AM +0300, Shlomo Solomon wrote:
OK - I think I'm making some progress here. Each time I connect or
At last :-)
disconnect the USB cable, there are changes in the /dev directory. Notice
that there are several USB devices being created - always two at a time.
29 matches
Mail list logo
