1 |
It's been quiet on this list for a while, eh? Here's a question for Qube |
2 |
owners: |
3 |
I've been trying to get Gentoo running on my Qube 2, and while |
4 |
things seem to work fine with minor glitches so far, I can't get the |
5 |
CoLo chainloading to work. I've netbooted the box, CoLo loads fine from |
6 |
NFS, loads my kernel, I've done all the installation of the base system, |
7 |
and now I'm trying to get the Qube to boot on its own. What does work is |
8 |
to netboot again so the CoLo image gets pulled from NFS, and then have |
9 |
CoLo load and boot my kernel from disk by hand (it runs into problems |
10 |
trying to start udev but I think I can get this fixed later, with |
11 |
init=/bin/bash it's fine so far). It doesn't however want to load CoLo |
12 |
from the boot partition: |
13 |
| Cobalt Microserver Diagnostics - 'We serve it, you surf it' |
14 |
| Built Tue May 25 15:58:41 PDT 1999 |
15 |
| |
16 |
| 1.LCD Test................................PASS |
17 |
| 2.Controller Test.........................PASS |
18 |
| 5.Bank 0:.................................64M |
19 |
| 6.Bank 1:.................................64M |
20 |
| 7.Bank 2:.................................64M |
21 |
| 8.Bank 3:.................................64M |
22 |
| 9.Serial Test.............................PASS |
23 |
| 10.PCI Expansion Slot....................**Unknown Card** |
24 |
| 12.IDE Test................................PASS |
25 |
| 13.Ethernet Test...........................PASS |
26 |
| 16.RTC Test................................PASS |
27 |
| BOOTLOADER ramcode: selected partition /dev/hda1 |
28 |
| Decompressing done |
29 |
| Executing bootloader kernel... |
30 |
| Jump_to_Real_Kernel: disk error, trying BFD again |
31 |
| BOOTLOADER ramcode: selected partition /dev/hdc1 |
32 |
| Decompressing - done |
33 |
| Executing bootloader kernel... |
34 |
| Jump_to_Real_Kernel: disk error, trying BFD again |
35 |
| get_root_dev: nr_boot_failures 0x00000002 exceeds maxtries 0x00000002 for boot_index 0x00000000 |
36 |
| |
37 |
| |
38 |
| *** halting *** |
39 |
|
40 |
My hda1 looks like this: |
41 |
| (none) etc # mount /boot |
42 |
| (none) etc # ls -l /boot |
43 |
| total 1152 |
44 |
| -rw-r--r-- 1 root root 353 Jan 1 2000 default.colo |
45 |
| -rwxr-xr-x 1 root root 1098628 May 15 2007 kernel-2.6.17.14-mips.gz |
46 |
| drwx------ 2 root root 12288 Jan 1 2000 lost+found |
47 |
| -rw-r--r-- 1 root root 59614 Jan 1 01:07 vmlinux.gz |
48 |
| lrwxrwxrwx 1 root root 24 May 15 2007 vmlinux.gz.working -> kernel-2.6.17.14-mips.gz |
49 |
|
50 |
It is an ext2r0 partition and vmlinux.gz is the zipped colo-chain.elf. |
51 |
I'm not sure about who writes what message in that console dump but it |
52 |
seems to me that CoLo isn't even being loaded. Otherwise I should get a |
53 |
menu on the console in case it couldn't find the kernel or something, |
54 |
right? |
55 |
|
56 |
cheers! |
57 |
Matthias |
58 |
-- |
59 |
I prefer encrypted and signed messages. KeyID: FAC37665 |
60 |
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665 |