Sorry about the delay. I was swamped at work.
Conny Enström wrote:
----- Original Message -----
From: "Thomas Dodd" <[EMAIL PROTECTED]>
Maybe I can disable the serial to start at boot, but then it will effect
the built in serial ports?
You chould be abolt to try the modem with minicomm or the ppp tools.
Just select /dev/ttyS3 for the modem (not /dev/modem).
Also try booting without the card, then start the
above tail, insert the card, wait for it to configure,
then eject it. Send the section of all.log from
insertion to the hang on eject.
The output when I boot without the card and then insert it:
-----------
Oct 29 18:51:57 localhost cardmgr[581]: socket 1: Xircom CEM56
Ethernet/Modem
That says CEM56 not REM56G-100, but the CEM56-100 is also supported.
The driver may not detect the RealPort version as different.
It's not CardBus either, and is listed on the LinuxModems page.
Oct 29 18:51:57 localhost cardmgr[581]: executing: 'modprobe serial_cs'
loaded the serial port driver to interface with the modem.
Oct 29 18:51:58 localhost kernel: divert: allocating divert_blk for eth0
Oct 29 18:51:58 localhost /etc/hotplug/net.agent: invoke ifup eth0
ifup loads the driver and configures with DHCP
Oct 29 18:52:01 localhost kernel: eth0: MII link partner: 05e1
Oct 29 18:52:01 localhost kernel: eth0: MII selected
Oct 29 18:52:01 localhost cardmgr[581]: executing: './network start eth0'
Oct 29 18:52:01 localhost kernel: eth0: media 100BaseT, silicon revision 0
Oct 29 18:52:01 localhost kernel: eth0: Xircom: port 0x300, irq 3, hwaddr
00:10:A4:F9:0C:82
Oct 29 18:52:01 localhost kernel: ttyS3 at port 0x02e8 (irq = 3) is a 16550A
ttyS3 and eth0 are sharing IRQ3. You might want to check BIOS,
and make sure the built in serial ports aren't using IRQ3, or IO 0x02e8.
Oct 29 18:52:01 localhost kernel: eth0: MII link partner: 05e1
Oct 29 18:52:01 localhost kernel: eth0: MII selected
Oct 29 18:52:01 localhost kernel: eth0: media 100BaseT, silicon revision 0
Oct 29 18:52:01 localhost cardmgr[581]: executing: './serial start ttyS3'
Oct 29 18:52:11 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255
port 67
Oct 29 18:52:11 localhost dhclient: DHCPACK from 192.168.0.1
Oct 29 18:52:11 localhost dhclient: bound to 192.168.0.3 -- renewal in 98943
seconds.
Every thing looks good here.
And then I run 'cardctl eject 1'
------
Oct 29 19:14:34 dhcppc2 cardmgr[581]: executing: './network check eth0'
Oct 29 19:14:34 dhcppc2 cardmgr[581]: executing: './serial check ttyS3'
Oct 29 19:14:34 dhcppc2 cardmgr[581]: executing: './network stop eth0'
---------->Here everything freeze and I have to turn off the laptop
There should be and ifdown eth0 here.
The 'network stop eth0' line runs /etc/pcmcia/network
which is supposed to check for /etc/sysconfig/network-scripts/ifcfg-eth0
and call ifdown. Looking at the ones I have it would call
'/etc/sysconfig/network-scripts/ifdown ifcfg-eth0'.
I have initscripts-6.95-1 and kernel-pcmcia-cs-3.1.31-9.
Let's try this then.
Boot to runlevel 3.
Login as root
#/sbin/ifconfig
should report eth0 correctly
#/sbin/ifdown eth0
Does this hang as well?
What version of dhclient are you using?
-Thomas
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
