Re: Kernel 2.4.20 + PCMCIA not working (testing)
* Cesar Rincon <[EMAIL PROTECTED]> [2003 Jan 26 06:25 -0600]: > Weird. And of course you are using speed 115200, or at least 57600, in > your ppp configuration, right? (just ruling out common > misconfigurations). Check also for IRQ conflicts between your modem and > your NIC. Maybe they're being forced to share an interrupt, and one or > both do not like that. Yes, the speed is set to 115200. I have no other pcmcia card installed in the machine, just a Megahertz 56k PC Card modem. > IMO you'll miss 2.4 if you go back to 2.2, and you'll miss woody even > more, if you go back to potato. There should be no need for that. You're most likely right! > yenta is needed only for the *kernel* PCMCIA support. I don't use that > myself, I use a custom 2.4.18 kernel with modules from pcmcia_cs (that > is, I use i82365, not yenta_socket). With pcmcia-cs I also use i82365 and it's always worked great. I had a thought this morning of seeing if pcmcia-cs was available for the 2.4 series and apparently it is. I wonder if I should go with the kernel source from kernel.org or if the Debian patched source I have on the machine now would be "better". > What I do is get the kernel-source, pcmcia-source, and kernel-package > packages. Uncompress the PCMCIA tarball, so you end up with a "modules" > directory right under "/usr/src". Configure the kernel with no PCMCIA > support (that's right, disable it completely). Run the usual make-kpkg > kernel_image and, after that, a make-kpkg modules. You should probably > make the rest of the PCMCIA packages, as well, to avoid version problems > with the kernel. See the make-kpkg and pcmcia-source docs for details. I've given up on the kernel-package myself and have gone back to installing my custom built kernel by hand, as from my Slackware days. I had a fight with dselect once... > That should give you a pcmcia modules package, with modules from > pcmcia_cs, not from the kernel. Then you'll configure for i82365 again > and, if your problem is yenta, it should be gone. Thanks for the advice. The reminder is good as it's been some time (three years?) since I had performed the kernel install on that laptop. - Nate >> -- Wireless | Amateur Radio Station N0NB | "We have awakened a Internet | [EMAIL PROTECTED] | sleeping giant and Location | Bremen, Kansas USA EM19ov | have instilled in him Amateur radio exams; ham radio; Linux info @ | a terrible resolve". http://www.qsl.net/n0nb/ | - Admiral Yamamoto
Re: Kernel 2.4.20 + PCMCIA not working (testing)
* Cesar Rincon <[EMAIL PROTECTED]> [2003 Jan 26 06:25 -0600]: > Weird. And of course you are using speed 115200, or at least 57600, in > your ppp configuration, right? (just ruling out common > misconfigurations). Check also for IRQ conflicts between your modem and > your NIC. Maybe they're being forced to share an interrupt, and one or > both do not like that. Yes, the speed is set to 115200. I have no other pcmcia card installed in the machine, just a Megahertz 56k PC Card modem. > IMO you'll miss 2.4 if you go back to 2.2, and you'll miss woody even > more, if you go back to potato. There should be no need for that. You're most likely right! > yenta is needed only for the *kernel* PCMCIA support. I don't use that > myself, I use a custom 2.4.18 kernel with modules from pcmcia_cs (that > is, I use i82365, not yenta_socket). With pcmcia-cs I also use i82365 and it's always worked great. I had a thought this morning of seeing if pcmcia-cs was available for the 2.4 series and apparently it is. I wonder if I should go with the kernel source from kernel.org or if the Debian patched source I have on the machine now would be "better". > What I do is get the kernel-source, pcmcia-source, and kernel-package > packages. Uncompress the PCMCIA tarball, so you end up with a "modules" > directory right under "/usr/src". Configure the kernel with no PCMCIA > support (that's right, disable it completely). Run the usual make-kpkg > kernel_image and, after that, a make-kpkg modules. You should probably > make the rest of the PCMCIA packages, as well, to avoid version problems > with the kernel. See the make-kpkg and pcmcia-source docs for details. I've given up on the kernel-package myself and have gone back to installing my custom built kernel by hand, as from my Slackware days. I had a fight with dselect once... > That should give you a pcmcia modules package, with modules from > pcmcia_cs, not from the kernel. Then you'll configure for i82365 again > and, if your problem is yenta, it should be gone. Thanks for the advice. The reminder is good as it's been some time (three years?) since I had performed the kernel install on that laptop. - Nate >> -- Wireless | Amateur Radio Station N0NB | "We have awakened a Internet | [EMAIL PROTECTED] | sleeping giant and Location | Bremen, Kansas USA EM19ov | have instilled in him Amateur radio exams; ham radio; Linux info @ | a terrible resolve". http://www.qsl.net/n0nb/ | - Admiral Yamamoto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
On Sat, 2003-01-25 at 08:33, Nate Bargmann wrote: > First thanks to those of you who suggested the yenta_socket option. > That allowed both the Debian 2.4.20-586tsc and my own custom kernel to > load the card services modules. However, (there's always a caveat) the > throughput speed on the PCMCIA modem, which has worked very wery in all > the 2.2 kernels I've used, is very poor with rates less than 1000 B/s. Weird. And of course you are using speed 115200, or at least 57600, in your ppp configuration, right? (just ruling out common misconfigurations). Check also for IRQ conflicts between your modem and your NIC. Maybe they're being forced to share an interrupt, and one or both do not like that. > Booting the 2.2.20 Debian kernel from the Woody installation results in > normal transfer rates, however I must change /etc/default/pcmcia back to > i82365 as the rate with yenta_socket is poor. > > Thus I'm inclined to think that for some reason the yenta_socket code is > to blame, but I'm tired of fighting it. I have a working kernel plus > pcmcia-cs from a hard drive with Potato on it so I think I'll revert to > that. IMO you'll miss 2.4 if you go back to 2.2, and you'll miss woody even more, if you go back to potato. There should be no need for that. yenta is needed only for the *kernel* PCMCIA support. I don't use that myself, I use a custom 2.4.18 kernel with modules from pcmcia_cs (that is, I use i82365, not yenta_socket). What I do is get the kernel-source, pcmcia-source, and kernel-package packages. Uncompress the PCMCIA tarball, so you end up with a "modules" directory right under "/usr/src". Configure the kernel with no PCMCIA support (that's right, disable it completely). Run the usual make-kpkg kernel_image and, after that, a make-kpkg modules. You should probably make the rest of the PCMCIA packages, as well, to avoid version problems with the kernel. See the make-kpkg and pcmcia-source docs for details. That should give you a pcmcia modules package, with modules from pcmcia_cs, not from the kernel. Then you'll configure for i82365 again and, if your problem is yenta, it should be gone. Hope this helps. -CR
Re: Kernel 2.4.20 + PCMCIA not working (testing)
On Sat, 2003-01-25 at 08:33, Nate Bargmann wrote: > First thanks to those of you who suggested the yenta_socket option. > That allowed both the Debian 2.4.20-586tsc and my own custom kernel to > load the card services modules. However, (there's always a caveat) the > throughput speed on the PCMCIA modem, which has worked very wery in all > the 2.2 kernels I've used, is very poor with rates less than 1000 B/s. Weird. And of course you are using speed 115200, or at least 57600, in your ppp configuration, right? (just ruling out common misconfigurations). Check also for IRQ conflicts between your modem and your NIC. Maybe they're being forced to share an interrupt, and one or both do not like that. > Booting the 2.2.20 Debian kernel from the Woody installation results in > normal transfer rates, however I must change /etc/default/pcmcia back to > i82365 as the rate with yenta_socket is poor. > > Thus I'm inclined to think that for some reason the yenta_socket code is > to blame, but I'm tired of fighting it. I have a working kernel plus > pcmcia-cs from a hard drive with Potato on it so I think I'll revert to > that. IMO you'll miss 2.4 if you go back to 2.2, and you'll miss woody even more, if you go back to potato. There should be no need for that. yenta is needed only for the *kernel* PCMCIA support. I don't use that myself, I use a custom 2.4.18 kernel with modules from pcmcia_cs (that is, I use i82365, not yenta_socket). What I do is get the kernel-source, pcmcia-source, and kernel-package packages. Uncompress the PCMCIA tarball, so you end up with a "modules" directory right under "/usr/src". Configure the kernel with no PCMCIA support (that's right, disable it completely). Run the usual make-kpkg kernel_image and, after that, a make-kpkg modules. You should probably make the rest of the PCMCIA packages, as well, to avoid version problems with the kernel. See the make-kpkg and pcmcia-source docs for details. That should give you a pcmcia modules package, with modules from pcmcia_cs, not from the kernel. Then you'll configure for i82365 again and, if your problem is yenta, it should be gone. Hope this helps. -CR -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
First thanks to those of you who suggested the yenta_socket option. That allowed both the Debian 2.4.20-586tsc and my own custom kernel to load the card services modules. However, (there's always a caveat) the throughput speed on the PCMCIA modem, which has worked very wery in all the 2.2 kernels I've used, is very poor with rates less than 1000 B/s. Booting the 2.2.20 Debian kernel from the Woody installation results in normal transfer rates, however I must change /etc/default/pcmcia back to i82365 as the rate with yenta_socket is poor. Thus I'm inclined to think that for some reason the yenta_socket code is to blame, but I'm tired of fighting it. I have a working kernel plus pcmcia-cs from a hard drive with Potato on it so I think I'll revert to that. Thanks again for the help. - Nate >> -- Wireless | Amateur Radio Station N0NB | "We have awakened a Internet | [EMAIL PROTECTED] | sleeping giant and Location | Bremen, Kansas USA EM19ov | have instilled in him Amateur radio exams; ham radio; Linux info @ | a terrible resolve". http://www.qsl.net/n0nb/ | - Admiral Yamamoto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
First thanks to those of you who suggested the yenta_socket option. That allowed both the Debian 2.4.20-586tsc and my own custom kernel to load the card services modules. However, (there's always a caveat) the throughput speed on the PCMCIA modem, which has worked very wery in all the 2.2 kernels I've used, is very poor with rates less than 1000 B/s. Booting the 2.2.20 Debian kernel from the Woody installation results in normal transfer rates, however I must change /etc/default/pcmcia back to i82365 as the rate with yenta_socket is poor. Thus I'm inclined to think that for some reason the yenta_socket code is to blame, but I'm tired of fighting it. I have a working kernel plus pcmcia-cs from a hard drive with Potato on it so I think I'll revert to that. Thanks again for the help. - Nate >> -- Wireless | Amateur Radio Station N0NB | "We have awakened a Internet | [EMAIL PROTECTED] | sleeping giant and Location | Bremen, Kansas USA EM19ov | have instilled in him Amateur radio exams; ham radio; Linux info @ | a terrible resolve". http://www.qsl.net/n0nb/ | - Admiral Yamamoto
Re: Kernel 2.4.20 + PCMCIA not working (testing)
On Fri, Jan 24, 2003 at 06:14:39AM -0600, Nate Bargmann wrote: > * Ivar Alm <[EMAIL PROTECTED]> [2003 Jan 24 06:08 -0600]: > > At 01:35 2003-01-24, Nate Bargmann wrote: > > > Tried yenta_socket instead of pcmcia_cs? > > U, that's a new one on me. Is that a package or a configuration > option? tends to be a kernel module. hugh
Re: Kernel 2.4.20 + PCMCIA not working (testing)
* Cesar Rincon <[EMAIL PROTECTED]> [2003 Jan 24 17:05 -0600]: > It is a module. That (useful) piece of advice should be read: "try > yenta_socket instead of i82635". > > E.g., try > > PCIC="yenta_socket" > > in /etc/default/pcmcia > > As far as I remember, yenta is required in machines that would otherwise > use i82365, when using the standard Debian 2.4 kernel-image and > kernel-pcmcia-modules packages. Thanks CR. That did the trick. At least I can feel confident that 2.4.20 will support my hardware. I'll probably roll my own kernel anyway just to save disk space and memory bloat. - Nate >> -- Wireless | Amateur Radio Station N0NB | "We have awakened a Internet | [EMAIL PROTECTED] | sleeping giant and Location | Bremen, Kansas USA EM19ov | have instilled in him Amateur radio exams; ham radio; Linux info @ | a terrible resolve". http://www.qsl.net/n0nb/ | - Admiral Yamamoto
Re: Kernel 2.4.20 + PCMCIA not working (testing)
On Fri, Jan 24, 2003 at 06:14:39AM -0600, Nate Bargmann wrote: > * Ivar Alm <[EMAIL PROTECTED]> [2003 Jan 24 06:08 -0600]: > > At 01:35 2003-01-24, Nate Bargmann wrote: > > > Tried yenta_socket instead of pcmcia_cs? > > U, that's a new one on me. Is that a package or a configuration > option? tends to be a kernel module. hugh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
On Fri, 2003-01-24 at 06:14, Nate Bargmann wrote: > * Ivar Alm <[EMAIL PROTECTED]> [2003 Jan 24 06:08 -0600]: > > At 01:35 2003-01-24, Nate Bargmann wrote: > > > Tried yenta_socket instead of pcmcia_cs? > > U, that's a new one on me. Is that a package or a configuration > option? It is a module. That (useful) piece of advice should be read: "try yenta_socket instead of i82635". E.g., try PCIC="yenta_socket" in /etc/default/pcmcia As far as I remember, yenta is required in machines that would otherwise use i82365, when using the standard Debian 2.4 kernel-image and kernel-pcmcia-modules packages. -CR
Re: Kernel 2.4.20 + PCMCIA not working (testing)
* Cesar Rincon <[EMAIL PROTECTED]> [2003 Jan 24 17:05 -0600]: > It is a module. That (useful) piece of advice should be read: "try > yenta_socket instead of i82635". > > E.g., try > > PCIC="yenta_socket" > > in /etc/default/pcmcia > > As far as I remember, yenta is required in machines that would otherwise > use i82365, when using the standard Debian 2.4 kernel-image and > kernel-pcmcia-modules packages. Thanks CR. That did the trick. At least I can feel confident that 2.4.20 will support my hardware. I'll probably roll my own kernel anyway just to save disk space and memory bloat. - Nate >> -- Wireless | Amateur Radio Station N0NB | "We have awakened a Internet | [EMAIL PROTECTED] | sleeping giant and Location | Bremen, Kansas USA EM19ov | have instilled in him Amateur radio exams; ham radio; Linux info @ | a terrible resolve". http://www.qsl.net/n0nb/ | - Admiral Yamamoto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
On Fri, 2003-01-24 at 06:14, Nate Bargmann wrote: > * Ivar Alm <[EMAIL PROTECTED]> [2003 Jan 24 06:08 -0600]: > > At 01:35 2003-01-24, Nate Bargmann wrote: > > > Tried yenta_socket instead of pcmcia_cs? > > U, that's a new one on me. Is that a package or a configuration > option? It is a module. That (useful) piece of advice should be read: "try yenta_socket instead of i82635". E.g., try PCIC="yenta_socket" in /etc/default/pcmcia As far as I remember, yenta is required in machines that would otherwise use i82365, when using the standard Debian 2.4 kernel-image and kernel-pcmcia-modules packages. -CR -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
On Fri, 2003-01-24 at 02:11, iain d broadfoot wrote: > * Zak ([EMAIL PROTECTED]) wrote: > > I have compiled kernel 2.4.20 on Sid several times and never had pcmcia > > work. I haven't made any serious attempt at diagnosing this, but it does > > seem to be a problem with that versison of the kernel. > > hmm, i can't remember if mine worked prior to upgrading to 2.4.20 or > not... specificaly, i can't remember if i had the card before then. :D > > have you been enabling all the right things in the config? > > iain > > -- > wh33, y1p33 3tc. I'm the first to admit that I'm no expert on compiling kernels, but I have compiled a number of 2.4 kernels and never had a problem with pcmcia. I'm sure I have the right things enabled as I essentially reused the config from 2.4.18, in which pcmcia worked perfectly. I'm patiently waiting for 2.6. -- Zak <[EMAIL PROTECTED]>
Re: Kernel 2.4.20 + PCMCIA not working (testing)
On Fri, 2003-01-24 at 02:11, iain d broadfoot wrote: > * Zak ([EMAIL PROTECTED]) wrote: > > I have compiled kernel 2.4.20 on Sid several times and never had pcmcia > > work. I haven't made any serious attempt at diagnosing this, but it does > > seem to be a problem with that versison of the kernel. > > hmm, i can't remember if mine worked prior to upgrading to 2.4.20 or > not... specificaly, i can't remember if i had the card before then. :D > > have you been enabling all the right things in the config? > > iain > > -- > wh33, y1p33 3tc. I'm the first to admit that I'm no expert on compiling kernels, but I have compiled a number of 2.4 kernels and never had a problem with pcmcia. I'm sure I have the right things enabled as I essentially reused the config from 2.4.18, in which pcmcia worked perfectly. I'm patiently waiting for 2.6. -- Zak <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
iain d broadfoot wrote: > * Zak ([EMAIL PROTECTED]) wrote: > > I have compiled kernel 2.4.20 on Sid several times and never had pcmcia > > work. I haven't made any serious attempt at diagnosing this, but it does > > seem to be a problem with that versison of the kernel. > > hmm, i can't remember if mine worked prior to upgrading to 2.4.20 or > not... specificaly, i can't remember if i had the card before then. :D I use only kernel modules for PCMCIA (no pcmcia-cs-module package) and I have here 2.4.20 from kernel-sources and it works like a charm (using only Linksys 10/100 PC Card and Orinoco wireless Ethernet cards though). Have a nice day, Matej -- Matej Cepl, Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 I love deadlines. I like the whooshing sound they make as they fly by. -- Douglas Adams
Re: Kernel 2.4.20 + PCMCIA not working (testing)
"Nate" == Nate Bargmann <[EMAIL PROTECTED]> writes: Nate> Meanwhile booting 2.2.20 results in pcmcia-cs loading fine Nate> and recognizing the modem. An lsmod reveals that the Nate> pcmcia_core, i82365, ds, and serial_cs modules are loaded. Nate> Oddly, the reported version for Linux PCMCIA Card Services Nate> and cardmgr when using the 2.2.20 kernel is 3.1.33 which is Nate> newer than that in the 2.4.20 kernel! Nate> Has anyone solved this? Is a custom kernel necessary? Nate> Should I file a bug report? Try setting 'PCIC=yenta_socket' in /etc/default/pcmcia. Restart the cardmgr and see if that works. /Shyamal
Re: Kernel 2.4.20 + PCMCIA not working (testing)
iain d broadfoot wrote: > * Zak ([EMAIL PROTECTED]) wrote: > > I have compiled kernel 2.4.20 on Sid several times and never had pcmcia > > work. I haven't made any serious attempt at diagnosing this, but it does > > seem to be a problem with that versison of the kernel. > > hmm, i can't remember if mine worked prior to upgrading to 2.4.20 or > not... specificaly, i can't remember if i had the card before then. :D I use only kernel modules for PCMCIA (no pcmcia-cs-module package) and I have here 2.4.20 from kernel-sources and it works like a charm (using only Linksys 10/100 PC Card and Orinoco wireless Ethernet cards though). Have a nice day, Matej -- Matej Cepl, Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 I love deadlines. I like the whooshing sound they make as they fly by. -- Douglas Adams -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
"Nate" == Nate Bargmann <[EMAIL PROTECTED]> writes: Nate> Meanwhile booting 2.2.20 results in pcmcia-cs loading fine Nate> and recognizing the modem. An lsmod reveals that the Nate> pcmcia_core, i82365, ds, and serial_cs modules are loaded. Nate> Oddly, the reported version for Linux PCMCIA Card Services Nate> and cardmgr when using the 2.2.20 kernel is 3.1.33 which is Nate> newer than that in the 2.4.20 kernel! Nate> Has anyone solved this? Is a custom kernel necessary? Nate> Should I file a bug report? Try setting 'PCIC=yenta_socket' in /etc/default/pcmcia. Restart the cardmgr and see if that works. /Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
* Ivar Alm <[EMAIL PROTECTED]> [2003 Jan 24 06:08 -0600]: > At 01:35 2003-01-24, Nate Bargmann wrote: > Tried yenta_socket instead of pcmcia_cs? U, that's a new one on me. Is that a package or a configuration option? Thanks to everyone else for the replies. I generally build my own kernels for all my machines, so I may need to give that a try. - Nate >> -- Wireless | Amateur Radio Station N0NB | "We have awakened a Internet | [EMAIL PROTECTED] | sleeping giant and Location | Bremen, Kansas USA EM19ov | have instilled in him Amateur radio exams; ham radio; Linux info @ | a terrible resolve". http://www.qsl.net/n0nb/ | - Admiral Yamamoto
Re: Kernel 2.4.20 + PCMCIA not working (testing)
* Ivar Alm <[EMAIL PROTECTED]> [2003 Jan 24 06:08 -0600]: > At 01:35 2003-01-24, Nate Bargmann wrote: > Tried yenta_socket instead of pcmcia_cs? U, that's a new one on me. Is that a package or a configuration option? Thanks to everyone else for the replies. I generally build my own kernels for all my machines, so I may need to give that a try. - Nate >> -- Wireless | Amateur Radio Station N0NB | "We have awakened a Internet | [EMAIL PROTECTED] | sleeping giant and Location | Bremen, Kansas USA EM19ov | have instilled in him Amateur radio exams; ham radio; Linux info @ | a terrible resolve". http://www.qsl.net/n0nb/ | - Admiral Yamamoto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
At 01:35 2003-01-24, Nate Bargmann wrote: Hi All. I haven't found a great deal of help on this subject after Googling for a while. I've installed a base of Woody on a larger hard drive in my Thinkpad 760ED. The base install with kernel 2.2.20 and the pcmcia-cs modules worked flawlessly as it always had under Potato. Tried yenta_socket instead of pcmcia_cs? //I -- * Ivar Alm ! Where does Microsoft want to drag you today? ! Umeå, Sweden ! Do you really want to go there? ! [EMAIL PROTECTED] http://www.octofingers.com
Re: Kernel 2.4.20 + PCMCIA not working (testing)
At 01:35 2003-01-24, Nate Bargmann wrote: Hi All. I haven't found a great deal of help on this subject after Googling for a while. I've installed a base of Woody on a larger hard drive in my Thinkpad 760ED. The base install with kernel 2.2.20 and the pcmcia-cs modules worked flawlessly as it always had under Potato. Tried yenta_socket instead of pcmcia_cs? //I -- * Ivar Alm ! Where does Microsoft want to drag you today? ! Umeå, Sweden ! Do you really want to go there? ! [EMAIL PROTECTED] http://www.octofingers.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
* Zak ([EMAIL PROTECTED]) wrote: > I have compiled kernel 2.4.20 on Sid several times and never had pcmcia > work. I haven't made any serious attempt at diagnosing this, but it does > seem to be a problem with that versison of the kernel. hmm, i can't remember if mine worked prior to upgrading to 2.4.20 or not... specificaly, i can't remember if i had the card before then. :D have you been enabling all the right things in the config? iain -- wh33, y1p33 3tc.
Re: Kernel 2.4.20 + PCMCIA not working (testing)
I have compiled kernel 2.4.20 on Sid several times and never had pcmcia work. I haven't made any serious attempt at diagnosing this, but it does seem to be a problem with that versison of the kernel.
Re: Kernel 2.4.20 + PCMCIA not working (testing)
* Zak ([EMAIL PROTECTED]) wrote: > I have compiled kernel 2.4.20 on Sid several times and never had pcmcia > work. I haven't made any serious attempt at diagnosing this, but it does > seem to be a problem with that versison of the kernel. hmm, i can't remember if mine worked prior to upgrading to 2.4.20 or not... specificaly, i can't remember if i had the card before then. :D have you been enabling all the right things in the config? iain -- wh33, y1p33 3tc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
I have compiled kernel 2.4.20 on Sid several times and never had pcmcia work. I haven't made any serious attempt at diagnosing this, but it does seem to be a problem with that versison of the kernel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.4.20 + PCMCIA not working (testing)
* Nate Bargmann ([EMAIL PROTECTED]) wrote: > Has anyone solved this? Is a custom kernel necessary? Should I file a > bug report? try a custom kernel first (frankly, i'd recomend this for most laptop users anyway). iain -- wh33, y1p33 3tc.
Re: Kernel 2.4.20 + PCMCIA not working (testing)
* Nate Bargmann ([EMAIL PROTECTED]) wrote: > Has anyone solved this? Is a custom kernel necessary? Should I file a > bug report? try a custom kernel first (frankly, i'd recomend this for most laptop users anyway). iain -- wh33, y1p33 3tc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
