F21 disk image idea
by Brendan Conoboy
Hi everybody,
There are two significant issues with the disk images in F20 that I
would like to address in F21:
1. Duplicate disk images with and without a VFAT partition. This
doubles QA load and can confuse end users.
2. Unlike x86 spins, images aren't always ready to be used after they're
written to storage. Instead, uboot bits need to be copied into place
using a specific method. This is unintuitive and prone to user error.
In F18 and earlier we simply produced images per supported device, but
the matrix of supported devices and spins makes this prohibitively
expensive, so something else needs to be done. The following proposal
is one way to handle it, but I'm open to anything that improves on
either or both of the aforementioned issues.
The idea: 2 images per device, a board image and an OS image. Here's
how it works:
The board image: This is a very small image that contains the essential
bootloader bits for booting Fedora on a board. It contains the
bootloader if a board doesn't have one, a partition table, and just
enough brains to load the proper dynamic material like extlinux.conf
from the OS image.
The OS image: This contains / (No separate /boot). One per spin is all
we need.
The key idea is that we're trying to decouple the Fedora OS from the
idiosyncrasies of the hardware. We can make lots of board images,
they're really small- they don't even need to be part of the Fedora
release cycle unless we think that is desirable.
For a hypothetical end user with a beaglebone black, the experience is
something like:
download f21-xfce.img
download fedora-arm-bbb.img
write f21-xfce.img to block device
write fedora-arm-bbb.img to same block device
Alternately:
download f21-xfce.img
download fedora-arm-bbb.img
write fedora-arm-bbb.img to same block device
partprobe
write f21-xfce.img to partition 3 of block device
Clearly some decisions need to be made about partition vs block device
for the OS image, but ultimately we resolve issue #1 and simplify issue
#2. Assuming we went with writing a partition instead of a complete
block device, end users would only need to install the per-device disk
image once an could move between Fedora versions by updating the /
partition.
Anyway, that's where my mind is on this one. What do you all think? Can
you make it better?
--
Brendan Conoboy / Red Hat, Inc. / blc(a)redhat.com
10 years, 4 months
ARM Tegra Toshiba AC100 Fedora 19 Remix
by Nicolas Chauvet
Hello,
Here is a simplified process to install the Fedora 19 armhfp remix for the
Toshiba AC100
You need to have:
- The BCT retrieved from your specific AC100 device (as ac100.bct)
- A mini-usb/usb cable
- A sdcard at least 4GB class 10
- The Toshiba AC100 device itself.
# yum install tegrarcm cbootimage
# curl -O
http://dl.kwizart.net/pub/ac100/Fedora-LXDE-AC100-Remix-19-1-sda.raw.xz
# curl -O http://dl.kwizart.net/pub/ac100/Fedora-LXDE-AC100-Remix-19-1-sda.raw.xz.C...
#sha256sum -c Fedora-LXDE-AC100-Remix-19-1-sda.raw.xz.CHECKSUM
Fedora-LXDE-AC100-Remix-19-1-sda.raw.xz: OK
# xzcat Fedora-LXDE-AC100-Remix-19-1-sda.raw.xz > /dev/sd? (the
# partprobe /dev/sd?
# cp -p /run/media/*/__/usr/share/uboot-paz00/u-boot-dtb-tegra.bin .
Plug your AC100 to the host via the USB cable and power-on the device
holding <Crtl> + <Esc>. That will enter the device into the recovery mode
of the tegra device.
Plug the sdcard into the device
# tegrarcm --bct ac100.bct --bootloader u-boot-dtb-tegra.bin
--loadaddr=0x00108000
You should see the uboot text booting the 3.10 kernel,
..., then it should start the initial-setup of Fedora 19 LXDE
Known issues. (please read carefully)
- The right rtc isn't selected by default, the wired rtc is available as
/dev/rtc1
Better is to set time during initial-setup, rely on network time, or do
this on cold boot:
/sbin/hwclock --hctosys -f /dev/rtc1 && /sbin/hwclock --systohc -f /dev/rtc0
- Sometime the screen poweron/off sequence fails, you need to hold power
button
- No sound yet
Updating u-boot, choices:
- Keeping the original proprietary bootloader
You will need to keep booting with the usb cable and tegrarcm from another
host:
- Updating to the provided uboot form the remix.
This version adds non-upstream patches over the fedora uboot package to
support the tegra keyboard. So it's a quite decent choice
- Using the android cyanogen remix from zombah (Recommended).
You need to install the cm-paz00 remix first, then plugin the sdcard after
xzcat step and just poweron. The device will boot using the sdcard.
Installing Fedora into the internal mmc:
Not tested yet.
Next steps is to backport what is needed from 3.14 to 3.13, so I can build
a f20 Remix.
We can envision to support the device by Fedora 21.(exept for the uboot kb).
What will remains is about how to select the right Xorg ddx and probably
few dracuts adjustments.
Resources:
https://dl.kwizart.net/pub/ac100/
http://repos.fedorapeople.org/repos/kwizart/ac100/
http://fedorapeople.org/cgit/kwizart/public_git/kernel.git/log/?h=f19-3.1...
http://ac100.grandou.net/start
https://code.google.com/p/cm-paz00/
http://http.download.nvidia.com/tegra-public-appnotes/
Nicolas (kwizart)
10 years, 4 months
Fedora ARM Status Meeting Minutes 2014-01-08
by Paul Whalen
Thanks to those that were able to join us for the status meeting today, for those unable the minutes are posted below:
Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-08/fedora-meeti...
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-08/fedora-meeti...
Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-08/fedora-meeti...
============================================
#fedora-meeting-1: Fedora ARM status meeting
============================================
Meeting started by pwhalen at 21:01:22 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-08/fedora-meeti...
.
Meeting summary
---------------
* 1a) Aarch64 - Status Update (pwhalen, 21:03:00)
* koji builds are running now- pbrobinson driving builds (bconoboy,
21:04:37)
* Numerous bugs being worked through- mariadb is pressing (bconoboy,
21:07:04)
* More builders being added this month (bconoboy, 21:08:54)
* 2a) F21 - Hardware Support Goals (pwhalen, 21:13:27)
* 3.13 kernel feature set is similar to 3.12, no new hardware
specifically tested yet (bconoboy, 21:20:38)
* Note to BBB users: 3.12 kernel will make BBB video work on F20
release (bconoboy, 21:21:07)
* 3.12.7 will be the one to go with (pbrobinson, 21:21:32)
* 2b) F21 - Installation Images (pwhalen, 21:27:34)
* LINK: Hans' proposed kernel patch plan needs attention
https://lists.fedoraproject.org/pipermail/kernel/2013-December/004752.html
(bconoboy, 21:32:48)
* 4) Open Floor (pwhalen, 21:35:47)
* LINK:
https://lists.fedoraproject.org/pipermail/qa-devel/2014-January/000599.html
(handsome_pirate, 21:36:30)
Meeting ended at 21:49:57 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* pbrobinson (69)
* bconoboy (50)
* dgilmore (38)
* hrw (29)
* handsome_pirate (22)
* pwhalen (21)
* jwb (13)
* masta (12)
* zodbot (12)
* ctyler (4)
* jcapik (3)
* ahs3 (2)
* dmarlin (1)
* agreene (1)
* msalter (0)
* jdisnard (0)
* jonmasters (0)
* ddd (0)
10 years, 4 months
Fedora ARM Status Meeting 2014-01-08
by Paul Whalen
Happy New Year!
Please join us today (Wednesday, January 8th) at 4PM EST (9PM UTC)
for the Fedora ARM status meeting in #fedora-meeting-1 on Freenode.
On the agenda so far..
1) Aarch64 - Status Update
- Problem Packages
2) F21 - Hardware Support Goals
- Installation Images
3) Open Floor
If there is something that you would like to discuss that isn't mentioned
please feel free to bring it up at the end of the meeting or send an email
to the list.
Paul
10 years, 4 months
kernel build on fc19 aarch64 model
by Sandeepa Prabhu
Hi,
I am trying to build kernel on fc19 aarch64 image based on v8 Foundation model.
kernel branch is based on "armv8-uefi-v3.13rc" and toolchain: gcc
version 4.8.1 20130920 (Red Hat 4.8.1-10) (GCC) - using 8GB RAM.
Kernel build is taking for me more than 12 hours, and adding more
threads (-j6 etc) does not improve the build speed. Is this expected ?
or is there a step to improve kernel build?
Thanks,
Sandeepa
10 years, 4 months
FOSDEM ?
by Daniel Veillard
Hello everybody,
I was wondering if we planned something specific in term of presence at
FOSDEM (Brussel 1&2 Feb) for Fedora ARM ?
Maybe by then the Allwinner remix for F20 will be available ;-) and
I would be glad to come with a few Cubietruck or Cubieboard2, that we could
install, show and give a few as gifts, but I have no idea if people plan to
be present, if we can squat part of the Fedora stand (they should have 2 tables
- K area downstairs).
Opinions ? Hans, Rich do you plan to go there ? I would love to be
able to demo KVM on ARM 32bits :-)
Daniel
--
Daniel Veillard | Open Source and Standards, Red Hat
veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | virtualization library http://libvirt.org/
10 years, 4 months
livemedia-creator pyanaconda.nm.SettingsNotFoundError
by Paul Schroeder
Hello all..
Whenever I run livemedia-creator in my F20 ARM virtual machine, I see the
issue shown below. Has anybody else run into this or have an idea as to
why I'm running into this?
Thanks...Paul...
Starting installer, one moment...
Error in sys.excepthook:
anaconda 20.25.15-1 for anaconda bluesky (pre-release) started.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/meh/handler.py", line 161, in
<lambda>
self.handleException(DumpInfo(ExceptionInfo(ty, value, tb), obj))
File "/usr/lib/python2.7/site-packages/pyanaconda/exception.py", line 97,
in handleException
from gi.repository import Gtk
File "/usr/lib/python2.7/site-packages/gi/importer.py", line 68, in
load_module
dynamic_module._load()
File "/usr/lib/python2.7/site-packages/gi/module.py", line 289, in _load
self._overrides_module = importlib.import_module('gi.overrides.' +
self._namespace)
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
File "/usr/lib/python2.7/site-packages/gi/overrides/Gtk.py", line 68, in
<module>
class Widget(Gtk.Widget):
File "/usr/lib/python2.7/site-packages/gi/module.py", line 176, in
__getattr__
interfaces = tuple(interface for interface in
get_interfaces_for_object(info)
File "/usr/lib/python2.7/site-packages/gi/module.py", line 104, in
get_interfaces_for_object
interfaces.append(getattr(module, name))
File "/usr/lib/python2.7/site-packages/gi/module.py", line 313, in
__getattr__
return getattr(self._introspection_module, name)
File "/usr/lib/python2.7/site-packages/gi/module.py", line 215, in
__getattr__
wrapper = metaclass(name, bases, dict_)
File "/usr/lib/python2.7/site-packages/gi/types.py", line 194, in __init__
register_interface_info(cls.__info__.get_g_type())
TypeError: must be an interface
Original exception was:
Traceback (most recent call last):
File "/usr/sbin/anaconda", line 1118, in <module>
anaconda._intf.setup(ksdata)
File "/usr/lib/python2.7/site-packages/pyanaconda/ui/tui/__init__.py",
line 166, in setup
should_schedule = obj.setup(self.ENVIRONMENT)
File
"/usr/lib/python2.7/site-packages/pyanaconda/ui/tui/hubs/summary.py", line
35, in setup
should_schedule = TUIHub.setup(self, environment=environment)
File
"/usr/lib/python2.7/site-packages/pyanaconda/ui/tui/hubs/__init__.py", line
64, in setup
spoke.initialize()
File
"/usr/lib/python2.7/site-packages/pyanaconda/ui/tui/spokes/network.py",
line 56, in initialize
if nm.nm_device_setting_value(name, "connection", "slave-type"):
File "/usr/lib/python2.7/site-packages/pyanaconda/nm.py", line 646, in
nm_device_setting_value
raise SettingsNotFoundError(name)
pyanaconda.nm.SettingsNotFoundError: SettingsNotFoundError('eth0',)
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/usr/sbin/anaconda", line 58, in exitHandler
for loop in device.parents:
NameError: global name 'device' is not defined
Error in sys.exitfunc:
2014-01-02 20:58:11,841: Install failed: novirt_install failed
2014-01-02 20:58:11,985: ERROR: Image creation failed: novirt_install failed
--
---
Paul B Schroeder
paul.schroeder "at" drakerenergy "dot" com
10 years, 4 months
Getting Clang to work.
by Sean Omalley
I was trying to get clang to work in mock. I thought I would share how far I had gotten, before the end of the holidays and life picks up again. You can probably add -mstrict-align to the CFLAGS section for arm. This actually worked to build a few packages. (I also built a package to actually move symlink gcc to clang in case of hard coding, but I don't think it is needed.)
in your mock /etc/mock/fedora-20-xxx.cfg file you need to add something like:
config_opts['files']['etc/profile.d/mystuff.sh'] = """
export CC=clang
export CXX=clang
export CFLAGS="-std=gnu89 -O3 -g -mstackrealign -Wall "
# ...
"""
and from the rpm package you need to edit /usr/lib/rpm/find-debuginfo.sh
something like:
--- //usr/lib/rpm/find-debuginfo.sh 2013-09-09 08:11:23.000000000 -0400
+++ /home/so/find-debuginfo.sh 2014-01-01 12:32:25.360449406 -0500
@@ -53,6 +53,9 @@
case "$1" in
--strict-build-id)
strict=true
+if [ ${CC} = "clang" ]; then
+ strict=false
+fi
;;
--run-dwz)
run_dwz=true
10 years, 4 months
