From: Romano <unobe@cpan.org>
To: 9front@9front.org,cinap_lenrek@felloff.net
Subject: Re: [9front]
Date: Thu, 01 Apr 2021 18:33:48 +0000 [thread overview]
Message-ID: <CB0FCC47-EEA4-4DD3-B64E-0363ECEC1EC1@cpan.org> (raw)
In-Reply-To: <586EDF30A2796561481D53C56984C5C9@felloff.net>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
On March 31, 2021 4:32:37 PM UTC, cinap_lenrek@felloff.net wrote:
>Subject: state of emmc and usb on pi400 and cm4
>I'm in preparation for a new 9front release,
>fixing penting issues.
>
>I have confirmation that the XHCI (USB3) works
>now on the pi400, but there are still issues with
>the sdcard.
>
>On the CM4, we have to enable the usbdwc driver
>(as it does not have the xhci controller chip)
>in the kernel configuration, but i have no
>confirmation if this works.
>
>So is it possible for anyone owning these devices
>to troubleshoot this before the end of this week?
I don't have a pi400, but I do have a macbook pro, 13", early 2011. With the last release's ISO (8013), it booted and installed fine (albeit with a bunch of i8042 warnings and bcm not functioning) . I resolved my networking issue by tethering to a pinephone. However, with tip I get a kernel panic. I have attached screenshots. Any idea what could be the cause?
[-- Attachment #2: IMAG9252.jpg --]
[-- Type: image/jpeg, Size: 1550115 bytes --]
next prev parent reply other threads:[~2021-04-01 18:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 16:32 [9front] cinap_lenrek
2021-04-01 18:33 ` Romano [this message]
2021-04-01 18:54 ` [9front] Romano
2021-04-01 19:03 ` [9front] cinap_lenrek
2021-04-01 23:16 ` [9front] Romano
2021-04-02 14:31 ` [9front] cinap_lenrek
2021-04-02 18:31 ` [9front] cinap_lenrek
2021-04-03 0:41 ` [9front] Romano
2021-04-02 21:24 ` [9front] Romano
2021-04-02 21:54 ` [9front] cinap_lenrek
-- strict thread matches above, loose matches on Subject: below --
2022-06-22 12:28 [9front] roy niang
2022-06-22 12:32 ` [9front] stefncb
2022-01-10 8:44 [9front] thinktankworkspaces
2022-01-10 10:21 ` [9front] sirjofri
2022-01-10 17:25 ` [9front] thinktankworkspaces
2022-01-10 23:33 ` [9front] sirjofri
2022-01-12 1:16 ` [9front] thinktankworkspaces
2022-01-12 8:30 ` [9front] sirjofri
2022-01-12 9:29 ` [9front] Eckard Brauer
2022-01-12 13:09 ` [9front] sirjofri
2022-01-12 13:40 ` [9front] hiro
2022-01-12 14:59 ` [9front] thinktankworkspaces
2022-01-12 16:56 ` [9front] hiro
2022-01-14 11:45 ` [9front] cinap_lenrek
2022-01-12 14:40 ` [9front] thinktankworkspaces
2022-01-12 14:18 ` [9front] Stanley Lieber
2022-01-12 15:04 ` [9front] thinktankworkspaces
2022-01-10 12:10 ` [9front] mkf
2021-09-16 22:17 [9front] Drew Fargo
2021-08-24 19:25 [9front] Jonas
2021-06-09 14:33 [9front] adr
2021-01-22 16:32 [9front] Марко М. Костић
2021-01-22 23:41 ` [9front] Tanami Muller
2021-01-23 0:29 ` [9front] Stuart Morrow
2021-01-23 13:38 ` [9front] Thaddeus Woskowiak
2021-01-23 14:12 ` [9front] hiro
2018-08-20 19:42 [9front] umbraticus
2018-08-20 12:11 [9front] Alex Musolino
2018-06-06 12:30 Stanislav Paskalev
2018-06-06 15:50 ` [9front] Kurt H Maier
2018-02-17 4:53 [9front] kokamoto
2016-12-28 23:31 sl
2016-12-28 23:33 ` [9front] cinap_lenrek
2015-10-02 11:43 Holger Sebert
2015-10-02 14:32 ` [9front] Kurt H Maier
2015-10-04 21:18 ` [9front] Stanley Lieber
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=CB0FCC47-EEA4-4DD3-B64E-0363ECEC1EC1@cpan.org \
--to=unobe@cpan.org \
--cc=9front@9front.org \
--cc=cinap_lenrek@felloff.net \
/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).