unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Brice Waegeneire <brice@waegenei.re>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Ryan Osborne <r.asdert@gmail.com>,
	Mathieu Othacehe <m.othacehe@gmail.com>,
	41082@debbugs.gnu.org
Subject: bug#41082: nomodeset
Date: Sun, 10 May 2020 19:44:06 +0000	[thread overview]
Message-ID: <0f7d5d9a5755698baaf1a69df4f1fddb@waegenei.re> (raw)
In-Reply-To: <20200506225311.597322f0@scratchpost.org>

Hello,

On 2020-05-06 20:53, Danny Milosavljevic wrote:
[...]

> Maybe that's premature and we could use etc-service-type in the mean 
> time.
> However, if a kernel-module-configuration-service appeared later then 
> users
> would have to migrate to it manually.  Not great.
> 
>> > kernel-module-configuration-service if/when it exists.  (I did not
>> > know how to extend etc-service-type with a file created at runtime not
>> > build time, but maybe kernel-module-configuration-service works
>> > differently anyway.)
> 
> I think Brice already had a nice mockup for the design, but I don't 
> know whether
> Brice plans to do it or not.  Brice?

I don't have code for the kernel-module-configuration-service yet but 
since use
cases for this service come up every few weeks it may be time to 
implement it.
I'll work on it in the coming days.

Cheers,
- Brice




  reply	other threads:[~2020-05-10 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 17:03 bug#41082: Guix sd startup fails to initialize AMD Radeon RX 560 Ryan Osborne
2020-05-05  1:58 ` Boris A. Dekshteyn
2020-05-05 12:39 ` bug#41082: nomodeset Ryan Osborne
2020-05-06  6:56   ` Mathieu Othacehe
2020-05-06  8:19     ` pelzflorian (Florian Pelz)
2020-05-06 20:53       ` Danny Milosavljevic
2020-05-10 19:44         ` Brice Waegeneire [this message]
2020-05-06 14:57     ` Danny Milosavljevic

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0f7d5d9a5755698baaf1a69df4f1fddb@waegenei.re \
    --to=brice@waegenei.re \
    --cc=41082@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=m.othacehe@gmail.com \
    --cc=r.asdert@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).