Bug 107759 - Unable to load a kernel after clean install
Summary: Unable to load a kernel after clean install
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 6.1-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-10 16:40 UTC by Marno van der Molen
Modified: 2018-05-21 06:30 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marno van der Molen 2007-01-10 16:40:14 UTC
I tried installing FreeBSD about 4 times and each time it comes up with
this after the installation: I've followed the Installation Howto to the
letter and it appears that more people are experiencing this problem.

http://www.google.com/search?&q=unable+to+load+%27kernel%27+FreeBSD+6.1

Loading /boot/defaults/loader.conf
Unable to load a kernel !
/
can't load 'kernel'
Type '?' for a list of commands, 'help' for more detailed help.
OK

'Known workarounds' (Installing base and kernel seperately) didn't work
for me cause (probably) I'm not familiar enough with FreeBSD yet as this
is my first time using *BSD. I hope you can fix this problem cause I
would love to experiment with FreeBSD.

Fix: 

Apparantly installing 'base' and 'kernel' packages manually, though this
didn't work for me, but this might be due to my (lack of) experience with
FreeBSD.
How-To-Repeat: Install 6.1-RELEASE on a pc (i386, might also affect other architectures
although I can't verify this) and follow the installation manual on the
FreeBSD website.
Comment 1 nc 2007-01-19 22:51:16 UTC
Hi Marno, 

in order to work on the bug you submitted, can you please stay in touch 
with me via email. 

I installed a fresh 6.1 following the FreeBSD Handbook, and everything is OK 
for me. 

I usually install FreeBSD using the "expert mode", but this time I did that
with the express way, recommended in the handbook. 

Please mail me so that we can work on it. 

All the best, 

-- 
Nicolas CARTRON
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2007-04-24 10:51:33 UTC
State Changed
From-To: open->feedback

To submitter: were you able to overcome this problem? 


Comment 3 Mark Linimon freebsd_committer freebsd_triage 2007-04-24 10:51:33 UTC
Responsible Changed
From-To: freebsd-bugs->linimon
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2007-05-24 22:49:29 UTC
State Changed
From-To: feedback->closed

Feedback timeout (3 weeks).
Comment 5 Mark Linimon freebsd_committer freebsd_triage 2007-05-25 05:58:22 UTC
State Changed
From-To: closed->suspended

Actually, I had a response from the submitter, but only in personal 
email, so I wasn't able to see it in GNATS. 

This is apparently still a problem, but he is not using FreeBSD any 
more, so mark it as suspended for now.
Comment 6 Mark Linimon freebsd_committer freebsd_triage 2007-06-12 04:41:32 UTC
Responsible Changed
From-To: linimon->freebsd-bugs

Return this one to the pool.
Comment 7 Eitan Adler freebsd_committer freebsd_triage 2018-05-20 23:51:58 UTC
For bugs matching the following conditions:
- Status == In Progress
- Assignee == "bugs@FreeBSD.org"
- Last Modified Year <= 2017

Do
- Set Status to "Open"