• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2 3
1  Hardware and U-Boot firmware / U-Boot stuff / Re: SheevaPlug: no boot from SDHC after u-boot upgrade to DENX 2012.04.01-2 on: January 18, 2014, 03:14:32 AM
Yes, I already boot from an ext2 partition which is named as /boot in /etc/fstab. However wouldn't it be nice to have a single ext4 partition as I have in my Cubox's as the u-boot has these commands built in. I'm not sure now if I grabbed a binary or compiled the u-boot source for the cubox's. I have tried compiling a u-boot 2013-10 for sheevaplug but the patches and sources didn't work for me. I added the ext4 commands in the config but that was pointless.
2  Hardware and U-Boot firmware / U-Boot stuff / Re: SheevaPlug: no boot from SDHC after u-boot upgrade to DENX 2012.04.01-2 on: January 16, 2014, 10:34:47 AM
Thanks for the info. If you have the info, can this version boot from an EXT4 partition (commands 'ext4load' and 'ext4ls') as this could simplify the SDHC/disk partitioning?
3  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: December 10, 2013, 05:25:11 AM
I have updated my various boxes (3xeSata Sheevaplug, 3xGuruplug Server+,2xCubox,2xTonidoplug2,11xRPi) to kernel 3.12.3 and so far, all seems to be well! Well almost. It seems that this kernel has an interrupt problem on my Guruplugs and I show a dmesg from one of them. Also, one small point is there is a typo type error in the 'UPDATE-KERNEL.sh' script and the line
Code:
elif grep -qs 'GuruPlug' /proc/cpuinfo || grep -qs 'GuruPlug' /proc/device-tree/model; then
should be
Code:
elif grep -qs 'GuruPlug' /proc/cpuinfo || grep -qs 'Guruplug' /proc/device-tree/model; then

The 'dmesg' was taken after my plugs had been running for 48 hours though I do not know exactly when the errors occurred. It seems to be worse on a GP+ using SDHC rather than eSata.

Code:
root@NS2:/# dmesg
Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 3.12.3 (kelly@bbb.internal) (gcc version 4.8.2 20131014 (prerelease) (Linaro GCC 4.8-2013.10) ) #2 Wed Dec 4 14:41:22 MST 2013
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell Kirkwood (Flattened Device Tree), model: Globalscale Technologies Guruplug Server Plus
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c07205bc, node_mem_map c0992000
  Normal zone: 1024 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 131072 pages, LIFO batch:31
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200n8 root=/dev/sda2 rw rootwait
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512012K/524288K available (5015K kernel code, 328K rwdata, 1676K rodata, 261K init, 385K bss, 12276K reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc0691124   (6693 kB)
      .init : 0xc0692000 - 0xc06d370c   ( 262 kB)
      .data : 0xc06d4000 - 0xc0726028   ( 329 kB)
       .bss : 0xc0726028 - 0xc0786740   ( 386 kB)
SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:114
sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
Console: colour dummy device 80x30
Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys blkio
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0xc04c0a38 - 0xc04c0a90
devtmpfs: initialized
pinctrl core: initialized pinctrl subsystem
regulator-dummy: no parameters
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cpuidle: using governor menu
Kirkwood: MV88F6281-A0, TCLK=0.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switched to clocksource orion_clocksource
FS-Cache: Loaded
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
zbud: loaded
FS-Cache: Netfs 'nfs' registered for caching
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4000, nTxLock = 32000
msgmni has been set to 1000
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
kirkwood-pinctrl f1010000.pinctrl: registered pinctrl driver
mv_xor f1060800.xor: Marvell shared XOR driver
mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
mv_xor f1060900.xor: Marvell shared XOR driver
mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 12500000) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
sata_mv f1080000.sata: version 1.28
sata_mv f1080000.sata: slots 32 ports 1
scsi0 : sata_mv
ata1: SATA max UDMA/133 irq 25
NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit), 512MiB, page size: 2048, OOB size: 64
Scanning device for bad blocks
3 ofpart partitions found on MTD device orion_nand
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "data"
libphy: orion_mdio_bus: probed
mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 02:50:43:0c:95:90
mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC address 02:50:43:34:97:5e
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.ehci: EHCI Host Controller
orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
orion-ehci f1050000.ehci: irq 23, io mem 0xf1050000
orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver ums-cypress
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mousedev: PS/2 mouse device common for all mice
rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
i2c /dev entries driver
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mvsdio f1090000.mvsdio: no pins associated
mmc0: new high speed SDIO card at address 0001
mvsdio f1090000.mvsdio: lacking card detect (fall back to polling)
sdhci-pltfm: SDHCI platform and OF driver helper
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
zram: Created 1 device(s) ...
TCP: cubic registered
NET: Registered protocol family 10
NET: Registered protocol family 17
Key type dns_resolver registered
registered taskstats version 1
rtc-mv f1010300.rtc: setting system clock to 2013-12-09 18:27:23 UTC (1386613643)
usb 1-1: new high-speed USB device number 2 using orion-ehci
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
ata1.00: ATA-8: WDC WD2500BEVT-00A23T0, 01.01A01, max UDMA/133
ata1.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      WDC WD2500BEVT-0 01.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
usb 1-1.1: new high-speed USB device number 3 using orion-ehci
 sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 8:2.
usb-storage 1-1.1:1.0: USB Mass Storage device detected
scsi1 : usb-storage 1-1.1:1.0
devtmpfs: mounted
Freeing unused kernel memory: 260K (c0692000 - c06d3000)
scsi 1:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9909 PQ: 0 ANSI: 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
scsi 1:0:0:1: Direct-Access     Generic  STORAGE DEVICE   9909 PQ: 0 ANSI: 0
sd 1:0:0:1: Attached scsi generic sg2 type 0
sd 1:0:0:0: [sdb] Attached SCSI removable disk
sd 1:0:0:1: [sdc] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB)
sd 1:0:0:1: [sdc] Write Protect is off
sd 1:0:0:1: [sdc] Mode Sense: 03 00 00 00
sd 1:0:0:1: [sdc] No Caching mode page found
sd 1:0:0:1: [sdc] Assuming drive cache: write through
sd 1:0:0:1: [sdc] No Caching mode page found
sd 1:0:0:1: [sdc] Assuming drive cache: write through
 sdc: sdc1 sdc2
sd 1:0:0:1: [sdc] No Caching mode page found
sd 1:0:0:1: [sdc] Assuming drive cache: write through
sd 1:0:0:1: [sdc] Attached SCSI removable disk
systemd-udevd[825]: starting version 204
orion_wdt: Initial timeout 21 sec
cfg80211: Calling CRDA to update world regulatory domain
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
libertas_sdio: failed to load firmware
Bluetooth: module_cfg_cmd(f1): timeout: 1
EXT4-fs (sda2): re-mounted. Opts: (null)
EXT4-fs (sda2): re-mounted. Opts: (null)
fuse init (API version 7.22)
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
mv643xx_eth_port mv643xx_eth_port.1 eth1: link up, 1000 Mb/s, full duplex, flow control disabled
IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
root@NS2:/# ls

This doesn't seem to be mission critical for me though.
4  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: October 10, 2013, 03:31:51 AM
Although the console 'freezes' with Device Tree kernels earlier than 3.11.2 for Guruplug (I am running this on my Guruplugs) it is possible that you may get access using SSH after a period for the kernel to boot fully.

Another possibility is do you have a line 'machid=a63' in your u-boot environment? (Replaces arcNumber.)
5  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 26, 2013, 03:41:48 PM
I should also say that I compiled natively on an eSata Sheevaplug and thus had no need of cross compiler tools.
6  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 26, 2013, 03:37:10 PM
Ladies and Gentlemen, you are genius's (geni'i?) and I have successfully compiled 3.11.1 with the suggested configuration differences and it works! I admit the first couple of runs failed partly because I was using a copied system from another which had intensive applications running (Freeswitch) and partly because i forgot to re-enable the console in /etc/inittab. So I show the console output from the last reboot to prompt for info. I don't think I can post my config.gz file here.
Code:
reboot: Restarting system


U-Boot 2013.04-00006-g1aa0913-dirty (Jun 12 2013 - 02:42:25)
Marvell-Sheevaplug - eSATA - SD/MMC

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
MMC:   mvsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
====== BootStrap start ======
Card did not respond to voltage select!
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: not available  Bus 1: OK
  Device 1: Model: WDC WD3200BPVT-80JJ5T0 Firm: 01.01A01 Ser#:  WD-WXG1C52E4334
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
Card did not respond to voltage select!
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: not available  Bus 1: OK
  Device 1: Model: WDC WD3200BPVT-80JJ5T0 Firm: 01.01A01 Ser#:  WD-WXG1C52E4334
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
Card did not respond to voltage select!
** Bad device mmc 0 **
MMC Device 1 not found
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 0 **
MMC Device 1 not found
** Bad device mmc 1 **
** Bad device usb 0 **
** Bad device usb 1 **
** Bad device usb 0 **
** Bad device usb 1 **
** Bad device ide 0 **
2464568 bytes read in 967 ms (2.4 MiB/s)

## Checking Image at 00800000 ...
   Legacy image found
   Image Name:   Linux-Kirkwood-esata-sheevaplug-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2464504 Bytes = 2.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-Kirkwood-esata-sheevaplug-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2464504 Bytes = 2.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Using machid 0xa76 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 3.11.1 (root@debian) (gcc version 4.8.1 (Debian 4.8.1-10) ) #1 Thu Sep 26 15:44:57 BST 2013
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell Kirkwood (Flattened Device Tree), model: Globalscale Technologies eSATA SheevaPlug
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200n8 root=/dev/sda2 rw rootwait panic=5
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512352K/524288K available (4886K kernel code, 312K rwdata, 1508K rodata, 248K init, 377K bss, 11936K reserved)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc0646ba8   (6395 kB)
      .init : 0xc0647000 - 0xc0685334   ( 249 kB)
      .data : 0xc0686000 - 0xc06d4018   ( 313 kB)
       .bss : 0xc06d4018 - 0xc0732620   ( 378 kB)
SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:114
sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
Console: colour dummy device 80x30
Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys blkio
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0xc04a09d0 - 0xc04a0a0c
devtmpfs: initialized
pinctrl core: initialized pinctrl subsystem
regulator-dummy: no parameters
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
Kirkwood: MV88F6281-A0, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
USB Power: Failed to request enable GPIO29: -517
reg-fixed-voltage 1.regulator: Failed to register regulator: -517
platform 1.regulator: Driver reg-fixed-voltage requests probe deferral
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switched to clocksource orion_clocksource
FS-Cache: Loaded
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
zbud: loaded
FS-Cache: Netfs 'nfs' registered for caching
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4002, nTxLock = 32022
msgmni has been set to 1000
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
kirkwood-pinctrl f1010000.pinctrl: registered pinctrl driver
mv_xor f1060800.xor: Marvell shared XOR driver
mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
mv_xor f1060900.xor: Marvell shared XOR driver
mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
Serial: 8250/16550 driver, 2 ports, IRQ sharing enabled
f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
sata_mv f1080000.sata: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 21
ata2: SATA max UDMA/133 irq 21
NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit), 512MiB, page size: 2048, OOB size: 64
Scanning device for bad blocks
Bad eraseblock 326 at 0x0000028c0000
Bad eraseblock 2247 at 0x0000118e0000
Bad eraseblock 3112 at 0x000018500000
3 ofpart partitions found on MTD device orion_nand
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
libphy: orion_mdio_bus: probed
mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
ata1: SATA link down (SStatus 0 SControl F300)
mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:50:43:01:4d:07
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.ehci: EHCI Host Controller
orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
orion-ehci f1050000.ehci: irq 19, io mem 0xf1050000
orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver ums-cypress
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
mousedev: PS/2 mouse device common for all mice
rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mvsdio f1090000.mvsdio: Got CD GPIO #44.
mvsdio f1090000.mvsdio: Got WP GPIO #47.
mvsdio f1090000.mvsdio: using GPIO for card detection
sdhci-pltfm: SDHCI platform and OF driver helper
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
zram: Created 1 device(s) ...
TCP: cubic registered
NET: Registered protocol family 10
NET: Registered protocol family 17
Key type dns_resolver registered
registered taskstats version 1
USB Power: 5000 mV
rtc-mv f1010300.rtc: setting system clock to 2013-09-26 22:25:57 UTC (1380234357)
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
ata2.00: ATA-8: WDC WD3200BPVT-80JJ5T0, 01.01A01, max UDMA/133
ata2.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access     ATA      WDC WD3200BPVT-8 01.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
sd 1:0:0:0: [sda] 4096-byte physical blocks
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 < sda5 >
sd 1:0:0:0: [sda] Attached SCSI disk
EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 8:2.
devtmpfs: mounted
Freeing unused kernel memory: 248K (c0647000 - c0685000)
Mount failed for selinuxfs on /sys/fs/selinux:  No such file or directory
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevdsystemd-udevd[799]: starting version 204
. ok
[ ok ] Synthesizing the initial hotplug events...done.
[....] Waiting for /dev to be fully populated...orion_wdt: Initial timeout 21 sec
done.
[ ok ] Setting preliminary keymap...done.
[ ok ] Setting parameters of disc: (none).
[ ok ] Activating swap...done.
EXT4-fs (sda2): re-mounted. Opts: (null)
[....] Checking root file system...fsck from util-linux 2.20.1
/dev/sda2: clean, 252005/19431424 files, 3649038/77702912 blocks
done.
EXT4-fs (sda2): re-mounted. Opts: (null)
[ ok ] Cleaning up temporary files... /tmp.
[ ok ] Activating lvm and md swap...done.
[....] Checking file systems...fsck from util-linux 2.20.1
/dev/sda1: clean, 15/62248 files, 19620/248832 blocks
done.
[....] Loading kernel modules...fuse init (API version 7.22)
done.
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables ...done.
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Listening on LPF/eth0/00:50:43:01:4d:07
Sending on   LPF/eth0/00:50:43:01:4d:07
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPOFFER from 192.168.2.253
DHCPACK from 192.168.2.253
bound to 192.168.2.240 -- renewal in 41362 seconds.
done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting up ALSA...done (none loaded).
[info] Setting console screen modes.
setterm: cannot (un)set powersave mode: Inappropriate ioctl for device
[ ok ] Setting up console font and keymap...done.
[ ok ] Setting sensors limits.
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[ ok ] Updating the system logo...done.
[ ok ] Starting enhanced syslogd: rsyslogd.
[ ok ] Starting web server: apache2.
Starting Advanced TFTP server: atftpd.
[ ok ] Starting periodic command scheduler: cron.
[ ok ] Starting system message bus: dbus.
[ ok ] Starting Bacula Storage daemon...: bacula-sd.
[ ok ] Starting Bacula File daemon...: bacula-fd.
[ ok ] Loading cpufreq kernel modules...done (none).
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting internet superserver: inetd.
[ ok ] Starting ftp server: proftpd.
[ ok ] Starting MySQL database server: mysqld . . ..
[info] Checking for tables which need an upgrade, are corrupt or were
not closed cleanly..
[ ok ] Starting Bacula Director...: bacula-dir.
saned disabled; edit /etc/default/saned
[ ok ] Starting network management services::  snmpd[....] Starting OpenBSD Secure Shell server: sshd.
Path is:-
/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin/
No framebuffer device was found. Starting VNC
Starting  for user 'root' on :1
Starting with -depth 24 -geometry 1366x768 :1

New 'X' desktop is debian:1

Starting applications specified in //.vnc/xstartup
Log file is //.vnc/debian:1.log

mv643xx_eth_port mv643xx_eth_port.0 eth0: The PHY does not support set_wol, was CONFIG_MARVELL_PHY enabled?
Stopping tightvncserver for user 'root' on :1
Killing Xtightvnc process ID 3098
Path is:-
/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin/:/usr/X11R6/bin/
No framebuffer device was found. Starting VNC
Starting  for user 'root' on :1
Starting with -depth 24 -geometry 1366x768 :1

New 'X' desktop is debian:1

Starting applications specified in //.vnc/xstartup
Log file is //.vnc/debian:1.log


Debian GNU/Linux jessie/sid debian ttyS0

debian login: root
Password:
Last login: Thu Sep 26 23:23:20 BST 2013 from 192.168.2.47 on pts/0
Linux debian 3.11.1 #1 Thu Sep 26 15:44:57 BST 2013 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@debian:~# uname -a
Linux debian 3.11.1 #1 Thu Sep 26 15:44:57 BST 2013 armv5tel GNU/Linux


I see the console is reported properly too.
Thanks again gents(?)
7  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 23, 2013, 02:47:32 PM
Finally, after much swearing, cussing and almost losing the will to live, I have repaired my development Sheevaplug (new eSata disk drive) and am now in a position to start compiling a kernel natively. I will look at the above config elements tomorrow time permitting and see what is what. It really didn't help repairs with no console output. I also need to mirror disks so a SATA multiplexor to create a RAID array would be nice.

I think you are on the point of cracking the problem. Hopefully someone will confirm the cure!  Cheesy
8  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 18, 2013, 02:07:23 AM
I confirm that I find the same as Birdman on the disk thing. Also because my /etc/fstab requires it, my disks are unmounted, a fs check performed and then remounted. This is normal and a bit of a lifesaver as the i-node count get corrupted in service.
9  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 17, 2013, 12:23:52 PM
Thanks for your info and update. I think you are on to it. Is there a link for the Fedora kernel DT source? More minds the better especially to aid my old, worn out grey cells! Tony.
10  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 17, 2013, 02:02:46 AM
PQA, is your Fedora 3.10.10 kernel a Device Tree kernel? If not, this should help confirm that the console issue is in the Device Tree rather than the kernel itself.

I had a little look at schematics for a Guruplug and some of the Kirkwood data sheet and some of the MPP pins have multiple functions set up depending on initialisation. I see that MPP8 is shared between a gpio control of RTS (Request To Send) for serial and SDA for i2c/smbus; MPP9 is shared between gpio CTS (Clear To Send) and SCK for i2C/smbus.

I have the feeling that when the hardware is activated by the Device Tree code, the setup is not performed correctly for UART0 and possibly for other hardware. I'm not particularly familiar with the Kirkwood architecture so poring over code and datasheets to tie up the devices and initialisation may take some time and I do have other things to do. I am convinced that the kernel itself (as opposed to Device tree) is OK and the problem is not a .config issue.

11  Hardware and U-Boot firmware / Hardware / Second Sata/micro SDHC ports for Guruplug Server Plus on: September 16, 2013, 05:18:03 AM
I know this product is old and hardly state of the art these days but I rely on them for my network services. Lately, they have become less than perfect in the reliability stakes. I cannot let this situation continue.

I find that I get errors on both MMC (sdhc cards) and hard disks. I am in the process of rebuilding them with external power supply and heatsinks to keep things cooler inside but I am still getting write errors on the unit rebuilt. I have replaced the RTC battery and the micro SDHC card.

In order to improve reliability, I am wondering if the second Sata port has all the components and the second micro SDHC 'socket' is equippped as well. I have checked the board traces against the schematic so I guess this was in the mind of the designer. I know I will have to get connectors as a minimum but I am wondering if anyone has already equipped these second ports and what was needed to make them work (hardware components, u-boot and kernel tweaks)?

Since I need at least two gigabit ethernet ports for routing etc, there are not too many replacement options - perhaps the Smile plug but that is a bit pricey for the job. Any suggestions?
12  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 15, 2013, 05:58:32 AM
Just to add dmesg HDD errors for an esata sheevaplug:-

Code:
ata2: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
ata2: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
ata2: SError: { 10B8B Dispar }
ata2: hard resetting link
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata2.00: configured for UDMA/133
ata2: EH complete
ata2: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
ata2: edma_err_cause=00000020 pp_flags=00000003, SError=00180000
ata2: SError: { 10B8B Dispar }
ata2: hard resetting link
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata2.00: configured for UDMA/133
ata2: EH complete

2 Errors since last reboot a few days ago. At least these are not destructive. Kernel is DT 3.10.9
13  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 15, 2013, 05:22:31 AM
Marcus,

Thanks for your survey. Actually I am using 32Gb Sandisk Mobile ultra for my Guruplugs! I use 16Gb Integral Endurance (which had been recommended by NewIT because of their Single Layer Cell structure) for the two standard sheevaplugs. However, my other three Sheevaplugs are eSata and boot from the HDD drives (3Gb/Sec interfaces) and I am struggling to rebuild my development system with new 320Gb Western Digital Scorpio Blue drives. Although it cannot be related directly to the Guruplugs, I have tried things like 50cm cables, common power supplies (to avoid ground loops), replaced corroded RTC batteries but still there are issues. I have not seen problems with my eSata Tonidoplugs (also kirkwood) which boot from internal 1TB eSata disks.

I will say that the i-node errors seem to occur at approximately the same location which suggests overuse of the same cells of disk sector.

I did also find these errors on an old 3.7.7 non-Device Tree kernels.  Undecided

I am considering setting up a cron job to reboot my systems automatically during sleeping hours to effect a fsck daily.
14  Linux Stuff / Kernel / Re: 3.9.0+ Device-tree kernels on: September 15, 2013, 02:09:53 AM
Marcus, I had my suspicions that Device Tree for Kirkwood and Dove kernels were the problem and your work confirms that. Thankyou. I would have tried compiling a non-dt kernel but time has not permitted experimentation. I now no longer need to. I am puzzled why there are no more reports of this problem from others though? I do not want to delve into kernel issues as I want to consider the kernel as a 'black box'. Increasingly it seems that I have to. The same is true of u-boot. I want the latest versions to have significant improvements or corrections to the system - much like Microsoft Windows has updates that should be bulletproof (well that is a commercial product - OK I've got the carbolic soap ready to wash my mouth out). I am wondering if Netconsole is compiled into the kernel which might give a workable console when the serial port does not.

I also have had problems with hard disk or SDHC writes which may be kernel synchronisation with the HDD or the SDHC hardware and I have the feeling that there is something wrong with low level file system software (it seems that the problem happens to ext3 and ext4 formatted partitions) and I have seen slow writes being a problem. Every so often the number of errors seem to make a disk go read-only and requires a reboot to force a fs check. That corrects i-node errors. I note that the errors are frequently in the same 'place' so that suggests that a regular type of write for a certain section of code. That said, I think that the temperature inside sheeva and guruplugs may be a factor and a nice version of sensors for sheevaplug would be nice.

Thanks also for the u-boot BTW. I had noticed compilation issues with my version in that mmc has been 'mucked about with' and I want ext4 built in.
15  Hardware and U-Boot firmware / U-Boot stuff / Re: bad howto ? on: September 09, 2013, 03:24:10 AM
You appear to be loading your u-boot to SDRAM address 0x6400000 and trying to execute code from 0x0c100000. I'm sure this will not work. If you try to execute from 0x06400000 plus and offset for the header (possibly 0x6400200), you may get something but don't expect u-boot to work completely correctly in SDRAM.
Pages: [1] 2 3