Messages

1

For Sale / Wanted / [wanted] Zaurus Sl-c Series

« on: June 10, 2013, 06:07:14 pm »

Thanks

Canguy247,  sent you a PM.  Did you receive it?

2

C1000/3x00 General discussions / C3000 Hd Partitioning Musings

« on: October 13, 2005, 04:06:43 pm »

I'm at the stage in rebuilding my 3K that I want to start thinking about how to use it to best advantage.  So I thought before I started dropping applications and data onto /hdd3 I'd consider some amount of HD customization.

Specifically, being a bit of a purist, I'm not entirely happy having /hdd3 be completely VFAT, and having my ext3 symbolic links pointing to a file system that will not support the ext2/3 filesystem structure.  
However, if I just smash hdd3 and make it ext3 then I lose the USB HD function the 3K provides.  So I see value in having a VFAT partition for that.

So I'm thinking I should repartition /dev/hdc3 into two chunks.  One I will make VFAT to preserve USB HD, and the other ext3 to permit the symbolic link to /hdd3/Documents to point to a journalled file system.  I was thinking a 512/1.5M split.  

But, thinks I, /hdd1, /hdd2, and /hdd3 are hard drive mount points for the stock three partitions.  I just don't know if these are in the FLASH portion of the filesystem.  So if I wanted to make a /hdd4 mount point, what would I have to do to make it?

Or should I just bag that plan and create a different mount point in one of the HD partitions and mount the virtual /hdd4 somewhere in that tree?

I figure I still keep the ext3/ext3/vfat order of the stock rom and just append another ext3 partition.  This would keep the rc.rofilesys boot structure happy, and I could just add a line to /etc/rc.local to mount the final partition.

Is there a better way to accomplish this?

3

C1000/3x00 General discussions / Infinite Reboot On 3000

« on: October 12, 2005, 12:04:48 pm »

Ok... restoring my C3000 to stock was quite the edjumacation.  Having gone through that I think I could have solved my original problems just using the DB boot, fdisk, and mkfs.  That's how I finally got the stock rom to boot, as it was just as unhappy as the 3kb1 rom.  

That said, I finally have a stock machine localized to English (Thanks Trisoft!)  

However, I'm back to attempting to get Cacko 3kb1 installed.  I downloaded, after a lot of searching and frustration with Japanese character webpages, a file called zImage_v18a_c3000.bin in an attempt to install the Tetsu special kernel.  However, every time I put this file (renamed as zImage.bin) on my CF and reflash the kernel, the system fails to boot.  All I get is a slight "flashover" (i.e. LCD is birght, then dims) of the LCD and then it remains blank.  

So... did I download the correct image?
Am I waiting long enough for the kernel to do it's work?

I'm so happy to have my Z booting again, but I really want the "chatty" boot mode of the Tetsu kernel back.

4

C1000/3x00 General discussions / Infinite Reboot On 3000

« on: October 10, 2005, 12:06:24 pm »

Ok.... I managed to do something stupid.  I was trying to install Opera 7.3 C-series patch from the ZUG downloads.  It ended up putting the Z in portrait mode, so I tried to uninstall.  The Z sat there in portrait saying "please wait".  Well... I thought it was hung, so I punched the reset button.  Now my Cacko b1 install brings up the splash screen, thinks for awhile, and then goes back to text mode doing the "bootup countdown".  It never quits doing this.

How do I attempt to undo the damage?  Particulars:
Cacko 3kb1
hda3 formatted ext3
aborted "Opera 7.3 c-series" uninstall

potentially additional stupid thing done:
tried to reinstall cacko3kb1 from SD.  So now the rc.rofilesys is probably back to thinking hda3 is vfat.

5

Software / Kde-pim/pi 2.1.0 Available!

« on: June 15, 2005, 12:42:22 pm »

So this brings me to my next issue.... KO/Pi on the Z always runs out of memory during PI-Sync.  I get a "memory is low choose an app to close" dialog with only KO/Pi listed in it and then my Z either reboots, or I have to close KO/Pi.  I'm on a 5500 with the 3.1x Sharp ROM, so I'm stuck at 32/32 memory.  I removed some apps from my system, but I suppose that only removed them from the ramdisk, not the program heap.  Am I just stuck not being able to sync my calendar using a 32M image? 

Where did you start the sync?
I assume from the Z?
If you start it from the Desktop it should not need too much memory on the Z.

z.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=84345\"][{POST_SNAPBACK}][/a][/div]

It didn't seem to matter where it was started.  It always ran out of memory on the Z.  I finally broke down and created a swap file on my ramdisk.  The problem is solved for now, though it bites not having all of my ramdisk available.  Yes, I could put swap on SD/CF, but I don't like the idea of doing that.  That's one area where the C3000 wins in my opinion, swapfile actually on a HD.

Now I have to figure out how to sync PIM/Pi to Outlook 2K3.  I'm disturbed by what I saw in a previous post.  One of the reasons I'm looking at moving PIM's is that my other Z doesn't sync to O2K3 anymore.  The sync GPF's, making it useless to my fiance.  Does sync from O2K3 to PIM/Pi require a working Intellisync link?

6

Software / Kde-pim/pi 2.1.0 Available!

« on: June 10, 2005, 01:30:45 pm »

Interesting artifact....  I tried, I don't know why, to reimport the OL2K info again while I was trying to figure out how to get PI-Sync working, and noticed as I was working that KO/Pi for Windoze actually had my data.  I then closed the "Import" dialog and the app crashed.  Launching the app again shows my calendar data is in KO/Pi.  Later I deleted the ics file due to an issue with the timezone setting and attempted to reimport the data.  After multiple attempts I finally just left the "Finished importing" dialog up for a long time and watched the size of the ics file.  It finally got to >700K and then I closed the dialog.  KO/Pi crashed, but when I brought it back up, again all my calendar data is there.  

So this brings me to my next issue.... KO/Pi on the Z always runs out of memory during PI-Sync.  I get a "memory is low choose an app to close" dialog with only KO/Pi listed in it and then my Z either reboots, or I have to close KO/Pi.  I'm on a 5500 with the 3.1x Sharp ROM, so I'm stuck at 32/32 memory.  I removed some apps from my system, but I suppose that only removed them from the ramdisk, not the program heap.  Am I just stuck not being able to sync my calendar using a 32M image?  I'm considering creating a network swap drive to perhaps solve the problem.  Seems like thats a step I shouldn't have to take though...

Finally, I think it would be nice to have a primer on how to build the programs from source.  I downloaded the tarball on my RHEL system because I wasn't sure the SUSE RPM would run on RHEL 4.  

This looks like a much better PIM tool than the Sharp versions, but only so long as I can get the whole shooting match to work.....

7

Software / Kde-pim/pi 2.1.0 Available!

« on: June 07, 2005, 11:18:16 pm »

Unfortunately Z... the latest 2.1.5 version does not solve the problem.  Looks like I may have to abandon my old calendar information and just move forward without it.  I really don't have a lot of time right now to try and set up a compile/debug ability to chase this.  

8

Software / Kde-pim/pi 2.1.0 Available!

« on: June 07, 2005, 01:04:57 pm »

Please try to import your 2000 events with version 2.1.5 and let me know if it works.

z.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=83217\"][{POST_SNAPBACK}][/a][/div]

Will do...  I was starting to look into how to build the XP version of the tool in order to find out where in the code it was dying, and perhaps give feedback on what data was killing the app.  However, it was a bit confusing as to what I needed to compile, and I hadn't had time to figure out what tools I need to build the XP version.

9

Software / Kde-pim/pi 2.1.0 Available!

« on: June 06, 2005, 07:21:20 pm »

I tried creating a new test calender in O2K and added one or two items to it.  I told KO/Pi to import the entries from the new calender and it works fine.  What suggestion can you make for a next step?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=82932\"][{POST_SNAPBACK}][/a][/div]

What are you trying to accomplish, exactly?  

Well... based on my earlier post,  I'm trying to import my OL2K calendar data without the Windoze version of KDEPIM generating a GPF and collapsing in on itself.  As I said earlier the import brings up a dialog saying "xxxx entries imported" and then when I click OK the app GPF's.  Z suggested testing with another test calendar, which I did, and the one or two entries I created did import correctly.  So either the quantity of entries or something in my >2000 entries causes KDEPIM(Windoze) to crap out.  I'd rather not audit that number of entries in an attempt to find out why the KO/Pi (Windoze) dies.  Is there another path I can take to transfer my data away from OL2K so that I can move to an app that will let me sync to Linux apps?  

It appears there's a blown pointer in some code that gets invoked by some piece of data in my calendar.

10

Software / Kde-pim/pi 2.1.0 Available!

« on: June 05, 2005, 11:18:35 pm »

I tried creating a new test calender in O2K and added one or two items to it.  I told KO/Pi to import the entries from the new calender and it works fine.  What suggestion can you make for a next step?

11

Software / Kde-pim/pi 2.1.0 Available!

« on: June 03, 2005, 01:38:58 am »

Ok... So I finally had enough time to mess around with importing my Outlook 2K data into KDEPIM.  KA/Pi grabbed my data without a hiccup.  So all is looking good there.  However, when I use KO/Pi to import my OL2K records it crashes.  Specifically:

File->Import OL
Select Calendar
Click Import
Watch as thermometer increments to 100%
Click OK on dialog that says 2185 entries were read.
Close the Import dialog

CRASH!

I now have the ever so wonderful "Send/don't send info to M$oft" dialog.  

I did a search for this issue, and as usual, can't find anything about it.  I grabbed the 2.1.0 XP version of the Windoze apps, and the helper DLL's.  So I think I'm good there.  Any suggestions as to how to solve this?

Thx....

12

Linux Issues / Hotplug issue Slackware 10

« on: April 21, 2005, 12:55:36 am »

This may be relevant despite my gettting this working in CentOS 4.

I had to change the ifconfig and route lines to:

/sbin/ifconfig
/sbin/route

and the filename had to be usbnet, not usbdnet.

13

General Discussion / Sd Mounting Fun And Games

« on: April 20, 2005, 04:11:46 pm »

Ok... I know I tried this at some point during all of the fun I was having with this, but I now have the SD card working.  For whatever reason it appears the slide latch on the SD card was not fully pushed to "non-write protect mode".  I tried sliding this to writeprotect, and back, and it started working.  I guess Lexar just has a twitchy slide switch or somehow the Z was sliding it imperceptibly.  Makes me wish I could crack the case and just hardwire the switch to "write enabled" mode permanently.

14

General Discussion / Sd Mounting Fun And Games

« on: April 20, 2005, 02:43:58 am »

Ok... I"m at a loss.

Situation:
5500, Sharp 3.1, Lexar 1G SD, PNY 128M CF

I had the SD card able to mount and read/write data.  I had several IPK's installed on it.  Then I realized all of a sudden that I couldn't install anything to SD.  I just chalked it up to the usual "Must be installed in memory" routine.  However, today I noticed that I couldn't install ANYTHING to SD.  Then I noticed it was mounted read-only.  

So I search the forums and find several threads on "do an FSCK on the corrupt file-system and it should work".  

Ok... I did that, and no success.  I've reformatted the SD using my CentOS box.  I've formatted it in VFAT, and in EXT2 (4k blocks and 1k blocks).  The SD can be written from Windoze.  

Every time I install the card into the system it mounts read-only.  I can't mke2fs /dev/mmcda1 as the command always comes back saying the disk is read-only.

Dmesg returns:
# dmesg
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
EXT2-fs: Unrecognized mount option noatimei
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
cramfs: wrong magic
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Can't find a Minix or Minix V2 filesystem on device 3c:01.
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
MSDOS FS: IO charset utf8
VFS: Disk change detected on device mmcd(60,1)
VFS: busy inodes on changed media.
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
VFS: busy inodes on changed media.
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
VFS: busy inodes on changed media.
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
VFS: busy inodes on changed media.
 mmcda: mmcda1

Most of what dmesg spits out is a foreign language to me, so I don't know what it's telling me, nor what I can do to change it's attitude.

FSTAB has:
/dev/mmcda1     /mnt/card       vfat    rw,noatime,noauto,owner 0  0

The card is currently formatted as vfat, but using "auto" detect didn't change anything either.

Has my 5500 lost it's mind on how to mount SD?  I have a PNY 128M formatted vfat that doesn't even show up.

And no.... I don't have the write-protect tab switched to "LOCK".  

My faithful 5500 is not being so faithful at the moment, and I don't know how to make it any better.  

I was trying to move to Crow/Cacko, but every time I tried "fdisk /dev/mmcda" I would get "partition table is not writable".  However, it clearly is from CentOS fdisk.  I also got "Unable to mount mmcda1" from mke2fs from the Crow ROM setup.

What makes me think it is my 5500 losing it is that every once in awhile I would perform some magic and get the SD to mount rw.  I have been unable to determine what the sequence may be.

Can anybody give me a direction to pursue in fixing this?  I know I'm rambling a bit, as I'm a bit shell-shocked on all of this at the moment.

15

Software / Kde-pim/pi 2.1.0 Available!

« on: April 19, 2005, 01:17:36 pm »

First time KDE/PIM user here, so I have no experience with the tool.  

I grabbed the SharpROM package for my 5500 and installed every IPK.  However, Kopiemail complains that it needs "additional packages".  I looked in the release notes and didn't see anything indicating I needed anything other than the items in the zip file.  KA, KO, and KPWM all work, but the OM does not.  

Pointers to where I can get the missing piece?