headers
jmitchel | 13 Apr 2012 18:11

CF Data corruption on Jornada 680

Hello,

I've been seeing a strange problem with two different Jornada 680
handhelds. When copying files to a CF card in the PCMCIA slot, there is
data corruption. Basically I copy a file and then cmp the file with the
original and it doesn't match. Here's how the CF card is identified
(copied by hand):

wdc1: at pcmcia0 function 0: <TRANSCEND, TS4GCF  >
wdc1: i/o mapped mode
atabus1 at wdc1 channel 0:
wd1: at atabus1 drive 0: <TRANSCEND>
wd1: drive supports 1-sector PIO transfers, LBA addressing
wd1: 4011 MB, 8150 cyl, 16 head, 63 sec, 512 bytes/sect x 8215200 sectors

The same CF card and PCMCIA adapter work fine in a Jornada 720. Ideas as
to what the problem might be or how to troubleshoot it?

There is a strange message earlier in dmesg and the other CF card is in
memory mapped mode:

pcmcia0 at hd64461pcmcia0
pcmcia0: CIS checksum failed
pcmcia1 at hd64461pcmcia0
wdc0 at pcmcia 1 function 0: <TRANSCEND, TS1GCF100I, >
wdc0: memory mapped mode

Thanks,

Jason M.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Valeriy E. Ushakov | 13 Apr 2012 23:24
Picon

Re: Installing NetBSD 5.1.2 on a Jornada 680 - new hpcboot.exe needed?

On Fri, Mar 30, 2012 at 01:42:55 -0400, jmitchel <at> bigjar.com wrote:

> There is one more issue. The ramdisk doesn't appear to have sysinst. I
> just get dropped at a shell prompt. There are utilities on the ramdisk
> including "install" and "upgrade" in the root of the file system. But when
> run each utility complains "Can't open //install.md" There's nothing in
> the mailing list archives with that string. Any ideas?

sysinst was never taught how to deal with quirks of hpcsh, since in a
typical setup you want dual-fs CF card with FAT partition that
contains hpcboot and FFS partition that contains the system.  

I guess there's very little motivation to invest any time in that now.
The machines are more than a decade old and are rather underpowered,
so the user base is tiny.

-uwe
Permalink | Reply | 2 comments |
headers
Michael Wileman | 14 Apr 2012 00:29
Picon

Re: Installing NetBSD 5.1.2 on a Jornada 680 - new hpcboot.exe needed?

On Sat, 14 Apr 2012, Valeriy E. Ushakov wrote:

> I guess there's very little motivation to invest any time in that now.
> The machines are more than a decade old and are rather underpowered,
> so the user base is tiny.

It's a shame someone doesn't make a machine with the same form factor 
but more modern power.

Mike
Permalink | Reply | 1 comment |
headers
Jason Mitchell | 14 Apr 2012 01:15

Re: Installing NetBSD 5.1.2 on a Jornada 680 - new hpcboot.exe needed?

The Viliv N5 is close to the same form factor, but unfortunately the 
keyboard is horrible.

Jason M.

On 04/13/2012 06:29 PM, Michael Wileman wrote:
> On Sat, 14 Apr 2012, Valeriy E. Ushakov wrote:
>
>> I guess there's very little motivation to invest any time in that now.
>> The machines are more than a decade old and are rather underpowered,
>> so the user base is tiny.
>
> It's a shame someone doesn't make a machine with the same form factor 
> but more modern power.
>
> Mike
>
>
Permalink | Reply | 0 comments |
headers
Izumi Tsutsui | 14 Apr 2012 02:49
Picon
Gravatar

Re: Installing NetBSD 5.1.2 on a Jornada 680 - new hpcboot.exe needed?

> There is one more issue. The ramdisk doesn't appear to have sysinst. I
> just get dropped at a shell prompt. There are utilities on the ramdisk
> including "install" and "upgrade" in the root of the file system. But when
> run each utility complains "Can't open //install.md" There's nothing in
> the mailing list archives with that string. Any ideas?

Try 6.0_BETA.

---
Izumi Tsutsui
Permalink | Reply | 0 comments |
headers
jmitchel | 14 Apr 2012 04:48

Re: Installing NetBSD 5.1.2 on a Jornada 680 - new hpcboot.exe needed?

Sysinst pops up just like any other port -- Awesome! I'm running through
the install now. Thanks!

>> There is one more issue. The ramdisk doesn't appear to have sysinst. I
just get dropped at a shell prompt. There are utilities on the ramdisk
including "install" and "upgrade" in the root of the file system. But
when
>> run each utility complains "Can't open //install.md" There's nothing in
the mailing list archives with that string. Any ideas?
>
> Try 6.0_BETA.
>
> ---
> Izumi Tsutsui
>
Permalink | Reply | 0 comments |

Gmane