Find the answer to your Linux question:
Page 2 of 4 FirstFirst 1 2 3 4 LastLast
Results 11 to 20 of 37
Originally Posted by DaemonDave for the right firmware package run command as root: Code: uname -a this will tell you what kernel version you have. The on the page find ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Just Joined!
    Join Date
    Oct 2013
    Location
    Fredericton, New Brunswick
    Posts
    16

    Quote Originally Posted by DaemonDave View Post
    for the right firmware package

    run command as root:

    Code:
    uname -a
    this will tell you what kernel version you have.

    The on the page find the kernel version that closest matches :

    example your kernel is 1.1.1

    and at kernel.org they have

    firmwareA.tgz for 1.01
    firmwareB.tgz for 1.1 - 1.5

    then you choose to download firmwareB and follow the instructions
    I downloaded and installed 2.6.18-203.el5.jwltest.114 (replacing 2.6.18-194.el5). Are there any other upgrades you would reccommend?
    Also, in "Wireless Device Configuration" on the "Wireless Settings" tab, should "Mode" be set to Auto, Ad-Hoc, Managed, or Master?

  2. #12
    Just Joined!
    Join Date
    Oct 2013
    Posts
    47
    OK here's how things work inside a unix/ linux kernel:

    You have the generic kernel that runs the CPU memory etc. You have drivers for things that are attached to the kernel that aren't the main processor and they are .C programs that are slightly different than your normal main.c and they are compiled by GCC to become kernel modules: a driver in kernel friendly format. Now for things like a wireless ASIC it can also have it's own "BIOS" like the BIOS on the motherboard that handles tweaking the configuration: that is handled by the firmware and that's why it's smartest to get it right from the manufacturer - or they put it on kernel.org - because there's no guarantee the linux distribution one has the right version for your exact model. With me so far?

    So if you have the right firmware and load it right, you have the kmod and it's up and running, and then you have the right wireless configuration you are set.

    try command:

    Code:
    modprobe ath9k   OR  modprobe kmod-ath9k
    I'm not sure which module your distribution has. You can look it up by googling " kmod ath9k <YOUR EXACT LINUX DISTRO> and rpm " and you will most likely get the right name.

    Sorry I'm repeating myself but I just want to make sure you have all the right bits in the right place. Also repetition and you can learn the commands.

    modprobe goes looking for the kmod you told it to, finds it, installs it, and returns. If it's running you are set there.
    another way is to list modules with
    Code:
    lsmod
    and just look for it.
    Your wireless mode comes from the wireless router or whatever wireless system you are connecting to NOT your computer. You have to find that from your router. It's most likely "Managed".

  3. #13
    Just Joined!
    Join Date
    Oct 2013
    Posts
    47
    I told him to run uname -a because I wanted him to see the right RPM version if he may need to download it. You need i686 or i386 rpms NOT x86_64 rpm. that number string is the kernel version. The i686 is a 32 bit machine not a 64 bit machine so if you don't get the right ones the computer will scream at you!

  4. #14
    Just Joined!
    Join Date
    Oct 2013
    Location
    Fredericton, New Brunswick
    Posts
    16
    Thanks again DaemonDave.

    I ran the /sbin/modprobe ath9k command. Nothing apparent happened, I didn't receive an error so I assume the command was successful.

    I didn't see many x86 downloads available from kernel.org. I did see some downloads specifically referencing some of the items returned from the lsmod command.
    The text in red are the entries I suspect are relevant to wlan0. Hoping for a clue to what other updates I should download from kernel.org. If you've got some suggestions I'm all ears.
    Code:
    [root@localhost abacus]# /sbin/lsmod
    Module                  Size  Used by
    i915                   24257  1 
    drm                    65365  2 i915
    autofs4                29253  3 
    hidp                   23105  2 
    rfcomm                 42457  0 
    l2cap                  29505  10 hidp,rfcomm
    bluetooth              53925  5 hidp,rfcomm,l2cap
    lockd                  63337  0 
    sunrpc                146685  2 lockd
    cpufreq_ondemand       12493  1 
    acpi_cpufreq           13897  1 
    ip_conntrack_ftp       11569  0 
    ip_conntrack_netbios_ns     6977  0 
    ipt_REJECT              9665  1 
    xt_state                6209  12 
    ip_conntrack           53281  3 ip_conntrack_ftp,ip_conntrack_netbios_ns,xt_state
    nfnetlink              10713  1 ip_conntrack
    iptable_filter          7105  1 
    ip_tables              17029  1 iptable_filter
    ip6t_REJECT             9409  1 
    xt_tcpudp               7105  30 
    ip6table_filter         6849  1 
    ip6_tables             18181  1 ip6table_filter
    x_tables               17349  6 ipt_REJECT,xt_state,ip_tables,ip6t_REJECT,xt_tcpudp,ip6_tables
    loop                   18761  0 
    dm_multipath           25421  0 
    scsi_dh                12097  1 dm_multipath
    video                  21193  0 
    backlight              10049  1 video
    sbs                    18533  0 
    power_meter            16461  0 
    hwmon                   7365  1 power_meter
    i2c_ec                  9025  1 sbs
    dell_wmi                8401  0 
    wmi                    12137  1 dell_wmi
    button                 10705  0 
    battery                13637  0 
    asus_acpi              19289  0 
    ac                      9157  0 
    ipv6                  270305  17 ip6t_REJECT
    xfrm_nalgo             13381  1 ipv6
    parport_pc             29157  0 
    lp                     15849  0 
    parport                37513  2 parport_pc,lp
    joydev                 13185  0 
    snd_hda_intel         472337  1 
    snd_seq_dummy           7877  0 
    snd_seq_oss            32577  0 
    snd_seq_midi_event     11073  1 snd_seq_oss
    snd_seq                49585  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
    snd_seq_device         11725  3 snd_seq_dummy,snd_seq_oss,snd_seq
    snd_pcm_oss            42817  0 
    snd_mixer_oss          19009  1 snd_pcm_oss
    snd_pcm                72133  2 snd_hda_intel,snd_pcm_oss
    snd_timer              24517  2 snd_seq,snd_pcm
    sr_mod                 19941  0 
    snd_page_alloc         14281  2 snd_hda_intel,snd_pcm
    testmgr_cipher          6849  0 
    cdrom                  36577  1 sr_mod
    testmgr                52337  1 testmgr_cipher
    snd_hwdep              12869  1 snd_hda_intel
    aead                   11841  1 testmgr
    crypto_blkcipher       17601  1 testmgr
    crypto_algapi          22849  3 testmgr,aead,crypto_blkcipher
    crypto_api             12609  5 xfrm_nalgo,testmgr,aead,crypto_blkcipher,crypto_algapi
    snd                    55749  11 snd_hda_intel,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_hwdep
    arc4                    6209  2 
    ath9k                 285049  0 
    soundcore              11553  1 snd
    sg                     36717  0 
    serio_raw              10693  0 
    uvcvideo               53833  0 
    mac80211              139073  1 ath9k
    compat_ioctl32          5569  1 uvcvideo
    ath                    12737  1 ath9k
    cfg80211              141961  3 ath9k,mac80211,ath
    rfkill                 19797  1 cfg80211
    videodev               25793  1 uvcvideo
    v4l1_compat            16069  2 uvcvideo,videodev
    i2c_i801               11725  0 
    i2c_core               24001  2 i2c_ec,i2c_i801
    v4l2_common            24385  2 uvcvideo,videodev
    wireless_compat         5825  2 cfg80211,rfkill
    r8169                  43461  0 
    pcspkr                  7105  0 
    mii                     9409  1 r8169
    dm_raid45              67145  0 
    dm_message              6977  1 dm_raid45
    dm_region_hash         15681  1 dm_raid45
    dm_mem_cache            9537  1 dm_raid45
    dm_snapshot            23141  0 
    dm_zero                 6209  0 
    dm_mirror              24393  0 
    dm_log                 14657  3 dm_raid45,dm_region_hash,dm_mirror
    dm_mod                 63225  11 dm_multipath,dm_raid45,dm_snapshot,dm_zero,dm_mirror,dm_log
    usb_storage            80673  0 
    ahci                   36809  2 
    libata                157445  1 ahci
    sd_mod                 25281  3 
    scsi_mod              141973  6 scsi_dh,sr_mod,sg,usb_storage,libata,sd_mod
    ext3                  125513  2 
    jbd                    57321  1 ext3
    uhci_hcd               25421  0 
    ohci_hcd               25065  0 
    ehci_hcd               33869  0
    
    I apologize for the messy list. The formatting was removed when I saved the post.

    Edit: Note to OP - you can wrap text like this (command output, etc.) in CODE tags. Highlight your text and press the # button in the toolbar. Your list is still not perfect, but the scollable box makes it more forum-friendly, at least.
    Last edited by atreyu; 10-25-2013 at 08:55 PM. Reason: see Edit

  5. #15
    Just Joined!
    Join Date
    Oct 2013
    Posts
    47
    I apologize for the messy list. The formatting was removed when I saved the post.

    Hi there - not to worry. I was talking to Atryeu because he said run a different version of uname -r instead just to get the kernel number.

    Good news you have the kmod and it's running.

    The firmware won't be .i386 it's the firmware language. Sorry for the confusion. I know this is too much drinking from the firehose with so much to cover. RPMs will be 686 for the kmod and you have that installed. If you copied the files into the right place you are set, just reboot or you can run as root:

    Code:
    services network restart
    The last step is the wireless configuration.

  6. #16
    Just Joined!
    Join Date
    Oct 2013
    Posts
    47
    Here is the Unix default program operation: scream loud if you didn't work, say nothing if it's successful. You can get the details if you run:

    Code:
    dmesg | tail
    after the command and you will see the ath9k details in the code.

  7. #17
    Just Joined!
    Join Date
    Oct 2013
    Posts
    47
    great so the last step is the wireless network you are dealing with. There is one more piece of the puzzle you need to connect to password protected. There is a service that runs as a daemon (yea the same as my catchy nickname) that runs when it is called. It is used to negotiate with wireless routers with names and the psk key or whatever.

    It is called wpa_supplicant. If you plan on using password protected sites then you need to have this special service running.

    can you run as root:

    wpa_supplicant -Bw -c/etc/wpa_supplicant.conf -iwlan0

    and see if it can find the daemon. That will inform what the next step is. If it is already running even better we just need to tell it about which card and so on.

  8. #18
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,307
    sry, i missed this.

    Quote Originally Posted by DaemonDave View Post
    I told him to run uname -a because I wanted him to see the right RPM version if he may need to download it. You need i686 or i386 rpms NOT x86_64 rpm. that number string is the kernel version. The i686 is a 32 bit machine not a 64 bit machine so if you don't get the right ones the computer will scream at you!
    yeah, you are abs. right Dave. i was just answering his question technically, but you are straight up.

  9. #19
    Just Joined!
    Join Date
    Oct 2013
    Location
    Fredericton, New Brunswick
    Posts
    16
    Thank-you so much for all your help DaemonDave. I restarted the network service, see output below:

    [root@localhost /]# service network restart
    Shutting down interface wlan0: [ OK ]
    Shutting down loopback interface: [ OK ]
    Bringing up loopback interface: [ OK ]
    Bringing up interface eth0:
    Determining IP information for eth0... failed; no link present. Check cable?
    [FAILED]
    Bringing up interface wlan0:
    Determining IP information for wlan0... failed.
    [FAILED]

    "If you copied the files into the right place you are set,"
    Not certain I did this correctly. Which files are you referring to, and which location?

  10. #20
    Just Joined!
    Join Date
    Oct 2013
    Location
    Fredericton, New Brunswick
    Posts
    16
    I ran the dmesg command just for fun, although I wasn't expecting any results after seeing the [FAILED] message above.

    [root@localhost /]# dmesg | tail
    Bluetooth: RFCOMM TTY layer initialized
    Bluetooth: RFCOMM ver 1.8
    Bluetooth: HIDP (Human Interface Emulation) ver 1.1
    [drm] Initialized drm 1.0.1 20051102
    ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 177
    [drm] Initialized i915 1.8.0 20060929 on minor 0
    set status page addr 0x07fff000
    r8169: eth0: link down
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    ADDRCONF(NETDEV_UP): wlan0: link is not ready

Page 2 of 4 FirstFirst 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
  •