[opensuse-arm] Samsung Chromebook current tumbleweed images
Hello, Just tried latest 316/318 Tumbleweed images for Samsung Chromebook and noticed that u-boot wont auto load boot.scr now and output contain alot errors about extlinux pxeboot. If i load boot.scr manualy, with ext2load mmc 1:2 0x50000000 boot.scr and then source 0x50000000 boot starts fine. Also lcd screen stays black after kernel start, probably some drm module still missing. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 19/07/2015 18:15, Misha Komarovskiy a écrit :
Hello, Just tried latest 316/318 Tumbleweed images for Samsung Chromebook and noticed that u-boot wont auto load boot.scr now and output contain alot errors about extlinux pxeboot. If i load boot.scr manualy, with ext2load mmc 1:2 0x50000000 boot.scr and then source 0x50000000 boot starts fine.
This is because our boot partition has no boot flag. :(
Also lcd screen stays black after kernel start, probably some drm module still missing.
Upstream kernel is broken. :( Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Am 20.07.2015 um 14:28 schrieb Guillaume Gardet:
Le 19/07/2015 18:15, Misha Komarovskiy a écrit :
Also lcd screen stays black after kernel start, probably some drm module still missing.
Upstream kernel is broken. :(
How did you test? Actually there's a known issue that the Exynos IOMMU support breaks graphics on the Chromebooks because they enable a framebuffer early in bootloaders, before Linux initializes the IOMMU. Since some other platforms do need the IOMMU, I fear that we're going to need a new kernel flavor... :/ Not sure if that can be scripted as lpae minus certain options? Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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 23/07/2015 14:16, Andreas Färber a écrit :
Hi,
Le 19/07/2015 18:15, Misha Komarovskiy a écrit :
Also lcd screen stays black after kernel start, probably some drm module still missing. Upstream kernel is broken. :( How did you test? Actually there's a known issue that the Exynos IOMMU support breaks graphics on the Chromebooks because they enable a
Am 20.07.2015 um 14:28 schrieb Guillaume Gardet: framebuffer early in bootloaders, before Linux initializes the IOMMU. Since some other platforms do need the IOMMU, I fear that we're going to need a new kernel flavor... :/ Not sure if that can be scripted as lpae minus certain options?
You mean that if we disable IOMMU in kernel, graphics are working fine? CONFIG_DRM_EXYNOS_IOMMU is enabled. Should we disable it for chromebooks? Maybe some config options compiled as module (which?) and blacklisted for chromebooks could be ok? Guillaume
Regards, Andreas
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 23.07.2015 um 14:22 schrieb Guillaume Gardet <guillaume.gardet@free.fr>:
Le 23/07/2015 14:16, Andreas Färber a écrit :
Hi,
Also lcd screen stays black after kernel start, probably some drm module still missing. Upstream kernel is broken. :( How did you test? Actually there's a known issue that the Exynos IOMMU support breaks graphics on the Chromebooks because they enable a
Am 20.07.2015 um 14:28 schrieb Guillaume Gardet: Le 19/07/2015 18:15, Misha Komarovskiy a écrit : framebuffer early in bootloaders, before Linux initializes the IOMMU. Since some other platforms do need the IOMMU, I fear that we're going to need a new kernel flavor... :/ Not sure if that can be scripted as lpae minus certain options?
You mean that if we disable IOMMU in kernel, graphics are working fine? CONFIG_DRM_EXYNOS_IOMMU is enabled. Should we disable it for chromebooks?
Considering that chromebooks are the only Exynos devices with an actual user base, whatever we need to do to enable those wins over other random Exynos garbage. So if all out takes is to disable the Exynos IOMMU I'm all for it. Alex
Maybe some config options compiled as module (which?) and blacklisted for chromebooks could be ok?
Guillaume
Regards, Andreas
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 23.07.2015 um 14:38 schrieb Alexander Graf:
Am 23.07.2015 um 14:22 schrieb Guillaume Gardet <guillaume.gardet@free.fr>: Le 23/07/2015 14:16, Andreas Färber a écrit :
Also lcd screen stays black after kernel start, probably some drm module still missing. Upstream kernel is broken. :( How did you test? Actually there's a known issue that the Exynos IOMMU support breaks graphics on the Chromebooks because they enable a
Am 20.07.2015 um 14:28 schrieb Guillaume Gardet: Le 19/07/2015 18:15, Misha Komarovskiy a écrit : framebuffer early in bootloaders, before Linux initializes the IOMMU. Since some other platforms do need the IOMMU, I fear that we're going to need a new kernel flavor... :/ Not sure if that can be scripted as lpae minus certain options?
You mean that if we disable IOMMU in kernel, graphics are working fine? CONFIG_DRM_EXYNOS_IOMMU is enabled. Should we disable it for chromebooks?
Considering that chromebooks are the only Exynos devices with an actual user base, whatever we need to do to enable those wins over other random Exynos garbage. So if all out takes is to disable the Exynos IOMMU I'm all for it.
Ehrm, given the amount of breakage and lateness of reports, I disagree that Chromebooks have any significant userbase on Tumbleweed. And depending on which options we need to disable, it may affect non-Exynos users as well, which I would strongly object to. Finding a way to blacklist (or patch?) things specifically for the Chromebooks, as Guillaume suggests, sounds much more appealing to me. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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
Am 23.07.2015 um 14:22 schrieb Guillaume Gardet:
Le 23/07/2015 14:16, Andreas Färber a écrit :
Le 19/07/2015 18:15, Misha Komarovskiy a écrit :
Also lcd screen stays black after kernel start, probably some drm module still missing. Upstream kernel is broken. :( How did you test? Actually there's a known issue that the Exynos IOMMU support breaks graphics on the Chromebooks because they enable a
Am 20.07.2015 um 14:28 schrieb Guillaume Gardet: framebuffer early in bootloaders, before Linux initializes the IOMMU. Since some other platforms do need the IOMMU, I fear that we're going to need a new kernel flavor... :/ Not sure if that can be scripted as lpae minus certain options?
You mean that if we disable IOMMU in kernel, graphics are working fine?
Hopefully yes. I did not test the latest kernel. It used to be that way ~3 months ago in linux-next.git (cf. linux-samsung-soc) and I doubt it's improved.
CONFIG_DRM_EXYNOS_IOMMU is enabled. Should we disable it for chromebooks?
Yes. But at some point that got auto-selected, so it may be necessary to disable IOMMU or the corresponding Exynos sub-option completely.
Maybe some config options compiled as module (which?) and blacklisted for chromebooks could be ok?
Maybe. Someone with a Chromebook needs to sit down and try. :) Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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
On 07/23/15 14:43, Andreas Färber wrote:
Am 23.07.2015 um 14:22 schrieb Guillaume Gardet:
Le 23/07/2015 14:16, Andreas Färber a écrit :
Le 19/07/2015 18:15, Misha Komarovskiy a écrit :
Also lcd screen stays black after kernel start, probably some drm module still missing. Upstream kernel is broken. :( How did you test? Actually there's a known issue that the Exynos IOMMU support breaks graphics on the Chromebooks because they enable a
Am 20.07.2015 um 14:28 schrieb Guillaume Gardet: framebuffer early in bootloaders, before Linux initializes the IOMMU. Since some other platforms do need the IOMMU, I fear that we're going to need a new kernel flavor... :/ Not sure if that can be scripted as lpae minus certain options? You mean that if we disable IOMMU in kernel, graphics are working fine? Hopefully yes. I did not test the latest kernel. It used to be that way ~3 months ago in linux-next.git (cf. linux-samsung-soc) and I doubt it's improved.
CONFIG_DRM_EXYNOS_IOMMU is enabled. Should we disable it for chromebooks? Yes. But at some point that got auto-selected, so it may be necessary to disable IOMMU or the corresponding Exynos sub-option completely.
Maybe some config options compiled as module (which?) and blacklisted for chromebooks could be ok? Maybe. Someone with a Chromebook needs to sit down and try. :)
Hrm, rather than disable it one way or another manually, couldn't we just blacklist it inside the kernel? I doubt that we can load iommu as module... Alex
Regards, Andreas
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 23.07.2015 um 15:12 schrieb Alexander Graf:
On 07/23/15 14:43, Andreas Färber wrote:
Am 23.07.2015 um 14:22 schrieb Guillaume Gardet:
Maybe some config options compiled as module (which?) and blacklisted for chromebooks could be ok? Maybe. Someone with a Chromebook needs to sit down and try. :)
Hrm, rather than disable it one way or another manually, couldn't we just blacklist it inside the kernel? I doubt that we can load iommu as module...
You mean as in patch the iommu probe code to check for "google,snow", "google,spring", etc.? Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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
Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>:
Am 23.07.2015 um 15:12 schrieb Alexander Graf:
On 07/23/15 14:43, Andreas Färber wrote:
Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: Maybe some config options compiled as module (which?) and blacklisted for chromebooks could be ok? Maybe. Someone with a Chromebook needs to sit down and try. :)
Hrm, rather than disable it one way or another manually, couldn't we just blacklist it inside the kernel? I doubt that we can load iommu as module...
You mean as in patch the iommu probe code to check for "google,snow", "google,spring", etc.?
For example - or remove the respective dt node. Or as a property to the IOMMU dt node... Alex
Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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, Maybe we can disable only Exynos IOMMU in configs for now? Same way it is disabled in current exynos_defconfig here https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... As i understand it is broken for all exynos devices not only snow. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> wrote:
Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>:
Am 23.07.2015 um 15:12 schrieb Alexander Graf:
On 07/23/15 14:43, Andreas Färber wrote:
Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: Maybe some config options compiled as module (which?) and blacklisted for chromebooks could be ok? Maybe. Someone with a Chromebook needs to sit down and try. :)
Hrm, rather than disable it one way or another manually, couldn't we just blacklist it inside the kernel? I doubt that we can load iommu as module...
You mean as in patch the iommu probe code to check for "google,snow", "google,spring", etc.?
For example - or remove the respective dt node. Or as a property to the IOMMU dt node...
Alex
Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 16/08/2015 21:59, Misha Komarovskiy a écrit :
Hello, Maybe we can disable only Exynos IOMMU in configs for now? Same way it is disabled in current exynos_defconfig here https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... As i understand it is broken for all exynos devices not only snow.
That is exactly what I would like to do since I read this thread: https://lkml.org/lkml/2015/2/17/163 Before submitting the idea here, I wanted to check if disabling Exynos IOMMU in config was enough. I had only time to test the exynos_defconfig with openSUSE kernel and it was OK (boot messages and login prompt displayed). Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> wrote:
Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>:
Am 23.07.2015 um 15:12 schrieb Alexander Graf:
On 07/23/15 14:43, Andreas Färber wrote:
Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: Maybe some config options compiled as module (which?) and blacklisted for chromebooks could be ok? Maybe. Someone with a Chromebook needs to sit down and try. :) Hrm, rather than disable it one way or another manually, couldn't we just blacklist it inside the kernel? I doubt that we can load iommu as module... You mean as in patch the iommu probe code to check for "google,snow", "google,spring", etc.? For example - or remove the respective dt node. Or as a property to the IOMMU dt node...
Alex
Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hello Guillaume, I tested both exynos_defconfig and multi_v7_defconfig, they work fine. But ill test lpae config without EXYNOS_IOMMU today and will report. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 16/08/2015 21:59, Misha Komarovskiy a écrit :
Hello, Maybe we can disable only Exynos IOMMU in configs for now? Same way it is disabled in current exynos_defconfig here
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... As i understand it is broken for all exynos devices not only snow.
That is exactly what I would like to do since I read this thread: https://lkml.org/lkml/2015/2/17/163
Before submitting the idea here, I wanted to check if disabling Exynos IOMMU in config was enough. I had only time to test the exynos_defconfig with openSUSE kernel and it was OK (boot messages and login prompt displayed).
Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> wrote:
Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>:
Am 23.07.2015 um 15:12 schrieb Alexander Graf:
On 07/23/15 14:43, Andreas Färber wrote: > > Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: > Maybe some config options compiled as module (which?) and blacklisted > for chromebooks could be ok?
Maybe. Someone with a Chromebook needs to sit down and try. :)
Hrm, rather than disable it one way or another manually, couldn't we just blacklist it inside the kernel? I doubt that we can load iommu as module...
You mean as in patch the iommu probe code to check for "google,snow", "google,spring", etc.?
For example - or remove the respective dt node. Or as a property to the IOMMU dt node...
Alex
Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, system boots with black screen same, then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel start to work without kernel panic. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Hello Guillaume, I tested both exynos_defconfig and multi_v7_defconfig, they work fine. But ill test lpae config without EXYNOS_IOMMU today and will report. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 16/08/2015 21:59, Misha Komarovskiy a écrit :
Hello, Maybe we can disable only Exynos IOMMU in configs for now? Same way it is disabled in current exynos_defconfig here
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... As i understand it is broken for all exynos devices not only snow.
That is exactly what I would like to do since I read this thread: https://lkml.org/lkml/2015/2/17/163
Before submitting the idea here, I wanted to check if disabling Exynos IOMMU in config was enough. I had only time to test the exynos_defconfig with openSUSE kernel and it was OK (boot messages and login prompt displayed).
Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> wrote:
Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>:
Am 23.07.2015 um 15:12 schrieb Alexander Graf: > > On 07/23/15 14:43, Andreas Färber wrote: >> >> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >> Maybe some config options compiled as module (which?) and blacklisted >> for chromebooks could be ok? > > Maybe. Someone with a Chromebook needs to sit down and try. :)
Hrm, rather than disable it one way or another manually, couldn't we just blacklist it inside the kernel? I doubt that we can load iommu as module...
You mean as in patch the iommu probe code to check for "google,snow", "google,spring", etc.?
For example - or remove the respective dt node. Or as a property to the IOMMU dt node...
Alex
Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 17/08/2015 13:30, Misha Komarovskiy a écrit :
Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, system boots with black screen same, then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel start to work without kernel panic.
Thanks for your tests. Could you add thoses modules to /etc/dracut.conf.d/exynos_modules.conf with the new line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung" and recreate initrd with dracut and check if it boots fine? If it does not work, try 'force_drivers+=' instead of 'add_drivers +=' and recreate initrd. Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Hello Guillaume, I tested both exynos_defconfig and multi_v7_defconfig, they work fine. But ill test lpae config without EXYNOS_IOMMU today and will report. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 16/08/2015 21:59, Misha Komarovskiy a écrit :
Hello, Maybe we can disable only Exynos IOMMU in configs for now? Same way it is disabled in current exynos_defconfig here
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... As i understand it is broken for all exynos devices not only snow.
That is exactly what I would like to do since I read this thread: https://lkml.org/lkml/2015/2/17/163
Before submitting the idea here, I wanted to check if disabling Exynos IOMMU in config was enough. I had only time to test the exynos_defconfig with openSUSE kernel and it was OK (boot messages and login prompt displayed).
Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> wrote:
Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>:
> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >> On 07/23/15 14:43, Andreas Färber wrote: >>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>> Maybe some config options compiled as module (which?) and blacklisted >>> for chromebooks could be ok? >> Maybe. Someone with a Chromebook needs to sit down and try. :) > Hrm, rather than disable it one way or another manually, couldn't we > just blacklist it inside the kernel? I doubt that we can load iommu as > module... You mean as in patch the iommu probe code to check for "google,snow", "google,spring", etc.? For example - or remove the respective dt node. Or as a property to the IOMMU dt node...
Alex
Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
I made test on already installed image. Connected with usb network dongle, cloned kernel-source git, made sequence-patch to 4.1 source, copied modified lpae kernel config then booted resulting kernel. This extra modules i tried to add to /etc/modules-load.d/ and system start fine this way without manual modprobing, but this is not same as dracut config as i understand. I never tried to branch kernel-source repo on obs to create custom config, i can make this test also if you can give me please some directions on how to properly create modified kernel branch. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 17/08/2015 13:30, Misha Komarovskiy a écrit :
Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, system boots with black screen same, then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel start to work without kernel panic.
Thanks for your tests. Could you add thoses modules to /etc/dracut.conf.d/exynos_modules.conf with the new line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
and recreate initrd with dracut and check if it boots fine?
If it does not work, try 'force_drivers+=' instead of 'add_drivers +=' and recreate initrd.
Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Hello Guillaume, I tested both exynos_defconfig and multi_v7_defconfig, they work fine. But ill test lpae config without EXYNOS_IOMMU today and will report. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 16/08/2015 21:59, Misha Komarovskiy a écrit :
Hello, Maybe we can disable only Exynos IOMMU in configs for now? Same way it is disabled in current exynos_defconfig here
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... As i understand it is broken for all exynos devices not only snow.
That is exactly what I would like to do since I read this thread: https://lkml.org/lkml/2015/2/17/163
Before submitting the idea here, I wanted to check if disabling Exynos IOMMU in config was enough. I had only time to test the exynos_defconfig with openSUSE kernel and it was OK (boot messages and login prompt displayed).
Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> wrote:
> Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>: > >> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>> >>> On 07/23/15 14:43, Andreas Färber wrote: >>>> >>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>> Maybe some config options compiled as module (which?) and >>>> blacklisted >>>> for chromebooks could be ok? >>> >>> Maybe. Someone with a Chromebook needs to sit down and try. :) >> >> Hrm, rather than disable it one way or another manually, couldn't we >> just blacklist it inside the kernel? I doubt that we can load iommu >> as >> module... > > You mean as in patch the iommu probe code to check for "google,snow", > "google,spring", etc.?
For example - or remove the respective dt node. Or as a property to the IOMMU dt node...
Alex
> Andreas > > -- > SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Felix Imendörffer, Jane Smithard, 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
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
You do not need to modify your kernel for that. Remove your /etc/modules-load.d/ file to get back in non-auto loading. Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the following line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung" Then recreate your initrd with: dracut -f and reboot. If it does not help, replace: add_drivers += "cros_ec_devs ptn3460 pwm-samsung" by: force_drivers += "cros_ec_devs ptn3460 pwm-samsung" Then recreate your initrd with: dracut -f and reboot. Guillaume Le 17/08/2015 14:04, Misha Komarovskiy a écrit :
I made test on already installed image. Connected with usb network dongle, cloned kernel-source git, made sequence-patch to 4.1 source, copied modified lpae kernel config then booted resulting kernel. This extra modules i tried to add to /etc/modules-load.d/ and system start fine this way without manual modprobing, but this is not same as dracut config as i understand.
I never tried to branch kernel-source repo on obs to create custom config, i can make this test also if you can give me please some directions on how to properly create modified kernel branch.
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 17/08/2015 13:30, Misha Komarovskiy a écrit :
Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, system boots with black screen same, then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel start to work without kernel panic.
Thanks for your tests. Could you add thoses modules to /etc/dracut.conf.d/exynos_modules.conf with the new line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
and recreate initrd with dracut and check if it boots fine?
If it does not work, try 'force_drivers+=' instead of 'add_drivers +=' and recreate initrd.
Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Hello Guillaume, I tested both exynos_defconfig and multi_v7_defconfig, they work fine. But ill test lpae config without EXYNOS_IOMMU today and will report. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 16/08/2015 21:59, Misha Komarovskiy a écrit :
Hello, Maybe we can disable only Exynos IOMMU in configs for now? Same way it is disabled in current exynos_defconfig here
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... As i understand it is broken for all exynos devices not only snow.
That is exactly what I would like to do since I read this thread: https://lkml.org/lkml/2015/2/17/163
Before submitting the idea here, I wanted to check if disabling Exynos IOMMU in config was enough. I had only time to test the exynos_defconfig with openSUSE kernel and it was OK (boot messages and login prompt displayed).
Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> wrote: > >> Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>: >> >>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>> Maybe some config options compiled as module (which?) and >>>>> blacklisted >>>>> for chromebooks could be ok? >>>> Maybe. Someone with a Chromebook needs to sit down and try. :) >>> Hrm, rather than disable it one way or another manually, couldn't we >>> just blacklist it inside the kernel? I doubt that we can load iommu >>> as >>> module... >> You mean as in patch the iommu probe code to check for "google,snow", >> "google,spring", etc.? > For example - or remove the respective dt node. Or as a property to > the > IOMMU dt node... > > Alex > >> Andreas >> >> -- >> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >> GF: Felix Imendörffer, Jane Smithard, 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 >
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Adding them with force_drivers do the trick. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
You do not need to modify your kernel for that. Remove your /etc/modules-load.d/ file to get back in non-auto loading.
Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the following line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
If it does not help, replace: add_drivers += "cros_ec_devs ptn3460 pwm-samsung" by: force_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
Guillaume
Le 17/08/2015 14:04, Misha Komarovskiy a écrit :
I made test on already installed image. Connected with usb network dongle, cloned kernel-source git, made sequence-patch to 4.1 source, copied modified lpae kernel config then booted resulting kernel. This extra modules i tried to add to /etc/modules-load.d/ and system start fine this way without manual modprobing, but this is not same as dracut config as i understand.
I never tried to branch kernel-source repo on obs to create custom config, i can make this test also if you can give me please some directions on how to properly create modified kernel branch.
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 17/08/2015 13:30, Misha Komarovskiy a écrit :
Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, system boots with black screen same, then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel start to work without kernel panic.
Thanks for your tests. Could you add thoses modules to /etc/dracut.conf.d/exynos_modules.conf with the new line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
and recreate initrd with dracut and check if it boots fine?
If it does not work, try 'force_drivers+=' instead of 'add_drivers +=' and recreate initrd.
Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Hello Guillaume, I tested both exynos_defconfig and multi_v7_defconfig, they work fine. But ill test lpae config without EXYNOS_IOMMU today and will report. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 16/08/2015 21:59, Misha Komarovskiy a écrit : > > Hello, > Maybe we can disable only Exynos IOMMU in configs for now? Same way > it > is disabled in current exynos_defconfig here > > > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... > As i understand it is broken for all exynos devices not only snow.
That is exactly what I would like to do since I read this thread: https://lkml.org/lkml/2015/2/17/163
Before submitting the idea here, I wanted to check if disabling Exynos IOMMU in config was enough. I had only time to test the exynos_defconfig with openSUSE kernel and it was OK (boot messages and login prompt displayed).
Guillaume
> --- > Best Regards, > Misha Komarovskiy > zombahatgmaildotcom > > > On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> > wrote: >> >> >>> Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>: >>> >>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>> >>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>> >>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>> Maybe some config options compiled as module (which?) and >>>>>> blacklisted >>>>>> for chromebooks could be ok? >>>>> >>>>> Maybe. Someone with a Chromebook needs to sit down and try. :) >>>> >>>> Hrm, rather than disable it one way or another manually, couldn't >>>> we >>>> just blacklist it inside the kernel? I doubt that we can load >>>> iommu >>>> as >>>> module... >>> >>> You mean as in patch the iommu probe code to check for >>> "google,snow", >>> "google,spring", etc.? >> >> For example - or remove the respective dt node. Or as a property to >> the >> IOMMU dt node... >> >> Alex >> >>> Andreas >>> >>> -- >>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>> GF: Felix Imendörffer, Jane Smithard, 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 >>
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Perfect! I submitted an update request to include it: https://build.opensuse.org/request/show/323645 We still need to update our kernel config to disable exynos IOMMU. But kernel repo is currently broken for master. Could send your config patch against stable kernel (4.1), please? Guillaume Le 17/08/2015 14:31, Misha Komarovskiy a écrit :
Adding them with force_drivers do the trick. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
You do not need to modify your kernel for that. Remove your /etc/modules-load.d/ file to get back in non-auto loading.
Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the following line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
If it does not help, replace: add_drivers += "cros_ec_devs ptn3460 pwm-samsung" by: force_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
Guillaume
Le 17/08/2015 14:04, Misha Komarovskiy a écrit :
I made test on already installed image. Connected with usb network dongle, cloned kernel-source git, made sequence-patch to 4.1 source, copied modified lpae kernel config then booted resulting kernel. This extra modules i tried to add to /etc/modules-load.d/ and system start fine this way without manual modprobing, but this is not same as dracut config as i understand.
I never tried to branch kernel-source repo on obs to create custom config, i can make this test also if you can give me please some directions on how to properly create modified kernel branch.
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 17/08/2015 13:30, Misha Komarovskiy a écrit :
Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, system boots with black screen same, then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel start to work without kernel panic.
Thanks for your tests. Could you add thoses modules to /etc/dracut.conf.d/exynos_modules.conf with the new line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
and recreate initrd with dracut and check if it boots fine?
If it does not work, try 'force_drivers+=' instead of 'add_drivers +=' and recreate initrd.
Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Hello Guillaume, I tested both exynos_defconfig and multi_v7_defconfig, they work fine. But ill test lpae config without EXYNOS_IOMMU today and will report. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote: > Hi, > > Le 16/08/2015 21:59, Misha Komarovskiy a écrit : >> Hello, >> Maybe we can disable only Exynos IOMMU in configs for now? Same way >> it >> is disabled in current exynos_defconfig here >> >> >> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... >> As i understand it is broken for all exynos devices not only snow. > > That is exactly what I would like to do since I read this thread: > https://lkml.org/lkml/2015/2/17/163 > > Before submitting the idea here, I wanted to check if disabling Exynos > IOMMU > in config was enough. > I had only time to test the exynos_defconfig with openSUSE kernel and > it > was > OK (boot messages and login prompt displayed). > > > Guillaume > > >> --- >> Best Regards, >> Misha Komarovskiy >> zombahatgmaildotcom >> >> >> On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> >> wrote: >>> >>>> Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>: >>>> >>>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>>> Maybe some config options compiled as module (which?) and >>>>>>> blacklisted >>>>>>> for chromebooks could be ok? >>>>>> Maybe. Someone with a Chromebook needs to sit down and try. :) >>>>> Hrm, rather than disable it one way or another manually, couldn't >>>>> we >>>>> just blacklist it inside the kernel? I doubt that we can load >>>>> iommu >>>>> as >>>>> module... >>>> You mean as in patch the iommu probe code to check for >>>> "google,snow", >>>> "google,spring", etc.? >>> For example - or remove the respective dt node. Or as a property to >>> the >>> IOMMU dt node... >>> >>> Alex >>> >>>> Andreas >>>> >>>> -- >>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>> GF: Felix Imendörffer, Jane Smithard, 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 >>>
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
My patch in attach --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Mon, Aug 17, 2015 at 4:13 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Perfect!
I submitted an update request to include it: https://build.opensuse.org/request/show/323645
We still need to update our kernel config to disable exynos IOMMU. But kernel repo is currently broken for master. Could send your config patch against stable kernel (4.1), please?
Guillaume
Le 17/08/2015 14:31, Misha Komarovskiy a écrit :
Adding them with force_drivers do the trick. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
You do not need to modify your kernel for that. Remove your /etc/modules-load.d/ file to get back in non-auto loading.
Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the following line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
If it does not help, replace: add_drivers += "cros_ec_devs ptn3460 pwm-samsung" by: force_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
Guillaume
Le 17/08/2015 14:04, Misha Komarovskiy a écrit :
I made test on already installed image. Connected with usb network dongle, cloned kernel-source git, made sequence-patch to 4.1 source, copied modified lpae kernel config then booted resulting kernel. This extra modules i tried to add to /etc/modules-load.d/ and system start fine this way without manual modprobing, but this is not same as dracut config as i understand.
I never tried to branch kernel-source repo on obs to create custom config, i can make this test also if you can give me please some directions on how to properly create modified kernel branch.
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 17/08/2015 13:30, Misha Komarovskiy a écrit :
Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, system boots with black screen same, then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel start to work without kernel panic.
Thanks for your tests. Could you add thoses modules to /etc/dracut.conf.d/exynos_modules.conf with the new line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
and recreate initrd with dracut and check if it boots fine?
If it does not work, try 'force_drivers+=' instead of 'add_drivers +=' and recreate initrd.
Guillaume
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy <zombah@gmail.com> wrote: > > Hello Guillaume, > I tested both exynos_defconfig and multi_v7_defconfig, they work > fine. > But ill test lpae config without EXYNOS_IOMMU today and will report. > --- > Best Regards, > Misha Komarovskiy > zombahatgmaildotcom > > > On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet > <guillaume.gardet@free.fr> wrote: >> >> Hi, >> >> Le 16/08/2015 21:59, Misha Komarovskiy a écrit : >>> >>> Hello, >>> Maybe we can disable only Exynos IOMMU in configs for now? Same way >>> it >>> is disabled in current exynos_defconfig here >>> >>> >>> >>> >>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... >>> As i understand it is broken for all exynos devices not only snow. >> >> >> That is exactly what I would like to do since I read this thread: >> https://lkml.org/lkml/2015/2/17/163 >> >> Before submitting the idea here, I wanted to check if disabling >> Exynos >> IOMMU >> in config was enough. >> I had only time to test the exynos_defconfig with openSUSE kernel >> and >> it >> was >> OK (boot messages and login prompt displayed). >> >> >> Guillaume >> >> >>> --- >>> Best Regards, >>> Misha Komarovskiy >>> zombahatgmaildotcom >>> >>> >>> On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> >>> wrote: >>>> >>>> >>>>> Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>: >>>>> >>>>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>>>> >>>>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>>>> >>>>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>>>> Maybe some config options compiled as module (which?) and >>>>>>>> blacklisted >>>>>>>> for chromebooks could be ok? >>>>>>> >>>>>>> Maybe. Someone with a Chromebook needs to sit down and try. :) >>>>>> >>>>>> Hrm, rather than disable it one way or another manually, >>>>>> couldn't >>>>>> we >>>>>> just blacklist it inside the kernel? I doubt that we can load >>>>>> iommu >>>>>> as >>>>>> module... >>>>> >>>>> You mean as in patch the iommu probe code to check for >>>>> "google,snow", >>>>> "google,spring", etc.? >>>> >>>> For example - or remove the respective dt node. Or as a property >>>> to >>>> the >>>> IOMMU dt node... >>>> >>>> Alex >>>> >>>>> Andreas >>>>> >>>>> -- >>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>>> GF: Felix Imendörffer, Jane Smithard, 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 >>>>
Thanks. Could you submit your patch to stable branch for default, lpae and vanilla flavours, please? Patches against master branch should follow once git repo fixed. Guillaume Le 17/08/2015 16:07, Misha Komarovskiy a écrit :
My patch in attach --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 4:13 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Perfect!
I submitted an update request to include it: https://build.opensuse.org/request/show/323645
We still need to update our kernel config to disable exynos IOMMU. But kernel repo is currently broken for master. Could send your config patch against stable kernel (4.1), please?
Guillaume
Le 17/08/2015 14:31, Misha Komarovskiy a écrit :
Adding them with force_drivers do the trick. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
You do not need to modify your kernel for that. Remove your /etc/modules-load.d/ file to get back in non-auto loading.
Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the following line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
If it does not help, replace: add_drivers += "cros_ec_devs ptn3460 pwm-samsung" by: force_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
Guillaume
Le 17/08/2015 14:04, Misha Komarovskiy a écrit :
I made test on already installed image. Connected with usb network dongle, cloned kernel-source git, made sequence-patch to 4.1 source, copied modified lpae kernel config then booted resulting kernel. This extra modules i tried to add to /etc/modules-load.d/ and system start fine this way without manual modprobing, but this is not same as dracut config as i understand.
I never tried to branch kernel-source repo on obs to create custom config, i can make this test also if you can give me please some directions on how to properly create modified kernel branch.
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 17/08/2015 13:30, Misha Komarovskiy a écrit : > Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, system > boots with black screen same, > then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel start to > work without kernel panic.
Thanks for your tests. Could you add thoses modules to /etc/dracut.conf.d/exynos_modules.conf with the new line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
and recreate initrd with dracut and check if it boots fine?
If it does not work, try 'force_drivers+=' instead of 'add_drivers +=' and recreate initrd.
Guillaume
> --- > Best Regards, > Misha Komarovskiy > zombahatgmaildotcom > > > On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy <zombah@gmail.com> > wrote: >> Hello Guillaume, >> I tested both exynos_defconfig and multi_v7_defconfig, they work >> fine. >> But ill test lpae config without EXYNOS_IOMMU today and will report. >> --- >> Best Regards, >> Misha Komarovskiy >> zombahatgmaildotcom >> >> >> On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet >> <guillaume.gardet@free.fr> wrote: >>> Hi, >>> >>> Le 16/08/2015 21:59, Misha Komarovskiy a écrit : >>>> Hello, >>>> Maybe we can disable only Exynos IOMMU in configs for now? Same way >>>> it >>>> is disabled in current exynos_defconfig here >>>> >>>> >>>> >>>> >>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... >>>> As i understand it is broken for all exynos devices not only snow. >>> >>> That is exactly what I would like to do since I read this thread: >>> https://lkml.org/lkml/2015/2/17/163 >>> >>> Before submitting the idea here, I wanted to check if disabling >>> Exynos >>> IOMMU >>> in config was enough. >>> I had only time to test the exynos_defconfig with openSUSE kernel >>> and >>> it >>> was >>> OK (boot messages and login prompt displayed). >>> >>> >>> Guillaume >>> >>> >>>> --- >>>> Best Regards, >>>> Misha Komarovskiy >>>> zombahatgmaildotcom >>>> >>>> >>>> On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> >>>> wrote: >>>>> >>>>>> Am 23.07.2015 um 15:15 schrieb Andreas Färber <afaerber@suse.de>: >>>>>> >>>>>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>>>>> Maybe some config options compiled as module (which?) and >>>>>>>>> blacklisted >>>>>>>>> for chromebooks could be ok? >>>>>>>> Maybe. Someone with a Chromebook needs to sit down and try. :) >>>>>>> Hrm, rather than disable it one way or another manually, >>>>>>> couldn't >>>>>>> we >>>>>>> just blacklist it inside the kernel? I doubt that we can load >>>>>>> iommu >>>>>>> as >>>>>>> module... >>>>>> You mean as in patch the iommu probe code to check for >>>>>> "google,snow", >>>>>> "google,spring", etc.? >>>>> For example - or remove the respective dt node. Or as a property >>>>> to >>>>> the >>>>> IOMMU dt node... >>>>> >>>>> Alex >>>>> >>>>>> Andreas >>>>>> >>>>>> -- >>>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>>>> GF: Felix Imendörffer, Jane Smithard, 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 >>>>>
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
I can send patch to opensuse-kernel ml if thats suitable, this way is described on the wiki https://en.opensuse.org/openSUSE:Kernel_git#Submitting_your_changes_to_the_k... What do you think is patch for lpae enough or better add default and vanilla also? --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Mon, Aug 17, 2015 at 5:59 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Thanks.
Could you submit your patch to stable branch for default, lpae and vanilla flavours, please?
Patches against master branch should follow once git repo fixed.
Guillaume
Le 17/08/2015 16:07, Misha Komarovskiy a écrit :
My patch in attach --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 4:13 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Perfect!
I submitted an update request to include it: https://build.opensuse.org/request/show/323645
We still need to update our kernel config to disable exynos IOMMU. But kernel repo is currently broken for master. Could send your config patch against stable kernel (4.1), please?
Guillaume
Le 17/08/2015 14:31, Misha Komarovskiy a écrit :
Adding them with force_drivers do the trick. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
You do not need to modify your kernel for that. Remove your /etc/modules-load.d/ file to get back in non-auto loading.
Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the following line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
If it does not help, replace: add_drivers += "cros_ec_devs ptn3460 pwm-samsung" by: force_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
Guillaume
Le 17/08/2015 14:04, Misha Komarovskiy a écrit :
I made test on already installed image. Connected with usb network dongle, cloned kernel-source git, made sequence-patch to 4.1 source, copied modified lpae kernel config then booted resulting kernel. This extra modules i tried to add to /etc/modules-load.d/ and system start fine this way without manual modprobing, but this is not same as dracut config as i understand.
I never tried to branch kernel-source repo on obs to create custom config, i can make this test also if you can give me please some directions on how to properly create modified kernel branch.
--- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote: > > > Le 17/08/2015 13:30, Misha Komarovskiy a écrit : >> >> Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, system >> boots with black screen same, >> then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel start >> to >> work without kernel panic. > > > Thanks for your tests. > Could you add thoses modules to > /etc/dracut.conf.d/exynos_modules.conf > with > the new line: > add_drivers += "cros_ec_devs ptn3460 pwm-samsung" > > and recreate initrd with dracut and check if it boots fine? > > If it does not work, try 'force_drivers+=' instead of 'add_drivers > +=' > and > recreate initrd. > > > Guillaume > > >> --- >> Best Regards, >> Misha Komarovskiy >> zombahatgmaildotcom >> >> >> On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy >> <zombah@gmail.com> >> wrote: >>> >>> Hello Guillaume, >>> I tested both exynos_defconfig and multi_v7_defconfig, they work >>> fine. >>> But ill test lpae config without EXYNOS_IOMMU today and will >>> report. >>> --- >>> Best Regards, >>> Misha Komarovskiy >>> zombahatgmaildotcom >>> >>> >>> On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet >>> <guillaume.gardet@free.fr> wrote: >>>> >>>> Hi, >>>> >>>> Le 16/08/2015 21:59, Misha Komarovskiy a écrit : >>>>> >>>>> Hello, >>>>> Maybe we can disable only Exynos IOMMU in configs for now? Same >>>>> way >>>>> it >>>>> is disabled in current exynos_defconfig here >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... >>>>> As i understand it is broken for all exynos devices not only >>>>> snow. >>>> >>>> >>>> That is exactly what I would like to do since I read this thread: >>>> https://lkml.org/lkml/2015/2/17/163 >>>> >>>> Before submitting the idea here, I wanted to check if disabling >>>> Exynos >>>> IOMMU >>>> in config was enough. >>>> I had only time to test the exynos_defconfig with openSUSE kernel >>>> and >>>> it >>>> was >>>> OK (boot messages and login prompt displayed). >>>> >>>> >>>> Guillaume >>>> >>>> >>>>> --- >>>>> Best Regards, >>>>> Misha Komarovskiy >>>>> zombahatgmaildotcom >>>>> >>>>> >>>>> On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> >>>>> wrote: >>>>>> >>>>>> >>>>>>> Am 23.07.2015 um 15:15 schrieb Andreas Färber >>>>>>> <afaerber@suse.de>: >>>>>>> >>>>>>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>>>>>> >>>>>>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>>>>>> >>>>>>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>>>>>> Maybe some config options compiled as module (which?) and >>>>>>>>>> blacklisted >>>>>>>>>> for chromebooks could be ok? >>>>>>>>> >>>>>>>>> Maybe. Someone with a Chromebook needs to sit down and try. >>>>>>>>> :) >>>>>>>> >>>>>>>> Hrm, rather than disable it one way or another manually, >>>>>>>> couldn't >>>>>>>> we >>>>>>>> just blacklist it inside the kernel? I doubt that we can load >>>>>>>> iommu >>>>>>>> as >>>>>>>> module... >>>>>>> >>>>>>> You mean as in patch the iommu probe code to check for >>>>>>> "google,snow", >>>>>>> "google,spring", etc.? >>>>>> >>>>>> For example - or remove the respective dt node. Or as a property >>>>>> to >>>>>> the >>>>>> IOMMU dt node... >>>>>> >>>>>> Alex >>>>>> >>>>>>> Andreas >>>>>>> >>>>>>> -- >>>>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>>>>> GF: Felix Imendörffer, Jane Smithard, 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 >>>>>>
-- 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
Yes, this the way to do. Please patch lpae, default and vanilla to be consistent across configs. Guillaume Le 17/08/2015 17:27, Misha Komarovskiy a écrit :
I can send patch to opensuse-kernel ml if thats suitable, this way is described on the wiki https://en.opensuse.org/openSUSE:Kernel_git#Submitting_your_changes_to_the_k... What do you think is patch for lpae enough or better add default and vanilla also? --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 5:59 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Thanks.
Could you submit your patch to stable branch for default, lpae and vanilla flavours, please?
Patches against master branch should follow once git repo fixed.
Guillaume
Le 17/08/2015 16:07, Misha Komarovskiy a écrit :
My patch in attach --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 4:13 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Perfect!
I submitted an update request to include it: https://build.opensuse.org/request/show/323645
We still need to update our kernel config to disable exynos IOMMU. But kernel repo is currently broken for master. Could send your config patch against stable kernel (4.1), please?
Guillaume
Le 17/08/2015 14:31, Misha Komarovskiy a écrit :
Adding them with force_drivers do the trick. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
You do not need to modify your kernel for that. Remove your /etc/modules-load.d/ file to get back in non-auto loading.
Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the following line: add_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
If it does not help, replace: add_drivers += "cros_ec_devs ptn3460 pwm-samsung" by: force_drivers += "cros_ec_devs ptn3460 pwm-samsung"
Then recreate your initrd with: dracut -f and reboot.
Guillaume
Le 17/08/2015 14:04, Misha Komarovskiy a écrit : > I made test on already installed image. Connected with usb network > dongle, cloned kernel-source git, made sequence-patch to 4.1 source, > copied modified lpae kernel config then booted > resulting kernel. > This extra modules i tried to add to /etc/modules-load.d/ and system > start fine this way without manual modprobing, but this is not same as > dracut config as i understand. > > I never tried to branch kernel-source repo on obs to create custom > config, i can make this test also if you can give me please some > directions on how to properly create modified kernel branch. > > > > --- > Best Regards, > Misha Komarovskiy > zombahatgmaildotcom > > > On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet > <guillaume.gardet@free.fr> wrote: >> >> Le 17/08/2015 13:30, Misha Komarovskiy a écrit : >>> Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, system >>> boots with black screen same, >>> then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel start >>> to >>> work without kernel panic. >> >> Thanks for your tests. >> Could you add thoses modules to >> /etc/dracut.conf.d/exynos_modules.conf >> with >> the new line: >> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >> >> and recreate initrd with dracut and check if it boots fine? >> >> If it does not work, try 'force_drivers+=' instead of 'add_drivers >> +=' >> and >> recreate initrd. >> >> >> Guillaume >> >> >>> --- >>> Best Regards, >>> Misha Komarovskiy >>> zombahatgmaildotcom >>> >>> >>> On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy >>> <zombah@gmail.com> >>> wrote: >>>> Hello Guillaume, >>>> I tested both exynos_defconfig and multi_v7_defconfig, they work >>>> fine. >>>> But ill test lpae config without EXYNOS_IOMMU today and will >>>> report. >>>> --- >>>> Best Regards, >>>> Misha Komarovskiy >>>> zombahatgmaildotcom >>>> >>>> >>>> On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet >>>> <guillaume.gardet@free.fr> wrote: >>>>> Hi, >>>>> >>>>> Le 16/08/2015 21:59, Misha Komarovskiy a écrit : >>>>>> Hello, >>>>>> Maybe we can disable only Exynos IOMMU in configs for now? Same >>>>>> way >>>>>> it >>>>>> is disabled in current exynos_defconfig here >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... >>>>>> As i understand it is broken for all exynos devices not only >>>>>> snow. >>>>> >>>>> That is exactly what I would like to do since I read this thread: >>>>> https://lkml.org/lkml/2015/2/17/163 >>>>> >>>>> Before submitting the idea here, I wanted to check if disabling >>>>> Exynos >>>>> IOMMU >>>>> in config was enough. >>>>> I had only time to test the exynos_defconfig with openSUSE kernel >>>>> and >>>>> it >>>>> was >>>>> OK (boot messages and login prompt displayed). >>>>> >>>>> >>>>> Guillaume >>>>> >>>>> >>>>>> --- >>>>>> Best Regards, >>>>>> Misha Komarovskiy >>>>>> zombahatgmaildotcom >>>>>> >>>>>> >>>>>> On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> >>>>>> wrote: >>>>>>> >>>>>>>> Am 23.07.2015 um 15:15 schrieb Andreas Färber >>>>>>>> <afaerber@suse.de>: >>>>>>>> >>>>>>>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>>>>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>>>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>>>>>>> Maybe some config options compiled as module (which?) and >>>>>>>>>>> blacklisted >>>>>>>>>>> for chromebooks could be ok? >>>>>>>>>> Maybe. Someone with a Chromebook needs to sit down and try. >>>>>>>>>> :) >>>>>>>>> Hrm, rather than disable it one way or another manually, >>>>>>>>> couldn't >>>>>>>>> we >>>>>>>>> just blacklist it inside the kernel? I doubt that we can load >>>>>>>>> iommu >>>>>>>>> as >>>>>>>>> module... >>>>>>>> You mean as in patch the iommu probe code to check for >>>>>>>> "google,snow", >>>>>>>> "google,spring", etc.? >>>>>>> For example - or remove the respective dt node. Or as a property >>>>>>> to >>>>>>> the >>>>>>> IOMMU dt node... >>>>>>> >>>>>>> Alex >>>>>>> >>>>>>>> Andreas >>>>>>>> >>>>>>>> -- >>>>>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>>>>>> GF: Felix Imendörffer, Jane Smithard, 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 >>>>>>> -- 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 17/08/2015 17:41, Guillaume Gardet a écrit :
Yes, this the way to do.
Please patch lpae, default and vanilla to be consistent across configs.
The patched kernel reached Factory/Tumbleweed but there is still a black screen! :( The boot (and reboot) problem is fixed with latest image. Guillaume
Guillaume
Le 17/08/2015 17:27, Misha Komarovskiy a écrit :
I can send patch to opensuse-kernel ml if thats suitable, this way is described on the wiki https://en.opensuse.org/openSUSE:Kernel_git#Submitting_your_changes_to_the_k... What do you think is patch for lpae enough or better add default and vanilla also? --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 5:59 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Thanks.
Could you submit your patch to stable branch for default, lpae and vanilla flavours, please?
Patches against master branch should follow once git repo fixed.
Guillaume
Le 17/08/2015 16:07, Misha Komarovskiy a écrit :
My patch in attach --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 4:13 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Perfect!
I submitted an update request to include it: https://build.opensuse.org/request/show/323645
We still need to update our kernel config to disable exynos IOMMU. But kernel repo is currently broken for master. Could send your config patch against stable kernel (4.1), please?
Guillaume
Le 17/08/2015 14:31, Misha Komarovskiy a écrit :
Adding them with force_drivers do the trick. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote: > You do not need to modify your kernel for that. > Remove your /etc/modules-load.d/ file to get back in non-auto loading. > > Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the > following > line: > add_drivers += "cros_ec_devs ptn3460 pwm-samsung" > > Then recreate your initrd with: > dracut -f > and reboot. > > > If it does not help, replace: > add_drivers += "cros_ec_devs ptn3460 pwm-samsung" > by: > force_drivers += "cros_ec_devs ptn3460 pwm-samsung" > > Then recreate your initrd with: > dracut -f > and reboot. > > > Guillaume > > > > Le 17/08/2015 14:04, Misha Komarovskiy a écrit : >> I made test on already installed image. Connected with usb network >> dongle, cloned kernel-source git, made sequence-patch to 4.1 source, >> copied modified lpae kernel config then booted >> resulting kernel. >> This extra modules i tried to add to /etc/modules-load.d/ and system >> start fine this way without manual modprobing, but this is not same as >> dracut config as i understand. >> >> I never tried to branch kernel-source repo on obs to create custom >> config, i can make this test also if you can give me please some >> directions on how to properly create modified kernel branch. >> >> >> >> --- >> Best Regards, >> Misha Komarovskiy >> zombahatgmaildotcom >> >> >> On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet >> <guillaume.gardet@free.fr> wrote: >>> >>> Le 17/08/2015 13:30, Misha Komarovskiy a écrit : >>>> Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, system >>>> boots with black screen same, >>>> then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel start >>>> to >>>> work without kernel panic. >>> >>> Thanks for your tests. >>> Could you add thoses modules to >>> /etc/dracut.conf.d/exynos_modules.conf >>> with >>> the new line: >>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>> >>> and recreate initrd with dracut and check if it boots fine? >>> >>> If it does not work, try 'force_drivers+=' instead of 'add_drivers >>> +=' >>> and >>> recreate initrd. >>> >>> >>> Guillaume >>> >>> >>>> --- >>>> Best Regards, >>>> Misha Komarovskiy >>>> zombahatgmaildotcom >>>> >>>> >>>> On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy >>>> <zombah@gmail.com> >>>> wrote: >>>>> Hello Guillaume, >>>>> I tested both exynos_defconfig and multi_v7_defconfig, they work >>>>> fine. >>>>> But ill test lpae config without EXYNOS_IOMMU today and will >>>>> report. >>>>> --- >>>>> Best Regards, >>>>> Misha Komarovskiy >>>>> zombahatgmaildotcom >>>>> >>>>> >>>>> On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet >>>>> <guillaume.gardet@free.fr> wrote: >>>>>> Hi, >>>>>> >>>>>> Le 16/08/2015 21:59, Misha Komarovskiy a écrit : >>>>>>> Hello, >>>>>>> Maybe we can disable only Exynos IOMMU in configs for now? Same >>>>>>> way >>>>>>> it >>>>>>> is disabled in current exynos_defconfig here >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... >>>>>>> As i understand it is broken for all exynos devices not only >>>>>>> snow. >>>>>> >>>>>> That is exactly what I would like to do since I read this thread: >>>>>> https://lkml.org/lkml/2015/2/17/163 >>>>>> >>>>>> Before submitting the idea here, I wanted to check if disabling >>>>>> Exynos >>>>>> IOMMU >>>>>> in config was enough. >>>>>> I had only time to test the exynos_defconfig with openSUSE kernel >>>>>> and >>>>>> it >>>>>> was >>>>>> OK (boot messages and login prompt displayed). >>>>>> >>>>>> >>>>>> Guillaume >>>>>> >>>>>> >>>>>>> --- >>>>>>> Best Regards, >>>>>>> Misha Komarovskiy >>>>>>> zombahatgmaildotcom >>>>>>> >>>>>>> >>>>>>> On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf <agraf@suse.de> >>>>>>> wrote: >>>>>>>> >>>>>>>>> Am 23.07.2015 um 15:15 schrieb Andreas Färber >>>>>>>>> <afaerber@suse.de>: >>>>>>>>> >>>>>>>>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>>>>>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>>>>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>>>>>>>> Maybe some config options compiled as module (which?) and >>>>>>>>>>>> blacklisted >>>>>>>>>>>> for chromebooks could be ok? >>>>>>>>>>> Maybe. Someone with a Chromebook needs to sit down and try. >>>>>>>>>>> :) >>>>>>>>>> Hrm, rather than disable it one way or another manually, >>>>>>>>>> couldn't >>>>>>>>>> we >>>>>>>>>> just blacklist it inside the kernel? I doubt that we can load >>>>>>>>>> iommu >>>>>>>>>> as >>>>>>>>>> module... >>>>>>>>> You mean as in patch the iommu probe code to check for >>>>>>>>> "google,snow", >>>>>>>>> "google,spring", etc.? >>>>>>>> For example - or remove the respective dt node. Or as a property >>>>>>>> to >>>>>>>> the >>>>>>>> IOMMU dt node... >>>>>>>> >>>>>>>> Alex >>>>>>>> >>>>>>>>> Andreas >>>>>>>>> >>>>>>>>> -- >>>>>>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>>>>>>> GF: Felix Imendörffer, Jane Smithard, 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 >>>>>>>> -- 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, On Mon, Aug 31, 2015 at 5:08 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 17/08/2015 17:41, Guillaume Gardet a écrit :
Yes, this the way to do.
Please patch lpae, default and vanilla to be consistent across configs.
The patched kernel reached Factory/Tumbleweed but there is still a black screen! :(
Are you sure it is included? I see 4.1.5 version in http://download.opensuse.org/ports/armv7hl/factory/repo/oss/suse/armv7hl/ And my patch was applied to Kernel:stable after 4.1.6 patch.
The boot (and reboot) problem is fixed with latest image.
Guillaume
Guillaume
Le 17/08/2015 17:27, Misha Komarovskiy a écrit :
I can send patch to opensuse-kernel ml if thats suitable, this way is described on the wiki
https://en.opensuse.org/openSUSE:Kernel_git#Submitting_your_changes_to_the_k... What do you think is patch for lpae enough or better add default and vanilla also? --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 5:59 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Thanks.
Could you submit your patch to stable branch for default, lpae and vanilla flavours, please?
Patches against master branch should follow once git repo fixed.
Guillaume
Le 17/08/2015 16:07, Misha Komarovskiy a écrit :
My patch in attach --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 4:13 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Perfect!
I submitted an update request to include it: https://build.opensuse.org/request/show/323645
We still need to update our kernel config to disable exynos IOMMU. But kernel repo is currently broken for master. Could send your config patch against stable kernel (4.1), please?
Guillaume
Le 17/08/2015 14:31, Misha Komarovskiy a écrit : > > Adding them with force_drivers do the trick. > --- > Best Regards, > Misha Komarovskiy > zombahatgmaildotcom > > > On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet > <guillaume.gardet@free.fr> wrote: >> >> You do not need to modify your kernel for that. >> Remove your /etc/modules-load.d/ file to get back in non-auto >> loading. >> >> Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the >> following >> line: >> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >> >> Then recreate your initrd with: >> dracut -f >> and reboot. >> >> >> If it does not help, replace: >> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >> by: >> force_drivers += "cros_ec_devs ptn3460 pwm-samsung" >> >> Then recreate your initrd with: >> dracut -f >> and reboot. >> >> >> Guillaume >> >> >> >> Le 17/08/2015 14:04, Misha Komarovskiy a écrit : >>> >>> I made test on already installed image. Connected with usb network >>> dongle, cloned kernel-source git, made sequence-patch to 4.1 >>> source, >>> copied modified lpae kernel config then booted >>> resulting kernel. >>> This extra modules i tried to add to /etc/modules-load.d/ and >>> system >>> start fine this way without manual modprobing, but this is not same >>> as >>> dracut config as i understand. >>> >>> I never tried to branch kernel-source repo on obs to create custom >>> config, i can make this test also if you can give me please some >>> directions on how to properly create modified kernel branch. >>> >>> >>> >>> --- >>> Best Regards, >>> Misha Komarovskiy >>> zombahatgmaildotcom >>> >>> >>> On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet >>> <guillaume.gardet@free.fr> wrote: >>>> >>>> >>>> Le 17/08/2015 13:30, Misha Komarovskiy a écrit : >>>>> >>>>> Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, >>>>> system >>>>> boots with black screen same, >>>>> then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel >>>>> start >>>>> to >>>>> work without kernel panic. >>>> >>>> >>>> Thanks for your tests. >>>> Could you add thoses modules to >>>> /etc/dracut.conf.d/exynos_modules.conf >>>> with >>>> the new line: >>>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>> >>>> and recreate initrd with dracut and check if it boots fine? >>>> >>>> If it does not work, try 'force_drivers+=' instead of 'add_drivers >>>> +=' >>>> and >>>> recreate initrd. >>>> >>>> >>>> Guillaume >>>> >>>> >>>>> --- >>>>> Best Regards, >>>>> Misha Komarovskiy >>>>> zombahatgmaildotcom >>>>> >>>>> >>>>> On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy >>>>> <zombah@gmail.com> >>>>> wrote: >>>>>> >>>>>> Hello Guillaume, >>>>>> I tested both exynos_defconfig and multi_v7_defconfig, they work >>>>>> fine. >>>>>> But ill test lpae config without EXYNOS_IOMMU today and will >>>>>> report. >>>>>> --- >>>>>> Best Regards, >>>>>> Misha Komarovskiy >>>>>> zombahatgmaildotcom >>>>>> >>>>>> >>>>>> On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet >>>>>> <guillaume.gardet@free.fr> wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Le 16/08/2015 21:59, Misha Komarovskiy a écrit : >>>>>>>> >>>>>>>> Hello, >>>>>>>> Maybe we can disable only Exynos IOMMU in configs for now? >>>>>>>> Same >>>>>>>> way >>>>>>>> it >>>>>>>> is disabled in current exynos_defconfig here >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... >>>>>>>> As i understand it is broken for all exynos devices not only >>>>>>>> snow. >>>>>>> >>>>>>> >>>>>>> That is exactly what I would like to do since I read this >>>>>>> thread: >>>>>>> https://lkml.org/lkml/2015/2/17/163 >>>>>>> >>>>>>> Before submitting the idea here, I wanted to check if disabling >>>>>>> Exynos >>>>>>> IOMMU >>>>>>> in config was enough. >>>>>>> I had only time to test the exynos_defconfig with openSUSE >>>>>>> kernel >>>>>>> and >>>>>>> it >>>>>>> was >>>>>>> OK (boot messages and login prompt displayed). >>>>>>> >>>>>>> >>>>>>> Guillaume >>>>>>> >>>>>>> >>>>>>>> --- >>>>>>>> Best Regards, >>>>>>>> Misha Komarovskiy >>>>>>>> zombahatgmaildotcom >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf >>>>>>>> <agraf@suse.de> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>>> Am 23.07.2015 um 15:15 schrieb Andreas Färber >>>>>>>>>> <afaerber@suse.de>: >>>>>>>>>> >>>>>>>>>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>>>>>>>>> >>>>>>>>>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>>>>>>>>> Maybe some config options compiled as module (which?) and >>>>>>>>>>>>> blacklisted >>>>>>>>>>>>> for chromebooks could be ok? >>>>>>>>>>>> >>>>>>>>>>>> Maybe. Someone with a Chromebook needs to sit down and >>>>>>>>>>>> try. >>>>>>>>>>>> :) >>>>>>>>>>> >>>>>>>>>>> Hrm, rather than disable it one way or another manually, >>>>>>>>>>> couldn't >>>>>>>>>>> we >>>>>>>>>>> just blacklist it inside the kernel? I doubt that we can >>>>>>>>>>> load >>>>>>>>>>> iommu >>>>>>>>>>> as >>>>>>>>>>> module... >>>>>>>>>> >>>>>>>>>> You mean as in patch the iommu probe code to check for >>>>>>>>>> "google,snow", >>>>>>>>>> "google,spring", etc.? >>>>>>>>> >>>>>>>>> For example - or remove the respective dt node. Or as a >>>>>>>>> property >>>>>>>>> to >>>>>>>>> the >>>>>>>>> IOMMU dt node... >>>>>>>>> >>>>>>>>> Alex >>>>>>>>> >>>>>>>>>> Andreas >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>>>>>>>> GF: Felix Imendörffer, Jane Smithard, 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 >>>>>>>>>
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 31/08/2015 16:39, Misha Komarovskiy a écrit :
Hello Guillaume,
On Mon, Aug 31, 2015 at 5:08 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 17/08/2015 17:41, Guillaume Gardet a écrit :
Yes, this the way to do.
Please patch lpae, default and vanilla to be consistent across configs.
The patched kernel reached Factory/Tumbleweed but there is still a black screen! :(
Are you sure it is included? I see 4.1.5 version in http://download.opensuse.org/ports/armv7hl/factory/repo/oss/suse/armv7hl/ And my patch was applied to Kernel:stable after 4.1.6 patch.
Yes, I can see: kernel-lpae-4.1.6-2.1.armv7hl.rpm in this repo and in the build log of JeOS-chromebook image, it is the same version. Guillaume
The boot (and reboot) problem is fixed with latest image.
Guillaume
Guillaume
Le 17/08/2015 17:27, Misha Komarovskiy a écrit :
I can send patch to opensuse-kernel ml if thats suitable, this way is described on the wiki
https://en.opensuse.org/openSUSE:Kernel_git#Submitting_your_changes_to_the_k... What do you think is patch for lpae enough or better add default and vanilla also? --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 5:59 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Thanks.
Could you submit your patch to stable branch for default, lpae and vanilla flavours, please?
Patches against master branch should follow once git repo fixed.
Guillaume
Le 17/08/2015 16:07, Misha Komarovskiy a écrit :
My patch in attach --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 4:13 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote: > Perfect! > > I submitted an update request to include it: > https://build.opensuse.org/request/show/323645 > > We still need to update our kernel config to disable exynos IOMMU. But > kernel repo is currently broken for master. > Could send your config patch against stable kernel (4.1), please? > > > Guillaume > > > > Le 17/08/2015 14:31, Misha Komarovskiy a écrit : >> Adding them with force_drivers do the trick. >> --- >> Best Regards, >> Misha Komarovskiy >> zombahatgmaildotcom >> >> >> On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet >> <guillaume.gardet@free.fr> wrote: >>> You do not need to modify your kernel for that. >>> Remove your /etc/modules-load.d/ file to get back in non-auto >>> loading. >>> >>> Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the >>> following >>> line: >>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>> >>> Then recreate your initrd with: >>> dracut -f >>> and reboot. >>> >>> >>> If it does not help, replace: >>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>> by: >>> force_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>> >>> Then recreate your initrd with: >>> dracut -f >>> and reboot. >>> >>> >>> Guillaume >>> >>> >>> >>> Le 17/08/2015 14:04, Misha Komarovskiy a écrit : >>>> I made test on already installed image. Connected with usb network >>>> dongle, cloned kernel-source git, made sequence-patch to 4.1 >>>> source, >>>> copied modified lpae kernel config then booted >>>> resulting kernel. >>>> This extra modules i tried to add to /etc/modules-load.d/ and >>>> system >>>> start fine this way without manual modprobing, but this is not same >>>> as >>>> dracut config as i understand. >>>> >>>> I never tried to branch kernel-source repo on obs to create custom >>>> config, i can make this test also if you can give me please some >>>> directions on how to properly create modified kernel branch. >>>> >>>> >>>> >>>> --- >>>> Best Regards, >>>> Misha Komarovskiy >>>> zombahatgmaildotcom >>>> >>>> >>>> On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet >>>> <guillaume.gardet@free.fr> wrote: >>>>> >>>>> Le 17/08/2015 13:30, Misha Komarovskiy a écrit : >>>>>> Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, >>>>>> system >>>>>> boots with black screen same, >>>>>> then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel >>>>>> start >>>>>> to >>>>>> work without kernel panic. >>>>> >>>>> Thanks for your tests. >>>>> Could you add thoses modules to >>>>> /etc/dracut.conf.d/exynos_modules.conf >>>>> with >>>>> the new line: >>>>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>>> >>>>> and recreate initrd with dracut and check if it boots fine? >>>>> >>>>> If it does not work, try 'force_drivers+=' instead of 'add_drivers >>>>> +=' >>>>> and >>>>> recreate initrd. >>>>> >>>>> >>>>> Guillaume >>>>> >>>>> >>>>>> --- >>>>>> Best Regards, >>>>>> Misha Komarovskiy >>>>>> zombahatgmaildotcom >>>>>> >>>>>> >>>>>> On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy >>>>>> <zombah@gmail.com> >>>>>> wrote: >>>>>>> Hello Guillaume, >>>>>>> I tested both exynos_defconfig and multi_v7_defconfig, they work >>>>>>> fine. >>>>>>> But ill test lpae config without EXYNOS_IOMMU today and will >>>>>>> report. >>>>>>> --- >>>>>>> Best Regards, >>>>>>> Misha Komarovskiy >>>>>>> zombahatgmaildotcom >>>>>>> >>>>>>> >>>>>>> On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet >>>>>>> <guillaume.gardet@free.fr> wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> Le 16/08/2015 21:59, Misha Komarovskiy a écrit : >>>>>>>>> Hello, >>>>>>>>> Maybe we can disable only Exynos IOMMU in configs for now? >>>>>>>>> Same >>>>>>>>> way >>>>>>>>> it >>>>>>>>> is disabled in current exynos_defconfig here >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... >>>>>>>>> As i understand it is broken for all exynos devices not only >>>>>>>>> snow. >>>>>>>> >>>>>>>> That is exactly what I would like to do since I read this >>>>>>>> thread: >>>>>>>> https://lkml.org/lkml/2015/2/17/163 >>>>>>>> >>>>>>>> Before submitting the idea here, I wanted to check if disabling >>>>>>>> Exynos >>>>>>>> IOMMU >>>>>>>> in config was enough. >>>>>>>> I had only time to test the exynos_defconfig with openSUSE >>>>>>>> kernel >>>>>>>> and >>>>>>>> it >>>>>>>> was >>>>>>>> OK (boot messages and login prompt displayed). >>>>>>>> >>>>>>>> >>>>>>>> Guillaume >>>>>>>> >>>>>>>> >>>>>>>>> --- >>>>>>>>> Best Regards, >>>>>>>>> Misha Komarovskiy >>>>>>>>> zombahatgmaildotcom >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf >>>>>>>>> <agraf@suse.de> >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Am 23.07.2015 um 15:15 schrieb Andreas Färber >>>>>>>>>>> <afaerber@suse.de>: >>>>>>>>>>> >>>>>>>>>>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>>>>>>>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>>>>>>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>>>>>>>>>> Maybe some config options compiled as module (which?) and >>>>>>>>>>>>>> blacklisted >>>>>>>>>>>>>> for chromebooks could be ok? >>>>>>>>>>>>> Maybe. Someone with a Chromebook needs to sit down and >>>>>>>>>>>>> try. >>>>>>>>>>>>> :) >>>>>>>>>>>> Hrm, rather than disable it one way or another manually, >>>>>>>>>>>> couldn't >>>>>>>>>>>> we >>>>>>>>>>>> just blacklist it inside the kernel? I doubt that we can >>>>>>>>>>>> load >>>>>>>>>>>> iommu >>>>>>>>>>>> as >>>>>>>>>>>> module... >>>>>>>>>>> You mean as in patch the iommu probe code to check for >>>>>>>>>>> "google,snow", >>>>>>>>>>> "google,spring", etc.? >>>>>>>>>> For example - or remove the respective dt node. Or as a >>>>>>>>>> property >>>>>>>>>> to >>>>>>>>>> the >>>>>>>>>> IOMMU dt node... >>>>>>>>>> >>>>>>>>>> Alex >>>>>>>>>> >>>>>>>>>>> Andreas >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>>>>>>>>> GF: Felix Imendörffer, Jane Smithard, 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 >>>>>>>>>> -- 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, On Tue, Sep 1, 2015 at 11:17 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 31/08/2015 16:39, Misha Komarovskiy a écrit :
Hello Guillaume,
On Mon, Aug 31, 2015 at 5:08 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 17/08/2015 17:41, Guillaume Gardet a écrit :
Yes, this the way to do.
Please patch lpae, default and vanilla to be consistent across configs.
The patched kernel reached Factory/Tumbleweed but there is still a black screen! :(
Are you sure it is included? I see 4.1.5 version in http://download.opensuse.org/ports/armv7hl/factory/repo/oss/suse/armv7hl/ And my patch was applied to Kernel:stable after 4.1.6 patch.
Yes, I can see: kernel-lpae-4.1.6-2.1.armv7hl.rpm in this repo and in the build log of JeOS-chromebook image, it is the same version.
You are right. Kernel is fine now, but but required modules won't auto load even with force_drivers 8( If i run dracut -f manually output is: line 2: force_drivers: command not found but this fix worked for me before, maybe something changed in dracut itself?
Guillaume
The boot (and reboot) problem is fixed with latest image.
Guillaume
Guillaume
Le 17/08/2015 17:27, Misha Komarovskiy a écrit :
I can send patch to opensuse-kernel ml if thats suitable, this way is described on the wiki
https://en.opensuse.org/openSUSE:Kernel_git#Submitting_your_changes_to_the_k... What do you think is patch for lpae enough or better add default and vanilla also? --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 5:59 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Thanks.
Could you submit your patch to stable branch for default, lpae and vanilla flavours, please?
Patches against master branch should follow once git repo fixed.
Guillaume
Le 17/08/2015 16:07, Misha Komarovskiy a écrit : > > My patch in attach > --- > Best Regards, > Misha Komarovskiy > zombahatgmaildotcom > > > On Mon, Aug 17, 2015 at 4:13 PM, Guillaume Gardet > <guillaume.gardet@free.fr> wrote: >> >> Perfect! >> >> I submitted an update request to include it: >> https://build.opensuse.org/request/show/323645 >> >> We still need to update our kernel config to disable exynos IOMMU. >> But >> kernel repo is currently broken for master. >> Could send your config patch against stable kernel (4.1), please? >> >> >> Guillaume >> >> >> >> Le 17/08/2015 14:31, Misha Komarovskiy a écrit : >>> >>> Adding them with force_drivers do the trick. >>> --- >>> Best Regards, >>> Misha Komarovskiy >>> zombahatgmaildotcom >>> >>> >>> On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet >>> <guillaume.gardet@free.fr> wrote: >>>> >>>> You do not need to modify your kernel for that. >>>> Remove your /etc/modules-load.d/ file to get back in non-auto >>>> loading. >>>> >>>> Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the >>>> following >>>> line: >>>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>> >>>> Then recreate your initrd with: >>>> dracut -f >>>> and reboot. >>>> >>>> >>>> If it does not help, replace: >>>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>> by: >>>> force_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>> >>>> Then recreate your initrd with: >>>> dracut -f >>>> and reboot. >>>> >>>> >>>> Guillaume >>>> >>>> >>>> >>>> Le 17/08/2015 14:04, Misha Komarovskiy a écrit : >>>>> >>>>> I made test on already installed image. Connected with usb >>>>> network >>>>> dongle, cloned kernel-source git, made sequence-patch to 4.1 >>>>> source, >>>>> copied modified lpae kernel config then booted >>>>> resulting kernel. >>>>> This extra modules i tried to add to /etc/modules-load.d/ and >>>>> system >>>>> start fine this way without manual modprobing, but this is not >>>>> same >>>>> as >>>>> dracut config as i understand. >>>>> >>>>> I never tried to branch kernel-source repo on obs to create >>>>> custom >>>>> config, i can make this test also if you can give me please some >>>>> directions on how to properly create modified kernel branch. >>>>> >>>>> >>>>> >>>>> --- >>>>> Best Regards, >>>>> Misha Komarovskiy >>>>> zombahatgmaildotcom >>>>> >>>>> >>>>> On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet >>>>> <guillaume.gardet@free.fr> wrote: >>>>>> >>>>>> >>>>>> Le 17/08/2015 13:30, Misha Komarovskiy a écrit : >>>>>>> >>>>>>> Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, >>>>>>> system >>>>>>> boots with black screen same, >>>>>>> then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel >>>>>>> start >>>>>>> to >>>>>>> work without kernel panic. >>>>>> >>>>>> >>>>>> Thanks for your tests. >>>>>> Could you add thoses modules to >>>>>> /etc/dracut.conf.d/exynos_modules.conf >>>>>> with >>>>>> the new line: >>>>>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>>>> >>>>>> and recreate initrd with dracut and check if it boots fine? >>>>>> >>>>>> If it does not work, try 'force_drivers+=' instead of >>>>>> 'add_drivers >>>>>> +=' >>>>>> and >>>>>> recreate initrd. >>>>>> >>>>>> >>>>>> Guillaume >>>>>> >>>>>> >>>>>>> --- >>>>>>> Best Regards, >>>>>>> Misha Komarovskiy >>>>>>> zombahatgmaildotcom >>>>>>> >>>>>>> >>>>>>> On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy >>>>>>> <zombah@gmail.com> >>>>>>> wrote: >>>>>>>> >>>>>>>> Hello Guillaume, >>>>>>>> I tested both exynos_defconfig and multi_v7_defconfig, they >>>>>>>> work >>>>>>>> fine. >>>>>>>> But ill test lpae config without EXYNOS_IOMMU today and will >>>>>>>> report. >>>>>>>> --- >>>>>>>> Best Regards, >>>>>>>> Misha Komarovskiy >>>>>>>> zombahatgmaildotcom >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet >>>>>>>> <guillaume.gardet@free.fr> wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> Le 16/08/2015 21:59, Misha Komarovskiy a écrit : >>>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> Maybe we can disable only Exynos IOMMU in configs for now? >>>>>>>>>> Same >>>>>>>>>> way >>>>>>>>>> it >>>>>>>>>> is disabled in current exynos_defconfig here >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... >>>>>>>>>> As i understand it is broken for all exynos devices not only >>>>>>>>>> snow. >>>>>>>>> >>>>>>>>> >>>>>>>>> That is exactly what I would like to do since I read this >>>>>>>>> thread: >>>>>>>>> https://lkml.org/lkml/2015/2/17/163 >>>>>>>>> >>>>>>>>> Before submitting the idea here, I wanted to check if >>>>>>>>> disabling >>>>>>>>> Exynos >>>>>>>>> IOMMU >>>>>>>>> in config was enough. >>>>>>>>> I had only time to test the exynos_defconfig with openSUSE >>>>>>>>> kernel >>>>>>>>> and >>>>>>>>> it >>>>>>>>> was >>>>>>>>> OK (boot messages and login prompt displayed). >>>>>>>>> >>>>>>>>> >>>>>>>>> Guillaume >>>>>>>>> >>>>>>>>> >>>>>>>>>> --- >>>>>>>>>> Best Regards, >>>>>>>>>> Misha Komarovskiy >>>>>>>>>> zombahatgmaildotcom >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf >>>>>>>>>> <agraf@suse.de> >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> Am 23.07.2015 um 15:15 schrieb Andreas Färber >>>>>>>>>>>> <afaerber@suse.de>: >>>>>>>>>>>> >>>>>>>>>>>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>>>>>>>>>>> Maybe some config options compiled as module (which?) >>>>>>>>>>>>>>> and >>>>>>>>>>>>>>> blacklisted >>>>>>>>>>>>>>> for chromebooks could be ok? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Maybe. Someone with a Chromebook needs to sit down and >>>>>>>>>>>>>> try. >>>>>>>>>>>>>> :) >>>>>>>>>>>>> >>>>>>>>>>>>> Hrm, rather than disable it one way or another manually, >>>>>>>>>>>>> couldn't >>>>>>>>>>>>> we >>>>>>>>>>>>> just blacklist it inside the kernel? I doubt that we can >>>>>>>>>>>>> load >>>>>>>>>>>>> iommu >>>>>>>>>>>>> as >>>>>>>>>>>>> module... >>>>>>>>>>>> >>>>>>>>>>>> You mean as in patch the iommu probe code to check for >>>>>>>>>>>> "google,snow", >>>>>>>>>>>> "google,spring", etc.? >>>>>>>>>>> >>>>>>>>>>> For example - or remove the respective dt node. Or as a >>>>>>>>>>> property >>>>>>>>>>> to >>>>>>>>>>> the >>>>>>>>>>> IOMMU dt node... >>>>>>>>>>> >>>>>>>>>>> Alex >>>>>>>>>>> >>>>>>>>>>>> Andreas >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>>>>>>>>>> GF: Felix Imendörffer, Jane Smithard, 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 >>>>>>>>>>> -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Tue, Sep 1, 2015 at 3:35 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Hello Guillaume,
On Tue, Sep 1, 2015 at 11:17 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 31/08/2015 16:39, Misha Komarovskiy a écrit :
Hello Guillaume,
On Mon, Aug 31, 2015 at 5:08 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 17/08/2015 17:41, Guillaume Gardet a écrit :
Yes, this the way to do.
Please patch lpae, default and vanilla to be consistent across configs.
The patched kernel reached Factory/Tumbleweed but there is still a black screen! :(
Are you sure it is included? I see 4.1.5 version in http://download.opensuse.org/ports/armv7hl/factory/repo/oss/suse/armv7hl/ And my patch was applied to Kernel:stable after 4.1.6 patch.
Yes, I can see: kernel-lpae-4.1.6-2.1.armv7hl.rpm in this repo and in the build log of JeOS-chromebook image, it is the same version.
You are right. Kernel is fine now, but but required modules won't auto load even with force_drivers 8( If i run dracut -f manually output is: line 2: force_drivers: command not found but this fix worked for me before, maybe something changed in dracut itself?
It seems the problem that force_drivers line must not contain empty spaces, now it look like: force_drivers += "cros_ec_devs ptn3460 pwm-samsung" and correct one is force_drivers+="cros_ec_devs ptn3460 pwm-samsung" with such line, dracut parse force_drivers fine.
Guillaume
The boot (and reboot) problem is fixed with latest image.
Guillaume
Guillaume
Le 17/08/2015 17:27, Misha Komarovskiy a écrit :
I can send patch to opensuse-kernel ml if thats suitable, this way is described on the wiki
https://en.opensuse.org/openSUSE:Kernel_git#Submitting_your_changes_to_the_k... What do you think is patch for lpae enough or better add default and vanilla also? --- Best Regards, Misha Komarovskiy zombahatgmaildotcom
On Mon, Aug 17, 2015 at 5:59 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote: > > Thanks. > > Could you submit your patch to stable branch for default, lpae and > vanilla > flavours, please? > > Patches against master branch should follow once git repo fixed. > > > Guillaume > > > Le 17/08/2015 16:07, Misha Komarovskiy a écrit : >> >> My patch in attach >> --- >> Best Regards, >> Misha Komarovskiy >> zombahatgmaildotcom >> >> >> On Mon, Aug 17, 2015 at 4:13 PM, Guillaume Gardet >> <guillaume.gardet@free.fr> wrote: >>> >>> Perfect! >>> >>> I submitted an update request to include it: >>> https://build.opensuse.org/request/show/323645 >>> >>> We still need to update our kernel config to disable exynos IOMMU. >>> But >>> kernel repo is currently broken for master. >>> Could send your config patch against stable kernel (4.1), please? >>> >>> >>> Guillaume >>> >>> >>> >>> Le 17/08/2015 14:31, Misha Komarovskiy a écrit : >>>> >>>> Adding them with force_drivers do the trick. >>>> --- >>>> Best Regards, >>>> Misha Komarovskiy >>>> zombahatgmaildotcom >>>> >>>> >>>> On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet >>>> <guillaume.gardet@free.fr> wrote: >>>>> >>>>> You do not need to modify your kernel for that. >>>>> Remove your /etc/modules-load.d/ file to get back in non-auto >>>>> loading. >>>>> >>>>> Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the >>>>> following >>>>> line: >>>>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>>> >>>>> Then recreate your initrd with: >>>>> dracut -f >>>>> and reboot. >>>>> >>>>> >>>>> If it does not help, replace: >>>>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>>> by: >>>>> force_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>>> >>>>> Then recreate your initrd with: >>>>> dracut -f >>>>> and reboot. >>>>> >>>>> >>>>> Guillaume >>>>> >>>>> >>>>> >>>>> Le 17/08/2015 14:04, Misha Komarovskiy a écrit : >>>>>> >>>>>> I made test on already installed image. Connected with usb >>>>>> network >>>>>> dongle, cloned kernel-source git, made sequence-patch to 4.1 >>>>>> source, >>>>>> copied modified lpae kernel config then booted >>>>>> resulting kernel. >>>>>> This extra modules i tried to add to /etc/modules-load.d/ and >>>>>> system >>>>>> start fine this way without manual modprobing, but this is not >>>>>> same >>>>>> as >>>>>> dracut config as i understand. >>>>>> >>>>>> I never tried to branch kernel-source repo on obs to create >>>>>> custom >>>>>> config, i can make this test also if you can give me please some >>>>>> directions on how to properly create modified kernel branch. >>>>>> >>>>>> >>>>>> >>>>>> --- >>>>>> Best Regards, >>>>>> Misha Komarovskiy >>>>>> zombahatgmaildotcom >>>>>> >>>>>> >>>>>> On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet >>>>>> <guillaume.gardet@free.fr> wrote: >>>>>>> >>>>>>> >>>>>>> Le 17/08/2015 13:30, Misha Komarovskiy a écrit : >>>>>>>> >>>>>>>> Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, >>>>>>>> system >>>>>>>> boots with black screen same, >>>>>>>> then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel >>>>>>>> start >>>>>>>> to >>>>>>>> work without kernel panic. >>>>>>> >>>>>>> >>>>>>> Thanks for your tests. >>>>>>> Could you add thoses modules to >>>>>>> /etc/dracut.conf.d/exynos_modules.conf >>>>>>> with >>>>>>> the new line: >>>>>>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>>>>> >>>>>>> and recreate initrd with dracut and check if it boots fine? >>>>>>> >>>>>>> If it does not work, try 'force_drivers+=' instead of >>>>>>> 'add_drivers >>>>>>> +=' >>>>>>> and >>>>>>> recreate initrd. >>>>>>> >>>>>>> >>>>>>> Guillaume >>>>>>> >>>>>>> >>>>>>>> --- >>>>>>>> Best Regards, >>>>>>>> Misha Komarovskiy >>>>>>>> zombahatgmaildotcom >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy >>>>>>>> <zombah@gmail.com> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Hello Guillaume, >>>>>>>>> I tested both exynos_defconfig and multi_v7_defconfig, they >>>>>>>>> work >>>>>>>>> fine. >>>>>>>>> But ill test lpae config without EXYNOS_IOMMU today and will >>>>>>>>> report. >>>>>>>>> --- >>>>>>>>> Best Regards, >>>>>>>>> Misha Komarovskiy >>>>>>>>> zombahatgmaildotcom >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet >>>>>>>>> <guillaume.gardet@free.fr> wrote: >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> Le 16/08/2015 21:59, Misha Komarovskiy a écrit : >>>>>>>>>>> >>>>>>>>>>> Hello, >>>>>>>>>>> Maybe we can disable only Exynos IOMMU in configs for now? >>>>>>>>>>> Same >>>>>>>>>>> way >>>>>>>>>>> it >>>>>>>>>>> is disabled in current exynos_defconfig here >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... >>>>>>>>>>> As i understand it is broken for all exynos devices not only >>>>>>>>>>> snow. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> That is exactly what I would like to do since I read this >>>>>>>>>> thread: >>>>>>>>>> https://lkml.org/lkml/2015/2/17/163 >>>>>>>>>> >>>>>>>>>> Before submitting the idea here, I wanted to check if >>>>>>>>>> disabling >>>>>>>>>> Exynos >>>>>>>>>> IOMMU >>>>>>>>>> in config was enough. >>>>>>>>>> I had only time to test the exynos_defconfig with openSUSE >>>>>>>>>> kernel >>>>>>>>>> and >>>>>>>>>> it >>>>>>>>>> was >>>>>>>>>> OK (boot messages and login prompt displayed). >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Guillaume >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> --- >>>>>>>>>>> Best Regards, >>>>>>>>>>> Misha Komarovskiy >>>>>>>>>>> zombahatgmaildotcom >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf >>>>>>>>>>> <agraf@suse.de> >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> Am 23.07.2015 um 15:15 schrieb Andreas Färber >>>>>>>>>>>>> <afaerber@suse.de>: >>>>>>>>>>>>> >>>>>>>>>>>>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>>>>>>>>>>>> Maybe some config options compiled as module (which?) >>>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>> blacklisted >>>>>>>>>>>>>>>> for chromebooks could be ok? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Maybe. Someone with a Chromebook needs to sit down and >>>>>>>>>>>>>>> try. >>>>>>>>>>>>>>> :) >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hrm, rather than disable it one way or another manually, >>>>>>>>>>>>>> couldn't >>>>>>>>>>>>>> we >>>>>>>>>>>>>> just blacklist it inside the kernel? I doubt that we can >>>>>>>>>>>>>> load >>>>>>>>>>>>>> iommu >>>>>>>>>>>>>> as >>>>>>>>>>>>>> module... >>>>>>>>>>>>> >>>>>>>>>>>>> You mean as in patch the iommu probe code to check for >>>>>>>>>>>>> "google,snow", >>>>>>>>>>>>> "google,spring", etc.? >>>>>>>>>>>> >>>>>>>>>>>> For example - or remove the respective dt node. Or as a >>>>>>>>>>>> property >>>>>>>>>>>> to >>>>>>>>>>>> the >>>>>>>>>>>> IOMMU dt node... >>>>>>>>>>>> >>>>>>>>>>>> Alex >>>>>>>>>>>> >>>>>>>>>>>>> Andreas >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>>>>>>>>>>> GF: Felix Imendörffer, Jane Smithard, 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 >>>>>>>>>>>> > -- > To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org > To contact the owner, e-mail: opensuse-arm+owner@opensuse.org >
-- Best Regards, Misha Komarovskiy zombahatgmaildotcom
-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 01/09/2015 14:49, Misha Komarovskiy a écrit :
On Tue, Sep 1, 2015 at 3:35 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Hello Guillaume,
On Tue, Sep 1, 2015 at 11:17 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 31/08/2015 16:39, Misha Komarovskiy a écrit :
Hello Guillaume,
On Mon, Aug 31, 2015 at 5:08 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 17/08/2015 17:41, Guillaume Gardet a écrit :
Yes, this the way to do.
Please patch lpae, default and vanilla to be consistent across configs.
The patched kernel reached Factory/Tumbleweed but there is still a black screen! :(
Are you sure it is included? I see 4.1.5 version in http://download.opensuse.org/ports/armv7hl/factory/repo/oss/suse/armv7hl/ And my patch was applied to Kernel:stable after 4.1.6 patch.
Yes, I can see: kernel-lpae-4.1.6-2.1.armv7hl.rpm in this repo and in the build log of JeOS-chromebook image, it is the same version.
You are right. Kernel is fine now, but but required modules won't auto load even with force_drivers 8( If i run dracut -f manually output is: line 2: force_drivers: command not found but this fix worked for me before, maybe something changed in dracut itself? It seems the problem that force_drivers line must not contain empty spaces, now it look like: force_drivers += "cros_ec_devs ptn3460 pwm-samsung" and correct one is force_drivers+="cros_ec_devs ptn3460 pwm-samsung"
with such line, dracut parse force_drivers fine.
Indded. Just tried it and I get the display! :D Thanks a lot! SR #328325 is pending: https://build.opensuse.org/request/show/328325 Guillaume
Guillaume
The boot (and reboot) problem is fixed with latest image.
Guillaume
Guillaume
Le 17/08/2015 17:27, Misha Komarovskiy a écrit : > I can send patch to opensuse-kernel ml if thats suitable, this way is > described on the wiki > > > https://en.opensuse.org/openSUSE:Kernel_git#Submitting_your_changes_to_the_k... > What do you think is patch for lpae enough or better add default and > vanilla also? > --- > Best Regards, > Misha Komarovskiy > zombahatgmaildotcom > > > On Mon, Aug 17, 2015 at 5:59 PM, Guillaume Gardet > <guillaume.gardet@free.fr> wrote: >> Thanks. >> >> Could you submit your patch to stable branch for default, lpae and >> vanilla >> flavours, please? >> >> Patches against master branch should follow once git repo fixed. >> >> >> Guillaume >> >> >> Le 17/08/2015 16:07, Misha Komarovskiy a écrit : >>> My patch in attach >>> --- >>> Best Regards, >>> Misha Komarovskiy >>> zombahatgmaildotcom >>> >>> >>> On Mon, Aug 17, 2015 at 4:13 PM, Guillaume Gardet >>> <guillaume.gardet@free.fr> wrote: >>>> Perfect! >>>> >>>> I submitted an update request to include it: >>>> https://build.opensuse.org/request/show/323645 >>>> >>>> We still need to update our kernel config to disable exynos IOMMU. >>>> But >>>> kernel repo is currently broken for master. >>>> Could send your config patch against stable kernel (4.1), please? >>>> >>>> >>>> Guillaume >>>> >>>> >>>> >>>> Le 17/08/2015 14:31, Misha Komarovskiy a écrit : >>>>> Adding them with force_drivers do the trick. >>>>> --- >>>>> Best Regards, >>>>> Misha Komarovskiy >>>>> zombahatgmaildotcom >>>>> >>>>> >>>>> On Mon, Aug 17, 2015 at 3:09 PM, Guillaume Gardet >>>>> <guillaume.gardet@free.fr> wrote: >>>>>> You do not need to modify your kernel for that. >>>>>> Remove your /etc/modules-load.d/ file to get back in non-auto >>>>>> loading. >>>>>> >>>>>> Open the file '/etc/dracut.conf.d/exynos_modules.conf' and add the >>>>>> following >>>>>> line: >>>>>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>>>> >>>>>> Then recreate your initrd with: >>>>>> dracut -f >>>>>> and reboot. >>>>>> >>>>>> >>>>>> If it does not help, replace: >>>>>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>>>> by: >>>>>> force_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>>>> >>>>>> Then recreate your initrd with: >>>>>> dracut -f >>>>>> and reboot. >>>>>> >>>>>> >>>>>> Guillaume >>>>>> >>>>>> >>>>>> >>>>>> Le 17/08/2015 14:04, Misha Komarovskiy a écrit : >>>>>>> I made test on already installed image. Connected with usb >>>>>>> network >>>>>>> dongle, cloned kernel-source git, made sequence-patch to 4.1 >>>>>>> source, >>>>>>> copied modified lpae kernel config then booted >>>>>>> resulting kernel. >>>>>>> This extra modules i tried to add to /etc/modules-load.d/ and >>>>>>> system >>>>>>> start fine this way without manual modprobing, but this is not >>>>>>> same >>>>>>> as >>>>>>> dracut config as i understand. >>>>>>> >>>>>>> I never tried to branch kernel-source repo on obs to create >>>>>>> custom >>>>>>> config, i can make this test also if you can give me please some >>>>>>> directions on how to properly create modified kernel branch. >>>>>>> >>>>>>> >>>>>>> >>>>>>> --- >>>>>>> Best Regards, >>>>>>> Misha Komarovskiy >>>>>>> zombahatgmaildotcom >>>>>>> >>>>>>> >>>>>>> On Mon, Aug 17, 2015 at 2:53 PM, Guillaume Gardet >>>>>>> <guillaume.gardet@free.fr> wrote: >>>>>>>> >>>>>>>> Le 17/08/2015 13:30, Misha Komarovskiy a écrit : >>>>>>>>> Just tested lpae config without CONFIG_EXYNOS_IOMMU on snow, >>>>>>>>> system >>>>>>>>> boots with black screen same, >>>>>>>>> then modprobe cros_ec_devs, ptn3460, pwm-samsung makes panel >>>>>>>>> start >>>>>>>>> to >>>>>>>>> work without kernel panic. >>>>>>>> >>>>>>>> Thanks for your tests. >>>>>>>> Could you add thoses modules to >>>>>>>> /etc/dracut.conf.d/exynos_modules.conf >>>>>>>> with >>>>>>>> the new line: >>>>>>>> add_drivers += "cros_ec_devs ptn3460 pwm-samsung" >>>>>>>> >>>>>>>> and recreate initrd with dracut and check if it boots fine? >>>>>>>> >>>>>>>> If it does not work, try 'force_drivers+=' instead of >>>>>>>> 'add_drivers >>>>>>>> +=' >>>>>>>> and >>>>>>>> recreate initrd. >>>>>>>> >>>>>>>> >>>>>>>> Guillaume >>>>>>>> >>>>>>>> >>>>>>>>> --- >>>>>>>>> Best Regards, >>>>>>>>> Misha Komarovskiy >>>>>>>>> zombahatgmaildotcom >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Aug 17, 2015 at 12:01 PM, Misha Komarovskiy >>>>>>>>> <zombah@gmail.com> >>>>>>>>> wrote: >>>>>>>>>> Hello Guillaume, >>>>>>>>>> I tested both exynos_defconfig and multi_v7_defconfig, they >>>>>>>>>> work >>>>>>>>>> fine. >>>>>>>>>> But ill test lpae config without EXYNOS_IOMMU today and will >>>>>>>>>> report. >>>>>>>>>> --- >>>>>>>>>> Best Regards, >>>>>>>>>> Misha Komarovskiy >>>>>>>>>> zombahatgmaildotcom >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Aug 17, 2015 at 9:59 AM, Guillaume Gardet >>>>>>>>>> <guillaume.gardet@free.fr> wrote: >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> Le 16/08/2015 21:59, Misha Komarovskiy a écrit : >>>>>>>>>>>> Hello, >>>>>>>>>>>> Maybe we can disable only Exynos IOMMU in configs for now? >>>>>>>>>>>> Same >>>>>>>>>>>> way >>>>>>>>>>>> it >>>>>>>>>>>> is disabled in current exynos_defconfig here >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/... >>>>>>>>>>>> As i understand it is broken for all exynos devices not only >>>>>>>>>>>> snow. >>>>>>>>>>> >>>>>>>>>>> That is exactly what I would like to do since I read this >>>>>>>>>>> thread: >>>>>>>>>>> https://lkml.org/lkml/2015/2/17/163 >>>>>>>>>>> >>>>>>>>>>> Before submitting the idea here, I wanted to check if >>>>>>>>>>> disabling >>>>>>>>>>> Exynos >>>>>>>>>>> IOMMU >>>>>>>>>>> in config was enough. >>>>>>>>>>> I had only time to test the exynos_defconfig with openSUSE >>>>>>>>>>> kernel >>>>>>>>>>> and >>>>>>>>>>> it >>>>>>>>>>> was >>>>>>>>>>> OK (boot messages and login prompt displayed). >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Guillaume >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> --- >>>>>>>>>>>> Best Regards, >>>>>>>>>>>> Misha Komarovskiy >>>>>>>>>>>> zombahatgmaildotcom >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Jul 23, 2015 at 4:29 PM, Alexander Graf >>>>>>>>>>>> <agraf@suse.de> >>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Am 23.07.2015 um 15:15 schrieb Andreas Färber >>>>>>>>>>>>>> <afaerber@suse.de>: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Am 23.07.2015 um 15:12 schrieb Alexander Graf: >>>>>>>>>>>>>>>> On 07/23/15 14:43, Andreas Färber wrote: >>>>>>>>>>>>>>>>> Am 23.07.2015 um 14:22 schrieb Guillaume Gardet: >>>>>>>>>>>>>>>>> Maybe some config options compiled as module (which?) >>>>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>>> blacklisted >>>>>>>>>>>>>>>>> for chromebooks could be ok? >>>>>>>>>>>>>>>> Maybe. Someone with a Chromebook needs to sit down and >>>>>>>>>>>>>>>> try. >>>>>>>>>>>>>>>> :) >>>>>>>>>>>>>>> Hrm, rather than disable it one way or another manually, >>>>>>>>>>>>>>> couldn't >>>>>>>>>>>>>>> we >>>>>>>>>>>>>>> just blacklist it inside the kernel? I doubt that we can >>>>>>>>>>>>>>> load >>>>>>>>>>>>>>> iommu >>>>>>>>>>>>>>> as >>>>>>>>>>>>>>> module... >>>>>>>>>>>>>> You mean as in patch the iommu probe code to check for >>>>>>>>>>>>>> "google,snow", >>>>>>>>>>>>>> "google,spring", etc.? >>>>>>>>>>>>> For example - or remove the respective dt node. Or as a >>>>>>>>>>>>> property >>>>>>>>>>>>> to >>>>>>>>>>>>> the >>>>>>>>>>>>> IOMMU dt node... >>>>>>>>>>>>> >>>>>>>>>>>>> Alex >>>>>>>>>>>>> >>>>>>>>>>>>>> Andreas >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>>>>>>>>>>>> GF: Felix Imendörffer, Jane Smithard, 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 >>>>>>>>>>>>> >> -- >> To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org >> To contact the owner, e-mail: opensuse-arm+owner@opensuse.org >>
-- Best Regards, Misha Komarovskiy zombahatgmaildotcom
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 01.09.2015 um 15:37 schrieb Guillaume Gardet:
Le 01/09/2015 14:49, Misha Komarovskiy a écrit :
On Tue, Sep 1, 2015 at 3:35 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Kernel is fine now, but but required modules won't auto load even with force_drivers 8( If i run dracut -f manually output is: line 2: force_drivers: command not found but this fix worked for me before, maybe something changed in dracut itself? It seems the problem that force_drivers line must not contain empty spaces, now it look like: force_drivers += "cros_ec_devs ptn3460 pwm-samsung" and correct one is force_drivers+="cros_ec_devs ptn3460 pwm-samsung"
with such line, dracut parse force_drivers fine.
Indded. Just tried it and I get the display! :D Thanks a lot!
SR #328325 is pending: https://build.opensuse.org/request/show/328325
Guillaume, I'm pretty sure I saw a comment in the JeOS script that says that add_drivers (or so) needs the string to start with a space, to avoid that being concatenated to a previously added driver. I imagine the same applies to force_drivers as well then. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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 01/09/2015 15:42, Andreas Färber a écrit :
Le 01/09/2015 14:49, Misha Komarovskiy a écrit :
On Tue, Sep 1, 2015 at 3:35 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Kernel is fine now, but but required modules won't auto load even with force_drivers 8( If i run dracut -f manually output is: line 2: force_drivers: command not found but this fix worked for me before, maybe something changed in dracut itself? It seems the problem that force_drivers line must not contain empty spaces, now it look like: force_drivers += "cros_ec_devs ptn3460 pwm-samsung" and correct one is force_drivers+="cros_ec_devs ptn3460 pwm-samsung"
with such line, dracut parse force_drivers fine. Indded. Just tried it and I get the display! :D Thanks a lot!
SR #328325 is pending: https://build.opensuse.org/request/show/328325 Guillaume, I'm pretty sure I saw a comment in the JeOS script that says
Am 01.09.2015 um 15:37 schrieb Guillaume Gardet: that add_drivers (or so) needs the string to start with a space, to avoid that being concatenated to a previously added driver. I imagine the same applies to force_drivers as well then.
Fixed in SR #328558. Guillaume
Regards, Andreas
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hello, I just tested openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-1.12.1-Build326.1.raw.xz: 1. On first boot screen still stays black, starts to work only after first reboot. Maybe we need to force_drivers for initial initrd also? 2. rtc_max77686 spam log and tty output with messages: rtc_max77686: RTC cannot handle the year 1970. Assume it's 2000. As i understand rtc drivers built-in inside kernel, but i2c driver which it use built as module and i2c driver init call happen too late for rtc on system power on? This is probably not chromebook specific issue but for all boards with i2c rtc drivers. On Wed, Sep 2, 2015 at 10:21 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 01/09/2015 15:42, Andreas Färber a écrit :
Am 01.09.2015 um 15:37 schrieb Guillaume Gardet:
Le 01/09/2015 14:49, Misha Komarovskiy a écrit :
On Tue, Sep 1, 2015 at 3:35 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Kernel is fine now, but but required modules won't auto load even with force_drivers 8( If i run dracut -f manually output is: line 2: force_drivers: command not found but this fix worked for me before, maybe something changed in dracut itself?
It seems the problem that force_drivers line must not contain empty spaces, now it look like: force_drivers += "cros_ec_devs ptn3460 pwm-samsung" and correct one is force_drivers+="cros_ec_devs ptn3460 pwm-samsung"
with such line, dracut parse force_drivers fine.
Indded. Just tried it and I get the display! :D Thanks a lot!
SR #328325 is pending: https://build.opensuse.org/request/show/328325
Guillaume, I'm pretty sure I saw a comment in the JeOS script that says that add_drivers (or so) needs the string to start with a space, to avoid that being concatenated to a previously added driver. I imagine the same applies to force_drivers as well then.
Fixed in SR #328558.
Guillaume
Regards, Andreas
-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hello, Just get time to run more tests. Kernel-source branch stable compiled with exynos_defconfig boots fine, tried 4.1.3, screen working i was able to reach login on first boot. Dmesg http://paste.opensuse.org/54891427 --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Thu, Jul 23, 2015 at 3:16 PM, Andreas Färber <afaerber@suse.de> wrote:
Hi,
Am 20.07.2015 um 14:28 schrieb Guillaume Gardet:
Le 19/07/2015 18:15, Misha Komarovskiy a écrit :
Also lcd screen stays black after kernel start, probably some drm module still missing.
Upstream kernel is broken. :(
How did you test? Actually there's a known issue that the Exynos IOMMU support breaks graphics on the Chromebooks because they enable a framebuffer early in bootloaders, before Linux initializes the IOMMU. Since some other platforms do need the IOMMU, I fear that we're going to need a new kernel flavor... :/ Not sure if that can be scripted as lpae minus certain options?
Regards, Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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
-- 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 Komarovskiy