samedi, octobre 6 2018

A Fedora 28 Remix for Tegra using i3

This is dedicated to older Tegra such as Tegra20, Tegra30 and Tegra114. It can work on Tegra K1, but at this time, using Fedora 29 is a better choice. Specially as Fedora 29 on Tegra K1 and later have support for GPU acceleration with nouveau.

The image integrates the grate-driver that provides a reverse-engineer mesa driver (FLOSS, but not yet upstream). This only advertises OpenGL 1.4 yet, but it can at least run glxgears fine. This is not the case with the softpipe driver on Tegra20.

There is also a HW video decode driver using [libvdpau_tegra||en].

Please use mpv or vlc from [RPM Fusion||en|RPM Fusion] for video acceleration.

This spin was only tested on Toshiba AC100 and Trimslice.

* Download [Tegra Fedora 28 Respin via torrent||en]

* Install the disk image on a sdcard

> SDCARD=/dev/sdc (to be adapted)

> xzcat Fedora-remix-tegra-i3-28-20180918.n.0-sda.raw.xz | sudo dd of=${SDCARD} bs=4M

You need a recent u-boot version with Extlinux support. I recommends 2018.09 release or later

To update the bootloader on tegra20 devices please see

Remind that paz00 still lacks keyboard support for the bootloader upstream. To have keyboard support you can to get:
There is a pre-built u-boot binary based on this tree in the same directory.

If you want to install the packaged grate-driver from an official Fedora 28 image:
> curl -o /etc/yum.repos.d/fedora-ac100.repo
This will replace mesa libdrm, but you can keep the fedora kernel

Interested in having an official i3 spin in Fedora?
For Tegra, it will depends on the upstreaming of the grate-driver, but I've submitted a PR to have a generic i3 spin. As some arm or aarch64 based devices that can output display, but may not be able to have enough accelerated desktop capabilities (Unless using a proprietary or downstream driver that won't be in Fedora). See if you want to help:

mardi, septembre 26 2017

RPM Fusion is near 10 years old

10 years ago, one of the internal root Certificate Authority was generated for the project. The infra wasn't production ready yet, but few months later there was support for Fedora 8. One of the earlier message from the developers mailing list.

At that time, the idea to form a community shaped against Fedora was to bring people to work together on the same complementary repository for the distribution. Remember how Fedora started ? So this is still one root of the project.

samedi, mai 9 2015

RPM Fusion free available for fedora 22

As this concern was raised in several places already, I would like to announce that the RPM Fusion free repository is published since few days for Fedora 22.

At this time, only the free section is available, but it's also there for armhfp at the same time as i686 and x86_64. (no aarch64 but that's can be a secondary step if I manage to have a builder).

It's only a rebuilt for f21 packages made for f22. Several f22 specific updates will be pushed progressively.

If you previously had installed the rpmfusion-free-release for f22, but miss the updates for any reason, maybe you will need to re-install the release package or verify previously modified configuration files.

I'm still working hard to get the infrastructure migrated to Koji/distgit and it's unlikely that the migration process will be finished in time for f22 GA, but at least it will be possible for users to install working packages and for package maintainers to provide the needed bugfix updates for f22.

If you can help fixing FTBFS package for f22, please see the bug tracker for f22.

dimanche, mars 2 2014

mesa 10.2 from git for Fedora 20

This has started as a attempt to test the improvements of the freedreno ARM driver, so I've made an updated mesa package (and newer libdrm) specially for testing.

You can grab it installing the kwizart-release repository and

yum update --enablerepo=kwizart-testing libdrm\* mesa\*

The updated mesa 10.2 package from git20140209 is available for i686 x86_64 and armv7hl. The final version is scheduled in 3 months from now (so it could be in Fedora 21 by default). This is a different branch from the 10.1 branch to be released soon.

I'm not interested in xorg-x11-drv-vmware in this case, and there is an ABI break behind, so you need to:

yum remove xorg-x11-drv-vmware

Also an interesting feature of the mesa 10.2 branch is the OpenMAX IL feature on AMD devices. I try to maintain libomxil-bellagio within fedora, so I'm interested in feedbacks on this topic. The AMD GPU I can test on doesn't seem to be compatible with the feature. But there are also probably few issues with libomxil-bellagio given the lack of upstream activity. Still you can test using:

yum install --enablerepo=kwizart-testing mesa-omx-drivers

VLC from RPM Fusion should be compatible with OpenMAX IL, and gstreamer has a plugin that should enter into Fedora at some point (currently in review).

Also the packaging git work is currently ahead of the fedora rawhide spec, so there are probably few patches that can be used in the next fedora package.

dimanche, novembre 24 2013

nvidia instancied kernel modules with the RPM Fusion package

With the new akmod-nvidia-331.20-3.fc19 released today comes an option to build the nvidia kernel modules several times. This is useful as advertised in the nvidia FAQ to "Minimize the software overhead when driving many GPUs in a single system" . That, specially when each GPU is processing different workload such as with CUDA applications.

You can use it by setting the following RPM macro, with up to 8 different kernel modules:
#File /etc/rpm/macros.nvidia - Set the number of nvidia kernel modules to build (up to 8)
%_nv_build_module_instances 2

Then you can use akmod-nvidia to automatically rebuild the kernel modules with the above option:
$ sudo yum install akmod-nvidia kernel-devel (or kernel-PAE-devel when using kernel-PAE)

If you previously had the package installed, and want to rebuild with the new option, you can use:
$ sudo akmods --force akmod nvidia

This will build the specified number of kernel modules along with the nvidia-frontend.ko
$ rpm -qpl ~builder/rpmbuild/RPMS/x86_64/kmod-nvidia-3.11.8-200.fc19.x86_64-331.20-3.fc19.x86_64.rpm

Then, you can modprobe the appropriate kernel modules, as mentioned in the FAQ, this command will assign two cards to the nvidia0 kernel module instance:
$ sudo modprobe nvidia0 NVreg_AssignGpus="0:01:00.0,0:02:00.0"

The Official documentation for the RPM Fusion packaged nvidia driver is still at nVidia How on the RPM Fusion Wiki.