From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9front@9front.org
Subject: Re: [9front] Cannot install 9front
Date: Sat, 20 Aug 2022 16:06:17 -0400 [thread overview]
Message-ID: <d5e47f8d-57de-0798-9529-f23e84c3e258@fjrhome.net> (raw)
In-Reply-To: <CAJ4zFb+qaXL401qyQF87R8EKKxSsyxvOvW0TiOSd4MyiXEOeqA@mail.gmail.com>
For whatever it is worth, my Mac (macOS 12) doesn't like the images either.
Disk Utility won't even list the partitions on it.
If I run hdiutil imageinfo on it from the command line I get a few
details on the partitions but a few lines later it exits telling me that
the utility had an "internal error".
I tried grabbing an older image from one of the mirror sites and it is
doing the same.
The first partition is marked as a standard ISO filesystem which
probably contains the bulk of the operating system.
The second one might be an empty/blank partition?
The third filesystem is the FAT filesystem which is likely being
referenced below. If that is what you were able to mount under windows,
it sounds like it contains the EFI boot loader.
Regardless, the fact that the utility can't even give the full info
without hitting that "internal error" suggests that whatever process is
being used to create these images is causing them to become corrupted or
to otherwise be set up in some nonstandard way that is confusing the
utility.
I do find "Partitioned: false" to be rather curious after three
partitions were listed just above that... but I may simply be
misunderstanding what that particular piece of output is trying to say.
partitions:
0:
partition-name: Master Boot Record
partition-start: 0
partition-synthesized: true
partition-length: 1
partition-hint: MBR
boot-code:
0xFA31C08ED0BCEC7B89E58ED8BE007C8EC0BF0006B90001FCF3A5EA1F06000030C038C27502B280885612BE9007BF2007FFD7BEBE07B90400B48030C08A5C0038DC741338D8751F81C610004975EEBE3307BFFD06FFD789F781C6100049740F8A5C0038DC75F2BE4A07BFFD06FFD7B441BBAA558A5612CD13725081FB55AA754A81E101007444C6460010C6460100C6460201C6460300C74604007CC7460600008B850800898608008B850A0089860A00C7460C0000C7460E000089EEB442CD137324BE5607BFFD06FFD78A75018B8D0200B801028A5612BB007CCD137308BE5607BFFD06FFD7BB007C8B87FE0181F855AA750789FEEA007C0000BE6007BF2007FFD7BE6C07BF2007FFD731C0CD1631DB8EC3BB7204B83412268907EA0000FFFF6031DBAC08C07409B40ECD10AC08C075F761C34E6F2061637469766520656E74727920696E204D425200496E76616C6964204D425200492F4F206572726F7200496E76616C696420504253000D0A507265737320616C6D6F737420616E79206B657920746F207265626F6F742E2E2E004D42522E2E2E00000000000000000000000000000000000000000000000000000000000000000000000000000000
1:
partition-name: PLAN 9 FRONT (AMD64)
partition-start: 1
partition-synthesized: true
partition-length: 947071
partition-hint: Apple_ISO
2:
partition-name:
partition-start: 947072
partition-synthesized: true
partition-length: 1152
partition-hint: Apple_Free
3:
partition-start: 948224
partition-number: 1
partition-length: 2048
partition-hint: Type EF
partition-filesystems:
FAT12: CYLINDRICAL
burnable: true
Format Description: raw read/write
Checksum Value:
Properties:
Encrypted: false
Kernel Compatible: true
Checksummed: false
Software License Agreement: false
Partitioned: false
Compressed: no
Segments:
0:
/Users/fde101/Downloads/9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso
Backing Store Information:
URL:
file:///Users/fde101/Downloads/9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso
Name:
9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso
Class Name: CBSDBackingStore
hdiutil: imageinfo failed - internal error
On 8/20/22 3:08 PM, M. Osman Talayman wrote:
> My Windows computer could not see the USB drive, so I went to disk
> management to check. It was there. It has three partitions. Two are
> listed as not allocated.
> I gave the drive a drive letter, but all I can see on the drive is the
> file "9bootfat" and a directory "efi". In that directory there is a
> directory "boot" and inside that are two files of insignificant size
> "bootia32.efi" and "bootx64.efi". That's it.
> I have flashed the stick again, but I get the same result.
> Maybe something is wrong with BelenaEtcher...
>
> I then tried the mashing the keys on boot. That gave me a command
> promt. I tried writing the parameters, but boot stoped at the same
> place as before
>
> /Osman
>
> Den lør. 20. aug. 2022 kl. 20.28 skrev <smj@9p.sdf.org>:
>> Quoth M. Osman Talayman <talayman@gmail.com>:
>>> I'm sorry, I am new to Plan9
>>>
>>> Where should I type these boot paramters? I can type at the boot
>>> screen right after it stops booting, but nothing happens when I press
>>> enter
>> Boot windows on your computer and plug in the USB or SD card then you should
>> see the FAT file system mount as 'CYLINDRICAL'. In there you will find a
>> plan9.ini file where you can edit and set the necessary parameters you need.
>> You can try the individually mentioned ones in 9.5.2 or just for the ethernet
>> and see how far you go.
>>
>>
>>
>>
next prev parent reply other threads:[~2022-08-20 20:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 16:22 M. Osman Talayman
2022-08-20 16:28 ` Stanley Lieber
2022-08-20 16:30 ` Jacob Moody
2022-08-20 17:55 ` M. Osman Talayman
2022-08-20 18:26 ` smj
2022-08-20 18:28 ` Jacob Moody
2022-08-20 19:08 ` M. Osman Talayman
2022-08-20 20:06 ` Frank D. Engel, Jr. [this message]
2022-08-21 6:40 ` william
2022-08-21 7:37 ` hiro
2022-08-20 21:34 ` sl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5e47f8d-57de-0798-9529-f23e84c3e258@fjrhome.net \
--to=fde101@fjrhome.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).