Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: 1 lingering question ....



On 04/09/15 02:09, Joerg Wiegand wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On platforms with a bootloader that lets you select a kernel,
typically drop in as a new name and select it at boot time. In
your case you may have to rename awy the old kernel and put it in
as /netbsd.
Hmmmm .... there in no /netbsd on the system now. There are 2
kernels under /boot, kernel.img & kernel7.img (straight off of
rpi.gzimg file I downloaded a few days ago, no mods by me) .... I
also don't have a monitor hooked up now, did when it was back in my
work room, so I can't choose a kernel if I wanted to :-/ ....

Hi, here is how I do it:

save the old kernel: cp /boot/kernel.img /boot/kernel.img.old

then download the file netbsd-RPI.bin.gz, unzip it and move the file
to /boot/kernel.img .

The other, somewhat bigger file netbsd-RPI.gz contains the kernel in
another format that can be converted to Raspberry's this way (as far
as I remember):

	objcopy -S -O binary netbsd kernel.img

This produces the file in netbsd-RPI.bin.gz.


The modules will unpack in an own directory for each kernel version,
so don't mind about that, no need for backups here.

If the new kernel doesn't work, you can still cp and mv the kernels in
the boot-partition with any other system, so there should be little risk.

But unfortunately I don't see any way to choose between different
kernels at boot time.


Hope this helps,
Joerg Wiegand
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJVJiWUAAoJENQZzfWzYhr44jkH/3wwZVdW2uhhe9P0GfVRjZjJ
UPqU6jFKS8wlpOSnFO6jfGEqk03VTpV22svtX/fnG735NBlhTwC9UyKZwUAkAiTV
j9l6MA2qa6qTHkGe7D6lgJ3pBsP0D3YnaJR01C2RlDRaq3a66fQQxDtA0LLdhAuR
/ukqjeXc5nP/juGAUNj2ai2bKzbap80+hKL9Mc8MxHhBuKpyBOKYvuqAORYZ0+Mr
al06AXKseBU50kYQuVUG//m7YCLEaQqlmjM450smvRuW6hAeXGduCyZWN6fCMgQa
rw8QE2VvfrZrrk6Vl2uyp78Tn8ZE2COicMyn3yhi6nr1f2LGcsCJGEKbgmEuNdM=
=9Yuk
-----END PGP SIGNATURE-----


Thanks for your reply, it clears up much, especially on the 2 different available kernel images (.bin.gz & .gz). The only lingering problem is which of the 2 kernels in /boot is actually booted. The boot code seems to be binary (This was/is NetBSD-7 rpi.gzimg from a few days ago), & I don't know how to tell what was booted, see below:


rpi # grep kernel /var/log/messages
rpi # grep boot /var/log/messages
Mar 27 23:55:59 rpi /netbsd: boot device: ld0
Mar 28 04:44:56 rpi /netbsd: unmounted /dev/ld0e on /boot type msdos
Mar 28 04:44:56 rpi /netbsd: Please press any key to reboot.
Mar 28 04:44:56 rpi /netbsd: rebooting...
Mar 28 04:44:56 rpi /netbsd: boot device: ld0
Mar 28 07:02:02 rpi /netbsd: unmounted /dev/ld0e on /boot type msdos
Mar 28 07:02:02 rpi /netbsd: rebooting...
Mar 28 07:02:03 rpi /netbsd: boot device: ld0
Mar 28 07:02:03 rpi /netbsd: unmounted /dev/ld0e on /boot type msdos
Mar 28 07:02:03 rpi /netbsd: rebooting...
Mar 28 07:02:03 rpi /netbsd: boot device: ld0
Apr  8 00:05:34 rpi /netbsd: boot device: ld0
Apr  8 22:15:14 rpi /netbsd: boot device: ld0
rpi # uname -a
NetBSD rpi 7.0_BETA NetBSD 7.0_BETA (RPI.201503272230Z) evbarm
rpi # lltr /boot/
total 14313
   1   16 drwxr-xr-x   1 root  wheel    16384 Dec 31  1979 ./
1826  544 -rwxr-xr-x   1 root  wheel   555896 Mar 27 19:01 start_cd.elf*
1824 2592 -rwxr-xr-x   1 root  wheel  2651576 Mar 27 19:01 start.elf*
1813 5584 -rwxr-xr-x   1 root  wheel  5715712 Mar 27 19:01 kernel7.img*
1811 5532 -rwxr-xr-x   1 root  wheel  5661248 Mar 27 19:01 kernel.img*
1822    4 -rwxr-xr-x   1 root  wheel     2357 Mar 27 19:01 fixup_cd.dat*
1820    8 -rwxr-xr-x   1 root  wheel     6148 Mar 27 19:01 fixup.dat*
1818   20 -rwxr-xr-x   1 root  wheel    17856 Mar 27 19:01 bootcode.bin*
1816    4 -rwxr-xr-x   1 root  wheel     1447 Mar 27 19:01 LICENCE.broadcom*
   2    1 drwxr-xr-x  21 root  wheel      512 Mar 28 01:30 ../
1829    4 -rwxr-xr-x   1 root  wheel      116 Mar 28 01:57 cmdline.orig.txt*
1809    4 -rwxr-xr-x   1 root  wheel      116 Mar 28 02:15 cmdline.txt*
rpi # cat /boot/cmdline.txt
root=ld0a console=fb
#fb=1280x1024           # to select a mode, otherwise try EDID
#fb=disable             # to disable fb completely
rpi # file /boot/bootcode.bin
/boot/bootcode.bin: data
rpi #


I also wasn't clear that you could copy/mv the kernel file once it had booted, but you apparently can, no ? TIA & thanks again :-) ....


--

	William A. Mahaffey III

 ----------------------------------------------------------------------

	"The M1 Garand is without doubt the finest implement of war
	 ever devised by man."
                           -- Gen. George S. Patton Jr.



Home | Main Index | Thread Index | Old Index