[opensuse-arm] JeOS image status (Beagle, Panda, Arndale and chromebook tested)

newer
[opensuse-arm] ARM images builds...

older
[opensuse-arm] U-Boot v2014.10-rc2

Guillaume Gardet

8 Sep 2014 8 Sep '14

13:26

Hi, Fatcory:ARM repo has new JeOS (E17 and XFCE) images but there are some ghost files remaining. Pandaboard and Beagleboard boots u-boot but then hangs after "Starting kernel ...". Beagle should use a newer u-boot managing FDT for Beagle. Is there any known problem with Factory Kernel for OMAP3/OMAP4 boards? Arndale : Does boot u-boot but fails with a "Wrong Image Format" which should be fixed by SR #248024 (already accepted by Alex, thanks). I fixed it manually before the SR were accepted but I get lots of "cpufreq: __target_index: Failed to change cpu frequency: -22" errors logged but I finaly get a prompt. Serial console and USB2 work, but eth0 seems to have some problems. Second boot seems to be broken (I fallback to a dracut prompt). Chromebook: Does boot u-boot but then fails with a black screen once kernel is (or seems to be) loaded. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Show replies by date

Alexander Graf

8 Sep 8 Sep

14:01

On 08.09.14 15:26, Guillaume Gardet wrote:

...

Hi,

Fatcory:ARM repo has new JeOS (E17 and XFCE) images but there are some ghost files remaining.

Pandaboard and Beagleboard boots u-boot but then hangs after "Starting kernel ...". Beagle should use a newer u-boot managing FDT for Beagle. Is there any known problem with Factory Kernel for OMAP3/OMAP4 boards?

Phew, I haven't tried. But the QEMU beagle emulation I mentioned earlier could be very useful in finding out.

...

Arndale : Does boot u-boot but fails with a "Wrong Image Format" which should be fixed by SR #248024 (already accepted by Alex, thanks). I fixed it manually before the SR were accepted but I get lots of "cpufreq: __target_index: Failed to change cpu frequency: -22" errors logged but I finaly get a prompt.

Yes, you can work around this by echo'ing "performance" into the governor sysfs file. I haven't quite figured out what's going wrong here.

...

Serial console and USB2 work, but eth0 seems to have some problems. Second boot seems to be broken (I fallback to a dracut prompt).

I though I had fixed that one. The problem is that dracut doesn't include all modules required to access the SD card. So I added them to INITRD_MODULES in /etc/sysconfig/kernel in config.sh. Can you please check on first boot whether the line was properly updated?

...

Chromebook: Does boot u-boot but then fails with a black screen once kernel is (or seems to be) loaded.

Ah, debugging the Chromebook is always fun. Fortunately you do get into u-boot, so you can try a nifty little hack. Find out the address of __log_buf in the kernel you're trying to boot (nm should be able to tell you, subtract PAGE_OFFSET and add the physical memory offset). Then boot the kernel that doesn't work. Soft reset (ctrl-alt-f3 or so) and from the u-boot prompt, md.b that address. If the kernel started booting at all you should be able to see kernel log output which usually helps to get things working. If you don't see anything, chances are good the device tree is wrong ;). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Guillaume Gardet

15:50

Le 08/09/2014 16:01, Alexander Graf a écrit :

...

On 08.09.14 15:26, Guillaume Gardet wrote:

...
Hi,

Fatcory:ARM repo has new JeOS (E17 and XFCE) images but there are some ghost files remaining.

Pandaboard and Beagleboard boots u-boot but then hangs after "Starting kernel ...". Beagle should use a newer u-boot managing FDT for Beagle. Is there any known problem with Factory Kernel for OMAP3/OMAP4 boards? Phew, I haven't tried. But the QEMU beagle emulation I mentioned earlier could be very useful in finding out.

Maybe. I will try to find out without qemu. I prefere real hardware. ;) I will update JeOS-beagle to use FDT once u-boot get updated in Factory.

...

...
Arndale : Does boot u-boot but fails with a "Wrong Image Format" which should be fixed by SR #248024 (already accepted by Alex, thanks). I fixed it manually before the SR were accepted but I get lots of "cpufreq: __target_index: Failed to change cpu frequency: -22" errors logged but I finaly get a prompt. Yes, you can work around this by echo'ing "performance" into the governor sysfs file. I haven't quite figured out what's going wrong here.

Ok. It seems that the CPU voltage cannot be adjusted ("exynos-cpufreq exynos-cpufreq: failed to set cpu voltage to 1100000"). Maybe we are missing a power chip driver in the kernel?

...

...
Serial console and USB2 work, but eth0 seems to have some problems. Second boot seems to be broken (I fallback to a dracut prompt). I though I had fixed that one. The problem is that dracut doesn't include all modules required to access the SD card. So I added them to INITRD_MODULES in /etc/sysconfig/kernel in config.sh.

Can you please check on first boot whether the line was properly updated?

There is no /etc/sysconfig/kernel file on firstboot.

...

...
Chromebook: Does boot u-boot but then fails with a black screen once kernel is (or seems to be) loaded. Ah, debugging the Chromebook is always fun. Fortunately you do get into u-boot, so you can try a nifty little hack. Find out the address of __log_buf in the kernel you're trying to boot (nm should be able to tell you, subtract PAGE_OFFSET and add the physical memory offset). Then boot the kernel that doesn't work. Soft reset (ctrl-alt-f3 or so) and from the u-boot prompt, md.b that address.

If the kernel started booting at all you should be able to see kernel log output which usually helps to get things working. If you don't see anything, chances are good the device tree is wrong ;).

Ok, will try this later. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Alexander Graf

15:57

On 08.09.14 17:50, Guillaume Gardet wrote:

...

Le 08/09/2014 16:01, Alexander Graf a écrit :

...
On 08.09.14 15:26, Guillaume Gardet wrote:

...
Hi,

Fatcory:ARM repo has new JeOS (E17 and XFCE) images but there are some ghost files remaining.

Pandaboard and Beagleboard boots u-boot but then hangs after "Starting kernel ...". Beagle should use a newer u-boot managing FDT for Beagle. Is there any known problem with Factory Kernel for OMAP3/OMAP4 boards? Phew, I haven't tried. But the QEMU beagle emulation I mentioned earlier could be very useful in finding out.

Maybe. I will try to find out without qemu. I prefere real hardware. ;) I will update JeOS-beagle to use FDT once u-boot get updated in Factory.

Well, the nice thing about qemu is that you can attach gdb to the system. Of course if you have a JTAG you can try to debug it on real hardware too ;).

...

...
...
Arndale : Does boot u-boot but fails with a "Wrong Image Format" which should be fixed by SR #248024 (already accepted by Alex, thanks). I fixed it manually before the SR were accepted but I get lots of "cpufreq: __target_index: Failed to change cpu frequency: -22" errors logged but I finaly get a prompt. Yes, you can work around this by echo'ing "performance" into the governor sysfs file. I haven't quite figured out what's going wrong here.

Ok. It seems that the CPU voltage cannot be adjusted ("exynos-cpufreq exynos-cpufreq: failed to set cpu voltage to 1100000"). Maybe we are missing a power chip driver in the kernel?

Maybe - I have no idea about power chip drivers :). Can you take a look?

...

...
...
Serial console and USB2 work, but eth0 seems to have some problems. Second boot seems to be broken (I fallback to a dracut prompt). I though I had fixed that one. The problem is that dracut doesn't include all modules required to access the SD card. So I added them to INITRD_MODULES in /etc/sysconfig/kernel in config.sh.

Can you please check on first boot whether the line was properly updated?

There is no /etc/sysconfig/kernel file on firstboot.

O_o. There should be. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Guillaume Gardet

16:39

Le 08/09/2014 17:57, Alexander Graf a écrit :

...

On 08.09.14 17:50, Guillaume Gardet wrote:

...
Le 08/09/2014 16:01, Alexander Graf a écrit :

...
On 08.09.14 15:26, Guillaume Gardet wrote:

...
Hi,

Fatcory:ARM repo has new JeOS (E17 and XFCE) images but there are some ghost files remaining.

Pandaboard and Beagleboard boots u-boot but then hangs after "Starting kernel ...". Beagle should use a newer u-boot managing FDT for Beagle. Is there any known problem with Factory Kernel for OMAP3/OMAP4 boards? Phew, I haven't tried. But the QEMU beagle emulation I mentioned earlier could be very useful in finding out. Maybe. I will try to find out without qemu. I prefere real hardware. ;) I will update JeOS-beagle to use FDT once u-boot get updated in Factory. Well, the nice thing about qemu is that you can attach gdb to the system. Of course if you have a JTAG you can try to debug it on real hardware too ;).

Fixed using different load addr for kernel, initrd and fdt.

...

...
...
...
Arndale : Does boot u-boot but fails with a "Wrong Image Format" which should be fixed by SR #248024 (already accepted by Alex, thanks). I fixed it manually before the SR were accepted but I get lots of "cpufreq: __target_index: Failed to change cpu frequency: -22" errors logged but I finaly get a prompt. Yes, you can work around this by echo'ing "performance" into the governor sysfs file. I haven't quite figured out what's going wrong here. Ok. It seems that the CPU voltage cannot be adjusted ("exynos-cpufreq exynos-cpufreq: failed to set cpu voltage to 1100000"). Maybe we are missing a power chip driver in the kernel? Maybe - I have no idea about power chip drivers :). Can you take a look?

Yes, I will.

...

...
...
...
Serial console and USB2 work, but eth0 seems to have some problems. Second boot seems to be broken (I fallback to a dracut prompt). I though I had fixed that one. The problem is that dracut doesn't include all modules required to access the SD card. So I added them to INITRD_MODULES in /etc/sysconfig/kernel in config.sh.

Can you please check on first boot whether the line was properly updated? There is no /etc/sysconfig/kernel file on firstboot. O_o. There should be.

There are other files in this folder but no kernel file. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Guillaume Gardet

9 Sep 9 Sep

09:14

Le 08/09/2014 17:57, Alexander Graf a écrit :

...

...
...
...
Arndale : Does boot u-boot but fails with a "Wrong Image Format" which should be fixed by SR #248024 (already accepted by Alex, thanks). I fixed it manually before the SR were accepted but I get lots of "cpufreq: __target_index: Failed to change cpu frequency: -22" errors logged but I finaly get a prompt. Yes, you can work around this by echo'ing "performance" into the governor sysfs file. I haven't quite figured out what's going wrong here. Ok. It seems that the CPU voltage cannot be adjusted ("exynos-cpufreq exynos-cpufreq: failed to set cpu voltage to 1100000"). Maybe we are missing a power chip driver in the kernel? Maybe - I have no idea about power chip drivers :). Can you take a look?

The power chip driver is included. So maybe just a broken cpu freq for exynos?

...

...
...
...
Serial console and USB2 work, but eth0 seems to have some problems. Second boot seems to be broken (I fallback to a dracut prompt). I though I had fixed that one. The problem is that dracut doesn't include all modules required to access the SD card. So I added them to INITRD_MODULES in /etc/sysconfig/kernel in config.sh.

Can you please check on first boot whether the line was properly updated? There is no /etc/sysconfig/kernel file on firstboot. O_o. There should be.

Using dracut prompt, I listed "/lib/modules/3.16.1-2.g2ab6585-lpae/kernel/drivers/mmc/host" folder and only got: mmci.ko omap.ko omap_hsmmc.ko sdhci-pltfm.ko sdhci-tegra.ko sdhci.ko So, no dw_* mmc modules. But how those mmc modules get added? According to dracut documentation: https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_adding_kerne... We should use /etc/dracut.conf or /etc/dracut.conf.d/myconf.conf and NOT /etc/sysconfig/kernel Am I wrong? First boot is ok since kiwi adds dw_* mmc modules in initial initrd. But 2nd boot is broken because generated initrd does not include them. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Alexander Graf

09:26

On 09.09.14 11:14, Guillaume Gardet wrote:

...

Le 08/09/2014 17:57, Alexander Graf a écrit :

...
...
...
...
Arndale : Does boot u-boot but fails with a "Wrong Image Format" which should be fixed by SR #248024 (already accepted by Alex, thanks). I fixed it manually before the SR were accepted but I get lots of "cpufreq: __target_index: Failed to change cpu frequency: -22" errors logged but I finaly get a prompt. Yes, you can work around this by echo'ing "performance" into the governor sysfs file. I haven't quite figured out what's going wrong here. Ok. It seems that the CPU voltage cannot be adjusted ("exynos-cpufreq exynos-cpufreq: failed to set cpu voltage to 1100000"). Maybe we are missing a power chip driver in the kernel? Maybe - I have no idea about power chip drivers :). Can you take a look?

The power chip driver is included. So maybe just a broken cpu freq for exynos?

Maybe, or maybe it's missing infrastructure in the dt.

...

...
...
...
...
Serial console and USB2 work, but eth0 seems to have some problems. Second boot seems to be broken (I fallback to a dracut prompt). I though I had fixed that one. The problem is that dracut doesn't include all modules required to access the SD card. So I added them to INITRD_MODULES in /etc/sysconfig/kernel in config.sh.

Can you please check on first boot whether the line was properly updated? There is no /etc/sysconfig/kernel file on firstboot. O_o. There should be.

Using dracut prompt, I listed "/lib/modules/3.16.1-2.g2ab6585-lpae/kernel/drivers/mmc/host" folder and only got: mmci.ko omap.ko omap_hsmmc.ko sdhci-pltfm.ko sdhci-tegra.ko sdhci.ko

So, no dw_* mmc modules. But how those mmc modules get added?

According to dracut documentation: https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_adding_kerne...

We should use /etc/dracut.conf or /etc/dracut.conf.d/myconf.conf and NOT /etc/sysconfig/kernel Am I wrong?

It depends on how you generate the initrd. Usually it gets generated by a call to "mkinitrd" which is a wrapper script around dracut these days. That script reads /etc/sysconfig/kernel and adds the modules to the command line as parameters.

...

First boot is ok since kiwi adds dw_* mmc modules in initial initrd. But 2nd boot is broken because generated initrd does not include them.

Yes, exactly. That's why I added them to /etc/sysconfig/kernel. Meh. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Guillaume Gardet

09:47

Le 09/09/2014 11:26, Alexander Graf a écrit :

...

On 09.09.14 11:14, Guillaume Gardet wrote:

...
Le 08/09/2014 17:57, Alexander Graf a écrit :

...
...
...
...
Arndale : Does boot u-boot but fails with a "Wrong Image Format" which should be fixed by SR #248024 (already accepted by Alex, thanks). I fixed it manually before the SR were accepted but I get lots of "cpufreq: __target_index: Failed to change cpu frequency: -22" errors logged but I finaly get a prompt. Yes, you can work around this by echo'ing "performance" into the governor sysfs file. I haven't quite figured out what's going wrong here. Ok. It seems that the CPU voltage cannot be adjusted ("exynos-cpufreq exynos-cpufreq: failed to set cpu voltage to 1100000"). Maybe we are missing a power chip driver in the kernel? Maybe - I have no idea about power chip drivers :). Can you take a look? The power chip driver is included. So maybe just a broken cpu freq for exynos? Maybe, or maybe it's missing infrastructure in the dt.

Maybe.

...

...
...
...
...
...
Serial console and USB2 work, but eth0 seems to have some problems. Second boot seems to be broken (I fallback to a dracut prompt). I though I had fixed that one. The problem is that dracut doesn't include all modules required to access the SD card. So I added them to INITRD_MODULES in /etc/sysconfig/kernel in config.sh.

Can you please check on first boot whether the line was properly updated? There is no /etc/sysconfig/kernel file on firstboot. O_o. There should be. Using dracut prompt, I listed "/lib/modules/3.16.1-2.g2ab6585-lpae/kernel/drivers/mmc/host" folder and only got: mmci.ko omap.ko omap_hsmmc.ko sdhci-pltfm.ko sdhci-tegra.ko sdhci.ko

So, no dw_* mmc modules. But how those mmc modules get added?

According to dracut documentation: https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_adding_kerne...

We should use /etc/dracut.conf or /etc/dracut.conf.d/myconf.conf and NOT /etc/sysconfig/kernel Am I wrong? It depends on how you generate the initrd. Usually it gets generated by a call to "mkinitrd" which is a wrapper script around dracut these days. That script reads /etc/sysconfig/kernel and adds the modules to the command line as parameters.

There is a "Prefer: dracut" in Factory project config and mkinitrd package have been removed from factory. So, I guess we should use dracut directly?

...

...
First boot is ok since kiwi adds dw_* mmc modules in initial initrd. But 2nd boot is broken because generated initrd does not include them. Yes, exactly. That's why I added them to /etc/sysconfig/kernel. Meh.

I am trying to use dracut conf file directly. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Andreas Schwab

09:54

Guillaume Gardet writes:

...

There is a "Prefer: dracut" in Factory project config and mkinitrd package have been removed from factory. So, I guess we should use dracut directly?

The dracut package contains the mkinitrd wrapper. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Guillaume Gardet

10:01

Le 09/09/2014 11:54, Andreas Schwab a écrit :

...

Guillaume Gardet writes:

...
There is a "Prefer: dracut" in Factory project config and mkinitrd package have been removed from factory. So, I guess we should use dracut directly? The dracut package contains the mkinitrd wrapper.

Ok. Does this wrapper also use dracut config file or not? The /etc/sysconfig/kernel is not part of dracut package. mkinitrd package had a template in /var/adm/fillup-templates/sysconfig.kernel-mkinitrd and was probably copied to /etc/sysconfig/kernel. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Matwey V. Kornilov

8 Sep 8 Sep

16:13

New subject: [opensuse-arm] Re: JeOS image status (Beagle, Panda, Arndale and chromebook tested)

08.09.2014 17:26, Guillaume Gardet пишет:

...

Hi,

Fatcory:ARM repo has new JeOS (E17 and XFCE) images but there are some ghost files remaining.

Pandaboard and Beagleboard boots u-boot but then hangs after "Starting kernel ...". Beagle should use a newer u-boot managing FDT for Beagle. Is there any known problem with Factory Kernel for OMAP3/OMAP4 boards?

Same for BeagleBone Black. :( Just tested... -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Guillaume Gardet

16:34

New subject: [opensuse-arm] Re: JeOS image status (Beagle, Panda, Arndale and chromebook tested)

Le 08/09/2014 18:13, Matwey V. Kornilov a écrit :

...

08.09.2014 17:26, Guillaume Gardet пишет:

...
Hi,

Fatcory:ARM repo has new JeOS (E17 and XFCE) images but there are some ghost files remaining.

Pandaboard and Beagleboard boots u-boot but then hangs after "Starting kernel ...". Beagle should use a newer u-boot managing FDT for Beagle. Is there any known problem with Factory Kernel for OMAP3/OMAP4 boards? Same for BeagleBone Black. :( Just tested...

I managed to boot beagleboard using differents load adress for kernel, initrd and fdt. I submitted a SR (#248058) for JeOS. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Matwey V. Kornilov

16:44

New subject: [opensuse-arm] Re: JeOS image status (Beagle, Panda, Arndale and chromebook tested)

08.09.2014 20:34, Guillaume Gardet пишет:

...

I managed to boot beagleboard using differents load adress for kernel,

What could be the problem with the old addresses? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Guillaume Gardet

18:29

New subject: [opensuse-arm] Re: JeOS image status (Beagle, Panda, Arndale and chromebook tested)

Le 08/09/2014 18:44, Matwey V. Kornilov a écrit :

...

08.09.2014 20:34, Guillaume Gardet пишет:

...
I managed to boot beagleboard using differents load adress for kernel, What could be the problem with the old addresses?

Maybe an overlap with u-boot relocation addr. The thing is it does boot with new addr for beagleboard xM. I also updated BB black and panda with those addr. You should try the new image for beaglebone black once SR will be accepted and images rebuilt. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Matwey V. Kornilov

18:34

New subject: [opensuse-arm] Re: JeOS image status (Beagle, Panda, Arndale and chromebook tested)

08.09.2014 22:29, Guillaume Gardet пишет:

...

The thing is it does boot with new addr for beagleboard xM. I also updated BB black and panda with those addr. You should try the new image for beaglebone black once SR will be accepted and images rebuilt.

Yes, thank you. I've fixed current by hands, and now it boots. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Guillaume Gardet

9 Sep 9 Sep

14:44

New subject: [opensuse-arm] Re: JeOS image status (Beagle, Panda, Arndale and chromebook tested)

Le 08/09/2014 20:34, Matwey V. Kornilov a écrit :

...

08.09.2014 22:29, Guillaume Gardet пишет:

...
The thing is it does boot with new addr for beagleboard xM. I also updated BB black and panda with those addr. You should try the new image for beaglebone black once SR will be accepted and images rebuilt. Yes, thank you. I've fixed current by hands, and now it boots.

Matwey, could you try new image which include new load addr and new u-boot, please? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Guillaume Gardet

16:32

Just tested last factory build (201.1) with omap loadaddr and arndale boot type fixes and new u-boot (2014.10-rc2). Dracut initrd is VERY long to generate on (first boot). Any idea why? Beagle has a working console on serial port, but no video output, no USB and no Ethernet (connected on USB). Maybe related to FDT since beagle had switch to FDT recently. Panda has a working console on serial port, video output (HDMI), USB and Ethernet working. :) Arndale does not boot anymore (hang after Starting kernel...). :( Probably a problem with u-boot 2014.10-rc2. No update on Chromebook which does not boot. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Matwey V. Kornilov

10 Sep 10 Sep

07:40

New subject: [opensuse-arm] JeOS image status (BeagleBone Black tested)

Hi, BeagleBone Black. 201.1 boots, networking works, but wicked is completely wicked. There is an issue with USB (see my PATCH in opensuse-kernel, our configuration is invalid). Workaround is to add options musb_hdrc use_dma=0 to /etc/modprobe.d/99-local.conf However, there is another problem for me, I have been trying to run USB with no luck. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

3523

Age (days ago)

3525

Last active (days ago)

List overview

Download

17 comments

4 participants

participants (4)

Alexander Graf
Andreas Schwab
Guillaume Gardet
Matwey V. Kornilov