From mboxrd@z Thu Jan 1 00:00:00 1970 From: "pelzflorian (Florian Pelz)" Subject: bug#40538: installer: Support uvesafb to install on machines without KMS. Date: Mon, 13 Apr 2020 07:37:25 +0200 Message-ID: <20200413053725.5fwe57hyz7vkhlbq@pelzflorian.localdomain> References: <87tv1rv21e.fsf@gnu.org> <20200411184346.c3cgop7egcjyqzwf@pelzflorian.localdomain> <874ktpspr5.fsf@gnu.org> <20200412090257.jxljqbkwfhn7afnr@pelzflorian.localdomain> <20200412112400.x4qufeztdnkmzqhx@pelzflorian.localdomain> <874ktooj3v.fsf@gmail.com> <20200412153052.ewxdd6m4f6yar2jw@pelzflorian.localdomain> <20200412174819.GA10140@LionPure> <20200412181101.tfhtbyviwqbwsaqg@pelzflorian.localdomain> <20200413050026.GA17633@LionPure> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:56080) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jNrnH-0000dW-4k for bug-guix@gnu.org; Mon, 13 Apr 2020 01:38:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jNrnG-0000lj-5a for bug-guix@gnu.org; Mon, 13 Apr 2020 01:38:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:47587) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jNrnF-0000la-PN for bug-guix@gnu.org; Mon, 13 Apr 2020 01:38:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jNrnF-0007Qi-Im for bug-guix@gnu.org; Mon, 13 Apr 2020 01:38:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20200413050026.GA17633@LionPure> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Bengt Richter Cc: 40538@debbugs.gnu.org On Mon, Apr 13, 2020 at 07:00:26AM +0200, Bengt Richter wrote: > Sorry I don't seem to be able to accept a mystery sigsev ;-) Thank you for your debugging help. Of course you are right that sigsegv is not good error handling. I can look later what might be the error in /sbin/v86d. But now I am busy with other bugs. > Hm, could it be there in /gnu/store and have been built so it's a wrong > version somehow for the running kernel? That's the only bug possibility > I can think of now ;-) The latest commits to https://github.com/mjanusz/v86d are from 2014. However we patch v86d to use a more recent x86emu. Maybe there is some incompatibility. > sudo dmesg|grep -i fb in that context doesn't show anything weird? > > Oh, well. > Could it be wrapped and caught in a catch? Probably yes. I will get back to this bug later, feel free to change and catch things in the meantime. Maybe the sigsegv even shows up in QEMU? Regards, Florian