You are not logged in.
I have a 3Com 3CRWE154G72 PCMCIA wireless card.
When I ran Mepis Linux it worked straight out of the box with Mepis' GUI configuration tool, (I never had to get my hands dirty!).
On my new Arch Linux 0.7.1 installation it seems to have detected this card and correctly loaded the prism54 module.
iwconfig reveals that my /etc/conf.d/wireless has been read correctly as it shows my ESSID, etc. against eth1.
ifconfig, however, doesn't show anything for eth1. There's only an eth0 entry for my wired connection.
Typing lspci reveals:
03:00:0 Network Controller: 3Com Corporation: Unknown device 6001 (rev 01)
Typing lshwd reveals:
03:00:0 Network Controller: 3Com Corp:|3cRWE154G72 Wireless LAN adapter (prism 54)
So it looks like I'm nearly there?
Can someone tell me what's left to do to get this fully working, please?
Offline
did you edit /etc/rc.conf ?
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo eth0 eth1)
or simply run
#ifconfig -a
#ifconfig eth1 up
#dhcpcd eth1
if that doesnt work check you ESSID is the same as your router
iifconfig eth1 essid YOUR ESSID
replace YOUR ESSID with appropriate name
do you have WEP enabled in your router?
check your WEP key
also checkout http://wiki.archlinux.org/index.php/Wireless_Setup
if your gonna run arch be prepared to learn if you dont want to learn
i find arch doesnt automate much if i didnt turn it on... it usually aint on
iwconfig --help
man iwconfig
my best friend
http://www.google.com/
Offline
I thought one was encouraged to post questions, no matter how silly they may appear to those with more experience, to this area of the forum?
Firstly, as I made clear in a previous post, I am here to learn. That's why I've moved to Arch Linux.
Secondly, I have already spent time perusing the Wiki, etc. and only posted my question when I couldn't make any headway.
I am using static IP addresses with my router and these have been specified in my rc.conf
My ESSID and WEP key have been provided correctly. (They work correctly on my Windows workstations and worked okay when I supplied them in Mepis)
eth1 won't startup. ifconfig proves that it's not correctly setup yet so it won't start.
Offline
Do I need the pcmcia-cs package installed?
And uncomment !pcmcia in rc.conf?
I've tried it but it doesn't seem to make any difference!
Though, as mentioned in my first post, Arch seemed to have recognised the 3Com PCMCIA card according to the output of lshwd.
I've furthered Googled but other references talk about older kernels (prism54 is built into my 2.6.13 as far as I am aware?) or the instructions seem to be for disimilar distros; ie. the config files don't match.
Offline
If I do an ifconfig -a then an entry for eth1 appears and seems to have been assigned the IP address I specified in rc.conf. However, its MAC address isn't the MAC address of my 3Com card.
I don't know if this helps?
Offline
Does lsmod show ndiswrapper loaded?
Offline
You don't need ndiswrapper for this card - as already mentioned the required prism54 driver is included in the kernel.
You also don't need pcmcia-cs - it's a Cardbus device, which means it's handled as pci.
Can you post your rc.conf, and also grep your dmesg for anything related to prism54 or eth1?
Offline
Thanks - I'll post these details tonight when I get home.
(By the way, when I tried to cut and paste from a terminal windows into Firefox it wouldn't seem to work. How can I avoid retyping in the output from the terminal window into this box on Firefox?)
Offline
It's not cut-and-paste in the windoze sense. Select the required text in your terminal, and then depending on your mouse, use either a middle-button click or a simultaneous-left-right-buttons click to enter it in Firefox - or any other gui-fied app.
Offline
My rc.conf:
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
#
# Localization
#
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: fount in /usr/share/kbd/consolefonts (only needed for non-us)
# USECOLOR: use ANSI color sequences in startup messages
#
HARDWARECLOCK="localtime"
TIMEZONE=Europe/GB
KEYMAP=uk
CONSOLEFONT=
USECOLOR="yes"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
#
# Networking
#
HOSTNAME="sanctuary"
#
# Module to load at boot-up (in this order)
# (prefix a module with a ! to disable it)
#
MODULES=(8139too prism54 !usbserial !ide-scsi)
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# (prefix an interface in INTERFACES with a ! to disable it)
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="eth0 192.168.1.103 netmask 255.255.255.0 broadcast 192.168.1.255"
eth1="eth1 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(lo eth0 eth1)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
#
gateway="default gw 192.168.1.1"
ROUTES=(gateway)
#
# Daemons to start at boot-up (in this order)
# (prefix a daemon with a ! to disable it)
#
DAEMONS=(syslog-ng hwd !hotplug pcmcia network netfs crond)
# End of file
eth0 is for my wired connection.
eth1 is for my wireless connection.
Grep'ing dmesg maybe gives us a clue:
[root@sanctuary /]# dmesg | grep prism54
Loaded prism54 driver, version 1.2
prism54: request_firmware() failed for 'isl3890'
prism54: request_firmware() failed for 'isl3890'
Looks like I've something missing?
Offline
Ummm after your reboot, try "modprobe -r prism54 && modprobe prism54" - then do a network restart - if it's working then, there's some firmware issues which we can deal with at that point.
Offline
I entered that then tried "ifconfig eth1 up" but just got this message "SIOCSIFFLAGS: No such file or directory".
The end of dmesg reads:
eth1: resetting device...
eth1: uploading firmware...
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00000000001e5020]
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
eth1: islpci_reset: failure
eth1: resetting device...
eth1: uploading firmware...
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
eth1: islpci_reset: failure
eth1394: $Rev: 1264 $ Ben Collins <bcollins@debian.org>
eth1394: eth2: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
eth0: no IPv6 routers present
eth1: removing device
ACPI: PCI interrupt for device 0000:03:00.0 disabled
Unloaded prism54 driver
Loaded prism54 driver, version 1.2
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
eth1: resetting device...
eth1: uploading firmware...
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
eth1: islpci_reset: failure
eth1: removing device
ACPI: PCI interrupt for device 0000:03:00.0 disabled
Unloaded prism54 driver
Loaded prism54 driver, version 1.2
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
eth1: resetting device...
eth1: uploading firmware...
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
eth1: islpci_reset: failure
eth1: resetting device...
eth1: uploading firmware...
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
eth1: islpci_reset: failure
Offline
Obvious question - do you have /lib/firmware/isl3890 on your system?
Offline
There is no firmware folder beneath /lib !
Presumably there should be? Shouldn't this have been created when I installed?
Would do I need to do to correct this?
Offline
Create /lib/firmware and put the firmware file in it. Arch does not do this automatically.
The only completely legal way to get hold of the firmware file is to extract it from the Windoze driver CD - it will have the extension .arm. Rename it to isl3890.
Of course, if you're in a hurry, or lazy, you can get it here.
Offline
Followed your link but the subsequent links to the firmware on that page seem to be dead!
Offline
Not dead here - I just d'led it.
Try here.
Offline
Ok. My thanks again.
I've downloaded it, renamed it to isl3890.arm and put it in /lib/firmware.
What do I do next?
Offline
No, just isl3890 i.e. what you just downloaded, no changes.
Just do what you were doing before.
Offline
Woohoo!
Renamed it back.
Entered "ifconfig eth1 up" and the link light turned on!
Gonna disconnect my wired link and see if I remain connected...
Offline
glad to see your up if i seemed to come off as an ass it was not my intention
by all means ask away my 1st question here was way more newbie than your
check it out http://bbs.archlinux.org/viewtopic.php? … highlight=
Offline
Yes, it's working!
Thank you so much.
To think that one missing file could cause all that frustration!
Offline
Cool - glad it's working.
Here's an observation to finish with. You say you want to learn, and that's why you're using Arch. In this thread, I don't think you've learned anything - you've been told what to do. Our wiki is good and improving all the time, but it doesn't have everything - some preparatory googling would have turned up something you obviously didn't know i.e. the "one missing file" is actually the firmware, and the card won't work without it. If you want to get the most out of Arch, you need to put some effort into it - that's how you learn.
My 2c - feel free to ignore.
Offline
Hi all, I'm trying to setup my network card with archlinux.
The card is a "isl3890", so I downloaded Prism54 firmware for isl3890, renamed it and moved to /lib/firmware/isl3890
I've that error doing ifconfig eth2 up : SIOCSIFFLAGS: Time expired .
First, without installing firmware it sayd: SIOCSIFFLAGS: No such file or directory .
Can you help me please? i've googled, and I saw that others had this error too, but no solution.
Thanks.
Offline