9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "M. Osman Talayman" <talayman@gmail.com>
To: 9front@9front.org
Subject: [9front] Cannot install 9front
Date: Sat, 20 Aug 2022 18:22:23 +0200	[thread overview]
Message-ID: <CAJ4zFbK1nNwyBGbyU_1xesAzrdCsezoEEJUCcEB2n+LE7gkTww@mail.gmail.com> (raw)

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

             reply	other threads:[~2022-08-20 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20 16:22 M. Osman Talayman [this message]
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.
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=CAJ4zFbK1nNwyBGbyU_1xesAzrdCsezoEEJUCcEB2n+LE7gkTww@mail.gmail.com \
    --to=talayman@gmail.com \
    --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).