December 2014 - openSUSE ARM - openSUSE Mailing Lists

Re: [opensuse-arm] Chromebook factory image problems
by Misha Komarovsky 13 Dec '14

13 Dec '14

Hello, I think cgpt repair is crucial part, after i added it right to dd_snow.sh i was able to boot hand crafted u-boot. I can now confirm black screen right after kernel start, it look like same behaviour i have with paz00, after waiting for couple minutes xorg started with garbled screen, this is probably because drm/lcd modules not injected to initrd by dracut (only guess yet, based on this patch series https://git.kernel.org/cgit/boot/dracut/dracut.git/commit/?id=49fe860b22afd… ) Switching to console vty not working, because no logind services started, noticed by killing xorg with double ctrl+alt+backspace. On Fri, Dec 12, 2014 at 12:41 PM, Guillaume Gardet <guillaume.gardet(a)free.fr> wrote: > Forgot to say something on the repair part. You should make a cgpt repair > (sudo cgpt repair /dev/sdX) but then, you must run dd_snow.sh again. > > > Guillaume > > > > Le 12/12/2014 10:24, Misha Komarovsky a écrit : > > Hello, > I compiled myself rc3 from your update to base:system u-boot and doing all > steps from script pointing to correct device. Already double checked couple > times, but maybe still something will try to create partition myself from > scratch. > > On Dec 12, 2014 11:39 AM, "Guillaume Gardet" <guillaume.gardet(a)free.fr> > wrote: >> >> Hi, >> >> The image I gave you is a patched -rc2. So, you will get -rc2 as u-boot >> version. ;) >> >> Did you edit dd_snow.sh script to point to your device ? Check if there is >> no remaining /dev/sdX1 file when your USB stick is unplugged. >> >> U-boot is loaded from 1st partition (as raw image), where the script >> should copy it. >> >> I updated u-boot in Base:System but I am waiting for Dirk to update some >> packages (I have no admin rights in Base:System project) before pushing it >> to Factory. :( >> >> >> Guillaume >> >> >> >> >> Le 12/12/2014 01:47, Misha Komarovsky a écrit : >>> >>> Hello Guillaume, >>> I cant understand where u-boot now lives in snow images. >>> I tried dd_snow.sh script, it asks for run cgpt repair first on fresh >>> created usb stick but no luck, u-boot version still same on start. >>> Filled first partition of usb stick with /dev/zero, still same u-boot >>> 2015.01-rc2, mystic. >>> Got crazy idea maybe it is loaded from lxroot/boot/u-boot.img, >>> replaced it with custom binary, no luck still 2015.01-rc2. >>> Tried deleting gpt partitions one by one and only after partition 1 >>> deleted, it stops to work, but whole partition filled >>> with zeros. >>> >>> On Sun, Dec 7, 2014 at 5:55 PM, Guillaume Gardet >>> <guillaume.gardet(a)free.fr> wrote: >>>> >>>> new_kern is built using vbutil_kernel command. So, you need the vboot >>>> package to be installed: >>>> http://software.opensuse.org/package/vboot?search_term=vboot >>>> >>>> >>>> Guillaume >>>> >>>> >>>> Le 07/12/2014 15:43, Misha Komarovsky a écrit : >>>>> >>>>> dd_snow.sh script need also /tmp/newkern is it symlink to u-boot.img >>>>> or real new kernel? >>>>> >>>>> >>>>> On Sun, Dec 7, 2014 at 4:21 PM, Guillaume Gardet >>>>> <guillaume.gardet(a)free.fr> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Le 06/12/2014 22:19, Misha Komarovsky a écrit : >>>>>>> >>>>>>> Hello, >>>>>>> Just tried to book chromebook images version 253. >>>>>>> Usb wont boot sayin no kernel found, maybe so trick is required? >>>>>> >>>>>> >>>>>> You need an updated u-boot. ;) I am waiting for 2015.01-rc3 (should be >>>>>> out >>>>>> in 2 or 3 days) to push my changes because there are lots of problem >>>>>> with >>>>>> -rc2. >>>>>> If you want to test now, please use this u-boot (based on a modified >>>>>> GIT >>>>>> version): >>>>>> http://guillaume.gardet.free.fr/openSUSE/u-boot.img >>>>>> >>>>>> Then, copy it to your USB stick with this script (update path to >>>>>> u-boot.img >>>>>> and fix your device: /dev/sdX): >>>>>> http://guillaume.gardet.free.fr/openSUSE/dd_snow.sh >>>>>> >>>>>> >>>>>> SD card booting is not working ATM, so please boot from USB (black >>>>>> USB2 >>>>>> slot, not blue USB3 slot). >>>>>> >>>>>> JeOS is working fine. X11 images are broken (strange display once Xorg >>>>>> is >>>>>> booted, only the cursor is ok.) >>>>>> >>>>>> >>>>>> Guillaume >>>>>> >>>>>> >>>>>>> VbTryLoadKernel() start, get_info_flags=0x1 >>>>>>> USB: Register 1313 NbrPorts 3 >>>>>>> USB EHCI 1.00 >>>>>>> 2 USB Device(s) found >>>>>>> USB: Register 1313 NbrPorts 3 >>>>>>> USB EHCI 1.00 >>>>>>> 2 USB Device(s) found >>>>>>> scanning bus for storage devices... 1 Storage Device(s) >>>>>>> found >>>>>>> MMC: no card present >>>>>>> mmc_init err -16, time 1986 >>>>>>> boot_device_mmc.c: boot_device_mmc_scan: mmc_init fail >>>>>>> MMC Device 4 not found >>>>>>> VbTryLoadKernel() found 0 disks >>>>>>> VbSetRecoveryRequest(90) >>>>>>> VbBootDeveloper() - no kernel found on USB >>>>>>> utility.c: VbExBeep: About to beep for 250 ms at 200 Hz. >>>>>>> VbSetRecoveryRequest(0) >>>>>>> leaving VbDisplayScreenFromGBB() with 0 >>>>>>> VbBootDeveloper() - trying fixed disk >>>>>>> >>>>>>> >>>>>>> >From SD i can reach u-boot, it said unknow partition for mmc dev 1 >>>>>>> and >>>>>>> detect capacity is wrong. >>>>>>> >>>>>>> snow # mmc dev 1 >>>>>>> dwmci_send_cmd: DATA ERROR! >>>>>>> dwmci_send_cmd: DATA ERROR! >>>>>>> switch to partitions #0, OK >>>>>>> mmc1 is current device >>>>>>> snow # mmc info >>>>>>> Device: EXYNOS DWMMC >>>>>>> Manufacturer ID: 3 >>>>>>> OEM: 5344 >>>>>>> Name: SL08G >>>>>>> Tran Speed: 50000000 >>>>>>> Rd Block Len: 512 >>>>>>> SD version 3.0 >>>>>>> High Capacity: Yes >>>>>>> Capacity: w.4 GiB >>>>>>> Bus Width: 4-bit >>>>>>> snow # mmc part >>>>>>> ## Unknown partition table >>>>>>> snow # >>>>>>> >>>>>>> If i try to use SD card and USB stick at same time, mainline u-boot >>>>>>> start only XHCI hub and wont detect any storage devices here: >>>>>>> >>>>>>> U-Boot 2015.01-rc2 (Dec 01 2014 - 21:54:38) for snow >>>>>>> >>>>>>> CPU: Exynos5250@1700MHz >>>>>>> Board: Google Snow >>>>>>> I2C: ready >>>>>>> DRAM: 2 GiB >>>>>>> trace: copying 000ad9c0 bytes of early data from 50000000 to bedef000 >>>>>>> trace: enabled >>>>>>> Board PMIC init >>>>>>> TPS>5090 PMIC init >>>>>>> MMC: EXYNOS DWMMC: 0, GXYNOS DWMMC: 1 >>>>>>> SF: Detectmd GD25LQ32 with page size 256 Bytes, erase size 4 KiBl >>>>>>> total >>>>>>> 4 >>>>>>> MiB >>>>>>> *** Warning - bad CRC, using default environment >>>>>>> >>>>>>> Exynos DP init done >>>>>>> RKɽ͵ec-keyb >>>>>>> _ut: lcd >>>>>>> Err: lcd >>>>>>> Net: No ethernet found. >>>>>>> Hit any key`to stop autoboot: 0 >>>>>>> mmc - MMC sub system >>>>>>> >>>>>>> Usage: >>>>>>> mmc info - display info of the current MMC device >>>>>>> mmc read addr blk# cnt >>>>>>> mmc write addr blk# cnt >>>>>>> mmc erase blk# cnt >>>>>>> mmc rescan >>>>>>> mmc part - lists available partition on current mmc device >>>>>>> mmc dev [dev] [part] - show or set current mmc device [partition] >>>>>>> mmc list - lists available devices >>>>>>> mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode >>>>>>> - Set the BOOT_BUS_WIDTH field of the specified device >>>>>>> mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> >>>>>>> - Change sizes of boot and RPMB partitions of specifiel device >>>>>>> mmc partconf dev boot_ack boot_partition partition_access >>>>>>> - Change the bits of the PARTITION_CONFIG field of the specified >>>>>>> device >>>>>>> mmc rst-function dev value >>>>>>> - Change the RST_n_FUNCTION field of the specified device >>>>>>> WARNING: This is a write-once field and 0 / 1 / 2 are the only >>>>>>> valid >>>>>>> values. >>>>>>> mmc setdsr <value> - set DWR register value >>>>>>> >>>>>>> snow # usb storage >>>>>>> USB is stoppel. Please issue 'usb start' first. >>>>>>> snow # usb start >>>>>>> (Re)start USB... >>>>>>> USB0: Register 2000140 NbrPorts 2 >>>>>>> Starting the controller >>>>>>> USB XHCI 1.00 >>>>>>> scanning bus 0 for devices... 1 USB Device(s) found >>>>>>> scanning usb for storage devices... 0 Storage Device(s) >>>>>>> found >>>>>>> snow # usb storage >>>>>>> No storage devices, perhaps not 'usb start'ed..? >>>>>>> snow # >>>>>>> >>>>>>> On Wed, Dec 3, 2014 at 5:19 PM, Guillaume Gardet >>>>>>> <guillaume.gardet(a)free.fr> wrote: >>>>>>>> >>>>>>>> Le 02/12/2014 13:57, Guillaume Gardet a écrit : >>>>>>>>> >>>>>>>>> Le 02/12/2014 00:34, Alexander Graf a écrit : >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 02.12.14 00:19, Misha Komarovsky wrote: >>>>>>>>>>> >>>>>>>>>>> Hello, >>>>>>>>>>> I found that kernel or dtb file in current Chromebook contrib >>>>>>>>>>> factory >>>>>>>>>>> image, tested on version 245, have boot problems. After kernel >>>>>>>>>>> start >>>>>>>>>>> no signs of activity on stdout or serial console. >>>>>>>>>>> >>>>>>>>>>> If i replace linux.vmx and dtb on lxboot partition and modules on >>>>>>>>>>> lxroot with same files from 12.3 dist image for chromebook im >>>>>>>>>>> able >>>>>>>>>>> to >>>>>>>>>>> boot and pass installation fine. >>>>>>>>>>> >>>>>>>>>>> Also after installation and reboot, sd card not bootable at all, >>>>>>>>>>> first >>>>>>>>>>> partition on sdcard changed type code to 0700 and size to 32mb, >>>>>>>>>>> probably cgpt script failed to fix it after installation for some >>>>>>>>>>> reason. >>>>>>>>>>> >>>>>>>>>>> Bundled armsoc x11 driver fail to start because it is for abi 13 >>>>>>>>>>> not >>>>>>>>>>> abi >>>>>>>>>>> 18. >>>>>>>> >>>>>>>> >>>>>>>> I updated armsoc driver just now from 0.0.1 to 1.1.0. It may help. >>>>>>>> :) >>>>>>>> >>>>>>>>>> That does indeed sound pretty broken. I think someone needs to sit >>>>>>>>>> down >>>>>>>>>> and check which of all those components is already done well >>>>>>>>>> enough >>>>>>>>>> upstream to drop our hacks. >>>>>>>>>> >>>>>>>>>> For example, I think u-boot has upstream snow support now, so we >>>>>>>>>> could >>>>>>>>>> just use that. The kernel should be ok as well. >>>>>>>>> >>>>>>>>> >>>>>>>>> Current Factory u-boot-snow (2015.01-rc2) does boot but is not >>>>>>>>> really >>>>>>>>> usable. It seems there is a problem to access SD card. But LCD and >>>>>>>>> keyboard >>>>>>>>> are working fine. :) >>>>>>>>> >>>>>>>>> I will have a look at it. >>>>>>>> >>>>>>>> >>>>>>>> With some patches, I am able to use a USB stick (no external SD) >>>>>>>> with >>>>>>>> upstream u-boot-snow and Factory kernel-lpae does boot ! >>>>>>>> On kernel start, you must wait a little bit because at the >>>>>>>> beginning, >>>>>>>> there >>>>>>>> is just a black screen, followed later by a normal screen and a blue >>>>>>>> YaST >>>>>>>> Firstboot screen. :) >>>>>>>> >>>>>>>> But the are some problems: >>>>>>>> * upstream u-boot does not handle external SD card for an unknown >>>>>>>> reason >>>>>>>> (internal eMMC is usable). Downstream u-boot has no bootz support. >>>>>>>> * keyboard does not work under Linux (you must use an USB keyboard). >>>>>>>> * Second boot is deeply broken. U-Boot is not launched at all >>>>>>>> because >>>>>>>> "cgpt" >>>>>>>> command is applied to /dev/mmcblk0 (internal eMMC) instead of >>>>>>>> /dev/sda >>>>>>>> (USB >>>>>>>> stick) (Kiwi bug?). Once this one manually fixed, u-boot load the >>>>>>>> kernel >>>>>>>> and >>>>>>>> then hang with a black screen. Probably due to missing modules in >>>>>>>> dracut >>>>>>>> initrd. (I will submit a JeOS update once tested) >>>>>>>> * No wifi (at least on 1st boot) >>>>>>>> >>>>>>>> I will send an update (and SR) once tests are passed. >>>>>>>> >>>>>>>> >>>>>>>> Guillaume >>>>>>>> >>>>> >>> >>> >> > -- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 1

[opensuse-arm] Chromebook factory image problems
by Misha Komarovsky 12 Dec '14

12 Dec '14

Hello, I found that kernel or dtb file in current Chromebook contrib factory image, tested on version 245, have boot problems. After kernel start no signs of activity on stdout or serial console. If i replace linux.vmx and dtb on lxboot partition and modules on lxroot with same files from 12.3 dist image for chromebook im able to boot and pass installation fine. Also after installation and reboot, sd card not bootable at all, first partition on sdcard changed type code to 0700 and size to 32mb, probably cgpt script failed to fix it after installation for some reason. Bundled armsoc x11 driver fail to start because it is for abi 13 not abi 18. -- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 10

[opensuse-arm] libisl missing
by Michael Ströder 11 Dec '14

11 Dec '14

HI! It seems something broke in openSUSE_Factory_ARM during the last hour. My builds are marked unresolvable with this message: nothing provides libisl.so.10 needed by gcc48, nothing provides libisl.so.10 needed by libcloog-isl4, nothing provides libisl.so.10 needed by cpp48 Ciao, Michael.

3 5

[opensuse-arm] New version clamav for Raspberry Pi
by Freek de Kruijf 09 Dec '14

09 Dec '14

openSUSE 13.2 has an updated version for clamav. I don't see that version yet in the repositories for the Raspberry Pi. Is there anything I can do to fix that? Should this new version end up the oss repository or in update? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 5

[opensuse-arm] Hello
by Thatsanawan 06 Dec '14

06 Dec '14

Dearest, I am Miss.Thatsanawan Thiansanat,the daughter of Mr.Anuwat Thiansanat former personal adviser to Mr.Sondhi Limthongkul he work under an exiled but still-popular former Prime Minister Thaksin Shinawatra who was ousted in military coup that resulted in the overthrow of the Thai Rak Thai government in September 2006 and I am writing to you regarding a legitimate business proposition/deal in my control which will be executed under a legitimate arrangement. I am writing for the investment of the money left to me by my father,thus I am impelled to request for your assistance to receive this money since I am under surveillance from the authorities herein.Copy and paste below link on your browser for your perusal and better understanding to my email.LINK: http://www.th4u.com/sondhi_limthongkul.htm Very sorry if my mail is against your moral ethics and try to read with understanding and if you find it interested in partnering with me on this project,should write back to me,I shall give you full detail of the money Note:I am contacting you independently and this is absolutely confidential. If you accept this offer, I will appreciate your timely response. Yours Sincerely. Miss.Thatsanawan Thiansanat. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] Kernel-default for 13.2
by Oscar C 05 Dec '14

05 Dec '14

Hi, Does anyone know where can I get the kernel of the 13.2 version? I though I would it find in here http://download.opensuse.org/repositories/openSUSE:/13.2/ports but the repository is not published. :( Thanks, -- Cheers -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] Re: [opensuse-factory] Wanted: Correct power-switch for ARM based Chromebook
by Dr. Werner Fink 04 Dec '14

04 Dec '14

Hi, just to be noted, that is not required to boot with openSUSE. Any nmodern Linux is enough, that is that there should be is the /sys file system and the filled /dev/input/ directory. I'd like to know the output of for n in /dev/input/event*; do udevadm info -a --name=$n done then we might catch the input device for gpio-keys.8 and the power switch therein. Werner > Le 01/10/2014 14:35, Andreas Färber a écrit : > > Hi, > Let's CC opensuse-arm for such ARM questions... > Am 30.09.2014 um 09:29 schrieb Dr. Werner Fink: > > Hi, > > just to be noted that the patch > > rules-add-lid-switch-of-ARM-based-Chromebook-as-a-power-sw.patch > > which includes the line > > SUBSYSTEM=="input", KERNEL=="event*", KERNELS=="gpio-keys.8", > > TAG+="power-switch" > > in the 70-power-switch.rules can not be fully corect. This because the > > "gpio-keys.8" > > is much to general and may cause trouble with other keyboard layouts. > > Therefore I'd like to see the output of such a Chromebook of the command: > > udevadm info -a /dev/input/by-path/*kbd > > which may give the more specific name of the power button. > > > > Werner > > Alex? Guillaume? Can any of you provide the requested information for > the Samsung Chromebook? > > From Chrome OS (kernel 3.8.11), "udevadm info -a > --name=/dev/input/by-path/*kbd" returns: > ********************************************************************** > Udevadm info starts with the device specified by the devpath and then > walks up the chain of parent devices. It prints for every device > found, all possible attributes in the udev rules key format. > A rule to match, can be composed by the attributes of the device > and the attributes from one single parent device. > > looking at device > '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0/event0': > KERNEL=="event0" > SUBSYSTEM=="input" > DRIVER=="" > > looking at parent device > '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3/input/input0': > KERNELS=="input0" > SUBSYSTEMS=="input" > DRIVERS=="" > ATTRS{name}=="cros-ec-i2c" > ATTRS{phys}=="i2c-4-mux (chan_id 0)" > ATTRS{uniq}=="" > ATTRS{properties}=="0" > > looking at parent device > '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e/cros-ec-keyb.3': > KERNELS=="cros-ec-keyb.3" > SUBSYSTEMS=="platform" > DRIVERS=="cros-ec-keyb" > > looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104/104-001e': > KERNELS=="104-001e" > SUBSYSTEMS=="i2c" > DRIVERS=="cros-ec-i2c" > ATTRS{name}=="cros-ec-i2c" > > looking at parent device '/devices/12ca0000.i2c/i2c-4/i2c-104': > KERNELS=="i2c-104" > SUBSYSTEMS=="i2c" > DRIVERS=="" > ATTRS{name}=="i2c-4-mux (chan_id 0)" > > looking at parent device '/devices/12ca0000.i2c/i2c-4': > KERNELS=="i2c-4" > SUBSYSTEMS=="i2c" > DRIVERS=="" > ATTRS{name}=="s3c2410-i2c" > > looking at parent device '/devices/12ca0000.i2c': > KERNELS=="12ca0000.i2c" > SUBSYSTEMS=="platform" > DRIVERS=="s3c-i2c" > ********************************************************************** > > My openSUSE SD card is currently broken, so I cannot test under openSUSE. > > > Independent of the exact GPIO key, the term "ARM based Chromebook" in > > the subject and patch name seems to be rather broad given that there's > > the original Samsung Chromebook, plus the HP Chromebook 11, plus an Acer > > Chromebook based on Tegra, plus some based on Rockchip, etc. which > > likely all use different GPIO configurations. > > Mine is a Samsung Chromebook. > > > Guillaume > -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

2 2

Re: [opensuse-arm] Chromebook factory image problems
by Andreas Färber 04 Dec '14

04 Dec '14

Hi, the black screen may be related to leftover fbdev xorg.d config file - linux-next plus drm patchset is needed for eDP-LVDS bridge or u-boot with simplefb. Having both results in black screen. Regards, Andreas P.S. Sorry for top-posting. Guillaume Gardet <guillaume.gardet(a)free.fr> schrieb: >Le 02/12/2014 13:57, Guillaume Gardet a écrit : >> Le 02/12/2014 00:34, Alexander Graf a écrit : >>> >>> On 02.12.14 00:19, Misha Komarovsky wrote: >>>> Hello, >>>> I found that kernel or dtb file in current Chromebook contrib factory >>>> image, tested on version 245, have boot problems. After kernel start >>>> no signs of activity on stdout or serial console. >>>> >>>> If i replace linux.vmx and dtb on lxboot partition and modules on >>>> lxroot with same files from 12.3 dist image for chromebook im able to >>>> boot and pass installation fine. >>>> >>>> Also after installation and reboot, sd card not bootable at all, first >>>> partition on sdcard changed type code to 0700 and size to 32mb, >>>> probably cgpt script failed to fix it after installation for some >>>> reason. >>>> >>>> Bundled armsoc x11 driver fail to start because it is for abi 13 not abi 18. > >I updated armsoc driver just now from 0.0.1 to 1.1.0. It may help. :) > >>> That does indeed sound pretty broken. I think someone needs to sit down >>> and check which of all those components is already done well enough >>> upstream to drop our hacks. >>> >>> For example, I think u-boot has upstream snow support now, so we could >>> just use that. The kernel should be ok as well. >> >> Current Factory u-boot-snow (2015.01-rc2) does boot but is not really usable. It seems there is a problem to access SD card. But LCD and keyboard are working fine. :) >> >> I will have a look at it. > >With some patches, I am able to use a USB stick (no external SD) with upstream u-boot-snow and Factory kernel-lpae does boot ! >On kernel start, you must wait a little bit because at the beginning, there is just a black screen, followed later by a normal screen and a blue YaST Firstboot screen. :) > >But the are some problems: >* upstream u-boot does not handle external SD card for an unknown reason (internal eMMC is usable). Downstream u-boot has no bootz support. >* keyboard does not work under Linux (you must use an USB keyboard). >* Second boot is deeply broken. U-Boot is not launched at all because "cgpt" command is applied to /dev/mmcblk0 (internal eMMC) instead of /dev/sda (USB stick) (Kiwi bug?). Once this one manually fixed, u-boot load the kernel and then hang with a black screen. Probably due to missing modules in dracut initrd. (I will submit a JeOS update once tested) >* No wifi (at least on 1st boot) > >I will send an update (and SR) once tests are passed. > > >Guillaume > >-- >To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org >To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org >

1 0

[opensuse-arm] Fwd: Data corruption/crash bug in Firefox for armhf
by Guillaume Gardet 03 Dec '14

03 Dec '14

Hi, I forward you an e-mail received on cross-distro ML which may be useful for openSUSE arm. Guillaume -------- Message transféré -------- Sujet : Data corruption/crash bug in Firefox for armhf Date : Wed, 3 Dec 2014 09:44:29 +0000 De : Steve Capper <steve.capper(a)linaro.org> Pour : cross-distro(a)lists.linaro.org <cross-distro(a)lists.linaro.org> Hi folks, As a heads-up, there's a long standing bug in the way Firefox handles register assignment in XPCOM for 32-bit ARM: https://bugzilla.mozilla.org/show_bug.cgi?id=1050258 The symptoms are random data corruption and crashes. (details of bug and fix in the link above). Whilst upstream go through the motions of getting this fix merged, I would encourage you to pull in the fix for now into your packages (or at least keep an eye on this bug report). Cheers, -- Steve _______________________________________________ cross-distro mailing list cross-distro(a)lists.linaro.org http://lists.linaro.org/mailman/listinfo/cross-distro -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] BeagleBone Black updates: HDMI
by Matwey V. Kornilov 01 Dec '14

01 Dec '14

Hi, JeOS from here https://build.opensuse.org/package/show/home:matwey:JeOS-hdmi/LXQT-beaglebo… have HDMI support (not perfect one, I suppose there is some issue with hot-pluging) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3