From mboxrd@z Thu Jan 1 00:00:00 1970 From: "pelzflorian (Florian Pelz)" Subject: Re: kmscon not working on MacBook Date: Fri, 20 Mar 2020 09:48:50 +0100 Message-ID: <20200320084850.klhoxexhnamkoelg@pelzflorian.localdomain> 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> 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]:47919) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jFDKp-0007db-7h for guix-devel@gnu.org; Fri, 20 Mar 2020 04:48:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jFDKo-000166-1J for guix-devel@gnu.org; Fri, 20 Mar 2020 04:48:55 -0400 Content-Disposition: inline In-Reply-To: <20200311071437.6ykyxcqdrgjtagrq@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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org, jbranso@dismail.de On Wed, Mar 11, 2020 at 08:14:37AM +0100, pelzflorian (Florian Pelz) wrot= e: > I could get the installer to display properly by using [=E2=80=A6]the u= seful v86d helper[=E2=80=A6] >=20 > guix package -f v86d.scm > ln -s /gnu/store/yj9mxi0yr4ksg5v7031mdrc8fvb2wxrb-linux-libre-5.4.24/li= b/ /lib > modprobe uvesafb v86d=3D/root/.guix-profile/sbin/v86d >=20 > Without the symbolic linking, kmscon displays a flickering Module > uvesafb not found in directory /lib/modules=E2=80=A6 >=20 > I will try to properly package v86d now (without bundled libraries). > uvesafb does not work on my Macbook though; I believe it conflicts > with modesetting. >=20 Now that v86d is pushed as e2303e8e375ed2e07c1fd760c86a204eb51fbc6e (see ): The attached patch makes the graphical installer work on two old computers I tested. I do not know how to proceed with it. I would like something similar to be included in the next release. Maybe kmscon works everywhere then. ('nomodeset' is not needed; I leave it in only for testing on computers where the graphical installer works anyway when not passing 'nomodeset'.) The patch should not change behavior on machines where /dev/fb0 is created via modesetting anyway. Regards, Florian