<antiatom>I think Guix would make a perfect fit for such a operating system agnostic handheld computer
<ellis>So, I must have messed up the partition table for GuidSD. It won't install GRUB because there's no boot partition?
<mark_weaver>antiatom: The Neo Freerunner (GTA02) used a wireless chip that did not require loading a blob to function, so your claim that "the Neo900 gets us closer than anything" is false.
<mark_weaver>please do not spam this channel promoting a device that requires loading non-free blobs to function.
<mark_weaver>also, your claim "This blob never touches the main CPU" is false. The main CPU needs to load the blob into the WLAN device.
<mark_weaver>"There is no alternative on the market that can offer this, or even projects in the planning stages that are trying to offer this." is also false. The GTA02 had the same unusual feature of preventing the baseband processor from being able to control the user's CPU, but did not require loading a blob to use the wifi.
<phant0mas>failed on the rebased branch, sending log to ml
<antiatom>AFAIK mark_weaver, the WLAN chip in the GTA02 is the Accton 3236AQ which uses the Atheros AR6001GZ chipset. This chipset is FullMAC and implements a large part of the 802.11 stack in a non-libre, non-replaceable firmware blob stored on the ROM of the chip itself. If you use the ar6000 or ar6k driver with your GTA02, it may be GPLed but a lot of the complex code implementing Wi-Fi is non-libre but stored on-chip
<antiatom>Contrast this to the AR9170 chipset also from Atheros. This chipset has no ROM to store firmware, so you can load LIBRE firmware to the WLAN chipset's RAM so it can function.
<antiatom>Non-libre code burned onto the ROM of the WLAN chip does not make the problem of spying and the ethics of user liberties somehow magically disappear.
<antiatom>At least with the Neo900, because the firmware blob is not burned into WLAN chip ROM, there is a possibility to replace the firmware easily once someone reverse engineers it.
<antiatom>Also, Neo900 does not require WLAN to function. You can use a USB to ethernet adaptor if you want.
<phant0mas>civodul: first time failed, second succeeded
<benben9621>Hi everyone ! I'm here looking for an advice : I'm starting a new year in my university and I have to choose which distribution to put on my computer. I was considering using GuixSD but I don't know if it's stable enough since it's still at alpha stage, I would not really appreciate loosing all of my courses just before the exams actually :/
<civodul>then we need to find a way to silence the collisions
<iyzsong>civodul: sure. the 'icon-theme.cache' can be remove safely, it's for 'core-updates' right?
<iyzsong>I have remove the 'generate-icon-cache' phase in my glib-or-gtk-build-system locally. but still some packages build the cache (eg: dconf). how about split the 'gtk-update-icon-cache' out from gtk+, and then let me fixes the broke ones..
<mark_weaver>I don't remember the details, but UEFI systems require a special partition where the bootloader(s) are stored. GRUB tries to install something on that partition when the GPT partition map is present on the disk.
<ellis>My BIOS hase a setting for UEFI/Both/LegacyOnly. I had it set to legacy only. I'll read the documentation and give it another go.
<mark_weaver>iyzsong: as I recall, wingo successfully installed GuixSD with a GPT partition map, and it worked for him.
<mark_weaver>ellis: the link that iyzsong cited describes how to create the special boot partition. I suspect that if you create that partition, you'll be able to successfully install grub with GPT. alternatively, you could use MBR instead.
<iyzsong>mark_weaver: yes, GPT is supported. but UEFI require a file 'grubx64.efi' (our grub desn't have this) install into the EFI partinion.
<ellis>I've got to create the partion first right? I mean it's not intrinsically part of the disk, correct?
<iyzsong>ellis: yes, you have to create it manually (using gdisk, select '0xEF02', and 1M should be enough)
<ellis>alright. Thanks very much. I'll give it another go.
<civodul>i have a GPT too, but UEFI is another story, i think
<mark_weaver>if it's true that our GRUB doesn't support UEFI, I wonder why not.
<mark_weaver>the lack of grubx64.efi in our build output is not conclusive evidence. On the YeeLoong, I need 'grub.elf' which is loaded from PMON. That file is dynamically generated by 'grub-mkimage', which is run by 'grub-install'.
<mark_weaver>as I recall, upstream flashrom requires some old libraries, and I had to patch it up to get it to build against the new ones we have in guix. I had some difficulties making a similar patch for a newer flashrom release.
<mark_weaver>it's possible that I didn't try using libusb-compat-0.1. I don't remember, and right now I don't have time to investigate.
<mark_weaver>however, I'll say this: the 'flashrom' that comes with libreboot is hacked up to only support a few flash chips: the ones in Libreboot-supported machines, and is done in such a way so that you don't need to tell it which kind of chip you want to flash.
<amz3>np. libusb-compat-0.1 is part of LFS so I guess it's a good candidate for package, anyway I will send my patch so it doesn't get lost
<mark_weaver>so, using the upstream flashrom requires adding some extra command-line options that aren't documented in the libreboot docs.
<mark_weaver>amz3: for now, you could just use the pre-compiled 'flashrom' executable that is libreboot provides.
<mark_weaver>at some point, I'd like to add a guix package to build the libreboot images and utilities from source.
<mark_weaver>but lately I've been trying to get our MIPS and ARMHF ports in better shape
<amz3>I already did flash my laptop using libreboot provided tools, I did not know they provided pre-compiled flashrom executable, so I compiled it myself
<antiatom>True that Parabola was not the best to recommend, however...
<antiatom>mark_weaver: It is impossible to recommend to anyone who wants a handheld computer with a GSM radio + WLAN chip *anything* that does not require blobs.
<antiatom>There are no SDIO WLAN cards that run a fully libre stack, and the only practical way to handle GSM radios is to isolate them in hardware like Neo900 does.
<antiatom>People want GSM/UMTS/LTE on mobile, and they want those same computers to have WLAN. They expect that. If there is any current "smartfone" owner now who is looking for something that even BEGINS to respect the user's freedom, the only options are Openmoko and decendents (including Neo900)