Fedora ARM 12 on IGEPv2 (Beagle Board clone)
by Matthew Wilson
Hi all,
I would like to introduce myself to the group. I have recently
received an IGEPv2 board [1], which is based on the Beagle Board, but
with wifi, bluetooth, ethernet, and more RAM. I'm still at the "wow,
it's tiny and it runs Linux" stage. I should get a bit more time over
the next month and Christmas to play around properly with it.
I'm new to embedded development, but neither new to Linux nor ARM
(writing my first ARM assembly some 15 years ago). However, for the
past 6 years I've not even built a Linux kernel, preferring to use the
default kernel in Fedora for simplicity :)
Firstly, a thank you to those involved in Fedora ARM for getting it to
this stage. If I get the time, I'd really like to contribute some
(probably small) effort to help get Fedora ARM working well on the
IGEPv2 and Beagle Board. As I progress, I'd like to know what I can
do to help.
In the meantime, I have some questions. Apologies in advance if these
seem simple.
1) There are various different kernels from different sources. I'm
used to there being a small set of "right" kernels (that is, Fedora's
idea of "right") for x86. I fully appreciate that different ARM-based
boards are quite different in capabilities (like different instruction
set variants).
a) Is there likely to be some standardised vanilla Fedora ARM kernel
source? (Or is that simply the source RPM available for Fedora?)
Then patches /could/ be offered for the more common systems (e.g.
Beagle Board & clones, SheevaPlug).
b) Would it then make sense to offer these as pre-built RPMs for common systems?
c) Is there any guidance on which version is good to use as a base?
I've seen quite different kernel versions being used (from 2.6.27 to
2.6.31).
2) I understand a little bit about the different calling conventions,
FP differences (e.g. soft FPU versus VFP), and instruction set
differences (v5 versus v7).
a) Can the kernel can be safely built with a different instruction set
targeted? (I know there are different optimisation options passed to
GCC. Apologies if this seems a bit newbie-ish.)
b) For FP-heavy programs (e.g. ogg encoding), is it possible to build
the packages with VFP/NEON but still get them to work in a soft FPU
system? I'd imagine any call to an external library would have to
somehow be defined to use a different calling standard.
3) There seem to be some missing dependencies in the packages in the
current Fedora ARM repository. For example, emacs is requiring
libotf, which doesn't seem to be there in the repository. And
likewise with the xorg-x11-font* packages needing ttmkdir. I'm
confused as to how the RPM could have been successfully built without
it. What am I missing?
4) I see there has been some discussion over unaligned data access.
(Oh, I remember that from the ARM2 days.) It seems as if the
Cortex-A8 cores allow unaligned data access when set up to do so [2].
Does this, in any way, help with the compatibility of packages
targetting Cortex-A8?
5) I've managed to get various source packages missing from the Fedora
ARM repositories to compile successfully (natively). I guess there is
a reason why there are not in the repos right now -- is that reason
down to time and priorities, or is there some blocking bugs with many
of these packages?
I look forward to being able to contribute something back into Fedora!
Kind regards,
Matthew
[1] http://www.igep-platform.com/index.php?option=com_content&view=article&id...
[2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0344j/Beih...
8 years, 4 months
- 11
- 15
iSCSI on ARM
by Chris Tyler
I've been testing iSCSI on an OpenRD-Client system (F12).
This is the configuration:
target: F12 x86_64 system running netbsd-iscsi service, 100GB target
available
initiator: F12 ARM openrd-client running iscsi and iscsid service,
logged in to 100GB target
On the 100G target I have an ext3 filesystem. Under low load, this works
fine, but under high load it fails, leading to data corruption.
On the target, /var/log/messages shows:
Apr 11 09:53:40 hongkong iscsi-target: pid 1930:iscsi.c:1149:
***ERROR*** Bad "Opcode": Got 1 expected 5.
Apr 11 09:53:40 hongkong iscsi-target: pid 1930:target.c:1318:
***ERROR*** iscsi_write_data_decap() failed
Apr 11 09:53:40 hongkong iscsi-target: pid 1930:iscsi.c:1149:
***ERROR*** Bad "Opcode": Got 49 expected 5.
Apr 11 09:53:40 hongkong iscsi-target: pid 1930:target.c:1318:
***ERROR*** iscsi_write_data_decap() failed
Apr 11 09:53:40 hongkong iscsi-target: pid 1930:iscsi.c:1149:
***ERROR*** Bad "Opcode": Got 13 expected 5.
Apr 11 09:53:40 hongkong iscsi-target: pid 1930:target.c:1318:
***ERROR*** iscsi_write_data_decap() failed
Apr 11 09:53:40 hongkong iscsi-target: pid 1930:iscsi.c:1149:
***ERROR*** Bad "Opcode": Got 38 expected 5.
Apr 11 09:53:40 hongkong iscsi-target: pid 1930:target.c:1318:
***ERROR*** iscsi_write_data_decap() failed
...snip...
On the initiator, /var/log/messages shows:
Apr 12 21:47:57 fedora-arm kernel: connection2:0: Got CHECK_CONDITION
but invalid data buffer size o
f 0
Apr 12 21:47:57 fedora-arm kernel: connection2:0: detected conn error
(1020)
Apr 12 21:47:57 fedora-arm kernel: sd 4:0:0:0: [sdb] Unhandled error
code
Apr 12 21:47:57 fedora-arm kernel: sd 4:0:0:0: [sdb] Result:
hostbyte=0x04 driverbyte=0x00
Apr 12 21:47:57 fedora-arm kernel: sd 4:0:0:0: [sdb] CDB: cdb[0]=0x2a:
2a 00 08 03 34 a8 00 04 00 00
Apr 12 21:47:57 fedora-arm kernel: end_request: I/O error, dev sdb,
sector 134427816
Apr 12 21:47:57 fedora-arm kernel: quiet_error: 118 callbacks suppressed
Apr 12 21:47:57 fedora-arm kernel: Buffer I/O error on device sdb,
logical block 16803477
Apr 12 21:47:57 fedora-arm kernel: lost page write due to I/O error on
sdb
Apr 12 21:47:57 fedora-arm kernel: Buffer I/O error on device sdb,
logical block 16803478
Apr 12 21:47:57 fedora-arm kernel: lost page write due to I/O error on
sdb
...snip...
There are no transport errors reported on the target or initiator.
Wondering if this was an ARM or iSCSI issue, I repeated the same test
using an x86_64 initiator against the same target, and was successful
(however, on reflection, it's cabled at 100 Mbps instead of 1Gbps).
To provoke these errors, one need only write a large file quickly:
dd if=/dev/zero of=/mnt/iscsi/test1 bs=1M count=1024
Because the target was showing "opcode" errors, I wondered if CPU
alignment on the ARM was an issue, but I have /proc/cpu/alignment set to
3 (fixup+warn).
Any suggestions?
-Chris
14 years
- 2
- 2
Storcenter ix-200 > Fedora?
by Frank Murphy
Have been refered to this list from my email:
http://lists.fedoraproject.org/pipermail/mini/2010-April/000006.html
At the moment the only admin\interaction with the ix-200,
is through http:lanip.
--
Regards,
Frank Murphy
UTF_8 Encoded, Fedora.x86 64-32 Hybrid
14 years, 1 month
- 1
- 0
- ← Newer
- 1
- Older →