Home Home > Base-system
Sign up | Login

Deprecation notice: openSUSE Lizards user blog platform is deprecated, and will remain read only for the time being. Learn more...

Archive for the ‘Base System’ Category

ATI/AMD fglrx 8.850 Catalyst 11.5 available for openSUSE 11.2, 11.3, 11.4, Factory

May 14th, 2011 by

New version of catalyst 11.5 / fglrx 8.850 available

Please refer to my previous article where all the installation procedure is explained.

At least after a wrong 11.4 version, and a first buggy 11.5 catalyst version, the new one is finally build and ready to install from the repo. Like for 11.3 I’ve clean up all previous version which are not xpic, so everybody can easily know which drivers he has to install.
I’ve resigned all rpm with my key. And the tests made show them working.

Warning

Some instabilities have been reported. In case of crash like no keyboard, mouse, and blackscreen on reboot. Try to shutdown properly your computer with the shutdown poweroff button. On reboot, just add 3 at the end of grub line to restart in console mode.
Then with yast or zypper you can always try the previous version.

All credits to Sebastian Siebert (freespacer) : 11.5 article

What about tumbleweed, factory?

Users have reported that version 8.850 of catalyst 11.5 compile correctly under Tumbleweed with 2.6.38 kernel and the driver is ready for kernel 2.6.39, so until xorg change too much and then AMD support for the new version, installing the 11.4 version should work

For factory, I’ve build a repository (see previous article) that can be used, and fglrx build

Numbers ?

Month Unique IP Number of visits Pages Hits Bandwidth
Jan 2011 2355 6411 19688 35263 16.63 GB
Feb 2011 2906 7719 26383 41142 22.37 GB
Mar 2011 8055 21157 228494 258613 59.13 GB
Apr 2011 10592 29129 418281 437416 76.87 GB

All served by openSUSE powered server!

AMD/ATI Catalyst 11.4 pre-build package … next week

May 3rd, 2011 by

Just a quick note for those of you asking themselve why the new catalyst 11.4 (fglrx 8.841) are not yet published on the non-official repository, there’s an answer : hollidays 🙂

I’ll be back from Greece next week, so I will publish them around the 15th May.

In the meantime, you can counsult this article from Sebastian Siebert

Have fun!

Gnome3 launch party @ Zürich report

April 10th, 2011 by

Gnome3 launch party in Zürich, April 8th 2011

ETHZ building

A group of 20 people met in ETHZ F26.3 room Friday afternoon (3pm to 7pm). To assist the Gnome 3 Launch party. We were expecting more people, but a so sunny weather, and a Monday off in Zürich doesn’t help to keep people inside after a long winter. 🙂

Marcus Moeller showed us a deep overview of the whole Gnome 3 desktop, with the strength and weakness (non yet finished features or controversial ones).

Then there’s some talks about features, what will happen unity/ubuntu/gnome etc …

On my side I did a late presentation about what’s openSUSE project is, and its associated SUPER COOL tools like OBS and susestudio.
It was supposed to last 15 minutes long. I was asked only Tuesday night to do it! But in fact we spend more than half an hour demoing obs and susestudio. Really was cool to do.

openSUSE project presentation

A special thanks to Biju Gopi Thilaka for setting up that party.

Biju Gopi was kind enough to share his slides with us, so keep reading …

(more…)

GNOME3 iso by fcrozat and ATI radeon driver… a quick easy fix!

April 10th, 2011 by

Hi all,

For some time I wanted to check out GNOME3 and gnome-shell… My current chipset is ATI M92 RV710 and while the thermal performance with the proprietary driver is somewhat what I expect, the open source radeon driver does overheat my laptop a lot compared to flgrx. For the time being, fglrx isn’t really a choice because it just borgs the ‘activities’ bar on top… And until ATI fixes their driver, there’s no other choice than running with the standard radeon drm driver, which does provide a very pleasant experience with GNOME3 / gnome-shell.

For all that matters, KMS is to be enabled, period, full stop. And from this point… we have two options regarding power management:

1. Dynamic Frequency switching (not really working for me);
2. Profile based frequency switching (does provide what I need);

For all that matters regarding ‘profile based frequency switching’ we have 5 profiles available:

  • “default” uses the default clocks and does not change the power state. This is the default behavior.
  • “auto” selects between “mid” and “high” power states based on the whether the system is on battery power or not. The “low” power state are selected when the monitors are in the dpms off state.
  • “low” forces the gpu to be in the low power state all the time. Note that “low” can cause display problems on some laptops; this is why auto only uses “low” when displays are off.
  • “mid” forces the gpu to be in the “mid” power state all the time. The “low” power state is selected when the monitors are in the dpms off state.
  • “high” forces the gpu to be in the “high” power state all the time. The “low” power state is selected when the monitors are in the dpms off state.

Now, what I did might not be an option to everyone, but for sure it does provide a nice solution for my problem… So be mindful of that… this is a personal preference based on the fact that I don’t require intensive GPU usage, neither I run intensive GPU requiring applications within GNOME3/gnome-shell (I have a normal openSUSE 11.4 with GNOME 2.32.x with fglrx dual boot config for those apps).

The first thing we might want to do is to switch to profile based frequency switching… how do we this? As root:

[code] echo profile > /sys/class/drm/card0/device/power_method[/code]

Now we have to pick one of those 5 profiles… and since I’ve already stated… I want the ‘low’ profile since I don’t really do much intensive GPU work…

[code] echo low > /sys/class/drm/card0/device/power_profile[/code]

Now… you might want to check out the different profiles and the different clocks used… this can be done through:

[code] cat /sys/kernel/debug/dri/0/radeon_pm_info[/code]

and will report something like this:

[code]linux-331w:~ # cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 680000 kHz
current engine clock: 299530 kHz
default memory clock: 800000 kHz
current memory clock: 249750 kHz
voltage: 900 mV
PCIE lanes: 16[/code]

This one is using the ‘low’ profile… Feel free to test stuff around and find which one better answers your needs… Also there’s far more that can be done… I hope this helps ATI users with DRM driver to bring out the best of your system and improves your GNOME3 / gnome-shell experience, at so that you can run it with good thermal performance without fglrx.

NM

ATI/AMD fglrx 8.831 Catalyst 11.3 available for openSUSE 11.2, 11.3, 11.4

April 3rd, 2011 by

New version of catalyst 11.3 / fglrx 8.831 available

Please refer to my previous article where all the installation procedure is explained.

I’ve clean up all previous version which are not xpic, so everybody can easily know which drivers he has to install.

All credits to Sebastian Siebert (freespacer) : 11.3 article

What about tumbleweed, factory?

Users have reported that version 8.831 of catalyst 11.3 compile correctly under Tumbleweed with 2.6.38 kernel, so until xorg change too much, installing the 11.4 version should work

For factory, I’ve build a repository (see previous article) that can be used, and fglrx build

Numbers ?

Month Unique IP Number of visits Pages Hits Bandwidth
Jan 2011 2355 6411 19688 35263 16.63 GB
Feb 2011 2906 7719 26383 41142 22.37 GB
Mar 2011 8055 21157 228494 258613 59.13 GB

All served by openSUSE powered server!

GSOC Idea: Improve Clic Filesystem

March 24th, 2011 by

I really look for the perfect gsoc student: someone who has a brilliant idea, noone else thought of how to improve linux in general or openSUSE in specific and just needs my guidance.

But for those that need some ideas, my best bet is really to rewrite clicfs to make it even better. Right now clicfs is a FUSE filesystem hosting a loop image. So a page read goes from ext4->loop->fuse->clicfs->CD->clicfs->fuse->loop->ext4.
If it lived in the kernel, it could offer a block device you mount your ext4 on, leaving aside loop and fuse:


modprobe clicfs packfile=/read-only/openSUSE-kde.i586 cowfile=/read-write/.COWfile cowlog=/dev/ttyS0
mount /dev/clicfs/0 /mnt
chroot /mnt /bin/init

Great idea, no? For someone who wants to become famous, it would be the perfect target!

Securing SSH (Secure Shell) from attacker

March 22nd, 2011 by

Secure Shell or SSH is a network protocol that allows exchange of data through secure channels between two network devices.

Particularly widely used on Linux and Unix-based system to access your shell, SSHwas designed as a substitute for Telnet and other insecure remote shells, which sentinformation, especially passwords, in the form of simple text that makes it easy to be intercepted. Encryption used by SSH provides confidentiality and integrity of dataover an insecure network like the Internet.

For the Security Server We From Attacks The attacker who usually Always Use SSHAs a door Early Entry Into System To us, of course, become an admin obligation todispel various Efforts That.

There are several ways which ordinary people do to secure SSH from a variety ofattacks which one of them is by editing the file / etc / ssh / sshd_config.

before doing the configuration in the file / etc / ssh / sshd_config make sure SSH isinstalled on your linux distribution, and for openSUSE that I use it already automatically installed.

#vim /etc/ssh/sshd_config

change options, as below :

LoginGraceTime 2m
PermitRootLogin no
MaxAuthTries 3

LoginGraceTime which option is used to give a time limit of user logins, so please change these options according to your wishes.

PermitRootLogin is no option to allow the root user can login to ssh or not to give yes or no value on the options tersebut.sebaiknya give no value, so that users can not loginas root into your ssh.

MaxAuthTries 3 to give the limit on the number of errors allowed when the user logs in,this is very useful to avoid attackers do brute force on the server anda.dimana usersonly allowed to make a mistake typing the password in accordance with that alreadyset on the options.

If you want only certain users who may log into your ssh add AllowUsers option at the end of the line followed by a distinguished user name in the allowed login.

otherwise, you can install software, denyhost, for your ssh security

NB:do not enable the root user, for ssh login

Similarly, a fairly simple tutorial .. hopefully this can be useful.

Best Regards
Saydul Akram
Email : idulk@opensuse.org

ATI/AMD fglrx 8.821 Catalyst 11.2 available for openSUSE 11.2, 11.3, 11.4

February 19th, 2011 by

Updated : April 4th 2011

Preambule : free software

Warning

I would notice everybody which will install these software : you will install proprietary softwares on your computer. Nobody will be able to debug them, nor help you to resolve what can be happen. That must be said !

The free future

The real future is already in place : it’s called radeon (or free-radeon), it’s fully integrated in kernel & xorg. Actually ( for openSUSE 11.4, or openSUSE 11.3 with kernel-stable + X11 obs repo ). Support for many chipset is in real progress even for the 6xxx series.
Give it a try before using the proprietary software, report any bugs you find with it. Only your contributions can help and will make a real differences. Thanks for doing that !

Unofficial but working repository

I offer for those of you that for any reasons can’t use successfully the free-radeon drivers a repository where you will find the latest fglrx/catalyst drivers following the packaging policy made avalaible by AMD.
Thanks to Sebastian Siebert ( check his blog ) to work in coordination with ati/amd and follow the catalyst packaging. His work allow us to have that driver available for openSUSE.

The quick how-to

Adding the repository

For openSUSE Factory
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_Factory/ "ATI/AMD FGLRX"
For openSUSE 11.4
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.4/ "ATI/AMD FGLRX"
For openSUSE 11.3
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.3/ "ATI/AMD FGLRX"
For openSUSE 11.2
zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.2/ "ATI/AMD FGLRX"

Installing the driver

Nota previous version

Due to change in ati/amd way of life, it’s recommanded to completely remove any version of fglrx previously installed with a zypper rm

I can only recommand to also (as root)

# Remove old conf & stuff
rm -fr /etc/ati
# Remove any old fglrx inside kernel modules
find /lib/modules -type f -iname "fglrx.ko" -exec rm -fv {} \;
New installation

Once the repo has been added, you will certainly have to reboot to get ride off free radeon module. At boot on the grub line add
nomodeset blacklist=radeon 3
Don’t panic you will be land to a console, open it with root account to install fglrx.
Search the software you want for example under openSUSE 11.4

zypper se -s fglrx
Loading repository data...
Reading installed packages...

S | Name                  | Type    | Version | Arch   | Repository
--+-----------------------+---------+---------+--------+-----------
i | fglrx64_xpic_SUSE114  | package | 8.831-1 | x86_64 | ATI/AMD fglrx non-official  
  | fglrx64_xpic_SUSE114  | package | 8.821-1 | x86_64 | ATI/AMD fglrx non-official  
  | fglrx_xpic_SUSE114    | package | 8.831-1 | i586   | ATI/AMD fglrx non-official
  | fglrx_xpic_SUSE114    | package | 8.821-1 | i586   | ATI/AMD fglrx non-official

Starting with 8.821 (Catalyst 11.2) ATI use now xpic (full explanation)
So use that one. I’ve removed all non xpic drivers the 2 April 2011.

For a 64bits version
zypper in fglrx64_xpic_SUSE114
For a 32bits version
zypper in fglrx_xpic_SUSE114

During the installation process, all the dependencies will be added, which mostly are needed to build the kernel modules. Expect around 200MB to dowload.

Then the installer will build the module for your installed kernel.
And if there’s a kernel update, the script will automagically detect that, and will rebuild the module for the new kernel installed. (So if you find that your workstation is slow on reboot just press the esc key to see the details … )

Preparing xorg to use fglrx

Once the module is build and installed, you should have a file fglrx.conf or 50-fglrx.conf in /etc/modprobe.d

cat /etc/modprobe.d/50-fglrx.conf
blacklist radeon

Next ati recommend to use ati –initial-config but that break the auto-detect stack of xorg. So I recommend changing one line in file /etc/X11/xorg.conf.d/50-device.conf
just change driver line to driver “fglrx”
All the rest of the setup (double screen etc) will be made lately with the ati catalyst control center (command is amdcccle).
For those of you which want to have an xorg.conf file just have a look at aticonfig –help command.

Start X

If you are inside the console we start to use before just run “init 5” to start xorg, and normally you will find your normal xorg login screen (kdm, gdm, ldm, xdm).
Hit ctrl+alt+f1 to return to the console and type exit or logout or ctrl+d to close it.
then ctrl+alt+f7 to return to the xorg session.

Updates

ati/amd catalyst are release on a month basis, but this vary from 3 weeks to 8 weeks.

  • Catalyst 11.2 – fglx 8.821 : 14 February 2011

References

Sebastian Siebert blog ( German ) with nice howto and problem resolution.
My previous post on the subject

ATI Amd flgrx 8.812 catalyst 11.1 available also for 11.4/factory

February 13th, 2011 by

A quick note for the week-end, I’ve build and uploaded the new fglrx drivers.
The good news, they are also available for 11.4/factory,

Unofficial-but-working repository

For openSUSE 11.4 (factory) NEW !

zypper ar -c -f -n "ATI/AMD fglrx non-official" http://linux.ioda.net/mirror/ati/openSUSE_11.4/ "ATI/AMD FGLRX"

I would like to have feedback about how that works for you, please comment !

Factory specifics troubles

on a fresh auto-configuration factory install : libomp43

Problem: fglrx64_7_6_0_SUSE114-8.812-1.x86_64 requires gcc, but this requirement cannot be provided
  uninstallable providers: gcc-4.5-16.1.i586[openSUSE-11.4-11.4-1.35]
                   gcc-4.5-16.1.x86_64[openSUSE-11.4-11.4-1.35]
 Solution 1: deinstallation of libgomp43-4.3.4_20091019-5.23.x86_64
 Solution 2: do not install fglrx64_7_6_0_SUSE114-8.812-1.x86_64
 Solution 3: break fglrx64_7_6_0_SUSE114 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c] (c): 1
Resolving dependencies...
Resolving package dependencies...

The following NEW packages are going to be installed:
  binutils-gold fglrx64_7_6_0_SUSE114 gcc gcc45 glibc-devel 
  kernel-default-devel kernel-desktop-devel kernel-devel kernel-source 
  kernel-syms kernel-xen-devel libgomp45 linux-glibc-devel make patch 

The following package is going to be REMOVED:
  libgomp43 

15 new packages to install, 1 to remove.
Overall download size: 127.9 MiB. After the operation, additional 600.9 MiB 
will be used.

Normally this bug (in M5/M6) should has been resolved in RC1.

See full details on my previous dedicated post
//lizards.opensuse.org/?p=4673

Configuring an IPv6 DSL connection

January 19th, 2011 by

The German company rh-tec offers free IPv6 internet connections for people that already have T-DSL. Configuring such a connection on openSUSE 11.3 is not as straight forward as with IPv4. It’s not hard either if you know where to put the settings though.

  1. start the yast2 DSL module
  2. follow the instructions of the wizard to set up a new PPPoE device. Enter your user name and password at the provider screen.
  3. At the “Connection Parameters” screen uncheck “Automatically Retrieve DNS”. Enter an arbitrary IPv4 address as first DNS server (yast doesn’t accept IPv6 there yet, bug 665516).
  4. finish the wizard and leave yast
  5. open /etc/sysconfig/network/providers/provider0 (or whatever name was chosen by yast) in an editor
  6. change DNS1 and DNS2 to the actual IPv6 addresses of your provider’s name servers
  7. add the following line to the file:
    PPPD_OPTIONS="noip +ipv6 ipv6cp-accept-local"
  8. save and quit
  9. Done! You may now use cinternet or qinternet to dial in and enjoy the (rather empty) IPv6 internet.