guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: KMScon vs. AMD Radeon


From: pelzflorian (Florian Pelz)
Subject: Re: KMScon vs. AMD Radeon
Date: Tue, 2 Apr 2019 13:42:38 +0200
User-agent: NeoMutt/20180716

On Tue, Apr 02, 2019 at 11:26:05AM +0200, pelzflorian (Florian Pelz) wrote:
> On Mon, Apr 01, 2019 at 10:01:58PM +0200, Ludovic Courtès wrote:
> > Hi Mathieu,
> > 
> > Mathieu Othacehe <address@hidden> skribis:
> > 
> > > Here's a patch that fallback to mingetty if kmscon is not supported. I
> > > don't have a machine with AMD GPU for testing so if Florian or Pierre
> > > could test the patch that would be very helpful :)
> > 
> > That was fast, thanks!
> > 
> > We’ll wait for your feedback Florian & Pierre.  :-)
> > 
> 
> I applied Mathieu’s patch to current Guix, but the kernel panics on
> QEMU and on non-AMD Radeon hardware.  I have not tried on AMD Radeon
> yet.  I will first try again an older Guix without the patch but it
> will take a few hours.
> 

So guix pulling the old Guix commit
37099f58442419ebd847616ffe21b19c4b655a41 without the patch boots fine
on QEMU and my grandma’s 10-years-old non-AMD BIOS laptop.

The more current commit 0e558640361b6ab4aac0f424cb587b21a642bab8
without the patch runs into a Guile prompt because of an error in
resolve-variable of something with setuid-binaries on grandma’s laptop
and into a different error and a Guile prompt on QEMU with
[   9.426604] random: dbus-uuidgen: uninitialized urandom read (12 bytes read)
[   9.518845] attempt to access beyond end of device
[   9.519037] sda: rw=524288, want=3194596, limit=3184000
ERROR: In procedure primitive-load:
In procedure fport_read: Input/output error

0e558640361b6ab4aac0f424cb587b21a642bab8 with the AMD Radeon patch
runs into a kernel panic on QEMU and grandma’s laptop.  I have not
tested AMD Radeon.

Regards,
Florian



reply via email to

[Prev in Thread] Current Thread [Next in Thread]