Each time I install a new kernel for Suse 9.1 I seem to get problems with detection of my PCMCIA network card at boot.
Here's the /var/log/boot.log output on kernel 2.6.13.4:
Code:
<notice>start services (network)
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
It's not possible to reject outgoing packets. Expect Timeouts.
Warning: /etc/resolv.conf not found
Warning: No interface active (yet?)ip6tables: No chain/target/match by that name
ip6tables: No chain/target/match by that name
ip6tables: No chain/target/match by that name
done eth-id-00:08:a1:6a:b2:83 No interface found
failedSetting up service network . . . . . . . . . . . . . . . .failed
<notice>exit status of (network) is (7)
The timeouts and
ip6tables warnings are not important (something to do with a patch that Suse is expecting). In kernel 2.6.12.3 the card loads okay, despite these warnings.
Here's the equivalent output from /var/log/messages:
Code:
Oct 24 17:36:11 linux kernel: Yenta: CardBus bridge found at 0000:00:0c.0 [0e11:b048]
Oct 24 17:36:11 linux kernel: Yenta: Enabling burst memory read transactions
Oct 24 17:36:11 linux kernel: Yenta: Using CSCINT to route CSC interrupts to PCI
Oct 24 17:36:11 linux kernel: Yenta: Routing CardBus interrupts to PCI
Oct 24 17:36:11 linux kernel: Yenta TI: socket 0000:00:0c.0, mfunc 0x00000000, devctl 0x64
Oct 24 17:36:11 linux kernel: Yenta: ISA IRQ mask 0x06d8, PCI irq 11
Oct 24 17:36:11 linux kernel: Socket status: 30000006
Oct 24 17:36:11 linux kernel: ACPI: PCI Interrupt 0000:00:0c.1[A] -> Link [C187] -> GSI 11 (level, low) -> IRQ 11
Oct 24 17:36:11 linux kernel: Yenta: CardBus bridge found at 0000:00:0c.1 [0e11:b048]
Oct 24 17:36:11 linux kernel: Yenta: Using CSCINT to route CSC interrupts to PCI
Oct 24 17:36:11 linux kernel: Yenta: Routing CardBus interrupts to PCI
Oct 24 17:36:11 linux kernel: Yenta TI: socket 0000:00:0c.1, mfunc 0x00000000, devctl 0x64
Oct 24 17:36:11 linux kernel: Yenta: ISA IRQ mask 0x06d8, PCI irq 11
Oct 24 17:36:11 linux kernel: Socket status: 30000020
[...]
Oct 24 17:38:50 linux kernel: 8139too Fast Ethernet driver 0.9.27
Oct 24 17:38:50 linux kernel: PCI: Enabling device 0000:06:00.0 (0000 -> 0003)
Oct 24 17:38:50 linux kernel: ACPI: PCI Interrupt 0000:06:00.0[A] -> Link [C187] -> GSI 11 (level, low) -> IRQ 11
Oct 24 17:38:50 linux kernel: PCI: Setting latency timer of device 0000:06:00.0 to 64
Oct 24 17:38:50 linux kernel: eth0: RealTek RTL8139 at 0xc8bec000, 00:08:a1:6a:b2:83, IRQ 11
Oct 24 17:38:50 linux kernel: eth0: Identified 8139 chip type 'RTL-8139C'
Oct 24 17:38:50 linux kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 24 17:38:51 linux kernel: NET: Registered protocol family 17
Oct 24 17:38:51 linux dhcpcd[13340]: broadcasting DHCP_DISCOVER
Oct 24 17:38:51 linux dhcpcd[13340]: dhcpIPaddrLeaseTime=21600 in DHCP server response.
Oct 24 17:38:51 linux dhcpcd[13340]: dhcpT1value is missing in DHCP server response. Assuming 10800 sec
Oct 24 17:38:51 linux dhcpcd[13340]: dhcpT2value is missing in DHCP server response. Assuming 18900 sec
Oct 24 17:38:51 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
Oct 24 17:38:53 linux SuSEfirewall2: Another SuSEfirewall2 with PID 13399 found, waiting ...
Oct 24 17:38:54 linux /etc/hotplug/net.agent[13254]: ip6tables: No chain/target/match by that name
Oct 24 17:38:54 linux last message repeated 2 times
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpIPaddrLeaseTime=21594 in DHCP server response.
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpT1value is missing in DHCP server response. Assuming 10797 sec
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpT2value is missing in DHCP server response. Assuming 18894 sec
Oct 24 17:38:55 linux dhcpcd[13340]: DHCP_OFFER received from (212.198.0.73)
Oct 24 17:38:55 linux dhcpcd[13340]: broadcasting DHCP_REQUEST for 81.67.26.244
Oct 24 17:38:55 linux kernel: SFW2-IN-ILL-TARGET IN=eth0 OUT= MAC=00:08:a1:6a:b2:83:00:30:b8:c2:cd:50:08:00 SRC=81.67.26.1 DST=81.67.26.244 LEN=361 TOS=0x00 PREC=0x00 TTL=255 ID=15994 PROTO=UDP SPT=67 DPT=68 LEN=341
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpIPaddrLeaseTime=21594 in DHCP server response.
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpT1value is missing in DHCP server response. Assuming 10797 sec
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpT2value is missing in DHCP server response. Assuming 18894 sec
Oct 24 17:38:55 linux dhcpcd[13340]: DHCP_ACK received from (212.198.0.73)
Oct 24 17:38:55 linux kernel: SFW2-IN-ILL-TARGET IN=eth0 OUT= MAC=00:08:a1:6a:b2:83:00:30:b8:c2:cd:50:08:00 SRC=81.67.26.1 DST=81.67.26.244 LEN=361 TOS=0x00 PREC=0x00 TTL=255 ID=16000 PROTO=UDP SPT=67 DPT=68 LEN=341
Oct 24 17:38:55 linux dhcpcd[13776]: terminating on signal 15
Oct 24 17:38:59 linux SuSEfirewall2: Firewall rules successfully set from /etc/sysconfig/SuSEfirewall2
Oct 24 17:39:00 linux kernel: eth0: no IPv6 routers present
So it looks like the network card is being detected, and yet network services fails. It must be a change I made to the kernel config, but which one?
The problem is solved with a
modprobe of the network card module. As a further clue, on shutdown I then get:
Code:
Shutting down service network
Shutting down PCMCIA cardmgr
FATAL: module yenta-socket is in use
FATAL: module pcmcia-core is in use
Advice appreciated.
Best kernel config to ensure PCMCIA network card detection?
