• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 2 3 [4] 5 6 ... 10
 31 
 on: January 16, 2014, 10:34:47 AM 
Started by odoll - Last post by apemberton
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?

 32 
 on: January 16, 2014, 06:56:31 AM 
Started by odoll - Last post by odoll
I think I haven't seen it been mentioned somewhere else in this forum, yet so let me make the following hint:

I recently noticed that Michael updated his u-boot binaries repository at http://people.debian.org/~tbm/u-boot/ with a newer version which is called 2013.10-2 from 02-Nov-2013.

I upgraded both my SheevaPlugs (prod and spare) a few days ago and I noticed no issues since then. Even with having the system on the 4 GB MicroSD, which, when plugged in instead of another 4 GB 'big' SD, usually now and then loses the USB attached 2 TB HDD (http://www.plugcomputer.org/plugforum/index.php?topic=6113.0).

 33 
 on: December 24, 2013, 03:29:28 AM 
Started by mgillespie - Last post by mgillespie
Link is the same as usual (so save you scrolling back to page 1).


http://www.mediafire.com/sheeva-with-debian


 34 
 on: December 24, 2013, 03:21:25 AM 
Started by mgillespie - Last post by mgillespie
Updated the script and prebuilt images today with the latest Debian Wheezy (7.3).   Also posted a complete ready to go ESIA application image with Linux 3.0.60/Wheezy7.3

I would recommend running this with DenX U-Boot 2013.10-rc1-00034-g2b26201
(not created/compiled by me, but I have put it in the same mediafire directory, incase it disappears from the web in the future)

Tested it all out on my original Globalscale Sheevaplug, which aside from a powersupply replacement has turned out to be a very trusty and reliable bit of kit.

Once loaded, don't forget to change the password, create new ssl keys, flash the latest sheeva kernel using the update script:

http://www.xilka.com/sheeva/kernel/UPDATE-KERNEL.sh

and pick up the latest Debian package updates with an apt-get update.

Enjoy.

 35 
 on: December 23, 2013, 05:45:59 PM 
Started by UnaClocker - Last post by UnaClocker
Heya guys.. It's been a good 4 years with my SheevaPlug. I got my SheevaPlug for Christmas 2009. It's been running 24/7 ever since, as my fileserver (NAS), webserver, and firewall. I used the same 8gb SD card the whole time, though I managed to fill it all the way up a year or two back and have been kind of cramped ever since.
I just wanted to thank everyone here for the great help. Especially cbxbiker61 for continuing to release pre-compiled kernels for the unit, I upgraded several times along the way and it was always a relief to have a kernel that Just Worked. Smiley
In the end, I'm retiring it because I wanted to play with something new. My new server is a budget PC running FreeBSD.
If anyone would like my Sheeva, let me know.

 36 
 on: December 12, 2013, 11:08:06 PM 
Started by cbxbiker61 - Last post by cbxbiker61
apemberton, it's great that your testing on a wide variety of systems!

I fixed the typo in UPDATE-KERNEL.sh, it may be a while before it makes it's way to the main web servers due to caching.

As far as the mvsdio interrupt warning, I'm seeing that on my sheevaplug and it hasn't caused any problems for me.  I'm sure that in due time someone will figure out what changed in the interrupt handling code and fix it.

 37 
 on: December 10, 2013, 05:25:11 AM 
Started by cbxbiker61 - Last post by apemberton
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.

 38 
 on: December 01, 2013, 07:53:35 AM 
Started by math - Last post by math
Hum... what's up doc...

The green led was lightening an hour ago.. and suddently, no led !
I have opened the guruplug to check the Power supply : sounds good! and I don't think it has burned as I can see on lots pictures on that forum...

NB: it was plug 24/24 7/7 since more than 3 years (w/o Wifi nor bluetooth)

Please, give me advices and thank you.

 39 
 on: December 01, 2013, 06:11:56 AM 
Started by math - Last post by math
Hello,

Today I'm facing a new issue on my guruplug.
I don't know why nor when exactly, I have lost eth connection to guruplug.

I tryed to reboot, but unfortunately, guruplug didn't boot correctly. I don't know why...
So I decided to plug the jtag to see what happened on the console. I usually got the u-boot messages and the log booting messages displayed. But nothing is displayed today; black console screen.

I never installed minicom on my old xubuntu desktop. I was using putty on Serial over /dev/ttyUSB0 speed=115200

Putty setting didn't changed on my desktop (tryed both Windows and Linux Xubuntu) and I was connecting well and instantaneously few weeks ago.. but today, it didn't connect.

Guruplug has the green led lightened..

What would you suggest ?

Thanks for your support.

 40 
 on: November 25, 2013, 02:06:42 AM 
Started by ineiti - Last post by ineiti
Trying to revive this thorny subject... Here is what I tried:

- u-boot from u-boot_2013.10-2_armel.deb
- 3.12.1-version of the kernel from http://www.xilka.com/
- the latest version of the sd8787-firmware (md5sum: bda543cb5943eac34e16d12911f3ee99)
- the latest version of hostapd from git

But there is definitively something wrong, as I only get a "mlan0"-interface, and no "wlan0" or other.

If I use mlan0 in hostapd, I get the following error:

Configuration file: hostapd.conf
ieee80211 phy0: mlan0: changing to 3 not supported
ieee80211 phy0: mlan0: changing to 3 not supported
nl80211: Could not configure driver mode
nl80211 driver initialization failed.
hostapd_free_hapd_data: Interface mlan0 wasn't started

Any idea what I missed? It works fine in client-mode, but I'd prefer AP Wink

Pages: 1 2 3 [4] 5 6 ... 10