Debian Configuration :: Wrong Name For The Wireless Card On Reboot
Feb 17, 2016
A couple of days ago I asked why my pc changes the wireless card name.It switches between AR9285 ( right) and AR5008 ( wrong). Well, it is not the case. When system identified with AR9285,it loads ath9k and I can connect to the router. When system identifies my card as AR5008, no kernel module is present at all ( lspci -k). The wrong card name occurs only when system rebooted. If I gracefully shut down the system, it always comes up with a right name for the card( AR9285). So, how to force the system identify my card right no matter if I reboot or shut down?
I'm having trouble getting my wireless card (RNX-G300LX, from Rosewill) working with my Debian install. I had it working at one point in time, but (apparently) something has gone wrong, as it no longer connects. The network I'm trying to connect to uses WPA2. When I try to start up my wireless card as follows: # ifup wlan0
I get the following response: wmaster0: unknown hardware address type 801 wmaster0: unkown hardware address type 801 Listening on LPF/wlan0/00:1a:... Sending on LPF/wlan0/00:1a:... Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 No DHCPOFFERS received. No working leases in persistent database - sleeping.
I have set up /etc/network/interfaces as follows: auto lo iface lo inet loopback iface wlan0 inet dhcp wpa-conf /etc/wpa_supplicant.conf auto wlan0 and /etc/wpa_supplicant.conf looks like this: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 ap_scan=1 fast_reauth=1 network={ ssid="apt_102" scan_ssid=1 key_mgmt=WPA-PSK psk="mypassword" proto=WPA2 }
I should also note that running wpa_cli -i wlan0 tells me that it is "trying to associate" with my router, but authentication times out each time.
I use Debian Stretch and I've installed it twice with the same ISO on the same laptop. First just to test a few things, then freshly installed it again.
The first time the wireless card was named wlan0 (as always for me, I've never had another name), the second time though it was suddenly named wlp3s0.
How did this occur and may I change it back to wlan0?
I'm trying to install the driver for mi wireless card. The instructions say that to build the tar.gz file, I have to:
# mkdir hybrid_wl # cd hybrid_wl # tar <path>/hybrid-portsrc.tarhybrid-portsrc-x86_64.tar.gz
The third step i don't understand. I want the folder of the driver to be located in a folder inside home called "Programas" so what I did was to open the terminal, went su, and then did cd Programas. Then I followed instructions 1 and 2, but I don't know what to put where it says <path>.
I am currently trying to connect to internet through my wireless card, after half day's effort I reached to this point:
/******The following error appears in the dmesg kernel ring buffer output: ipw2200: ipw2200-bss.fw load failed: Reason -2 ipw2200: Unable to load firmware: -2 ipw2200: failed to register network device ipw2200: probe of 0000:02:03.0 failed with error -5*********/
I found a solution from Intel website saying that the problem might be: "firmware in wrong location or wrong firmware version". So I proceeded to download the firmware and placed it in /lib/firmware. Also I tried to use menuconfig to enable loading firmware via hot-plug, but I think I have done something wrong when I was configuring the hotplug and firmware.
I just installed fresh Squeeze to my new hpmini 210-1100 netbook. No wireless. I have checked and I have Network Manager installed already.
I also compiled and installed Broadcom driver from here[url]
I followed their instructions and compiled the driver. I did get a wl.ko driver and installed it insmod wl.ko after modprobe lib80211
I noticed after rebooting neither wl.ko nor lib80211 showed when i did lsmod. So I did modprobe and insmod again. Still no wireless. Here are output of some commands that I thought would be relevant.
lspci:
I see only 2 computer icon in the system tray but not the parallel bars. When I went to System>Administration>Network, I was not able to add my wireless network name. The Add button was grayed out.
I am *finally* getting around to rebuilding my file-sharing computer. I'll be sharing files with both Linux and Windoze machines. It's a home network, so there's nothing fancy needed. I know I have to tweak my smb.conf file until I'm satisfied with the features and security. I'm using SWAT and I'm starting with a bare-bones conf file. It's not secure but I can see the server and selected files/directories from my other Linux box.
My really dumb question is, do I have to reboot both the server and the client machines every time I change the SAMBA configuration? I thought I just had to stop and restart the SAMBA service in the SWAT software - but then the server disappears from my client. It looks like I need to reboot both machines for the client to see the server.
I recently installed another Linux distro, Kali Linux, alongside my Debian 8 and discovered to my chagrin that my computer boots to Kali's grub rather than to the Debian grub. I had spent some time customizing Debian's grub and would hate to see that effort go to waste. Is there a way I can get my computer to boot to Debian's grub instead? I tried deleting Kali's boot partition with gparted but that did not seem to do anything.
Today I fresh installed the latest stable version of debian (jessie) with gnome from the USB DVD image for a 64bit machine. Everything got fine except the graphic driver, I think.
Now Gnome 3 is running but graphic is super slow. My previous debian/gnome 3 ran much better and I think there is a problem with the graphic driver.
I'm on an thinkpad t61.
Processor: Intel Core2 Duo CPU T7500 @ 2.20GHz × 2 Ram: 4GB Graphic: VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
Now the graphic is: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits) which is likely wrong. If I'm not mistaken llvmpipe is pure slow software acceleration.
Moreover this was different on my previous debian (wheezy), which was faster. Anyway I don't know what " Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits) " is and it was for sure different in wheezy.
According to apt-get I have the latest intel graphic divers installed. So maybe this an X-org confic problem?
I've been working on the setup of a FTP server on my Debian system for the whole afternoon. But I can't get it straight! Normally I get it working in just a second, but it's been a while I guess.
I installed only proftpd-basic and it's default dependencies. Should be enough right?
My configuration files are as follows:
I created the user zeitgeist, gave it a password, group and a homedir. Group of the user is nogroup and the homedir is correct with the 755 permission. My port 21 for FTP is open I tested it with nmap -p 21 [ip-address].
My Filezilla client tells me that at first he is connecting, then the connection is established, And then the connection is closed by server.
Using Debian 5.0 Stable, with all current updates, if I type \192.168.0.249 I get samba access and can use all the shared files ok.if I go via the network the computer should be called \squ-eee-zeboxserver but instead comes up as \SQU-EEE-ZEBOXSERsqu-eee-zeboxserver which when clicked gives the attached error.
I've got a strage problem with openssh-server on debian lenny. I've done setup of sshd and basically everything works fine. I can check the fingerprint of the ssh-keys on the server and it matches with the fingerprint shown on the client for the first connection. so the key is stored in the known-hosts-file on the client.
The problem occurs after a "connection reset by peer" (i guess when the connected client goes to sleep or a timeout occures)!
After such a reset, when I try to connect to the server, the banner "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" appears and the shown fingerprint of the server-key is totally wrong (it differs from the one on the server, BUT it is everytime when this problem occurs the same fingerprint). If I nevertheless remove the correct key from the known-host-file and accept the new key, I still can't login (permission denied).
To fix this situation temporarily I just need to restart the networking on the server. After the network-restart I get (again) the correct fingerprint of the server-key and can login without problems. Until the next connection reset.
At the moment I am having a problem with the MySQL server on my VPS. It's a completely fresh install of both Debian 5 and MySQL but the problem is upon logging in I get:
[root@boris ~]#mysql -u root -p Enter password: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
Hey guys. I have a client computer PXE booting from my host computer and it is supposed to give the client the ip address 172.16.0.100 however instead it gives it the ip address 172.16.0.208.
I have this set up working with two other computers and there is no noticeable difference other than mac addresses for the network card.
Here is an extract from my '/etc/dhcp3/dhcpd.conf' file...
I have quadruple checked the mac address of the client and it is definitely "00:07:E9:32:16:81" so why is it not giving it the IP address that I have specified?
Installed 6.01a from DVD 1 on a system with 4GB ram. Installer installed amd64 version by default. When I try to install amd64.deb files I get "wrong architecture" error messages from the package manager. root@Laptop-RalphDeb:/home/ralphq# uname -r 2.6.32-5-amd64 root@Laptop-RalphDeb:/home/ralphq# uname -p unknown Why I can install amd64 programs and why I get unknown for the uname -p command?
I rebooted my vServer (Debian 8) and it doesn't came back up. Well, I used the rescue console on my server and the server seems to be running fine, except the network was broken. So I tried 'ifconfig' but nothing came up. So I tried to enable my interface with 'ifconfig venet0 up', and now it appears in my ifconfig list
My HWaddr doesn't look that well :) 'ip addr' prints this result:
Code: Select allroot@i67svof:/var/www# ip addr 1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
These are the last lines in /var/log/syslog:
Code: Select allroot@i67svof:/var/www# tail /var/log/syslog Feb 20 11:34:16 i67svof systemd[1]: Stopping memcached daemon... Feb 20 11:34:16 i67svof systemd[1]: Stopping Network Name Resolution... Feb 20 11:34:16 i67svof systemd[1]: Stopping Regular background program processing daemon... Feb 20 11:34:16 i67svof systemd[1]: Stopping Login Prompts.
[Code] .....
And finally my network config in /etc/network/interfaces
Code: Select all# Auto generated lo interface auto lo iface lo inet loopback # Auto generated venet0 interface auto venet0
I have installed Firestarter, and set it up following some manual (just a simple, baseline setting, nothing fancy). However, after restart I got error message: Starting the Firestarter firewall... failed! and then, later: startpar: service(s) returned failure: firestarter ... failed! Why this happens?
Upgraded webserver to Jessie as an upgrade to Wheezy produced errors, and before reboot everything was up and running, but as all upgrade docs and info I read, I rebooted the server. However it never came back. I have the original backup files before I did the Wheezy upgrade. I also have access by Rescue to the server.Made a back up of critical files and have a 24GB tar file and I can connect by SFTP.
how to check the Debian files... Grub etc.. I would prefer to find the issue than start again.I am not able to sudo from Putty. I cannot run apt-get update. I did go to chroot, but then I get unable to resolve host errors and Could not open lock file because Permission denied errors and asking if I am root.There is information by googling for start up issues, but as I am working remotely with a Rescue set up, a lot of the commands I see and have tied do not work.
after a reboot of my Lenny system, the default gateway will lost. Then i must try "networking restart" and the gatway will be set
my interfaces looks :
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback
I've got an old Compaq Armada laptop (850 mhz PIII processor, 512mb RAM, 30GB HD, DVD ROM) that I've been running OpenSUSE 11.1 on in a dual boot configuration with WinXP for almost a year. I've downloaded and burned a LiveCD of OpenSUSE 11.2 and booted the computer with it. Very impressive. I want to install it on the HD without doing a clean install. That is, I want to replace 11.1 and keep the WinXP partition intact. My biggest trepidation is getting the wireless card configured again. It was a bear the first time. Is there a way to update OpenSUSE without losing those settings?
I've an Blade 1500, sparc64 IIIi with 2 hard disks and 2go of RAM. The computer run with debian 7.7.0 and BSD (opensxce) for each hard disks.
1/ When it's run under BSD there are no problems, the uptime are on many hours. 2/ when it's run under debian with XFCE x-window, the uptime is 4 hours 30 minutes and computer reboot automatically !
Into the control panel i've deactivate the hibernation, screensaver and power management ! I want to find the files for manage the time down. I think that the problem is in XFCE window manager.
I've upgraded a server on our LAN from fully functioning Wheezy to Jessie. All seems fine except remote administering using Putty from my windows workstation when issuing reboot from command line, it goes down and reboots but stops at login prompt asking for username and password and does not come back on the LAN network. This server does not normally have a monitor or keyboard so my ability to remote admin this server in effect is disabled.
If I log on, it will come back on the LAN network. I've checked the logs but can't see any errors. Is it in the configuration of Jessie somewhere or perhaps a Grub issue. I have 5 other production Wheezy servers that I intend to update to Jessie once I understand how to deal with this problem.
I've been using various distros of Linux for over 20 years - but I'm stumped.
Was running Mint. But after taking an update a few weeks ago the network stopped working. After a lot of time and effort decided to give up on Mint and switch distros to Debian 8 Jessie.
But after changing the Network settings from default DHCP to my usual IPV4 static 10.net configuration and rebooting the network will not work.
I have several systems on a 10.100.0.0/16 LAN behind another Linux system acting as firewall/gateway.
Now, after about 7 hours of mining the Internet, I still can't get basic networking to work:
- Have tried a few combinations, with and without Network Manager and eth0 in interfaces - /etc/network/interfaces is configured with a static IP and relevant parameters - ifconfig shows eth0 and the correct information - netstat -rn shows the basic default route to the gateway - have tried with IPV6 enabled and disabled; it is not used on my LAN
The box is a desktop system, ASUS Maximum VI Formula mobo with onboard Ethernet, dual GTX 780 cards. Nothing very weird.
It all LOOKS right, but ping can't get off the box "destination unreachable", and no other system on the LAN can ping it.
I'm amazed a basic static IPV4 network setup completely breaks it. This is my main workstation - a dual-boot system where Windows runs fine - so it's not hardware.
EDIT: This has been solved. See the solution post: [URL]
I have recently come across a Debian installation page for powerpc: viewtopic.php?t=20481. It got me motivated to fix the Debian I have on my iBook G4. I have a Debian Lenny installed on my iBook G4 -- but I have been having some sort of problem (mostly likely due to hardware) which causes the system to crash. After the latest crash, the clock on iBook has been readjusted. For this reason, I cannot reboot Debian completely.
Every time I turn on the computer it begins the booting process but before I get to my desktop I encounter numerous error messages concerning my clock. After either OK'ing or canceling these error messages, I get to my desktop but the system by then is either frozen or else not working at all. Worse, I can't even turn off the computer since the upper right corner of the desktop is completely blank and I have no menu to turn off or reboot the system.
It took this computer to a local Apple store and they ran many different hardware diagnostic tests on it. They concluded there's "technically" nothing wrong with the computer. But they said although the system has successfully passed all hardware tests, there may still remain some complicated but slight hardware glitch/es which the hardware diagnostics could not pick up.
