Find the answer to your Linux question:
Page 1 of 4 1 2 3 4 LastLast
Results 1 to 10 of 32
Hello there, I am new to RedHat, and I installed RHEL 5 on my laptop (Acer aspire 4736z). After my installation I found out my LAN and wireless network is ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2010
    Posts
    15

    my wireless and LAN adaptor is not working, help


    Hello there,
    I am new to RedHat, and I installed RHEL 5 on my laptop (Acer aspire 4736z). After my installation I found out my LAN and wireless network is not working.

    using following command shows

    /sbin/lspci

    Wireless Network Adapter : Atheros comunication inc. AR928X (PCI express)
    Ethernet controller : Attansic tech. corp.

    Can anybody have solution to my problem?

    Thank you

  2. #2
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    Hi and Welcome !

    Check this sticky, execute script or code given there and post output here.
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

  3. #3
    Linux Guru reed9's Avatar
    Join Date
    Feb 2009
    Location
    Boston, MA
    Posts
    4,651
    Same question followed up on in a thread from linuxquestions.org

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    There is a RHEL/CentOS repository that has drivers for newer network devices.

    ELRepo : HomePage

    It has drivers for the Attansic atl1, atl1c, atl1e and atl2 chips. I don't know if any of these will work with your card, I will need more detailed info for that.

    Please post the output of this command.
    Code:
    /sbin/lspci -vnn
    Unfortunately, they don't have drivers for the Atheros wireless cards. You may have to use NDISwrapper, with a WinXP driver. LRepo does have a NDISwrapper kernel module that you can install.
    Please do not send Private Messages to me with requests for help. I will not reply.

  6. #5
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    When I tried RHEL 5.4 on my Eee PC, I had to use the MadWifi drivers for the wireless. The ath5k/ath9k driver are too new for the older kernel that RHEL uses. You will have to compile it from source, the snapshots of the source can be found here:

    snapshots.madwifi.org

    There are several different versions of the driver. I had to try several, until I found one that worked for me. It was the madwifi-hal version that I found worked for me, but your results may be different.

    You won't get this kind of in-depth help at LinuxQuestions! In fact, I see that they are steering you wrong!
    Please do not send Private Messages to me with requests for help. I will not reply.

  7. #6
    Just Joined!
    Join Date
    Mar 2010
    Posts
    15
    # lspci -vnn
    00:00.0 0600: 8086:2a40 (rev 09)
    Subsystem: 1025:0260
    Flags: bus master, fast devsel, latency 0
    Capabilities: [e0] Vendor Specific Information

    00:02.0 0300: 8086:2a42 (rev 09)
    Subsystem: 1025:0260
    Flags: bus master, fast devsel, latency 0, IRQ 17
    Memory at 90000000 (64-bit, non-prefetchable) [size=4M]
    Memory at 80000000 (64-bit, prefetchable) [size=256M]
    I/O ports at 5110 [size=8]
    Capabilities: [90] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
    Capabilities: [d0] Power Management version 3

    00:02.1 0380: 8086:2a43 (rev 09)
    Subsystem: 1025:0260
    Flags: bus master, fast devsel, latency 0
    Memory at 93400000 (64-bit, non-prefetchable) [size=1M]
    Capabilities: [d0] Power Management version 3

    00:1a.0 0c03: 8086:2937 (rev 03)
    Subsystem: 1025:0260
    Flags: bus master, medium devsel, latency 0, IRQ 21
    I/O ports at 50e0 [size=32]
    Capabilities: [50] #13 [0306]

    00:1a.1 0c03: 8086:2938 (rev 03)
    Subsystem: 1025:0260
    Flags: bus master, medium devsel, latency 0, IRQ 19
    I/O ports at 50c0 [size=32]
    Capabilities: [50] #13 [0306]

    00:1a.7 0c03: 8086:293c (rev 03) (prog-if 20)
    Subsystem: 1025:0260
    Flags: bus master, medium devsel, latency 0, IRQ 19
    Memory at 96705c00 (32-bit, non-prefetchable) [size=1K]
    Capabilities: [50] Power Management version 2
    Capabilities: [58] Debug port
    Capabilities: [98] #13 [0306]

    00:1b.0 0403: 8086:293e (rev 03)
    Subsystem: 1025:0260
    Flags: bus master, fast devsel, latency 0, IRQ 23
    Memory at 96700000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [50] Power Management version 2
    Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
    Capabilities: [70] Express Unknown type IRQ 0

    00:1c.0 0604: 8086:2940 (rev 03)
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
    I/O behind bridge: 00004000-00004fff
    Memory behind bridge: 95700000-966fffff
    Prefetchable memory behind bridge: 0000000090400000-0000000091300000
    Capabilities: [40] Express Root Port (Slot+) IRQ 0
    Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
    Capabilities: [90] #0d [0000]
    Capabilities: [a0] Power Management version 2

    00:1c.1 0604: 8086:2942 (rev 03)
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
    I/O behind bridge: 00003000-00003fff
    Memory behind bridge: 94600000-956fffff
    Prefetchable memory behind bridge: 0000000091400000-0000000092300000
    Capabilities: [40] Express Root Port (Slot+) IRQ 0
    Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
    Capabilities: [90] #0d [0000]
    Capabilities: [a0] Power Management version 2

    00:1c.2 0604: 8086:2944 (rev 03)
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
    I/O behind bridge: 00001000-00002fff
    Memory behind bridge: 93500000-945fffff
    Prefetchable memory behind bridge: 0000000092400000-0000000093300000
    Capabilities: [40] Express Root Port (Slot+) IRQ 0
    Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
    Capabilities: [90] #0d [0000]
    Capabilities: [a0] Power Management version 2

    00:1d.0 0c03: 8086:2934 (rev 03)
    Subsystem: 1025:0260
    Flags: bus master, medium devsel, latency 0, IRQ 20
    I/O ports at 50a0 [size=32]
    Capabilities: [50] #13 [0306]

    00:1d.1 0c03: 8086:2935 (rev 03)
    Subsystem: 1025:0260
    Flags: bus master, medium devsel, latency 0, IRQ 22
    I/O ports at 5080 [size=32]
    Capabilities: [50] #13 [0306]

    00:1d.2 0c03: 8086:2936 (rev 03)
    Subsystem: 1025:0260
    Flags: bus master, medium devsel, latency 0, IRQ 21
    I/O ports at 5060 [size=32]
    Capabilities: [50] #13 [0306]

    00:1d.3 0c03: 8086:2939 (rev 03)
    Subsystem: 1025:0260
    Flags: bus master, medium devsel, latency 0, IRQ 18
    I/O ports at 5040 [size=32]
    Capabilities: [50] #13 [0306]

    00:1d.7 0c03: 8086:293a (rev 03) (prog-if 20)
    Subsystem: 1025:0260
    Flags: bus master, medium devsel, latency 0, IRQ 20
    Memory at 96705800 (32-bit, non-prefetchable) [size=1K]
    Capabilities: [50] Power Management version 2
    Capabilities: [58] Debug port
    Capabilities: [98] #13 [0306]

    00:1e.0 0604: 8086:2448 (rev 93) (prog-if 01)
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=06, subordinate=06, sec-latency=32
    Capabilities: [50] #0d [0000]

    00:1f.0 0601: 8086:2919 (rev 03)
    Subsystem: 1025:0260
    Flags: bus master, medium devsel, latency 0
    Capabilities: [e0] Vendor Specific Information

    00:1f.2 0106: 8086:2929 (rev 03) (prog-if 01)
    Subsystem: 1025:0260
    Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 22
    I/O ports at 5108 [size=8]
    I/O ports at 511c [size=4]
    I/O ports at 5100 [size=8]
    I/O ports at 5118 [size=4]
    I/O ports at 5020 [size=32]
    Memory at 96705000 (32-bit, non-prefetchable) [size=2K]
    Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/4 Enable-
    Capabilities: [70] Power Management version 3
    Capabilities: [a8] #12 [0010]
    Capabilities: [b0] #13 [0306]

    00:1f.3 0c05: 8086:2930 (rev 03)
    Subsystem: 1025:0260
    Flags: medium devsel, IRQ 18
    Memory at 96706000 (64-bit, non-prefetchable) [size=256]
    I/O ports at 5000 [size=32]

    00:1f.6 1180: 8086:2932 (rev 03)
    Subsystem: 1025:0260
    Flags: fast devsel, IRQ 11
    Memory at 96704000 (64-bit, non-prefetchable) [size=4K]
    Capabilities: [50] Power Management version 3

    04:00.0 0280: 168c:002a (rev 01)
    Subsystem: 1a32:0306
    Flags: bus master, fast devsel, latency 0, IRQ 11
    Memory at 94600000 (64-bit, non-prefetchable) [size=64K]
    Capabilities: [40] Power Management version 2
    Capabilities: [50] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
    Capabilities: [60] Express Legacy Endpoint IRQ 0
    Capabilities: [90] MSI-X: Enable- Mask- TabSize=1

    05:00.0 0200: 1969:1063 (rev c0)
    Subsystem: 1025:0260
    Flags: bus master, fast devsel, latency 0, IRQ 11
    Memory at 93500000 (64-bit, non-prefetchable) [size=256K]
    I/O ports at 1000 [size=128]
    Capabilities: [40] Power Management version 3
    Capabilities: [48] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
    Capabilities: [58] Express Endpoint IRQ 0
    Capabilities: [6c] Vital Product Data

  8. #7
    Linux Guru reed9's Avatar
    Join Date
    Feb 2009
    Location
    Boston, MA
    Posts
    4,651
    Plus from linuxquestions.org
    Code:
    04:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)
    05:00.0 Ethernet controller: Attansic Technology Corp. Unknown device 1063 (rev c0)
    As I said there, you need the atl1c driver. Enable the ELrepo as Waterhead said. I linked to the driver on linuxquestions.

    For your wireless, no change there either. You need either the ath9k driver as I linked to before, or madwifi as Waterhead said. I looked briefly before and it didn't look like madwifi would work, but Waterhead knows more than I do about these things, so I'll defer to him.

  9. #8
    Linux Guru reed9's Avatar
    Join Date
    Feb 2009
    Location
    Boston, MA
    Posts
    4,651
    It strikes me that the reason I posted the link before rather than instructions to enable the elrepo, is because you presumably have no network connection at all, since you're looking for both wired and wireless drivers. You'll need to download the package to a flash drive and transfer it over to you RHEL box to install.

    It's possible there are some other dependencies, I just don't know RHEL well enough to say. Maybe someone else can chime in there.

    I asked it before, I'm still curious, is there a reason you're using Enterprise linux, and an old release at that, on what appears to be a fairly new netbook or laptop? A current desktop oriented distro will have this hardware working out of the box.

  10. #9
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    I want to caution you guys to keep this within Linux Forums. Referencing or linking to needed info, that you posted on another forum, is not good. This has raised the ire of more than one of this forums moderators.

    Don't assume that anyone knows what you posted in another forum. Post all needed information in this thread.
    Please do not send Private Messages to me with requests for help. I will not reply.

  11. #10
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    Thank you for the info, bunkdeath.

    Here is the ID of your network card:
    Code:
    05:00.0 0200: 1969:1063 (rev c0)
    The USB ID is the 1969:1063 number. Using that, I was able to confirm that the atl1c driver is the correct one to use. You haven't said if you have a 32-bit or 64 bit kernel. You can determine that with this command, please post the output of it:
    Code:
    uname -rm
    We need this kernel information before we can tell you which file to download.

    As for the wireless, the ath5k/ath9k drivers will not compile on the older RHEL kernel. The MadWifi driver did, that last time I used them. There are two or three versions, so you may have to try them all before you find the one that works. It is also possible that they won't work either.
    Please do not send Private Messages to me with requests for help. I will not reply.

Page 1 of 4 1 2 3 4 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •