• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2]
16  Linux Stuff / Kernel / Re: 2.6.35.11 new kernel available on: February 28, 2011, 05:10:22 AM

i think you've not downloaded/flashed these files:
-rw-r--r--  1 root root 5403668 Feb 28 12:45 sheeva-2.6.35.11-Modules.tar.gz
-rw-r--r--  1 root root      66 Feb 28 12:45 sheeva-2.6.35.11-Modules.tar.gz.md5


Code:
root@Guruplug:/var/log/fhem# ls -la /lib/modules/
total 24
drwxr-xr-x  4 root root  4096 Feb 28 13:09 .
drwxr-xr-x 11 root root 12288 Feb 28 12:19 ..
drwxr-xr-x  3 root root  4096 Feb 27 14:43 2.6.32-5-kirkwood
drwxr-xr-x  3 root root  4096 Feb 28 09:31 2.6.35.11
root@Guruplug:/var/log/fhem#

All is there as i can see
17  Linux Stuff / Kernel / Re: 2.6.35.11 new kernel available on: February 28, 2011, 02:23:41 AM
i just installed the 2.6.35.11 rootkernel and i get the following errors on boot:

Code:
Begin: Running /scripts/local-premount ... done.
FATAL: Could not load /lib/modules/2.6.35.11/modules.dep: No such file or directory
mount: mounting /dev/sdb3 on /root failed: Invalid argument
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
done.
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have requested /sbin/init.
FATAL: Could not load /lib/modules/2.6.35.11/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.35.11/modules.dep: No such file or directory
No init found. Try passing init= bootarg.


BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

I've added "rootfstype=jffs2" af option to my bootargs but it seems like iḿ missing something here. Anyone sugestions?
18  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: February 28, 2011, 01:57:50 AM
after a big "tug of war" i completed the 1st draft

Would somebody be so kind to double check it?



##########################################################################################
1) Setup OpenOCD with guruplug installer @ http://www.plugcomputer.org/index.php/us/resources/downloads?func=fileinfo&id=65 (my prefference)

Or do it the manual way via: http://plugcomputer.org/plugwiki/index.php/Setting_Up_OpenOCD_Under_Linux

2) Enter the OpenOCD directory and download and untar the "flipflip" ultimate uboot config
Code:
cd openocd
wget http://oinkzwurgl.org/dl.php?file=guruplug-u-boot-flipflip-20101111.tar.gz
tar zxvf guruplug-u-boot-flipflip-20101111.tar.gz
cp guruplug-u-boot-flipflip-20101111/u-boot.elf .
mv u-boot.elf uboot.elf

3) Install tftpd
Code:
sudo apt-get install tftpd

4) Copy over the u-boot.kwb image to the tftp dir
Code:
cp guruplug-u-boot-flipflip-20101111/u-boot.kwb /srv/tftp/

5) Boot the guruplug via OpenOCD
Code:
sudo ./openocd -f ./board/guruplug.cfg -c init -c guruplug_load_uboot -c exit

6) Connect via minicom and set the ip address of the guruplug and set the tftp server ip adress (on the booted plug)
Code:
setenv ipaddr 192.168.10.110
setenv serverip 192.168.10.105

7) Load the u-boot.kwb from the tftp server
Code:
tftp 0x6400000 u-boot.kwb

Cool Flash the loaded u-boot.kwb into NAND and reset
Code:
nand erase 0x00000000 0x0100000
nand write 0x6400000 0x0000000 0x80000
reset

The error message "*** Warning - bad CRC, using default environment" can be ignored. This is because the default "setenv" settings are used.

9) Verify u-boot version
After booting the plug verify the correct version installed by typing "version"at the Marvell prompt.
Code:
GuruPlug>> version                     
                                       
U-Boot 2010.09-02612-g27fb783-dirty (Nov 11 2010 - 22:51:37)
Marvell-GuruPlug (-: flipflip's version 20101111 :-)
GuruPlug>>

Nice ;-) lets rock and roll

*** Installing debian (source http://bzed.de/posts/2010/05/installing_debian_on_the_guruplug_server_plus/)

10) Download uImage and uInitrd installer to your tftp server
Code:
wget http://http.us.debian.org/debian/dists/squeeze/main/installer-armel/current/images/kirkwood/netboot/marvell/guruplug/uImage
wget http://http.us.debian.org/debian/dists/squeeze/main/installer-armel/current/images/kirkwood/netboot/marvell/guruplug/uInitrd

11) Set your plugs environment variables to the correct achitecture

Find your arc
Code:
GuruPlug>> bdinfo
arch_number = 0x00000A63
boot_params = 0x00000100
DRAM bank   = 0x00000000
-> start    = 0x00000000
-> size     = 0x10000000
DRAM bank   = 0x00000001
-> start    = 0x10000000
-> size     = 0x10000000
DRAM bank   = 0x00000002
-> start    = 0x00000000
-> size     = 0x00000000
DRAM bank   = 0x00000003
-> start    = 0x62616C69
-> size     = 0x2A20656C
ethaddr     = 02:50:43:f7:34:25
ip_addr     = 192.168.10.110
baudrate    = 115200 bps
TLB addr    = 0x1FFF0000
relocaddr   = 0x1FF50000
reloc off   = 0x1F950000
irq_sp      = 0x1FE2FF74
sp start    = 0x1FE2FF70
FB base     = 0x00000000
GuruPlug>>

Your Arc = "arch_number = 0x00000A63" Convert this hex number to decimal via: http://easycalculation.com/hex-converter.php
The result in decimal is: 2659

Code:
setenv
setenv arcNumber 2659
saveenv
reset
the "Bad CRC" error will be gone finally ;-)

12) REPLUG YOUR POWER! Why? beat me, just do it! I found that the installer might hang when its trying to boot the kernel if you dont. I tested this about 20 times and replugging power worked for me every time.

13) Running the Debian installer to install on the internal MicroSD card.
Code:
setenv ipaddr 192.168.10.110
setenv serverip 192.168.10.105
tftp 0x01100000 uInitrd
tftp 0x00800000 uImage
setenv bootargs console=ttyS0,115200
bootm 0x00800000 0x01100000
[code]

Follow the installer and do what makes you feel comfortable. Use ext3 for your /boot filesystem and use the ext4 journaling filesystem for other filesystems for optimal performance. Its tested and ext4 is much much much faster that ext3.

When The installation is done, continue to reboot

14) Find your boot files

Start usb
[code]
GuruPlug>> usb start
(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
2 Storage Device(s) found
GuruPlug>>

List your USB stree
Code:
GuruPlug>> usb tree

Device Tree:
  1  Hub (480 Mb/s, 0mA)
  |  u-boot EHCI Host Controller
  |
  +-2  Hub (480 Mb/s, 100mA)
    |   USB2.0 Hub
    |
    +-3  Mass Storage (480 Mb/s, 500mA)
          USB Storage 000000009909
       
GuruPlug>> usb storage
  Device 0: Vendor: Generic  Rev: 9909 Prod: STORAGE DEVICE 
            Type: Removable Hard Disk
            Capacity: not available
  Device 1: Vendor: Generic  Rev: 9909 Prod: STORAGE DEVICE 
            Type: Removable Hard Disk
            Capacity: 7580.0 MB = 7.4 GB (15523840 x 512)
GuruPlug>>

Device 1 is your internal MicroSD and this will be your target device.

List the partitions on the target
Code:
GuruPlug>> usb part 1

Partition Map for USB device 1  --   Partition Type: DOS

Partition     Start Sector     Num Sectors     Type
    1                 2048          497664      83
    2               499712         1953792      82
    3              2453504        13068288      83
GuruPlug>>

Find where your uImage and uInitrd are located. Use ext2ls usb <device>:<partition> <path>
Code:
GuruPlug>> ext2ls usb 1:1 /
<DIR>       1024 .
<DIR>       1024 ..
<DIR>      12288 lost+found
         1003346 System.map-2.6.32-5-kirkwood
         1431872 vmlinuz-2.6.32-5-kirkwood
<SYM>         28 initrd.img
<SYM>         25 vmlinuz
         1431936 uImage
           84197 config-2.6.32-5-kirkwood
         2571713 initrd.img-2.6.32-5-kirkwood
         2571777 uInitrd
GuruPlug>>

Find your root "/" (in my case partition 3 on device 1)
Code:
GuruPlug>> ext2ls usb 1:3 /
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 var
<DIR>       4096 boot
<DIR>       4096 etc
<DIR>       4096 media
<DIR>      12288 lib
<DIR>       4096 usr
<DIR>       4096 tmp
<DIR>       4096 proc
<DIR>       4096 root
<DIR>       4096 dev
<DIR>       4096 bin
<DIR>       4096 mnt
<DIR>       4096 home
<DIR>       4096 sbin
<DIR>       4096 selinux
<DIR>       4096 sys
<DIR>       4096 srv
<DIR>       4096 opt
GuruPlug>>

15) Make your plug boot

Now that we've found the Kernel, initrd and root filesystem we can start building the boot parameters.
Code:
setenv mainlineLinux yes
setenv bootargs console=ttyS0,115200 root=/dev/sdb3
setenv bootcmd_usb 'usb start; ;ext2load usb 1:1 0x0800000 /uImage; ext2load usb 1:1 0x1100000 /uInitrd'
bootm 0x00800000 0x01100000
saveenv
run bootcmd

So if all went correct you should end up with a prompt telling you to enter a username and password. Meaning: We have succeeded!!
[/code][/code]
19  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: February 27, 2011, 04:26:30 AM
installer is running finally ;-)
20  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: February 27, 2011, 02:07:38 AM
I did yesterday so iḿ hoping for a reply.

So iḿ at the point of installing Debian to the internal SD. I followed the page: http://bzed.de/posts/2010/05/installing_debian_on_the_guruplug_server_plus/

This worked flawlessly in the passed but now the installer stops @

Code:
Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Any ideas?

21  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: February 26, 2011, 03:15:23 PM
true... it's working for me also but that is what i mean with lackings docs. you miss stuff but you dont know what and that is when people start wondering
22  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: February 26, 2011, 02:05:58 AM
Hum!

I thought that this part of updating the uboot is rather well done actually.

Where I got it wrong (if I did!) in my case is more during the installation of Debian on the SD card



Could you please explain how you flashed the NAND with the correct u-boot version?

If i follow the instruction and flash it via openocd the plug dies and nothings happes after that.

If i flash it via tftp/rarp i must use the .kwb image because the .bin doesnt do anything.
After writing it in NAND and resetting i mis the 1st part of u-boot which says : Marvel blabla date bl;abla flipflip
23  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: February 23, 2011, 02:35:45 PM
I thought that this part of updating the uboot is rather well done actually

Than please explain me what you did because i just have it running follwoing the (creappy) description but i have totally no enviroment settings and i even dont see The version of uboot "flipflip"displayed. As i'm proceeding i'm writing a detailed step-by-step howto usable for beginner and pro
24  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: February 23, 2011, 10:29:24 AM
This is the best site I found to update your guruplug

http://oinkzwurgl.org/guruplug

So it looked fine ant the beginning but this is what i call a classic case of BAD documentation  Cry

I started to update my plug wuth the flipflip version of u-boot and after flashing it tot NAND total darkness. Plug wont go back or forth anymore.

Is it really that difficult to make a simpel work instruction howto update? or at least supply the steps and the expected outcome.   More hours puzzeling here
25  Hardware and U-Boot firmware / U-Boot stuff / Re: One good uniform way to install a guru/sheeva wanted on: February 22, 2011, 12:17:28 AM
Thnx guys, both options look very good and i'll start with the 1st post.
26  Hardware and U-Boot firmware / U-Boot stuff / One good uniform way to install a guru/sheeva wanted on: February 20, 2011, 06:24:20 AM
All,

Like most of you i've been struggeling with my guruplug for quite some time now and out off frustration i left the damm thing lying in the corner of my room.
It is running but with an ancient version of UBOOT and a kernel that has a big pile of dust on it.

There are about 1000 different ways to get this nice thing working but all have the problem that intercooperation between "ways" is more than problematic.

For instrance i tried to get my plug booting the kernel from my SD-card and i got a zillion different  versions of uboot which just not all work.

Would it be an idea to combine the knowledge you guruś have and make 1 (or 2)  different instructions that cover the whole flow from uboot till upgrading the kernel.

It would help me and i knwo it will help a whole bunch of other people out there.

Hoping for your responds.

Ernst
27  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25 on: February 11, 2011, 06:45:49 AM
Gents,

Will this version of uboot work correctly with the Guruserver Plus? Iḿ working with a pretty ancient version here so an update would be great ;-)

28  Linux Stuff / Kernel / Re: [HELP] Guruplug bricked after kernel upgrade on: January 12, 2011, 05:59:49 AM
I would advise you to follow this guide through I find it very useful:

http://bzed.de/posts/2010/05/installing_debian_on_the_guruplug_server_plus/

I used this article with 100% succes.

ONLY...... when you want to install the 35.10 kernel it hopelessly crashes while trying to find /lib/modules

I also tried ESIA but that just wrecked my plug for now with a big dark console doing nothing.......... well........ nothing actually
Pages: 1 [2]