From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
Date: Thu, 25 Jun 2009 10:42:09 -0700 [thread overview]
Message-ID: <5bdc1c8b0906251042m6d9b078ckdcf2b9f43f4a40ea@mail.gmail.com> (raw)
In-Reply-To: <4A4339B5.1060201@gmail.com>
On Thu, Jun 25, 2009 at 1:47 AM, bn<brullonulla@gmail.com> wrote:
> Mark Knecht ha scritto:
>
>> No, I need a new kernel also. The kernel on this machine is 2 years
>> old. Also, I have about a dozen packages masked so I've unmasked those
>> and will need to get the whole machine up to date.
>
> There is something I didn't understand at all in this thread. Why did
> you need to update the machine at all? Did you badly need some support
> for new video formats or performance improvement? Otherwise I really
> don't see the point of upgrading it. I see the point of upgrading a
> desktop or server system (yet my desktop kernel is 1.5 years old and I'm
> fine), but a MythTV box looks like an appliance that once working , you
> touch no more.
>
> m.
>
>
With the switch to digital TV I had to buy new hardware to record.
Even though this machine is only a frontend it started having trouble
that my other Gentoo desktop PCs were not. I updated everything I
could on this machine without updating the video driver, the kernel
and xorg-x11. Since I couldn't change the kernel or the video driver I
chose to update xorg-x11 and hit the wall.
I don't do these things for fun. It's OK with me if a machine never
gets updated but with MythTV they change data formats, database
formats, communication protocols and break things along the way WRT
remote frontends that haven't been updated, or that's my experience. I
figured that is what happened here.
Anyway, that's all done. The machine is updated and close to clean.
Still have to do a grub update but that can wait.
I'm having a few problems with things like eselect opengl set 1
complaining about libraries and things so I'll have to work on that
before I push forward.
Hope that explains a bit anyway.
Cheers,
Mark
next prev parent reply other threads:[~2009-06-25 17:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 23:20 [gentoo-user] xorg-server-1.5 update/old kernel+old fglrx Mark Knecht
2009-06-23 23:27 ` [gentoo-user] " Nikos Chantziaras
2009-06-23 23:40 ` Mark Knecht
2009-06-23 23:53 ` Mark Knecht
2009-06-24 0:06 ` Mark Knecht
2009-06-24 0:16 ` Nikos Chantziaras
2009-06-24 0:27 ` Mark Knecht
2009-06-24 0:33 ` Nikos Chantziaras
2009-06-24 0:42 ` Mark Knecht
2009-06-24 1:32 ` Neil Bothwick
2009-06-24 3:13 ` Mark Knecht
2009-06-24 5:55 ` Dale
2009-06-24 0:29 ` Nikos Chantziaras
2009-06-24 0:37 ` Mark Knecht
2009-06-24 1:46 ` Dale
2009-06-24 1:14 ` Keith Dart
2009-06-24 1:28 ` Neil Bothwick
2009-06-24 1:42 ` Mark Knecht
2009-06-24 7:46 ` Neil Bothwick
2009-06-24 20:17 ` Mark Knecht
2009-06-24 20:29 ` Neil Bothwick
2009-06-24 20:32 ` Alan McKinnon
2009-06-25 0:08 ` Adam Carter
2009-06-25 0:46 ` Mark Knecht
2009-06-25 0:59 ` Nikos Chantziaras
2009-06-25 1:25 ` Mark Knecht
2009-06-25 1:04 ` Adam Carter
2009-06-25 1:07 ` Nikos Chantziaras
2009-06-25 1:15 ` Adam Carter
2009-06-25 1:27 ` Mark Knecht
2009-06-25 1:51 ` Nikos Chantziaras
2009-06-25 2:33 ` Mark Knecht
2009-06-25 8:47 ` bn
2009-06-25 17:42 ` Mark Knecht [this message]
2009-06-24 9:21 ` Peter Humphrey
2009-06-24 14:25 ` Paul Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bdc1c8b0906251042m6d9b078ckdcf2b9f43f4a40ea@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox