Not signed in (Sign In)

Choose a language

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

Support and General Discussion: First run, LiveCD and wlan etc

Bottom of Page

1 to 3 of 3

  1.  
    • CommentAuthorhamil
    • CommentTimeJan 28th 2008
     # 1
    Hello,

    Downloaded the CD today (014), and decided to test it on my laptop (Zepto Znote 6214).

    It booted up just fine, and it did not take long time before X was up and running. However, I found that my wifi card was not supported from the start, and I could not find any gui for any wireless assistants etc. shipped with the live CD. For me, and many others like me, something like that would be highly appreciated. I am running Sabayon on the machine for now, and they are shipping both knetworkmanager and wlanassistant together with support for a lot of different cards. It becomes somewhat more work if would have to download the different modules and networkprograms on one machine, for so to install it on another one.. :)

    This is not meant as criticism, just as a wish from my point of view... (and my machine is equipped with the Intel 3945 card)

    And since I never have used GoboLinux before, when I have downloaded the IPW3945 package from SF.net, and the recipe file from here, how do I install them locally? The recipe file contains a url target, is there a way to make it look for it locally?

    Thanks for inputs
    Lasse
    • CommentAuthorNereusRen
    • CommentTimeJan 28th 2008
     # 2
    The recipe file contains a url target, is there a way to make it look for it locally?

    Yes, there is: First put the downloaded archive in /Files/Compile/Archives/, and then run Compile with the --no-web option. This will prevent it from attempting to fetch the archive from the web (or checking for a new version of the Recipe).
    You'll have to make sure it is exactly the file the Recipe is expecting (ipw3945-1.2.2.tgz, since that's what's on the end of the URL in the Recipe). If you have a different file that contains the same version of the source code, like .tar.bz2, you can simply change the name in the local recipe so it can find your archive. If you have a later version of the driver, you could do the same thing but it would be kind of a hack. The "right" way to do it is to call NewVersion IPW3945 [version number], which will generate a new recipe and automatically update the URL to expect the archive with that version number attached.
    • CommentAuthorm@cCo
    • CommentTimeJan 29th 2008 edited
     # 3
    I'd suggest you to use the new iwlwifi driver from Intel. I'm using it here and there haven't been problems so far. Also it allows you to get rid of the ipw3945 daemon.
    Actually you can just run "Compile iwlwifi" and it will search for the recipe, download the archive and install everything automatically. The recipe also checks for the ucode dependencies (there are two of them, one for the 3945 and one for the 4965 chipset, so just skip the second 'cause you're not going to need it in any way), thus relieving you of this part of the installation process.

    As for the graphical network manager yes, we still lack support for any of the ones available, but you can easily setup your wireless connection with the help of wpa_supplicant and the gobo tasks. Or, if you prefer, with wireless-tools. For the latter follow this topic on the mailing list: http://lists.gobolinux.org/pipermail/gobolinux-users/2008-January/007003.html

    For the former instead take a look at the wiki, here: http://gobo.kundor.org/wiki/WifiProtectedAccess

    However I find it to be tidier to put all the wpa_supplicant related commands in the /System/Settings/NetworkOptions file. Mine looks like this:
    NetworkInterfacesOnBoot=(
    lo
    wlan0
    )

    function wlan0_PreUp(){
    echo Starting WPA service...
    wpa_supplicant -i wlan0 -B -w -D wext -c /System/Settings/wpa_supplicant.conf
    }

    wlan0_PostDown(){
    echo Stopping WPA service...
    wpa_cli -i wlan0 terminate 1>/dev/null
    }

    lo_IP=127.0.0.1
    lo_Netmask=255.0.0.0
    eth0_BootProto=DHCP # DHCP (requires DHCPCD package), Static (default if empty)

    wlan0_BootProto=DHCP

    #Gateway=192.168.2.1
    GatewayInterface=wlan0
    You should also remember to load the iwl3945 module at startup. To do this, just add its name in the /System/Settings/BootOptions file, within the UserDefinedModules array.

    As a side note, I'm still trying to make a recipe for knetwork manager or better wicd. I'll let you know if I'll manage to :D

1 to 3 of 3

  1.