Messages

1

OpenBSD / Cpio File Name Out Of Range Error On Installation

« on: October 25, 2007, 03:07:24 am »

Thanks mathemajikian,

I had thought of that as a possible issue (it's formatted FAT16) but I dismissed it as only one file seems to be suffering any problems or corruption because of it..

I'm not sure if my cheapo generic CF Ethernet card will work to grab them from FTP but i'll give it a go and see what happens.

If it isn't detected by OpenBSD are there any windows writeable filesystems I can format the CF card with that BSD will like during the installation? It's just easier as for some reason my card reader doesnt work under linux or i'd write the sets to the CF cazrd there.

Thanks,
sam

2

OpenBSD / Cpio File Name Out Of Range Error On Installation

« on: October 24, 2007, 05:09:10 am »

I'm currently trying to install OpenBSD using the zipped up sharp flash package available on this forum to simplify the boot, however after setting up the disklabels etc I get stuck at an error message while copying the sets:

I get many of these:
tar: Cpio file name length xxxxx is out of range
which are interspersed with a progress bar which seems to complete loading that package even though those errors are appearing. (im loading them all locally from a compactflash card in my Zaurus SL-C3200)

All sets work fine except for the xserv41.tgz file..
'xserv41.tgz' did not install correctly
I've tried redownloading this file and still have no luck.

I've also tried to install clean again using the 4.2 snapshot releases and get the exact same error but with the xserv42.tgz file this time so it seems to be something with the xserv files causing me problems.

Any pointers would be appreciated as i've searched here for cpio and no one mentione it so i assume no one else has had this issue.

TIA,
sam

3

OpenBSD / Destroyed Linux/partitions On Sl-c3200

« on: August 28, 2006, 06:39:48 pm »

This seems like as good a place as any to ask this as a search didn't turn it up..

If i install OpenBSD and totally screw up my 3200.. i can recover it using the recovery tools that are on there (the japanese screen) as nothing can touch this as far as i can see? This seems to be what the OP here has done, and then used the HDD scripts to get the HDD back up..

Is the 3200 therefore practically un-killable in this sense since this menu cannot be overwritten no matter how much i destroy the rest of it?

If this is the case then OpenBSd is going on there ASAP as the linux ports all feel very very unfinished.

4

5x00 General discussions / Dead? Sl-5500 - Any Advice?

« on: July 05, 2006, 01:15:43 pm »

System: SL-5500
Battery: 0v - i think the battery is *dead* this may be a ciontributing factor.

The Z won't boot at all.. However if i put a Sharp Ospack on the CF, hold D,C and reset the device (with the suspect battery in and the power in also - battery switch set to open mode) i get the green and orange lights up.. the flash goes through and the machine restarts.. it then gives the error:

Code: [Select]

INIT: version 2.78 booting
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
Couldn't find ext2 superblock, trying backup blocks...

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with alternate superblock:
   e2fsck -b 8193

ext2fs_check_if_mount: No such file or directory while determinating whether /dev/mtdblock1 is mounted.
e2fsck Invalid argument while trying to open /dev/mtdblock1

*** An error occured during
*** the file system check.
*** Dropping you to a shell;
*** the system will reboot
*** when you leave the shell.
/etc/passwd: root password garbled
Give root password for maintence (or type Control-D for normal startup):
And I cannot proceed any further.. (well i can get to single user/restore mode but nothing there seems to be working - all the suggested lines fail.. although i can run some stuff there - vi doesnt work but shell commands seem to work ok)


None of the diagnostic menus appear to be working at all (D,M and D,P do nothing at all) and the power button will not start the Z.. if i shut it down from single mode.. the only way to get it back up is too reflash again.

OpenZaurus, Cacko, pdaXrom all seem to do nothing when i try to flash with them.


Im starting to think it's bricked and gone.. but the fact i can see single usermode after a flash makes me think there must be some way to salvage the unit even if i have to manually rebuild the whole layout oor something..

any one got any ideas if this is dead or can i restore?

any help would be most greatly appreciated..

Thanks,
sam

5

5x00 General discussions / Dead (?) 5500 [solved]

« on: July 05, 2006, 12:16:24 pm »

I've been playing with this one for a day or 2 now and decided its dead.. though i can reflash and can see the EXACT same error messgae as the poster above bnothing will boot and i cant seem to do anything from thew recovery console to pewrsuade this collie to bark any longer.

I've tried a few reflashes with OZ and that doesnt seem to be working any better.

Can abnyone tell me what part of nmemory the /dev/mtdblock1 device is referring too? Is it possible a mem resize form OZ could cause this error?

Cheers,
Sam

6

5x00 General discussions / Dead (?) 5500 [solved]

« on: July 04, 2006, 03:39:38 pm »

I'm getting the exact same error on a 5500... did you manage to get this one solved?

Any info would be much appreciated.. I'm gonna try a few things now, anything works i'll post back