Denniston, Todd A CIV NAVSURFWARCENDIV Crane wrote:
>> -Original Message-
>> From: m.r...@5-cent.us [mailto:m.r...@5-cent.us]
>> Sent: Thursday, November 05, 2015 10:23 AM
>> To: CentOS mailing list
>> Subject: Re: [CentOS] Centos 7, ATI card, 30" moni
> -Original Message-
> From: m.r...@5-cent.us [mailto:m.r...@5-cent.us]
> Sent: Thursday, November 05, 2015 10:23 AM
> To: CentOS mailing list
> Subject: Re: [CentOS] Centos 7, ATI card, 30" monitor
> That's why I said that at some point I was going to hand-
On 11/05/2015 10:23 AM, m.r...@5-cent.us wrote:
Did. I am *not* going to paste in almost 3,000 lines (what a *useful*
logfile... NOT!), but the relevant lines, I believe, are
[18.760] (EE) open /dev/fb0: No such file or directory
[18.760] (WW) Falling back to old probe method for fbdev
F
Lamar Owen wrote:
> On 11/04/2015 04:48 PM, m.r...@5-cent.us wrote:
>> Yep. They got nothing for CentOS 7. Btw, we got him the full width by
>> changing the cable, from DVI-I to DVI-D (dual link). Then he had to
>> change it back to not recognizing the full width of the screen via the
>> control ct
On 11/04/2015 04:48 PM, m.r...@5-cent.us wrote:
Yep. They got nothing for CentOS 7. Btw, we got him the full width by
changing the cable, from DVI-I to DVI-D (dual link). Then he had to
change it back to not recognizing the full width of the screen via the
control ctr, because when it did, ever
Denniston, Todd A CIV NAVSURFWARCENDIV Crane wrote:
>> From: m.r...@5-cent.us [mailto:m.r...@5-cent.us]
>>
>> John R Pierce wrote:
>> > On 11/3/2015 8:11 AM, John R Pierce wrote:
>> >> On 11/3/2015 7:33 AM, m.r...@5-cent.us wrote:
>> >>> Well, I got my user back to being able to use his system, but
> -Original Message-
> From: m.r...@5-cent.us [mailto:m.r...@5-cent.us]
> Sent: Tuesday, November 03, 2015 11:58 AM
> To: CentOS mailing list
> Subject: Re: [CentOS] Centos 7, ATI card, 30" monitor
>
> John R Pierce wrote:
> > On 11/3/2015 8:11 AM, John R P
John R Pierce wrote:
> On 11/3/2015 8:11 AM, John R Pierce wrote:
>> On 11/3/2015 7:33 AM, m.r...@5-cent.us wrote:
>>> Well, I got my user back to being able to use his system, but I've
>>> still got one issue: it's running on the VESA driver - there is
>>> *no* Catalyst build for this monitor, for
On 11/3/2015 8:11 AM, John R Pierce wrote:
On 11/3/2015 7:33 AM, m.r...@5-cent.us wrote:
Well, I got my user back to being able to use his system, but I've still
got one issue: it's running on the VESA driver - there is*no* Catalyst
build for this monitor, for CentOS 7. From a lot of googling, n
On 11/3/2015 7:33 AM, m.r...@5-cent.us wrote:
Well, I got my user back to being able to use his system, but I've still
got one issue: it's running on the VESA driver - there is*no* Catalyst
build for this monitor, for CentOS 7. From a lot of googling, nothing's
been done since the summer of '14
Well, I got my user back to being able to use his system, but I've still
got one issue: it's running on the VESA driver - there is *no* Catalyst
build for this monitor, for CentOS 7. From a lot of googling, nothing's
been done since the summer of '14 (lspci reports it as a FirePro V3900).
Any thou
11 matches
Mail list logo