PDA

View Full Version : Wireless Issues


sk8er
2004-07-20, 10:00 AM CDT
i just typed a big post basically mentioning i cooled down after music. and other stuff
bottomline: i shall write a article mentioning my making wirless netowkring thing to work (this and many other site lack one) if someone helps me fix this problem. Please sugget a detailed one because I have a dual boot system and each time to access your rpelies I would have to coem back to my windows side.

Picomp314
2004-07-20, 10:42 AM CDT
ok, thanks for chillin out dude
so i gather that you have an orinoco card
is this card PCI or is it a PC card ?

I am assuming you are running FC2
/sbin/modprobe orinoco_cs.ko

post the output of
/sbin/ifconfig
and
/sbin/iwconfig

sk8er
2004-07-20, 10:58 AM CDT
pci 11mbps dwl-520. dude i did all that. here is my dmesg output. look where it cmplains abut hw_unavaliable.

orinoco.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
orinoco_pci.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> & Jean Tourrilhes <jt@hpl.hp.com>)
PCI: Enabling device 0000:01:0b.0 (0004 -> 0006)
Detected Orinoco/Prism2 PCI device at 0000:01:0b.0, mem:0x40300000 to 0x40300FFF -> 0x1a92a000, irq:11
Reset done.............................................. .............................................<7>orinoco_lock() called with hw_unavailable (dev=15c82ce0)
.<7>orinoco_lock() called with hw_unavailable (dev=15c82ce0)
.<7>orinoco_lock() called with hw_unavailable (dev=15c82ce0)
.................................................. .................................................. .................................................. .......;
Clear Reset............................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. ........;
pci_cor : reg = 0x2 - 16AAD6 - 16A8E2
divert: allocating divert_blk for eth2
hermes @ MEM 0x1a92a000: Timeout waiting for card to reset (reg=0x0000)!
eth2: failed to initialize firmware (err = -110)
divert: freeing divert_blk for eth2
eth2: Failed to register net device
orinoco_pci: probe of 0000:01:0b.0 failed with error -110

Picomp314
2004-07-20, 11:02 AM CDT
to help you i NEED the output of
/sbin/lspci

because there are several revisions of the dwl-520 card; despite the fact that they use the same name there are at least three seperate chipsets that you could have, and thus three seperate drivers...

sk8er
2004-07-20, 11:05 AM CDT
hey
are u on aim
i tried messgaing you
anywayz
i would have to go to my other partition
do u think u can return my ims
it is
Intrsil Chip revision E

sk8er
2004-07-20, 11:17 AM CDT
01:0b.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)
Subsystem: D-Link System Inc DWL-520 Wireless PCI Adapter, Rev E1
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at 40300000 (32-bit, prefetchable)
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Picomp314
2004-07-20, 11:17 AM CDT
sorry the IM window was in another workspace, and I am in FC3T1 which isn't configured *properly*
normally the window changes to the active workspace...

sk8er
2004-07-20, 11:22 AM CDT
so are u receivin an IMs
i woudl appreciate if you could Im me back at sk8ercool2001

i also posted my lspci. would like to get it done tnoght so I write my
"how to " troubleshoot network thing tomorrow.

Ug
2004-07-20, 01:10 PM CDT
I would also appreciate it if you could keep the conversation here. So that a solution is available to anyone who has a similar problem.

sk8er
2004-07-20, 08:09 PM CDT
ok.
basically we got the hostap drivers. type in hostap in google and get the link.
I compiled them. on doing modprobe this is the message I get. Even dmesg says the same thing. What could it mean??

[root@localhost wireless]# modprobe hostap_pci
hostap: version magic '2.6.5 686 REGPARM gcc-3.3'
should be '2.6.5-1.358 686 REGPARM 4KSTACKS gcc-3.3'
WARNING: Error inserting hostap
(/lib/modules/2.6.5-1.358/kernel/drivers/net/wireless/hostap.ko):
Invalid module format
hostap_pci: version magic '2.6.5 686 REGPARM gcc-3.3'
should be '2.6.5-1.358 686 REGPARM 4KSTACKS gcc-3.3'
FATAL: Error inserting hostap_pci
(/lib/modules/2.6.5-1.358/kernel/drivers/net/wireless/hostap_pci.ko):
Invalid module format

sk8er
2004-07-20, 10:21 PM CDT
cmon noone. ever faced this issue??
I know a lot of smart fedora geeks browse this. cmon guys one of you?????????

Ug
2004-07-20, 11:33 PM CDT
sk8er, Thread bumping won't get your problem solved any quicker. People are more likely to ignore such threads.

imdeemvp
2004-07-21, 02:41 AM CDT
sk8er.....check this site: www.linuxant.org they work out around wireless issues

sk8er
2004-07-21, 09:44 AM CDT
yeah hostap are native linux drivers
i rather have those

Picomp314
2004-07-21, 09:49 AM CDT
i do think that native linux drivers should be used whenever possible; the problem imdeemvp is that driverloader is a 30-day trial version, one must pay to get more usage

sk8er
2004-07-21, 12:51 PM CDT
well,
I think I am pretty close. secodly, as I mentioned before, this is really polualr chip.
thirdly, redhat / fedora are xtremely polualr linux distro
thus, people using thse chips on fedore - posibility = good

lastly, it might have someting to do with firmware?
any diea how would I load it on the chip. aprogram./script comes wit the driver but i have no idea where to find the file??

any help is appreciated

Picomp314
2004-07-21, 08:44 PM CDT
it IS a possiblity that you would have to load the firmware if you had the DWL-520 rev. E1 or the DWL-650 rev. P1 both of which have an incomplete flash chip
that requires you to load the firmware onto it

the command is in the hostap-utils and is called hostap_fw_load
there should be a readme on how to do it inside the directory...


hostap-utils-0.2.4/README

See hostap_fw_load script for an example that loads firmware images
for cards without firmware in a flash chip (e.g., D-Link DWL-650
rev. P1 and D-Link DWL-520 rev. E1).

sk8er
2004-07-22, 12:21 AM CDT
hey,
I have the freakin module up??
any idea what those magic numbers mean................

Cupy
2004-10-10, 03:56 PM CDT
Hi,
the same prob as sk8er, HW: Zcom XI626, hostap 0.2.5 (today latest), did anybody succeed?
isn't hostap 0.1.3 better?
anyway, the HW works in RH7.3 hostap 0.1.2 great, but need to upgrade, 7.3 is quiet old...
------------------
Solved.
driver (module) must be compiled for current kernel, the version
is in /usr/src/linux-2.6.XXXX/include/linux/version.h
# cat /usr/src/linux-2.6.5-1.358/include/linux/version.h
#define UTS_RELEASE "2.6.5-1.358"
#define LINUX_VERSION_CODE 132613
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))


the problem was that I compiled hostap after kernel compilation,
(it changes version.h to #define UTS_RELEASE "2.6.5-1.358custom")
but current used kernel was 2.6.5-1.358, not the custom.
So I edited version.h - deleted word "custom" and recompiled hostap
make clean; make; make install
then modprobe works flawlesly

Why did I ever compile kernel? well, 1st I did not succeed with hostap compile.
it gave me a plenty of include errors. this fixed by
cd /usr/src/linux-2.6.xxxx
make oldconfig
make dep
make bzImage (this added some links like
/usr/src/linux-2.6.5-1.358/include/asm -> /usr/src/linux-2.6.5-1.358/asm-i386
which fixed the include errors during hostap compile

that's all, folks, hope this helps someone...

oldsoundguy
2004-10-10, 09:45 PM CDT
sk8er.....check this site: www.linuxant.org they work out around wireless issues
Yes, that IS a paid program .. and having tried their supposed fix for the texas instrument chipset, it does not work! They take your money and run!! IF you upgrade the os .. you PAY for a new version. NOT my idea of nice guys.

BTW, your fc installation guide PDF link doesn't yield anything but a non html index page and will not launch as a pdf and print. You need to check that.