RH7.3 keyborad lock-up
In-Reply-To: Message from Ray Olszewski <[email protected]>
of "Fri, 09 Aug 2002 23:59:11 MST."
<5.1.0.14.1.20020809234007.0208bd20@celine>
Thanks!
Quoted 4 lines · [email protected] said:
The one characteristic I see as common to the three problem apps, but absent in the OK apps, is speed and frequency of screen updating. They
would be more likely to trip an infrequently occurring failure in the
X server, simply because they make a lot more calls to it.
I came slowly to this conclusion myself that it must have something to do with the graphics.
Quoted 5 lines · [email protected] said:
I'd bet that you are switching from XFree86-3.3.6 or so to XFree86-4.something, and this is a big change. I'm not sure where RH puts X config info, but look for a file named XF86Config (maybe
/etc/X11/XF86Config-4 for the new version) to see which X server you are running.
I made that switch with RH7.1 some time ago with no problems. 7.1 runs on XFree86-4.0.3-5 and and 7.3 om XFree-4.2.0-8. It is there /etc/X11/XF86Config-4 but I can not find anything specific as to what X server I am running. Must be my ignorance.
If you think that the problem might be in these XF86Config files and I have no problem with RH7.1, how about installing the kernel of RH7.3, libraries etc and then replacing the 7.3 XF86Config files with the ones of RH7.1.
BTW I posted the problem as well to the redhat-install list and somebody sugested
to turn off the apmd system (advanced power management) by unmarking the "apmd" entry in ntsysv.
What do you think about that? Would that have something to do with tuxracer or chromium?
Regards
Signature · 6 lines
Peter - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 3 lines · Peter
[...]
I made that switch with RH7.1 some time ago with no problems. 7.1 runs on XFree86-4.0.3-5 and and 7.3 om XFree-4.2.0-8.
This move by Red Hat may be optimistic. Even Debian unstable (Sid) still runs XFree86 4.1.0-17.
Quoted 3 lines
It is there
/etc/X11/XF86Config-4but I can not find anything specific as to what X server I am running. Must be my ignorance.
You want the "Driver" entry in the "Device" block. Here is mine as an example:
Section "Device"
Identifier "ATI OEM Card"
Driver "ati"
EndSection
Quoted 3 lines
If you think that the problem might be in these XF86Config files and I have no problem with RH7.1, how about installing the kernel of RH7.3, libraries etc and then replacing the 7.3 XF86Config files with the ones of RH7.1.
Risky. Likely to encounter library incompatibilities.
Quoted 6 lines
BTW I posted the problem as well to the redhat-install list and somebody sugested
to turn off the apmd system (advanced power management) by unmarking the "apmd" entry in ntsysv.
What do you think about that? Would that have something to do with tuxracer or chromium?
Well outside my real expertise, but it seems farfetched, given that the system is running and only the keyboard (and perhaps portions of the display) has failed.
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Hi Peter.
Quoted 5 lines
Quoted 2 lines
I made that switch with RH7.1 some time ago with no problems. 7.1 runs on XFree86-4.0.3-5 and 7.3 on XFree-4.2.0-8.
This move by Red Hat may be optimistic. Even Debian unstable (Sid) still runs XFree86 4.1.0-17.
That is certainly possible. What version does RH 7.2 use?
XFree86 is extremely difficult to downgrade. However, one option may exist if you have a CD-writer, and that is to create a CDR set with the 7.3 image, but with the XFree86 RPM's from 7.2 rather than the ones supplied with 7.3 and install from that.
Quoted 11 lines
Quoted 2 lines
It is there
/etc/X11/XF86Config-4but I can not find anything specific as to what X server I am running. Must be my ignorance.You want the "Driver" entry in the "Device" block. Here is mine as an example:
Section "Device" Identifier "ATI OEM Card" Driver "ati" EndSection
Quoted 6 lines
Quoted 4 lines
If you think that the problem might be in these XF86Config files and I have no problem with RH7.1, how about installing the kernel of RH7.3, libraries etc and then replacing the 7.3 XF86Config files with the ones of RH7.1.
Risky. Likely to encounter library incompatibilities.
Probably impossible.
Quoted 9 lines
Quoted 5 lines
BTW I posted the problem as well to the redhat-install list and somebody sugested to turn off the apmd system (advanced power management) by unmarking the "apmd" entry in ntsysv. What do you think about that? Would that have something to do with tuxracer or chromium?
Well outside my real expertise, but it seems farfetched, given that the system is running and only the keyboard (and perhaps portions of the display) has failed.
I can't comment re tuxracer and chromium, but that could easily be a problem with xscreensaver as it kicks into operation is precicely the same circumstances as apmd does. However, it's easy to test for, as apmd is, after all, a piece of software. If apmd is the problem, then upgrading to the version of apmd supplied with 7.3 will cause the problem to start occurring on your 7.1 based system.
If that causes the problem to occur, then you can cure it either by downgrading to the 7.1 version again or, more simply, by disabling apmd with the chkconfig apmd off command.
Best wishes from Riley.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs