[opensuse-arm] Problem with openSUSE Factory on samsung chromebook (snow)
Hi, Current Factory image does boot on Chromebook (repartition append) but display stay black. I have no serial cable for this laptop, so I cannot debug further. Is there anyone who could have a look, please? I sent SR #290617 to fix 2nd boot when booting from SD. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 13.03.2015 um 09:26 schrieb Guillaume Gardet <guillaume.gardet@free.fr>:
Hi,
Current Factory image does boot on Chromebook (repartition append) but display stay black. I have no serial cable for this laptop,
So if repartitioning happened that means the system should be up and running. Could you just plug in a usb ethernet dongle and ssh in? Alex
so I cannot debug further. Is there anyone who could have a look, please?
I sent SR #290617 to fix 2nd boot when booting from SD.
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 13/03/2015 15:51, Alexander Graf a écrit :
Am 13.03.2015 um 09:26 schrieb Guillaume Gardet <guillaume.gardet@free.fr>:
Hi,
Current Factory image does boot on Chromebook (repartition append) but display stay black. I have no serial cable for this laptop, So if repartitioning happened that means the system should be up and running. Could you just plug in a usb ethernet dongle and ssh in?
I have no USB-Ethernet dongle. I should buy one. Guillaume
Alex
so I cannot debug further. Is there anyone who could have a look, please?
I sent SR #290617 to fix 2nd boot when booting from SD.
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Am 13.03.2015 um 15:26 schrieb Guillaume Gardet:
Current Factory image does boot on Chromebook (repartition append) but display stay black. I have no serial cable for this laptop, so I cannot debug further. Is there anyone who could have a look, please?
There's a known DRM issue reported on linux-samsung-soc list. I have the same problem on my HP Chromebook 11 with linux-next - I can ssh into it, but dmesg has not been telling. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 14/03/2015 12:20, Andreas Färber a écrit :
Hi,
Am 13.03.2015 um 15:26 schrieb Guillaume Gardet:
Current Factory image does boot on Chromebook (repartition append) but display stay black. I have no serial cable for this laptop, so I cannot debug further. Is there anyone who could have a look, please? There's a known DRM issue reported on linux-samsung-soc list. I have the same problem on my HP Chromebook 11 with linux-next - I can ssh into it, but dmesg has not been telling.
Thanks for information. Any pointers to ML archives to follow the thread? Guillaume
Regards, Andreas
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 16.03.2015 um 14:00 schrieb Guillaume Gardet:
Le 14/03/2015 12:20, Andreas Färber a écrit :
Am 13.03.2015 um 15:26 schrieb Guillaume Gardet:
Current Factory image does boot on Chromebook (repartition append) but display stay black. I have no serial cable for this laptop, so I cannot debug further. Is there anyone who could have a look, please? There's a known DRM issue reported on linux-samsung-soc list. I have the same problem on my HP Chromebook 11 with linux-next - I can ssh into it, but dmesg has not been telling.
Thanks for information.
Any pointers to ML archives to follow the thread?
Javier just pointed me to the following new workaround: http://article.gmane.org/gmane.linux.ports.arm.kernel/400290/ It helps initially, but the screensaver can still turn it off. As alternative, pd_ignore_unused is a bootargs option to try. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hello Guillaume, I confirm that build 269 of factory chromebook image now start to boot from sdcard. I have serial console on my chromebook snow, but as default kernel have no serial console enabled, last thing i saw in serial output is starting kernel string. Here is full log i captured http://paste.opensuse.org/44607835 As chromebook images still use contrib repo maybe we can enable serial console output in its kernel-default config? --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Fri, Mar 13, 2015 at 5:26 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Current Factory image does boot on Chromebook (repartition append) but display stay black. I have no serial cable for this laptop, so I cannot debug further. Is there anyone who could have a look, please?
I sent SR #290617 to fix 2nd boot when booting from SD.
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 14/03/2015 19:50, Misha Komarovsky a écrit :
Hello Guillaume, I confirm that build 269 of factory chromebook image now start to boot from sdcard. I have serial console on my chromebook snow, but as default kernel have no serial console enabled, last thing i saw in serial output is starting kernel string. Here is full log i captured http://paste.opensuse.org/44607835 As chromebook images still use contrib repo maybe we can enable serial console output in its kernel-default config?
You can add a "console=ttySAC3" to your bootargs in boot script, you should get more details. ;) Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Fri, Mar 13, 2015 at 5:26 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Current Factory image does boot on Chromebook (repartition append) but display stay black. I have no serial cable for this laptop, so I cannot debug further. Is there anyone who could have a look, please?
I sent SR #290617 to fix 2nd boot when booting from SD.
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hello Guillaume, I thought CONFIG_DEBUG_LL in mainline kernels is device specific option and not enabled in openSUSE default kernels? Or chromebook serial console is independent from DEBUG_LL? --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Mon, Mar 16, 2015 at 4:06 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 14/03/2015 19:50, Misha Komarovsky a écrit :
Hello Guillaume, I confirm that build 269 of factory chromebook image now start to boot from sdcard. I have serial console on my chromebook snow, but as default kernel have no serial console enabled, last thing i saw in serial output is starting kernel string. Here is full log i captured http://paste.opensuse.org/44607835 As chromebook images still use contrib repo maybe we can enable serial console output in its kernel-default config?
You can add a "console=ttySAC3" to your bootargs in boot script, you should get more details. ;)
Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Fri, Mar 13, 2015 at 5:26 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Current Factory image does boot on Chromebook (repartition append) but display stay black. I have no serial cable for this laptop, so I cannot debug further. Is there anyone who could have a look, please?
I sent SR #290617 to fix 2nd boot when booting from SD.
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 16.03.15 08:18, Misha Komarovsky wrote:
Hello Guillaume, I thought CONFIG_DEBUG_LL in mainline kernels is device specific option and not enabled in openSUSE default kernels? Or chromebook serial console is independent from DEBUG_LL?
You only need DEBUG_LL for the early console messages. Real output from the kernel and a shell go via the normal serial framework which don't need DEBUG_LL. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hello, Yes, i was wrong. Here is kernel log http://paste.opensuse.org/57334127 I will also test device tree fix which Andreas posted today later. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Mon, Mar 16, 2015 at 7:23 PM, Alexander Graf <agraf@suse.de> wrote:
On 16.03.15 08:18, Misha Komarovsky wrote:
Hello Guillaume, I thought CONFIG_DEBUG_LL in mainline kernels is device specific option and not enabled in openSUSE default kernels? Or chromebook serial console is independent from DEBUG_LL?
You only need DEBUG_LL for the early console messages. Real output from the kernel and a shell go via the normal serial framework which don't need DEBUG_LL.
Alex
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Misha, Am 16.03.2015 um 19:44 schrieb Misha Komarovsky:
Here is kernel log http://paste.opensuse.org/57334127
Looks like ptn3460 still/again has problems when built as a module. The Samsung developers mostly use exynos_defconfig (with everything built-in), so one of you* needs to investigate and post a patch to fix this. Changing our config to "needlessly" build in stuff is just papering over such bugs.
I will also test device tree fix which Andreas posted today later.
Unlikely to help if the eDP-LVDS bridge is not initializing properly. pd_ignore_unused did not help on my device btw. Regards, Andreas * My Spring has ps8622 instead and is not yet fully upstream. -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Yes patch you posted is against linux-next and out Factory is 3.19.1 which don't include power domain yet. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Tue, Mar 17, 2015 at 1:10 AM, Andreas Färber <afaerber@suse.de> wrote:
Hi Misha,
Am 16.03.2015 um 19:44 schrieb Misha Komarovsky:
Here is kernel log http://paste.opensuse.org/57334127
Looks like ptn3460 still/again has problems when built as a module.
The Samsung developers mostly use exynos_defconfig (with everything built-in), so one of you* needs to investigate and post a patch to fix this. Changing our config to "needlessly" build in stuff is just papering over such bugs.
I will also test device tree fix which Andreas posted today later.
Unlikely to help if the eDP-LVDS bridge is not initializing properly.
pd_ignore_unused did not help on my device btw.
Regards, Andreas
* My Spring has ps8622 instead and is not yet fully upstream.
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Forgot to say that overall system work fine i can login and work from serial console. Black screen and annoying exynos-cpufreq spam to syslog is only current issues on chromebook snow. Regarding exynos-cpufreq i found this thread which look same http://www.spinics.net/lists/arm-kernel/msg378589.html, but module mentioned in it, i2c_s3c2410, wont prevent exynos-cpufreq spam. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Tue, Mar 17, 2015 at 1:57 AM, Misha Komarovsky <zombah@gmail.com> wrote:
Yes patch you posted is against linux-next and out Factory is 3.19.1 which don't include power domain yet. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Tue, Mar 17, 2015 at 1:10 AM, Andreas Färber <afaerber@suse.de> wrote:
Hi Misha,
Am 16.03.2015 um 19:44 schrieb Misha Komarovsky:
Here is kernel log http://paste.opensuse.org/57334127
Looks like ptn3460 still/again has problems when built as a module.
The Samsung developers mostly use exynos_defconfig (with everything built-in), so one of you* needs to investigate and post a patch to fix this. Changing our config to "needlessly" build in stuff is just papering over such bugs.
I will also test device tree fix which Andreas posted today later.
Unlikely to help if the eDP-LVDS bridge is not initializing properly.
pd_ignore_unused did not help on my device btw.
Regards, Andreas
* My Spring has ps8622 instead and is not yet fully upstream.
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (4)
-
Alexander Graf -
Andreas Färber -
Guillaume Gardet -
Misha Komarovsky