• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2 3
1  Linux Stuff / Linux distributions / Re: The alternative Debian install method. on: August 11, 2014, 02:23:52 PM
I have the plug for some years now, booting from sd card debian wheezy, i have some old sd rootfs.tar.gz back ups that can extract to sd card if something is wrong.
I tried to get a fresh new copy and formated a partition on sd card, created inside the rootfs.tar.gz   with DebianSheeva1-7.sh script, copy to a usb disk attached with plug and extract it from the usb disk to the sd partition
I reboot and I try to connect with putty (from another lan computer) get the login screen and type  user: root   password:nosoup4u , I get "acess denied"
I reset the password from shadow file reboot--user:root-password:<enter>--"acess denied"
Can rootfs.tar.gz be used like this, meaning , extract and get it work;; or I am doing something wrong?
I also can boot form plug's internal memory if I pull the sd card and reboot so I do some stuff but not get the generated rootfs from your script....
Thanx in advance!
2  Linux Stuff / Kernel / Re: 2.6.39.2 new kernel available on: July 05, 2011, 01:25:49 PM
It's working fine with my debian wheezy on sd card sheeva plug, faster and with better memory management.
3  Hardware and U-Boot firmware / Hardware / Re: Sheeva cant boot from sd card. on: July 05, 2011, 01:19:55 PM
@ moderators : I can't edit my message so I started a new reply to continue writing.

So I extracted again my old working backup and this time I upgraded the kernel to the latest version 2.6.39.2 and after I did the necessary apt-get updates and dist-upgrades I rebooted to check if the problem remains but this time it worked.
And until now I haven't got any problems.
I think that the problem was that the old kernel I was using was not working well with the new wheezy philosophy.
4  Hardware and U-Boot firmware / Hardware / Re: Sheeva cant boot from sd card. on: July 05, 2011, 01:04:03 PM
I extracted an old backup I had from 3/2011 and worked fine with debian wheezy.
I also rebooted 2 times and the plug was workink ok from sd card.
After that I did apt-get update with 195 updates and after that a apt-get dist upgrade.
And then after a reboot the same messages but without warnings about the new /run directory because after the updates the /run was there.
So again I couldn't boot from sd card and the boot process was stoping with the message "unable to receive ctrl connection: Function not implemented".. below is the boot proccess ...
Code:
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Jul 19 2009 - 16:03:28) Marvell version: 3.4.19

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  3  2  1  0
SDHC found. Card desciption is:
Manufacturer:       0x1d, OEM "AD"
Product name:       "SD   ", revision 1.0
Serial number:      2690664377
Manufacturing date: 4/2011
CRC:                0x00, b0 = 0

2821988 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32.6
   Created:      2010-01-25  20:14:12 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2821924 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.32.6 (kelly@speedy) (gcc version 4.4.1 (Sourcery G++ Lite er) ) #1 PREEMPT Mon Jan 25 13:14:06 MST 2010
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell SheevaPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 rw root=/dev/mmcblk0p2 rootdelay=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: 256MB 256MB = 512MB total
Memory: 513152KB available (5104K code, 1034K data, 140K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:114
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A0, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) Β 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4010, nTxLock = 32083
msgmni has been set to 1002
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 3553 at 0x00001bc20000
Bad eraseblock 3554 at 0x00001bc40000
Bad eraseblock 3555 at 0x00001bc60000
Bad eraseblock 3556 at 0x00001bc80000
Bad eraseblock 3557 at 0x00001bca0000
Bad eraseblock 3558 at 0x00001bcc0000
Bad eraseblock 3559 at 0x00001bce0000
Bad eraseblock 3560 at 0x00001bd00000
Bad eraseblock 3561 at 0x00001bd20000
Bad eraseblock 3562 at 0x00001bd40000
Bad eraseblock 3563 at 0x00001bd60000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:50:43:01:6a:6a
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
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
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv 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
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: plug:green:health
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address b368
mmcblk0: mmc0:b368 SD    7.51 GiB
 mmcblk0: p1 p2
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
rtc-mv rtc-mv: setting system clock to 2011-07-01 22:22:45 UTC (1309558965)
Waiting 5sec before mounting root device...
usb 1-1: new high speed USB device using orion-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
VFS: Mounted root (ext2 filesystem) on device 179:2.
Freeing init memory: 140K

INIT: version 2.88 booscsi 0:0:0:0: Direct-Access     WD       My Passport 070A 2003 PQ: 0 ANSI: 4
tingsd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 975400960 512-byte logical blocks: (499 GB/465 GiB)
scsi 0:0:0:1: CD-ROM            WD       Virtual CD 070A  2003 PQ: 0 ANSI: 4
scsi 0:0:0:1: Attached scsi generic sg1 type 5
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
scsi 0:0:0:2: Enclosure         WD       SES Device       2003 PQ: 0 ANSI: 4
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda:
scsi 0:0:0:2: Attached scsi generic sg2 type 13
Using makefile-style concurrent boot in runlevel S.
.udev/ already exists on the static /dev! ... (warning).
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...udevd[627]: unable to receive ctrl connection: Function not implemented
udevd[627]: unable to receive ctrl connection: Function not implemented
udevd[627]: unable to receive ctrl connection: Function not implemented
udevd[627]: unable to receive ctrl connection: Function not implemented
udevd[62 sda17]: unable to re sda2ceive ctrl conne
ction: Function not implemented
udevd[627]: sd 0:0:0:0: [sda] Assuming drive cache: write through
unable to receivsd 0:0:0:0: [sda] Attached SCSI disk
e ctrl connection: Function not implemented
udevd[627]: unable to receive ctrl connection: Function not implemented
...
...
udevd[627]: unable to receive ctrl connection: Function not implemented
udevd[627]: unable to receive ctrl connesr0: scsi3-mmc drive: 51x/51x caddy
ction: Function Uniform CD-ROM driver Revision: 3.20
not implemented
udevd[627]: unable to receive ctrl connection: Function not implemented
udevd[627]: unable to receive ctrl connection: Function not implemented
udevd[627]: unable to receive ctrl connection: Function not implemented
...
...
udevd[627]: unable to receive ctrl connection: Function not implemented
udevd[627]: unable to receive ctrl connection: Function not implemented
WTF?
The last days I had in mind to update my sd kernel because I was running a very old version 2.6.32.6
So


5  Hardware and U-Boot firmware / Hardware / Re: Sheeva cant boot from sd card. on: June 28, 2011, 01:41:22 PM
I added the following line to /etc/fstab of the sd card ...
6  Hardware and U-Boot firmware / Hardware / Re: Sheeva cant boot from sd card. on: June 28, 2011, 01:19:17 PM
I renamed the /dev/.udevd from the SD to /dev/.1udev-for-delete
added the following line to /fstab
  tmpfs /run              tmpfs nodev,nosuid,size=100M,mode=0755  0 0
Rebooted the plug but with no luck
Code:
Starting the hotplug events dispatcher: udevdudevd[589]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'

.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...udevd[590]: unable to receive ctrl connection: Function not implemented


udevd[590]: unable to receive ctrl connection: Function not implemented

After that I created the /run directory to the sd  card
and again the same bad luck...
From the  http://wiki.debian.org/ReleaseGoals/RunDirectory#Packages_using_.2BAC8-dev.2BAC8..2A
it says :
/dev/.udev/, v167+ will automatically use /run/udev if /run is available and writable. (168-2 available from unstable)

and from http://wiki.debian.org/ReleaseGoals/RunDirectory#How_to_transition_from_.2BAC8-dev.2C_.2BAC8-dev.2BAC8-shm_or_.2BAC8-etc_to_.2BAC8-run.3F
says that :
All users must transition to /run for wheezy
....
1 Depend on initscripts (>= 2.88dsf-13.3)
2 Replace all usage of /dev/.* /dev/shm/.* or etc with /run
3 Move all files in /dev/.* /dev/shm/.* or etc to /run in the package postinst
...
If you need to use /run in the early initramfs, you'll need to support both /run and the existing /dev/.xxx as a fallback:



WTF?
Can we use a symlink to temporary resolve this??



7  Hardware and U-Boot firmware / Hardware / Sheeva cant boot from sd card. on: June 27, 2011, 07:02:53 AM
I've been running almost two years sheeva plug from sd card and suddenly I noticed some kernel i/o errors.
FYI I'm running Debian testing...
I booted from nand and fsck the sd card with many errors so I proceeded with fdisk and extracted a backup I had from last month to the sd card.
e2fsck says that mmcblk0p1 (kernel uimage) and mmcblk0p2(rootfs) are ok
But when i'm trying to boot from sd-card I get a "udevd[596]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev"
and after that I get stuck to the error : Waiting for /dev to be fully populated...udevd[597]: unable to receive ctrl connection: Function not implemented
udevd[597]: unable to receive ctrl connection: Function not implemented

Can someone help to resolve this or is my sd-card almost dead ?
Below is the serial console print when I try to boot from sd card (mmc).
Code:
Marvell>> boot
SDHC found. Card desciption is:
Manufacturer:       0x27, OEM "PH"
Product name:       "SD08G", revision 2.0
Serial number:      2953843753
Manufacturing date: 8/2009
CRC:                0x00, b0 = 0

2821988 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32.6
   Created:      2010-01-25  20:14:12 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2821924 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.32.6 (kelly@speedy) (gcc version 4.4.1 (Sourcery G++ Lite er) ) #1 PREEMPT Mon Jan 25 13:14:06 MST 2010
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell SheevaPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 rw root=/dev/mmcblk0p2 rootdelay=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: 256MB 256MB = 512MB total
Memory: 513152KB available (5104K code, 1034K data, 140K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:114
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A0, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4010, nTxLock = 32083
msgmni has been set to 1002
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 3553 at 0x00001bc20000
Bad eraseblock 3554 at 0x00001bc40000
Bad eraseblock 3555 at 0x00001bc60000
Bad eraseblock 3556 at 0x00001bc80000
Bad eraseblock 3557 at 0x00001bca0000
Bad eraseblock 3558 at 0x00001bcc0000
Bad eraseblock 3559 at 0x00001bce0000
Bad eraseblock 3560 at 0x00001bd00000
Bad eraseblock 3561 at 0x00001bd20000
Bad eraseblock 3562 at 0x00001bd40000
Bad eraseblock 3563 at 0x00001bd60000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:50:43:01:6a:6a
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
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
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv 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
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: plug:green:health
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address 0007
mmcblk0: mmc0:0007 SD08G 7.49 GiB
 mmcblk0: p1 p2
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
rtc-mv rtc-mv: setting system clock to 2011-06-26 21:51:29 UTC (1309125089)
Waiting 5sec before mounting root device...
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem) on device 179:2.
Freeing init memory: 140K

INIT: version 2.88 bootingUsing makefile-style concurrent boot in runlevel S.
.udev/ already exists on the static /dev! ... (warning).
Starting the hotplug events dispatcher: udevdudevd[596]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...udevd[597]: unable to receive ctrl connection: Function not implemented
udevd[597]: unable to receive ctrl connection: Function not implemented
udevd[597]: unable to receive ctrl connection: Function not implemented
udevd[597]: unable to receive ctrl connection: Function not implemented
udevd[597]: unable to receive ctrl connection: Function not implemented
8  General Category / Application ideas and development Q/A / Re: WINE / .net port to GURU Plug ? on: January 26, 2011, 02:10:06 PM
If you can wait a little you may install windows on the plug because the next version of windows will support arm ...
http://arstechnica.com/microsoft/news/2011/01/windows-on-arm-official-but-leaves-many-questions-unanswered.ars
9  General Category / General Discussion / Re: Recommendable SD(HC) cards/USB sticks for the Sheevaplug on: September 21, 2010, 12:54:09 PM
I have a 8GB ssd hc almost a year now and I'm running debian squeeze from it.
I am also using a usb disk for extra storage.
I think that 4GB sd card is enough (if you keep it clean with only what you need and not filling it up with trash )
And the other thing is that a smaller card has lower price to replace it.
10  Hardware and U-Boot firmware / Hardware / Re: Having replaced my Sheeva power supply... on: September 19, 2010, 10:17:38 AM
For the extra heat I also attached a heat sink and left the plug open for the air to flow, because the plug's board is heating a lot.
This picture is taken before I replaced the power supply.


My full post...
http://plugcomputer.org/plugforum/index.php?topic=1735.msg11797#msg11797
11  Hardware and U-Boot firmware / Hardware / Re: Poll: What is the status of your SheevaPlug's Power Supply? on: September 17, 2010, 01:58:28 PM
I had a power supply failure and replaced it with a switced 5v-24v / 3A external p.s and the plug comp. is running fine until now.
After I replaced it I noticed that the plug was running faster (faster boot time, remote response, iceweasel page draw etc).
I also have connected a usb powered 500GB disk, but it's covered by the plug's usb output.
Another thing that I posted on another thread is :
Why when I'm using an external 5v/3A power supply it's relatively cool or warm but when I was using my plug's original power supply (which is dead now) it was so hot that sometimes you could not touch the little metal case?
The answer is : because the plug's original power supply is for trash.
So the best thing to do is to replace it as soon as possible....
12  Hardware and U-Boot firmware / Hardware / Re: Having replaced my Sheeva power supply... on: September 16, 2010, 12:52:51 PM
I'm a happy plug computer addict with external power supply, and it's working fine until now(fingers crossed).
So I think that the right question is:
Why when I'm using an external 5v/3A power supply it's relatively cool or warm but when I was using my plug's original power supply (which is dead now) it was so hot that sometimes you could not touch the little metal case?
13  Hardware and U-Boot firmware / Hardware / Re: GuruPlug Server Plus Heat Problems on: July 14, 2010, 01:20:25 PM
I found an old cpu heat sink and after I cut it a little it was a perfect fit for my sheeva plug.
Except for the thermal silicon paste I also used a plastic cord to tighten the heat sink, I placed it on the side of the leds, where the cpu is located to put more pressure to the heat sink on the cpu, this plastic cord can hold 85 celcius so I think that it won't melt.
The only problem that I was worrying was that the metal heat spreader on top of sheeva board has a little curve so the heat sink wasn't fitting perfectly so I putted a lot of thermal silicon paste to fill the gaps.
Now with a normal use the heat sink is heating a little but when the plug runs with a big cpu load then the heat sink is getting very hot, and this means that it's working.
I'm glad that I helped my little beloved plug to cool down and feel better, also my sd card now is very cool.
As you can see on the pictures I didn't bother to put the other half of the plug and left it open for the air to flow (especially between the psu and the board), it' s more cool that way.  Wink


14  Hardware and U-Boot firmware / Hardware / Re: GuruPlug Server Plus Heat Problems on: July 12, 2010, 03:52:38 AM
to alessio
I wanted to do something similar to your solution for my sheevaplug.
In a previous post you attached some pictures and I have some questions.
In the first picture that shows the original metallic heat spreader attached on top of the mainboard , it seems that the cavities (where the metal attaches on the chip or the memory modules ) are filled with some metal pieces.
Did you put those metal pieces or they are from the manufacturer? cause mine metal spreader has those cavities so I must fill the up with some metal and not only with glue.
And the other question is for the heat sink, is it safe to put only glue to firmly connect the extra heat sink with out worry that it will fall apart?
or we can use something else to tighten it more firmly.
In a previous post in the same thread, jiinx used plastic cords to tight the heat sink (and attached some pictures), is it dangerous for that plastic to  melt down or it can hold to the temperatures that the plug produces?
Thanx in advance...
15  Hardware and U-Boot firmware / Hardware / Re: Replacement Sheevaplug power supply: What's the best thing to do? on: June 25, 2010, 03:49:55 PM
Replacing sheeva's psu with a new external 5v/3A ps adapter, what is the power draw in watts?
Is it the same with the sheeva's psu or more?
Pages: [1] 2 3