Messages

421

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 08, 2015, 03:43:49 am »

and yes, I enabled everything needed for the tethering you mentioned.

422

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 08, 2015, 03:42:40 am »

Hi daalnroti!

Great to see you've got the new kernel config up before my new gear arrives! I was hoping it might arrive yesterday but that was the absolute earliest they could've arrived. Stuff arriving today is more realistic.

I have failed to find a photo guide to swapping out the C3x00 MD drive but there is at least one thread on here discussing the process and it sounds pretty straightforward, if a bit fiddly.

We're never going to get more than about 1MB/s via the USB port as thats what USB 1 tops out at. That should should suffice for acceptable tethering speeds, if that will work over USB OTG 1? Did you check the USB tethering stuff was enabled? Of course, CF will achieve much faster rattes so I may get more than that with my new wifi card and lets see how fast the CF memory card is. I'll be sure to get some before and after boot times and transfer rates for the drives.

Shame about the newer kernel. I'm very interested to see what the newest we can get to run is.

Seeing as I'll have physical access to my new CF card, I'll be writing ALARM to it via my laptops USB CF reader, if it can read it! I'll be formatting it as ext4 as I'm  pretty sure kexecboot supports ext4. I think you can tell fstab / mount to mount ext3 partitions as ext4 without reformatting drives anyway.

Thanks!

Hi danboid,

there must be some photo guides somewhere on google cache. I am sure I saw some not too long ago.
take care when doing it, do not break your Z

Sure, USB1 has it limits, but with the card you ordered, higher speed might be possible.

I will give my best to get a new kernel going, but saying that, 3.11.3 is stable and does what is should do.

Let me know how you go with WiFi and the rebuild kernel.

Cheers!

423

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 08, 2015, 03:04:58 am »

but yesterday I ordered a SparkLAN WCFM-100 because thats faster and supports 802.11g so that should arrive in the next couple of days. Might you make another kernel release with more PCMCIA wifi (and PCMCIA ethernet) drivers included? That would be handy as it must take an age to compile the kernel on the Z!

Let me know if you can get the new card to work.

It would be very interesting what throughput you can achieve with that card.

My Buffalo CF LAN is 10mbit only, the DLINK 660W 802.11b and with a USB 100mbit LAN adapter I get still not more than 750KB/s to the internal 4GB MicroDrive (via SSH) and about 850KB/s to a class 4 SD card via the USB1.1 port. Please give some benchmarks with your 32GB CF card too.

Cheers!

424

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 08, 2015, 01:21:51 am »

Some more info for the curious:

boot log dmesg 3.11.3-c3x00-arch on C3100:

Code: [Select]

[    0.573342] 0x000000140000-0x000000800000 : "Boot PROM Filesystem"
[    0.580806] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
[    0.580922] Scanning device for bad blocks
[    0.631902] 3 cmdlinepart partitions found on MTD device sharpsl-nand
[    0.631945] Creating 3 MTD partitions on "sharpsl-nand":
[    0.631989] 0x000000000000-0x000000700000 : "smf"
[    0.637892] 0x000000700000-0x000002700000 : "root"
[    0.643755] 0x000002700000-0x000008000000 : "home"
[    0.651137] hdlc: HDLC support module revision 1.22
[    0.651262] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.651290] ehci_hcd: block sizes: qh 64 qtd 96 itd 160 sitd 96
[    0.652402] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.652452] ohci_hcd: block sizes: ed 64 td 64
[    0.652666] In ohci_hcd_pxa27x_drv_probe
[    0.652983] pxa27x-ohci pxa27x-ohci: PXA27x OHCI
[    0.653129] pxa27x-ohci pxa27x-ohci: new USB bus registered, assigned bus number 1
[    0.653269] pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c000000
[    0.653295] pxa27x-ohci pxa27x-ohci: ohci_pxa27x_start, ohci:c3afc4d8
[    0.653465] pxa27x-ohci pxa27x-ohci: created debug files
[    0.712511] pxa27x-ohci pxa27x-ohci: OHCI controller state
[    0.712580] pxa27x-ohci pxa27x-ohci: OHCI 1.0, NO legacy support registers, rh state running
[    0.712619] pxa27x-ohci pxa27x-ohci: control 0x083 HCFS=operational CBSR=3
[    0.712647] pxa27x-ohci pxa27x-ohci: cmdstatus 0x00000 SOC=0
[    0.712680] pxa27x-ohci pxa27x-ohci: intrstatus 0x00000004 SF
[    0.712711] pxa27x-ohci pxa27x-ohci: intrenable 0x8000005a MIE RHSC UE RD WDH
[    0.712736] pxa27x-ohci pxa27x-ohci: hcca frame #0009
[    0.712771] pxa27x-ohci pxa27x-ohci: roothub.a 04001202 POTPGT=4 NOCP NPS NDP=2(3)
[    0.712797] pxa27x-ohci pxa27x-ohci: roothub.b 00000000 PPCM=0000 DR=0000
[    0.712827] pxa27x-ohci pxa27x-ohci: roothub.status 00008000 DRWE
[    0.712864] pxa27x-ohci pxa27x-ohci: roothub.portstatus [0] 0x00000100 PPS
[    0.712895] pxa27x-ohci pxa27x-ohci: roothub.portstatus [1] 0x00000100 PPS
[    0.712927] pxa27x-ohci pxa27x-ohci: roothub.portstatus [2] 0x00000100 PPS
[    0.713110] usb usb1: default language 0x0409
[    0.713182] usb usb1: udev 1, busnum 1, minor = 0
[    0.713212] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[    0.713238] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.713261] usb usb1: Product: PXA27x OHCI
[    0.713283] usb usb1: Manufacturer: Linux 3.11.3-c3x00 ohci_hcd
[    0.713305] usb usb1: SerialNumber: pxa27x
[    0.715507] usb usb1: usb_probe_device
[    0.715567] usb usb1: configuration #1 chosen from 1 choice
[    0.715701] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[    0.716849] hub 1-0:1.0: usb_probe_interface
[    0.716893] hub 1-0:1.0: usb_probe_interface - got id
[    0.716921] hub 1-0:1.0: USB hub found
[    0.717023] hub 1-0:1.0: 3 ports detected
[    0.717046] hub 1-0:1.0: standalone hub
[    0.717065] hub 1-0:1.0: no power switching (usb 1.0)
[    0.717086] hub 1-0:1.0: no over-current protection
[    0.717109] hub 1-0:1.0: power on to power good time: 8ms
[    0.717195] hub 1-0:1.0: 180mA bus power budget for each child
[    0.717228] hub 1-0:1.0: local power source is good
[    0.717485] hub 1-0:1.0: trying to enable port power on non-switchable hub
[    0.719822] usbcore: registered new interface driver cdc_wdm
[    0.721353] mousedev: PS/2 mouse device common for all mice
[    0.723558] input: matrix-keypad as /devices/platform/matrix-keypad/input/input0
[    0.728793] pxa-rtc pxa-rtc: rtc core: registered pxa-rtc as rtc0
[    0.730848] APM Battery Driver
[    0.734017] PXA CPU 27x max frequency not defined (pxa27x_maxfreq), assuming pxa271 with 416000kHz maxfreq
[    0.734076] PXA CPU frequency change support initialized
[    0.794110] ledtrig-cpu: registered to indicate activity on CPUs
[    0.797497] usbcore: registered new interface driver usbhid
[    0.797533] usbhid: USB HID core driver
[    0.808392] soc-audio soc-audio: ASoC: machine Spitz should use snd_soc_register_card()
[    0.815143] hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000
[    0.884205] mmc0: new SDHC card at address aaaa
[    0.886253] mmcblk0: mmc0:aaaa SD04G 3.79 GiB
[    0.889989]  mmcblk0: p1
[    1.304623] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[    1.308715] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 201)
[    1.314702] pcmcia_socket pcmcia_socket1: pccard: PCMCIA card inserted into slot 1
[    1.319517] pcmcia 1.0: pcmcia: registering new device pcmcia1.0 (IRQ: 202)
[    1.369945] scsi0 : pata_pcmcia
[    1.372078] ata1: PATA max PIO0 cmd 0xc4880000 ctl 0xc488000e irq 202
[    1.545011] ata1.00: CFA: HMS360404D5CF00, DN4SCA2A, max PIO4
[    1.545063] ata1.00: 7999488 sectors, multi 0: LBA
[    1.822474] soc-audio soc-audio:  wm8750-hifi <-> pxa2xx-i2s mapping ok
[    1.830083] TCP: cubic registered
[    1.830625] XScale iWMMXt coprocessor detected.
[    1.841233] input: gpio-keys as /devices/platform/gpio-keys/input/input1
[    1.843996] pxa-rtc pxa-rtc: setting system clock to 2000-01-01 07:11:19 UTC (946710679)
[    1.844230] ALSA device list:
[    1.844245]   #0: Spitz
[    2.684995] ata1.00: configured for PIO0
[    2.686431] scsi 0:0:0:0: Direct-Access     ATA      HMS360404D5CF00  DN4S PQ: 0 ANSI: 5
[    2.691239] sd 0:0:0:0: [sda] 7999488 512-byte logical blocks: (4.09 GB/3.81 GiB)
[    2.693255] sd 0:0:0:0: [sda] Write Protect is off
[    2.693317] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.694157] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    2.704233] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    2.725683]  sda: sda1 sda2 sda3
[    2.736186] sd 0:0:0:0: [sda] Attached SCSI disk
[    2.791667] EXT3-fs (sda3): mounted filesystem with writeback data mode
[    2.791847] VFS: Mounted root (ext3 filesystem) readonly on device 8:3.
[    2.792338] kjournald starting.  Commit interval 5 seconds
[    2.848378] devtmpfs: mounted
[    2.849349] Freeing unused kernel memory: 172K (c04dd000 - c0508000)
[    7.463956] NET: Registered protocol family 10
[    7.714201] ip_tables: (C) 2000-2006 Netfilter Core Team

425

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 08, 2015, 01:11:41 am »

These are some examples to help you going. No guarantee these work in all circumstances. Just as a guideline.

Kexecboot :

Create a file boot.cfg in /boot on you ALARM partition if you need a boot menu entry for dual boot etc.
Make sure to change your root= entry to match your setup.

Example:

Code: [Select]

LABEL=ArchLinux
KERNEL=/boot/zImage-3.11.3-c3x00
APPEND=root=/dev/sda3 rootfstype=ext3 fbcon=rotate:1 noinitrd loglevel=3 pxa27x_maxfreq=624

LABEL=Debian
KERNEL=/boot/zImage-2.6.36-rc3
APPEND=console=ttyS0,115200n8 root=/dev/hda1 rootfstype=ext3 console=tty1 noinitrd  fbcon=rotate:1  debug dyntick=enable
fstab :

Make sure to change to your file system type,  and root device /dev/hdax etc

Example:

Code: [Select]

/dev/hda3               /               ext3 noatime,nodiratime,commit=600,reservation,defaults,errors=remount-ro 0 1

426

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 08, 2015, 12:06:12 am »

Hi daalnroti

Enjoy reading about progress and updates with Arch.....

Haven't given up on OpenBSD yet, still building programs....

But if I do decide to try Arch, will your files work with my 3200?

Thanks,

Mark

I can not confirm, but I am confident that C3200 will work.

427

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 07, 2015, 11:17:30 pm »

new release 3.11.3 kernel

428

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 07, 2015, 08:57:04 pm »

If you want to overclock, you can try to add

Code: [Select]

pxa27x_maxfreq=624 to your kernel parameters and see if you can get a higher clock rate.
I have not played with it under ALARM.

429

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 07, 2015, 08:52:24 pm »

Code: [Select]

poweroff
Seems to be the only clean and reliable way to shut down the Z under Arch, vs using halt or shutdown.

If I'm lucky my 32GB CF (which cost me £15 inc. postage) and new wifi card should be arriving today although I don't think I'll be able to use the wifii until dallnroti gets the new kernel uploaded or I build one myself of course. I think I can wait!

Excluding your tweak to get the power LED to indicate the kernels heartbeat, have you applied any custom patches to your kernel or is it all mainlined, upstream code daalnroti?

The 3.11.3 kernel has follwing patches :

Power LED => cpu heartbeat
HDD LED => disk activity ( needed to be patches, vanilla kernel does not show HDD activity )
USB  => increased max power to 180mA ( _may_ work to get some USB sicks running )
BOOT => some boot hang fix that happenend with 3.x kenels

thats about it.

I will have rebuild 3.11.3 kernel ready this afternoon, containing all USB / CF WiFi drivers, no heartbeat LED and no boot logo.

The 3.18 series did not boot from a vanilla kernel and I will need to troubleshoot later this week. Possibly some patches required.

Cheers!

430

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 06, 2015, 07:49:39 am »

Dying? It died almost a decade ago!

Weedy as its specs may be today, the fact remains we can still run modern software on it and thats one of the main reasons I bought it. I'd say the Z makes a better pocket SSH client than any of the latest gen smartphones because of its hardware keyboard so its still very useful to us techies.

I think its a shame that, apart from the Pandora which I don't think is available any more either, there hasn't been anything to supercede the Z for pocket Linux boxes. The Pyra should be out soon but I won't buy one unless Imagination release a fully-functional, open source X driver for their PVR GPUs. I can't believe they went that route when it could've used Tegra or Adreno.

You got a point there, it is dead already, we are the last souls to keep it alive.

Also I agree, as a pocket ssh client, it is still useful and more secure compared to android devices.

Saying this, lets focus on one thing. Keep the Z alive , with ALARM.

I appreciate a tester and user a like you. hopefully there might be more joining us with their Z!!

Cheers.

431

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 06, 2015, 07:23:34 am »

Danboid,

great you got the keymap working.

you can download the firmware package manually and may be able to install it using pacman -U

still, I will put in some effort to get an updated kernel going and add any needed drivers.

The zaurus is a dying platform, but I will keep it going until my Z hardware dies.

Cheers!

432

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 06, 2015, 06:42:33 am »

I have just tried to recompile the kernel, but since my system is now way up to date, I will need to upgrade the kernel to at least 3.18 or 4.x

Maybe a good chance to get a new kernel going. just give me a few days and I will see what I can get going.

But saying this, I still can compile the 3.11.3 kernel on a older system backup , using older gcc.

I will find out what is more efficient and will let you know. Give me a couple of days, I am busy working at IT daytime and will work on it at nights.

Cheers.

433

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 06, 2015, 06:26:24 am »

danboid,

zgrom uses a sdl library optimized for the the Z, not sure the source code of that library was ever made public..

anyway, the 3.11.3 kernel has hostap support. also for prism 2/3 , I checked.

can you please give me some more details about your card. ? try a "modprobe hostap" first and check "dmesg"

also you may need just the kernel firmware package, that is available via pacman. but you need to get network going first ..

Cheers,

434

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 06, 2015, 05:12:37 am »

danboid,

if you want to get mame going you should try this first : https://code.google.com/p/zgrom/wiki/Emulators

Back in the days, I invested a lot of time to get SDL apps working in pure console, using the framebuffer only for emulators etc.

zgrom is the way to go, anything else is just frustrating. The Z uses a rotated frambuffer as default for landscape view. this is a big performance draw back.

and is a real nightmare to get proper Xorg running fast. it has always to rotate in software ! zgrom is the most optimized as far as I know, for gaming.

Thats why I stick to console only. The impact of rotated console is minimal. obsd has the same issue, has to rotate in software, using wcons for SDL.

In regards to led, logo and wifi / tethering . I will post a testing kernel tar.gz in this thread before uploading the sourced to github.

I will post a testing build later tonight (NZ time) or tomorrow. Different timezones man.

Cheers.

435

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: October 06, 2015, 04:03:34 am »

Hi danboid,

In regards to charging, I guess I got it wrong. When turned on and with a 3.x kernel , the Z charges really slow. When off line, normal charging speed.

If you like, I can remove the LED patch and make it behave as usual. no problem there.

Also I can add the wifi modules for you and recompile, then upload to github.

Overclock, well I never tried, cpufreq on ALARM shows only 416 as max.

This does not mean it cant be done, but I have no need for it to be honest.

Do you have a CF LAN card too , or only WiFi ?

Any USB drivers you may need ?

Cheers