|
Hi there, I have recently installed Debian on my Cobalt Qube 2 and have
/ had a few teething troubles: When NETbooting: ‘udp: no matching socket’ The fix that worked for me was editing ‘/etc/services’ on my nfs server (debian sarge on i386) and adding: ‘mount’ 768/udp’ It would appear that the Qube’s nfs client tries to
connect to the NFS server via a random udp port < 1024, whereas the NFS server expects connections portmapped >
1024. With this setting in my ‘services’ file my Qube found the exported root directory quickly –
prior to this it just sat there repeating ‘udp: no matching socket’ whilst trying to
connect on various ports (520, 768,769,823 to name a few – 768 seemed most common). ymmv My present problem is with Colo 1.14. With the default 1.10
installed the Qube boots fine; I upgraded to the New 1.14 via martins .deb package and / or the tar.gz from
Peters page and the Qube refuses to boot. It displaysthis on the LCD: ! UNIT BOOT ! ! FAILED ! And shows this in the console (Trimmed off uneeded bits):
1> lcd 'Booting...' /dev/{mounted-volume} 1> -load /boot/default.colo ext2: {boot/default.colo} --> {./default.colo} 00000093 147t 1> -script 2> ext2: revision 0 2> load /vmlinux ext2: {vmlinux} --> {vmlinux-2.4.27-r5k-cobalt} 002a5bfe 2776062t 2> lcd "Booting Debian" 2> execute root=/dev/hda2 console=ttyS0,{console-speed} no such variable script aborted <2> 1> load /boot/vmlinux.gz ext2: {boot/vmlinux.gz} --> {./vmlinux.gz} 0000d191 53649t 1> execute elf32: 00080000 - 0009a7bf (80080000) (ffffffff.80000000) elf32: 80080000 (80080000) 108464t + 16t refusing to load "CoLo" chain loader script aborted <1> If I have this figured out correctly this is what is
happening: 1) The Cobalts
firmware searches for vmlinux_raq-2800.gz (Which is linked to vmlinux.gz) 2) Boots Peters
colo bootloader (which is colo-chain.elf renamed to vmlinux.gz) 3) Colo 1.14
comes up and runs ‘default.colo’ (Which is ok? as colo-1.10 boots
correctly from) 4) Colo tells
it to mount hda1 (/boot), load vmlinux (which is linked to vmlinux-2.4.27 etc
kernel) 5) Executes above
kernel whilst setting root partition and console info At this point it has failed. If I type ‘boot’
the boot menu comes up, if I then select hda on the panel or do nothing …..it boots ok. If instead I type: ‘load /vmlinux’, and then ‘execute
root=/dev/hda2 console=ttyS0,{console-speed}’ -----it boots ok Interestingly, either way (although booted via colo-1.14)
does not seem to start ‘paneld’ (If I install Martins deb package panel is started – and then I get these boot problems
again) neither can I start it manually. I have read through the INSTALL and README in the tar but
alas I’m still clueless as to what is going on. I only Installed 1.14 to get the Panel going properly so I can
reboot on the buttons instead of via console or ssh. Any ideas? Nick B What’s the etiquette on posting to these lists? I feel
I have posted too much info but yet it is all relevant stuff? Ran NetBSD 1.6.1 previously – Felt very ‘quick’ in operation but packages are
a bit out of date if they exist at all! |