Re: Can't load kernel, trying to install on a Dell R900.



Nicky Bulthuis wrote:
Mel wrote:
On Thursday 28 February 2008 12:51:10 Nicky Bulthuis wrote:

I'm having 'a lot' of troubles installing FreeBSD on a new Dell R900
from CD. Somehow it just doesn't seem to be able to load the kernel
from
the CD.

The machine is turned on with the CD is inserted.
It shows the message of the BTX Loader and then it stops with an error
message:

can't load 'kernel'

At first i figured my CD was broken, so i used a different image. Still
no dice, same error message. I've tried 6.2 (amd64), 6.3 (amd64) and
7.0
(amd64), sadly none of them work.

I've disabled the internal CDrom drive and used an external USB CDrom
drive. I figured, perhaps the internal cdrom drive is incompatible with
FreeBSD. Sadly that also didn't work.

Output from lsdev:

cd devices:
cd0: Device 0x0
disk devices:
disk0: Bios drive C:


What does ls / give? And ls -l /boot/kernel/kernel?

Been a while since I loaded a kernel manually, but I think:
boot -v cd0:/boot/kernel/kernel
should do the trick.

Does any of that give more hints to what might be the problem?

Well, i've made some progress with your suggestions.

First things first, i had already updated the BIOS from version 1.1.0
to 1.1.3, the latest i could find on the Dell website.

"ls /" and "ls -l /boot/kernel/kernel" both give me 'bad path'.
"boot -v cd0:/boot/kernel/kernel" gives two messages, "can't boot
kernel" followed by "no bootable kernel"

Using 'ls cd0:/' gives me the cdrom file listing, so that works. I can
browse the cdrom directory structure.

I've done 'load cd0:/boot/kernel/kernel', which actually loads the
kernel.
I get the 'text[memadres] data[memaddress] syms[memaddress]' messages,
and 'lsmod' shows me a loaded kernel.

however, running 'boot -v' doesn't seem to work. It shows me the
progressbar "|-/\", make a full circle, but stops right after.
you sure there is not option in bios about supported systems or something?
ive seen exactly the same problem with OpenBSD on HP boxes and you have
to disable one option in bios (can find out how is it called but its HP
not DELL) and then it works just fine

if you are 100% sure it is nothing to do with bios then sorry for
bothering you with my ideas.


--
bEsT rEgArDs | "Confidence is what you have before you
tomasz dereszynski | understand the problem." -- Woody Allen
|
Spes confisa Deo | "In theory, theory and practice are much
numquam confusa recedit | the same. In practice they are very
| different." -- Albert Einstein


_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: NForce2 pseudoscience stability testing (2.6.0-test11)
    ... > I upgraded the BIOS about a week ago to 1007. ... I was running the SMP ... > It is clear that the UP kernel is considerable more stable than the SMP ... > machine being under constant 100% CPU load and fairly active IO load. ...
    (Linux-Kernel)
  • Re: [Linux-fbdev-devel] Generic VESA framebuffer driver and Video card BOOT?
    ... >> kernel image or that the image is corrupt or that hardware diagnostics failed. ... Well being able to use this BIOS emulator logic to bring up the primary ... the same as Open Firmware really). ... Actually there is nothing wrong with the x86 BIOS from the perspective of ...
    (Linux-Kernel)
  • Re: Grub
    ... But beware of what the bios exactly is!! ... It asks the disk ... Grub, for example, or Windows bootloader, or whatever... ... there is no kernel to provide access to them. ...
    (Fedora)
  • Re: GRUB module query
    ... config screen for various RAID options - I turn them off and use kernel ... The whole interaction between BIOS, ... case a secondary "on card" bios, and then GRUB, and then Kernel. ... So on boot the BIOS conspire to load the ...
    (Ubuntu)
  • Re: Big-disk woes
    ... >> In the olden days the system still needed the bios to load any boot loader ... >> to Linux (which would talk to the hardware directly and not need the BIOS ... but I seem to remember days where the kernel would be in / and not ...
    (comp.os.linux.setup)