From: Matthias Bethke <matthias@towiski.de>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] Qube2 can't load CoLo
Date: Thu, 17 May 2007 13:04:06 +0200 [thread overview]
Message-ID: <20070517110405.GB12611@huxley.cablesurf.de> (raw)
In-Reply-To: <464BF8E0.9000105@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2835 bytes --]
Hi Kumba,
on Thursday, 2007-05-17 at 02:40:32, you wrote:
> Even though I've not messed with my RaQ2 in ages, that is indeed an
> odd error from the old cobalt ROM. What kind of hard drive do you
> have?, maybe some bunk data is stored in the MBR that's throwing the
> bootloader off? IMHO, the old bootloader/ROM is a flaky, hunk of
> garbage anyways. You can always try flashing colo directly to the ROM
> chip. Just keep it on an UPS for safety, and colo itself should be
> more than stable enough to handle that.
Thanks for the encouragement---I had been too chicken to try it yet as
the manual said to make sure the chainloading version works first.
Actually I even have a flasher but I'd have to install Windows for it in
case it screwed my flash chip, so... :)
Anyway, I tried and it worked flawlessley in a matter of seconds. Kudos
to Colonel Panic! It's still dropping me to the boot menu to load the
kernel by hand but I think that has got to do with my default.colo file,
have to check it once my new kernel compile has finished.
> Your udev errors, what do they entail? I've been keeping an eye out for
> people running 2.6.17 kernels and having problems with userland. I'm
> curious to know what glibc revision you have merged. I've got a nagging
> suspicion we may be about to hit into an upgrade path issue that i ran into
> on my Octane, but have yet to ascertain whether it was specific to me or
> not.
The error message says:
| * Mounting /dev for udev ...[ oops ]
|
|
| * The "mount" command failed with error:
|
| wrong fs type, bad option, bad superblock on udev,
| missing codepage or other error
| In some cases useful info is found in syslog - try
| dmesg | tail or so
|
| * Since this is a critical task, startup cannot continue.
My glibc is 2.3.6-r4, it's all still the original 2007.0 install image
from redhatter. But I'm quite sure that's not the problem, this looks
pretty much like a problem I had on a HPPA box a while ago. I had
disabled support for hotplug devices in the kernel since it's a server
and I thought I didn't need it. Afterwards, udevd wouldn't start any
more, complaining about some missing netlink functionality, I don't
remember exactly what it was.
On the Qube I should have dumped the config from the netbooted
installation kernel but went with "make cobal_defconfig" first, which I
found later has no hotplug support either. So I'm pretty confident it
will work once I have the new kernel compiled (it's going through the
whole 2h procedure right now because I forgot to set the clock last time
8-]). I'll post my result when I have any.
cheers!
Matthias
--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-17 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 8:56 [gentoo-mips] Qube2 can't load CoLo Matthias Bethke
2007-05-17 6:40 ` Kumba
2007-05-17 11:04 ` Matthias Bethke [this message]
2007-05-17 11:47 ` Andrew Gaffney
2007-06-04 22:24 ` Matthias Bethke
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=20070517110405.GB12611@huxley.cablesurf.de \
--to=matthias@towiski.de \
--cc=gentoo-mips@lists.gentoo.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