Mixed news: new UP 1.0.9 on Ultra5

Mixed news: new UP 1.0.9 on Ultra5

[Malcolm Beattie]

I had a go at installing the latest UltraPenguin 1.0.9 on my Ultra5.
The previous version of 1.0.9 I tried had difficulties with booting
due to various bits of the ultra and, thanks to a flurry of new
kernel images from Eddie Dost, it got booting but didn't appear in
installable form for a while.

The spec of this thing is: Ultra5 270MHz UltraSPARC IIi CPU,
128MB RAM, 4GB IDE disk, SunSwift card (SCSI HBA + extra hme NIC).
The boot PROM is "Openboot 3.11". I set up the new tftpboot.img and
did a "boot net". The good news is that in this configuration, the
new UP1.0.9 boots OK into the installation menus (539 BogoMIPS :-).
The extra hme on the sunswift card gets seen as eth0 and the built-in
hme as eth1. After switching cables, it turns out that Linux refuses
to use the sunswift hme properly. Using tcpdump shows the ultra
sending out lots of arp queries (and the replies heading for the
ultra) but nothing else. It won't respond to ping requests, nor will
NFS work. I confirmed this by setting up the box in a completely
different location on another network and the same happens: the kernel
log shows detection of both hme's OK (eth0: HAPPY..., eth1: HAPPY...)
and the successful bringing up of the link (100/FD in the first test,
10/HD in the second) but no replies. I did configure IP properly.

So then I removed the sunswift card and just used the builtin
hme and eth0. Good news: it boots fine and gets a long way through
installation. All the necessary RPMs were installed and I manually
answered the X questions. Then it failed with
    Error during "Configure timezone"
with the log on VC3 saying
    running /usr/sbin/timeconfig
      tool failed
So I did the next steps manually from the installation menu. The
"Install bootloader" step failed with
    cannot run /bin/rmmod: No such file or directory
so I made a symlink to install2 just as /usr/bin/rmmod has. However,
even after sorting out rmmos/insmod of loop.o the boot loader still
fails to install. I ended up writing an attempted silo.conf from
scratch: I can't remember what my old sparc at home has so I guessed
    boot=/dev/hda
    map=/boot/map
    install=/boot/ultra.b
    image=1/kernel/unix
      label=solaris
      solaris
    image=8/boot/vmlinux-2.1.125.gz
      label=linux
      root=/dev/hda8
      read=only
since I installed Linux on partition 8 (counting 1-8). Running
    silo -r /mnt
gave me the error "failed to open superblock on /dev/hda8".
So I did a "sync;sync;sync;halt". That leaves me in the state where
Linux has successfully installed (as far as I'm aware) but I need to
boot it somehow. I tried a net boot and a floppy boot:
    boot net linux root=/dev/hda8
    boot net root=/dev/hda8
with the same UP1.0.9 installation tftpboot.img. Both put me straight
into the installation dialog rather than mounting my installed
partition as root. Then I wrote the UP1.0.9 boot.img to floppy and did
    boot floppy
    boot floppy linux root=/dev/hda8
    boot floppy root=/dev/hda8
but "boot floppy" with anything just says

    Boot device: /pci@1f,0/pci@1,1/ebus@1/fdthree File and args: ...
    Bad magic number in disk label
    Can't open disk label package

    Can't open boot device

Finally the question: how can I boot this thing now?
If anyone wants more details of the problems along the way (sunswift,
multiple ethernet cards, timeconfig, silo etc.) then let me know.

--Malcolm

-- 
Malcolm Beattie <mbeattie@sable.ox.ac.uk>
Unix Systems Programmer
Oxford University Computing Services

Re: Mixed news: new UP 1.0.9 on Ultra5

[David Andrew - Sun MDE]

Malcolm,

To find the actual OBP version on an Ultra5 or any Sparc, I think, you can 
do "prtconf -V" in bash, or ".version" at the OK prompt.  If your Ultra5 
version is not at least 3.11.7, please send ME a note; I can help you with 
that. 

I had the same timezone problem with the install yesterday; Jakub said he 
was looking into it.  I had no trouble installing Linux on my Ultra5 with 
the previous kernel and boot image on Jakub's cz site (2.1.106).

David
---
> Subject: Mixed news: new UP 1.0.9 on Ultra5
> To: ultralinux@vger.rutgers.edu
> Date: Fri, 30 Oct 1998 16:52:36 +0000 (GMT)
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> From: Malcolm Beattie <mbeattie@sable.ox.ac.uk>
> X-Orcpt: rfc822;ultralinux@vger.rutgers.edu
> X-Loop: majordomo@vger.rutgers.edu
> 
> I had a go at installing the latest UltraPenguin 1.0.9 on my Ultra5.
> The previous version of 1.0.9 I tried had difficulties with booting
> due to various bits of the ultra and, thanks to a flurry of new
> kernel images from Eddie Dost, it got booting but didn't appear in
> installable form for a while.
> 
> The spec of this thing is: Ultra5 270MHz UltraSPARC IIi CPU,
> 128MB RAM, 4GB IDE disk, SunSwift card (SCSI HBA + extra hme NIC).
> The boot PROM is "Openboot 3.11". I set up the new tftpboot.img and
> did a "boot net". The good news is that in this configuration, the
> new UP1.0.9 boots OK into the installation menus (539 BogoMIPS :-).
> The extra hme on the sunswift card gets seen as eth0 and the built-in
> hme as eth1. After switching cables, it turns out that Linux refuses
> to use the sunswift hme properly. Using tcpdump shows the ultra
> sending out lots of arp queries (and the replies heading for the
> ultra) but nothing else. It won't respond to ping requests, nor will
> NFS work. I confirmed this by setting up the box in a completely
> different location on another network and the same happens: the kernel
> log shows detection of both hme's OK (eth0: HAPPY..., eth1: HAPPY...)
> and the successful bringing up of the link (100/FD in the first test,
> 10/HD in the second) but no replies. I did configure IP properly.
> 
> So then I removed the sunswift card and just used the builtin
> hme and eth0. Good news: it boots fine and gets a long way through
> installation. All the necessary RPMs were installed and I manually
> answered the X questions. Then it failed with
>     Error during "Configure timezone"
> with the log on VC3 saying
>     running /usr/sbin/timeconfig
>       tool failed
> So I did the next steps manually from the installation menu. The
> "Install bootloader" step failed with
>     cannot run /bin/rmmod: No such file or directory
> so I made a symlink to install2 just as /usr/bin/rmmod has. However,
> even after sorting out rmmos/insmod of loop.o the boot loader still
> fails to install. I ended up writing an attempted silo.conf from
> scratch: I can't remember what my old sparc at home has so I guessed
>     boot=/dev/hda
>     map=/boot/map
>     install=/boot/ultra.b
>     image=1/kernel/unix
>       label=solaris
>       solaris
>     image=8/boot/vmlinux-2.1.125.gz
>       label=linux
>       root=/dev/hda8
>       read=only
> since I installed Linux on partition 8 (counting 1-8). Running
>     silo -r /mnt
> gave me the error "failed to open superblock on /dev/hda8".
> So I did a "sync;sync;sync;halt". That leaves me in the state where
> Linux has successfully installed (as far as I'm aware) but I need to
> boot it somehow. I tried a net boot and a floppy boot:
>     boot net linux root=/dev/hda8
>     boot net root=/dev/hda8
> with the same UP1.0.9 installation tftpboot.img. Both put me straight
> into the installation dialog rather than mounting my installed
> partition as root. Then I wrote the UP1.0.9 boot.img to floppy and did
>     boot floppy
>     boot floppy linux root=/dev/hda8
>     boot floppy root=/dev/hda8
> but "boot floppy" with anything just says
> 
>     Boot device: /pci@1f,0/pci@1,1/ebus@1/fdthree File and args: ...
>     Bad magic number in disk label
>     Can't open disk label package
> 
>     Can't open boot device
> 
> Finally the question: how can I boot this thing now?
> If anyone wants more details of the problems along the way (sunswift,
> multiple ethernet cards, timeconfig, silo etc.) then let me know.
> 
> --Malcolm
> 
> -- 
> Malcolm Beattie <mbeattie@sable.ox.ac.uk>
> Unix Systems Programmer
> Oxford University Computing Services

David Andrew                Tel:  978-442-2316   Internal:   22316
Market Development Engineer - I/O Technologies   FAX:  978-442-1520	
Sun Microsystems, 2 Omni Way - M/S UCHL02-102,   Chelmsford, MA 01824	 
e-mail:  david.andrew@sun.com

Re: Mixed news: new UP 1.0.9 on Ultra5

[Hine,C]

[cut]
> Good news: it boots fine and gets a long way through
> installation. All the necessary RPMs were installed and I manually
> answered the X questions. Then it failed with
>     Error during "Configure timezone"
> with the log on VC3 saying
>     running /usr/sbin/timeconfig
>       tool failed
> So I did the next steps manually from the installation menu. The
> "Install bootloader" step failed with
>     cannot run /bin/rmmod: No such file or directory
> so I made a symlink to install2 just as /usr/bin/rmmod has. However,
> even after sorting out rmmos/insmod of loop.o the boot loader still
> fails to install.
[cut]

I've had a very similar experience here. Different hardware though,
Netra i (which is basically an Ultra 1 AFAIK) UltraSPARC 143MHz, 64MB
OpenBoot 3.5, 2.1Gb IBM SCSI disk, NCR53C9XF SCSI controller, Toshiba
SCSI CD-ROM, on-board (LANCE ??) ethernet.

I also first tried to install using the floppy disk method. The boot disk
works until after just the partition check it says:

   floppy0: WARNING disk change called early

then asks for the root disk. After inserting the root disk nothing happens.

I then tried the network boot method, and got results as above.

If anyone wants more details, I'll try and help.

Regards,
Chris Hine
---
Internet/Intranet Development
Oce (UK) Ltd.
Email: cph@oce.co.uk

Re: Mixed news: new UP 1.0.9 on Ultra5

[Hine,C]

> [cut]
> > Good news: it boots fine and gets a long way through
> > installation. All the necessary RPMs were installed and I manually
> > answered the X questions. Then it failed with
> >     Error during "Configure timezone"
> > with the log on VC3 saying
> >     running /usr/sbin/timeconfig
> >       tool failed
> > So I did the next steps manually from the installation menu. The
> > "Install bootloader" step failed with
> >     cannot run /bin/rmmod: No such file or directory
> > so I made a symlink to install2 just as /usr/bin/rmmod has. However,
> > even after sorting out rmmos/insmod of loop.o the boot loader still
> > fails to install.
> [cut]
> 
> I've had a very similar experience here. Different hardware though,
> Netra i (which is basically an Ultra 1 AFAIK) UltraSPARC 143MHz, 64MB
> OpenBoot 3.5, 2.1Gb IBM SCSI disk, NCR53C9XF SCSI controller, Toshiba
> SCSI CD-ROM, on-board (LANCE ??) ethernet.
> 
> I also first tried to install using the floppy disk method. 
> The boot disk
> works until after just the partition check it says:
> 
>    floppy0: WARNING disk change called early
> 
> then asks for the root disk. After inserting the root disk 
> nothing happens.
> 
> I then tried the network boot method, and got results as above.

I've just tried the new floppy and tftpboot images Jakub uploaded last night
(02/11).

I had exactly the same problems as above with the floppy install, but
the tftpboot install worked. No problems with any of the installation
steps, except making a recovery disk, put in the blank floppy, and
it just sat there. I'm beginning to suspect a floppy drive problem.
Just a guess but, when I boot using the floppy drive, it says:
Boot device: /sbus/SUNW,fdtwo
could it be an fd0/fd1 problem?

Although the tftpboot installation routine worked, the machine does not boot
properly.
SILO works, the kernel uncompresses, then goes through until i get:
tty_io.c: process 1 (swapper) used obsolete /dev/cua1 - update software to
use /dev/ttyS1
tty_io.c: process 1 (init) used obsolete /dev/cua1 - update software to use
/dev/ttyS1
tty_io.c: process 1 (init) used obsolete /dev/cua1 - update software to use
/dev/ttyS1
tty_io.c: process 1 (init) used obsolete /dev/cua1 - update software to use
/dev/ttyS1
tty_io.c: process 1 (init) used obsolete /dev/cua1 - update software to use
/dev/ttyS1
Which seems like it probably shouldn't cause any problems. The next step is
adding
swap (82072k), at which point it waits for approx. 1 min., before displaying
the
IPX 0.38 stuff followed by:
eth0: Carrier Lost, trying TPE
and that's it, it just sits there.
I tried pinging the machine whilst it boots and and it starts responding
when the
carrier lost message appears.
I can telnet into the machine OK, so I would guess that it a framebuffer
console
problem.
Copied from the linux boot:
Console: switching to colour frame buffer device 128x54
fb0: cgsix at 0000000020000000 TEC Rev 4 CPU sparc Rev b
Any ideas anyone?

If anyone wants anymore information just ask.

Regards,
Chris Hine
---
Internet/Intranet Development
Oce (UK) Ltd.
Email: cph@oce.co.uk

Re: Mixed news: new UP 1.0.9 on Ultra5

[Jakub Jelinek]

> I've just tried the new floppy and tftpboot images Jakub uploaded last night
> (02/11).
> 
> I had exactly the same problems as above with the floppy install, but
> the tftpboot install worked. No problems with any of the installation
> steps, except making a recovery disk, put in the blank floppy, and
> it just sat there. I'm beginning to suspect a floppy drive problem.
> Just a guess but, when I boot using the floppy drive, it says:
> Boot device: /sbus/SUNW,fdtwo
> could it be an fd0/fd1 problem?

Aha, I forgot to mention that SBUS fdtwo is not in healthy state in the
kernel yet, what works perfectly is PCI fdthree (both fd0 and fd1 whichever
it happens), plus maybe sun4m fdtwo, but I'm not sure about it. In fact, I'd
be graceful if someone with a sun4m fdtwo could acknowledge if it works in
recent kernels (2.1.120+) or not. If yes, then we have some Ultra/SBUS
floppy related bug, otherwise it is a problem common to fdtwo.

> 
> Although the tftpboot installation routine worked, the machine does not boot
> properly.
> SILO works, the kernel uncompresses, then goes through until i get:
> tty_io.c: process 1 (swapper) used obsolete /dev/cua1 - update software to
> use /dev/ttyS1
> tty_io.c: process 1 (init) used obsolete /dev/cua1 - update software to use
> /dev/ttyS1
> tty_io.c: process 1 (init) used obsolete /dev/cua1 - update software to use
> /dev/ttyS1
> tty_io.c: process 1 (init) used obsolete /dev/cua1 - update software to use
> /dev/ttyS1
> tty_io.c: process 1 (init) used obsolete /dev/cua1 - update software to use
> /dev/ttyS1

Ok, this is my bug (well, laziness on my part) in that I have not fixed the
setserial package to omit overwriting /dev/console device, so that serial
installs do the above. I'll do that in a couple of minutes.
I've nearly finished with merging the remaining rh5.2 installer changes, so
it is time to have soon a decent distribution.
Thanks guys for all the testing.

Cheers,
    Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.1.126 on a sparc64 machine (498.80 BogoMips).
___________________________________________________________________

Re: Mixed news: new UP 1.0.9 on Ultra5

[Malcolm Beattie]

I retried installing on my Ultra5 today with Jakub's latest UP 1.0.9
update that he put there on Monday. The installation went fine right
up until it tried to make a boot disk. I put a floppy in the drive,
hit "Yes, make a boot disk" and the kernel log on VC 4 came up with:
    <4>floppy0: probe failed...
      (12 lines of the above)
    <4>end_request: I/O error, dev 02:00 (floppy), sector 0
    <7>VFS: Disk change detected on device 02:00
and the cycle then repeated indefinitely "probe failed" x 12 etc).
I killed the "bask mkbootdisk" process but the genromfs process
stuch in D state. That kept the loop device busy so that the
following "install SILO bootloader" couldn't do its
"insmod /modules/loop.o" and thus failed.

I redid the installation from scratch and this time chose not to
make a boot diskette. Everything seemed to install perfectly this
time and at the "Congratulations...hit return to reboot" I did so.
Booting went fine up until the
    Adding swap...
line at which point there was a pause (30 secs to 1 minute perhaps)
before it went on with
    Swansea...
    IPX...
    sunhme.c:v1.2 ...
    eth0: HAPPY MEAL...
    eth0: Link is up using internal transceiver at 10Mb/s, Half Duplex
and then hung. Hitting the CapsLock key lit the light (I don't know if
that's relevant on sparc arch).

I power cycled and did "boot" from the boot prom "ok" prompt.
This time the boot only got as far as
    CMD646: MDMA enable...
and then hung at that point.

Are there any magic keys enabled on sparc to dump any info?
It looks like I'm nearly but not quite there.

--Malcolm

-- 
Malcolm Beattie <mbeattie@sable.ox.ac.uk>
Unix Systems Programmer
Oxford University Computing Services

Re: Mixed news: new UP 1.0.9 on Ultra5

[Malcolm Beattie]

Jakub Jelinek writes:
> > 
> > I retried installing on my Ultra5 today with Jakub's latest UP 1.0.9
> > update that he put there on Monday. The installation went fine right
> > up until it tried to make a boot disk. I put a floppy in the drive,
> > hit "Yes, make a boot disk" and the kernel log on VC 4 came up with:
> >     <4>floppy0: probe failed...
> >       (12 lines of the above)
> >     <4>end_request: I/O error, dev 02:00 (floppy), sector 0
> >     <7>VFS: Disk change detected on device 02:00
> > and the cycle then repeated indefinitely "probe failed" x 12 etc).
> > I killed the "bask mkbootdisk" process but the genromfs process
> > stuch in D state. That kept the loop device busy so that the
> > following "install SILO bootloader" couldn't do its
> > "insmod /modules/loop.o" and thus failed.
> 
> This is strange. My PCI fd (fdthree) works just fine, and I doubt there are
> more types of floppies on PCI machines. I know SBUS floppy is broken at the
> moment, but that's about it. Was the floppy working fine for you with
> previous kernels ever?

This is the first Linux kernel I've been able to try on it. It has
Solaris on it but, on thinking about it, I don't think I've ever
needed to use the diskette drive. I'll do some experiments. It
definitely is an fdthree.

> > I redid the installation from scratch and this time chose not to
> > make a boot diskette. Everything seemed to install perfectly this
> > time and at the "Congratulations...hit return to reboot" I did so.
> > Booting went fine up until the
> >     Adding swap...
> > line at which point there was a pause (30 secs to 1 minute perhaps)
> > before it went on with
> >     Swansea...
> >     IPX...
> >     sunhme.c:v1.2 ...
> >     eth0: HAPPY MEAL...
> >     eth0: Link is up using internal transceiver at 10Mb/s, Half Duplex
> > and then hung. Hitting the CapsLock key lit the light (I don't know if
> > that's relevant on sparc arch).
> 
> This is strange. Was the machine visible on the network (ie. could you ping
> to it)? Were interrupts going? What was the machine doing
> ({shift,alt,ctrl}+scroll lock)? Was Stop+A working? (go should work in these
> kernels already).

In hindsight, I suspect it had booted OK, but events happened as
follows: I powered down and up and it hung after printing the
    CMD646: MDMA enable
message. At this point the machine really did hang: Ctrl-ScrollLock
showed just three processes running: kernel tasks. I then power
cycled it again and tried again. This time it got past that message
and did the same as the previous time: sitting there doing nothing
after the "eth0: Link is up" line. Hitting Ctrl-ScrollLock from time
to time showed fsck running and then other things started. It ended
up with the usual kflushd, atd, crond stuff running and a single
getty. I could indeed ping it across the network and telnet to it to
get a login prompt. With only a root account, that was no good though.
Since the single getty clearly wasn't running on tty1 I went and got a
dumb terminal and plugged that in and, sure enough, could log in as
root there. Success! /etc/inittab has only one getty entry for console
and no others which semi-explains it. What's left to explain is why it
made /dev/console as a serial console. Now I *had* been using a
serial console (ttyb) for Solaris but using it to boot Linux came up
with the error
    Can't init console on serial line
(That's from the scrawl in my notebook so may be wrong). So then I did
    setenv output-device screen
    setenv input-device keyboard
    reset
from the boot prom and all my attempts at installing Linux were then
using the screen/keyboard. Perhaps something somewhere still "knows"
(incorrectly) that I want a serial console?

The upshot is that I now have a running, working Linux on the Ultra5
which should make it easier to debug some of the problems I've been
having. I'll try out the floppy drive and put back in the sunswift
hme/scsi card which had network problems during an attempted install.

--Malcolm

-- 
Malcolm Beattie <mbeattie@sable.ox.ac.uk>
Unix Systems Programmer
Oxford University Computing Services

Re: Mixed news: new UP 1.0.9 on Ultra5

[Hine,C]

> Aha, I forgot to mention that SBUS fdtwo is not in healthy 
> state in the kernel yet, what works perfectly is PCI fdthree
> (both fd0 and fd1 whichever it happens), plus maybe sun4m fdtwo, but 
> I'm not sure about it. In fact, I'd be graceful if someone with a sun4m
> fdtwo could acknowledge if it works in recent kernels (2.1.120+) or not.
> If yes, then we have some Ultra/SBUS floppy related bug, otherwise it is
> a problem common to fdtwo.

OK, if you want anyone to test any changes, to get it working, just ask.

> > tty_io.c: process 1 (init) used obsolete /dev/cua1 - update 
> > software to use /dev/ttyS1
> 
> Ok, this is my bug (well, laziness on my part) in that I have 
> not fixed the setserial package to omit overwriting /dev/console
> device, so that serial installs do the above. I'll do that in a
> couple of minutes.

I've just grabbed the latest changes, and it all works. :)

I noted a few very minor errors though:
Xconfigurator tries to run, even though I have not installed
any X stuff.
When booting for the first time the root partition was not
cleanly unmounted.
I still cannot make a boot disk, but that is probably the floppy drive
problem.

Now this machine is installed I was going to start using it, but
if you want me to test installing ultrapenguin again, I'll wait
before doing any work on it, as its the only UltraSPARC machine
we've got here.

Thanks for all the work you've done.

Cheers,
Chris Hine
---
Internet/Intranet Development
Oce (UK) Ltd.
Email: cph@oce.co.uk

Re: Mixed news: new UP 1.0.9 on Ultra5

[Jakub Jelinek]

> 
> > Aha, I forgot to mention that SBUS fdtwo is not in healthy 
> > state in the kernel yet, what works perfectly is PCI fdthree
> > (both fd0 and fd1 whichever it happens), plus maybe sun4m fdtwo, but 
> > I'm not sure about it. In fact, I'd be graceful if someone with a sun4m
> > fdtwo could acknowledge if it works in recent kernels (2.1.120+) or not.
> > If yes, then we have some Ultra/SBUS floppy related bug, otherwise it is
> > a problem common to fdtwo.
> 
> OK, if you want anyone to test any changes, to get it working, just ask.

I have the floppy drive here myself (well, to be honest, now for a couple of
days I've exchanged together with my Ultra1/FFB for another Ultra1/cg6), but
I haven't yet had time to dig into that.

> 
> > > tty_io.c: process 1 (init) used obsolete /dev/cua1 - update 
> > > software to use /dev/ttyS1
> > 
> > Ok, this is my bug (well, laziness on my part) in that I have 
> > not fixed the setserial package to omit overwriting /dev/console
> > device, so that serial installs do the above. I'll do that in a
> > couple of minutes.
> 
> I've just grabbed the latest changes, and it all works. :)
> 
> I noted a few very minor errors though:
> Xconfigurator tries to run, even though I have not installed
> any X stuff.

But you have installed Xconfigurator, that's why it is run.
You don't have to, and in fact it is not in the Base set, by default only in
X sets.

> When booting for the first time the root partition was not
> cleanly unmounted.

Are you sure you were not doing something on tty2? I get the same result
e.g. when I forgot some mount hanging on tty2...

> I still cannot make a boot disk, but that is probably the floppy drive
> problem.

Yep.
> 
> Now this machine is installed I was going to start using it, but
> if you want me to test installing ultrapenguin again, I'll wait
> before doing any work on it, as its the only UltraSPARC machine
> we've got here.

Go ahead and use it :)

Cheers,
    Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.1.126 on a sparc64 machine (498.80 BogoMips).
___________________________________________________________________