On Wed, 26 Jun 2002, Joerg Rambau wrote:
> Hi,
>
> I have successfully installed 8.2 on my PBG3 WS (266MHz/192MBRAM, stock kernel
> 2.4.18-6.1mdk). I have had before a manually updated glibc-2.1 YDL system
> before (everything was working fine but no manual upgrades possible anymore
> because of glibc.)
>
> Thank you very much for a very attractive distribution that is essentially
> consistent to what Mandrake offers on the intel side. Below I list some
> problems I encountered. Some of them are yet unsolved. Many thanks for any
> input!
>
>
> Good in MDK8.2:
>
> * fast & stable
> * really nice configuration tools (i.p. Software Manager, Printer Manager),
> actually the first ones I really prefer over unix style hacking.
>
Thanks :)
>
> Solved Problems (that might make it into the FAQ):
>
> [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?
> [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.
> [Solution:] Fortunately I have a floppy disk drive, and mcopy worked. So I
> could copy the kernel from /boot on the linux side to the MacOS side by
> floppy.
>
> [3] No devfsd running.
>
> [Solution:] 'devfsd=mount' needs to be in the kernel parameters on old-world
> machines. (Thanks to this list.)
>
Not specifically mentioned in the docs - should have been :(
> [4] wvdial can screw up your netconf ppp configuration.
>
> The internal modem is recognized and can be configured to dial into an ISP
> by netconf and /sbin/ifup ppp0. However, installing wvdial made this
> unusable: if wvdial is installed then netconf will use it (in
> /etc/ppp/peers/ppp0 `chat' ist replaced by a corresponding `wvdial' command
> that does not work properly on my machine.) It seems wvdialconf did not
> succeed in producing a working configuration file.
>
> [Solution:] deinstall wvdial, delete /etc/ppp/peers/pp0 and reconfigure in
> netconf. (Note that also the drake tool was failing in the presence of a
> `/etc/ppp/peers/ppp0' with wvdial because it essentially calls `/sbin/ifup
> ppp0')
>
I think most folks have been using kppp. I haven't really looked at
wvdial in a while.
>
> 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? Have you tried just minicom or tuning the serial
settings with setserial?
> [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?
> [3] I cannot get mol to run: white screen after the startboing.
> I have the -rw -boot flag set on my main MacOS partition and I
> use MacOS 8.6 with the ROM image from the MacOS ROM Update.
>
> [Attempts:]
> - used the kmods fitting the version of the kernel: did not help.
>
>
I get the same on my iMac, yet it works well on the powerbook. It did use
to work some time ago, in the LinuxPPC days. but that was many kernels/mol
versions ago. :(
Stew Benedict
--
MandrakeSoft
PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3
IRC: irc.openproject.net #cooker-ppc
