• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2 3
1  Linux Stuff / General Linux questions / Re: USB Hard Drive on: October 09, 2009, 02:17:16 PM
I assume you used swat to set a file on the hard drive partition as a share for samba. Still doesn't work?

Wes
2  Linux Stuff / General Linux questions / iSCSI Initiator on Sheeva on: September 28, 2009, 10:22:09 AM
I have linux-2.6.30.3 on the plug with the Jaunty file system. I have a 2 1/2 inch 250GB USB hard drive from which I boot. I want to install the iSCSI initiator supplied by http://linux-iscsi.sourceforge.net/. I compile the kernel and modules on the plug. When I try to compile iSCSI I get the following:

root@ubuntu:/usr/src/iscsi/linux-iscsi-3.6.3# make TOPDIR=/usr/src/kernel/linux-
2.6.30.3/

Note: using kernel source from /usr/src/kernel/linux-2.6.30.3/ containing
kernel version 2.6.30.3

Note: using kernel config from /usr/src/kernel/linux-2.6.30.3//.config

gcc  -DMODULE -DLINUX=1 -Iinclude -Idriver/include -Icommon/auth -Icommon/login
-Imisc/include -I/usr/src/kernel/linux-2.6.30.3//include -I/usr/src/kernel/linux
-2.6.30.3//drivers/scsi  -MMD -c -o /usr/src/iscsi/linux-iscsi-3.6.3/Linux-armv5
tel/kobj/driver/iscsi.o driver/iscsi.c
In file included from driver/iscsi.c:22:
include/linux/config.h:1:2: error: #error "Compilation aborted. Please read the
FAQ for linux-libc-headers package."
include/linux/config.h:2:2: error: #error "(can be found at http://ep09.pld-linu
x.org/~mmazur/linux-libc-headers/doc/)"
In file included from include/linux/module.h:9,
                 from driver/iscsi.c:24:
include/linux/sched.h:12:22: warning: asm/page.h: No such file or directory

Apparently there is some problem with the header files. When I go to the website recommended by the error messages I find FAQs, but none of them seem to help solve the errors. Can anyone shed some light on the issue?

Wes
3  Linux Stuff / General Linux questions / Re: Directly connecting the plug with a network cable to a notebook on: September 19, 2009, 07:10:46 AM
Wikipedia describes a crossover cable--see
http://en.wikipedia.org/wiki/Ethernet_crossover_cable

Wes
4  Linux Stuff / Linux distributions / Not Page Aligned on: September 10, 2009, 06:04:57 PM
Trying to write the jffs2 image onto the SheevaPlug NAND flash. I have it on USB memory as "compaps.jffs2". When I try to burn it on the nand I get

root@ubuntu:~# nandwrite /dev/mtd2 /compaps.jffs2
Input file is not page aligned
Data was only partially written due to error

How can I get the file to be page aligned so that I can burn it properly?

Wes
5  Linux Stuff / General Linux questions / mkimage on: August 24, 2009, 01:25:36 PM
How to make mkimage?

1. I am trying to build the kernel for Sheeva Plug with iSCSI.

2. Scratchbox does not compile the kernel with any toolchain I have been able to find or to make.

3. The 2.6.30.3 kernel compiles fine outside of Scratchbox using the CROSS_COMPILE option, but the iSCSI (from SourceForge) has problems outside of Scratchbox. So I decided a good option would be to compile the kernel native on the Plug and add iSCSI native on the Plug.

4. When I try to build the kernel native on the Plug, the "make ARCH=arm uImage" runs, but ends without generating uImage because of a missing mkimage. I have tried a number of attempts to make a suitable mkimage, unsuccessfully.

Can anyone suggest a way to get the mkimage?

Wes
6  Linux Stuff / General Linux questions / Kernesl#2 on: July 28, 2009, 06:05:23 PM
My basic objective is to build a kernel, put the uImage on partition 1 (fat) of a USB memory stick, put the file system on partition 2 (ext2), and boot the Sheeva Plug from the memory stick. Then I will be able to make a kernel of my choice.

I have had success using the linux-2.6.30.rc6 uImage and the file system distributed therewith. I have not had success trying to compile the kernel from the distributed source (linux-2.6.22.18), probably because I have had trouble finding and handling the patches that go with it.

Now I have downloaded the linux-2.6.30.3 source and am trying to compile and run it from the memory stick. Here are the steps that I have gone through:


1. Go to ftp.kernel.org and get linux-2.6.30.3.tar.bz2 and linux-2.6.30.3.tar.bz2.sign.

2. Expand this and rename the directory to linux-feroceon_4_2_7_KW.

3. Apply the Marvell LSP patch (linux-feroceon_4_2_7_KW.zip.

4. Apply the big endian patch (0001_gw_BE-fix.patch), but it said it couldn't find the file to be changed.

5. Edit the Makefile to redefine $ARCH to be "arm", and $CROSS_COMPILE to be "arm-none-linux-gnueabi-"

6. make mrproper

7. make mv88f62181_defconfig

8. make uImage  This gives a uImage 2,013,908 bytes long. Copy it to stick part 1.

9. make modules

10. copy the /home/Sheevaplug/linux-feroceon_4_2_7_KW/crypto to stick part 2/lib/modules/kernel/crypto

11. do the same for /drivers, fs, lib, net and sound.

When I try to boot the stick, I get this:

Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
reading uImage
...

2013908 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.30.3
   Created:      2009-07-28  20:53:18 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2013844 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

And there it hangs, so it seems that the kernel is not even getting decompressed.
7  Linux Stuff / General Linux questions / Re: Kernels on: July 26, 2009, 08:53:13 AM
So I go to ftp.kernel.org and get linux-2.6.30.3.tar.bz2 and linux-2.6.30.3.tar.bz2.sign. Do I expand this and rename the directory to linux-feroceon_4_2_7_KW? Can I then apply the Marvell LSP patch (linux-feroceon_4_2_7_KW.zip? And the big endian patch (0001_gw_BE-fix.patch)? What other patches are necessary to compile a kernel for the Sheeva Plug?
8  Linux Stuff / General Linux questions / Re: Kernels on: July 25, 2009, 01:13:58 PM
Here are the boot environs:

Marvell>> printenv
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
bootargs_root=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
mtdpartitions=mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
ethaddr=00:62:81:a0:00:00
real_bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootargs_console=console=ttyS0,115200
recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions); bootm 0x00800000 0x01100000
recover3=run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
recover4=usb start; fatload usb 0 0x00800000 uImage; fatload usb 0 0x01100000 initrd
arcNumber=2097
bootargs=console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
bootargs_usb=console=ttyS0,115200 root=/dev/sda2 rootdelay=20 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw
bootcmd_nand=setenv bootargs $(bootargs_nand); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_usb=setenv bootargs $(bootargs_usb); usb start; fatload usb 0:1 0x800000 uImage; bootm 0x800000; reset
bootargs_nand=console=ttyS0,115200 mtdparts=nand_flash:0x400000@0x100000(uImage) ro,0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock2 rootfstype=jffs2
bootcmd=run bootcmd_usb
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes

Environment size: 2492/131068 bytes

Here is uImage #2:
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16

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

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
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND: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
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
reading uImage
...

2106760 bytes read
## 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, booting the kernel.

And here is from kernel #3:

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16

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

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
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND: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
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
reading uImage
...

2033340 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-07-23  20:49:05 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2033276 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Wes
9  Linux Stuff / General Linux questions / Re: Kernels on: July 24, 2009, 07:54:56 PM
Hi restamp,

OK, I give up. Where do I get the modules that go with the kernel? I copied the /lib/modules from the Installer set into my USB /dev/sda2/lib/modules and tried again. The kernel still hung.

Wes
10  Linux Stuff / General Linux questions / Kernels on: July 24, 2009, 10:36:55 AM
I have three uImages for the Sheeva Plug, one boots up OK, the other two load but hang:

1. uImage from installer, 2,595,208 bytes long, works OK.

2. uImage.sheeva.20090319, 2,106,760 bytes long, hangs.

3. uImage compiled according to the SheevaPlug dev kit document "Procedure to Configure and Build the Linux kernel with 4.2.7 LSP". It is 2,033,276 bytes long, hangs.

These are all trying to be booted from a USB memory stick using the same boot environment. What could be wrong with the kernels that hang?

Here is the boot console for kernel 2.

Code:
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
reading uImage
...

2106760 bytes read
## 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, booting the kernel.


Wes
11  Linux Stuff / General Linux questions / Re: uImage won't start on: July 23, 2009, 06:06:24 PM
I am now able to boot uImage as distributed. The load and start address of 0x800000 is OK. The distributed uImage is 2595208 bytes long. When I compile the uImage per SheevaPlug dev kit document "Procedure to Configure and Build the Linux kernel with 4.2.7 LSP", I get a uImage that is 2033276 bytes long. It hangs.

Wes
12  Linux Stuff / General Linux questions / Re: Kernel panic - not syncing: No init found. on: July 22, 2009, 09:59:51 AM
Hi, da1l6,

Thanks for the tip. Actually, I had no file system at all. I am booting from USB memory stick only, and I have a /dev/sda1, FAT16 (type 0xe), with uImage, and /dev/sda2, NTFS (type 0x86). Probably nobody else would be so ignorant, but I'll tell my problem just in case.

The uImage, of course is a single, binary file and shows up as such when you mount it on a separate Linux system. I also found in the distributed material a file called "rootfs", which I copied to the /dev/sda2. This was not recognized by the kernel as a file system.

In the installer package there is a rootfs.tar.gz that contains a suitable file system. I copied it to the /dev/sda2 and un-tared it there, then removed the tar source. Now I boot up to the Linux prompt.

Wes
13  Linux Stuff / General Linux questions / Kernel panic - not syncing: No init found. on: July 20, 2009, 06:52:03 PM
Can someone tell me what it means, "unable to open an initial console"?
This is what I get when trying to boot up the Sheeva Plug:

EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem) on device 8:2.
Freeing init memory: 140K
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

Wes
14  Hardware and U-Boot firmware / Hardware / Re: mv88f6281 cpu is too hot on: July 20, 2009, 05:20:11 PM
Hi Victor,

I noticed that my Sheeva Plug gets very warm also. I was letting it stay powered-up continuously, like my desktop. Now that it is summer and the weather here (Southern California) is fairly warm, my Sheeva Plug actually failed--I lost the U-Boot and all. After letting it cool off I was able to use the "Installer" to bring it back.

Wes
15  Linux Stuff / General Linux questions / Re: uImage won't start on: July 18, 2009, 04:04:11 PM
I did try 0x800000 for load address and entry point, but the kernel still did not start. When I build uImage it says this:

Image Name:   Linux-2.6.22.18
Created:      Sat Jul 18 16:02:57 2009
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    2106700 Bytes = 2057.32 kB = 2.01 MB
Load Address: 0x00008000
Entry Point:  0x00008000
  Image arch/arm/boot/uImage is ready

I think it is saying that the image was built for loading at 0x8000 and entry point of 0x8000. Is this not correct? Should I modify the make to build for 0x800000?
Pages: [1] 2 3