subject:"\[opensuse\-arm\] Samsung Chromebook \(Snow\) status\?"

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

2017-11-20 Thread Daniel Bischof

Hi,

On Mon, 20 Nov 2017, Guillaume Gardet wrote:

Le 18/11/2017 à 21:12, Misha Komarovskiy a écrit :

On Sat, Oct 7, 2017 at 3:06 PM, Daniel Bischof
wrote:

On Mon, 21 Aug 2017, Misha Komarovskiy wrote:

On Sun, Aug 20, 2017 at 3:09 PM, Daniel Bischof
wrote:

On Mon, 14 Aug 2017, msuchanek wrote:

On Sat, 12 Aug 2017 14:16:51 +0200 (CEST) Daniel Bischof
wrote:

I tried
openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1
recently, but it just beeps and kicks me back to the boot screen
immediately. No messages on screen, partition resizing, etc.

Any hints? Some cgpt magic I could try from ChromeOS perhaps?

You can try installing upstream u-boot following the chainload
steps deteailed in several places on the interwebs - eg here
http://chrodyssey.blogspot.cz/2015/04/the-bootloader-chained.html

The current u-boot supports display on Snow but the EFI GOP
emulation (which the Tumbleweed image would use if it booted) is
broken.

It probably does not boot because the loader is missing or not
marked as bootable or you did not enable USB boot on the
chromebook.

The developer mode on current versions of ChromeOS has more
features than it used to but is also more flaky - it seems
services tend to stop working randomly and currently I Cannot boot
at all after the devmode installation fell apart.

thanks to both of you (Michal and Misha) for your answers, nice to
hear that you didn't give up on Snow, even since it is no longer
available for purchase.

I partly revived my chromebook snow and i was able to test current
Tumbleweed image
openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.08.13-Build1.6.raw.xz
I found that factory U-Boot for some reason don't like our
chainloading U-BOOT partition with message:

GptNextKernelEntry looking at new prio partition 1
GptNextKernelEntry s1 t5 p10
GptNextKernelEntry likes partition 1
Found kernel entry at 2048 size 409604
Not a valid verified boot key block.
Verifying key block signature failed.
Not a valid verified boot key block.
Verifying key block hash failed.
Marking kernel as invalid.
GptNextKernelEntry looking at new prio partition 1
GptNextKernelEntry s1 t5 p10
GptNextKernelEntry no more kernels

i will try to investigate further why this happen. [...]

i tried
openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.10.02-Build1.1
today and still no luck. Did you dig into this already? I'm not
skilled enough to be helpful in this stage, i'm afraid...

Guillaume fixed chromebook snow images you can try current TW build

http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Chromebook/images/openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.11.17-Build2.2.raw.xz
It boots fine here, i only expirienced hard freeze on first boot which
chanhes partition setup, here is fault output to serial uart
http://paste.opensuse.org/98361543 If it wont reboot for too long on
first boot you probably also caught this fault just reboot by power
key, second boot is fine.

It seems that Build2.4 has video output broken. I guess this is due to
new 4.14.0 kernel? Unfortunately, I do not have any serial access on my
chromebook. Could you have a look, since it seems you have serial on
your chromebook. Or anyone else?

I tried 2017.11.17-Build2.4 today: It boots (yay!) and resizes the file
system. After "Starting the kernel" the screen goes and stays black. So,
yes, video output broken seems likely. I will try again as soon as a new
build is available.

Thank you very much, both of you.

Best regards,

--Daniel.

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

2017-11-20 Thread Guillaume Gardet

Le 20/11/2017 à 15:19, Misha Komarovskiy a écrit :

Hello Guillaume,

On Mon, Nov 20, 2017 at 4:51 PM, Guillaume Gardet
wrote:

Le 18/11/2017 à 21:12, Misha Komarovskiy a écrit :

Hello Daniel,

On Sat, Oct 7, 2017 at 3:06 PM, Daniel Bischof
wrote:

Hi,

On Mon, 21 Aug 2017, Misha Komarovskiy wrote:

On Sun, Aug 20, 2017 at 3:09 PM, Daniel Bischof
wrote:

On Mon, 14 Aug 2017, msuchanek wrote:

On Sat, 12 Aug 2017 14:16:51 +0200 (CEST) Daniel Bischof
wrote:

I tried
openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1
recently,
but it just beeps and kicks me back to the boot screen immediately.
No
messages on screen, partition resizing, etc.

Any hints? Some cgpt magic I could try from ChromeOS perhaps?

You can try installing upstream u-boot following the chainload steps
deteailed in several places on the interwebs - eg here
http://chrodyssey.blogspot.cz/2015/04/the-bootloader-chained.html

The current u-boot supports display on Snow but the EFI GOP emulation
(which the Tumbleweed image would use if it booted) is broken.

It probably does not boot because the loader is missing or not marked
as
bootable or you did not enable USB boot on the chromebook.

The developer mode on current versions of ChromeOS has more features
than it used to but is also more flaky - it seems services tend to
stop
working randomly and currently I Cannot boot at all after the devmode
installation fell apart.

thanks to both of you (Michal and Misha) for your answers, nice to hear
that you didn't give up on Snow, even since it is no longer available
for
purchase.

I partly revived my chromebook snow and i was able to test current
Tumbleweed image

openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.08.13-Build1.6.raw.xz I
found that factory U-Boot for some reason don't like our chainloading
U-BOOT
partition with message:

i will try to investigate further why this happen. [...]

i tried
openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.10.02-Build1.1
today and still no luck. Did you dig into this already? I'm not skilled
enough to be helpful in this stage, i'm afraid...

Guillaume fixed chromebook snow images you can try current TW build

http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Chromebook/images/openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.11.17-Build2.2.raw.xz
It boots fine here, i only expirienced hard freeze on first boot which
chanhes partition setup, here is fault output to serial
uart http://paste.opensuse.org/98361543
If it wont reboot for too long on first boot you probably also caught
this fault just reboot by power key, second boot is fine.

It seems that Build2.4 has video output broken. I guess this is due to new
4.14.0 kernel?
Unfortunately, I do not have any serial access on my chromebook. Could you
have a look, since it seems you have serial on your chromebook.
Or anyone else?

There is hard freeze near 4 of 5 times, here is output from serial
http://paste.opensuse.org/96574215
Maybe misconfig in our kernel config or regression in 4.14 need to investigate.

Thanks. I sent an e-mail to opensuse-kernel ML to check if they have any idea.

Guillaume

Best regards,

--D.
---
Daniel Bischof
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

2017-11-20 Thread Misha Komarovskiy

Hello Guillaume,

On Mon, Nov 20, 2017 at 4:51 PM, Guillaume Gardet
 wrote:
>
>
> Le 18/11/2017 à 21:12, Misha Komarovskiy a écrit :
>>
>> Hello Daniel,
>>
>> On Sat, Oct 7, 2017 at 3:06 PM, Daniel Bischof 
>> wrote:
>>>
>>> Hi,
>>>
>>> On Mon, 21 Aug 2017, Misha Komarovskiy wrote:
>>>
 On Sun, Aug 20, 2017 at 3:09 PM, Daniel Bischof 
 wrote:
>
> On Mon, 14 Aug 2017, msuchanek wrote:
>
>> On Sat, 12 Aug 2017 14:16:51 +0200 (CEST) Daniel Bischof
>>  wrote:
>>
>>> I tried
>>> openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1
>>> recently,
>>> but it just beeps and kicks me back to the boot screen immediately.
>>> No
>>> messages on screen, partition resizing, etc.
>>>
>>> Any hints? Some cgpt magic I could try from ChromeOS perhaps?
>>
>>
>> You can try installing upstream u-boot following the chainload steps
>> deteailed in several places on the interwebs - eg here
>> http://chrodyssey.blogspot.cz/2015/04/the-bootloader-chained.html
>>
>> The current u-boot supports display on Snow but the EFI GOP emulation
>> (which the Tumbleweed image would use if it booted) is broken.
>>
>> It probably does not boot because the loader is missing or not marked
>> as
>> bootable or you did not enable USB boot on the chromebook.
>>
>> The developer mode on current versions of ChromeOS has more features
>> than it used to but is also more flaky - it seems services tend to
>> stop
>> working randomly and currently I Cannot boot at all after the devmode
>> installation fell apart.
>
>
> thanks to both of you (Michal and Misha) for your answers, nice to hear
> that you didn't give up on Snow, even since it is no longer available
> for
> purchase.


 I partly revived my chromebook snow and i was able to test current
 Tumbleweed image

 openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.08.13-Build1.6.raw.xz I
 found that factory U-Boot for some reason don't like our chainloading
 U-BOOT
 partition with message:

 GptNextKernelEntry looking at new prio partition 1
 GptNextKernelEntry s1 t5 p10
 GptNextKernelEntry likes partition 1
 Found kernel entry at 2048 size 409604
 Not a valid verified boot key block.
 Verifying key block signature failed.
 Not a valid verified boot key block.
 Verifying key block hash failed.
 Marking kernel as invalid.
 GptNextKernelEntry looking at new prio partition 1
 GptNextKernelEntry s1 t5 p10
 GptNextKernelEntry no more kernels

 i will try to investigate further why this happen. [...]
>>>
>>>
>>> i tried
>>> openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.10.02-Build1.1
>>> today and still no luck. Did you dig into this already? I'm not skilled
>>> enough to be helpful in this stage, i'm afraid...
>>>
>> Guillaume fixed chromebook snow images you can try current TW build
>>
>> http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Chromebook/images/openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.11.17-Build2.2.raw.xz
>> It boots fine here, i only expirienced hard freeze on first boot which
>> chanhes partition setup, here is fault output to serial
>> uart http://paste.opensuse.org/98361543
>> If it wont reboot for too long on first boot you probably also caught
>> this fault just reboot by power key, second boot is fine.
>
>
> It seems that Build2.4 has video output broken. I guess this is due to new
> 4.14.0 kernel?
> Unfortunately, I do not have any serial access on my chromebook. Could you
> have a look, since it seems you have serial on your chromebook.
> Or anyone else?

There is hard freeze near 4 of 5 times, here is output from serial
http://paste.opensuse.org/96574215
Maybe misconfig in our kernel config or regression in 4.14 need to investigate.

>
>
> Guillaume
>
>
>
>>> Best regards,
>>>
>>> --D.
>>> ---
>>> Daniel Bischof 
>>> --
>>> To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
>>> To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
>>>
>>
>>
>



-- 
Best Regards,
Misha Komarovskiy
zombahatgmaildotcom
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

2017-11-20 Thread Guillaume Gardet

Le 18/11/2017 à 21:12, Misha Komarovskiy a écrit :

Hello Daniel,

On Sat, Oct 7, 2017 at 3:06 PM, Daniel Bischof wrote:

Hi,

On Mon, 21 Aug 2017, Misha Komarovskiy wrote:

On Sun, Aug 20, 2017 at 3:09 PM, Daniel Bischof
wrote:

On Mon, 14 Aug 2017, msuchanek wrote:

On Sat, 12 Aug 2017 14:16:51 +0200 (CEST) Daniel Bischof
wrote:

I tried
openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1 recently,
but it just beeps and kicks me back to the boot screen immediately. No
messages on screen, partition resizing, etc.

Any hints? Some cgpt magic I could try from ChromeOS perhaps?

You can try installing upstream u-boot following the chainload steps
deteailed in several places on the interwebs - eg here
http://chrodyssey.blogspot.cz/2015/04/the-bootloader-chained.html

The current u-boot supports display on Snow but the EFI GOP emulation
(which the Tumbleweed image would use if it booted) is broken.

It probably does not boot because the loader is missing or not marked as
bootable or you did not enable USB boot on the chromebook.

The developer mode on current versions of ChromeOS has more features
than it used to but is also more flaky - it seems services tend to stop
working randomly and currently I Cannot boot at all after the devmode
installation fell apart.

thanks to both of you (Michal and Misha) for your answers, nice to hear
that you didn't give up on Snow, even since it is no longer available for
purchase.

I partly revived my chromebook snow and i was able to test current
Tumbleweed image
openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.08.13-Build1.6.raw.xz I
found that factory U-Boot for some reason don't like our chainloading U-BOOT
partition with message:

i will try to investigate further why this happen. [...]

i tried openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.10.02-Build1.1
today and still no luck. Did you dig into this already? I'm not skilled
enough to be helpful in this stage, i'm afraid...

Guillaume fixed chromebook snow images you can try current TW build
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Chromebook/images/openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.11.17-Build2.2.raw.xz
It boots fine here, i only expirienced hard freeze on first boot which
chanhes partition setup, here is fault output to serial
uart http://paste.opensuse.org/98361543
If it wont reboot for too long on first boot you probably also caught
this fault just reboot by power key, second boot is fine.

It seems that Build2.4 has video output broken. I guess this is due to new
4.14.0 kernel?
Unfortunately, I do not have any serial access on my chromebook. Could you have
a look, since it seems you have serial on your chromebook.
Or anyone else?

Guillaume

Best regards,

--D.
---
Daniel Bischof
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

2017-11-18 Thread Misha Komarovskiy

Hello Daniel,

On Sat, Oct 7, 2017 at 3:06 PM, Daniel Bischof  wrote:
> Hi,
>
> On Mon, 21 Aug 2017, Misha Komarovskiy wrote:
>
>> On Sun, Aug 20, 2017 at 3:09 PM, Daniel Bischof 
>> wrote:
>>>
>>> On Mon, 14 Aug 2017, msuchanek wrote:
>>>
 On Sat, 12 Aug 2017 14:16:51 +0200 (CEST) Daniel Bischof
  wrote:

> I tried
> openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1 
> recently,
> but it just beeps and kicks me back to the boot screen immediately. No
> messages on screen, partition resizing, etc.
>
> Any hints? Some cgpt magic I could try from ChromeOS perhaps?


 You can try installing upstream u-boot following the chainload steps
 deteailed in several places on the interwebs - eg here
 http://chrodyssey.blogspot.cz/2015/04/the-bootloader-chained.html

 The current u-boot supports display on Snow but the EFI GOP emulation
 (which the Tumbleweed image would use if it booted) is broken.

 It probably does not boot because the loader is missing or not marked as
 bootable or you did not enable USB boot on the chromebook.

 The developer mode on current versions of ChromeOS has more features
 than it used to but is also more flaky - it seems services tend to stop
 working randomly and currently I Cannot boot at all after the devmode
 installation fell apart.
>>>
>>>
>>> thanks to both of you (Michal and Misha) for your answers, nice to hear
>>> that you didn't give up on Snow, even since it is no longer available for
>>> purchase.
>>
>>
>> I partly revived my chromebook snow and i was able to test current
>> Tumbleweed image
>> openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.08.13-Build1.6.raw.xz I
>> found that factory U-Boot for some reason don't like our chainloading U-BOOT
>> partition with message:
>>
>> GptNextKernelEntry looking at new prio partition 1
>> GptNextKernelEntry s1 t5 p10
>> GptNextKernelEntry likes partition 1
>> Found kernel entry at 2048 size 409604
>> Not a valid verified boot key block.
>> Verifying key block signature failed.
>> Not a valid verified boot key block.
>> Verifying key block hash failed.
>> Marking kernel as invalid.
>> GptNextKernelEntry looking at new prio partition 1
>> GptNextKernelEntry s1 t5 p10
>> GptNextKernelEntry no more kernels
>>
>> i will try to investigate further why this happen. [...]
>
>
> i tried openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.10.02-Build1.1
> today and still no luck. Did you dig into this already? I'm not skilled
> enough to be helpful in this stage, i'm afraid...
>

Guillaume fixed chromebook snow images you can try current TW build
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Chromebook/images/openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.11.17-Build2.2.raw.xz
It boots fine here, i only expirienced hard freeze on first boot which
chanhes partition setup, here is fault output to serial
uart http://paste.opensuse.org/98361543
If it wont reboot for too long on first boot you probably also caught
this fault just reboot by power key, second boot is fine.



>
> Best regards,
>
> --D.
> ---
> Daniel Bischof 
> --
> To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
> To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
>



-- 
Best Regards,
Misha Komarovskiy
zombahatgmaildotcom
-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

2017-10-07 Thread Daniel Bischof


Hi,

On Mon, 21 Aug 2017, Misha Komarovskiy wrote:


On Sun, Aug 20, 2017 at 3:09 PM, Daniel Bischof  wrote:

On Mon, 14 Aug 2017, msuchanek wrote:


On Sat, 12 Aug 2017 14:16:51 +0200 (CEST) Daniel Bischof
 wrote:

I tried 
openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1 
recently, but it just beeps and kicks me back to the boot screen 
immediately. No messages on screen, partition resizing, etc.


Any hints? Some cgpt magic I could try from ChromeOS perhaps?


You can try installing upstream u-boot following the chainload steps 
deteailed in several places on the interwebs - eg here 
http://chrodyssey.blogspot.cz/2015/04/the-bootloader-chained.html


The current u-boot supports display on Snow but the EFI GOP emulation 
(which the Tumbleweed image would use if it booted) is broken.


It probably does not boot because the loader is missing or not marked 
as bootable or you did not enable USB boot on the chromebook.


The developer mode on current versions of ChromeOS has more features 
than it used to but is also more flaky - it seems services tend to 
stop working randomly and currently I Cannot boot at all after the 
devmode installation fell apart.


thanks to both of you (Michal and Misha) for your answers, nice to hear 
that you didn't give up on Snow, even since it is no longer available 
for purchase.


I partly revived my chromebook snow and i was able to test current 
Tumbleweed image 
openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.08.13-Build1.6.raw.xz 
I found that factory U-Boot for some reason don't like our chainloading 
U-BOOT partition with message:


GptNextKernelEntry looking at new prio partition 1
GptNextKernelEntry s1 t5 p10
GptNextKernelEntry likes partition 1
Found kernel entry at 2048 size 409604
Not a valid verified boot key block.
Verifying key block signature failed.
Not a valid verified boot key block.
Verifying key block hash failed.
Marking kernel as invalid.
GptNextKernelEntry looking at new prio partition 1
GptNextKernelEntry s1 t5 p10
GptNextKernelEntry no more kernels

i will try to investigate further why this happen. [...]


i tried openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.10.02-Build1.1 
today and still no luck. Did you dig into this already? I'm not skilled 
enough to be helpful in this stage, i'm afraid...



Best regards,

--D.
---
Daniel Bischof 
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

2017-08-20 Thread Misha Komarovskiy

Hello Daniel,

On Sun, Aug 20, 2017 at 3:09 PM, Daniel Bischof  wrote:
> Hi,
>
> On Mon, 14 Aug 2017, msuchanek wrote:
>
>> On Sat, 12 Aug 2017 14:16:51 +0200 (CEST) Daniel Bischof
>>  wrote:
>>
>>> I tried
>>> openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1 recently,
>>> but it just beeps and kicks me back to the boot screen immediately. No
>>> messages on screen, partition resizing, etc.
>>>
>>> Any hints? Some cgpt magic I could try from ChromeOS perhaps?
>>
>>
>> You can try installing upstream u-boot following the chainload steps
>> deteailed in several places on the interwebs - eg here
>> http://chrodyssey.blogspot.cz/2015/04/the-bootloader-chained.html
>>
>> The current u-boot supports display on Snow but the EFI GOP emulation
>> (which the Tumbleweed image would use if it booted) is broken.
>>
>> It probably does not boot because the loader is missing or not marked as
>> bootable or you did not enable USB boot on the chromebook.
>>
>> The developer mode on current versions of ChromeOS has more features than
>> it used to but is also more flaky - it seems services tend to stop working
>> randomly and currently I Cannot boot at all after the devmode installation
>> fell apart.
>
>
> thanks to both of you (Michal and Misha) for your answers, nice to hear that
> you didn't give up on Snow, even since it is no longer available for
> purchase.
>

I partly revived my chromebook snow and i was able to test current
Tumbleweed image
openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.08.13-Build1.6.raw.xz
I found that factory U-Boot for some reason don't like our
chainloading U-BOOT partition with message:

GptNextKernelEntry looking at new prio partition 1
GptNextKernelEntry s1 t5 p10
GptNextKernelEntry likes partition 1
Found kernel entry at 2048 size 409604
Not a valid verified boot key block.
Verifying key block signature failed.
Not a valid verified boot key block.
Verifying key block hash failed.
Marking kernel as invalid.
GptNextKernelEntry looking at new prio partition 1
GptNextKernelEntry s1 t5 p10
GptNextKernelEntry no more kernels

i will try to investigate further why this happen.

> I played around a little with the broken image, but failed to recompile
> u-boot as described in the above link - need to dig into this.
>
> I switched (temporarily, i hope) to archlinuxARM [1], which works fine (all
> HW incl. 2d acceleration), but it is uncomfortable for me, since i've never
> used archlinux before. Kali (Debian-based) works, too, but has no 2d
> acceleration. Both appear to use the ChromeOS-kernel.
>
> I don't use ChromeOS, but keep it up-to-date via guest mode - maybe a
> not-so-good idea afterwards...
>
> [1] https://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook
>
>
> Best regards,
>
> --D.
> ---
> Daniel Bischof 
> --
> To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
> To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
>



-- 
Best Regards,
Misha Komarovskiy
zombahatgmaildotcom
-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

2017-08-20 Thread Daniel Bischof


Hi,

On Mon, 14 Aug 2017, msuchanek wrote:


On Sat, 12 Aug 2017 14:16:51 +0200 (CEST) Daniel Bischof 
 wrote:

I tried 
openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1 
recently, but it just beeps and kicks me back to the boot screen 
immediately. No messages on screen, partition resizing, etc.


Any hints? Some cgpt magic I could try from ChromeOS perhaps?


You can try installing upstream u-boot following the chainload steps 
deteailed in several places on the interwebs - eg here 
http://chrodyssey.blogspot.cz/2015/04/the-bootloader-chained.html


The current u-boot supports display on Snow but the EFI GOP emulation 
(which the Tumbleweed image would use if it booted) is broken.


It probably does not boot because the loader is missing or not marked as 
bootable or you did not enable USB boot on the chromebook.


The developer mode on current versions of ChromeOS has more features 
than it used to but is also more flaky - it seems services tend to stop 
working randomly and currently I Cannot boot at all after the devmode 
installation fell apart.


thanks to both of you (Michal and Misha) for your answers, nice to hear 
that you didn't give up on Snow, even since it is no longer available for 
purchase.


I played around a little with the broken image, but failed to recompile 
u-boot as described in the above link - need to dig into this.


I switched (temporarily, i hope) to archlinuxARM [1], which works fine 
(all HW incl. 2d acceleration), but it is uncomfortable for me, since i've 
never used archlinux before. Kali (Debian-based) works, too, but has no 2d 
acceleration. Both appear to use the ChromeOS-kernel.


I don't use ChromeOS, but keep it up-to-date via guest mode - maybe a 
not-so-good idea afterwards...


[1] https://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook


Best regards,

--D.
---
Daniel Bischof 
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

2017-08-14 Thread Misha Komarovskiy

Hello Daniel,

On Sat, Aug 12, 2017 at 3:16 PM, Daniel Bischof  wrote:
> Hi,
>
> I tried openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1
> recently, but it just beeps and kicks me back to the boot screen
> immediately. No messages on screen, partition resizing, etc.
>

Last version i tested was
openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.06.10-Build2.10.raw.xz,
it worked fine except outdated armsoc driver.
But after that i updated vboot package to newer version to play with
newer chromebooks,
maybe it is broken with snow, i will try newer builds to find out.

> Any hints? Some cgpt magic I could try from ChromeOS perhaps?
>

You can try to boot old openSUSE 13.1 version to find out that your
sdcard or usb flash is ok first, if yes try to rebuild chaniloading partition.

>
> Best regards, --D.
> --
> To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
> To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
>

-- 
Best Regards,
Misha Komarovskiy
zombahatgmaildotcom
-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

2017-08-13 Thread msuchanek

On Sat, 12 Aug 2017 14:16:51 +0200 (CEST)
Daniel Bischof  wrote:

> Hi,
> 
> I tried
> openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1
> recently, but it just beeps and kicks me back to the boot screen
> immediately. No messages on screen, partition resizing, etc.
> 
> Any hints? Some cgpt magic I could try from ChromeOS perhaps?

You can try installing upstream u-boot following the chainload steps
deteailed in several places on the interwebs - eg here
http://chrodyssey.blogspot.cz/2015/04/the-bootloader-chained.html

The current u-boot supports display on Snow but the EFI GOP emulation
(which the Tumbleweed image would use if it booted) is broken.

It probably does not boot because the loader is missing or not marked
as bootable or you did not enable USB boot on the chromebook.

The developer mode on current versions of ChromeOS has more features
than it used to but is also more flaky - it seems services tend to stop
working randomly and currently I Cannot boot at all after the devmode
installation fell apart.

HTH

Michal
-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

Re: [opensuse-arm] Samsung Chromebook (Snow) status?

10 matches

Site Navigation

Mail list logo

Footer information