Fedora Linux Support Community & Resources Center
  #1  
Old 10th June 2006, 05:48 PM
supermal Offline
Registered User
 
Join Date: Jun 2006
Location: Newcastle upon tyne. uk
Posts: 3
wireless problems

Joined: 2006/6/6
From
Posts: 1

Hello to everybody.

I am tryiung on this forum becauseI understand that centos is based heavily on Fedora, and that maybe someone here can help. i hope I'm not out of line.

I am trying to get my wireless centos v4 up and running on my Sony vaio but!!
When I ry to activate eth1 the wireless card I get some error message(s).
First let me say that the card appears to be recognised properly and is obviously visible in the network configuration window.
The usual proviso that it is ok in winXP.

The card is a 3com card.
on trying to activate it the following occurs.
An error window appears with following in it.

-----------------------------------------------------------
Error for wireless request "Set Bit Rate" (8B20) :
SET failed on device eth1 ; Input/output error.

Determining IP information for eth1...SIOCSIFFLAGS: No such file or directory
SIOCSIFFLAGS: No such file or directory

If I cancel and try again I get the following

Error for wireless request "Set Bit Rate" (8B20) :
SET failed on device eth1 ; Input/output error.

Determining IP information for eth1...dhclient(24954) is already running - exiting.
failed.
-------------------------------------------------------------------------------
On checking the PCI info I get
06:00.0 Network Controller 3com (then the details of the ard, which are correct)
FLAGS bus master,medium devsel,latency 80 irq9
Memory at 21000000(32 bit non prefetchable) {size = 8K}
Capabilities {dc} Power Management version1.
At no time do I see any activity on the card LED's.
Can anyone start me in the ight direction here.
Reply With Quote
  #2  
Old 11th June 2006, 06:22 PM
supermal Offline
Registered User
 
Join Date: Jun 2006
Location: Newcastle upon tyne. uk
Posts: 3
As a point of interest I have now loaded fed 5 instead of centos with exactly tha esame error.
It gives no clues whatsoever.
Reply With Quote
  #3  
Old 11th June 2006, 06:38 PM
scotta3234's Avatar
scotta3234 Offline
Registered User
 
Join Date: Sep 2005
Location: Fairfax, VA
Posts: 1,280
Many of those 3com cards should be supported directly in FC5. First, I would go into /System/Administration/Network and double click on your wireless card and check all the settings there like DHCP, correct hardware and card, Mode should be "Auto" and make sure you specify your SSID correctly.
Reply With Quote
  #4  
Old 12th June 2006, 08:54 PM
supermal Offline
Registered User
 
Join Date: Jun 2006
Location: Newcastle upon tyne. uk
Posts: 3
Thanks for your reply.

I have tried the setups several times , unfortunatly always with the same result. Basically as per my first post.

For information I have added the relevant contents of dmesg in case they help. I am going to try the bit about "pci=routeirq". I presume its a terminal command. Eth0 is my wireless card, eth1 my mobo network card according to the network controller window , the 3com card is a 3crwe154g72. Note that this conflicts with what dmesg reports.
Thanks again.

Linux version 2.6.15-1.2054_FC5 (bhcompile@hs20-bc1-3.build.redhat.com) (gcc version 4.1.0 20060304 (Red Hat 4.1.0-3)) #1 Tue Mar 14 15:48:33 EST 2006

Allocating PCI resources starting at 30000000 (gap: 20000000:dffe0000)
Built 1 zonelists
Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (01402000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0


Intel machine check reporting enabled on CPU#0.
CPU: AMD mobile AMD Athlon(tm) XP-M 2200+ stepping 00
ACPI: setting ELCR to 0200 (from 0a00)
checking if image is initramfs... it is
Freeing initrd memory: 1644k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd944, last bus=1
PCI: Using configuration type 1
ACPI: Subsystem revision 20060127
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 8000-807f claimed by vt8235 PM
PCI quirk: region 8100-810f claimed by vt8235 SMB
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs *9 10 11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs *9 10 11 12)
ACPI: Embedded Controller [EC0] (gpe 1) interrupt mode.
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PPB_._PRT]
Linux Plug and Play Support v0.97 (c) Adam Belay

PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Bus 2, cardbus bridge: 0000:00:0e.0

PCI: Bus 6, cardbus bridge: 0000:00:0e.1
IO window: 00002800-000028ff
IO window: 00002c00-00002cff
PREFETCH window: 34000000-35ffffff
MEM window: 36000000-37ffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt 0000:00:0e.1[B] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ 9
Simple Boot Flag at 0x36 set to 0x1
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
audit(1150143966.692:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key EE596B44DDA71123
- User ID: Red Hat, Inc. (Kernel Module GPG key)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: PCI Interrupt 0000:00:11.1[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
PCI: Via IRQ fixup for 0000:00:11.1, from 0 to 11
ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:00:0e.0 [104d:8143]
Yenta: ISA IRQ mask 0x04b8, PCI irq 11
ACPI: PCI Interrupt 0000:00:0e.1[B] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ 9
Yenta: CardBus bridge found at 0000:00:0e.1 [104d:8143]
Yenta: ISA IRQ mask 0x04b8, PCI irq 9
Socket status: 30000006
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 327680 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
powernow: PowerNOW! Technology present. Can scale: frequency and voltage.
Detected 1667.033 MHz processor.
powernow: SGTC: 13333
powernow: Minimum speed 400 MHz. Maximum speed 1667 MHz.

Write protecting the kernel read-only data: 359k
pccard: CardBus card inserted into slot 0



NET: Registered protocol family 23
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
8139cp: pci dev 0000:00:0c.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp: Try the "8139too" driver instead.
8139too Fast Ethernet driver 0.9.27
PCI: Enabling device 0000:00:0c.0 (0000 -> 0003)
ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ 9
PCI: Setting latency timer of device 0000:00:0c.0 to 64
eth0: RealTek RTL8139 at 0xe0836000, 08:00:46:af:c4:4c, IRQ 9
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
via82xx: Assuming DXS channels with 48k fixed sample rate.
Please try dxs_support=5 option
and report if it works on your machine.
For more details, read ALSA-Configuration.txt.
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
PCI: Via IRQ fixup for 0000:00:11.5, from 255 to 11

PCI: Enabling device 0000:00:11.6 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:11.6[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
PCI: Via IRQ fixup for 0000:00:11.6, from 255 to 11
PCI: Setting latency timer of device 0000:00:11.6 to 64
MC'97 1 converters and GPIO not ready (0xff00)
Loaded prism54 driver, version 1.2
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
cs: IO port probe 0x3d4-0x4ff: excluding 0x3ec-0x3fb
cs: IO port probe 0x3c0-0x3d2: clean.
cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0x3d4-0x4ff: excluding 0x3ec-0x3fb
cs: IO port probe 0x3c0-0x3d2: clean.
cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0xa00-0xaff: clean.

ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
PCI: Via IRQ fixup for 0000:00:10.0, from 9 to 11
PCI: Setting latency timer of device 0000:00:10.0 to 64

ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ 9
PCI: Via IRQ fixup for 0000:00:10.1, from 0 to 9
ieee1394: Initialized config rom entry `ip1394'
ACPI: PCI Interrupt 0000:00:10.2[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
PCI: Via IRQ fixup for 0000:00:10.2, from 0 to 11


PCI: Enabling device 0000:00:0e.2 (0000 -> 0002)
ACPI: PCI Interrupt 0000:00:0e.2[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[11] MMIO=[e0000800-e0000fff] Max Packet=[2048] IR/IT contexts=[4/4]
PCI: Enabling device 0000:00:10.3 (0010 -> 0012)
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9
PCI: Via IRQ fixup for 0000:00:10.3, from 255 to 9
PCI: Setting latency timer of device 0000:00:10.3 to 64
h
NET: Registered protocol family 10

IPv6 over IPv4 tunneling driver


SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
Reply With Quote
Reply

Tags
problems, wireless

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Wireless problems with FC7 help!!_newbie Servers & Networking 1 5th July 2007 09:18 AM
wireless problems gutaker Hardware & Laptops 6 30th April 2006 01:08 AM
wireless nic problems jwdvd Servers & Networking 2 27th February 2006 03:31 PM
wireless problems tedmg09130913 Servers & Networking 1 20th February 2005 02:22 AM


Current GMT-time: 05:35 (Sunday, 19-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat