iLamp/tibook modem

Carsten Milling yellowdog-general@lists.terrasoftsolutions.com
Tue Jul 23 09:09:00 2002


On Sun, Jul 21, 2002 at 04:24:51PM -0400, Stefan Bruda wrote:
> At 18:20 +0200 on 21-7-2002 Carsten Milling wrote:
>  >
>  > Ok, just to satisfy my curiosity, I tried to get the modem work again
>  > under my current setup (TiBook 400MHz, YDL 2.3 [with the 2.4.18 kernel
>  > of YDL 2.2]). Here is what I did:
> 
> Well, I had no luck with my modem. I am not sure whether this is a
> matter of hardware or configuration, but in case somebody is
> interested let me summarize what happens in my case.

[...]

> TiBook 667MHz (rev III, the one with resolution of 1280x854)
> YDL 2.2, but with kernel 2.4.19-rc1-ben0 and some other changes (none
>          relevant to this issue I believe)
> WvDial 1.41
> Qt: 2.3.2
> KDE: 2.2.2-2a
> KPPP: 2.0.9
> 
> Might it be that KPPP 3.something (the one you use) is smarter? I
> don't know, and I am reluctant to upgrade to KDE 3 since I do not use
> (or like for that matter) KDE anyway.

I don't think it's kppp. It rather looks like a kernel issue to
me. It's quite possible that your 2.4.19 ben kernel differs from my
2.4.18 stock YDL kernel in one way or the other ;). Here is what I
find in /var/log/messages when booting:

 kernel: macserial: i2c-modem detected, id: 1
 kernel: PowerMac Z8530 serial driver version 2.0
 kernel: ttyS0 at 0xd9af5020 (irq = 22) is a Z8530 ESCC (internal modem)
 kernel: ttyS1 at 0xd9afc000 (irq = 23) is a Z8530 ESCC (IrDA)

The other, less likely, chance is that the modem hardware changed
between the different TiBook revisions. Perhaps one of the hardware
experts on this list could say anything more precise here.

As for sleep, it almost works perfectly under my configuration (with
pmud-0.10-1b). There are some strange effects on the display when
waking up, but it disappears after a second or so and everything works
fine. The only problem I had was when the firewire modules were loaded
before going to sleep, after the wake up firewire was completely hosed
(could only get it work again with a reboot). As a workaround I umount
the firewire drives and unload the modules in /etc/power/pwctl-local.
Oh, I forgot, /etc/power/pwrctl was not executable after the standard
install and so was not executed by pmud. I did the obvious to fix
this.

Carsten