Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Franky G

Pages: [1] 2 3
1
Angstrom & OpenZaurus / Openzaurus And Intellisync 1.43e
« on: December 23, 2004, 06:04:35 pm »
What reads the error message?

What happens when you hit sync button on the cradle?

2
Angstrom & OpenZaurus / Oz Synchronisation
« on: December 11, 2004, 08:07:25 am »
Violator,

please see the postings here: https://www.oesf.org/forums/inde...topic=7300&st=0
That's the way many people got it to work.

Frank

P.S.: I am using "Opie" as the sync software under tab "sync" in settings (not Qtopia as suggested in the other post). This is working much faster for me. Just a tip to try it out.

3
Angstrom & OpenZaurus / Oz Synchronisation
« on: December 09, 2004, 12:02:08 pm »
Did you set up Security --> Sync under Settings correctly?

4
Angstrom & OpenZaurus / CF card fails to mount on OZ 3.5.1
« on: October 16, 2004, 02:49:46 pm »
Well, just to let you know and for others who also encountered this behaviour, I think I got it to work now.

Reading the messages that fly over the screen while booting (after buying myself a magnifier!), I stumbled across a message that read "invalid mount option: user" or the like.

So, I changed "/etc/fstab" to the following:
Code: [Select]
/dev/mtdblock4  /       jffs2   defaults        1  1
proc            /proc   proc    defaults        0  0
#/dev/hda1      /mnt/cf auto    defaults,sync,noatime,user,exec,suid,gid=100,umask=0002 0  0
/dev/mmcda1     /mnt/card       auto    defaults,sync,noauto,noatime,user,exec,suid     0  0
tmpfs           /var    tmpfs   defaults        0  0

# we use a non-volatile ramdisk, see /etc/init.d/ramdisk
#tmpfs          /mnt/ram        tmpfs   defaults        0  0

/dev/hda1       /mnt/cf         auto defaults 0 0
/dev/hda1  auto defaults 0 0

Original line 3 got commented out (/dev/hda1      /mnt/cf auto    defaults,sync,...). One of the options given at the end of this line caused the card to not get mounted. Dunno which one it was yet. After that I changed the last line of the old fstab (see above) to "/dev/hda1       /mnt/cf         auto defaults 0 0". Now, after rebooting or after re-inserting the cf card it automounts!

What I don't understand is why "/dev/hda1  auto defaults 0 0" is always appended to "/etc/fstab" after rebooting if it is not existing in the file. Again, it shows up in my fstab (last line above), but doesn't seem to cause any trouble.

Is this a bug? My problem only? Any one else experienced this?

Peace,
Frank

5
Angstrom & OpenZaurus / CF card fails to mount on OZ 3.5.1
« on: October 16, 2004, 09:54:58 am »
Quote
install e2fsprogs-fsck

or turn off DO_FSCK line in /etc/pcmcia/ide.opts
Thanks Hrw,
installing e2fsprogs-fsck didn't help and DO_FSCK line in /etc/pcmcia/ide.opts was already disabled/commented out (#) by default on my 5500.
Funny thing is I cannot "mount /mnt/cf" (giving error "mount: Mounting /dev/hda1 on /mnt/cf failed: Invalid argument").
But I can "mount /dev/hda1 /mnt/cf".

Having NOT mounted the cf card
"# cat /etc/fstab" outputs:
Code: [Select]
/dev/mtdblock4  /       jffs2   defaults        1  1
proc            /proc   proc    defaults        0  0
/dev/hda1       /mnt/cf auto    defaults,sync,noatime,user,exec,suid,gid=100,umask=0002 0  0
/dev/mmcda1     /mnt/card       auto    defaults,sync,noauto,noatime,user,exec,suid     0  0
tmpfs           /var    tmpfs   defaults        0  0

# we use a non-volatile ramdisk, see /etc/init.d/ramdisk
#tmpfs          /mnt/ram        tmpfs   defaults        0  0

But having mounted the cf card
"# cat /etc/fstab" outputs:
Code: [Select]
/dev/mtdblock4  /       jffs2   defaults        1  1
proc            /proc   proc    defaults        0  0
/dev/hda1       /mnt/cf auto    defaults,sync,noatime,user,exec,suid,gid=100,umask=0002 0  0
/dev/mmcda1     /mnt/card       auto    defaults,sync,noauto,noatime,user,exec,suid     0  0
tmpfs           /var    tmpfs   defaults        0  0

# we use a non-volatile ramdisk, see /etc/init.d/ramdisk
#tmpfs          /mnt/ram        tmpfs   defaults        0  0
/dev/hda1  auto defaults 0 0
(note additional last line!)

"# logread" gives some additional info:
Code: [Select]
Oct 16 13:50:27 collie user.debug kernel: VFS: Disk change detected on device ide0(3,1)
Oct 16 13:50:27 collie user.info kernel:  hda1
Oct 16 13:50:27 collie user.debug kernel: VFS: Disk change detected on device ide0(3,1)
Oct 16 13:50:27 collie user.info kernel:  hda1
Oct 16 13:50:27 collie user.warn kernel: EXT2-fs: Unrecognized mount option user
Oct 16 13:50:27 collie user.debug kernel: VFS: Disk change detected on device ide0(3,1)
Oct 16 13:50:27 collie user.info kernel:  hda1
Oct 16 13:50:27 collie user.debug kernel: VFS: Disk change detected on device ide0(3,1)
Oct 16 13:50:27 collie user.info kernel:  hda1
Oct 16 13:50:27 collie user.err kernel: cramfs: wrong magic
Oct 16 13:50:27 collie user.debug kernel: VFS: Disk change detected on device ide0(3,1)
Oct 16 13:50:27 collie user.info kernel:  hda1
Oct 16 13:50:27 collie user.debug kernel: VFS: Disk change detected on device ide0(3,1)
Oct 16 13:50:27 collie user.info kernel:  hda1
Oct 16 13:50:27 collie user.warn kernel: VFS: Can't find a Minix or Minix V2 filesystem on device 03:01.
Oct 16 13:50:27 collie user.debug kernel: VFS: Disk change detected on device ide0(3,1)
Oct 16 13:50:27 collie user.info kernel:  hda1
Oct 16 13:50:27 collie user.debug kernel: VFS: Disk change detected on device ide0(3,1)
Oct 16 13:50:27 collie user.info kernel:  hda1
Oct 16 13:50:27 collie user.warn kernel: FAT: bogus logical sector size 0
Oct 16 13:50:27 collie user.warn kernel: VFS: Can't find a valid FAT filesystem on dev 03:01.
Oct 16 13:50:27 collie user.debug kernel: VFS: Disk change detected on device ide0(3,1)
Oct 16 13:50:27 collie user.info kernel:  hda1
Oct 16 13:50:27 collie user.debug kernel: VFS: Disk change detected on device ide0(3,1)
Oct 16 13:50:27 collie user.info kernel:  hda1
Oct 16 13:50:27 collie user.debug kernel: jffs2: attempt to mount non-MTD device 03:01

So far so good. But how can I get the cf card to mount at boot time?  

Thanks,
Franky G

6
Angstrom & OpenZaurus / CF card fails to mount on OZ 3.5.1
« on: October 15, 2004, 04:28:34 pm »
Hi there,

I have two cf cards which I both use on my 5500.

The first one is a 128 MB cf card formatted with fat32.
The other card is a 512 MB cf card formatted with ext2.

The 128 MB card works well for me. Automount on reboot etc.
The 512 MB used to work well for me under OZ 3.3.5.

But under OZ 3.5.1 I seem to not be able to mount the card neither automatically nor manually. I tried ext2 and ext3 -- no luck.

Interestingly formatting the card with fat32 the card mounts after reboot or by hand. Formatting with mkfs.minix this works, too (aside from giving me only 64 MB with minix which I assume is normal).

Is this known?

Frank

7
Angstrom & OpenZaurus / Still "Sync Connection Alert" Annoyance
« on: October 09, 2004, 02:29:30 pm »
Finally I am back with OZ 3.5.1 Opie. Yay!

Sync is working perfectly now and FAST!
Thanks to everybody for tracking down this issue (and many other related problems as well).

Franky G  

8
Angstrom & OpenZaurus / Security / Authentication locked me out
« on: October 09, 2004, 09:52:21 am »
Quote
I tried to enable the security in OPIE 1.1.6 under the assumption that my root password would get me back in after suspending.  I couldn't get back in at all - everything I tried was rejected ('Try Again...').  I had assumed that not having any plugins listed merely meant that my password was the only way back in.  If a plug-in is required, I would have thought that OPIE would not allow me to enable security without one.  Is there something I missed, or is this a bug?
Woops, I also ran into this problem just now!  
Cyboreal, did you find a solution besides re-flashing?

9
Angstrom & OpenZaurus / Still "Sync Connection Alert" Annoyance
« on: October 08, 2004, 08:13:39 pm »
Oh, I forgot to say that having "Qtopia 1.7" selected as the sync software in "security app", my datebook app needs to be reloaded (close and start again) to show the changes made by syncing with Outlook. Having chosen "Opie 1.0" as the sync app, changes are shown at once (no reload needed).

Franky

10
Angstrom & OpenZaurus / Still "Sync Connection Alert" Annoyance
« on: October 08, 2004, 07:58:50 pm »
Quote
After looking at the source code (looks like they need to make a small change to allow connections for a period of time), the fix is really really simple...

Choose Qtopia 1.7 as your sync software in the Security app. It will still sync with Intellisync and requires ONE click of Allow.

I can't believe no one else has tried this....
WTF! Now it's working... So, papercrane, you're my personal hero now

I also tried security app settings for "Qtopia 1.7" and "Opie 1.0" before, but it wouldn't work for me (EDIT: it appeared that no connection could be established via Intellisync). Maybe I did anything else wrong or I got into trouble caused by another oddity. Please see:
zaurus sometimes disconnects from desktop

Currently I am running Hentges ROM OZ3.3.6-pre1/Opie 1.1.4 on my 5500. I've noticed that having chosen "Opie 1.0" for "sync software" in the security app on my 5500, sync process is any faster than having chosen "Qtopia 1.7".

Interestingly I do not have to confirm "Allow" anymore (EDIT: not even only ONE time). Neither using "Qtopia 1.7" nor using "Opie 1.0" setting in security app.  

11
Angstrom & OpenZaurus / Still "Sync Connection Alert" Annoyance
« on: October 08, 2004, 04:36:11 pm »
Btw, is this problem only related to windows and OZ?
Don't linux users encounter this glitch?

12
Angstrom & OpenZaurus / Still "Sync Connection Alert" Annoyance
« on: October 08, 2004, 04:34:39 pm »
Quote
One would think that this could easily be disabled somehow....
That's excactly what I am thinking.

Can't any of the developers give us a tiny, tiny, tiny hint related to that problem?

I think many potential OZ/Windows users will be scared by that and stay with older OZ versions or stall with Sharp's ROMs. Just my 5 cent.

Franky G

13
Angstrom & OpenZaurus / PIM Importing/Exporting
« on: October 08, 2004, 03:54:54 pm »
Quote
basically, i just need some easy way of getting all my contact info into OPIE's address book -- and I'm using the new version of the Sharp ROM on my SL-5500 -- which uses different communication drivers and all that fun stuff.  I've had difficulty uninstalling the drivers and then reinstalling the old sharp drivers that use tcp/ip to connect.  So i was wondering if there was any manual way to do it.
For Sharp's ROMs I can't tell you.

But if you consider switching to latest OZ-OPIE image, it's easy as 1 - 2 - 3.
As long as you have all your contacts in Outlook, after syncing OPIE will hold a copy of all your contacts as well.

14
Angstrom & OpenZaurus / PIM Importing/Exporting
« on: October 08, 2004, 03:40:45 pm »
Quote
Well I think the time has come to migrate from the Sharp ROM to an OpenZaurus Rom.  My question is, is there any way to export data from qtopia desktop or outlook to where i can import it into my PIMs on OPIE?
Umm, how do you mean "export"?

Possibly you mean syncing between Outlook/Qtopia-Desktop and your Z device via Intellisync?

15
Angstrom & OpenZaurus / intellisynch and OZ 3.5.1
« on: October 08, 2004, 01:09:00 pm »
Quote
Do you have this fixed now? If you don't there is a patch available at http://openzaurus.org/official/unstable/3.5.1/upgrades/
Oh, thanks.

I switched to latest Hentges earlier because of given problems I noticed (timezomes, connection alarm, sync-to-wrong-dir). But Hentges also has that connection alert bug and sync-to-wrong-dir "problem" (I think because both distros are based on latest OE; or maybe OPIE is responsible for it!?). But soon I will re-flash to OZ-OPIE 3.5.1 again

Does anyone know if there is a workaround or upgrade to stop connection alert problem?  

Franky G

Pages: [1] 2 3