[DragonFlyBSD - Bug #1407] (Resolved) disklabel64 boot problem

[Thomas Nikolajsen via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #1407 has been updated by Thomas Nikolajsen.

Status changed from New to Resolved
Assignee deleted (0)

(don't remember why I kept this one open)
----------------------------------------
Bug #1407: disklabel64 boot problem
http://bugs.dragonflybsd.org/issues/1407

Author: Thomas Nikolajsen
Status: Resolved
Priority: Normal
Assignee: 
Category: 
Target version: 


Booting DragonFly from disklabel64 slice has problems:
 - using HAMMER it almost works: one module can't be read
Reading /modules/acpi.ko fails; after booting (host can run without ACPI)
(i.e. by kernel) acpi.ko can be read and contents is correct.
(files on test HAMMER system are just cpdup'ed from a working system;
cmp verified acpi.ko is readable and has same contents)

Also doing ls command in loader on HAMMER file system can crash loader.
It seems like libstand/hammerread has an issue.

 - using UFS it doesn't work: I just see a spinning bar
It doesn't show any text, like BTX..

I had the impression that disklabel64 booting should be working
(since commits below); is this correct?

http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/d64b2e330d33214f962ba88
400ebbf8d11c18ef4
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/6080181b861dd0889598b54
645d4512a48800d21

Is zeroing slice start before making bootable disklabel still needed?
If yes: is it enough to zero 16KB, like disklabel32.

I was going to update disklabel64.8 to include boot info again;
but will hold it back until this issue is resolved.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account