Unfortunately, no one can be told what Redcore Linux is. You have to see it for yourself!
You are not logged in.
Pages: 1
Topic closed
After several tryouts to update my system I am now unable to terminate correctly due to :
>>> Emerging (236 of 1503) sys-kernel/bcmwl-dkms-6.30.223.271-r7::redcore
>>> Failed to emerge sys-kernel/bcmwl-dkms-6.30.223.271-r7, Log file:
>>> '/var/tmp/portage/sys-kernel/bcmwl-dkms-6.30.223.271-r7/temp/build.log'
>>> Jobs: 235 of 1503 complete, 1 failed Load avg: 2.10, 1.70, 1.50
--2023-12-29 21:21:26-- http://www.broadcom.com/docs/linux_sta/hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz
Resolving www.broadcom.com... 2606:4700:4400::ac40:9b6a, 2606:4700:4400::6812:2096, 172.64.155.106, ...
Connecting to www.broadcom.com|2606:4700:4400::ac40:9b6a|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.broadcom.com/docs/linux_sta/hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz [following]
--2023-12-29 21:21:26-- https://www.broadcom.com/docs/linux_sta/hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz
Connecting to www.broadcom.com|2606:4700:4400::ac40:9b6a|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://docs.broadcom.com/docs/linux_sta/hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz [following]
--2023-12-29 21:21:26-- https://docs.broadcom.com/docs/linux_sta/hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz
Resolving docs.broadcom.com... 2606:4700:4400::6812:2096, 2606:4700:4400::ac40:9b6a, 104.18.32.150, ...
Connecting to docs.broadcom.com|2606:4700:4400::6812:2096|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-12-29 21:21:28 ERROR 404: Not Found.
!!! Couldn't download 'hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz'. Aborting.
* Fetch failed for 'sys-kernel/bcmwl-dkms-6.30.223.271-r7', Log file:
* '/var/tmp/portage/sys-kernel/bcmwl-dkms-6.30.223.271-r7/temp/build.log'
...
First I thought that the system had been without update for to long ...
After the first fail tried to fully reinstall with 2101 ISO with to reach this same error ....
Next tried to fully reinstall with 2301 ISO also to reach this same error ....
So now I turn to the Forum in order to understand how to solve this ...
Or can I simply ignore this file ?
If so how do I do such thing ?
Last edited by Mmako (2023-12-29 22:07:11)
Offline
emerge -NuDGav --backtrack=100 --with-bdeps=y @world
This will succeed.
Offline
Hi,
After trying to execute the emerge command as stated I got a segmentation fault with :
>>> /usr/lib64/pkgconfig/libusb-1.0.pc
>>> Failed to install dev-libs/libusb-1.0.26, Log file:
>>> '/var/tmp/portage/dev-libs/libusb-1.0.26/temp/build.log'
build.log file is :
redCore /var/tmp/portage/dev-libs/libusb-1.0.26/temp # cat build.log
>>> Extracting info
* Package: dev-libs/libusb-1.0.26:1
* Repository: gentoo
* USE: abi_x86_32 abi_x86_64 amd64 udev elibc_glibc kernel_linux split-usr
* FEATURES: compressdebug fakeroot network-sandbox preserve-libs sandbox splitdebug usersandbox
>>> Extracting dev-libs/libusb-1.0.26
* checking 15 files for package collisions
>>> Merging dev-libs/libusb-1.0.26 to /
--- /lib64/
>>> /lib64/libusb-1.0.so.0.3.0
>>> /lib64/libusb-1.0.so.0 -> libusb-1.0.so.0.3.0
--- /usr/
--- /usr/share/
--- /usr/share/doc/
--- /usr/share/doc/libusb-1.0.26/
>>> /usr/share/doc/libusb-1.0.26/PORTING.bz2
>>> /usr/share/doc/libusb-1.0.26/TODO
>>> /usr/share/doc/libusb-1.0.26/NEWS
>>> /usr/share/doc/libusb-1.0.26/README.bz2
>>> /usr/share/doc/libusb-1.0.26/AUTHORS.bz2
>>> /usr/share/doc/libusb-1.0.26/ChangeLog.bz2
--- /usr/include/
--- /usr/include/libusb-1.0/
>>> /usr/include/libusb-1.0/libusb.h
--- /usr/lib/
>>> /usr/lib/libusb-1.0.so -> libusb-1.0.so.0.3.0
>>> /usr/lib/libusb-1.0.so.0.3.0
--- /usr/lib/pkgconfig/
>>> /usr/lib/pkgconfig/libusb-1.0.pc
>>> /usr/lib/libusb-1.0.so.0 -> libusb-1.0.so.0.3.0
--- /usr/lib64/
>>> /usr/lib64/libusb-1.0.so
--- /usr/lib64/pkgconfig/
>>> /usr/lib64/pkgconfig/libusb-1.0.pc
Any more ideas ?
Although if I call emerge without the backtrack=100 flag I also get a simple segmentation fault ...
Last edited by Mmako (2023-12-30 12:37:55)
Offline
Apparently after another emerge call ( with exactly the same backtrack values and flags ) worked.
Took several hours but it finished without any errors ...
Thank you for the fast reply ....
Offline
This has been meanwhile sorted. Closing!
Offline
Pages: 1
Topic closed