Dear Stew,
thanks for the prompt answers. Here are my comments:
At Wed, 26 Jun 2002 06:25:23 -0400 (EDT),
Stew Benedict wrote:
> > [1] xemacs complained about inconsistent modifier maps. The culprit is
> > the compose key setting in `/etc/X11/xinit.d/PPC_altgr_compose'.
> > [Solution:] I changed `/etc/X11/xinit.d/PPC_altgr_compose to use the enter
> > key for `Compose' in mod3 instead of the Apple key for `Mode_switch Compose'
> > (that key is already in mod4 under the name `Super_L').
> >
>
> Any other thoughts on this? I don't think all the keyboards have the
> extra Enter key next to the spacebar, do they?
... well, the way it is right now is simply not correct. PPC_altgr_compose
makes the Apple-key work as Super_L and Mode_switch, which is inconsistent.
And this is reported by xemacs. I think the Super_L definition is supposed to
be removed by antoher script in /etc/X11/xinit.d/ called `Mod_Meta_L_Disable'.
However, that one poses the wrong question to `/etc/sysconfig/keyboard': it
checks for `REMOVE_MOD_META_L=yes', it should check for
`DISABLE_WINDOWS_KEY=yes', at least if it was to cure the inconsistency
mentioned above.
> > [2] It was not at all clear how to install the production kernel 2.4.18-6.1mdk
> > on the MacOS side on a BootX system because in the installation kernel there
> > has neither hfs nor cdrom support included. I have read here that one of the
> > initrd files is the right kernel: not easy to guess.
> >
>
> BootX folder on the ISO :) Should be mentioned in the installtion docs,
> and I know I've mentioned it here a few dozen times.
This is the place where I have found it. However, to find the searchable
archive of this list was not so easy: the MDK page has the link on the PPC FAQ
page. On the mailing lists page there is only a link to a non-searchable
archive.
> > Unsolved Problems:
> >
> > [1] I own a Zyxel ISDN terminal adapter that can be used like a modem. I used
> > to operate it on `/dev/ttyS0' (printer/modem port). This port does not
> > connect the powerbook to the TA anymore, it is dead or misconfigured. Any
> > signal sent to the TA would formerly cause the display backlight to switch on.
> > No reaction for my system now. Init commands don't reach the TA.
> > I would like to use it because it is faster (128k) than the internal modem
> > (56k).
> >
> > [Attempts:]
> > - checked port under MacOS: okay.
> > - checked for `alias serial macserial' in /etc/modules.conf: yes.
> > - checked the output of macserial: ttyS{0,1,2} all recognized
> > - stopped irda service, removed irda module: still not working
> >
>
> I'm not familiar with this device. Does it normally resond to AT commands
> like a normal modem?
Plain AT commands work.
> Have you tried just minicom or tuning the serial
> settings with setserial?
No. It used to work on my old system under kernel 2.4.4, where macserial was
built in.
> > [2] I can connect to the TA via USB Cardbus. Then the TA can be used to dial
> > into the ISP. The routes and name servers are set correctly and I can use
> > e.g. ssh. However, I cannot use the imap or http protocols: `could not
> > connect' (imap) or an infinite `retrieving site ...' (http) are the result.
> >
> > [Attempts:]
> > - I have already tried various options for ppp: no success
> > - switched off hardware compression at the TA: no success
> >
>
> Rather odd. Do you have a firewall setup?
Not that I know of. And a possible default MDK firewall should not notice
whether I am connected via internal modem (everything works) or USB TA (no WWW).
With best regards,
Joerg
--
Joerg Rambau ____ ___ Konrad Zuse Zentrum fuer Informationstechnik Berlin
____________// //// // Takustrasse 7, D-14195 Berlin-Dahlem, GERMANY
////_/ *Phone: +49-30 841 85-249 *Fax: -269
\\_//// \\[EMAIL PROTECTED]
