i was upgrading parrot os and it failed realtek driver and said to use dpkg -a --configure [closed] - operating-system

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 months ago.
Improve this question
dpkg --configure -a
Setting up realtek-rtl8188eus-dkms (5.3.9~git20220829.4ba8e08-0parrot1) ...
Removing old realtek-rtl8188eus-5.3.9~git20220829.4ba8e08 DKMS files...
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/realtek-rtl8188eus/5.3.9~git20220829.4ba8e08/source/dkms.conf)
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/realtek-rtl8188eus/5.3.9~git20220829.4ba8e08/source/dkms.conf)
Module realtek-rtl8188eus-5.3.9~git20220829.4ba8e08 for kernel 5.18.0-14parrot1-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.
8188eu.ko:
Uninstallation
Deleting from: /lib/modules/5.18.0-14parrot1-amd64/updates/dkms/
Original module
No original module was found for this module on this kernel.
Use the dkms install command to reinstall any previous module version.
depmod....
Deleting module realtek-rtl8188eus-5.3.9~git20220829.4ba8e08 completely from the DKMS tree.
Loading new realtek-rtl8188eus-5.3.9~git20220829.4ba8e08 DKMS files...
Deprecated feature: REMAKE_INITRD (/usr/src/realtek-rtl8188eus-5.3.9~git20220829.4ba8e08/dkms.conf)
Building for 6.0.0-2parrot1-amd64
Building initial module for 6.0.0-2parrot1-amd64
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/realtek-rtl8188eus/5.3.9~git20220829.4ba8e08/source/dkms.conf)
Error! Bad return status for module build on kernel: 6.0.0-2parrot1-amd64 (x86_64)
Consult /var/lib/dkms/realtek-rtl8188eus/5.3.9~git20220829.4ba8e08/build/make.log for more information.
dpkg: error processing package realtek-rtl8188eus-dkms (--configure):
installed realtek-rtl8188eus-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
realtek-rtl8188eus-dkms
VERSION ID5.1
VERSION 5.1 Electro Ara
VERSION CODENAME=ara
6.0.0-2parrot1-amd64
any ideas for trouble shoot

Kernel VERSION ID5.1 VERSION 5.1 Electro Ara VERSION CODENAME=ara 6.0.0-2parrot1-amd64 not supported to that device i got some problem with you, downgrade to the stable kernel is the fast way solve this error

deleting the old not installable packages will fix it use:
sudo rm -rf /usr/src/realtek-rtl8*
and
sudo rm -rf /usr/src/r8168-8.050.03/

it would be a real pain in the ass to fix so the most straightforward way to fix it as a whole is to recompile the kernel for Parrot os. download the lastest kernel from kernel.org, untar it and then recompile it and reinstall with a couple of commands and it should work as expected with no errors.

Related

stack-protector enabled but compiler support broken while installing VirtualBox Guest Additions with devtoolset-8

Note: This problem, which I have already solved, is a very different problem from every other similar question on Stack Overflow. I have posted this question and answer in the hopes that it will help someone else experiencing the same issue (or so that, when I have this problem again in 3 years, I'll find this answer).
I am running VirtualBox 6.1.26 on macOS Catalina 10.15.7. I am emulating centOS 7:
$ uname -r
3.10.0-1160.36.2.el7.x86_64
I "inserted" the VirtualBox Guest Additions CD and followed the auto-run prompts to install the Guest Additions. Part way through, it aborted, saying:
This system is currently not set up to build kernel modules.
Please install the gcc make perl packages from your distribution.
Note that I have gcc, make, perl, kernel-devel, and kernel-headers all installed. It also prompted me to check the file /var/log/vboxadd-setup.log for more details. The contents of that log were interesting:
Building the main Guest Additions 6.1.26 module for kernel 3.10.0-1160.36.2.el7.x86_64.
Error building the module. Build output follows.
make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/3.10.0-1160.36.2.el7.x86_64/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j4 modules
arch/x86/Makefile:96: stack-protector enabled but compiler support broken
arch/x86/Makefile:166: *** CONFIG_RETPOLINE=y, but not supported by the compiler. Compiler update recommended.. Stop.
make: *** [vboxguest] Error 2
modprobe vboxguest failed
Extensive searching for these errors yields multiple forum posts and Stack Overflow questions whose replies and accepted answers reveal either that I'm missing one of those installed packages (I'm not) or that my GCC version is less than 7.3 (when support for CONFIG_RETPOLINE=y was added). However:
$ gcc --version
gcc (GCC) 8.3.1 20190311 (Red Hat 8.3.1-3)
This is > 7.3, so it does support this feature. I should note that I installed GCC using the Yum devtoolset packages in order to use this newer compiler:
$ sudo yum list installed|grep devtoolset
...
devtoolset-8-gcc.x86_64 8.3.1-3.2-el7 #centos-sclo-rh
devtoolset-8-gcc-c++.x86_64 8.3.1-3.2-el7 #centos-sclo-rh
devtoolset-8-gcc-gdb-plugin.x86_64 8.3.1-3.2-el7 #centos-sclo-rh
...
devtoolset-8-make.x86_64 1:4.2.1-4.el7 #centos-sclo-rh
...
And I do not have any other GCC versions installed:
$ sudo yum list installed|grep gcc
devtoolset-8-gcc.x86_64 8.3.1-3.2-el7 #centos-sclo-rh
devtoolset-8-gcc-c++.x86_64 8.3.1-3.2-el7 #centos-sclo-rh
devtoolset-8-gcc-gdb-plugin.x86_64 8.3.1-3.2-el7 #centos-sclo-rh
libgcc.x86_64 4.8.5-44.el7 #anaconda
And I have this in ~/.bashrc to enable devtoolset upon login:
...
source scl_source enable devtoolset-8
...
What am I doing wrong?
It turned out the problem wasn't that I was using the wrong GCC version (not possible) or that I was missing any installed packages (I wasn't). Instead, it was a consequence of how the VirtualBox Guest Additions "auto-run" works. Something about the way it runs results in a "fresh" environment without devtoolset-8 properly sourced. As a result, it cannot find the installed GCC 8.3.
The solution was simple: When the auto-run prompt appeared, I dismissed it and did not run auto-run. Instead, I opened a fresh Terminal window and changed directories to /run/media/[username]/VBox_GAs_6.1.26 (YMMV on the exact location of the mounted disk), then ran this command:
$ sudo ./VBoxLinuxAdditions.run
That command completed successfully, the kernel module compiled, the Guest Additions installed, and they are working properly now.

How to compile Bazel on CentOS 6.x? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
As of today, only Ubuntu packages are available.
Can Bazel be compiled on CentOS 6.x?
Bazel is tested to be able to compile on CentOS 6.7 using the docker image produced by this docker file.
The C++ compiler shipped with CentOS 6.7 is too old to compile Bazel, so the trick is simply to use a newer one:
# Install the dependencies of Bazel
yum install java-1.8.0-openjdk-devel wget which findutils binutils gcc tar gzip zip unzip java java-devel git clang zlib-devel gcc-c++
# Install a newer gcc
wget http://people.centos.org/tru/devtools-2/devtools-2.repo -O /etc/yum.repos.d/devtools-2.repo
yum install devtoolset-2-gcc devtoolset-2-gcc-c++ devtoolset-2-binutils
# Set the path to java and gcc
export JAVA_HOME=/usr/lib/jvm/java-1.8.0
export CC=/opt/rh/devtoolset-2/root/usr/bin/gcc
# Clone the repository
git clone https://github.com/bazelbuild/bazel /tmp/bazel
# Compile bazel
cd /tmp/bazel; ./compile.sh
# Copy the bazel binary to some binary directory
cp /tmp/bazel/output/bazel ~/bin

How to install docker on CentOS 7? [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 25 days ago.
Improve this question
After installing EPEL repository and enabling EPEL, I tried the following:
# yum install docker-io || yum --enablerepo=epel install docker-io
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirrors.btte.net
* epel: mirrors.yun-idc.com
* extras: mirrors.btte.net
* updates: mirrors.btte.net
No package docker-io available.
Error: Nothing to do
In CentOS 7, how can I install docker?
As described here, docker is inside the CentOS-Extras repository of CentOS 7 and can be installed without the need for enabling EPEL.
Please note: As of CentOS 7, the correct name of the package should be simply docker, while in the EPEL repository for CentOS 6, it is yet called docker-io.) I guess that's the problem why it fails for you. Hope this helps!
Some additional comments (thanks to #Martin Preusse for the hints):
The packages in the extras repository are a little bit outdated right now. Available version is 0.11.1, while the current stable version of docker is 1.2.0.
While docker was available in the EPEL repository for CentOS 6 as docker-io (because docker is conflicting with the package name of a system tray dock), it is not available in the beta EPEL repository for CentOS 7. And even worse: The version in the EPEL for CentOS 6 is 1.1.2 and much newer than the current version in the official extras repository of CentOS 7.
It wasn't optimal, but I pulled a recent rpm from FC19 and used that on CentOS7. I used docker-io-1.1.2-3.fc19.x86_64 from:
http://rpm.pbone.net/index.php3/stat/4/idpl/27150558/dir/fedora_19/com/docker-io-1.1.2-3.fc19.x86_64.rpm.html
and then performed a local rpm install. I have not had any issues. My CentOS version is CentOS Linux release 7.0.1406 (Core)
This wasn't my preferred way of doing this, but it was better than being so far back in terms of versions.
I have tried with below command it is working.
yum install -y docker.x86_64
You can install docker using repo or a package file as below:
yum install -y yum-utils
yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
yum install docker-ce docker-ce-cli containerd.io docker-compose-plugin
Verify that the fingerprint matches 060A 61C5 1B55 8A7F 742B 77AA C52F EB6B 621E 9F35 and accept the GPG key if requested to do so.
For the installation of a particular version you can refer the command below :
yum list docker-ce --showduplicates | sort -r
OR
You can also install it without adding the repository on the server.
Installation steps using the package download Visit this link: https://download.docker.com/linux/centos Then select your preferred CentOS version. Once you've found the.rpm file for the Docker version you wish to instal, navigate to x86 64/stable/Packages/.

Cabal install error /usr/bin/ld: --hash-size=31: unknown option

When trying to install any package on my computer using a command like
cabal install http-conduit
the installation aborts with the following error:
/usr/bin/ld: --hash-size=31: unknown option
How can I resolve this?
Note: This question intentionally doesn't show research effort, because it was answered immediately in a Q&A-Style manner.
This issue occurs with the binutils-gold package and GHC 7.4. There is an old mailing list entry discussing this issue.
You might need binutils-gold for LLVM for example, but GHC 7.4 can't handle the GOLD linker correctly, because it doesn't understand the --hash-size option.
As noted on the mailing list post, the solution to this is to remove binutils-gold, e.g. on Ubuntu use:
sudo apt-get remove binutils-gold
This will re-symlink /usr/bin/ld to a non-GOLD linker version. After that, repeat the cabal install command.

Install postgres 9.0 in debian lenny [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Dear all,
My system has the following distribution details
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 5.0 (lenny)
Release: 5.0
Codename: lenny
I need to install postgres 9.0 in this machine , but I cannot find any stable lenny packages for postgres 9.0 , Is there any other way to do this
Any suggestion would be appreciated !
Thanks to the new debian backports suite, here's how to install PostgreSQL 9.0 on Debian lenny:
Add the following to /etc/apt/sources.list:
deb http://backports.debian.org/debian-backports lenny-backports main
deb http://backports.debian.org/debian-backports lenny-backports-sloppy main
Then run these 2 commands
apt-get install -t lenny-backports postgresql-common
apt-get install -t lenny-backports-sloppy postgresql-9.0 postgresql-client-9.0 postgresql-contrib-9.0
Note that this utilizes the new lenny-backports-sloppy backport suite - please read the announcement in order to be aware of the trade offs of using this suite.
Installing from source is quite easy:
Basically: Download postgresql-9.0.1.tar.bz2
tar xjf postgresql-9.0.1.tar.bz2
cd postgresql-9.0.1
./configure
make
make install
Details here
thanks leonbloy the backport for lenny is no longer supported. use this site to download
http://ftp.riken.go.jp/pub/FreeBSD/distfiles/postgresql/
wget http://ftp.riken.go.jp/pub/FreeBSD/distfiles/postgresql/postgresql-version.tar.bz2
Then follow leonbloy's instructions above and read the file INSTALL when you uncompress the file.