Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

1 votes
2 answers
56 views
How can I set up Environment Modules on my personal Linux machine to manage multiple compiler versions?
I’m an RSE working on a personal Linux machine and need to manage multiple compiler and MPI versions (e.g., GCC, Clang, Intel). I’m looking to use Lmod or Environment Modules to load and switch toolchains cleanly without manually managing environment variables. Goals: - Install and manage multiple c...
I’m an RSE working on a personal Linux machine and need to manage multiple compiler and MPI versions (e.g., GCC, Clang, Intel). I’m looking to use Lmod or Environment Modules to load and switch toolchains cleanly without manually managing environment variables. Goals: - Install and manage multiple compiler/MPI versions without conflict - Load/unload specific toolchains using module load/unload - Use a personal ~/modulefiles/ directory for modulefiles - Avoid hard-coded paths in .bashrc/.zshrc Setup: - Distro: rocky Linux - Software installed under custom prefixes like /home/user/pkg/gcc/10.2/ - Planning to use Lmod or environment-modules with a personal MODULEPATH Questions: 1. What’s the cleanest setup for Lmod on a personal (non-HPC) system? 2. How should I structure and load my personal modulefiles directory? 3. Are there simple examples of modulefiles for compilers or MPI? 4. How do I handle module version conflicts or dependencies with Lmod? I’ve read the official docs, but most examples assume a shared HPC setup. I’m looking for practical advice or examples tailored to single-user, personal setups.
Roberto_1986 (111 rep)
Jul 12, 2025, 10:23 AM • Last activity: Jul 16, 2025, 11:11 PM
-1 votes
0 answers
24 views
help me understand Modules package RHEL 8
I am having a problem understanding `modules`. In RHEL-8.8 doing an `rpm -qa` shows no specific `module` rpm, and doing a `which module` responds with module () { _module_raw "$@" 2>&1 } a `man module` responds with *command interface to the Modules package.* Can a simple explanation of this be give...
I am having a problem understanding modules. In RHEL-8.8 doing an rpm -qa shows no specific module rpm, and doing a which module responds with module () { _module_raw "$@" 2>&1 } a man module responds with *command interface to the Modules package.* Can a simple explanation of this be given... what/where is the module package in RHEL8? the main problem I am having is with the MODULEPATH and MODULESHOME environment variables. In a specialized install of RHEL-8.8 for a cluster mgr software it makes use of modules and sets these two environment variables to a single specific location... /cm/local/modules/. But I do not know where it does this and there is no /usr/share/Modules folder present unlike in a default install of RHEL, so my other question is what is the proper convention for setting these two environment variables when a /usr/share/Modules/init/ does not exist? I am only ever using the bash shell so I **assume** that would correspond to /usr/share/Modules/init/bash for which has this statement within: # define module command and surrounding initial environment (default value # for MODULESHOME, MODULEPATH, LOADEDMODULES and parse of init config files) _mlcode=${_mlre:-}/usr/bin/tclsh /usr/share/Modules/libexec/modulecmd.tcl bash autoinit _mlret=$? so I assume this is the original conventional location of MODULEPATH being set? In a standard RHEL-8.10 install for reference this is what is under /usr/share/Modules/init/ bash fish lisp profile.csh ruby.rb tcsh_completion bash_completion fish_completion perl.pm profile.sh sh zsh cmake ksh profile-compat.csh python.py tcl zsh-functions/ csh ksh-functions/ profile-compat.sh r.R tcsh
ron (8647 rep)
Jul 15, 2025, 06:00 PM
0 votes
1 answers
50 views
finding location of modules shown from "module list"
my `.bashrc` has a `module add shared cmsh cmd slurm` line, followed only by a `module load slurm`. how can I find the underlying configuration of the `module` program and **specifically** where the modules `cmsh` and `cmd` live ? I want to find out where the path `/cm/local/apps/cmd/bin/cmsh` is ge...
my .bashrc has a module add shared cmsh cmd slurm line, followed only by a module load slurm. how can I find the underlying configuration of the module program and **specifically** where the modules cmsh and cmd live ? I want to find out where the path /cm/local/apps/cmd/bin/cmsh is getting added to my PATH.. which somehow gets lost after doing particular yum installs where I think some dependency items come along for the ride and upset this configuration that results in whenever a new terminal is opened that .bashrc *module add items* all fails. I assume the module add cmsh causes that PATH modification how do I find that particular cmsh.? "module" file ?
ron (8647 rep)
Jul 15, 2025, 03:26 PM • Last activity: Jul 15, 2025, 04:02 PM
2 votes
0 answers
1250 views
How do I prevent module load conflicts (environment modules)?
I am setting up [Environment Modules](http://modules.sourceforge.net/index.html) for a server and have two modules: `test1` and `test2`. The `test1` module needs `java/1.7.0` and `test2` needs `java/1.8.0`. If I use `prereqs`/`conflicts`, as seems to be standard practice, then I must load `java/1.7....
I am setting up [Environment Modules](http://modules.sourceforge.net/index.html) for a server and have two modules: test1 and test2. The test1 module needs java/1.7.0 and test2 needs java/1.8.0. If I use prereqs/conflicts, as seems to be standard practice, then I must load java/1.7.0 before loading test1 but if I load test2 afterwards and module switch java to 1.8.0, test1 remains loaded and may still be functional in a warped manner. The user, of course, has to do the module switch themselves but is there any way to avoid this scenario so that test1 is unloaded if its prereq is. It may be fairly easy to keep track of in the above scenario but if there are lots of tools each with multiple dependencies, I expect problems to arise. Is there some functionality of Environment Modules I'm not aware of or misunderstanding?
Tobi (21 rep)
Feb 15, 2019, 12:50 PM • Last activity: May 26, 2025, 11:14 AM
0 votes
1 answers
2135 views
How to get only stdout_lines with Ansible using mail module
I'm using ansible to scan hosts with clam antivirus and I'm receiving reports via email. Reports contain everything and I want only to receive stdout lines. Is there any way to accomplish this? I wrote email template according to https://gist.github.com/halberom/0aea275632d2b47af0536e5def01d4d2 alth...
I'm using ansible to scan hosts with clam antivirus and I'm receiving reports via email. Reports contain everything and I want only to receive stdout lines. Is there any way to accomplish this? I wrote email template according to https://gist.github.com/halberom/0aea275632d2b47af0536e5def01d4d2 although only thing that is not the same is that I've piped to nice json: The {{ host }} says {{ hostvars[host]['result']['stdout'] | to_nice_json }} The error I get is: > Unable to convert data using to_nice_json, falling back to to_json: 'dict object' has no attribute 'stdout'. the task includes an option with an undefined variable the error was ansible no_log:false If I remove
['stdout']
then email report looks like this: ClamAV scan was performed on host_server { "changed": true, "msg": "All items completed", "results": [ { "ansible_loop_var": "item", "changed": true, "cmd": [ "clamscan", "-r", "-i", "/usr/bin" ], "delta": "0:00:37.293719", "end": "2021-09-09 18:47:55.626094", "failed": false, "invocation": { "module_args": { "_raw_params": "clamscan -r -i /usr/bin", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true, "warn": true } }, "item": "/usr/bin", "rc": 0, "start": "2021-09-09 18:47:18.332375", "stderr": "", "stderr_lines": [], "stdout": "\n----------- SCAN SUMMARY -----------\nKnown viruses: 8563204\nEngine version: 0.103.2\nScanned directories: 1\nScanned files: 701\nInfected files: 0\nData scanned: 110.08 MB\nData read: 109.50 MB (ratio 1.01:1)\nTime: 37.113 sec (0 m 37 s)\nStart Date: 2021:09:09 18:47:18\nEnd Date: 2021:09:09 18:47:55", "stdout_lines": [ "", "----------- SCAN SUMMARY -----------", "Known viruses: 8563204", "Engine version: 0.103.2", "Scanned directories: 1", "Scanned files: 701", "Infected files: 0", "Data scanned: 110.08 MB", "Data read: 109.50 MB (ratio 1.01:1)", "Time: 37.113 sec (0 m 37 s)", "Start Date: 2021:09:09 18:47:18", "End Date: 2021:09:09 18:47:55 " ] } ] } Is there a way to accomplish getting only stdout_lines in my report? I tried with grep in the shell command but failed
shiva (3 rep)
Sep 9, 2021, 03:26 PM • Last activity: May 13, 2025, 04:02 PM
1 votes
3 answers
13933 views
Stuck in initramfs after reboot
I got that error already twice while having my laptop, and I previously were able to fix it after them google search and switching to AHCI in BIOS. However, this time it seems to be another problem because even though sata-mode is AHCI it kicks me back to initramfs. I tried this, [How to switch from...
I got that error already twice while having my laptop, and I previously were able to fix it after them google search and switching to AHCI in BIOS. However, this time it seems to be another problem because even though sata-mode is AHCI it kicks me back to initramfs. I tried this, How to switch from IDE to AHCI , with the hope to not get that error in the future. After that I sadly got the error that I am now stuck on. Original error message ![Original error message ][2] Output from cat /proc/modules and ls dev ![Output from cat /proc/modules and ls dev ][3] Help is greatly appreciated.
Yanis Wilbrand (11 rep)
Nov 11, 2021, 05:30 PM • Last activity: Feb 19, 2025, 04:58 AM
2 votes
1 answers
361 views
Attempt to call undefined import method with arguments ("abs2rel") via package "File::Spec"
I have `Debian GNU/Linux trixie/sid` and I installed [publican][1] from repo of debian. (publican is doing write and publish for `DocBook`) When I run `publican` , It get the following messages: Attempt to call undefined import method with arguments ("abs2rel") via package "File::Spec" (Perhaps you...
I have Debian GNU/Linux trixie/sid and I installed publican from repo of debian. (publican is doing write and publish for DocBook)
When I run publican , It get the following messages: Attempt to call undefined import method with arguments ("abs2rel") via package "File::Spec" (Perhaps you forgot to load the package?) at /usr/share/perl5/Publican/TreeView.pm line 12. Duplicate specification "help" for option "help" Can't open publican: No such file or directory at /usr/bin/publican line 646. Version of my publican is 4.3.2-4.
Also I installed libfile-spec-native-perl package from repo. Then I download source code via: apt source publican Then run publican and get the following error: mohsen@debian:~/src-compiled/publican/publican-4.3.2/bin$ ./publican Attempt to call undefined import method with arguments ("abs2rel") via package "File::Spec" (Perhaps you forgot to load the package?) at /usr/share/perl5/Publican/TreeView.pm line 12. Duplicate specification "help" for option "help" Action required! According to above Action Required! string added to output. I don't know how do I solve it.
You make me happy if solved my problem.
PersianGulf (11308 rep)
Feb 2, 2025, 12:46 PM • Last activity: Feb 3, 2025, 12:49 AM
1 votes
1 answers
26 views
What is the "reports" command in install errors
While trying to install the [`Chart::Clicker`](https://metacpan.org/pod/Chart::Clicker) perl module, I get a lot of dependency errors. When trying to resolve them, I get similar output for each module from the first to the last module listed in the dependencies list. Example For `Module::Pluggable`:...
While trying to install the [Chart::Clicker](https://metacpan.org/pod/Chart::Clicker) perl module, I get a lot of dependency errors. When trying to resolve them, I get similar output for each module from the first to the last module listed in the dependencies list. Example For Module::Pluggable:
Failed 1/45 test programs. 2/192 subtests failed.
make: *** [Makefile:914: test_dynamic] Error 2
  SIMONW/Module-Pluggable-6.2.tar.gz
  /usr/bin/make test -- NOT OK
//hint// to see the cpan-testers results for installing this module, try:
  reports SIMONW/Module-Pluggable-6.2.tar.gz
What/where is reports? This is running on xubuntu 24.04LTS
Gene (11 rep)
Jan 6, 2025, 06:42 PM • Last activity: Jan 6, 2025, 07:55 PM
0 votes
1 answers
200 views
Writing additional kernel layer on UART driver
I want to take leverage the existing kernel API/module to create packet layer abstraction for user space application to transfer "packets" via UART interface. So, the intention is a kernel module that does the following 1) Uses different module to read UART bytes (I'm not sure what I should use, I c...
I want to take leverage the existing kernel API/module to create packet layer abstraction for user space application to transfer "packets" via UART interface. So, the intention is a kernel module that does the following 1) Uses different module to read UART bytes (I'm not sure what I should use, I can see "usbserial" available, but not sure if it can be extended that way) 2) After reading a certain number of bytes do some calculation on in, like crc, type etc. And then transfers the packet to the user space program 3) User space program can use poll mechanism to get notified, and then read the entire packet. How can I build such a thing? I'm having trouble connecting the pieces, and google/chatgpt is not helping. Any example that does something similar would be awesome, thanks! edit: As a packet I'm referring to an internal data structure, nothing to do with any networking protocol, it's literally. struct comms_packet { uint8_t length; uint8_t type; uint8_t data[PACKET_DATA_LEN]; uint8_t crc; };
konradk (1 rep)
Nov 6, 2024, 09:01 PM • Last activity: Nov 7, 2024, 05:16 PM
0 votes
1 answers
243 views
Add symbols of LKM to kernel
I am trying to get my Android kernel working but I have a kernel module that is needed in order to get access to the file system of the device. Unfortunately there is no source code available so there are only the pre-compiled module and the kernel source. The kernel now tries to load the module wit...
I am trying to get my Android kernel working but I have a kernel module that is needed in order to get access to the file system of the device. Unfortunately there is no source code available so there are only the pre-compiled module and the kernel source. The kernel now tries to load the module without success. In the Module.symvers file in the kernel root directory the symbol that is needed is missing but the manufacturer of the device delivered a Module.symvers file from the root of the kernel source tree which includes all symbols that are needed. How can I include those symbols in my kernel to get the module working?
lehmanju (1 rep)
Mar 20, 2016, 02:07 PM • Last activity: Nov 4, 2024, 03:40 PM
0 votes
1 answers
126 views
Unable to install libffi-dev on Debian 8: 404 errors and "_ctypes" module issue
We have a Debian 8 (Jessie) cluster. I am trying to install a software which resulted error: ```none ModuleNotFoundError: No module named '_ctypes' ``` As a remedy, I attempted: `sudo apt-get install libffi-dev` as per [support platform][1] This led to error: ```none E: Failed to fetch http://securi...
We have a Debian 8 (Jessie) cluster. I am trying to install a software which resulted error:
ModuleNotFoundError: No module named '_ctypes'
As a remedy, I attempted: sudo apt-get install libffi-dev as per support platform This led to error:
E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/libf/libffi/libffi-dev_3.1-2+deb8u1_amd64.deb  404  Not Found [IP: 151.101.130.132 80]
I followed these suggestions . Now, my /etc/apt/sources.list file looks like:
deb     http://archive.debian.org/debian/  jessie main contrib non-free
deb-src http://archive.debian.org/debian/  jessie main contrib non-free

deb     http://security.debian.org/debian-security  jessie/updates main
deb-src http://security.debian.org/debian-security  jessie/updates main

deb     http://archive.debian.org/debian/  jessie-backports main
deb-src http://archive.debian.org/debian/  jessie-backports main

# apt-get -t jessie-backports install "package"
deb [ arch=amd64 ] http://www.chem.ucl.ac.uk/repo/  jessie main
Still, the issue is not solved and I am getting error:
E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/libf/libffi/libffi-dev_3.1-2+deb8u1_amd64.deb   404  Not Found [IP: 151.101.66.132 80]
Your advice is highly appreciated. Please help me in rectifying the error.
user654910 (11 rep)
Oct 14, 2024, 03:14 PM • Last activity: Oct 21, 2024, 01:22 PM
1 votes
0 answers
473 views
Problem enabling perl module stream AlmaLinux 8.10
I have an issue with our AlmaLinux 8.10 systems that they suddenly have issues with perl dependancies. It tuns out that the current active perl stream is 5.26 (dnf module list perl*) but some packages want to install the versions that are only available for 5.32 (local own repo). The packages are av...
I have an issue with our AlmaLinux 8.10 systems that they suddenly have issues with perl dependancies. It tuns out that the current active perl stream is 5.26 (dnf module list perl*) but some packages want to install the versions that are only available for 5.32 (local own repo). The packages are available for 5.32, but it complains it cannot install both of them.
cannot install both perl-libs-4:5.32.1-473.module_el8.10.0+3779+d5938d28.x86_64 from almalinux8x-repo and perl-libs-4:5.26.3-422.el8.0.1.x86_64 from @System
This on several packages. We use own own local repo as the machines cannot access the internet. Thus the only package available is the 'latest 5:32' versions. when I try to enable module perl:5.32 it an error:
[bogusadmin@bogusserver1 ~]$ sudo dnf module enable perl:5.32
Last metadata expiration check: 0:04:35 ago on Tue 16 Jul 2024 02:23:47 PM CEST.
Error: Problems in request:
Modular dependency problems:

 Problem 1: module perl:5.26:8020020201210074505:9edba152.x86_64 from almalinux8x-repo conflicts with module(perl:5.32) provided by perl:5.32:8060020220420215943:103a1005.x86_64 from almalinux8x-repo
  - module perl:5.32:8060020220420215943:103a1005.x86_64 from almalinux8x-repo conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba152.x86_64 from almalinux8x-repo
  - module freeradius:3.0:8050020211012203145:ab0f257b.x86_64 from almalinux8x-repo requires module(perl:5.26), but none of the providers can be installed
  - conflicting requests
 Problem 2: module perl:5.26:8020020201210074505:9edba152.x86_64 from almalinux8x-repo conflicts with module(perl:5.32) provided by perl:5.32:8080020230404080540:9edba152.x86_64 from almalinux8x-repo
  - module perl:5.32:8080020230404080540:9edba152.x86_64 from almalinux8x-repo conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba152.x86_64 from almalinux8x-repo
  - module freeradius:3.0:8050020220203082853:aa8850cc.x86_64 from almalinux8x-repo requires module(perl:5.26), but none of the providers can be installed
  - conflicting requests
 Problem 3: module perl:5.26:8020020201210074505:9edba152.x86_64 from almalinux8x-repo conflicts with module(perl:5.32) provided by perl:5.32:8100020240409203632:9edba152.x86_64 from almalinux8x-repo
  - module perl:5.32:8100020240409203632:9edba152.x86_64 from almalinux8x-repo conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba152.x86_64 from almalinux8x-repo
  - module freeradius:3.0:8060020220503123814:fbe42456.x86_64 from almalinux8x-repo requires module(perl:5.26), but none of the providers can be installed
  - conflicting requests
I also cannot disable the old 5.26 first and then enable 5.32, it refuses. It just drops me back to the prompt. already tried deleting ALL perl packages and switch then, but still a no go. As these machines have no connectivity to the internet I have to install packages through our repo server which is a current full mirror of the AlmaLinux 8 repo + EPEL8 but I have some options to add rpm packages ourselfs as I also have a repo called middleware with our own application packages. Does anyone have an idea to switch to the new 5.32 module stream for perl??? P.S. Also a fresh install from the minimal ISO, en then updating the OS with our own repo it get the same result.
Stefan Lelieveld (21 rep)
Jul 16, 2024, 12:57 PM
0 votes
0 answers
935 views
zsh module command not found
I recently switched from `bash` to `zsh` on CentOS 7. I am using `oh-my-zsh` I'm encountering an issue where modules cannot be loaded from a script. When I manually load the module in the login shell, it works fine. However, when I incorporate the same command into a test.sh script, I receive an err...
I recently switched from bash to zsh on CentOS 7. I am using oh-my-zsh I'm encountering an issue where modules cannot be loaded from a script. When I manually load the module in the login shell, it works fine. However, when I incorporate the same command into a test.sh script, I receive an error stating module command not found. I discovered that sourcing /usr/share/Modules/init/zsh in the script resolves the issue. Nonetheless, if I do not source it, the script fails. I've tried including this source command in both .zshrc and .zsh_profile, but neither approach has been successful. Is there anything else I should consider doing? Any advice would be greatly appreciated, thank you. .zshrc # Enable Powerlevel10k instant prompt. Should stay close to the top of ~/.zshrc. # Initialization code that may require console input (password prompts, [y/n] # confirmations, etc.) must go above this block; everything else may go below. #if [[ -r "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh" ]]; then # source "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh" #fi # If you come from bash you might have to change your $PATH. export PATH=$HOME/bin:/usr/local/bin:$PATH unsetopt nomatch # Path to your oh-my-zsh installation. export ZSH="$HOME/.oh-my-zsh" # Set name of the theme to load --- if set to "random", it will # load a random theme each time oh-my-zsh is loaded, in which case, # to know which specific one was loaded, run: echo $RANDOM_THEME # See https://github.com/ohmyzsh/ohmyzsh/wiki/Themes ZSH_THEME="robbyrussell" # Set list of themes to pick from when loading at random # Setting this variable when ZSH_THEME=random will cause zsh to load # a theme from this variable instead of looking in $ZSH/themes/ # If set to an empty array, this variable will have no effect. # ZSH_THEME_RANDOM_CANDIDATES=( "robbyrussell" "agnoster" ) # Uncomment the following line to use case-sensitive completion. #CASE_SENSITIVE="true" # Uncomment the following line to use hyphen-insensitive completion. # Case-sensitive completion must be off. _ and - will be interchangeable. # HYPHEN_INSENSITIVE="true" # Uncomment one of the following lines to change the auto-update behavior # zstyle ':omz:update' mode disabled # disable automatic updates # zstyle ':omz:update' mode auto # update automatically without asking # zstyle ':omz:update' mode reminder # just remind me to update when it's time # Uncomment the following line to change how often to auto-update (in days). # zstyle ':omz:update' frequency 13 # Uncomment the following line if pasting URLs and other text is messed up. # DISABLE_MAGIC_FUNCTIONS="true" # Uncomment the following line to disable colors in ls. # DISABLE_LS_COLORS="true" # Uncomment the following line to disable auto-setting terminal title. # DISABLE_AUTO_TITLE="true" # Uncomment the following line to enable command auto-correction. # ENABLE_CORRECTION="true" # Uncomment the following line to display red dots whilst waiting for completion. # You can also set it to another string to have that shown instead of the default red dots. # e.g. COMPLETION_WAITING_DOTS="%F{yellow}waiting...%f" # Caution: this setting can cause issues with multiline prompts in zsh < 5.7.1 (see #5765) # COMPLETION_WAITING_DOTS="true" # Uncomment the following line if you want to disable marking untracked files # under VCS as dirty. This makes repository status check for large repositories # much, much faster. # DISABLE_UNTRACKED_FILES_DIRTY="true" # Uncomment the following line if you want to change the command execution time # stamp shown in the history command output. # You can set one of the optional three formats: # "mm/dd/yyyy"|"dd.mm.yyyy"|"yyyy-mm-dd" # or set a custom format using the strftime function format specifications, # see 'man strftime' for details. # HIST_STAMPS="mm/dd/yyyy" # Would you like to use another custom folder than $ZSH/custom? # ZSH_CUSTOM=/path/to/new-custom-folder # Which plugins would you like to load? # Standard plugins can be found in $ZSH/plugins/ # Custom plugins may be added to $ZSH_CUSTOM/plugins/ # Example format: plugins=(rails git textmate ruby lighthouse) # Add wisely, as too many plugins slow down shell startup. plugins=(git zsh-autosuggestions zsh-syntax-highlighting web-search you-should-use colored-man-pages dirhistory git colorize cp) source $ZSH/oh-my-zsh.sh # User configuration # export MANPATH="/usr/local/man:$MANPATH" # You may need to manually set your language environment # export LANG=en_US.UTF-8 # Preferred editor for local and remote sessions # if [[ -n $SSH_CONNECTION ]]; then # export EDITOR='vim' # else # export EDITOR='mvim' # fi # Compilation flags # export ARCHFLAGS="-arch x86_64" # Set personal aliases, overriding those provided by oh-my-zsh libs, # plugins, and themes. Aliases can be placed here, though oh-my-zsh # users are encouraged to define aliases within the ZSH_CUSTOM folder. # For a full list of active aliases, run alias. # # Example aliases # alias zshconfig="mate ~/.zshrc" # alias ohmyzsh="mate ~/.oh-my-zsh" # To customize prompt, run p10k configure or edit ~/.p10k.zsh. #[[ ! -f ~/.p10k.zsh ]] || source ~/.p10k.zsh # .bashrc # Uncomment the following line if you don't like systemctl's auto-paging feature: # export SYSTEMD_PAGER= # Add cuda10 binaries to the path export PATH=/usr/local/cuda-10.2/bin/:$PATH ## PULCHARA ####### export PATH=/home/$USER/Downloads/pulchra304/src/:$PATH # User specific aliases and functions .bash_profile # .bash_profile # Get the aliases and functions if [ -f ~/.bashrc ]; then . ~/.bashrc fi # User specific environment and startup programs PATH=$PATH:$HOME/.local/bin:$HOME/bin export PATH
Adupa Vasista (117 rep)
Apr 22, 2024, 09:52 AM • Last activity: Apr 25, 2024, 08:18 AM
0 votes
2 answers
2372 views
Reducing microphone noise using pipewire modules
With pulseaudio, it was easy to load a module for microphone noise reduction. This link explains it clearly: I want to add rnnoise as a plugin of pipewire to cancel the noise of the microphone for all users. I'm looking for a minimalist solution and would like to avoid applications. Like this one:
With pulseaudio, it was easy to load a module for microphone noise reduction. This link explains it clearly: I want to add rnnoise as a plugin of pipewire to cancel the noise of the microphone for all users. I'm looking for a minimalist solution and would like to avoid applications. Like this one:
floupinette (163 rep)
Apr 17, 2024, 10:52 PM • Last activity: Apr 22, 2024, 02:30 PM
1 votes
0 answers
54 views
Shell script looking for a missing module
I want to run a shell script on a compute cluster but I get an error because at some point it is looking for a module that does not exist since a major update on the cluster a few months ago. This module is not loaded in my script, therefore my script is not the direct cause of the problem. One hypo...
I want to run a shell script on a compute cluster but I get an error because at some point it is looking for a module that does not exist since a major update on the cluster a few months ago. This module is not loaded in my script, therefore my script is not the direct cause of the problem. One hypothesis is that the lmod cache is out of date, but I have no idea where is this cache. Or a file is sourced in which the module in question is loaded "intel/2018a". Here is the complete message of the error:
> # User specific environment and startup programs

> PATH=$PATH:$HOME/.local/bin:$HOME/bin
> + PATH=/node/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/cluster/bin:/cluster/home/sbarthelemy/.local/bin:/cluster/home/sbarthelemy/bin:/cluster/home/sbarthelemy/.local/bin:/cluster/home/sbarthelemy/bin

> export PATH
> + export PATH
> # NIRD settings 
> if [ uname -n | head -3c == 'tos' ]
> then
>  # intel compiler
>  source /opt/intel/compilers_and_libraries/linux/bin/compilervars.sh -arch intel64 -platform linux

>  # NCL 
>  export NCARG_ROOT=/opt/ncl64
>  export PATH=/opt/ncl64/bin/:${PATH}
> fi
> ++ uname -n
> ++ head -3c
> + '[' log == tos ']'

> module --force purge
> + module --force purge
> + '[' -z '' ']'
> + case "$-" in
> + __lmod_sh_dbg=vx
> + '[' -n vx ']'
> + set +vx
> Shell debugging temporarily silenced: export LMOD_SH_DBG_ON=1 for Lmod's output
> Shell debugging restarted
> + unset __lmod_sh_dbg
> + return 0
> module load StdEnv
> + module load StdEnv
> + '[' -z '' ']'
> + case "$-" in
> + __lmod_sh_dbg=vx
> + '[' -n vx ']'
> + set +vx
> Shell debugging temporarily silenced: export LMOD_SH_DBG_ON=1 for Lmod's output
> Shell debugging restarted
> + unset __lmod_sh_dbg
> + return 0
> module load intel/2018a
> + module load intel/2018a
> + '[' -z '' ']'
> + case "$-" in
> + __lmod_sh_dbg=vx
> + '[' -n vx ']'
> + set +vx
> Shell debugging temporarily silenced: export LMOD_SH_DBG_ON=1 for Lmod's output
Lmod has detected the following error:  The following module(s) are unknown: "intel/2018a"

> Please check the spelling or version number. Also try "module spider ..."
> It is also possible your cache file is out-of-date; it may help to try:
>   $ module --ignore_cache load "intel/2018a"
Seb (11 rep)
Feb 5, 2024, 10:53 AM • Last activity: Feb 5, 2024, 11:53 AM
2 votes
0 answers
708 views
Whether I can use ipmitool in the VM?
When I start the `ipmi_si` module: modprobe ipmi_si there gets error: >FATAL: Error inserting ipmi_si (/lib/modules/2.6.32-696.el6.x86_64/kernel/drivers/char/ipmi/ipmi_si. My environment is a Virtual Machine `CentOS 6.9`. I found some speech says this because of its a VM, not a physical machine. So,...
When I start the ipmi_si module: modprobe ipmi_si there gets error: >FATAL: Error inserting ipmi_si (/lib/modules/2.6.32-696.el6.x86_64/kernel/drivers/char/ipmi/ipmi_si. My environment is a Virtual Machine CentOS 6.9. I found some speech says this because of its a VM, not a physical machine. So, I want to know whether I can use ipmitool in the VM?
244boy (685 rep)
Jan 14, 2019, 03:44 AM • Last activity: Jan 23, 2024, 12:40 AM
4 votes
4 answers
1987 views
meld won't start on Cygwin: No module named 'meld'
I'm using Cygwin 64 on Windows 10; just updated. Some relevant package versions: * meld: 3.18.0-1 * python3: 3.8.6-1 * python2: 2.7.18-4 I'm also using MobaXTerm's X server (and it works - I can run xclock for example.) When I run meld in a Cygwin bash session (within mintty), I get: ``` Traceback (...
I'm using Cygwin 64 on Windows 10; just updated. Some relevant package versions: * meld: 3.18.0-1 * python3: 3.8.6-1 * python2: 2.7.18-4 I'm also using MobaXTerm's X server (and it works - I can run xclock for example.) When I run meld in a Cygwin bash session (within mintty), I get:
Traceback (most recent call last):
  File "/usr/bin/meld", line 71, in 
    import meld.conf
ModuleNotFoundError: No module named 'meld'
Why is this happening, and how can I get meld to properly run? Notes: * I _think_ this question is on-topic here, but I wasn't quite sure; if it isn't, please comment and I'll move this to SU or whatever. * A related question, which in fact would be even more on-topic here...: Can not start meld on ubuntu 16.04 as error import meld.conf .
einpoklum (10753 rep)
Sep 20, 2021, 03:39 PM • Last activity: Nov 19, 2023, 02:08 AM
1 votes
1 answers
1354 views
Have to rmmod and modprobe every time I start up
I have got a raspberry pi and I've installed it correctly the 8821cu module for my Wi-Fi Dongle and it works ok. But every time I reboot the pi I have to `sudo rmmod 8821cu && modprobe 8821cu` to connect to my access point. Before that the nm-applet says the device is not ready. Output of dmesg befo...
I have got a raspberry pi and I've installed it correctly the 8821cu module for my Wi-Fi Dongle and it works ok. But every time I reboot the pi I have to sudo rmmod 8821cu && modprobe 8821cu to connect to my access point. Before that the nm-applet says the device is not ready. Output of dmesg before rmmod and mmodprobe [ 5.087767] 8821cu: loading out-of-tree module taints kernel. [ 154.347730] rtl8821cu 1-1.2:1.0 wlx000f007d127a: renamed from wlan0 [ 198.536962] IPv6: ADDRCONF(NETDEV_UP): wlx000f007d127a: link is not ready
Ra&#250;l Ulises Mart&#237;n Hern&#225;ndez (11 rep)
Jan 5, 2019, 01:55 PM • Last activity: Nov 7, 2023, 07:35 AM
0 votes
1 answers
128 views
GPL/CCO: Fedora 38 driver module build takes hours instead of minutes
FYI: The driver's Linux specific content if GPL. Everything else is CC0. I made a virgin installation of Fedora 38. To verify that all was setup suitably, I went on to build one of my drivers. The output to the screen was slightly different than previous Fedora releases, but such changes are common....
FYI: The driver's Linux specific content if GPL. Everything else is CC0. I made a virgin installation of Fedora 38. To verify that all was setup suitably, I went on to build one of my drivers. The output to the screen was slightly different than previous Fedora releases, but such changes are common. What was new was that the build takes a long time - a very long time. At present, three different builds have been running for over 22 hours. Each build should have taken about seven minutes. Looking at the .o file dates, it emphasized texttakes about 20 minutes to compile each driver source file. Each eventually completed successfully after about 25 hours. I'm seeking assistance to correct the excruciatingly slow driver builds. Any help would be greatly appreciated. Thank you, **Generate the problem:** 1. Download the "Fedora Workstation 38 Live ISO" image for "For Intel and AMD x86_64 systems" from "https://fedoraproject.org/workstation/download/ ". 2. Install to suitable media. 3. Boot the installable media and perform installation. 4. Boot to the virgin installation and proceed with user account generation and so forth. 5. Install various packages: elfutils-libelf-devel, "kernel-headers-xxx" for current kernel version, "kernel-devel-xxx" for current kernel version 6. Download the driver archive from the General Standards web site (the version number will change over time): http://www.generalstandards.com/downloads/24dsi6c500k.linux.2.3.104.47.1.tar.gz 7. Decompress the archive: tar -xf ./Download/24dsi6c500k.linux.2.3.104.47.0.tar.gz 8. Change into the driver directory: cd 24dsi6c500k/driver 9. Build the driver: make -f Makefile 10. Some initial output is generated, but the build output otherwise proceeds at about one source file compiled every 20 minutes. The final steps take even longer. **The output generated is as follows:**
make: Entering directory '/usr/src/kernels/6.2.9-300.fc38.x86_64'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (GCC) 13.0.1 20230318 (Red Hat 13.0.1-0)
  You are using:           gcc (GCC) 13.0.1 20230401 (Red Hat 13.0.1-0)
  CC [M]  /root/c/gsc/24dsi6c500k/linux/driver/close.o
  CC [M]  /root/c/gsc/24dsi6c500k/linux/driver/device.o
  CC [M]  /root/c/gsc/24dsi6c500k/linux/driver/io.o
....
  CC [M]  /root/c/gsc/24dsi6c500k/linux/driver/os_spinlock.o
  CC [M]  /root/c/gsc/24dsi6c500k/linux/driver/os_time.o
  CC [M]  /root/c/gsc/24dsi6c500k/linux/driver/os_write.o"
It does eventually go to completion. **What I've tried to remedy the problem:** 1. The build’s initial screen output is shown here.
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (GCC) 13.0.1 20230318 (Red Hat 13.0.1-0)
  You are using:           gcc (GCC) 13.2.1 20230728 (Red Hat 13.2.1-0)
Supposing that the slowdown could be a compiler issue I downgraded gcc to the version reported to have been used to build the kernel. The initial output is now as follows, but the build is still extremely slow.
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (GCC) 13.0.1 20230318 (Red Hat 13.0.1-0)
  You are using:           gcc (GCC) 13.0.1 20230401 (Red Hat 13.0.1-0)
2. I reinstalled Fedora 38 and tried again, but there was no improvement. 3. I applied all available updates, but this too did not help. 4. I’ve also turned off the firewall, disabled SELinux and logged in as root, but none of these helped. 5. My builds are normally done over the network on a SAMBA mounted Windows 10 share. So, I tried the build on the local drive, which was a USB 3.0 based M.2 drive. There was no improvement. 6. I then tried another virgin installation on a SATA drive. There was no improvement when building over the network or when building on the local SATA drive. 7. I’ve tried the build under Fedora 38 on three entirely different hosts and have observed the same, very slow results. 8. I've built the driver on several different Fedora installations and hosts to demonstrate the build times for Fedora 38 and for some previous Fedora releases. A. Fedora 38, 64-bit, 8 core, 3.6GHz, 8GB, 2-year-old motherboard (Gigabyte Z390 Designare), Samba mount: 22 hours so far B. Fedora 38, 64-bit, 8 core, 3.6GHz, 8GB, 2-year-old motherboard (Gigabyte Z390 Designare), SATA drive: 22 hours so far C. Fedora 38, 64-bit, 8 core, 3.2GHz, 32GB, 7-year-old motherboard (Asus X99-A/USB 3.1), USB 3 M.2: 22 hours so far D. Fedora 37, 64-bit, 2 core, 2.5GHz, 8GB, 12-year-old motherboard (Asus X99-A/USB 3.1), USB 2 M.2: 7 minutes E. Fedora 36, 64-bit, 2 core, 2.5GHz, 8GB, 12-year-old motherboard (Super X7SBA), SATA drive: 7 minutes F. Fedora 3, 32-bit, 2 core, 2.2GHz, 1GB, 20-year-old motherboard (Iwill DP400), IEDE drive: 37 seconds Over the years I’ve used every formal Fedora release since Fedora Core 3, plus many other distributions. Builds have never taken more than about seven minutes for any of the 45 different drivers I’ve written, maintain and built thousands of times. Build obstacles under new distributions and versions have, until now, been trivial in comparison. (For those who suggest I contact the manufacturer of this driver, well, that would be me.) **Here are my make files:** **Makefile:**
TARGET      := 24dsi6c500k

.NOTPARALLEL: %.o

OBJ_FILES   =                   \
            close.o             \
            device.o            \
            io.o                \
            ioctl.o             \
            irq.o               \
            open.o              \
            read.o              \
            reg.o               \
                                \
            gsc_bar.o           \
            gsc_close.o         \
            gsc_dma.o           \
            gsc_dma_pci.o       \
            gsc_eeprom.o        \
            gsc_endian.o        \
            gsc_endian_pci.o    \
            gsc_init.o          \
            gsc_io.o            \
            gsc_ioctl.o         \
            gsc_irq.o           \
            gsc_irq_pci.o       \
            gsc_open.o          \
            gsc_read.o          \
            gsc_reg.o           \
            gsc_utils.o         \
            gsc_wait.o          \
            gsc_write.o         \
                                \
            os_bar.o            \
            os_close.o          \
            os_event.o          \
            os_init.o           \
            os_ioctl.o          \
            os_irq.o            \
            os_kernel_2_2.o     \
            os_kernel_2_4.o     \
            os_kernel_2_6.o     \
            os_kernel_3.o       \
            os_kernel_4.o       \
            os_kernel_5.o       \
            os_kernel_6.o       \
            os_mem.o            \
            os_metrics.o        \
            os_open.o           \
            os_pci.o            \
            os_proc.o           \
            os_read.o           \
            os_reg.o            \
            os_sem.o            \
            os_spinlock.o       \
            os_time.o           \
            os_write.o



###############################################################################
# Everything here is needed so we can access os_makefile.inc.

.EXPORT_ALL_VARIABLES:

# Locate the source from the starting directory.
ifndef GSC_DEV_DIR
GSC_DEV_DIR := $(shell pwd)
endif

include ${GSC_DEV_DIR}/os_makefile.inc
**os_makefile.inc:**
default: all

# Identify the /dev/nul(l) device
NULL    := $(shell ls /dev/nu[l]* | grep -w null | wc -l )
NULL    := $(shell expr ${NULL})

ifeq ("${NULL}","1")
NULL    := /dev/null
else
NULL    := /dev/nul
endif

.PHONY: all clean default makefile release

# Most of this is ignored by the 2.6 (and later) module builder.
CC          = gcc
CC_FLAGS    += -c -O6 -pipe -fomit-frame-pointer -Wall
CC_FLAGS    += -D__KERNEL__ -DLINUX
CC_FLAGS    += -I. -I${KERNELDIR}
DEP_FILE    = ${GSC_DEV_DIR}/makefile.dep
KERNELDIR   =
KERNELVER   = $(shell uname -r | cut -d . -f1-2 )
KERNELMAJOR = $(shell uname -r | cut -d . -f1 )
RELEASE_RM  = ${OBJ_FILES} .tmp* .*.o.cmd .*.ko.cmd .*.mod.cmd .*.ko.*.cmd *.ko.unsigned *.mod.* *.mod Modules*



# kernel 2.2 ==================================================================
ifeq ("${KERNELVER}","2.2")
KERNELDIR   = /usr/src/linux
MODULE_NAME = ${TARGET}.o

${MODULE_NAME}: ${OBJ_FILES}
    @echo ==== Linking: $@
    @ld -r -o $@ ${OBJ_FILES}
endif

# kernel 2.4 ==================================================================
ifeq ("${KERNELVER}","2.4")

K_DIR   := $(shell ls -d /usr/src/linux/include 2>/dev/null | wc -l )
K_DIR   := $(shell echo $(K_DIR) | sed -e 's/[ \t]*//g')

ifeq ("${K_DIR}","1")
KERNELDIR   = /usr/src/linux/include
else
KERNELDIR   = /usr/src/linux-2.4/include
endif

MODULE_NAME = ${TARGET}.o

${MODULE_NAME}: ${OBJ_FILES}
    @echo ==== Linking: $@
    @ld -r -o $@ ${OBJ_FILES}
endif

# kernel 2.6 ==================================================================
ifeq ("${KERNELVER}","2.6")

${TARGET}-objs  = ${OBJ_FILES}
KERNELDIR       = /lib/modules/$(shell uname -r)/build
MODULE_NAME     = ${TARGET}.ko
obj-m           = ${TARGET}.o
PWD             = $(shell pwd)
RELEASE_RM      += ${TARGET}.o Module.symvers

${MODULE_NAME}: $(shell ls ${GSC_DEV_DIR}/*.[ch])
    @-chmod +rw ${DEP_FILE}
    @-echo -n > ${DEP_FILE}
    @make -C ${KERNELDIR} SUBDIRS=${PWD} modules
    @strip -d --strip-unneeded $@
    @rm -f *.mod.c
endif

# kernel 3.x ==================================================================
ifeq ("${KERNELMAJOR}","3")

${TARGET}-objs  = ${OBJ_FILES}
KERNELDIR       = /lib/modules/$(shell uname -r)/build
MODULE_NAME     = ${TARGET}.ko
obj-m           = ${TARGET}.o
PWD             = $(shell pwd)
RELEASE_RM      += ${TARGET}.o Module.symvers

${MODULE_NAME}: $(shell ls ${GSC_DEV_DIR}/*.[ch])
    @-chmod +rw ${DEP_FILE}
    @-echo -n > ${DEP_FILE}
    @make -C ${KERNELDIR} SUBDIRS=${PWD} modules
    @strip -d --strip-unneeded $@
    @rm -f *.mod.c
endif

# kernel 4.x ==================================================================
ifeq ("${KERNELMAJOR}","4")

${TARGET}-objs  = ${OBJ_FILES}
KERNELDIR       = /lib/modules/$(shell uname -r)/build
MODULE_NAME     = ${TARGET}.ko
obj-m           = ${TARGET}.o
PWD             = $(shell pwd)
RELEASE_RM      += ${TARGET}.o Module.symvers

${MODULE_NAME}: $(shell ls ${GSC_DEV_DIR}/*.[ch])
    @-chmod +rw ${DEP_FILE}
    @-echo -n > ${DEP_FILE}
    @make -C ${KERNELDIR} SUBDIRS=${PWD} modules
    @strip -d --strip-unneeded $@
    @rm -f *.mod.c
endif

# kernel 5.x ==================================================================
ifeq ("${KERNELMAJOR}","5")

${TARGET}-objs  = ${OBJ_FILES}
KERNELDIR       = /lib/modules/$(shell uname -r)/build
MODULE_NAME     = ${TARGET}.ko
obj-m           = ${TARGET}.o
PWD             = $(shell pwd)
RELEASE_RM      += ${TARGET}.o Module.symvers

${MODULE_NAME}: $(shell ls ${GSC_DEV_DIR}/*.[ch])
    @-chmod +rw ${DEP_FILE}
    @-echo -n > ${DEP_FILE}
    @make -C ${KERNELDIR} M=${PWD} modules
    @strip -d --strip-unneeded $@
    @rm -f *.mod.c
endif

# kernel 6.x ==================================================================
ifeq ("${KERNELMAJOR}","6")

${TARGET}-objs  = ${OBJ_FILES}
KERNELDIR       = /lib/modules/$(shell uname -r)/build
MODULE_NAME     = ${TARGET}.ko
obj-m           = ${TARGET}.o
PWD             = $(shell pwd)
RELEASE_RM      += ${TARGET}.o Module.symvers

${MODULE_NAME}: $(shell ls ${GSC_DEV_DIR}/*.[ch])
    @-chmod +rw ${DEP_FILE}
    @-echo -n > ${DEP_FILE}
    @make -C ${KERNELDIR} M=${PWD} modules
    @strip -d --strip-unneeded $@
    @rm -f *.mod.c
endif

# kernel OTHER ================================================================
ifeq ("${KERNELDIR}","")

KERNELDIR   = KERNELDIR_os_makefile.inc_not_known_at_this_time
MODULE_NAME = MODULE_NAME_os_makefile.inc_not_known_at_this_time

${MODULE_NAME}:
    @echo ERROR: KERNEL ${KERNELVER} IS NOT SUPPORTED BY THIS MAKEFILE.
    @_ERROR_ERROR_ERROR_ERROR_ERROR_ERROR_ERROR_ERROR_ERROR
endif



# COMMON ======================================================================

#This is ignored by the 2.6 (and later) module builder.
.c.o:
    @echo == Compiling: $  .tmp1
    @# Remove trailing white space and backslash, if present.
    @-sed -e "s/[ ]*[\\\\]//g"  .tmp2
    @# Put everything on seperate lines.
    @-tr [:space:] \\n  .tmp3
    @# Remove all of the system include files.
    @-grep -v "^[ ]*/"  .tmp4
    @# Remove all empty lines.
    @-grep [[:alnum:]]  .tmp5
    @# Put everything on the same line.
    @-tr '\n' '\040'  .tmp6
    @-echo -e '\012' >> .tmp6
    @# Add all the other dependencies to the end of this file.
    @-echo >> ${DEP_FILE}
    @-grep -v "^[ ]*$@" > .tmp6
    @# Remove blank lines from the list.
    @-grep "[[:alnum:]]"  .tmp7
    @# Sort the list and put it in the dependency file.
    @-sort  ${DEP_FILE}
    @# Cleanup.
    @rm -f .tmp?
    @rm -r -f -d .tmp*\*
    @# Compile the module.
    @${CC} ${CC_FLAGS} $ ${DEP_FILE}

${DEP_FILE}:
    @echo ==== Creating: $@
    @echo > ${DEP_FILE}
    @-chmod +rw ${DEP_FILE}

include ${DEP_FILE}
**makefile.dep:** (an empty file essentially ignored under 2.6 and later kernel builds)
Don (11 rep)
Aug 22, 2023, 01:01 PM • Last activity: Oct 5, 2023, 09:30 PM
0 votes
1 answers
56 views
Unable to find network card after executing mdev - s?
I am customizing a Linux system with a Linux kernel version of 6.4.0. I executed `mdev -s` in `rcS` and checked the startup print, which was also successful. When I entered the live environment, I saw that the name of the network card was `enp2s0`. However, after startup, I found that `enp2s0` could...
I am customizing a Linux system with a Linux kernel version of 6.4.0. I executed mdev -s in rcS and checked the startup print, which was also successful. When I entered the live environment, I saw that the name of the network card was enp2s0. However, after startup, I found that enp2s0 could not be found. I don't know what's going on? I have checked the kernel configuration and found that the network driver is compiled. rcS: echo PATH=/sbin:/bin:/usr/bin:/usr/sbin echo LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib:/lib:/lib64 mount -a source /etc/profile mkdir /dev/pts -p mount -t devpts devpts /dev/pts mdev -s if [ $? -eq 0 ]; then echo "mdev -s executed successfully." else echo "mdev -s execution failed." fi ip addr add 192.168.5.2/24 dev enp2s0 Screenshot of error reporting: enter image description here
just a student (135 rep)
Aug 31, 2023, 11:46 AM • Last activity: Sep 4, 2023, 01:57 AM
Showing page 1 of 20 total questions