** Changed in: gnome-pilot (Ubuntu)
Status: Incomplete => Invalid
** Changed in: gnome-pilot (Ubuntu)
Assignee: Ubuntu PDA team (ubuntu-pda) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
I haven't even used the Palm in question for at least 4 years. I think
it is safe to close this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/108512
Title:
sync on feisty with Palm m130, 'visor
Does this happen in supported Ubuntu versions? Thank you for telling us!
** Changed in: gnome-pilot (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/108512
I mentioned in Bug #71837 I am also experiencing this issue with a Sony
Clie and Ubuntu 8.04 Hardy Heron.
Ms.Kai
May 25, 2008
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launchpad.net/bugs/108512
You received this bug notification because you are a member of U
Manually loading the visor module works for me, but using "usb:" instead
of "dev/pilot" just doesn't seem to work with my Z22.
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launchpad.net/bugs/108512
You received this bug notification because you are a member of U
I can confirm this bug is also present in Gutsy.
One way to fix it is to edit /etc/modprobe.d/libpisock9 and comment the line
"blacklist visor".
The other way is to configure gnome-pilot to use "usb:" instead of "/dev/pilot"
as device.
--
sync on feisty with Palm m130, 'visor' kernel module not
Thank you. These instructions solved the same problem on my laptop,
which has a fresh feisty installation.
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launchpad.net/bugs/108512
You received this bug notification because you are a member of Ubuntu
Bugs, which is
btw, does the ubuntu pda team have some email address? I want to forward
a mail from a pilot-link.org guy.
He thinks, that using libusb for palm sync by default is not such a good
idea (yet). Mail includes some details.
regards
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
reagarding permissions: you have to be in the group dialout.
see /etc/udev/rules.d/60-libpisock.rules
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launchpad.net/bugs/108512
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Hi,
it looks like it is not a bug, it is a feature ... ;)
The visor module is not loaded anymore after plug-in because it is
blacklisted in /etc/modprobe.d/libpisock9. Well, and libpisock9 is some
userspace palm communication library, which could be used by pilot-xfer,
kpilot etc.
For example:
This is one of the several things that already worked in Edgy but didn't work
in Feisty.
I also think this is a regression bug.
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launchpad.net/bugs/108512
You received this bug notification because you are a member of
I think the use of the visor module with gnome-pilot may be deprecated.
I don't remember where I saw it, but try changing the device to "usb:"
instead of /dev/anything ... that worked for me on a Tungsten C. (I
don't know if it will still work if you've already done "modprobe
visor".)
--
sync on
I can confirm this also applies to my Palm Zire 71. This is a regression
bug, I'd assume, since it did work in Edgy?
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launchpad.net/bugs/108512
You received this bug notification because you are a member of Ubuntu
Bugs
My guess is that something changed in the udev directory. I suspect a keyword
is missing/vid/pid in one of these files:
/etc/udev/rules.d/ 60-libpisock.rules or 60-symlinks.rules
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launchpad.net/bugs/108512
You recei
I haven't made any new changes since April 24th, when I made my last
comment. Since then, I can boot up and sync immediately without doing
anything else. I did add the visor module to the list in /etc/modules on
April 24th, so it has loaded automatically since then.
--
sync on feisty with Palm m1
Hmm, I wonder what has changed. Late last month I could still sync if I
loaded the visor module manually. Now doing that does not seem to help
any at all. Is this workaround still working for the rest of you?
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launchpa
Lynoure: agreed. I've used this Palm with Hoary, Breezy, and Edgy (it
had problems with Dapper, though).
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launchpad.net/bugs/108512
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
** Changed in: gnome-pilot (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu PDA team
Status: Unconfirmed => Confirmed
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launchpad.net/bugs/108512
You received this bug notificati
The thing is that before, visor module would load automatically.
Something is still wrong, but it is nice there is a workaround.
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launchpad.net/bugs/108512
You received this bug notification because you are a member of
I should add, for those who might be looking for help and don't know
this is possible, you can make the module load automatically.
sudo gkedit /etc/modules
add visor to the end of the list, save. You're done..
--
sync on feisty with Palm m130, 'visor' kernel module not loaded
https://bugs.launc
Lynoure: thanks for the input, that was the nudge I needed to get my
thoughts together.
I found the "something simple" that I was missing. The solution was
quite simple. I'm still using /dev/ttyUSB0 and 1.
Before starting gnome-pilot, open a terminal and type:
sudo modprobe visor
to load the vi
I think this is caused by the kernel and not by gnome-pilot. At the
earlier kernel on feisty and the same kpilot I have now I could get
synching to happen fine, and lsmod would show the visor module. Now the
device gets detected, but visor module does not get loaded, and so
nothing happens with kpi
22 matches
Mail list logo
