Pdaxrom For C3000 (based On Beta1/beta3)

[danboid]

rui65:

You got mplayer working? I'd imagine you're running the Tetsu kernel aren't you? Does wifi work for you with Tetsu kernel?

I suppose that, after installing the bvdd module I could install a non-iwmmxt mplayer and run that under the b2 kernel but I'm absolutely certain I could run the iwmmxt accelerated mplayer under the last beta with stock kernel. Am I imagining that?

[jpmatrix]

hi
great job meanie ! i was hesitating between openBSD and openzaurus/GPE for my C3000 but i think none are yet user ready...
i tried your pdaxii13 and i had the same troubles as everybody here (calibration, wifi...)
calibration is ok after ts_calibrate, hang, reboot
but would someone post a simple wifi howto ?
thanks in advance!

[rui65]

rui65:

You got mplayer working? I'd imagine you're running the Tetsu kernel aren't you? Does wifi work for you with Tetsu kernel?

I suppose that, after installing the bvdd module I could install a non-iwmmxt mplayer and run that under the b2 kernel but I'm absolutely certain I could run the iwmmxt accelerated mplayer under the last beta with stock kernel. Am I imagining that?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147218\"][{POST_SNAPBACK}][/a][/div]

Yes : Tetsu's kernel.
Sorry I don't use Wifi, only a very classical CF Ethernet adaptor.

[kahm]

rui65:

You got mplayer working? I'd imagine you're running the Tetsu kernel aren't you? Does wifi work for you with Tetsu kernel?

I suppose that, after installing the bvdd module I could install a non-iwmmxt mplayer and run that under the b2 kernel but I'm absolutely certain I could run the iwmmxt accelerated mplayer under the last beta with stock kernel. Am I imagining that?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147218\"][{POST_SNAPBACK}][/a][/div]

Yes : Tetsu's kernel.
Sorry I don't use Wifi, only a very classical CF Ethernet adaptor.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147223\"][{POST_SNAPBACK}][/a][/div]

Interesting that you got a CF card working on the Tetsu kernel - Meanie's post and subsequent replies made me believe there'd be a problem with *all* CF cards...

[chrisluu]

I thought I'd give a quick rundown of my experience with pdaXii13. I started out with the base image and Tetsu kernel. It worked rather well for me, including my Socket CF Wifi card, meaning that the problems with mounting a CF card are purely module based in terms of loading the ide driver. BVDD in Mplayer worked fine for me out of the box. Unfortunately, I started getting the FS errors again. Basically when it happens, I can't do anything anymore. If by chance I have a console open when it happens, I can try to do things like "reboot" but I just get "bus error" or "I/O error." Since it seems like most other people aren't getting it, I'm now suspecting that it's a problem with my Ebook reader, Justreader. I just flashed with hdimage-custom so I'll see if I get the problem without installing Justreader.

For those that are giving suggestions for what default programs / settings to have in the hdimage, keep in mind that this hdimage-custom is Meanie's specific style / programs that he only posted so that we could see what he's got so far. Once you get things exactly as you like for a default installation, you can run his zbackup program and get a tgz of your specific default programs, which I think is awesome.

[Meanie]

Oh man, I've been busy. Assembled a dinner table and four chairs as well as a complete wardrobe all by myself

anyway, as some of you might have realised, the only image that is ready is hdimage-base.tgz. hdimage-full.tgz is still in the workings and well hdimage-custom.tgz seems all broken atm

anyways, i was hoping for those daring enough to test to make sure that the installer was working properly and easy enough to use (and had all the features you would need).  the base image is what really needs testing so we can have something stable and useful to build upon.
the custom image was kinda like a sneak preview for the very curious. i was in a bit of a hurry in my last post  had to rush and didn't explain everything clearly enough i guess.
so again, the aim of this release was to make sure everything in the base image works and also test out the two different kernels and see which one provides more stability.

please note that my site http://www.users.on.net/~hluc/myZaurus/pdaxii13.html describes pdaXii13 full while I have just released pdaXii13 base for testing (which is a trimmed down version and does not have everything that is in the full version, ie updated mplayer...)

it seems that the cf card problem is only isolated to cf flash not mounting with the tetsu kernel. this might get fixed if i manage to compile ide-cs.o which i am havig problems with... the old beta1 kernel seems to have this module correctly compiled into the kernel while the tetsu kernel apparently has this module compiled in as well because it can access the microdrive but spews on the second cf flash card. interestingly, the other cf card will work if you boot with it inserted and you can mount and unmount it several times and it will continue to work until you eject it. then it won't ever work again until you reboot

so if the old kernel works fine, performance wise and stability wise, then maybe just drop the tetsu kernel and get on with other important stuff like the apps...

please test more between the differences of tetsu and old kernel...

[danboid]

I'm surprised that Chrisluu had no problems with mplayer bvdd- I've tried all the combinations of kernels and images now but I still haven't got bvdd working properly. I even tried running atty's mplayer-bvdd (not iwmmx one) with the bvdd module but that gave a small vertically aligned video on the left hand side of the screen.

Thankfully the base hdimage doesn't have the calibration or logging out of X problems of the custom image. I was also pleased to see suspend working under all combinations and the updated sd-driver was working in both images.

Neither CF memory cards or my wifi card work under the tetsu kernel but both work fine under b2 kernel.

bvdd video is broke under both kernels under either hdimage for me. Even the tetsu kernel doesn't have bvdd support compiled in. I managed to get the bvdd module to load (with tainting error) under b2 but strangely enough not under tetsu which said the module wasn't an ELF file.

[danboid]

What I mean by bvdd video is editing /usr/share/mplayer/mplayer.conf to end with

vo = bvdd
vm = yes

or adding the -vo bvdd option to your mplayer command. If anyone can get bvdd working under the b2 kernel then please tell me how you did it.

If you do end up recompiling a kernel Meanie please don't forget the iwmmx extensions as these, along with bvdd, aren't in the b2 kernel you posted.

Looks like I've just been hit with a bit of the dreaded file corruption myself in the form of io errors on the console when trying to view a directory but this has occured whilst I've been experimenting with the tetsu kernel. I'm going to try flashing anew with the b2 kernel and the hdimage base this time with no tetsu excursion, see how it goes.

EDIT

As i said i got an i/o error off my MD so I've just tried twice to install anew with the b2 kernel and the core image. Now I don't know if this is just a combination that the installer doesn't like or what but now when I try to boot it gets as far as 'Loading Driver for Microdrive' then I get

cardmgr[71]: 'ide-cs' already bound to socket 1
Internal harddrive is /dev/hdc1
e2fsck- no such device /dev/hdc1
run fsck manually on hdc1

The boot process ends there and I'm left with a prompt. Shouldn't it be trying to boot /dev/hda1 anyway? How has this happened?

[relapse808]

I can go back to the tetsu kernal and do more testing.  I personally think its faters that the B2 kernal, even in bootup.  I ditched it so quickly because I couldnt get the wifi to work.  I would like to see PDAXROM using the tetsu special kernal.

[danboid]

Can anybody explain this MD error I'm getting? I've booted into D+M and ran a fsck on hda1 and it passed with no errors. As I said, I tried twice to flash the combination of b2 kernel and the core hdimage. The first time I did it I tried booting it for the first time with my wifi CF card inserted. When I got that error I tried flashing the same combination but made sure that no CF card was inserted on first boot after install but the same error occured (no /dev/hdc).

I'd be happy if someone could tell me why this is happening or how to fix it. I'd also like to hear from anyone else who has tried this combination out and what your findings were.

[iczer3]

Dear Meanie,

I have installed the pdaxii13 on my C3000. After installation /media/realroot was
not created in my built-in microdrive. After creating it manually and reboot it
is ok.
The one problem I have is that if I insert a microdrive into the CF slot then
it won't boot sometimes, with error saying partition error on hda1.

Will do further testing.

BR,

Felix.

[danboid]

iczer3:

That's it! I made a dir called /media/realroot then rebooted and that put an end to my '/dev/hdc not found' error- thanks for pointing that out!

Anyone got bvdd (and iwmmxt pref. too) working under the b2 kernel?

[jpmatrix]

welcome back meanie !

well, do you mean (!) we should only install the base tgz and report the bugs we find ?
it seems all packages are removed from tyrannozaurus web site. are you preparing new uploads ?

[relapse808]

Can anybody explain this MD error I'm getting? I've booted into D+M and ran a fsck on hda1 and it passed with no errors. As I said, I tried twice to flash the combination of b2 kernel and the core hdimage. The first time I did it I tried booting it for the first time with my wifi CF card inserted. When I got that error I tried flashing the same combination but made sure that no CF card was inserted on first boot after install but the same error occured (no /dev/hdc).

I'd be happy if someone could tell me why this is happening or how to fix it. I'd also like to hear from anyone else who has tried this combination out and what your findings were.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147312\"][{POST_SNAPBACK}][/a][/div]

Is this the same error I am getting when I sometimes boot the device?  During bootup it tells me that HDA1 hasnt been checked for errors and attempts to do so.  It then drops me into the console telling me to run fsck manually.  I run FSCK on /dev/hda1 and then reboot and it will work again.  This issue is a annoying one.

[jpmatrix]

same trouble as danboid:
i installed base tgz and b2 kernel
first boot: it complains about hdc1:

checking /dev/hdc1
e2fsck : no such device or address...

perhaps it is because i have one 4gb partition ?
i try the standard partition scheme

edited: same problem with standard partitioning...
help!

ps: all worked with the custom image...should i go back to it ?