PCMCIA does not bring up eth1 during boot

[SimonWerner]

Problem:

After upgrading (apt-get dist-upgrade) from Breezy to Dapper my PCMCIA network card was no longer configured during boot. dmesg will report that a PCMCIA card is present in the slot, but it will not configure it. After manually ejecting the card and putting it back into the slot the PCMCIA card is detected, the network magic happens and eth1 is configured with an IP address (via DHCP). I am required to do this after every boot such that the network works properly. The same problem will occur if I the PC hibernates or is put to sleep.

Hardware:

- IBM ThinkPad R40 (has internal ethernet and is configured properly as eth0 at boot, but can not be used because it is physically damaged).

- PCMCIA card is a Xircom combo modem and ethernet card.

- ADSL modem connected to eth1 that assigns DHCP

Things I have tried:

- Running "dhcp eth1" after boot

- Turning off acpi in the kernel using boot flags

- Turning on acpi partially (using pci=noacpi)

- reinstalling/removing pcmciautils package

See the attached dmesg output for details.

See http://ubuntuforums.org/showthread.php?t=172687 for a call for help

[SimonWerner (simonwerner)]

[4294667.296000] Linux version 2.6.15-22-686 (buildd@vernadsky) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 SMP PREEMPT Sun May 7 16:37:57 UTC 2006
[4294667.296000] BIOS-provided physical RAM map:
[4294667.296000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
[4294667.296000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
[4294667.296000] BIOS-e820: 00000000000d2000 - 00000000000d4000 (reserved)
[4294667.296000] BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
[4294667.296000] BIOS-e820: 0000000000100000 - 000000001ff60000 (usable)
[4294667.296000] BIOS-e820: 000000001ff60000 - 000000001ff78000 (ACPI data)
[4294667.296000] BIOS-e820: 000000001ff78000 - 000000001ff7a000 (ACPI NVS)
[4294667.296000] BIOS-e820: 000000001ff80000 - 0000000020000000 (reserved)
[4294667.296000] BIOS-e820: 00000000ff800000 - 0000000100000000 (reserved)
[4294667.296000] 0MB HIGHMEM available.
[4294667.296000] 511MB LOWMEM available.
[4294667.296000] On node 0 totalpages: 130912
[4294667.296000] DMA zone: 4096 pages, LIFO batch:0
[4294667.296000] DMA32 zone: 0 pages, LIFO batch:0
[4294667.296000] Normal zone: 126816 pages, LIFO batch:31
[4294667.296000] HighMem zone: 0 pages, LIFO batch:0
[4294667.296000] DMI present.
[4294667.296000] ACPI: RSDP (v002 IBM ) @ 0x000f6d30
[4294667.296000] ACPI: XSDT (v001 IBM TP-1O 0x00001120 LTP 0x00000000) @ 0x1ff6ee35
[4294667.296000] ACPI: FADT (v003 IBM TP-1O 0x00001120 IBM 0x00000001) @ 0x1ff6ef00
[4294667.296000] ACPI: SSDT (v001 IBM TP-1O 0x00001120 MSFT 0x0100000e) @ 0x1ff6f0b4
[4294667.296000] ACPI: ECDT (v001 IBM TP-1O 0x00001120 IBM 0x00000001) @ 0x1ff77e54
[4294667.296000] ACPI: TCPA (v001 IBM TP-1O 0x00001120 PTL 0x00000001) @ 0x1ff77ea6
[4294667.296000] ACPI: BOOT (v001 IBM TP-1O 0x00001120 LTP 0x00000001) @ 0x1ff77fd8
[4294667.296000] ACPI: DSDT (v001 IBM TP-1O 0x00001120 MSFT 0x0100000e) @ 0x00000000
[4294667.296000] ACPI: PM-Timer IO Port: 0x1008
[4294667.296000] Allocating PCI resources starting at 30000000 (gap: 20000000:df800000)
[4294667.296000] Built 1 zonelists
[4294667.296000] Kernel command line: root=/dev/hda2 ro acpi=on apm=off quiet splash
[4294667.296000] Local APIC disabled by BIOS (or by default) -- you can enable it with "lapic"
[4294667.296000] mapped APIC to ffffd000 (014c1000)
[4294667.296000] Initializing CPU#0
[4294667.296000] PID hash table entries: 2048 (order: 11, 32768 bytes)
[4294667.296000] Detected 1595.379 MHz processor.
[4294667.296000] Using pmtmr for high-res timesource
[4294667.296000] Console: colour VGA+ 80x25
[4294669.047000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[4294669.048000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[4294669.065000] Memory: 507264k/523648k available (2093k kernel code, 15756k reserved, 589k data, 332k init, 0k highmem)
[4294669.065000] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[4294669.125000] Calibrating delay using timer specific routine.. 3199.94 BogoMIPS (lpj=1599971)
[4294669.125000] Security Framework v1.0....

[SimonWerner (simonwerner)]

This problem still exists in Edgy Eft Knot 3. It was not a problem in Breezy.

To get the PCMCIA to work properly I need to eject the card, either manually or via the commandline (e.g. "sudo pccardctl eject" then "sudo pccardctl insert").

[Tom Eisenmenger (teisenmenger)]

I'm having a similar problem - my ACX111 802.11g card is recognized just fine by Edgy but is not configured at boot. Unfortunately, even physically ejecting and reinserting the card doesn't activate it. Also tried it with an Orinoco card. Cards don't even power up.

[Philippe Escarbassière (phil-esc)]

I have a similar problem, the card need to be ejected and reinserted to be activated. However, if the card was not present during boot, it doesn't work at all...
The problem persists on feisty (kernel 2.6.20-3)

[SimonWerner (simonwerner)]

I am still having this problem with Feisty Fawn. I am still running "sudo pccardctl eject" then "sudo pccardctl insert" on boot. Except that now I also need to run 'dhcp eth0'.

I upgraded by installing from CD-ROM.

[SimonWerner (simonwerner)]

This problem has not changed in Gutsy Gibbon.

[TSloth (launchpad-jblack)]

This same problem occurs on Ubuntu 7.10 Gutsy Gibbon with Xircom RealPort REM56G-100 in a Dell Inspiron 4000 laptop. Most likely in Latitude C series laptops as well since they are virtually identical.

Physically ejecting the card and re-inserting it brings the network (eth0) up in seconds.

Also I have installed pcmcia-cs and can get it to work with
cardctl eject 0
cardctl insert 0
if these commands are executed via sudo

- TSloth

[Henrik Nilsen Omma (henrik)]

This will be retargeted towards the Hardy kernel once it is released. I've tagged this as "hardy-kernel-candidate" so that we make sure to retarget this report once the new release is out. However against the linux-source-2.6.22 package this is being marked as "Won't Fix" as it does not meet the criteria for a stable release update. To learn more about the stable release update process please refer to https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

[Leann Ogasawara (leannogasawara)]

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

[SimonWerner (simonwerner)]

This is still a problem in Hardy Heron Alpha2. I will attach my dmesg output.

[Philippe Escarbassière (phil-esc)]

The problem seems fixed with the 8 jan daily build (fresh install)
LAN works at startup automatically and it does even work if card is plugged after boot

[SimonWerner (simonwerner)]

This is still a problem for me on Hardy Heron Alpha3.

[Leann Ogasawara (leannogasawara)]

Thanks for testing and theupdate. Can you also attach your lspci -vvnn information? Thanks.

[SimonWerner (simonwerner)]

Here is my 'lspci -vvnn'

[SimonWerner (simonwerner)]

The above 'lspci -vvnn' is for Gusty Gibbon, are there any changes for Hardy Heron?

[Patrick Frey (patrick-frey)]

I have the same problem with 8.04, kernel 2.6.24-19-server
Xircom card does not work after boot, but after eject and reinsertion everything is ok.

[Patrick Frey (patrick-frey)]

The issue is not related to the Xircom card (at least not exclusively). I have the same problem with a Linksys WLAN adapter (WPC45G). Static assignment of IP-address does not help.
Syslog output from boot differs significantly from the output during insertion of the card. It seems to me. that udev rules are not triggered, because the 'kernel' does not detect the card correctly during boot.

BTW, the Xircom card is a multi-device card (LAN and modem device) and the modem is detected and configured during boot, but not the LAN.
The kernel module 'serial_cs' is loaded and bound to the device
The kernel module 'xirc2ps_cs' is loaded but not bound !?

Might the problem be related to udev ?

[Urmel (thorsten-seidel)]

I have the same problems with several PCMPIA cards on my HP 4150a Notebook running 8.10 (daily 20080823):
- The Xircom CreditCard Ethernet card version I works fine, version II doesn't (I tested 2 devices)
- The NETGEAR WG511v1 (WLAN) works fine, WG511v2 doesn't
- The NETGEAR WG511T works fine.

The Xircom cards worked fine with 7.04.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Jim Lieb (lieb)]

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04. To reopen the bug, click on the current status, under the Status column, and change the status back to "New". Thanks.

[kja002 (kja002)]

Same thing in Ubuntu 9.04, Xircom card is detected at boot, but no communication is done. After ejecting and inserting the card again, it is detected an communication starts, everything works.

[kernel-janitor (kernel-janitor)]

Hi SimonWerner,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 45295

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]