 Show Posts
|
|
Pages: [1] 2 3
|
|
1
|
Linux Stuff / Kernel / Re: 2.6.30 new release
|
on: June 26, 2009, 08:40:00 AM
|
|
I assume those iperf numbers are from this 2.6.30 kernel...?
Do we know how they compare to the stock kernel, or at least one without iptables, bridging, and other applicable additions?
|
|
|
|
|
2
|
Linux Stuff / General Linux questions / Re: iptables
|
on: June 25, 2009, 07:39:23 PM
|
Sorry for the noobery. I figured it out. I knew I was keeping this Linux Server Hacks book handy, even though it's overdue at the library. After hours of googling and reading man pages, that's where I found the answer. I needed to preface my iptables command with the following: echo "1" /prov/sys/net/ipv4/ip_forward |
|
|
|
|
3
|
Linux Stuff / General Linux questions / iptables
|
on: June 25, 2009, 05:45:14 PM
|
I've never done anything manually with iptables before, but I need my sheevaplug to nat traffic for vpn clients connected to it. I'm running cbxbiker's 2.6.30 kernel on ubuntu, and installed openvpn (rc11) and iptables (1.4.1.1) with apt-get. The openvpn documentation says to issue the following command: iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE However, when I connect a client after issuing that command and restarting openvpn, all the client can do is ping the server, but cannot see the public internet. I'm kinda new at this, but it looks like that chain isn't sticking: root@vpnplug1:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination Any idears? |
|
|
|
|
4
|
Linux Stuff / Kernel / Re: 2.6.30 new release
|
on: June 25, 2009, 12:35:01 PM
|
Woops, I think the problem was with the jffs2 image I was using. I just tried another one, and I booted in fine. Though, I did get four message during boot like these: FATAL: Could not load /lib/modules/2.6.30/modules.dep: No such file or directory Are those anything to worry about? |
|
|
|
|
5
|
Linux Stuff / Kernel / Re: 2.6.30 new release
|
on: June 25, 2009, 11:32:55 AM
|
Ya know, it's been long enough since I messed with it that I don't remember. Looks like you're right: -sh-3.2# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "uboot"
mtd1: 00300000 00020000 "uImage"
mtd2: 1fc00000 00020000 "rootfs"
I took my best shot at changing the bootargs, but I'm still getting the same thing. 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
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
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;
ethaddr=00:50:43:56:23:2e
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
autoload=no
ethact=egiga0
loadaddr=0x2000000
mtd1Size=0x300000
filesize=0x44ad000
arcNumber=2097
bootargs=rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x300000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1
bootcmd=nand read.e 0x800000 0x100000 0x300000; bootm 0x800000’
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x300000@0x100000(uImage),0x1fc00000@0x400000(rootfs)rw
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
|
|
|
|
|
6
|
Linux Stuff / Kernel / Re: 2.6.30 new release
|
on: June 25, 2009, 10:42:55 AM
|
Could someone who has this working post a printenv, or maybe give me some hints what I have wrong? I'm getting Kernel panic - not syncing: No init found after flashing with this. Here's my 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
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
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;
ethaddr=00:50:43:56:23:2e
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
autoload=no
ethact=egiga0
loadaddr=0x2000000
mtd1Size=0x300000
filesize=0x44ad000
arcNumber=2097
bootcmd=nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootargs=rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x300000@0x100000(uImage),0x1fc00000@0x400000(rootfs)rw
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: 1350/131068 bytes
|
|
|
|
|
7
|
Linux Stuff / Kernel / Re: 2.6.30-rc8 new release
|
on: June 24, 2009, 11:00:28 PM
|
|
I'm loving your kernels, cbxbiker. Thanks for the work you put into them. You've saved me a ton of time and headache.
I need to do some iptables stuff on my sheevaplug, and I'm finding that this kernel isn't set up for it. Could you make sure the standard iptables stuff is enabled in the next compile, as well as the following:
Networking -> Network options -> Netfilter -> Core Netfilter Configuration:
* Netfilter connection tracking support
* state match support
Networking -> Network options -> Netfilter -> Core Netfilter Configuration:
* IPv4 connection tracking support
|
|
|
|
|
8
|
Linux Stuff / Kernel / Re: anyone compile a custom kernel yet?
|
on: April 30, 2009, 02:17:31 PM
|
|
Thanks for the info.
I always do an eraseall before flashing. In fact, I've reflashed my plug successfully around 20 times, but always using the stock kernel and either the stock root fs or my own fs.
So, I'm fairly well versed with the process, but using my custom kernel has stumped me.
|
|
|
|
|
9
|
Linux Stuff / Kernel / Re: anyone compile a custom kernel yet?
|
on: April 30, 2009, 08:06:02 AM
|
|
I used:
# nandwrite –p /dev/mtd1 uImage.myimage.v01
# nandwrite –p /dev/mtd2 <filesystem>
I saw your previous comment about the -p switch and tried it without it on my second go around. It gave me an error that said, in effect, that my image was not properly aligned to allow flashing without padding. It wouldn't flash without -p.
|
|
|
|
|
10
|
Linux Stuff / Kernel / Re: anyone compile a custom kernel yet?
|
on: April 29, 2009, 11:27:37 PM
|
|
To all those that have successfully compiled and booted a custom kernel, are there any additional tricks that I'd need to know?
After wrestling with the (rather poor) PDF documentation for a day, I got my custom kernel to compile using the toolchain and kernel sources Marvell supplies. I throw the uImage and jffs2 image on a USB drive, flash both to the plug, and when I reboot I get Bad Magic Number. I didn't resize my MTD1 because my custom kernel is smaller than the stock one, probably because I didn't compile audio support.
I toyed for a bit at making MTD1 bigger, but when I do that then I can't get it to mount rootfs when booting from USB to flash write the images to NAND. I only played with that for a bit, though, because it seems like I shouldn't need a bigger MTD1, what with my uImage being smaller than the original.
Is there anything else I can try?
|
|
|
|
|
11
|
Linux Stuff / General Linux questions / Re: Network: writes fast / reads slow?
|
on: April 29, 2009, 05:40:17 PM
|
|
How big are the files you're copying, and are you going to/from the internal NAND or somewhere else?
One explanation could be that files being sent to the plug are being buffered to RAM, allowing the plug to accept data from the network at a higher speed than the NAND can write it. It then writes it to the NAND as it is able to. Obviously, it can only read as fast as the NAND will allow, which would explain why it sends data more slowly.
You could test this by moving around some very large files. If the receiving speed slows down partway through, then you know that this is what is happening. The buffer fills, forcing the TCP/IP stack to close the receive window which slows down the transmission.
|
|
|
|
|
12
|
Linux Stuff / Kernel / Re: "Bad Magic Number"
|
on: April 29, 2009, 01:19:15 PM
|
Yep. Marvell>> print
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
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;
ethaddr=00:50:43:d6:13:26
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
netretry=no
rcvrip=169.254.100.100
autoload=no
ethact=egiga0
bootcmd=nand read.e 0x800000 0x100000 0x300000; bootm 0x800000
nandEcc=4
loadaddr=0x2000000
mtd1Size=0x300000
filesize=0x44ad000
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0x00000(u-boot),0x300000@0x100000(uImage)ro,0x1fc00000@0x400000(rootfs)rw root=/dev/mtdblock2
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x300000@0x100000(uImage),0x1fc00000@0x400000(rootfs)rw
mainlineLinux=no
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: 1338/131068 bytes
|
|
|
|
|
13
|
Linux Stuff / Kernel / Re: "Bad Magic Number"
|
on: April 29, 2009, 12:50:55 PM
|
|
I'm getting "Bad Magic Number" after I compiled my own kernel, flashed it to NAND via USB (following the instructions in the PDF), and then tried to boot it. My kernel image is actually smaller than the 040309 image provided by Marvell (which I have flashed successfully), probably because I removed support for audio devices when I compiled. The only other change I made from the default config was enabling TUN/TAP support. Still, I get Bad Magic Number when I use the suggested mtd1Size 0x300000. I've tried making it bigger, but have yet to find the right bootargs that'll let me boot at all with a bigger MTD1. I doubt I need to make it bigger anyway, since my image is smaller.
My cross compiler is the one included on the disc, set up as it says in the PDF. I compiled the kernel on the disc, following the instructions in the PDF. I flashed it to NAND from USB using the instructions in the PDF.
Are there any other things I should be looking at for Bad Magic Number?
|
|
|
|
|
14
|
Linux Stuff / Linux distributions / Re: Anybody upgraded to Ubuntu 9.04 Final yet?
|
on: April 26, 2009, 04:02:51 PM
|
|
If you do it, be sure to autoremove and clean afterwards. The upgrade leaves a lot of cruft that will just be eating up space.
Incidentally, is samba installed by default on the devices when they ship? I noticed that it was installed after the upgrade. Removing and purging it brought free space back down to within 10MB of where it was before the upgrade.
|
|
|
|
|
15
|
Linux Stuff / Linux distributions / Re: Modifying the Ubuntu jffs2 Image
|
on: April 24, 2009, 03:02:39 PM
|
mkfs.jffs2 -l -e 0x20000 --pad -r/mnt/usb/ -o my-fs.jffs2
This command needs to include the -n switch, which tells it not to write cleanmarker nodes to the beginning of eraseblocks. NAND memory doesn't want to see them, and will generate warnings at each and every eraseblock when you flash the image back to NAND and mount it as the root FS. It will work, it just generates a ton of warnings and a huge delay as it spits them all out. The command should read something like: mkfs.jffs2 -l -n -e 0x20000 --pad -r /mnt/usb/ -o my-fs.jffs2 |
|
|
|
|
