GNU bug report logs - #38804
Samsung Chromebook 3

Previous Next

Package: guix;

Reported by: Caleb Herbert <csh <at> bluehome.net>

Date: Mon, 30 Dec 2019 02:03:01 UTC

Severity: normal

To reply to this bug, email your comments to 38804 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#38804; Package guix. (Mon, 30 Dec 2019 02:03:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Caleb Herbert <csh <at> bluehome.net>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Mon, 30 Dec 2019 02:03:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Caleb Herbert <csh <at> bluehome.net>
To: bug-guix <at> gnu.org
Subject: Samsung Chromebook 3
Date: Sun, 29 Dec 2019 20:02:11 -0600
[Message part 1 (text/plain, inline)]
I tried running the Guix System installer on my Chromebook.  I wanted to
try replacing GalliumOS.

Unsurprisingly, I get many errors do to proprietary firmware.  My
keyboard doesn't work, so I can't check what all the messages said, and
I can go no further with the installation.

Model
Samsung Chromebook 3

Hardware ID
CELES

Year
2016

Processor
Intel Braswell

It's supported by GalliumOS, but there are multiple issues:

	CELES (Samsung Chromebook 3) This model has been problematic for many
users, but it has also been perfectly successful for others, We haven't
been able to find the differences that separate these two groups, so we
do not recommend CELES. If you already own a CELES, and would like to
try GalliumOS, give it a shot! You might be one of the lucky ones.
However, if you are looking to purchase a Chromebook with the intention
of running GalliumOS, we strongly suggest choosing a different model.

https://wiki.galliumos.org/Hardware_Compatibility#cite_note-CELES-22
[csh.vcf (text/x-vcard, attachment)]

Information forwarded to bug-guix <at> gnu.org:
bug#38804; Package guix. (Mon, 30 Dec 2019 02:21:02 GMT) Full text and rfc822 format available.

Message #8 received at 38804 <at> debbugs.gnu.org (full text, mbox):

From: Brett Gilio <brettg <at> gnu.org>
To: Caleb Herbert <csh <at> bluehome.net>
Cc: 38804 <at> debbugs.gnu.org
Subject: Re: bug#38804: Samsung Chromebook 3
Date: Mon, 30 Dec 2019 02:20:25 +0000 (UTC)

Dec 29, 2019 8:03:39 PM Caleb Herbert :

> I tried running the Guix System installer on my Chromebook. I wanted to
> try replacing GalliumOS.
>
> Unsurprisingly, I get many errors do to proprietary firmware. My
> keyboard doesn't work, so I can't check what all the messages said, and
> I can go no further with the installation.
>
> Model
> Samsung Chromebook 3
>
> Hardware ID
> CELES
>
> Year
> 2016
>
> Processor
> Intel Braswell
>
> It's supported by GalliumOS, but there are multiple issues:
>
> CELES (Samsung Chromebook 3) This model has been problematic for many
> users, but it has also been perfectly successful for others, We haven't
> been able to find the differences that separate these two groups, so we
> do not recommend CELES. If you already own a CELES, and would like to
> try GalliumOS, give it a shot! You might be one of the lucky ones.
> However, if you are looking to purchase a Chromebook with the intention
> of running GalliumOS, we strongly suggest choosing a different model.
>
> https://wiki.galliumos.org/Hardware_Compatibility#cite_note-CELES-22
>


Hey Caleb,

Thanks for the report! I don't have much to say other than I suspect that this is going to have to be resolved by somebody reverse-engineering the proprietary components and releasing them as free software.

Maybe I am wrong though, so I will let somebody else take over from here. :)

Best!

-- 
Brett M. Gilio
GNU Guix, Contributor | GNU Project, Webmaster
[DFC0 C7F7 9EE6 0CA7 AE55 5E19 6722 43C4 A03F 0EEE]
< brettg <at> gnu.org [mailto:brettg <at> gnu.org] > < brettg <at> posteo.net [mailto:brettg <at> posteo.net] >





Information forwarded to bug-guix <at> gnu.org:
bug#38804; Package guix. (Mon, 30 Dec 2019 02:30:02 GMT) Full text and rfc822 format available.

Message #11 received at 38804 <at> debbugs.gnu.org (full text, mbox):

From: Caleb Herbert <csh <at> bluehome.net>
To: Brett Gilio <brettg <at> gnu.org>
Cc: 38804 <at> debbugs.gnu.org
Subject: Re: bug#38804: Samsung Chromebook 3
Date: Sun, 29 Dec 2019 20:29:47 -0600
[Message part 1 (text/plain, inline)]
No problem, I just promised on IRC that I'd document this.
[csh.vcf (text/x-vcard, attachment)]

Information forwarded to bug-guix <at> gnu.org:
bug#38804; Package guix. (Tue, 31 Dec 2019 12:50:02 GMT) Full text and rfc822 format available.

Message #14 received at 38804 <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: Caleb Herbert <csh <at> bluehome.net>
Cc: 38804 <at> debbugs.gnu.org
Subject: Re: bug#38804: Samsung Chromebook 3
Date: Tue, 31 Dec 2019 13:49:02 +0100
[Message part 1 (text/plain, inline)]
Hi,

On Sun, 29 Dec 2019 20:02:11 -0600
Caleb Herbert <csh <at> bluehome.net> wrote:

> I tried running the Guix System installer on my Chromebook.  I wanted to
> try replacing GalliumOS.
> 
> Unsurprisingly, I get many errors do to proprietary firmware.  My
> keyboard doesn't work, so I can't check what all the messages said

If you want, try connecting an usb keyboard in order to find out.  It might
work.
[Message part 2 (application/pgp-signature, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#38804; Package guix. (Tue, 31 Dec 2019 16:26:01 GMT) Full text and rfc822 format available.

Message #17 received at 38804 <at> debbugs.gnu.org (full text, mbox):

From: Caleb Herbert <csh <at> bluehome.net>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 38804 <at> debbugs.gnu.org
Subject: Re: bug#38804: Samsung Chromebook 3
Date: Tue, 31 Dec 2019 10:25:34 -0600
[Message part 1 (text/plain, inline)]
On 12/31/2019 06:49 AM, Danny Milosavljevic wrote:
>> Unsurprisingly, I get many errors do to proprietary firmware.  My
>> keyboard doesn't work, so I can't check what all the messages said
> 
> If you want, try connecting an usb keyboard in order to find out.  It might
> work.

I would have, if I had one.  I'm the only one who uses a real computer
here, and it's an X200 laptop.  Everyone else uses Swindles and Android
for all of their computing.

-- 
Caleb Herbert
KE0VVT
816-892-9669
https://bluehome.net/csh
[csh.vcf (text/x-vcard, attachment)]
[signature.asc (application/pgp-signature, attachment)]

Information forwarded to bug-guix <at> gnu.org:
bug#38804; Package guix. (Tue, 31 Dec 2019 16:29:01 GMT) Full text and rfc822 format available.

Message #20 received at 38804 <at> debbugs.gnu.org (full text, mbox):

From: Caleb Herbert <csh <at> bluehome.net>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 38804 <at> debbugs.gnu.org
Subject: Re: bug#38804: Samsung Chromebook 3
Date: Tue, 31 Dec 2019 10:28:13 -0600
[Message part 1 (text/plain, inline)]
On 12/31/2019 06:49 AM, Danny Milosavljevic wrote:
> If you want, try connecting an usb keyboard in order to find out.  It might
> work.

Also, I will have to unplug the Wi-Fi adapter to plug in the keyboard.
There are only two USB ports, and one of them is the installation medium.

I guess I won't need Wi-Fi on a laptop that doesn't even have a
functioning keyboard.  Although I've heard of RMS using a USB keyboard
on top of his laptop because the default one was proprietary.  (Isn't
that why he used a keyboard on top of his OLPC?)

-- 
Caleb Herbert
KE0VVT
816-892-9669
https://bluehome.net/csh
[csh.vcf (text/x-vcard, attachment)]
[signature.asc (application/pgp-signature, attachment)]

This bug report was last modified 4 years and 116 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.