From: "A. Eijkhoudt" <penguin@dhcp.net>
To: sparclinux@vger.kernel.org
Subject: Re: Desperate after upgrading OBP from 3.11 to 3.31
Date: Sun, 10 Jul 2005 13:07:53 +0000 [thread overview]
Message-ID: <42D11DA9.70804@dhcp.net> (raw)
In-Reply-To: <42D04BC9.9060105@dhcp.net>
Perhaps this rings a bell for someone:
I just noticed something odd that might be the actual cause of the
problem. I used to be able to netboot the SUN as well, just slam the
image into /tftpboot on the TFTP server and done. However, now I get
'Fast Instruction Access MMU Miss' no matter what image I try to boot
(most notably, the flash PROM updates from SUN). Perhaps there is
something set incorrectly in the OpenBoot I should look at?
Arnim.
Ben Collins wrote:
> Sorry. Didn't read far enough.
>
> Only things that come to my mind is that it is not booting the sectory
> from /dev/hda (maybe some incorrect partition). Or you installed the
> incorrect flash upgrade for your machine.
>
> Are you sure that 3.31 is the latest? I seem to remember there being a
> newer version than that for your type of Ultra. You can always try
> downgrading your prom back to the older version.
>
> On Sun, Jul 10, 2005 at 02:54:10AM +0200, A. Eijkhoudt wrote:
>
>>Hello,
>>
>>Right now:
>>
>>gateway boot # cat silo.conf
>>partition=1
>>root=/dev/hda2
>>timeout\x10
>>device=/dev/hda
>>image=/boot/2.6.12
>> label=linux
>>image=/boot/2.6.12-old
>> label=old
>>
>>So, the same as listed below in my original posting.
>>
>>TIA,
>>
>>Arnim.
>>
>>Ben Collins wrote:
>>
>>>What's your silo.conf look like?
>>>
>>>On Sun, Jul 10, 2005 at 02:25:35AM +0200, A. Eijkhoudt wrote:
>>>
>>>
>>>>Hi Ben,
>>>>
>>>>Thanks for responding. I have, but to no avail. I've tried running SILO
>>>>with multiple exotic combinations such as -f and -u to force it to
>>>>rewrite the bootblock for my Ultra. What I don't understand is how the
>>>>boot sector could get corrupted in the first place. I've also tried
>>>>putting the first partition back at 'Start = 0' now; no deal.
>>>>
>>>>Kind regards,
>>>>
>>>>Arnim
>>>>
>>>>Ben Collins wrote:
>>>>
>>>>
>>>>>After booting from CD, rerun the silo command. Sounds like your boot
>>>>>sector got corrupted, or you moved second.b on your filesystem without
>>>>>rerunning silo.
>>>>>
>>>>>On Sun, Jul 10, 2005 at 12:12:25AM +0200, A. Eijkhoudt wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Hello all,
>>>>>>
>>>>>>I've upgraded my OBP from 3.11 to 3.31 and now my SUN won't boot
>>>>>>anymore. Whatever I try at the 'ok' prompt has no effect, it keeps
>>>>>>saying 'The file just loaded does not appear to be executable'. I've
>>>>>>tried pretty much all versions of 'boot disk#:#' by now. The system in
>>>>>>question is a SUN Ultra10, 300MHz, 320MB RAM, 40GB HD Maxtor 6E040L.
>>>>>>
>>>>>>Partition layout:
>>>>>>
>>>>>><snip>
>>>>>>Disk /dev/ide/host0/bus0/target0/lun0/disc (Sun disk label): 16 heads,
>>>>>>63 sectors, 16383 cylinders
>>>>>>Units = cylinders of 1008 * 512 bytes
>>>>>>
>>>>>> Device Flag Start End
>>>>>>Blocks Id System
>>>>>>/dev/ide/host0/bus0/target0/lun0/part1 1 101
>>>>>>50400 83 Linux native
>>>>>>/dev/ide/host0/bus0/target0/lun0/part2 101 79144
>>>>>>39837672 83 Linux native
>>>>>>/dev/ide/host0/bus0/target0/lun0/part3 0 79656
>>>>>>40146624 5 Whole disk
>>>>>>/dev/ide/host0/bus0/target0/lun0/part4 u 79147 79655
>>>>>>256032 82 Linux swap
>>>>>>
>>>>>>Disk /dev/ide/host0/bus0/target0/lun0/part3 (Sun disk label): 16 heads,
>>>>>>63 sectors, 16383 cylinders
>>>>>>Units = cylinders of 1008 * 512 bytes
>>>>>>
>>>>>> Device Flag Start End
>>>>>>Blocks Id System
>>>>>>/dev/ide/host0/bus0/target0/lun0/part3p1 1 101
>>>>>>50400 83 Linux native
>>>>>>/dev/ide/host0/bus0/target0/lun0/part3p2 101 79144
>>>>>>39837672 83 Linux native
>>>>>>/dev/ide/host0/bus0/target0/lun0/part3p3 0 79656
>>>>>>40146624 5 Whole disk
>>>>>>/dev/ide/host0/bus0/target0/lun0/part3p4 u 79147 79655
>>>>>>256032 82 Linux swap
>>>>>></snip>
>>>>>>
>>>>>>As you can see, I can boot fine from CD...
>>>>>>
>>>>>>My SILO configuration:
>>>>>>
>>>>>><snip>
>>>>>>partition=1
>>>>>>root=/dev/hda2
>>>>>>timeout\x10
>>>>>>device=/dev/hda
>>>>>>image=/boot/2.6.12
>>>>>> label=linux
>>>>>>image=/boot/2.6.12-old
>>>>>> label=old
>>>>>></snip>
>>>>>>
>>>>>>This is all correct:
>>>>>>
>>>>>><snip>
>>>>>>livecd ~ # ls /boot/
>>>>>>2.6.12 System.map System.map-2.6.12-old fd.b
>>>>>>generic.b isofs.b old.b silo.conf ultra.b
>>>>>>2.6.12-old System.map-2.6.12 boot first.b ieee32.b
>>>>>>lost+found second.b silotftp.b
>>>>>></snip>
>>>>>>
>>>>>>Running SILO yields no errors... Can someone please help? There has to
>>>>>>be a simple way of fixing this, and I really don't believe I'm the only
>>>>>>one who has ever had this problem either. I've already spent 5(!) hours
>>>>>>reading every single search result I could find on Google and on the
>>>>>>Gentoo forums about this... My SUN is pretty much dead in the water
>>>>>>right now, as I don't feel like booting from a LiveCD just to get it
>>>>>>beyond the OpenBoot POST.
>>>>>>
>>>>>>Kind regards,
>>>>>>
>>>>>>Arnim Eijkhoudt
>>>>>>-
>>>>>>To unsubscribe from this list: send the line "unsubscribe sparclinux" in
>>>>>>the body of a message to majordomo@vger.kernel.org
>>>>>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>>
>>>>>
>
--
This message has been scanned for viruses and
dangerous HTML content by Valethosting.
Dit bericht is gecontroleerd op virussen en gevaarlijke
HTML door Valethosting's MailScanner.
prev parent reply other threads:[~2005-07-10 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 22:12 Desperate after upgrading OBP from 3.11 to 3.31 A. Eijkhoudt
2005-07-09 23:36 ` Ben Collins
2005-07-10 0:25 ` A. Eijkhoudt
2005-07-10 0:44 ` Ben Collins
2005-07-10 13:07 ` A. Eijkhoudt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42D11DA9.70804@dhcp.net \
--to=penguin@dhcp.net \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox