 Show Posts
|
|
Pages: 1 ... 3 4 [5] 6 7
|
|
63
|
Linux Stuff / Kernel / Re: [HELP] Guruplug bricked after kernel upgrade
|
on: January 19, 2011, 12:32:26 AM
|
|
Hi,
Finally, I was able to get my guruplug working again. I was having an error tftf'ing the rootfs file, but it was due to the incorrect tftp version installed on the server. As it's a big file, the standard tftp failed, so I had to install another tftp server application, as read somewhere in the forum.
After reinstalling the system, some modules of a newer kernel were needed, so I scp'ed them. Now it boots the newer kernel (Linux guruplug-debian 2.6.33.7), and the best of all is that Zoneminder now is working much better, with cpu loads less than half. I do not know what's the cause of it, but each zmc process was dragging about 23% of cpu before the 'accidental kernel upgrade', and now is consistently ~6%. The load in the ZM console is ~0.1%!!!!!
I want to thank all the users that pointed me to the correct path to get my guruplug back to life (specially radael & richard).
I have also written a process to get Zoneminder working from scratch, so if anyone is interested, ask for it using PM.
Thanks again,
PacoLM
|
|
|
|
|
66
|
Linux Stuff / Kernel / Re: [HELP] Guruplug bricked after kernel upgrade
|
on: January 13, 2011, 03:20:11 PM
|
I've had this error message in the past Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) what it was for me was that I had not selected the following option in menuconfig during the build; File Systems --> Miscellaneous File Systems --> UBIFS file system support Make sure it is built into the Kernel (i.e. showing - and not [M]) as the kernel needs it to read the file system
Regards Rich Could you tell me where are this options? Regards. |
|
|
|
|
68
|
Linux Stuff / Kernel / Re: [HELP] Guruplug bricked after kernel upgrade
|
on: January 13, 2011, 11:05:18 AM
|
Hi, Here is the bootlog right now, any clue? U-Boot 2010.03-01161-gd91b0a9 (Apr 22 2010 - 03:24:41)
Marvell-GuruPlug
SoC: Kirkwood 88F6281_A0
DRAM: 512 MB
NAND: 512 MiB
In: serial
Out: serial
Err: serial
Net: egiga0, egiga1
88E1121 Initialized on egiga0
88E1121 Initialized on egiga1
Hit any key to stop autoboot: 3 2 1 0
*** ERROR: `ipaddr' not set
ping failed; host 192.168.2.1 is not alive
No link on egiga1
*** ERROR: `ipaddr' not set
ping failed; host 192.168.2.1 is not alive
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... Device NOT ready
Request Sense returned 02 3A 00
1 Storage Device(s) found
NAND read: device 0 offset 0x100000, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 06400000 ...
Image Name: Linux-2.6.33.2-00003-g4b82fc0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2688524 Bytes = 2.6 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.33.2-00003-g4b82fc0 (root@msi-linux-build.marvell.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33.fa1)) #1 PREEMPT Thu Apr 22 03:29:35 PDT 2010
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell GuruPlug 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 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
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: 513536KB available (4808K code, 862K 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: 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: 00
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
(2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
(5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
cfg80211: Calling CRDA to update world regulatory domain
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
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 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 = 4014, nTxLock = 32113
msgmni has been set to 1003
alg: No test for stdrng (krng)
io scheduler noop 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: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 3556 at 0x00001bc80000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd2 to ubi0
UBI: MTD device name: "root"
UBI: MTD device size: 507 MiB
UBI: number of good PEBs: 4055
UBI: number of bad PEBs: 1
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 4011
UBI: total number of reserved PEBs: 44
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 2/1
UBI: image sequence number: 0
UBI: background thread "ubi_bgt0d" started, PID 448
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:50:43:67:64:06
net eth1: port 0 with MAC address 00:50:43:67:64:07
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
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: guruplug:red:health
Registered led device: guruplug:green:health
Registered led device: guruplug:red:wmode
Registered led device: guruplug:green:wmode
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: new high speed SDIO card at address 0001
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: 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-01-13 18:03:29 UTC (1294941809)
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 1024 mtdblock0 (driver?)
1f01 4096 mtdblock1 (driver?)
1f02 519168 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[<c003062c>] (unwind_backtrace+0x0/0xd4) from [<c003da9c>] (panic+0x48/0x13c)
[<c003da9c>] (panic+0x48/0x13c) from [<c0008f3c>] (mount_block_root+0x1c4/0x20c)
[<c0008f3c>] (mount_block_root+0x1c4/0x20c) from [<c0009114>] (prepare_namespace+0x8c/0x1cc)
[<c0009114>] (prepare_namespace+0x8c/0x1cc) from [<c000875c>] (kernel_init+0xe0/0x11c)
[<c000875c>] (kernel_init+0xe0/0x11c) from [<c002c3f0>] (kernel_thread_exit+0x0/0x8)
Seems that is not able to find any OS, isn't it?. Is there any reliable way of having a guruplug exactly as a new guruplug? PacoLM |
|
|
|
|
69
|
Linux Stuff / Kernel / Re: [HELP] Guruplug bricked after kernel upgrade
|
on: January 12, 2011, 11:43:35 PM
|
|
Hi,
After two days struggling with this, reading the posts, ubooting, kerneling, resetting.... still no success but I'm on the way. This morning before coming to work, the guruplug passed the uboot process uncompressed the kernel and know I'm getting another error. I will add it to the post this afternoon.
Good news is a little advance, bad news is none of the processes listed in the post worked. I will send also the details. Arriving to this point has been frustrating for me!.
Thanks!,
PacoLM
|
|
|
|
|
70
|
Linux Stuff / Kernel / Re: [HELP] Guruplug bricked after kernel upgrade
|
on: January 11, 2011, 03:32:24 PM
|
Hi, Here again, and I believe I found the guilty of all my pain....a cable of the JTAG. Seems that there's a bad contact that sometimes interrupt the communication. Even that, I was able to flash the uboot, but I'm stuck in the tftp process!. I have set : setenv serverip 192.168.1.33 // ip of my computer setenv ipaddr 192.168.1.43 // ip of guruplug After this I could ping from the computer to the guruplug, when pinging from guruplug to the computer I get this : Using egiga0 device host 192.168.1.33 is alive So looks like the connection it's ok. Could someone explain me how to send the file. I have read some posts/googled and I think I have to open a tftp session in my computer and send the file (put 'filename') and in the other way, run the command 'tftp 0x6400000 <filename' and wait till the process has finished, but this is the output of the guruplug console: Marvell>> tftp 0x6400000 uImage-guruplug
Using egiga0 device
TFTP from server 192.168.1.33; our IP address is 192.168.1.43
Filename 'uImage-guruplug'.
Load address: 0x6400000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
No link on egiga1
Using egiga0 device
TFTP from server 192.168.1.33; our IP address is 192.168.1.43
Filename 'uImage-guruplug'.
Load address: 0x6400000
Loading: T T T T T T T T T T And I could wait for hours, but nothing happens, in fact, the 'T' is like a timeout, isn't it. Sorry, but I'm a newbie on this, and I need a little more help.... Thanks in advance, PacoLM |
|
|
|
|
71
|
Linux Stuff / Kernel / Re: [HELP] Guruplug bricked after kernel upgrade
|
on: January 10, 2011, 10:55:19 PM
|
Hi radael, You're the man!. After several tries, I was able to get the jtag communicating with the guruplug and the process finished as expected, but the console didn't opened. I repeated the same process but this time using this files instead -> http://www.plugcomputer.org/plugwiki/index.php/File:Guruplug-installer.tar.gz. Now the guruplug console starts, but complains about the kernel image: U-Boot 2010.03-01161-gd91b0a9 (Apr 22 2010 - 03:24:41)
Marvell-GuruPlug
SoC: Kirkwood 88F6281_A0
DRAM: 512 MB
NAND: 512 MiB
In: serial
Out: serial
Err: serial
Net: egiga0, egiga1
88E1121 Initialized on egiga0
88E1121 Initialized on egiga1
Hit any key to stop autoboot: 0
No link on egiga0
No link on egiga1
ping failed; host 192.168.2.1 is not alive
No link on egiga1
No link on egiga0
ping failed; host 192.168.2.1 is not alive
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... Device NOT ready
Request Sense returned 02 3A 00
1 Storage Device(s) found
NAND read: device 0 offset 0x100000, size 0x400000
4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
This is the printenv listing: bootdelay=3
baudrate=115200
x_bootcmd_usb=usb start
ethaddr=00:50:43:67:64:06
eth1addr=00:50:43:67:64:07
x_bootcmd_kernel=nand read.e 0x6400000 0x100000 0x400000
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
x_bootargs=console=ttyS0,115200
x_bootcmd_ethernet1=set ethact egiga1
x_bootcmd_ethernet=ping 192.168.2.1
x_bootcmd=$(x_bootcmd_ethernet); $(x_bootcmd_ethernet1); $(x_bootcmd_ethernet); $(x_bootcmd_usb); $(x_bootcmd_kernel); setenv bootargs $(x_bootargs) $(x_bootargs_root) ;bootm 0x6400000;
bootcmd=run x_bootcmd
stdin=serial
stdout=serial
stderr=serial
ethact=egiga1
bootargs=console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
Environment size: 665/131068 bytes
Note to self: remember to rewrite the nand with the proper mac address of my plug.... What's the next step? -> http://www.plugcomputer.org/plugwiki/index.php/Reflashing_images_on_the_GuruPlug ? Thanks a lot to all the people who bricked its plug and helped other users to get his plug back to life! PacoLM |
|
|
|
|
73
|
Linux Stuff / Kernel / Re: [HELP] Guruplug bricked after kernel upgrade
|
on: January 10, 2011, 01:14:34 PM
|
Hi, When running the runme.sh script this is the output of the terminal: **** Preparing environment variables file ...
**** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M
BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Error: JTAG communication failure, check connection, JTAG interface, target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x00. tap=feroceon.cpu pos=0 expected 0x1 got 0
Warn : Could not validate JTAG chain, continuing anyway...
Warn : value captured during scan didn't pass the requested check:
Warn : captured: 0x00 check_value: 0x01 check_mask: 0x0F
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: unknown EmbeddedICE version (comms ctrl: 0x00000000)
Error: unexpected Feroceon EICE version signature
Error: timed out while waiting for target halted
Runtime error, file "./openocd/./board/guruplug.cfg", line 24:
**** openocd FAILED
**** Is the mini USB cable connected?
**** Try powering down, then replugging the Sheevaplug
And this is the output of the dmesg after disconnecting and connecting the Jtag: [90414.955169] ftdi_sio 1-1.1:1.1: device disconnected
[90419.264104] usb 1-1.1: new full speed USB device using ehci_hcd and address 10
[90419.383123] usb 1-1.1: Ignoring serial port reserved for JTAG
[90419.386704] ftdi_sio 1-1.1:1.1: FTDI USB Serial Device converter detected
[90419.386770] usb 1-1.1: Detected FT2232C
[90419.386777] usb 1-1.1: Number of endpoints 2
[90419.386784] usb 1-1.1: Endpoint 1 MaxPacketSize 64
[90419.386789] usb 1-1.1: Endpoint 2 MaxPacketSize 64
[90419.386795] usb 1-1.1: Setting MaxPacketSize 64
[90419.390829] usb 1-1.1: FTDI USB Serial Device converter now attached to ttyUSB0
I'll try to reset the computer and repeat the process, just in case the serial port is being used by another process, but I doubt it, because I'm getting the same error that I got when running the ESIA application under WXP. Regards, PacoLM |
|
|
|
|
74
|
Linux Stuff / Kernel / Re: [HELP] Guruplug bricked after kernel upgrade
|
on: January 10, 2011, 08:58:33 AM
|
|
Hi Rich,
Thanks for the quick reply, I downloaded all the files and read the guide, but I'm stuck in the beginning....I do not have communication using the JTAG. You mentioned that you had the same problem. What did you do to enable communication using JTAG?.
Regards,
PacoLM
EDIT: OK, once at home, I will try to run the script runme.sh in my ubuntu computer.
|
|
|
|
|
75
|
Linux Stuff / Kernel / [HELP] Guruplug bricked after kernel upgrade
|
on: January 10, 2011, 12:59:10 AM
|
Hi, I tried to upgrade my shiny and nice guruplug with the new kernel 2.6.35.10, following this topic http://plugcomputer.org/plugforum/index.php?topic=4158.0. This seemed to be a bad decission, because now my guruplug is bricked!!!. First my fault was to copy the upgrading script to a temporary directory under /tmp, so when the upgrade script finished and I restarted the plug, the boot was stuck here : U-Boot 2009.11-rc1-00602-g28a9c08-dirty (Feb 09 2010 - 18:15:21)
Marvell-Plug2L
SoC: Kirkwood 88F6281_A0
DRAM: 512 MB
NAND: 512 MiB
In: serial
Out: serial
Err: serial
Net: egiga0, egiga1
88E1121 Initialized on egiga0
88E1121 Initialized on egiga1
Hit any key to stop autoboot: 0
*** ERROR: `ipaddr' not set
ping failed; host 192.168.2.1 is not alive
No link on egiga1
*** ERROR: `ipaddr' not set
ping failed; host 192.168.2.1 is not alive
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... Device NOT ready
Request Sense returned 02 3A 00
1 Storage Device(s) found
NAND read: device 0 offset 0x100000, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 06400000 ...
Image Name: Linux-2.6.35.10
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2820480 Bytes = 2.7 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel. After reading lots of topics, I decided to do some changes to get my plug back to life again, but in one of this tests while modifying the setenv variables (bootcmd to be more accurate), the plug rebooted for the last time and then I loose communication. I'm using the JTAG and since this, I'm not able to enter in the 'Marvell' prompt. I dowloaded ESIA in order to try reflashing the nand, but I get this error: Open On-Chip Debugger 0.2.0 (2009-07-27-16:41) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Error: JTAG communication failure: check connection, JTAG interface, target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x00. tap=feroceon.cpu pos=0 expected 0x1 got 0
Warn : Could not validate JTAG chain, continuing anyway...
Error: unexpected Feroceon EICE version signature
Error: timed out while waiting for target halted
Runtime error, file "C:\Program Files\ESIA\uboot\openocd\config/board\sheevaplug.cfg", line 21: Please, help me!. I would like to have my guruplug working again. It's (or it was) the core of my home surveillance system!!!! Is my guruplug completely dead or it's possible to unbrick it even with no JTAG communication?. Thanks in advance, PacoLM |
|
|
|
|
