cbxbiker61
Global Moderator
Sr. Member
Karma: 37
Posts: 488
|
 |
« on: August 03, 2009, 10:35:02 AM » |
|
2.6.30.4 is now available. Due to changes in vm security a change must be made in /etc/sysctl.d/10-process-security.conf. vm.mmap_min_addr should be set to 32768 (This change is safe for any kernel version). If this is not done it is likely that you will not be able to login remotely. Although you should still be able to login as root on the main console. Kernel and modules are available from the following locations: IPV4: http://sheeva.with-linux.com/sheeva/IPV6: http://sheeva6.with-linux.com/sheeva/Features IPV6, CIFS, NFS4, EXT3, EXT4, JFS, XFS, FUSE(for ntfs-3g), UBIFS, usb-serial, uvcvideo, iptables, appletalk, bluetooth, v4l and ppp. |
|
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #1 on: August 03, 2009, 04:36:28 PM » |
|
Couple of problems here. 1/ http://sheeva6.with-linux.com/sheeva/ does not point to a valid domain, so the script just downloads a openDNS index.html file and then fails. I had to comment out the wget for this line. 2/ I don't have a /etc/sysctl.d/10-process-security.conf !!!! |
|
|
|
|
Logged
|
|
|
|
|
cbxbiker61
Global Moderator
Sr. Member
Karma: 37
Posts: 488
|
|
« Reply #2 on: August 03, 2009, 04:44:55 PM » |
|
2/ I don't have a /etc/sysctl.d/10-process-security.conf !!!!
sheeva:~$ cat /proc/sys/vm/mmap_min_addr 32768 As long as that shows 32768 (or less) you will be fine. |
|
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #3 on: August 03, 2009, 05:03:24 PM » |
|
It is 32768, perhaps the readme needs to be reworded, as this caused me some confusion, and I had already expected it not to recover gracefully after a reboot because that file was not present on my system....
|
|
|
|
|
Logged
|
|
|
|
|
levrin
Newbie
Karma: 0
Posts: 4
|
|
« Reply #4 on: August 04, 2009, 10:36:57 AM » |
|
1/ http://sheeva6.with-linux.com/sheeva/ does not point to a valid domain, so the script just downloads a openDNS index.html file and then fails. I had to comment out the wget for this line. This is probably because OpenDNS(among others) hijacks the NXDOMAIN response that is supposed to indicate an unreachable server and instead spits back the IP address of a support/advertising page of their own. Not much one can do about it short of switching to a DNS that follows the rules or running Dnsmasq between your computer and the DNS servers with the appropriate OpenDNS IP addresses set in the "bogus-nxdomain" option. |
|
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #5 on: August 09, 2009, 08:36:07 PM » |
|
Is there any way btrfs.ko could be added to the modules?
Thanks in advance.
|
|
|
|
|
Logged
|
|
|
|
|
cbxbiker61
Global Moderator
Sr. Member
Karma: 37
Posts: 488
|
|
« Reply #6 on: August 10, 2009, 01:06:49 AM » |
|
btrfs has been added.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #7 on: August 10, 2009, 05:45:43 AM » |
|
btrfs has been added.
Awesome. Thanks. |
|
|
|
|
Logged
|
|
|
|
|
joosty
Newbie
Karma: 0
Posts: 26
|
|
« Reply #8 on: August 10, 2009, 06:34:09 AM » |
|
1/ http://sheeva6.with-linux.com/sheeva/ does not point to a valid domain, so the script just downloads a openDNS index.html file and then fails. I had to comment out the wget for this line. This is probably because OpenDNS(among others) hijacks the NXDOMAIN response that is supposed to indicate an unreachable server and instead spits back the IP address of a support/advertising page of their own. Not much one can do about it short of switching to a DNS that follows the rules or running Dnsmasq between your computer and the DNS servers with the appropriate OpenDNS IP addresses set in the "bogus-nxdomain" option. Register for free, and you can use their 'dashboard' app to control this behaviour. |
|
|
|
|
Logged
|
|
|
|
|
boerner
Jr. Member
Karma: 0
Posts: 54
|
|
« Reply #9 on: August 10, 2009, 02:41:29 PM » |
|
Apologies in advance for the newbie question...
I just received my plug and have successfully used the alpha installer to bring the device up to kernel 2.6.30-rc6. Everything seemed fine. I then tried to follow the instructions in the wiki to install the 'drop-in' kernels from cbxbiker61. Everything seemed okay except when it came to setting the uboot environment variables. The types of variables mentioned in the wiki did not match what was on my plug (I know the actual content may differ slightly). I did my best to make the required changes, but upon reboot the plug kernel panics. The out put of printenv and the relevant portions of the panic follow. Any help would be most appreciated. Thanks.
Environment size: 1992/131068 bytes
Marvell>>
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_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
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
filesize=1CAE6D
bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
arcNumber=2097
bootargs_root=bootargs_root=ubi.mtd=1 root=ubi0:rootfs rootfstype=jffs2
console=console=ttyS0,115200 mtdparts=orion_nand:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
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
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 4096 mtdblock0 (driver?)
1f01 519168 mtdblock1 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[<c00309c0>] (unwind_backtrace+0x0/0xe0) from [<c003db50>] (panic+0x50/0x120)
[<c003db50>] (panic+0x50/0x120) from [<c0008ec0>] (mount_block_root+0x1d4/0x214)
[<c0008ec0>] (mount_block_root+0x1d4/0x214) from [<c000908c>] (prepare_namespace+0x90/0x1c4)
[<c000908c>] (prepare_namespace+0x90/0x1c4) from [<c0008734>] (kernel_init+0xc0/0xec)
[<c0008734>] (kernel_init+0xc0/0xec) from [<c0040b3c>] (do_exit+0x0/0x6ac)
|
|
|
|
|
Logged
|
|
|
|
|
restamp
Global Moderator
Sr. Member
Karma: 4
Posts: 273
|
|
« Reply #10 on: August 10, 2009, 04:57:55 PM » |
|
I have to confess, after running the alpha-6 installer, I moved to an SDcard first, and only later upgraded the kernel (and never looked back), so I have no experience with the UBIFS and cbxbiker61's kernels. However, it seems to me that you don't want to declare your FS "rootfstype=jffs2", but "rootfstype=ubifs". I'd give the following a try: setenv bootargs_root 'ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs'
saveenv
reset Good luck! |
|
|
|
« Last Edit: August 10, 2009, 05:15:26 PM by restamp »
|
Logged
|
|
|
|
|
boerner
Jr. Member
Karma: 0
Posts: 54
|
|
« Reply #11 on: August 10, 2009, 05:07:04 PM » |
|
Gave that a try, still have a kernel panic (although slightly different):
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 4096 mtdblock0 (driver?)
1f01 519168 mtdblock1 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[<c00309c0>] (unwind_backtrace+0x0/0xe0) from [<c003db50>] (panic+0x50/0x120)
[<c003db50>] (panic+0x50/0x120) from [<c0008ec0>] (mount_block_root+0x1d4/0x214)
[<c0008ec0>] (mount_block_root+0x1d4/0x214) from [<c000908c>] (prepare_namespace+0x90/0x1c4)
[<c000908c>] (prepare_namespace+0x90/0x1c4) from [<c0008734>] (kernel_init+0xc0/0xec)
[<c0008734>] (kernel_init+0xc0/0xec) from [<c0040b3c>] (do_exit+0x0/0x6ac)
|
|
|
|
|
Logged
|
|
|
|
|
restamp
Global Moderator
Sr. Member
Karma: 4
Posts: 273
|
|
« Reply #12 on: August 10, 2009, 05:16:38 PM » |
|
Oops, sorry: I screwed up the ubi.mtd assignment above. Give the corrected version a try and let us know the results...
|
|
|
|
|
Logged
|
|
|
|
|
boerner
Jr. Member
Karma: 0
Posts: 54
|
|
« Reply #13 on: August 10, 2009, 05:26:00 PM » |
|
That did the trick. Much appreciated! Can I safely assume that I am not crazy and the wiki article here: http://plugcomputer.org/plugwiki/index.php/Install_Prebuilt_Kernels_From_sheeva.with-linux.comis no longer correct, given the steps I followed? (new unit out of box re-flashed using alpha installer, and then trying the drop kernel steps) Thanks very much for the help. This is one of the friendly boards I have ever been on  |
|
|
|
|
Logged
|
|
|
|
|
Zup
Newbie
Karma: 0
Posts: 6
|
|
« Reply #14 on: August 13, 2009, 04:32:42 PM » |
|
Did you drop making releases for the next kernel candidates? I kinda miss having those. Ie -rc2, - rc3 etc.
|
|
|
|
|
Logged
|
|
|
|
|
|
