Re: [fedora-arm] Network not working on Devkit8000
On 05/14/2012 06:34 PM, Brendan Conoboy wrote: On 05/14/2012 03:19 PM, Robert Nelson wrote: What "issue" are you seeing with bconoby's F17-hardfp image? (theres no dm9000 on the beagle xm) If I understand correctly, the Beagleboard XM's ethernet interface is not working with the official FC17 kernel-omap (3.3.4). It's visible, but does not pass traffic. I can confirm that this was the case with the the XM's hardfp nightly image I downloaded Friday. The interface comes up as usb0 (as seen in dmesg), but spits out "device not ready" errors when using NetworkManager or ifup/down to establish a connection. I swapped in Angstrom's kernel (3.0.17 I think) and the network interface came up as eth0 and functioned properly. The image I downloaded from the nightly page Sunday didn't boot at all. I can supply console output if desired; I'm downloading the latest image now to see if anything is different. It also looks like the kernels and initrds up to this point don't have all of the usb storage drivers included. I had my XM rigged to boot the kernel from SD and use a USB HDD as /, but to debug these images I've only been able to use the SD card. Rich ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Network not working on Devkit8000
On 05/14/2012 03:19 PM, Robert Nelson wrote: What "issue" are you seeing with bconoby's F17-hardfp image? (theres no dm9000 on the beagle xm) If I understand correctly, the Beagleboard XM's ethernet interface is not working with the official FC17 kernel-omap (3.3.4). It's visible, but does not pass traffic. -- Brendan Conoboy / Red Hat, Inc. / b...@redhat.com ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Network not working on Devkit8000
On Mon, May 14, 2012 at 5:12 PM, Jared K. Smith wrote: > On Mon, May 14, 2012 at 5:58 PM, Danilo Câmara wrote: >> Early on boot I see this message: >> Net: Net Initialization Skipped >> No ethernet found. >> Hit any key to stop autoboot: 0 >> >> I'm able to login as root but I can not bring up the network: > > For what little it's worth, I'm having the same problem on my > BeagleBoard XM (using bconoboy's F17-hardfp images as of last week), > but haven't yet had a chance to try Angstrom to see if it's a software > problem or a hardware problem. I'm strongly suspecting there's > something wrong with the images, but haven't had time to track down > exactly where the problem lies. What "issue" are you seeing with bconoby's F17-hardfp image? (theres no dm9000 on the beagle xm) Regards, -- Robert Nelson http://www.rcn-ee.com/ ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Network not working on Devkit8000
On Mon, May 14, 2012 at 4:58 PM, Danilo Câmara wrote: > Devkit8000 is a BeagleBoard clone that has an Enthernet interface. > I've installed Fedora 14 ARM as described in > http://elinux.org/BeagleBoardFedora using the following command: > $ sudo ./mk_mmc.sh --mmc /dev/sdb --uboot beagle_xm Patches welcome*, as I DO NOT have the Devkit8000, so i'm unable to test/fix it... https://github.com/RobertCNelson/stable-kernel Remember this is also using an external kernel, with fedora userspace... > > Early on boot I see this message: > Net: Net Initialization Skipped > No ethernet found. > Hit any key to stop autoboot: 0 > > I'm able to login as root but I can not bring up the network: > > # modprobe dm9000 > [ 275.382568] dm9000 Ethernet Driver, V1.31 > > # ifup eth0 > Device eth0 does not seem to be present, delaying initialization. > > In the original Angstrom image that came with the board, the network > is identified during boot and works fine: > brd: module loaded > loop: module loaded > dm9000 Ethernet Driver, V1.31 > eth0: dm9000a at c88ae000,c88b2400 IRQ 185 MAC: 00:11:22:33:44:55 (chip) > > I used "--uboot beagle_xm" because it also has Enthernet interface, > but I tried with "beagle_bx" and "beagle_cx" with the same results. That's because, the only difference between those boards, is the disabling of eth0 on bootup... But still your using the Beagle MLO/u-boot.img on a non Beagle device... (In the past i had to separate them to using different version of MLO/u-boot.bin, but those days are past, so there's zero bootloader differences now between those 3..) Regards, -- Robert Nelson http://www.rcn-ee.com/ ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Debugging our kernels under qemu + gdb
On 14 May 2012 16:57, Jon Masters wrote: > On 05/13/2012 04:34 PM, Michael Hope wrote: >> On 12 May 2012 22:12, Richard W.M. Jones wrote: >>> On Fri, May 11, 2012 at 01:41:43PM -0700, Brendan Conoboy wrote: On 05/11/2012 01:04 PM, Richard W.M. Jones wrote: > Has anyone tried to debug our Fedora/arm kernels under qemu-system-arm? > (In this case, the host is also arm, but I don't think that matters.) Richard, FYI, we as of a few hours ago have nearly-official F17-beta images for versatile express on the following page: http://scotland.proximity.on.ca/arm-nightlies/ There's a link for vexpress and vexpress+x rootfs images. A second link provides a kernel, initramfs, and script for starting qemu. Note that vexpress is much faster than versatile and allows more ram (1GB). Recommend you try this out! >>> >>> So one issue appears to be lack of PCI support (according to Linaro's >>> notes: https://wiki.linaro.org/PeterMaydell/QemuVersatileExpress). >>> >>> Unfortunately all of the virtio hardware is PCI-based, so it doesn't >>> seem like this is going to work for the virt tools :-( >> >> Hi Richard. The plan is to use virtio-mmio and use Device Tree to set >> where the virtio devices are. virtio-mmio is in the mainline kernel >> and in the queue for QEMU. > > Note, we're not using dtb (device tree) yet in the qemu kernel. To do > that properly, we'll need to get a qemu that works with U-Boot, etc. I > know Linaro have put such a combination together, right? Should any of > that be working with upstream bits yet? Brendan mentioned he'd tried > poking briefly at the U-Boot that Linaro put together but it apparently > didn't boot on our qemu (I know upstream was missing e.g. the model > instantiation for the hardware memory controller, etc. in vexpress). > > I guess I could/should ping Peter Maydell? Is he the best contact? Peter or Ricardo, yip. Ricardo has a good handle on the integration work that's been done and the upstream versions. We've standardised on the vexpress-a9 model as it's neutral, has a good amount of RAM, and has good support in upstream QEMU and mainline Linux. The vexpress-a15 isn't as tested but goes up to 2 GB and will probably be the base model for KVM. -- Michael ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Network not working on Devkit8000
On Mon, May 14, 2012 at 5:58 PM, Danilo Câmara wrote: > Early on boot I see this message: > Net: Net Initialization Skipped > No ethernet found. > Hit any key to stop autoboot: 0 > > I'm able to login as root but I can not bring up the network: For what little it's worth, I'm having the same problem on my BeagleBoard XM (using bconoboy's F17-hardfp images as of last week), but haven't yet had a chance to try Angstrom to see if it's a software problem or a hardware problem. I'm strongly suspecting there's something wrong with the images, but haven't had time to track down exactly where the problem lies. -- Jared Smith ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Network not working on Devkit8000
Devkit8000 is a BeagleBoard clone that has an Enthernet interface. I've installed Fedora 14 ARM as described in http://elinux.org/BeagleBoardFedora using the following command: $ sudo ./mk_mmc.sh --mmc /dev/sdb --uboot beagle_xm Early on boot I see this message: Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: 0 I'm able to login as root but I can not bring up the network: # modprobe dm9000 [ 275.382568] dm9000 Ethernet Driver, V1.31 # ifup eth0 Device eth0 does not seem to be present, delaying initialization. In the original Angstrom image that came with the board, the network is identified during boot and works fine: brd: module loaded loop: module loaded dm9000 Ethernet Driver, V1.31 eth0: dm9000a at c88ae000,c88b2400 IRQ 185 MAC: 00:11:22:33:44:55 (chip) I used "--uboot beagle_xm" because it also has Enthernet interface, but I tried with "beagle_bx" and "beagle_cx" with the same results. Any help is welcome. Thanks. -- -- Danilo Câmara ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Test request: epiphany on armv7hl
On Mon, May 14, 2012 at 02:20:04PM -0600, Daniel Drake wrote: > On Mon, May 14, 2012 at 2:17 PM, Richard W.M. Jones wrote: > > With the caveat that I was doing it remotely (X over ssh), yes it > > segfaulted for me as well. > > Thanks for the quick test! Just for the record, which hardware did you test > on? Sorry, I forgot to say: Trim Slice. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Test request: epiphany on armv7hl
On Mon, May 14, 2012 at 2:17 PM, Richard W.M. Jones wrote: > With the caveat that I was doing it remotely (X over ssh), yes it > segfaulted for me as well. Thanks for the quick test! Just for the record, which hardware did you test on? Daniel ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Test request: epiphany on armv7hl
On Mon, May 14, 2012 at 01:58:04PM -0600, Daniel Drake wrote: > Hi, > > OLPC are seeing a javascript-triggered crash in WebKit on armv7hl. > > I'd love to know if this is reproducible on other platforms. Anyone up > for running a quick test on non-OLPC? > > Test case is: > 1. Install epiphany > 2. Open epiphany > 3. Go to gmail.com and login > 4. See if it manages to load the inbox, scroll around a bit, try > opening some mails > > Must be done on top of F17 armv7hl (not armv5). > > On OLPC XO-1.75 ot will almost always crash while loading, before you > get a chance to scroll. > https://bugs.webkit.org/show_bug.cgi?id=85076 With the caveat that I was doing it remotely (X over ssh), yes it segfaulted for me as well. -- $ epiphany GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. ** (epiphany:31454): WARNING **: Failed to open file: /usr/share/bookmarks/default-bookmarks.html ** Message: console message: https:[...] @208: No relay set (used as window.postMessage targetOrigin), cannot send cross-domain message ** Message: console message: @0: Unsafe JavaScript attempt to access frame with URL https://mail.google.com/mail/?shva=1 from frame with URL https:[...] Domains, protocols and ports must match. ** Message: console message: @0: Unsafe JavaScript attempt to access frame with URL https:[...] from frame with URL https:[...] Domains, protocols and ports must match. Segmentation fault -- $ rpm -q epiphany epiphany-3.4.1-2.fc17.armv7hl Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Test request: epiphany on armv7hl
Hi, OLPC are seeing a javascript-triggered crash in WebKit on armv7hl. I'd love to know if this is reproducible on other platforms. Anyone up for running a quick test on non-OLPC? Test case is: 1. Install epiphany 2. Open epiphany 3. Go to gmail.com and login 4. See if it manages to load the inbox, scroll around a bit, try opening some mails Must be done on top of F17 armv7hl (not armv5). On OLPC XO-1.75 ot will almost always crash while loading, before you get a chance to scroll. https://bugs.webkit.org/show_bug.cgi?id=85076 Thanks, Daniel ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] A couple fixes fixes for ARM Fedora-17 kernels to enable performance monitoring tools
I have a trimslice that I am using to make sure that various performance tools such as papi, perf, oprofile, and systemtap work on. There are a couple of bugzilla entries that have patches, but the patches are not in the RPMs: Bug 741325 - ARM fc14 kernels does not provide hardware perf counter support Bug 816761 - ARM fc17 kernel-devel missing /usr/src/kernels/3.3.2-8.fc17.armv7hl.tegra/arch/arm/mach-tegra/include/mach It would be nice to get these patches into the Fedora kernel RPMs, so people can use the performance tools on ARM platform out of the box rather than having to have people roll their own RPMs with those fixes. bz741325 is specific to trimslice, but there are a number of people using trimslice machines for development work. It is a one line patch that initializes the performance monitoring unit hardware driver and makes it available to perf, oprofile, and papi. bz816761 patch to the spec file copies over needed include files for ARM machine into kernel-*-devel so that systemtap can compile instrumentation on the arm machine. -Will ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Daily Koji Compare Stats
Mon May 14 09:05:01 EDT 2012 f17 : arm vs PA Same |Newer |Older |Local | Remote | Missing | -- 10999 | 31 | 135 |1 | 472 | 379 | http://142.204.133.82/jon/koji/kc.17.diff.html f18 : arm vs PA Same |Newer |Older |Local | Remote | Missing | -- 9905 | 22 | 1291 |4 | 545 | 2115 | http://142.204.133.82/jon/koji/kc.18.diff.html ARM Build Status Wiki: https://fedoraproject.org/wiki/Architectures/ARM/Fedora17_rawhide Mon May 14 09:16:54 EDT 2012 ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Using livemedia-creator on ARM
I have a draft of the instructions for using livemedia-creator (Anaconda/Lorax) for creating a disk image on ARM: https://fedoraproject.org/wiki/Architectures/ARM/Installer I have only tested this on the Trim Slice, and it seems to work well. This assumes you have adequate backing storage (hard disk) to hold the resulting images. If the host system does not have a hard drive, some alternate storage may need to be set up to hold the disk image (i.e., NFS or iSCSI). Although other ARM platforms should be recognized by Anaconda/Lorax, I don't have any specific U-Boot scripts or templates set up for them yet. Note: I am trying to get these changes upstream, but they will not be accepted in F17 (too late in the cycle), so I am keeping them in a separate repo for testing. Please let me know if you have any questions or have suggestions for improvement. Thank you, d.marlin ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Debugging our kernels under qemu + gdb
On 05/14/2012 03:37 AM, Richard W.M. Jones wrote: > There's something quite broken about our qemu package. I haven't > looked at what it is yet, but at the moment I'm using qemu built from > upstream git for all testing. I'll try to look at what's going on > with the qemu package later. Note, our qemu package in F16 runs the images just fine. The issue I'm referring to is specific to dtb and U-Boot environment emulation. But if there are other issues - sure, take a look! Jon. ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Debugging our kernels under qemu + gdb
On Mon, May 14, 2012 at 12:57:09AM -0400, Jon Masters wrote: > On 05/13/2012 04:34 PM, Michael Hope wrote: > > On 12 May 2012 22:12, Richard W.M. Jones wrote: > >> On Fri, May 11, 2012 at 01:41:43PM -0700, Brendan Conoboy wrote: > >>> On 05/11/2012 01:04 PM, Richard W.M. Jones wrote: > Has anyone tried to debug our Fedora/arm kernels under qemu-system-arm? > (In this case, the host is also arm, but I don't think that matters.) > >>> > >>> Richard, > >>> > >>> FYI, we as of a few hours ago have nearly-official F17-beta images > >>> for versatile express on the following page: > >>> > >>> http://scotland.proximity.on.ca/arm-nightlies/ > >>> > >>> There's a link for vexpress and vexpress+x rootfs images. A second > >>> link provides a kernel, initramfs, and script for starting qemu. > >>> Note that vexpress is much faster than versatile and allows more ram > >>> (1GB). Recommend you try this out! > >> > >> So one issue appears to be lack of PCI support (according to Linaro's > >> notes: https://wiki.linaro.org/PeterMaydell/QemuVersatileExpress). > >> > >> Unfortunately all of the virtio hardware is PCI-based, so it doesn't > >> seem like this is going to work for the virt tools :-( > > > > Hi Richard. The plan is to use virtio-mmio and use Device Tree to set > > where the virtio devices are. virtio-mmio is in the mainline kernel > > and in the queue for QEMU. > > Note, we're not using dtb (device tree) yet in the qemu kernel. To do > that properly, we'll need to get a qemu that works with U-Boot, etc. I > know Linaro have put such a combination together, right? Should any of > that be working with upstream bits yet? Brendan mentioned he'd tried > poking briefly at the U-Boot that Linaro put together but it apparently > didn't boot on our qemu (I know upstream was missing e.g. the model > instantiation for the hardware memory controller, etc. in vexpress). There's something quite broken about our qemu package. I haven't looked at what it is yet, but at the moment I'm using qemu built from upstream git for all testing. I'll try to look at what's going on with the qemu package later. > I guess I could/should ping Peter Maydell? Is he the best contact? > > Jon. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
