Re: PCMCIA problems on IBM ThinkPad 600X
Jeff Garzik wrote: > On Sun, 1 Apr 2001, Constantine Gavrilov wrote: > >> There are problems with some PCMCIA drivers included in the kernel. For >> example, support for cardbus 3com cards was moved to 3c59x.o driver. It >> works (on 600X at least) only of you compile it in. It will not work as >> a module. > > > It works just fine as a module. What problems are you seeing? > Exactly as reported by Anton. "cs: socket X timed out during reset" messages on the console when loading the module. This is at least on IBM Thinkpad 600X. 16-bit cards work fine. > >> I think a much better solution right now is to use drivers from >> pcmcia-cs package. It always works. If you do not configure any support >> for pcmcia in your kernel, when you build pcmcia-cs it will build kernel >> drivers from its own source tree. Just make sure you use the latest >> version. This also allows configuration files interoperbility with 2.2.x >> kernel, if you wish to use that as well. > > > pcmcia-cs does not always work, and it puts your nice 32-bit hardware > into 16-bit compatibility mode AFAIK. > > If you have 2.4 bugs, please report them instead of spewing B.S. > > Jeff > > Several points: * this bug and the workaround have been reported several times on several mailing lists, probably on linux-kernel as well. Explanations also stated that it has been broken and reported since 2.4.0-preX (I do not remember which pre-release). So it is not a hidden knowledge and I do not have to report a known bug. * I do not think pcmcia-cs puts cardbus cards into 16-bit compatibility mode. According to David Hinds, pcmcia code has been integrated into 2.4, so 2.4 uses a similar code base. My tests of bonding code showed 2 Mbit/sec with PCMCIA (100% CPU utilization) and 12 Mbit/sec with CardBus (<5% CPU utilization). * The letter has not been addressed to you, but to the list. Why are you taking this personal? What I said is no BS. The bug has been known and reported. I personally use multiple versions of 2.2.x and 2.4.x kernels installed on my machine for research and development. These include various experimental patches and pre-releases. For people in my situation, it is more convenient to use drivers from pcmcia-cs mainly for two reasons: 1) I can use the same PCMCIA configuration for all kernels; 2) I do not have to recompile kernel to upgrade PCMCIA drivers. Why should it bother you? David's stuff happens to work better right now. So what? There are several quite logical reasons for it: * PCMCIA code has been integrated relatively recently and not all integration problems have been solved yet. "Official" and "unofficial" Linux documentation state this and recommend pcmcia-cs in the case of problems. * Since 2.4 has come out, a lot of efforts are made to fix bugs. Some changes in the code incidentally break "other" stuff. Since David has to concentrate on PCMCIA only, he can respond quickly to fix integration problems. He is not bound to kernel release schedules and can release more frequently. In the current situation, it helps. * When you (or somebody else) update network drivers, you cannot possibly make sure that changes work across all card models. For David, on the other hand, it is by far much easier to insure compatibility, since he has to deal with CardBus and PCMCIA only. He also has had a lot of experince doing this and his releases have always being of high quality. So, you do not have to get angry. I did not reflect on the quality of your code and the thought has not even occurred to me. After all, if you update epro100 code, for instance, these changes appear in pcmcia-cs package rather quickly. Part of David's job has been to make sure that network drivers written in whole or in large part by other people work WELL with PCMCIA and CardBus cards. He has been doing an excellent job -- why should it bother you? -- Constantine Gavrilov Linux Leader Optibase Ltd 7 Shenkar St, Herzliya 46120, Israel Phone: (972-9)-970-9140 Fax: (972-9)-958-6099 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCMCIA problems on IBM ThinkPad 600X
On Sun, 1 Apr 2001, Constantine Gavrilov wrote: > There are problems with some PCMCIA drivers included in the kernel. For > example, support for cardbus 3com cards was moved to 3c59x.o driver. It > works (on 600X at least) only of you compile it in. It will not work as > a module. It works just fine as a module. What problems are you seeing? > I think a much better solution right now is to use drivers from > pcmcia-cs package. It always works. If you do not configure any support > for pcmcia in your kernel, when you build pcmcia-cs it will build kernel > drivers from its own source tree. Just make sure you use the latest > version. This also allows configuration files interoperbility with 2.2.x > kernel, if you wish to use that as well. pcmcia-cs does not always work, and it puts your nice 32-bit hardware into 16-bit compatibility mode AFAIK. If you have 2.4 bugs, please report them instead of spewing B.S. Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCMCIA problems on IBM ThinkPad 600X
There are problems with some PCMCIA drivers included in the kernel. For example, support for cardbus 3com cards was moved to 3c59x.o driver. It works (on 600X at least) only of you compile it in. It will not work as a module. I think a much better solution right now is to use drivers from pcmcia-cs package. It always works. If you do not configure any support for pcmcia in your kernel, when you build pcmcia-cs it will build kernel drivers from its own source tree. Just make sure you use the latest version. This also allows configuration files interoperbility with 2.2.x kernel, if you wish to use that as well. You just need to make sure you are using "ordinary" configuration files if you use pcmcia-cs, since 2.4 uses different names for some of pcmcia drivers. Stock pcmcia-cs package will do nicely. -- Constantine Gavrilov Linux Leader Optibase Ltd 7 Shenkar St, Herzliya 46120, Israel Phone: (972-9)-970-9140 Fax: (972-9)-958-6099 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PCMCIA problems on IBM ThinkPad 600X
On Fri, 30 Mar 2001, Anton Safonov wrote: > Hi! > > I have a problem with PCMCIA support on this IBM ThinkPad 600X. > > kernel - 2.4.2 + patch-2.4.3-pre4 > pcmcia-cs - 3.1.25 (also tried with 3.1.23) > > Then I insert a card (I'm trying now with two cards: 3COM 3CCFE575CT, > D-Link DFE-680TX) the computer beeps and responds with: > "cs: socket X timed out during reset" > > > kernel config file is following: > > # > # PCMCIA/CardBus support > # > CONFIG_PCMCIA=m > CONFIG_CARDBUS=y > CONFIG_I82365=y > CONFIG_TCIC=y If you have CardBus support, do -not- define CONFIG_I82365 or CONFIG_TCIC. Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PCMCIA problems on IBM ThinkPad 600X
Hi! I have a problem with PCMCIA support on this IBM ThinkPad 600X. kernel - 2.4.2 + patch-2.4.3-pre4 pcmcia-cs - 3.1.25 (also tried with 3.1.23) Then I insert a card (I'm trying now with two cards: 3COM 3CCFE575CT, D-Link DFE-680TX) the computer beeps and responds with: "cs: socket X timed out during reset" kernel config file is following: # # PCMCIA/CardBus support # CONFIG_PCMCIA=m CONFIG_CARDBUS=y CONFIG_I82365=y CONFIG_TCIC=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m CONFIG_PM=y # CONFIG_ACPI is not set CONFIG_APM=m # CONFIG_APM_IGNORE_USER_SUSPEND is not set # CONFIG_APM_DO_ENABLE is not set # CONFIG_APM_CPU_IDLE is not set # CONFIG_APM_DISPLAY_BLANK is not set # CONFIG_APM_RTC_IS_GMT is not set # CONFIG_APM_ALLOW_INTS is not set # CONFIG_APM_REAL_MODE_POWER_OFF is not set I have found from the kernel-traffic list some information that it could be because of wrong initalization of socket power (5V instead of 3.3V). But how it could be solved? Is there any ready patch or know-how available? PS. The same computer works perfectly with RedHat6.2 - kernel 2.2.1X (don't remember exact version). Best wishes! -- Mr. Anton Safonov [EMAIL PROTECTED] - tel.+372 56469626 SOT Finnish Software Engineering Ltd. - fax +372 6419975 Kreutzwaldi 7-4, 10124 TALLINN- http://www.sot.com/ ESTONIA - http://bestlinux.net/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
