• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2
1  Linux Stuff / General Linux questions / Re: Make IP Forwarding permanent? on: September 13, 2010, 04:29:30 AM
Thanks guys. I ended up going with birdman's suggestion, as that seemed more 'userland' than cjm's approach. Sure enough, after a reboot I checked the contents of /proc/sys/net/ipv4/ip_forward and it had 1 in there rather than 0, so looks like it's going to stick now.
2  Linux Stuff / General Linux questions / Make IP Forwarding permanent? on: September 10, 2010, 04:41:58 AM
I setup OpenVPN on my plug a while back, and I forgot that I had enabled IP forwarding on it so that my client machine could see the subnet behind my OpenVPN server. It took me a while to figure out that the reason this no longer worked was because the plug had been rebooted and had therefore reverted back to the original setting of ip_forward=0. Is there some way to make this setting permanent so that it sticks across reboots? Thanks.
3  Linux Stuff / General Linux questions / Re: How can I share root filesystem read-write via Samba? on: September 07, 2009, 01:55:30 PM
Thanks a lot! I simply added 'force user = "root"' and that did the trick.
4  Linux Stuff / General Linux questions / How can I share root filesystem read-write via Samba? on: September 07, 2009, 11:30:40 AM
I'm trying to share the root of the Sheevaplug file system via Samba so that I can mount it from a Windows computer. I can view all the files from the remote Windows machine, but all attempts to write fail. The share I've defined in smb.conf looks like this:

Code:
[Root]
   comment = Root
   path = /
   guest ok = no
   browseable = yes
   public = yes
   writable = yes

Even if I select "Map network drive" from file explorer on Windows, and enter the root credentials, I still can't write to the share (but I can still read everything on it). Has anyone gotten something like this working?
5  Linux Stuff / Kernel / Re: Mainline 2.6.30.1 always stuck at "done, booting the kernel" on: August 12, 2009, 07:27:29 PM
Yep; the installer seems to have done the trick. I guess the uBoot that it puts on there solved my problem, because after that I could simply use the following lines at the uBoot prompt and it would boot my existing kernel and rootfs from SD card.

Code:
set bootargs_mainline 'console=ttyS0,115200 mtdparts=orion_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mmcblk0p1 rw ip=192.168.1.119:192.168.1.21:::DB88FXX81:eth0:none'
set boot_sd_mainline 'setenv image_name sheeva-2.6.30.1-uImage;setenv mainlineLinux yes;run bootsd;setenv bootargs $(bootargs_mainline);bootm 0x2000000'
set bootsd 'mmcinit;ext2load mmc 0:1 0x2000000 /$(image_name)'
6  Linux Stuff / Kernel / Re: Mainline 2.6.30.1 always stuck at "done, booting the kernel" on: August 12, 2009, 06:28:03 PM
Thanks for the reply. I tried changing the mtdparts to match my working config, but it didn't help at all. I think I'm going to try the installer next.
7  Linux Stuff / Kernel / Mainline 2.6.30.1 always stuck at "done, booting the kernel" on: August 11, 2009, 05:49:36 AM
I've been trying to get this kernel (from cbxbiker) to boot for several days now, and no matter what I try, it always gets stuck with the message "Uncompressing Linux...done, booting the kernel", at which point I have no choice but to insert a pin into the reset hole. I've tried booting it from SD card and via TFTP with the same results. I have no trouble booting the stock kernel (2.6.22.18) from NAND, SD, or TFTP, and I'm using the modified uBoot created by kwonsk a few months ago (described here: http://plugcomputer.org/plugforum/index.php?topic=183.30).

I've been searching the forums, but I'm not exactly a Linux guy, so some of the stuff mentioned doesn't make a lot of sense to me. But from what I've gathered, is it possible that:

1) Since the newer kernel is somewhat larger than the stock kernel, by about 600,000 bytes, do I need an even newer version of uBoot? Do I need to adjust the orion_nand parameters somehow?
2) I'm using a high-speed (SanDisk Extreme III 4 GB) SD card, and while I haven't had any problems with it, I do keep finding posts about disabling high-speed operations in the kernel. I'm able to get to the exact same point when I boot the kernel via TFTP, but is this high-speed card somehow the problem?

I would really appreciate any help anyone can give in this area. Thanks in advance.


Working config; stock kernel and rootfs on SD card:
Code:
bootsd=mmcinit;ext2load mmc 0:1 0x2000000 /$(image_name)
bootargs_sd=root=/dev/mmcblk0p1 rw
console=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x0@0x100000(uImage),0x1ff00000@0x100000(rootfs)rw
boot_sd=set mainlineLinux no; run bootsd; setenv bootargs $(console) $(bootargs_sd) ip=$(ipaddr):$(serverip)$(bootargs_end);bootm 0x2000000
image_name=uImage.sheeva.040309

Non-working config; mainline 2.6.30.1 kernel and rootfs on SD card:
Code:
boot_sd_mainline=setenv image_name sheeva-2.6.30.1-uImage;setenv mainlineLinux yes;run bootsd;setenv bootargs $(bootargs_mainline);bootm 0x2000000
bootargs_mainline=console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mmcblk0p1 rw ip=192.168.1.119:192.168.1.21:::DB88FXX81:eth0:none
arcNumber=2097

Non-working config; mainline 2.6.30.1 kernel on TFTP and rootfs on SD card:
Code:
boot_nfs_mainline=setenv image_name sheeva-2.6.30.1-uImage;setenv mainlineLinux yes;run boottftp;setenv bootargs $(bootargs_mainline);bootm 0x2000000
boottftp=tftpboot 0x2000000 $(image_name)
bootargs_mainline=console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mmcblk0p1 rw ip=192.168.1.119:192.168.1.21:::DB88FXX81:eth0:none
arcNumber=2097

Full dump:
Code:
CASset=min
MALLOC_len=1
arcNumber=2097
autoload=no
baudrate=115200
boot_nand=run bootnand;setenv bootargs $(console) $(bootargs_nand) ip=$(ipaddr):$(serverip)$(bootargs_end);bootm 0x2000000
boot_nfs=run boottftp;setenv bootargs $(console) $(bootargs_nfs) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end);bootm 0x2000000
boot_nfs_mainline=setenv image_name sheeva-2.6.30.1-uImage;setenv mainlineLinux yes;run boottftp;setenv bootargs $(bootargs_mainline);bootm 0x2000000
boot_sd=set mainlineLinux no; run bootsd; setenv bootargs $(console) $(bootargs_sd) ip=$(ipaddr):$(serverip)$(bootargs_end);bootm 0x2000000
boot_sd_mainline=setenv image_name sheeva-2.6.30.1-uImage;setenv mainlineLinux yes;run bootsd;setenv bootargs $(bootargs_mainline);bootm 0x2000000
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x0@0x100000(uImage),0x1ff00000@0x100000(rootfs)rw root=/dev/mtdblock2 rw ip=192.168.1.119:192.168.1.21:::DB88FXX81:eth0:none
bootargs_end=:::DB88FXX81:eth0:none
bootargs_mainline=console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mmcblk0p1 rw ip=192.168.1.119:192.168.1.21:::DB88FXX81:eth0:none
bootargs_nand=root=/dev/mtdblock2 rw
bootargs_nfs=root=/dev/nfs rw
bootargs_root=root=/dev/nfs rw
bootargs_sd=root=/dev/mmcblk0p1 rw
bootcmd=run boot_sd
bootdelay=3
bootnand=nand read.e 0x2000000 0x00100000 0x00500000
bootsd=mmcinit;ext2load mmc 0:1 0x2000000 /$(image_name)
boottftp=tftpboot 0x2000000 $(image_name)
cesvcid=ULULULULULULPPULULULULULDA
console=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x0@0x100000(uImage),0x1ff00000@0x100000(rootfs)rw
console_mainline=console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw
disL2Cache=no
disL2Prefetch=yes
disaMvPnp=no
enaAutoRecovery=yes
enaCpuStream=no
enaDCPref=yes
enaICPref=yes
enaMonExt=no
enaWrAllo=no
ethact=egiga0
ethaddr=00:50:43:01:C4:BD
ethmtu=1500
ethprime=egiga0
fileaddr=2000000
filesize=1F972C
image_name=uImage.sheeva.040309
ipaddr=192.168.1.119
loadaddr=0x02000000
loads_echo=0
mainlineLinux=no
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
nandEcc=1bit
netbsd_en=no
netmask=255.255.0.0
netretry=no
pexMode=RC
rcvrip=169.254.100.100
rootpath=/root/rootfsv1.0
run_diag=no
sata_dma_mode=yes
serverip=192.168.1.21
setL2CacheWT=yes
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
stderr=serial
stdin=serial
stdout=serial
usb0Mode=host
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81
8  Linux Stuff / Kernel / Re: USB port dead? (Debian) on: June 07, 2009, 08:07:48 AM
I had a similar problem with the SDIO port being dead. Fortunately, GlobalScale support is very responsive, so if you do determine the USB port is dead, you shouldn't have much trouble getting a replacement sent out once you contact them.
9  Hardware and U-Boot firmware / U-Boot stuff / Re: MMC/SD support in u-boot on: May 17, 2009, 07:14:01 PM
I'm still unable to compile u-boot from source. I have confirmed that include/config.mk was generated correctly, because all the #defines needed for SheevaPlug are listed in that file, and if I delete it, make will fail with 'System not configured - see README'. Is everyone using the supplied Marvell cross-compiler, or should I be using a different one? I basically just extracted the contents of the Linux host support package and prepended  its gcc/bin directory to my path, so I believe gcc is able to locate all the ARM-specific versions of the toolchain. Yet every time I run make, it gives me the same error that I listed earlier in this thread: MV_BOOTSIZE undefined. It's as if it's not properly reading the config.mk file that was generated by the earlier step and appending the options listed therein. Can anyone who has successfully compiled u-boot tell me how they setup their cross-compiler? Thanks.
10  Hardware and U-Boot firmware / U-Boot stuff / Re: Trouble using ext2ls/ext2load on: May 17, 2009, 02:54:35 PM
I finally figured this out. Assuming you have a single ext2 partition on your SD card, and have placed the kernel image in the root of that partition, the following sequence of commands from the uBoot prompt will load the kernel image into memory and then boot it:

Code:
mmcinit
ext2load mmc 0:1 0x2000000/uImage.sheeva.040309
bootm 0x2000000

Hope this helps someone else, and thanks to kwonsk for the patches to uBoot to make this possible.

11  Hardware and U-Boot firmware / U-Boot stuff / Re: Trouble using ext2ls/ext2load on: May 17, 2009, 02:29:05 PM
Ok, I got a little farther with ext2ls. The built-in help doesn't tell you all the options that need to be passed in, but searching around revealed the syntax to be something similar to:

ext2ls mmc 0:1 /

That command lists all the files in the root of my SD card. Now I'm just having trouble figuring out the correct args for ext2load.
12  Hardware and U-Boot firmware / U-Boot stuff / Trouble using ext2ls/ext2load on: May 17, 2009, 02:22:22 PM
I'm using kwonsk's uBoot modifications in order to try and get my kernel to boot from an SD card. I have that uBoot version installed successfully, and mmcinit works just fine, but I can't figure out how to use the ext2ls and ext2load commands. Both of them simply display usage information, regardless of what options I pass. Are those commands just placeholders that aren't functional yet? How can I get ext2ls to display the contents of a folder on my SD card, which appears as /dev/mmcblk0p1 when I have booted Ubuntu?
13  Hardware and U-Boot firmware / U-Boot stuff / Re: MMC/SD supprot in u-boot on: May 07, 2009, 06:56:19 PM
kwonsk, I tried following the directions in a previous post you made, but at step 8, I get the following error:

Code:
make[1]: Entering directory `/home/paragchandra/SheevaPlug/SheevaPlug_U-Boot/Sources/u-boot-3.4.16-modified/post'
arm-none-linux-gnueabi-gcc -Wa,-gstabs -D__ASSEMBLY__ -g  -Os   -fno-strict-aliasing  -fno-common -ffixed-r8 -msoft-float -D__KERNEL__ -DTEXT_BASE=0x00600000 -I/home/paragchandra/SheevaPlug/SheevaPlug_U-Boot/Sources/u-boot-3.4.16-modified/include -fno-builtin -ffreestanding -nostdinc -isystem /home/paragchandra/SheevaPlug/LinuxHost/gcc/bin/../lib/gcc/arm-none-linux-gnueabi/4.2.1/include -pipe  -DCONFIG_ARM -D__ARM__ -march=armv5t -g  -Os   -fno-strict-aliasing  -fno-common -ffixed-r8 -msoft-float -D__KERNEL__ -DTEXT_BASE=0x00600000 -I/home/paragchandra/SheevaPlug/SheevaPlug_U-Boot/Sources/u-boot-3.4.16-modified/include -fno-builtin -ffreestanding -nostdinc -isystem /home/paragchandra/SheevaPlug/LinuxHost/gcc/bin/../lib/gcc/arm-none-linux-gnueabi/4.2.1/include -pipe  -DCONFIG_ARM -D__ARM__ -march=armv5t -c -o cache_8xx.o cache_8xx.S
In file included from /home/paragchandra/SheevaPlug/SheevaPlug_U-Boot/Sources/u-boot-3.4.16-modified/include/configs/mv_kw.h:34,
                 from /home/paragchandra/SheevaPlug/SheevaPlug_U-Boot/Sources/u-boot-3.4.16-modified/include/config.h:2,
                 from cache_8xx.S:23:
/home/paragchandra/SheevaPlug/SheevaPlug_U-Boot/Sources/u-boot-3.4.16-modified/include/configs/../../board/mv_feroceon/mv_kw/mvSysHwConfig.h:306:2: error: #error "MV_BOOTSIZE undefined"

I'm not sure what to set this to; any ideas why it isn't defined in the first place? Thanks.
14  Hardware and U-Boot firmware / U-Boot stuff / Re: Bad Magic Number with uImage.sheeva.040309 and NFS on: May 04, 2009, 11:30:07 AM
Skywalker, that makes perfect sense. I kept trying Ctrl-C,Ctrl-V like in Windows, and when that didn't work and there was no menu option to do it either, I figured it simply wasn't supported. I should have tried those key combos as well, as I think I've seen them listed in the menus of other Linux programs I use. Thanks!
15  Hardware and U-Boot firmware / U-Boot stuff / Re: Bad Magic Number with uImage.sheeva.040309 and NFS on: May 02, 2009, 03:08:53 PM
Thanks for the suggestions, but I couldn't find anything in the help (for xterm at least) that indicates how you could make a connection over a serial port. Tera Term offers this capability, as well as copy and paste, but I think it's only for Windows.
Pages: [1] 2