Skip to main content

From FUDCon, setting up Fedora 13 Artwork

Due to the poor network in Seneca College, my message will be short. Final release name is known as Goddard, American scientist behind one of first rockets using liquid fuel . Fedora 13 Artwork wiki has been created as kick-off for designers. Feel free to submit your concept as sketch, illustration, collage as long it follow the theme related to rocketry, space, galaxies.
Labels:

Comments

Post a Comment

Popular posts from this blog

gnome-shell useless with nouveau driver

Running rawhide 20090924 from desktop system , I test gnome-shell to explore its features (seems Activities name is inspired from Sugar interface . Very disappointing because the shell needs hardware acceleration i.e 3D support. Even Sugar interface did a much better job despite its simple look. Picture speaks itself.
7 comments
Read more

Using AMD RX Vega driver OpenCL on Fedora 29

The Raven Ridge APU is very capable processor to handle OpenCL inside some applications like Blender, Darktable and Gimp. Unfortunately, the current implementation from Mesa, clover, stuck to 1.3, is not supported. AMD released their driver 18.40 with OpenCL2.0+ targeting only Red Hat Enterprise Linux/Cent OS 6.10 and 7.5 in addition of Ubuntu LTS. The good new is the former rpm format can be used on Fedora. The graphical part of Raven Ridge is Vega 8, basically a cut-down of Vega56 or Vega64 meaning choosing either driver for RX Vega . The instruction is provided for extracting the rpm files but here is  some requirements for OpenCL: kernel-devel (provided by Fedora repository) amdgpu-dkms dkms libopencl-amdgpu-pro opencl-amdgpu-pro-icd Once done, applications needing OpenCL will automatically detect the driver located on /opt/amdgpu/lib64 . Blender will list as unknown AMD GPU and Darktable will enable it. OpenCL from official AMD driver enabled on Darktable ...
Post a Comment
Read more

No network on Fedora 9 x86_64 follow up

Following my post related to NetworkManager . I have found out about the workaround. If you have x86_64 system with 4GB support enabled, you should disable it in order to make NetworkManager work. I am not sure if that bug affects other distributions so, possibly the bug may be related to the x86_64 kernel. Let see if my theory can be verified.
9 comments
Read more