Messages

1

Sharp ROMs / Prism 2.5 Firmware Trouble

« on: October 20, 2011, 01:17:12 am »

I have a Buffalo WLI-CF-S11G wireless card for my SL-C1000. It is running Cacko 1.23 (heavy?).
I want to be able to connect the Zaurus to my secure WPA network at home and I am interested in testing 'aircrack-ng' . From their website it seems one must use Station firmware >=1.5.6.

My card was running older firmware; here is the output of

Code: [Select]

# dmesg | grep wifi

wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.0.5
wifi0: STA: id=0x1f v1.3.4

I followed Jun Sun's mini-HOWTO guide and flashed the card on my Windows XP laptop using the WinUpdate program. It didn't go so smoothly and I had to select 'Disable' in the 'Firmware Download' section of the card's properties (explained clearer here).
After that, flashing with WinUpdate seemed to work and the card now has Primary firmware 1.1.1 and Secondary (Station) firware 1.7.4.
But, now the card is not functioning well. It appears that the card is working for about 1 second after insertion - as the lights come on, and then it is susended or somesuch - as the lights go off.
The command

Code: [Select]

# dmesg | grep wifispits out repetitions of this

wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_red: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
wifi0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wifi0: hfa384x_cmd_issue - timeout - reg-0x8888
wifi0: hfa384x_cmd: entry still in list? (entry-c3a64be0, type=0, res=-1)

(but an odd thing happened as I ran that last code, appended to the end was this

wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_red: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
wifi0: NIC: id=0x0800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.7.4

When I ran the command again it was back to the usual repetitions without the above appendage.

I decided to try and download and compile hostap-utils-0.4.7 as suggested here.
I downloaded the file from here and then followed these commands but when I came to the command

Code: [Select]

makeThis message was returned

-bash: make: command not found

What am I doing wrong?
Should I be using a different ROM?
Why won't my card function properly in Cacko 1.23 with the updated firmware?

Could you give me a little help if you are able to please?

2

Ubuntu / Extracted Cacko 1.23 Rootfs

« on: October 03, 2009, 09:22:10 am »

I'm confused.

I've spent much of the day trying to follow the instruction to get Cacko and Zubuntu working on my sl-c1000 (Akita) but I've come up against a few things I don't fully understand and some that just baffle me.

- I did a Trisoft NAND restore, that was easy.
- I resized my root partition to 53Mb and installed Cacko  ROM 1.23 from Katastrophos
- I tried flashing the multiboot kernel but came a bit unstuck.
What I did was: on a FAT16 formated SD card I put the 'updater.sh' and 'zImage.bin' files as described on Omegamoon blog. I really wasn't too sure about the 'zImage.bin' file though, I ended up using the 'zImage' file from the /boot folder from the zubuntu version 2.0 root-addition archive and appending '.bin' to the file. I then followed the multiboot kernel flashing procedure.
- Perhaps it is late but when I looked at Step 4 I realised I had no idea what to do. Where do I find the Katastrophos kernel? What is the Katastrophos kernel? I fear my brain is overheating! I looked at the two Cacko root filesystems mentioned in Scottfa's first post but they look to me like identical filesystems. What are they for? How are they relevant to this process? Should I be searching for Katastrophos' kernel there?

This is all good fun, learning about all this stuff and getting more familiar with my Zaurus and linux filesystems and multiboot flashing and whatnot but I think I should sleep on it for now. With any luck someone will have read this post and given me a few pointers or hints by tomorrow.

EDIT: Slept on it, thought about it, slept on it again and then reread this thread and Omegamoon's instructions.
Why would I use the zImage file from the /boot folder??? I must have been more tired than I had realized! Later today I'll try flashing the multiboot kernel using the updater.sh and zImage.bin (sl-c1000) files provided in the "Flashing The Multiboot Kernel" section of Omegamoon's blog.
I suppose the two filesystems in Scottfa's post are there to be used if you want to run a Cacko or Sharp ROM off of an SD/CF card partition...right?

3

Ubuntu / Extracted Cacko 1.23 Rootfs

« on: October 02, 2009, 09:33:12 pm »

Thanks very much for clearing that up for me.

4

Ubuntu / Extracted Cacko 1.23 Rootfs

« on: October 01, 2009, 01:42:18 am »

Could you give a little more detail of

5. boot into cacko, remount root partition as rw.
make boot folder on root. copy kernel over and reboot. (take out sd)

please? I'm not sure what 'rw' is or where one copies the kernel from.

Thanks.

5

Debian / Lan Network Settings With Debian On C1000

« on: August 07, 2009, 12:21:47 am »

I reverted to the original /etc/network/interface file but uncommented the line "iface eth0 inet dhcp".
I then ran the command "dhclient eth0"in the console. This is what resulted:

Code: [Select]

.
.
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
I could really do with some help from the community please.

6

Debian / Lan Network Settings With Debian On C1000

« on: August 03, 2009, 11:50:23 am »

Love the ease of installing and the look of Debian on my Zaurus, thanks to ZDevil's guide. This is a great forum with loads of good tips, guides and helpful people.
I'm still pretty new to configuring things on a Zaurus, in particular setting up a network connection.

I had no luck trying to set-up the same Buffalo LPC-CF-CLT network LAN card using Zubuntu on my sl-c1000. Anyone else use one of these?
Since installing Debian I've been trying to set up the network but I'm having problems with the same card again or more accurately with my own lack of understanding!

With Cacko the card just connects but I want to venture out and explore other ROMs/Distros.

Went over my previous post  and still could get further than both lights lit up on the network card but no connection.

Is there a guru or someone who's overcome the same or similar problem and can offer some advice?

I don't know if the device is 'lo' or 'eth0' or 'eth1'.
Same connection as my desktop box which requires no configuration, so presumably it is not static.... but I don't know.


Zaurus:~# ifconfig
lo               Link encap:Local Loopback
                               .
                               .
                               .
                  RX bytes:0 (0.0 b ) TX bytes:0 (0.0 b )

Zaurus: ~# modprobe pxa2xx
FATAL: Mobuke pxa2xx not found.

Zaurus:~# pccardctl ident
Socket 0:
      product info: "BUFFALO", "LPC-CF-CLT", "R01", ""
      manfid: 0x026f, 0x0307
      function: 6 (network)

7

Ubuntu / Buffalo Lpc-cf-clt Lan Card Connection

« on: July 07, 2009, 03:07:39 am »

Anyone?
Anything?

8

Ubuntu / Buffalo Lpc-cf-clt Lan Card Connection

« on: July 03, 2009, 12:14:59 pm »

My /etc/network/interfaces file looked liked this:

Code: [Select]

auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp
I altered it to look like this:

Code: [Select]

auto eth0
iface eth0 inet dhcpRebooted.
Modeprobed.
Ran:

Code: [Select]

ifup eth0...and again got this message:

Code: [Select]

No support for INET on this system.
Can't create addrlist socket
Failed to bring up eth0.
Anything else I should try?

9

Ubuntu / Buffalo Lpc-cf-clt Lan Card Connection

« on: July 03, 2009, 11:50:40 am »

I have tried:

Code: [Select]

root@Zubuntu:~# ifup eth0A few lines of text about Internet Systems Consortium appear followed by these lines:

Code: [Select]

No support for INET on this system.
Can't create addrlist socket
Failed to bring up eth0.I tried:

Code: [Select]

root@Zubuntu:~# ifup eth1....but that resulted in this:

Code: [Select]

Ignoring unknown interface eth1=eth1.What next?

EDIT: Spent too long composing this message and missed duo's message posted before it. Will try duo's suggestion.

10

Ubuntu / Buffalo Lpc-cf-clt Lan Card Connection

« on: July 03, 2009, 10:49:11 am »

Many thanks for your assistance duo.

Code: [Select]

root@Zubuntu:~# lsmodmakes no mention of pxa2xx_cs

Code: [Select]

root@Zubuntu:~# modeprobe pxa2xx_csgets the ACT light on, then plugging in the LAN gets the LINK light on.

Is there a further command to complete the connection? Currently firefox just displays "Address Not Found".

11

Ubuntu / Buffalo Lpc-cf-clt Lan Card Connection

« on: July 03, 2009, 03:16:12 am »

Hi,

Has anyone got a buffalo LPC-CF-CLT LAN card connected while running Zubuntu? (HINT: It's not a wifi card, it's a wired one).
It works without any tinkering under Cacko. It couldn't be as ludicrously simple as just copying over drivers from Cacko to a driver folder in Zubuntu, could it?

Should I do a "dmesg" as suggested in a previous post on connectivity today and post the last 10 lines over here?

12

Ubuntu / Zubuntu And Sl-c1000

« on: May 12, 2009, 02:59:22 am »

Thanks very much. I'll try it out.

On a different note: is the Zaurus still limited to a standard 4Gig max. SD card? Or have recent kernel updates increased the size?

13

Ubuntu / Zubuntu And Sl-c1000

« on: May 11, 2009, 05:33:18 am »

I'm having a little trouble with Zubuntu on my Zaurus sl-c1000. I was hoping someone could spare me a little of their time to help me get it right.
I believe I have correctly made a 1Gig SD card with Zubuntu on it, following Omegamoon's instructions.

I get the bootmenu showing Zubuntu but after selecting it I always end up with this line: Press enter for maintenance (or type Control-D to continue)

I'm not sure how much of the previous text to include, here's a bit more:

/dev/shm/root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
              (i.e., without -a or -p options)
fsck died with exit status 4                                                                                                  [fail]
* An automatic file system check (fsck) of the root filesystem failed.
A manual fsck must be performed, then the system restarted.
The fsck should be performed in maintenance mode with the
root filesystem mounted in read-only mode.
* The root filesystem is currently mounted in read-only mode.
A maintenance shell will now be started.
After performing system maintenance, press CONTROL-D
to terminate the maintenance shell and restart the system.
Press enter for maintenance
(or type Control-D to continue)


If I press enter (for maintenance)
then I get:
bash: no job control in this shell
bash: groups: command not found
bash: lesspipe: command not found
bash: dircolors: command not found

root@Zubuntu:~#


Has anyone any idea what might be going on here?