Debian Configuration :: Wlan0 Gets Deactivated While Login
May 13, 2010
From yesterday on, I am not able to connect my Laptop to my WiFi Router automatically when logging in to gnome desktop.
The following is the message found in /var/log/messages.
Its Lenny 5.0.4 and I can see my wifi LED ON till the gdm login page. After the login, while loading my desktop, the LED goes OFF and I have to restart the network-manager for enabling the wifi again. Why is this happening? Do I have to change the configuration settings in /etc/dbus-1/system.d/ to fix this. I really don't know what change needs to be done there and where.
The same day when this problem started while logging in I got an error message from nautilus. The screen-shot is attached with this mail. Does this error have anything to do with the network issue?
I had one of those random system deaths, so reinstalled squeeze (daily netinst image I think...) on my eee 1000, which uses an rt2860 wireless chip. The new install only installed 2.6.32, which I had been avoiding using because of a few problems, including it dealing with networking slightly differently. I couldn't get it to work - even without encryption - using wicd. Having had a read of [URL]... , I had a look at /etc/network/interfaces, which read; This file describes the network interfaces available on your system and how to activate them. For more information, see interfaces(5).
[code]...
ra0 is now called wlan0, as far as I'm aware. I've read in several places that it is best to expunge this file of all references to wifi, so I removed the bottom section (after '# The primary network interface'). I still got nothing. However, if I go ahead and change the 'ra0's to 'wlan0's, it seems to work - wicd connects. Not very familiar with Debian (spent more time on SUSE. Drop your tomatoes - I like it. Any idea what is happening? Is what I'm doing wrong? Conversely, is the file wrong? Should it be reported? Against which package? Including any particular files?
I've recently installed Debian. But the wireless network is not working. In Gnome it says "Device not configured" And if i try a ifup it says: root@accroft-msi:/home/accroft# ifup wlan0Internet Systems Consortium DHCP Client 4.1.1-P1Copyright 2004-2010 Internet Systems Consortium.All rights reserved.
Listening on LPF/wlan0/My mac address here Sending on LPF/wlan0/My mac address here Sending on Socket/fallback
I'm having problems getting my wireless network working. The same problem exists in both Debian 5.04 and Ubuntu 8.04. I'm using a Sonet ZEW2500P USB wireless card, which shows up when I look at lsusb. The card works under Windows, so its not a hardware problem.
When I run iwconfig, wlan0 simply doesn't show up on the list. It doesn't go by any other name either. I've tried adding iface wlan0 inet dhcp auto wlan0 to my /etc/network/interfaces file, but to no effect. I've tried using both the rt2000usb driver and the old rt2570 driver, and made sure both are not loaded at the same time using lsmod, but this doesn't help.
I wanted to try the CONFIG_NET_RADIO enable/rebuild kernel technique, but I can't find CONFIG_NET_RADIO anywhere in my autoconf.h file!
I assume someone will want to see a log file of some kind - just let me know which one (and where I can find it).
This is embarrassing. I can't get a wireless address from my router with dhclient. The distribution is sid/lxde/liquorix kernel with no network manager on /dev/sdb1.
root@sid:/home/jheaton5# dhclient -4 -v wlan0 Internet Systems Consortium DHCP Client 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium.
I am very new to linux.I have a network camera which only has an Ethernet port but no WiFi. Sadly no Ethernet port is available close to the camera.
Therefore I now bought a raspberry pi and installed raspbian to create a bridge into the wireless network, for connecting the camera to the internet.I now played around with the interface- and bridge configuration but I have problems with it.This is how my interfaces file looks like:
(The WiFi is secured with WPA2 Enterprise)
Code: Select all# interfaces(5) file used by ifup(8) and ifdown(8)
# Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d
[code]....
The WiFi is connection works fine and I am in the internet using the WiFi.But I am wondering about eth0. The network parameters I specified are not the same as the parameters ifconfig tells me.Ip, Broadcast, Mask, nothing is as specified.It would be nice to give the camera a static IP that I can access it always with the same IP from the RaspberryPi.The Raspberry Pi itself gets always a new IP from the WiFi network. How do I get the camera into the internet using the existing connection of the Pi?
I've installed firmware-iwlwifi I've modprobe -r'd and modprobed the iwlagn module I CAN scan, using iwlist wlan0 scanning, and I can see my essid, hovering in the distance. it is definitely broadcasting.
I use wicd and wicd-curses. No wireless show up in wicd-curses. ifup wlan0 gives me no dhcp offers received and slumbers again. from iwconfig:
wlan0 IEEE 802.11abgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off from lspci: 03:00.0 Network controller: Intel Corporation WiFi Link 5100
Hardware: Toshiba Satellite A505D-S6958 Wireless: Realtek 8192e Ubuntu 10.04, x86
lspci
I was using ndsiwrapper with XP driver, but always prefer to Linux drivers if they are available. So, I emailed Realtek web support and they sent me latest drivers for Ubuntu 10.04. I followed their instructions and it works great! With, the exception of, I have to run ./wlan0up each time after I login to start the wireless.
I seem to remember having to modify a file some place, which was very easy to do, but for the life of me I cannot seem to remember what it was or what to put into it? and also, how do you tell if your wireless card is making use of the "n" speed, if the network your are on has it available?
I have a strange issue that I cannot put my finger on. Recently,I installed a new Ubuntu 10.04 server. No extra software yet, apart from openssh-server. The wired connection (eth1) works fine. I then added a wireless card with chipset p54pci, which appears to work with the wext driver. Configured /etc/wpa_supplicant, and /etc/network/interfaces as well:
This is wpa_supplicant:
Code:
This is interfaces:
Code:
After a reboot the machine comes up with both NICs active.
If I do a ssh from another Ubuntu machine to this machine (to 192.168.2.100, so the wired address) it takes about 30 seconds before I get the login as: prompt.
If I change the interfaces file so that wlan0 is not started (I comment out the line auto wlan0, and reboot), connecting from another machine with ssh alsmost instantly gives me te login prompt.
I tried switching the order of both NICs in the interfaces file. Also tried changing the sshd config file so that it only listens on the wired ip address. Both did not help.
Does anyone have a clue why logging in with ssh from another machine is very much slower in response with wlan0 activated than without ?
the PC just hangs for ever. No mouse movement, ctrl-alt-del, nothing.
I have downloaded a Linux driver from Realtek but it will not compile. I have the latest kernel-devel, headers, and gcc. I can post compiler errors if anybody would like. They're all apparently to do with missing parameters.
I'm new to the world of linux I've started using it just one week ago.I installed Debian Lenny without problem, and after 2 or 3 days managed to make my wifi and ATI card to work. Today I tried installing compiz, through the packet manager that comes with the system. It was downloaded and installed successfully, so I rebooted to see it effects (I guess) but after that, I wasn't able to get to the login screen anymore, it just gets stuck at the "gray" screen before that (I took a pic of what screen i'm talkin about). Then I accessed in console mode and removed all the compiz packages, tried dpkg-reconfigure gnome and gnome-core, then reinstalled the ati drivers, but the problem is still there.I don't want to reinstall the whole system, I don't think a simple problem like this is enough to do so, but sincerely I'm completly lost.
We have setup Squeeze a Test machine , just for some tests, without network, Internet etc. and we need to allow root login in Gnome. We've changed /etc/gdm3/daemon.conf:[security] AllowRoot=truebut still doesn't work.
So I have this laptop with a busted battery, I'm trying to get it into some kind of headless server, media topbox hybrid.
First thing I want to do is being able to leave it shut (powered on) in the corner without having to interact with it directly.
I've setup ssh and vnc so to login remotely and do task, transfer files and etc.
However there is a little issue with the laptop lid down upon turning it on, it immediately goes into suspend when getting to the display manager, which is 'lightdm'.
I suppose this is the default setting for Xorg and as such my custom configs for KDE only kick in after I login.
Question is: I never seen configuration for default power management stuff being done in Xorg, is there some way to disable automatic suspension on lid down?
Another question is: After the KDE kicks in does it always replace power options? I have setup a xorg.conf file specifying dpms options but these don't seem to remain.
I'm working on embedded debian. I do configuration to lightdm for autologin. My device start with autologin but sometimes I see login screen. ı will try it more than 20 times. 17 times its do autologin 3 times not do autologin and show login screen.
I'm testing to log in using openldap authentication on jessie by following article from [URL] ..... and when I try to log in from ldap client (another debian 8 VM), it failed with
Code: Select allFeb 3 09:25:33 clt nscd: nss_ldap: could not connect to any LDAP server as cn=admin,dc=test,dc=lab - Can't contact LDAP server Feb 3 09:25:33 clt nscd: nss_ldap: failed to bind to LDAP server ldap:///192.168.191.120: Can't contact LDAP server Feb 3 09:25:33 clt nscd: nss_ldap: reconnecting to LDAP server... Feb 3 09:25:33 clt nscd: nss_ldap: could not connect to any LDAP server as cn=admin,dc=test,dc=lab - Can't contact LDAP server
After fossicking around I can not find anything around that I can invoke in a terminal to configure settings in network-manager. The applet(?) on the task bar doesn't ask for a login, so options are grey/grayed out. The "program" in the applications menu is similarly grey/grayed out.
If it was a once off, then I suspect that it would be simple as login as root to start X, but I have a series of config files to edited each time of their initial use. also, there is the ongoing problem of vpn target switching.
woops; wheezy with xfce4 and everything is uptodate.
I removed my .gnome and .nautilus folders and .notifier file. it is working now. I do not know exactly which of these 3 fixed it but I hope this might help someone else!I have some major issue with nautilus which is preventing me from loogging in into my system which is kind of criticle this weekend.I'm running Squeeze with latest updates.
The problem:Today gnome gave some problems caus my taskbar was suddently gone. I couldn't get it back to i reinstall gnome-desktop and updated my whole system. At the update some yes/no questions on a blue screen asking me to restart cups etc had corrupted yes/no buttons. Weird character sets were shown. Well that can happen sometimes i thought.After reinstalling gnome i can't login anymore. My screen keeps flashing while it shows the loading icon of the mouse.Anyone got suggestions? I can't find similar problems on the internet, only problems that happen while already logged in. In my case the segfault prevents gdm starting! Maurice
i've written a bash script to add new users to our system. the script works so I won't bother you all about that. when a new user is created with it, they can immediately login to our domain from any terminal, which is good. However, the newly created user is unable to login to debian at all, and so cannot access the server. when attempting to do so, they get a message like "the system administrator has disabled your account". This is a good thing really as normal users have no need for debian login, but I do need to add a few admin users who will need direct access to the server machine.
This is the code I'm using to add the user. The rest of my script is just a wrapper and GUI. I figure the login shell may have something to do with it, so I tried changing the shell of a user to the default /bin/bash. This resulted in the user being able to login - sort of. Gnome doesn't load though, and there's a cascade of errors across the screen about things failing to save or load settings. mostly stuff like nautilus, X, and gnome. the desktop background is black and there's no interface. Logging in with a previously existing account works fine though. Clearly I have an issue somewhere.
I have one of my user's home directory on a seperate partition, and I was wondering if there was a way to only mount it when/if the user is logged in and unmount it if they log out.
I have squeeze with gnome. Various apps let me log in as root when needed to but if I logout as a user and try to login as root it won't let me (won't authenticate password). I had this problem before and reinstalled Debian and definitely checked for it to allow me to do this and it worked for a while after new install. Apparently some update overrode my preferences. This is a major defect and may force me to abandon Debian. I don't use root often but I don't have any use for a operating system that won't let me use it. Anyone know how to correct this. I am not interested in using a terminal on a regular basis or ever for that matter.
I have just setup a debian box, and I want to be able to login to the machine remotely.Currently I have the following setup:Cable Modem -> Netgear Router (DHCP to outside world) -> Debian Box (DHCP for internal network)As I under stand it I have to set my Debian Box to use a static IP, but from there I di not know where to go.Also since my cable modem IP is dynamic, is there some way to have that the debian box get the IP address for the outside world, and e-mail it to my gmail account when it changes, or least every X hours?
I just installed Debian 6 on a server and when the server powers up, it shows me all the accounts I created in order for me to choose and login under an account, except for the root account. At the colo where the server is going, they need the root account at the login screen.
I'm new to Debian and installed it with Cinnamon because I want to learn some OpenCL programming in Linux. I have a Nvidia GT 525M GPU. Once the operating system is installed, I followed [URL] ..... article to install the proprietary Nvidia drivers. As the forum suggested, instead of creating an Xorg server configuration file, I installed Bumblebee according to [URL]..... article.
But when I restarted my machine after completing all the steps when I try to log in I get the follwoing message:
Today I upgraded my system to the Nvidia driver 340.93 and 4.2.0-1 kernel on Debian Stretch.
While I wait for the gnome login screen to pop up I get the "Oh no something has gone wrong" message.
When I log in from another terminal and execute startx , gnome initiates and starts although settings like my resolution and other xserver settings are not loaded.
From the journalctl I believe the error is located in the following section:
Code: Select allOct 06 14:23:17 DEBIAN-PC org.a11y.atspi.Registry[1692]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Oct 06 14:23:17 DEBIAN-PC gnome-session[1680]: X Error of failed request:Â BadValue (integer parameter out of range for operation) Oct 06 14:23:17 DEBIAN-PC gnome-session[1680]: Major opcode of failed request:Â 154 (GLX)
[Code] ....
I reinstalled the xorg-xserver and the nvidia drivers and I get the same behavior.
Looking for some info in order to reconfigure the gnome-session to work?
I just upgraded to jessie and now Samba won't let me log in anymore. I merged smb.conf manually. It now looks like this (removed comments):
Code: Select all[global]   workgroup = WORKGROUP   dns proxy = no   bind interfaces only = no   log file = /var/log/samba/log.%m   max log size = 1000   syslog = 0
[Code] .....
With smbclient logs as follows: Code: Select allsmbclient -L 192...
Enter user's password: session setup failed: NT_STATUS_UNSUCCESSFUL
If I provide a wrong password, it raises NT_STATUS_LOGON_FAILURE, also if retry with the correct password.
Not sure about what resolved the issue. But after I purged samba, reconfigured it, added the users AND set www-data's shell to bash again (which was changed during the update), it now seems to work
I've been working on building an LTSP server for diskless booting. I have a tftp server that's booting the system. I followed the steps on [URL] .... to build the LTSP server.
I had to make one change from the guide. I have a cisco router that's acting as the DHCP, I'm not very familiar with Cisco IOS so instead of playing with that, I decided to modify the default file on the PXE.
I commented the kernel append line and added the following instead
I'm mounting the nfs as a rw file system for now. I'm planning to make it read only once I have it working the way I want. In addition to this, I also chroot into the LTSP root and installed lightdm + mate. As I understood what I read, this would boot the environment on the diskless system. All of this seem to work correctly.
What I need to do next is to find a way to setup the LTSP clients to log in by authenticating on the active directory. I understand that the login account used by the LTSP client has to exist on the LTSP server.
I have successfully added the LTSP server as a worksation within the windows domain and I can log into domain accounts from the LTSP server but domain credentials do not work when using an LTSP client, I can only log in if I use an account that exists on the LTSP server. I wanted to know if there is a way to accomplish AD authentication.
Do I have to build an LDAP server on the LTSP server, sync accounts with the Active Directory to be able to log in with AD credentials?