Ceni crashes on Eeepc 901A

Forum Forums New users New Users and General Questions Ceni crashes on Eeepc 901A

  • This topic has 2 replies, 3 voices, and was last updated Nov 19-1:35 am by christophe.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #93512
    Member
    roadkill13

      I have installed Antix Linux 22 Core on my little eeepc 901A that has an atom N270 32 bit processor, 2G of RAM and an RT2790 pci wireless adapter. Ceni identifies the adapter as such and it appears as wlan0. When I try to scan for networks a message is displayed “WPA_Supplicant Initiliazed Successfully” and everything stops at that point. There is no further activity. I have to use the keyboard to restart the computer at that point. This has always worked on previous versions of Antix core.

      Thank you

      #93528
      Member
      semicynic
        Helpful
        Up
        1
        ::

        Greetings
        I have a eeepc 901 and had a bit of a problem getting wireless set up. I use antiX full and use static IP4 and ceni to set up networking. Naturally I had to refer to my ISP’s docs to get the correct settings for ceni to use. sudo ifconfig was useful.
        I could ping a site if I use IP address, for example, 8.8.8.8 but pinging website by name showed no connection.
        dhclient -4 gave me enough info to make a resolv.conf.keep file something like:

        # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
        # DO NOT EDIT THIS FILE BY HAND — YOUR CHANGES WILL BE OVERWRITTEN
        nameserver 192.168.0.1 # for your local gateway
        nameserver nnn.nnn.nnn.nnn # nameserver 1
        nameserver nnn.nnn.nnn.nnn # nameserver 2
        search nnn.nnn.nnn.nnn Home # from ISP provider

        When I looked for /etc/resolv.conf, it didn’t exist so I did “touch /etc/resolv.conf” (without the quotes) to create it.
        Then when ping showed connection with IP4 but not with named website, I did

        sudo cp resolv.conf.keep /etc/resolv.conf

        This was my workaround using command line interface. Since I do this any time if I boot system, a script is useful.

        I hope this helps you find a solution for your problem.

        Have fun and be safe. semicynic

        #93532
        Moderator
        christophe
          Helpful
          Up
          0
          ::

          When I try to scan for networks a message is displayed “WPA_Supplicant Initiliazed Successfully” and everything stops at that point. There is no further activity.

          I ran into this, too. I thought like you did, too: that it’s broken — BUT it’s not.

          I was on my third reboot, trying different wifi dongles, when I got distracted. I had to do something for my wife… and when I got back, it worked! It had detected wifi networks! The key (for me) was to wait one or two minutes, then it proceeded to show the detected networks. (I know, it seems like 10 minutes, when your staring at the screen, but this only happens once, while setting it up.) Upon reboot, it detects it quickly, as normal.

          So once you start scanning for networks, try waiting: Go pour yourself your favorite drink, then come back…

          • This reply was modified 5 months, 2 weeks ago by christophe.

          confirmed antiX frugaler, since 2019

        Viewing 3 posts - 1 through 3 (of 3 total)
        • You must be logged in to reply to this topic.