On 9/20/17 12:51 PM, Apostolos Syropoulos via illumos-discuss wrote:
Hello,
I have noticed that even people who use Windows have problems with his
processor:
https://forum.giga-byte.co.uk/index.php?topic=18331.0
https://tech.slashdot.org/story/17/03/21/1934217/amd-confirms-its-issuing-a-fix-to-stop-new-ryzen-processors-from-crashing-desktops
Maybe the problem is the processor.
Those pages refer to a very early issue from March that I think was
fixed some time ago in BIOS. Almost certainly not this issue.
Instead, Gary Mills posted the same "no rootfs module" issue back on
Sept. 9th (see below). And there's also a SmartOS thread under
https://www.mail-archive.com/[email protected]/msg04625.html
which probably hit the same case.
Toomas Soome helped to debug Gary's case to a memory layout problem
early in boot filed as https://www.illumos.org/issues/8651.
I think you'll need a fix for 8651 and then try again.
Hugh.
-------- Forwarded Message --------
Subject: Re: [developer] No rootfs module provided
Date: Sun, 10 Sep 2017 09:18:25 +0300
From: Toomas Soome <>
To: illumos-developer <[email protected]>
> On 9. sept 2017, at 23:52, Gary Mills <> wrote:
>
> On Sat, Sep 09, 2017 at 05:38:49PM +0300, Toomas Soome wrote:
>> On 9. sept 2017, at 17:32, Gary Mills <> wrote:
>>
>> I just put together a system with a ASUS B350M-A system board, an AMD
>> Ryzen 3 1200 CPU and an ASUS HD 6450 Silent video card.
>> When I attempt to boot the OI-hipster-gui-20170502 DVD on this system,
>> I get the boot menu normally, but it's followed by these three lines:
>> Loading unix...
>> Loading /platform/186pc/amd64/boot_archive...
>> Loading /platform/186pc/amd64/boot_archive.hash...
>> Booting...
>> No rootfs module provided, aborting
>>
>> no, for some reason it does not have boot_archive loaded (despite the
>> message). You can try to load it manually as:
>> unload (to make sure we do not have anything loaded)
>> load /platform/i86pc/kernel/amd64/unix
>> load -t rootfs /platform/i86pc/amd64/boot_archive
>> and verify with lsmod command. then boot -B
>> prom_debug=true,kbm_debug=true
>
> I only got as far as the second load command before I got an error:
>
> ok load /platform/i86pc/kernel/amd64/unix
> Loading /platform/i86pc/kernel/amd64/unix...
> ok load -t rootfs /platform/i86pc/amd64/boot_archive
> Loading /platform/i86pc/amd64/boot_archive...
> error reading '/platform/i86pc/amd64/boot_archive': file too large
> ok lsmod
> 0xbffe70: /platform/i86pc/kernel/amd64/unix (aout multiboot
kernel, 0x1e4268)
Ok, so what is happening is, we have kernel loaded at 0xc00000 - sizeof
(elf header), and boot_archive is supposed to land right after it, but
apparently there is not enough space.
The loader heap is allocated in high memory and the module read code is
checking if we are going to hit the heap or not. So the question is,
where is the heap and why it is getting allocated there.
on ok prompt, the command smap will give the memory map (type 1 is
usable memory), biosmem will tell information about memory detection,
and the command heap will tell us heap base (see
usr/src/boot/sys/boot/i386/libi386/biosmem.c)
Also note the boot loader is running in 32-bit protected mode, so we are
limited to 4GB space.
rgds,
toomas
------------------------------------------
illumos-discuss
Archives:
https://illumos.topicbox.com/groups/discuss/discussions/Tb342e2cdbf33d692-M6f24c47838d91d0faad4ef96
Powered by Topicbox: https://topicbox.com
