New installation from disc - "can't load kernel"
-
I am here searching for an answer with an OPNsense download.
Similar circumstances, I get some cd0: messages, but a common bug appears to be in the bootstrap loader -
either you media is corrupt, broken hardware or your hardware is not compatible with freebsd
-
@debesty What application did you burn these with in Windows?
-
@stephenw10 Sorry for not replying earlier. As I mentioned up in the thread, for the 1st burn I used the built-in Windows 10 feature, and for the 2nd I used ImgBurn on a different Windows 7 machine. Both discs failed on my repurposed Dell in the same way on bootup (as apparently it did for @Impatient ). I have successfully created bootable DVDs for Linux and FreeBSD from ISO files on the Windows 7 machine in the past.
I went out and bought a USB drive, downloaded the USB image and transferred it. It worked perfectly on the Dell.
No idea if you want to investigate the ISO image further, but as far as I'm concerned, it's a moot point.
-
Thanks for following up. It's interesting, I asked around about this and no-one had seen it. But also almost no-one had tested a physical burned disc in recent memory.
I will certainly try to confirm this if I can.Steve
-
@stephenw10
Just a follow up, The only way I could succeed was to install Window's 10 clean.
Remove drive delete all partition's, wipe, Then install Window's.After bootup, disable all window's defender setting's and reboot then burn the disk.
Also I had to enter the bios and allow booting from cd-rom.
Before Window's install this was enabled and how it was disabled I don't know. -
@impatient said in New installation from disc - "can't load kernel":
@stephenw10
Just a follow up, The only way I could succeed was to install Window's 10 clean.
Remove drive delete all partition's, wipe, Then install Window's.After bootup, disable all window's defender setting's and reboot then burn the disk.
Also I had to enter the bios and allow booting from cd-rom.
Before Window's install this was enabled and how it was disabled I don't know.Let me understand this.
You need to take down an re install an entire Windows 10 PC to make an "USB boottable disk" with the pfSense installer on it ?No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
No, to burn an ISO to disk from Win10 that was then bootable. Though I suspect there are too many variables there to know for sure.
-
@gertjan
Not a USB Drive but DVD.I am fairly sure it has something to do with window's security setting's even with a new install.
Also I had to enter the bios and allow booting from cd-rom.
(Before Window's install this was enabled and how it was disabled I don't know.)
I am still trying to figure this out, How and Why would a Window's install disable a bios setting?This is with the latest win10 version, However win10 version 1803 does Not change bios
setting and burn's dvd just fine. -
@impatient
I don't think my issue is the same as yours. As I mentioned before, before I went the route of going with a USB boot device, I put an old FreeNAS disk (which uses an identical bootloader process as pfSense) into the same Dell box, and the Dell booted it up into the FreeNAS installer no problem. I made no changes to the BIOS settings before or after. The problem was clearly either the ISO image, or a coincidence that two completely different applications, on two different versions of Windows, on two different machines, on two different brands of optical media, both went about burning that image with exactly the same failure.It would be interesting to experiment some more on what's going on, but the Dell is now happily acting as the gateway to my home network, and the wife and kid would be upset if I brought down their Internet in order to play around with it. :-) Sorry!
-
@debesty i had the same problem with AMD64 version
I used an i386 version exactly 2.2.6 and the installation went fine
then update to 2.3.5 in the http admin console
I hope this will help -
If you care about security (and I assume since you're here you do
) then you really shouldn't be running anything that old.Steve
-
@impatient said in New installation from disc - "can't load kernel":
I am still trying to figure this out, How and Why would a Window's install disable a bios setting?
As far as I know, Windows (Microsoft) doesn't force you to update your BIOS : I never saw a BIOS update to be part of Wndows Update scheme.
But ... If you were notified by the OEM software that came with your PC, and it updates your BIOS, then this BIOS installer could find out that it's running '10' and thus preset some safety features for you, like booting from nothing else except the EUFI based hard drive.
Not accepting DVD's CD's or USB flash drives does make your system more safe.It's something like that, or you're not the only one adminning your system ^^
No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
Mmm, that seems extremely unlikely!
-
@stephenw10 :
Well, that are the little green ones. -
@gertjan
Who said anything about updating bios or oem software?A 10-pass wiped disk has no oem software or anything else on it worth mentioning.
Maybe something was lost in translation or I do not know how to make myself clear but newest window's-10 iso Did some strange thing's.
Anyway I am glad the OP resolved his issue
-
I have the same issue on Athlon CPU 2 cores, 2GB Ram with ISO CD 2.4.5
Is ok on 2.4.4-p3 though !!
-
@bambos @stephenw10 More evidence that there might be something wrong specifically with the ISO image of 2.4.5-p1. As has been suggested earlier in this thread, it might be that few people are using this method of installation any longer (and I myself gave up and used a USB drive in the end), but if this is a reproducible issue, then it might be worth investigating?
-
I had a GEDODE board that refused to boot from USB , and made a CD. Now it "booted" , but i think i got the same error as above.
I don't have access to my notes right now , but i think the solution was to specify some kind of "Wait for disk ready" delay or retrys , in the CLI.
And then boot.
/Bingo
