| View previous topic :: View next topic |
| Author |
Message |
|MamboKing|
n00b
Joined: 15 Aug 2004
Posts: 2
|
 Posted: Sun Aug 15, 2004 4:23 am Post subject: Another happy customer (using Enterasys RoamAbout card) |
 |
|
This thread is a saviour! It gave me the right pointers to configure my card. The first time I tried it, I followed it exactly, and unfortunately couldn't get it to work. I just couldn't find the i82.... and ds modules. Then I decided to go about in another way, I did it slightly differently and it worked:
* I first removed pcmcia from run-level: rc-update del pcmcia boot
* Then I recompiled my kernel **with** pcmcia support, and also by selecting the 'CardBus yenta-compatible bridge support' as built-in
I then rebooted...and voila! The card picked up my wireless LAN and everything, the system loaded the right module and everything (I am using an 'Enterasys RoamAbout card', which is essentially an orinoco classic gold card, so it automatically loaded the orinoco_cs module).
Thanks for this post dude! I am using the kernel 2.6.5 btw, and maybe that could have been why I had to go about a little differently?
Cheers,
Praveen |
|
| Back to top |
|
 |
hunn
n00b
Joined: 18 Mar 2004
Posts: 12
Location: Århus - Denmark
|
| Posted: Wed Aug 18, 2004 1:31 pm Post subject: Re: PCMCIA nic: getting it working with pcmcia-cs (for n00bs |
|
|
| charlieg wrote: | After following the install docs to the letter and rebooting, there were still issues with pcmcia-cs. As far as I can guess, this should hold true for all users with pcmcia nics.
BTW, you might not need to do every step here, so if you know any step is unecessary, please say! Also, this is aimed at all skill levels, so apologies if you find parts of it patronising.
Preface
Assumptions:- You successfully completed the install docs and rebooted
ie if you didn't 'emerge pcmcia-cs' then this same command which has to be repeated later won't work now - you have no network set up! By emerging it before you've downloaded the sources necessary to install it. If you didn't, go to the end for a quick how-to.
- /usr/src/linux is a symlink to your linux kernel
eg for me it's a symlink to /usr/src/linux-2.4.19-gentoo-r10 and you can check this using 'ls -l /usr/src/linux' and, if needed, correct it using 'ln -sf /usr/src/linux-your-version /usr/src/linux'
Notes:
My machine is called gentoo1
Kernel preparation
| Code: | gentoo1 / # cd /usr/src/linux
gentoo1 linux # make menuconfig |
Since we're using pcmcia-cs, we don't need the kernel's specific pcmcia modules, so make sure they're deselected:
| Code: | General setup --->
PCMCIA/CardBus support --->
< > PCMCIA/CardBus support |
If this was already deselected, then skip the next bit. Otherwise, exit and remember to select 'yes' when asked if you want to save your 'new kernel configuration' and recompile the kernel:
| Code: | Saving your kernel configuration...
*** End of Linux kernel configuration.
*** Check the top-level Makefile for additional configuration.
*** Next, you must run 'make dep'.
gentoo1 linux # make dep && make clean bzImage modules modules_install |
Once this is complete (~30 mins or less) then you need to move it. You'll need to mount /boot if you haven't already done so. If you are mounting your /boot, you'll need to substitute 'hda1' with whatever device you use as your boot partition.
| Code: | gentoo1 linux # mount /dev/hda1 /boot
gentoo1 linux # cd /boot
gentoo1 boot # mv bzImage bzImage.old
gentoo1 boot # cp /usr/src/linux/arch/i386/boot/bzImage .
gentoo1 boot # cd /
gentoo1 / # umount /boot |
(Re)Install pcmcia-cs
A reboot may be required at this point, but I don't think so! However, a reboot does confirm that your kernel is functioning.
Re-emerge pcmcia-cs ('make clean' will have removed it as a module), and add it to the default runlevel so it runs on boot:
| Code: | gentoo1 / # emerge pcmcia-cs
gentoo1 / # rc-update add pcmcia boot |
Prepare configuration files
Now we need to make sure the appropriate modules are loaded when the computer boots:
| Code: | | gentoo1 / # nano -w /etc/modules.autoload |
This file, as indicated by it's name, loads modules automatically. For pcmcia you'll need either 'i82365' or 'i82092' compatable bridge support - depending upon which worked for you during the initial installation - and 'ds' (drive service). For most of us it's 'i82365', so substitute if with i82092 below if that's what you need.
Note the omission of pcmcia_core.
| Code: | # /etc/modules.autoload: kernel modules to load when system boots.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/modules.autoload,v 1.5 2002/$
#
# Add the names of modules that you'd like to load when the system
# starts into this file, one per line. Comments begin with a # and
# are ignored. Read man modules.autoload for additional details
# For example:
# 3c59x
# Here we'll put our relevant pcmcia modules
i82365
ds |
Finally, make sure you have the right information in the /etc/conf.d/net configuration file. As per usual you'll have to substitute information relevant to your network over mine:
| Code: | gentoo1 / # nano -w /etc/conf.d/net
# In this file we'll need the following correct definitions:
# iface_eth0
# gateway
# Note the similarity between this and the ifconfig command!
iface_eth0="10.0.0.130 broadcast 10.0.0.255 netmask 255.255.255.0"
# The gateway definition was definited during the installation by the
# route command, and the 'netmask 0.0.0.0 metric 1' is assumed
gateway="eth0/10.0.0.5" |
That's it! Reboot and hopefully it should work!
If it's still not working...
Check that your card is supported on the pcmcia-cs support cards list.
Did you correctly create resolv.conf? Check it anyway:
| Code: | gentoo1 / # nano -w /etc/resolv.conf
# nameservers go here but I shall not show mine for legal reasons!
# so these are rather made up
nameserver 123.1.2.3
nameserver 1.2.3.123 |
Did you add eth0 using rc-update, as the installation doc told you to? The following will output an explicit statement if you already have:
| Code: | | gentoo1 / # rc-update add net.eth0 default |
Double-check /etc/conf.d/net for typos - I find they're easier to make than they are to spot.
Check your modules loaded correctly, check yours is similar to mine with lsmod:
| Code: | gentoo1 / # lsmod
Module Size Used by Not tainted
serial_cs 7344 0 (unused)
xirc2ps_cs 16740 1
ds 7112 2 [serial_cs xirc2ps_cs]
i82365 26976 2
pcmcia_core 43520 0 [serial_cs xirc2ps_cs ds i82365] |
Check cardmgr is loaded:
| Code: | gentoo1 / # ps -C cardmgr
PID TTY TIME CMD
2416 ? 00:00:00 cardmgr |
I've tried to be as comprehensive as possible. Any other ideas, please suggest!
Addition - thanks to anz for this tip (edited quote):
| anz wrote: | I had the problem that the modules could not be found (... no i82365 and ds). But it worked after:
env-update
source /etc/profiles
ldconfig
update-modules force |
Getting pcmcia-cs
If you forgot to emerge it during the initial installation procedure, don't worry, it's easy to get it.
You can find out what version of pcmcia-cs your gentoo wants fairly easily:
| Code: | | gentoo1 linux # emerge -p pcmcia-cs |
You need to find it's url on a gentoo mirror. Then reboot and use the liveCD to boot, mount your partition and wget it into /mnt/gentoo/usr/portage/distfiles.
Replace /dev/hda3 by your main gentoo partition, if it differs.
| Code: | # mkdir /mnt/gentoo
# mount /dev/hda3 /mnt/gentoo
# cd /mnt/gentoo/usr/portage/distfiles
# wget http://path/to/pcmcia-cs |
Then take out the liveCD, boot back into your gentoo installation, and:
| Code: | | gentoo1 / # emerge pcmcia-cs |
Then resume. |
_________________
Nor am I a fish... |
|
| Back to top |
|
|
xmoy
Tux's lil' helper
Joined: 03 Aug 2004
Posts: 108
Location: .ch
|
| Posted: Mon Aug 30, 2004 6:22 pm Post subject: |
|
|
Hi
I've got a problem: I doesn't work 
I use a Dell Latitude A366 & a Xircom pcmcia card, kernel 2.6.8.1 (development-sources)
I disabled 'PCMCIA/CardBus support' in the kernel config (as described in this thread) and and recompiled the kernel. after that, I emerge'd pcmcia-cs, added it to the default runlevel and edited my modules.autoload (ok, i ln'ed . I checked, that iface_eth0 was set to "dhcp" and rebooted. But it did not work.
Here is the error message:
| Code: | * Using /etc/modules.autoload as config:
* Loading module i82365...
* Failed to load i82365 [!!]
* Loading module ds...
* Failed to load ds [!!]
...
* Starting pcmcia...
cardmgr[4884]: no sockets found!
* cardmgr failed to start. Make sure that you have PCMCIA
* modules build or support compiled into the kernel [!!] |
And, of course, eth0 won't start
If i manually
| Code: | chlaebtop root # modprobe i82365
FATAL: Module i82365 not found. |
If i boot from the LiveCD (adding dopcmcia to the kernel boot prompt), it works fine and 'lsmod' tells me that i82365 is loaded, so this should be the module i need, right? 
I think this is a simple problem, but I don't know what to do....
regards,
jonathan
_________________
:wq |
|
| Back to top |
|
|
xmoy
Tux's lil' helper
Joined: 03 Aug 2004
Posts: 108
Location: .ch
|
| Posted: Mon Aug 30, 2004 9:24 pm Post subject: |
|
|
Ouh...
when I tried to emerge pcmcia-cs, it told me 'enable pcmcia support in kernel config'. This should be done with kernels > 2.5.0. But the tutorial in this thread is written for 2.4.x, right?
hmm..
_________________
:wq |
|
| Back to top |
|
|
xenu
n00b
Joined: 04 Mar 2004
Posts: 16
Location: Teegeeack...of course...
|
| Posted: Wed Sep 01, 2004 3:06 pm Post subject: |
|
|
| terje_sagen wrote: | Ouh...
when I tried to emerge pcmcia-cs, it told me 'enable pcmcia support in kernel config'. This should be done with kernels > 2.5.0. But the tutorial in this thread is written for 2.4.x, right?
hmm.. |
I just did the same thing. Perhaps the first page can be modified to show that 2.5.0 kernels and later need PCMCIA configured in the source tree.
exact error when emerging pcmcia-cs.
"2.5.0 and later kernels require that PCMCIA be configured in the kernel source tree. To fix, reconfigure and rebuild your kernel with PCMCIA enabled."
cp /boot/bzImage.old /boot/ bzImage |
|
| Back to top |
|
|
xmoy
Tux's lil' helper
Joined: 03 Aug 2004
Posts: 108
Location: .ch
|
| Posted: Wed Sep 01, 2004 3:40 pm Post subject: |
|
|
Hi
I just found this in the menuconfig:
Device Drivers --> Networking support --> PCMCIA network device support
And there, i enabled the Xircom-Module support
Maybe it works now, I'll know it after rebooting 
jonathan
_________________
:wq |
|
| Back to top |
|
|
xenu
n00b
Joined: 04 Mar 2004
Posts: 16
Location: Teegeeack...of course...
|
| Posted: Thu Sep 02, 2004 2:35 pm Post subject: |
|
|
Installed Mandrake...ech at least it works. Now if I can get portage working on here
This needs to get sorted out for 2.6+ kernels. |
|
| Back to top |
|
|
xmoy
Tux's lil' helper
Joined: 03 Aug 2004
Posts: 108
Location: .ch
|
| Posted: Fri Sep 03, 2004 1:10 pm Post subject: |
|
|
it works fine with kernel 2.4, as I discovered...
_________________
:wq |
|
| Back to top |
|
|
xenu
n00b
Joined: 04 Mar 2004
Posts: 16
Location: Teegeeack...of course...
|
| Posted: Thu Sep 09, 2004 10:18 pm Post subject: |
|
|
For the record I removed Mandrake...I couldn't handle it.
I grabbed gentoo-dev-sources and used genkernel , emerged pcmcia-cs, and I am up and running. I guess my lack of knowledge in configuring the kernel manually was giving the problems.
Now onto getting the WIFI working.  |
|
| Back to top |
|
|
SerfurJ
l33t
Joined: 10 Apr 2004
Posts: 824
Location: Texas
|
| Posted: Sat Sep 11, 2004 3:05 pm Post subject: |
|
|
maybe this should be added to the howto:
| Code: | * For 2.5/2.6 kernels, the PCMCIA support from the kernel should
* be used. Enable PCMCIA and any further drivers you need there,
* and then use this package to install the PCMCIA tools. |
|
|
| Back to top |
|
|
ilyung
n00b
Joined: 30 Apr 2004
Posts: 10
Location: South Korea
|
| Posted: Thu Sep 16, 2004 7:13 am Post subject: Desperate help!!! |
|
|
Well, I am facing some trouble with using IBM 10/100 Cardbus etherjet PC card on my notebook( IBM ThinkPad R40)
Let me show you some info.
Linux kernel : 2.6.8.1
Installed pcmcia-cs version : 3.2.5-r1
The following is the part of "dmesg"
----------------------------------------------------------
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:02:00.0 [1014:0528]
Yenta: Using INTVAL to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:00.0, mfunc 0x01d11002, devctl 0x64
Yenta TI: socket 0000:02:00.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:02:00.0 no PCI interrupts. Fish. Please report.
Yenta: ISA IRQ mask 0x0000, PCI irq 0
Socket status: 00200f00
ACPI: PCI interrupt 0000:00:1d.7[D] -> GSI 11 (level, low) -> IRQ 11
----------------------------------------------------------
And the following is the part of "/proc/pci"
..........
Bus 2, device 0, function 0:
CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller (rev 0).
IRQ 11.
Master Capable. Latency=168. Min Gnt=64.Max Lat=5.
Non-prefetchable 32 bit memory at 0x3ff7b000 [0x3ff7bfff].
Bus 2, device 8, function 0:
Ethernet controller: Intel Corp. 82801BD PRO/100 VE (MOB) Ethernet Controller (rev 129).
IRQ 11.
Master Capable. Latency=66. Min Gnt=8.Max Lat=56.
Non-prefetchable 32 bit memory at 0xc0200000 [0xc0200fff].
I/O at 0x8000 [0x803f].
-----------------------------------------
As you can see, IBM 10/100 cardbus ethernet card is not loaded...
I desperately need help! Please help.
Oops, I almost forgot to post Kernel..
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=y
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_YENTA=y
CONFIG_CARDBUS=y
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_I82365=m
CONFIG_TCIC=m
CONFIG_PCMCIA_PROBE=y
Many thanks, |
|
| Back to top |
|
|
his_royal_evilness
n00b
Joined: 19 Apr 2004
Posts: 6
Location: Rotterdam , The Netherlands
|
| Posted: Wed Nov 03, 2004 5:53 am Post subject: |
|
|
What bout Yenta support on 2.4.26-r9? really can't get it 2 work with either kernel or pcmcia-cs config .. It's irritating me now
_________________
To spoof or not to spoof, that is the packet
----------
(char MyBrain)malloc(sizeof)(MyBrain); **** OUT OF MEMORY **** |
|
| Back to top |
|
|
ilyung
n00b
Joined: 30 Apr 2004
Posts: 10
Location: South Korea
|
| Posted: Wed Nov 03, 2004 8:08 am Post subject: It was hardware issue..sorry |
|
|
Sorry everyone,
What I posted before turned out to be a hardware issue.
It was nothing wrong with gentoo.
Sorry to bother you all. |
|
| Back to top |
|
|
qriff
n00b
Joined: 04 Dec 2003
Posts: 73
|
| Posted: Fri Feb 25, 2005 12:07 am Post subject: |
|
|
The mystery of 3c589d has yet not been resolved.
Going thru the basic google/forum/etc nobody seems to get it working with gentoo. (works on some other distros and windows)
PCMCIA loading ok, kernel modules loading ok (yes, pcmcia-cs too), etc all ok. But no network connectivity.
Other pcmcia cards like 3com Megahertz 574B works (same cables, connectors)
Old card, whining user... everything else works just nicely so... =) |
|
| Back to top |
|
|
hoggbottom59
n00b
Joined: 14 Mar 2005
Posts: 16
|
| Posted: Wed Mar 23, 2005 11:33 pm Post subject: |
|
|
I get an error of 'no pcmcia drive in /proc/devices'.
Does this little project sort that problem out too??
L. |
|
| Back to top |
|
|
IamTCM
n00b
Joined: 28 Jun 2005
Posts: 4
|
| Posted: Wed Jul 06, 2005 8:30 pm Post subject: |
|
|
UGHHH. For some reason cardmgr can't find my card anymore. It could find it on the LiveCD.... Does anyone have any ideas? My problems are exactly the same as Xmoy and I'm using 2.6.11-r3
---------------------------
Nm, I didn't know half of the modules I actually needed in order to get my system working.
After Adding
yenta_socket
i82365
xirc2ps_cs (for my xircom realport)
to the /etc/modules.autoconfig.d/kernel-2.6
and in the make menuconfig it works like a charm |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Documentation, Tips & Tricks
