Reconnect to wireless network after boot

Questions about WIFI networks and devices
Forum rules
Before you post please read how to get help
Stjert
Level 1
Level 1
Posts: 8
Joined: Fri Oct 03, 2008 3:05 am

Reconnect to wireless network after boot

Post by Stjert » Fri Oct 03, 2008 3:53 am

I have installed Linux Mint (Elyssa) and everything is fine. After a lot of fuzz I got my USB-Wifi to connect to my network. But after a boot or after I've turned the PC off I have to manually connect to my network again. This is very annoying since my kids are using the PC and therefor need assistance everytime the turn it on. Does anyone have an idea on how to fix this ?

Following is the result of sudo /usr/lib/linuxmint/mintWifi/mintWifi.py


* I. scanning WIFI PCI devices...
-------------------------
* II. querying ndiswrapper...
smc2862w : driver installed
device (1260:EE22) present
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"MCFC"
Mode:Managed Frequency:2.412 GHz Access Point: 00:1E:E5:6D:C3:89
Bit Rate=54 Mb/s Tx-Power:17 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:XXXXXXXXXXXXXXXXXXXXXXXXXXX Security mode:restricted
Power Management:off
Link Quality:50/100 Signal level:-64 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 00:0b:db:80:3c:00
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Base address:0xdf40 Memory:feae0000-feb00000

eth0:avahi Link encap:Ethernet HWaddr 00:0b:db:80:3c:00
inet addr:169.254.4.50 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Base address:0xdf40 Memory:feae0000-feb00000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:88 errors:0 dropped:0 overruns:0 frame:0
TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4400 (4.2 KB) TX bytes:4400 (4.2 KB)

wlan0 Link encap:Ethernet HWaddr 00:12:bf:10:03:c1
inet addr:192.168.2.103 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16444 errors:0 dropped:0 overruns:0 frame:0
TX packets:15384 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15600766 (14.8 MB) TX bytes:2422370 (2.3 MB)

-------------------------
* V. querying DHCP...
sudo: unable to resolve host guro-desktop
There is already a pid file /var/run/dhclient.pid with pid 6038
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:12:bf:10:03:c1
Sending on LPF/wlan0/00:12:bf:10:03:c1
Listening on LPF/eth0/00:0b:db:80:3c:00
Sending on LPF/eth0/00:0b:db:80:3c:00
Sending on Socket/fallback
DHCPREQUEST of 192.168.2.103 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.2.103 from 192.168.2.1
bound to 192.168.2.103 -- renewal in 32516 seconds.
-------------------------
* VI. querying nslookup google.com...
Server: 217.13.4.24
Address: 217.13.4.24#53

Non-authoritative answer:
Name: google.com
Address: 64.233.187.99
Name: google.com
Address: 72.14.207.99
Name: google.com
Address: 209.85.171.99

Husse
Level 23
Level 23
Posts: 18701
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Re: Reconnect to wireless network after boot

Post by Husse » Fri Oct 03, 2008 7:15 am

I've never heard of smc2862w
It seems it's using a prism chip
You should not have to manually turn it on after a reboot - how did you install it? (exactly)
Run lsusb and post the result - this way we may find out what it is
Perhaps you need to run sudo lsusb -v to get more details
We need more info
Image
Don't fix it if it ain't broken, don't break it if you can't fix it

Stjert
Level 1
Level 1
Posts: 8
Joined: Fri Oct 03, 2008 3:05 am

Re: Reconnect to wireless network after boot

Post by Stjert » Fri Oct 03, 2008 10:19 am

Thanks for trying to help. I an completely new to Linux :?

I used ndiswrapper to install the driver to SMC2862. A USB WiFi card.

See the enclosed output from lsusb:

Bus 005 Device 003: ID 1260:ee22
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 004: ID 0461:4d15 Primax Electronics, Ltd
Bus 001 Device 001: ID 0000:0000

I will enclose the output from sudo lsusb -v :
(When running this I have to restart the computer to get on net again)

Bus 005 Device 003: ID 1260:ee22
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1260
idProduct 0xee22
bcdDevice 1.00
iManufacturer 1 17
iProduct 2 802.11g Wireless USB Adapter
iSerial 3 1260-EE22
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 53
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 5
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

Bus 005 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.24-19-generic ehci_hcd
iProduct 2 EHCI Host Controller
iSerial 1 0000:00:1d.7
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Hub Descriptor:
bLength 11
bDescriptorType 41
nNbrPorts 8
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 10 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00 0x00
PortPwrCtrlMask 0xff 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0503 highspeed power enable connect
Port 3: 0000.0100 power
Port 4: 0000.0100 power
Port 5: 0000.0100 power
Port 6: 0000.0100 power
Port 7: 0000.0100 power
Port 8: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled

Bus 004 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.24-19-generic uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled

Bus 003 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.24-19-generic uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.2
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled

Bus 002 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.24-19-generic uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled

Bus 001 Device 004: ID 0461:4d15 Primax Electronics, Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0461 Primax Electronics, Ltd
idProduct 0x4d15
bcdDevice 2.00
iManufacturer 0
iProduct 2 USB Optical Mouse
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 52
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered)

Bus 001 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.24-19-generic uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0303 lowspeed power enable connect
Port 2: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled

Husse
Level 23
Level 23
Posts: 18701
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Re: Reconnect to wireless network after boot

Post by Husse » Fri Oct 03, 2008 12:54 pm

Normally the id # of the device (0461:4d15) leads you to a list of useful hits, but not in this case
It seems it's been sitting there while people have had all sorts of problems with other devices so I find myself reading about cameras and printers and....
Anyway red the wifi wiki
http://www.linuxmint.com/wiki/index.php/MintWifi
I think you have somehow forgotten this step
http://www.linuxmint.com/wiki/index.php ... hing_works
Image
Don't fix it if it ain't broken, don't break it if you can't fix it

Stjert
Level 1
Level 1
Posts: 8
Joined: Fri Oct 03, 2008 3:05 am

Re: Reconnect to wireless network after boot

Post by Stjert » Fri Oct 03, 2008 2:12 pm

After "sudo ndiswrapper -m" I get the following:

module configuration already contains alias directive

What now ?

Husse
Level 23
Level 23
Posts: 18701
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Re: Reconnect to wireless network after boot

Post by Husse » Fri Oct 03, 2008 3:44 pm

already contains alias directive
Fine - it's already done
Check /etc/modules for ndiswrapper - if it's absent:
Add the following line to /etc/modules: (gksu gedit /etc/modules)

ndiswrapper
Image
Don't fix it if it ain't broken, don't break it if you can't fix it

Stjert
Level 1
Level 1
Posts: 8
Joined: Fri Oct 03, 2008 3:05 am

Re: Reconnect to wireless network after boot

Post by Stjert » Fri Oct 03, 2008 3:56 pm

Thanks again for taking care of my petty problems. It is much appreciated. :D

I have added a new line so that the file looks like this:

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

fuse
lp
ndiswrapper

Is this how it should look ?

Husse
Level 23
Level 23
Posts: 18701
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Re: Reconnect to wireless network after boot

Post by Husse » Fri Oct 03, 2008 4:14 pm

yes
Image
Don't fix it if it ain't broken, don't break it if you can't fix it

Stjert
Level 1
Level 1
Posts: 8
Joined: Fri Oct 03, 2008 3:05 am

Re: Reconnect to wireless network after boot

Post by Stjert » Fri Oct 03, 2008 4:56 pm

Well. I rebooted and I still had to "Connect to other network" by typing in SSID and password. Thanks anyway

Now I've put the kids to bed so the computer is not available. But further advice is most welcome. I will check again tomorrow.

Husse
Level 23
Level 23
Posts: 18701
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Re: Reconnect to wireless network after boot

Post by Husse » Sat Oct 04, 2008 9:19 am

I'll add this to my list of unsolved topics and come back to you (fairly soon)
It sort of works so you are not "stranded" as some other poor guys
Image
Don't fix it if it ain't broken, don't break it if you can't fix it

Stjert
Level 1
Level 1
Posts: 8
Joined: Fri Oct 03, 2008 3:05 am

Re: Reconnect to wireless network after boot

Post by Stjert » Sat Oct 04, 2008 10:01 am

Thanks for your help so far. I guess I will have to make a guide on how to connect for the kids.

Husse
Level 23
Level 23
Posts: 18701
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Re: Reconnect to wireless network after boot

Post by Husse » Sun Oct 05, 2008 11:00 am

Hmm this is not a problem with ndiswrapper - it can happen that the focus changes I have way to many posts to remember much about any of them.
This is a problem with the keyring and should not occur in Elyssa
It's unfortunately normal that you may have to make a couple of attempts to connect before success, but that should just be left clicking on "Network manager" and select your wifi. "Network manager" is the applet with two monitors down by the clock
This of course makes me wonder how you connect
Do you use "Roaming mode"?
In the Control Center > Network > Properties you can enable roaming mode
If you did not have it enabled before you will be asked for credentials when you left click on "Network manager" and select your wifi.
This should be the first and only time - I have never tried the other option so I don't know what happens then
If this does not work tell me what you find in Control Center > Encryption and Keyrings
Not that I really think it has anything to do with it, but just in case
Image
Don't fix it if it ain't broken, don't break it if you can't fix it

Stjert
Level 1
Level 1
Posts: 8
Joined: Fri Oct 03, 2008 3:05 am

Re: Reconnect to wireless network after boot

Post by Stjert » Thu Oct 09, 2008 1:08 pm

Do you use "Roaming mode"?

If this does not work tell me what you find in Control Center > Encryption and Keyrings
____________________________________________________________________________
Yes. Roaming mode is enabled


Encryption and Keyrings
Password and keyrings: login Automatically unlocked
Encryption: None Prompt for a key
PGP Passphrases: Never remember

Husse
Level 23
Level 23
Posts: 18701
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Re: Reconnect to wireless network after boot

Post by Husse » Thu Oct 09, 2008 4:04 pm

Beats me completely - I'm beginning to suspect the driver
To be sure - is there anything odd with the hardware and/or software?
Image
Don't fix it if it ain't broken, don't break it if you can't fix it

Stjert
Level 1
Level 1
Posts: 8
Joined: Fri Oct 03, 2008 3:05 am

Re: Reconnect to wireless network after boot

Post by Stjert » Thu Oct 09, 2008 4:36 pm

I haven't noticed anything odd, but then again I am quite new to the world of Linux. :wink:

Husse
Level 23
Level 23
Posts: 18701
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Re: Reconnect to wireless network after boot

Post by Husse » Thu Oct 09, 2008 7:21 pm

Run

Code: Select all

lsmod | grep p54usb
p54usb is an alternate driver - it may conflict with the ndiswrapper one...
Image
Don't fix it if it ain't broken, don't break it if you can't fix it

GTengineer
Level 1
Level 1
Posts: 4
Joined: Sun May 04, 2008 10:58 am

Re: Reconnect to wireless network after boot

Post by GTengineer » Sat Oct 11, 2008 2:38 pm

hi guys,

I just upgraded to Mint 5.0 (from 4.0) and I am having the same problem. It is actually a problem with encryption because when I use no encryption on my wireless router then it connect just fine after a reboot. Also WEP doesn't seem to work period, I am using WPA but the reboot and no connection problem continues.

GTengineer
Level 1
Level 1
Posts: 4
Joined: Sun May 04, 2008 10:58 am

Re: Reconnect to wireless network after boot

Post by GTengineer » Sat Oct 11, 2008 2:45 pm

Husse wrote:Run

Code: Select all

lsmod | grep p54usb
p54usb is an alternate driver - it may conflict with the ndiswrapper one...

Just tried this and it worked. Thanks Husse. WEP still not working but I have no problems using WPA. Hopefully this will be fixed in the future though.

Husse
Level 23
Level 23
Posts: 18701
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Re: Reconnect to wireless network after boot

Post by Husse » Sat Oct 11, 2008 4:59 pm

GTengineer I suppose you are no newbie but to help the newbie that started the topic I'll post what I suppose you did - blacklisted p54usb

Code: Select all

echo "blacklist p54usb" | sudo tee -a /etc/modprobe.d/blacklist
Image
Don't fix it if it ain't broken, don't break it if you can't fix it

GTengineer
Level 1
Level 1
Posts: 4
Joined: Sun May 04, 2008 10:58 am

Re: Reconnect to wireless network after boot

Post by GTengineer » Sat Oct 11, 2008 10:56 pm

Husse wrote:GTengineer I suppose you are no newbie but to help the newbie that started the topic I'll post what I suppose you did - blacklisted p54usb

Code: Select all

echo "blacklist p54usb" | sudo tee -a /etc/modprobe.d/blacklist
Husse, actually I am a newbie. I have been using various distros for about a year but mainly I am just a "user". I thought the problem was fixed but it is not. I tried doing what you suggested above and it gives me an error while booting (then continues to main screen) and the wireless problem continues. If I cannot solve this I will have to go back to Mint 4.0 :(

Post Reply

Return to “Wireless”