[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Cobalt Qube 2





On 7 March 2012 19:30, Martin Michlmayr <tbm@cyrius.com> wrote:
> I see two problems:
>
> * Andy Barnes <andy@barnes.net> [2012-03-07 15:54]:
>> host cobalt {
>>       hardware ethernet 00:10:e0:00:e1:3d;
>>
>> host qube {
>>       hardware ethernet 00:10:e0:00:e1:3d;
>
> You're using the same MAC.  One of these entries should be for
> 00:10:e0:00:bf:04

I don't know how but that was just a typo from my copy/paste of the values. It is set correctly in dhcpd.conf, when I change it to the wrong mac address this is the output I get on the Qube:

Cobalt Microserver Diagnostics - 'We serve it, you surf it'
Built Tue May 25 15:58:41 PDT 1999

1.LCD Test................................PASS
2.Controller Test.........................PASS
5.Bank 0:.................................64M
6.Bank 1:.................................64M
7.Bank 2:.................................16M
8.Bank 3:.................................0M
9.Serial Test.............................PASS
10.PCI Expansion Slot....................**EMPTY**
12.IDE Test................................PASS
13.Ethernet Test...........................PASS
16.RTC Test................................PASS
BOOTLOADER ramcode: selected partition /dev/hda1
Decompressing done
Executing bootloader kernel...
Decompressing - done.

[ "CoLo" v1.10 ]
stage2: 88fb0000-89000000
pci: unit type <Qube2>
tulip: {00:10:e0:00:bf:04}
ide: resetting
boot: running boot menu
> lcd 'Booting...'
> net
net: interface up
dhcp: DISCOVER
dhcp: OFFER 192.168.1.12 <-- 192.168.1.0
dhcp: REQUEST
arp: sent request for 192.168.1.0
arp: resolved 192.168.1.0
dhcp: ACK
net: interface down
net: interface up
 address     192.168.1.12
 netmask     255.255.255.0
 name server 192.168.1.0
> lcd 'Booting...' {ip-address}
> nfs {dhcp-next-server} {dhcp-root-path} {dhcp-boot-file}
no such variable
script aborted
> arp: request from 192.168.1.0
udp: no matching socket 192.168.1.10:17500 --> 192.168.1.255:17500

When I change it back it goes back to correctly picking up the 192.168.1.78 address.

>> 16.RTC Test................................PASS
>> BOOTLOADER ramcode: selected partition /dev/hda1
>> Decompressing done
>> Executing bootloader kernel...
>> Decompressing - done.
>>
>> [ "CoLo" v1.10 ]
>
> Where does CoLo 1.10 come from?  The output above suggests that CoLo
> is loaded from the hard drive.  However, if you follow the manual and
> press the left and right key when booting it should load CoLo from
> your NFS server.

I don't know. It's one of the things that is bugging me, I thought the CoLo was loaded off the NFS share but it looks like it's using a copy on the local disk. I think this is deffinately the case as if I pull the disk out and put a 40gb blank ide drive in there I get CoLo related errors.

> Make sure it says "Net booting" on the LCD.  If it says "Starting up",
> it's loading CoLo from disk.

I have been using the LCD menu to net boot. When I power the Qube on after a second or so it goes to a menu with the following options (I have been using the Network (NFS) option):

BOOT SELECTION
Disk (hda)
Network (NFS)
Network (TFTP)
Boot shell
Network shell

When I press and hold the < > buttons next to the panel on power on, the panel changes to say Net booting but this is the output I get:


Cobalt Microserver Diagnostics - 'We serve it, you surf it'
Built Tue May 25 15:58:41 PDT 1999

1.LCD Test................................PASS
2.Controller Test.........................PASS
5.Bank 0:.................................64M
6.Bank 1:.................................64M
7.Bank 2:.................................16M
8.Bank 3:.................................0M
9.Serial Test.............................PASS
10.PCI Expansion Slot....................**EMPTY**
12.IDE Test................................PASS
13.Ethernet Test...........................PASS
16.RTC Test................................PASS
Decompressing done
Executing bootloader kernel...
Jump_to_Real_Kernel: disk error, trying BFD again
Decompressing - done
Executing bootloader kernel...

it never seems to get any further. This happens on both the Qube's.

Andy
Reply to: