[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #34, bug #8 (project grub): ah, ok, i think i can see what is going on there -- the mzap itself has indeed number of chunks defined as 16bit int, meaning that single mzap entry can not have more; however, in case of large directory, there are probably more mzap entries in use

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #29, bug #8 (project grub): ok, from this debug list it appears its getting full listing without the errors, did you compare this full listing with real ls command output? was there anything missing? at least the zfs.ko, which was used in some previous examples was listed the

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #27, bug #8 (project grub): ok, thanks, the code is the same. so, can you post the command and debug output for listing files in that /boot/kernel please. the full directory, not just one file. to save space you can compress it, i understand you have quite many files there

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #25, bug #8 (project grub): just to clarify why i'm insisting to check with extendible dataset patch - since freebsd zfs does implement it, it *may* be the case the actual write did use this feature but did not update feature flag properly, in which case the updated read test

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #24, bug #8 (project grub): Were you able to apply the patch cleanly and can you mail me the zfs.c? If patch was successful, please post an full debug log from "grub-fstest ls /ROOT/default/@/boot/kernel" with command line you used. Also please try to paste the actual comma

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #21, bug #8 (project grub): just for future reference; your current grub-fstest ls command fails because you are running it as "ls /boot/kernel", but you need to run it as "ls /@/boot/kernel" - the boot is directory on dataset, and dataset root is specified by /@/. or if you

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #19, bug #8 (project grub): uh, which part were left out? i can post you git format-patch, so you should get it applied clean and we can be sure we are on the same code base:) ___ Reply to this item at:

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #16, bug #8 (project grub): so, do i understand correctly, you were able to apply the patch and it did not solve it? if so, can you post debug output from it? ___ Reply to this item at:

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #14, bug #8 (project grub): can you grab patch from https://lists.gnu.org/archive/html/grub-devel/2015-04/msg00055.html and test it against version from git? from this log, I would suspect the most plausible reason is missing support for extendible dataset feature, but this

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #10, bug #8 (project grub): can you please post zfs debug outputs; from grub itself you can set debug=zfs, with grub-fstest you can use -d zfs switch. also note that this log is pretty large, so, with grub itself you may wanna add serial output (if you have connection) to gra

[bug #42875] grub-core/disk/ata.c grub_ata_dumpinfo() has too small array.

URL: Summary: grub-core/disk/ata.c grub_ata_dumpinfo() has too small array. Project: GNU GRUB Submitted by: tsoome Submitted on: Wed Jul 30 00:20:46 2014 Category: Compilation