Nachdem es ja schon klar ist, dass Finnisch Weltsprache wird, jetzt der nächste Schritt: Salmiakki, das Weltgetränk! Zumindest in der MySQL-Welt. Und die ist groß! 
(danke an Kristian für die Anleitung)
This:
--- google.com ping statistics --- 49 packets transmitted, 30 received, 38% packet loss, time 54259ms rtt min/avg/max/mdev = 1288.705/2175.903/3347.027/364.736 ms, pipe 4
really makes me want back my internet at home.
But a good reason to finally install and configure presto. For the sake of all the poor Linux users, who do not have a fast internet connection I really hope, that it will make it into Fedora 9.
Ich bin jetzt hochoffiziell Übersetzer in Fedoras German Translation Team. Was mache ich da? Übersetzen natürlich. Damit wird versucht, Linux, hier Fedora im Speziellen, für möglichst viele Sprecher nicht-Englischer Sprachen zugänglich zu machen. Weil Deutsch mit über 100 Millionen Sprechern eine große Zielgruppe ist, sind hier Helfer immer gerne gesehen.
Aber natürlich gibt es auch andere Möglichkeiten, bei Fedora mitzuhelfen. Diese Seite zeigt diese Möglichkeiten auf.
Schaut euch also meine Seite über mich an und meldet Fehler oder schlechte Übersetzungen! Dann können wir die verbessern!
As some of you may have read or somehow learnt, I do own a new laptop now. Well, actually it’s only used-new, but as good as new and still with warranty. Anyway, first thing I did: Put in the Fedora 8 Live-CD, booted, enjoyed. Almost everything worked out of the box. Exceptions were the graphics (ATI Mobility Radeon x1300) and the webcam, at least everything else I checked worked, including wireless (most important!) and the CPU-throttling, which cools the laptop quite down a lot. So, next logical step: Install Fedora. After doing so, I activated the additional repositories, livna, freshrpms and atrpms. Following the guidelines from this tutorial, I got almost my previous installation. Only one really bothering thing was still there: Graphics not working!
The laptop does have the already mentioned ATI Mobility x1300 graphics chipset and there is the proprietary fglrx driver for it. BUT: the version available until some time ago (7.12) did not support the native resolution of the screen, which is 1680×1050. I want that resolution, badly, that’s what I spent the money for! So, what are the alternatives? I don’t use the 3D-effects of the desktop, so any driver would be fine. That’s how I found out about the radeonhd driver. It’s a free, though yet incomplete driver for ATI graphic cards. At least, with it I got my 1680×1050 resolution. Too bad though, that it doesn’t allow me to use my webcam, at least it’s not working within skype and cheese but it worked when I used the fglrx driver for testing. Lately, a new version of that driver was released and it promises to fix my resolution problem. I will give it a try, as soon as it is in the livna-repo. And yes, I am too lazy to circumvent my package manager!
What would be the overall conclusion, regarding the Acer Travelmate 8204 and Fedora? Well, it is a pleasure. I barely, if ever reboot, as Suspend and Hibernate are working as well and I can say for sure, that this is the most productive and fastest laptop I’ve ever worked with. Well done, Acer! Not so well done, ATI!
Yesterday I somehow managed to screw up my home partition. It was a cryptsetup-luks encrypted partition and it seems like I wrote over the beginning of the partition when updating grub, which I had to do due to some re-partitioning… Today was consequently mostly spent on fixing that mess. At home I usually keep a copy of the most current Fedora Rescue CD. Or several copies. Well – I am not at home. And the Ubuntu 7.10 Live CD does not support LVM… Quite a hazzle with a not-so-happy ending.
Anyway, my “new” /home is now bigger (who would not like that) and my last backup is luckily less than two weeks old. Rdiff-backup is doing its thing and restoring (almost) all data.
Lessons learned:
Next time, I just won’t resize but delete stuff instead…
* somehow one directory within my ~/.evolution can not be restored. rdiff-backup hangs at 100% cpu and seems to do nothing on that 4 MB directory with ~20 files in it. I didn’t find anything on that, but if anyone knows something…
Yesterday Evening I had an idea.
Inspired by the changing background in Fedora 8 (which rocks, by the way!!!), I had the idea about some “mood-applet” for GNOME (or any desktop, for that matter). What’s the idea?
Well, think of it as a global setting applet, where you can somehow “change” your mood, kind of like you do with the volume of your speakers. Depending on the mood, the desktop could change its appearance, the music selection could be influenced, your instant messenger will change your status, maybe something else?
It’s just an idea and I am not a programmer, who could implement it, but if there are some, feel free
If you use rdiff-backup or some program, which sits on top of it (e.g. backupninja) and you get errors similar to this:
Traceback (most recent call last):
File “/usr/bin/rdiff-backup”, line 23, in ?
rdiff_backup.Main.error_check_Main(sys.argv[1:])
File “/var/lib/python-support/python2.4/rdiff_backup/Main.py”, line 298, in error_check_Main
try: Main(arglist)
File “/var/lib/python-support/python2.4/rdiff_backup/Main.py”, line 318, in Main
take_action(rps)
File “/var/lib/python-support/python2.4/rdiff_backup/Main.py”, line 276, in take_action
elif action == “check-destination-dir”: CheckDest(rps[0])
File “/var/lib/python-support/python2.4/rdiff_backup/Main.py”, line 780, in CheckDest
need_check = checkdest_need_check(dest_rp)
File “/var/lib/python-support/python2.4/rdiff_backup/Main.py”, line 817, in checkdest_need_check
assert len(curmir_incs) == 2, “Found too many current_mirror incs!”
AssertionError: Found too many current_mirror incs
Then you might try to go to your rdiff-backup-data directory of your backup and delete all but the latest current-mirror-*.data files. At least my backups (simple rdiff-backup) are working again.
Maybe this also concerns others, despite me.
I have Fedora running on my Acer Laptop, which is a Travelmate 661 LCi (now running flawlessly for almost four years!). Since I upgraded to Fedora 7 with its Kernel 2.6.21 I had problems with the fan of the laptop: When it started spinning, the laptop froze. Under X, it froze the whole computer, the num lock led was blinking. When using the console solely, the computer just froze and sometimes threw some acpi error messages on the console.
Well, after a while I found out, that it is a regression in the Linux kernel, bug #8385 in kernel’s bugzilla, to be more precise.
So, what to do about that? I want to use Fedora 7 and its kernels. Just patch them with the patch supplied in Comment #50 of the above mentioned bugzilla report. And for those new to building kernels, here is a short howto on how to do so (hence the name “howto”…)
I hope, this mini-howto helps anyone out there to get Fedora 7 turned back into a usable system again.
Update: edited to include the recent development / updates / better patches
Ich habe es endlich (zugegeben, vorher nie intensiv probiert…) geschafft, suspend to disk auf meinem Acer Travelmate 661 LCi unter Fedora Core 6 zum Laufen zu kriegen. Im Nachhinein war es gaaaanz einfach…
[atrpms]
name=Fedora Core $releasever – $basearch – ATrpms
baseurl=http://dl.atrpms.net/fc$releasever-$basearch/atrpms/stable
zur yum.conf bzw. als Datei in /etc/yum.repos.d hinzu
Die Kernelversion kann sich natürlich ändern, außerdem sollten alle zugehörigen Module installiert werden
SuspendDevice swap:/dev/EuerSwapDevice
kernel /vmlinuz-2.6.18-1.2849_1.fc6.cubbi_suspend2 ro root=/dev/VolGroup00/RootVol000 resume2=/dev/EuerSwapDevice quiet
OnResume 20 /usr/sbin/855resolution 4d 1400 1050
Diese “Anleitung” ist kein HowTo und kein Handbuch, nur eine kurze schriftliche Niederlegung meiner Schritte, damit andere und auch ich etwas zum Nachlesen haben.
Mein Dank geht vor allem an diese Seite, mit deren Hilfe ich das 1400×1050-Auflösungs-Problem behoben habe.
Ich habe mich heute mit der Frage beschäftigt, warum mein FC6, welches ich von FC5 aktualisiert habe, nicht richtig mit WLANs zusammenarbeiten wollte. Es war nicht mehr möglich, mit dem NetworkManager einfach ein WLAN auszuwählen und sich dann zu verbinden. In der /var/log/messages gab es immer Fehler mit wpa_supplicant. Die Erleuchtung kam mir dann eher per Zufall: Es war noch ein wpa_supplicant-Paket von den ATRPMs installiert:
Removing:
wpa_supplicant i386 1:0.4.9-13.fc5.at installed
Dadurch kam es also zu den Unstimmigkeiten. Bei einem einfachen yum update wurde das Paket übrigens nicht aktualisiert. Also schnell ein yum remove wpa_supplicant und dann ein yum install NetworkManager, das hat’s dann geholfen und jetzt habe ich
wpa_supplicant i386 1:0.4.9-1.fc6
installiert. Alles läuft. Juhu.