I agree. Under Debian, it is extremely easy to compile a kernel. One or two commands and then poof you have an installable debian package. Not really compiling, more like waiting then installing.
Robert
On Mon, 2006-01-09 at 15:53 -0500, Tom Alderman wrote:
On 1/9/06, giuliano <[EMAI
On 1/9/06, giuliano <[EMAIL PROTECTED]> wrote:
> On Sun, 8 Jan 2006 22:13:11 -0500
> golfer <[EMAIL PROTECTED]> wrote:
>
> >
> > Yes, this is a kernel problem. If you upgrade to 2.6.15 (build your
> > own using kernel-package), you can plug and unplug without problems.
>
> I have never compiled a
On Sun, 8 Jan 2006 22:13:11 -0500
golfer <[EMAIL PROTECTED]> wrote:
>
> Yes, this is a kernel problem. If you upgrade to 2.6.15 (build your
> own using kernel-package), you can plug and unplug without problems.
I have never compiled a kernel: I don't know if I am able to do it but perhaps
in t
On 12/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've a problem with pcmcia on my laptop (Hamlet Fe1500 net card): at boot the
> loading of pcmcia freezes the system (I renamed the S20pcmcia in /etc/rc2.s
> and /etc/rc3.d): the same happened when installation takes place, b
Hi all,
I've a problem with pcmcia on my laptop (Hamlet Fe1500 net card): at boot the
loading of pcmcia freezes the system (I renamed the S20pcmcia in /etc/rc2.s and
/etc/rc3.d): the same happened when installation takes place, but the insertion
of the card solved the problem : what is the diff
Ive just upgraded my laptop with linux 2.6.7 kernel using the debian
kernel-image, it boots up fine etc but when i plug in my pcmcia cards it
says:
"cs: unable to map card memory"
as such only one of my pcmcia slots work, if i try to slot anything in
the second pcmcia slot it gives the error abov
Ive just upgraded my laptop with linux 2.6.7 kernel using the debian
kernel-image, it boots up fine etc but when i plug in my pcmcia cards it
says:
"cs: unable to map card memory"
as such only one of my pcmcia slots work, if i try to slot anything in
the second pcmcia slot it gives the error abov
On Mon, 8 Mar 2004, Dennis Breithaupt wrote:
Hi,
I have a similar problem with 2.6.x kernels using my sitecom
wireless LAn cards. In this case (sitecom one using acx111 chipset) the
card is cardbus rather than PCMCIA card. To get the card recognised using
kernel 2.4.25 I compiled the kernel
On Mon, 8 Mar 2004, Dennis Breithaupt wrote:
Hi,
I have a similar problem with 2.6.x kernels using my sitecom
wireless LAn cards. In this case (sitecom one using acx111 chipset) the
card is cardbus rather than PCMCIA card. To get the card recognised using
kernel 2.4.25 I compiled the kernel
Hello,
I would greatly appreciate your help with the following problem:
My laptop is an Acer TravelMate 529ATXV, running debian/sarge - kernel
2.6.3.
I'm trying to install a NETGEAR WG511 802.11.a/b/g PCMCIA card. But it
seems, that cardmgr does not even recognize the physical installation o
Hello,
I would greatly appreciate your help with the following problem:
My laptop is an Acer TravelMate 529ATXV, running debian/sarge - kernel
2.6.3.
I'm trying to install a NETGEAR WG511 802.11.a/b/g PCMCIA card. But it
seems, that cardmgr does not even recognize the physical installation of
Am 20.12.03 17:40:53, schrieb "s. keeling" <[EMAIL PROTECTED]>:
>>
>> > Anyway I would like to know how do I do under
>> > debian "make cloneconfig" --> is it the same
>> > command under debian or a diffrent command?
>>
>> Isn't it "make oldconfig"? Copy your /boot/config-* to
>> /usr/src/linu
Am 20.12.03 17:40:53, schrieb "s. keeling" <[EMAIL PROTECTED]>:
>>
>> > Anyway I would like to know how do I do under
>> > debian "make cloneconfig" --> is it the same
>> > command under debian or a diffrent command?
>>
>> Isn't it "make oldconfig"? Copy your /boot/config-* to
>> /usr/src/linu
Incoming from s. keeling:
> Incoming from [EMAIL PROTECTED]:
> >
> > Am 18.12.03 22:09:18, schrieb "s. keeling" <[EMAIL PROTECTED]>:
> >
> > >Is yours a stock kernel? If so, what does:
> >
> > Please explain stock kernel!
>
> "Stock" means from Debian, in already compiled format, as compared t
Incoming from [EMAIL PROTECTED]:
>
> Am 18.12.03 22:09:18, schrieb "s. keeling" <[EMAIL PROTECTED]>:
>
> >Is yours a stock kernel? If so, what does:
>
> Please explain stock kernel!
"Stock" means from Debian, in already compiled format, as compared to
a kernel you built yourself.
> Anyway I w
Incoming from s. keeling:
> Incoming from [EMAIL PROTECTED]:
> >
> > Am 18.12.03 22:09:18, schrieb "s. keeling" <[EMAIL PROTECTED]>:
> >
> > >Is yours a stock kernel? If so, what does:
> >
> > Please explain stock kernel!
>
> "Stock" means from Debian, in already compiled format, as compared t
Incoming from [EMAIL PROTECTED]:
>
> Am 18.12.03 22:09:18, schrieb "s. keeling" <[EMAIL PROTECTED]>:
>
> >Is yours a stock kernel? If so, what does:
>
> Please explain stock kernel!
"Stock" means from Debian, in already compiled format, as compared to
a kernel you built yourself.
> Anyway I w
Am 18.12.03 22:09:18, schrieb "s. keeling" <[EMAIL PROTECTED]>:
>>
>> Well under /lib/modules/2.4.22/kernel/drivers/scsi
>> exist and is full of drivers, only the "aha152x_cs.o"
>> (is not "aha152x") dont exist in there.
>>
>> I compile and install pcmcia-cs-3.2.5.tar.gz but the
>> "aha152x_cs.
Am 18.12.03 22:09:18, schrieb "s. keeling" <[EMAIL PROTECTED]>:
>>
>> Well under /lib/modules/2.4.22/kernel/drivers/scsi
>> exist and is full of drivers, only the "aha152x_cs.o"
>> (is not "aha152x") dont exist in there.
>>
>> I compile and install pcmcia-cs-3.2.5.tar.gz but the
>> "aha152x_cs.
Incoming from [EMAIL PROTECTED]:
>
> The 16.12.03 20:06:14, wrote "s. keeling" <[EMAIL PROTECTED]>:
>
> >> But the 1460D dont recognise my scsi-hd
> >> because the module aha152x_cs.o for
> >> the 1460D won´t load?!
> >
> >Define "won't load"; what are the error messages? What is the
>
> Sorry
Incoming from [EMAIL PROTECTED]:
>
> The 16.12.03 20:06:14, wrote "s. keeling" <[EMAIL PROTECTED]>:
>
> >> But the 1460D dont recognise my scsi-hd
> >> because the module aha152x_cs.o for
> >> the 1460D won´t load?!
> >
> >Define "won't load"; what are the error messages? What is the
>
> Sorry
The 16.12.03 20:06:14, wrote "s. keeling" <[EMAIL PROTECTED]>:
>>
>> Who can tell me whats wrong with my
>> request below, because no body answer
>>
>> But the 1460D dont recognise my scsi-hd
>> because the module aha152x_cs.o for
>> the 1460D won´t load?!
>
>Define "won't load"; what are the e
The 16.12.03 20:06:14, wrote "s. keeling" <[EMAIL PROTECTED]>:
>>
>> Who can tell me whats wrong with my
>> request below, because no body answer
>>
>> But the 1460D dont recognise my scsi-hd
>> because the module aha152x_cs.o for
>> the 1460D won´t load?!
>
>Define "won't load"; what are the e
Incoming from [EMAIL PROTECTED]:
>
> Who can tell me whats wrong with my
> request below, because no body answer
>
> But the 1460D dont recognise my scsi-hd
> because the module aha152x_cs.o for
> the 1460D won´t load?!
Define "won't load"; what are the error messages? What is the
filesystem ty
Greetings to the members of this list,
Who can tell me whats wrong with my
request below, because no body answer
to it ??
I need some help with:
Notbook: Dell Inspiron 8000
System: Woddy 3.0.1
The pcmcia configures normal ok.
I use the adaptek slim-scsi 1460D.
But the 1460D dont recognise my
Incoming from [EMAIL PROTECTED]:
>
> Who can tell me whats wrong with my
> request below, because no body answer
>
> But the 1460D dont recognise my scsi-hd
> because the module aha152x_cs.o for
> the 1460D won´t load?!
Define "won't load"; what are the error messages? What is the
filesystem ty
Greetings to the members of this list,
Who can tell me whats wrong with my
request below, because no body answer
to it ??
I need some help with:
Notbook: Dell Inspiron 8000
System: Woddy 3.0.1
The pcmcia configures normal ok.
I use the adaptek slim-scsi 1460D.
But the 1460D dont recognise my
Greetings to the members of this list,
I need some help with:
Notbook: Dell Inspiron 8000
System: Woddy 3.0.1
The pcmcia configures normal ok.
I use the adaptek slim-scsi 1460D.
But the 1460D dont recognise my scsi-hd
because the module aha152x_cs.o for
the 1460D won´t load?!
exclude port 0x800
Greetings to the members of this list,
I need some help with:
Notbook: Dell Inspiron 8000
System: Woddy 3.0.1
The pcmcia configures normal ok.
I use the adaptek slim-scsi 1460D.
But the 1460D dont recognise my scsi-hd
because the module aha152x_cs.o for
the 1460D won´t load?!
exclude port 0x800
Greetings to the members of this list,
I need some help with:
Notbbok: Dell Inspiron 8000
System: Woddy 3.1
The pcmcia configures normal ok.
I use the adaptek slim-scsi 1460D.
But the 1460D dont recognise my scsi-hd.
exclude port 0x800-0x8ff is done!
Under SuSE 8.2 it works without problems!
Greetings to the members of this list,
I need some help with:
Notbbok: Dell Inspiron 8000
System: Woddy 3.1
The pcmcia configures normal ok.
I use the adaptek slim-scsi 1460D.
But the 1460D dont recognise my scsi-hd.
exclude port 0x800-0x8ff is done!
Under SuSE 8.2 it works without problems!
I didnt get anything out of that site but thanks
anyway, the pcmcia card holder is a "Texas Instruments PCI1131" and the network
card in it is called "Xicom RealPort Ethernet 10/100+Modem 56" so i need drivers
that is possible to install during the debian installation progress for both
these
I didnt get anything out of that site but thanks
anyway, the pcmcia card holder is a "Texas Instruments PCI1131" and the network
card in it is called "Xicom RealPort Ethernet 10/100+Modem 56" so i need drivers
that is possible to install during the debian installation progress for both
these
Jon Lachmann, 2003-Aug-28 07:35 +0200:
> I got a Dell Latitude CPi laptop, and i'm trying to install debian
on it, but i get stuck on the installation of my PCMCIA card holder
(internal) and it says something like "Could not install modules for
PCMCIA" i have no idea of what the pcmcia-card-
I got a Dell Latitude CPi laptop, and i'm trying to install debian on it, but i get
stuck on the installation of my PCMCIA card holder (internal) and it says something
like "Could not install modules for PCMCIA" i have no idea of what the
pcmcia-card-holder is called, but i shoose the intel one
Jon Lachmann, 2003-Aug-28 07:35 +0200:
> I got a Dell Latitude CPi laptop, and i'm trying to install debian
on it, but i get stuck on the installation of my PCMCIA card holder
(internal) and it says something like "Could not install modules for
PCMCIA" i have no idea of what the pcmcia-card-
I got a Dell Latitude CPi laptop, and i'm trying to install debian on it, but i
get stuck on the installation of my PCMCIA card holder (internal) and it says
something like "Could not install modules for PCMCIA" i have no idea of what
the pcmcia-card-holder is called, but i shoose the intel one
Hi!
I've used a EagleTec PCMCIA modem for a while. It worked with 2.4.20 and now
I want to use it with 2.5, but I have some problems with it:
Mar 15 18:44:21 exodus cardmgr[1325]: watching 2 sockets
Mar 15 18:44:21 exodus cardmgr[1326]: starting, version is 3.2.2
Mar 15 18:44:27 exodus cardmgr[13
Hi!
I've used a EagleTec PCMCIA modem for a while. It worked with 2.4.20 and now
I want to use it with 2.5, but I have some problems with it:
Mar 15 18:44:21 exodus cardmgr[1325]: watching 2 sockets
Mar 15 18:44:21 exodus cardmgr[1326]: starting, version is 3.2.2
Mar 15 18:44:27 exodus cardmgr[13
Thanks to Derek and Neal for the fix. Changing to PCIC=yenta_socket
fixed the problem and the card is working again now. Thanks to you
both.
To answer Derek's question:
--- Derek Broughton <[EMAIL PROTECTED]> wrote:
> > I read where the new pcmcia required hotplug, so I installed the
> > hotplug
Thanks to Derek and Neal for the fix. Changing to PCIC=yenta_socket
fixed the problem and the card is working again now. Thanks to you
both.
To answer Derek's question:
--- Derek Broughton <[EMAIL PROTECTED]> wrote:
> > I read where the new pcmcia required hotplug, so I installed the
> > hotplug
> My pcmcia network card stopped working when I upgraded from kernel
> 2.2.20 to 2.4.19. I upgraded the kernel by apt-get install:
> kernel-image-2.4.19-686
> kernel-pcmcia-modules-2.4.19-686
>
> I read where the new pcmcia required hotplug, so I installed the
> hotplug package but it still does n
My pcmcia network card stopped working when I upgraded from kernel
2.2.20 to 2.4.19. I upgraded the kernel by apt-get install:
kernel-image-2.4.19-686
kernel-pcmcia-modules-2.4.19-686
I read where the new pcmcia required hotplug, so I installed the
hotplug package but it still does not work.
I am
> My pcmcia network card stopped working when I upgraded from kernel
> 2.2.20 to 2.4.19. I upgraded the kernel by apt-get install:
> kernel-image-2.4.19-686
> kernel-pcmcia-modules-2.4.19-686
>
> I read where the new pcmcia required hotplug, so I installed the
> hotplug package but it still does n
My pcmcia network card stopped working when I upgraded from kernel
2.2.20 to 2.4.19. I upgraded the kernel by apt-get install:
kernel-image-2.4.19-686
kernel-pcmcia-modules-2.4.19-686
I read where the new pcmcia required hotplug, so I installed the
hotplug package but it still does not work.
I am
Hi,
I have some problems with my PCMCIA network card (W-LINX LinxPro) in
a Toshiba Satellite Pro 480CDT laptop. My distribution is Debian 3.0 (but
still Kernel 2.2.17) with pcmcia-cs-3.1.33 (source package from sourceforge,
not .deb):
- When I stop the card services and start them afterwards, I
Hi,
I have some problems with my PCMCIA network card (W-LINX LinxPro) in
a Toshiba Satellite Pro 480CDT laptop. My distribution is Debian 3.0 (but
still Kernel 2.2.17) with pcmcia-cs-3.1.33 (source package from sourceforge,
not .deb):
- When I stop the card services and start them afterwards,
Heather <[EMAIL PROTECTED]> wrote:
> I don't think orinoco cards can be classed as either rare or crappy
> - but their module has definitely changed names, and *that* was
> dependent on the kernel rev.
Apples ... oranges. I was *not* talking about orinoco cards.
However, since you have brought
> > > or laptops. Examples of these special cases can be found in
> > > /usr/share/doc/pcmcia-cs/config.opts.gz.
>
> To which Heather <[EMAIL PROTECTED]> commented:
>
> > Is it me, or does "only a few cases will need hand hacking" sound like
> > it *does not satisfy* "folks with any kernel-image
Heather <[EMAIL PROTECTED]> wrote:
> I don't think orinoco cards can be classed as either rare or crappy
> - but their module has definitely changed names, and *that* was
> dependent on the kernel rev.
Apples ... oranges. I was *not* talking about orinoco cards.
However, since you have brought
> > > or laptops. Examples of these special cases can be found in
> > > /usr/share/doc/pcmcia-cs/config.opts.gz.
>
> To which Heather <[EMAIL PROTECTED]> commented:
>
> > Is it me, or does "only a few cases will need hand hacking" sound like
> > it *does not satisfy* "folks with any kernel-imag
Tom Allison <[EMAIL PROTECTED]> wrote:
> I have managed to get this working with 3.1.31-7. However, my kernel
> drivers are selected for a driver 'orinoco' while the pcmcia package
> based drivers are wlan_cs. The wlan_cs drivers are the older drivers
> for the D-Link DWL-650 and are being repla
Tom Allison <[EMAIL PROTECTED]> wrote:
> I have managed to get this working with 3.1.31-7. However, my kernel
> drivers are selected for a driver 'orinoco' while the pcmcia package
> based drivers are wlan_cs. The wlan_cs drivers are the older drivers
> for the D-Link DWL-650 and are being repl
Brian Mays wrote:
Heather <[EMAIL PROTECTED]> wrote:
[symlinks bug in kernel-image-* ellided] Well, since the dev gang are
aware of this I'm sure kernel-image-2.4.18-* will be fixed when they
happen.
They should be. If not, complain to Herbert Xu.
Brian Mays wrote:
Try version 3.1.31-7
Brian Mays wrote:
> Heather <[EMAIL PROTECTED]> wrote:
>
>
>>[symlinks bug in kernel-image-* ellided] Well, since the dev gang are
>>aware of this I'm sure kernel-image-2.4.18-* will be fixed when they
>>happen.
>>
>
> They should be. If not, complain to Herbert Xu.
>
> Brian Mays wrote:
>
>
Heather <[EMAIL PROTECTED]> wrote:
> [symlinks bug in kernel-image-* ellided] Well, since the dev gang are
> aware of this I'm sure kernel-image-2.4.18-* will be fixed when they
> happen.
They should be. If not, complain to Herbert Xu.
Brian Mays wrote:
> > Try version 3.1.31-7. The only "han
> Heather <[EMAIL PROTECTED]> replied:
>
> > When the names of modules that are used by some -cards- changed
> > between 2.2 and 2.4, and (gasp) if they're different between David
> > Hind's external modules or Linus' internal ones, then yes, it
> > certainly -is- going to bother pcmcia-cs. The c
Heather <[EMAIL PROTECTED]> wrote:
> [symlinks bug in kernel-image-* ellided] Well, since the dev gang are
> aware of this I'm sure kernel-image-2.4.18-* will be fixed when they
> happen.
They should be. If not, complain to Herbert Xu.
Brian Mays wrote:
> > Try version 3.1.31-7. The only "ha
> Heather <[EMAIL PROTECTED]> replied:
>
> > When the names of modules that are used by some -cards- changed
> > between 2.2 and 2.4, and (gasp) if they're different between David
> > Hind's external modules or Linus' internal ones, then yes, it
> > certainly -is- going to bother pcmcia-cs. The
Brian Mays wrote:
> > I just checked to refresh my memory on the problem that you are
> > discussing. If you are using the 2.4 kernel drivers, then you do
> > not need to install (or even build) a pcmcia-modules-2.4.18 package.
> > This is the package that had the conflicts with the kernel-image
> I just checked to refresh my memory on the problem that you are
> discussing. If you are using the 2.4 kernel drivers, then you do not need
> to install (or even build) a pcmcia-modules-2.4.18 package. This is the
> package that had the conflicts with the kernel-image package. Since you
>
Brian Mays wrote:
> > I just checked to refresh my memory on the problem that you are
> > discussing. If you are using the 2.4 kernel drivers, then you do
> > not need to install (or even build) a pcmcia-modules-2.4.18 package.
> > This is the package that had the conflicts with the kernel-image
> I just checked to refresh my memory on the problem that you are
> discussing. If you are using the 2.4 kernel drivers, then you do not need
> to install (or even build) a pcmcia-modules-2.4.18 package. This is the
> package that had the conflicts with the kernel-image package. Since you
>
Tom Allison <[EMAIL PROTECTED]> wrote:
> I upgrade pcmcia-cs to pull in the newer applications (cardctl
> v3.1.31) and in that process ended up with this problem.
>
> In the past 2.4.xx kernels I have been using the kernel supplied
> drivers for my network cards. Is it safe to assume that the
Tom Allison <[EMAIL PROTECTED]> wrote:
> I upgrade pcmcia-cs to pull in the newer applications (cardctl
> v3.1.31) and in that process ended up with this problem.
>
> In the past 2.4.xx kernels I have been using the kernel supplied
> drivers for my network cards. Is it safe to assume that the
Brian Mays wrote:
Tom Allison <[EMAIL PROTECTED]> asked:
QUESTION: If I were to use the kernel from ftp.kernel.org and then
run a make-kpkg, would I see this same problem?
It depends. If you are using the 2.4 kernel drivers (i.e., you have
turned on the CONFIG_PCMCIA option) then you woul
Brian Mays wrote:
> Tom Allison <[EMAIL PROTECTED]> asked:
>
>
>>QUESTION: If I were to use the kernel from ftp.kernel.org and then
>>run a make-kpkg, would I see this same problem?
>>
>
> It depends. If you are using the 2.4 kernel drivers (i.e., you have
> turned on the CONFIG_PCMCIA option
Tom Allison <[EMAIL PROTECTED]> asked:
> QUESTION: If I were to use the kernel from ftp.kernel.org and then
> run a make-kpkg, would I see this same problem?
It depends. If you are using the 2.4 kernel drivers (i.e., you have
turned on the CONFIG_PCMCIA option) then you would not experience the
On Sun, Feb 17, 2002 at 02:17:35PM -0500, Michael Stone wrote:
> On Sun, Feb 17, 2002 at 08:23:26AM -0500, Pann McCuaig wrote:
> > I had a similar problem. I turned off all PCMCIA support in the kernel.
> > I don't know why it's there in the first place (seems to be new with
> > 2.4.x).
>
> Well,
Tom Allison <[EMAIL PROTECTED]> asked:
> QUESTION: If I were to use the kernel from ftp.kernel.org and then
> run a make-kpkg, would I see this same problem?
It depends. If you are using the 2.4 kernel drivers (i.e., you have
turned on the CONFIG_PCMCIA option) then you would not experience th
Brian Mays wrote:
Tom Allison <[EMAIL PROTECTED]> wrote:
But I built my own pcmcia-modules package and kernel-image package
from the 2.4.17 kernel-source and 3.1.36 pcmcia-source. You mean that
these are still building bad links?
Not the pcmcia source. The kernel source is building the b
On Sun, Feb 17, 2002 at 02:17:35PM -0500, Michael Stone wrote:
> On Sun, Feb 17, 2002 at 08:23:26AM -0500, Pann McCuaig wrote:
> > I had a similar problem. I turned off all PCMCIA support in the kernel.
> > I don't know why it's there in the first place (seems to be new with
> > 2.4.x).
>
> Well,
Brian Mays wrote:
> Tom Allison <[EMAIL PROTECTED]> wrote:
>
>
>>But I built my own pcmcia-modules package and kernel-image package
>>from the 2.4.17 kernel-source and 3.1.36 pcmcia-source. You mean that
>>these are still building bad links?
>>
>
> Not the pcmcia source. The kernel source is
On Sun, Feb 17, 2002 at 08:23:26AM -0500, Pann McCuaig wrote:
> I had a similar problem. I turned off all PCMCIA support in the kernel.
> I don't know why it's there in the first place (seems to be new with
> 2.4.x).
Well, I've got some machines that only work with the kernel pcmcia
drivers and so
Tom Allison <[EMAIL PROTECTED]> wrote:
> But I built my own pcmcia-modules package and kernel-image package
> from the 2.4.17 kernel-source and 3.1.36 pcmcia-source. You mean that
> these are still building bad links?
Not the pcmcia source. The kernel source is building the bad links,
and there
On Sun, Feb 17, 2002 at 08:23:26AM -0500, Pann McCuaig wrote:
> I had a similar problem. I turned off all PCMCIA support in the kernel.
> I don't know why it's there in the first place (seems to be new with
> 2.4.x).
Well, I've got some machines that only work with the kernel pcmcia
drivers and s
Brian Mays wrote:
[EMAIL PROTECTED] (Tom Allison) wrote:
I have built a kernel and modules images and have tried to install
them both. I have to do a dpkp -i --force-overwrite in order to get
them to install. The error is related to a duplicate of pcmcia_core
modules.
It's not a dupli
Pann McCuaig wrote:
> I had a similar problem. I turned off all PCMCIA support in the
> kernel. I don't know why it's there in the first place (seems to be
> new with 2.4.x).
The 2.4 kernels have introduced their own PCMCIA drivers. Now there are
two sets of drivers, the 2.4 kernel drivers, and
[EMAIL PROTECTED] (Tom Allison) wrote:
> I have built a kernel and modules images and have tried to install
> them both. I have to do a dpkp -i --force-overwrite in order to get
> them to install. The error is related to a duplicate of pcmcia_core
> modules.
It's not a duplicate of the modul
Pann McCuaig wrote:
On Sat, Feb 16, 2002 at 23:13, Tom Allison wrote:
Has anyone else noticed that the kernel-source for 2.4.17 and the
pcmcia-source for 3.1.31 are not playing well with each other?
I have found that the 2.4.17 orinoco driver (driver/net/wireless/) is
version 08a and the pc
Tom Allison <[EMAIL PROTECTED]> wrote:
> But I built my own pcmcia-modules package and kernel-image package
> from the 2.4.17 kernel-source and 3.1.36 pcmcia-source. You mean that
> these are still building bad links?
Not the pcmcia source. The kernel source is building the bad links,
and ther
Brian Mays wrote:
> [EMAIL PROTECTED] (Tom Allison) wrote:
>
>
>>I have built a kernel and modules images and have tried to install
>>them both. I have to do a dpkp -i --force-overwrite in order to get
>>them to install. The error is related to a duplicate of pcmcia_core
>>modules.
>>
>
>
Pann McCuaig wrote:
> I had a similar problem. I turned off all PCMCIA support in the
> kernel. I don't know why it's there in the first place (seems to be
> new with 2.4.x).
The 2.4 kernels have introduced their own PCMCIA drivers. Now there are
two sets of drivers, the 2.4 kernel drivers, an
[EMAIL PROTECTED] (Tom Allison) wrote:
> I have built a kernel and modules images and have tried to install
> them both. I have to do a dpkp -i --force-overwrite in order to get
> them to install. The error is related to a duplicate of pcmcia_core
> modules.
It's not a duplicate of the modu
On Sat, Feb 16, 2002 at 23:13, Tom Allison wrote:
> Has anyone else noticed that the kernel-source for 2.4.17 and the
> pcmcia-source for 3.1.31 are not playing well with each other?
>
> I have found that the 2.4.17 orinoco driver (driver/net/wireless/) is
> version 08a and the pcmcia 3.1.31 ori
Pann McCuaig wrote:
> On Sat, Feb 16, 2002 at 23:13, Tom Allison wrote:
>
>>Has anyone else noticed that the kernel-source for 2.4.17 and the
>>pcmcia-source for 3.1.31 are not playing well with each other?
>>
>>I have found that the 2.4.17 orinoco driver (driver/net/wireless/) is
>>version 08
On Sat, Feb 16, 2002 at 23:13, Tom Allison wrote:
> Has anyone else noticed that the kernel-source for 2.4.17 and the
> pcmcia-source for 3.1.31 are not playing well with each other?
>
> I have found that the 2.4.17 orinoco driver (driver/net/wireless/) is
> version 08a and the pcmcia 3.1.31 or
Has anyone else noticed that the kernel-source for 2.4.17 and the
pcmcia-source for 3.1.31 are not playing well with each other?
I have found that the 2.4.17 orinoco driver (driver/net/wireless/) is
version 08a and the pcmcia 3.1.31 orinoco driver is at version 08
(from /usr/src/modules/pcmcia
Has anyone else noticed that the kernel-source for 2.4.17 and the
pcmcia-source for 3.1.31 are not playing well with each other?
I have found that the 2.4.17 orinoco driver (driver/net/wireless/) is
version 08a and the pcmcia 3.1.31 orinoco driver is at version 08
(from /usr/src/modules/pcmcia
> Sounds like your card is recognised as being some sort of PCNET variant,
> but you will need to build a "binary-modules" target from the 3.1.25
> source. The pcmcia-cs source will build either or both packages for you
> - take a look at the debian/rules file for what targets are valid. From
>
> Sounds like your card is recognised as being some sort of PCNET variant,
> but you will need to build a "binary-modules" target from the 3.1.25
> source. The pcmcia-cs source will build either or both packages for you
> - take a look at the debian/rules file for what targets are valid. Fro
Robert Voigt wrote:
>
> > pcnet_cs: sorry, the AX88190 chipset is not supported.
> > pcnet_cs: unable to read hardware net address for io
> > base 0x300
>
> I have the same problem, I'm getting this same message.
> I have a W-Linx Linx Pro 10/100 Card. It's listed as supported in the
> pcmcia-
> pcnet_cs: sorry, the AX88190 chipset is not supported.
> pcnet_cs: unable to read hardware net address for io
> base 0x300
I have the same problem, I'm getting this same message.
I have a W-Linx Linx Pro 10/100 Card. It's listed as supported in the
pcmcia-cs-3.1.25 list of supported cards, but
Robert Voigt wrote:
>
> > pcnet_cs: sorry, the AX88190 chipset is not supported.
> > pcnet_cs: unable to read hardware net address for io
> > base 0x300
>
> I have the same problem, I'm getting this same message.
> I have a W-Linx Linx Pro 10/100 Card. It's listed as supported in the
> pcmcia
> pcnet_cs: sorry, the AX88190 chipset is not supported.
> pcnet_cs: unable to read hardware net address for io
> base 0x300
I have the same problem, I'm getting this same message.
I have a W-Linx Linx Pro 10/100 Card. It's listed as supported in the
pcmcia-cs-3.1.25 list of supported cards,
hey all,
I have nec versa 4000c with a linksys pcmpc100
ethernet pcmcia card. I am using kernel 2.2.17 and
the pcmcia source is version _. The computer
recognizes my card, but eth0 is not coming up when I
do "ifconfig." I did "modprobe pcnet_cs" and then
"dmesg" and it says:
pcnet_cs: sor
hey all,
I have nec versa 4000c with a linksys pcmpc100
ethernet pcmcia card. I am using kernel 2.2.17 and
the pcmcia source is version _. The computer
recognizes my card, but eth0 is not coming up when I
do "ifconfig." I did "modprobe pcnet_cs" and then
"dmesg" and it says:
pcnet_cs: so
On Mon, Aug 21, 2000 at 10:42:27AM -0700, EXT-Springer, Aaron C wrote:
> Hello,
>
> I just did an apt get upgrade from 2.1r4 to 2.2. It worked quite
> well.. except that my xircom Ethernet does not work. The card
> initializes and I have routes but I get an operation not authorized
> when I ping an
On Mon, 28 Aug 2000, Heather wrote:
>I just had a machine try this sometime this weekend, so I figured I'd note,
>it appears that 2.4.0 test 7 has "unresolved symbols in pcnet_cs". Yep,
Kernels up to 2.4.0-test4 worked fine on my Thinkpad. Test5 broke the Intel
PCMCIA controller support and this
On Mon, Aug 21, 2000 at 10:42:27AM -0700, EXT-Springer, Aaron C wrote:
> Hello,
>
> I just did an apt get upgrade from 2.1r4 to 2.2. It worked quite
> well.. except that my xircom Ethernet does not work. The card
> initializes and I have routes but I get an operation not authorized
> when I ping a
1 - 100 of 117 matches
Mail list logo
