Problem with uvisor0, comms/pilot-link, and LifeDrive, on i386

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem with uvisor0, comms/pilot-link, and LifeDrive, on i386

Andreas Kahari
Hi,

I'm having problems getting pilot-xfer (from the comms/pilot-link port
on i386 (CURRENT)) to work properly (at all) with my Lifedrive trough
uvisor and ucom.

First of all, when I connect the USB cable to my LifeDrive, I get the
following lines in my dmesg (see last in this message for full dmesg):

  uvisor0 at uhub2 port 1
  uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5

These are followed after 4 to 5 seconds by

  uvisor0: init failed, TIMEOUT

Pressing the "HotSync" button on the LifeDrive results in the
following new dmesg lines:

  uvisor0: at uhub2 port 1 (addr 5) disconnected
  uvisor0 detached
  uvisor0 at uhub2 port 1
  uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5

... again followed by

  uvisor0: init failed, TIMEOUT

after about five seconds or so.

The pilot-xfer program is unable to connect to either of /dev/ttyU0 or
/dev/ttyU1, which with the above in mind doesn't seem too strange.
There seems to be something wrong in the initialization preventing the
ucom driver ("at uvisor?") to appear...

Has anyone got this to work with the LifeDrive?

dmesg (sorry for possibly badly formatted lines):

OpenBSD 3.9-beta (GENERIC) #62: Fri Feb 17 16:10:35 GMT 2006
    [hidden email]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) M processor 1700MHz ("GenuineIntel"
686-class) 1.69 GHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,EST,TM2
cpu0: Enhanced SpeedStep 1700 MHz (1484 mV): speeds: 1700, 1400, 1200,
1000, 800, 600 MHz
real mem  = 535863296 (523304K)
avail mem = 481939456 (470644K)
using 4278 buffers containing 26894336 bytes (26264K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(97) BIOS, date 11/21/03, BIOS32 rev. 0 @ 0xfd751
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xfd750/0x8b0
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf30/176 (9 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #3 is the last bus
bios0: ROM list: 0xc0000/0x10000 0xd8000/0x4000! 0xdc000/0x4000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82855PE Hub" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82855PE AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Radeon Mobility M6 LY" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x03: irq 9
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x03: irq 9
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev
0x03pci_intr_map: no mapping for pin C
: couldn't map interrupt
ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev
0x03pci_intr_map: no mapping for pin D
: couldn't map interrupt
ppb1 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x83
pci2 at ppb1 bus 2
cbb0 at pci2 dev 5 function 0 "Ricoh 5C475 CardBus" rev 0xb8: irq 3
"Ricoh 5C551 Firewire" rev 0x00 at pci2 dev 5 function 1 not configured
fxp0 at pci2 dev 8 function 0 "Intel PRO/100 VE" rev 0x83, i82562: irq
9, address 08:00:46:c8:ad:ab
inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0
iwi0 at pci2 dev 11 function 0 "Intel PRO/Wireless 2200BG" rev 0x05:
irq 9, address 00:0e:35:07:44:15
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 3 device 0 cacheline 0x0, lattimer 0x40
pcmcia0 at cardslot0
ichpcib0 at pci0 dev 31 function 0 "Intel 82801DBM LPC" rev 0x03
pciide0 at pci0 dev 31 function 1 "Intel 82801DBM IDE" rev 0x03: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
wd0 at pciide0 channel 0 drive 0: <IC25N080ATMR04-0>
wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <MATSHITA, UJ-812, K101> SCSI0 5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
ichiic0 at pci0 dev 31 function 3 "Intel 82801DB SMBus" rev
0x03pci_intr_map: no mapping for pin B
: polling
iic0 at ichiic0
auich0 at pci0 dev 31 function 5 "Intel 82801DB AC97" rev 0x03: irq 9, ICH4 AC97
ac97: codec id 0x594d4803 (Yamaha YMF753-S)
ac97: codec features 18 bit DAC, No 3D Stereo
audio0 at auich0
"Intel 82801DB Modem" rev 0x03 at pci0 dev 31 function 6 not configured
isa0 at ichpcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: using exception 16
biomask effd netmask effd ttymask ffff
pctr: 686-class user-level performance counters enabled
mtrr: Pentium Pro MTRR support
uhub2 at uhub0 port 2
uhub2: NEC Corporation USB2.0 Hub Controller, rev 2.00/1.00, addr 2
uhub2: 3 ports with 3 removable, self powered
ulpt0 at uhub1 port 2 configuration 1 interface 0
ulpt0: Prolific Technology Inc. IEEE-1284 Controller, rev 1.00/2.02,
addr 2, iclass 7/1
ulpt0: using bi-directional mode
uhidev0 at uhub2 port 2 configuration 1 interface 0
uhidev0: Sun Microsystems Type 6 Mouse, rev 1.00/1.02, addr 3, iclass 3/1
ums0 at uhidev0: 3 buttons
wsmouse1 at ums0 mux 0
uhidev1 at uhub2 port 3 configuration 1 interface 0
uhidev1: Sun Microsystems Type 6 Keyboard, rev 1.00/1.01, addr 4, iclass 3/1
ukbd0 at uhidev1: 8 modifier keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
dkcsum: wd0 matches BIOS drive 0x80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302

The following added when trying to get the HotSync to work.  Then I
gave up, mounted an SD card in the LifeDrive, transferred some files,
unmounted the card, and tried HotSync'ing again:

uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
umass0 at uhub2 port 1 configuration 1 interface 0
umass0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
umass0: using SCSI over Bulk-Only
scsibus1 at umass0: 2 targets
sd0 at scsibus1 targ 1 lun 0: <Toshiba, SD256, 1.0> SCSI0 0/direct removable
sd0: 3817MB, 3817 cyl, 64 head, 32 sec, 512 bytes/sec, 7818112 sec total
sd1 at scsibus1 targ 1 lun 1: <Toshiba, SD256, 1.0> SCSI0 0/direct removable
sd1: 243MB, 243 cyl, 64 head, 32 sec, 512 bytes/sec, 498176 sec total
umass0: at uhub2 port 1 (addr 5) disconnected
sd0 detached
sd1 detached
scsibus1 detached
umass0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT
uvisor0: at uhub2 port 1 (addr 5) disconnected
uvisor0 detached
uvisor0 at uhub2 port 1
uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
uvisor0: init failed, TIMEOUT


--
Andreas Kahari

Reply | Threaded
Open this post in threaded view
|

Re: Problem with uvisor0, comms/pilot-link, and LifeDrive, on i386

Antoine Jacoutot
Selon Andreas Kahari <[hidden email]>:
> First of all, when I connect the USB cable to my LifeDrive, I get the
> following lines in my dmesg (see last in this message for full dmesg):
>
>   uvisor0 at uhub2 port 1
>   uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
>
> These are followed after 4 to 5 seconds by
>
>   uvisor0: init failed, TIMEOUT

Hi.

I've been seeing the exact same behaviour here. As I sync my LifeDrive using
WiFi, I did not further investigate this problem.
Do you have a Linux box around (or a live CD) to see if it works with it (or
maybe pilot-link USB sync does not work withe this model yet) ?

As soon as I have time for this, I'll have a look at it.

--
Antoine

Reply | Threaded
Open this post in threaded view
|

Re: Problem with uvisor0, comms/pilot-link, and LifeDrive, on i386

Andreas Kahari
On 17/03/06, Antoine Jacoutot <[hidden email]> wrote:

> Selon Andreas Kahari <[hidden email]>:
> > First of all, when I connect the USB cable to my LifeDrive, I get the
> > following lines in my dmesg (see last in this message for full dmesg):
> >
> >   uvisor0 at uhub2 port 1
> >   uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
> >
> > These are followed after 4 to 5 seconds by
> >
> >   uvisor0: init failed, TIMEOUT
>
> Hi.
>
> I've been seeing the exact same behaviour here. As I sync my LifeDrive using
> WiFi, I did not further investigate this problem.
> Do you have a Linux box around (or a live CD) to see if it works with it (or
> maybe pilot-link USB sync does not work withe this model yet) ?
>
> As soon as I have time for this, I'll have a look at it.

Hi Antoine,

I really would like to sync with my OpenBSD machine as I wouldn't want
to have to install Linux for something as "trivial" as this. Could you
please describe how you go about syncing using WiFi?  This would be
very useful.

Thanks,
Andreas

--
Andreas Kahari

Reply | Threaded
Open this post in threaded view
|

Re: Problem with uvisor0, comms/pilot-link, and LifeDrive, on i386

Antoine Jacoutot
Selon Andreas Kahari <[hidden email]>:
> I really would like to sync with my OpenBSD machine as I wouldn't want
> to have to install Linux for something as "trivial" as this. Could you
> please describe how you go about syncing using WiFi?  This would be
> very useful.

First, you need to configure the network/wifi on your Palm and configure hotsync
to sync using the network with the "wi-fi" service.

It is explained in the LifeDrive docs I guess, but basically, for the hotsync
configuration, all you have to do is :
- hotsync, options -> computer name (I have a French Palm OS so the exact name
might be different) ; enter the IP/Netmask of the computer you wish to sync to.
- come back to the hotsync main screen and choose the Network sync (on top of
the hotsync icon, there's Local and Network).
That's all... of course, your WiFi _must_ be configured for this to work.

On you OpenBSD box, if using pilot-link, you can start the network hotsync
daemon with the following command (read the docs about pi-csd, I'm not 100%
certain about the following line):
# /usr/local/bin/pi-csd -H hostname -a 127.0.0.1 -n 255.255.255.0 -q

If you're using jPilot, all you have to do is configure your port as:
"net:"

Hope that helps...

--
Antoine

Reply | Threaded
Open this post in threaded view
|

Re: Problem with uvisor0, comms/pilot-link, and LifeDrive, on i386

asmith-4
In reply to this post by Antoine Jacoutot
This error is coming back from uvisor.c which is part of the Kernel. The
init function is there to initialise the device and get the USB Serial
endpoints back... I recently fixed this for a range of Sony CLIE devices but
that fix was Sony vendor code specific and wouldn't touch this device.

There are essentially two commands performed for most init scenarios
depending upon the device type that the palm device maps as... either a
vendor command 3 for VISOR type devices or a vendor command 4 for PALM4 type
devices... this is selected from a table of device mappings in the uvisor
driver.

If these commands fail you normally see a stalled message coming back from
init.

The uvisor driver then typically goes on to query the free space of the
device and this command on the Sony CLIE returns a TIMEOUT so it is possible
that is what is happening here.

I don't actually have a LifeDrive but would suggest that if anyone has one
they take a look at the uvisor.c source and try quitting the init function
before the Free Space check.. I know for a fact that the free space checks
on the CLIE put the USB Serial endpoints to sleep anyway which is why in my
patch once a CLIE is detected we skip these checks.

http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/uvisor.c

pilot-link is a different matter, it will probably work once the USB Serial
mapping is up across cuaUxx.

-Andy

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of
Antoine Jacoutot
Sent: 17 March 2006 15:38
To: openbsd-misc
Subject: Re: Problem with uvisor0, comms/pilot-link, and LifeDrive, on i386

Selon Andreas Kahari <[hidden email]>:
> First of all, when I connect the USB cable to my LifeDrive, I get the
> following lines in my dmesg (see last in this message for full dmesg):
>
>   uvisor0 at uhub2 port 1
>   uvisor0: palmOne, Inc. palmOne Handheld, rev 2.00/1.00, addr 5
>
> These are followed after 4 to 5 seconds by
>
>   uvisor0: init failed, TIMEOUT

Hi.

I've been seeing the exact same behaviour here. As I sync my LifeDrive using
WiFi, I did not further investigate this problem.
Do you have a Linux box around (or a live CD) to see if it works with it (or
maybe pilot-link USB sync does not work withe this model yet) ?

As soon as I have time for this, I'll have a look at it.

--
Antoine

Reply | Threaded
Open this post in threaded view
|

Re: Problem with uvisor0, comms/pilot-link, and LifeDrive, on i386

Andreas Kahari
In reply to this post by Antoine Jacoutot
On 17/03/06, Antoine Jacoutot <[hidden email]> wrote:

> Selon Andreas Kahari <[hidden email]>:
> > I really would like to sync with my OpenBSD machine as I wouldn't want
> > to have to install Linux for something as "trivial" as this. Could you
> > please describe how you go about syncing using WiFi?  This would be
> > very useful.
>
> First, you need to configure the network/wifi on your Palm and configure hotsync
> to sync using the network with the "wi-fi" service.
>
> It is explained in the LifeDrive docs I guess, but basically, for the hotsync
> configuration, all you have to do is :
> - hotsync, options -> computer name (I have a French Palm OS so the exact name
> might be different) ; enter the IP/Netmask of the computer you wish to sync to.
> - come back to the hotsync main screen and choose the Network sync (on top of
> the hotsync icon, there's Local and Network).
> That's all... of course, your WiFi _must_ be configured for this to work.
>
> On you OpenBSD box, if using pilot-link, you can start the network hotsync
> daemon with the following command (read the docs about pi-csd, I'm not 100%
> certain about the following line):
> # /usr/local/bin/pi-csd -H hostname -a 127.0.0.1 -n 255.255.255.0 -q
>
> If you're using jPilot, all you have to do is configure your port as:
> "net:"
>
> Hope that helps...

Yes, this helped.  I'm now able to HotSync with JPilot, at least on my
amd64 machine at home (haven't had time to test on the i386 I was
playing with earlier, but I'm sure it will work).

Thanks a lot.

Regards,
Andreas


--
Andreas Kahari