Hello. I'm having a weird problem, hope somebody can help me.
I'm upgrading my linux system from an older slackware installation to
a new redhat one. Everything is fine except for one major obstackle -
I cannot get in contact with my modem while in X-windows.
If I dont go into x-windows minicom works correctly.
If, while in X-windows,
I try to use eg minicom or seyon they popup correctly and dont
report any errors, but they have no active contact with the modem,
like the initialization string didn't do its job properly. As a result
the two programs doesn't accept keystrokes in the modem window, that is:
the cursor doesn't react if I try to type eg. atdtxxxxxxx, whereas all
other aspects of those programs works ok, like changing port setup etc.
Both minicom and seyon works without any problems in my slackware
installation, and the setup of the modem port etc in the new redhat
installation is exactly the same as in the old slackware installation.
What can going into X-windows possibly do which could prevent my
contact with the modem???
Let me list two other, but less irritating, weird things, which maybe
can help people with insight to diagnoze my problem:
a) When I leave x-windows in the redhat installation the console screen
gets filled with ugly signs (lines, clumps, masterspaces etc) not the
normal characters (plus some extra from the xinit session) which where
there before I entered x-windows. Similar any new keystroke produces a
weird sign, not at all a normal character.
b) in X-windows the keyboard setups are not exactly similar ( ie. xmodmap
-pke produces different results in the old slackware and the new redhat
installation), however, if running the redhat installation I try to do
xmodmap slackware.map (where slackware map is a dump of the total xmodmap
view of the slackware keyboard settings) I cannot do that, as xmodmap
finds it cannot create all the settings.
Thanks in advance for any help. Henrik Vedel, Copenhagen, Denmark.