Browsing Russian translation

20.

A majority of connection settings can be changed from within the <guilabel>Network Settings</guilabel> section of System Settings. To access the Network Settings, go to <menuchoice><guimenu>Kickoff Application Launcher</guimenu><guimenuitem>System Settings</guimenuitem></menuchoice> and then select <guilabel>Network Settings</guilabel> at the lower left of the window.

72.

If the above did not work, open <application>Konsole</application> (<menuchoice><guimenu>Kickoff Application Launcher</guimenu><guisubmenu>Applications</guisubmenu><guisubmenu>System</guisubmenu><guimenuitem>Terminal (Konsole)</guimenuitem></menuchoice>) and type <userinput>ping gateway_ip_address</userinput> (substitute gateway_ip_address by the ip address of your gateway. This address will be something like 10.0.0.1, 192.168.1.1, or 192.168.2.1, but may vary depending on the nature of your network). If you are able to ping your gateway, then the DNS on your computer is working correctly. If you are not able to ping the gateway, then you do not have a proper Internet connection.

74.

<emphasis role="bold">Command line</emphasis>: (<menuchoice><guimenu>Kickoff Application Launcher</guimenu><guisubmenu>Applications</guisubmenu><guisubmenu>System</guisubmenu><guimenuitem>Terminal (Konsole)</guimenuitem></menuchoice>) This will open up <application>Konsole</application> providing you with a terminal or the command line. Once you are sitting at the command prompt simply type <userinput>lspci</userinput> and press the <keycap>Enter</keycap> key. Locate the <guilabel>Network controller:</guilabel> line as this will provide information about your wireless adapter.

85.

<application>NdisWrapper</application> is considered the wireless fix-all for Linux. A great percentage of wireless adapters that are not supported natively or with other utilities are supported with <application>NdisWrapper</application>. Install <application>ndiswrapper</application> by using <application>Software Management</application>. If you are uncomfortable with installation practices then it is advised that you review the <ulink url="help:/kubuntu/add-applications/">Adding Applications</ulink> document.

92.

Once you have <application>bcm43xx-fwcutter</application> installed you can read through a list of links to various drivers for your Broadcom device. To do this open up <application>Konsole</application> (<menuchoice><guimenu>Kickoff Application Launcher</guimenu><guisubmenu>Applications</guisubmenu><guisubmenu>System</guisubmenu><guimenuitem>Terminal (Konsole)</guimenuitem></menuchoice>) and type at the prompt <userinput>zless /usr/share/doc/bcm43xx-fwcutter/README.gz</userinput> and press <keycap>Enter</keycap>. You have the choice of picking a driver from that list, driver CD, or manufacturer's website. The file you are interested in using is the <filename>bcwl5.sys</filename> file. If you have the drivers in a <filename>.zip</filename> format, unzip the files to a local directory. If the drivers are in a <filename>.exe</filename> format, you will need to install <application>Cabextract</application>. With <application>Cabextract</application>, at the command line locate the directory where you downloaded or copied the file to. Once there type at the prompt <userinput>cabextract filename.exe</userinput> and press <keycap>Enter</keycap>. This will extract the file into the directory you are in.

93.

Now that you have the driver files extracted, navigate with <application>Konsole</application> to the directory with the driver files. Next you will use the <application>bcm43xx-fwcutter</application> utility to install the drivers. To do so, at the prompt type <userinput>sudo bcm43xx-fwcutter -w /lib/firmware/$(uname -r) bcwl5.sys</userinput>. You may receive a couple of warnings which are nothing to worry about. If it didn't work, it will provide an error that states either driver isn't supported or the driver is to old. If this is the case, you would repeat this step using one of the drivers from the list in the <filename>README.gz</filename> file shown above. If you continue to have issues, connect to the Internet with another source and review the following sites: <placeholder-1/> If you continue to have issues with loading the drivers, then you may need to use the <application>NdisWrapper</application> utility.

94.

Now if you went through the driver installation without any major errors or issues, the next step would be to load the new module you created in the previous step. At the command line type <userinput>sudo modprobe bcm43xx</userinput> and press <keycap>Enter</keycap>. To see if the module loaded and is working, at the prompt type <userinput>iwconfig</userinput> and press <keycap>Enter</keycap>. If it works it should return the name of the interface as <acronym>ethX</acronym> where X is the number of the device. In most cases it may be <acronym>eth1</acronym> if you have a <acronym>CAT-5</acronym> Ethernet device already installed and configured. Also to test and see if your device can scan, at the command prompt type <userinput>sudo iwlist ethX scan</userinput> and press <keycap>Enter</keycap>. Don't worry if it reports <emphasis>no networks found</emphasis> as your connection may still be working. Test and see if you can connect to your network and the Internet. If everything has worked then you will want to add the module so it will load at boot. To do so, at the command prompt type <userinput>sudo sh -c "echo bcm43xx &gt;&gt; /etc/modules"</userinput> and press <keycap>Enter</keycap>.

111.

To start your <acronym>ADSL</acronym> connection on demand type <userinput>pon dsl-provider</userinput> and press <keycap>Enter</keycap>.

128.

Winmodems are not modems website that contains a very broad database of Winmodem support. Use this to further verify support for your modem, or research the list first before trying to install a device that may not be supported.

137.

At the command prompt, type <userinput>sudo wvdialconf /etc/wvdial.conf</userinput> and then press <keycap>Enter</keycap>.