wireless network connections on Kubuntu 8.04.1

0 views
Skip to first unread message

Lisi Reisz

unread,
Sep 13, 2008, 5:55:20 AM9/13/08
to kubunt...@lists.ubuntu.com
I have a MSI 802.11g PCMCIA WiFi card with the Ralink RT2500 Chipset in a Dell
Latitude p4 connecting - or failing to connect :-( - via a Netgear DG834G v4
wireless ADSL modem router.

When I first installed Hardy, the wireless card was recognised and both green
lights were on, but it could only connect with static IP. After numerous
attempts over several days, in desperation I tried manually
editing /etc/network/interfaces. Still no joy. I tried a few different
combinations, including finally deleting /etc/network/interfaces and letting
Kubuntu regenerate it.

So I installed linux-backports-modules-hardy-generic. One of the green lights
went out and it would now not connect at all, even tho' network settings
could still see it.

So I uninstalled linux-backports-modules-hardy-generic (apt-get purge
linux-backports-modules-hardy-generic, aptget autoremove). Now the lights
are both on, but there is no actual connection.

I tried pinging the router. All packets were dropped. I pinged the laptop
from the router and all packets reached their destination. So I pinged the
router from the laptop. Nada. So I again pinged the laptop from the router.
This time nothing. And that is still the situation.

I also tried connecting the ethernet connection via DHCP. It would work only
if I told it the DNS to use - it could not get the information from the
server. Not much use for roving!! But the wrieless card could not even get
an IP from the router.

Suggestions? I'll try anything, short of throwing the whole lot through the
window. I have to get wireless DHCP going on this laptop. :-(

TIA
Lisi

--
kubuntu-users mailing list
kubunt...@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

Robert Costa

unread,
Sep 13, 2008, 6:51:27 AM9/13/08
to Kubuntu Help and User Discussions
Hi Lisi,

can you post the contents of your /etc/network/interfaces file and
maybe the output of the lspci command and lsmod, just in case no
drivers are running the WiFi card. hmm.. if it's a driver problem you
could also try out installing ndiswrapper and using the manufacturers
drivers, but of cause that's not an option if you want to stay on
linux native drivers :-)...

Cya,
Robert.

2008/9/13 Lisi Reisz <lisi....@gmail.com>:

--
Was man zu verstehen gelernt hat, das fürchtet man nicht mehr.

Lisi Reisz

unread,
Sep 13, 2008, 8:26:09 AM9/13/08
to Kubuntu Help and User Discussions
Hi, Robert,

Saturday 13 September 2008 11:51:27 に Robert Costa さんは書きました:


> 2008/9/13 Lisi Reisz <lisi....@gmail.com>:
> > I have a MSI 802.11g PCMCIA WiFi card with the Ralink RT2500 Chipset in a
> > Dell Latitude p4 connecting - or failing to connect :-( - via a Netgear
> > DG834G v4 wireless ADSL modem router.

> can you post the contents of your /etc/network/interfaces file and


> maybe the output of the lspci command and lsmod, just in case no
> drivers are running the WiFi card. hmm.. if it's a driver problem you
> could also try out installing ndiswrapper and using the manufacturers
> drivers, but of cause that's not an option if you want to stay on
> linux native drivers :-)...

Herewith. The /etc/network/interfaces file has been generated by Kubuntu, and
I currently have the Ralink configured to static. When it is configured to
DHCP it vanishes from /etc/network/interfaces.

The 3 things together are rather long, I'm afraid. I'd better say thank you
here at the beginning! So, thank you :-).
Lisi

**/etc/network/interfaces**

iface eth0 inet static
address 192.168.0.7
netmask 255.255.255.0
gateway 192.168.0.1

auto eth0

iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto lo


iface wlan0 inet static
address 192.168.0.8
netmask 255.255.255.0
gateway 192.168.0.1
wireless-essid Chitose

auto wlan0

------------------------------------------------------
***lspci***

root@localhost:/home/user# lspci
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host
Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge
(rev 04)
00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB Controller #1 (rev
02)
00:1d.2 USB Controller: Intel Corporation 82801CA/CAM USB Controller #3 (rev
02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio
Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801CA/CAM AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 440 Go]
(rev a3)
02:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev
78)
02:01.0 CardBus bridge: Texas Instruments PCI4451 PC card Cardbus Controller
02:01.1 CardBus bridge: Texas Instruments PCI4451 PC card Cardbus Controller
02:01.2 FireWire (IEEE 1394): Texas Instruments PCI4451 IEEE-1394 Controller
07:00.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
root@localhost:/home/user#

-------------------------------------------------------------------------
****lsmod****

root@localhost:/home/user# lsmod
Module Size Used by
rfcomm 41744 2
l2cap 25728 13 rfcomm
bluetooth 61156 4 rfcomm,l2cap
ppdev 10372 0
speedstep_ich 6288 0
speedstep_lib 6532 1 speedstep_ich
cpufreq_ondemand 9740 1
cpufreq_powersave 2688 0
cpufreq_stats 7104 0
freq_table 5536 3 speedstep_ich,cpufreq_ondemand,cpufreq_stats
cpufreq_userspace 5284 0
cpufreq_conservative 8712 0
container 5632 0
sbs 15112 0
sbshc 7680 1 sbs
dock 11280 0
iptable_filter 3840 0
ip_tables 14820 1 iptable_filter
x_tables 16132 1 ip_tables
aes_i586 33536 0
dm_crypt 15364 0
dm_mod 62660 1 dm_crypt
sbp2 24072 0
lp 12324 0
arc4 2944 2
ecb 4480 2
blkcipher 8324 1 ecb
rt2500pci 20352 0
rt2x00pci 11264 1 rt2500pci
rt2x00lib 22528 2 rt2500pci,rt2x00pci
rfkill 8592 1 rt2x00lib
input_polldev 5896 1 rt2x00lib
crc_itu_t 3072 1 rt2x00lib
mac80211 165652 3 rt2500pci,rt2x00pci,rt2x00lib
cfg80211 15112 1 mac80211
eeprom_93cx6 3200 1 rt2500pci
pcmcia 40876 0
ipv6 267780 8
video 19856 0
output 4736 1 video
snd_intel8x0 35356 3
snd_ac97_codec 101028 1 snd_intel8x0
ac97_bus 3072 1 snd_ac97_codec
snd_pcm_oss 42144 0
snd_mixer_oss 17920 1 snd_pcm_oss
snd_pcm 78596 4 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_seq_dummy 4868 0
yenta_socket 27276 3
rsrc_nonstatic 13696 1 yenta_socket
serio_raw 7940 0
pcmcia_core 40596 3 pcmcia,yenta_socket,rsrc_nonstatic
i2c_core 24832 0
button 9232 0
battery 14212 0
snd_seq_oss 35584 0
snd_seq_midi 9376 0
ac 6916 0
snd_rawmidi 25760 1 snd_seq_midi
parport_pc 36260 1
parport 37832 3 ppdev,lp,parport_pc
irda 203068 0
dcdbas 9504 0
evdev 13056 5
snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi
crc_ccitt 3072 1 irda
snd_seq 54224 6
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 24836 3 snd_pcm,snd_seq
snd_seq_device 9612 5
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
intel_agp 25492 1
snd 56996 15
snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 8800 1 snd
shpchp 34452 0
pci_hotplug 30880 1 shpchp
agpgart 34760 1 intel_agp
iTCO_wdt 13092 0
iTCO_vendor_support 4868 1 iTCO_wdt
snd_page_alloc 11400 2 snd_intel8x0,snd_pcm
pcspkr 4224 0
psmouse 40336 0
ext3 136712 3
jbd 48404 1 ext3
mbcache 9600 1 ext3
sg 36880 0
sr_mod 17956 0
cdrom 37408 1 sr_mod
sd_mod 30720 5
ata_generic 8324 0
ata_piix 19588 4
floppy 59588 0
ohci1394 33584 0
pata_acpi 8320 0
ieee1394 93752 2 sbp2,ohci1394
uhci_hcd 27024 0
3c59x 46376 0
mii 6400 1 3c59x
libata 159344 3 ata_generic,ata_piix,pata_acpi
scsi_mod 151436 5 sbp2,sg,sr_mod,sd_mod,libata
usbcore 146028 2 uhci_hcd
thermal 16796 1
processor 36872 2 thermal
fan 5636 1
fbcon 42912 0
tileblit 3456 1 fbcon
font 9472 1 fbcon
bitblit 6784 1 fbcon
softcursor 3072 1 bitblit
fuse 50708 1
root@localhost:/home/user#


> > When I first installed Hardy, the wireless card was recognised and both
> > green lights were on, but it could only connect with static IP. After
> > numerous attempts over several days, in desperation I tried manually
> > editing /etc/network/interfaces. Still no joy. I tried a few different
> > combinations, including finally deleting /etc/network/interfaces and
> > letting Kubuntu regenerate it.
> >
> > So I installed linux-backports-modules-hardy-generic. One of the green
> > lights went out and it would now not connect at all, even tho' network
> > settings could still see it.
> >
> > So I uninstalled linux-backports-modules-hardy-generic (apt-get purge
> > linux-backports-modules-hardy-generic, aptget autoremove). Now the
> > lights are both on, but there is no actual connection.
> >
> > I tried pinging the router. All packets were dropped. I pinged the
> > laptop from the router and all packets reached their destination. So I
> > pinged the router from the laptop. Nada. So I again pinged the laptop
> > from the router. This time nothing. And that is still the situation.
> >
> > I also tried connecting the ethernet connection via DHCP. It would work
> > only if I told it the DNS to use - it could not get the information from
> > the server. Not much use for roving!! But the wrieless card could not
> > even get an IP from the router.
> >
> > Suggestions? I'll try anything, short of throwing the whole lot through
> > the window. I have to get wireless DHCP going on this laptop. :-(

--

Lisi Reisz

unread,
Sep 13, 2008, 8:34:42 AM9/13/08
to Kubuntu Help and User Discussions
Saturday 13 September 2008 11:51:27 に Robert Costa さんは書きました:
> Hi Lisi,
>
> can you post the contents of your /etc/network/interfaces file and
> maybe the output of the lspci command and lsmod, just in case no
> drivers are running the WiFi card. hmm..

Robert you have traced it for me already!
<https://bugs.launchpad.net/ubuntu/hardy/+source/linux-ubuntu-modules-2.6.24/+bug/134660>

> if it's a driver problem you
> could also try out installing ndiswrapper and using the manufacturers
> drivers, but of cause that's not an option if you want to stay on
> linux native drivers :-)...

I'm open to all suggestions. Download a non-free driver, buy another card
that is known to work. Anything. If I don't get wireless going on dhcp this
week, my granddaughter is going to desert to Windows. :-((

I shall try the route suggested on that web page as soon as I have joined
Arthur in a nice hot cup of tea. I need fortifying. ;-)

Lisi.

Derek Broughton

unread,
Sep 15, 2008, 9:30:18 AM9/15/08
to kubunt...@lists.ubuntu.com
Lisi Reisz wrote:

> Saturday 13 September 2008 11:51:27 に Robert Costa さんは書きました:

>> can you post the contents of your /etc/network/interfaces file and
>

> Herewith. The /etc/network/interfaces file has been generated by Kubuntu,
> and
> I currently have the Ralink configured to static. When it is configured
> to DHCP it vanishes from /etc/network/interfaces.

As it should. How did you get Kubutu to "generate" this - I've never known
it to generate static interfaces, you have to do that.


>
> iface wlan0 inet static
> address 192.168.0.8
> netmask 255.255.255.0
> gateway 192.168.0.1
> wireless-essid Chitose

This should not be here - it's turning off Network Manager.
--
derek

Lisi Reisz

unread,
Sep 15, 2008, 3:32:43 PM9/15/08
to kubunt...@lists.ubuntu.com
Monday 15 Sep 2008 14:30:18 に Derek Broughton さんは書きました:

> Lisi Reisz wrote:
> > Saturday 13 September 2008 11:51:27 に Robert Costa さんは書きました:
> >> can you post the contents of your /etc/network/interfaces file and
> >
> > Herewith. The /etc/network/interfaces file has been generated by
> > Kubuntu, and
> > I currently have the Ralink configured to static. When it is configured
> > to DHCP it vanishes from /etc/network/interfaces.
>
> As it should. How did you get Kubutu to "generate" this - I've never known
> it to generate static interfaces, you have to do that.
>
> > iface wlan0 inet static
> > address 192.168.0.8
> > netmask 255.255.255.0
> > gateway 192.168.0.1
> > wireless-essid Chitose
>
> This should not be here - it's turning off Network Manager.

It was put there by Network Manager. I deleted the whole network interfaces
file and let Network Manager regenerate it as it wished, or didn't wish. All
that information was answers I gave to questions in Network Manager. I did
nothing to the interfaces file except read it. And I posted it in answer to
a question.

I am finding Network Manager a nightmare. :-( Give me an editable interfaces
file any day. But Kubuntu is willing to accept Japanese input from the
keyboard, albeit only in K apps. So I have somehow got to live with this.

Anyhow, thanks for your reply. I am about to try NDISwrapper and the Windows
driver.

Or can anyone recommend a wireless chipset that Kubuntu can run on DHCP otb?

Lisi

Lisi Reisz

unread,
Sep 16, 2008, 4:50:24 AM9/16/08
to Kubuntu Help and User Discussions
Monday 15 Sep 2008 20:32:43 に Lisi Reisz さんは書きました:

> I am finding Network Manager a nightmare. :-(  Give me an editable
> interfaces file any day.

Googling leads me to suppose that I can remove Network Manager.

Has anyone any ( helpful ;-0 ) comments?

TIA

Lisi Reisz

unread,
Sep 16, 2008, 5:17:47 AM9/16/08
to Kubuntu Help and User Discussions
Tuesday 16 Sep 2008 09:50:24 に Lisi Reisz さんは書きました:

> Monday 15 Sep 2008 20:32:43 に Lisi Reisz さんは書きました:
> > I am finding Network Manager a nightmare. :-(  Give me an editable
> > interfaces file any day.
>
> Googling leads me to suppose that I can remove Network Manager.
>
> Has anyone any ( helpful ;-0 ) comments?

In part answer to my own question, I have found this:
<http://ubuntuforums.org/showthread.php?t=385975&page=3>

But I would still value comments, particularly on the best way to go to retain
any advantages that Network Manager may have, but wrest networking from its
grasp.

Reply all
Reply to author
Forward
0 new messages