Messages

1

C1000/3x00 General discussions / Bricked It

« on: February 26, 2006, 05:04:53 am »

if you can get to the diagnostic menu then your not in that big of trouble.  I think trisoft has the instructions that might cover this.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Any idea where I can find those instructions?  I looked on the site and can't find anything.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=116113\"][{POST_SNAPBACK}][/a][/div]

HAHAHA IT IS A-LIVE!!!!!

Saved my ass:
[a href=\"http://www.xlfag.com/zaurus/]http://www.xlfag.com/zaurus/[/url]

2

C1000/3x00 General discussions / Bricked It

« on: February 26, 2006, 12:03:16 am »

if you can get to the diagnostic menu then your not in that big of trouble.  I think trisoft has the instructions that might cover this.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=116102\"][{POST_SNAPBACK}][/a][/div]

Any idea where I can find those instructions?  I looked on the site and can't find anything.

3

C1000/3x00 General discussions / Bricked It

« on: February 25, 2006, 05:07:51 pm »

I've bricked my zaurus.  The only thing I can boot to is the Diagnostic menu.  Anyone know how to fix this?  I wanted to sell this thing on eBay so I was trying to reflash it with a more standard image.   I had the pivot_root pdaxrom installed and I ran into trouble when I reflashed.

4

Zaurus - pdaXrom / Problem With Shutdown

« on: January 23, 2006, 04:29:42 am »

When I try to reboot from the CLI the system hangs after killing the CF services instead of cleanly rebooting.  Suspending the machine exhibits the same problem.  I think something needs to be modified to tell the CF services to only kill the wifi card instead of the wifi card and the hd, but I'm not sure where to look.

Any ideas?

I'm using 1.1.0beta1 with pivotroot
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111761\"][{POST_SNAPBACK}][/a][/div]

*bump*

Nobody else is seeing this behavior after installing pivot_root & KDE?

5

Zaurus - pdaXrom / Problem With Shutdown

« on: January 20, 2006, 07:51:40 pm »

When I try to reboot from the CLI the system hangs after killing the CF services instead of cleanly rebooting.  Suspending the machine exhibits the same problem.  I think something needs to be modified to tell the CF services to only kill the wifi card instead of the wifi card and the hd, but I'm not sure where to look.

Any ideas?

I'm using 1.1.0beta1 with pivotroot

6

Zaurus - pdaXrom / Kde 3.5

« on: January 18, 2006, 05:37:00 am »

That indeed did the trick. I was trying to install the earlier version of it. Thanks... booting presently biggrin.gif

Does this mean that the squashfs modules I compiled for 2.4.20 work?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111417\"][{POST_SNAPBACK}][/a][/div]

I installed the "squashfs_2.2r2_armv5tel.ipk" package I found on the other thread.  If that is the package you're refering to, then yes, it seems to work.  To be honest it's all a bit beyond me so far... I'm just struggling to keep my head above water here.

7

Zaurus - pdaXrom / Kde 3.5

« on: January 18, 2006, 04:55:43 am »

There are two squashfs packages, one for 2.4.18 kernel (mainly Cxx0 and SL-xk)) from the regular feed and another one newly complied by pgas for 2.4.20 kernel (Cxk series) whiich can be found earlier in this thread and in the contrib feed.  Dunno if this helps.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111408\"][{POST_SNAPBACK}][/a][/div]

That indeed did the trick.  I was trying to install the earlier version of it.  Thanks... booting presently  

8

Zaurus - pdaXrom / Kde 3.5

« on: January 17, 2006, 11:53:33 pm »

Can you see it in /usr/lib/kde/kde3.5/bin ?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

That directory is empty.  Something obviously didn't take.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111348\"][{POST_SNAPBACK}][/a][/div]

Which KDE packages are you using?  If you're using the "Lite" squashfs version, make sure that you've installed the latest symlinks package from here:  [a href=\"http://mail.pdaxrom.org/contrib/misc/]http://mail.pdaxrom.org/contrib/misc/[/url]
kstartupconfig should be right in /usr/lib/kde/de3.5/bin and symlinked to /usr/lib/kde/bin.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111362\"][{POST_SNAPBACK}][/a][/div]

i think the problem is that I don't have squashfs support installed, but when I try to install the ipk I get a bunch of errors.

9

Zaurus - pdaXrom / Kde 3.5

« on: January 17, 2006, 06:06:56 pm »

Can you see it in /usr/lib/kde/kde3.5/bin ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111347\"][{POST_SNAPBACK}][/a][/div]

That directory is empty.  Something obviously didn't take.

10

Zaurus - pdaXrom / Kde 3.5

« on: January 17, 2006, 03:38:09 pm »

I'm getting an error.  It can't find kstartupconfig.  I looked in the dir its supposed to be in but its not there.

Any ideas what I botched?

11

Zaurus - pdaXrom / Fvwm-pdaxrom 0.4.x

« on: January 15, 2006, 10:24:19 pm »

Hmm, it seems that you are using a different version of fvwm. Try installing the one in the 1.1.0beta1 feed. Your one searches for config files in /share/fvwm, the one in the feed searches in /usr/share/fvwm. Or, you can move .fvwm2rc from /usr/share/fvwm to /share/fvwm!

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

genius... for some reason the .rc was in the wrong place.  no idea why, but it seems to have fixed the problem.

Thanks so much!  Great work!

12

Zaurus - pdaXrom / Fvwm-pdaxrom 0.4.x

« on: January 15, 2006, 05:30:17 pm »

I'm having a problem getting the menus and toolbar to work.  I get the basic menu and no window management.  I've uninstalled and reinstalled fvwm_pdaxrom a number of times, but no luck.  mbsession and icewmsession both work flawlessly.  I have no idea what the problems is.

Any suggestions?

I do notice that when I run startx I get the folowing error.


[FVWM][main]: <<ERROR>> Cannot read startup file, tried:
        /home/root/.fvwm/.fvwm2rc
        /home/root/.fvwm2rc
        /share/fvwm/.fvwm2rc
        /share/fvwm/system.fvwm2rc
        /etc/system.fvwm2rc

13

Zaurus - pdaXrom / Kdepimpi For Rc12 On 3100

« on: January 10, 2006, 06:06:28 am »

Hi All,

I still have the prob with kapi complaining about not existing libmicrokabc_sharpdtm.so and libmicrokabc_olaccess.so. The trick with symbolic link in /opt/kdepimpi seems to not work with beta1 (the is no /opt/kdepimpi, it's /opt/kdepim-2.2.7, ok). I created the symbolic links as described above, but kapi still cant find this libs.
Any idea to solve this is very appricated

Thanks a lot in advance

Best regards

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

There is nothing wrong if you get these messages on pdaXrom.
Theses libs are not available for pdaXrom.

And libmicrokabc_olaccess will never be available for any platform ... I have to remove that message ...

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

I don't have an /opt directory and when I try to create one it tells me the filesystem is read-only.  I think I missed something when I installed the rom maybe or do I need to remount it rw and create a symlink?

Thanks.


------------
SL-C3000 : Linksys WCF12 : 128mb SD
pdaXrom rc12

14

Zaurus - pdaXrom / Pdaxrom Rc12 For C3000 Beta 1

« on: January 06, 2006, 05:31:48 am »

 
I thought I did but I'm 95% sure I must have screwed up the symlink.  Checking it out now.


The link is there and it seems to be correct.  I'm totally at a loss.

EDIT: (after hours of reboot) somewhat aggravated too...
 

DOUBLE EDIT:  I reflashed and seem to have fixed the problem but now bt appears to be broken and everything I install quits because it can't find libstdc+ which is already installed... I've had enough for one night.

15

Zaurus - pdaXrom / Pdaxrom Rc12 For C3000 Beta 1

« on: January 06, 2006, 04:56:57 am »

Did you follow this howto right ? (the modules don't go in the good dir so you'll have to move or link them after install)
The free space error during boot time is "normal" (you're not the only one the experience this one and I hope to fix it for next beta)
 
I thought I did but I'm 95% sure I must have screwed up the symlink.  Checking it out now.

Really great Rom you have here.  All the best with the development.  If I can help out (I doubt it cause I'm 99% tard) I certainly will.

Cheers!