From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bengt Richter Subject: Re: kmscon not working on MacBook Date: Thu, 26 Mar 2020 03:26:05 +0100 Message-ID: <20200326022605.GA21552@LionPure> References: <86lfoqy8h0.fsf@dismail.de> <87pne3d5t6.fsf@gnu.org> <60bd323b399bc4fafefc74d7fa84c0db@dismail.de> <20200308120400.bdrkyo653fhbtkml@pelzflorian.localdomain> <87a74q8spt.fsf_-_@gnu.org> <20200309074358.jly3mtrevwm75wip@pelzflorian.localdomain> <87h7yx1npi.fsf@gnu.org> <20200311071437.6ykyxcqdrgjtagrq@pelzflorian.localdomain> <20200320084850.klhoxexhnamkoelg@pelzflorian.localdomain> <20200325230018.h4f4k5cgmkivyo3h@pelzflorian.localdomain> Reply-To: Bengt Richter Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:54443) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jHIE3-00071s-E5 for guix-devel@gnu.org; Wed, 25 Mar 2020 22:26:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jHIE2-000316-60 for guix-devel@gnu.org; Wed, 25 Mar 2020 22:26:31 -0400 Content-Disposition: inline In-Reply-To: <20200325230018.h4f4k5cgmkivyo3h@pelzflorian.localdomain> 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-mx.org@gnu.org Sender: "Guix-devel" To: "pelzflorian (Florian Pelz)" Cc: guix-devel@gnu.org, jbranso@dismail.de Hi, On +2020-03-26 00:00:18 +0100, pelzflorian (Florian Pelz) wrote: > On Fri, Mar 20, 2020 at 09:48:50AM +0100, pelzflorian (Florian Pelz) wr= ote: > > I would > > like something similar to be included in the next release. Maybe > > kmscon works everywhere then. >=20 > Of course the machines that need uvesafb to show the installer also > later have problems showing Xorg. Maybe until Xorg on installed > systems without Kernel Mode Setting works fine without manually > fiddling with uvesafb or nonfree drivers, there is no use making the > installer work. >=20 > Perhaps uvesafb could somehow be made to work automatically, however > on one of my computers uvesafb can only be used after =E2=80=9Echmmod o= +rw > /dev/fb0=E2=80=9C which is a security issue, I suppose. > Are you a member of the video group? What do you see typing stat /dev/fb0 ? Maybe something to try? Or not relevant to your context? >=20 > > ('nomodeset' is not needed; I leave it > > in only for testing on computers where the graphical installer works > > anyway when not passing 'nomodeset'.) >=20 > In fact nomodeset was needed on a friend=E2=80=99s AMD GPU system. Pro= bably > one could blacklist yet another AMD graphics module instead of passing > nomodeset. But then the installer on AMD systems where the module is > working fine would be limited to uvesafb. >=20 > Regards, > Florian >=20 --=20 Regards, Bengt Richter