Find the answer to your Linux question:
Page 1 of 3 1 2 3 LastLast
Results 1 to 10 of 22
Hi I'm desperate for assistance. I have been reading through heaps of Linux Forums to get assistance but no luck what so ever. I have a Acer Aspire 4315 Notebook ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Nov 2008
    Location
    Auckland NZ
    Posts
    11

    WPA Security worked 100% till last Auto Update


    Hi I'm desperate for assistance. I have been reading through heaps of Linux Forums to get assistance but no luck what so ever. I have a Acer Aspire 4315 Notebook with Linux MInt Elyssa OS. Up to a week ago I had no problems connecting to my DLINK G604T Wireless router with WPA Security then I had a did a update in Elyssa and everything changed. I now can't get a connection with WPA configured. I can connect with NO Security no problem. I can also connect with a simple WEP 128bits key no problem. It took me a long time to set up wireless on this linux box with Wireless_Atheros_Foxconn_v.5.3.0.45 drivers and now this is a massive setback for me as I am very very new to Linux and to sort things out takes me forever. I red somewhere to blacklist the ath_pci which I did but no change all the same symptoms.

    What I did see after the update is when I start up my notebook I get 4 Kernels I can pick from I can't remember that before and it seemed the kernels were upgrade must have been when I did a auto update. The 4 I can choose from is:

    Linux Mint Kernel 2.6.24-21
    Linux Mint Kernel 2.6.24-21 Recovery Mode
    Linux Mint Kernel 2.6.24-16
    Linux Mint Kernel 2.6.24-16 Recovery Mode
    Linux Mint Kernel memtest86+

    Is this a problem. Please anyone I need help to sort this problem because a Notebook without wireless is useless...... and WPA Security is a must not so?

    Thanks

  2. #2
    Blackfooted Penguin daark.child's Avatar
    Join Date
    Apr 2006
    Location
    West Yorks
    Posts
    4,393
    Have you tried using the older kernel (number 3 in your list) instead of the new one?

  3. #3
    Just Joined!
    Join Date
    Nov 2008
    Location
    Auckland NZ
    Posts
    11
    Yes I have and it does the same thing.

    I use this notebook only for playing around with linux and surfing the web etc nothing major. I am thinking of starting all over agin by by re-installing Elyssa from the live cd do you think that will sort the problem? Also if I do that say for instance I have data in the machine with a re-install I would loose all that data.

    Correct? I'm really running out of ideas here and are thinking just to start from scratch in Elyssa again or even upgrade to Feliccia... I just want wireless to work again like it did a week back bugger....

    Thanks for your help

  4. $spacer_open
    $spacer_close
  5. #4
    Blackfooted Penguin daark.child's Avatar
    Join Date
    Apr 2006
    Location
    West Yorks
    Posts
    4,393
    Before reinstalling, maybe you should ask in the Linux Mint forum for possible solutions. Other users may have experienced the same problem and come up with a solution. If the original version you installed worked fine, then a reinstall should work fine. As for losing data, if you have a separate /home partition and decide to reinstall Mint, make sure you do not format it, so that your data is preserved.

  6. #5
    Just Joined!
    Join Date
    Nov 2008
    Location
    Auckland NZ
    Posts
    11
    Hi I have gone through that Mint Forum with no much success.

    When you talk about "separate /home partition" are you talking about like having dual OSS like Windows on it aswell.

    I don't undertstand what you mean with separate /home partition sorry.

    Thanks

  7. #6
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    Your problem seems to be a driver problem, but it should work on the older kernel.

    The usual way to connect with Atheros wireless was to use the MadWifi driver. That driver is not completely open source, so new open source drivers have been developed. They are called ath5k and ath9k, and are now included in the latest kernels.

    To determine what is actually going wrong, you will need to supply some information. Please read through the thread linked to below, and post the outputs of the listed commands here in this thread.

    http://www.linuxforums.org/forum/wir...tml#post589924
    Please do not send Private Messages to me with requests for help. I will not reply.

  8. #7
    Just Joined!
    Join Date
    Nov 2008
    Location
    Auckland NZ
    Posts
    11
    Hi Thanks for your help. Just to let you know on one of the other forums I saw that I could have a ndiswrapper and ath_pci driver conflict so I blacklisted the ath_pci driver and it still blacklisted not to sure how to undo the blacklist anyway even with it blacklisted I have the same problem.

    I did the following command BEFORE the blacklist of ath_pci : sudo /usr/lib/linuxmint/mintWifi/mintWifi.py ......

    Here is the results unfortunately I at the office at the moment and the notebook is at home so can't do your commands just now sorry :
    -------------------------
    * I. scanning WIFI PCI devices...
    -------------------------
    * II. querying ndiswrapper...
    net5211 : driver installed
    device (168C:001C) present (alternate driver: ath_pci)
    -------------------------
    * III. querying iwconfig...
    lo no wireless extensions.

    eth0 no wireless extensions.

    wlan0 IEEE 802.11g ESSID:off/any
    Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
    Bit Rate:54 Mb/s
    Encryption key:off
    Power Management:off
    Link Quality:0 Signal level:0 Noise level:0
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    -------------------------
    * IV. querying ifconfig...
    eth0 Link encap:Ethernet HWaddr 00:1d:72:0e:1d:4e
    inet addr:10.1.1.3 Bcast:10.255.255.255 Mask:255.0.0.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1018 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1106 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:743842 (726.4 KB) TX bytes:212899 (207.9 KB)
    Interrupt:16

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:174 errors:0 dropped:0 overruns:0 frame:0
    TX packets:174 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:8700 (8.4 KB) TX bytes:8700 (8.4 KB)

    wlan0 Link encap:Ethernet HWaddr 00:17:c4:09:b1:47
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
    Interrupt:17 Memory:f8000000-f8010000

    -------------------------
    * V. querying DHCP...
    Internet Systems Consortium DHCP Client V3.0.6
    Copyright 2004-2007 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/

    Listening on LPF/wlan0/00:17:c4:09:b1:47
    Sending on LPF/wlan0/00:17:c4:09:b1:47
    Listening on LPF/eth0/00:1d:72:0e:1d:4e
    Sending on LPF/eth0/00:1d:72:0e:1d:4e
    Sending on Socket/fallback
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
    DHCPOFFER of 10.1.1.3 from 10.1.1.1
    DHCPREQUEST of 10.1.1.3 on eth0 to 255.255.255.255 port 67
    DHCPACK of 10.1.1.3 from 10.1.1.1
    bound to 10.1.1.3 -- renewal in 1576 seconds.
    -------------------------
    * VI. querying nslookup google.com...
    Server: 10.1.1.1
    Address: 10.1.1.1#53

    Non-authoritative answer:
    Name: google.com
    Address: 209.85.171.99
    Name: google.com
    Address: 72.14.207.99
    Name: google.com
    Address: 64.233.187.99

  9. #8
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    When using NDISwrapper, you can screw your system up pretty easily. Linux Mint is an Ubuntu derivative, and it is very easy to install the native Linux drivers on it. There is no reason to use NDISwrapper.

    That being said, you have to remove and blacklist the native Linux drivers. If your new kernel has newer and different drivers, you will need to remove and blacklist those too. You also may need to re-install NDISwrapper for the new kernel.

    The lesson learned is this: Don't update your computer if everything is working OK.
    Please do not send Private Messages to me with requests for help. I will not reply.

  10. #9
    Blackfooted Penguin daark.child's Avatar
    Join Date
    Apr 2006
    Location
    West Yorks
    Posts
    4,393
    Quote Originally Posted by blommie View Post
    Hi I have gone through that Mint Forum with no much success.

    When you talk about "separate /home partition" are you talking about like having dual OSS like Windows on it aswell.

    I don't undertstand what you mean with separate /home partition sorry.

    Thanks
    What I meant by separate /home is that when you installed Linux Mint, did you install everything in one partition (like windows does) or did you make separate partitions for the operating system and your personal files?

  11. #10
    Just Joined!
    Join Date
    Nov 2008
    Location
    Auckland NZ
    Posts
    11
    Hi Paul.

    So how do I see how many wireless drivers are going at the moment. I blacklisted ath_pci so it should only be NDISwrapper not so. How will I remove and blacklist the newer kernel's drivers. Yes you right once I get this back working 100% I wont be doing no updates forsure..

    Thanks

    Riaan

Page 1 of 3 1 2 3 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
  •