1 |
On Thu, Aug 27, 2009 at 6:16 AM, BRM<bm_witness@×××××.com> wrote: |
2 |
<SNIP> |
3 |
> |
4 |
> I have to agree with Duncan on this one. (not that that's a bad thing - I've really enjoyed his insights on this thread.) |
5 |
|
6 |
As do I. |
7 |
|
8 |
> |
9 |
> Not everyone upgrades their video card every 6 months. |
10 |
> Most probably get a video card upgrade only when they buy a new computer; |
11 |
> and most don't buy a new computer every other year either, probably more like 4 years or so. |
12 |
> |
13 |
> I typically buy a new computer about every 8 years; and most people I know are probably between 4 and 8 years. |
14 |
> |
15 |
> So yes, KDE4 must be able to handle older hardware as Duncan describes. |
16 |
> |
17 |
> Glad you have the cash to burn on more frequent updates, but you're in the minority of computer users in general. |
18 |
> |
19 |
> One of the things I love about gentoo is using my older hardware - my server running gentoo (and hosting portage for my internal network) is a PII 233 from 1997. |
20 |
> My gentoo laptop is a Pentium M from 2003; and my desktop is an AMD64 from 2005; both run KDE3 and will be running KDE4 in time - just waiting for Gentoo to mark stable on respective architectures as I don't want to play with testing on these systems at that kind of level. |
21 |
> |
22 |
> And I'm sure there are plenty of users in the same boat as me. I may be a computer enthusiast, but I don't have cash to burn on "frequenty" hardware upgrades. I make the hardware I have last as long as I can - I just retired a P90 Slackware-base server last spring, but then only b/c the hard drive (from 1997) died due to the system being placed badly the truck during a move. |
23 |
> |
24 |
> Ben |
25 |
|
26 |
We need better tools for creating and maintaining personal overlays. |
27 |
Here is my story. |
28 |
|
29 |
Support for old hardware has been one of the downfalls of the devs |
30 |
deciding to not keep everything in portage but rather they start |
31 |
weeding out software before we users have really finished using it. I |
32 |
have 4 Asus Pundit-R machines which use an ATI chipset with |
33 |
intergrated graphics. They are low profile machines and you cannot |
34 |
just buy a new graphics controller for them. I use these machines as |
35 |
MythTV frontends. (2 at my house, 2 at my parents) The machine has |
36 |
S-Video outputs which drive most of our TVs and leave other inputs |
37 |
free. At the time I bought the machines the Open Source radeon driver |
38 |
didn't support S-Video so I had to use the ATI driver which worked |
39 |
fine. |
40 |
|
41 |
A couple of years ago ATI, in all wisdom, dropped TV Out support for |
42 |
this specific chipset from their closed source driver so I was forced |
43 |
to stick with the driver that was current at that time. This was OK |
44 |
for awhile as it was in portage and I could just mask higher |
45 |
revisions. However after awhile it turned out kernel updates forced |
46 |
incompatibilities between new kernels and this old driver so I was |
47 |
forced to mask newer revisions than the last one that worked with the |
48 |
last radeon driver that worked. |
49 |
|
50 |
3 months go by and portage maintainers decide to start weeding 'old' |
51 |
software out and, you guessed it, they weeded out what I needed to run |
52 |
this hardware. The ATI driver was gone. The kernel was gone. No |
53 |
discussions, no announcements. It was just gone. A machine I could |
54 |
build and run using a Gentoo 2006 install CD could no longer be built |
55 |
and run using a 2008 CD. |
56 |
|
57 |
Then I'm forced to learn about attics, building overlays, etc. It was |
58 |
a mess for a long time. |
59 |
|
60 |
Recently the Open Source driver has started to support TVOut on this |
61 |
version of the Radeon hardware, so I'm now back to using Open Source, |
62 |
but video quality is FAR inferior to the ATI driver, although CPU |
63 |
usage is far superior so at least with OS I have a quiet machine while |
64 |
watching a bad picture. |
65 |
|
66 |
Moral of the story - don't trust portage to support your machine |
67 |
tomorrow just because it works today, and don't expect portage |
68 |
maintainers to care. The response you'll get, if you get one at all, |
69 |
is 'be a man, create your own overlay, be responsible for your |
70 |
machine, and shut up'. |
71 |
|
72 |
From experience, |
73 |
Mark |