1:44 p.m.
I've been running several F8 and F9 machines behind a KVM switch
against what seemed the current high-end monitor in local stores. (My old
LCD, which was 1280x1024, died suddenly.)
The first weirdness, of several, is that my three PCs all handled
it well enough to be usable under F8, albeit not optimally -- they try
variously to treat the display or the hardware, or both, as anything from
1280x1024 to 1680x1050 (which is what it is), and often fail when they're
over 1280x1024.
This is the case even though I do my upgrades, and especially
installs, with the subject machine out from behind the KVM switch,
connected directly (and alone, of course) to the peripherals, so that it
can do any necessary negotiating with them, unimpeded by the KVM switch.
(In the past, that has sufficed. Once they're configured, they
can be put behind the switch again.)
One machine actually shows *almost* the model number (w2207,
without the h) -- but that's not in the list of all monitors that Fedora
knows about.
Is there some secret driver somewhere that I should be getting?
One reason I bought this on is that HP is supposed to be linux-
friendly ...
--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Remember I know precious little of what I am talking about.
11:53 a.m.
On Sun, 22 Jun 2008 20:54:23 -0400, Raymond C. Rodgers wrote:
[...]
My HP w2207h worked fine with both F8 and F9 on an ATI Radeon
HD3850,
and in fact the clean install of F9 I did didn't even bother to ask me
what resolution I wanted to run the monitor in, it just set it
automatically to 1680x1050.
Well, it's good to know it can be done -- already. I had a
problem with an LCD monitor on my first install of FC1, so bad that I
eventually went back to RH9 until the developers got to that monitor.
Sorry I'm of no help, but I do have a
question for you on this monitor & Fedora: Have you found a way to get
the monitor to actually display any of the text mode terminals (say
alt-control-1) without going to sleep because the signal is out of
range? I've had the monitor for about two months now, and I'm frustrated
that text mode access is out of visible reach, and the scaling settings
don't seem to solve the problem.
Unfortunately, I know nothing whatever of those terminals. I just
keep a gnome-terminal on workspace #1, with half a dozen tabs open, and
do everything CLI from there -- unless I want to use the machine I'm on
to work on another. But even then, all I do is put another gnome-
terminal, with different background colors, on a different workspace.
I *have* seen this monitor give me an impaired view just long
enough to let me log in, and then put itself relentlessly to sleep; and I
have not found any way to overcome that. I'd also be glad to know if
there is one -- maybe ssh into the machine from a better-adjusted one,
become root, and edit xorg.conf; but I've tried that a couple times
without success ....
Btw, with that spelling, are you related to our family friend Kay
Rodgers, formerly of LC?
--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Fedora 8 & 9; Alpine 1.10, Pan 0.132; Privoxy 3.0.6;
Dillo 0.8.6, Galeon 2.0.4, Epiphany 2.20, Opera 9, Firefox 2 & 3
Remember I know precious little of what I am talking about.
4:17 p.m.
--- On Wed, 7/2/08, Beartooth <Beartooth(a)swva.net> wrote:
From: Beartooth <Beartooth(a)swva.net>
Subject: Re: Wide, flat, & weird : HP w2207h with F8 & F9
To: fedora-list(a)redhat.com
Date: Wednesday, July 2, 2008, 12:25 PM
On Tue, 01 Jul 2008 23:33:55 +0200, Björn Persson wrote:
[...]
> The DMI data doesn't come from the various pieces
of hardware
> themselves. It's all stored in a memory on the
motherboard, so it
> doesn't necessarily have anything to do with what
hardware is actually
> installed. It seems only big corporations have tools
to write to the DMI
> memory.
>
>> Is there something else I should be looking for??
What I know of
>> hardware would go in a gnat's eye -- and never
discommode the gnat.
>
> Try running lspci and looking for words like
"display", "graphics" and
> "VGA".
On the #1 machine :
===== ===== =====
[root@localhost btth]# lspci|grep VGA
01:00.0 VGA compatible controller: VIA Technologies, Inc.
K8M890
[Chrome9] Integrated Video (rev 01)
[root@localhost btth]#
It appears to be the same as mine:
[root@localhost ~]# lspci|grep VGA
01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890 [Chrome9] Integrated
Video (rev 11)
[root@localhost ~]#
Start you machine in level 3, you shall see the difference. Read my other post, it will
tell you my experience.
Regards,
Antonio
===== ===== =====
But there is later, better info -- which I have just
posted here,
under the thread "Re: Fedora 9 Openchrome drv HP
w2207h Monitor"
--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Remember I know precious little of what I am talking about.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-list
12:05 p.m.
On Mon, 2008-06-30 at 16:45 +0000, Beartooth wrote:
(The machine was built for me, to my budget, by an electronic
friend; but I haven't found a way to ask it what video card it has,
and I hate to ask him to dig through his records (if any) to find
out.)
You can try "dmidecode" (it's a command line tool).
--
[tim@localhost ~]$ uname -r
2.6.25.6-55.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
2:25 p.m.
On Tue, 01 Jul 2008 23:33:55 +0200, Björn Persson wrote:
[...]
The DMI data doesn't come from the various pieces of hardware
themselves. It's all stored in a memory on the motherboard, so it
doesn't necessarily have anything to do with what hardware is actually
installed. It seems only big corporations have tools to write to the DMI
memory.
> Is there something else I should be looking for?? What I know of
> hardware would go in a gnat's eye -- and never discommode the gnat.
Try running lspci and looking for words like "display", "graphics"
and
"VGA".
On the #1 machine :
===== ===== =====
[root@localhost btth]# lspci|grep VGA
01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890
[Chrome9] Integrated Video (rev 01)
[root@localhost btth]#
===== ===== =====
But there is later, better info -- which I have just posted here,
under the thread "Re: Fedora 9 Openchrome drv HP w2207h Monitor"
--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Remember I know precious little of what I am talking about.
4:33 p.m.
måndagen den 30 juni 2008 skrev Beartooth:
On Tue, 01 Jul 2008 02:35:00 +0930, Tim wrote:
> On Mon, 2008-06-30 at 16:45 +0000, Beartooth wrote:
>> (The machine was built for me, to my budget, by an electronic friend;
>> but I haven't found a way to ask it what video card it has, and I hate
>> to ask him to dig through his records (if any) to find out.)
>
> You can try "dmidecode" (it's a command line tool).
Well, at least some of that is in English. I went through it,
line by line, a couple of times. But all I could see that might be
relevant was this :
===== ===== =====
Handle 0x0023, DMI type 10, 6 bytes.
On Board Device Information
Type: Video
Status: Enabled
Description: To Be Filled By O.E.M.
===== ===== =====
The DMI data doesn't come from the various pieces of hardware themselves. It's
all stored in a memory on the motherboard, so it doesn't necessarily have
anything to do with what hardware is actually installed. It seems only big
corporations have tools to write to the DMI memory.
Is there something else I should be looking for?? What I know of
hardware would go in a gnat's eye -- and never discommode the gnat.
Try running lspci and looking for words like "display", "graphics" and
"VGA".
Björn Persson
9:06 a.m.
On Tue, 01 Jul 2008 10:05:50 +0930, Tim wrote:
[....]
Faced with trying to read technobabble output, you could have posted
the
whole thing to the list for more help with it. At least you can with
command line tools.
Yes, ordinarily I would have; and I could have piped it into a
text editor to make a file I could copy in toto or attach -- or at least
I could have found out how to -- but this was such a vast file, and so
much of it surely irrelevant, that I couldn't see taking the bandwidth.
Meanwhile, fortunately, I've discovered the secret of lshw-gui :
you have to double-click (even though my machines are single-click),
*not* just on what looks likeliest among the bolded text, but all the way
into the upper left corner (In this case on "Desktop Computer") and open
branches column by column, as if you were drilling down a series of
directories in the CLI (as, I suppose, in fact you are, behind the front
end). There's no way to skim to the middle and go from there.
From there, I get to "Motherboard," and then to a listing of --
so help me -- BIOS, cpu, system memory, and *eleven* identical-looking
choices of "Host bridge." But ten of them don't seem to lead anywhere...
Any hints on what I'm looking for may look like, so I'll know it
when I slog to it? Most of what I see seems to've come from VIA
Technologies.
--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Fedora 8 & 9; Alpine 1.10, Pan 0.132; Privoxy 3.0.6;
nine (count 'em -- nine) different browsers
Remember I know precious little of what I am talking about.
7:35 p.m.
Tim:
> You can try "dmidecode" (it's a command line tool).
Beartooth:
Well, at least some of that is in English. I went through it,
line by line, a couple of times. But all I could see that might be
relevant was this :
===== ===== =====
Handle 0x0023, DMI type 10, 6 bytes.
On Board Device Information
Type: Video
Status: Enabled
Description: To Be Filled By O.E.M.
===== ===== =====
Ah yes, well that sort of thing will be a problem for most automatic
tools. They scan the hardware for identifying codes, and information
provided by the hardware. If the manufacturer didn't fill in the data,
or stuffed it with nonsense (my BIOS is full of 1234567890 serial
codes), then you won't get far with it.
That sort of nonsense doesn't help Windows users trying to install
hardware, either. They get some disc with half a dozen drivers for
their budget graphics/sound/network card, and they have to pick which
one to use, because the system can't do it for them.
Faced with trying to read technobabble output, you could have posted the
whole thing to the list for more help with it. At least you can with
command line tools.
--
(This computer runs FC7, my others run FC4, FC5 & FC6, all using Gnome
in case that's important to the thread.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
12:51 p.m.
On Tue, 01 Jul 2008 02:35:00 +0930, Tim wrote:
On Mon, 2008-06-30 at 16:45 +0000, Beartooth wrote:
> (The machine was built for me, to my budget, by an electronic friend;
> but I haven't found a way to ask it what video card it has, and I hate
> to ask him to dig through his records (if any) to find out.)
You can try "dmidecode" (it's a command line tool).
Well, at least some of that is in English. I went through it,
line by line, a couple of times. But all I could see that might be
relevant was this :
===== ===== =====
Handle 0x0023, DMI type 10, 6 bytes.
On Board Device Information
Type: Video
Status: Enabled
Description: To Be Filled By O.E.M.
===== ===== =====
Is there something else I should be looking for?? What I know of
hardware would go in a gnat's eye -- and never discommode the gnat.
--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Fedora 8 & 9; Alpine 1.10, Pan 0.132; Privoxy 3.0.6;
nine (count 'em -- nine) different browsers
Remember I know precious little of what I am talking about.
11:45 a.m.
On Mon, 23 Jun 2008 16:53:36 +0000, Beartooth wrote:
On Sun, 22 Jun 2008 20:54:23 -0400, Raymond C. Rodgers wrote:
[...]
> My HP w2207h worked fine with both F8 and F9 on an ATI Radeon HD3850,
> and in fact the clean install of F9 I did didn't even bother to ask me
> what resolution I wanted to run the monitor in, it just set it
> automatically to 1680x1050.
Somebody on another thread clued me into doing first downloading
an rpm to add livna to my repos, running rpm -ivh livna-release-8.rpm or
-9.rpm respectively, and then doing yum install kmod-nvidia. That helped
a lot. I now have two F9 PCs and an F8 PC giving acceptable if not
optimal displays.
The F8, unfortunately, is my #1 (newest, fastest) machine. I had
installed F8 over F9 already once, over the anaconda bug -- and,
apparently, somehow gotten an unclean install. I tried another fresh
install of F9, and failed again, the second time over this display issue.
I did the third fresh install of F8, did the livna bit, and re-re-
copied my data back in. Now I'm wondering if I dare try yet a third
upgrade to F9 -- before there's a re-spin to do it with.
Anybody know for sure if an upgrade F8 > F9 will keep all the
livna-nvidia settings?? Or even a way a subtechnoid can use to make #1
identify its video card for me?
(The machine was built for me, to my budget, by an electronic
friend; but I haven't found a way to ask it what video card it has, and I
hate to ask him to dig through his records (if any) to find out.)
--
Beartooth Subtechnoid, PhD, Neo-Redneck Power User
Fedora 8 & 9; Alpine 1.10, Pan 0.132; Privoxy 3.0.6;
nine (count 'em -- nine) different browsers
Remember I know precious little of what I am talking about.
7:54 p.m.
Beartooth wrote:
I've been running several F8 and F9 machines behind a KVM switch
against what seemed the current high-end monitor in local stores. (My old
LCD, which was 1280x1024, died suddenly.)
The first weirdness, of several, is that my three PCs all handled
it well enough to be usable under F8, albeit not optimally -- they try
variously to treat the display or the hardware, or both, as anything from
1280x1024 to 1680x1050 (which is what it is), and often fail when they're
over 1280x1024.
My HP w2207h worked fine with both F8 and F9 on an ATI Radeon HD3850,
and in fact the clean install of F9 I did didn't even bother to ask me
what resolution I wanted to run the monitor in, it just set it
automatically to 1680x1050. Sorry I'm of no help, but I do have a
question for you on this monitor & Fedora: Have you found a way to get
the monitor to actually display any of the text mode terminals (say
alt-control-1) without going to sleep because the signal is out of
range? I've had the monitor for about two months now, and I'm frustrated
that text mode access is out of visible reach, and the scaling settings
don't seem to solve the problem.
Raymond
6:03 p.m.
On Sun, 2008-06-22 at 22:56 +0000, Beartooth wrote:
On Sun, 22 Jun 2008 16:05:20 -0400, Tom Horsley wrote:
> So, if you have an nvidia card, the best bet for a working driver is to
> add the livna repo and download the kmod-nvidia driver.
I *think* so; what I know of hardware would go comfortably in a
gnat's eye.
I do now have livna on all three Fedora machines that use this
monitor; and have run or am running yum update. But I don't know how to
download -- just "yum install kmod-nvidia"? Or kmod-nvidia-driver? Or
kmod-nvidia_driver? Or ....
----
http://rpm.livna.org/rlowiki/LivnaSwitcher
Craig
6:07 p.m.
On Sun, 22 Jun 2008 22:56:41 +0000 (UTC)
Beartooth <Beartooth(a)swva.net> wrote:
On Sun, 22 Jun 2008 16:05:20 -0400, Tom Horsley wrote:
> So, if you have an nvidia card, the best bet for a working driver is to
> add the livna repo and download the kmod-nvidia driver.
I *think* so; what I know of hardware would go comfortably in a
gnat's eye.
I do now have livna on all three Fedora machines that use this
monitor; and have run or am running yum update. But I don't know how to
download -- just "yum install kmod-nvidia"? Or kmod-nvidia-driver? Or
kmod-nvidia_driver? Or ....
yum install kmod-nvidia will probably work, or you could search for
nvidia in whatever the new PackageKit tool is (probably under
something like Add/Remove software in the menus).
> You could take a look at the /var/log/Xorg.0.log file and see if is says
> things like "Oh look, I'm supposed to run this display at 1680x1050, but
> I don't think that's a good idea" :-).
Doing that now ...
The log file will have lines with (NV) on them if you are using the
nv driver. Possibly the installer generated xorg.conf file will also
mention the nv driver.
If its not an nvidia card, you definitely don't want to install the
nvidia drivers :-).
I think the lspci tool can also give you a good hint about what hardware
is on the system.
5:56 p.m.
On Sun, 22 Jun 2008 16:05:20 -0400, Tom Horsley wrote:
So, if you have an nvidia card, the best bet for a working driver is
to
add the livna repo and download the kmod-nvidia driver.
I *think* so; what I know of hardware would go comfortably in a
gnat's eye.
I do now have livna on all three Fedora machines that use this
monitor; and have run or am running yum update. But I don't know how to
download -- just "yum install kmod-nvidia"? Or kmod-nvidia-driver? Or
kmod-nvidia_driver? Or ....
You could take a look at the /var/log/Xorg.0.log file and see if is
says
things like "Oh look, I'm supposed to run this display at 1680x1050, but
I don't think that's a good idea" :-).
Doing that now ...
--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Fedora 8 & 9; Alpine 1.10, Pan 0.132; Privoxy 3.0.6;
Dillo 0.8.6, Galeon 2.0.3, Epiphany 2.20, Opera 9.27, Firefox 2.0
Remember I know precious little of what I am talking about.
5:36 p.m.
On Sun, 22 Jun 2008 16:05:20 -0400, Tom Horsley wrote:
On Sun, 22 Jun 2008 18:44:25 +0000 (UTC) Beartooth
<Beartooth(a)swva.net>
wrote:
> Is there some secret driver somewhere that I should be getting?
Depends on what driver you have now. The "nv" driver has problems with
lots of video cards and monitors:
https://bugzilla.redhat.com/show_bug.cgi?id=234824
as does the potential replacement "nouveau" driver:
https://bugzilla.redhat.com/show_bug.cgi?id=447526
So, if you have an nvidia card, the best bet for a working driver is to
add the livna repo and download the kmod-nvidia driver.
You could take a look at the /var/log/Xorg.0.log file and see if is says
things like "Oh look, I'm supposed to run this display at 1680x1050, but
I don't think that's a good idea" :-).
Hmmm ... I *think* the PackageKit in F9 (when it get to it) will
let me do that with a couple of clicks. I know there's a way to add livna
to F8 -- I've done it -- but it's been a while. I *think* I browse to
livna.org, download an rpm, install it, and then just use yum as always,
with one more file yum.repos.d; I'll check those things, and if it's so,
I'm golden -- no reply required. If I'm confused, prithee divulge one
more such excellent clue!
--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Fedora 8 & 9; Alpine 1.10, Pan 0.132; Privoxy 3.0.6;
Dillo 0.8.6, Galeon 2.0.3, Epiphany 2.20, Opera 9.27, Firefox 2.0
Remember I know precious little of what I am talking about.
3:05 p.m.
On Sun, 22 Jun 2008 18:44:25 +0000 (UTC)
Beartooth <Beartooth(a)swva.net> wrote:
Is there some secret driver somewhere that I should be getting?
Depends on what driver you have now. The "nv" driver has problems
with lots of video cards and monitors:
https://bugzilla.redhat.com/show_bug.cgi?id=234824
as does the potential replacement "nouveau" driver:
https://bugzilla.redhat.com/show_bug.cgi?id=447526
So, if you have an nvidia card, the best bet for a working
driver is to add the livna repo and download the kmod-nvidia
driver.
You could take a look at the /var/log/Xorg.0.log file and
see if is says things like "Oh look, I'm supposed to run this
display at 1680x1050, but I don't think that's a good idea" :-).
5775
days inactive
5785
days old
15 comments
7 participants
participants (7)
-
Antonio Olivares -
Beartooth -
Björn Persson -
Craig White -
Raymond C. Rodgers -
Tim -
Tom Horsley