date int64 1,220B 1,719B | question_description stringlengths 28 29.9k | accepted_answer stringlengths 12 26.4k | question_title stringlengths 14 159 |
|---|---|---|---|
1,377,610,923,000 |
I have a fresh Debian 8.1 installation and am trying to make its usability feel like OSX.
I run
xelatex document.tex && evince document.pdf &
but it only successfully runs xelatex and does not update the PDF document in the viewer which is already open.
How can I make evince fetch the updated document from the disk?
|
Evince is updating the pdf automatically. No need to restart it. At least mine does on Debian 8.1.
When it's not reloading automatically anymore, maybe you ran out of inotify watches. Increase it with:
echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p
Mine is set to 65536 by /etc/sysctl.d/30-tracker.conf.
| How to make PDF viewer responsive to changes in Debian |
1,377,610,923,000 |
I'm running a docker container, in the development environment. I'm trying to set the fs.inotify.max_user_instances value.
Since inside the docker container I'm the root user, thus the sudo is not needed. In fact, if I run sudo command_text I get:
bash: sudo: command not found
Thus I run sysctl fs.inotify.max_user_instances=8192 to increase the max_user_instances value. To my surprise I get this error:
sysctl: permission denied on key "fs.inotify.max_user_instances"
Based on this answer I realized that even the root user could not change some stuff because they affect the entire machine (though this seems silly because the root user is the owner of the system in some sense and should be able to change the whole machine if he wanted to).
Using -w flag makes not difference. Still the same error.
Thus I tried echo 8192 > /proc/sys/fs/inotify/max_user_instances to directly override the value inside the related file. And I got:
bash: /proc/sys/fs/inotify/max_user_instances: Read-only file system
I did not try to change the file system permissions. Because at this point I felt that this is probably not a good idea.
How can I safely increase the inotify quota inside a Docker container, as the root user?
Update
I even tried chmod +w max_user_instances, and I got this error:
chmod: changing permissions of 'max_user_instances': Read-only file system
My OS is:
root@panel:/# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
|
In simple words, Docker uses the technique of chroot with an overlay file-system to run a container.
The running container uses the host kernel and it's kernel parameters (sysctl).
Pseudo file-systems (/proc, /sys, ...) are mounted from the host read-only.
Changes on kernel parameters on the host are immediately seen in the running docker container. From the docker container, you can not change the kernel parameter of the host (read-only).
There are many details with Docker, which I do not mention for simplicity and response to the question. See Docker manual for all the details.
| sysctl: permission denied on key "fs.inotify.max_user_instances" |
1,377,610,923,000 |
I've been having trouble researching this topic so I'm hoping someone can point me in the right direction. Are there any Kernel configurations required to be enabled in the OS for Inotify to work? What options do I need to enable in the .config file of Linux kernel?
|
Yes, CONFIG_INOTIFY_USER. Here's the help text associated with that kernel option:
CONFIG_INOTIFY_USER:
Say Y here to enable inotify support for userspace, including the
associated system calls. Inotify allows monitoring of both files
and directories via a single open fd. Events are read from the
file descriptor, which is also select()- and poll()-able.
Inotify fixes numerous shortcomings in dnotify and introduces several
new features including multiple file events, one-shot support, and
unmount notification.
For more information, see <file:Documentation/filesystems/inotify.rst
If unsure, say Y.
Symbol: INOTIFY_USER [=y]
Type : bool
Defined at fs/notify/inotify/Kconfig:2
Prompt: Inotify support for userspace
Location:
-> File systems
Selects: FSNOTIFY [=y]
I found this by:
Navigating to the kernel sources
Doing a make menuconfig
Hitting / to do a search
Typing inotify and pressing Enter
| Any Linux Kernel configuration required to be enabled in OS for Inotify to work? |
1,377,610,923,000 |
The script below watches for close_write events in the TARGET directory and does something with the file
#!/bin/bash
TARGET=/home/*/ftp/files
inotifywait -m -r -e close_write $TARGET |
while read directory action file
do
if [[ "$file" =~ .*jpg$ ]] || [[ "$file" =~ .*mp4$ ]]
then
# do sth with the file
fi
done
So right now it is correctly watching for close_write events for files under e.g. /home/sammy/ftp/files and /home/neo/ftp/files.
The problem I'm facing is once a new user created, let's say mike, then the watch seems to no longer be working and I will have to re-execute the script so that it will know about the new user's path, i.e. the nohup process needs to be killed and be ran again.
Is there any way for inotifywait to know about newly created directories ?
|
With -r it automatically finds new directories created under the ones it's watching. But here, it gets the paths /home/sammy/ftp/files and /home/neo/ftp/files (etc.), and /home/mike isn't under either of them, so it won't be detected. (Remember, it's the shell that expands the glob /home/*/ftp/files before inotifywait even runs.)
In principle, you could watch the whole of /home and manually ignore anything that wasn't in /home/*/ftp/files. But that would create piles of watches and produce loads of unwanted events.
A better idea might be to watch /home in addition to the /home/*/ftp/files directories, and to restart the watch when seeing a new subdirectory added under /home. If any new users always get the ftp/files directory created immediately, that shouldn't be too bad. You should probably explicitly wait for the new ftp/files directory to appear though, so that you don't fall into the race where your script resets the inotifywait before the new ftp/files is created, thus missing it.
(Though restarting inotifywait creates a window where a new file could be created, with the script missing it. Stuff like this would probably be safer to do with some programming language that supports inotify directly.)
A completely different approach would be to change the directory structure so that instead of /home/$user/files/ftp, the related stuff would be in /srv/ftp/$user. Then you could just add a watch on /srv/ftp, automatically catching new users without problems.
| inotifywait not detecting new directories |
1,690,299,135,000 |
I’m working in ubuntu and need to monitor a directory tree for new subdirectories and files. These are populated by rsync; dozens of subdirectories and hundreds of files may be added in less than one second. I’m considering a few options:
option 1: Monitor the tree with python’s inotify.adapters.InotifyTree(). But the documentation contains this caveat:
"IMPORTANT: Recursively monitoring paths is not a functionality provided by the kernel. Rather, we artificially implement it. As directory-created events are received, we create watches for the child directories on-the-fly. This means that there is potential for a race condition: if a directory is created and a file or directory is created inside before you (using the event_gen() loop) have a chance to observe it, then you are going to have a problem: If it is a file, then you will miss the events related to its creation, but, if it is a directory, then not only will you miss those creation events but this library will also miss them and not be able to add a watch for them."
option 2: Monitor the tree with the linux inotifywatch utility using the ‘--recursive’ option. That documentation includes this caveat:
"Warning: If you use this option while watching the root directory of a large tree, it may take quite a while until all inotify watches are established, and events will not be received in this time."
Which of these two options do you think is less likely to miss new subdirectories and files? My sense is that option 2 is probably more reliable since inotifywatch is (probably) implemented in ‘C’.
Thanks!
|
Let's start by properly understanding the problem. The warnings you read in both manuals come from "limitations and caveats" in man 7 inotify: https://man7.org/linux/man-pages/man7/inotify.7.html
This comes from the kernel limitation so it's important to know both pieces of software might have the same problems even if their respective manuals don't mention some.
My own guess here is that notifywatch's manual doesn't mention the race condition because it is unlikely to be relevant to most users. The manual states:
notifywatch listens for filesystem events using Linux's inotify(7) interface, then outputs a summary count of the events received on each file or directory.
If this software skips a few file create events in new subdirectories it will still be doing what it's supposed to: reporting stats.
What can you do?
I don't think either solution is guaranteed to be perfect as you seem to need and I would never let a race condition break my software if I knew it could be a problem. Don't just "hope" it'll all be fine!
Again from inotify 7 manual:
However, robust applications should allow for the fact
that bugs in the monitoring logic or races of the kind described
below may leave the cache inconsistent with the filesystem state.
It is probably wise to do some consistency checking, and rebuild
the cache when inconsistencies are detected.
The wise thing to do in your case would be to use an option similar to 1 or 2 and code around the race condition. When you detect new directories being created:
Make a note of the new directory.
wait until after you have read all available inotify events
then scan the directory (pathlib.Path.iterdir()) to see if you somehow missed any files in the race condition.
How to wait?
Waiting for all available inotify events is tricky. Using option 1 (inotify from PyPi) you can fetch all available events using a short timeout:
gen = i.event_gen(yield_nones=False, timeout_s=0.1)
When you have new directories to scan, you can set a short timeout and scan those directories when it does timeout. When you have no new directories to scan you can use it without the timeout (never timeout).
| python InotifyTree versus linux inotifywatch: which is more reliable? |
1,690,299,135,000 |
OS: Ubuntu 22.04 LTS.
Many posts deal with file monitoring. One in particular is of interest and based on inotifywait, but I don't know how to modify it for my purpose.
Objective: to monitor $HOME/{Documents/,Downloads/,Archive/} for link files *.lnk as they are created. Those files are created every time I use Word in Wine to create, save, open or do anything with a document. Dozens *.lnk files can be created in mere minutes. This issue is killing me.
I am willing to learn but can't translate generic examples into what I need for lack of knowledge. I know how to run a script in a plain file, but if there's anything special I should know in this regard, please let me know. Tx in advance.
|
You need to write this small script in a file using your terminal. I assume you are using the bash shell since you are beginning, and on Ubuntu. Let us know if it is otherwise.
$ touch notify_links
$ chmod u+x notify_links
$ cat notify_script
#!/usr/bin/env bash
inotifywait -mr -e moved_to,create "$HOME"/{Documents,Downloads,Archive} |
while read directory action file; do
if [[ "$file" =~ .lnk$ ]]; then
echo rm -f "$file"
fi
done
Run this script. To do so, just issue (in terminal) the following command notify_links in terminal.
Once satisfied by what you see appearing on terminal display, remove the echo in the script line: echo rm -f "$file" to leave only rm -f "$file".
EDIT 1 per @ilkkachu's comment in order to specialize monitoring to three directories/folders instead of the complete $HOME subtree.
EDIT 2 per @Paul_Pedant's comment, in order to run this automatically every 10 seconds as soon as your boot process is finished, edit your /etc/crontab file with crontab -e to include:
* * * * * $USER for i in $(seq 5); do /usr/bin/find $HOME -name "*.lnk" -delete; sleep 10; done
EDIT 3 for faster result and lesser resource usage, you'll want to search only the directories that you mentionned in OP. The following will search their subtrees:
* * * * * $USER for i in $(seq 5); do /usr/bin/find "$HOME"/{Documents,Downloads,Archive} -name "*.lnk" -delete; sleep 10; done
In order to prevent find from recursing down the subtrees, add the following option -maxdepth 1 before -name "*.lnk" in the find command.
| Monitor several directories for specific files' creation, every 10s |
1,690,299,135,000 |
My laptop has a cracked touchscreen that the local Asus tech tells me can't be replaced, not even with a non-touch because they just don't make them anymore.
It is in all other respects a great laptop and works as well as ever with an external monitor but the crack on the screen sometimes generates random touch events that disrupt my session.
Disabling the screen with xinput --disable 17 solves that problem, but some events unknown seem to re-enable it. I can set up a watch on that device like this:
xinput --watch-props 17
Device 'USBest Technology SiS HID Touch Controller':
Device Enabled (177): 1
....
I want to parse out that 'Enabled' and respond with a disable.
So I want this to run as script, as a service perhaps, so that I can re-disable the screen when it is re-enabled. However this script produces no output at all
#!/bin/bash
xinput --watch-props 17 |
while read event; do
echo "$event"
done
I have a number of inotifywait and ip monitor scripts that use this format and they all work as expected, but there's something wrong with this one.
|
Instead of using inotifywait to actively re-disable the screen, you could tell the X server that the device is not needed.
You could do this by creating /etc/X11/xorg.conf.d/99-no-touch.conf with contents like this:
Section "InputClass"
Identifier "Disable a cracked touch screen"
MatchProduct "USBest Technology SiS HID Touch Controller"
# completely disregard the broken device
Option "Ignore" "true"
# alternative: just stop the device for being used as an active input device
# Option "Floating" "true"
EndSection
I believe that the Option "Ignore"... line will suit your purposes better by completely removing the touchscreen from the list of input devices given by xinput list.
The alternative method using the Option "Floating"... line would allow the device to remain listed, but would designate the device as "not currently being used as part of the virtual core pointer/keyboard group", which effectively makes the device ignored by any X11 application that does not specifically request that particular input device.
Since I took the MatchProduct value from your xinput --watch-props 17 output, it is probably correct, but if you need to tweak it, it might be helpful to look at /var/log/Xorg.0.log to see the exact identifier(s) used when the touchscreen controller is detected by the Xorg X11 server, and adjust the Match... clause accordingly. You can find more information on the various Match... keywords by using man xorg.conf on your system.
| monitoring xinput in script |
1,690,299,135,000 |
I am in need of a bash script to recursively watch a folder and symlink every new file and subdirectory to another folder.
this script correctly symlinks subdirectories and their contents:
#!/bin/bash
inotifywait -r -m '/source_dir' -e create -e moved_to |
while read dir action file; do
cp -as $dir/$file /destination_dir/$file
done
However, the problem is that if a file gets added to a sub directory, a symlink will be created directly in the destination directory instead of its respective subdirectory , how do I rectify this?
|
You need to use the directory path in the target destination
#!/bin/bash
#
src='/source_dir'
dst='/destination_dir'
inotifywait -r -m "$src" --format '%w%f' -e CREATE,MOVED_TO |
while IFS= read -r item
do
# echo "Got $item"
if [[ ! -d "$item" ]]
then
echo mkdir -p "${item%/*}"
echo cp -as "$item" "$dst/${item#$src/}"
fi
done
Remove the two echo prefixes when you're happy it's doing what you expect. Uncomment the echo "Got $item" to see some of what's going on.
Please note that it is not possible to use inotifywait in this manner to handle file or directory names that contain newlines (adding \000 or even \001 to the --format string, with or without $'...' seems to prevent inotifywait from delivering any status updates at all).
| Bash script for monitoring a directory and symlinking all newly created subdirectories and their files |
1,690,299,135,000 |
I have a inotifywait on syslog. It works without issue until the log rolls over.
Although the same filename is used, the new file is a new file and inotify loses its reference.
How do we compensate for this to maintain the watch through the log rollover?
|
You could restart your iwatch as part of the log rollover. man logrotate logrotate.conf.
added by OP:
The installed logrotate.conf (as of Ubuntu 20.04) is configured to read the contents of /etc/logrotate.d. In that directory, the syslog configuration is in rsyslog. In that file there is a syslog section as below which I modified as indicated.
/var/log/syslog
{
rotate 7
daily
missingok
notifempty
delaycompress
compress
postrotate
/usr/lib/rsyslog/rsyslog-rotate
<MY MONITOR SCRIPT HERE>
endscript
}
| inotify - maintaining watch through log rollover |
1,690,299,135,000 |
I'm using Ubuntu 20.04. I'm trying to run this script for inotifywait. The idea is to move files from dir to target every time a change in directory occurs; this script is a shell file that can be started automatically or manually via the command line.
#!/usr/bin/env bash
dir=/mnt/test1/test/ #ftp point of mount
target=/var/www/html/local/ #normal directory on filesystem
inotifywait -m "$dir" --format "%w%f" -e create -e moved_to |
while read path action file; do
mv "$file" "$target"
done
And files to move need to have the *.txt format. inotify is watching, but when I use my ftp client to put a file in dir and wait for inotify to move it to target, nothing happens with the file.
I am using this for reference: https://unix.stackexchange.com/a/86292/425161
|
Unfortunately, the inotify API can not be used to monitor remote file systems.
From man 7 inotify:
Inotify reports only events that a user-space program triggers through the filesystem API. As a result, it does not catch remote events that occur on network filesystems. (Applications must fall back to polling the filesystem to catch such events.)
Relating questions:
Is there a way to use inotify on remote filesystems (specifically WebDAV)?
Monitor folders mounted via SSHFS
How do I use inotify or named pipes over SSHFS?
That said, the script in your question would not work as expected anyway.
The idea of using "%w%f" as the format of inotifywait's output is to provide the command in the loop with the full path of files that triggered a listened-for file system event. %w expands to the path of the watched file (the $dir directory), and %f expands to the (base)name of the file that caused the event.
Thus, inotifywait is only emitting a single full path for every event it catches. On the other hand, your read command is given three variables to fill in: path, action and file. By default, read splits a read line based on the characters in IFS and assigns the resulting tokens to the names it is given as arguments: the first token to the first name, the second token to the second name, etc. (And, if there are more tokens than names after the penultimate name, all the remaining tokens are assigned to the last name).
As you can easily check, in your code the full path of any file that trigger a watched-for event is assigned to path (unless it contained blank characters):
$ inotifywait -m --format "%w%f" -e create -e moved_to /tmp/test |
while read path action file; do
printf 'path: "%s"; action: "%s"; file: "%s"\n' "$path" "$action" "$file"
done
# Type "touch /tmp/test/foo" in a different terminal
path: "/tmp/test/foo"; action: ""; file: ""
Also, as pointed out in a different answer in the Q/A you inked to, you should listen for close_write events, and not for create. What you are probably looking for is:
inotifywait -m -q --format "%w%f" -e close_write -e moved_to -- "$dir" |
while IFS= read -r src; do
if [ "${src##*.}" = 'txt' ]; then
mv -- "$src" "$target"
fi
done
-r tells read not to interpret backslash-escaped sequences. IFS= is used to prevent read from trimming blank characters from the end of file names (to handle the unlikely case of names ending with spaces or tabs).
Note that this will still fail for files whose name contains newline characters.
| inotifywait with curlsftpsf mount point is not moving files as expected |
1,690,299,135,000 |
I have the following bash script (which is saved as ~/fix-perms.sh):
#!/usr/bin/env bash
inotifywait -d -r -e close_write -o /dev/stdout ~/testdir |
while read path event file; do
sudo chown user:group "$path$file"
if [ -d "$file" ]; then
sudo chmod 750 "$path"
echo "Created directory '$path' with 750 permissions"
else
sudo chmod 640 "$path$file"
echo "Created file '$path$file' with 640 permissions"
fi
done
I think the intended purpose of this script is obvious, but running it in my .bashrc fails to set the group permissions properly, as demonstrated below:
# In .bashrc
~/fix-perms.sh &
# In bash session
user@CentOS8:~/testdir$ ls -lha
drwxr-x--- 8 user group 4.0K Jun 18 13:06 .
drwxr-x--- 8 user group 4.0K Jun 18 11:45 ..
drwxr-x--- 12 user group 4.0K Jun 15 21:23 somedir
-rw-r----- 1 user group 316 Jun 15 23:23 somefile
-rw-r----- 1 user group 1.1K Jun 15 21:24 someotherfile
user@CentOS8:~/testdir$ mkdir subdir
user@CentOS8:~/testdir$ ls -lha
drwxr-x--- 8 user group 4.0K Jun 18 13:06 .
drwxr-x--- 8 user group 4.0K Jun 18 11:45 ..
drwxr-x--- 12 user group 4.0K Jun 15 21:23 somedir
-rw-r----- 1 user group 316 Jun 15 23:23 somefile
-rw-r----- 1 user group 1.1K Jun 15 21:24 someotherfile
drwx------ 12 user group 4.0K Jun 15 21:23 subdir
As you can see, the subdir directory is created and given the correct ownership, but the chmod command is failing without error for some reason. So what am I doing wrong? MTIA! :-)
EDIT: I have confirmed that inotifywait is watching the directory by adding some echo statements to the script, the output of which is now shown in the terminal whenever I add a file or folder to ~/testdir. I have also changed the event from create to close_write in the hope that this may better handle my use case.
|
@muru's comment above got me thinking about how I was testing what's being created, and made me realise that I was being very silly. The following code in ~/fix-perms.sh works nicely:
#!/usr/bin/env bash
inotifywait -dr -e create -o /dev/stdout ~/testdir |
while read path event file; do
sudo chown user:group "$path$file"
if [[ $event == *"ISDIR" ]]; then
sudo chmod 750 "$path$file"
else
sudo chmod 640 "$path$file"
fi
done
| chmod command run within inotifywait doesn't work |
1,690,299,135,000 |
I am trying to create a daemon to monitor a users's bash_history file for manual modifications. In other words, if a user opens the file and modifies it, the daemon will notify this action for safety measures, but when the history updates itself, nothing happens.
The solution I tried is using inotifywait:
while true; do
inotifywait -e close_write,move,delete ~/.bash_history && notify
done
where notify is a script that will do a specific notification procedure.
I believe this would work fine for most of files, but in this case it doesn't, since notify is executed every time the history updates.
Is it possible this way, or should I use another application?
|
That is not possible with inotify. There is no configuration that could probe if a file is altered by an user or a process, neither if it will monitor only "append to files".
And EVEN if there exists one "append to file" inotify event, one user could inject bash_history data with echo >> creating bogus entries and losing all the meaning of your monitoring.
You could harden your history files by following this advice, and i think this is the best you could do:
Secured bash history usage
| How do I monitor bash_history file for manual modifications? |
1,690,299,135,000 |
When I'm coding, I usually have 2 terminal tabs open in VSCode. The tab on the left is used for git commands. The tab on the right always has git log --all --graph --decorate --oneline showing me all the branches and commits.
I'm trying to make it so that the tab on the right reruns the git log command as soon as I checkout branches, checkout new branches, commit, push, pull...
I tried this:
# watchgit.sh
inotifywait -m .git/refs -m .git/HEAD |
while read dir action file; do
git log
done
but it doesn't refresh. I also don't mind if I get a few extra refreshes here and there.
Would appreciate some help.
Thanks!
|
Take look to the bottom right there is the (END) this comes from the pager used by git.
There --no-pager to avoid this issue
Then do while to react to each event around inotifywait:
while inotifywait .git/refs .git/HEAD ; do
git --no-pager log --decorate=short --pretty=oneline
done
| How to create a bash script that watches my local git repo and runs 'git log' every time I commit/checkout -b/push/status? |
1,690,299,135,000 |
#!/bin/bash
watchDir="$1"
watchDir2="$2"
date1=$(date '+%Y-%m-%d-%H:%M:%S')
inotifywait -m -r --exclude \.log "$watchDir" "$watchDir2" -e attrib,delete,delete_self,close,close_write,close_nowrite,create,open,modify,move,moved_to,moved_from |
while read -r file; do
name=$(stat -c '%U' $file 2>/dev/null)
date=$(stat -c %Y $file 2>/dev/null | awk '{print strftime("%d-%m-%Y %T", $1,$2)}')
fileName=${file/* CREATE /}
echo "[${date%.*}]" "File: '$fileName' User: '$name'" >> /var/log/inotify/inotify-$date1.log
done
|
After a lot of study i found the limitations useful;
finding user who changed a file wont work with inotify.
Please read Limitations http://manpages.ubuntu.com/manpages/bionic/man7/inotify.7.html
Limitations and caveats
The inotify API provides no information about the user or process that triggered the inotify event. In particular, there is no easy way for a process that is monitoring events via inotify to distinguish events that it triggers itself from those that are triggered by other processes.
| My main goal is to monitor Tomcat directory, if any user modify files in tomcat directory; print that user name in the log; |
1,690,299,135,000 |
I'm new here and I'm on a little project currently.
I need to write a script in bash to scan a folder each time a file is dropped in it.
In second part it should move it in a new directory created with the name used by this file.
I thought to use incron or watch but I don't know if it's a good solution.
The scheme would be like this.
directory="/usr/share/docker-compose"
if "*.yml" exist; then
do
move /usr/share/used-images
Thanks in advance.
|
You could use inotifywait. Example script:
#!/bin/bash
watchdir="$1"
if ! [ -d "$watchdir" ]; then
echo "Dir $watchdir doesn't exist"
exit 1
fi
while file=$(inotifywait --format "%f" -e 'create' -e 'moved_to' "$watchdir"); do
if [ -f "$watchdir/$file" ]; then
tmpname=$(tempfile -d "$watchdir")
mv "$watchdir/$file" "$tmpname"
mkdir "$watchdir/$file"
mv "$tmpname" "$watchdir/$file/$file"
# YOURCOMMANDS
fi
done
| Script in bash to scan a folder to move a docker file and execute it |
1,690,299,135,000 |
I recently reconfigured the filesystem on my laptop so I can share my data with a second Linux. The Linux used in this matter is Fedora 28, 64-bit.
My disks are now laid out like so:
/dev/sda:
/dev/sda1 - efi partition
/dev/sda2 - swap
/dev/sda3 - data partition mounted via /etc/fstab at /media/data_partition
/dev/sdb:
/dev/sdb1 - root partition mounted at /
/dev/sdb2 - var partition mounted at /var
/dev/sdb3 - home partition mounted at /home
The data partition now contains the contents of /opt, everything under $HOME/Documents and some miscellaneous stuff. They are on the partition with the some directory names (i.e. opt/, Documents/)
At boot, after the partition is mounted, I have a bindfs mount that mounts /media/data_partition/opt to /opt, and on login in my $HOME/.bash_profile, I bindfs mount /media/data_partition/Documents to $HOME/Documents.
When I boot up IntelliJ IDEA, it shows the following:
Currently I have open a project "located" at $HOME/Documents/University/Class/project_repo3. $HOME/Documents is the destination for a bind mount from /media/data_partition/Documents.
Also, IntelliJ IDEA's installation is located in /media/data_partition/opt. This location is the source for a bind mount to /opt
The mount seems to be IntelliJ's problem, but I have no idea what the actual issue is, nor which bind mount is the problem. I found these links:
https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000013130-External-file-changes-sync-may-be-slow
https://youtrack.jetbrains.com/issue/IDEA-192665
https://blog.jetbrains.com/idea/2010/04/native-file-system-watcher-for-linux/
The last link explains their new usage of inotify and would seem to explain the problem and the solution, but I'm not 100%. I don't wanna change anything, and regret it later.
The questions:
Is the solution proposed in the last link safe and correct?
What is inotify (I read part of the manpage, but would appreciate additional explanation)?
What are inotify watchers, and inotify instances?
|
What the popup warns of has never happened. I attempted to increase of fs.inotify.max_user_watches, but that did not get ride of the popup. In my case, it effectively means nothing.
| Data partition and IntelliJ IDEA external file sync speed |
1,450,365,687,000 |
I just installed Debian on laptop, it tells me
Some of your hardware needs non-free firmware files to operate. The firmware can be loaded from removable media, such as a USB stick or floppy.
The missing firmware files are: iwlwifi-7265-9.ucode iwlwifi-7265-8.ucode
If you have media available now, insert it, and continue.
Load missing firmware from removable media?
Using minimal Debian iso and no mirror I was able to install terminal only. Two questions:
Where do I download these files?
How do I get Debian to recognize them once on flash drive? Grep?
Do I need to do special formatting or partitioning to flash drive?
|
See the relevant section in the installation manual.
To answer your questions in more detail:
You'll find the files on http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/; if you're installing Debian 8, look in http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/jessie/current/ and download whichever archive is the easiest for you to handle (presumably firmware.tar.gz or firmware.zip).
Extract the firmware archive in the root of a flash drive; plug the drive into the computer you're installing, and the installer should find the firmware automatically.
The typical FAT32 filesystem is just fine. If you've got a larger drive using ExFAT, I'm not sure the installer will be able to use it...
| How do I install "non-free firmware" (wifi driver) from USB? (Debian) |
1,450,365,687,000 |
looking for help diagnosing bluetooth mouse lag. I'm using a Logitech MX Anywhere 2, I've had it a few years now and it's worked well on a number of Linux distros. I recently installed Debian 10 and set it up to use Sid repos. In this environment, the mouse does not work as responsively as normal. I'm on a laptop, and the touchpad works perfectly smoothly, and a wired mouse is also perfectly smooth. What I get with the bluetooth mouse is as if the sampling rate is maybe once every 3 or 4 frames.
I still have Pop!_OS installed which is based on Ubuntu 19.04, the mouse works as expected in that environment. Forgetting the mouse and re-adding it offers no change to behaviour, same with reboots. I've updated to the latest state of the repos, no dice. I've also tried switching from Wayland to Xorg with no effect.
My best guess would be that it's down to the iwlwifi module (it's a Lenovo Yoga 900 with an Intel Core i7 6560U with integrated Intel Wireless 8260), but no idea where to go from here.
Cheers!
|
Solution from reddit from @ashughes in an above comment -https://www.reddit.com/r/linuxquestions/comments/bc15f8/bluetooth_mouse_is_laggy_very_limited_pollrate/ez3ufhs/
sudo nano /var/lib/bluetooth/xx\:xx\:xx\:xx\:xx\:xx/yy\:yy\:yy\:yy\:yy\:yy/info
where xx:xx.... is pc bluetooth address and yy:yy... is the mouse bluetooth address.
In the file, I added the section at the end:
[ConnectionParameters]
MinInterval=6
MaxInterval=7
Latency=0
Timeout=216
You may also need to reconnect the mouse.
I also tracked this proposal on ubuntu bug here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824559?comments=all
| Bluetooth Mouse Lag |
1,450,365,687,000 |
I'm using a Ubuntu Budgie 18.04. I've been using it for a year without any problems, but suddenly the wifi stopped working, and in the network settings, I get the message "No Wifi Adapter Found".
The result of the iwconfig command is
enp59s0 no wireless extensions.
lo no wireless extensions.
and the result of the lspci command tells me that I have a network controller: Intel Corporation Wireless-AC 9560[Jefferson Peak] (rev 10).
I tried some solutions I found but it doesn't work. Please, help me!
Update:
ifconfig output:
enp59s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.189.125.212 netmask 255.255.0.0 broadcast 10.189.255.255
inet6 fe80::a47c:fa2:5210:181e prefixlen 64 scopeid 0x20<link>
ether 54:bf:64:37:5d:ac txqueuelen 1000 (Ethernet)
RX packets 126268 bytes 160092432 (160.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 47855 bytes 6451226 (6.4 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 988 bytes 97858 (97.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 988 bytes 97858 (97.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
iw list output:
NOTHING
lshw -c network output:
*-network
description: Network controller
product: Wireless-AC 9560 [Jefferson Peak]
vendor: Intel Corporation
physical id: 14.3
bus info: pci@0000:00:14.3
version: 10
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list
configuration: driver=iwlwifi latency=0
resources: irq:16 memory:ed31c000-ed31ffff
*-network
description: Ethernet interface
product: Killer E2400 Gigabit Ethernet Controller
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@0000:3b:00.0
logical name: enp59s0
version: 10
serial: 54:bf:64:37:5d:ac
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=alx duplex=full ip=10.189.125.212 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:17 memory:ed200000-ed23ffff ioport:3000(size=128)
lsmod | grep iwlw output:
iwlwifi 286720 1 iwlmvm
cfg80211 622592 4 wl,iwlmvm,iwlwifi,mac80211
rfkill list output:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
dmesg | grep iwl output
[ 3.234002] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 3.252973] iwlwifi 0000:00:14.3: loaded firmware version 34.3125811985.0 op_mode iwlmvm
[ 3.314535] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9560, REV=0x318
[ 3.360663] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[ 3.360668] iwlwifi 0000:00:14.3: Not valid error log pointer 0x00000000 for Init uCode
[ 3.360825] iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 0x2459
[ 3.360827] iwlwifi 0000:00:14.3: Failed to start INIT ucode: -5
[ 3.372999] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -5
sudo dmesg | grep iwl output after executing sudo rmmod iwlmvm && sudo modprobe iwlmvm:
[ 3.255919] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 3.273432] iwlwifi 0000:00:14.3: loaded firmware version 34.3125811985.0 op_mode iwlmvm
[ 3.340146] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9560, REV=0x318
[ 3.393635] iwlwifi 0000:00:14.3: base HW address: 34:e1:2d:c7:37:15
[ 3.473579] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 3.534582] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
[ 6.643197] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
[ 989.877842] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9560, REV=0x318
[ 989.934163] iwlwifi 0000:00:14.3: base HW address: 34:e1:2d:c7:37:15
[ 990.001012] ieee80211 phy1: Selected rate control algorithm 'iwl-mvm-rs'
[ 990.010264] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
[ 990.250978] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
|
Per request, here is the solution to fixing the Failed to start INIT ucode: -5 issue
Solution
First, before you even move onto any steps having anything to do with the Linux kernel itself, make sure you have SecureBoot disabled in your BIOS. While SecureBoot was meant to be a security feature ensuring that all drivers are properly signed , from what I have seen this causes more problems than it solves in Linux kernel, especially when network and graphics drivers are concerned. This will more often than not be the key to solving this issue and your wifi driver will be loaded properly upon reboot.
Once inside your Linux distro (and this is a good situation where using root account is actually appropriate), first ascertain if your kernel can see your wireless controller.
This first one will tell you whether the wireless card/controller can be seen as a device at all by your kernel (even if the driver initialization fails)
lshw -c network
While this one will tell you whether the system actually initialized it as a wireless device.
iw list
Now, in the case of OP the first command did show the Intel AC 9560, while the second command had a null output, telling us that the kernel a) can see the card but b) fails to initialize it. This tells us that the problem is more than likely related to the module/driver of the card
Just to be safe all run
sudo rfkill list
and make sure your wifi device is unblocked or just execute
sudo rfkill unblock all
to be sure that everything radio related is unblocked.
If you have disabled SecureBoot in your BIOS, yet for some reason your wifi is still not loaded correctly on reboot you can then run:
sudo rmmod iwlmvm && sudo modprobe iwlmvm
and the kernel will reload the module and initialize it properly, and from then on it will work on every subsequent reboot. Why it often doesn't work right away upon the first reboot is a mystery to me, because as far as I know and have been taught, modules get freshly loaded upon every boot. It is also possible that simply rebooting twice might produce the same outcome as executing the above command.
Once you have a stable internet connection, update your kernel headers and microcode packages.
| Wifi suddenly stopped working on Ubuntu 18.04 |
1,450,365,687,000 |
I have an Intel wireless card driven by iwlwifi, and I can see the following message in dmesg:
iwlwifi 0000:03:00.0: loaded firmware version 17.168.5.3 build 42301
Given that I know which blob is loaded, how I can find out the version of this blob (.ucode file)?
If you look at the below where the ucode is loaded, it doesn't tell me the version information just that a blob was loaded. But I know Intel versions these.
$ sudo dmesg | grep ucode
[ 26.132487] iwlwifi 0000:03:00.0: firmware: direct-loading firmware iwlwifi-6000g2a-6.ucode
[40428.475015] (NULL device *): firmware: direct-loading firmware iwlwifi-6000g2a-6.ucode
|
The iwlwifi driver loads the microcode file for your wifi adapter at startup. If you want to know the version of the blobs you have on your machine, try Andrew Brampton's script. Run:
## Note the firmware may stored in `/usr/lib`
./ucode.py /lib/firmware/iwlwifi-*.ucode
And compare the output to your journal (dmesg output).
Note that the script works with python2.
| How can I parse the microcode (ucode) in iwlwifi to get the version numbers? |
1,450,365,687,000 |
I recently purchased a new laptop which features an Intel Wireless-AX200 Networking device for Wi-Fi and Bluetooth connectivity. I installed elementary OS 5.0 "Juno" along with the latest stable linux kernel (5.1.1), as I've heard that it should come with support for the aforementioned networking device
However, I cannot seem to find any drivers related to the device, either within /lib/firmware or within the 5.1.1 source (looking for anything prepended with "iwlwifi").
Looking through lspci reveals the following devices, none of which appear to be a wireless or bluetooth device:
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07)
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 20 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Device a334 (rev f0)
00:1e.0 Communication controller: Intel Corporation Device a328 (rev 10)
00:1f.0 ISA bridge: Intel Corporation Device a30d (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1f10 (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 10f9 (rev a1)
01:00.2 USB controller: NVIDIA Corporation Device 1ada (rev a1)
01:00.3 Serial bus controller [0c80]: NVIDIA Corporation Device 1adb (rev a1)
02:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)
03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981
04:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
05:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
05:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
05:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06)
06:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06)
45:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06)
Has anyone been able to locate these aforementioned drivers within the 5.1 or 5.1.1 source? I've also just emailed [email protected], and can update this post with their response as it comes in.
UPDATE
I received a response from Intel. The driver itself has not made it into the kernel, therefore they suggested using their backport driver (which has now made wi-fi accessible on my laptop [mid-2019 Razer Blade])
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release & Here
|
Update:
The driver has been released for all major kernels here
Original:
According to the product page it's a pre-certified solution and the driver has not been published yet.
Even Linus's Development branch doesn't reveal anything so I'm assuming that at the time of this writing, it's not Linux compatible yet and the article you're referring to uses marketing speak for: We'll be adding that soon...
| Locating Drivers for Intel AX200 Wireless on 5.1 Kernel |
1,450,365,687,000 |
Trying to trouble-shoot this error which pertains to microcode, my card from lspci shows,
Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
system.log shows,
iwlwifi: Detected Intel(R) Centrino(R) Advanced-N 6205 AGN, REV=0xB0
When I run modinfo, I get, (a lot of stuff cut off)
description: Intel(R) Wireless WiFi driver for Linux
## lots of stuff...
firmware: iwlwifi-6000g2b-6.ucode
firmware: iwlwifi-6000g2a-6.ucode
firmware: iwlwifi-6050-5.ucode
firmware: iwlwifi-6000-6.ucode
## lots of stuff...
## NO iwlwifi-6205-#.ucode
srcversion: 6BA065AF04F0DFDB8D91DBF
But none of those show 6205. Which .ucode is system.log referring to when it says,
iwlwifi: loaded firmware version 18.168.6.1 op_mode iwldvm
There are two that I could assume,
firmware: iwlwifi-6050-5.ucode
firmware: iwlwifi-6000-6.ucode
But, is there way to know for certain?
|
This is documented at the Linux Wireless wiki:
------------------------------------------------------------------------------
Device | Kernel | Module | Firmware |
----------------- | ---------| ------- | ------------------------------------ |
Intel® Centrino® | 2.6.36+ | iwldvm | 17.168.5.1, 17.168.5.2 or 17.168.5.3 |
Advanced-N 6205 | -------- | | ------------------------------------ |
| 3.2+ | | 18.168.6.1 |
------------------------------------------------------------------------------
This table reflects the minimal version of each firmware hosted at linux-firmware.git repository that is known to work with that module and kernel version. In your specific case, the file is iwlwifi-6000g2a-6.ucode.
modinfo will show all firmware files that can be used by that module(and that could support other hardware). The wireless wiki is a pretty reliable way to get information about hardware and firmware.
dmesg | grep firmware could help you on probing what firmware file is being used. Example 1 - firmware was loaded correctly:
[ 12.860701] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode
[ 12.949384] iwlagn 0000:03:00.0: loaded firmware version 8.24.2.12
Example 2 - missing firmware file d101m_ucode.bin:
[ 77.481635] e100 0000:00:07.0: firmware: requesting e100/d101m_ucode.bin
[ 137.473940] e100: eth0: e100_request_firmware: Failed to load firmware "e100/d101m_ucode.bin": -2
| Where can I find the microcode (ucode) that is being loaded by iwlwifi (Intel 6205)? |
1,450,365,687,000 |
I am experiencing quite heavy audio skipping when streaming audio to my bluetooth speaker (Sony SRS-X3) using pulseaudio and Arch Linux on a T430. I think it is related to a known bug [1]. The speaker works flawlessly with Android.
$ sudo lspci -nnk | grep -iA2 net
> Network controller [0280]: Intel Corporation Centrino Ultimate-N 6300 [8086:4238] (rev 3e)
> Subsystem: Intel Corporation Centrino Ultimate-N 6300 3x3 AGN [8086:1111]
> Kernel driver in use: iwlwifi
$ sudo lsusb | grep Blue
> 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad]
Does anyone have an idea on how to reduce/prevent the skipping? Information that helps me understand the problem is also appreciated.
I suspect it is related to interference with WiFi. There is less skipping with WiFi off or deep at night (less traffic). How does Android handle this? My research turned up the Linux Frequency Broker [2]. Is it implemented?
[1] https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294
[2] https://wireless.wiki.kernel.org/en/developers/frequencybroker
|
It may help to disable the bluetooth coexistance parameter of the iwlwifi module to see if conditions improve. Open a terminal window and enter
echo "options iwlwifi bt_coex_active=0" | sudo tee -a /etc/modprobe.d/iwlwifi.conf
Reboot
| How to prevent bluetooth audio skipping with the A2DP profile on Arch Linux? |
1,450,365,687,000 |
The iwd is the up-and-coming wireless daemon for linux released by
Intel and the wpasupplicant successor. The development of iwd is still in progress, but it is packaged under some linux distribution Gentoo, Arch-linux , Ubuntu (Cosmic) and Debian (Buster and Sid)...
The configuration of the network and the connection is possible through the interactive mode using iwctl , the help command will display the list of the available commands (no manpage ).
Without using the interactive mode :
How can I manually configure the wifi credentials?
How can I connect to the configured wifi through iwctl?
How can I automatically enable the wifi connection at boot?
|
1) From the non-interactive mode , you can scan and list the available access points :
iwctl station wlp8s0 scan
iwctl station wlp8s0 get-networks
The wifi credentials are stored under /var/lib/iwd , the exact name of the SSID should be used , the format:
SSID.psk
The content:
[Security]
PreSharedKey=encripted-password
Passphrase=the-plain-txt-password
The minimal configuration file should contain the encrypted wifi paswword (PreSharedKey)
To generate an encrypted psk , you can use the wpa_passhrase tool:
wpa_passhrase "My-SSID" passphrase
There is an example using "My SSID" and mysecretpassword:
$ cat My\ SSID.psk
[Security]
PreSharedKey=8e1e64a6ecaf2b5e0aa29816547af300d7f3b0473bbfa56ddb5514ad4683804c
2) To connect from the terminal:
iwctl station <INTERFACE> connect "SSID"
e,g:
iwctl station wlp8s0 connect "My SSID"
dhclient
dhclient can be replaced an iproute2 command to assign an IP address to wlp8s0.
3) to automatically enable the wifi connection at boot , there is a way using a systemd service:
A minimal script to connect:
$ cat /usr/local/enable-wifi.sh
#!/bin/bash
iwctl station wlan0 connect "My SSID"
dhclient
Create a systemd service.
$ cat /etc/systemd/system/enable-wifi.service
[Unit]
Before=network.target
Wants=network.target
[Service]
ExecStart=/usr/local/enable-wifi.sh
[Install]
WantedBy=default.target
then :
# chmod 744 /usr/local/enable-wifi.sh
# chmod 664 /etc/systemd/system/enable-wifi.service
# systemctl daemon-reload
# systemctl enable enable-wifi.service
documentation:
arch-linux wiki : iwd
Debian wiki: NetworkManager/iwd
lwn: iwd: simplifying WiFi management
| Connect to wifi from command line on linux systems through the iwd (wireless daemon for linux) |
1,450,365,687,000 |
Is it possible to attach a IE field to my wifi hotspot so that it appear in the iwlist output of other machine scanning it?
Example:
I choose 1234567891011121314151617181920 to be the additional field for my wifi hotspot (MAC address 11:22:33:44:55:66)
Users scanning my wifi hotspot with command iwlist wlan0 scan, should give the output:
wlan0 Scan completed :
Cell 01 - Address: 11:22:33:44:55:66
[...]
IE: Unknown 1234567891011121314151617181920
[...]
|
IE stands for Information Element. They are transmitted as part of the beacon frames and carry all kinds of information such as SSID, supported rates, etc.
Information element Element ID Length (in octets)
---------------------------------------------------------------------------
SSID (see 7.3.2.1) 0 2 to 34
Supported rates (see 7.3.2.2) 1 3 to 10
FH Parameter Set (see 7.3.2.3) 2 7
DS Parameter Set (see 7.3.2.4) 3 3
CF Parameter Set (see 7.3.2.5) 4 8
TIM (see 7.3.2.6) 5 6 to 256
IBSS Parameter Set (see 7.3.2.7) 6 4
Country (see 7.3.2.9) 7 8 to 256
Hopping Pattern Parameters (see 7.3.2.10) 8 4
Hopping Pattern Table (see 7.3.2.11) 9 6 to 256
Request (see 7.3.2.12) 10 2 to 256
BSS Load (see 7.3.2.28) 11 7
EDCA Parameter Set (see 7.3.2.29) 12 20
TSPEC (see 7.3.2.30) 13 57
TCLAS (see 7.3.2.31) 14 2 to 257
Schedule (see 7.3.2.34) 15 16
Challenge text (see 7.3.2.8) 16 3 to 255
Reserved 17–31
Power Constraint (see 7.3.2.15) 32 3
Power Capability (see 7.3.2.16) 33 4
TPC Request (see 7.3.2.17) 34 2
TPC Report (see 7.3.2.18) 35 4
Supported Channels (see 7.3.2.19) 36 4 to 256
Channel Switch Announcement (see 7.3.2.20) 37 5
Measurement Request (see 7.3.2.21) 38 5 to 16
Measurement Report (see 7.3.2.22) 39 5 to 24
Quiet (see 7.3.2.23) 40 8
IBSS DFS (see 7.3.2.24) 41 10 to 255
ERP Information (see 7.3.2.13) 42 3
TS Delay (see 7.3.2.32) 43 6
TCLAS Processing (see 7.3.2.33) 44 3
Reserved 45
QoS Capability (see 7.3.2.35) 46 3
Reserved 47
RSN (see 7.3.2.25) 48 36 to 256
Reserved 49
Extended Supported Rates (see 7.3.2.14) 50 3 to 257
Reserved 51–126
Extended Capabilities 127 2 to 257
Reserved 128–220
Vendor Specific (see 7.3.2.26) 221 3 to 257
Reserved 222–255
Some of these information elements are vendor specific, meaning they will probably be ignored by other vendors. Reserved means it may have a standard meaning in the future, in fact some of them already have. (I'm looking at an old standard.) You can configure them in hostapd.conf
# Additional vendor specific elements for Beacon and Probe Response frames
# This parameter can be used to add additional vendor specific element(s) into
# the end of the Beacon and Probe Response frames. The format for these
# element(s) is a hexdump of the raw information elements (id+len+payload for
# one or more elements)
vendor_elements=dd0411223301
The hex data is the of the following structure:
The Element ID shall be dd, OUI is a 3-byte number allocated by IEEE, but the good news is iwlist displays all of them as unknown, except WPA (0050f2) and WPA2 (000fac).
| How to add an IE field for my wifi hotspot? |
1,450,365,687,000 |
I've a PC with an Intel Wireless 8260 running Debian Unstable. networking.service slows the startup (with systemd) down with 1 minute and ~5 seconds. I'm running version 4.8.15-2 of the Linux kernel with version 20161130-2 of the iwlwifi firmware. After my system has finally started up, the internet is slow and I've to run sudo iw dev wlan set power_save off to make the speed acceptable, but still not the full speed I get on my cheap Windows laptop. The output of sudo dmesg | grep iwl is:
[ 4.668210] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[ 4.681311] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-8000C-24.ucode (-2)
[ 4.681313] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8000C-24.ucode failed with error -2
[ 4.681326] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-8000C-23.ucode (-2)
[ 4.681327] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8000C-23.ucode failed with error -2
[ 4.695991] iwlwifi 0000:01:00.0: firmware: direct-loading firmware iwlwifi-8000C-22.ucode
[ 4.696663] iwlwifi 0000:01:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm
[ 4.732100] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
[ 4.734471] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[ 4.735424] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[ 4.897671] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 66.833134] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[ 66.833550] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[ 66.972299] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[ 66.972727] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
The output of sudo iwconfig wlan0 is:
wlan0 IEEE 802.11 ESSID:"VFNL-DE1BA0"
Mode:Managed Frequency:2.447 GHz Access Point: 00:1D:AA:DE:1B:A0
Bit Rate=270 Mb/s Tx-Power=22 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=51/70 Signal level=-59 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:23 Missed beacon:0
How can I make my system startup fast and get the full speed of my internet?
|
There was a bug report filed against Ubuntu a few years back that said
echo "options iwlwifi 11n_disable=8" | sudo tee -a /etc/modprobe.d/iwlwifi.conf Would help regain the performance by enabling aggressive tx
You will need to reboot or unload and load iwlwifi to see the change
| Intel Wireless 8260 slow |
1,450,365,687,000 |
My desktop has lost wireless connectivity and I strongly suspect a hardware issue, but I would like to know how I can confirm that that is the problem before I buy a replacement.
My reasons for thinking this are:
My NIC was a standard size, but I have a low profile case so, as a bodge, I cut the metal bracket. This worked fine, but it's never felt like it was seated properly, so may have died due to my own miserly stupidity
I use wicd-curses to connect to my network and it no longer detected any SSIDs.
running sudo ifconfig wlan0 up returns SIOCSIFFLAGS: Connection timed out
running iw dev shows my device details
running sudo ip link set wlan0 up returns RTNETLINK answers: Connection timed out
dmesg gives:
iwlwifi 0000:01:00.0: Failed to load firmware chunk!
iwlwifi 0000:01:00.0: Could not load the [0] uCode section
iwlwifi 0000:01:00.0: Failed to start INIT ucode: -110
iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
I've exhausted my limited knowledge and Google searching from my phone isn't leading me anywhere. I'm really not familiar with this stuff, so any background info to help me understand what's going on here is very much appreciated!
OS: Xubuntu 16.04 (relatively recently upgraded from 14.04)
Kernel: 4.4.0-47
Edit: I found the solution to my lost connectivity, but I still don't know why. I am therefore leaving this question here in the hope that someone can answer my original question: how can I debug this kind of problem?
|
The solution to my actual problem of lost connectivity has been solved thanks to an answer on the AskUbuntu StackExchange. The solution was to disable power management as follows:
sudo iwconfig wlan0 power off
I did not need to disable the 802.11n extension.
| iwlwifi: Failed to start INIT ucode: -110 |
1,450,365,687,000 |
Connecting to a 2.4 GHz access point broke at some point of updating (don't remember exactly where, either kernel or iw update). When connecting associating times out and the whole connection process is cancel after few tries. 5 GHz access points still work normally as expected.
I tried several different distributions (Fedora 32, Pop!_OS 20.04, Ubuntu 20.04) and all of them have the same issue (I run them in a live environment).
The only distro that worked was Elementary OS 5.1. I assume that it is because it's based on Ubuntu 18.04 with older kernel and iw (linux 5.3.0, iw 4.14).
Bellow are my specs and a dmesg log when trying to connect to the 2.4 GHz access point.
Laptop: Thinkpad T540p
Wifi card: Intel Corporation Wireless 7260 (rev 83)
Router/Access Point: TP-Link Archer C6 v2.0 (don't think this is the issue, works fine for other devices)
Kernel: 5.8.7-arch1-1
iw --version: 5.8
wpa_supplicant -v: v2.9
[ 452.449105] wlan0: authenticate with 0c:80:63:xx:xx:xx
[ 452.452141] wlan0: send auth to 0c:80:63:xx:xx:xx (try 1/3)
[ 452.457298] wlan0: authenticated
[ 452.460765] wlan0: associate with 0c:80:63:xx:xx:xx (try 1/3)
[ 452.564113] wlan0: associate with 0c:80:63:xx:xx:xx (try 2/3)
[ 452.667437] wlan0: associate with 0c:80:63:xx:xx:xx (try 3/3)
[ 452.770826] wlan0: association with 0c:80:63:xx:xx:xx timed out
|
Solved by applying options iwlwifi i11n_disable=1 to /etc/modprobe.d/iwlwifi.conf
On newer versions the option is renamed as 11n_disable
| 2.4 GHz Wi-Fi associating timing out |
1,450,365,687,000 |
We recently upgrade our internet provider which now comes with 2.4Ghz and 5Ghz wifi. I can connect properly on 2.4Ghz while on 5Ghz I am experiencing random "lags" in the connection. More specifically, the network manager is not disconnecting from the router however to refresh a page in a browser when the lag strikes it needs 7-30 seconds. Some times ssh connection is dropped too. This is happening in a random manner but usually every 3-5 minutes.
I tried to change the 5Ghz channel with no luck. The rest of the devices in the house are not experiencing any issues.
I 've already tried to reinstall Intel 3160 drives from backports as well as to reinstall the linux-image with no luck. I 've also disabled wifi.powersave to wlan0 with no luck.
Does anyone have an idea how to solve or debug this issue?
These are some system information:
uname -a:
Linux debian 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u5 (2018-09-30) x86_64 GNU/Linux (Debian stretch)
lshw -C network:
*-network
description: Wireless interface
product: Wireless 3160
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 93
serial: 34:e6:ad:be:63:65
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=4.9.0-8-amd64 firmware=17.948900127.0 ip=192.168.0.17 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:49 memory:c1000000-c1001fff
iwconfig:
wlan0 IEEE 802.11 ESSID:"BRA****"
Mode:Managed Frequency:5.56 GHz Access Point: F8:AB:05:00:1E:DE
Bit Rate=390 Mb/s Tx-Power=22 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=62/70 Signal level=-48 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:125 Missed beacon:0
ifconfig:
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.17 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::36e6:adff:febe:6365 prefixlen 64 scopeid 0x20<link>
inet6 2a02:8109:a3c0:55af:36e6:adff:febe:6365 prefixlen 64 scopeid 0x0<global>
ether 34:e6:ad:be:63:65 txqueuelen 1000 (Ethernet)
RX packets 415816 bytes 507186123 (483.6 MiB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 144134 bytes 31353570 (29.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisi
lspci -k -nn | grep -A 3 -i net:
03:00.0 Network controller [0280]: Intel Corporation Wireless 3160 [8086:08b4] (rev 93)
Subsystem: Intel Corporation Dual Band Wireless AC 3160 [8086:8270]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
modinfo iwlwifi:
filename: /lib/modules/4.9.0-8-amd64/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
license: GPL
author: Copyright(c) 2003- 2015 Intel Corporation <[email protected]>
description: Intel(R) Wireless WiFi driver for Linux
firmware: iwlwifi-100-5.ucode
firmware: iwlwifi-1000-5.ucode
firmware: iwlwifi-135-6.ucode
firmware: iwlwifi-105-6.ucode
firmware: iwlwifi-2030-6.ucode
firmware: iwlwifi-2000-6.ucode
firmware: iwlwifi-5150-2.ucode
firmware: iwlwifi-5000-5.ucode
firmware: iwlwifi-6000g2b-6.ucode
firmware: iwlwifi-6000g2a-6.ucode
firmware: iwlwifi-6050-5.ucode
firmware: iwlwifi-6000-4.ucode
firmware: iwlwifi-7265D-26.ucode
firmware: iwlwifi-7265-17.ucode
firmware: iwlwifi-3168-26.ucode
firmware: iwlwifi-3160-17.ucode
firmware: iwlwifi-7260-17.ucode
firmware: iwlwifi-8265-26.ucode
firmware: iwlwifi-8000C-26.ucode
firmware: iwlwifi-9000-pu-a0-lc-a0--26.ucode
firmware: iwlwifi-9260-th-a0-jf-a0--26.ucode
firmware: iwlwifi-9000-pu-a0-jf-a0--26.ucode
firmware: iwlwifi-Qu-a0-jf-b0--26.ucode
alias: pci:v00008086d00002720sv*sd00000A10bc*sc*i*
alias: pci:v00008086d0000A370sv*sd00001030bc*sc*i*
alias: pci:v00008086d00002526sv*sd00001030bc*sc*i*
alias: pci:v00008086d000031DCsv*sd00000030bc*sc*i*
[...]
depends: cfg80211
retpoline: Y
intree: Y
vermagic: 4.9.0-8-amd64 SMP mod_unload modversions
parm: swcrypto:using crypto in software (default 0 [hardware]) (int)
parm: 11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)
parm: amsdu_size:amsdu size 0: 12K for multi Rx queue devices, 4K for other devices 1:4K 2:8K 3:12K (default 0) (int)
parm: fw_restart:restart firmware in case of error (default true) (bool)
parm: antenna_coupling:specify antenna coupling in dB (default: 0 dB) (int)
parm: nvm_file:NVM file name (charp)
parm: d0i3_disable:disable d0i3 functionality (default: Y) (bool)
parm: lar_disable:disable LAR functionality (default: N) (bool)
parm: uapsd_disable:disable U-APSD functionality bitmap 1: BSS 2: P2P Client (default: 3) (uint)
parm: bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
parm: led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 0) (int)
parm: power_save:enable WiFi power management (default: disable) (bool)
parm: power_level:default power save level (range from 1 - 5, default: 1) (int)
parm: fw_monitor:firmware monitor - to debug FW (default: false - needs lots of memory) (bool)
parm: d0i3_timeout:Timeout to D0i3 entry when idle (ms) (uint)
parm: disable_11ac:Disable VHT capabilities (default: false) (bool)
|
It seems that problem was the wifi adapter driver. I successfully solved the issue by upgrading the Kernel to the latest version (4.18) that is included in the stretch-backports repository.
Apt should have backports sources enabled
for Debian Stretch, append the following in /etc/apt/sources.list :
deb http://ftp.debian.org/debian stretch-backports main contrib non-free
deb-src http://ftp.debian.org/debian stretch-backports main contrib non-free
then install the kernel:
sudo apt update && sudo apt -t stretch-backports install linux-image-4.18.0-0.bpo.1-amd64 linux-headers-4.18.0-0.bpo.1-amd64
and reboot to load the new kernel.
| iwlwifi 5Ghz internet randomly lags for seconds |
1,450,365,687,000 |
I have just installed debian 9 on my msi laptop. It is the only OS on the computer.
While it was installing I had no network access and it stated that it could not find the firmware iwlwifi-3168-26.ucode,iwlwifi-3168-25.ucode,iwlwifi-3168-24.ucode,iwlwifi-3168-23.ucode and iwlwifi-3168-22.ucode.
the install finished and I tried the obvious sudo apt-get install firmware-iwlwifi which gave me this:
Package firmware-iwlwifi is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'firmware-iwlwifi' has no installation candidate.
I then followed the advice of downloading the iwlwifi-3168-29.ucode file and manually putting it in /lib/firmware, then rebooting the machine with no change.
It's worth noting that while my wired connection works ok, in the network manager (Cinnamon desktop) there isn't even a Wi-Fi option. I tried manually entering the Wi-Fi network details but it refused to connect.
ifconfig output:
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.25.14.118 netmask 255.255.0.0 broadcast 10.25.255.255
inet6 fe80::329c:23ff:fe15:2004 prefixlen 64 scopeid 0x20<link>
ether 30:9c:23:15:20:04 txqueuelen 1000 (Ethernet)
RX packets 214505 bytes 276211608 (263.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 23769 bytes 2129086 (2.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 19
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 168 bytes 13356 (13.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 168 bytes 13356 (13.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I also tried building it from the git git clone https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git but it refused to build.
I have reinstalled the OS five times now.
|
Package firmware-iwlwifi is in the non-free section of Debian and not "enabled" by default.
Add "non-free" to your entries in /etc/apt/sources.list like described here (scroll down a bit).
Example sources.list from the above link:
deb http://deb.debian.org/debian stretch main contrib non-free
deb-src http://deb.debian.org/debian stretch main contrib non-free
deb http://deb.debian.org/debian-security/ stretch/updates main contrib non-free
deb-src http://deb.debian.org/debian-security/ stretch/updates main contrib non-free
deb http://deb.debian.org/debian stretch-updates main contrib non-free
deb-src http://deb.debian.org/debian stretch-updates main contrib non-free
Then run apt-get update and apt-get install firmware-iwlwifi as root.
| firmware-iwlwifi missing in debian 9 |
1,450,365,687,000 |
After using my laptop for a while, wifi drops and kernel returns
iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
iwlwifi 0000:03:00.0: Could not load the [0] uCode section
iwlwifi 0000:03:00.0: Failed to run INIT ucode: -5
iwlwifi 0000:03:00.0: Unable to initialize device.
I'm running on an x230 running
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
|
The only way to recover from this is to remove the device, and rescan. This forces the kernel to re-add the device, and resolves all wifi issues.
echo 1 | sudo tee /sys/bus/pci/devices/0000:03:00.0/remove
sleep 3
echo 1 | sudo tee /sys/bus/pci/rescan
This assumes your device is 0000:03:00.0 you can find this number with lspci | grep Centrino
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
Answer provided by bakedcow on /r/archlinux
| iwlwifi: Failed to run INIT ucode: -5 |
1,450,365,687,000 |
I first came across this when I was trying to make a python program that used programs to scan for wireless networks. I've used the following tools:
iwlist, iw, wpa_cli, nmcli, and iwconfig
I run into the same behavior on all of them. Suppose you're sitting by your computer and wireless access point/router. Type out one of the following commands, assuming your wifi adapter is named wlan0, turn of the router, then press enter in the terminal window.
iw wlan0 scan | grep SSID
iwlist wlan0 scan | grep SSID
wpa_cli -i wlan0 scan && wpa_cli -i wlan0 scan_results
nmcli device wifi rescan && nmcli device wifi list
All of the commands still show the SSID for quite some time. I imagine longer than it would take for the E&M standing wave to disappear. Does anyone have any fix for this problem?
|
I solved this quite awhile ago, my apologies for leaving it unanswered. The following wpa_supplicant settings are responsible for the wifi behavior mentioned above:
bss_expire_count and bss_expire_age
The former is how many scans the SSID has to be missing from before it removes it from the list. The latter is the time in seconds to display an SSID after it's no longer broadcasting
| WiFi scans show SSID of a powered off network for several scans afterwards |
1,450,365,687,000 |
I can't get my WLAN working on a fresh Debian 8.7.1 64bit installation. Maybe you can help me find the issue. The card I am using is an Intel 8260 WLAN/Bluetooth card:
# lspci | grep Wire
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
I installed iwlwifi with apt and loaded the module:
# modprobe -r iwlwifi ; modprobe iwlwifi
lsmod output:
# lsmod | grep wif
iwlwifi 96547 0
cfg80211 413730 1 iwlwifi
iwconfig:
# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
So what am I missing?! I am getting the feel it's because of the firmware not supporting the Kernel?
root@dfog:/home/irrgeist# uname -a
Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux
I rebooted the system.
Edit:
#ls /lib/firmware/
av7110 iwlwifi-3160-8.ucode iwlwifi-7260-8.ucode
carl9170-1.fw iwlwifi-3160-9.ucode iwlwifi-7260-9.ucode
cis iwlwifi-3945-2.ucode iwlwifi-7265-8.ucode
dsp56k iwlwifi-4965-2.ucode iwlwifi-7265-9.ucode
hp iwlwifi-5000-2.ucode iwlwifi-8000C-13.ucode
intel iwlwifi-5000-5.ucode iwlwifi-8265-22.ucode
isci iwlwifi-5150-2.ucode keyspan_pda
iwlwifi-1000-5.ucode iwlwifi-6000-4.ucode RTL8192E
iwlwifi-100-5.ucode iwlwifi-6000g2a-5.ucode RTL8192SU
iwlwifi-105-6.ucode iwlwifi-6000g2a-6.ucode rtl_nic
iwlwifi-135-6.ucode iwlwifi-6000g2b-6.ucode rtlwifi
iwlwifi-2000-6.ucode iwlwifi-6050-4.ucode usbduxfast_firmware.bin
iwlwifi-2030-6.ucode iwlwifi-6050-5.ucode usbdux_firmware.bin
iwlwifi-3160-7.ucode iwlwifi-7260-7.ucode usbduxsigma_firmware.bin
sources.list
#
# deb cdrom:[Debian GNU/Linux 8.7.1 _Jessie_ - Official amd64 NETINST Binary-1 20170116-10:57]/ jessie main
#deb cdrom:[Debian GNU/Linux 8.7.1 _Jessie_ - Official amd64 NETINST Binary-1 20170116-10:57]/ jessie main
deb http://ftp.de.debian.org/debian/ jessie main non-free contrib
deb-src http://ftp.de.debian.org/debian/ jessie main non-free contrib
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
# jessie-updates, previously known as 'volatile'
deb http://ftp.de.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.de.debian.org/debian/ jessie-updates main contrib non-free
deb http://ftp.de.debian.org/debian/ jessie-backports main contrib non-free
|
According to the official website the Intel® Dual Band Wireless-AC 8260 work on kernel version 4.1 and higher.
You can add the backports repo to your sources.list
deb http://ftp.debian.org/debian jessie-backports main non-free
Update and run apt-cache search linux-image to get the available linux-image then install a kernel > 4.1
e,g :
apt-get install linux-image-4.8.0-0.bpo.2-amd64
or the latest kernel version:
apt-get install linux-image-4.9.0-0.bpo.1-amd64-unsigned
Reboot your system and install the firmware-iwlwifi needed to get the Bluetooth working :
apt-get install -t jessie-backports firmware-iwlwifi
The wifi firmware iwlwifi-8000C-16.ucode is included on the firmware-iwlwifi package , also it can be added through :
wget https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-8000-ucode-16.242414.0.tgz
tar xvf iwlwifi-8000-ucode-16.242414.0.tgz
cd iwlwifi-8000-ucode-16.242414.0
cp iwlwifi* /lib/firmware
EDIT
To solve the black screen after installing the new kernel reinstall xserver-xorg-video-intel from backports , to get more info about the problem , see the answer of Stephen Kitt.
apt-get remove xserver-xorg-video-intel
apt-get install -t jessie-backports xserver-xorg-video-intel
| No Wlan or Bluetooth Debian 8.7.1 with Intel 8260 card |
1,450,365,687,000 |
I am trying to set up an AP using the following configuration:
Wi-Fi adapter: TP-Link AX3000 (Intel AX200 based)
Operating system: Ubuntu Server 20.10 (groovy)
Kernel version: 5.8.0-44-generic
Firmware: iwlwifi-cc-a0-55.ucode
AP service: hostapd v2.9 (tried the custom-build from the latest source code as well)
I have two almost identical setups in Canada and France. The one in Canada - works, the other one - no. As I tried to exclude any software configuration discrepancy, I ended up suspecting that this problem is somehow related to the regulatory domain. Below are the details from the failing setup.
As this setup is located in France, I set the regulatory domain respectively:
$ sudo iw reg set FR
Verifying it I get the following (initially):
$ sudo iw reg set
global
country FR: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#10 (self-managed)
country 00: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN
(5190 - 5210 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN
(5210 - 5230 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN
(5230 - 5250 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN
(5250 - 5270 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5270 - 5290 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5290 - 5310 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5310 - 5330 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5490 - 5510 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5510 - 5530 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5530 - 5550 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5550 - 5570 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5570 - 5590 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5590 - 5610 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5610 - 5630 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5630 - 5650 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5650 - 5670 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5670 - 5690 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5690 - 5710 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5710 - 5730 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5735 - 5755 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5815 - 5835 @ 20), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, PASSIVE-SCAN
To set the country value for the phy#10 interface, I trigger scanning with the following command:
$ sudo iw dev wlp3s0 scan
Then I verify the regulatory settings again to confirm that adapter determines it correctly:
$ sudo iw reg get
global
country FR: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#10 (self-managed)
country FR: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN
(5190 - 5210 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN
(5210 - 5230 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN
(5230 - 5250 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN
(5250 - 5270 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5270 - 5290 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5290 - 5310 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5310 - 5330 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5490 - 5510 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5510 - 5530 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5530 - 5550 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5550 - 5570 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5570 - 5590 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5590 - 5610 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5610 - 5630 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN
(5630 - 5650 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN
(5650 - 5670 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5670 - 5690 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5690 - 5710 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5710 - 5730 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5735 - 5755 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ
(5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ
(5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ
(5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ
(5815 - 5835 @ 20), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
At this moment, iw list gives the following output (trunkated to minimize content):
Frequencies:
* 5180 MHz [36] (22.0 dBm) (no IR)
* 5200 MHz [40] (22.0 dBm) (no IR)
* 5220 MHz [44] (22.0 dBm) (no IR)
* 5240 MHz [48] (22.0 dBm) (no IR)
* 5260 MHz [52] (22.0 dBm) (no IR, radar detection)
* 5280 MHz [56] (22.0 dBm) (no IR, radar detection)
* 5300 MHz [60] (22.0 dBm) (no IR, radar detection)
* 5320 MHz [64] (22.0 dBm) (no IR, radar detection)
* 5340 MHz [68] (disabled)
* 5360 MHz [72] (disabled)
* 5380 MHz [76] (disabled)
* 5400 MHz [80] (disabled)
* 5420 MHz [84] (disabled)
* 5440 MHz [88] (disabled)
* 5460 MHz [92] (disabled)
* 5480 MHz [96] (disabled)
* 5500 MHz [100] (22.0 dBm) (no IR, radar detection)
* 5520 MHz [104] (22.0 dBm) (no IR, radar detection)
* 5540 MHz [108] (22.0 dBm) (no IR, radar detection)
* 5560 MHz [112] (22.0 dBm) (no IR, radar detection)
* 5580 MHz [116] (22.0 dBm) (no IR, radar detection)
* 5600 MHz [120] (22.0 dBm) (no IR, radar detection)
* 5620 MHz [124] (22.0 dBm) (no IR, radar detection)
* 5640 MHz [128] (22.0 dBm) (no IR, radar detection)
* 5660 MHz [132] (22.0 dBm) (no IR, radar detection)
* 5680 MHz [136] (22.0 dBm) (no IR, radar detection)
* 5700 MHz [140] (22.0 dBm) (no IR, radar detection)
* 5720 MHz [144] (22.0 dBm) (no IR, radar detection)
* 5745 MHz [149] (22.0 dBm)
* 5765 MHz [153] (22.0 dBm)
* 5785 MHz [157] (22.0 dBm)
* 5805 MHz [161] (22.0 dBm)
* 5825 MHz [165] (22.0 dBm)
* 5845 MHz [169] (disabled)
* 5865 MHz [173] (disabled)
* 5885 MHz [177] (disabled)
* 5905 MHz [181] (disabled)
With the following hostapd.conf:
ctrl_interface=/var/run/hostapd/
interface=wlan0 # overwritten with -i option
driver=nl80211
country_code=FR
ieee80211n=1
hw_mode=a
ieee80211ac=1
channel=149 # 5745 MHz
require_ht=1
require_vht=1
ieee80211d=1 # no impact on result with 0 as well
ieee80211h=1 # no impact on result with 0 as well
ssid=test-open
ieee80211w=2
auth_algs=1
wpa=0
I get the following output:
$ sudo hostapd /etc/hostapd/hostapd-5ghz-open.conf -i wlp3s0 -dd
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd/hostapd-5ghz-open.conf
nl80211: TDLS supported
nl80211: TDLS external setup
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported cipher 00-0f-ac:8
nl80211: Supported cipher 00-0f-ac:9
nl80211: Supported cipher 00-0f-ac:6
nl80211: Supported cipher 00-0f-ac:11
nl80211: Supported cipher 00-0f-ac:12
nl80211: Using driver-based off-channel TX
nl80211: Driver-advertised extended capabilities (default) - hexdump(len=8): 04 00 00 00 00 00 00 40
nl80211: Driver-advertised extended capabilities mask (default) - hexdump(len=8): 04 00 00 00 00 00 00 40
nl80211: Driver-advertised extended capabilities for interface type STATION
nl80211: Extended capabilities - hexdump(len=10): 04 00 40 00 00 00 00 40 00 20
nl80211: Extended capabilities mask - hexdump(len=10): 04 00 40 00 00 00 00 40 00 20
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: Enable multi-channel concurrent (driver advertised support)
nl80211: use P2P_DEVICE support
nl80211: key_mgmt=0x1ff0f enc=0x76f auth=0x7 flags=0x5800530fb5bfbe0 rrm_flags=0x79 probe_resp_offloads=0x0 max_stations=0 max_remain_on_chan=10000 max_scan_ssids=20
nl80211: interface wlp3s0 in phy phy10
nl80211: Set mode ifindex 14 iftype 3 (AP)
nl80211: Failed to set interface 14 to mode 3: -16 (Device or resource busy)
nl80211: Try mode change after setting interface down
nl80211: Set mode ifindex 14 iftype 3 (AP)
nl80211: Mode change succeeded while interface is down
nl80211: Setup AP(wlp3s0) - device_ap_sme=0 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x55cefdc6f780
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x55cefdc6f780 match= multicast=0
nl80211: Register frame type=0x0 (WLAN_FC_STYPE_ASSOC_REQ) nl_handle=0x55cefdc6f780 match= multicast=0
nl80211: Register frame type=0x20 (WLAN_FC_STYPE_REASSOC_REQ) nl_handle=0x55cefdc6f780 match= multicast=0
nl80211: Register frame type=0xa0 (WLAN_FC_STYPE_DISASSOC) nl_handle=0x55cefdc6f780 match= multicast=0
nl80211: Register frame type=0xc0 (WLAN_FC_STYPE_DEAUTH) nl_handle=0x55cefdc6f780 match= multicast=0
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0x55cefdc6f780 match= multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55cefdc6f780 match=04 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55cefdc6f780 match=0501 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55cefdc6f780 match=0503 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55cefdc6f780 match=0504 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55cefdc6f780 match=06 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55cefdc6f780 match=08 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55cefdc6f780 match=09 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55cefdc6f780 match=0a multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55cefdc6f780 match=11 multicast=0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55cefdc6f780 match=7f multicast=0
rfkill: initial event: idx=10 type=1 op=0 soft=0 hard=0
nl80211: Add own interface ifindex 14 (ifidx_reason -1)
nl80211: if_indices[16]: 14(-1)
nl80211: Do not open EAPOL RX socket - using control port for RX
phy: phy10
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
wlp3s0: interface state UNINITIALIZED->COUNTRY_UPDATE
Previous country code FR, new country code FR
nl80211: No channel number found for frequency 5905 MHz
nl80211: Regulatory information - country=00
nl80211: 2402-2437 @ 40 MHz 22 mBm
nl80211: 2422-2462 @ 40 MHz 22 mBm
nl80211: 2447-2482 @ 40 MHz 22 mBm
nl80211: 5170-5190 @ 160 MHz 22 mBm (no outdoor) (no IR)
nl80211: 5190-5210 @ 160 MHz 22 mBm (no outdoor) (no IR)
nl80211: 5210-5230 @ 160 MHz 22 mBm (no outdoor) (no IR)
nl80211: 5230-5250 @ 160 MHz 22 mBm (no outdoor) (no IR)
nl80211: 5250-5270 @ 160 MHz 22 mBm (DFS) (no IR)
nl80211: 5270-5290 @ 160 MHz 22 mBm (DFS) (no IR)
nl80211: 5290-5310 @ 160 MHz 22 mBm (DFS) (no IR)
nl80211: 5310-5330 @ 160 MHz 22 mBm (DFS) (no IR)
nl80211: 5490-5510 @ 240 MHz 22 mBm (DFS) (no IR)
nl80211: 5510-5530 @ 240 MHz 22 mBm (DFS) (no IR)
nl80211: 5530-5550 @ 240 MHz 22 mBm (DFS) (no IR)
nl80211: 5550-5570 @ 240 MHz 22 mBm (DFS) (no IR)
nl80211: 5570-5590 @ 240 MHz 22 mBm (DFS) (no IR)
nl80211: 5590-5610 @ 240 MHz 22 mBm (DFS) (no IR)
nl80211: 5610-5630 @ 240 MHz 22 mBm (DFS) (no IR)
nl80211: 5630-5650 @ 240 MHz 22 mBm (DFS) (no IR)
nl80211: 5650-5670 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5670-5690 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5690-5710 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5710-5730 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5735-5755 @ 80 MHz 22 mBm (no IR)
nl80211: 5755-5775 @ 80 MHz 22 mBm (no IR)
nl80211: 5775-5795 @ 80 MHz 22 mBm (no IR)
nl80211: 5795-5815 @ 80 MHz 22 mBm (no IR)
nl80211: 5815-5835 @ 20 MHz 22 mBm (no IR)
nl80211: Added 802.11b mode based on 802.11g information
nl80211: Mode IEEE 802.11g: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484[DISABLED]
nl80211: Mode IEEE 802.11a: 5180[NO_IR] 5200[NO_IR] 5220[NO_IR] 5240[NO_IR] 5260[NO_IR][RADAR] 5280[NO_IR][RADAR] 5300[NO_IR][RADAR] 5320[NO_IR][RADAR] 5340[DISABLED] 5360[DISABLED] 5380[DISABLED] 5400[DISABLED] 5420[DISABLED]
nl80211: Mode IEEE 802.11b: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484[DISABLED]
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=12 freq=2467 MHz max_tx_power=22 dBm
Allowed channel: mode=1 chan=13 freq=2472 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=12 freq=2467 MHz max_tx_power=22 dBm
Allowed channel: mode=0 chan=13 freq=2472 MHz max_tx_power=22 dBm
Frequency 5745 (primary) not allowed for AP mode, flags: 0x20053 NO-IR
Primary frequency not allowed
wlp3s0: IEEE 802.11 Configured channel (149) or frequency (5745) (secondary_channel=0) not found from the channel list of the current mode (2) IEEE 802.11a
wlp3s0: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-3)
wlp3s0: interface state COUNTRY_UPDATE->DISABLED
wlp3s0: AP-DISABLED
wlp3s0: Unable to setup interface.
hostapd_interface_deinit_free(0x55cefdc67e00)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0x55cefdc67e00)
wlp3s0: interface state DISABLED->DISABLED
hostapd_bss_deinit: deinit bss wlp3s0
wlp3s0: Deauthenticate all stations
nl80211: send_mlme - da=ff:ff:ff:ff:ff:ff noack=0 freq=0 no_cck=0 offchanok=0 wait_time=0 no_encrypt=0 fc=0xc0 (WLAN_FC_STYPE_DEAUTH) nlmode=3
nl80211: send_mlme - Use bss->freq=0
nl80211: send_mlme -> send_frame_cmd
nl80211: CMD_FRAME freq=0 wait=0 no_cck=0 no_ack=0 offchanok=0
CMD_FRAME - hexdump(len=26): c0 00 00 00 ff ff ff ff ff ff 5c 80 b6 b8 dd af 5c 80 b6 b8 dd af 00 00 03 00
nl80211: Frame command failed: ret=-22 (Invalid argument) (freq=0 wait=0)
wlp3s0: AP-DISABLED
hostapd_cleanup(hapd=0x55cefdc68fe0 (wlp3s0))
wlp3s0: CTRL-EVENT-TERMINATING
hostapd_free_hapd_data: Interface wlp3s0 wasn't started
hostapd_interface_deinit_free: driver=0x55cefc144c60 drv_priv=0x55cefdc6a1f0 -> hapd_deinit
nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
nl80211: Remove monitor interface: refcount=0
nl80211: Remove beacon (ifindex=14)
netlink: Operstate: ifindex=14 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
nl80211: Set mode ifindex 14 iftype 2 (STATION)
nl80211: Failed to set interface 14 to mode 2: -16 (Device or resource busy)
nl80211: Try mode change after setting interface down
nl80211: Set mode ifindex 14 iftype 2 (STATION)
nl80211: Mode change succeeded while interface is down
nl80211: Teardown AP(wlp3s0) - device_ap_sme=0 use_monitor=0
nl80211: Unsubscribe mgmt frames handle 0x8888dd46754e7f09 (AP teardown)
hostapd_interface_free(0x55cefdc67e00)
hostapd_interface_free: free hapd 0x55cefdc68fe0
hostapd_cleanup_iface(0x55cefdc67e00)
hostapd_cleanup_iface_partial(0x55cefdc67e00)
hostapd_cleanup_iface: free iface=0x55cefdc67e00
The following lines from the above trigger my concern:
wlp3s0: interface state UNINITIALIZED->COUNTRY_UPDATE
Previous country code FR, new country code FR
nl80211: No channel number found for frequency 5905 MHz
nl80211: Regulatory information - country=00
Why does regulatory information is reset to the world domain provided that I set the correct country value? Is it caused by nl80211 driver, hostapd service, hardware or something else? I will appreciate any ideas which could provide me with some clarity on this subject.
|
To my surprise, the solution was installing the network-manager package. No additional configuration was required, not even setting the wireless interface as managed by NetworkManager. I replicated the same behaviour on another system (Raspberry Pi CM4 board with Ubuntu Server 20.04).
Just a note, Ubuntu Server comes with systemd-networkd as the default service for managing network, whereas Ubuntu Desktop comes with NetworkManager.
| Why can't hostapd service start AP configured in the 5 GHz band using Intel AX200 based adapter? |
1,450,365,687,000 |
I just completed a desktop build and installed Linux Mint 17.3 and the PCIe WiFi card is not being detected at all. The card is a Gigabyte GC-WB867D-I.
There is nothing that recognizes the device to be present but missing a driver, but rather it is like there is nothing there at all.
I used Ethernet to perform all the recommended updates in the software center, and opened the driver manager and it told me that no devices were installed. I have also tried moving to a different PCIe slot on the motherboard and encountered the same symptoms.
I also read in the Amazon reviews of the WiFi card that it uses the Intel 7260AC chip, and so I downloaded the iwlwifi driver that I found on the Intel website and cp'd it into /library/firmware and rebooted. I don't know if that accomplishes anything or not.
I have also run sudo apt-get install linux-firmware and sudo apt-get install linux-firmware-nonfree.
Finally, here are the results of lspci
lspci
00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31)
00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1)
00:1b.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #19 (rev f1)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1)
00:1c.3 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #4 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
02:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 04)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
06:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
Here is the full parts list of the build:
The output of lspci -knn | grep Net is:
06:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Device [8086:1010]
|
According to wireless.wiki the Intel® Wireless 8260 device is supported by the kernel 4.1 and later ,
Install build-essential and linux headers
download iwlwifi-8000-ucode-25.30.13.0.tgz from here
Type the following command:
tar -zxvf iwlwifi-8000-ucode-25.30.13.0.tgz
cd iwlwifi-8000-ucode-25.30.13.0
sudo cp iwlwifi*.ucode /lib/firmware/
Download backport from here example:
wget https://www.kernel.org/pub/linux/kernel/projects/backports/stable/v4.3/backports-4.3-1.tar.gz
Unzip it and compile the iwlwifi module:
cd backports-4.3-1
make defconfig-iwlwifi
make
sudo make install
Reboot
| WiFi card on new build is not recognized by Linux Mint 17.3 |
1,450,365,687,000 |
Router: OpenWrt with CZ region successfully set for all WiFi adapters.
System: Linux Mint 20.1 Cinnamon, official link
WiFi driver: iwlwifi:
readlink /sys/class/net/wlp60s0/device/driver
../../../../bus/pci/drivers/iwlwifi
Problem:
iw reg get
shows BZ region, I remember to have set this region temporarily in my router, but not in computer(s).
What I tried:
sudo iw reg set CZ
That on one computer worked until reboot, on a second computer did not work at all.
Question
How to set country (region) for WiFi globally in Linux Mint 20.1 (Ubuntu 20.04 based) for the setting to apply across reboots?
|
I managed to find this file:
/etc/default/crda
which contains the following info:
Set REGDOMAIN to a ISO/IEC 3166-1 alpha2 country code so that iw(8) may set the initial regulatory domain setting for IEEE 802.11 devices which operate on this system. Governments assert the right to regulate usage of radio spectrum within their respective territories so make sure you select a ISO/IEC 3166-1 alpha2 country code suitable for your location or you may infringe on local legislature. See /usr/share/zoneinfo/zone.tab for a table of timezone descriptions containing ISO/IEC 3166-1 alpha2 country codes.
along with one setting only in my laptop, and blank (unset) on the second one:
REGDOMAIN=BZ
So the answer is to safely edit this file, e.g.:
sudoedit /etc/default/crda
editing the 2-letter country code.
To apply the new configuration:
sudo netplan apply
sudo systemctl restart network-manager.service
| How to set country (region) for WiFi globally in Linux Mint 20? |
1,450,365,687,000 |
I just bought an Intel NUC6i3SYH and I installed Debian Jessie on it. I couldn't get the WiFi working. I already tried installing firmware-iwlwifi by following this tutorial, but it still doesn't work. I also tried installing with the Debian non-free installer, but it also doesn't work. It also doesn't work with Lubuntu, but it works with Linux Mint. How can I get it working with Debian?
|
According to wireles-wiki-kernel Intel® Wireless 8260 is supported by Kernel version > 4.1. To get wifi working you need to install the required firmware from backport (the easy way) or Upgrade your current kernel version.
First you need to enable backport
echo deb http://ftp.debian.org/debian jessie-backports main contrib non-free | sudo tee /etc/apt/sources.list.d/jessie-backports.list
Then install the required firmware through the following command:
sudo apt-get update && sudo apt-get install -t jessie-backports firmware-iwlwifi
| WiFi on Intel NUC6i3SYH |
1,450,365,687,000 |
I recently installed Debian 11 (bullseye) onto a second SSD in my computer (so I'm dual-booting with Windows on another). I used the official installation image and had to include the firmware-iwlwifi package on the installation drive which worked fine and was able to use my wifi adapter during installation.
Since then, when I boot into Debian and check the GNOME settings dialog I see "No Wi-Fi Adapter Found". However, this is inconsistent and it's sometimes working fine (I've yet to notice any pattern behind this).
I've discovered that my wifi adapter is an "Intel Wi-Fi 6 AX200 160MHz" and you can see in the snippet of output from lspci -v here it is listed along with the iwlwifi firmware:
04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX200
Kernel modules: iwlwifi
I can also see that the module is currently loaded, as per this snippet of output from lsmod (note that third column is showing it is used by 0 running programs):
iwlwifi 294912 0
I've done some searching around and all previous questions I could find related to this (such as this one) are for an older Linux kernel or older versions of Debian (suggesting to use the backported package). However, as I understand it, my adapter should be supported by the latest version of package-iwlwifi for bullseye which I have installed.
What might cause this behaviour or what steps might I take to find and resolve the problem?
|
I was able to find the problem thanks to these specific lines of output from dmesg | grep iwl which show iwlwifi failing to probe the adapter:
[ 56.478063] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[ 56.511447] iwlwifi: probe of 0000:04:00.0 failed with error -110
Searching more specifically for failed probing lead me to find that the problem was due to duel booting with Windows 10 and having the Windows "fast startup" feature enabled (on by default). Disabling this has resolved the issue for me.
Relevant text from
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#about_dual-boot_with_windows_and_fast-boot_enabled:
If you have a dual-boot machine with a recent version of Windows and start seeing problems during initialization of the WiFi device when booting Linux, the problem could be due to the “fast startup” feature on Windows.
With this feature enabled, Windows don't really shut down the entire system, but leaves things partially running so you can start the machine faster again. Try to disable this option, on Windows 10 it should be in “Control Panel→Hardware and Sound→Power Options→System Settings”. Select “Chooose what the power buttons do” to access the System Settings from the Power Options. Then disable the “Fast Startup” option in “Shutdown Settings”. This will cause Windows to fully shutdown and may solve the issue.
| What is causing my Intel AX200 wifi adapter to be undetected on Debian 11 with firmware-iwlwifi? |
1,450,365,687,000 |
I dual-boot kali linux with windows 10. After installation wifi is not working. I can run internet by using USB modem. It's surprising because during its installation i provided all the required firmwares for wifi and ethernet which installer was asking. The rest of the firmwares which were still missing, i copied them to /lib/firmware after installation. I've Intel Dual-Band Wireless AC-3165 wifi adapter.
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: acer-wireless: Wireless LAN
Soft blocked: yes
Hard blocked: no
|
Download the firmware from here or from here
wget https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-7265-ucode-16.242414.0.tgz
tar xvf iwlwifi-7265-ucode-16.242414.0.tgz
copy it to your /lib/firmware
cp iwlwifi* /lib/firmware
install the required package build-essential and linux-headers :
sudo apt-get install build-essential
Run apt-cache search linux-headers then install it
Download and compile backports:
wget https://www.kernel.org/pub/linux/kernel/projects/backports/2016/03/24/backports-20160324.tar.gz
tar xvf backports-20160324
cd backports-20160324
make defconfig-iwlwifi
make
make install
Reboot
Edit
Open the sources.list file:
apt edit-sources
Choose the text editor e,g : 1 (nano) add the following line ( verify it):
deb http://http.kali.org/kali kali-rolling main contrib non-free
Save it then run the following commands :
apt-get update
apt-get upgrade
apt-cache search linux-headers
Then install the appropriate linux-headers
e,g:
apt-get install linux-headers-4.8.0-kali1-amd64
apt-get install linux-image-4.8.0-kali1-amd64
Reboot your system , from the advanced option Boot Kali-linux with the 4.8.0 kernel version then compile backports .
Update
Blacklist acer_wmi solve the problem
| Wifi is not working in kali-linux |
1,450,365,687,000 |
Cant see WiFi Icon in Debian.
I'm using Dell Inspiron 15r 5520 i5.
This is the error I saw while installing.
Some of your hardware needs non-free firmware files to operate. The firmware can be loaded from removable media, such as a USB stick or floppy.
The missing firmware files are: iwlwifi-2030-6. ucode iwlwifi-2030-5. ucode
If you have such media available now, insert it, and continue.
Load missing firmware from removable media?
Should I change the links?
|
Your sources.list is correctly configured to install the non-free package firmware-iwlwifi which provide the iwlwifi-2030-6.ucode firmware. to install it:
sudo apt update
sudo apt install firmware-iwlwifi
Then run:
sudo modprobe -vr iwlwifi
sudo modprobe -v iwlwifi
To apply the security updates you need to add contrib non-free to the security repository.
deb http://security.debian.org/debian-security buster/updates main contrib non-free
Debian: Example sources.list
| Some of your hardware needs non-free firmware files to operate. The missing firmware files are: iwlwifi-2030-6. ucode iwlwifi-2030-5 |
1,450,365,687,000 |
In my journal I see the following a few times a day:
kernel: wlp2s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
lspci reports:
02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
My kernel version is 4.14.15-1-MANJARO.
|
Kernel Bug 198357 - iwlwifi: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22) lists the issue as:
CLOSED CODE_FIX
Kernel Version: 4.15.0-rc6-00048-ge1915c8195b3
Regression: Yes
My hope is that this will be made available to earlier maintained kernel versions in the near future.
| kernel: wlp2s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22) |
1,450,365,687,000 |
Most of my systems are based on CentOS 7 minimal. This includes by default a number of wireless-related packages:
$ yum list installed | grep iw
iw.x86_64 4.3-1.el7 @base
iwl100-firmware.noarch 39.31.5.1-62.2.el7_5 @updates
iwl1000-firmware.noarch 1:39.31.5.1-62.2.el7_5 @updates
iwl105-firmware.noarch 18.168.6.1-62.2.el7_5 @updates
iwl135-firmware.noarch 18.168.6.1-62.2.el7_5 @updates
iwl2000-firmware.noarch 18.168.6.1-62.2.el7_5 @updates
iwl2030-firmware.noarch 18.168.6.1-62.2.el7_5 @updates
iwl3160-firmware.noarch 22.0.7.0-62.2.el7_5 @updates
iwl3945-firmware.noarch 15.32.2.9-62.2.el7_5 @updates
iwl4965-firmware.noarch 228.61.2.24-62.2.el7_5 @updates
iwl5000-firmware.noarch 8.83.5.1_1-62.2.el7_5 @updates
iwl5150-firmware.noarch 8.24.2.2-62.2.el7_5 @updates
iwl6000-firmware.noarch 9.221.4.1-62.2.el7_5 @updates
iwl6000g2a-firmware.noarch 17.168.5.3-62.2.el7_5 @updates
iwl6000g2b-firmware.noarch 17.168.5.2-62.2.el7_5 @updates
iwl6050-firmware.noarch 41.28.5.1-62.2.el7_5 @updates
iwl7260-firmware.noarch 22.0.7.0-62.2.el7_5 @updates
iwl7265-firmware.noarch 22.0.7.0-62.2.el7_5 @updates
I'm using these guest machines on a VM host and they should not ever use wireless.
In general, I'd like to uninstall anything that is not strictly necessary. Before I uninstall them and see what happens, I thought I'd ask here: is there any reason not to remove these packages?
|
No, there’s no reason not to uninstall them in a VM. There might be a dependency keeping those packages installed, but if there isn’t, you might as well remove them.
| Is there a reason not to uninstall wireless packages if no wireless is present? |
1,450,365,687,000 |
In Raspbian when I'm running command iwlist wlan0 scan | grep ESSID i'm getting results without SSID on it like below
ESSID:"OpenWrt"
ESSID:"dlink"
ESSID:"tplink"
ESSID:"linksys"
ESSID:"tenda"
ESSID:"pi"
ESSID:""
ESSID:"somessid"
ESSID:""
ESSID:"router"
ESSID:""
ESSID:""
ESSID:""
I don't why I getting this blank SSID lines. my work environment may have some hidden network. not sure. but I need to remove this before send to front end processing. how can I achieve this
|
$ iwlist wlan0 scan | grep 'ESSID:"..*"'
ESSID:"OpenWrt"
ESSID:"dlink"
ESSID:"tplink"
ESSID:"linksys"
ESSID:"tenda"
ESSID:"pi"
ESSID:"somessid"
ESSID:"router"
. meta character matches any character
.* will match zero or more characters
Can also use grep -E 'ESSID:".+"' which will match at least one character between the double quotes
| Remove SSIDs without name in iwlist wlan scan |
1,450,365,687,000 |
I have got Acer Swift 3 SF314-42-R7TJ (NX.HSEEU.00H) without an OS preinstalled. I made a Debian installation USB following the manual. I tried different hybrid CD and DVD installation images, including images with non-free firmware. EFI immediately recognizes the installation media on boot. Debian installs, but on boot I get a black screen with a blinking white underscore (_). It seems to do not respond to keyboard. How should I proceed?
|
This laptop comes with function keys working as "media" keys by default. You can either disable it in BIOS or add Fn to all usual combinations with the function keys. To access a command line press Ctrl+Fn+Alt+F3.
This laptop comes with AMD Ryzen 5 4500U processor with integrated AMD Radeon™ Graphics, which, in this case, is a Renoir APU. According to Phoronix, it is not supported in older Linux 5.4 kernel, but is supported in newer Linux 5.7 kernel. firmware-amd-graphics in Debian "buster" (current stable release) does not support Renoir. "buster" also has older kernel. Both, firmware and newer kernel are available in its backports:
# echo deb http://deb.debian.org/debian buster-backports main non-free >> /etc/apt/sources.list
# apt update
# apt -t buster-backports install linux-image-amd64 firmware-amd-graphics
You can borrow and use a USB Ethernet adapter to connect the laptop to Internet. Alternatively, you can download individual packages from debian.org, copy them on a USB drive, mount it, and install with apt:
# apt install ./linux-image-5.8.0-0.bpo.2-amd64_5.8.10-1~bpo10+1_amd64.deb ./firmware-amd-graphics_20200918-1~bpo10+1_all.deb
To make Wi-Fi working you will also need to install firmware-iwlwifi from backports. It has firmware, probably AX201, which enables the advertised Wi-Fi 6 2×2 MU-MIMO (Intel Wireless Wi-Fi 6 AX200) + Bluetooth 5.0.
In "buster", it will use CPU with LLVMpipe for graphics. It will be slow only for graphics-hungry tasks.
Alternatively, if you move to testing ("bullseye") or unstable ("sid"), it will pull in the necessary kernel and non-free firmware. They also come with newer version of Mesa, which uses the integrated graphics. Since a recent update, under "bullseye", I keep running into a bug with integrated speakers not working while headphones work just fine.
If after installation you get "No Bootable Device", press Ctrl+Alt+Del to reboot and then keep pressing F2 during boot to get to UEFI setup. There, on the "Security" tab, you need to "Set Supervisor Password" first, then the option to "Select an UEFI file as trusted for executing" becomes available. (You can clear the password later by changing it to empty string.) The necessary file is under HDD0 → <EFI> → <debian> → <shimx64.efi>. The boot description can be anything. If you perform a re-install and UEFI refuses to save the file complaining that the file already exists, then "Erase all Secure Boot Setting" first and exit with saving UEFI settings.
| How to install Debian on Acer Swift 3 SF314-42? |
1,470,719,584,000 |
I just upgraded Jessie to testing by updating the sources.list and running the apt-get upgrade a reboot then apt-get dist-upgrade. A subsequent reboot revealed that the system won't boot. I receive the error messages of:
iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7260-15.ucode (-2)
iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7260-15.ucode failed with error -2
iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7260-14.ucode (-2)
iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7260-14.ucode failed with error -2
iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7260-13.ucode (-2)
iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7260-13.ucode failed with error -2
iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7260-12.ucode (-2)
iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7260-12.ucode failed with error -2
iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7260-11.ucode (-2)
iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7260-11.ucode failed with error -2
iwlwifi 0000:04:00.0: firmware : direct-loading firmware iwlwifi-7260-10.ucode
iwlwifi 0000:04:00.0: Firmware has old API version, expected v12 through v15, got v10.
iwlwifi 0000:04:00.0: New firmware can be obtained from http://www.intellinuxwirelsss.org/.
Followed by a reboot and the continuation of this. I booted in recovery mode and scanned through all the log files with cat [logfile] | grep error and the aforementioned errors are same ones which come up with the exception of a few minors.
I also tried booting into the 3.16 kernel as the testing kernel is 4.2.0.1, but the system just stays in a freeze.
|
I booted Debian the next day and waited for a few seconds (20 or 30) and it miraculously booted to GNOME login screen. I tried logging in , but it freezes after receiving the correct password. I did a hard-reboot and went into tty1 and logged into root where I did a dist-upgrade and installed bumblebee with the proprietary Linux driver, removing nouveau. I rebooted and the freeze no longer occurs. Therefore, I can consider this problem solved.
| Can't boot Debian testing after upgrade |
1,470,719,584,000 |
Currently, I'm using Pop!_OS 21.04 x86_64
with kernel 5.15.5-76051505-generic
but I've reproduced this issue on Manjaro, Tails, Ubuntu, MX. So the distro doesn't matter.
When I boot a Linux, I cannot connect to Wi-Fi network.
I found a solution for that some time ago and it was connected with Windows (dual-boot).
I had to turn off Wi-Fi on Windows before shutting it down, only then Wi-Fi worked on Linux.
But right now I have only Linux (no dual-boot) on my machine.
Everything was working well until I used Hiren's BootCD PE which is live-usb Windows with some utility tools.
After I booted that utility (from a USB drive) and connected to Wi-Fi on it, Wi-Fi stopped working on Linux.
It looks like the same issue I had before, but this time I cannot successfully disable Wi-Fi on Hiren's Boot Windows. I've tried disabling the Wi-Fi card in the device manager, uninstalling it completely, uncheck allowing to turn off card due to power management, everything with no success.
My guess is that Windows blocks the Wi-Fi card somehow and it cannot be properly initialized by Linux after that.
My proven solution before (when I had Windows and Linux dual-boot) was to boot Windows, turn off Wi-Fi on it, then boot Linux.
But right now I don't have Windows installed, only that live-usb utility with Windows. It uses some non standard PE Network Manager to manage Wi-Fi and turning it off there doesn't help like it used to on standard Windows Wi-Fi interface.
Do you have any ideas on how to "wake up" the wireless card on Linux?
The wireless card is clearly detected but just doesn't work.
I really don't want to install Windows only to turn off Wi-Fi on it and then shred it.
Logs from current Linux state:
$ iwconfig
lo no wireless extensions.
enp0s31f6 no wireless extensions.
$ rfkill
ID TYPE DEVICE SOFT HARD
1 wlan dell-wifi unblocked unblocked
2 bluetooth dell-bluetooth blocked unblocked
$ sudo lshw -C network
*-network
description: Network controller
product: Wireless 8265 / 8275
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
version: 78
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=iwlwifi latency=0
resources: irq:135 memory:ef100000-ef101fff
*-network
description: Ethernet interface
product: Ethernet Connection (4) I219-LM
vendor: Intel Corporation
physical id: 1f.6
bus info: pci@0000:00:1f.6
logical name: enp0s31f6
version: 21
serial: 10:65:30:2e:ee:de
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=5.15.5-76051505-generic firmware=0.1-4 latency=0 link=no multicast=yes port=twisted pair
resources: irq:131 memory:ef300000-ef31ffff
$ sudo dmesg | grep iwlwifi
Dec 15 11:06:54 ncno2 kernel: iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
Dec 15 11:06:54 ncno2 kernel: iwlwifi 0000:02:00.0: loaded firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm
Dec 15 11:06:54 ncno2 kernel: iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
Dec 15 11:06:56 ncno2 kernel: iwlwifi 0000:02:00.0: Couldn't prepare the card
Dec 15 11:06:56 ncno2 kernel: iwlwifi 0000:02:00.0: Error while preparing HW: -110
Dec 15 11:06:57 ncno2 kernel: iwlwifi 0000:02:00.0: Master Disable Timed Out, 100 usec
|
I haven't found a working solution other than turning off wifi on Windows. So I created a portable version of Windows on a USB drive, booted it on the Linux machine, turned off wifi on Windows, then booted again Linux and everything went back to normal. Wifi works without any issues.
To get a portable version of Windows I simply installed Windows on VirtualBox on virtual disk .vdi, then I created .img file from that virtual disk and cloned it to USB drive.
Creating portable Windows using VirtualBox
Worth mentioning is that I shut down the virtual machine at the Windows installation step on region select (it asks "Let's start with the region. Is this right?"). Maybe it's not a big deal and you can finish installation in VirtualBox but I decided to finish it after booting Windows from a USB drive.
I took the following steps:
Install Windows on VirtualBox
Create a disk image file from the virtual disk
$ VBoxManage clonehd /path/to/existing/Windows10.vdi /path/to/new/disk/image/Windows10.img --format RAW
Check the device name of a plugged USB drive
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 119.5G 0 disk
├─sda1 8:1 1 50M 0 part
├─sda2 8:2 1 29.5G 0 part
└─sda3 8:3 1 508M 0 part
nvme0n1 259:0 0 476.9G 0 disk
├─nvme0n1p1 259:1 0 498M 0 part /boot/efi
├─nvme0n1p2 259:2 0 4G 0 part /recovery
├─nvme0n1p3 259:3 0 468.4G 0 part
│ └─cryptdata 253:0 0 468.4G 0 crypt
│ └─data-root 253:1 0 468.4G 0 lvm /
└─nvme0n1p4 259:4 0 4G 0 part
└─cryptswap 253:2 0 4G 0 crypt [SWAP]
In my case, the USB drive had sda name (with partitions sda1, sda2, sda3)
Clone Windows disk image to a USB drive:
WARNING: Use with caution.
Check twice of= path because you're going to erase the disk from that path.
$ sudo dd if=/path/to/Windows10.img of=/dev/sda bs=4M status=progress
Restart the computer and boot Windows from a USB drive
What if creating portable Windows using VirtualBox doesn't work for you?
There's also a second option but you need a machine with installed Windows.
Use Rufus or WinToUSB on installed Windows and create "Windows To Go" - a portable version of Windows installed on a USB drive.
| No wifi, iwlwifi error -110 "Couldn't prepare the card", Windows blocks wifi card? |
1,470,719,584,000 |
I recently installed Kali Linux on my PC, making it dual booting with Windows 10. I have a 500GB m.2 Samsung 980 Pro SSD where I've installed Windows 10 and I have another 500GB Samsung EVO 860 SSD where I've installed Kali Linux. I've installed Grub so when I turn on my computer, I have the option to pick Windows 10 or Kali.
If I pick Kali, I'm getting the following error before the login screen:
I'm able to login to Kali, however, if the above error shows, Kali is not able to detect my wifi adapter (Intel Wi-Fi 6 AX200).
HOWEVER, If I first boot into Windows 10, restart the PC, then boot into Kali, I get the following different set of errors, and wifi connects automatically and everything works.
I've tried this many times and the pattern is: if I want wifi to work in Kali, I'll need to boot into windows first then kali. Otherwise, if I boot straight into Kali, wifi adapter will not be found and wifi will not work.
How do I fix this wifi issue?
Hardware specs:
Gigabyte B550I Aorus Pro AX
AMD Ryzen 5 5600x
Samsung 980 Pro 500GB NVMe (Windows 10 installed)
Samsung 860 EVO 500GB SSD (Kali Linux installed)
Nvidia RTX3080 FE
Crucial Ballistix 32 GB (2 x 16 GB) DDR4-3200
Thanks
|
Try to disable Windows Fast Boot and see if it works.
If you have a dual-boot machine with a recent version of Windows and
start seeing problems during initialization of the WiFi device when
booting Linux, the problem could be due to the “fast startup” feature
on Windows.
From here.
| Dual boot wifi adaptor not detected (Windows 10 & Kali Linux) |
1,470,719,584,000 |
I recently updated my Debian 8 OS. Ever since, I've been unable to connect to wifi. LAN works just OK. See below a sample of my command output:
frank@debian8:~$ sudo iwlist wlan0 scan
wlan0 Interface doesn't support scanning.
frank@debian8:~$ sudo iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
frank@debian8:~$ sudo ifconfig -a
eth0 Link encap:Ethernet HWaddr 34:e6:d7:1e:50:21
inet addr:10.68.77.173 Bcast:10.68.77.255 Mask:255.255.255.128
inet6 addr: fe80::36e6:d7ff:fe1e:5021/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9246 errors:0 dropped:0 overruns:0 frame:0
TX packets:9323 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7078862 (6.7 MiB) TX bytes:2001113 (1.9 MiB)
Interrupt:20 Memory:f7400000-f7420000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:925 errors:0 dropped:0 overruns:0 frame:0
TX packets:925 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:104194 (101.7 KiB) TX bytes:104194 (101.7 KiB)
frank@debian8:~$ lspci -vnn | grep -i net
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I218-LM [8086:155a] (rev 04)
02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73)
frank@debian8:~$ sudo dmesg|grep 'firmw\|wl'
[ 4.588961] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-7260-17.ucode (-2)
[ 4.589058] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2
frank@debian8:~$ sudo rfkill unblock all ; sudo ip link set wlan0 up
Cannot find device "wlan0"
frank@debian8:~$ lspci -knn | grep Net -A2
02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4470]
03:00.0 3D controller [0302]: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1)
frank@debian8:~$ sudo rfkill list
1: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
I am using a DELL Latitude E5440.
UPDATE:
More command output:
frank@debian8:~$ lsmod | grep dell
dell_laptop 20480 0
dell_smbios 16384 1 dell_laptop
dcdbas 16384 1 dell_smbios
dell_smm_hwmon 16384 0
video 40960 3 dell_laptop,nouveau,i915
dell_smo8800 16384 0
dell_rbtn 16384 1
rfkill 24576 5 bluetooth,dell_laptop,dell_rbtn,cfg80211
|
According to Intel , the Intel® Dual Band Wireless-AC 7260 should work on kernel version 4.1 and higher.
Add backports to your /etc/apt/sources.list:
deb http://deb.debian.org/debian jessie-backports main contrib non-free
save and install a new kernel from backports:
sudo apt-get update
sudo apt-get install linux-image-4.9.0-0.bpo.3-amd64
sudo reboot
sudo modprobe -r iwlwifi
sudo modprobe iwlwifi
The missing dependencies should be installed through apt-get install -t jessie-backports package-name.
| Debian 8 (Jessie): Unable to connect to WIFI after update |
1,470,719,584,000 |
I just installed Debian Jessie yesterday, was having issues with my multi-monitor setup and so upgraded the 3.x kernel to linux-generic-4.6. Now, for whatever reason, my iwlwifi driver has stopped working. Luckily I have a USB network card so I am not internet-less, but I can't seem to get the built in card working which is pretty frustrating.
This is the output of ip a:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether fc:3f:db:8a:88:a6 brd ff:ff:ff:ff:ff:ff
and lspci -nn | grep Wireless:
03:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 48)
I have uninstalled and reinstalled iwlwifi multiple times from the normal debian repo's as well as from backports.
Let me know if there is anything else you need.
|
Install the latest driver from here
wget https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-7265-ucode-16.242414.0.tgz
tar xvf iwlwifi-7265-ucode-16.242414.0.tgz
cd iwlwifi-7265-ucode-16.242414.0
cp iwlwifi-*.ucode /lib/firmware
Reboot
Unload and load driver:
rmmod iwlwifi
modprobe iwlwifi
Or you can use backports:
wget https://www.kernel.org/pub/linux/kernel/projects/backports/stable/v4.4.2/backports-4.4.2-1.tar.gz
tar xvf backports-4.4.2-1.tar.gz
cd backports-4.4.2-1
make defconfig-iwlwifi
make
sudo make install
Reboot and reload the driver.
| firmware-iwlwifi not working on linux kernel 4.6 - debian jessie |
1,470,719,584,000 |
I'm using Intel (R) Dual Band Wireless-AC 8260 on my laptop and installed Kali Linux 2020.2 on virtual box. My problem is when I run sudo airmon-ng it doesn't get detected, I get no output under PHY, Interface, Driver or Chipset. But on Ubuntu 20.04 installed on my HDD when I run the same command I get PHY(phy0), Interface(wlp2s0), Driver(iwlwifi), Chipset(Intel Corporation Wireless 8260 (rev 3a)). How can I get Kali Linux on virtual box to detect my Wi-Fi card? I already installed the firmware through sudo apt-get install firmware-iwlwifi and it's in the newest version.
|
Your host OS is controlling the WiFi adapter.
Since VirtualBox (nor any other virtualization software) has not implemented a virtual WiFi adapter, and your physical WiFi adapter is on a PCIe bus, the only way to get the Kali VM to control it would be to use PCI passthrough, which is complicated. And I think the PCI passthrough feature was removed from the newest major release of VirtualBox because it did not work well enough.
You might want to buy a USB-connected Wi-Fi adapter that is known to support "monitor mode" in Linux. Then you can tell VirtualBox to hand over full control of that adapter to the VM. Only then you will be able to use the full functionality of airmon-ng or other WiFi monitoring/penetration tools from within a VM.
| Wifi card not getting detected |
1,470,719,584,000 |
I am trying to figure out why the WiFi on my Intel NUC with CentOS 7 continues to die. As info, I have 5 node Hadoop cluster and they are all configured the same (as far as I can tell), however, the other machines which are on WiFi do not crash. I don't know what is wrong with this particular machine.
Here is the error from /var/log/messages. It is the same message that I see regularly as I've been watching this problem for days.
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: Microcode SW error detected. Restarting 0x2000000.
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: Start IWL Error Log Dump:
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: Status: 0x00000100, count: 6
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: Loaded firmware version: 34.0.1
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x000022CE | ADVANCED_SYSASSERT
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x05900280 | trm_hw_status0
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | trm_hw_status1
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00023FDC | branchlink2
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0003915A | interruptlink1
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | interruptlink2
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0000012C | data1
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x03830000 | data2
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xDEADBEEF | data3
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xD28011F1 | beacon time
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x72F4FDDD | tsf low
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000182 | tsf hi
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | time gp1
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xCA511FA7 | time gp2
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000001 | uCode revision type
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000022 | uCode version major
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | uCode version minor
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000230 | hw version
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00C89000 | board version
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0A96001C | hcmd
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xA7F93882 | isr0
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00050000 | isr1
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0020180A | isr2
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x40417DCD | isr3
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | isr4
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0A95001C | last cmd Id
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | wait_event
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00004288 | l2p_control
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00018024 | l2p_duration
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | l2p_mhvalid
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x000000EF | l2p_addr_match
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0000000D | lmpm_pmg_sel
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x30101345 | timestamp
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00007888 | flow_handler
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: Start IWL Error Log Dump:
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: Status: 0x00000100, count: 7
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000070 | ADVANCED_SYSASSERT
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | umac branchlink1
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC0086964 | umac branchlink2
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC0083A94 | umac interruptlink1
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC0083A94 | umac interruptlink2
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000800 | umac data1
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC0083A94 | umac data2
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xDEADBEEF | umac data3
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000022 | umac major
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | umac minor
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC088628C | frame pointer
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC088628C | stack pointer
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00DF019C | last host cmd
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | isr status reg
Jan 2 08:41:06 mapr04 kernel: ieee80211 phy0: Hardware restart was requested
Jan 2 08:41:06 mapr04 kernel: iwlwifi 0000:3a:00.0: FW error in SYNC CMD STATISTICS_CMD
Jan 2 08:41:06 mapr04 kernel: CPU: 0 PID: 4898 Comm: NetworkManager Kdump: loaded Not tainted 3.10.0-957.1.3.el7.x86_64 #1
Jan 2 08:41:06 mapr04 kernel: Hardware name: Intel Corporation NUC7i7BNH/NUC7i7BNB, BIOS BNKBL357.86A.0049.2017.0724.1541 07/24/2017
Jan 2 08:41:06 mapr04 kernel: Call Trace:
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaeb61e41>] dump_stack+0x19/0x1b
Jan 2 08:41:06 mapr04 kernel: [<ffffffffc0afa983>] iwl_trans_pcie_send_hcmd+0x563/0x580 [iwlwifi]
Jan 2 08:41:06 mapr04 kernel: [<ffffffffae4c2d00>] ? wake_up_atomic_t+0x30/0x30
Jan 2 08:41:06 mapr04 kernel: [<ffffffffc0b060fc>] iwl_trans_send_cmd+0x5c/0xe0 [iwlwifi]
Jan 2 08:41:06 mapr04 kernel: [<ffffffffc0c6d312>] iwl_mvm_send_cmd+0x32/0xb0 [iwlmvm]
Jan 2 08:41:06 mapr04 kernel: [<ffffffffc0c6e632>] iwl_mvm_request_statistics+0x72/0x100 [iwlmvm]
Jan 2 08:41:06 mapr04 kernel: [<ffffffffc0c616fe>] iwl_mvm_mac_sta_statistics+0xbe/0x100 [iwlmvm]
Jan 2 08:41:06 mapr04 kernel: [<ffffffffc0bb68f7>] sta_set_sinfo+0xb7/0x800 [mac80211]
Jan 2 08:41:06 mapr04 kernel: [<ffffffffc0bcd052>] ieee80211_get_station+0x52/0x80 [mac80211]
Jan 2 08:41:06 mapr04 kernel: [<ffffffffc08cae41>] nl80211_get_station+0xa1/0x240 [cfg80211]
Jan 2 08:41:06 mapr04 kernel: [<ffffffffae794d0d>] ? list_del+0xd/0x30
Jan 2 08:41:06 mapr04 kernel: [<ffffffffae5bdf1a>] ? __rmqueue+0x8a/0x460
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea77918>] genl_family_rcv_msg+0x208/0x430
Jan 2 08:41:06 mapr04 kernel: [<ffffffffae5bf134>] ? free_one_page+0x2e4/0x310
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea77b9b>] genl_rcv_msg+0x5b/0xc0
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea73ec0>] ? __netlink_lookup+0xc0/0x110
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea77b40>] ? genl_family_rcv_msg+0x430/0x430
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea75bab>] netlink_rcv_skb+0xab/0xc0
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea760e8>] genl_rcv+0x28/0x40
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea75530>] netlink_unicast+0x170/0x210
Jan 2 08:41:06 mapr04 kernel: [<ffffffffae78c042>] ? memcpy_fromiovec+0x62/0xb0
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea758d8>] netlink_sendmsg+0x308/0x420
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea73112>] ? netlink_recvmsg+0x212/0x490
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea193a6>] sock_sendmsg+0xb6/0xf0
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea194f5>] ? sock_recvmsg+0xc5/0x100
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea1a269>] ___sys_sendmsg+0x3e9/0x400
Jan 2 08:41:06 mapr04 kernel: [<ffffffffae656fe0>] ? __pollwait+0xf0/0xf0
Jan 2 08:41:06 mapr04 kernel: [<ffffffffae68ee1e>] ? ep_poll+0x31e/0x360
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea1b921>] __sys_sendmsg+0x51/0x90
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaea1b972>] SyS_sendmsg+0x12/0x20
Jan 2 08:41:06 mapr04 kernel: [<ffffffffaeb74ddb>] system_call_fastpath+0x22/0x27
Where should I start trying to debug? I can edit the original post with updates.
Here are some things which I think might be helpful:
uname -a:
Linux mapr04.wired.carnoustie 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
dmesg | grep iwlwifi:
[ 3.822041] iwlwifi 0000:3a:00.0: irq 132 for MSI/MSI-X
[ 3.831295] iwlwifi 0000:3a:00.0: loaded firmware version 34.0.1 op_mode iwlmvm
[ 3.924043] iwlwifi 0000:3a:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[ 3.984049] iwlwifi 0000:3a:00.0: base HW address: f8:94:c2:5c:07:24
Here is the latest error:
Here is the latest error:
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: Error sending STATISTICS_CMD: time out after 2000ms.
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: Current CMD queue read_ptr 246 write_ptr 247
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: Start IWL Error Log Dump:
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: Status: 0x00000100, count: 6
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: Loaded firmware version: 34.0.1
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000280 | trm_hw_status0
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | trm_hw_status1
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00023FDC | branchlink2
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0003915A | interruptlink1
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0003915A | interruptlink2
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | data1
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000080 | data2
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x03830000 | data3
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xD4C029D9 | beacon time
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x456535F1 | tsf low
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x000001BA | tsf hi
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | time gp1
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x6D3BFE27 | time gp2
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000001 | uCode revision type
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000022 | uCode version major
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | uCode version minor
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000230 | hw version
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00C89000 | board version
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0000001C | hcmd
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00012000 | isr0
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | isr1
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0000180A | isr2
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00417CC0 | isr3
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | isr4
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0A89001C | last cmd Id
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | wait_event
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00004288 | l2p_control
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00018024 | l2p_duration
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | l2p_mhvalid
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x000000EF | l2p_addr_match
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x0000000D | lmpm_pmg_sel
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x30101345 | timestamp
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00002838 | flow_handler
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: Start IWL Error Log Dump:
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: Status: 0x00000100, count: 7
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000070 | ADVANCED_SYSASSERT
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | umac branchlink1
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC0086964 | umac branchlink2
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC0083A94 | umac interruptlink1
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC0083A94 | umac interruptlink2
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000800 | umac data1
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC0083A94 | umac data2
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xDEADBEEF | umac data3
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000022 | umac major
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | umac minor
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC088628C | frame pointer
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0xC088628C | stack pointer
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00F6019C | last host cmd
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: 0x00000000 | isr status reg
Jan 5 03:17:01 mapr04 kernel: ieee80211 phy0: Hardware restart was requested
Jan 5 03:17:01 mapr04 kernel: iwlwifi 0000:3a:00.0: Microcode SW error detected. Restarting 0x2000000.
|
It seems the wifi drivers cannot manage the wifi hardware in your NUCs.
Several linux distros can be tried live without installing. I think NUCs have Intel wifi, which should work with built-in linux drivers, but they must be new enough.
I have a NUC with Intel 6th generation hardware. I have noticed that older versions of operating systems cannot manage the wifi hardware, but newer versions manage it without any tweaks, 'out of the box'.
Edit 1: I tested with live systems: Ubuntu 18.04.1 LTS can manage both the wired and wireless hardware of my NUC6i3SYH. Debian 9, Stretch, can manage the wired network automatically. I failed with the wifi, but other people might fix it (I don't know if there is a driver problem or if I cannot manage the user interface for wifi in Debian.)
Edit 2: I downloaded CentOS-7-x86_64-LiveGNOME-1810.iso ran it live and it can manage both the wired and wireless hardware of my NUC6i3SYH. It was started as easily as with Ubuntu 18.04.1 LTS. But I have not tested the stability during a long time.
Edit 3: You should consider that the hardware might be damaged (for example failing when getting hot). But if it works well with another operating system, you can conclude that the hardware is good.
When was your NUC hardware developed, and when was the CentOS 7 software developed?
Centos 7 has an old kernel series, 3.10; the kernel version in the live system '1810' is 3.10.0-957.el7.x86_64 #1 SMP. Ubuntu 18.04.1 live has kernel version 4.15.0-29 and an up to date installed system has 4.15.0-43.
Please try with another operating system with a newer linux kernel with newer hardware drivers.
| NUC with Centos 7 crashing: Microcode SW Error Detected |
1,470,719,584,000 |
Unfortunately I keep running into this issue when trying to install Debian. It occurs after I install the nvidia graphics drivers as per this guide https://wiki.debian.org/NvidiaGraphicsDrivers. I am following the Version 390.48 (via stretch-backports) guide and then the configuration steps via nvidia-xconfig.
How can I troubleshoot this and get it working?
|
I have now managed to fix the issue. On a fresh install of Debian, these were the steps that allowed me to install the Nvidia drivers:
Enter ttyl mode by pressing CTRL + ALT + F4 or CTRL + ALT + F1
Stop the X server with the command sudo /etc/init.d/gdm3 stop. In my case this was gdm3. You may need to type CTRL + ALT + F4/F1 again to get back into ttyl.
Run the cuda installation runfile: sudo sh ~/Downloads/cuda_<version>_linux.run
Add the suggested variables to .bashrc:
export PATH=/usr/local/cuda-<version>/bin${PATH:+:${PATH}}
export LD_LIBRARY_PATH=/usr/local/cuda-<version>/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
export CUDA_VISIBLE_DEVICES=0
| Boot fails after installing nvidia graphics drivers |
1,470,719,584,000 |
I'm running the following command:
sudo iwconfig wlan1 essid "wifi network"
I keep getting back:
SET failed on device wlan1 ; Operation not permitted.
On other computers there is no problem.
I'm wondering if I need to change the mode first? How can I go about debugging this issue?
|
I seemed to be able to fix the problem by putting the interface in ad-hoc mode:
sudo ifconfig wlan1 down
sudo iwconfig wlan1 mode ad-hoc
sudo ifconfig wlan1 up
sudo iwconfig wlan1 essid "wifi network"
Update: I tried the same process with auto, and managed which also worked. The mode master did not work.
| iwconfig operation not permitted? |
1,470,719,584,000 |
I have serious WiFi stability issues on Debian 8 [1] with Intel 7265 WiFi chipset [2]. I randomly loose the internet connection, albeit seemingly retaining the WiFi connection intact. Ad hoc I could regain connection by turning off/on the Wifi, or rebooting the system. Last months things got worse -- lost connection more frequently, <5min --, so I decided to reinstall the OS. Without success :-(
I researched and tried but got no results. I found out that the chipset lost support for the newest firmware versions. I've discovered some commands to readout the/some errors [3]. And a possible solution -- which is to cryptic for me to adapt --, to a seemingly very similar problem linked here. As well as the there required output [4].
Since I'm using the non-free drivers, I thought, maybe I should try the free ones instead. Maybe things get better. However I'm afraid I'm to unexperienced to remove the now active faulty drivers, install the open ones, and reconfigure the kernel. But, with some assistance, I would definitively give it a try. Thank you :)
[1] Linux version
$ uname -a
Linux XXXXXX 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
[2] Chipset
$ lspci | grep Wireless
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 3b)
[3] Error output
$ dmesg | grep iwlwifi
[ 38.436666] iwlwifi 0000:02:00.0: irq 65 for MSI/MSI-X
[ 38.450545] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-7265-9.ucode
[ 38.450870] iwlwifi 0000:02:00.0: loaded firmware version 23.214.9.0 op_mode iwlmvm
[ 38.486339] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x184
[ 38.486636] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[ 38.486798] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[ 40.220157] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[ 40.220323] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[ 275.958950] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 0
[ 275.958958] iwlwifi 0000:02:00.0: Current SW read_ptr 14 write_ptr 15
[ 275.958995] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[ 275.959007] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x80102052
[ 275.959019] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[ 275.959032] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x8030000e
[ 275.959044] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[ 275.959056] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[ 275.959069] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[ 275.959082] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x00709082
[ 275.959133] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [14,15]
[ 275.959183] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [0,0]
[ 275.959233] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [83,83]
[ 275.959284] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959335] iwlwifi 0000:02:00.0: Q 4 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959385] iwlwifi 0000:02:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959435] iwlwifi 0000:02:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959485] iwlwifi 0000:02:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959536] iwlwifi 0000:02:00.0: Q 8 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959587] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid 0x0000 [131,131]
[ 275.959637] iwlwifi 0000:02:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959687] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959738] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959788] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959838] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959888] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959938] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.959988] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.960038] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 275.960090] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 276.212876] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
[ 6230.465289] iwlwifi 0000:02:00.0: RF_KILL bit toggled to enable radio.
[ 6230.466255] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[ 6230.466413] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[4] Required output for possible solution
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 30:65:ec:4b:84:e4 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 60:57:18:17:7d:4d brd ff:ff:ff:ff:ff:ff
inet 192.168.178.24/24 brd 192.168.178.255 scope global dynamic wlan0
valid_lft 860308sec preferred_lft 860308sec
inet6 fe80::6257:18ff:fe17:7d4d/64 scope link
valid_lft forever preferred_lft forever
|
As workaround I've set the router 5G network with a distinctive name and created a wifi profile on the machine for it. The disconnections stopped!
It seems that the problem is rooted in the SSID management for multiple wifi-stardads by the linux-driver.
| Wifi Intel 7265 error & disconnecting -- iwlwifi fail to flush all tx fifo queues -- Debian 8 Jessie |
1,470,719,584,000 |
We upgraded several computers from Linux Mint 17.3 to version 18 and later recently to 18.1. I say this, as the particular computer did not have this kind of problem before this release upgrade.
That was a big step for sure, as the Ubuntu base changed from 14.04 to 16.04.
Everything works under normal conditions, but we have one computer, that the user suspends to memory several times a day.
The problem is that sometimes, approximately 1 from 100 times, the WiFi does not work.
More precisely, when we wake that computer up from sleep, the WiFi seems to be on, but does not show up any wireless connections, the user can switch the WiFi off and on, in the panel, but that does not help.
When I, the troubleshooter, am at the computer and try like 10 times to suspend and wake it up, then it of course works.
Hardware:
laptop Lenovo IdeaPad Z50
card Wireless 3160
Kernel and driver:
4.4.0-59-generic
iwlwifi
OS and DE:
Linux Mint 18.1 64-bit
Cinnamon
I am trying to read logs and find some clues as to what causes this and how to fix it, but to me it's like finding a needle in a haystack.
So I have defined the following alias for the user to try it out when this happens, which may be during the week or today, so I will report, if this helps or not:
alias wifi='sudo systemctl restart network-manager.service'
|
We believe that in this case this issue was caused by kernel.
The reason being that since we upgraded it to 4.8, it does not happen.
Case solved for me.
| WiFi sometimes does not work after wake up from suspend |
1,470,719,584,000 |
Freshly installed Debian 8 on a Dell XPS - Developer Edition laptop, and running the 3.16.0-4 kernel since the newer one doesn't boot (dont care to fix that at the moment).
sudo lspci -nnk | grep -iA2 net lists the following:
3a:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
Subsystem: Intel Corporation Device [8086:0050]
3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:525a] (rev 01)
I downloaded the firmware (tried both iwlwifi-8000C-13.ucode and iwlwifi-8000C-17.ucode) and copied it to /lib/firmware, rebooted and nothing changed.
If I try to install using apt-get install firmware-iwlwifi, my USB-ethernet adapter stops working as well.
Edit: Also, my driver (8000-17.ucode) isn't even listed in the firmware-iwlwifi packed here:
https://packages.debian.org/search?keywords=firmware-iwlwifi
errors when trying make menuconfig
root@001:/linux-4.1.26#
HOSTCC scripts/kconfig/mconf.o
In file included from scripts/kconfig/mconf.c:23:0:
scripts/kconfig/lxdialog/dialog.h:38:20: fatal error: curses.h: No such file or directory
#include CURSES_LOC
^
compilation terminated.
scripts/Makefile.host:108: recipe for target 'scripts/kconfig/mconf.o' failed
make[1]: *** [scripts/kconfig/mconf.o] Error 1
Makefile:541: recipe for target 'menuconfig' failed
make: *** [menuconfig] Error 2
|
According to Linux* Support for Intel® Wi-Fi Adapters the Intel 8260 is only suppoted by the 4.1 Kernel version:
Download and build the 4.1.26 kernel.
Use the iwlwifi-8000-ucode-25.30.13.0.tgz driver
| Debian 8 no wlan0 on XPS-13 Intel 8260 (rev 3a) |
1,470,719,584,000 |
I'm not able to use wpa_supplicant to set the essid and other parameters on the wireless interface.
Using -Dwext throws ioctl[SIOCSIWENCODEEXT]
$ sudo wpa_supplicant -B -i wlan0 -Dwext -c universitywpa
Successfully initialized wpa_supplicant
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
and also fails to set the ESSID:
$ iwconfig wlan0
wlan0 IEEE 802.11abgn ESSID:off/any
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
If I use -Dnl80211, no IOCTL error is thrown:
$ sudo wpa_supplicant -B -i wlan0 -Dnl80211 -c universitywpa
Successfully initialized wpa_supplicant
But the ESSID is still off/any:
$ iwconfig wlan0
wlan0 IEEE 802.11abgn ESSID:off/any
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
I run the same command with -d (verbose) to see what might be going on:
$ sudo wpa_supplicant -B -i wlan0 -Dnl80211 -c universitywpa -d
wpa_supplicant v2.3
random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf 'universitywpa' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'universitywpa' -> '/home/my-user/repos/university_connect/universitywpa'
Reading configuration file '/home/my-user/repos/university_connect/universitywpa'
Priority group 0
id=0 ssid='UNIVERSITY-SECURE'
rfkill: initial event: idx=0 type=2 op=0 soft=0 hard=0
rfkill: initial event: idx=1 type=1 op=0 soft=0 hard=0
rfkill: initial event: idx=43 type=2 op=0 soft=0 hard=0
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Using driver-based off-channel TX
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 3 iftype 2 (STATION)
nl80211: Subscribe to mgmt frames with non-AP handle 0x7ff6aa428fc0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=040a
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 04 0a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=040b
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 04 0b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=040c
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 04 0c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=040d
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 04 0d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=090a
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 09 0a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=090b
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 09 0b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=090c
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 09 0c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=090d
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 09 0d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=0409506f9a09
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=6): 04 09 50 6f 9a 09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=7f506f9a09
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=5): 7f 50 6f 9a 09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=0801
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 08 01
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=06
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=1): 06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=0a07
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 0a 07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x7ff6aa428fc0 match=0a11
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 0a 11
nl80211: Failed to register Action frame processing - ignore for now
netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT)
nl80211: driver param='(null)'
Add interface wlan0 to a new radio phy0
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz 20 mBm
nl80211: 2457-2482 @ 40 MHz 20 mBm (no IR)
nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR)
nl80211: 5170-5250 @ 80 MHz 20 mBm (no IR)
nl80211: 5250-5330 @ 80 MHz 20 mBm (DFS) (no IR)
nl80211: 5490-5730 @ 160 MHz 20 mBm (DFS) (no IR)
nl80211: 5735-5835 @ 80 MHz 20 mBm (no IR)
nl80211: 57240-63720 @ 2160 MHz 0 mBm
nl80211: Added 802.11b mode based on 802.11g information
wlan0: Own MAC address: a0:88:b4:98:95:d4
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=4 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=5 set_tx=0 seq_len=0 key_len=0
wlan0: RSN: flushing PMKID list in the driver
nl80211: Flush PMKIDs
wlan0: Setting scan request: 0.100000 sec
TDLS: TDLS operation not supported by driver
TDLS: Driver uses internal link setup
wlan0: WPS: UUID based on MAC address: 886beebd-10cf-544f-bba7-5c23f8ceb3b3
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
nl80211: Skip set_supp_port(unauthorized) while not associated
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
wlan0: Added interface wlan0
wlan0: State: DISCONNECTED -> DISCONNECTED
nl80211: Set wlan0 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
Daemonize..
$
I notice these:
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Failed to register Action frame processing - ignore for now
But I'm not sure how to interpret this.
Why is the ESSID not being set?
If I run iwconfig manually, I can set the ESSID:
sudo iwconfig wlan0 essid UNIVERSITY-SECURE
$ iwconfig wlan0
wlan0 IEEE 802.11abgn ESSID:"UNIVERSITY-SECURE"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
$
But obviously there's more than the ESSID needed to get the connection to work.
contents of universitywpa:
network={
ssid="UNIVERSITY-SECURE"
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=PEAP
identity="my-user"
password="mypass"
ca_cert="university_comodo_cert.pem"
phase1="peapver=0"
phase2="MSCHAPV2"
}
I've used these settings to connect on other machines without problems. But I've always used -Dwext, never -Dnl80211.
lshw wireless interface:
*-network
description: Wireless interface
product: Centrino Advanced-N 6205 [Taylor Peak]
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: 34
serial:
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=3.16.0-4-amd64 firmware=18.168.6.1 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn
the driver is iwlwifi.
Is this a problem between iwlwifi and -Dnl80211? How do I further diagnose this issue?
|
I ended up removing the -B (run daemon in background)
sudo wpa_supplicant -i wlan0 -c wpaconfig -D nl80211,wext
and realize that my script wasn't waiting for the connection to complete:
wlan0: CTRL-EVENT-CONNECTED - Connection to 00:11:22:33:44:55 completed [id=0 id_str=]
and was aborting early due to not seeing the essid. There seems to be no option to programmatically ask wpa_supplicant to daemonize itself only upon CTRL-EVENT-CONNECTED, so I might have to use a expect script for this.
| wpa_supplicant unable to set essid and other parameters from config file |
1,470,719,584,000 |
I am deeply wondering about this top (man page) output in uptime 5 hours 30 minutes only:
top - 00:41:41 up 5:48, 1 user, load average: 0.36, 0.44, 0.63
Tasks: 281 total, 1 running, 280 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.2 us, 0.1 sy, 0.0 ni, 99.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 31827.3 total, 15894.9 free, 1933.8 used, 13998.6 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 29321.2 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4567 vlastim+ 20 0 5229056 292040 141472 S 0.5 0.9 9:40.38 cinnamon
278 root -51 0 0 0 0 S 0.2 0.0 7:29.32 irq/140-nvidia
746 root -51 0 0 0 0 S 0.0 0.0 5:52.90 irq/142-iwlwifi
1423 root 20 0 25.1g 181056 118612 S 0.3 0.6 5:48.33 Xorg
280 root 20 0 0 0 0 S 0.0 0.0 2:23.89 nv_queue
276 root 20 0 0 0 0 S 0.0 0.0 0:31.17 nvidia-modeset/
17208 root 20 0 0 0 0 I 0.0 0.0 0:15.22 kworker/2:1-events
391 root 20 0 0 0 0 S 0.1 0.0 0:10.72 jbd2/nvme0n1p2-
21613 vlastim+ 20 0 32.7g 418536 216740 S 0.1 1.3 0:09.15 brave
Laptop specs for question background
Using Linux Mint 21.1 Cinnamon with kernel 5.15.0-76-generic and Nvidia driver version 535.54.03.
I am playing one specific HTML5 game in Google Chrome (stable), I have some decent specs of my laptop, it's getting old though, I know:
CPU: Intel Core i7-7700HQ @ 2.80GHz base freq. / 3.80 GHz turbo freq.; (4 cores, 8 threads)
RAM: 32 GB DDR4 2400MHz, 2 sticks in dual-channel, disabled swap file
GPU: NVIDIA, GeForce GTX 1060, Max-Q Design, 6 GB GDDR5X VRAM
Display: Believe it or not, my laptop has a 15.6" UltraHD = 4K = 3840x2160 resolution, it was the cause for overheating of my laptop even if doing little tasks, so I have added a "normal" FullHD, and turned the built-in display off. No overheating now even when hours on the game.
The actual question
Sad to say that I do not understand how IRQ works / what they are for. So it is impossible for me to understand why my computer spends so much time dealing with it.
To clarify, from comment: Can they be avoided or limited to some extent? For example, I could switch to cable, which I do not have right now (standard Cat.6, I mean). Would that eliminate the hours of CPU time or would that cause just another IRQ to consume my CPU?
Clues
nvidia-smi
Mon Jul 17 01:41:49 2023
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.54.03 Driver Version: 535.54.03 CUDA Version: 12.2 |
|-----------------------------------------+----------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+======================+======================|
| 0 NVIDIA GeForce GTX 1060 ... Off | 00000000:01:00.0 On | N/A |
| N/A 48C P0 23W / 60W | 360MiB / 6144MiB | 0% Default |
| | | N/A |
+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=======================================================================================|
| 0 N/A N/A 1423 G /usr/lib/xorg/Xorg 132MiB |
| 0 N/A N/A 4567 G cinnamon 57MiB |
| 0 N/A N/A 21650 G ...ble-features=BlockInsecureDownloads 167MiB |
+---------------------------------------------------------------------------------------+
wavemon
┌─Interface───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│wlp60s0 (IEEE 802.11), phy 0, reg: n/a, SSID: =CENSORED │
├─Levels──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ │
│link quality: 73% (51/70) │
│======================================================================================================================================================== │
│ │
│ │
│signal level: -59 dBm (1.26 nW) │
│=============================================================================================== │
│ │
├─Statistics──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│RX: 9e+06 (3.26 GiB), drop: 10846 (0.1%) │
│TX: 2e+07 (1.74 GiB), retries: 9k (0.0%) │
├─Info────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│mode: Managed, connected to: =====CENSORED====, time: 6:51h, inactive: 6.0s │
│freq: 5745 MHz, ctr1: 5755 MHz, channel: 149 (width: 40 MHz) │
│rx rate: 360.0 Mbit/s VHT-MCS 8 40MHz short GI VHT-NSS 2, tx rate: 400.0 Mbit/s VHT-MCS 9 40MHz short GI VHT-NSS 2 │
│beacons: 238339, avg sig: -57 dBm, interval: 0.1s, DTIM: 2 │
│power mgt: off, tx-power: 22 dBm (158.49 mW) │
│retry: short limit 7, rts/cts: off, frag: off │
├─Network─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│wlp60s0 (UP RUNNING BROADCAST MULTICAST) │
│mac: =====CENSORED====, qlen: 1000 │
│ip: ==CENSORED==/24 │
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
|
I recently switched from WiFi to a cable connection (from my D-Link DGS-108 switch to my laptop), and soft-disabled WiFi with the help from rfkill.
Now I can verify, that iwlwifi driver eats zero CPU time:
$ ps aux | grep 'irq/142-iwlwifi'
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 588 0.0 0.0 0 0 ? S May02 0:00 [irq/142-iwlwifi]
I understand that I cannot disable Nvidia IRQ as explained in the other answer, but at least something.
| Wondering about my `top` output = IRQ (nvidia, iwlwifi) |
1,470,719,584,000 |
I just installed debian bullseye on a lenovo Thinkpad X1 Carbon Gen 10.
The installation process was pretty straightforward. Except for one part: networking. During the installation, it said the wifi card was not recognized.
Apparently this is a known case. I am just supposed to install the firmware-iwlwifi package and everything is supposed to be fine.
Thanks to an usb driver I uploaded this file ftp.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20210315-3_all.deb to the laptop and ran dpkg -i.
apt search iwl
firmware-iwlwifi/now 20210315-3 all [installed,local]
Binary firmware for Intel Wireless cards
However, lsmod | grep iwl initally doesn't show that the iwlwifi module, suggesting it's not loaded.
After modprobe iwlwifi, lsmod | grep iwl displays:
iwlwifi 299008 0
cfg80211 983040 1 iwlwifi
I interpret the third column being at 0 as "the driver is not being used".
Finally, lspci -nnkv | sed -n '/Network/,/^$/p' doesn't show the line Kernel driver in use: iwlwifi Kernel modules: iwlwifi like on this page https://wiki.debian.org/InstallingDebianOn/Thinkpad/X1%20Carbon%20Gen%2810%29/bullseye.
Even after rebooting, making sure the kernel module is loaded at boot time (adding iwlwifi in /etc/modules), I don't have a wifi network interface (ip a show).
At this point I'm lost. I feel something's wrong but can't identify what. The installation guide on the debian wiki I linked above proposes some commands to run but none of them seem to be about wifi.
Isn't the iwlwifi module supposed to load automatically after installing the firmware-iwlwifi package?
What am I missing to make the Intel network device use that module?
Note: I don't have access to internet via ethernet. I tried plugging an USB-C to ethernet adapter and an RJ45 cable but for some reason the ethernet interface doesn't go up either.
|
I solved my issue by sharing an internet connection with my phone via USB.
I installed the latest kernel and it seemed to have fixed the issue.
The best hypothesis I have is, as @Peregrino69 mentioned, that my driver version was not aligned with my kernel version.
| Intel wifi card not using iwlwifi module |
1,580,455,562,000 |
I installed Debian 9 on my acer aspire 7 (A715-72G-75XG) laptop. However the network-manager does not detect wi-fi. Those are the outputs of a few commands:
$iwlist wlan0 scan
wlan0 Interface doesn't support scanning.
lspci -knn | grep -i net
00:14.3 Network controller [0280]: Intel Corporation Device
[8086:a370] (rev 10)
06:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
[10ec:8168] (rev 12)
Subsystem: Acer Incorporated [ALI] RTL8111/8168/8411 PCI Express
Gigabit Ethernet Controller [1025:125e]
I have no idea what to do.
|
You need to install the linux-image and the firmware-iwlwifi (non-free) from backports.
add the following line to your /etc/apt/sources.list:
deb http://deb.debian.org/debian stretch-backports main contrib non-free
Then :
sudo apt update
sudo apt -t stretch-backports linux-image-4.19.0-0.bpo.5-amd64 firmware-iwlwifi
sudo reboot
Intel Dual Band Wireless-AC 9560
Intel® Wireless-AC 9560 : A kernel version 4.14+ is required.
PCI-IDS Device 8086:a370 : Name: Wireless-AC 9560 [Jefferson Peak]
| Debian 9 on acer aspire 7 doesn't detect wifi ( intel AC 9560 ) |
1,580,455,562,000 |
Recently I noticed my wireless card isn't "available" until 60s after boot.
When X is ready I run
%> ifconfig wlan0
wlan0: error fetching interface information: Device not found
Then about 20s later I can see this in dmesg, and wlan0 is ready afterwards.
[ 61.713944] iwlwifi 0000:03:00.0: loaded firmware version 17.168.5.3 build 42301 op_mode iwldvm
[ 61.713958] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 61.713959] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[ 61.713961] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[ 61.713962] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Advanced-N 6205 AGN, REV=0xB0
I'm not sure why but this is quite unusual, anyone know where I should be looking at?
I'm running Arch Linux, with customized 3.15.10 kernel.
|
I'm not quite sure about it.
Upgraded kernel to 3.17.6, no change to kernel configuration and it just worked.
I guess the NetworkManager or udev or whatever userspace tools that changed it behavior, which is incompatible with older kernels.
If someone has better answer I will have this removed
| Slow detection of wireless card |
1,580,455,562,000 |
I got this error and I couldn't find the mentionned files in the debian website . I tried to download the ISo again but the same problem remained .
Where can I find those files and should I put them on the kali usb stick or on another one ?
|
1) If you can connect TEMPORARILY by cable you don't need to pay any attention to this message.
You need to edit the sources list to make sure that the relevant lines include: contrib non-free
See https://docs.kali.org/general-use/kali-linux-sources-list-repositories
Then, having connected TEMPORARILY by cable, you: sudo apt install firmware-iwlwifi
2) If you CANNOT connect temporarily by cable then follow the instructions and put firmware-iwlwifi from another computer onto a usb stick during installation.
3) Reboot for it to take effect.
| iwlwifi error while installing kali linux [duplicate] |
1,580,455,562,000 |
My system is the latest Debian stretch (9.4) on a ThinkPad L380 which has a Intel® Dual Band Wireless-AC 8265 card. The special key for enabling/disabling wifi works but does not change the hard blocked condition.
rfkill list all yields the following
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
rfkill unblock all doesn't change anything.
dmesg:
[ 2.872137] Intel(R) Wireless WiFi driver for Linux
[ 2.872139] Copyright(c) 2003- 2015 Intel Corporation
[ 2.872486] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[ 2.876566] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8265-26.ucode (-2)
[ 2.876573] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-26.ucode failed with error -2
[ 2.876585] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8265-25.ucode (-2)
[ 2.876589] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-25.ucode failed with error -2
[ 2.876598] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8265-24.ucode (-2)
[ 2.876602] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-24.ucode failed with error -2
[ 2.876611] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8265-23.ucode (-2)
[ 2.876615] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-23.ucode failed with error -2
[ 2.878550] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 2.880064] i915 0000:00:02.0: firmware: direct-loading firmware i915/kbl_dmc_ver1_01.bin
[ 2.880899] [drm] Finished loading i915/kbl_dmc_ver1_01.bin (v1.1)
[ 2.881548] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-8265-22.ucode
[ 2.882171] iwlwifi 0000:02:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm
[ 2.896266] kvm: disabled by bios
[ 2.898967] [drm] GuC firmware load skipped
[ 2.899261] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[ 2.900584] intel_rapl: Found RAPL domain package
[ 2.900586] intel_rapl: Found RAPL domain core
[ 2.900588] intel_rapl: Found RAPL domain uncore
[ 2.900590] intel_rapl: Found RAPL domain dram
[ 2.903322] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 2.905080] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 2.910783] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 2.911257] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
[ 2.911369] [drm] Initialized i915 1.6.0 20160919 for 0000:00:02.0 on minor 0
[ 2.930964] ucsi_acpi: probe of USBC000:00 failed with error -110
[ 2.931015] input: PC Speaker as /devices/platform/pcspkr/input/input9
[ 2.946639] i2c_hid i2c-INT3515:02: unexpected HID descriptor bcdVersion (0x0000)
[ 2.969235] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 2.969634] thermal thermal_zone8: failed to read out thermal zone (-5)
[ 2.973763] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
[ 2.993050] clocksource: Switched to clocksource tsc
[ 3.097358] EXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Opts: (null)
[ 3.154598] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 3.154599] fbcon: inteldrmfb (fb0) is primary device
[ 3.179329] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 3.179331] snd_hda_codec_generic hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 3.179334] snd_hda_codec_generic hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 3.179335] snd_hda_codec_generic hdaudioC0D0: mono: mono_out=0x0
[ 3.179337] snd_hda_codec_generic hdaudioC0D0: inputs:
[ 3.179339] snd_hda_codec_generic hdaudioC0D0: Mic=0x19
[ 3.179341] snd_hda_codec_generic hdaudioC0D0: Internal Mic=0x12
[ 3.191106] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input10
[ 3.191189] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11
[ 3.191265] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
[ 3.191343] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13
[ 3.191430] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
[ 3.274143] random: crng init done
[ 3.373058] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.373058] Bluetooth: BNEP filters: protocol multicast
[ 3.373061] Bluetooth: BNEP socket layer initialized
[ 3.570603] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
[ 3.785160] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
[ 3.793653] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 4.418209] Bluetooth: hci0: Waiting for firmware download to complete
[ 4.418301] Bluetooth: hci0: Firmware loaded in 1686937 usecs
[ 4.418426] Bluetooth: hci0: Waiting for device to boot
[ 4.430367] Bluetooth: hci0: Device booted in 11735 usecs
[ 4.432598] bluetooth hci0: firmware: direct-loading firmware intel/ibt-12-16.ddc
[ 4.432604] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc
[ 4.434334] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 4.434512] Console: switching to colour frame buffer device 240x67
[ 4.457449] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 4.817747] [drm] RC6 on
[ 183.889440] Bluetooth: RFCOMM TTY layer initialized
[ 183.889445] Bluetooth: RFCOMM socket layer initialized
[ 183.889450] Bluetooth: RFCOMM ver 1.11
dmesg after suspend:
[ 365.379893] PM: Syncing filesystems ... done.
[ 365.382921] PM: Preparing system for sleep (mem)
[ 365.383087] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_01.bin
[ 365.383332] (NULL device *): firmware: direct-loading firmware intel/ibt-12-16.sfi
[ 365.383362] (NULL device *): firmware: direct-loading firmware intel/ibt-12-16.ddc
[ 365.383573] (NULL device *): firmware: direct-loading firmware iwlwifi-8265-22.ucode
[ 365.383620] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 365.384944] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 365.386059] PM: Suspending system (mem)
[ 365.386098] Suspending console(s) (use no_console_suspend to debug)
[ 365.518772] e1000e: EEE TX LPI TIMER: 00000011
[ 365.800524] PM: suspend of devices complete after 294.867 msecs
[ 365.828976] PM: late suspend of devices complete after 28.444 msecs
[ 365.837474] e1000e 0000:00:1f.6: System wakeup enabled by ACPI
[ 365.880923] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[ 365.916944] PM: noirq suspend of devices complete after 87.962 msecs
[ 365.917688] ACPI: Preparing to enter system sleep state S3
[ 366.020987] ACPI : EC: event blocked
[ 366.020988] ACPI : EC: EC stopped
[ 366.020989] PM: Saving platform NVS memory
[ 366.021000] Disabling non-boot CPUs ...
[ 366.022735] smpboot: CPU 1 is now offline
[ 366.039307] smpboot: CPU 2 is now offline
[ 366.063297] smpboot: CPU 3 is now offline
[ 366.087841] smpboot: CPU 4 is now offline
[ 366.110934] smpboot: CPU 5 is now offline
[ 366.134904] smpboot: CPU 6 is now offline
[ 366.158874] smpboot: CPU 7 is now offline
[ 366.180266] ACPI: Low-level resume complete
[ 366.180375] ACPI : EC: EC started
[ 366.180376] PM: Restoring platform NVS memory
[ 366.181093] Suspended for 14.006 seconds
[ 366.181149] Enabling non-boot CPUs ...
[ 366.192664] x86: Booting SMP configuration:
[ 366.192665] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 366.195048] cache: parent cpu1 should not be sleeping
[ 366.195208] CPU1 is up
[ 366.208592] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 366.211383] cache: parent cpu2 should not be sleeping
[ 366.211679] CPU2 is up
[ 366.224603] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 366.227400] cache: parent cpu3 should not be sleeping
[ 366.227700] CPU3 is up
[ 366.240619] smpboot: Booting Node 0 Processor 4 APIC 0x1
[ 366.243639] cache: parent cpu4 should not be sleeping
[ 366.243981] CPU4 is up
[ 366.256644] smpboot: Booting Node 0 Processor 5 APIC 0x3
[ 366.259517] cache: parent cpu5 should not be sleeping
[ 366.259858] CPU5 is up
[ 366.272656] smpboot: Booting Node 0 Processor 6 APIC 0x5
[ 366.275536] cache: parent cpu6 should not be sleeping
[ 366.275897] CPU6 is up
[ 366.288664] smpboot: Booting Node 0 Processor 7 APIC 0x7
[ 366.291540] cache: parent cpu7 should not be sleeping
[ 366.292063] CPU7 is up
[ 366.303628] ACPI: Waking up from system sleep state S3
[ 366.661536] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[ 366.661575] PM: noirq resume of devices complete after 65.045 msecs
[ 366.673068] PM: early resume of devices complete after 11.452 msecs
[ 366.673178] ACPI : EC: event unblocked
[ 366.673671] e1000e 0000:00:1f.6: System wakeup disabled by ACPI
[ 366.674032] ACPI : button: The lid device is not compliant to SW_LID.
[ 366.674067] rtc_cmos 00:03: System wakeup disabled by ACPI
[ 366.674076] iwlwifi 0000:02:00.0: RF_KILL bit toggled to enable radio.
[ 366.681335] [drm] GuC firmware load skipped
[ 366.739793] xhci_hcd 0000:00:14.0: port 6 resume PLC timeout
[ 366.977498] usb 1-5: reset high-speed USB device number 2 using xhci_hcd
[ 367.297291] usb 1-7: reset full-speed USB device number 3 using xhci_hcd
[ 367.439880] PM: resume of devices complete after 766.807 msecs
[ 367.440297] usb 1-7:1.0: rebind failed: -517
[ 367.440301] usb 1-7:1.1: rebind failed: -517
[ 367.440685] PM: Finishing wakeup.
[ 367.440687] Restarting tasks ... done.
[ 367.444167] thermal thermal_zone8: failed to read out thermal zone (-5)
[ 367.446979] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[ 367.447922] [drm] RC6 on
[ 367.447954] Bluetooth: hci0: Device revision is 16
[ 367.447955] Bluetooth: hci0: Secure boot is enabled
[ 367.447956] Bluetooth: hci0: OTP lock is enabled
[ 367.447957] Bluetooth: hci0: API lock is enabled
[ 367.447958] Bluetooth: hci0: Debug lock is disabled
[ 367.447959] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 367.447962] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[ 367.572753] e1000e: enp0s31f6 NIC Link is Down
[ 367.573316] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
[ 367.788561] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
[ 367.789646] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 367.792250] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 367.793168] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 367.910290] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 367.910749] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 367.972456] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 367.984050] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 367.985447] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 368.103032] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 368.103417] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 368.162578] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 368.240193] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 368.956315] Bluetooth: hci0: Waiting for firmware download to complete
[ 368.957013] Bluetooth: hci0: Firmware loaded in 1475934 usecs
[ 368.957104] Bluetooth: hci0: Waiting for device to boot
[ 368.968956] Bluetooth: hci0: Device booted in 11659 usecs
[ 368.968960] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc
[ 368.971033] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 371.590758] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 371.717298] wlp2s0: authenticate with 50:c7:bf:f0:1a:f9
[ 371.728900] wlp2s0: send auth to 50:c7:bf:f0:1a:f9 (try 1/3)
[ 371.733499] wlp2s0: authenticated
[ 371.736554] wlp2s0: associate with 50:c7:bf:f0:1a:f9 (try 1/3)
[ 371.740114] wlp2s0: RX AssocResp from 50:c7:bf:f0:1a:f9 (capab=0x411 status=0 aid=1)
[ 371.742706] wlp2s0: associated
[ 371.763991] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[ 421.946525] wlp2s0: deauthenticating from 50:c7:bf:f0:1a:f9 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 421.971128] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 422.801433] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 423.825836] wlp2s0: authenticate with 50:c7:bf:72:0d:72
[ 423.833627] wlp2s0: send auth to 50:c7:bf:72:0d:72 (try 1/3)
[ 423.841483] wlp2s0: authenticated
[ 423.844477] wlp2s0: associate with 50:c7:bf:72:0d:72 (try 1/3)
[ 423.847587] wlp2s0: RX AssocResp from 50:c7:bf:72:0d:72 (capab=0x431 status=0 aid=4)
[ 423.850208] wlp2s0: associated
[ 423.859782] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[ 615.260094] wlp2s0: disconnect from AP 50:c7:bf:72:0d:72 for new auth to 50:c7:bf:f0:1a:f9
[ 615.267474] wlp2s0: authenticate with 50:c7:bf:f0:1a:f9
[ 615.276197] wlp2s0: send auth to 50:c7:bf:f0:1a:f9 (try 1/3)
[ 615.276915] wlp2s0: authenticated
[ 615.283055] wlp2s0: associate with 50:c7:bf:f0:1a:f9 (try 1/3)
[ 615.284028] wlp2s0: RX AssocResp from 50:c7:bf:f0:1a:f9 (capab=0x411 status=0 aid=1)
[ 615.284930] wlp2s0: associated
[ 718.274056] wlp2s0: disconnect from AP 50:c7:bf:f0:1a:f9 for new auth to 50:c7:bf:72:0d:72
[ 718.285258] wlp2s0: authenticate with 50:c7:bf:72:0d:72
[ 718.294788] wlp2s0: send auth to 50:c7:bf:72:0d:72 (try 1/3)
[ 718.399207] wlp2s0: send auth to 50:c7:bf:72:0d:72 (try 2/3)
[ 718.411186] wlp2s0: authenticated
[ 718.415211] wlp2s0: associate with 50:c7:bf:72:0d:72 (try 1/3)
[ 718.498645] wlp2s0: RX AssocResp from 50:c7:bf:72:0d:72 (capab=0x431 status=0 aid=4)
[ 718.507714] wlp2s0: associated
Another thing I noticed is that the special keys for adjusting display brightness show the same behaviour.
|
Upgrading from debian stretch to the buster (testing) release fixed the issue for me.
Edit: If you don't want to upgrade to a testing distribution, there is also the option to install a newer kernel via stretch-backports instead. After updating my /etc/apt/sources.list accordingly, I installed the newest available kernel and wifi works upon boot now. It might also be necessary to install the backports version of iwlwifi.
In conclusion: the problem was due to an outdated kernel.
| Debian wifi hard blocked, working only after suspend |
1,580,455,562,000 |
I'm trying to set the blink mode for iwlwifi on Debian 8.
I have created iwlwifi.conf in /etc/modprobe.d and added options iwlwifi led_mode=1, but this is not affecting the activity light.
The firmware is installed as part of firmware-iwlwifi/oldstable.
Any advice is appreciated.
|
The device in this instance is an iwl4965.
The correct way to disable the LED on this device is options iwlegacy led_mode=1
Hopefully, this will be useful for anybody trying to disable this activity on Debian 8 Jessie.
| iwlwifi light blinking on Debian 8 |
1,580,455,562,000 |
I have a fresh install of Arch Linux on a Lenovo laptop. I installed NetworkManager, but when I run nmcli d I only see the loopback device. The same result is shown when running ip link.
Both the NetworkManager and wpa_supplicant services are started and running. Currently I am not able to use Wifi and NetworkManager does not show the device.
Running lpsci -k yields
Network controller: Intel Corporation Ice Lake-LP PCH CNVI WiFi (Rev 30)
Subsystem Intel Corporation Wi-fi 6
Kernel Modules iwlwifi
How do I get NetworkManager to recognize this device?
|
The solution was to install the package linux-firmware and reboot the laptop
Once that was done, I was able to see all available networks and utilize Wifi
| nmcli does not show any devices |
1,580,455,562,000 |
I recently switched from Windows to Void Linux, and ever since, my internet connection has been extremely unreliable.
Symptoms:
In a live environment / after a fresh install of Void Linux, browsing internet is smooth and internet speeds are around 100 Mbps download and upload.
After a few hours, browsing internet is inconsistent, and while download speed stays around 100 Mbps (slightly lower (?), and also inconsistent, between 50-300 Mbps), upload speeds take a big hit: between 0 and 50 Mbps (tested on speedtest.net and testmy.net).
This happens on all browsers I have tried (Firefox and Chromium).
This did not happen when my laptop had Windows.
This only happens on my Void Linux laptop, no other device on my home network has this issue.
This does not happen on my university's eduroam WiFi.
pinging and diging websites while they are taking forever to load get instant and correct replies; doing a CLI speed test indicates (mostly) normal download speeds (see above).
Wireshark shows a very large number of TCP retransmissions and dup ACK's with several seconds passing between each one, though I am not 100% sure what is a normal amount. (I am fairly certain this amount is not normal from what little I can gather though.)
Internet sometimes randomly drops.
All of these symptoms are extremely random and I seem to get new problems all the time.
Things I have tried:
Since internet starting dipping around the time I ran a system upgrade, I thought switching to an older kernel version might work, but it does not (tested on version 5.14, 5.15, and 5.16).
I have blacklisted my laptop vendor's acer_wmi driver, but it does not seem to affect anything.
I have tried setting my MTU to a wide range of values (1000 - 1492) to no avail.
I have tried using several public DNS servers (Cloudflare, Google, OpenDNS).
I have checked power management for my WiFi card, power management is turned off.
What I think:
I don't think it could be a hardware problem since my laptop connects to my university's wifi with no problems and other devices on my home network connect to the router and have good download and upload speeds.
I think this might be a driver problem, but I can't find any good resources to troubleshoot WiFi driver problems + this unreliable internet doesn't help when I need to troubleshoot something.
Info:
No errors in log files or dmesg.
Network card: Intel Corporation Wi-Fi 6 AX200
Firewall is turned off.
Though I am not the only one using my home network, it is definitely not congested (I am pretty much the only one generating traffic on it).
iwconfig output:
lo no wireless extensions.
wlp1s0 IEEE 802.11 ESSID:"energifyn-70209695"
Mode:Managed Frequency:5.24 GHz Access Point: 00:0F:94:C5:7E:D8
Bit Rate=40.5 Mb/s Tx-Power=22 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=43/70 Signal level=-67 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:12 Invalid misc:7 Missed beacon:0
ip address output:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 18:26:49:43:cd:99 brd ff:ff:ff:ff:ff:ff
inet 192.168.20.251/24 brd 192.168.20.255 scope global dynamic noprefixroute wlp1s0
valid_lft 85264sec preferred_lft 85264sec
inet6 fe80::3d37:94bc:a28a:60c5/64 scope link noprefixroute
valid_lft forever preferred_lft forever
ip route output:
default via 192.168.20.254 dev wlp1s0 proto dhcp src 192.168.20.252 metric 3002
192.168.20.0/24 dev wlp1s0 proto dhcp scope link src 192.168.20.252 metric 3002
ip -s -s link show dev wlp1s0 output:
2: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 18:26:49:43:cd:99 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
2497582 3439 0 0 0 0
RX errors: length crc frame fifo overrun
0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
615263 2579 0 0 0 0
TX errors: aborted fifo window heartbeat transns
0 0 0 0 2
resolv.conf contents:
# Generated by resolvconf
domain fibernetcpe
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.20.254
|
Some tips.
Not sure if the high number of TCP retransmissions is related to your wifi connection, but there is a possibility of interference if you say it works fine in a different environment. Check if you are connecting in 2.4 Ghz or 5 Ghz and which channel (frequency). You can perhaps configure your router to choose another channel or let it determine a less crowed, more optimal channel if it's sophisticated enough.
Your router might support both 2.4 Ghz and 5 Ghz, but it remains to be seen if your computer wifi is capable of operating on both frequency ranges. Regardless of the hardware capabilities, the OS and the driver have to support those capabilities.
A driver issue is also possible. Try to identify your hardware, in particular the chipset and check on https://wireless.wiki.kernel.org/ to see if it's supported and what the appropriate driver could be. Try lspci -v to get some information on your onboard devices. Verify your Linux kernel version using for example uname -a.
I also suggest running sudo dmesg -wT in a terminal window and watch out for suspicious messages. You can always update your question with additional information.
| Laptop internet connection unreliable after switching to Linux |
1,580,455,562,000 |
I use a custom built Linux distro. When I try to enable wifi I cannot view any existing networks. My wifi card is Intel Wifi link 5100 and the output of lspci -vv is
Subsystem: Intel Corporation WiFi Link 5100 AGN
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 35
Region 0: Memory at d6d00000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee02004 Data: 402b
Capabilities: [e0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
ip link shows
wlp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 52:ce:71:xx:xx:xx brd ff:ff:ff:ff:ff:ff permaddr 00:22:fb:xx:xx:xx
ifconfig:
wlp5s0 Link encap:Ethernet HWaddr 52:CE:71:XX:XX:XX
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 TX bytes:0
I don't understand where the issue is. Can you please help?
sudo iwlist:
wlp5s0 Scan completed :
Cell 01 - Address:
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=40/70 Signal level=-70 dBm
Encryption key:on
ESSID:"ACT102474534110"
Cell 02 - Address:
Channel:2
Frequency:2.417 GHz (Channel 2)
Quality=38/70 Signal level=-72 dBm
Encryption key:on
ESSID:"Abhijit"
Cell 03 - Address:
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=48/70 Signal level=-62 dBm
Encryption key:on
ESSID:"gagsbuds"
Cell 04 - Address:
Channel:5
Frequency:2.432 GHz (Channel 5)
Quality=34/70 Signal level=-76 dBm
Encryption key:on
ESSID:"sanjay"
Cell 05 - Address:
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=44/70 Signal level=-66 dBm
Encryption key:on
ESSID:"The Devs"
Cell 07 - Address:
Channel:8
Frequency:2.447 GHz (Channel 8)
Quality=35/70 Signal level=-75 dBm
Encryption key:on
ESSID:"Tnet"
Cell 08 - Address:
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=70/70 Signal level=-21 dBm
Encryption key:on
ESSID:"MaANAS"
Cell 09 - Address:
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=69/70 Signal level=-41 dBm
Encryption key:on
ESSID:"DIRECT-np-BRAVIA"
Cell 10 - Address:
Channel:13
Frequency:2.472 GHz (Channel 13)
Quality=24/70 Signal level=-86 dBm
Encryption key:on
ESSID:"PanduHome"
|
Based off your comments whatever utility you're using to connect to Wi-Fi is malfunctioning (e.g. due to missing dependencies) and your Wi-Fi adapter is working just fine.
For instance NetworkManager requires NetworkManager-wifi and wpa_supplicant.
| Why can't I view any available networks in linux |
1,580,455,562,000 |
I recently installed Debian onto my 3rd gen Thinkpad X1 Carbon and am having some issues with getting WiFi to work. I tried following quite a few different suggestions online and none seem to be helping me - here is some info about my machine and what I have done already. Bluetooth works perfectly.
Output of nmcli device:
DEVICE TYPE STATE CONNECTION
enp0s25 ethernet unavailable --
lo loopback unmanaged --
And the response of lspci doesn't have a wireless controller inside. Ethernet Controller is Intel Corporation Ethernet Connection (3) I218-LM (rev 3).
Output of sudo dmesg | grep iwl is nothing.
I can't run modinfo because it isn't installed.
My computer has an Intel 7265 Wireless card, and I've tried downloading both the drivers from here - List of firmware in Linux kernel and dropping them into /lib/firmware, which didn't work for me. Nothing appeared to change.
I tried following this guide - Re: wifi not working on my new lenovo thinkpad x-1 but it requires installing software onto my laptop without internet, which I can't easily do. Keryx doesn't appear to be working anymore, and I can't install software with its dependencies onto my X1 Carbon effectively over bluetooth.
Any advice or suggestions?
|
Download and install the firmware for your device's wireless adapter. If your device uses an Intel WLAN adapter, follow this guide.
If your device isn't connected to the internet, the iwlwifi firmware can be installed without an internet connection:
Download the iwlwifi firmware from here.
Move the .deb file to your device.
Install the file:
$ sudo dpkg -i /path/to/deb/file
$ sudo apt-get install -f
Restart your machine. Internet should now work!
| Wifi Adapter not Found on X1 Carbon 3rd Gen |
1,580,455,562,000 |
I have the latest Slackware with Linux kernel 4.4.14 installed. The system has been giving me issues with network since installation. I have Intel Wireless-AC 9560 Wi-Fi card, which works fine in Windows 10, (as expected), but isn't working heck, isn't even showing up in slackware when I type iwconfig or ifconfig. lspci recognises it though. I downloaded the drivers for it from the Intel official driver site. However, copying the ucode images to the /lib/firmware directory is somehow not working. What are my alternatives?
P.S. It should be noted that this doesn't help
|
the GUI is also broken... ok
Can you try and run startx command as root? to see if the GUI is working as root? if yes then go to your home account delete all .serverauthXXX and .Xauthority files as root.
Also did you install Slackware as a full install on the installation steps?
Can you please also give a try to install the exton kernel
https://news.softpedia.com/news/you-can-now-run-a-custom-linux-4-14-2-kernel-on-your-slackware-pc-here-s-how-518751.shtml
to see if the newest kernel will find your card
If I was you I will give one more try to reinstall slackware from the start and follow the first step the one I told you the chmod +x /etc/rc.d/rc.networkmanager for your wifi card (do a reboot after this command)
Then follow the instructions
https://docs.slackware.com/slackware:beginners_guide
1) to add user
2) to select mirror
3) update Slackware
I dont know what you did exactly I am just guessing. Slackware is my best operating system and you should give one more try and you will find your way. I was in your position too when I was trying to do my first Slackware installation. It was a nightmare :) for me too but I learned a lot of things using this particular operating system. Good luck my friend
| Installing WiFi driver for slackware Linux |
1,580,455,562,000 |
Network manager doesn't see wifi card. Card keep being disabled after restart. Something overwrites /etc/resolv.conf.
|
If you have problem using wifi it's probably lack of firmware or conflicts. connman conflicts with network manager. wicd also can canflict but I can't confirm. You should remove both of them and stick with network-manager.
You should also copy wifi firmware file into /lib/firmware. I don't remember the name and version but if you run dmesg | grep ilwifi.
I found old version of firmware here and the newer here . Keep in mind I don't remember exact names and version at this moment and it would be better to find more certified source of firmware.
The same is if you want to enable bluetooth. Apart of installing bluez package i recommend dmesg | grep blue, find firmware and put it /lib/firmware/intel
And I recommend installing and/or reconfigure resolvconf.
| Wifi on Debian on Dell E7270 |
1,580,455,562,000 |
I'm struggling with very poor wireless performance on a Fedora 25 setup running kernel 4.8.15-300.fc25.x86_64.
When downloading anything via wget, I get like 5Kb/s, and downloads usually stop. If I happen to launch the following ping command in bash while trying to download, performance is fine (about 1Mb/s).
ping google.fr -i .05
As far as I tested, I can surf on internet with some 3-5 seconds lag between pages, which disappears if I use that ping command.
Wifi driver is iwlwifi, firmware is installed even if dmesg complains:
[ 4.225476] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
[ 4.225484] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2
[ 4.226742] iwlwifi 0000:02:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm
According to bugzilla (see https://bugzilla.redhat.com/show_bug.cgi?id=1400269), this shoudln't be an issue.
I manage my own AP (TPLink EAP 110) where I tried to change channel, disabling 802.11n, changing channel width, nothing helps.
The laptop I have the wireless issues with also has a Win10 dualboot. Wifi performance on Win10 is normal.
I can imagine that at some point, the ping forces a keep alive or something (not a wireless specialist speaking).
I have no clue how to get around this. Any ideas please ?
|
Well in my case, I've tried disabling 802.11n, tried other iwl-7265D firmwares. At the end of the day, disabling power management did the trick with iwconfig wlan0 power off.
Seems to be a big issue with intel cards and iwlwifi drivers.
Rendering this permanent is done by creating the following file in /etc/NetworkManager/dispatcher.d/02-wlan-power
#!/bin/sh
IF=$1
STATUS=$2
IFACES=$(iwconfig 2> /dev/null | grep "802.11" | awk '{print $1}')
for iface in $IFACES; do
if [ "${IF}" = "${iface}" ] && [ "${STATUS}" = "up" ]; then
iwconfig ${iface} power off
logger "${iface}: turning off powersave mode to prevent constant reconnections"
fi
done
Don't forget to chmod 755 that file.
Rebooting should do the trick.
| Very bad wireless performance |
1,580,455,562,000 |
I put my .ucode file in /lib/firmware folder. On boot Debian write me:
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.215242] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x22983f10a64, max_idle_ns: 440795218721 ns
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216451] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8000C-21.ucode (-2)
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216494] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-21.ucode failed with error -2
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216505] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8000C-20.ucode (-2)
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216546] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-20.ucode failed with error -2
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216554] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8000C-19.ucode (-2)
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216592] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216600] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8000C-18.ucode (-2)
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216640] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216648] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8000C-17.ucode (-2)
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216684] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216692] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8000C-16.ucode (-2)
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216730] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-16.ucode failed with error -2
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216737] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8000C-15.ucode (-2)
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216769] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-15.ucode failed with error -2
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216777] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8000C-14.ucode (-2)
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216820] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-14.ucode failed with error -2
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216830] iwlwifi 0000:02:00.0: firmware: failed to load iwlwifi-8000C-13.ucode (-2)
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216867] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-13.ucode failed with error -2
Oct 22 22:32:28 LionZXY-debian kernel: [ 2.216869] iwlwifi 0000:02:00.0: no suitable firmware found!
Exit modinfo iwlwifi:
filename: /lib/modules/4.7.0-1-amd64/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
license: GPL
author: Copyright(c) 2003- 2015 Intel Corporation <[email protected]>
description: Intel(R) Wireless WiFi driver for Linux
firmware: iwlwifi-100-5.ucode
firmware: iwlwifi-1000-5.ucode
firmware: iwlwifi-135-6.ucode
firmware: iwlwifi-105-6.ucode
firmware: iwlwifi-2030-6.ucode
firmware: iwlwifi-2000-6.ucode
firmware: iwlwifi-5150-2.ucode
firmware: iwlwifi-5000-5.ucode
firmware: iwlwifi-6000g2b-IWL6000G2B_UCODE_API_MAX.ucode
firmware: iwlwifi-6000g2a-6.ucode
firmware: iwlwifi-6050-5.ucode
firmware: iwlwifi-6000-4.ucode
firmware: iwlwifi-7265D-21.ucode
firmware: iwlwifi-7265-17.ucode
firmware: iwlwifi-3168-21.ucode
firmware: iwlwifi-3160-17.ucode
firmware: iwlwifi-7260-17.ucode
firmware: iwlwifi-8265-21.ucode
firmware: iwlwifi-8000C--21.ucode
firmware: iwlwifi-9260-th-a0-lc-a0--21.ucode
firmware: iwlwifi-9260-th-a0-jf-a0--21.ucode
firmware: iwlwifi-9000-pu-a0-lc-a0--21.ucode
depends: cfg80211
intree: Y
vermagic: 4.7.0-1-amd64 SMP mod_unload modversions
parm: swcrypto:using crypto in software (default 0 [hardware]) (int)
parm: 11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)
parm: amsdu_size:amsdu size 0:4K 1:8K 2:12K (default 0) (int)
parm: fw_restart:restart firmware in case of error (default true) (bool)
parm: antenna_coupling:specify antenna coupling in dB (default: 0 dB) (int)
parm: nvm_file:NVM file name (charp)
parm: d0i3_disable:disable d0i3 functionality (default: Y) (bool)
parm: lar_disable:disable LAR functionality (default: N) (bool)
parm: uapsd_disable:disable U-APSD functionality bitmap 1: BSS 2: P2P Client (default: 3) (uint)
parm: bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
parm: led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 0) (int)
parm: power_save:enable WiFi power management (default: disable) (bool)
parm: power_level:default power save level (range from 1 - 5, default: 1) (int)
parm: fw_monitor:firmware monitor - to debug FW (default: false - needs lots of memory) (bool)
parm: d0i3_timeout:Timeout to D0i3 entry when idle (ms) (uint)
parm: disable_11ac:Disable VHT capabilities (default: false) (bool)
My Linux version:
[ 0.000000] Linux version 4.7.0-1-amd64 ([email protected]) (gcc version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.8-1 (2016-10-19)
I can't enable WiFi.
Download driver from git.kernel.org (I need reputation to post more than 2 links)
All log and other things you can find here.
Big thanks for your response!
|
This is typical for the std deb kernel, it will look for a version and fail to load it until it finds a valid one and it will load that one.
for example in my log file;
Oct 23 16:39:43 mike-laptop4 kernel: [ 7.432898] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-24.ucode failed with error -2
Oct 23 16:39:43 mike-laptop4 kernel: [ 7.432921] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7265D-23.ucode failed with error -2
(I have iwlwifi-7265D-22.ucode but not 23 or 24 in my firmware directory)
so, for some reason if your wifi is not loading it's not finding the correct firmware version.
I'd suggest checking kernel wifi for a firmware download.
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
you can run lspci to check your wifi chip, then you can download the appropriate firmware blob based off your kernel version and wifi card.
also there are some good tips there regarding power management.
| .ucode driver not load in Debian |
1,580,455,562,000 |
After upgrading debian jessie to stretch my wifi didn't work anymore (Toshiba Kira book). The laptop uses an Intel Wireless 7265 which is supported by iwlwifi.
So I downloaded the .deb files as linked here and did the following:
dpkg - i firmware-iwlwifi_0.43_all.deb
modprobe -r iwlwifi
modprobe iwlwifi
However, even after rebooting, the wifi doesn't show up... iwconfig says that there is no wireless extension.... the dpkg command worked and the iwlwifi module is installed.
dmesg | grep wifi tells me a couple of times:
firmware failed to load iwlwifi-7265D-18.u code with error (-2)
Direct firmware load for iwlwifi-7265D-18.u code failed with error -2
The numbers after the second dash go from 13 to 18.
The wifi did work before I upgraded to stretch so it should in principle be supported. How can I get it to work?
Edit
lspci -knn | grep Net -A2 outputs:
01:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 61)
Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5110]
Kernel modules: iwlwifi
|
Try saving iwlwifi-7265D-13.ucode to /lib/firmware, and if that fixes things, run reportbug firmware-iwlwifi and request an updated package.
| debian stretch wifi not working - iwlwifi installs but doesn't load correctly |
1,580,455,562,000 |
How can I choose which software I want to install from a Debian repository? I know that didn't make much sense, let me explain more detail.
I want to install a «unstable» version of gnupg with (ECC support), but I'm afraid of adding a «unstable» repository to my sources.list file, because it will mess up other sotware when i run:
aptitude upgrade
In short: I want all other packages to be in stable version, except gnupg.
|
Pinning all packages in unstable is easy. Just add
Package: *
Pin: release a=unstable
Pin-Priority: 50
or similar to /etc/apt/preferences.
This will hold back all packages in unstable from upgrade by apt or aptitude. Note that there is nothing magic about 50. From man apt_preferences:
0 < P < 100
causes a version to be installed only if there is no installed version of the package
NOTE: I think this could be better expressed as:
causes a version to be installed only if there is no installable version of higher priority available.
I.e. if pkg is available in your default release, then the unstable version of pkg will not be installed by default.
So any number in that range will work.
To install a version from unstable in this case, you will either have to do
apt-get install pkg/unstable pkg/dep1 pkg/dep2 ...
in which case you will have to add additional dependencies manually (as shown, using dep1 and dep2 as examples) if they are not available in your current release version, or
apt-get install -t unstable pkg
which will automatically take dependencies from unstable, which you probably don't want do to in general. So, be careful with this latter command.
| Choose software from Debian repository |
1,580,455,562,000 |
my Labtop is thinkpad nano，i7, installed centos 7, I update the kernel to adapt to touchpads and HDMI displays...
yum install -y kernel-lt --enablerepo=elrepo-kernel // 5.4.265-1.el7.elrepo
yum install -y kernel-ml --enablerepo=elrepo-kernel // 6.6.10-1.el7.elrepo
Launch kernel 5+, typeC-2-HDMI + Monitor doesn't work;
Launch kernel 6+, WI-FI not work;
lspci | grep -i net
00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)
Then I try to solve the wifi-card problem, display the messages when system starting
iwlwifi 0000:00:14.3: no suitable firmare found!
iwlwifi 0000:00:14.3: minimum version required: iwlwifi-QuZ-a0-hr-b0-50
iwlwifi 0000:00:14.3: minimum version required: iwlwifi-QuZ-a0-hr-b0-77
while When I download the either one of 50～77 firmware form
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree, display the messages of "uCode file size does not match..."
iwlwifi 0000:00:14.3: uCode file size 9342899 does not match expected size
iwlwifi 0000:00:14.3: no suitable firmare found!
iwlwifi 0000:00:14.3: minimum version required: iwlwifi-QuZ-a0-hr-b0-50
iwlwifi 0000:00:14.3: minimum version required: iwlwifi-QuZ-a0-hr-b0-77
the firmware for Intel Corporation Wi-Fi 6 AX201 from Intel Official Site https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html is Qu-*-48, not "QuZ-"
I tried different version for Qu- or QuZ, no luck, Could any help to solve this firmware dirver problem? I just want both of my wifi and HDMI-Monitor working, am I too greedy...
|
When downloading firmware files from the linux-firmware Git repository through its web interface, use the plain link at the far right; otherwise you'll end up downloading a HTMLized hex dump of the firmware, instead of the actual firmware file.
| Centos 7 kernel 6+ cannot recognize wifi-card |
1,580,455,562,000 |
I'm using Mint 21 on an HP 17-y002na laptop. It's been connected via ethernet cable for much of the time since I updated to 21, but has had wifi capability at times. Last week I noticed that the symbol showing ethernet connection was absent from my panel, but wired connection still works. Unplugged, I get no wifi options or connection
Since then I have tried to sort it to no avail, and I think I may be doing more harm than good, so I'm asking for help. Current situation is:
iwconfig returns
lo no wireless extensions.
eno1 no wireless extensions.
wlo1 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
lspci -nnk | grep 0280 -A4 returns
03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n [14e4:4365] (rev 01)
DeviceName: WLAN Broadcom 43142 bgn 1x1
Subsystem: Hewlett-Packard Company BCM43142 802.11b/g/n [103c:804a]
Kernel driver in use: wl
Kernel modules: bcma, wl
'rfkill list all' returns
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
The bluetooth unblocks when I select 'Turn Bluetooth On' in the panel, and the above command does then show 'Soft blocked: no'
'dmesg | grep wl' gives me
[ 13.649275] wl: loading out-of-tree module taints kernel.
[ 13.649291] wl: module license 'MIXED/Proprietary' taints kernel.
[ 13.660611] wl: module verification failed: signature and/or required key missing - tainting kernel
[ 13.877253] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334)
[ 14.674777] wl 0000:03:00.0 wlo1: renamed from wlan0
Wifi is (still) enabled in my BIOS/UEFI set up. Safe boot is disabled
Driver Manager shows I am using bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu10~22.04.1
I do want to be able to use the laptop without having to be ethernet connected
Any information, advice or guidance appreciated. Thank you in advance,
Phil
Edit 1 - replaced output of all commands with current output
Edit 2 - I neglected to include all of the linux-header* i had showing as installed. These were:
linux-headers-5.15.0-79
linux-headers-5.15.0-79-generic
linux-headers-5.15.0-82
linux-headers-5.15.0-82-generic
linux-headers-6.2.0-31-generic
linux-headers-generic
linux-headers-generic-hwe-20.04
linux-headers-generic-hwe-20.04-edge
linux-headers-generic-hwe-22.04
linux-headers-generic-hwe-22.04-edge
I have now uninstalled each of the 5.15.0-79* and 5.15.0-82* headers, as well as the linux-headers-generic-hwe-20.04* headers, and rebooted. Software manager informed me I needed to install 5.15.0-82* again, so I did, and uninstalled linux-headers-6.2.0-31-generic, which automatically removed the linux-headers-generic-hwe-22.04*. Rebooted again, and this time Software Manager didn't flag anything up. Still no wifi, but possibly getting closer to a solution?
|
After running
sudo apt remove bcmwl-kernel-source && sudo apt install --reinstall broadcom-sta-dkms
sudo modprobe -rv bcma wl
and
sudo modprobe -v wl,
then rebooting, still no wifi icon or connection, but I hit on the idea of running terminal commands to see what could be seen
nmcli dev wifi
listed networks I could try connecting to, then
nmcli dev wifi connect <name> password <password>
(put a space at the start of the command to not store details in bash history ) with the appropriate details got me connected and working
Still no icon in the panel, and I don't know if it will survive a reboot, but this is definite progress and I'm going to mark this as solved. I'll add more if I find a) a more persistent solution is needed, and b) a more persistent solution
edit - nmcli con up <network> works if authentication details are already present, and is persistent
| Linux Mint 21 - Broadcom 43142 - wifi stopped working |
1,580,455,562,000 |
I know Linux pretty well, and I know how to use Kali Linux. But when I boot it, it can't connect to my wifi AC.
Apparently, to fix this there's some stuff about ethernet cables and access the wifi and run installation commands...
While I know security research and Linux, I don't know a thing about using ethernet. I've tried to connect it to another computer and whatnot and it doesn't work. All other distros I've tried connect to my wifi adapter just fine.
Ultimately, is there a way I can fix this without fidgeting with ethernet?
Note: It has a message in the installer boot where it asks for the driver files. 1: I don't know where to find them and 2: I don't know how to give them.
My wifi AC is:
Intel(R) Dual Band Wireless-AC 7265
Please help me.
|
Solve: Plug the computer into ethernet while running the installer drive. It does the rest on it's own.
| Installing Kali Linux wifi AC driver without ethernet |
1,289,319,364,000 |
What are the differences between
$ nohup foo
and
$ foo &
and
$ foo &
$ disown
|
Let's first look at what happens if a program is started from an interactive shell (connected to a terminal) without & (and without any redirection). So let's assume you've just typed foo:
The process running foo is created.
The process inherits stdin, stdout, and stderr from the shell. Therefore it is also connected to the same terminal.
If the shell receives a SIGHUP, it also sends a SIGHUP to the process (which normally causes the process to terminate).
Otherwise the shell waits (is blocked) until the process terminates or gets stopped.
Now, let's look what happens if you put the process in the background, that is, type foo &:
The process running foo is created.
The process inherits stdout/stderr from the shell (so it still writes to the terminal).
The process in principle also inherits stdin, but as soon as it tries to read from stdin, it is halted.
It is put into the list of background jobs the shell manages, which means especially:
It is listed with jobs and can be accessed using %n (where n is the job number).
It can be turned into a foreground job using fg, in which case it continues as if you would not have used & on it (and if it was stopped due to trying to read from standard input, it now can proceed to read from the terminal).
If the shell received a SIGHUP, it also sends a SIGHUP to the process. Depending on the shell and possibly on options set for the shell, when terminating the shell it will also send a SIGHUP to the process.
Now disown removes the job from the shell's job list, so all the subpoints above don't apply any more (including the process being sent a SIGHUP by the shell). However note that it still is connected to the terminal, so if the terminal is destroyed (which can happen if it was a pty, like those created by xterm or ssh, and the controlling program is terminated, by closing the xterm or terminating the SSH connection), the program will fail as soon as it tries to read from standard input or write to standard output.
What nohup does, on the other hand, is to effectively separate the process from the terminal:
It closes standard input (the program will not be able to read any input, even if it is run in the foreground. it is not halted, but will receive an error code or EOF).
It redirects standard output and standard error to the file nohup.out, so the program won't fail for writing to standard output if the terminal fails, so whatever the process writes is not lost.
It prevents the process from receiving a SIGHUP (thus the name).
Note that nohup does not remove the process from the shell's job control and also doesn't put it in the background (but since a foreground nohup job is more or less useless, you'd generally put it into the background using &). For example, unlike with disown, the shell will still tell you when the nohup job has completed (unless the shell is terminated before, of course).
So to summarize:
& puts the job in the background, that is, makes it block on attempting to read input, and makes the shell not wait for its completion.
disown removes the process from the shell's job control, but it still leaves it connected to the terminal. One of the results is that the shell won't send it a SIGHUP. Obviously, it can only be applied to background jobs, because you cannot enter it when a foreground job is running.
nohup disconnects the process from the terminal, redirects its output to nohup.out and shields it from SIGHUP. One of the effects (the naming one) is that the process won't receive any sent SIGHUP. It is completely independent from job control and could in principle be used also for foreground jobs (although that's not very useful).
| Difference between nohup, disown and & |
1,289,319,364,000 |
I have started a wget on remote machine in background using &. Suddenly it stops downloading. I want to terminate its process, then re-run the command. How can I terminate it?
I haven't closed its shell window. But as you know it doesn't stop using Ctrl+C and Ctrl+Z.
|
There are many ways to go about this.
Method #1 - ps
You can use the ps command to find the process ID for this process and then use the PID to kill the process.
Example
$ ps -eaf | grep [w]get
saml 1713 1709 0 Dec10 pts/0 00:00:00 wget ...
$ kill 1713
Method #2 - pgrep
You can also find the process ID using pgrep.
Example
$ pgrep wget
1234
$ kill 1234
Method #3 - pkill
If you're sure it's the only wget you've run you can use the command pkill to kill the job by name.
Example
$ pkill wget
Method #4 - jobs
If you're in the same shell from where you ran the job that's now backgrounded. You can check if it's running still using the jobs command, and also kill it by its job number.
Example
My fake job, sleep.
$ sleep 100 &
[1] 4542
Find it's job number. NOTE: the number 4542 is the process ID.
$ jobs
[1]+ Running sleep 100 &
$ kill %1
[1]+ Terminated sleep 100
Method #5 - fg
You can bring a backgrounded job back to the foreground using the fg command.
Example
Fake job, sleep.
$ sleep 100 &
[1] 4650
Get the job's number.
$ jobs
[1]+ Running sleep 100 &
Bring job #1 back to the foreground, and then use Ctrl+C.
$ fg 1
sleep 100
^C
$
| How to terminate a background process? |
1,289,319,364,000 |
I have a process originally running in the foreground. I suspended by Ctrl+Z, and then resume its running in the background by bg <jobid>.
I wonder how to suspend a process running in the background?
How can I bring a background process to foreground?
Edit:
The process outputs to stderr, so how shall I issue the command fg <jobid> while the process is outputting to the terminal?
|
As Tim said, type fg to bring the last process back to foreground.
If you have more than one process running in the background, do this:
$ jobs
[1] Stopped vim
[2]- Stopped bash
[3]+ Stopped vim 23
fg %3 to bring the vim 23 process back to foreground.
To suspend the process running in the background, use:
kill -STOP %job_id
The SIGSTOP signal stops (pauses) a process
in essentially the same way Ctrl+Z does.
example: kill -STOP %3.
sources:
How to send signals to processes in Linux and Unix
How to manage background and foreground jobs.
| How to suspend and bring a background process to foreground |
1,289,319,364,000 |
In the bash terminal I can hit Control+Z to suspend any running process... then I can type fg to resume the process.
Is it possible to suspend a process if I only have it's PID? And if so, what command should I use?
I'm looking for something like:
suspend-process $PID_OF_PROCESS
and then to resume it with
resume-process $PID_OF_PROCESS
|
You can use kill to stop the process.
For a 'polite' stop to the process (prefer this for normal use), send SIGTSTP:
kill -TSTP [pid]
For a 'hard' stop, send SIGSTOP:
kill -STOP [pid]
Note that if the process you are trying to stop by PID is in your shell's job table, it may remain visible there, but terminated, until the process is fg'd again.
To resume execution of the process, sent SIGCONT:
kill -CONT [pid]
| How to suspend and resume processes |
1,289,319,364,000 |
I have a running program on a SSH shell. I want to pause it and be able to unpause its execution when I come back.
One way I thought of doing that was to transfer its ownership to a screen shell, thus keeping it running in there.
Is there a different way to proceed?
|
You can revoke “ownership” of the program from the shell with the disown built-in:
# press Ctrl+Z to suspend the program
bg
disown
However this only tells the shell not to send a SIGHUP signal to the program when the shell exits. The program will retain any connection it has with the terminal, usually as standard input, output and error streams. There is no way to reattach those to another terminal. (Screen works by emulating a terminal for each window, so the programs are attached to the screen window.)
It is possible to reattach the filedescriptors to a different file by attaching the program in a debugger (i.e. using ptrace) and making it call open, dup and close. There are a few tools that do this; this is a tricky process, and sometimes they will crash the process instead. The possibilities include (links collected from answers to How can I disown a running process and associate it to a new screen shell? and Can I nohup/screen an already-started process?):
grab (and the more ambitious cryopid)
neercs
reredirect
reptyr
retty
| How can I disown a running process and associate it to a new screen shell? |
1,289,319,364,000 |
What is the difference between a "job" and a "process"?
|
A process is any running program with its own address space.
A job is a concept used by the shell - any program you interactively start that doesn't detach (ie, not a daemon) is a job. If you're running an interactive program, you can press CtrlZ to suspend it. Then you can start it back in the foreground (using fg) or in the background (using bg).
While the program is suspended or running in the background, you can start another program - you would then have two jobs running. You can also start a program running in the background by appending an "&" like this: program &. That program would become a background job. To list all the jobs you are running, you can use jobs.
For more information on jobs, see this section of the bash man page.
| What is the difference between a job and a process? |
1,289,319,364,000 |
On the man page, it just says:
-m Job control is enabled.
But what does this actually mean?
I came across this command in a SO question, I have the same problem as OP, which is "fabric cannot start tomcat". And set -m solved this. The OP explained a little, but I don't quite understand:
The issue was in background tasks as they will be killed when the
command ends.
The solution is simple: just add "set -m;" prefix before command.
|
Quoting the bash documentation (from man bash):
JOB CONTROL
Job control refers to the ability to selectively stop
(suspend) the execution of processes and continue (resume)
their execution at a later point. A user typically employs
this facility via an interactive interface supplied jointly
by the operating system kernel's terminal driver and bash.
So, quite simply said, having set -m (the default for
interactive shells) allows one to use built-ins such as fg and bg,
which would be disabled under set +m (the default for non-interactive shells).
It's not obvious to me what the connection is between job control and
killing background processes on exit, however, but I can confirm that
there is one: running set -m; (sleep 10 ; touch control-on) & will
create the file if one quits the shell right after typing that
command, but set +m; (sleep 10 ; touch control-off) & will not.
I think the answer lies in the rest of the documentation for set -m:
-m Monitor mode. [...] Background pro‐
cesses run in a separate process group and a line con‐
taining their exit status is printed upon their comple‐
tion.
This means that background jobs started under set +m are not actual
"background processes" ("Background processes are those whose process
group ID differs from the terminal's"): they share the same process
group ID as the shell that started them, rather than having their own
process group like proper background processes. This explains the
behavior observed when the shell quits before some of its background
jobs: if I understand correctly, when quitting, a signal is sent to
the processes in the same process group as the shell (thus killing
background jobs started under set +m), but not to those of other
process groups (thus leaving alone true background processes started
under set -m).
So, in your case, the startup.sh script presumably starts a
background job. When this script is run non-interactively, such as
over SSH as in the question you linked to, job control is disabled,
the "background" job shares the process group of the remote shell, and
is thus killed as soon that shell exits. Conversely, by enabling job
control in that shell, the background job acquires its own process
group, and isn't killed when its parent shell exits.
| Can someone explain in detail what "set -m" does? |
1,289,319,364,000 |
sometimes I run an app in the gnome-terminal, but then I suddenly have to restart gnome or something. I guess the answer to the question is also useful then I want to disconnect from SSH where something is happenning.
Gnome's terminal tree looks like this:
gnome-terminal
bash
some-boring-process
Can I 'detach' bash from gnome-terminal (or detach some-boring-process from bash and redirect its output somewhere)? If I just kill gnome-terminal, bash will be killed to will all its subprocesses
|
If some-boring-process is running in your current bash session:
halt it with ctrl-z to give you the bash prompt
put it in the background with bg
note the job number, or use the jobs command
detach the process from this bash session with disown -h %1 (substitute the actual job number there).
That doesn't do anything to redirect the output -- you have to think of that when you launch your boring process. [Edit] There seems to be a way to redirect it https://gist.github.com/782263
But seriously, look into screen. I have shells on a remote server that have been running for months.
Looks like this:
$ sleep 999999
^Z
[1]+ Stopped sleep 999999
$ bg
[1]+ sleep 999999 &
$ disown -h %1
| How can I close a terminal without killing its children (without running `screen` first)? |
1,289,319,364,000 |
The full portion of the Bash man page which is applicable only says:
If the operating system on which bash is running supports job control, bash contains
facilities to use it. Typing the suspend character (typically ^Z, Control-Z) while
a process is running causes that process to be stopped and returns control to bash.
Typing the delayed suspend character (typically ^Y, Control-Y) causes the process to
be stopped when it attempts to read input from the terminal, and control to be
returned to bash. The user may then manipulate the state of this job, using the bg
command to continue it in the background, the fg command to continue it in the foreground, or the kill command to kill it. A ^Z takes effect immediately, and has the
additional side effect of causing pending output and typeahead to be discarded.
I have never used Ctrl-Y; I only just learned about it. I have done fine with Ctrl-Z (suspend) only.
I am trying to imagine what this option is for. When would it be useful?
(Note that this feature doesn't exist on all Unix variants. It's present on Solaris and OpenBSD but not on Linux or FreeBSD. The corresponding setting is stty dsusp.)
Perhaps less subjectively: Is there anything that can be accomplished with Ctrl-Y that cannot be accomplished just as easily with Ctrl-Z?
|
From the 4BSD manual for csh:
A ^Z takes effect immediately and is like an interrupt in that pending output and unread input are discarded when it is typed. There is another special key ^Y which does not generate a STOP signal until a program attempts to read(2) it. This can usefully be typed ahead when you have prepared some commands for a job which you wish to stop after it has read them.
So, the purpose is to type multiple inputs while the first one is being processed, and have the job stop after they are done.
| What is the purpose of delayed suspend (Ctrl-Y) in Bash? |
1,289,319,364,000 |
Ctrl+Z stops the job whereas Ctrl+C kills the job.
Why is that? Wouldn't the other way make more sense?
z@z-lap:~$ sleep 100&
[1] 4458
z@z-lap:~$ sleep 200&
[2] 4459
z@z-lap:~$ jobs
[1]- Running sleep 100 &
[2]+ Running sleep 200 &
z@z-lap:~$ fg %1
sleep 100
^Z
[1]+ Stopped sleep 100
z@z-lap:~$ jobs
[1]+ Stopped sleep 100
[2]- Running sleep 200 &
z@z-lap:~$ fg %1
sleep 100
^C
z@z-lap:~$ jobs
[2]+ Running sleep 200 &
|
I think you may be confused about the job control notation. Notably "Stopped" means that a job is still alive but that its ability to process anything has been held (it is not given any time on the CPU to process anything). This is effectively a "Pause" or "Suspended" state, although that is not the correct technical term.
CtrlC does not "stop" a job, it cancels or kills it. Technically it causes an interrupt signal to be sent to the program telling it to abort what it is doing and exit immediately. Some programs will hear this signal and do some emergency clean up work on themselves before exiting. Others will not respond to the signal and are subsequently just aborted.
CtrlZ, on the other hand, "stops" a job. Again this is done with a signal, but this time it is a 'stop' instead of an 'interrupt' signal. This effectively puts it on hold and returns control to the shell, but does not actually kill the job. If you would like such a job to keep running, you can then issue a bg command to send the last stopped job to the background. It will then continue running as a background job as if you had run it with & in the first place. You may also use fg to resume the last stopped job in the foreground (allowing it to continue where it left off, and allowing you to interact with it again).
| ctrl c vs. ctrl z with foreground job |
1,289,319,364,000 |
Does a program that is run from an ssh session depend on the connection to the client? For example when the connection is really slow.
So does it actively wait until things are printed on the screen?
And if it does depend on the connection, does it also happen with screen or byobu for example? Since with these the programs are kept running even after disconnecting from the host.
Note: I only found these related questions:
Does temporary disconnecting of ssh session affect a running program?
What happens to screen session over ssh when connection is lost?
|
The output of programs is buffered, so if the connection is slow the program will be halted if the buffer fills up.
If you use screen, it has a buffer as well that it uses to try and display to a connected session. But a program connected in the screen session will not be stopped if screen cannot update the remote terminal fast enough. Just like when a connection is lost, the program continues filling screens buffer until it overflows (pushing out the oldest information). What you see coming in (and can scroll back to) is depending on what is (still) in that buffer. screen effectively discouples your program from your terminal (and your slow SSH connection).
| Do programs run from an ssh session depend on the connection? |
1,289,319,364,000 |
"Yes, and..." is a wonderful rule-of-thumb in improvisational comedy. Not so much in the UNIX world.
When I run the admittedly silly yes& command, I cannot interrupt it. The terminal crashes or gets stuck into a loop.
I expect the yes process to be suspended immediately, since any process in the background should suspend if attempting to write to stdout, but it doesn't seem to be the case, and I'm wondering why.
|
Background processes which write to the terminal are only suspended if the TOSTOP output mode is set, which isn’t the case by default. Try
stty tostop
yes &
and you’ll see that yes is suspended.
Background processes which read from the terminal are suspended by default, because there’s no sensible way for them to get correct input.
See the section on accessing the terminal in the GNU C library manual.
With TOSTOP off, the terminal doesn’t crash or become stuck, it remains responsive to input; so you can stop the background yes by either killing it (kill % if it’s the only background job), or bringing it to the foreground (fg) and stopping it (CtrlC). You’ll have to enter commands blindly but they will work.
| Why does "yes&" crash my Bash session? |
1,289,319,364,000 |
I'm trying to set up a shell script so that it runs background processes, and when I Ctrlc the shell script, it kills the children, then exits.
The best that I've managed to come up with is this. It appears that the kill 0 -INT also kills the script before the wait happens, so the shell script dies before the children complete.
Any ideas on how I can make this shell script wait for the children to die after sending INT?
#!/bin/bash
trap 'killall' INT
killall() {
echo "**** Shutting down... ****"
kill 0 -INT
wait # Why doesn't this wait??
echo DONE
}
process1 &
process2 &
process3 &
cat # wait forever
|
Your kill command is backwards.
Like many UNIX commands, options that start with a minus must come first, before other arguments.
If you write
kill -INT 0
it sees the -INT as an option, and sends SIGINT to 0 (0 is a special number meaning all processes in the current process group).
But if you write
kill 0 -INT
it sees the 0, decides there's no more options, so uses SIGTERM by default. And sends that to the current process group, the same as if you did
kill -TERM 0 -INT
(it would also try sending SIGTERM to -INT, which would cause a syntax error, but it sends SIGTERM to 0 first, and never gets that far.)
So your main script is getting a SIGTERM before it gets to run the wait and echo DONE.
Add
trap 'echo got SIGTERM' TERM
at the top, just after
trap 'killall' INT
and run it again to prove this.
As Stephane Chazelas points out, your backgrounded children (process1, etc.) will ignore SIGINT by default.
In any case, I think sending SIGTERM would make more sense.
Finally, I'm not sure whether kill -process group is guaranteed to go to the children first. Ignoring signals while shutting down might be a good idea.
So try this:
#!/bin/bash
trap 'killall' INT
killall() {
trap '' INT TERM # ignore INT and TERM while shutting down
echo "**** Shutting down... ****" # added double quotes
kill -TERM 0 # fixed order, send TERM not INT
wait
echo DONE
}
./process1 &
./process2 &
./process3 &
cat # wait forever
| How can I kill and wait for background processes to finish in a shell script when I Ctrl+C it? |
1,289,319,364,000 |
I'm looking for something like command1 ; command2 i.e. how to run command2 after command1 but I'd like to plan execution of command2 when command1 is already running.
It can be solved by just typing the command2 and confirming by Enter supposed that the command1 is not consuming standard input and that the command1 doesn't produce to much text on output making it impractical to type (typed characters are blended with the command1 output).
|
Generally what I do is: Ctrl+Z fg && command2
Ctrl+Z to pause it and let you type more in the shell.
Optionally bg, to resume command1 in the background while you type out command2.
fg && command2 to resume command1 in the foreground and queue up command2 afterwards if command1 succeeds. You can of course substitute ; or || for the && if you so desire.
| How to plan a task to run after another already running task in bash? [duplicate] |
1,289,319,364,000 |
As we know, the shell enables the user to run background processes using & at the command line's end. Each background process is identified by a job ID and, of course, by it's PID.
When I'm executing a new job, the output is something like [1] 1234 (the second number is the process ID). Trying to invoke commands like stop 1 and stop %1 causes a failure message: stop: Unknown job: 1
Understanding that the stop command causes a job to be suspended, I was wondering how to get the job ID and do it right.
If the only way to kill a job is by it's process ID, what is the purpose of the job ID?
|
After a process is sent to the background with &, its PID can be retrieved from the variable $!. The job IDs can be displayed using the jobs command, the -l switch displays the PID as well.
$ sleep 42 &
[1] 5260
$ echo $!
5260
$ jobs -l
[1] - 5260 running sleep 42
Some kill implementations allow killing by job ID instead of PID. But a more sensible use of the job ID is to selectively foreground a particular process. If you start five processes in the background and want to foreground the third one, you can run the jobs command to see what processes you launched and then fg %3 to foreground the one with the job ID three.
| How to get the Job ID? [duplicate] |
1,289,319,364,000 |
Yesterday before going to sleep I started a long process of which I thought it would be finished before I stand up, therefore I used
./command && sudo poweroff
my system is configured to not ask for a password for sudo poweroff, so it should shutdown when that command is finished.
However it is still running and I want to use that system for other tasks now. Having that command running in the background is not an issue, but having my system possibly shutting down any second is.
Is there a way to prevent zsh from executing the poweroff command while making sure that the first one runs until it is done?
Would editing the /etc/sudoers file so that the system asks for my password still help in this case?
|
As you clarified in comments it's still running in foreground on an interactive shell, you should just be able to press Ctrl+Z.
That will suspend the ./command job. Unless ./command actually intercepts the SIGTSTP signal and chooses to exit(0) in that case (unlikely), the exit status will be non-0 (128+SIGTSTP, generally 148), so sudo poweroff will not be run.
Then, you can resume ./command in foreground or background with fg or bg.
You can test with:
sleep 10 && echo poweroff
And see that poweroff is not output when you press Ctrl+Z and resume later with fg/bg.
Or with
sleep 10 || echo "failed: $?"
And see failed: 148 as soon as you press Ctrl+Z.
Note that this is valid for zsh and assuming you started it with ./command && sudo poweroff. It may not be valid for other shells, and would not be if you started it some other way such as (./command && sudo poweroff) in a subshell or { ./command && sudo poweroff; } as part of a compound command (which zsh, contrary to most other shells transforms to a subshell so it can be resumed as a whole when suspended).
| How can I prevent the second command in a chain while keeping the first one running? |
1,289,319,364,000 |
Possible Duplicate:
How can I disown a running process and associate it to a new screen shell?
I launched a command that lasts a long time.
I had to disconnect so I moved it in the background (with CTRL+Z and bg) before exiting.
Something like this:
$ my_command
***command is beeing executed and is taking a long time***
^Z
[1]+ Stopped my_command
$ bg
[1]+ my_command &
$ exit
I reconnected and can see the command in the process list but cannot recover with fg.
$ fg
-bash: fg: current: no such job
How do I recover my job in the foreground?
|
If you've already started something somewhere, backgrounded it, and now need to attach it to a new terminal, you can use reptyr to re-attach it. (The man page summarises the command as "Reparent a running program to a new terminal".)
The reason you can't see it in the "jobs" command or use "fg" to bring it to the foreground is because these commands are actually built-in to the shell. They don't technically detach the processes from the terminal you're connected with, so when you exit the shell they should exit as well (you should get a warning when you attempt to exit).
| How to recover a backgrounded job from a previous shell? [duplicate] |
1,289,319,364,000 |
Let's say I have a bash script with the following:
#!/bin/sh
gedit
rm *.temp
When I execute it using sh ./test.sh, gedit pops-up but the rm part does not run until after I close gedit.
I want the script to continue running even if gedit isn't closed; like the gedit isn't blocking the bash execution.
The example I gave is just an example (putting the rm first won't work in a real situation).
|
The term you are looking for is called "backgrounding" a job. When you run a command either in your shell or in a script you can add a flag at the end to send it to the background and continue running new commands or the rest of the script. In most shells including sh, this is the & character.
#!/bin/sh
gedit &
rm ./*.temp
That way, the shell doesn't wait for the termination of gedit and both rm and gedit will run concurrently.
The term "blocking" usually has to do with input/output streams, often to files or a device. It's also used in compiled languages in something similar to the sense you used, but in bash and similar shell scripting, the terminology (and function!) is rather different.
| Non-blocking bash command |
1,289,319,364,000 |
Run a job in the background
$ command &
When it's done, the terminal prints
[n]+ command
or
[n]- command
So sometimes it's a plus and other times it's a minus following [n].
What does plus/minus mean?
|
They are to distinguish between current and previous job; the last job and the second last job for more than two jobs, with + for the last and - for the second last one.
From man bash:
The previous job may be referenced using %-. If there is only a
single job, %+ and %- can both be used to refer to that job. In
output pertaining to jobs (e.g., the output of the jobs command), the
current job is always flagged with a +, and the previous job with a
-.
Example:
$ sleep 5 &
[1] 21795
$ sleep 5 &
[2] 21796
$ sleep 5 &
[3] 21797
$ sleep 5 &
[4] 21798
$ jobs
[1] Running sleep 5 &
[2] Running sleep 5 &
[3]- Running sleep 5 &
[4]+ Running sleep 5 &
$
[1] Done sleep 5
[2] Done sleep 5
[3]- Done sleep 5
[4]+ Done sleep 5
| +/- after a job in the background is done |
1,289,319,364,000 |
Can some one please explain in an easy to understand way the concept of controlling terminal in unix and unix like systems ? Is it related to a session ? If yes, then how ?
|
There is a process group leader - sort of like the head process - that owns the terminal, /dev/tty. A process group can be one or many processes.
The stty command changes and displays terminal settings. If you are actually going to use UNIX seriously consider finding a copy of Stevens 'Advanced Programming in the UNIX Environment'.
Terminals have a lot of heavy baggage from the 1970's. You will spot that right away. Most of those odd settings can be ignored except for special things like UNIX system consoles.
| Concept of controlling terminal in Unix |
1,289,319,364,000 |
Is it possible to change the parent process of a process? If yes, how?
For example,
how does screen manage to attach a screen session and the processes running inside it to different shell processes? Is there change of parent process?
I seem to heard of other ways of change of shell process in which a program is running, but I don't remember. Is there also change of parent process of the program?
I thought disown on a process changes the parent process of the process, simply because the name disown implies that. But I found it is not true.
Emacs client can attach to emacs server on a different terminal tab. Is there change of parent process?
|
The parent process id (ppid) of a process cannot be changed outside of the kernel; there is no setppid system call. The kernel will only change the ppid to (pid) 1 after the processes parent has terminated - if the process did not respond to a signal that the parent was terminated. For this to happen, the process needs to have ignored various signals (SIGHUP, SIGTERM, etc.) beforehand.
screen(1) has a very elegant means of handling detaching and reattaching. When you first start screen, you are actually starting a user interface (ui), which by default will create a daemon (the session manager). This daemon has no terminal associated with it, a new process group (setpgrp(2)), a new session id (setsid(2)). The daemon, running as SCREEN, will then create subprocesses connected to pseudo-terminals (pty), then multiplexes the data from the ptys and the ui (screen). The subprocesses think they are talking with a real terminal.
If the ui screen terminates, the daemon SCREEN will still be running, buffering data, handling signals, waiting for a new ui, etc. because it is a different process group and in its own session. When you reattach with a new ui screen, then the daemon will continue to multiplex as it was doing before. The daemon will run continue running until all subprocesses terminate, is killed, a fatal bug is encountered or the host reboots.
| Change the parent process of a process? |
1,289,319,364,000 |
It happens to me sometimes, that I press CTRL+Z by accident and my application disappears into background. I know, I can bring it back with fg, so it's not such a big deal. But I am wondering about turning this job control off anyway. In my whole life, I cannot remember one instance when I needed it, it just looks to me as a relic form the past.
Is this OK to disable job control entirely? Or am I missing something, and this feature can be useful?
How would I disable it in my .bashrc
UPDATE:
I have tried set +m as suggested by @Falsenames. However, this only works when I type it in the terminal. Adding set +m into my .bashrc has no effect.
|
You can add the following into your command line to stop using monitoring mode.
set +m
If you really need the ctrl-z functionality later, you can just type 'set -m' to enable monitoring for that session.
From man bash. Note that this is for '-m', with "+m" toggling that setting to disable.
set [+abefhkmnptuvxBCEHPT] [+o option] [arg ...]
....
-m
Monitor mode. Job control is enabled. This option is on by default for interactive
shells on systems that support it (see JOB CONTROL above). Background processes
run in a separate process group and a line containing their exit status is printed
upon their completion.
As a last ditch effort, you may want to manually compile a version of bash without the "--enable-job-control" flag. Here is a quick install guide from GNU. If you do choose to go this route, DO NOT replace /bin/bash just in case background processes run through bash expect job control. Instead, make a /bin/bash.alt or another file. Your default shell can be changed to this alternate one by running usermod or editing /etc/passwd as root.
| disabling job control in bash (CTRL-Z) |
1,289,319,364,000 |
I have an exercise to put in a file some data (*conf from some directories) and need to do this in background. I did it and I am wondering what is the meaning of output messages:
[A@localhost tests]$ ls -ld /etc/*conf /usr/*conf > test1_6_conf.txt 2>&1 &
Enter rises this row:
[1] 2533
what does it mean?
After other Enter, another messages appear
[A@localhost tests]$
[1]+ Exit 2 ls --color=auto -ld /etc/*conf /usr/*conf > test1_6_conf.txt 2>&1
What does it mean? What is "Exit 2"?
Enter an check results - seems to be all OK.
[A@localhost tests]$
[A@localhost tests]$ ls -l test1_6_conf.txt
-rw-rw-r--. 1 A A 2641 Nov 22 14:19 test1_6_conf.txt
[A@localhost tests]$
I am using CentOS 6.4, Gnome Terminal Emulator.
|
What does it mean? What is "Exit 2"?
It is exit status of ls. See man for ls:
Exit status:
0 if OK,
1 if minor problems (e.g., cannot access subdirectory),
2 if serious trouble (e.g., cannot access command-line argument).
I guess the reason is that you have lots of *conf files in /etc and no *conf files in /usr. In fact ls -ld /usr/*conf; would have had the same effect.
So If I do on my computer ls for an existing file:
ls main.cpp; echo $?
main.cpp
0
And for a file that does not exists:
ls main.cppp; echo $?
ls: cannot access main.cppp: No such file or directory
2
Or as a background process ls for a a file that does not exists:
>ls main.cppp &
[1] 26880
ls: cannot access main.cppp: No such file or directory
[1]+ Exit 2 ls main.cppp
| What is "Exit 2" from finished background job status? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.