From: "B. Atticus Grobe" <grobe0ba@tcp80.org>
To: 9front@9front.org
Subject: Re: [9front] Libaml does not recognize opcode 0x86
Date: Mon, 23 Oct 2023 17:04:28 -0500 [thread overview]
Message-ID: <4ca40378-935e-4d03-875e-36cf8fb9fb46@tcp80.org> (raw)
In-Reply-To: <88d0f7d1-6607-4486-b829-cbf98ae9dfb8@invalid.invalid>
On 10/23/23 16:48, Blue-Maned_Hawk wrote:
> On 10/23/23 17:14, Jacob Moody wrote:
>> On 10/23/23 16:05, Blue-Maned_Hawk wrote:
>>> Libaml does not recognize opcode 0x86.
>>
>> What is the context here? What are you trying to do?
>>
> My machine's battery is not detected by aux/acpi, meaning that
> /dev/battery never shows up, meaning that neither bar nor stats can show
> what is a critical piece of information.
what machine? model number? manufacturer? the output of sysinfo as run
by the hostowner?
you've provided no actionable information whatsoever. if you're going to
make a bug report, include the above information as well as any error
messages and contextual information in the first place so people don't
have to waste their time playing twenty questions.
next prev parent reply other threads:[~2023-10-23 22:05 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 21:05 Blue-Maned_Hawk
2023-10-23 21:14 ` Jacob Moody
2023-10-23 21:48 ` Blue-Maned_Hawk
2023-10-23 22:04 ` B. Atticus Grobe [this message]
2023-10-23 23:21 ` Blue-Maned_Hawk
2023-10-23 23:54 ` ori
2023-10-24 0:12 ` Blue-Maned_Hawk
2023-10-24 0:52 ` ori
2023-10-24 0:53 ` Kurt H Maier
2023-10-23 22:22 ` ori
2023-10-24 0:38 ` Kurt H Maier
2023-10-24 0:57 ` Blue-Maned_Hawk
2023-10-24 1:07 ` Michael Misch
2023-10-24 1:18 ` Blue-Maned_Hawk
2023-10-24 2:38 ` Kurt H Maier
2023-10-24 3:00 ` Blue-Maned_Hawk
2023-10-24 3:18 ` Kurt H Maier
2023-10-24 3:26 ` Ellenor Bjornsdottir
2023-10-24 3:32 ` Kurt H Maier
2023-10-24 3:32 ` Blue-Maned_Hawk
2023-10-24 3:37 ` Kurt H Maier
2023-10-24 3:52 ` Blue-Maned_Hawk
2023-10-24 4:03 ` unobe
2023-10-24 5:46 ` Lucas Francesco
2023-10-24 3:16 ` Ellenor Bjornsdottir
2023-10-24 3:23 ` Kurt H Maier
2023-10-24 3:35 ` Blue-Maned_Hawk
2023-10-24 3:43 ` B. Atticus Grobe
2023-10-24 3:53 ` Blue-Maned_Hawk
2023-10-24 8:46 ` hiro
2023-10-24 3:55 ` Tonight on Top Gear: ACPI problems, me learning a thing, and accusations of theft (was Re: [9front] Libaml does not recognize opcode 0x86) Ellenor Bjornsdottir
2023-10-24 4:04 ` [9front] multiple sending Ellenor Bjornsdottir
2023-10-24 4:10 ` Tonight on Top Gear: ACPI problems, me learning a thing, and accusations of theft (was Re: [9front] Libaml does not recognize opcode 0x86) Jacob Moody
2023-10-24 3:59 ` Ellenor Bjornsdottir
2023-10-24 4:03 ` [9front] Tonight on Top Gear. ACPI problems, me learning a thing, and accusations of theft Ellenor Bjornsdottir
2023-10-24 5:09 ` Kurt H Maier
2023-10-24 5:29 ` Ellenor Bjornsdottir
2023-10-24 5:43 ` Kurt H Maier
2023-10-24 6:06 ` [9front] Theatre of the absurd Ellenor Bjornsdottir
2023-10-24 6:27 ` Kurt H Maier
2023-10-24 3:57 [9front] Libaml does not recognize opcode 0x86 unobe
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=4ca40378-935e-4d03-875e-36cf8fb9fb46@tcp80.org \
--to=grobe0ba@tcp80.org \
--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).