Re: installing Debian on Cobalt Qube 2
Martin Michlmayr schrieb:
* Markus Schröder <m.schroeder@automaten-produkte-service.de> [2009-09-07 17:50]:
I tried to install but got stuck after the Qube got the bootloader
from the NFS/DHCP-Server. Found it out when i changed one of the
characters from the messages of the bootloader and message was
displayed on the Qube, and there is no traffic on my network anyway
after the bootloader is pulled from the Qube.
Is there a way to identify the RAM inside 'cause i believe its only
16MB and i don't have a serial connector on either the server or my
laptop!?
IIRC CoLo (the 2nd stage boot loader that's loaded via the network)
will display the amount of RAM when it starts.
I finally bought a serial cable to see whats happening on the Qube², and
128MB Ram when i saw it had only 16MB installed. But i still have the
probs it won't load the bootloader at all.
In the 1st, i connected the Qube², the NFS/DHCP-Server, my regular
desktop machine and the Router/Gateway over a 3com Hub. There was a
serial connection between my regular desktop running HyperTerm and the
Qube, too. IP-Address was assigned to the Qube as i could ping it from
the NFS/DHCP-Server, but it only went to "Installing SSH-Server", not
further. I tried several times using both NFS and TFT boot option, and
one time it got to the "Booting...$IP-Address" message.
> Cobalt Microserver Diagnostics - 'We serve it, you surf it'
Built Tue Dec 15 04:11:42 PST 1998
1.LCD Test................................PASS
2.Controller Test.........................PASS
5.Bank 0:.................................64M
6.Bank 1:.................................64M
7.Bank 2:.................................16M
8.Bank 3:.................................16M
9.Serial Test.............................PASS
10.PCI Expansion Slot....................**EMPTY**
12.IDE Test................................PASS
13.Ethernet Test...........................PASS
16.RTC Test................................PASS
Decompressing done
Decompressing \ done.
[ "CoLo" v1.22 ]
stage2: 89fa0000-8a000000
cpu: clock 250.000MHz
pci: unit type <Qube2>
tulip: #0 device 21143
tulip: #1 device 21143
tulip: {00:10:e0:00:26:e9}
ide: resetting
boot: running boot menu
1> lcd 'Booting...'
1> net
tulip: link up (100Mbps)
net: interface up
dhcp: DISCOVER
dhcp: OFFER 192.168.178.5 <-- 192.168.178.40
dhcp: REQUEST
dhcp: ACK
net: interface down
tulip: link up (100Mbps)
net: interface up
address 192.168.178.5
netmask 255.255.255.0
gateway 192.168.178.1
name server 192.168.178.1
1> lcd 'Booting...' {ip-address}
1> tftp {dhcp-next-server} {dhcp-boot-file}
no response
script aborted <1>
another time i tried i got this message i copied from the terminal on my
desktop machine:
Cobalt Microserver Diagnostics - 'We serve it, you surf it'
Built Tue Dec 15 04:11:42 PST 1998
1.LCD Test................................PASS
2.Controller Test.........................PASS
5.Bank 0:.................................64M
6.Bank 1:.................................64M
7.Bank 2:.................................16M
8.Bank 3:.................................16M
9.Serial Test.............................PASS
10.PCI Expansion Slot....................**EMPTY**
12.IDE Test................................PASS
13.Ethernet Test...........................PASS
16.RTC Test................................PASS
Decompressing done
Decompressing \ done.
[ "CoLo" v1.22 ]
stage2: 89fa0000-8a000000
cpu: clock 250.000MHz
pci: unit type <Qube2>
tulip: #0 device 21143
tulip: #1 device 21143
tulip: {00:10:e0:00:26:e9}
ide: resetting
boot: running boot menu
1> lcd 'Booting...'
1> mount
ide: {ST314220A}
ide: LBA 27853148
ide: supports PIO mode 4
ide: mode 4 timing
ide: partition 1
ext2: revision 1
ext2: has journal (ext3)
1> lcd 'Booting...' /dev/{mounted-volume}
1> -load /boot/default.colo
file not found
(unknown error #1)
1> -script
no script loaded
(unknown error #1)
1> load /boot/vmlinux.gz
file not found
script aborted <1>
I wonder there was no IP-address assigned at all this time, so this
would be the cause why booting failed.
After i spent a complete evening on that prob, i connected the Qube² to
the NFS/DHCP-Server using a crossover cable and the serial to my desktop
running HyperTerm, but doesn't work at all. Started the Qube a few times
with tcpdump running on the server, but i haven't any clue at all what's
going wrong there...
cu...
...Markus...
Reply to: