On Mon, 30 Jun 2008 21:05:38 +0100, Frank Murphy wrote: [...]
[In a long thread, called "Hardware browser??" about ways to configure a PC with unknown video card, so that it can use a HP w2207h 1680x1050 monitor]
look under /var/log/Xorg.0.log
it will give you a lot of info about your monitor and card.
If your unsure what to look for.
Start a new tread with maybe subject: help with setting up graphics/
I made that "cat /var/log/Xorg.0.log|most" and started slogging. Other than the two lines below, I see nothing that even might be enlightening.
===== ===== ===== (II) VESA(0): VESA VBE OEM: VIA K8M890CE
(II) <default pointer>: Setting mouse protocol to "ExplorerPS/2" (It's actually a USB mouse, currently behind a MiniView G-CSIO4U KVM switch.) ===== ===== =====
Btw, I *run* machines behind the KVM switch; but I *install* OSs, one machine at a time, with the machine pulled out from behind the switch and connected directly to the peripherals.
On Mon, 2008-06-30 at 21:00 +0000, Beartooth wrote:
On Mon, 30 Jun 2008 21:05:38 +0100, Frank Murphy wrote: [...]
[In a long thread, called "Hardware browser??" about ways to configure a PC with unknown video card, so that it can use a HP w2207h 1680x1050 monitor]
look under /var/log/Xorg.0.log
it will give you a lot of info about your monitor and card.
If your unsure what to look for.
Start a new tread with maybe subject: help with setting up graphics/
I made that "cat /var/log/Xorg.0.log|most" and started slogging. Other than the two lines below, I see nothing that even might be enlightening.
===== ===== =====
Could you post the complete Xorg.0.log. Try not to use the grep\more\less etc..
There will be stuff usefule that others more knowledgeable (a lot more) than myself will gather from it.
The same with any other log post the full thing.
http://h10010.www1.hp.com/wwpc/uk/en/ho/WF06b/20491-314293-314303-314303-314...
Should be you monitor?
Frank
On Wed, 02 Jul 2008 11:50:02 +0100, Frank Murphy wrote:
On Mon, 2008-06-30 at 21:00 +0000, Beartooth wrote:
[...]
Start a new tread with maybe subject: help with setting up graphics/
I made that "cat /var/log/Xorg.0.log|most" and started slogging. Other than the two lines below, I see nothing that even might be enlightening.
[...]
Could you post the complete Xorg.0.log. Try not to use the grep\more\less etc..
[...]
I wrote a detailed email reply, which should have appeared here (on Gmane) ere now; I think there was a glitch in the list address. I'll go copy it from my outbox and re-post. My apologies in advance if it eventually shows up twice!
When it does appear, I have a follow-up with videocard info.
On Wed, 02 Jul 2008 11:50:02 +0100, Frank Murphy wrote:
Could you post the complete Xorg.0.log. Try not to use the grep\more\less etc..
There will be stuff useful that others more knowledgeable (a lot more) than myself will gather from it.
The same with any other log post the full thing.
I'll try. But I'm on email (Alpine 1.10) at the moment, and I'm not going to try to copy a file that length into it, page by page or screen by screen.
Does the list accept attachments?? I can probably do that; or I can use Pan (0.132) against Gmane -- my normal and strongly favored way of monitoring this list -- which will let me paste the whole huge thing (from gedit, which will let me copy it all at once) smack into the text of a post.
http://h10010.www1.hp.com/wwpc/uk/en/ho/WF06b/20491-314293 -314303-314303-314303-80720291-80720356.html
Should be you monitor?
That certainly seems to be the one, yes, thanks! But I've moused all over it, following every likely link, only to conclude there's no finding a driver without knowing your video card.
So I broke down and sent an email to the guy who built my current machines for me, asking if he has records of what he put in. Stay tuned.
On Wed, 02 Jul 2008 18:53:12 +0000, I Beartooth wrote:
On Wed, 02 Jul 2008 11:50:02 +0100, Frank Murphy wrote:
[...]
http://h10010.www1.hp.com/wwpc/uk/en/ho/WF06b/20491-314293 -314303-314303-314303-80720291-80720356.html
Should be you monitor?
That certainly seems to be the one, yes, thanks! ButI've moused all over it, following every likely link, only to conclude there's no finding a driver without knowing your video card.
So I broke down and sent an email to the guy whobuilt my current machines for me, asking if he has records of what he put in. Stay tuned.
My query and the response from the builder are as follows :
===== ===== =====
I've tried the hardware browsing tools I can find. I see M2V-TVM on this newest machine, and I seem to be seeing A7NVM400 on both the others -- is that possible? Or am I looking in the wrong place?
It's possible the two computers have the same motherboards. That particular one was very good with several updates and series available for almost 2 years. It's also possible that one is an A7N8X-VM and the other is an A7N8X-VM/400 which was released about a year later. This series uses the nVidia nForce2 video adaptor.
The M2V-TVM has a VIA DeltaChrome Graphics Controller. ===== ===== =====
Translation : that means what I call machine #1 (now running F8) has the VIA DeltaChrome Graphics Controller, while what I call #2 and #3 both have the nVidia nForce2 video adaptor.
Meanwhile, fwiw, I took #1 out from behind the KVM switch, meaning to try again to upgrade, hit a large snag, thought better of the attempt, and put it back. In the process, all three machines got rebooted.
On all three reboots, X failed; I logged in as root, ran system- config-display, logged back out, logged in as user, and commanded startx.
On all three, I got a display -- a bad one; ran the display applet (whose Properties give /usr/bin/system-config-display as its command), logged out, and repeated the exercise at least once, till I got each to run 1280x1024 given under Settings and "generic lcd 1280x1024" under Hardware. That's not optimal, of course, on a 1680x1050 monitor; but it's more usable, I find, than some of the other things that get substituted for it, such as iirc 1440x900 or 1400x1050 -- more usable, at least, in that the monitor adapts by stretching in ways that gripe me less.
Upshot : I *think* what I now need is to discover what drivers to get, and where, for the VIA DeltaChrome Graphics Controller and the nVidia nForce2 video adaptor. And then, of course, to install them on the right machines. Right?
On Wed, 2008-07-02 at 19:24 +0000, Beartooth wrote:
On Wed, 02 Jul 2008 18:53:12 +0000, I Beartooth wrote:
On Wed, 02 Jul 2008 11:50:02 +0100, Frank Murphy wrote:
[...]
http://h10010.www1.hp.com/wwpc/uk/en/ho/WF06b/20491-314293 -314303-314303-314303-80720291-80720356.html
<massive snip>
Would you be willing to send (email me the logs from all three machines. It's the one monitor they share?
Send me the xorg.conf mark them machine 1,2,3 as you know them as i'm on gmt (Ireland) you may not get a reply till the following day in your tz
Frank
--- On Wed, 7/2/08, Beartooth Beartooth@swva.net wrote:
From: Beartooth Beartooth@swva.net Subject: Re: Fedora 9 Openchrome drv HP w2207h Monitor was: Re: help with setting up graphics To: fedora-list@redhat.com Date: Wednesday, July 2, 2008, 11:53 AM On Wed, 02 Jul 2008 11:50:02 +0100, Frank Murphy wrote:
Could you post the complete Xorg.0.log. Try not to use the grep\more\less etc..
There will be stuff useful that others more
knowledgeable
(a lot more) than myself will gather from it.
The same with any other log post the full thing.
I'll try. But I'm on email (Alpine 1.10) atthe moment, and I'm not going to try to copy a file that length into it, page by page or screen by screen.
Does the list accept attachments?? I can probablydo that; or I can use Pan (0.132) against Gmane -- my normal and strongly favored way of monitoring this list -- which will let me paste the whole huge thing (from gedit, which will let me copy it all at once) smack into the text of a post.
http://h10010.www1.hp.com/wwpc/uk/en/ho/WF06b/20491-314293
-314303-314303-314303-80720291-80720356.html
Should be you monitor?
That certainly seems to be the one, yes, thanks!But I've moused all over it, following every likely link, only to conclude there's no finding a driver without knowing your video card.
So I broke down and sent an email to the guy whobuilt my current machines for me, asking if he has records of what he put in. Stay tuned.
-- Beartooth Staffwright, PhD, Neo-Redneck Linux Convert Remember I know precious little of what I am talking about.
--
I missed your previous posts, maybe clicking real fast, but I have an integrated video in the motherboard and I use OpenChrome driver.
[olivares@localhost ~]$ su - Password: [root@localhost ~]# lspci 00:00.0 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge 00:00.5 PIC: VIA Technologies, Inc. K8M890CE I/O APIC Interrupt Controller 00:00.7 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] 00:02.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller 00:03.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller 00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237A PCI to ISA Bridge 00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c) 00:13.0 Host bridge: VIA Technologies, Inc. VT8237A Host Bridge 00:13.1 PCI bridge: VIA Technologies, Inc. VT8237A PCI to PCI Bridge 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890 [Chrome9] Integrated Video (rev 11) 04:05.0 Communication controller: Agere Systems LT WinModem (rev 02) 80:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller (rev 10)
When I installed the machine, I booted to level 5, and I tried to play a dvd and I would see lines across the screen and I have a Samsumg SyncMater 914v Flat Panel Monitor. I tried getting the via drivers and thankfully they did not compile. What I did to fix my situation was the following:
Change inittab:5 to 3, that is from level 5 to level 3 and then type startx.
What I noticed is that I did not see the lines that I saw when the system booted into level 5. I played movies and did not see the bad lines that I previously saw. This corrected the issue for me. I also use Slax Linux on this machine and when the machine booted and logged in automatically to X, the lines appeared, but then, I booted in text mode and created a module for the OpenChrome drivers
http://www.slax.org/modules.php?action=detail&id=713
I started X with startx and the lines did not appear. Problem was solved for me. I hope that this helps you with your problems.
Regards,
Antonio
On Wed, 02 Jul 2008 14:12:29 -0700, Antonio Olivares wrote: [...]
I missed your previous posts, maybe clicking real fast, but I have an integrated video in the motherboard and I use OpenChrome driver.
[olivares@localhost ~]$ su - Password: [root@localhost ~]# lspci 00:00.0 Host bridge: VIA Technologies, Inc. K8M890CE [...]
Somewhere in there, I did hit a K8M890, but not with the CE.
[...] What I did to fix my situation was the following:
Change inittab:5 to 3, that is from level 5 to level 3 and then type startx.
Hmmm ... With mine, startx as user works *after* I've gone through all the screens Fedora gives you when it can't start X -- including running what appears identical to the display you get with system-config-display, and changing both the Settings and Hardware entries *back* to what I had when I shut down last. Why it doesn't keep them, as it always used to, I don't know.
I couldn't make sense of what I found by searching inittab; so I'm probably missing something. I'm guessing that I could simply edit / etc/grub.conf, putting a 3 after the first kernel entry. Then it would boot into level 3; I could log in as user, and simply command startx. Is that right?
Or, as a prior experiment, I could edit the kernel line from the grub boot-up splash, try init 3 that way, and only actually edit grub.conf if the experiment succeeds.
[...] I also use Slax Linux on this machine and when the machine booted and logged in automatically to X, the lines appeared, but then, I booted in text mode and created a module for the OpenChrome drivers
Now I'm very confused, in part perhaps because I know nothing at all about slax. It looks to me as if that site is offering to download something to run under that OS, rather than Fedora. Not the case?
I started X with startx and the lines did not appear. Problem was solved for me. I hope that this helps you with your problems.
I can't imagine why startx would work immediately after logging in in text mode, without touching anything that affects the configuration of X; and it seems a strange, roundabout approach. But I'm willing to try it, if I understand aright what it is I'm to try.
--- On Thu, 7/3/08, Beartooth Beartooth@swva.net wrote:
From: Beartooth Beartooth@swva.net Subject: Re: Fedora 9 Openchrome drv HP w2207h Monitor was: Re: help with setting up graphics To: fedora-list@redhat.com Date: Thursday, July 3, 2008, 9:20 AM On Wed, 02 Jul 2008 14:12:29 -0700, Antonio Olivares wrote: [...]
I missed your previous posts, maybe clicking real
fast, but I have an
integrated video in the motherboard and I use
OpenChrome driver.
[olivares@localhost ~]$ su - Password: [root@localhost ~]# lspci 00:00.0 Host bridge: VIA Technologies, Inc. K8M890CE
[...]
Somewhere in there, I did hit a K8M890, but not with the CE.
[...] What I did to fix my situation was the following:
Change inittab:5 to 3, that is from level 5 to level 3
and then type
startx.
Hmmm ... With mine, startx as user works *after* I've gone through all the screens Fedora gives you when it can't start X -- including running what appears identical to the display you get with system-config-display, and changing both the Settings and Hardware entries *back* to what I had when I shut down last. Why it doesn't keep them, as it always used to, I don't know.
I couldn't make sense of what I found by searching inittab; so I'm probably missing something. I'm guessing that I could simply edit / etc/grub.conf, putting a 3 after the first kernel entry. Then it would boot into level 3; I could log in as user, and simply command startx. Is that right?
Well you could do that, but it is easier as root user to do the following:
$ su - password: #
open up with an editor of your choice and edit /etc/inittab
change the line "id:5:initdefault:" to "id:3:initdefault:" and that will start the system in level 3.
[root@localhost ~]# cat /etc/inittab # inittab is only used by upstart for the default runlevel. # # ADDING OTHER CONFIGURATION HERE WILL HAVE NO EFFECT ON YOUR SYSTEM. # # System initialization is started by /etc/event.d/rcS # # Individual runlevels are started by /etc/event.d/rc[0-6] # # Ctrl-Alt-Delete is handled by /etc/event.d/control-alt-delete # # Terminal gettys (tty[1-6]) are handled by /etc/event.d/tty[1-6] and # /etc/event.d/serial # # For information on how to write upstart event handlers, or how # upstart works, see init(8), initctl(8), and events(5). # # Default runlevel. The runlevels used are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:3:initdefault:
Or, as a prior experiment, I could edit the kernel line from the grub boot-up splash, try init 3 that way, and only actually edit grub.conf if the experiment succeeds.
[...] I also use Slax Linux on this machine and when the machine
booted and logged in
automatically to X, the lines appeared, but then, I
booted in text mode
and created a module for the OpenChrome drivers
http://www.slax.org/modules.php?action=detail&id=713
Now I'm very confused, in part perhaps because I know nothing at all about slax. It looks to me as if that site is offering to download something to run under that OS, rather than Fedora. Not the case?
Yes, it is a module, that will run under Slax not Fedora. Fedora has the driver built in.
[root@localhost ~]# rpm -qa xorg-x11-drv-o* xorg-x11-drv-openchrome-0.2.902-3.fc9.x86_64 [root@localhost ~]#
In slax, it was not there so I downloaded the (OpenChrome)driver and built it using the rules for that system(Slax) and I have the same functionality that I do under Fedora with it. I just start slax in text mode, load that module referenced above and configure the X window with xconf and then type startx and I have a much better experience than with the default driver loaded there.
In Fedora I tried different things and it did not work for me. So I tried changing xorg.conf and still the same, I did Xorg -configure as root and changed xorg.conf and still no go. I went back to the original and started in level 3. Then I tried to play a movie and the lines that appeared did not appear and it solved the problem for me.
I started X with startx and the lines did not appear.
Problem was
solved for me. I hope that this helps you with your
problems.
I can't imagine why startx would work immediately after logging in in text mode, without touching anything that affects the configuration of X; and it seems a strange, roundabout approach. But I'm willing to try it, if I understand aright what it is I'm to try.
-- 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.
--
I will attach xorg.conf here in case it might help.
[root@localhost ~]# cat /etc/X11/xorg.conf # Xorg configuration created by pyxf86config
Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "InputDevice" # keyboard added by rhpxl Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection
Section "Device" Identifier "Videocard0" Driver "openchrome" EndSection
Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection
[root@localhost ~]#
Hope this helps fix your issues.
Regards,
Antonio
Beartooth wrote:
I can't imagine why startx would work immediately after logging in in text mode, without touching anything that affects the configuration of X; and it seems a strange, roundabout approach. But I'm willing to try it, if I understand aright what it is I'm to try.
I don't understand it either but similar things happen to me. If I boot into runlevel 5 I only get a black screen. If I boot into runlevel 3, log in as root and run "init 5 ; exit", then X starts just fine. I've described the problem here:
https://bugzilla.redhat.com/show_bug.cgi?id=448340
Weird.
Björn Persson
On Fri, 04 Jul 2008 02:20:14 +0200, Björn Persson wrote: [...]
I don't understand it either but similar things happen to me. If I boot into runlevel 5 I only get a black screen. If I boot into runlevel 3, log in as root and run "init 5 ; exit", then X starts just fine. I've described the problem here:
I'll take a look at that shortly, thanks. Meanwhile, I did manage to get #1 as well as #2 machine to run F9; but unless/until I hear better from Frank Murphy, I have to boot both in init3, log in as root, and play with the X configuration first by editing /etc/X11/xorg.conf and then by running system-config-display. That gives me a weird error message, something to the effect that the connection to the Xserver is temporarily unavailable. But if I then log root out and my userid in, I can command startx, and it takes a while but works.
Next time I have to shut one of them down, or sooner if I get to it, I'll try your way instead; it certainly sounds shorter and easier. And, come to think of it, last time I did mine, I didn't change anything with either my editor or my config command; just ran them, logged root out and userid in.
I have to say, I've already had more trouble with F9 than ever with any other release, since I started on RH7. (I had RH6, boughten in a bookstore, but never succeeded in installing it at all.) What's more, I can't remember nearly so many others describing install problems in my time watching this list ....
Otoh, it certainly isn't any fault of our developers that (what seems to be) a new generation of hardware technology (i.e., wide-screen monitors with numerous bells & whistles) has been coming out right along with their release, not giving them to take account of it.
On Sun, 06 Jul 2008 15:56:37 +0000, Beartooth wrote:
On Fri, 04 Jul 2008 02:20:14 +0200, Björn Persson wrote: [...]
I don't understand it either but similar things happen to me. If I boot into runlevel 5 I only get a black screen. If I boot into runlevel 3, log in as root and run "init 5 ; exit", then X starts just fine. I've described the problem here:
I'll take a look at that shortly, thanks.
Meanwhile, I did manage to get #1 as well as #2 machine to runF9; but unless/until I hear better from Frank Murphy, I have to boot both in init3, log in as root, and play with the X configuration first by editing /etc/X11/xorg.conf and then by running system-config-display. That gives me a weird error message, something to the effect that the connection to the Xserver is temporarily unavailable. But if I then log root out and my userid in, I can command startx, and it takes a while but works.
Next time I have to shut one of them down, or sooner if I get to it, I'll try your way instead; it certainly sounds shorter and easier. And, come to think of it, last time I did mine, I didn't change anything with either my editor or my config command; just ran them, logged root out and userid in.
[....]
Yesterday evening we had a short power failure, about the time I'd've normally been getting offline anyway; so I shut everything down, all the way to the UPSs. This morning I've just brought up my #2 machine, the one with the nvidia video card, which has long been running F9.
I tried Bjorn Persson's shorter way first. No joy. After init 5, I had a couple of failures among the messages on the screen, and then it hung.
One failure, new to me afaik, said :
===== ===== ===== [....] rpc.idmap: Unable to create user id mappings: FAILED [...] Starting router discovery FAILED [but during init 3 boot it had handled not only eth0 but ntp time synch -- so it was connecting, somehow.] [...] Starting NetworkManager daemon OK ===== ===== =====
NMd may have been OK, but something wasn't; everything hung at that point. After a long time, I tried Ctrl-Alt-Backspace; no visible result. Ctrl-Alt-Delete got a message, repeated six or eight times, saying those keys had been pressed, and the machine was going down -- but it didn't. It hung again there.
So I tried the reset button, and that worked.
At the grub splash, I edited the first kernel to add a 3, and booted. But when I got my prompt, and logged in as root, I tried first "nano -w /etc/X11/xorg.conf" -- and made no changes. (It said, then, that livna nvidia, or whatever, had created it.) Both the monitor section and the screen section had 1280x1024. (The videocard section had, iirc, vesa.)
So I commanded system-config-display. The hardware tab called itself autoconfigured, and when I told it to let me, it came up with generic CRT; I changed that to 1280x1024 LCD, and then the settings from 800x600 to 1280x1024.
It gave messages saying :
===== ===== ===== Couldn't start X server on card 0 " " " " with old config, trying with a fresh configuration Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) display ': 17.0' ===== ===== =====
There it stopped, and gave root's prompt back. I logged out, and back in as user; commanded startx; it sat there ten or twenty seconds with the monitor showing shaded horizontal gray bands; and then came up almost normally.
xorg.conf now says it was created by system-config-display; and the videocard driver is set to nv.
The apps I had left on when shutting down were all or almost all in the upper left workspace, and my gnome terminal had only one tab and was not quite the right size nor in quite the right place. But otherwise it seemed normal, except that privoxy wasn't running.
Now I'll go try machine #1, which has a VIA card -- and which, yesterday or the day before, I had tried yet again to upgrade from F8 to F9 -- successfully, this time, at last, afaict (except that it had not been through a reboot). I'll make those results a separate post, when I have them. Stay tuned.
On Mon, 07 Jul 2008 15:02:08 +0000, I Beartooth wrote:
On Fri, 04 Jul 2008 02:20:14 +0200, Björn Persson wrote: [...]
I don't understand it either but similar things happen to me. If I boot into runlevel 5 I only get a black screen. If I boot into runlevel 3, log in as root and run "init 5 ; exit", then X starts just fine. I've described the problem here:
[....]
There it stopped, and gave root's prompt back. I logged out, and back in as user; commanded startx; it sat there ten or twenty seconds with the monitor showing shaded horizontal gray bands; and then came up almost normally.
xorg.conf now says it was created by system-config-display; and the videocard driver is set to nv.
The apps I had left on when shutting down were all or almost all in the upper left workspace, and my gnome terminal had only one tab and was not quite the right size nor in quite the right place. But otherwise it seemed normal, except that privoxy wasn't running.
Now I'll go try machine #1, which has a VIA card -- and which, yesterday or the day before, I had tried yet again to upgrade from F8 to F9 -- successfully, this time, at last, afaict (except that it had not been through a reboot). I'll make those results a separate post, when I have them. Stay tuned.
I'm now on the other machine; the Persson method worked here -- or mostly did. I can get my remote email, and the browsers I've checked so far can get to some, but not all, of the sites they had at shutdown yesterday. I have checked that both xinetd and privoxy are running; and the error messages I get on the unreached sites are not privoxy messages, anyway, but "Address not found," apparently from the browser. At least one of them (a trail & hiking forum) does come up, and let me participate, on Firefox but not on Galeon.
I'll keep trying a little longer, in hopes of a clue to whether the trouble is in Galeon a/o other browsers, or in F9, or my hardware -- or at my local access provider.
Meanwhile, Frank Murphy has kindly emailed a whole xorg.conf designed specifically for this monitor. I have moved the old one out of the way, and created a new one copied from his email. I'll log out and back in in a little while, and report how it does.
On Mon, 07 Jul 2008 16:21:41 +0000, I Beartooth wrote: [....]
I'll keep trying a little longer, in hopes of a clue to whether the trouble is in Galeon a/o other browsers, or in F9, or my hardware -- or at my local access provider.
Meanwhile, Frank Murphy has kindly emailed a whole xorg.conf designed specifically for this monitor. I have moved the old one out of the way, and created a new one copied from his email. I'll log out and back in in a little while, and report how it does.
Disaster -- but I have no idea whether Frank's xorg.conf had anything at all to do with it.
That machine has been going into occasional snits lately -- acting as if it were over its head in cold molasses. Small example : a time or two, on reboot, it got as far as "Stand by for reboot" -- and then went without any further sign of activity for six whole minutes, by the sweep second hand on my atomic wristwatch. Another example: one time I left it doing nothing visible, ran into town, and did errands for a couple of hours. When I got home, it had finally done the next thing -- and was stuck again.
It does it under both F8 and F9 -- but not XP (which is on the other hard drive). I can't even tell whether it's hitting an endless 100% cpu loop, or heating something up in the hardware. But I have asked a young friend who does computer repair & maintenance for a living to come by some evening this week, with his testing tools.
Whatever the reason, when it does that, it doesn't respond to Ctrl-Alt-Backspace, nor to Ctrl-Alt-Delete, nor yet to the reset button, nor even to the power button. I have to literally pull the plug on it.
Then when I restore electricity, sometimes it comes back still in the snit, and sometimes not.
So I haven't yet managed to give the new xorg.conf anything like a real test yet, and don't know when I'll be able to.
On Mon, 2008-07-07 at 18:35 +0000, Beartooth wrote:
On Mon, 07 Jul 2008 16:21:41 +0000, I Beartooth wrote:
Disaster -- but I have no idea whether Frank's xorg.conf had anything at all to do with it.
Gulp ;)
That machine has been going into occasional snits lately -- acting as if it were over its head in cold molasses. Small example : a time or two, on reboot, it got as far as "Stand by for reboot" -- and then went without any further sign of activity for six whole minutes, by the sweep second hand on my atomic wristwatch. Another example: one time I left it doing nothing visible, ran into town, and did errands for a couple of hours. When I got home, it had finally done the next thing -- and was stuck again.
Do the hardware tests, and then have another crack at it.
Frank
On Mon, 07 Jul 2008 19:42:31 +0100, Frank Murphy wrote:
On Mon, 2008-07-07 at 18:35 +0000, Beartooth wrote:
On Mon, 07 Jul 2008 16:21:41 +0000, I Beartooth wrote:
Disaster -- but I have no idea whether Frank's xorg.conf had anything at all to do with it.
Gulp ;)
[...] <grin>
Do the hardware tests, and then have another crack at it.
I plugged it back in, booted to init 3, moved the xorg.conf it had to xorg.conf.fmurph and the backup back into xorg.conf, and then ran nano -w against that -- changing "vesa" to "openchrome" but leaving all else alone. Then I tried system-config-display again; usually, when I do that as root from an init 3 prompt, it lets me use the minimal gui it gives me. This time, however, the cursor immediately froze, and I couldn't even get to the hardware tab. Keyboard commands did nothing visible. The reset button eventually got me a reboot; I changed the driver back to vesa, and system-config-display opened properly -- with nothing to change.
I logged out, and back in as user; did su - and then "init 5" instead of startx. It hesitated a moment, gave me the normal login screen, and let me log in.
It looks pretty normal; but neither Galeon, nor Epiphany, nor Firefox (the three browsers I've tried so far) can connect. I had to get into the little system-config-network (launcher showing two monitors on one pipe) to make a connection; but xinet and privoxy were both already running. Yum update couldn't connect, either.
According to bugbuddy, epiphany has just crashed.
The very bottommost line of Firefox was doing a Saint Vitus dance, back and forth. that stopped when I told it to work offline, and didn't start again when I rescinded that; but it still doesn't connect. Neither does Opera, nor Pan. Stay tuned.
On Mon, 07 Jul 2008 21:18:52 +0000, Beartooth wrote:
It looks pretty normal; but neither Galeon, nor Epiphany, nor Firefox (the three browsers I've tried so far) can connect. I had to get into the little system-config-network (launcher showing two monitors on one pipe) to make a connection; but xinet and privoxy were both already running. Yum update couldn't connect, either.
According to bugbuddy, epiphany has just crashed.
The very bottommost line of Firefox was doing a Saint Vitus dance, back and forth. that stopped when I told it to work offline, and didn't start again when I rescinded that; but it still doesn't connect. Neither does Opera, nor Pan. Stay tuned.
I let it run all night, and tried again this morning. xinetd and privoxy were still running, and the two net launchers on my left panel (the system-config-network one and the one with two monitors not visibly connected, which fails to give its name) both claimed a connection; but still nothing would connect.
I got into the s-c-n app, made eth0 inactive, changed localhost.localdomain on the DNS tab to Tpbk.localdomain, and made eth0 active again -- Lo! and Behold! -- everything worked.
When I tried that again just now (couldn't remember the name of the tab), it said localhost.localdomain again. So I suppose what did it was just turning eth0 off and back on ...
I'm on #1 now. I'll keep running it till I get my routine pensum behind me, and then try xorg.conf.fmurph again, some hours from now. Stay tuned.
On Sun, 06 Jul 2008 15:56:37 +0000, Beartooth wrote:
On Fri, 04 Jul 2008 02:20:14 +0200, Björn Persson wrote: [...]
I don't understand it either but similar things happen to me. If I boot into runlevel 5 I only get a black screen. If I boot into runlevel 3, log in as root and run "init 5 ; exit", then X starts just fine. I've described the problem here:
I'll take a look at that shortly, thanks.
Meanwhile, I did manage to get #1 as well as #2 machine to runF9; but unless/until I hear better from Frank Murphy, I have to boot both in init3, log in as root, and play with the X configuration first by editing /etc/X11/xorg.conf and then by running system-config-display. That gives me a weird error message, something to the effect that the connection to the Xserver is temporarily unavailable. But if I then log root out and my userid in, I can command startx, and it takes a while but works.
Next time I have to shut one of them down, or sooner if I get to it, I'll try your way instead; it certainly sounds shorter and easier. And, come to think of it, last time I did mine, I didn't change anything with either my editor or my config command; just ran them, logged root out and userid in.
[....]
One relevant and one almost surely relevant discovery.
My #1 hardware (with the VIA card) didn't like the xorg.conf file that Frank Murphy sent -- not quite; but almost. I made three copies, with changes in each; first with "vesa" replacing "openchrome" as the driver; second, with the resolution choked all the way back from 1680x1050, which the monitor demands, to 1280x1024, which I know both machines #1 and #2 can handle; third with both those changes.
With the first, the vesa version, I didn't just boot, but took the Persson Precaution : edited grub to boot to init 3, logged in as root, and simply commanded "init 5."
That worked so well I haven't tried anything else yet, not even booting without the Persson Precaution. I have full use of the whole 1680x1050 resolution, and have had neither any sort of display breakdowns, nor any other trouble. I look forward to getting #2 (with the nvidia card) to do as well some day.
Since then, yum update on at least one machine (I wish I could remember which! But I may have spotted the like on only one but gotten it on both...) -- on one machine, I say, yum update has brought at least a dozen X11 items, about half containing the substring "-drv-"; I *think* those must be drivers, right?
Has anybody else tried any of them with the HP w2207h yet? Would it be a good idea just to run system-config-display again?
Perhaps try the list of HP flat panel monitors, which didn't include this one last time I looked? Or run system-config-display only after editing a particular one of them into xorg.conf?
Björn Persson wrote:
Beartooth wrote:
I can't imagine why startx would work immediately after logging in in text mode, without touching anything that affects the configuration of X; and it seems a strange, roundabout approach. But I'm willing to try it, if I understand aright what it is I'm to try.
I don't understand it either but similar things happen to me. If I boot into runlevel 5 I only get a black screen. If I boot into runlevel 3, log in as root and run "init 5 ; exit", then X starts just fine.
This thread is a bit old but I thought I should mention what I've discovered: Booting into runlevel 5 works if I disable RHGB (by removing "rhgb" from the Linux command line). RHGB also doesn't run in runlevel 3, so that's why booting into runlevel 3 made a difference. It seems like X works only if X hasn't run before since the machine was booted. (RHGB uses its own instance of X.)
I no longer have to run "init 5" manually. Of course I don't know how this will work for anyone else.
Björn Persson
-
Antonio Olivares -
Beartooth -
Björn Persson -
Björn Persson -
Frank Murphy