I like the idea of using apt-get install to update the kernel. I just tried it and got an error when it tried to edit uEnv.txt. I hand edited uEnv.txt and rebooted into the new kernel with no problems.
--Mark [1] apt-get install linux-image-3.8.13.bone59 Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'linux-image-3.8.13-bone59' for regex 'linux-image-3.8.13.bone59' Suggested packages: linux-firmware-image-3.8.13-bone59 The following NEW packages will be installed: linux-image-3.8.13-bone59 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 17.5 MB of archives. After this operation, 40.9 MB of additional disk space will be used. Get:1 http://repos.rcn-ee.net/debian/ wheezy/main linux-image-3.8.13-bone59 armhf 1wheezy [17.5 MB] Fetched 17.5 MB in 19s (909 kB/s) Selecting previously unselected package linux-image-3.8.13-bone59. (Reading database ... 66002 files and directories currently installed.) Unpacking linux-image-3.8.13-bone59 (from .../linux-image-3.8.13-bone59_1wheezy_armhf.deb) ... Setting up linux-image-3.8.13-bone59 (1wheezy) ... update-initramfs: Generating /boot/initrd.img-3.8.13-bone59 zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=3.8.13-bone59] sudo: unable to resolve host yoder-debian-bone sed: -e expression #1, char 15: unterminated `s' command run-parts: /etc/kernel/postinst.d/zz-uenv_txt exited with return code 1 dpkg: error processing linux-image-3.8.13-bone59 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-3.8.13-bone59 E: Sub-process /usr/bin/dpkg returned an error code (1) On Thursday, July 17, 2014 4:44:39 PM UTC-4, john3909 wrote: > > > On 7/17/14, 8:14 AM, "Robert Nelson" <[email protected] <javascript:>> > wrote: > > >On Wed, Jul 16, 2014 at 7:22 PM, Robert Nelson <[email protected] > <javascript:>> > >wrote: > >> On Wed, Jul 16, 2014 at 5:45 PM, John Syn <[email protected] > <javascript:>> wrote: > >>> I've attached my uEnv.txt file I use for mounting rootfs over NFS. Not > >>> sure how to work around using two kernels, one built with initrd and > >>> another without initrd support. > > > >okay, same kernel (v3.15.5-bone5) supports both initrd boot and nfs > >boot. Now i'm confused, why was this broken in prior kernels? > I¹m also confused. I recall working on TFTP boot/NFS rootfs early in the > v3.8 kernel and I had to remove both the initrd reference in bootz and > also compile the kernel without initrd support. If I didn¹t do this, the > kernel boot would hang. I have just rebuilt u-boot with your latest patch > and I used your V3.15.5-bone5 kernel together with your proposed uEnv.txt > and it works perfectly. This is very nice. Thank you for making this so > much easier. Excellent work. > > One change I¹m going to make is change the uboot mount to my tftp folder > so when I update the kernel, it updates the kernel/dtbs on my tftp folder > and not on the MMC BOOT partition. > > Regards, > John > > > >nfsboot: > >http://pastebin.com/sXFSu7k3 > > > >debian@beaglebone:~$ cat disk/uEnv.txt > >client_ip=192.168.0.118 > >server_ip=192.168.0.10 > >gw_ip=192.168.0.1 > >root_dir=/opt/wheezy > > > >mmcboot: > >http://pastebin.com/EKDpTvYc > > > >Regards, > > > >-- > >Robert Nelson > >http://www.rcn-ee.com/ > > > >-- > >For more options, visit http://beagleboard.org/discuss > >--- > >You received this message because you are subscribed to the Google Groups > >"BeagleBoard" group. > >To unsubscribe from this group and stop receiving emails from it, send an > >email to [email protected] <javascript:>. > >For more options, visit https://groups.google.com/d/optout. > > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
