Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#531 - kernel updates brake pcmcia_cs

Attached to Project: Arch Linux
Opened by Pink Chick (Pink Chick) - Friday, 12 March 2004, 14:56 GMT
Last edited by Judd Vinet (judd) - Friday, 12 March 2004, 18:14 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

It happened while updating arch kernels from 2.4 to 2.6, to 2.6.1, to 2.6.3, to 2.6.4.

Whenever kernels are changed, you should consider to update the kernel depending packages, too, at least the ones that have to be compiled against the current kernel.

Everytime, I get my kernel updated, I find that my pcmcia_cs environment is broken. If you'd be so kind to think about:

- store kernel files wihth real numbers, so kernel26 update does not mean 2.6.3 files are overwritten with 2.6.4 files.
Therefore, it could be possible to stay with one kernel minor version.

- if kernel is to be updated, please recompile any depending kernel packages to match to the new kernel. Therefore, I suggest those packages should have a name relative to it's depending kernel versions, f.e. kernel2.6.4-pcmcia_cs, kernel-2.6.4-synaptics.

- if you won't consider any of my ideas, please think about a warning sign before kernels are updated. The kind "You want to update kernel26. Following packages will be broken due to unmatching kernel dependencies:
- pcmcia_cs
- ...
- ..."

:)
This task depends upon

Closed by  Judd Vinet (judd)
Wednesday, 14 April 2004, 17:43 GMT
Reason for closing:  Fixed
Comment by Judd Vinet (judd) - Friday, 12 March 2004, 18:17 GMT
Can you describe how it fails for you? I'm running the stock 2.6.4 on my laptop, and cardmgr appears to be working fine for me.
Comment by Pink Chick (Pink Chick) - Friday, 12 March 2004, 18:38 GMT
Cardmgr works, but finds no cards to handle.

Although my pcmcia_cs env was working with 2.6.3, the kernel update leaves my wifi card unrecognized.

I am not sure if it is the socket mod, or the pcmcia mods ...
Comment by Judd Vinet (judd) - Monday, 15 March 2004, 04:53 GMT
What pcmcia wifi module do you normally use?
Comment by Pink Chick (Pink Chick) - Monday, 15 March 2004, 08:15 GMT
I don't use a sophosticated wifi environment, just pcmcia_cs:
/etc/rc.conf:

modules=(orinoco_cs ...)
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo eth0 eth1)

DAEMONS=(... pcmcia network ...)

That's it. As the modules are loaded, pcmcia daemon solves the puzzle, and network daemon solves dhcp. The wifi is ready then.

It runs as long as I use the 2.6.3 kernel, and when I boot 2.6.4, my card is missbehaving. The modules are loaded, the pcmcia daemon recognizes the sockets, but the network daemon won't get the card up and therefore fetches no dhcp informations.
Comment by Judd Vinet (judd) - Sunday, 11 April 2004, 19:20 GMT
PCMCIA still works fine for me. Does 2.6.5 work for you?
Comment by Pink Chick (Pink Chick) - Wednesday, 14 April 2004, 13:19 GMT
Works again. I just tested on a fresh install. Seemed to be a 2.6.4 thing ... :)

Loading...