1 |
Matthias Bethke wrote: |
2 |
> It's been quiet on this list for a while, eh? Here's a question for Qube |
3 |
> owners: |
4 |
> I've been trying to get Gentoo running on my Qube 2, and while |
5 |
> things seem to work fine with minor glitches so far, I can't get the |
6 |
> CoLo chainloading to work. I've netbooted the box, CoLo loads fine from |
7 |
> NFS, loads my kernel, I've done all the installation of the base system, |
8 |
> and now I'm trying to get the Qube to boot on its own. What does work is |
9 |
> to netboot again so the CoLo image gets pulled from NFS, and then have |
10 |
> CoLo load and boot my kernel from disk by hand (it runs into problems |
11 |
> trying to start udev but I think I can get this fixed later, with |
12 |
> init=/bin/bash it's fine so far). It doesn't however want to load CoLo |
13 |
> from the boot partition: |
14 |
> | Cobalt Microserver Diagnostics - 'We serve it, you surf it' |
15 |
> | Built Tue May 25 15:58:41 PDT 1999 |
16 |
> | |
17 |
|
18 |
[snip] |
19 |
|
20 |
> | BOOTLOADER ramcode: selected partition /dev/hda1 |
21 |
> | Decompressing done |
22 |
> | Executing bootloader kernel... |
23 |
> | Jump_to_Real_Kernel: disk error, trying BFD again |
24 |
> | BOOTLOADER ramcode: selected partition /dev/hdc1 |
25 |
> | Decompressing - done |
26 |
> | Executing bootloader kernel... |
27 |
> | Jump_to_Real_Kernel: disk error, trying BFD again |
28 |
> | get_root_dev: nr_boot_failures 0x00000002 exceeds maxtries 0x00000002 for boot_index 0x00000000 |
29 |
> | |
30 |
> | |
31 |
> | *** halting *** |
32 |
|
33 |
[snip] |
34 |
|
35 |
> |
36 |
> It is an ext2r0 partition and vmlinux.gz is the zipped colo-chain.elf. |
37 |
> I'm not sure about who writes what message in that console dump but it |
38 |
> seems to me that CoLo isn't even being loaded. Otherwise I should get a |
39 |
> menu on the console in case it couldn't find the kernel or something, |
40 |
> right? |
41 |
|
42 |
Even though I've not messed with my RaQ2 in ages, that is indeed an odd error |
43 |
from the old cobalt ROM. What kind of hard drive do you have?, maybe some bunk |
44 |
data is stored in the MBR that's throwing the bootloader off? IMHO, the old |
45 |
bootloader/ROM is a flaky, hunk of garbage anyways. You can always try flashing |
46 |
colo directly to the ROM chip. Just keep it on an UPS for safety, and colo |
47 |
itself should be more than stable enough to handle that. |
48 |
|
49 |
Your udev errors, what do they entail? I've been keeping an eye out for people |
50 |
running 2.6.17 kernels and having problems with userland. I'm curious to know |
51 |
what glibc revision you have merged. I've got a nagging suspicion we may be |
52 |
about to hit into an upgrade path issue that i ran into on my Octane, but have |
53 |
yet to ascertain whether it was specific to me or not. |
54 |
|
55 |
|
56 |
--Kumba |
57 |
|
58 |
-- |
59 |
Gentoo/MIPS Team Lead |
60 |
|
61 |
"Such is oft the course of deeds that move the wheels of the world: small hands |
62 |
do them because they must, while the eyes of the great are elsewhere." --Elrond |
63 |
-- |
64 |
gentoo-mips@g.o mailing list |