Good clue. Generally, I've found you do not want to use the serial.o
module, but only the mac_serial module. Then installer generally sets
this up in /etc/modules.conf. It looks like something is also trying to
insert the plain serial module. I played around with this a lot, testing
PCMCIA, and sometimes things would work with the serial module loaded too,
but I seemed to get the bet results with just mac_serial loaded. Check
/etc/modules.conf for:
alias serial mac_serial
Stew Benedict
--
MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/
On Sun, 24 Jun 2001, Dippy Black wrote:
> On Saturday 23 June 2001 11:45, you wrote:
> > Doesn't sound like you need to, based on your other response ;^)
> >
> > rpm -i minicom
> >
> > make sure /dev/modem is linked to your modem (typically /dev/ttyS0 on
> > Macs)
> >
> > minicom
> >
> > ATZ
> > ATDT some-phone-number
> >
> > CONNECT
> >
> >
> > Stew Benedict
>
> Okay, installed minicom. I configured it as you described up above. It seems
> to hang looking for the modem. I have been messing around with the problem
> some more trying to figure out exactly what is happening.
>
> I must use the Mandrake Control Center and reconfigure my internet settings
> each time and also I must choosed to attempt to connect from within it. If I
> just apply the settings and leave the app. I will still freeze when it looks
> for the modem. After doing this one time, i can connect in a normal manner
> with kppp. I also tried minicom. After having connected within mandrake
> conttrol center, minicom works fine as well. I checked the configs for
> minicom it does not change in any way.
>
> On one of my freezes I got this error message:
> Kwrited- listening on device /dev/pts/0
> message from syslogd@localhost at (gives date and time)
> localhost kernel: kernel panic : machine check
>
> Here is a copy of the syslog that I believe corresponds with the crash. I can
> also send you a copy of the syslog during the mandrake control center
> session. Or I can clear the log and get you a whole session. Hope this helps
> in some way.
>
> Jun 23 10:17:16 localhost init: Entering runlevel: 5
> Jun 23 10:17:17 localhost network: Setting network parameters: succeeded
> Jun 23 10:17:18 localhost network: Bringing up interface lo: succeeded
> Jun 23 10:17:21 localhost xfs: xfs startup succeeded
> Jun 23 10:17:22 localhost xfs: listening on port -1
> Jun 23 10:18:00 localhost CROND[742]: (root) CMD (
> /usr/share/msec/promisc_check.sh)
> Jun 23 10:18:05 localhost modprobe: modprobe: Can't locate module binfmt-0000
> Jun 23 10:18:05 localhost modprobe: modprobe: Can't locate module binfmt-0000
> Jun 23 10:18:46 localhost kernel: Serial driver version 4.27 with MANY_PORTS
> MULTIPORT SHARE_IRQ enabled
>