I run an acer aspire 1694 laptop (build 2006) with xp. I decided to install opensuse 11.2 in addition to xp (on separate partitions). Installation went fine but I have no internet connection (wired or wireless).
Network Settings- Overview- top panel says:
“PRO/Wireless 2200BG [Calexico2] Network Connection Not configured”
lower panel says:
PRO/Wireless 2200BG [Calexico2] Network Connection (Not connected)
MAC : 00:13:ce:6e:86:11
The device is not configured. Press Edit to configure.
Needed firmware : ipw-firmware
Ethernet connection is not listed at all.
I have downloaded the ipm firmware to a usb stick on another pc but am holding off installing it as I feel I do not really know what I am doing.
One piece of good news is that the laptop and Linus are both visible in my wireless router where IP an MAC Addresses have been assigned.
My router is a Belkin 54 G.
My ethernet hardware is ‘Texas Instruments OHCI compliant IEEE 1394 Host Controller’ on PCI Bus (just something I noted while searching Hardware information).
Any help (if possible in ‘idiot speak’)will be very much appreciated.
On 05/31/2010 03:56 PM, DeDee wrote:
>
> I run an acer aspire 1694 laptop (build 2006) with xp. I decided to
> install opensuse 11.2 in addition to xp (on separate partitions).
> Installation went fine but I have no internet connection (wired or
> wireless).
>
> Network Settings- Overview- top panel says:
> “PRO/Wireless 2200BG [Calexico2] Network Connection Not configured”
>
> lower panel says:
> PRO/Wireless 2200BG [Calexico2] Network Connection (Not connected)
> MAC : 00:13:ce:6e:86:11
> The device is not configured. Press Edit to configure.
> Needed firmware : ipw-firmware
>
> Ethernet connection is not listed at all.
>
> I have downloaded the ipm firmware to a usb stick on another pc but am
> holding off installing it as I feel I do not really know what I am
> doing.
>
> One piece of good news is that the laptop and Linus are both visible in
> my wireless router where IP an MAC Addresses have been assigned.
>
> My router is a Belkin 54 G.
>
> My ethernet hardware is ‘Texas Instruments OHCI compliant IEEE 1394
> Host Controller’ on PCI Bus (just something I noted while searching
> Hardware information).
>
> Any help (if possible in ‘idiot speak’)will be very much appreciated.
On 05/31/2010 05:26 PM, DeDee wrote:
>
> Thank you for your prompt attention.
>
> Please take me through that ie how to “copy it(as root) to
> /lib/firmware”. Sorry but am really a novice. I have it on a USB stick
> waiting.
On 05/31/2010 06:46 PM, DeDee wrote:
>
> I think I have now installed the firmware.
> Top panel of Network Settings now reads:
>
> “PRO/Wireless 2200BG [Calexico2] Network Connection DHCP”. The lower
> panel however reads:
>
> ‘PRO/Wireless 2200BG [Calexico2] Network Connection (Not connected) MAC
> : 00:13:ce:6e:86:11
>
> Device Name: eth0
> Started automatically at boot
> IP address assigned using DHCP’
>
> Ethernet is still not showing or working. Will apprecaite help in
> reolving this.
Wireless will never work as long as eth0 is started at boot. You need to
set it to start “on cable connection” and disconnect the wire to get
wireless.
It appears as if you are using “ifup” rather than NetworkManager. That
is the hard way. Where do you expect Ethernet to be “showing”? If ypu
mean i the tray in the lower-right hand corner, then turn NM on.
I am really gratefull for your help but, as I mentioned, I am a novice and new to openSUSE. Therefore it would help if you could include the steps required when you reply. For instance, I have spent sometime reading up on how to turn on Network Manager and found nothing on the point. I have also read the ‘Welcome’ posts in Networking/Internet.
‘http://en.opensuse.org/KNetworkManager’ describes how NM works. I see it on ‘Kick Off’ under ‘Recently Used’ but when I click on it, nothing happens. So, how do I turn on Network Manager? Is there something I need to do before booting up or a command I need to type into ‘Terminal’?
Also, where do I go to tell Eth0 to start ‘on cable connection’?
‘User Control with NetworkManager’ ‘IPV6’ and ‘Change Default Route via DHCP’ are all enabled under Global Options. I still have a mast signal at the lower right hand corner of the screen which says ‘Not Connected’ when I hover over it. Any further tips?
Also is there a quick and easy way to get ethernet connection to work so that I can at least have internet on the laptop?
Hooraay, got it working! Actually, I re-installed and chose GNOME instead. I then configured the Network connection in GNOME and it works fine albeit a bit slow.
I still prefer KDE and intend to re-install KDE if anyone can help me get internet working there. I also want to have wired ethernet working. Sometimes I connect via wired to get utmost speed for downloads. I have read Iwfinger’s Sticky on the wireless sub-forum in readiness.
Although I have managed to configure wireless on GNOME it is very erratic. The signal drops every minute or so even while sitting next to the router and/or with signal at full strenght.It also appears to attempt to look up neighbouring routers. I ran the ‘iwlist’ command and got the following results:
lo Interface doesn’t support scanning.
Cell 03 - Address: XX:XX:XX:XX:XX
ESSID:“belkin54g”
Protocol:IEEE 802.11bg
Mode:MasterFrequency:2.4GHz(Channel6)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=95/100 Signal level=-32 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 7240ms ago
pan0 Interface doesn’t support scanning.
These set of figures were reported amongst two others belonging to nearby networks. Can I stop this happening? Are the outputs in order? Can I tweak anything elsewhere to get a stable connection.
I ran ‘iwconfig’ with and without a connection with the following results:
with connection down:
lo no wireless extensions.
eth0 unassociated ESSID:“h*(\x83\x8F\x1D\xE4:9\xCC\xCA\x94\xE8y^\x91\x8A\xD6\xDEW\xB7\x19\xDF\x18\x8Di\x8Ei\xDD/\xD1”
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:47 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
pan0 no wireless extensions.
with connection running
lo no wireless extensions.
eth0 IEEE 802.11g ESSID:“belkin54g”
Mode:Managed Frequency:2.437 GHz Access Point: XX:XX:XX:XX:XX
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=84/100 Signal level=-46 dBm Noise level=-89 dBm
Rx invalid nwid:0 Rx invalid crypt:47 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
pan0 no wireless extensions.
Again,from these figures is there anything I can tweak to get a stable connection?
3.I still cannot get wired internet access.Looking through Hardware Information, I believe the details are:
Loopback network interface
Device Name: lo
Device Names
Hwcfg:none
Model: Loopback network interface
Old Unique Key: qtiw.GQNx7L4uPNA
Resources
Sys ID: /class/net/lo
Unique Key:ZsBS.GQNx7L4uPNA
There are no outstanding firmware downloads in system log.
Any help in configuring wired internet access will be appreciated.
The reply I got from the command is ‘/:is a directory’. Is there another means of obtaining the the chipset information?
One other point I have discovered is that system and boot logs say:
‘Kill switch must be turned off for wireless networking to work’.
Is this the cause of the unstable/erratic wireless connection? My laptop has a switch to the front, but this does not appear to have any effect now. It works perfectly well on windows XP however.
The reply I got from the command is ‘/:is a directory’. Is there another means of obtaining the the chipset information?
Thats probably because you typed ‘/’ then a space before the command. It has to be typed exactly as shown.
One other point I have discovered is that system and boot logs say:
‘Kill switch must be turned off for wireless networking to work’.
Is this the cause of the unstable/erratic wireless connection?
If the kill switch was on you wouldn’t have wireless at all. The erratic operation is quite common for some wireless drivers and wireless routers. I have experienced exactly your symptoms at one of my previous workplaces. With the connection manager constantly reconnecting every few minutes, regardless of signal strength.
Thanks for your reply. I simply could not get internet connection to work on 11.2.Even the unstable connection I got after switching to GNOME disappeared completely after a while. I spent a great deal of time reading, researching and adjusting settings. Surely internet connection should not be that tasking. …And to prove the point, I formatted the entire disk (after a short research) and installed Ubuntu 10.04 LTS. I have wireless connection in less that 3 minutes after installation.
It’s a shame though as I really prefer openSUSE 11.2- it promises so much. I will keep a tag on any progress it makes with regard to simplifying internet connection.
Thanks for your reply. I simply could not get internet connection to work on 11.2.Even the unstable connection I got after switching to GNOME disappeared completely after a while. I spent a great deal of time reading, researching and adjusting settings. Surely internet connection should not be that tasking. …
You didn’t provide the info that I asked for may have enabled us to help further. I have no idea what ethernet hardware (chipset) you have, or even what driver is being used.
Was the stable Gnome connection a wireless ethernet connection?
I just could not get that command right despite my best efforts. I ran a different command on Ubuntu and got the following. Do the figures mean anything in terms fo the chipset/details?
Thats the same chipset as I have in my laptop. FWIW, I have experienced an unstable wireless connection (at a previous job) with good signal strength and wpa2 authentication. However, I haven’t had these problems elsewhere. I deduced (correctly or incorrectly) that it must have been down to the router interaction.
