From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: KMScon vs. AMD Radeon Date: Wed, 3 Apr 2019 23:02:44 +0200 Message-ID: <20190403230244.663ee305@scratchpost.org> References: <871s3a4xd4.fsf@gnu.org> <87sgv89w3k.fsf@gnu.org> <20190328000935.qnhrbamajj47vibu@pelzflorian.localdomain> <87h8bl8xrb.fsf_-_@gnu.org> <875zs1k5ac.fsf@gmail.com> <20190329180022.pqzdrzcjrbm3z5ub@pelzflorian.localdomain> <871s2o6cyt.fsf@gmail.com> <87imw0u558.fsf@ambrevar.xyz> <20190330152211.2ugzdbvp2hjy3lvl@pelzflorian.localdomain> <871s2lkesq.fsf@gmail.com> <87a7h9jxzd.fsf@gnu.org> <87y34sj122.fsf@gmail.com> <20190402183102.3d951dc2@scratchpost.org> <87tvffilot.fsf@gmail.com> <20190403131944.2b4244c5@scratchpost.org> <20190403205630.30b80f49@scratchpost.org> <87wokaq0gd.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/wgSMRG6b3eyw29K/p.Y4upD"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:36253) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hBn2Q-0006DC-3z for guix-devel@gnu.org; Wed, 03 Apr 2019 17:03:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hBn2N-0001tq-JX for guix-devel@gnu.org; Wed, 03 Apr 2019 17:03:13 -0400 In-Reply-To: <87wokaq0gd.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?ISO-8859-1?Q?Court=E8s?= Cc: Guix-devel , Mathieu Othacehe --Sig_/wgSMRG6b3eyw29K/p.Y4upD Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > To summarize, we=E2=80=99re just missing =E2=80=98--with-video=3Dfbdev,dr= m2d=E2=80=99 and then > we=E2=80=99re done, right? Reading the kmscon source code (configure.ac), it seems that the default is "fbdev,drm2d,drm3d". I suspect that the drm hangs the kernel in Florian's case. It indeed might make sense to try whether "--with-video=3Dfbdev,drm2d" (i.e. without "drm3d") improves things, and if not, just disable drm modesetting at bootup. If it's not there then it can't break :P --Sig_/wgSMRG6b3eyw29K/p.Y4upD Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlylH3QACgkQ5xo1VCww uqW79Qf9HwtruoIV/cVMN6Z/bmD230vijFmvTuYYZBSg/reWVDkYaQMyU2DOY6Bd PDS2YszE/UnVeN1S7bwu7m18s2cdh2bzjD7qC18hTfttbPVMbsTC6evtx/pjEN/9 JtmCEEp8am7fViBtZ+1Ts5MUYddUIl0XlnlkHEv/4vWDZxKz7E3+0xpghBy6slfF 105wmDY3CI3w/D172bJBmNHoFhbhDCgRJE2lph6cW5opaxP6CwDWIfVVbux5nsDt qVe6VgqrcrdHaPjFjSM3Sxb/6GU6XRRghDrda66+x7jflQkgorb0Wv98jOljxGEG BYtAlxK5w0LFVxljEj8Jj8q78iG6HA== =3ebw -----END PGP SIGNATURE----- --Sig_/wgSMRG6b3eyw29K/p.Y4upD--