April 2014 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Re: [opensuse-kernel] [PATCH] ARM: update armv7 default config - master branch
by Guillaume Gardet 11 Jun '14

11 Jun '14

CC'ing -arm ML Le 03/04/2014 13:48, Alexander Graf a écrit : > > On 03.04.14 13:47, Guillaume Gardet wrote: >> Le 03/04/2014 13:39, Alexander Graf a écrit : >>> On 02.04.14 20:48, Guillaume Gardet wrote: >>>> Hi, >>>> >>>> please find in attachment an ARMv7 -default config update to fix Ethernet and HDMI output on iMX6 SABRE Lite board. It also add initial support to USB on this board. >>>> >>>> This patch is against master branch. >>>> >>>> Signed-off-by: Guillaume GARDET <guillaume.gardet(a)opensuse.org> >>> Moving modules from =m to =y is the wrong answer usually. Why don't the modules work as modules? >> I do not know. >> Modules are loaded with no error but they do not work. The fact is switching FEC and SDMA from =m to =y fix the problems. It is true for 13.1 and master branches. > > Yes, I've spent some time myself to fix FEC as a module on i.MX53 a while ago. We really don't want to even start going into the game of enabling random devices as =y on the default config, otherwise we'll end up with a 30MB kernel on all boards. I agree, but the fact is we have no board which works really fine ATM. See: http://en.opensuse.org/openSUSE:Supported_ARM_boards#13.1 There are only RPi and Chromebook which have a correct support (and they use _downstream_ kernels). But chromebook boot only once and need a hack to boot then (I am on it, Marcus gave me some hints to fix that using kiwi hooks) and had a lot of X stability problems (random freezes, X crash when switching VT). Raspberry Pi is not booting at all as is (kiwi partitioning bug) and need a hack to get a bootable image: http://en.opensuse.org/HCL:Raspberry_Pi#Known_Issues Maybe Beaglebone or Beaglebone black have a good support? (I do not have such devices and there is no feedback on our wiki) Now, SABRE Lite is the only board where I got graphics working with upstream kernel. The last blocking problem on this board is USB which is not working, even with imx_v6_v7_defconfig. The main things to do for boards support are : 1) Get boards booting Linux (should be a minimum). 2) Have a maximum number of supported devices (USB, sound, video, etc.) on each board (even if it does mean to have '=y' instead of '=m'). 3) Clean-up / fix our kernel / kernel configs to use modules (=m) instead of built-in (=y) when it is possible. I think we should use again our Trello board or setup a wiki page or something to write down what must be done for each board and who is taking care of each task. What do you think about that? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

[opensuse-arm] Package clamav for ARM
by Freek de Kruijf 06 May '14

06 May '14

Some time ago I generated the clamav rpm package in OBS as a copy from that package in the security project. Somehow the status of this rpm for different ARM architectures is Not Public. I wonder why. I can't find this package in a repository except my own. The oss repository only contains the srcrpm of clamav. Is this a bug? -- 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

4 4

[opensuse-arm] BeagleBone Black: openSUSE 13.1
by Matwey V. Kornilov 30 Apr '14

30 Apr '14

Hi, I've just checked JeOS. Now, 13.1 works as described in https://en.opensuse.org/HCL:BeagleBone_Black -- 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] systemd waiting on dev-ttySAC3.device
by Andreas Färber 29 Apr '14

29 Apr '14

Hello, On Exynos5 devices I've seen the following problem with Factory rootfs. For example, using upstream v3.14 plus a .dts patch with exynos_defconfig (devtmpfs) on Arndale Octa: [ 10.900000] systemd[1]: Expecting device dev-ttySAC3.device... Expecting device dev-ttySAC3.device... [...] [ TIME ] Timed out waiting for device dev-ttySAC3.device. [DEPEND] Dependency failed for Serial Getty on ttySAC3. systemd proceeds printing to console=ttySAC3,115200n8 until reaching target Graphical Interface, but I do not get a login prompt on serial. The YaST firstboot worked on first run, too. No HDMI output, and network not blinking/lit. Booting is currently broken on 3.15.0-rc2-00205-g9a60ee1, and we do not have a building kernel-exynos package, therefore vanilla 3.14 plus http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/… Initially I had seen this issue on a downstream kernel 3.4.x on my ODROID-XU with s/ttySAC3/ttySAC2/g. There, I was able to log in via ssh and confirm that /dev/ttySAC2 was in fact present. Any suggestions how to debug what is going wrong there? Thanks, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

[opensuse-arm] Package clamav for ARM
by Freek de Kruijf 28 Apr '14

28 Apr '14

Some time ago I generated the clamav rpm package in OBS as a copy from that package in the security project. Somehow the status of this rpm for different ARM architectures is Not Public. I wonder why. I can't find this package in a repository except my own. The oss repository only contains the srcrpm of clamav. Is this a bug? -- 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

1 0

[opensuse-arm] Does NOT boot on Pandaboard-ES Rev B3
by 孙钰 28 Apr '14

28 Apr '14

Hi all, Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because the Modification of Elpida DDR2 RAM Here follows the serial port messages: U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM: identified size not same as expected size identified: 0 expected: 40000000 Regards, SunYu -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 15

[opensuse-arm] Can't make recent Raspberry Pi image to work
by Freek de Kruijf 28 Apr '14

28 Apr '14

I downloaded the image from http://download.opensuse.org/repositories/devel:/ARM:/13.1:/Contrib:/Raspbe… Used the command "xzcat [image].raw.xz | dd bs=4M of=/dev/sdc; sync" to write the image to the SD card. While the SD card was still plugged in, I gave the command # parted /dev/sdc --script -- resize 1 1049kB 185MB which changed the FAT partition to 185MB, see the output below. # parted /dev/sdc --script print Model: SD/MMC Card Reader (scsi) Disk /dev/sdc: 3980MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 185MB 184MB primary fat16 boot, lba, type=0e 2 212MB 976MB 764MB primary ext4 type=83 Running this SD card in the Raspberry Pi does not bring up the network, although I do see activity on the network. -- fr.gr. member openSUSE 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

3 2

[opensuse-arm] Freedreno vs. X11 module ABI mismatch
by Andreas Färber 28 Apr '14

28 Apr '14

Hi, On my IFC6410 board running Factory I am seeing the following error: [ 14129.554] (II) LoadModule: "freedreno" [ 14129.556] (II) Loading /usr/lib/xorg/modules/drivers/freedreno_drv.so [ 14129.557] (II) Module freedreno: vendor="X.Org Foundation" [ 14129.557] compiled for 1.15.0, module version = 1.0.0 [ 14129.557] ABI class: X.Org Video Driver, version 15.0 [ 14129.557] (EE) module ABI major version (15) doesn't match the server's version (17) [ 14129.557] (II) UnloadModule: "freedreno" [ 14129.557] (II) Unloading freedreno [ 14129.557] (EE) Failed to load module "freedreno" (module requirement mismatch, 0) Rob Clark, the freedreno author, told me that this indicates the xf86-video-freedreno driver was built against a too old X11, i.e. X11 is newer than freedreno. However, I observed xf86-video-freedreno package [1] going from "Blocked" to "Succeeded", without a new package becoming available via OBS web interface (and not getting published either). Among others there's BuildRequires: pkgconfig(xorg-server) which I had copied from another xf86-video-* package and would expect it to trigger a rebuild if X11 is updated... Here's my installed versions: i | libdrm_freedreno1 | Paket | 2.4.53-1.1 | armv7hl | openSUSE-Factory-repo-oss i | xf86-video-freedreno | Paket | 1.0.0-2.1 | armv7hl | openSUSE-Factory-repo-oss i | xorg-x11-driver-video | Paket | 7.6_1-13.1 | armv7hl | openSUSE-Factory-repo-oss i | xorg-x11-server | Paket | 7.6_1.15.99.902-1.1 | armv7hl | openSUSE-Factory-repo-oss Any hints what might be going wrong here? Thanks, Andreas [1] https://build.opensuse.org/package/show/openSUSE:Factory:ARM/xf86-video-fre… -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 6

Re: [opensuse-arm] SR for openSUSE:13.1:Ports kernel
by Alexander Graf 28 Apr '14

28 Apr '14

On 27.04.14 17:23, Matwey V. Kornilov wrote: > > > I don't know. If it is the best solution, then we can. Basically, what > I need is to fetch the 11 patches from Kernel:openSUSE-13.1 > However, I am not aware of how does kernel updates usually get into > Ports tree. > Please don't top post :). I don't think we have a really good solution for this. The "usual" way we envisioned things to work is that openSUSE:<release> just contains everything necessary for the release. Any board we have to enable after that process should just get a Contrib subproject where we can add newer versions of kernels etc specific to that board. In parallel all the changes go into Factory where we can then enable that board for the next <release> version of openSUSE. However, getting hardware support working for a release is so incredibly hard that I'm fairly sure we'd end up with an empty set of hardware platforms if we really went with that plan. So we started loosing up the requirements. I'm not sure up to which point it does make sense to loosen them though. Would it help you if we create a Contrib for the BeagleBone and add you as admin for that? There you could linkpac the JeOS package inside and copypac the latest kernel and then have your own playing ground for that particular platform without necessarily relying on us. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] osc broken in Factory:ARM
by Andreas Färber 27 Apr '14

27 Apr '14

Hey, Recently Dirk assured that the latest version of python-M2Crypto got published for fixing a library load error on osc co. Unfortunately since then I am seeing a different error: $ osc getbinaries openSUSE:Factory:ARM xf86-video-freedreno standard armv7l cannot import name HTTPSConnection M2Crypto is needed to access https://api.opensuse.org in a secure way. Please install python-m2crypto. $ osc co Xorg:X11 xf86-video-freedreno cannot import name HTTPSConnection M2Crypto is needed to access https://api.opensuse.org in a secure way. Please install python-m2crypto. python-M2Crypto is installed: i | python-M2Crypto | Paket | 0.22.3-1.1 | armv7hl | openSUSE-Factory-repo-oss Any help? Thanks, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

Re: [opensuse-arm] OpenSuse 13.1 on beaglebone
by Sad Clouds 27 Apr '14

27 Apr '14

On Fri, 25 Apr 2014 08:32:44 +0400 "Matwey V. Kornilov" <matwey.kornilov(a)gmail.com> wrote: > Instructions look very common, the page might be created from > template. However, you help in editing the page would be highly > appreciated. 24.04.2014 23:26 ???????????? "Sad Clouds" < > cryintothebluesky(a)googlemail.com> ???????: > > > On Thu, 24 Apr 2014 09:40:06 +0400 > > Matwey Kornilov <matwey.kornilov(a)gmail.com> wrote: > > > > > Hi, > > > > > > It worked some time ago, but you need fetch images from > > > home:matwey:beaglebone > > > > I'm confused. I came to https://en.opensuse.org/HCL:BeagleBone_Black > > via Google. I assumed that page contained official instructions on > > how to get 13.1 up and running on Bealgebone Black. > > > > If it doesn't work, why have a page with instructions on it? Has > > anyone tested it, or did someone create it for a laugh? > > Never mind, I'll give another distro a try. Cheers. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 12

[opensuse-arm] SR for openSUSE:13.1:Ports kernel
by Matwey Kornilov 26 Apr '14

26 Apr '14

Hello, All. Could you please either accept or reply something on 224264? -- Best regards! Posted using Hotdoged on Android -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] OpenSuse 13.1 on beaglebone
by Sad Clouds 24 Apr '14

24 Apr '14

Hello, could I ask if OpenSuse 13.1 works with beaglebone? I followed instructions on https://en.opensuse.org/HCL:BeagleBone_Black However I get as far as "Starting kernel" and then nothing else happens. Any ideas? U-Boot 2013.04 (Mar 17 2014 - 15:34:07) I2C: ready DRAM: 512 MiB WARNING: Caches not enabled NAND: No NAND device found!!! 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 Net: <ethaddr> not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 mmc0 is current device SD/MMC found on device 0 1948 bytes read in 5 ms (379.9 KiB/s) Running bootscript from mmc0 ... ## Executing script at 80200000 kerneladdr=0x80200000 ramdiskaddr=0x81000000 mmc0 is current device 4500264 bytes read in 571 ms (7.5 MiB/s) 65308180 bytes read in 8153 ms (7.6 MiB/s) 21959 bytes read in 13 ms (1.6 MiB/s) ## Loading init Ramdisk from Legacy Image at 81000000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 65308116 Bytes = 62.3 MiB Load Address: 00000000 Entry Point: 00000000 ## Flattened Device Tree blob at 80f80000 Booting using the fdt blob at 0x80f80000 Using Device Tree in place at 80f80000, end 80f885c6 Starting kernel ... -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] Re: Asking for help about ARM version of SuseLinux
by Alexander Graf 14 Apr '14

14 Apr '14

Hi Mathias, Sorry for the late reply - I was on vacation and only now managed to work myself through my inbox far enough for your email :). Do you still see that problem? What exactly fails for you? Alex On 04.03.14 13:51, Mathias Bauer wrote: > Hi together, > > thanks for the hint with the IRC, I already joined. > > Any help is greatly appreciated! > > BTW: Maybe I wasn't clear enough in my mail, while I use clang for my > own code, the build of gcc that I tried was done with gcc (the same > gcc 4.7.2. that was already installed). > > (I had to remove Andrew from the list of recipients, my mail server > for whatever reason did not accept this mail address) > > Regards, > Mathias > > Am 04.03.14 13:04, schrieb Michael Meeks: >> Hi guys, >> >> An old friend is asking for some help with openSUSE on ARM - IMHO >> it's >> great that he wants to use openSUSE there. Alex / Andrew - is there any >> chance you can find the best person to help him and/or help out. >> >> Mathias - have you tried #opensuse-arm on irc.freenode.net ? that's >> prolly a good place to hang out too. >> >> Many thanks ! >> >> Michael. >> >> On Tue, 2014-03-04 at 09:55 +0100, Mathias Bauer wrote: >>> I'm currently trying to do some hacking on OpenSuse on an Arndale >>> Board, >>> but I ran into problems that I couldn't solve by myself and also didn't >>> find any solution by searching. Maybe you can point me to someone who >>> can help me? >>> >>> I'm using clang, but had problems with the exception handling. It was >>> activated for ARM processors recently, but it still has bugs that I >>> wanted to track down. >>> >>> So I tried to build the libgcc_s with debug information (that's where >>> the code for the stack unwinding is located, if I'm not wrong), but for >>> the life of me I can't compile gcc4.7 on this system. It's an Armdale >>> Board running OpenSuse 12.3 (image directly from OpenSuse, completely >>> unmodified). >>> >>> Do you know someone at Suse or a mailing list where I could get some >>> help? It's starting to drive me mad. >>> >>> All the best, >>> Mathias >> -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] kiwi does not find boot partition in Factory
by Guillaume Gardet 12 Apr '14

12 Apr '14

Hi, with Factory ARM images, kiwi is not able to find boot device on firstboot and we get: ******************************************************************************** [1397088002.636285] Including oem partition info file [1397088002.701788] Searching for boot device... [1397088022.334972] Failed to find boot device ! [1397088022.344577] rebootException: reboot in 120 sec... ******************************************************************************** It seems that modules from initrd are not loaded. In this case MMC modules are not loaded whereas they are in initrd. It works fine with 13.1 images with same kiwi version. I guess there is a change between 13.1 and Factory and kiwi may need some update so that modules get loaded? Any idea? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 4

[opensuse-arm] chroot - /bin/bash not found?
by Per Jessen 11 Apr '14

11 Apr '14

For getting my Minix Neo X7 to run openSUSE, I have been using the chroot method as described here: http://en.opensuse.org/HCL:Chroot It has worked quite well on my laptop, but today I wanted to move it to a different machine. So I grabbed the latest rootfs image: openSUSE-13.1-ARM-JeOS.armv7-rootfs.armv7l-1.12.1-Build33.1.tbz With this when I try to chroot, I get "/bin/bash not found". With Build32 it works though: openSUSE-13.1-ARM-JeOS.armv7-rootfs.armv7l-1.12.1-Build32.2.tbz -- Per Jessen, Zürich (12.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- 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] 13.1:Ports and Factory:ARM
by Guillaume Gardet 10 Apr '14

10 Apr '14

Hi Dirk, Hi Alex, We need you for some updates. 13.1:Ports: * JeOS-vexpress64 is setup to be build for armv7l instead of AArch64. => Just switch JeOS-vexpress64 build flag. * All DTB files are broken => Update from latest Base:System is a solution but we will lost Beaglebone Black fixes. * E17-beaglebone must be rebuild (failed due to a broken worker apparently) Factory:ARM: * JeOS-sabrelite, E17-sabrelite and XFCE-sabrelite links need to be created. Would it be possible to setup a contrib project for iMX6 SABRE Lite board, please? So that, I (and others, if any) can get things working for this board, as suggested by Alex. Regards, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] dtb-source
by Matwey V. Kornilov 03 Apr '14

03 Apr '14

Hi, It would be great if dtb-source version were in sync with the kernel one. What do you think, is it worth to reimplement dtb-source, using buildrequires: kernel-source instead of using linux tarball? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 8

[opensuse-arm] Re: [opensuse-kernel] [PATCH] ARM: update armv7 default config - master branch
by Alexander Graf 03 Apr '14

03 Apr '14

On 03.04.14 13:47, Guillaume Gardet wrote: > Le 03/04/2014 13:39, Alexander Graf a écrit : >> On 02.04.14 20:48, Guillaume Gardet wrote: >>> Hi, >>> >>> please find in attachment an ARMv7 -default config update to fix Ethernet and HDMI output on iMX6 SABRE Lite board. It also add initial support to USB on this board. >>> >>> This patch is against master branch. >>> >>> Signed-off-by: Guillaume GARDET <guillaume.gardet(a)opensuse.org> >> Moving modules from =m to =y is the wrong answer usually. Why don't the modules work as modules? > I do not know. > Modules are loaded with no error but they do not work. The fact is switching FEC and SDMA from =m to =y fix the problems. It is true for 13.1 and master branches. Sascha, you're the one closest to upstream i.MX development that I'm aware of. Do you have any idea why we have to set FEC and SDMA to =y to make them work? Have you ever tried to use them as modules? Thanks, Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 4

[opensuse-arm] kernel default for armv7l
by Dirk Müller 03 Apr '14

03 Apr '14

Hi, anyone working on the xen bits build failure in kernel-default on armv7l on Factory right now? Tia, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] SR for JeOS
by Guillaume Gardet 03 Apr '14

03 Apr '14

Hi, please accept SR#228774 to update/fix 13.1 images: https://build.opensuse.org/request/show/228774 and SR#228775 to update factory images: https://build.opensuse.org/request/show/228775 Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

Re: [opensuse-arm] qemu-systaem-aarch64
by Alexander Graf 02 Apr '14

02 Apr '14

On 02.04.14 15:25, Valery Reznic wrote: > > > ----- Original Message ----- > > From: Alexander Graf <agraf(a)suse.com> > > To: opensuse-arm(a)opensuse.org > > Cc: > > Sent: Wednesday, April 2, 2014 4:08 PM > > Subject: Re: [opensuse-arm] qemu-systaem-aarch64 > > > > > > On 02.04.14 15:05, Valery Reznic wrote: > >> Hello. > >> > >> I was using openSUSE's > > http://csgraf.de/aarch64/openSUSE-12.3-AArch64-JeOS.alpha1.raw.tgz > >> > >> to run it under Foundation model. > >> > >> > >> Now I am trying to run it under qemu (qemu-2.0.0-rc0) on x86-64 > Fedora 20: > >> > >> > >> qemu-system-aarch64 -hda openSUSE-12.3-AArch64-JeOS.alpha1.raw > >> > >> > >> Results: > >> > >> VNC server running on `::1:5900' > >> > >> qemu: fatal: Trying to execute code outside RAM or ROM at > > 0x0000000008000000 R00=00000000 R01=00000000 R02=00000000 R03=00000000 > >> R04=00000000 R05=00000000 R06=00000000 R07=00000000 > >> R08=00000000 R09=00000000 R10=00000000 R11=00000000 > >> R12=00000000 R13=00000000 R14=00000000 R15=08000000 > >> PSR=400001d3 -Z-- A svc32 > >> s00=00000000 s01=00000000 d00=0000000000000000 > >> s02=00000000 s03=00000000 d01=0000000000000000 > >> s04=00000000 s05=00000000 d02=0000000000000000 > >> s06=00000000 s07=00000000 d03=0000000000000000 > >> s08=00000000 s09=00000000 d04=0000000000000000 > >> s10=00000000 s11=00000000 d05=0000000000000000 > >> s12=00000000 s13=00000000 d06=0000000000000000 > >> s14=00000000 s15=00000000 d07=0000000000000000 > >> s16=00000000 s17=00000000 d08=0000000000000000 > >> s18=00000000 s19=00000000 d09=0000000000000000 > >> s20=00000000 s21=00000000 d10=0000000000000000 > >> s22=00000000 s23=00000000 d11=0000000000000000 > >> s24=00000000 s25=00000000 d12=0000000000000000 > >> s26=00000000 s27=00000000 d13=0000000000000000 > >> s28=00000000 s29=00000000 d14=0000000000000000 > >> s30=00000000 s31=00000000 d15=0000000000000000 > >> > >> FPSCR: 00000000 > >> Aborted (core dumped) > >> > >> > >> It's happened with both selinux on and off. > >> > >> I tried to add to the command '-M virt' - same result. (Only crash > > happened quicker) > >> > >> What am I missing? How can I run aarch64 system under > qemu-system-aarch64? > > > > I'm fairly sure you still need to pass in a -kernel to QEMU so it can > I tried it too - without any luck. > > > find something to execute. That said, I haven't tried the current > > aarch64 system emulation patch set from Peter yet. Upstream QEMU > > definitely does not work with aarch64 system emulation today. > So, why then last qemu (2.0.0rc0) has option to build qemu-system-aarh64? It has some preliminary support - probably KVM only. The AArch64 system target is WIP. > And where can I find Peter's patch set? > > > By the way, what confused me is the output of > qemu-system-aarch64 -M ? > Supported machines are: > versatileab ARM Versatile/AB (ARM926EJ-S) > lm3s811evb Stellaris LM3S811EVB > z2 Zipit Z2 (PXA27x) > connex Gumstix Connex (PXA255) > sx1 Siemens SX1 (OMAP310) V2 > realview-eb ARM RealView Emulation Baseboard (ARM926EJ-S) > cubieboard cubietech cubieboard > vexpress-a9 ARM Versatile Express for Cortex-A9 > lm3s6965evb Stellaris LM3S6965EVB > realview-pbx-a9 ARM RealView Platform Baseboard Explore for Cortex-A9 > musicpal Marvell 88w8618 / MusicPal (ARM926EJ-S) > mainstone Mainstone II (PXA27x) > terrier Terrier PDA (PXA270) > n810 Nokia N810 tablet aka. RX-44 (OMAP2420) > xilinx-zynq-a9 Xilinx Zynq Platform Baseboard for Cortex-A9 > nuri Samsung NURI board (Exynos4210) > realview-eb-mpcore ARM RealView Emulation Baseboard (ARM11MPCore) > verdex Gumstix Verdex (PXA270) > canon-a1100 Canon PowerShot A1100 IS > akita Akita PDA (PXA270) > smdkc210 Samsung SMDKC210 board (Exynos4210) > integratorcp ARM Integrator/CP (ARM926EJ-S) (default) > sx1-v1 Siemens SX1 (OMAP310) V1 > kzm ARM KZM Emulation Baseboard (ARM1136) > highbank Calxeda Highbank (ECX-1000) > n800 Nokia N800 tablet aka. RX-34 (OMAP2420) > collie Collie PDA (SA-1110) > realview-pb-a8 ARM RealView Platform Baseboard for Cortex-A8 > vexpress-a15 ARM Versatile Express for Cortex-A15 > spitz Spitz PDA (PXA270) > cheetah Palm Tungsten|E aka. Cheetah PDA (OMAP310) > none empty machine > midway Calxeda Midway (ECX-2000) > tosa Tosa PDA (PXA255) > virt ARM Virtual Machine > borzoi Borzoi PDA (PXA270) > versatilepb ARM Versatile/PB (ARM926EJ-S) > > To me looks like most (or even all) of them are arm, not arm8. Yes, The AArch64 target will be able to run AArch32 models as well. The same holds true for qemu-system-x86_64 which can run i386 boards or qemu-system-ppc64 which can run 32bit boards too. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] qemu-systaem-aarch64
by Valery Reznic 02 Apr '14

02 Apr '14

Hello. I was using openSUSE's http://csgraf.de/aarch64/openSUSE-12.3-AArch64-JeOS.alpha1.raw.tgz to run it under Foundation model. Now I am trying to run it under qemu (qemu-2.0.0-rc0) on x86-64 Fedora 20: qemu-system-aarch64 -hda openSUSE-12.3-AArch64-JeOS.alpha1.raw Results: VNC server running on `::1:5900' qemu: fatal: Trying to execute code outside RAM or ROM at 0x0000000008000000 R00=00000000 R01=00000000 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=00000000 R14=00000000 R15=08000000 PSR=400001d3 -Z-- A svc32 s00=00000000 s01=00000000 d00=0000000000000000 s02=00000000 s03=00000000 d01=0000000000000000 s04=00000000 s05=00000000 d02=0000000000000000 s06=00000000 s07=00000000 d03=0000000000000000 s08=00000000 s09=00000000 d04=0000000000000000 s10=00000000 s11=00000000 d05=0000000000000000 s12=00000000 s13=00000000 d06=0000000000000000 s14=00000000 s15=00000000 d07=0000000000000000 s16=00000000 s17=00000000 d08=0000000000000000 s18=00000000 s19=00000000 d09=0000000000000000 s20=00000000 s21=00000000 d10=0000000000000000 s22=00000000 s23=00000000 d11=0000000000000000 s24=00000000 s25=00000000 d12=0000000000000000 s26=00000000 s27=00000000 d13=0000000000000000 s28=00000000 s29=00000000 d14=0000000000000000 s30=00000000 s31=00000000 d15=0000000000000000 FPSCR: 00000000 Aborted (core dumped) It's happened with both selinux on and off. I tried to add to the command '-M virt' - same result. (Only crash happened quicker) What am I missing? How can I run aarch64 system under qemu-system-aarch64? Thank you, Valery. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1