Messages

1

Deals and Great Z Buys / Sell Poodle 5600+wlan+cfu1

« on: November 15, 2006, 01:57:59 pm »

Item no 140053257876,140053262922,140053260861.
cheers

2

OpenZaurus/Opie/Qtopia / No Appropriate Decoders

« on: November 03, 2006, 02:19:10 pm »

Hi, I was watching a movie yesterday, then got a Segfault error and when I tried to load the movie again, I get sorry, no appropriate decoders found for this file.
It's an xvid video and I didn't change anything.
Should I reinstall the videos package?
I've tried to reinstall the qtopia with the format and update option in the maintenance menu but same problem.
any ideas as where I should start the troubleshooting?
Thanks

3

OpenZaurus/Opie/Qtopia / Segfault Error 11 With Videos

« on: October 27, 2006, 03:25:41 pm »

Hi, I got the latest qtopia installed and trying to play some xvid videos with ac3 music.
I'm using 20 fps, resolution about 320 and mono 56kps audio.
@ about halt the song, it hangs n gives an error 11 segfault.
then if I rerun the program, it's fine for couple of minutes and hangs again.
tried music and it doesn't crash

Is there a way to track exactly to what the problem is due to with a certain log.
I've verified in logread but it's not recording any errors.

I'm not sure if it's due to the problem but I've tryed to use the special kernel with 471 mhz http://www.zaurususergroup.org/UpDownload+...t-lid-188.phtml but I'm not sure that it worked (is there a way to know if the xscale is @ 471 MHz? beside answering it should be faster)
thanks

4

Angstrom & OpenZaurus / Need Troubleshooting Help For Qclockchange

« on: October 25, 2006, 01:23:07 am »

Hi, I'm trying to use qclockchange but it doesn't open. What would be the first troubleshooting step for this kind of issue?
Thanks

5

OpenZaurus/Opie/Qtopia / Backlight Doesn't Turn On After Suspend

« on: November 17, 2005, 02:38:12 pm »

Hi, I got a weird problem: After my poodle turn in non-suspend mode, the backlight doesn’t turn on automatically. I got to click on the light icon in taskbar n move it down, than up.
It’s not a big deal but it happens each time it goes in suspend.
Thanks

6

Angstrom & OpenZaurus / Hentges / Konqueror Sigsegv Woes

« on: November 17, 2005, 02:07:38 pm »

You're not using liquid as a style or are you?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=103063\"][{POST_SNAPBACK}][/a][/div]

Hi, I got the same issue. Some site works, others not. Same error message with sigsegv. I used liquid as apparence n switch over to others but I still get the same error message.
On other threads, there's posting about changing cache size for opera n replacing opera.ini file. Is there a workaround for konqueror?
Thanks

7

Angstrom & OpenZaurus / Module Usbcore.o Not Available. Why?

« on: November 14, 2005, 02:10:14 pm »

Ah, sorry, I mis-understood.

So you have OE setup and working fine? Have you built something to test that it's working okay (try 'bitbake virtual/kernel')

Now you want to build the kernel modules & build the cfu1 driver I take it?


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

Yes, that's right, I'm not too sure where to start for the built of kernel n module.

8

Angstrom & OpenZaurus / Module Usbcore.o Not Available. Why?

« on: November 12, 2005, 01:26:55 pm »

I'm glad you've got it sorted - you don't need to post an entire 'ROM', just the ipks for the kernel modules will be enough for others to install and use.


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

No it's not sorted out, I just need the other steps that you were talking about.

9

Angstrom & OpenZaurus / Module Usbcore.o Not Available. Why?

« on: November 11, 2005, 04:06:13 pm »

Hi, I did it.
So...  what's next? It seems that a lot of people needs those steps. Asa I'm finished with it, I'll post the new rom with usbcore module for the 5600
Cheers

Get OE setup (see http://openembedded.org -> wiki -> GettingStarted), then I'll run you through it,


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

10

Angstrom & OpenZaurus / Cannot Get Socket Wifi Card To Work Under Oz 3.5.3

« on: September 19, 2005, 07:54:26 pm »

Copied/Pasted from another topic about this (although that topic seems to be quite dead)

Well, first of all, those truncated LTV records are consistent with what I'm seeing. I can also run wellenreiter without problem, but lock up the moment I touch the opie network app or iwconfig

my MAC is also scrambled, but some of the octets are recognizable. But all of our addresses here SHOULD be starting with 00, and they're not. So something is definitely borken™

Now let's have a look at this dmesg log, specifically the names of the RIDs that are failing

STAIdentity (I'm betting the firmware revision is NOT 18-thousand some odd number, just a hunch)
hermes @ IO 0xf6000000: Truncating LTV record from 129544 to 8 bytes. (rid=0xfd20, len=0xfd05)
eth0: Station identity 0002:0001:4920:2000
eth0: Looks like a Lucent/Agere firmware version 18720.8192
eth0: Ad-hoc demo mode supported
eth0: IEEE standard IBSS ad-hoc mode supported
eth0: WEP supported, 104-bit key

cnfOwnMACAddress (note this is where the MAC is failing)
hermes @ IO 0xf6000000: hermes_read_ltv(): rid (0xfc01) does not match type (0x5e00)
hermes @ IO 0xf6000000: Truncating LTV record from 129030 to 6 bytes. (rid=0xfc01, len=0xfc04)
eth0: MAC address 14:1C:01:00:20:49

cnfOwnName (not really sure what this value should be, but chances are "m I" is going to end up being wrong. Quick google shows me this is probably trying to set "Prism I")
hermes @ IO 0xf6000000: hermes_read_ltv(): rid (0xfc0e) does not match type (0x7200)
hermes @ IO 0xf6000000: Truncating LTV record from 129058 to 34 bytes. (rid=0xfc0e, len=0xfc12)
eth0: Station name "m I"

ChannelList
hermes @ IO 0xf6000000: hermes_read_ltv(): rid (0xfd10) does not match type (0x72ff)
hermes @ IO 0xf6000000: Truncating LTV record from 129538 to 2 bytes. (rid=0xfd10, len=0xfd02)

cnfSystemScale
hermes @ IO 0xf6000000: hermes_read_ltv(): rid (0xfc06) does not match type (0x72ff)
hermes @ IO 0xf6000000: Truncating LTV record from 129022 to 2 bytes. (rid=0xfc06, len=0xfc00)

RTSThreshold
hermes @ IO 0xf6000000: hermes_read_ltv(): rid (0xfc83) does not match type (0x722b)
hermes @ IO 0xf6000000: Truncating LTV record from 129026 to 2 bytes. (rid=0xfc83, len=0xfc02)

cnfDefaultKey1
hermes @ IO 0xf6000000: hermes_read_ltv(): rid (0xfc25) does not match type (0x722b)
hermes @ IO 0xf6000000: Truncating LTV record from 129022 to 2 bytes. (rid=0xfc25, len=0xfc00)

cnfMaxSleepDuration
hermes @ IO 0xf6000000: hermes_read_ltv(): rid (0xfc0c) does not match type (0x7264)
hermes @ IO 0xf6000000: Truncating LTV record from 129026 to 2 bytes. (rid=0xfc0c, len=0xfc02)

cnfPMHoldoverDuration
hermes @ IO 0xf6000000: hermes_read_ltv(): rid (0xfc0d) does not match type (0x7264)
hermes @ IO 0xf6000000: Truncating LTV record from 129026 to 2 bytes. (rid=0xfc0d, len=0xfc02)
eth0: ready
eth0: index 0x01: Vcc 3.3, irq 39, io 0xf6000000-0xf6000047

I also doubt each of these messages is supposed to be in excess of 128k.
I'm no kernel debugger here, but let's take a look at the MAC address record, for one:

hermes @ IO 0xf6000000: Truncating LTV record from 129030 to 6 bytes.

That makes sense. A MAC address should be 6 bytes long, not 129030. So it appears that we are doing the correct thing by truncating these records, but what we need to find out is why these records are over one hundred thousand bytes long to begin with.

Now, it appears that hermes.c defines the hermes_read_ltv function, which is called by orinoco.c - so that PROBABLY means that orinoco.c is doing Something Wrong™ or is being passed bad data from spectrum_cs.

It might be worthwhile checking what paramaters we can pass to these modules at load time, but gut feeling here is that these modules will need to be recompiled.

EDIT:
Looking at the following:

The other weird part is the mis-interpretation of the MAC address, it is really:
MAC 00 A0 F8 5E 14 1C

instead of the
MAC address 14:1C:01:00:02:88 that is shows above

We see that it seems to be getting the last 2 bytes of the MAC correct, but setting them as the FIRST two bytes in software (the rest is probably junk data).
Also noticing that in the cnfOwnName record, it's getting the last three bytes ("m I") correct. Presumably, it's getting the last four, since the fourth would be a null terminator - which is why we probably don't see any junk data after the "I".

I'm not really sure what this tells us about the driver itself, but it's possible that memory addresses are being shifted/transposed here, which may also have something to do with the length of these LTV records being horribly, horribly WRONG (ie. the variable that stores the record length isn't pointing at record length data).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=96335\"][{POST_SNAPBACK}][/a][/div]

Ya, I saw this post but it all sounds greek to me loll.

11

Angstrom & OpenZaurus / Module Usbcore.o Not Available. Why?

« on: September 19, 2005, 12:55:29 pm »

You'll need to modify your defconfig file (called defconfig-poodle in packages/linux/openzaurus-pxa_2.4.18-rmk7-pxa3-embedix20031107 I think) to add the appropriate lines - see my shepherd patch, then patch the kernel (see below) re-build the kernel so that usbcore is built.

Message: 1
Date: Fri, 11 Feb 2005 15:59:14 -0000
From: Simon Pickering <S.G.Pickering@bath.ac.uk>
Subject: [Oe] Proposed patch to enable usbcore.o (and other usb)
   module build
To: oe@handhelds.org
Message-ID: <200502111601.aa27442@bath.ac.uk>
Content-Type: text/plain;   charset="us-ascii"

I submitted the driver for the REX-cfu1 usb host CF card earlier today. It needs the usbcore.o module to run.

I have modified the defconfig-shepherd (via make menuconfig) to produce some USB related modules (I just went through and clicked on anything that looked interesting). The patch is here:
http://students.bath.ac.uk/enpsgp/Zaurus/d...g-shepherd.diff

The kernel also needs a patch to remove an ifneq check I'd guess comes directly from the Sharp code, otherwise usbcore.o isn't built.

Lines 45-47 of drivers/usb/Makefile are as follows:

ifneq ($(CONFIG_ARCH_SHARP_SL),y)
obj-$(CONFIG_USB)  += usbcore.o
endif

To make usbcore build I simply removed the ifneq/endif from around the middle line.

Patch here: http://students.bath.ac.uk/enpsgp/Zaurus/e...e-usbcore.patch

I don't know why this ifneq is in there, and hopefully this patch won't break anything (the kernel and modules all built correctly, but I've only tested the usbcore.o module).

Cheers,


Si

You'll also need to build cfu1 for your kernel/machine combo. This is in OE:

Message: 5
Date: Fri, 11 Feb 2005 11:21:44 -0000
From: Simon Pickering <S.G.Pickering@bath.ac.uk>
Subject: [Oe] cfu1-driver (ratoc CF usb host card driver)
To: oe@handhelds.org
Message-ID: <200502111123.aa26043@bath.ac.uk>
Content-Type: text/plain;   charset="us-ascii"

Builds, and works fine on my Shepherd.

http://students.bath.ac.uk/enpsgp/Zaurus/cfu1-driver.tar.gz

Requires usbcore.o (kernel-module-usbcore) to run (this is in the bb as an RDEPENDS), defconfig patch and kernel patch to follow to create this module as part of openzaurus-pxa_2.4.18-rmk7-pxa3-embedix20031107.bb

Cheers,


Si

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

So I need to recompile a new kernel with usbcore "enabled" right?
Any good "how to" about this recompile process?
thanks alot

12

Angstrom & OpenZaurus / Module Usbcore.o Not Available. Why?

« on: September 15, 2005, 06:56:39 pm »

usbcore and usbdcore are different things - usbdcore is what allows ethernet over usb iirc.

You probably need to modify the defconfig for your machine to enable usb (you may also need a minor patch - I sent the defconfig and patch for the Shepherd to the OE mailing list a long time agao, that should get you started looking in the right place).


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

Great. thanks. I'm a newbie n not sure how to modify defconfig n neither to get the oesf mailing list.
I did some research on google and on this site about those but I didn't get much info.
Any links or more info about how to modify defconfig?
Thanks

13

Angstrom & OpenZaurus / Cannot Get Socket Wifi Card To Work Under Oz 3.5.3

« on: September 15, 2005, 02:04:10 am »

Any news on this issue guys?
getting the same error unable to handle kernel paging request at virtual address on same memory address.

14

Angstrom & OpenZaurus / Module Usbcore.o Not Available. Why?

« on: September 11, 2005, 07:03:31 pm »

Hi, I'm trying to get a CFU1 usb host workinf on my poodle.
Here's my logread:
"
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: socket 0: RATOC USB HOST CF+ Card
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: executing: 'modprobe usbcore 2>&1'
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + modprobe: module usbcore not found.
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + modprobe: failed to load module usbcore
Sep 11 21:58:29 poodle daemon.notice cardmgr[555]: modprobe exited with status 1
Sep 11 21:58:29 poodle daemon.notice cardmgr[555]: module /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/usbcore.o not available
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: executing: 'modprobe hc_sl811 2>&1'
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + Using /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/usb/hc_sl811.o
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_alloc_bus
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_free_dev
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_deregister_bus
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_disconnect
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_connect
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_new_device
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_root_hub_string
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_alloc_dev
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_register_bus
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_free_bus
Sep 11 21:58:29 poodle daemon.info cardmgr[555]: + modprobe: failed to load module hc_sl811
Sep 11 21:58:29 poodle daemon.notice cardmgr[555]: modprobe exited with status 1
Sep 11 21:58:29 poodle daemon.notice cardmgr[555]: module /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/hc_sl811.o not available
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: executing: 'modprobe sl811_cs 2>&1'
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + Using /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/usb/hc_sl811.o
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_alloc_bus
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_free_dev
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_deregister_bus
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_disconnect
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_connect
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_new_device
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_root_hub_string
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_alloc_dev
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_register_bus
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol usb_free_bus
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + Using /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/sl811_cs.o
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol hci_hcd_cleanup
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol hc_found_hci
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + modprobe: failed to load module sl811_cs
Sep 11 21:58:30 poodle daemon.notice cardmgr[555]: modprobe exited with status 1
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: executing: 'insmod /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/sl811_cs.o 2>&1'
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + Using /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/sl811_cs.o
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol hci_hcd_cleanup
Sep 11 21:58:30 poodle daemon.info cardmgr[555]: + insmod: unresolved symbol hc_found_hci
Sep 11 21:58:30 poodle daemon.notice cardmgr[555]: insmod exited with status 1
Sep 11 21:58:31 poodle daemon.err cardmgr[555]: get dev info on socket 0 failed: Resource temporarily unavailable
"
And here's my lsmod:
"
Module                  Size  Used by    Tainted: P  
rfcomm                 33488   0 (autoclean)
l2cap                  17028   2 (autoclean) [rfcomm]
bluez                  32616   1 (autoclean) [rfcomm l2cap]
sharp_mmcsd_m          26200   1
pxa_bi                 20028   0 (unused)
net_fd                 25012   0 (unused)
usbdcore               30424   0 [pxa_bi net_fd]
"
So I don't know why it says module usbcore not found.
It's trying to get a "module /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/usbcore.o" with a error "not available" but this file is in /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/usb/device so I did a copy to "/lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia" but it still says not available
Man, this zaurus is driving crazy!
Here what I've done:
reinstaled cfu1-driver_0.0.2-3_arm.ipk
installed from feed machine/poodle kernel-module-usbdcore_2.4.18-rmk7-pxa3-embedix-r36_poodle.ipk

Any help would be apprecated.Thanks

15

Angstrom & OpenZaurus / Read-only File System

« on: September 11, 2005, 06:06:51 pm »

You have to set the write permissions for the card in fstab,


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

Thanks but the fstab is fine (it was set to default so rw was enabled).
oh well, I've juste reflashed the rom and now it's ok.
Thanks