bug#30589: serial login not working

2018-02-23 Thread George myglc2 Clemmer
The recent move of agetty-service into #base-services caused serial login to stop working here. Previously this worked ... (agetty-service (agetty-configuration (tty "ttyS1") (baud-rate "115200"))) First I tried removing the lines above. The

bug#30537: glibc 2.26 refuses to run on CentOS 6.8

2018-02-23 Thread Ludovic Courtès
Hello, Ricardo Wurmus skribis: > I have a bad day. After the upgrade to glibc 2.26 none of the > Guix-installed software runs on the HPC cluster running CentOS 6.8. Bah. :-( > The glibc 2.26 expects a minimum kernel version of 3.x on x86_64, but > CentOS 6.8 only comes with a heavily patched

bug#30537: Grafts vs. early bootstrapping packages

2018-02-23 Thread Ludovic Courtès
Hello, Mark H Weaver skribis: >> Ricardo Wurmus writes: [...] >> (define glibc-final >>;; The final glibc, which embeds the statically-linked Bash built above. >> - (package (inherit glibc-final-with-bootstrap-bash) >> + (package/inherit glibc-final-with-bootstrap-bash >> (name "g

bug#30505: Starting console/terminal Unicode support

2018-02-23 Thread Ludovic Courtès
Hello! Danny Milosavljevic skribis: > On Wed, 21 Feb 2018 23:21:34 +0100 > l...@gnu.org (Ludovic Courtès) wrote: > >> >> This ‘unicode-start’ procedure is essentially a port of the >> >> ‘unicode_start’ script from ‘kbd’. I suppose the justification is to >> >> make sure we’re using UTF-8 input

bug#30467: GuixSD fails to display login prompt on headless server

2018-02-23 Thread George myglc2 Clemmer
On 02/22/2018 at 11:41 Danny Milosavljevic writes: > Hi George, > > On Wed, 21 Feb 2018 20:35:34 -0500 > George myglc2 Clemmer wrote: > >> I think we got side-tracked to the serial port when my real issue is >> with the VGA port. Maybe my bug report was not clear. Let me clarify ... > > Oh, that

bug#30311: efi-less grub install fails

2018-02-23 Thread Marius Bakke
Ricardo Wurmus writes: > Marius Bakke writes: > >> Ricardo: Can you post the output of `find /sys/firmware/efi -maxdepth 1` >> on the affected machine? With luck, we'll find a variable that is only >> present on "real" EFI. >> >> Can you also post the contents of '/sys/firmware/efi/runtime'? >