Hello, I'm trying to install 9front from the amd64 ISO from http://9front.org/iso/ I flashed the ISO to a USB stick using balenaEtcher on Windows10. The computer I try to install on is a Lenovo T570. It starts to boot, but stops shortly after. The last few line of the boot message is: i219: phy 1 wedged 08210000 i219: phy 2 wedged 08420000 i219 phy2 oui oxfffde #11: '/lib/firmware/iwm-8265-34' does not exist i219: phy 2 wedged 085a0000 i219: phy 2 wedged 085a0000 i219: phy 2 wedged 085a0000 sdN (nvme): using 4 submit queues i219: phy 2 wedged 085a0000 I notice that something is missing in /lib/firmware, but I don't know if that is the reason it doesn't get any further. The complete output is Plan 9 HPET: fed00000 0086a701 24 MHz 124 holes free 0x00026000 0x00058000 204800 0x00059000 0x0009d000 278528 0x00100000 0x00110000 65536 0x0059b000 0x7ffff000 2141601792 2142150656 bytes free cpu0: 2913MHz GenuineIntel Celeron (AX 000806E9 CX 77FAFBFF DX BFEBFBFF) LAPIC: fee00000 0xfffffe80fee00000 ec: cmd 66, data 62 ELCR: 0000 cpu0: lapic clock at 24MHz cpu2: 2913MHz GenuineIntel Celeron (AX 000806E9 CX 77FAFBFF DX BFEBFBFF) cpu1: 2913MHz GenuineIntel Celeron (AX 000806E9 CX 77FAFBFF DX BFEBFBFF) cpu3: 2913MHz GenuineIntel Celeron (AX 000806E9 CX 77FAFBFF DX BFEBFBFF) i219: bad eeprom checksum - 0x13ba: ignored #10: i219: 1000Mbps port 0xEC200000 irq 255 ea 54ee75fc0345 pcienable PCI.0.28.6: pcr 3->7 pcienable PCI.4.0.0: pcr 0->2 "11: iwl: 54Mbps port 0xEC100000 irq 255 ea 000000000000 #A0: hda mcm ec240000 irq 255 #A0: codec #0, vendor 10cc0298, rev 001000103 #a0: codec #2, vendor 8086280b, rev 00100000 usbxhci: 0x8086 0x9d2f: port ec220000 size 65536 irq 255 31375M memory: 2048M kernel data, 2932M user, 29952M swap bootfs: Wed Apr 13 13:58:09 GMT 2022 fingerprint: 158c55aeed3a9f19c1243d7bfdbcf31890b5e2ef i219: phy 1 wedged 08210000 i219: phy 2 wedged 08420000 i219 phy2 oui oxfffde #11: '/lib/firmware/iwm-8265-34' does not exist i219: phy 2 wedged 085a0000 i219: phy 2 wedged 085a0000 i219: phy 2 wedged 085a0000 sdN (nvme): using 4 submit queues i219: phy 2 wedged 085a0000 Any idea what I should do or if my computer is even compatible with Plan9? Thanks /Osman
[-- Attachment #1: Type: text/plain, Size: 2550 bytes --] try: http://fqa.9front.org/fqa9.html#9.5.2 sl > On Aug 20, 2022, at 12:24 PM, M. Osman Talayman <talayman@gmail.com> wrote: > > Hello, > > I'm trying to install 9front from the amd64 ISO from > > http://9front.org/iso/ > > I flashed the ISO to a USB stick using balenaEtcher on Windows10. > > The computer I try to install on is a Lenovo T570. It starts to boot, > but stops shortly after. The last few line of the boot message is: > > i219: phy 1 wedged 08210000 > i219: phy 2 wedged 08420000 > i219 phy2 oui oxfffde > #11: '/lib/firmware/iwm-8265-34' does not exist > i219: phy 2 wedged 085a0000 > i219: phy 2 wedged 085a0000 > i219: phy 2 wedged 085a0000 > sdN (nvme): using 4 submit queues > i219: phy 2 wedged 085a0000 > > I notice that something is missing in /lib/firmware, but I don't know > if that is the reason it doesn't get any further. > > The complete output is > > Plan 9 > HPET: fed00000 0086a701 24 MHz > 124 holes free > 0x00026000 0x00058000 204800 > 0x00059000 0x0009d000 278528 > 0x00100000 0x00110000 65536 > 0x0059b000 0x7ffff000 2141601792 > 2142150656 bytes free > cpu0: 2913MHz GenuineIntel Celeron (AX 000806E9 CX 77FAFBFF DX BFEBFBFF) > LAPIC: fee00000 0xfffffe80fee00000 > ec: cmd 66, data 62 > ELCR: 0000 > cpu0: lapic clock at 24MHz > cpu2: 2913MHz GenuineIntel Celeron (AX 000806E9 CX 77FAFBFF DX BFEBFBFF) > cpu1: 2913MHz GenuineIntel Celeron (AX 000806E9 CX 77FAFBFF DX BFEBFBFF) > cpu3: 2913MHz GenuineIntel Celeron (AX 000806E9 CX 77FAFBFF DX BFEBFBFF) > i219: bad eeprom checksum - 0x13ba: ignored > #10: i219: 1000Mbps port 0xEC200000 irq 255 ea 54ee75fc0345 > pcienable PCI.0.28.6: pcr 3->7 > pcienable PCI.4.0.0: pcr 0->2 > "11: iwl: 54Mbps port 0xEC100000 irq 255 ea 000000000000 > #A0: hda mcm ec240000 irq 255 > #A0: codec #0, vendor 10cc0298, rev 001000103 > #a0: codec #2, vendor 8086280b, rev 00100000 > usbxhci: 0x8086 0x9d2f: port ec220000 size 65536 irq 255 > 31375M memory: 2048M kernel data, 2932M user, 29952M swap > bootfs: Wed Apr 13 13:58:09 GMT 2022 > fingerprint: 158c55aeed3a9f19c1243d7bfdbcf31890b5e2ef > i219: phy 1 wedged 08210000 > i219: phy 2 wedged 08420000 > i219 phy2 oui oxfffde > #11: '/lib/firmware/iwm-8265-34' does not exist > i219: phy 2 wedged 085a0000 > i219: phy 2 wedged 085a0000 > i219: phy 2 wedged 085a0000 > sdN (nvme): using 4 submit queues > i219: phy 2 wedged 085a0000 > > Any idea what I should do or if my computer is even compatible with Plan9? > > Thanks > /Osman > [-- Attachment #2: Type: text/html, Size: 3875 bytes --]
On 8/20/22 10:28, Stanley Lieber wrote:
> try:
>
> http://fqa.9front.org/fqa9.html#9.5.2 <http://fqa.9front.org/fqa9.html#9.5.2>
>
> sl
>
Since it seems it looks like something strange is going on with your ethernet card as well.
There is also a
*noetherprobe=
that can be used to prevent the kernel from automatically enumerating the network interfaces.
Perhaps it should be added to that list in the fqa as well?
Thanks,
moody
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
/Osman
Den lør. 20. aug. 2022 kl. 18.44 skrev Jacob Moody <moody@mail.posixcafe.org>:
>
> On 8/20/22 10:28, Stanley Lieber wrote:
> > try:
> >
> > http://fqa.9front.org/fqa9.html#9.5.2 <http://fqa.9front.org/fqa9.html#9.5.2>
> >
> > sl
> >
>
> Since it seems it looks like something strange is going on with your ethernet card as well.
> There is also a
>
> *noetherprobe=
>
> that can be used to prevent the kernel from automatically enumerating the network interfaces.
> Perhaps it should be added to that list in the fqa as well?
>
> Thanks,
> moody
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.
On 8/20/22 12:26, smj@9p.sdf.org wrote:
> 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.
>
You can also just mash keys at startup to get dropped in to a prompt.
Then you can write out parameters in the command prompt.
Once you are done writing parameters type 'boot'
to actually continue the boot process.
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.
>
>
>
>
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.
>>
>>
>>
>>
>> http://fqa.9front.org/fqa9.html#9.5.2 <http://fqa.9front.org/fqa9.html#9.5.2>
>>
>> sl
>>
>
> Since it seems it looks like something strange is going on with your ethernet card as well.
> There is also a
>
> *noetherprobe=
>
> that can be used to prevent the kernel from automatically enumerating the network interfaces.
> Perhaps it should be added to that list in the fqa as well?
done!
sl
as a litmus test you could install virtual box on the windows box and try the install in virtual box.
That would validate the image is good or not.You can also utilize usb devices in virtualbox and
write or cat images to a usb device where it might fail in windows you know cause its windows which is likely unstable to begin with. Well maybe virtualbox is not good either so you can try qemu.
Either way you will learn more about the install with virtual box or qemu
Quoth M. Osman Talayman <talayman@gmail.com>:
> 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.
> >
> >
> >
> >
>
no. vbox is a known error source!
On 8/21/22, william@thinktankworkspaces.com
<william@thinktankworkspaces.com> wrote:
> as a litmus test you could install virtual box on the windows box and try
> the install in virtual box.
> That would validate the image is good or not.You can also utilize usb
> devices in virtualbox and
> write or cat images to a usb device where it might fail in windows you know
> cause its windows which is likely unstable to begin with. Well maybe
> virtualbox is not good either so you can try qemu.
>
> Either way you will learn more about the install with virtual box or qemu
>
>
>
> Quoth M. Osman Talayman <talayman@gmail.com>:
>> 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.
>> >
>> >
>> >
>> >
>>
>
>