From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] 9front kernel panic on bootstrap on rpi
Date: Thu, 30 Apr 2020 09:30:00 -0700 [thread overview]
Message-ID: <4DEE521904ACAA89152A46A6BDAD3997@eigenstate.org> (raw)
In-Reply-To: <56E8B6A3-F137-4570-84CA-63A0CB1F9A5B@me.com>
> Hi folks,
> After the mice problems I have on my rpi2 with 9front [1], I
> decided to check if I can have an instance working on another
> machine, i.e. an old rpi model A. I cannot get through the
> boostrap process, the kernel panics.
Thanks for the reports. Two things:
0) It's going to be very hard to debug this if you don't have
a way to rebuild the software for testing. Getting net boot
working (even from a VM) would make it much easier.
1) You're likely to get better results on the 9front mailing
list. (9front@9front.org)
Unfortunately, I have neither version of the rasperry pi,
and the mouse model you have doens't seem to be available
on Amazon any more, so I can't even try it out on the PC
on my end.
> I can provide more context and information, but first I
> wanted to ask: am I picking a broken image?
cpu% sha1sum 9front.pi.img
ffb9f6569c7c239a58f0e6e508aac9d2418333af 9front.pi.img
> [2] Again, as for the mice problme, the legacy miller
> version works like a charm even on this rpi!
From what I understand, the difference there is that 9front
will parse the HID descriptor, while 9legacy will hardcode
the boot protocol. There are a number of places that this can
be going wrong -- from bad HID descriptors to power brownouts
to USB bugs.
As far as booting: A picture of the panic message would help.
As far as the mouse: First question -- does it work if you
plug it into a PC? (You can test with a USB stick). If it
fails there, then it's likely a problem with HID parsing.
Second question: Does it work with a powered USB hub? If
yes, then it's likely to be the Pi's power limitations.
Third question: Does it work with a different mouse?
If not, then it'll take more work to investigate.
next prev parent reply other threads:[~2020-04-30 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 7:51 Daniel Morandini
2020-04-30 16:30 ` ori [this message]
2020-05-01 10:18 ` [9fans] " Daniel Morandini
2020-05-01 12:11 ` Marshall Conover
2020-05-01 19:01 ` Daniel Morandini
2020-05-01 15:04 ` ori
2020-05-01 18:57 ` Daniel Morandini
2020-05-04 20:35 ` Daniel Morandini
2020-04-30 18:24 ` cinap_lenrek
2020-05-01 9:52 ` Daniel Morandini
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=4DEE521904ACAA89152A46A6BDAD3997@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.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).