New IT forum
13 August 2022, 01:21:49 pm *
Welcome, %1$s. Please login or register.

: PiHub now in stock.
 
Pages: [1] 2

Author Topic: unable to login after update  (Read 36590 times)

ashrob

  • Newbie
  • *
  • Posts: 11
unable to login after update
« on: 18 December 2009, 10:37:47 am »

Hi there,

I received my plug yesterday and all was well until I ran an update on the Os. It got almost all the way through then it asked me if I wanted to update a file, keep the old one or compare the two. I pressed D to compare them and then N to keep the old one. It then asked me for my name and some contact details. Then it stopped updating. I left it for an hour or so and it hadn't moved so I turned it off. I realise that in the Update Bible this is close to heresy but I didn't know what else to do. So now it's just booting and getting to a point where it's saying FATAL. Now I don't know much about Ubuntu but I know that something being FATAL is not good.

I would really appreciate some help with this. I will cry all Christmas if I've broken my new toy.

Code: [Select]
512 MB

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:  0

NAND read: device 0 offset 0x100000, size 0x400000

Bad block at 0x140000 in erase block from 0x140000 will be skipped
Reading data from 0x51f800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-03-19   9:18:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2106696 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................
....................................................................... done, bo
oting the kernel.
Linux version 2.6.22.18 ([email protected]) (gcc version 4.2.1) #1 Thu Mar 19 14:46:
22 IST 2009
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists.  Total pages: 130048
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:[email protected](uI
mage),[email protected](rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50
.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB 0MB 0MB = 512MB total
Memory: 515456KB available (3864K code, 257K data, 104K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 256MB
SDRAM_CS1 ....base 10000000, size 256MB
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB
PEX0_IO ....base f2000000, size   1MB
INTER_REGS ....base f1000000, size   1MB
NFLASH_CS ....base fa000000, size   2MB
SPI_CS ....base f4000000, size  16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size   2MB

  Marvell Development Board (LSP Version KW_LSP_4.2.7_patch2)-- SHEEVA PLUG  Soc
: 88F6281 A0 LE

 Detected Tclk 200000000 and SysClk 400000000
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c08b8600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
RTC registered
Use the XOR engines (acceleration) for enhancing the following functions:
  o RAID 5 Xor calculation
  o kernel memcpy
  o kenrel memzero
Number of XOR engines to use: 4
cesadev_init(c000c894)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
MV Buttons Driver Load
NTFS driver 2.1.28 [Flags: R/O].
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o Single RX Queue support - ETH_DEF_RXQ=0
  o Single TX Queue support - ETH_DEF_TXQ=0
  o TCP segmentation offload enabled
  o Receive checksum offload enabled
  o Transmit checksum offload enabled
  o Network Fast Processing (Routing) supported
  o Driver ERROR statistics enabled
  o Driver INFO statistics enabled
  o Proc tool API enabled
  o Rx descripors: q0=128
  o Tx descripors: q0=532
  o Loading network interface(s):
    o eth0, ifindex = 1, GbE port = 0
    o eth1, ifindex = 2, GbE port = 1

mvFpRuleDb (dfd00000): 16384 entries, 65536 bytes
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation

Warning Sata is Powered Off
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)

Scanning device for bad blocks
Bad eraseblock 10 at 0x00140000
Bad eraseblock 691 at 0x05660000
Bad eraseblock 731 at 0x05b60000
Bad eraseblock 2167 at 0x10ee0000
Bad eraseblock 4005 at 0x1f4a0000
Bad eraseblock 4009 at 0x1f520000
Bad eraseblock 4067 at 0x1fc60000
2 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 2 MTD partitions on "nand_mtd":
0x00100000-0x00500000 : "uImage"
0x00500000-0x20000000 : "rootfs"
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Linux telephony interface: v1.00
Marvell Telephony Driver:
mvBoardVoiceAssembleModeGet: TDM not supported(boardId=0x9)
assembly=-1,irq=-1
mp_check_config: Error, invalid voice assembley mode
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1     97 MB/s
raid6: int32x2    114 MB/s
raid6: int32x4    122 MB/s
raid6: int32x8    110 MB/s
raid6: using algorithm int32x4 (122 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
   arm4regs  :  1071.600 MB/sec
   8regs     :   754.800 MB/sec
   32regs    :   900.000 MB/sec
raid5: using function: arm4regs (1071.600 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [email protected]

dm_crypt using the OCF package.
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mvsdmmc: irq =28 start f1090000
mvsdmmc: no IRQ detect
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 200
7 UTC).
mvCLAudioCodecRegGet: Error while reading register!
mvCLAudioCodecInit: Error - Invalid Cirrus Logic chip/rev ID!
Error - Cannot initialize audio decoder.at address =0xff<6>ALSA device list:
  #0: Marvell mv88fx_snd ALSA driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
eth0: link down
eth0: started
IP-Config: Complete:
      device=eth0, addr=10.4.50.4, mask=255.255.255.0, gw=10.4.50.5,
     host=DB88FXX81, domain=, nis-domain=(none),
     bootserver=10.4.50.5, rootserver=10.4.50.5, rootpath=
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
eth0: link up, full duplex, speed 100 Mbps
jffs2_scan_dirent_node(): Node CRC failed on node at 0x1206ffe0: Read 0xffffffff
, calculated 0x8abd0b10
Empty flash at 0x12070010 ends at 0x12070800
Empty flash at 0x1c5fdc58 ends at 0x1c5fe000
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 104K
[ OK ]ting preliminary keymap...
[ OK ]rting kernel event manager...
 * Loading hardware drivers...        udevadm trigger is not permitted while ude
v is unconfigured.
[ OK ]ding kernel modules...         * Loading manual drivers...
[ OK ]ting kernel variables (/etc/sysctl.conf)...
[ OK ]ting kernel variables (/etc/sysctl.d/10-console-messages.conf)...
 * Setting kernel variables (/etc/sysctl.d/10-network-security.conf)...        e
rror: "net.ipv4.tcp_syncookies" is an unknown key
[fail]
[ OK ]ivating swap...
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or direct
ory
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or direct
ory
[ OK ]rting early crypto disks...
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or direct
ory
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or direct
ory
[ OK ]rting remaining crypto disks...
 * Checking file systems...        fsck 1.41.4 (27-Jan-2009)
[ OK ]
[fail]nting local filesystems...
[ OK ]ivating swapfile swap...
[fail]figuring network interfaces...
fat: exports duplicate symbol fat_add_entries (owned by kernel)

It gets to this point and I can type whatever I like and it just returns to the next line.

I'm guessing I need to reinstall those modules but as it won't let me talk to it I'm at a bit of a loss. I would flash it and reinstall Ubuntu but I don't know how. Any help would be greatly appreciated.
Logged

ashrob

  • Newbie
  • *
  • Posts: 11
Re: unable to login after update
« Reply #1 on: 18 December 2009, 03:56:33 pm »

Ok well, I've faffed on with it a bit more. Couldn't load the u-boot.img so I loaded the recovery image. It got to this bit -

Code: [Select]
RAMDISK: Couldn't find valid RAM disk image starting at 0.
List of all partitions:
1f00       1024 mtdblock0 (driver?)
1f01       2048 mtdblock1 (driver?)
1f02     521216 mtdblock2 (driver?)
No filesystem could mount root, tried:  squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

And there it stopped. I am guessing that it's unhappy about being unable to find the RAM disk image but why that is I have no idea. It's on the stick and I've followed the instructions on the Sheevaplug Dev Kit cd to the letter.

I'm doing all this from a Windows machine as I have left my copy of Ubuntu at work and my broadband is broken and down to 15KB/s at the moment. It took me an hour and a half to download the 100MB Gparted Live cd to partition the USB stick. I suppose I could download Ubuntu overnight but if it was corrupt then I would lose the will to live.

On http://www.earth.org.uk/note-on-SheevaPlug-setup.html this guy has the same problem. He sorts it by doing something from a Linux machine. What the something is however, is not clear.

I would reeeeeally appreciate a little help.
« Last Edit: 18 December 2009, 04:06:46 pm by ashrob »
Logged

NewIT_Marcus

  • Hero Member
  • *****
  • Posts: 960
Re: unable to login after update
« Reply #2 on: 18 December 2009, 06:15:00 pm »

It's very easy to make typing errors when you are tweaking the U-Boot environment variables. Your best bet is to attempt recovery, and copy & paste here each of the steps that you are performing. You may be making an error that you just can't see, but someone else will notice.

Although I haven't had occasion to use the USB recovery method, the installer procedures perform a similar wholesale re-writing of the file system. For the installer, it's usual to download a rootfs image - but for reasons that you have explained, that is not your first choice at this time. I have to tell you that if you can take this opportunity to learn how to use the installer, you will be learning something that may be useful many times in the future. The downside would be the significant downloads that may be required (i.e. 144M).
Logged

NewIT_Marcus

  • Hero Member
  • *****
  • Posts: 960
Re: unable to login after update
« Reply #3 on: 18 December 2009, 07:14:42 pm »

Ok well, I've faffed on with it a bit more. Couldn't load the u-boot.img so I loaded the recovery image. It got to this bit -

Code: [Select]
RAMDISK: Couldn't find valid RAM disk image starting at 0.
List of all partitions:
1f00       1024 mtdblock0 (driver?)
1f01       2048 mtdblock1 (driver?)
1f02     521216 mtdblock2 (driver?)
No filesystem could mount root, tried:  squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

And there it stopped. I am guessing that it's unhappy about being unable to find the RAM disk image but why that is I have no idea. It's on the stick and I've followed the instructions on the Sheevaplug Dev Kit cd to the letter.


OK, I got exactly the same errors as you. I didn't re-flash U-Boot, not having a TFTP server on standby, but my result does seem to be the same as yours.

I'd recommend the installer route. I'll look into whatever seems to the be the problem with this recovery procedure, but we know the installer works; we also know it has some confusing instructions, but it's not terribly difficult, so give it a try and let us know how you get along.
Logged

ashrob

  • Newbie
  • *
  • Posts: 11
Re: unable to login after update
« Reply #4 on: 18 December 2009, 11:10:48 pm »

It's very easy to make typing errors when you are tweaking the U-Boot environment variables. Your best bet is to attempt recovery, and copy & paste here each of the steps that you are performing. You may be making an error that you just can't see, but someone else will notice.

Although I haven't had occasion to use the USB recovery method, the installer procedures perform a similar wholesale re-writing of the file system. For the installer, it's usual to download a rootfs image - but for reasons that you have explained, that is not your first choice at this time. I have to tell you that if you can take this opportunity to learn how to use the installer, you will be learning something that may be useful many times in the future. The downside would be the significant downloads that may be required (i.e. 144M).

Hi there,

Thank you so much for helping.
 
Here are the instructions for the installer, I'll c&p them here and insert my own comments in order to show my thinking.

Installation -
--------------
1.  Prepare an empty USB stick that is FAT16/32 formatted.
2.  Download the installer tarball to your PC and unpack it to your working
     directory (for example: ~/work/sheevaplug-installer)
3.  Edit the ~/work/sheevaplug-installer/installer/uboot-custom.txt file to burn
     the correct MAC address according to the MAC address on the back of the
     Plug (change the ethaddr value)


The only files in the installer tar ball I can find that have a name approaching this are the two in "sheevaplug-installer-v1.0\uboot\uboot-env" called 'uboot-nand-custom.txt' and 'uboot-mmc-custom.txt'. I have edited them both to hold the MAC address of the plug. I have also edited them to boot from NAND. 'uboot-mmc-custom.txt' is self-explanatory but 'uboot-nand-custom.txt' says:

Code: [Select]
# Following for installation on SD card. If you want to boot from USB stick change it to /dev/sda1
# or /dev/mtdblock1 if you installed rootfs on the NAND inside the plug
bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs

I will be installing rootfs on the NAND (I think) so I want to change it to '/dev/mtdblock1' but where do I change it? The forward slashes suggest a folder structure but in the code it doesn't look as though there are any folders. I think I change 'ubi.mtd=1' but I'm not sure.



4.  Populate the USB stick with a all files inside the installer directory.
    NOTE: that the files should be written to the root directory of the USB stick.
          For example if the recovery directory is sheevaplug-installer and USB
          stick mount is: /media/usb run on the host Linux PC:
          sudo cp -a ~/work/sheevaplug-installer/installer/* /media/usb/


I'm not sure what this is for, as it seems to be repeated in step 5.

5.  Copy the following to the USB stick root directory:
      a. Root file-system (packed into rootfs.tar.gz)
      b. Kernel (named uImage)
      c. Kernel modules (packed into modules.tar.gz)
      d. Init ramdisk (uImage.initrd)

   If you do not have all, you can download from:
      a. http://plugcomputer.org/index.php/us/resources/downloads (distro, kernel(LSP), uboot)
      b. http://plugcomputer.org/plugwiki/index.php/Main_Page     (distrio,uboot)
      c. http://sheeva.with-linux.com/sheeva                      (mainline kernel+modules)
6.  Copy the uboot image (named uboot.bin) to the ~/work/sheevaplug-installer/uboot/ directory (use prev bullet links as sources)


This seems to be the same as 4 and 5.

7.  Safely remove the USB stick from the host PC and plug it into the Plug's USB host interface (not via USB HUB!)
8.  Connect the power to the Plug
9.  Connect the mini USB connector to the Plug (not via USB HUB!)
10. On Win PC, close any connected console (tera-term, tutty, RealTerm...), since the flash burning is done via this port


If I do this then I don't get chance to break into the autoboot process, if it autoboots it just gets to the part that is broken and stops. I don't understand this.

12. On the host PC, change the working directory to ~/work/sheevaplug-installer and run the runme.php file (or the runme.exe on Win host PC). (on Linux PC you should be root in order to do that)

I think this means that I run 'runme.exe' on the USB stick connected to the plug but to do that I need to open a console, if I do that then it uses the port that the flash burning uses. I also have no idea how to browse to the file and run it from my Windows pc without using Hyperterminal.

   When the runme finishes it will beep to indicate that the flash burning process  finished.
    On Win PC:
      a. wait for the uboot.bin to be burned (you should see: "wrote file uboot.bin to NAND flash 0 up to offset 0x00073000 in 112.746002s")
      b. exit the runme.exe program by executing Control+C
      c. disconnect the mini USB and reconnect
      d. wait for Windows to idevntify the new inserted mini USB
      e. you can open your serial (like putty) only now.
13. On a Linux PC. if the installer is unattended, watch the console and wait until the
     whole process is done.
14. If the installer is an interactive one (like Debian network installer) then
     watch the console for messages and act accordingly.

Installer directory structure -
-------------------------------
|
+-- README   - This file
+-- runme.php   - The installer script
+-- runme.exe   - The installer executable for Windows
+-- uboot   - Includes uboot images
  +-- openocd   - Scripts for openocd
  +-- uboot-env   - uboot-env manipulation
+-- installer   - Installer directory - this is specific per distro
+-- win32       - Windows 32bit dll Cygwin DLLs
+-- src         - sources and HOWTO for initrd
« Last Edit: 18 December 2009, 11:13:54 pm by ashrob »
Logged

NewIT_Marcus

  • Hero Member
  • *****
  • Posts: 960
Re: unable to login after update
« Reply #5 on: 19 December 2009, 10:39:29 am »

Here are the instructions for the installer, I'll c&p them here and insert my own comments in order to show my thinking.

Installation -
--------------
1.  Prepare an empty USB stick that is FAT16/32 formatted.
2.  Download the installer tarball to your PC and unpack it to your working
     directory (for example: ~/work/sheevaplug-installer)
3.  Edit the ~/work/sheevaplug-installer/installer/uboot-custom.txt file to burn
     the correct MAC address according to the MAC address on the back of the
     Plug (change the ethaddr value)


The only files in the installer tar ball I can find that have a name approaching this are the two in "sheevaplug-installer-v1.0\uboot\uboot-env" called 'uboot-nand-custom.txt' and 'uboot-mmc-custom.txt'. I have edited them both to hold the MAC address of the plug. I have also edited them to boot from NAND. 'uboot-mmc-custom.txt' is self-explanatory but 'uboot-nand-custom.txt' says:

Those are the correct files; the incorrect identification of them is the key flaw in the installer instructions.


Code: [Select]
# Following for installation on SD card. If you want to boot from USB stick change it to /dev/sda1
# or /dev/mtdblock1 if you installed rootfs on the NAND inside the plug
bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs




I will be installing rootfs on the NAND (I think) so I want to change it to '/dev/mtdblock1' but where do I change it? The forward slashes suggest a folder structure but in the code it doesn't look as though there are any folders. I think I change 'ubi.mtd=1' but I'm not sure.

If you are installing to NAND, you'll be using uboot-nand-custom.txt but the only part of that file you should change is the MAC address.




4.  Populate the USB stick with a all files inside the installer directory.
    NOTE: that the files should be written to the root directory of the USB stick.
          For example if the recovery directory is sheevaplug-installer and USB
          stick mount is: /media/usb run on the host Linux PC:
          sudo cp -a ~/work/sheevaplug-installer/installer/* /media/usb/


I'm not sure what this is for, as it seems to be repeated in step 5.

You are correct, this step is described twice. But do make sure that you copy the files to the root of the USB drive. (The ones I use were bought pre-formatted with FAT formatting; I'm not certain what other formats would work, but FAT certainly does).



5.  Copy the following to the USB stick root directory:
      a. Root file-system (packed into rootfs.tar.gz)
      b. Kernel (named uImage)
      c. Kernel modules (packed into modules.tar.gz)
      d. Init ramdisk (uImage.initrd)

   If you do not have all, you can download from:
      a. http://plugcomputer.org/index.php/us/resources/downloads (distro, kernel(LSP), uboot)
      b. http://plugcomputer.org/plugwiki/index.php/Main_Page     (distrio,uboot)
      c. http://sheeva.with-linux.com/sheeva                      (mainline kernel+modules)
6.  Copy the uboot image (named uboot.bin) to the ~/work/sheevaplug-installer/uboot/ directory (use prev bullet links as sources)


Yes, see above.


7.  Safely remove the USB stick from the host PC and plug it into the Plug's USB host interface (not via USB HUB!)
8.  Connect the power to the Plug
9.  Connect the mini USB connector to the Plug (not via USB HUB!)
10. On Win PC, close any connected console (tera-term, tutty, RealTerm...), since the flash burning is done via this port


If I do this then I don't get chance to break into the autoboot process, if it autoboots it just gets to the part that is broken and stops. I don't understand this.

What these steps are attempting to describe is that you have completed preparation of the USB stick; it should contain the following files:

Code: [Select]
initrd
modules.tar.gz
rootfs.tar.gz
uImage

So now remove it from the host PC and put it into the SheevaPlug. When you do this, plug it directly into the Sheevaplug, not via hub.

Then connect your PC to the SheevaPlug using the supplied USB cable. But if you are using Windows, do not establish a serial connection, because the flashing process will use the connection and only one such connection is available (under linux, two ports are available, and one can observe the flash process on the plug).



12. On the host PC, change the working directory to ~/work/sheevaplug-installer and run the runme.php file (or the runme.exe on Win host PC). (on Linux PC you should be root in order to do that)

I think this means that I run 'runme.exe' on the USB stick connected to the plug but to do that I need to open a console, if I do that then it uses the port that the flash burning uses. I also have no idea how to browse to the file and run it from my Windows pc without using Hyperterminal.

I've never run the process on a Windows PC. If I understand correctly, you cannot view the serial session whilst the installer is running, because the installer uses the same connection that the serial session would use. The instructions say that for a Windows PC you wait until the process has completed. A 10 minute wait should be sufficient. See below.



   When the runme finishes it will beep to indicate that the flash burning process  finished.
    On Win PC:
      a. wait for the uboot.bin to be burned (you should see: "wrote file uboot.bin to NAND flash 0 up to offset 0x00073000 in 112.746002s")
      b. exit the runme.exe program by executing Control+C
      c. disconnect the mini USB and reconnect
      d. wait for Windows to idevntify the new inserted mini USB
      e. you can open your serial (like putty) only now.
13. On a Linux PC. if the installer is unattended, watch the console and wait until the
     whole process is done.
14. If the installer is an interactive one (like Debian network installer) then
     watch the console for messages and act accordingly.

Installer directory structure -
-------------------------------
|
+-- README   - This file
+-- runme.php   - The installer script
+-- runme.exe   - The installer executable for Windows
+-- uboot   - Includes uboot images
  +-- openocd   - Scripts for openocd
  +-- uboot-env   - uboot-env manipulation
+-- installer   - Installer directory - this is specific per distro
+-- win32       - Windows 32bit dll Cygwin DLLs
+-- src         - sources and HOWTO for initrd


So how far have you progressed, what seems to be working, and what seems not to be working?
Logged

ashrob

  • Newbie
  • *
  • Posts: 11
Re: unable to login after update
« Reply #6 on: 19 December 2009, 01:13:16 pm »

Well I thought it would help to install Ubuntu on the drive in my PC that had Windows 7 Beta on it. I have an XP install on another drive that I was using for this. I instructed Ubuntu to wipe the Windows 7 drive completely (less room for error, I thought) and then when it rebooted, at first I just got a command line, no GUI. Then after another install the GRUB loader just booted straight into Ubuntu. So my two year old XP install is unavailable. No problem I thought, just FIXMBR from a Windows cd. Nope, won't do that as the GRUB loader doesn't recognise my USB keyboard.

So I am now bald.

Thing is, I can see how it will work now. From Windows. I suppose I'll have to go through the process again with Ubuntu. Thanks for your help Marcus, it is much appreciated.

Ok well I've followed the process for Linux and am waiting 10 minutes for it to do its thing.

I"ve now telnetted into the plug via PUTTY on Ubuntu. Gotta go out now so I'll get back to you about whether it has worked or not.

« Last Edit: 19 December 2009, 02:15:51 pm by ashrob »
Logged

NewIT_Marcus

  • Hero Member
  • *****
  • Posts: 960
Re: unable to login after update
« Reply #7 on: 19 December 2009, 02:55:11 pm »

There is an Ubuntu package startup manager, the purpose of which is to configure the grub menu. It may automagically detect your Windows 7 installation and create the required entry. Or it might not.
Logged

ashrob

  • Newbie
  • *
  • Posts: 11
Re: unable to login after update
« Reply #8 on: 20 December 2009, 09:46:54 am »

Thanks for the heads up on the startup manager. I've just installed it so will let you know if it lets me access my Windows install.

I've had a go at the installer. I have no idea what's going on but nothing has changed.

Code: [Select]
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists.  Total pages: 130048
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:[email protected](uImage),[email protected](rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB 0MB 0MB = 512MB total
Memory: 515456KB available (3864K code, 257K data, 104K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 256MB
SDRAM_CS1 ....base 10000000, size 256MB
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB
PEX0_IO ....base f2000000, size   1MB
INTER_REGS ....base f1000000, size   1MB
NFLASH_CS ....base fa000000, size   2MB
SPI_CS ....base f4000000, size  16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size   2MB

  Marvell Development Board (LSP Version KW_LSP_4.2.7_patch2)-- SHEEVA PLUG  Soc: 88F6281 A0 LE

 Detected Tclk 200000000 and SysClk 400000000
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c08b8600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
RTC registered
Use the XOR engines (acceleration) for enhancing the following functions:
  o RAID 5 Xor calculation
  o kernel memcpy
  o kenrel memzero
Number of XOR engines to use: 4
cesadev_init(c000c894)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
MV Buttons Driver Load
NTFS driver 2.1.28 [Flags: R/O].
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o Single RX Queue support - ETH_DEF_RXQ=0
  o Single TX Queue support - ETH_DEF_TXQ=0
  o TCP segmentation offload enabled
  o Receive checksum offload enabled
  o Transmit checksum offload enabled
  o Network Fast Processing (Routing) supported
  o Driver ERROR statistics enabled
  o Driver INFO statistics enabled
  o Proc tool API enabled
  o Rx descripors: q0=128
  o Tx descripors: q0=532
  o Loading network interface(s):
    o eth0, ifindex = 1, GbE port = 0
    o eth1, ifindex = 2, GbE port = 1

mvFpRuleDb (dfd00000): 16384 entries, 65536 bytes
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation

Warning Sata is Powered Off
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 10 at 0x00140000
Bad eraseblock 691 at 0x05660000
Bad eraseblock 731 at 0x05b60000
Bad eraseblock 2167 at 0x10ee0000
Bad eraseblock 4005 at 0x1f4a0000
Bad eraseblock 4009 at 0x1f520000
Bad eraseblock 4067 at 0x1fc60000
2 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 2 MTD partitions on "nand_mtd":
0x00100000-0x00500000 : "uImage"
0x00500000-0x20000000 : "rootfs"
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usb 1-1: new high speed USB device using ehci_marvell and address 2
usb 1-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Linux telephony interface: v1.00
Marvell Telephony Driver:
mvBoardVoiceAssembleModeGet: TDM not supported(boardId=0x9)
assembly=-1,irq=-1
mp_check_config: Error, invalid voice assembley mode
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1     97 MB/s
raid6: int32x2    114 MB/s
raid6: int32x4    122 MB/s
raid6: int32x8    111 MB/s
raid6: using algorithm int32x4 (122 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
   arm4regs  :  1084.000 MB/sec
   8regs     :   754.800 MB/sec
   32regs    :   900.000 MB/sec
raid5: using function: arm4regs (1084.000 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [email protected]
dm_crypt using the OCF package.
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mvsdmmc: irq =28 start f1090000
mvsdmmc: no IRQ detect
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC).
mvCLAudioCodecRegGet: Error while reading register!
mvCLAudioCodecInit: Error - Invalid Cirrus Logic chip/rev ID!
Error - Cannot initialize audio decoder.at address =0xff<6>ALSA device list:
  #0: Marvell mv88fx_snd ALSA driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
eth0: link down
eth0: started
IP-Config: Complete:
      device=eth0, addr=10.4.50.4, mask=255.255.255.0, gw=10.4.50.5,
     host=DB88FXX81, domain=, nis-domain=(none),
     bootserver=10.4.50.5, rootserver=10.4.50.5, rootpath=
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
eth0: link up, full duplex, speed 100 Mbps
Empty flash at 0x0df09b30 ends at 0x0df0a000
Empty flash at 0x11503d7c ends at 0x11504000
jffs2_scan_dirent_node(): Node CRC failed on node at 0x1206ffe0: Read 0xffffffff, calculated 0x8abd0b10
Empty flash at 0x12070010 ends at 0x12070800
jffs2_scan_eraseblock(): Node at 0x15b5a7fc {0x1985, 0xe002, 0xe0021985) has invalid CRC 0x00000083 (calculated 0xd7cd6a7b)
Empty flash at 0x164cac9c ends at 0x164cb000
Empty flash at 0x188aead4 ends at 0x188af000
Empty flash at 0x1c5fdc58 ends at 0x1c5fe000
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 104K
scsi 0:0:0:0: Direct-Access     USB 2.0  SD MMC Reader         PQ: 0 ANSI: 0 CCS
sd 0:0:0:0: [sda] 15523840 512-byte hardware sectors (7948 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 15523840 512-byte hardware sectors (7948 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
 * Setting preliminary keymap...                                         [ OK ]
 * Starting kernel event manager...                                      [ OK ]
 * Loading hardware drivers...                                                  udevadm trigger is not permitted while udev is unconfigured.
 * Loading kernel modules...                                                     * Loading manual drivers...                                             [ OK ]
 * Setting kernel variables (/etc/sysctl.conf)...                        [ OK ]
 * Setting kernel variables (/etc/sysctl.d/10-console-messages.conf)...  [ OK ]
 * Setting kernel variables (/etc/sysctl.d/10-network-security.conf)...         error: "net.ipv4.tcp_syncookies" is an unknown key
                                                                         [fail]
 * Activating swap...                                                    [ OK ]
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory
 * Starting early crypto disks...                                        [ OK ]
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory
 * Starting remaining crypto disks...                                    [ OK ]
 * Checking file systems...                                                     fsck 1.41.4 (27-Jan-2009)
                                                                         [ OK ]
 * Mounting local filesystems...                                         [fail]
 * Activating swapfile swap...                                           [ OK ]
 * Configuring network interfaces...                                     [fail]
fat: exports duplicate symbol fat_add_entries (owned by kernel)
p\p/^A

The last line is me, faffing about.

I'm gonna keep trying. I've attempted to update uboot.bin by following the tutorial from Martin Michlmayr's page but again, it seems not to recognise the USB stick. I'm now learning how to tftp into the plug, that seems to be a more effective method of working with it.

Just a thought, after reading the uboot.bin tutorial for a usb stick (the tftp tutorial is on the back burner for now) , the first command is 'usb start'. I don't need to do that with this, do I?
« Last Edit: 20 December 2009, 10:29:33 am by ashrob »
Logged

ashrob

  • Newbie
  • *
  • Posts: 11
Re: unable to login after update
« Reply #9 on: 20 December 2009, 11:27:32 am »

Great, it won't even boot now. I turn it on and all I get in the Putty window is a cursor. Nothing happens. Any way to bring it back from this? I've tried resetting it.

On post 8 on this this thread it mentions that if one of the lights is out then that's a hardware failure. The blue light (one nearest the ethernet point) isn't on on mine. Is that the same thing?
« Last Edit: 20 December 2009, 11:41:45 am by ashrob »
Logged

NewIT_Marcus

  • Hero Member
  • *****
  • Posts: 960
Re: unable to login after update
« Reply #10 on: 20 December 2009, 04:37:27 pm »

Great, it won't even boot now. I turn it on and all I get in the Putty window is a cursor. Nothing happens. Any way to bring it back from this? I've tried resetting it.

You'll have to be more specific about the symptoms, i.e. what kind of connection are you attempting via puTTY, and from what host operating system? If you are attempting an ssh connection, all this is telling us is that the plug won't get as far as the ssh daemon running. If you are attempting a serial connection, you should hit enter a few times to see if any output is produced.

you also should say what you did *before* this happened. U-Boot 3.4.25 can make the plug no longer display console output.

On post 8 on this this thread it mentions that if one of the lights is out then that's a hardware failure. The blue light (one nearest the ethernet point) isn't on on mine. Is that the same thing?

Normally, first the green light should illuminate, and then approximately 1 second later, the blue one.

In your previous post, the plug seemed to be booting normally right up to the end; only the file mount fail and network fail messages are abnormal.

Theoretically, you should still be able to use the installer to restore at least a partial boot, as it was in your penultimate message.
Logged

ashrob

  • Newbie
  • *
  • Posts: 11
Re: unable to login after update
« Reply #11 on: 22 December 2009, 03:08:49 pm »

Great, it won't even boot now. I turn it on and all I get in the Putty window is a cursor. Nothing happens. Any way to bring it back from this? I've tried resetting it.

You'll have to be more specific about the symptoms, i.e. what kind of connection are you attempting via puTTY, and from what host operating system?

If you are attempting an ssh connection, all this is telling us is that the plug won't get as far as the ssh daemon running. If you are attempting a serial connection, you should hit enter a few times to see if any output is produced.

you also should say what you did *before* this happened. U-Boot 3.4.25 can make the plug no longer display console output.

The connection was serial and I hit enter and nothing happened i.e. the cursor didn't move. The host operating system is Ubuntu 9.10.

I attempted to update the plug via a serial connection with the latest uboot.bin file. The plug looked as though it was updating but after the dots had finished it said something like ‘fatload failed’. Sorry, I can’t be any more specific than that.

On post 8 on this this thread it mentions that if one of the lights is out then that's a hardware failure. The blue light (one nearest the ethernet point) isn't on on mine. Is that the same thing?

Quote
Normally, first the green light should illuminate, and then approximately 1 second later, the blue one.

The blue one does not illuminate.

Quote
In your previous post, the plug seemed to be booting normally right up to the end; only the file mount fail and network fail messages are abnormal.

Theoretically, you should still be able to use the installer to restore at least a partial boot, as it was in your penultimate message.
I haven’t had a go at the installer since the bluelight stopped illuminating. I’ll give it another shot.

Thanks for your help.
Logged

NewIT_Marcus

  • Hero Member
  • *****
  • Posts: 960
Re: unable to login after update
« Reply #12 on: 22 December 2009, 07:00:10 pm »

OK I have confirmation from above that:

If the green light flashes, and the blue light stays off, it indicates there is no "Operating System" and the plug must be re-flash again.


Quote
The plug looked as though it was updating but after the dots had finished it said something like ‘fatload failed’
This message was on the host PC?

I think that fatload is the part where U-Boot tries to copy a file from the USB stick to the NAND. So if that fails, we need to look at the procedure you are attempting in more detail:

What is the content of the USB stick that you have attached (please list all files - there should be somewhere between 4 and 6, depending upon whether you copied the readme and (unnecessary) script). And what are the file paths?
What is the filesystem of that stick?
Logged

ashrob

  • Newbie
  • *
  • Posts: 11
Re: unable to login after update
« Reply #13 on: 23 December 2009, 01:07:48 pm »

Hi Marcus,

The 'fatload failed' message was in the Putty window on the host pc, when I was attempting to install the uboot.bin.

I was using FAT 32 format on the USB stick but I reformatted to FAT 16 for the uboot.bin install. At the time I tried that install there was only uboot.bin on the stick, no other files. uboot.bin was in the root of the USB stick.

When I tried the Sheevaplug Installer I untar'd the 'sheevaplug-installer-v1.0.tar.gz' file into the root of the USB stick (formatted in FAT 32) and took all files and folders out of the 'sheevaplug-installer-v1.0' folder and dropped them into the root of the USB stick . Then I dragged the four files 'initrd', 'modules.tar.gz', 'rootfs.tar.gz', 'uImage' from 'installer' folder into the root of the stick.

I didn't delete any files from the stick after untaring the 'sheevaplug-installer-v1.0.tar.gz' file.

Then I did this -
Quote
If you are installing to NAND, you'll be using uboot-nand-custom.txt but the only part of that file you should change is the MAC address.

I haven't tried it again yet. I'll get back to you when I do. I'm back on Windows 7 now too.

Edited to add: I've now tried this method again and there's still nothing happening. If I Putty into the plug on COM4 (the USB serial port) there is nothing but a cursor, it's not flashing and I can't type anything into the box. I then turn the plug off (Putty too), plug in the USB stick with the above files and folder structure on it, turn the plug on, plug in the mini-usb, wait ten minutes and look again and there's still just a cursor and nothing else. No signs of activity.
« Last Edit: 23 December 2009, 03:02:33 pm by ashrob »
Logged

NewIT_Marcus

  • Hero Member
  • *****
  • Posts: 960
Re: unable to login after update
« Reply #14 on: 23 December 2009, 03:31:33 pm »

When I tried the Sheevaplug Installer I untar'd the 'sheevaplug-installer-v1.0.tar.gz' file into the root of the USB stick (formatted in FAT 32) and took all files and folders out of the 'sheevaplug-installer-v1.0' folder and dropped them into the root of the USB stick . Then I dragged the four files 'initrd', 'modules.tar.gz', 'rootfs.tar.gz', 'uImage' from 'installer' folder into the root of the stick.

I didn't delete any files from the stick after untaring the 'sheevaplug-installer-v1.0.tar.gz' file.

There only needs to be 4 files on the USB stick (and they must be in the root, and FAT32 is fine, I think FAT16 is OK too):

initrd
modules.tar.gz
rootfs.tar.gz
uImage

everything else should reside on your PC. That's where you will run runme.exe, and it is the instructions regarding that that you should be reviewing at this time. So far as I understand it, for Windows, you must close your serial session for the duration.
Logged
Pages: [1] 2
 
 

Powered by MySQL Powered by PHP SMF 2.0.10 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!