Subject: Re: System load?
To: Andy Ruhl <acruhl@gmail.com>
From: Erik Berls <cyber@ono-sendai.com>
List: port-cobalt
Date: 12/11/2006 08:58:20
------=_Part_134869_7777507.1165856300197
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
3.1 is NOT. 3.1 is the 3.0 branch with some additional pullups. 3.99.17 is
of about 6 months ago. Thus its closer to the 4 branch.
I'm not sure about the cubes, but on the raq's you can execute a BFD line at
the prom that may allow you to execute alternate kernels. (It's been a
while since I've had to do this.)
-=erik.
On 12/11/06, Andy Ruhl <acruhl@gmail.com> wrote:
>
> On 12/11/06, Glyn Astill <glynastill@yahoo.co.uk> wrote:
> > Sorry to sound basic, if I upgrade the kernel to v4 will that mean
> > that I'm running version 4 of NetBSD?
> >
> > In theory this shouldn't change the way my machine works, it'll just
> > be running a newer kernel?
> >
> > What worries me is if I compile a poo kernel and am unable to get
> > back into the os to put the old image back.
> >
> > What are the Qube specific switches and configurations used to do
> > this?
> >
> > I think I'm going to need some hand hloding through this or I may
> > cry.
>
> Start with this.
>
> (Same old "back up your box" disclaimer will apply eventually)
>
> Mount your Linux partition and do ls -l in the boot directory on the
> Linux partition. Here's a quick example:
>
> My Qube2 disk (non fixed font garbled, sorry):
>
> # disklabel -r wd0
> # /dev/rwd0d:
> type: ESDI
> disk: IC35L060AVER07-0
> label: fictitious
> flags:
> bytes/sector: 512
> sectors/track: 63
> tracks/cylinder: 16
> sectors/cylinder: 1008
> cylinders: 119150
> total sectors: 120103200
> rpm: 3600
> interleave: 1
> trackskew: 0
> cylinderskew: 0
> headswitch: 0 # microseconds
> track-to-track seek: 0 # microseconds
> drivedata: 0
>
> 8 partitions:
> # size offset fstype [fsize bsize cpg/sgs]
> a: 118993074 1110126 4.2BSD 2048 16384 28608 # (Cyl. 1101*-
> 119149)
> b: 1048576 61550 swap # (Cyl.
> 61*- 1101*)
> c: 120041650 61550 unused 0 0 # (Cyl. 61*-
> 119149)
> d: 120103200 0 unused 0 0 # (Cyl. 0 -
> 119149)
> e: 61487 63 Linux Ext2 0 0 # (Cyl.
> 0*- 61*)
> f: 120041650 61550 unused 0 0 # (Cyl. 61*-
> 119149)
>
> Linux partition is /dev/wd0e, so let's mount it:
>
> # mount -t ext2fs /dev/wd0e /mnt
> # ls -l /mnt/boot
> total 104
> -r-xr-xr-x 1 root wheel 22470 Sep 19 2005 boot.gz
> -r--r--r-- 1 root wheel 27838 Jul 12 2004 boot.old.gz
> -r-xr-xr-x 1 root wheel 22473 Sep 19 2005 vmlinux.gz
> -r--r--r-- 1 root wheel 27838 Jul 12 2004 vmlinux.old.gz
>
> I'm not remembering at this point if it's vmlinux.gz or boot.gz that
> is being read by the Cobalt firmware... I believe it's vmlinux.gz. The
> point is, if it's this small (22k or so), then it's really just the
> NetBSD bootloader, and this is good news. What it means is, you can
> just change the NetBSD kernel in / at your own whim to try different
> kernels.
>
> Meaning:
>
> 1. compile a new kernel
> 2. cp /netbsd /netbsd.old
> 3. cp newkernel /netbsd
> 4. reboot
>
> It's not very likely that you will render the machine unbootable, I
> haven't had that problem in quite a long time now. The main thing to
> remember is, you can change the kernels all you want. But once you
> start upgrading userland utilities to match that kernel, you can't
> then go backwards back to your old kernel.
>
> My best advice is:
>
> Find a newer kernel that is newer than your current userland. I'm not
> sure if 3.1 is, anyone? If so, you can get it here:
>
> ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-3.1/cobalt/binary/kernel/netbsd-GENERIC.gz
>
> Then put that one in place and try it. If this one is not newer than
> your userland, then you'll have to grab either the release-4 or
> current source and compile a kernel. The NetBSD guide has rather good
> instructions on doing this. But maybe we can help.
>
> Andy
>
------=_Part_134869_7777507.1165856300197
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
3.1 is NOT. 3.1 is the 3.0 branch with some additional pullups. 3.99.17 is of about 6 months ago. Thus its closer to the 4 branch.<br><br>I'm not sure about the cubes, but on the raq's you can execute a BFD line at the prom that may allow you to execute alternate kernels. (It's been a while since I've had to do this.)
<br><br>-=erik.<br><br><br><br><br><div><span class="gmail_quote">On 12/11/06, <b class="gmail_sendername">Andy Ruhl</b> <<a href="mailto:acruhl@gmail.com">acruhl@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 12/11/06, Glyn Astill <<a href="mailto:glynastill@yahoo.co.uk">glynastill@yahoo.co.uk</a>> wrote:<br>> Sorry to sound basic, if I upgrade the kernel to v4 will that mean<br>> that I'm running version 4 of NetBSD?
<br>><br>> In theory this shouldn't change the way my machine works, it'll just<br>> be running a newer kernel?<br>><br>> What worries me is if I compile a poo kernel and am unable to get<br>> back into the os to put the old image back.
<br>><br>> What are the Qube specific switches and configurations used to do<br>> this?<br>><br>> I think I'm going to need some hand hloding through this or I may<br>> cry.<br><br>Start with this.<br><br>
(Same old "back up your box" disclaimer will apply eventually)<br><br>Mount your Linux partition and do ls -l in the boot directory on the<br>Linux partition. Here's a quick example:<br><br>My Qube2 disk (non fixed font garbled, sorry):
<br><br># disklabel -r wd0<br># /dev/rwd0d:<br>type: ESDI<br>disk: IC35L060AVER07-0<br>label: fictitious<br>flags:<br>bytes/sector: 512<br>sectors/track: 63<br>tracks/cylinder: 16<br>sectors/cylinder: 1008<br>cylinders: 119150
<br>total sectors: 120103200<br>rpm: 3600<br>interleave: 1<br>trackskew: 0<br>cylinderskew: 0<br>headswitch: 0 # microseconds<br>track-to-track seek: 0 # microseconds<br>drivedata: 0<br><br>8 partitions:<br># size offset fstype [fsize bsize cpg/sgs]
<br> a: 118993074 1110126 4.2BSD 2048 16384 28608 # (Cyl. 1101*- 119149)<br> b: 1048576 61550 swap # (Cyl.<br>61*- 1101*)<br> c: 120041650 61550 unused 0 0 # (Cyl. 61*- 119149)
<br> d: 120103200 0 unused 0 0 # (Cyl. 0 - 119149)<br> e: 61487 63 Linux Ext2 0 0 # (Cyl.<br>0*- 61*)<br> f: 120041650 61550 unused 0 0 # (Cyl. 61*- 119149)
<br><br>Linux partition is /dev/wd0e, so let's mount it:<br><br># mount -t ext2fs /dev/wd0e /mnt<br># ls -l /mnt/boot<br>total 104<br>-r-xr-xr-x 1 root wheel 22470 Sep 19 2005 boot.gz<br>-r--r--r-- 1 root wheel 27838 Jul 12 2004
boot.old.gz<br>-r-xr-xr-x 1 root wheel 22473 Sep 19 2005 vmlinux.gz<br>-r--r--r-- 1 root wheel 27838 Jul 12 2004 vmlinux.old.gz<br><br>I'm not remembering at this point if it's vmlinux.gz or boot.gz that<br>is being read by the Cobalt firmware... I believe it's
vmlinux.gz. The<br>point is, if it's this small (22k or so), then it's really just the<br>NetBSD bootloader, and this is good news. What it means is, you can<br>just change the NetBSD kernel in / at your own whim to try different
<br>kernels.<br><br>Meaning:<br><br>1. compile a new kernel<br>2. cp /netbsd /netbsd.old<br>3. cp newkernel /netbsd<br>4. reboot<br><br>It's not very likely that you will render the machine unbootable, I<br>haven't had that problem in quite a long time now. The main thing to
<br>remember is, you can change the kernels all you want. But once you<br>start upgrading userland utilities to match that kernel, you can't<br>then go backwards back to your old kernel.<br><br>My best advice is:<br><br>Find a newer kernel that is newer than your current userland. I'm not
<br>sure if 3.1 is, anyone? If so, you can get it here:<br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-3.1/cobalt/binary/kernel/netbsd-GENERIC.gz">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-3.1/cobalt/binary/kernel/netbsd-GENERIC.gz
</a><br><br>Then put that one in place and try it. If this one is not newer than<br>your userland, then you'll have to grab either the release-4 or<br>current source and compile a kernel. The NetBSD guide has rather good<br>
instructions on doing this. But maybe we can help.<br><br>Andy<br></blockquote></div><br>
------=_Part_134869_7777507.1165856300197--