Showing only posts in category “linux”.
Until a few days ago, I had a TV cable-based network connection. I had a fixed IP so it was easy to configure firewall in various machines that I can access to allow access only from my home IP. And I was happy.
My ISP has recently moved me to a more robust, Ethernet connection, which is done via PPPoE. All great, but the IP is changing every time I connect. That wouldn't be a problem if I never had any downtimes, but in practice this is not possible. Every once in a while, my router will reconnect and will get me a brand new IP and machines where I configured a firewall won't let me in.
( read more... )
Heard the news?
ATI AMD finally releases a new driver for Linux which brings the long awaited AIGLX support. AIGLX is cool stuff. Great work, although it's kind of late—since most other producers had it long ago.
Unfortunately, the suspend/resume problems seem to be still in place so I think I'll just stick to VESA for now... But hey, there is hope—since they brought us AIGLX by the end of 2007, I think we'll have suspend/resume working some time next year. Grrr.
Couldn't resist so I spent half a day trying this driver. For one thing, it didn't work because my hardware is unsupported. Applied the patch, messed with the ChipID option, finally got it to work. It was damn slow for 2D, so slow actually that I'd be happy to revert to VESA any time.
But let's keep trying. After these new hacks in xorg.conf it was about as fast as VESA. What can I say—cool, they finally match the performance of a general, unoptimized driver. I expected better, but I can live with it.
Let's try AIGLX now. apt-get install compiz 'n shit, finally killing sawfish (still my preferred window manager) and trying to start compiz results in an error (err... forgot what was it. I'd love to paste, but I can't since I upgraded to VESA since). OK, they claim to support AIGLX, but compiz doesn't really work—no problem, maybe it will later. LATER. I mean, in a few years or so. No problem.
Let's try suspend. Oh, it WORKS. How cool is that? My machine suspended. Now let's RESUME IT! And... you don't wanna hear the rest of the story...
So I switched back to VESA. I'm happy. I can suspend/resume. Compiz doesn't work (but Sawfish is so cool and so.... Emacs-like.). I bet that moments after I'll have bought a new laptop, which definitely won't have any AMD label on it, their crap driver will work just fine. I bet. But I won't be giving them any more cents...
I can't believe it, I must be dreaming! ATI finally did the Right Thing. I don't yet know if this is a result of the fact that they can't write and maintain a proper driver for Linux, or to beat competition, but one thing's for sure: I might eventually get to use this hardware to its full potential (though, chances are, I will purchase a new one before this card gets proper open-source support). I'm also sure that this will increase ATI sales (though they'll probably be blind enough to not realize it.).
So I have upgraded my kernel. Day three. I finally realized why suspend doesn't work anymore. Because along with this kernel update, I also updated the infamous ATI drivers. My never ending nightmare.
I don't want to say that suspend/resume was always dependable. It worked, sometimes. Most of the times, it didn't. Basically, it was random. Sometimes it worked, sometimes it didn't. When it didn't, I risked losing all my work. I was conscious about it, but I still risked, saying—“hey, Linux is in heavy development; I'm using a bleeding-edge kernel; folks don't have support from hardware producers” etc.
It is only today when I realized, after another 3 painful days trying to set things up for the millionth time, that it's not the kernel and it's not Debian. It's ATI. Yes, if you upgrade to kernel 126.96.36.199 and to latest ATI drivers (8.39.4 as I write this) then suspend doesn't work. It hangs with this message: “Suspending console(s)”.
I rebooted a million times. I tried a million variants, only to come up to the logical conclusion (and I wonder how was I stupid enough not to think about it from the first place): “fglrx” can't suspend. It worked, sometimes, with a certain combination of fglrx and kernel versions, but it was buggy. And I blamed it on the wrong side.
By pure chance, I switched my X to a “vesa” driver today to find out that suspend/resume works flawlessly, over and over. Never crashes. With “fglrx”, it crashed twice a day (in those days when it worked at all). But VESA is sooo slow. I guess I should be thankful to ATI that they gave me this buggy driver that wasted tens of hours of my life (but it's oh so fast).
I'm almost 30. It's mid 2007. And I can't suspend my laptop. Thanks to ATI. They can't write a good driver, yet they won't release any documentation. Basically, they don't grant us the right to use their expensive crap hardware—which we paid for. Doesn't this suck?!
I bought a Wacom Graphire 4 tablet today, for my daughter. There were 2 versions in the store. One came with Adobe Photoshop and cost around 100$ more. I obviously chosen the cheapest one.
I was convinced that it'll take me 2 days to make it work in Linux, but — surprise — it only took 20 minutes. And now I know why. They support the open-source development of Linux drivers. They provide sample tablets and documentation to open-source driver developers. And for this reason, it almost works out of the box.
I wish ATI would do the same. But they don't, which is why running Linux with an ATI card is nightmare.
Kudos to Wacom. I plan to buy 2 more graphic tablets, and they sure will be Wacom. I'm happy. Thanks guys!
The other day a friend of mine having zero experience in Linux asked me if I could make his printer and modem work in Linux. At least for the modem, I thought, what the hell—I did this before. So I went there to try.
He was running Fedora 6. For some reason, it seemed to me quite old and after hacking it for a half an hour, I thought I should first try with a newer distro. FC6 didn't detect any modem, and while it did detect a printer, it said there's no available driver for it.
Because I'm a Debian user for about 4 years, I chose to go with Ubuntu. Ubuntu is a bleeding edge Debian distro. Pretty good for Linux newbies.
I went home to download and burn the latest Ubuntu distro. Back at my friend, I throw the CD in and restart. It takes 15 minutes to boot Ubuntu. That's because he has an old machine (AMD Athlon at 1GHz, which is OK, but with only 256MB RAM). He also doesn't have a swap partition—because the one that installed FC6 was “an expert”.
Next, I try to start the installer. I click on the "Install" icon on the desktop, then I literally wait for 10 minutes until a window appears. The CD led was blinking during this time.
Almost one month ago I upgraded my Debian to 4.0 (Etch). I did that for no specific reason—I'm just trying to keep my box up-to-date as it's generally a good thing. In this release they switched to a new X version, which for some reason is named 1.3.0. The old version was 7.2 or something.
The version change is planned for a long time and AFAIK it has been in the X.Org development tree for 6 months or so. But, the proprietary ATI driver, one of my primary sources of frustration ever since I bought this laptop, will only work on X.Org 6.7, 6.8, 6.9, 7.0 and 7.1, even though it was last released two weeks ago.
I tried all sorts of hacks but I couldn't convince it to run on X 1.3.0. If you ask me, there are 2 problems here:
The X team shouldn't have changed the version number in such a dumb way. They should have named it 7.3.0. That would make sense. 1.3.0 doesn't. But anyway, it's a lost battle—they did it and so it shall stay.
ATI should either allow me to force loading it regardless the X version, or just update the fucking driver to support something that has been planned for half a year.
Some people got it to work by either downgrading X (not really an option for me as I upgraded the whole distro and the changelist was huge), and others by rebuilding X after changing the version in the code—which means that there's no practical reason why the driver wouldn't work on the new version and also means that it would only take 30 seconds for an ATI engineer to "upgrade" it.
So here am I with this super-powerful multi-hundred-dollars card, stuck with a slow VESA driver and no acceleration whatsoever. Almost one month has passed and probably I'll have to wait for another 2-3 months until ATI thinks they should update the driver.
Meanwhile, my friends with cheap Intel cards have absolutely no problem and they even have AIGLX + Compiz/Beryl eye-candy desktops, something ATI still doesn't support in 2007 and, judging by how things go, probably never will. It's definitely a great advantage to have open-source drivers! I can understand now why kernel hackers refuse hooks to run proprietary code.
I keep saying that I won't buy another ATI product ever again, but unfortunately when you purchase a brand laptop you don't really have a choice. Except for Linux support, they produce great cards. But why do they make Linux people life so miserable? Dear ATI, can't you hear we hate you? I hate you! F**k you and your cards. And, did I mention I hate you?
sed -i 's/\xe8\xec\x4f\xfe\xff\x85\xc0\x7f\x31/\xe8\xec\x4f\xfe\xff\x85\xc0\x90\x90/' x710/usr/X11R6/lib/modules/drivers/fglrx_drv.so sed -i 's/\xe8\xaa\x72\xfe\xff\x85\xc0\x7f\x23/\xe8\xaa\x72\xfe\xff\x85\xc0\x90\x90/' x710_64a/usr/X11R6/lib64/modules/drivers/fglrx_drv.so sed -i 's/\x0f\x88\x3c\x09\x00\x00/\x90\xe9\x3c\x09\x00\x00/' x710/usr/X11R6/lib/modules/drivers/fglrx_drv.so sed -i 's/\x0f\x88\x3b\x08\x00\x00/\x90\xe9\x3b\x08\x00\x00/' x710_64a/usr/X11R6/lib64/modules/drivers/fglrx_drv.so
Never in my life have I done something as horrible. But it worked. Kudos to whoever created the patch. And shame on you ATI!
Wow. Isn't it cool that I'm still talking about this in 2007? When Windows/Mac folks have it working for years without bothering?
I think this is the most frequent problem happening in Linux, and for some reason you have to solve it over and over, usually involving different steps. It never works until it suddenly starts working and sometimes you don't even remember what you did. :-) Only SynCE is more complicated (I actually made that work, once, then upgraded the kernel and even though I patched and reinstalled all SynCE stuff, it's not working anymore. God only knows why. But that's a future story).
Analysis — It's no secret that Linus Torvalds, Linux's founder, dislikes the GNOME desktop. In 2005, for example, Torvalds posted on the GNOME-usability list that "I personally just encourage people to switch to KDE.".
This “users are idiots, and are confused by functionality” mentality of Gnome is a disease. If you think your users are idiots, only idiots will use it. I don't use Gnome, because in striving to be simple, it has long since reached the point where it simply doesn't do what I need it to do.
Oh, so true! I am a Gnome user since ancient times, but I have to agree Linus on the matter. I've watched Gnome how it went from a powerful and configurable desktop into a toy that's only good to help you see what time is it.
Linus is complaining that Gnome developers reject patches and features (and many times even drop existing features) on the lame excuse that they are too confusing for end users. Let me add my own small story to this.