Archlinuxarm On C3x00

[greguu]

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

[greguu]

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!

[danboid]

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. Its not much but that  should suffice for acceptable tethering speeds, if it 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!

[greguu]

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!

[greguu]

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

[greguu]

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.

The oe-kexecboot possibly supports ext4, but I am not sure. I am still on ext3.

I am not sure there is a real advantage for the Z to use ext4 on CF flash drive over ext3.

The 3.11.3 kernel does support ext4.

If we need a new kexecboot kernel , I may find the time to compile one. I have done it before.

Cheers!

[danboid]

As for the tethering, I'd prob get better speeds using my new 54Mb/s card with portable wifi hotspot on my phone versus a USB link but the USB option would certainly be very handy to have, especially for those who don't have a (working) wifi or ethernet card or struggle to get wifi to work due to various potential issues.

I doubt using ext4 over ext3 would be detrimental to performance although I'm not expecting a huge or even a very noticeable gain by switching. I'm going to try it now.

Good to hear you have already recompiled kexec. What did you need to rebuild it for previously?

[greguu]

Good to hear you have already recompiled kexec. What did you need to rebuild it for previously?

Need to build a minimal kernel with a build in initrd image.

That image contains the kexecboot binary and will get executed on boot.

It is possible to change boot logo etc for that.

Cheers!

[greguu]

danboid : any success with the "new" kernel and WiFi ?

[danboid]

Thanks for explaining how to overclock! I'll be trying that soon - after I have networking sorted and hence something installed that would benefit from a higher clock (gcc, MAME or something).

My new hardware didn't arrive today. I've checked the tracking and I should have both tomorrow so there is no progress on the wifi or CF benchmarks to report. I don't think its worth the hassle trying to get my prism card to work now.

I've installed the new kernel and it seems to be running fine - better than fine actually! Suspend works now! I was NOT expecting that! This is shaping up very nicely now!

Why are there two kernel images in the new archive? One has -arch appended but I've only tried the one without because there wasn't a -arch kernel module dir to go with it.

The power LED is no longer blinking but I've noticed some odd beviour with it in that it sometimes doesn't light up when AC is plugged in. Do you get this? I've not worked out what might be causing that yet.

Looks like I might be out of luck with the USB tethering - I just get lots of "hub 1-0:1.0: connect-debounce failed, port 2 disabled" errors when I connect my phone and USB tethering is still greyed out under Android.

Indeed you can mount an ext3 partition as ext4 under Arch. You need to change the fs type in both /boot/boot.cfg and fstab. My tests indicate reading is slightly faster with ext4 but it makes no discernable difference to write speed:

Stock 4GB MD, ext3

kexec menu to login prompt boot time: 49s

hdparm -Tt /dev/sda

cached reads: 44.55 MB/s
buffered disk reads: 2.25 MB/s

hdparm -Tt --direct /dev/sda

cached reads: 1.99 MB/s
disk reads: 2.02 MB/s

sync;time bash -c "(dd if=/dev/zero of=bf bs=8k count=25000; sync)"

2.4MB/s (write speed)
1m 27s real



Stock 4GB MD mounted as ext4

kexec menu to login prompt boot time: 49s

hdparm -Tt /dev/sda

cached reads: 46.69 MB/s
buffered disk reads: 2.31 MB/s

hdparm -Tt --direct /dev/sda

cached reads: 2.03 MB/s
disk reads: 2.04 MB/s

sync;time bash -c "(dd if=/dev/zero of=bf bs=8k count=25000; sync)"

2.4MB/s (write speed)
1m 27s real

[danboid]

I've just noticed there is a note on github explaing the differences between the two kernel images altough I'm still unsure about it.

It seems the -arch version has a different boot logo and still has the LED heartbeat indicator but the note makes it sound like the included firmware might only work with zImage-3.11.3-c3x00-arch? That would seem a bit odd to me but you must have a reason if that's the case?

In any case I'd presume they share the same modules dir and thats why there is only one included?

[greguu]

I've just noticed there is a note on github explaing the differences between the two kernel images altough I'm still unsure about it.

It seems the -arch version has a different boot logo and still has the LED heartbeat indicator but the note makes it sound like the included firmware might only work with zImage-3.11.3-c3x00-arch? That would seem a bit odd to me but you must have a reason if that's the case?

In any case I'd presume they share the same modules dir and thats why there is only one included?

Yes,  modules, firmware work with both versions. I might fix that github entry to make this more clear.

[greguu]

Thanks for explaining how to overclock! I'll be trying that soon - after I have networking sorted and hence something installed that would benefit from a higher clock (gcc, MAME or something).

My new hardware didn't arrive today. I've checked the tracking and I should have both tomorrow so there is no progress on the wifi or CF benchmarks to report. I don't think its worth the hassle trying to get my prism card to work now.

I've installed the new kernel and it seems to be running fine - better than fine actually! Suspend works now! I was NOT expecting that! This is shaping up very nicely now!

Why are there two kernel images in the new archive? One has -arch appended but I've only tried the one without because there wasn't a -arch kernel module dir to go with it.

The power LED is no longer blinking but I've noticed some odd beviour with it in that it sometimes doesn't light up when AC is plugged in. Do you get this? I've not worked out what might be causing that yet.

Looks like I might be out of luck with the USB tethering - I just get lots of "hub 1-0:1.0: connect-debounce failed, port 2 disabled" errors when I connect my phone and USB tethering is still greyed out under Android.

Overclocking : let me know if you have success. I had no time to test it really.

Great you got suspend working. It does work somewhat, but needs some tweaking to make it useful. See /etc/systemd/logind.conf for some settings. Also SD card does not get unmounted proberly when suspending...

The power LED does not blink when turned on because online charging is broken. The Z does charge, but I guess very slowly. To charge properly you need to turn off. ;(
Actually that was the reason why I added the CPU heartbeat instead if I remember correctly. It has been a few years ago when I build the 3.5 and 3.11.3 kernels.

The tethering issue may be related to the low power on the usb port? Try with a powered usb hub just to test if that is the case.

[danboid]

If the SD card not getting unmounted is the only prob with suspend then I can live with that.

As for the USB tethering, I suppose there is a chance its lack of power but I doubt it and if it does require a powered hub for me to use USB tethering then I don't think I'd bother.

You forgot to include an example boot.cfg file in the updated kernel tarball like you did in the previous release.

My 32GB CF card arrived this morning so I'm just setting it up now before I disassemble my Z to replace the MD. I'll hopefully be back shortly with some benchmarks rather than bad news!

I'm still awaiting delivery of my wifi card...

[greguu]

If the SD card not getting unmounted is the only prob with suspend then I can live with that.

As for the USB tethering, I suppose there is a chance its lack of power but I doubt it and if it does require a powered hub for me to use USB tethering then I don't think I'd bother.

You forgot to include an example boot.cfg file in the updated kernel tarball like you did in the previous release.

My 32GB CF card arrived this morning so I'm just setting it up now before I disassemble my Z to replace the MD. I'll hopefully be back shortly with some benchmarks rather than bad news!

I'm still awaiting delivery of my wifi card...

Tethering : I understand that a powered usb hub is not an option, but it would clarify if the issue is the power on the usb port or not. There is still the chance it may work if some further kernel or userland settings are required.

boot.cfg : you are right, I forgot to add the file.

did you have any success with you current WiFi card ? Would be good to know that you can use pacman and do an update of packages.

Thanks for testing, very much appreciated, any input welcome.
Cheers!