Which KDE do I have? was -- Can't get wireless to work with kubuntu 9.04

Bruce Bales bbales at cox.net
Sat Aug 1 16:27:50 BST 2009


On Saturday 01 August 2009 05:45:31 Errol Sapir wrote:
> I see that this thread is over but I still want to put in my 2c. I use
> WICD as my network manager. Since being introduced to that program I
> have NOOOOOOO problems connecting to wireless or wired connection. The
> network manager (I was told - and also found out from my own experience)
> is pretty lousy so WICD, answers the problem very well.
> Errol
>
Errol, David and Nils,

Thanks to all for the help.  After several subsequent boots on the laptop, I 
found that I no longer needed to put in the iwconfig .... line.  All I needed 
to do was go to the network manager (which has a list of nearby wireless 
providers) and click on my essid (bbs).  It has even stored my key code and 
firefox came right up. 

With Kubuntu 9.04 and so many changes to the looks of the thing, I assumed I 
was working with KDE 4.2.  Running kded --version gives me 

Qt 3.3.8b
KDE 3.5.10
KDE Daemon? $ID: kded.cp 711061 2007-09-01 09:07:51z tpatzig$

What happened to KDE 4?
bruce

PS. If this is a top-post, it seemed appropriate here. b²



> Nils Kassube wrote:
> > David McGlone wrote:
> >> This is what my interfaces file looks like on my laptop:
> >>
> >> auto lo
> >> iface lo inet loopback
> >>
> >> #auto eth0
> >> #iface eth0 inet static
> >> #address 192.168.2.2
> >> #netmask 255.255.255.0
> >> #network 192.168.2.0
> >> #broadcast 192.168.2.255
> >> #gateway 192.168.2.1
> >> #dns-nameserver 192.168.2.1
> >> #dns-search dmcghome
> >>
> >> iface wlan0 inet static
> >> address 192.168.2.3
> >> netmask 255.255.255.0
> >> gateway 192.168.2.1
> >> dns-nameserver 192.168.2.1
> >> dns-search dmcghome
> >> wireless-essid dmcghome
> >>
> >> auto wlan0
> >>
> >>
> >> I had to comment out eth0 because for some odd reason, I couldn't
> >> connect to wlan0 with the eth0 info in the file
> >
> > I think the odd reason is that both eth0 and wlan0 would be on the same
> > network, i.e. 192.168.2.0. If you don't have your eth0 connected, the
> > network seems to be unreachable because data are sent on either eth0 or
> > wlan0 but not on both at the same time. That is the disadvantage of
> > static entries if your hardware connection isn't static. You have to
> > enable / disable the interfaces manually if they aren't connected.
> >
> >> Without this info in the file, Internet wouldn't work for me.
> >
> > Then you didn't try to use networkmanager or wicd lately, they don't
> > need static entries in the interfaces file. And they can handle
> > switching wired/wireless more or less automatically.
> >
> >> I doubt this will help, but I hope it does.
> >
> > At least it is always interesting to see how others have solved their
> > network problems. Fortunately Bruce seems to have his machine working in
> > the meantime.
> >
> >
> > Nils





More information about the kubuntu-users mailing list