Re: [gentoo-user] After Update grub does not work anymore

[Alexander Puchmayr]

Thanks for the hints. Indeed, I didn't read the news regarding grub. 
Booting from a rescue system and running grub-install followed by a grub-
mkconfig solved the problem.

Although I do not fully understand why this happend. AFIAK, installing/
updating grub does not update files in /boot nor /boot/efi. And grub-mkconfig 
only updates /boot/grub/grub.cfg. And the other files from the grub package are 
inside an encrypted system disk, which grub cannot access without getting the 
pass phrase. So, why do the EFI files suddenly stop working without having been 
changed?

Thanks
Alex 

On Freitag, 29. März 2024, 12:00:24 CET hitachi303 wrote:
> Am 29.03.24 um 11:55 schrieb Alexander Puchmayr:
> > Hi,
> > 
> > After upgrading two Lenovo Laptops (UEFI, secure boot disabled), grub does
> > not work anymore; instead it says "Welcome to Grub" ... And then
> > immediately boots into bios setup.
> > 
> > What did go wrong?
> > I did the usual things:
> > * emerge update world
> > * emerge --config gentoo-kernel
> > * grub-mkconfig -o /boot/grub/grub.cfg
> > 
> > Everything went fine without errors, but then the final reboot, only bios
> > setup. And these steps do not alter the efi boot loaders
> > 
> > Any ideas? How to get out of this?
> > 
> > Alex
> 
> Hi,
> 
> die you follow the announcement about grub? eselect news read
> 
> 2024-02-01-grub-upgrades
>Title GRUB upgrades
>AuthorMike Gilbert 
>Posted2024-02-01
>Revision  2
> 
> When booting with GRUB, it is important that the core image and modules
> have matching versions. Usually, running grub-install is sufficient to
> ensure this.
> 
> On the UEFI platform, grub-install allows the core image to be placed in
> two different locations:
> 
> EFI/gentoo/grubx64.efi
> This is the location used by grub-install without options.
> 
> EFI/BOOT/BOOTX64.EFI
> This is the location used by grub-install --removable.
> 
> On upgrades, it is common for users to mismatch the grub-install options
> they used for the current and previous versions of grub. This will cause
> a stale core image to exist. For example:
> 
> /boot/efi/EFI/BOOT/BOOTX64.EFI (grub 2.06 core image)
> /boot/efi/EFI/gentoo/grubx64.efi (grub 2.12 core image)
> /boot/grub/x86_64-efi/*.mod (grub 2.12 modules)
> 
> Booting this system using BOOTX64.EFI image would likely fail due to a
> symbol mismatch between the core image and modules. [1]
> 
> Re-runing grub-install both with and without the --removable option
> should ensure a working GRUB installation.
> 
> However, this will clobber any BOOTX64.EFI image provided by other
> loaders. If dual-booting using another boot loader, users must take care
> not to replace BOOTX64.EFI if it is not provided by GRUB.
> 
> References:
> [1] https://bugs.gentoo.org/920708

[gentoo-user] After Update grub does not work anymore

[Alexander Puchmayr]

Hi,

After upgrading two Lenovo Laptops (UEFI, secure boot disabled), grub does not 
work anymore; instead it says "Welcome to Grub" ... And then immediately boots 
into bios setup.

What did go wrong?
I did the usual things:
* emerge update world
* emerge --config gentoo-kernel
* grub-mkconfig -o /boot/grub/grub.cfg

Everything went fine without errors, but then the final reboot, only bios 
setup. 
And these steps do not alter the efi boot loaders

Any ideas? How to get out of this?

Alex

Re: [gentoo-user] CPU ISA level is lower than required

[Alexander Puchmayr]

Hi there,

Unfortunately this still did not help.

I repeat my original question:

Q: The binary (e.g. /usr/bin/bzip2) obviously "knows" what it requires. How do 
I find out what this is? Neither ldd, ld.so or the like seem to give me this 
information.

BR
   Alex


On Sonntag, 3. März 2024, 18:45:16 CET Alexander Puchmayr wrote:
> Am Sonntag, 3. März 2024, 14:32:41 CET schrieb Andreas K. Huettel:
> > > I set CFLAGS="-O2 -pipe march=x86-64-v2" on the buildhost and performed
> > > a
> > > emerge -ev @world, re-creating all packages in binary form.
> > > 
> > > My expectation was that these packages would work on the target
> > > platform,
> > > but they don't. Error message "CPU ISA level is lower than required".
> > 
> > Quiz question: did you rebuild your toolchain *before* or *after* bzip2?
> > 
> > Suspicion without proof, the startup code embedded by gcc and glibc may
> > well be affected by the microarchitecture level. As may be libraries
> > statically linked in...
> > 
> > The safer way would be to run emerge -ev world, and afterwards build the
> > packages with a second emerge -ev world ...
> 
> Indeed, that seems to be the problem. I remember, my first try was with -v3
> (as my buildhost supported this), and, after discovering the "surprise" on
> the target machine, started the emerge -ev @world. Likely, glibc was not
> the first package, so there are an unknown number of packets that have the
> problem.
> 
> I started to recompile the "usual suspects", like bzip2 and xz, which made
> it a bit better, but still the emerge -uavDNk @world did not succeed.
> 
> Now I'm doing again a emerge -ev @world on my buildhost again, so tomorrow
> it should be solved.
> 
> Thanks for the hint
>   Alex

Re: [gentoo-user] CPU ISA level is lower than required

[Alexander Puchmayr]

Am Sonntag, 3. März 2024, 14:32:41 CET schrieb Andreas K. Huettel:
> > I set CFLAGS="-O2 -pipe march=x86-64-v2" on the buildhost and performed a
> > emerge -ev @world, re-creating all packages in binary form.
> > 
> > My expectation was that these packages would work on the target platform,
> > but they don't. Error message "CPU ISA level is lower than required".
> 
> Quiz question: did you rebuild your toolchain *before* or *after* bzip2?
> 
> Suspicion without proof, the startup code embedded by gcc and glibc may well
> be affected by the microarchitecture level. As may be libraries statically
> linked in...
> 
> The safer way would be to run emerge -ev world, and afterwards build the
> packages with a second emerge -ev world ...

Indeed, that seems to be the problem. I remember, my first try was with -v3 (as 
my buildhost supported this), and, after discovering the "surprise" on the 
target machine, started the emerge -ev @world. Likely, glibc was not the first 
package, so there are an unknown number of packets that have the problem.

I started to recompile the "usual suspects", like bzip2 and xz, which made it 
a bit better, but still the emerge -uavDNk @world did not succeed.

Now I'm doing again a emerge -ev @world on my buildhost again, so tomorrow it 
should be solved.

Thanks for the hint
Alex

[gentoo-user] CPU ISA level is lower than required

[Alexander Puchmayr]

Hi,

I tried to tweak some settings regarding CFLAGS="march=x86-64-v2" on my 
buildhost and then install the binary packages on the target machines.

Buildhost: AMD Ryzen 7 2700; ld.so --help says:
Subdirectories of glibc-hwcaps directories, in priority order:
  x86-64-v4
  x86-64-v3 (supported, searched)
  x86-64-v2 (supported, searched)

Target platform: AMD A8-5500; ld.so --help says
Subdirectories of glibc-hwcaps directories, in priority order:
  x86-64-v4
  x86-64-v3
  x86-64-v2 (supported, searched)

I set CFLAGS="-O2 -pipe march=x86-64-v2" on the buildhost and performed a 
emerge -ev @world, re-creating all packages in binary form.

My expectation was that these packages would work on the target platform, but 
they don't. Error message "CPU ISA level is lower than required". 

Q: The binary (e.g. /usr/bin/bzip2) obviously "knows" what it requires. How do 
I find out what this is? Neither ldd, ld.so or the like seem to give me this 
information.

Q: Does the xpak format encode those requirements in any way, if so , how can 
I read them?

Q: Can I compile binary packages with multiple ISA sets and let portage on the 
target machine decide which sub-package to use depending on capabilities of 
the target CPU?

[gentoo-user] Media-sound/strawberry and external mass storage devices

[Alexander Puchmayr]

Hi there,

I installed strawberry on two systems: My desktop and my laptop computer; 
While my desktop shows all attached USB mass storage media in stawberry's 
device tab, the laptop's device tab stays empty, no matter what I connect or 
in which order (start strawberry first, then insert USB stick or the other way 
round).

Mounting and accessing the devices in KDE/Dolphin works fine, they immediately 
appear in plasma's removable device widget, I can open and use them as usual. 

However, when starting strawberry on command line with option --version, I see 
some differences:

10:11:33.916 INFO  DeviceManager:450Device added: "Gio//f2fs/
29868666880" ("Gio//f2fs/29868666880")
10:11:33.917 INFO  DeviceManager:450Device added: "Udisks2/
AA5YSPHZ0QR09UDC/Corsair/Voyager 3.0/30408704000/5ca996d4-0070-4196-865c-
d5c8f32c59eb"

Those lines are only shown on the desktop PC (the one that shows the devices 
in the device tab), the laptop shows no single DeviceManager message. 

Does anyone have an idea what prevents Strawberry's device manager from 
showing/scanning devices? 

Thanks
Alex

[gentoo-user] Gentoo-kernel 6.6 -- how to install?

[Alexander Puchmayr]

Hi there,

Since now kernel 6.6 is stable, installation procedure seems to have changed.

I used to install it by 

emerge --config gentoo-kernel
grub-mkconfig -o /boot/grub/grub.cfg

But grub does not find the kernel, since it is not installed in /boot's root 
but in some uuid named sub directory.

Eselect news says for grub users, nothing changes, but actually it does not 
work.

So how is this now supposed to work?

Best regards
Alex

Re: [gentoo-user] Kmail does not show all imap folders

[Alexander Puchmayr]

On Montag, 22. Jänner 2024, 10:48:02 CET Michael wrote:
> In Kmail make sure you have subscribed on the server folders you want Kmail
> to show.  Right-click on the top folder and select 'Serverside
> Subscription' to show the tree of folders on the server.

Indeed, that was missing. I only looked at "local subscriptions", not server 
side subscriptions. Now folders are shown :-)

Thanks a lot
Alex

[gentoo-user] Kmail does not show all imap folders

[Alexander Puchmayr]

Hi there,

I'm using dovecot as imap server, some sieve scripts sorting incoming mails 
into a folder structure and kmail on multiple different machines as client. The 
folder structure on the server looks fine, I can access the folders via command 
line and I don't see anything obviously wrong.

Some of those target folders are not shown on all machines, they are simply 
ignored; Unfortunately these folders contain important mails which I need to 
react to (which is bad if I do not see them on my main machine, only in some 
test VM). 

I checked folder subscriptions in kmail, but I do not see the missing folders 
there either. Also akonadi-console does not show them. I also tried 
curl imaps:///
Showing all of the missing folders, so I think its an akonadi/kmail problem 
and not an imap problem. 

Any ideas? 

BR
Alex 

Kde-apps/kmail-23.08.3
Kde-frameworks/kjobwidgets-5.112.0
kde-apps/akonadi-23.08.3-r1

[gentoo-user] About python dependencies

[Alexander Kurakin]

Suppose, we have package A which depends on package B.
 
I see three statements in
https://projects.gentoo.org/python/guide/single.html#dependencies
and
https://projects.gentoo.org/python/guide/multi.html#dependencies :
 
1. If A is multi-impl, we should use `B[${PYTHON_USEDEP}]`.
 
2a. If A is single-impl and B is single-impl, we should use 
`B[${PYTHON_SINGLE_USEDEP}]`.
 
2b. If A is single-impl and B is multi-impl, we should use 
`$(python_gen_cond_dep 'B[${PYTHON_USEDEP}])`.
 
Are all statements correct? Thanks!
 
Sincerely,
Alexander Kurakin.

Re: [gentoo-user] After upgrade no login screen anymore

[Alexander Puchmayr]

On Samstag, 11. März 2023, 13:03:41 CET Alexander Puchmayr wrote:
> Hi there,
> 
> After having done a world update, neither sddm nor lightdm do start an
> Xserver anymore. The X server itself runs fine, I can start it from the
> console and I after setting DISPLAY properly can even start programs using
> it, but the login managers do not start X for some reason.
> 
> No hint so far in the logs, and no ideas where I should looking.
> 
> The system is running inside a virtualbox VM, with Win10 as host operating
> system.
> 

Its even getting more strange, the very same image copied from the windows 
laptop to a linux box and started with kvm/libvirt works fine, but in windows/
virtualbox it doesn't.

Now I have two completely identical systems which only differn in the 
hypervisor they're started with, named "virtualbox" and "libvirt". On both 
systems, I start lightdm from the command line with -d option, and compare the 
results.

Intrestingly the "libvirt" system writes "New seat added from logind: seat0", 
the "virtualbox" system does not, which seems to be the relevant difference 
(see log output below)

Further, I found the following command in another forum:

Gdbus introspect --system --dest org.freedesktop.login1 --object-path /org/
freedesktop/login1/seat/seat0

And the relevant difference here is in the org.freedesktop.login1.Seat 
properties section

...
readonly b CanGraphical = false;
...

on virtualbox. The same command on "libvirt" machine shows "true" here.

So, what is required for a login seat to be treated as "graphical"?  

Thanks
Alex


[virtualbox] # lightdm -d
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=867
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/
lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/
lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation local 
(GLocalVfs) for ?gio-vfs?
[+0.01s] DEBUG: Using cross-namespace EXTERNAL authentication (this will 
deadlock if server is GDBus < 2.73.3)
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process 
?plymouth? (No such file or directory)
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User2001 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.09s] DEBUG: User /org/freedesktop/Accounts/User2002 added
...waiting for ctrl-C and no login screen ...

[libvirt] # lightdm -d
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=793
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/
lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/
lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will 
deadlock if server is GDBus < 2.73.3)
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local 
(GLocalVfs) for ?gio-vfs?
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process 
?plymouth? (No such file or directory)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/
root/:0
[+0.01s] DEBUG: XServer 0: Launching X Server
[+0.01s] DEBUG: Launching process 799: /usr/bin/X :0 -seat seat0 -auth /var/
run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus pa

Re: [gentoo-user] After upgrade no login screen anymore

[Alexander Puchmayr]

Am Samstag, 11. März 2023, 16:21:01 CET schrieb netfab:
> In lightdm.conf, try to set :
> > logind-check-graphical=false
> 
> Then restart the service.
> 
> Does this help ?

No. Same as before.

Re: [gentoo-user] After upgrade no login screen anymore

[Alexander Puchmayr]

On Samstag, 11. März 2023, 13:17:12 CET Michael wrote:
> On Saturday, 11 March 2023 12:03:41 GMT Alexander Puchmayr wrote:
> > Hi there,
> > 
> > After having done a world update, neither sddm nor lightdm do start an
> > Xserver anymore. The X server itself runs fine, I can start it from the
> > console and I after setting DISPLAY properly can even start programs using
> > it, but the login managers do not start X for some reason.
> > 
> > No hint so far in the logs, and no ideas where I should looking.
> > 
> > The system is running inside a virtualbox VM, with Win10 as host operating
> > system.
> > 
> > Any ideas?
> > 
> > Thanks
> > 
> >Alex
> 
> Asking the obvious, but is display-manager service running?

Of course. I even tried starting it on the command line with the -d option to 
see whether I get any useful information. 

lightdm -d
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=1176
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/
lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/
lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using Xephyr for X servers
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local 
(GLocalVfs) for ?gio-vfs?
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will 
deadlock if server is GDBus < 2.73.3)
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process 
?plymouth? (No such file or directory)
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User2001 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.09s] DEBUG: User /org/freedesktop/Accounts/User2002 added
^C[+27.38s] DEBUG: Got signal 2 from process 0
[+27.38s] DEBUG: Caught Interrupt signal, shutting down
[+27.38s] DEBUG: Stopping display manager
[+27.38s] DEBUG: Display manager stopped
[+27.38s] DEBUG: Stopping daemon
[+27.38s] DEBUG: Exiting with return value 0

[gentoo-user] After upgrade no login screen anymore

[Alexander Puchmayr]

Hi there,

After having done a world update, neither sddm nor lightdm do start an Xserver 
anymore. The X server itself runs fine, I can start it from the console and I 
after setting DISPLAY properly can even start programs using it, but the login 
managers do not start X for some reason. 

No hint so far in the logs, and no ideas where I should looking.

The system is running inside a virtualbox VM, with Win10 as host operating 
system.

Any ideas?

Thanks
   Alex

Re: [gentoo-user] [SOLVED] Nextcloud-24.0.7 and proxy settings

[Alexander Puchmayr]

Hi there,

The problem has a rather simple cause and also a simple solution:

Nextcloud expects a working DNS server for resolving its own app server, 
*then* it is using the proxy to access it. 

After configuring a DNS proxy in my DMZ and ensuring that /etc/resolv.conf on 
the nextcloud instance is correctly pointing to it, it suddenly works :-)

Alex 


On Sonntag, 19. Februar 2023, 13:17:41 CET Alexander Puchmayr wrote:
> Hi there,
> 
> I'm trying to setup a nextcloud instance inside a DMZ that has no direct
> connection to the outside world, only via proxy. The proxy itself is working
> fine, but I fail to configure nextcloud to actually use this proxy.
> 
> According to the docs, I tried setting the proxy field in config/config.php,
> i.e.
> 
>  $CONFIG = array (
>   ...
>   'proxy' => '10.46.1.109:3128',
>   'proxyuserpwd' => '',
>   ...
> );
> 
> But this setting seems to be ignored, tcpdump does not show any connection
> attempt to that ip and nextcloud complains that it cannot connect to the
> internet.
> 
> In another forum I found that in
> /etc/apache2/vhosts.d/10_nextcloud_vhosts.conf, environment variables like
> HTTP_PROXY and HTTPS_PROXY may be set, i.e.
> 
> 
> ...
> SetEnv HTTP_PROXY 10.46.1.109:3128
> SetEnv HTTPS_PROXY 10.46.1.109:3128
> ...
> 
> 
> But this also does not seem to work.
> 
> Any other ideas?
> 
> Thanks
>   Alex

Re: [gentoo-user] emerge times blown out

[Alexander Puchmayr]

Am Samstag, 18. Februar 2023, 01:49:11 CET schrieb Adam Carter:
> I have three systems (all ~arch) and the emerge times have blown out on all
> of them across all packages. Worst example appears to be;
> 
> Fri Dec 23 13:11:44 2022 >>> net-libs/webkit-gtk-2.38.3-r410
>merge time: 37 minutes and 8 seconds.
> 
>  Fri Dec 23 13:43:08 2022 >>> net-libs/webkit-gtk-2.38.3
>merge time: 31 minutes and 24 seconds.
> 
>  Sat Feb  4 21:16:40 2023 >>> net-libs/webkit-gtk-2.38.4-r410
>merge time: 6 hours, 53 minutes and 28 seconds.
> 
>  Sun Feb  5 04:17:12 2023 >>> net-libs/webkit-gtk-2.38.4
>merge time: 7 hours and 32 seconds.
> 
> Is anyone else seeing this?

Could it be that some kind of Spectre mitigation is active? I just read about 
some massive performance problems in Kernel 5.19+ on Skylake CPUs. Stable 
gentoo kernel was upgraded to 6.1 recently, which could also be affected by 
this problem.
See https://lkml.iu.edu/hypermail/linux/kernel/2209.1/02248.html

Try turning the mitigations off or revert to a 5.15.x kernel.

Alex

[gentoo-user] Nextcloud-24.0.7 and proxy settings

[Alexander Puchmayr]

Hi there,

I'm trying to setup a nextcloud instance inside a DMZ that has no direct 
connection to the outside world, only via proxy. The proxy itself is working 
fine, but I fail to configure nextcloud to actually use this proxy.

According to the docs, I tried setting the proxy field in config/config.php, 
i.e.

 '10.46.1.109:3128',
  'proxyuserpwd' => '',
  ...
);

But this setting seems to be ignored, tcpdump does not show any connection 
attempt to that ip and nextcloud complains that it cannot connect to the 
internet.

In another forum I found that in 
/etc/apache2/vhosts.d/10_nextcloud_vhosts.conf, environment variables like 
HTTP_PROXY and HTTPS_PROXY may be set, i.e.


...
SetEnv HTTP_PROXY 10.46.1.109:3128
SetEnv HTTPS_PROXY 10.46.1.109:3128
...


But this also does not seem to work. 

Any other ideas?

Thanks
Alex

[gentoo-user] .ebuild-Bash-scripts and (non-)fatal errors

[Alexander Kurakin]

Good day!
 
What are the reasons why `.ebuild`-Bash-scripts are started by `emerge`/etc. 
without `set -e` flag?
In other words, `QA Notice: command not found` is just a QA notice instead of a 
fatal error.
 
And can I change it for some `emerge` run?
 
Sincerely,
Alexander Kurakin.
 

[gentoo-user] Re: Move HOMEPAGE, DESCRIPTION, etc. to metadata.xml?

[Alexander Kurakin]

> For what it's worth, among what I maintain, there is
> one package (nvidia-drivers) where the 0/vulkan slot (525.47.x) has
> a different HOMEPAGE pointing to the vulkan page.
 
BTW, as I understand, there is `restrict` attribute for this option [1].
But as for now, its syntax is poor as it’s EAPI 0-compatible.
 
[1]  https://devmanual.gentoo.org/ebuild-writing/misc-files/metadata/index.html
 
Sincerely,
Alexander Kurakin.
 
 

[gentoo-user] How to produce broken binary packages

[Alexander Puchmayr]

Hi there, 

I just encountered a problem regarding binary packages and got some broken 
packages and I don't know how to solve this permanently; On my buildhost I 
compile all packages I need for several VMs and install only those packages I 
really need on the target machines.

Problem combination:

* net-fs/samba-4.15.12-r2 has a direct dependency to sys-libs/liburing. 
* dev-db/mariadb does not have a dependency to liburing, but during build, if 
liburing is available it will use it for some reason yielding a binary that 
links against it:

Buildhost-server ~ # ldd /usr/sbin/mysqld 
linux-vdso.so.1 (0x7ffec5b61000)
libpcre2-8.so.0 => /usr/lib64/libpcre2-8.so.0 (0x7fcfbd704000)
libcrypt.so.2 => /lib64/libcrypt.so.2 (0x7fcfbd6c9000)
liburing.so.2 => /usr/lib64/liburing.so.2 (0x7fcfbd6c2000)
---

Installing that package on a target VM does not install liburing, hence 
yielding a broken /usr/sbin/mysqld binary because the library is missing, and 
the reason why I still have a consistent system on my buildhost is because 
samba has it as dependency.

A quick on-the-fly solution is either manually installing liburing and adding 
it to the world profile (@world is required otherwise emerge -c will remove it 
again), or install mariadb by compiling it (not using emerge -k). But all of 
them are somewhat unclean.

A) Is this a problem in the ebuild script of mysql because not taking care of 
this?
b) Is this a problem of mariadb's configure/make script because of implicitly 
using the library without being told so by ebuild?

Alex

[gentoo-user] Re: Move HOMEPAGE, DESCRIPTION, etc. to metadata.xml?

[Alexander Kurakin]

Thanks!
 
Sincerely,
Alexander Kurakin.
 
 

[gentoo-user] Move HOMEPAGE, DESCRIPTION, etc. to metadata.xml?

[Alexander Kurakin]

Good day!
 
Was there an idea to move HOMEPAGE, DESCRIPTION, etc. to metadata.xml?
 
Are the properties common for package, aren’t they?
 
Thanks!
 
Sincerely,
Alexander Kurakin.

[gentoo-user] Cryfs error Crashed Deserialization failed - missing nullbyte for string termination

[Alexander Puchmayr]

Hi there,

I just encountered a weird problem when trying to access my kde-plasma vault. 
Although I entered the correct password, it refused to open. Journalctl shows

Nov 01 18:41:50 zeus kded5[1348]: OUT:  "CryFS Version 0.10.3\n\nPassword: 
\nDeriving encryption key (this can take some time)...done\n"
Nov 01 18:41:50 zeus kded5[1348]: ERR:  "[2022-11-01 18:41:50.894] [Log] 
[error] Crashed: Deserialization failed - missing nullbyte for string 
termination\n"

Using cryfs on the command line shows the same thing:

alex@zeus ~ $ cryfs .local/share/plasma-vault/Privat.enc Vaults/Privat/
CryFS Version 0.10.3

Password: 
Deriving encryption key (this can take some time)...done
[2022-11-01 18:49:24.052] [Log] [error] Crashed: Deserialization failed - 
missing nullbyte for string termination

Googling this error shows exactly 3 (!) matches, the most useful is assuming a 
corruption on the file system; so I compared with backup, even more than 
several months ago. No changes, the files are identical and the backup is OK.

Next, I copied the encrypted files from .local/share/plasma-vault to an ubuntu 
installation (kubuntu-2020-04LTS which uses cryfs 0.10.2 instead of 0.10.3 
that gentoo uses) , and there the container opened fine. 

It looks like as if gentoo's cryfs 0.10.3-r1 cannot open the container, 
ubuntu's 0.10.2 can. What's wrong with the gentoo version? Any ideas? 

Thanks in advance

[gentoo-user] Layman adding git over ssh only repository

[Alexander Puchmayr]

Hi there,

I tried to add a repository which is only reachable via git over ssh; no 
access via git port (9418 according to /etc/services) or http(s). Only ssh 
connections with public key are accepted.

I tried 
Layman -o ssh://git@myserver/path/to/repo.git -f -a myrepo, but failed with 
"invalid url".
Then I tried the same with "git://git@..." , also failed.

It seems like it does not accept the url scheme and refusing to connect at 
all. Next thing I tried is to create a repository.xml and put it to the local 
file system:




  
my-repo
My overlay

  alexander.puchmayr#my-email.com
  Alexander Puchmayr>

  
git://myserver/path/to/repo.git


Layman -o repository.xml -f -a myrepo now tries to fetch it via the git port 
(9418), failing with timeout.

Replacing source type="git" with "ssh", "ssh+git", "git+ssh" also did not 
succeed. 

I'm pretty sure not being the first one trying this, but I cannot find any 
useful information how to do this. So how can I achieve this?

Thanks
Alex

Re: [gentoo-user] Selective news?

[Alexander Puchmayr]

Am Dienstag, 2. August 2022, 01:04:56 CEST schrieb Ramon Fischer:
> Take a look in "/etc/pulse/client.conf".
> 
> You can either set "autospawn = yes" or comment it.
> 
That did it. For some reason, after the update it was set to no.

Thanks
   Alex

Re: [gentoo-user] Selective news?

[Alexander Puchmayr]

Same here, pulseaudio daemon is no longer started automatically. Starting it 
from a shell (simply call pulseaudio ) and audio works fine again.

Not sure which start script to add it to; .login or .profile are unsuitable 
because it would then start it at every login even with ssh). 

Alex

Am Sonntag, 31. Juli 2022, 00:12:49 CEST schrieb Peter Humphrey:
> On Saturday, 30 July 2022 15:36:35 BST Rich Freeman wrote:
> > From:
> > https://gitweb.gentoo.org/data/gentoo-news.git/tree/2022-07-29-pipewire-so
> > un d-server/2022-07-29-pipewire-sound-server.en.txt
> > 
> > Display-If-Installed: media-video/pipewire
> > Display-If-Installed: media-sound/pulseaudio
> > Display-If-Installed: media-sound/pulseaudio-daemon
> > Display-If-Installed: media-libs/libpulse
> > 
> > If you have any of those packages installed, the news will display.
> 
> But pulseaudio is installed, having been pulled in by plasma-meta; that's
> why I was puzzled.
> 
> $ eix -Ic pulse
> [I] media-libs/libpulse (16.1{xpak:2}@30/06/22): Libraries for PulseAudio
> clients
> [I] media-sound/pulseaudio (16.1{xpak}@10/07/22): A meta package for
> PulseAudio (networked sound server)
> [I] media-sound/pulseaudio-daemon (16.1{xpak:2}@30/06/22): Daemon component
> of PulseAudio (networked sound server)
> Found 3 matches
> 
> The only pertinent difference between the machines is that one is amd64, the
> other ~amd64. Well, the ~amd64 box has no sound hardware, but apart from
> that...
> 
> > We try to filter news so that users aren't bombarded by things that
> > aren't relevant to them.
> 
> And it has worked well for me too until now.
> 
> > For example, a few weeks ago there was apparently a corruption in the mu
> > MUA (which I'd never heard of), which would be really important to know
> > about if you were one of the 0.001% of Gentoo users who rely on it.
> 
> Yes, I saw that, and no, I hadn't heard of it either.

Re: [gentoo-user] Would a Thinkpad X200 be too much trouble too run gentoo on?

[Alexander Puchmayr]

Am Donnerstag, 21. April 2022, 14:49:24 CEST schrieb Dex Conner:
> Hi everyone,
> 
> So I've found a Thinkpad X200 online and I'm thinking of buying it for
> libreboot purposes. Do you think the P8600 cpu can handle all the
> compiling on gentoo? For the record, I don't have any of the "big stuff"
> like KDE, GNOME, Firefox (all I have is Tor Browser [which I don't
> compile], dwl and some terminal programs like neomutt and profanity).
> Surely, I wouldn't be spending 5 hours to do small upgrades,
> right?..right?
> 

Do you have some more powerful machine in the background? If yes, you can 
either create binary packages on this machine and only install them on your 
laptop, or use distcc for moving the big compilation tasks to this other 
machine. 
Using binary packages, I can still use a Lenovo SL510, which seems to have 
similar properties regarding CPU and RAM than the X200, with all desktop 
programs, including full KDE/plasma, Firefox, libreoffice, etc. 

Alex

Re: [gentoo-user] "sys-libs/glibc[crypt(+)]" is soft blocking sys-libs/libxcrypt

[Alexander Puchmayr]

Am Sonntag, 3. April 2022, 10:23:25 CEST schrieb n952162:
> My emerge fails due to a collision with xorg-server and glibc. How can I
> find out where the problem is, actually?
> 
> Output attached.

Did you have a look at 
https://www.gentoo.org/support/news-items/2021-10-18-libxcrypt-migration-stable.html

Alex

Re: [gentoo-user] systemd DNS does not resolve 'local' addresses

[Alexander Puchmayr]

Thanks for the hint with mDNS, I wasn't aware of that. I'm using the '.local' 
domain for all my machines for more than 15 years now, longer than mDNS 
exists, but finally, after some research I found the problem, and actually it 
wasn't systemd per se, it was an update of /etc/nsswitch.conf. The old version 
had 

Hosts:  mymachines files myhostname dns

while the new version contains

Hosts:  mymachines resolve [!UNAVAIL=return] files myhostname dns

The extra "resolve [!UNAVAIL=return]" makes the difference. It loads the 
glibc's plugin nss-resolve [1], which then calls systemd-resolved [2], which 
interprets '.local' as mDNS address. The mDNS is not activated on purpose, it 
seems to be some default setting of the router which does not appear in the 
configuration pages (or I didn't find it).

Anyway, there are some ways to solve this:
1) create an entry in /etc/hosts on every machine. Contradicts the idea of 
DNS, but works
2) keep the old setting in nsswich.conf (without "resolve ...")
3) change my "own" TLD from .local to something else, like .home, as suggested 
in [3]

I think as long term strategy option 3 would be the best.

Regards
Alex

[1] https://www.freedesktop.org/software/systemd/man/nss-resolve.html
[2] https://www.freedesktop.org/software/systemd/man/systemd-resolved.html#
[3] https://www.rfc-editor.org/rfc/rfc6762#appendix-G



Am Samstag, 2. April 2022, 23:48:06 CEST schrieb Rich Freeman:
> On Sat, Apr 2, 2022 at 5:22 PM Alexander Puchmayr
> 
>  wrote:
> > ## portage.local maps to 192.168.1.6
> > ## DNS-Server provided via DHCP is 192.168.1.1 (openwrt-router)
> > 
> > buildhost-desktop ~ # ping portage.local
> > ping: portage.local: Temporary failure in name resolution
> > 
> >Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
> 
> So, I haven't really used resolved much, but I see you have mDNS
> enabled.  Does the portage.local host broadcast itself using mDNS?  If
> it is running Gentoo then the answer is no unless you have it running
> avahi, which is usually not installed by default.  Many
> desktop-oriented linux distros provide avahi by default.
> 
> A resolver that supports mDNS will not use DNS to resolve the .local
> TLD, in accordance with RFC 6762.
> 
> If you intend to use .local for DNS and not mDNS then you probably do
> not want mDNS enabled.  You can either disable it for resolved
> globally by setting MulticastDNS=no in the [Resolve] section of
> /etc/systemd/resolved.conf, or by disabling it for a specific network
> in your network manager (the setting has the same name for
> systemd-networkd).
> 
> This is one of those reasons why it is best to not use the .local TLD
> for DNS on your home network.  You can disable it on systemd-resolved,
> but some IoT device in your home might have it permanently enabled.
> It allows a form of name resolution to work without any DNS server as
> devices discover and broadcast on their own.

[gentoo-user] systemd DNS does not resolve 'local' addresses

[Alexander Puchmayr]

Hi,

After upgrading systemd from 249.9 to 249.11, some of my host names defined in 
my router's host file do no longer resolve, but nslookup can still resolve 
them properly. With 249.9 everything works fine, and all other machines which 
did not yet get the update work fine.

Any ideas?

Thanks,
  Alex

## portage.local maps to 192.168.1.6
## DNS-Server provided via DHCP is 192.168.1.1 (openwrt-router)

buildhost-desktop ~ # ping portage
ping: portage: Name or service not known

buildhost-desktop ~ # ping portage.local
ping: portage.local: Temporary failure in name resolution

buildhost-desktop ~ # host portage
portage has address 192.168.1.6

buildhost-desktop ~ # nslookup portage
Server: 192.168.1.1
Address:192.168.1.1#53

Name:   portage
Address: 192.168.1.6

buildhost-desktop ~ # dig portage
; <<>> DiG 9.16.27 <<>> portage
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40446
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;portage.   IN  A

;; ANSWER SECTION:
portage.0   IN  A   192.168.1.6

;; Query time: 3 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Sat Apr 02 22:49:50 CEST 2022
;; MSG SIZE  rcvd: 52

buildhost-desktop ~ # resolvectl 
Global
   Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: uplink
Fallback DNS Servers: 1.1.1.1#cloudflare-dns.com 8.8.8.8#dns.google
  1.0.0.1#cloudflare-dns.com 8.8.4.4#dns.google
  2606:4700:4700::#cloudflare-dns.com
  2001:4860:4860::#dns.google
  2606:4700:4700::1001#cloudflare-dns.com
  2001:4860:4860::8844#dns.google

Link 2 (enp3s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
 Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/
unsupported
Current DNS Server: 192.168.1.1
   DNS Servers: 192.168.1.1
buildhost-desktop ~ #

Re: [gentoo-user] Emerge -u -k package install order - broken system [SOLVED]

[Alexander Puchmayr]

Am Montag, 6. September 2021, 16:33:32 CEST schrieb Alexander Puchmayr:
> Hi there,
> 
> I just tried to upgrade a older installation via binary packages and this
> broke my system. After around 25 packages of almost 300 it stopped with
> error and failing packages.
> 
> $ emerge
> Failed to validate a sane '/dev'.
> bash process substitution doesn't work; this may be an indication of a
> broken '/dev/fd'.
> $ ls -l /dev/fd/
> insgesamt 0
> lrwx-- 1 root root 64  6. Sep 14:18 0 -> /dev/pts/0
> lrwx-- 1 root root 64  6. Sep 14:18 1 -> /dev/pts/0
> lrwx-- 1 root root 64  6. Sep 14:18 2 -> /dev/pts/0
> lr-x-- 1 root root 64  6. Sep 14:18 3 -> /proc/27261/fd
> 
> --> looks allright, but:
> 
> $ bash
> bash: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by /lib64/
> libreadline.so.8)
> 
> --> system broken(!), cannot start any shell anymore, cannot install
> anything anymore and it's obvious that the system is bricked after reboot
> or even when the ssh session I'm logged in is closed.
> 
> It seems like as if sys-libs/readline-8.1_p1-r1-1:0/8::gentoo is installed
> *before* installing a suitable glibc, breaking any binary that has the
> useflag readline (including bash).
> 
> Two questions:
> How do I get out of this mess?
> Why does portage not work in correct package order? Portage bug?

The problem was caused by a newly compiled sys-libs/readline as binary 
package. The package itself was compiled on my buildhost by a emerge -auvDN 
world, and when readline was compiled, the latest glibc-2.33 was already 
installed on the buildhost, hence the readline packet had a (implicit) 
dependency to >=glibc-33. Portage does not seem to be aware of that (the glibc 
version is not a dependency of readline), so portage did not care and install 
it at some suitable position later. From the time on that readline was emerged 
from that binary package, all programs linked with it have now that implicit 
dependency of >=glibc-2.33, which is not yet installed (which was 2.28). Bang!

HOW TO FIX THIS BREAKAGE:

For the system recovery I was lucky to have a backup of the old packages, so I 
could extract the readline-tbz2-package file to the temporary directly and copy 
the so files to /usr/local/lib64 (I chose /usr/local/ to avoid overwriting the 
package files) 

Ls -l /usr/local/lib64/
insgesamt 368
lrwxrwxrwx 1 root root 15  6. Sep 14:53 libhistory.so -> libhistory.so.8
lrwxrwxrwx 1 root root 17  6. Sep 15:04 libhistory.so.8 -> libhistory.so.
8.0
-rwxr-xr-x 1 root root  47368  6. Sep 14:53 libhistory.so.8.0
lrwxrwxrwx 1 root root 16  6. Sep 14:53 libreadline.so -> libreadline.so.8
lrwxrwxrwx 1 root root 18  6. Sep 15:04 libreadline.so.8 -> 
libreadline.so.8.0
-rwxr-xr-x 1 root root 325464  6. Sep 14:53 libreadline.so.8.0

Then, I created a ld.so.conf config file to ensure that /usr/local/lib is at 
*first* place:

echo "/usr/local/lib64" >/etc/ld.so.conf.d/10-temporary-fix.conf 
ldconfig

Notes: 
* The config file *must* end with .conf
* Although /usr/local/lib64 is already in the ld.so.conf file, this step is 
necessary to get it at first place; otherwise it is after /lib64 and /usr/
lib64, and ld.so finds the non-working version first
* setting LD_LIBRARY_PATH does not work as ebuild does not forward the 
environment variables from the calling process.

Test it with ldd /usr/bin/bash -- no errors shall be reported, and the 
readline library shall show the /usr/local/lib64 path.

Now, I could emerge glibc-2.33 the usual way (emerge -avk1 glibc), and then 
afterwards remove the temporary ld.so.conf file

rm /etc/ld.so.conf.d/10-temporary-fix.conf 
ldconfig

Test again with  ldd /usr/bin/bash -- the new readline library from /usr/lib64 
and /lib64 shall now be used. 
Now, the libraries from /usr/local/lib can be removed safely.

System recovered!

Best regards,
 Alex

Re: [gentoo-user] Emerge -u -k package install order - broken system

[Alexander Puchmayr]

Am Montag, 6. September 2021, 19:38:38 CEST schrieb Jack:
> On 2021.09.06 10:33, Alexander Puchmayr wrote:
> > Hi there,
> > 
> > I just tried to upgrade a older installation via binary packages and
> > this
> > broke my system. After around 25 packages of almost 300 it stopped
> > with error
> > and failing packages.
> > 
> > $ emerge
> > Failed to validate a sane '/dev'.
> > bash process substitution doesn't work; this may be an indication of
> > a broken
> > '/dev/fd'.
> > $ ls -l /dev/fd/
> > insgesamt 0
> > lrwx-- 1 root root 64  6. Sep 14:18 0 -> /dev/pts/0
> > lrwx-- 1 root root 64  6. Sep 14:18 1 -> /dev/pts/0
> > lrwx-- 1 root root 64  6. Sep 14:18 2 -> /dev/pts/0
> > lr-x-- 1 root root 64  6. Sep 14:18 3 -> /proc/27261/fd
> > 
> > --> looks allright, but:
> > 
> > $ bash
> > bash: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by
> > /lib64/
> > libreadline.so.8)
> > 
> > --> system broken(!), cannot start any shell anymore, cannot install
> > anything
> > anymore and it's obvious that the system is bricked after reboot or
> > even when
> > the ssh session I'm logged in is closed.
> > 
> > It seems like as if sys-libs/readline-8.1_p1-r1-1:0/8::gentoo is
> > installed
> > *before* installing a suitable glibc, breaking any binary that has
> > the useflag
> > readline (including bash).
> > 
> > Two questions:
> > How do I get out of this mess?
> > Why does portage not work in correct package order? Portage bug?
> 
> It might help if you stated which version of packages you currently
> have installed - specifically glibc.
> 
> As for recovery, you most likely need to boot to a live image (CD or
> USB) then chroot into the existing system.  I'm only guessing as to
> what is the minimal list of files you will need to replace, but I'd see
> if you can find or create a binary package of the latest glibc and then
> install or unpack that to your system.
> 
> As to whether this might be a bug in portage, I'd say you need to
> provide more details about exactly what you did.  What emerge line,
> what you mean by installation via binary packages, and where you got
> those binary packages.
> 
> If you do still have a running shell, does emerge still run at all?

What I did is:
* On my build host, I compiled the full system and creating packages
* On the client (i.e. The machine in question) I simply did a emerge -auvDNk 
world.
* Portage did not complain about any conflicts, the amount of packages is what 
I expected, so I started the upgrade.
* After about 25 packages installed successfully, emerge stopped with the 
errors explained before.

For me the problem is solved now as I could recover the system, but I still 
would like to know how to prevent this -- installing glibc prior world may be 
a good idea.

Thanks,
  Alex

[gentoo-user] Emerge -u -k package install order - broken system

[Alexander Puchmayr]

Hi there,

I just tried to upgrade a older installation via binary packages and this 
broke my system. After around 25 packages of almost 300 it stopped with error 
and failing packages.

$ emerge
Failed to validate a sane '/dev'.
bash process substitution doesn't work; this may be an indication of a broken 
'/dev/fd'.
$ ls -l /dev/fd/
insgesamt 0
lrwx-- 1 root root 64  6. Sep 14:18 0 -> /dev/pts/0
lrwx-- 1 root root 64  6. Sep 14:18 1 -> /dev/pts/0
lrwx-- 1 root root 64  6. Sep 14:18 2 -> /dev/pts/0
lr-x-- 1 root root 64  6. Sep 14:18 3 -> /proc/27261/fd

--> looks allright, but:

$ bash
bash: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by /lib64/
libreadline.so.8)

--> system broken(!), cannot start any shell anymore, cannot install anything 
anymore and it's obvious that the system is bricked after reboot or even when 
the ssh session I'm logged in is closed.

It seems like as if sys-libs/readline-8.1_p1-r1-1:0/8::gentoo is installed 
*before* installing a suitable glibc, breaking any binary that has the useflag 
readline (including bash).

Two questions:
How do I get out of this mess? 
Why does portage not work in correct package order? Portage bug?

Re: [gentoo-user] Laptop internal speakers no longer working after recent updates

[Alexander Puchmayr]

Am Dienstag, 31. August 2021, 19:24:15 CEST schrieb Michael:
> On Tuesday, 31 August 2021 12:08:04 BST Alexander Puchmayr wrote:
> > Am Dienstag, 31. August 2021, 00:18:43 CEST schrieb Michael:
> > > If the alsa drivers are not compiled as modules, the above file would
> > > not
> > > have any effect.  Anyway, let's try this in /etc/asound.conf:
> > > 
> > > defaults.pcm.card 1
> > > defaults.pcm.device 0
> > > defaults.ctl.card 1
> > > 
> > > On a reboot your Generic_1 analogue card should be available and
> > > recognised
> > > as the default audio device.  You may need to unmute it, via pactl or
> > > kmix.
> > 
> > Sorry, didn't change anything.
> > 
> > I doubt that the problem is wrong default settings of alsa.
> > 
> > I run pulseaudio -vvv and the output was interesting:
> > 
> > Pci:00/:00:08.1/:07:00.1/sound/card0
> > and
> > pci:00/:00:08.1/:07:00.6/sound/card1
> > 
> > Where the latter one is the one that is not used by pulseaudio.
> > 
> > Both report  "UCM available for card HD-Audio Generic"
> > Note: the card name "HD-Audio Generic" is identical, and this is reported
> > by alsa-libs, as far as I could see from the code.
> 
> Your *card* names according to your 'aplay -l' output are/were:
> 
> card 0: Generic
> card 1: Generic_1
> card 3: Headset
> 
> You can re-check this with:
> 
> aplay -l | awk -F \: '/,/{print $2}' | awk '{print $1}' | uniq
> 
> 
> Another way to discover all card name(s) including unused cards is by the
> output of:
> 
> cat /sys/class/sound/card*/id
> 
> The alsa-ucm function involves creating use case alsa mixer profiles,
> similar to pulseaudio profiles and will work even without pulseaudio
> running.   If a UCM configuration file exists for a card, then pulseaudio
> will ignore built-in profiles and will generate a profile based on the UCM
> config file.
> 
> Take a look at:
> 
> /usr/share/alsa/ucm2/README.md
> 
> and for various mixer profiles look under /usr/share/alsa/ucm2/
> 
> However, my usage of pulseaudio  has been cursory and don't know much about
> its auto-configuration.  In any case, I suspect the alsa-ucm output is only
> relevant in highlighting the common codec name, as you confirm below.
> 
> > [...]
> > 
> > Alsa-info.sh reveals further info:
> > !!Soundcards recognised by ALSA
> > !!-
> > 
> >  0 [Generic]: HDA-Intel - HD-Audio Generic
> >  
> >   HD-Audio Generic at 0xfd3c8000 irq 91
> >  
> >  1 [Generic_1  ]: HDA-Intel - HD-Audio Generic
> >  
> >   HD-Audio Generic at 0xfd3c irq 92
> >  
> >  2 [acp]: acp - acp
> >  
> >   acp
> > 
> > To me it looks like as if pulseaudio is quering card0, getting the name
> > "HD- Audio Generic", finding the HDMI channels; then it tries to read
> > card1, gets also "HD-Audio Generic" as name and hence the same channels
> > as for card0.
> > 
> > I have no idea how to fix this.
> > 
> > Cheers
> > 
> > Alex
> 
> As I understand it, "HD-Audio" is the kernel driver (CONFIG_SND_HDA=m) and
> "Generic" is the generic codec parser (CONFIG_SND_HDA_GENERIC=m) used by the
> snd-hda-intel module (CONFIG_SND_HDA_INTEL=m) - unless a specific model
> codec is (also) configured for a card, e.g. in my case I have
> CONFIG_SND_HDA_CODEC_CONEXANT=m
> 
> If in your recent system update/upgrade you did not change your kernel, or
> the available options of any audio modules under /etc/modprobe.d/ then the
> drivers were always configured so and therefore the problem you experience
> now is unlikely to be caused by the generic codec parser.
> 
> Someone more knowledgeable in pulseaudio should chime in, assuming this
> problem is being caused by pulseaudio.  :-/

I just downgraded to alsa-utils and alsa-tools 1.2.3, and the problem 
disappeared. I will keep this combination for a while until the next update.

However, I'm not sure whether this is an alsa problem or a pulseaudio problem.

Thanks for your help
   Alex

Re: [gentoo-user] Laptop internal speakers no longer working after recent updates

[Alexander Puchmayr]

Am Dienstag, 31. August 2021, 00:18:43 CEST schrieb Michael:
 
> If the alsa drivers are not compiled as modules, the above file would not
> have any effect.  Anyway, let's try this in /etc/asound.conf:
> 
> defaults.pcm.card 1
> defaults.pcm.device 0
> defaults.ctl.card 1
> 
> On a reboot your Generic_1 analogue card should be available and recognised
> as the default audio device.  You may need to unmute it, via pactl or kmix.

Sorry, didn't change anything. 

I doubt that the problem is wrong default settings of alsa. 

I run pulseaudio -vvv and the output was interesting:

Pci:00/:00:08.1/:07:00.1/sound/card0
and 
pci:00/:00:08.1/:07:00.6/sound/card1 

Where the latter one is the one that is not used by pulseaudio.

Both report  "UCM available for card HD-Audio Generic"
Note: the card name "HD-Audio Generic" is identical, and this is reported by 
alsa-libs, as far as I could see from the code.

Then it finds HDMI1-3 for both cards.

*** card0 *** 
[...]
D: [pulseaudio] module-udev-detect.c: /devices/
pci:00/:00:08.1/:07:00.1/sound/card0 is busy: no
D: [pulseaudio] module-udev-detect.c: Loading module-alsa-card with arguments 
'device_id="0" name="pci-_07_00.1" card_name="alsa_card.pci-_07_00.1" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-
udev-detect.discovered=1"'
D: [pulseaudio] reserve-wrap.c: Unable to contact D-Bus session bus: 
org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon 
without a $DISPLAY for X11
I: [pulseaudio] alsa-ucm.c: UCM available for card HD-Audio Generic
I: [pulseaudio] alsa-ucm.c: Set UCM verb to HiFi
D: [pulseaudio] alsa-ucm.c: Got TQ for verb HiFi: HiFi
D: [pulseaudio] alsa-ucm.c: Got PlaybackPCM for device HDMI3: hw:Generic,8
D: [pulseaudio] alsa-ucm.c: Got PlaybackPriority for device HDMI3: 1300
D: [pulseaudio] alsa-ucm.c: Got JackControl for device HDMI3: HDMI/DP,pcm=8 
Jack
W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 
'CaptureChannels'for device HDMI3, assuming stereo duplex.
D: [pulseaudio] alsa-ucm.c: No _conflictingdevs for device HDMI3
D: [pulseaudio] alsa-ucm.c: No _supporteddevs for device HDMI3
D: [pulseaudio] alsa-ucm.c: Got PlaybackPCM for device HDMI2: hw:Generic,7
D: [pulseaudio] alsa-ucm.c: Got PlaybackPriority for device HDMI2: 1200
D: [pulseaudio] alsa-ucm.c: Got JackControl for device HDMI2: HDMI/DP,pcm=7 
Jack
W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 
'CaptureChannels'for device HDMI2, assuming stereo duplex.
D: [pulseaudio] alsa-ucm.c: No _conflictingdevs for device HDMI2
D: [pulseaudio] alsa-ucm.c: No _supporteddevs for device HDMI2
D: [pulseaudio] alsa-ucm.c: Got PlaybackPCM for device HDMI1: hw:Generic,3
D: [pulseaudio] alsa-ucm.c: Got PlaybackPriority for device HDMI1: 1100
D: [pulseaudio] alsa-ucm.c: Got JackControl for device HDMI1: HDMI/DP,pcm=3 
Jack
W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 
'CaptureChannels'for device HDMI1, assuming stereo duplex.
D: [pulseaudio] alsa-ucm.c: No _conflictingdevs for device HDMI1
D: [pulseaudio] alsa-ucm.c: No _supporteddevs for device HDMI1
[...]

*** card1 *** (the one that is ignored by pulseaudio)
[...]
D: [pulseaudio] module-udev-detect.c: /devices/
pci:00/:00:08.1/:07:00.6/sound/card1 is busy: no
D: [pulseaudio] module-udev-detect.c: Loading module-alsa-card with arguments 
'device_id="1" name="pci-_07_00.6" card_name="alsa_card.pci-_07_00.6" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-
udev-detect.discovered=1"'
D: [pulseaudio] reserve-wrap.c: Unable to contact D-Bus session bus: 
org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon 
without a $DISPLAY for X11
I: [pulseaudio] alsa-ucm.c: UCM available for card HD-Audio Generic
I: [pulseaudio] alsa-ucm.c: Set UCM verb to HiFi
D: [pulseaudio] alsa-ucm.c: Got TQ for verb HiFi: HiFi
D: [pulseaudio] alsa-ucm.c: Got PlaybackPCM for device HDMI3: hw:Generic,8
D: [pulseaudio] alsa-ucm.c: Got PlaybackPriority for device HDMI3: 1300
D: [pulseaudio] alsa-ucm.c: Got JackControl for device HDMI3: HDMI/DP,pcm=8 
Jack
W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 
'CaptureChannels'for device HDMI3, assuming stereo duplex.
D: [pulseaudio] alsa-ucm.c: No _conflictingdevs for device HDMI3
D: [pulseaudio] alsa-ucm.c: No _supporteddevs for device HDMI3
D: [pulseaudio] alsa-ucm.c: Got PlaybackPCM for device HDMI2: hw:Generic,7
D: [pulseaudio] alsa-ucm.c: Got PlaybackPriority for device HDMI2: 1200
D: [pulseaudio] alsa-ucm.c: Got JackControl for device HDMI2: HDMI/DP,pcm=7 
Jack
W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 
'CaptureChannels'for device HDMI2, assuming stereo duplex.
D: [pulseaudio] 

Re: [gentoo-user] Laptop internal speakers no longer working after recent updates

[Alexander Puchmayr]

Am Montag, 30. August 2021, 13:30:03 CEST schrieb Michael:
> On Monday, 30 August 2021 11:30:38 BST Alexander Puchmayr wrote:
> > Hi there,
> > 
> > I have a weird problem on my Lenovo P14s laptop. Before I applied a world
> > upgrade (based on August 22 state portage), the internal speaker of the
> > laptop worked fine, but now its all silent, although all mixer levels are
> > 100% and no channel is muted.
> 
> There was a recent move to pipewire which could have jumbled audio devices
> around for you - but I am not familiar with how pipewire works, or why it
> would have caused this problem.
> 
> https://wiki.gentoo.org/wiki/PipeWire
> 

I did not install pipewire, so we can exclude this.

[snip...]

> $ aplay -l
>  List of PLAYBACK Hardware Devices 
> card 0: HDMI [HDA ATI HDMI], device 3: Generic Digital [Generic Digital]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 1: Generic [HD-Audio Generic], device 0: CX20757 Analog [CX20757
> Analog] Subdevices: 1/1
>   Subdevice #0: subdevice #0
> 

Here is output of aplay -l:
 List of PLAYBACK Hardware Devices 
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [HDMI 1]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 8: HDMI 2 [HDMI 2]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 0: ALC257 Analog [ALC257 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: Headset [Logitech USB Headset], device 0: USB Audio [USB Audio]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

I added an old USB headset for testing, and *this* card (card 3) is shown in 
pavcontrol and kde-plasma audio settings, along with the three sub-devices of 
card 0; however, card 1 is not shown. In alsamixer and aplay I can see the 
device as "Generic_1", and -- after finding out the pcm name of it via aplay -L 
-- I could play some wav file with  aplay on it:

aplay -D front:CARD=Generic_1,DEV=0 some_wav_file.wav

It seems to be a pulseaudio problem, which seems to arbitrarily ignoring 
Generic_1 card.

> Alternatively, take a look at this method of controlling the order in which 
> audio modules are loaded:
> https://wiki.gentoo.org/wiki/ALSA#Laptops_with_HDMI_audio_output

Thanks for the link, brought me to inspect /etc/modprobe.d/alsa.conf. 
Corrected the number of sound cards there, but did not help :-( 
I remember to have edited this file about 10 years ago, not sure if those 
settings are still relevant.

Cheers, Alex

[gentoo-user] Laptop internal speakers no longer working after recent updates

[Alexander Puchmayr]

Hi there,

I have a weird problem on my Lenovo P14s laptop. Before I applied a world 
upgrade (based on August 22 state portage), the internal speaker of the laptop 
worked fine, but now its all silent, although all mixer levels are 100% and no 
channel is muted. 

Observed facts:
* Connecting a HDMI tv-set produces sound over the tv-set properly
* Booting Win10: Internal speakers working fine --> no hw issue
* Connecting headphone via audio jack under linux - no sound.
* Reverting to backup makes sound work again --> config/sw problem introduced 
by update
* In plasma's system settings/audio tray, the Speaker output device is not 
shown -- only 3xHDMI (The analog speaker seems to have gone)

The kernel is exactly the same as before the upgrade, didn't recompile it 
(sys-kernel/gentoo-sources-5.12.0) --> no kernel issue

Relevant packet changes:
sys-kernel/linux-firmware-20210511 -> sys-kernel/linux-firmware-20210716
dev-python/pyalsa-1.1.6-r1 = dev-python/pyalsa-1.1.6-r1
Media-libs/alsa-lib-1.2.3.2-r1 -> media-libs/alsa-lib-1.2.4
Media-libs/alsa-topology-conf-1.2.3 -> media-libs/alsa-topology-conf-1.2.4
Media-libs/alsa-ucm-conf-1.2.3 -> media-libs/alsa-ucm-conf-1.2.4
Media-plugins/alsa-plugins-1.2.2 = media-plugins/alsa-plugins-1.2.2
Media-sound/alsa-tools-1.2.2-r1 = media-sound/alsa-tools-1.2.2-r1
Media-sound/alsa-utils-1.2.3 -> media-sound/alsa-utils-1.2.4
Media-libs/pulseaudio-qt-1.2 = media-libs/pulseaudio-qt-1.2
Media-plugins/gst-plugins-pulse-1.16.3 = media-plugins/gst-plugins-
pulse-1.16.3
Media-sound/pulseaudio-13.0-r1 = media-sound/pulseaudio-13.0-r1
Kde-plasma/plasma-meta-5.20.5 -> 5.21.5 (including all dependencies)


I tried downgrading linux-firmware to the old version from the backup -- did 
not help.
I tried logging in from a completely fresh account to exclude any bad config in 
the local home directory -> no success.

Any further ideas?

Thanks, Alex

PS: lspci shows
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host 
Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host 
Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host 
Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe 
GPP Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 
51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: 
Function 7
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM981/PM981/PM983
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 0e)
02:00.1 Serial controller: Realtek Semiconductor Co., Ltd. Device 816a (rev 
0e)
02:00.2 Serial controller: Realtek Semiconductor Co., Ltd. Device 816b (rev 
0e)
02:00.3 IPMI Interface: Realtek Semiconductor Co., Ltd. Device 816c (rev 0e)
02:00.4 USB controller: Realtek Semiconductor Co., Ltd. Device 816d (rev 0e)
03:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI 
Express Card Reader (rev 01)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 15)
06:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host 
Controller (rev 02)
07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Renoir (rev d1)
07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637
07:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) Platform Security Processor
07:00.3 USB controller: Advanced 

[gentoo-user] Emerge --root= headerfiles taken from / or ROOT?

[Alexander Puchmayr]

Hi there,

I'm just trying setup a small target image with the --root (env SYSROOT), -
config-root and --sysroot options, and some builds fail, because the header 
files as well as cmake include files are not taken from the path specified to 
root/sysroot, but from /.

How can I make emerge/ebuild take the headers from the target path?

The goal is to have a target image, which contains only minimum set of 
packages and also a minimum set of use flags, just to get it booting and 
fulfill 
its purpose. The use flags and the package set are different from the host 
build 
system. The architecture is the same, so I'm not cross compiling.

Thanks
Alex

Re: [gentoo-user] Weird harddisk problem: AHCI disks sometimes not found

[Alexander Puchmayr]

Hi there,

Thanks for all suggestions and answers so far.

I'm pretty sure it is not a hardware problem, because 
* Exchanging SATA cables does not affect the problem
* Using different SATA slots on the mainboard does not affect the problem
* Using different SATA power connectors does not affect the problem

I continued to experiment with different kernel versions and configs:
* Ubuntu-5.4.0-48-generic works
* sys-kernel/gentoo-sources-5.4.60 [self compiled and configured for a similar 
machine some time ago]: WORKS
* sys-kernel/gentoo-kernel-5.4.97 [default config] FAILS
* sys-kernel/gentoo-kernel-bin-5.4.97 FAILS
* sys-kernel/vanilla-sources-5.4.102 [same config as with 5.4.60] WORKS
* sys-kernel/gentoo-kernel-5.10.20 [default config] FAILS
* sys-kernel/gentoo-sources-5.10.20 [same config as with 5.4.60] WORKS

The common thing seems to be that my self-configured kernels work and the 
default dist-kernels fail. I checked the differences in the configs (/usr/src/
linux/.config) related to SATA or AHCI, and one candidate was 
CONFIG_SATA_MOBILE_LPM_POLICY, which was set to 3 (medium power save) in 
distkernel's config and 0 (keep seetings from firmware) in my self compiled 
kernels.

SOLUTION:
Adding CONFIG_SATA_MOBILE_LPM_POLICY=0 to /etc/kernel/config.d and recompiling 
the gentoo-kernel actually solved the problem. 

I assume the reason is an incompatibility between the link power modes (mode 
3) and the drives making the link to appear to be down.

Alex

Am Donnerstag, 11. März 2021, 20:39:04 CET schrieb Alexander Puchmayr:
> Hi there,
> 
> I have a weird harddisk detection problem which rises the questio: what does
> the gentoo-kernel make differently than the ubuntu kernel?
> 
> The system in question has 2 identical SSDs (Kingston SV300S3 60GB) and two
> identical HDDs (older Maxtor7V300F0 300GB) , all connected to SATA/AHCI
> ports; the HDDs are combined to a LVM-raid1 volume. SATA controller is a
> onboard SB7x on an Asus M3A78 mainboard in AHCI mode.
> 
> Only one of the two SSDs is attached at the same time to the system, the
> other one is disconnected. One contains a gentoo installation (just updated
> yesterday), the other one an Ubuntu LTS 20.04. This allows dual-.boot by
> switching connection cables.
> 
> When I connect the gentoo-SSD and boot it, BIOS finds all HDDs and the SSD,
> and starts booting; but gentoo does not recognize at least one of the HDDs
> (/dev/ sdc missing, dmesg shows link down on Sata-Interface
> . Going back to the bios shows that even BIOS does not recognize the disk
> anymore. A full powercycle (pressing reset button is not sufficent) to make
> BIOS to recognize the disks again.
> 
> Doing the same with the Ubuntu-Disk works absolutely fine, all HDDs are
> recognized and the raid is working fine, not a single time that one of the
> disks was not recognized.
> 
> Without the Ubuntu observation I'd say its a hardware problem and the old
> HDDs are simply beyond their age, but why are they working in ubuntu and
> not in gentoo? And what is it doing with BIOS/Harddisk that even Bios does
> not find it anymore? I need a full powercycle to make bios find it again.
> This  indicates a gentoo kernel problem, and I have no idea where to start
> looking, and AFAIK there's nothing much to configure a SATA/AHCI drive.
> 
> Any ideas?
> 
> Thanks
>   Alex
> 
> PS:
> Sys-kernel/gentoo-kernel-5.4.97, default configuration
> Hardware:
> 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge
> 00:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to
> PCI bridge (int gfx)
> 00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI
> bridge (PCIE port 2)
> 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
> SB9x0 SATA Controller [AHCI mode]
> 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
> SB9x0 USB OHCI0 Controller
> 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB
> OHCI1 Controller
> 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
> SB9x0 USB EHCI Controller
> 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
> SB9x0 USB OHCI0 Controller
> 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB
> OHCI1 Controller
> 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
> SB9x0 USB EHCI Controller
> 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller
> (rev 3a)
> 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
> SB9x0 IDE Controller
> 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia
> (Intel HDA)
> 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0
>

[gentoo-user] Weird harddisk problem: AHCI disks sometimes not found

[Alexander Puchmayr]

Hi there,

I have a weird harddisk detection problem which rises the questio: what does 
the gentoo-kernel make differently than the ubuntu kernel?

The system in question has 2 identical SSDs (Kingston SV300S3 60GB) and two 
identical HDDs (older Maxtor7V300F0 300GB) , all connected to SATA/AHCI ports; 
the HDDs are combined to a LVM-raid1 volume. SATA controller is a onboard SB7x 
on an Asus M3A78 mainboard in AHCI mode.

Only one of the two SSDs is attached at the same time to the system, the other 
one is disconnected. One contains a gentoo installation (just updated 
yesterday), the other one an Ubuntu LTS 20.04. This allows dual-.boot by 
switching connection cables.

When I connect the gentoo-SSD and boot it, BIOS finds all HDDs and the SSD, and 
starts booting; but gentoo does not recognize at least one of the HDDs (/dev/
sdc missing, dmesg shows link down on Sata-Interface
. Going back to the bios shows that even BIOS does not recognize the disk 
anymore. A full powercycle (pressing reset button is not sufficent) to make 
BIOS 
to recognize the disks again.

Doing the same with the Ubuntu-Disk works absolutely fine, all HDDs are 
recognized and the raid is working fine, not a single time that one of the 
disks was not recognized.

Without the Ubuntu observation I'd say its a hardware problem and the old HDDs 
are simply beyond their age, but why are they working in ubuntu and not in 
gentoo? And what is it doing with BIOS/Harddisk that even Bios does not find it 
anymore? I need a full powercycle to make bios find it again. This  indicates a 
gentoo kernel problem, and I have no idea where to start looking, and AFAIK 
there's nothing much to configure a SATA/AHCI drive.

Any ideas?

Thanks
Alex

PS:
Sys-kernel/gentoo-kernel-5.4.97, default configuration
Hardware: 
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge
00:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI 
bridge (int gfx)
00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge 
(PCIE port 2)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
SB9x0 SATA Controller [AHCI mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 
Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
SB9x0 USB OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 
Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 3a)
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
SB9x0 IDE Controller
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/
SB9x0 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RS780 [Radeon HD 3200]
01:05.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RS780 HDMI Audio 
[Radeon 3000/3100 / HD 3200/3300]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 02)

Re: [gentoo-user] emerge warnings or errors

[Alexander Openkowski]

https://wiki.gentoo.org/wiki/Elogv

On Fri, Nov 13, 2020 at 12:27 AM Jude DaShiell  wrote:

> About 6 different complaints about my kernel configuration that blew off
> the screen as packages were being emerged.  Does any way exist to have
> emerge write these to a log file of some sort for later checking and
> action?
>
>
>
> -- United States has 633 Billionaires with only 10 doing any annual
> significant giving.
>
>
>

[gentoo-user] Broken binary packages

[Alexander Puchmayr]

Hi there,

I'm using a build host to generate all packages for my different machines in my 
local network; Not every machine gets every package. 

I encountered a problem where a package that looks absolutely fine on the 
buildhost but on the target machine its broken since some libraries are 
missing. NB: I previously did an emerge -e world before on the buildhost.

As an example I'd like to take media-tv/mythtv-31.0-r1, which has a dependency 
to dev-qt/qtwebkit:5 if the xmltv useflag is set:

buildhost-desktop ~ # equery depends dev-qt/qtwebkit-5.212.0_pre20200309-r1
 * These packages depend on dev-qt/qtwebkit-5.212.0_pre20200309-r1:
dev-python/PyQt5-5.14.2 (webkit ? dev-qt/qtwebkit:5[printsupport])
dev-qt/designer-5.14.2 (webkit ? >=dev-qt/qtwebkit-5.9.1:5)
dev-util/kdevelop-5.5.2 (webkit ? >=dev-qt/qtwebkit-5.212.0_pre20180120:5)
kde-apps/k3b-19.12.3 (webkit ? >=dev-qt/qtwebkit-5.212.0_pre20180120:5)
kde-apps/kdenlive-19.12.3-r3 (freesound ? >=dev-qt/
qtwebkit-5.212.0_pre20180120:5)
kde-apps/umbrello-19.12.3 (>=dev-qt/qtwebkit-5.212.0_pre20180120:5)
media-gfx/digikam-6.4.0-r1 (webkit ? >=dev-qt/qtwebkit-5.212.0_pre20180120:5)
media-gfx/wkhtmltopdf-0.12.5 (dev-qt/qtwebkit:5[printsupport])
media-tv/mythtv-31.0-r1 (xmltv ? dev-qt/qtwebkit:5)
net-misc/teamviewer-15.4.4445 (dev-qt/qtwebkit:5)

The Useflag "xmltv" is not set, but since the packages kde-apps/umbrello and  
media-gfx/wkhtmltopdf have a direct dependency to dev-qt/qtwebkit, it is 
installed on the buildhost. 
When building mythtv, it finds the webkit libraries and headers installed and 
uses it, even if the xmltv-useflag is NOT set(!), yielding a binary that has an 
implicit dependency to qtwebkit, but portage does not know of it.

When I install now the mythtv package on my laptop, where none of the other 
packages are installed that require qtwebkit, there's no need for portage to 
install it, and so we get a broken mythtv package. 

I see several ways to solve this, but none is really satisfying:
* set the xmltv use flag to mythtv to get an explict dependency -- I don't want 
it and I don't need it.
* rebuild mythtv on my 12-year old notebook locally -- nothing I'd really like 
to do.
* Install qtwebkit in the world set -- I don't like those library packages in 
the world set
* remove those packages requiring qtwebkit explicity, then rebuild mythtv, 
build package, install on notebook and rebuild/reinstall the removed packages 
on the buildhost again -- too cumbersome and I have the same problem again at 
the next update session. And mythtv is not the only package that may cause 
such problems, so I would have to do this in many different combinations.

Is there a better way to solve this? Is it possible to tell mythtv's build 
system to ignore the unwanted libraries if the xmltv use-flag is NOT set?

Regards
Alex

Re: [gentoo-user] Realtek r8169 realtek.ko not loaded.

[Alexander Puchmayr]

Am Sonntag, 17. Mai 2020, 13:09:44 CEST schrieb Victor Ivanov:
> Hi Alexander,
> 
> A while back I had the exact same issue with a remote machine that I am
> managing. It has an Asus B45-M mobo with an r8169 chipset. Ever since
> the 5.2.x kernel family - where it last used to work - it has been a pain.
> 
> Initially I added a manual "soft" dependency in "/etc/conf.d/modules" as
> William has suggested to you with "realtek" appearing first in the list.
> But this stopped working following an update to 5.4.x and is still the
> case today with the 5.6.x family (I keep testing it once in a while).
> 
> I then decided to build both realtek and r8169 modules into the kernel:
> 
> REALTEK_PHY=y
> CONFIG_R8169=y
> 

This worked, and as I found out in an answer for William's mail, it seems to 
be a problem with genkernel's way to create initrds with embedded busybox. It 
seems as if busybox does not support softdeps.

Regards
Alex






> It did require a bit of faff as the whole chain of dependencies from
> REALTEK_PHY had to be built in as well, but I think that was about 5-6
> kernel options in total.
> 
> Adding it to the ramdisk as William suggests might work too. In my case
> I didn't bother trying this due to the fact that every failed attempted
> required manual intervention by someone to get the machine booted with
> working kernel.
> 
> I have a gut feeling that tells me adding it to the initrd probably
> won't work. But if you're planning on trying it, please keep us posted.
> I would be very interested in hearing your solution.
> 
> Regards,
> V
> 
> On 17/05/2020 09:07, Alexander Puchmayr wrote:
> > Hi there
> > 
> > I just upgraded an older notebook with r8169 network chip to new kernel
> > 5.4
> > (sys-kernel/gentoo-sources-5.4.28) with genkernel.
> > After booting the new kernel the network adapter was not initialized, no
> > network interface eth0.
> > Dmesg says
> > [6.390973] r8169 :08:00.0: realtek.ko not loaded, maybe it needs
> > to be added to initramfs?
> > [6.392864] r8169: probe of :08:00.0 failed with error -2
> > 
> > After searching with google I found a thread in the kernel mailing list
> > https://bugzilla.kernel.org/show_bug.cgi?id=204343
> > The cause is a soft depencency to module realtek.ko, which needs to be
> > loaded first.
> > 
> > Doing this manually, i.e. rmmod r8169 && modprobe realtek && modprobe
> > r8169
> > works fine; network interface eth0 gets configured and is operating.
> > 
> > Since the kernel loads the network module before systemd is running, it
> > has to be configured in initrd somehow.
> > So, the final question is, how to get that into initrd with genkernel?
> > I need to add something like this
> > 
> > cat /etc/modprobe.d/realtek
> > Softdep r8169 pre: realtek
> > 
> > How do I get this into initrd with genkernel-next?
> > 
> > Thanks in advance
> > 
> > Alex
> > 
> > PS
> > Profile:
> > default/linux/amd64/17.0/desktop/plasma/systemd
> > 
> > Relevant packages:
> > sys-apps/gentoo-systemd-integration-7
> > sys-apps/kmod-26-r5
> > sys-apps/systemd-244.3
> > sys-kernel/genkernel-next-69
> > sys-kernel/gentoo-sources-5.4.28
> > 
> > Lspci
> > 08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

Re: [gentoo-user] Realtek r8169 realtek.ko not loaded.

[Alexander Puchmayr]

Am Sonntag, 17. Mai 2020, 10:24:00 CEST schrieb William Kenworthy:
> Easiest would be to put it in /etc/conf.d/modules and rebuild the
> initrd.  Genkernel picks it up from there.  You could also ask genkernel
> to add all built modules to the initrd via its config file.
> 

Whats the format of that file?

Alex



> BillK
> 
> On 17/5/20 4:07 pm, Alexander Puchmayr wrote:
> > Hi there
> > 
> > I just upgraded an older notebook with r8169 network chip to new kernel
> > 5.4
> > (sys-kernel/gentoo-sources-5.4.28) with genkernel.
> > After booting the new kernel the network adapter was not initialized, no
> > network interface eth0.
> > Dmesg says
> > [6.390973] r8169 :08:00.0: realtek.ko not loaded, maybe it needs
> > to be added to initramfs?
> > [6.392864] r8169: probe of :08:00.0 failed with error -2
> > 
> > After searching with google I found a thread in the kernel mailing list
> > https://bugzilla.kernel.org/show_bug.cgi?id=204343
> > The cause is a soft depencency to module realtek.ko, which needs to be
> > loaded first.
> > 
> > Doing this manually, i.e. rmmod r8169 && modprobe realtek && modprobe
> > r8169
> > works fine; network interface eth0 gets configured and is operating.
> > 
> > Since the kernel loads the network module before systemd is running, it
> > has to be configured in initrd somehow.
> > So, the final question is, how to get that into initrd with genkernel?
> > I need to add something like this
> > 
> > cat /etc/modprobe.d/realtek
> > Softdep r8169 pre: realtek
> > 
> > How do I get this into initrd with genkernel-next?
> > 
> > Thanks in advance
> > 
> > Alex
> > 
> > PS
> > Profile:
> > default/linux/amd64/17.0/desktop/plasma/systemd
> > 
> > Relevant packages:
> > sys-apps/gentoo-systemd-integration-7
> > sys-apps/kmod-26-r5
> > sys-apps/systemd-244.3
> > sys-kernel/genkernel-next-69
> > sys-kernel/gentoo-sources-5.4.28
> > 
> > Lspci
> > 08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)


-- 
Dipl. Ing. Alexander Puchmayr
Grundbachstraße 36
4060 Leonding, Österreich

[gentoo-user] Realtek r8169 realtek.ko not loaded.

[Alexander Puchmayr]

Hi there

I just upgraded an older notebook with r8169 network chip to new kernel 5.4 
(sys-kernel/gentoo-sources-5.4.28) with genkernel. 
After booting the new kernel the network adapter was not initialized, no 
network interface eth0.
Dmesg says
[6.390973] r8169 :08:00.0: realtek.ko not loaded, maybe it needs to be 
added to initramfs?
[6.392864] r8169: probe of :08:00.0 failed with error -2

After searching with google I found a thread in the kernel mailing list
https://bugzilla.kernel.org/show_bug.cgi?id=204343
The cause is a soft depencency to module realtek.ko, which needs to be loaded 
first.

Doing this manually, i.e. rmmod r8169 && modprobe realtek && modprobe r8169 
works fine; network interface eth0 gets configured and is operating.

Since the kernel loads the network module before systemd is running, it has to 
be configured in initrd somehow.
So, the final question is, how to get that into initrd with genkernel?
I need to add something like this

cat /etc/modprobe.d/realtek 
Softdep r8169 pre: realtek

How do I get this into initrd with genkernel-next?

Thanks in advance
Alex

PS 
Profile:
default/linux/amd64/17.0/desktop/plasma/systemd

Relevant packages:
sys-apps/gentoo-systemd-integration-7
sys-apps/kmod-26-r5
sys-apps/systemd-244.3
sys-kernel/genkernel-next-69
sys-kernel/gentoo-sources-5.4.28

Lspci
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 03)

Re: [gentoo-user] can genkernel install files with different names?

[Alexander Openkowski]

I struggle with the naming of genkernel generated kernels for quite a while
now and have written a small wapper script for this purpose...

On Fri, Oct 18, 2019 at 11:27 AM Caveman Al Toraboran <
toraboracave...@protonmail.com> wrote:

> specifically, i want to install kernel + initramfs without version
> numbers.  this way, i will not need to update my boot loader every time i
> update the kernel.
>
> rgrds,
> cm.
>
>

[gentoo-user] Portage/emerge became extremely slow

[Alexander Puchmayr]

Hi there,

In the last months I experienced that emerge takes longer and longer to 
collect all dependencies, sometimes more than 10 to 20 minutes until it asks 
me whether to install the packages.

Today I had a new record. 61min(!) on a i7-Quadcore notebook, 59min user time, 
i.e. Portage being busy. What is portage doing all the time? It can't be that 
it takes more than one hour to tell me what packages to install without having 
installed/compiled one single package!


apollo ~ # time emerge -p -avukDN -j2 --verbose-conflicts --keep-going=y --
binpkg-changed-deps --with-bdeps=y --rebuilt-binaries=y --exclude cross-
armv7v-hardfloat-linux-gnueabi/glibc world

 * IMPORTANT: config file '/etc/portage/package.keywords/yapf' needs updating.
 * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
 * sections of the emerge man page to learn how to update config files.

These are the packages that would be merged, in order:

Calculating dependencies... done!

[verbose output messages, packages, conflicts skipped here]

 * IMPORTANT: 59 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


real61m51,252s
user59m5,839s
sys 2m45,123s
apollo ~ # 

Regards
Alex

Re: [gentoo-user] sysrescuecd gone rogue

[Alexander Openkowski]

I found some hints for using non-Gentoo LiveCDs for installation over here
when I realized that my beloved SystemRescueCD switched over to Arch:
https://wiki.gentoo.org/wiki/Installation_alternatives#Installation_from_non-Gentoo_LiveCDs

It seems though that these special advices (tar options when unpacking the
stage tarball) have also been added to the regular installation
instructions meanwhile, however in a slightly different form?

On Tue, Jun 4, 2019 at 4:02 PM Dale  wrote:

> Mick wrote:
> > I just downloaded my preferred medium of choice for installing Gentoo
> and
> > discovered sysrescuecd now runs Linux Arch instead of Gentoo and to make
> > things worse it is running systemd instead of openrc.  :-(
> >
> > A quick look in the forums did not reveal the reasons for this strategic
> > change.  Regardless, have you used the Arch based sysrescuecd to install
> > Gentoo and are there are any gotchas I should be aware of?
> >
> > Would I be better off to use a Gentoo Live ISO to install with?  I don't
> think
> > I have used one of these for more than 10 years ... or more!  O_O
> >
>
>
> I used to keep a copy of Knoppix around.  It can be used and has quite a
> lot of features.  If sysrescue is going that route, I may be just using
> something else.
>
> As another said tho, you can use about anything Linux as long as you are
> able to mount and chroot into the install.
>
> Dale
>
> :-)  :-)
>
>

Re: [gentoo-user] Re: OT scripting - strip zero if between period and digit

[Alexander Kapshuk]

On Wed, Jan 23, 2019 at 9:41 PM Grant Edwards  wrote:
>
> On 2019-01-23, Alexander Kapshuk  wrote:
>
> > This any better? :-)
> >
> > echo '198.088.0.01
> > 198.088.062.01
> > 198.088.0.001' | sed -r 's/\.0+([^.0]+)/.\1/g'
>
> I guess it's 'better', but it's still broken:
>
> $ echo '003.4.5.6' | sed -r 's/\.0+([^.0]+)/.\1/g'
> 003.4.5.6
>
> This is not a good application for a regex.
>
> --
> Grant Edwards   grant.b.edwardsYow! I have accepted
>   at   Provolone into my life!
>   gmail.com
>
>
The OP stated that there were no leading zeros in the first octet of
the IP address, so that case did not need to be handled.

Re: [gentoo-user] Re: OT scripting - strip zero if between period and digit

[Alexander Kapshuk]

On Wed, Jan 23, 2019 at 4:10 PM Grant Edwards  wrote:
>
> On 2019-01-23, Alexander Kapshuk  wrote:
> >
> > How about this one?
> >
> > echo '198.088.0.01
> > 198.088.062.01' | sed 's/\.0\([0-9][0-9]*\)/.\1/g'
> > 198.88.0.1
> > 198.88.62.1
>
> Also no.
>
> $ echo 198.088.0.001 |   sed 's/\.0\([0-9][0-9]*\)/.\1/g'
> 198.88.0.01
>
>
> --
> Grant Edwards   grant.b.edwardsYow! Hello.  Just walk
>   at   along and try NOT to think
>   gmail.comabout your INTESTINES being
>almost FORTY YARDS LONG!!
>
>

This any better? :-)

echo '198.088.0.01
198.088.062.01
198.088.0.001' | sed -r 's/\.0+([^.0]+)/.\1/g'
198.88.0.1
198.88.62.1
198.88.0.1

Re: [gentoo-user] OT scripting - strip zero if between period and digit

[Alexander Kapshuk]

On Wed, Jan 23, 2019 at 9:05 AM Paul Colquhoun
 wrote:
>
> On Wednesday, 23 January 2019 5:52:57 PM AEDT Alexander Kapshuk wrote:
> > On Wed, Jan 23, 2019 at 5:20 AM Adam Carter  wrote:
> > >> > François-Xavier
> > >>
> > >> My bad, it should be:
> > >>
> > >> sed 's/0*\([0-9][0-9]*\)/\1/g'
> > >>
> > >> (tests are indeed needed!)
> > >
> > > Many thanks François. This is almost right, but it is also stripping zeros
> > > that follow a letter, and I only want it to strip zeros that are
> > > proceeded by a period. There are no leading zeros in the first octet of
> > > the IP so that case does not need to be handled.
> > >
> > > Does the \1 refer to what's in the ()'s? So anything that one would wont
> > > to carry through should be inside the ()'s and anything that's outside is
> > > stripped, right?
> > Would something like to do the trick?
> > echo 198.088.062.01 | sed 's/\.0/./g'
> > 198.88.62.1
>
> In a word, no.
>
> echo 198.088.0.01 | sed 's/\.0/./g'
> 198.88..1
>
>
> --
> Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/
>   Asking for technical help in newsgroups?  Read this first:
>  http://catb.org/~esr/faqs/smart-questions.html#intro
>
>
>
>

How about this one?

echo '198.088.0.01
198.088.062.01' | sed 's/\.0\([0-9][0-9]*\)/.\1/g'
198.88.0.1
198.88.62.1

Re: [gentoo-user] OT scripting - strip zero if between period and digit

[Alexander Kapshuk]

On Wed, Jan 23, 2019 at 5:20 AM Adam Carter  wrote:
>>
>> > François-Xavier
>> >
>> >
>>
>> My bad, it should be:
>>
>> sed 's/0*\([0-9][0-9]*\)/\1/g'
>>
>> (tests are indeed needed!)
>
>
> Many thanks François. This is almost right, but it is also stripping zeros 
> that follow a letter, and I only want it to strip zeros that are proceeded by 
> a period. There are no leading zeros in the first octet of the IP so that 
> case does not need to be handled.
>
> Does the \1 refer to what's in the ()'s? So anything that one would wont to 
> carry through should be inside the ()'s and anything that's outside is 
> stripped, right?
>
>
>

Would something like to do the trick?
echo 198.088.062.01 | sed 's/\.0/./g'
198.88.62.1

Re: [gentoo-user] Re: bash upgrading problem

[Alexander Kapshuk]

On Mon, Jan 21, 2019 at 3:43 PM Jacques Montier  wrote:
>
>
> Le lun. 21 janv. 2019 à 14:16, Alexander Kapshuk 
>  a écrit :
>>
>>
>>
>> What is the output of:
>> env | grep libsandbox.so
>>
>
> There is no output of env | grep libsandbox.so, but with env | grep sandbox, 
> i get this :
>
> $ env | grep sandbox
> 13:CONFIG_PROTECT_MASK=/etc/sandbox.d /etc/php/cli-php7.2/ext-active/ 
> /etc/php/cgi-php7.2/ext-active/ /etc/php/apache2-php7.2/ext-active/ 
> /etc/fonts/fonts.conf /etc/gentoo-release /etc/gconf /etc/terminfo /etc/dconf 
> /etc/ca-certificates.conf /etc/revdep-rebuild
>
> --
> Jacques
>

(1). Are you attempting to build bash as yourself or as user root?
(2). If the latter, what's in LD_PRELOAD and LD_LIBRARY_PATH?

(3). What's the output of:
ls -l /path/to/libsandbox.so?
(4). And:
file /path/to/libsandbox.so

Re: [gentoo-user] Re: bash upgrading problem

[Alexander Kapshuk]

On Mon, Jan 21, 2019 at 3:03 PM Jacques Montier  wrote:
>
> Le lun. 21 janv. 2019 à 13:04, Alexander Kapshuk 
>  a écrit :
>>
>>
>>
>> What is the output of:
>> echo $LD_PRELOAD
>> echo $LD_LIBRARY_PATH
>>
>
> No output.
>
> --
> Jacques
>

So these variables are both unset. But the build log you supplied, had
a record saying the object 'libsandbox.so' could not be preloaded from
LD_PRELOAD.
Is that in your build environment, or in your regular user's
environment, or are they both the same on your system?

What is the output of:
env | grep libsandbox.so

Re: [gentoo-user] Re: bash upgrading problem

[Alexander Kapshuk]

On Mon, Jan 21, 2019 at 1:31 PM Jacques Montier  wrote:
>
>
>
> Le lun. 21 janv. 2019 à 12:11, Alexander Kapshuk 
>  a écrit :
>
>>
>> The /proc/PID directory listed by the ls command is the directory for
>> the process that executed the ls command. See below.
>>
>> % ls -ld /proc/self &
>> [1] 27318
>> % lrwxrwxrwx 1 root root 0 Sep 24 14:06 /proc/self -> 27318
>> [1] +  Done
>>
>> As for the user/group owning the files in /proc/self, they are owned
>> by the user who initiated the process that created those entries in
>> the proc file system.
>>
>
> Thanks Alexander for your explanation.
> Nevertheless, the bash rejected password remains a mystery to me. :-(
>
> Regards,
>
>

What is the output of:
echo $LD_PRELOAD
echo $LD_LIBRARY_PATH

Re: [gentoo-user] Re: bash upgrading problem

[Alexander Kapshuk]

On Mon, Jan 21, 2019 at 12:52 PM Jacques Montier  wrote:
>
>
> Le lun. 21 janv. 2019 à 11:21, Raffaele Belardi  a 
> écrit :
>>
>>
>> Well, they are owned by jacques instead of root. Could it be the reason why 
>> you're asked
>> for a password? Maybe some strange interaction with the sandbox?
>>
>> raffaele
>
>
>
> Yes, i noticed that, but how to explain my root password rejected when 
> emerging bash ?
>
> I also noticed something strange :
> $ ls -al /proc/self/fd
> total 0
> dr-x-- 2 jacques jacques  0 21 janv. 11:49 ./
> dr-xr-xr-x 9 jacques jacques  0 21 janv. 11:49 ../
> lrwx-- 1 jacques jacques 64 21 janv. 11:49 0 -> /dev/pts/1
> lrwx-- 1 jacques jacques 64 21 janv. 11:49 1 -> /dev/pts/1
> lrwx-- 1 jacques jacques 64 21 janv. 11:49 2 -> /dev/pts/1
> lr-x-- 1 jacques jacques 64 21 janv. 11:49 3 -> /proc/4461/fd/
>
> The /proc/4461 directory does not exist !
>
> --
> Jacques
>

The /proc/PID directory listed by the ls command is the directory for
the process that executed the ls command. See below.

% ls -ld /proc/self &
[1] 27318
% lrwxrwxrwx 1 root root 0 Sep 24 14:06 /proc/self -> 27318
[1] +  Done

As for the user/group owning the files in /proc/self, they are owned
by the user who initiated the process that created those entries in
the proc file system.

Re: [gentoo-user] sys-process/audit | gen_flagtabs_h-gen_tables.o] Error 1

[Alexander Kapshuk]

On Wed, Dec 12, 2018 at 4:13 PM Hasan Ç.  wrote:
>
> Hello,
>
> Any idea?
>
>  * Package:sys-process/audit-2.8.3
>  * Repository: gentoo
>  * Maintainer: seli...@gentoo.org robb...@gentoo.org
>  * USE:abi_x86_64 amd64 elibc_glibc kernel_linux python 
> python_targets_python2_7 python_targets_python3_6 userland_GNU
>  * FEATURES:   preserve-libs sandbox userpriv usersandbox
>  * Determining the location of the kernel source code
>  * Found kernel source directory:
>  * /usr/src/linux
>  * Found sources for kernel version:
>  * 4.19.8-gentoo
>  * Checking for suitable kernel configuration options...
>  [ ok ]
>  * Applying audit-2.4.3-python.patch ...
>  [ ok ]
>  * Applying audit-2.1.3-ia64-compile-fix.patch ...
>  [ ok ]
>  * Running eautoreconf in 
> '/var/tmp/portage/sys-process/audit-2.8.3/work/audit-2.8.3' ...
>  * Running libtoolize --install --copy --force --automake ...
>  [ ok ]
>  * Running aclocal ...
>  [ ok ]
>  * Running autoconf --force ...
>  [ ok ]
>  * Running autoheader ...
>  [ ok ]
>  * Running automake --add-missing --copy --force-missing ...
>  [ ok ]
>  * Running elibtoolize in: audit-2.8.3/
>  *   Applying portage/1.2.0 patch ...
>  *   Applying sed/1.5.6 patch ...
>  *   Applying as-needed/2.4.3 patch ...
>  * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
> Configuring auditd
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking target system type... x86_64-pc-linux-gnu
> checking for a BSD-compatible install... 
> /usr/lib/portage/python3.6/ebuild-helpers/xattr/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking how to print strings... printf
> checking for style of include used by make... GNU
> checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
> checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
> checking whether x86_64-pc-linux-gnu-gcc understands -c and -o together... yes
> checking dependency style of x86_64-pc-linux-gnu-gcc... none
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by x86_64-pc-linux-gnu-gcc... 
> /usr/x86_64-pc-linux-gnu/bin/ld
> checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... 
> /usr/bin/x86_64-pc-linux-gnu-nm -B
> checking the name lister (/usr/bin/x86_64-pc-linux-gnu-nm -B) interface... 
> BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 201326592
> checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
> format... func_convert_file_noop
> checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
> func_convert_file_noop
> checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... 
> -r
> checking for x86_64-pc-linux-gnu-objdump... x86_64-pc-linux-gnu-objdump
> checking how to recognize dependent libraries... pass_all
> checking for x86_64-pc-linux-gnu-dlltool... no
> checking for dlltool... no
> checking how to associate runtime and link libraries... printf %s\n
> checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
> checking for archiver @FILE support... @
> checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip
> checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
> checking command to parse /usr/bin/x86_64-pc-linux-gnu-nm -B output from 
> x86_64-pc-linux-gnu-gcc object... ok
> checking for sysroot... no
> checking for a working dd... /bin/dd
> checking how to truncate binary pipes... /bin/dd bs=4096 count=1
> checking for x86_64-pc-linux-gnu-mt... no
> checking for mt... no
> checking if : is a manifest tool... no
> checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
> checking 

Re: [gentoo-user] kstars and indilib

[Alexander Puchmayr]

Am Samstag, 8. Dezember 2018, 05:50:59 CET schrieb David Haller:
> Hello,
> 
> Just updated the one in the tree in my local overlay, see attached
> indilib-1.7.5.ebuild.
> 
Thanks a lot, works fine!

But there's still the problem that the stable version of kstars does not check 
the correct version of indi and compiles a version not supporting it although 
the use flag has been set. 
Do you create a bug report for kstars or shall I do it?

Alex

Re: [gentoo-user] CPU upgrade and LVM questions.

[Alexander Puchmayr]

Am Donnerstag, 6. Dezember 2018, 10:27:31 CET schrieb Dale:
> Howdy,
> 
> I mentioned in other threads that I'm doing some upgrades to my system. 
> My first question is about a CPU upgrade.  I currently have this for my
> CPU, from cpuinfo:
> 
> AMD Phenom(tm) II X4 955 Processor
> 
> I've bought but not yet installed a FX-8350 CPU.  I have this in my
> make.conf file:
> 
> CFLAGS="-march=native -O2 -pipe"

Compiling the whole system with -march=native might lead to troubles, 
especially when doing a CPU change. This option means that gcc is determining 
the type of CPU automatically and adjusts the instruction set used to exactly 
this CPU. Although, in your case, it is highly likely that your new CPU 
understands all commands from the old, but I wouldn't bet on it. Its possible 
that your existing software encounters problems like "illegal instruction" or 
the like. Very bad if your compiler crashes after CPU replacement, then you 
cannot emerge anything. I highly recommend using CFLAGS="-O2 -pipe" and 
nothing more, the performance difference is, if measurable at all, negligible. 

> USE_CPU="fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
> pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc
> extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic
> cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt
> nodeid_msr hw_pstate npt lbrv svm_lock nrip_save"
> 
As someone else in this thread already mentioned, USE_CPU is not used. What 
you're looking for is CPU_FLAGS_X86=..., which defines what cpu-specific 
options 
will be enabled for packages supporting it and where it makes sense. See 
package cpuid2cpuflags for details.

Regards
Alex

[gentoo-user] kstars and indilib

[Alexander Puchmayr]

Hi there,

I tried to compile kstars with useflag indi, but the provided version in 
portage is too old:

[build.log from kstars]
-- Checking for module 'libindi'
--   Found libindi, version 1.6.0
-- INDI version 1.5.0 found in /usr/include/libindi, but at least version 
1.7.1 is required
-- INDI version 1.5.0 found in /usr/include/libindi, but at least version 
1.7.1 is required
-- Found INDI: /usr/lib/libindiclient.a, /usr/include/libindi

I have no idea why it pretends to find indi-1.5.0, when 1.6 is installed :-(
Version 1.6 is currently the only version in portage, which renders the useflag 
"indi" for kstars useless, as the resulting kstars binary does not support 
indi.

https://indilib.org/download/gentoo.html shows a way to add an overlay, but 
the repo proposed does not exist anymore.

Where do I find a ebuild for installing at least indilib-1.7.1?

Regards
Alex

Re: [gentoo-user] RAM checks for chromium

[Alexander Kapshuk]

On Tue, Dec 4, 2018 at 10:47 AM Mick  wrote:
>
> On Tuesday, 4 December 2018 08:06:22 GMT Alexander Kapshuk wrote:
> > On Tue, Dec 4, 2018 at 9:35 AM Mick  wrote:
> > > Two Intel systems with 4G RAM failed to build chromium, even after setting
> > >
> > > MAKEOPTS="-j2". The ebuild is checking for a minimum of 3G RAM:
> > > >>> Running pre-merge checks for www-client/chromium-70.0.3538.110
> > >
> > >  * Checking for at least 3 GiB RAM ...[ ok
> > >  ]
> > >  * Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/
> > >
> > > chromium-70.0.3538.110/temp" ...  [ ok
> > > ]
> > >
> > > Given I've spent more than two days compiling to get nowhere with this,
> > > I'm
> > > thinking:
> > >
> > > a) Chromium probably needs more than 3G now.
> > > b) Either the ebuild, or portage, ought to check available RAM and
> > > dynamically adjust the number of jobs accordingly - or have I watched too
> > > many AI movies?
> > >
> > > --
> > > Regards,
> > > Mick
> >
> > You're right. Chromium does require more than 3G of RAM to build.
> > Here are the current system requirements for building Chromium on Linux:
> >
> > System requirements
> > A 64-bit Intel machine with at least 8GB of RAM. More than 16GB is
> > highly recommended.
>
> OK it figures, an AMD system with 16G RAM and /var/portage/ on a tmpfs had no
> problem.
>
>
> > At least 100GB of free disk space.
>
> O_O  What the ... ?
>
>
> > You must have Git and Python v2 installed already.
> >
> > See the link below for details.
> > https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux_build_instr
> > uctions.md#system-requirements
>
> Thanks for this.  It may be I'll need to build chromium as a binary on the
> faster PC from now on and copy it over to the older clients, but I can't
> recall what command spews out the detailed CFLAGS for the client which I will
> need to run on the faster host's CLI to emerge the binary.  Grateful for any
> hints.
>
> --
> Regards,
> Mick

Perhaps these two gcc commands are what you're after:
gcc -c -Q -march=native --help=target
gcc -### -march=native /usr/include/stdlib.h

See this link for details, https://wiki.gentoo.org/wiki/GCC_optimization

Re: [gentoo-user] RAM checks for chromium

[Alexander Kapshuk]

On Tue, Dec 4, 2018 at 9:35 AM Mick  wrote:
>
> Two Intel systems with 4G RAM failed to build chromium, even after setting
> MAKEOPTS="-j2". The ebuild is checking for a minimum of 3G RAM:
>
> >>> Running pre-merge checks for www-client/chromium-70.0.3538.110
>  * Checking for at least 3 GiB RAM ...[ ok ]
>  * Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/
> chromium-70.0.3538.110/temp" ...  [ ok ]
>
> Given I've spent more than two days compiling to get nowhere with this, I'm
> thinking:
>
> a) Chromium probably needs more than 3G now.
> b) Either the ebuild, or portage, ought to check available RAM and dynamically
> adjust the number of jobs accordingly - or have I watched too many AI movies?
>
> --
> Regards,
> Mick

You're right. Chromium does require more than 3G of RAM to build.
Here are the current system requirements for building Chromium on Linux:

System requirements
A 64-bit Intel machine with at least 8GB of RAM. More than 16GB is
highly recommended.
At least 100GB of free disk space.
You must have Git and Python v2 installed already.

See the link below for details.
https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux_build_instructions.md#system-requirements

Re: [gentoo-user] Weird compilation error (nasm)

[Alexander Kapshuk]

On Tue, Nov 13, 2018 at 7:57 PM  wrote:
>
> On 11/13 07:52, Alexander Kapshuk wrote:
> > On Tue, Nov 13, 2018 at 7:10 PM  wrote:
> > >
> > > Hi,
> > >
> > > I got a weird looking error while upgrading/recompiling nasm:
> > > cmake -C 
> > > /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_common_config.cmake
> > >  -G Unix Makefiles -DCMAKE_INSTALL_PREFIX=/usr 
> > > -DCMAKE_INSTALL_DEFAULT_DOCDIR=/usr/share/doc/libjpeg-turbo-2.0.1 
> > > -DENABLE_STATIC=no -DWITH_JAVA=no -DWITH_MEM_SRCDST=ON 
> > > -DCMAKE_BUILD_TYPE=Gentoo 
> > > -DCMAKE_TOOLCHAIN_FILE=/var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_toolchain.cmake
> > >   /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1
> > > loading initial cache file 
> > > /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_common_config.cmake
> > > -- The C compiler identification is GNU 8.2.0
> > > -- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc
> > > -- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc -- works
> > > -- Detecting C compiler ABI info
> > > -- Detecting C compiler ABI info - done
> > > -- Detecting C compile features
> > > -- Detecting C compile features - done
> > > -- CMAKE_BUILD_TYPE = Gentoo
> > > -- VERSION = 2.0.1, BUILD = 20181113
> > > -- 64-bit build (x86_64)
> > > -- CMAKE_INSTALL_PREFIX = /usr
> > > -- CMAKE_INSTALL_BINDIR = bin (/usr/bin)
> > > -- CMAKE_INSTALL_DATAROOTDIR = share (/usr/share)
> > > -- CMAKE_INSTALL_DOCDIR = /usr/share/doc/libjpeg-turbo-2.0.1
> > > -- CMAKE_INSTALL_INCLUDEDIR = include (/usr/include)
> > > -- CMAKE_INSTALL_LIBDIR = lib64 (/usr/lib64)
> > > -- CMAKE_INSTALL_MANDIR = /usr/share/man
> > > -- Shared libraries enabled (ENABLE_SHARED = 1)
> > > -- Static libraries disabled (ENABLE_STATIC = 0)
> > > -- 12-bit JPEG support disabled (WITH_12BIT = 0)
> > > -- Arithmetic decoding support enabled (WITH_ARITH_DEC = 1)
> > > -- Arithmetic encoding support enabled (WITH_ARITH_ENC = 1)
> > > -- TurboJPEG API library enabled (WITH_TURBOJPEG = 1)
> > > -- TurboJPEG Java wrapper disabled (WITH_JAVA = 0)
> > > -- In-memory source/destination managers enabled (WITH_MEM_SRCDST = 1)
> > > -- Emulating libjpeg API/ABI v6.2 (WITH_JPEG7 = 0, WITH_JPEG8 = 0)
> > > -- libjpeg API shared library version = 62.3.0
> > > -- Compiler flags = -march=native -O -pipe
> > > -- Linker flags = -Wl,-O1 -Wl,--as-needed
> > > -- Looking for sys/types.h
> > > -- Looking for sys/types.h - found
> > > -- Looking for stdint.h
> > > -- Looking for stdint.h - found
> > > -- Looking for stddef.h
> > > -- Looking for stddef.h - found
> > > -- Check size of size_t
> > > -- Check size of size_t - done
> > > -- Check size of unsigned long
> > > -- Check size of unsigned long - done
> > > -- Performing Test HAVE_BUILTIN_CTZL
> > > -- Performing Test HAVE_BUILTIN_CTZL - Success
> > > -- Looking for include file locale.h
> > > -- Looking for include file locale.h - found
> > > -- Looking for include file stdlib.h
> > > -- Looking for include file stdlib.h - found
> > > -- Looking for include file sys/types.h
> > > -- Looking for include file sys/types.h - found
> > > -- Looking for memset
> > > -- Looking for memset - found
> > > -- Looking for memcpy
> > > -- Looking for memcpy - found
> > > -- Check size of unsigned char
> > > -- Check size of unsigned char - done
> > > -- Check size of unsigned short
> > > -- Check size of unsigned short - done
> > > -- Performing Test INCOMPLETE_TYPES
> > > -- Performing Test INCOMPLETE_TYPES - Success
> > > -- Compiler supports pointers to undefined structures.
> > > -- Performing Test RIGHT_SHIFT_IS_UNSIGNED
> > > -- Performing Test RIGHT_SHIFT_IS_UNSIGNED - Failed
> > > -- Performing Test __CHAR_UNSIGNED__
> > > -- Performing Test __CHAR_UNSIGNED__ - Failed
> > > -- Performing Test INLINE_WORKS
> > > -- Performing Test INLINE_WORKS - Success
> > > -- INLINE = __inline__ __attribute__((always_inline)) (FORCE_INLINE = 1)
> > > -- Performing Test HAVE_VERSION_SCRIPT
> > > -- Performing Test HAVE_VERSION_SCRIPT - Success
> > > -- Linker supports GNU-style version scripts
> > > -- CMA

Re: [gentoo-user] Weird compilation error (nasm)

[Alexander Kapshuk]

On Tue, Nov 13, 2018 at 7:10 PM  wrote:
>
> Hi,
>
> I got a weird looking error while upgrading/recompiling nasm:
> cmake -C 
> /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_common_config.cmake
>  -G Unix Makefiles -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_INSTALL_DEFAULT_DOCDIR=/usr/share/doc/libjpeg-turbo-2.0.1 
> -DENABLE_STATIC=no -DWITH_JAVA=no -DWITH_MEM_SRCDST=ON 
> -DCMAKE_BUILD_TYPE=Gentoo 
> -DCMAKE_TOOLCHAIN_FILE=/var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_toolchain.cmake
>   /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1
> loading initial cache file 
> /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_common_config.cmake
> -- The C compiler identification is GNU 8.2.0
> -- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc
> -- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- CMAKE_BUILD_TYPE = Gentoo
> -- VERSION = 2.0.1, BUILD = 20181113
> -- 64-bit build (x86_64)
> -- CMAKE_INSTALL_PREFIX = /usr
> -- CMAKE_INSTALL_BINDIR = bin (/usr/bin)
> -- CMAKE_INSTALL_DATAROOTDIR = share (/usr/share)
> -- CMAKE_INSTALL_DOCDIR = /usr/share/doc/libjpeg-turbo-2.0.1
> -- CMAKE_INSTALL_INCLUDEDIR = include (/usr/include)
> -- CMAKE_INSTALL_LIBDIR = lib64 (/usr/lib64)
> -- CMAKE_INSTALL_MANDIR = /usr/share/man
> -- Shared libraries enabled (ENABLE_SHARED = 1)
> -- Static libraries disabled (ENABLE_STATIC = 0)
> -- 12-bit JPEG support disabled (WITH_12BIT = 0)
> -- Arithmetic decoding support enabled (WITH_ARITH_DEC = 1)
> -- Arithmetic encoding support enabled (WITH_ARITH_ENC = 1)
> -- TurboJPEG API library enabled (WITH_TURBOJPEG = 1)
> -- TurboJPEG Java wrapper disabled (WITH_JAVA = 0)
> -- In-memory source/destination managers enabled (WITH_MEM_SRCDST = 1)
> -- Emulating libjpeg API/ABI v6.2 (WITH_JPEG7 = 0, WITH_JPEG8 = 0)
> -- libjpeg API shared library version = 62.3.0
> -- Compiler flags = -march=native -O -pipe
> -- Linker flags = -Wl,-O1 -Wl,--as-needed
> -- Looking for sys/types.h
> -- Looking for sys/types.h - found
> -- Looking for stdint.h
> -- Looking for stdint.h - found
> -- Looking for stddef.h
> -- Looking for stddef.h - found
> -- Check size of size_t
> -- Check size of size_t - done
> -- Check size of unsigned long
> -- Check size of unsigned long - done
> -- Performing Test HAVE_BUILTIN_CTZL
> -- Performing Test HAVE_BUILTIN_CTZL - Success
> -- Looking for include file locale.h
> -- Looking for include file locale.h - found
> -- Looking for include file stdlib.h
> -- Looking for include file stdlib.h - found
> -- Looking for include file sys/types.h
> -- Looking for include file sys/types.h - found
> -- Looking for memset
> -- Looking for memset - found
> -- Looking for memcpy
> -- Looking for memcpy - found
> -- Check size of unsigned char
> -- Check size of unsigned char - done
> -- Check size of unsigned short
> -- Check size of unsigned short - done
> -- Performing Test INCOMPLETE_TYPES
> -- Performing Test INCOMPLETE_TYPES - Success
> -- Compiler supports pointers to undefined structures.
> -- Performing Test RIGHT_SHIFT_IS_UNSIGNED
> -- Performing Test RIGHT_SHIFT_IS_UNSIGNED - Failed
> -- Performing Test __CHAR_UNSIGNED__
> -- Performing Test __CHAR_UNSIGNED__ - Failed
> -- Performing Test INLINE_WORKS
> -- Performing Test INLINE_WORKS - Success
> -- INLINE = __inline__ __attribute__((always_inline)) (FORCE_INLINE = 1)
> -- Performing Test HAVE_VERSION_SCRIPT
> -- Performing Test HAVE_VERSION_SCRIPT - Success
> -- Linker supports GNU-style version scripts
> -- CMAKE_EXECUTABLE_SUFFIX =
>  * ACCESS DENIED:  fopen_wr: /?
> -- The ASM_NASM compiler identification is NASM
> -- Found assembler: /usr/bin/nasm
> -- CMAKE_ASM_NASM_COMPILER = /usr/bin/nasm
> -- CMAKE_ASM_NASM_OBJECT_FORMAT = elf64
> -- CMAKE_ASM_NASM_FLAGS =  -DELF -D__x86_64__ -DPIC
> -- SIMD extensions: x86_64 (WITH_SIMD = 1)
> -- FLOATTEST = sse
> -- RPM architecture = x86_64, DEB architecture = amd64
> -- <<< Gentoo configuration >>>
> Build type  Gentoo
> Install path/usr
> Compiler flags:
> C   -march=native -O -pipe
> C++
> Linker flags:
> Executable  -Wl,-O1 -Wl,--as-needed
> Module  -Wl,-O1 -Wl,--as-needed
> Shared  -Wl,-O1 -Wl,--as-needed
>
> -- Configuring done
> -- Generating done
> -- Build files have been written to: 
> /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64
> >>> Source configured.
>  * --- ACCESS VIOLATION SUMMARY 
> ---
>  * LOG FILE: "/var/log/sandbox/sandbox-16492.log"
>  *
> VERSION 1.0
> FORMAT: F - Function called
> FORMAT: S - Access Status
> FORMAT: P - Path as passed to function
> FORMAT: A - 

Re: [gentoo-user] libQt5Core.so.5 => not found

[Alexander Kapshuk]

On Fri, Nov 9, 2018 at 1:33 PM  wrote:
>
> I'm trying to build/emerge dev-qt/qtgui-5.11.1, but I get this:
>
> # ldd 
> /Net/portage_tmpdir/portage/dev-qt/qtgui-5.11.1/work/qtbase-everywhere-src-5.11.1/bin/qvkgen
> linux-vdso.so.1 (0x7fff3ddff000)
> libQt5Core.so.5 => not found
> libc.so.6 => /lib64/libc.so.6 (0x7f697dbd8000)
> /lib64/ld-linux-x86-64.so.2 (0x7f697e1f5000)
> # strings /etc/ld.so.cache | grep libQt5Core.so.5
> libQt5Core.so.5
> /usr/lib64/libQt5Core.so.5
> # ls -l /usr/lib64/libQt5Core.so.5*
> lrwxrwxrwx 1 root root  20 Nov  5 12:49 /usr/lib64/libQt5Core.so.5 -> 
> libQt5Core.so.5.11.1
> lrwxrwxrwx 1 root root  20 Nov  5 12:49 /usr/lib64/libQt5Core.so.5.11 -> 
> libQt5Core.so.5.11.1
> -rwxr-xr-x 1 root root 5351376 Nov  5 12:49 /usr/lib64/libQt5Core.so.5.11.1
>
> So why isn't it found ?
>
> Regards,
> /Karl Hammar
>
> ---
> Aspö Data
> Lilla Aspö 148
> S-742 94 Östhammar
> Sweden
>
>
>

Seeing the actual build error message, rather then the output of ldd,
may contain information about the build environment, and other
information that might offer better clues as to what else might be
amiss.
Also, the output of 'strace /bin/qvkgen' will indicate what paths are
searched for libQt5Core.so.5.

Re: [gentoo-user] Compilation problem iptables

[Alexander Kapshuk]

On Wed, Oct 24, 2018 at 7:07 PM  wrote:
>
> Hi,
>
> while syncing/updateing, this happens (net-firewall/iptables-1.8.1) :
> ototypes -Wredundant-decls -Wshadow -Wstrict-prototypes -Wlogical-op  
>   -Winline -pipe -D_INIT=libxt_multiport_init -DPIC -fPIC -march=native -O 
> -pipe -o libxt_multiport.oo -c libxt_multiport.c;
> x86_64-pc-linux-gnu-gcc -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES 
> -D_FILE_OFFSET_BITS=64 -D_REENTRANT
> -DXTABLES_LIBDIR=\"/usr/lib64/xtables\" -DXTABLES_INTERNAL -I../include -I.. 
> -I../include -I.. -Wp,-MMD,./.libxt_nfacct.oo.d,-MT,libxt_nfacct.oo -Wall 
> -Waggregate-return -Wmissing-declarations-Wmissing-prototypes 
> -Wredundant-decls -Wshadow -Wstrict-prototypes -Wlogical-op-Winline 
> -pipe -D_INIT=libxt_nfacct_init -DPIC -fPIC -march=native -O -pipe -o 
> libxt_nfacct.oo -c libxt_nfacct.c;
> x86_64-pc-linux-gnu-gcc -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES 
> -D_FILE_OFFSET_BITS=64 -D_REENTRANT
> -DXTABLES_LIBDIR=\"/usr/lib64/xtables\" -DXTABLES_INTERNAL -I../include -I.. 
> -I../include -I.. -Wp,-MMD,./.libxt_osf.oo.d,-MT,libxt_osf.oo -Wall 
> -Waggregate-return -Wmissing-declarations  -Wmissing-prototypes 
> -Wredundant-decls -Wshadow -Wstrict-prototypes -Wlogical-op-Winline 
> -pipe -D_INIT=libxt_osf_init -DPIC -fPIC -march=native -O -pipe -o 
> libxt_osf.oo -c libxt_osf.c;
> In file included from ../iptables/nft.h:5,
>  from libxt_limit.c:18:
> ../iptables/nft-shared.h:6:10: fatal error: libnftnl/rule.h: No such file or 
> directory
>  #include 
>   ^
> compilation terminated.
> x86_64-pc-linux-gnu-gcc -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES 
> -D_FILE_OFFSET_BITS=64 -D_REENTRANT
> -DXTABLES_LIBDIR=\"/usr/lib64/xtables\" -DXTABLES_INTERNAL -I../include -I.. 
> -I../include -I.. -Wp,-MMD,./.libxt_owner.oo.d,-MT,libxt_owner.oo -Wall 
> -Waggregate-return -Wmissing-declarations  -Wmissing-prototypes 
> -Wredundant-decls -Wshadow -Wstrict-prototypes -Wlogical-op-Winline 
> -pipe -D_INIT=libxt_owner_i
>
> I wanted I sent the whole bunch of logs...
>
> Cheers!
> Meino
>
>
>
>

The header file reported as missing belongs to the net-libs/libnftnl package.
Do you have it installed?

Re: [gentoo-user] problem updating KDE breeze

[Alexander Kapshuk]

On Mon, Oct 22, 2018 at 7:15 AM Philip Webb  wrote:
>
> 181021 Franz Fellner wrote:
> > the actual error really is missing.
> > Can you use pastebin or something similar to upload the whole build.log?
> > The number of cores may help to estimate the unmber of compilation units
> > that still get built.  Unfortunately not with cmake.  It usually continues
> > building targets that do not depend on the failed target.
> > You may have to scroll up hundreds of lines.
> > So, again: Please give us the complete build.log !
>
> I hadn't run into this kind of error before
> & assumed there cb only  1  error for each Emerge.
> Here is where 'Error 1' occurs :
>
> [ 37%] Building CXX object 
> kdecoration/CMakeFiles/breezedecoration.dir/breezesettings.cpp.o
> cd 
> /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kdecoration
>  && /usr/bin/x86_64-pc-linux-gnu-g++ -DKCOREADDONS_LIB -DKGUIADDONS_LIB 
> -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -\
> DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB 
> -DTRANSLATION_DOMAIN=\"breeze_kwin_deco\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
> -Dbreezedecoration_EXPORTS -I/var/tmp/portage/portage/kde-plasm\
> a/breeze-5.13.5/work/breeze-5.13.5_build/kdecoration 
> -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kdecoration
>  -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.1\
> 3.5_build/kdecoration/breezedecoration_autogen/include -isystem 
> /usr/include/qt5 -isystem /usr/include/qt5/QtCore -isystem 
> /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtGui -isystem 
> /usr/i\
> nclude/qt5/QtDBus -isystem /usr/include/KDecoration2 -isystem 
> /usr/include/KF5 -isystem /usr/include/KF5/KConfigCore -isystem 
> /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KConfigWidgets -isyste\
> m /usr/include/KF5/KCodecs -isystem /usr/include/KF5/KWidgetsAddons -isystem 
> /usr/include/qt5/QtWidgets -isystem /usr/include/KF5/KConfigGui -isystem 
> /usr/include/qt5/QtXml -isystem /usr/include/KF5/KAut\
> h -isystem /usr/include/KF5/KGuiAddons -isystem /usr/include/KF5/KI18n 
> -isystem /usr/include/KF5/KWindowSystem -isystem /usr/include/qt5/QtX11Extras 
>   -DQT_NO_DEBUG -DNDEBUG -march=native -O2 -pipe -std=\
> c++0x -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align 
> -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
> -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type\
>  -Wvla -Wdate-time -fPIC -fvisibility=hidden -fvisibility-inlines-hidden   
> -fPIC -std=gnu++11 -o CMakeFiles/breezedecoration.dir/breezesettings.cpp.o -c 
> /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/\
> work/breeze-5.13.5_build/kdecoration/breezesettings.cpp
> /usr/lib64/libKF5Declarative.so.5: undefined reference to 
> `QQmlPropertyMap::init(QMetaObject const*)@Qt_5'
> /usr/lib64/libKF5Declarative.so.5: undefined reference to 
> `QQmlPropertyMap::allocatePrivate()@Qt_5'
> collect2: error: ld returned 1 exit status
> make[2]: *** [kstyle/config/CMakeFiles/breeze-settings5.dir/build.make:121: 
> kstyle/config/breeze-settings5] Error 1
> make[2]: Leaving directory 
> '/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build'
> make[1]: *** [CMakeFiles/Makefile2:550: 
> kstyle/config/CMakeFiles/breeze-settings5.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs
> Generating MOC source 4NBMFDNHZT/moc_breezetransitionwidget.cpp
> /usr/lib64/qt5/bin/moc 
> -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kstyle
>  
> -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kstyle/breeze_autog\
> en/include 
> -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle 
> -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle/animations
>  -I/var/tmp/portage/portag\
> e/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle/debug -I/usr/include/qt5 
> -I/usr/include/qt5/QtCore -I/usr/lib64/qt5/mkspecs/linux-g++ 
> -I/usr/include/qt5/QtGui -I/usr/include/qt5/QtWidgets -I/usr/inc\
> lude/qt5/QtDBus -I/usr/include/qt5/QtQuick -I/usr/include/qt5/QtQml 
> -I/usr/include/qt5/QtNetwork -I/usr/include/KF5/KConfigCore 
> -I/usr/include/KF5 -I/usr/include/KF5/KConfigWidgets -I/usr/include/KF5/KCo\
> decs -I/usr/include/KF5/KWidgetsAddons -I/usr/include/KF5/KConfigGui 
> -I/usr/include/qt5/QtXml -I/usr/include/KF5/KAuth 
> -I/usr/include/KF5/KCoreAddons -I/usr/include/KF5/KGuiAddons 
> -I/usr/include/KF5/KWin\
> dowSystem -I/usr/include/KF5/KStyle -I/usr/include/qt5/QtX11Extras 
> -I/usr/include -I/usr/include -DKCOREADDONS_LIB -DKGUIADDONS_LIB 
> -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG\
>  -DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB 
> -D_GNU_SOURCE -D_LARGEFILE64_SOURCE --include 
> /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/ksty\
> le/breeze_autogen/moc_predefs.h -o 
> 

Re: [gentoo-user] Nvidia proprietary driver broken

[Alexander Kapshuk]

On Wed, Oct 10, 2018 at 11:06 PM Christoph Böhmwalder
 wrote:
>
> Hi,
>
> Since the last kernel update (?), my Nvidia driver refuses to load:
>
> [   74.675437] udevd[3315]: worker [3376] /module/nvidia is taking a long time
> [   74.675445] udevd[3315]: worker [3377] 
> /devices/pci:00/:00:03.0/:03:00.0 is taking a long time
> [  193.411394] udevd[3376]: timeout 'nvidia-udev.sh add'
> [  193.411409] udevd[3376]: slow: 'nvidia-udev.sh add' [3544]
> [  194.412484] udevd[3376]: timeout: killing 'nvidia-udev.sh add' [3544]
> [  194.412504] udevd[3376]: slow: 'nvidia-udev.sh add' [3544]
> [  194.412668] udevd[3376]: 'nvidia-udev.sh add' [3544] terminated by signal 
> 9 (Killed)
> [  197.415861] udevd[3315]: worker [3377] 
> /devices/pci:00/:00:03.0/:03:00.0 timeout; kill it
> [  197.415875] udevd[3315]: seq 2089 
> '/devices/pci:00/:00:03.0/:03:00.0' killed
> [  616.150724] udevd[3315]: specified group 'render' unknown
>
> I haven't done a kernel update in a while, and I'm pretty sure I was
> running 4.17.3 before. After updating to 4.18.11 things started to
> break.
>
> I've also tried a more recent kernel (4.18.13) and a much older LTS
> kernel (4.14.75), of course recompiling the module every time.
>
> I'm using the default genkernel config minus Nouveau, so this is my
> procedure:
>
> # genkernel --menuconfig all
> (disable nouveau)
> # grub-mkconfig -o /boot/grub/grub.cfg
> # emerge -av @module-rebuild
> # reboot
>
> Any ideas on what could be wrong?
>
> Thanks!
>
> --
> Christoph
>

Here's a link to a Gentoo Bugzilla report for the issue in question:
https://bugs.gentoo.org/667362

With a workaround suggested.

Re: [gentoo-user] profile-sync-daemon "bad substitution" at boot

[Alexander Kapshuk]

On Thu, Sep 6, 2018 at 11:18 AM Alexander Kapshuk
 wrote:
>
> On Thu, Sep 6, 2018 at 10:48 AM Samuraiii  wrote:
> >
> > On 5.9.2018 21:20, Mick wrote:
> >
> > Hi All,
> >
> > I just noticed a psd error at boot time:
> >
> > /usr/bin/profile-sync-daemon: line 325: ${#DIRArr[@]##*/}: bad substitution
> >
> > Any idea what's brought this about?
> >
> > Hi,
> >
> > my bet is that your /bin/sh != /bin/bash and /usr/bin/profile-sync-daemon 
> > starts with #!/bin/sh.
> >
> > The other way around /usr/bin/profile-sync-daemon contains bashishms.
> >
> > You can try (as a test) to change #!/bin/sh for #!/bin/bash...
> >
> > S
>
> The shebang in the master repository is '#!/bin/bash'.
> https://raw.githubusercontent.com/graysky2/profile-sync-daemon/master/common/profile-sync-daemon.in
>
> The error message is a shell parameter expansion syntax error, which
> comprises two different expansion constructs referenced below.
> ${#parameter}
> String Length.
>
> ${parameter##[word]}
> Remove Largest Prefix Pattern.
>
> See section 2.6.2 Parameter Expansion,
> http://pubs.opengroup.org/onlinepubs/9699919799/nframe.html.
>
> The script in the master repository referenced above does not contain
> the line in question. It has '${#DIRArr[@]/}' and '${DIRArr[@]##*/}'.

This appears to have been reported as a bug in Debian [1]
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839049
And applied upstream [2].
https://github.com/graysky2/profile-sync-daemon/pull/185/files/654f5359abfe7aab2e1616dd74c8ba0f76ce4ab4

Re: [gentoo-user] profile-sync-daemon "bad substitution" at boot

[Alexander Kapshuk]

On Thu, Sep 6, 2018 at 10:48 AM Samuraiii  wrote:
>
> On 5.9.2018 21:20, Mick wrote:
>
> Hi All,
>
> I just noticed a psd error at boot time:
>
> /usr/bin/profile-sync-daemon: line 325: ${#DIRArr[@]##*/}: bad substitution
>
> Any idea what's brought this about?
>
> Hi,
>
> my bet is that your /bin/sh != /bin/bash and /usr/bin/profile-sync-daemon 
> starts with #!/bin/sh.
>
> The other way around /usr/bin/profile-sync-daemon contains bashishms.
>
> You can try (as a test) to change #!/bin/sh for #!/bin/bash...
>
> S

The shebang in the master repository is '#!/bin/bash'.
https://raw.githubusercontent.com/graysky2/profile-sync-daemon/master/common/profile-sync-daemon.in

The error message is a shell parameter expansion syntax error, which
comprises two different expansion constructs referenced below.
${#parameter}
String Length.

${parameter##[word]}
Remove Largest Prefix Pattern.

See section 2.6.2 Parameter Expansion,
http://pubs.opengroup.org/onlinepubs/9699919799/nframe.html.

The script in the master repository referenced above does not contain
the line in question. It has '${#DIRArr[@]/}' and '${DIRArr[@]##*/}'.

Re: [gentoo-user] kdevelop broken (llvm slot issue)

[Alexander Puchmayr]

Am Sonntag, 19. August 2018, 17:57:55 CEST schrieb Andrew Udvare:
> 
> I am not having issues with KDevelop with Clang support and I have
> everything on the latest version:
> 
> LLVM 6.0.1-r1 libffi ncurses
> Clang 6.0.1 +static-analyzer LLVM_TARGETS="AMDGPU BPF NVPTX X86"
> KDevelop 5.2.3 gdbui hex plasma qmake welcomepage
> kDevelop-php 5.2.3
> kdevelop-python 5.2.3
> Mesa 18.* classic dri3 egl gallium gbm gles2 llvm wayland
> 

Thanks for the quick response. Upgrading to mesa 18 solves the problem.

Regards
Alex

[gentoo-user] kdevelop broken (llvm slot issue)

[Alexander Puchmayr]

Hi there,

After recent upgrades of mesa, llvm, clang etc kdevelop does not work anymore. 
It crashes immediately after start with errors 

: CommandLine Error: Option 'help-list' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options

This issue is covered by bug https://bugs.gentoo.org/651658, which is open 
since March 2018 and no progress since also March 2018.

It seems as if multiple slots of llvm cause the problems. mesa pulls in llvm:
5, while other programs pull in llvm:6 (via clang:6)

Does anyone have an idea how to get a working kdevelop again?

Regards
Alex

Re: [gentoo-user] x86.c:(.text+0xb2): undefined reference to `l1tf_vmx_mitigation' with linux kernel 4.18.1

[Alexander Kapshuk]

On Fri, Aug 17, 2018 at 8:58 AM Alexander Kapshuk
 wrote:
>
> On Fri, Aug 17, 2018 at 8:57 AM Alexander Kapshuk
>  wrote:
> >
> > On Fri, Aug 17, 2018 at 8:10 AM  wrote:
> > >
> > > On 08/17 02:53, Adam Carter wrote:
> > > > On Fri, Aug 17, 2018 at 1:15 PM,  wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > CPU bugs seem to be more and more common:
> > > > > https://www.heise.de/security/meldung/Linux-Kernel-und-
> > > > > Distributionen-schuetzen-vor-Prozessorluecke-Foreshadow-L1TF-4137264.html
> > > > > https://www.heise.de/security/meldung/Spectre-NG-Foreshadow-
> > > > > gefaehrdet-Intel-Prozessoren-4137209.html
> > > > > (sorry, I only know of this german spoken references...)
> > > > >
> > > > > With Linux kernel 4.18.1 Linus has introduced a fix (aka workaround)
> > > > > of the  Foreshadow bug.
> > > > >
> > > >
> > > >  4.18, 4.17, 4.14, 4.9, and 4.4 have all had the fixes applied.
> > > >
> > > > >
> > > > > Unfortunately compiling that kernel (as downloaded from
> > > > > https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/ )
> > > > >
> > > > > gives me this bug:
> > > > >
> > > >
> > > > gentoo-sources with gcc 7.3 builds fine for me.
> > > >
> > > > Intel: grep . /sys/devices/system/cpu/vulnerabilities/*
> > > > /sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion
> > > > /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
> > > > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > > > Speculative Store Bypass disabled via prctl and seccomp
> > > > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > > > pointer sanitization
> > > > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full 
> > > > generic
> > > > retpoline, IBPB, IBRS_FW
> > > >
> > > > AMD: grep . /sys/devices/system/cpu/vulnerabilities/*
> > > > /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected
> > > > /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected
> > > > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > > > Speculative Store Bypass disabled via prctl and seccomp
> > > > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > > > pointer sanitization
> > > > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full AMD
> > > > retpoline, IBPB
> > >
> > > Hi,
> > >
> > > I am happy, that other sources do work for you Adam.
> > >
> > > Interesting would be, why the original sources does not compile for
> > > me.
> > > Any idea?
> > >
> > >
> > >
> >
> > This problem has been reported upstream. See below.
> > https://lkml.org/lkml/2018/8/15/118
> >
> > In particular:
> >
> > Build is successful with
> > CONFIG_KVM=y
> > CONFIG_KVM_INTEL=y
> > CONFIG_KVM_AMD=y
> > but fails if only
> > CONFIG_KVM=y
> > CONFIG_KVM_AMD=y
> > are selected.
>
> And a follow up email with a reference to a patch that addresses the issue:
> https://lkml.org/lkml/2018/8/15/122

The patch in question will become available in 4.18.2 upstream. See
the link below.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-4.18.y=eca268a3133cafcd188d85489f08a7c5907d985d

Re: [gentoo-user] x86.c:(.text+0xb2): undefined reference to `l1tf_vmx_mitigation' with linux kernel 4.18.1

[Alexander Kapshuk]

On Fri, Aug 17, 2018 at 8:57 AM Alexander Kapshuk
 wrote:
>
> On Fri, Aug 17, 2018 at 8:10 AM  wrote:
> >
> > On 08/17 02:53, Adam Carter wrote:
> > > On Fri, Aug 17, 2018 at 1:15 PM,  wrote:
> > >
> > > > Hi,
> > > >
> > > > CPU bugs seem to be more and more common:
> > > > https://www.heise.de/security/meldung/Linux-Kernel-und-
> > > > Distributionen-schuetzen-vor-Prozessorluecke-Foreshadow-L1TF-4137264.html
> > > > https://www.heise.de/security/meldung/Spectre-NG-Foreshadow-
> > > > gefaehrdet-Intel-Prozessoren-4137209.html
> > > > (sorry, I only know of this german spoken references...)
> > > >
> > > > With Linux kernel 4.18.1 Linus has introduced a fix (aka workaround)
> > > > of the  Foreshadow bug.
> > > >
> > >
> > >  4.18, 4.17, 4.14, 4.9, and 4.4 have all had the fixes applied.
> > >
> > > >
> > > > Unfortunately compiling that kernel (as downloaded from
> > > > https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/ )
> > > >
> > > > gives me this bug:
> > > >
> > >
> > > gentoo-sources with gcc 7.3 builds fine for me.
> > >
> > > Intel: grep . /sys/devices/system/cpu/vulnerabilities/*
> > > /sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion
> > > /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
> > > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > > Speculative Store Bypass disabled via prctl and seccomp
> > > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > > pointer sanitization
> > > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full 
> > > generic
> > > retpoline, IBPB, IBRS_FW
> > >
> > > AMD: grep . /sys/devices/system/cpu/vulnerabilities/*
> > > /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected
> > > /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected
> > > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > > Speculative Store Bypass disabled via prctl and seccomp
> > > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > > pointer sanitization
> > > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full AMD
> > > retpoline, IBPB
> >
> > Hi,
> >
> > I am happy, that other sources do work for you Adam.
> >
> > Interesting would be, why the original sources does not compile for
> > me.
> > Any idea?
> >
> >
> >
>
> This problem has been reported upstream. See below.
> https://lkml.org/lkml/2018/8/15/118
>
> In particular:
>
> Build is successful with
> CONFIG_KVM=y
> CONFIG_KVM_INTEL=y
> CONFIG_KVM_AMD=y
> but fails if only
> CONFIG_KVM=y
> CONFIG_KVM_AMD=y
> are selected.

And a follow up email with a reference to a patch that addresses the issue:
https://lkml.org/lkml/2018/8/15/122

Re: [gentoo-user] x86.c:(.text+0xb2): undefined reference to `l1tf_vmx_mitigation' with linux kernel 4.18.1

[Alexander Kapshuk]

On Fri, Aug 17, 2018 at 8:10 AM  wrote:
>
> On 08/17 02:53, Adam Carter wrote:
> > On Fri, Aug 17, 2018 at 1:15 PM,  wrote:
> >
> > > Hi,
> > >
> > > CPU bugs seem to be more and more common:
> > > https://www.heise.de/security/meldung/Linux-Kernel-und-
> > > Distributionen-schuetzen-vor-Prozessorluecke-Foreshadow-L1TF-4137264.html
> > > https://www.heise.de/security/meldung/Spectre-NG-Foreshadow-
> > > gefaehrdet-Intel-Prozessoren-4137209.html
> > > (sorry, I only know of this german spoken references...)
> > >
> > > With Linux kernel 4.18.1 Linus has introduced a fix (aka workaround)
> > > of the  Foreshadow bug.
> > >
> >
> >  4.18, 4.17, 4.14, 4.9, and 4.4 have all had the fixes applied.
> >
> > >
> > > Unfortunately compiling that kernel (as downloaded from
> > > https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/ )
> > >
> > > gives me this bug:
> > >
> >
> > gentoo-sources with gcc 7.3 builds fine for me.
> >
> > Intel: grep . /sys/devices/system/cpu/vulnerabilities/*
> > /sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion
> > /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
> > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > Speculative Store Bypass disabled via prctl and seccomp
> > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > pointer sanitization
> > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic
> > retpoline, IBPB, IBRS_FW
> >
> > AMD: grep . /sys/devices/system/cpu/vulnerabilities/*
> > /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected
> > /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected
> > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > Speculative Store Bypass disabled via prctl and seccomp
> > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > pointer sanitization
> > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full AMD
> > retpoline, IBPB
>
> Hi,
>
> I am happy, that other sources do work for you Adam.
>
> Interesting would be, why the original sources does not compile for
> me.
> Any idea?
>
>
>

This problem has been reported upstream. See below.
https://lkml.org/lkml/2018/8/15/118

In particular:

Build is successful with
CONFIG_KVM=y
CONFIG_KVM_INTEL=y
CONFIG_KVM_AMD=y
but fails if only
CONFIG_KVM=y
CONFIG_KVM_AMD=y
are selected.

Re: [gentoo-user] vlc failed to compile

[Alexander Kapshuk]

On Tue, Jul 10, 2018 at 3:00 PM gevisz  wrote:
>
> 2018-07-10 12:58 GMT+03:00 Alexander Kapshuk :
> > On Tue, Jul 10, 2018 at 12:42 PM gevisz  wrote:
> >>
> >> In today's update vlc failed to compile.
> >>
> >> What shall I do?
> >>
> >
> > Rebuild libebml:
> > emerge -1 libebml
> >
> > See 
> > https://forums.gentoo.org/viewtopic-p-8184582.html?sid=f451f5dcad08d0eba731189fa8480c77
>
> It has helped. Thank you.
>

Good to hear. Thanks for letting us know.

Re: [gentoo-user] vlc failed to compile

[Alexander Kapshuk]

On Tue, Jul 10, 2018 at 12:42 PM gevisz  wrote:
>
> In today's update vlc failed to compile:
>
> make[4]: Leaving directory
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3/modules'
> make[3]: *** [Makefile:26145: all-recursive] Error 1
> make[3]: Leaving directory
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3/modules'
> make[2]: *** [Makefile:11238: all] Error 2
> make[2]: Leaving directory
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3/modules'
> make[1]: *** [Makefile:1530: all-recursive] Error 1
> make[1]: Leaving directory
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3'
> make: *** [Makefile:1415: all] Error 2
>  * ERROR: media-video/vlc-3.0.3-r1::gentoo failed (compile phase):
>  *   emake failed
>  *
>  * If you need support, post the output of `emerge --info
> '=media-video/vlc-3.0.3-r1::gentoo'`,
>  * the complete build log and the output of `emerge -pqv
> '=media-video/vlc-3.0.3-r1::gentoo'`.
>  * The complete build log is located at
> '/var/log/portage/media-video:vlc-3.0.3-r1:20180710-081824.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/temp/environment'.
>  * Working directory: 
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3'
>  * S: '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3'
>
> >>> Failed to emerge media-video/vlc-3.0.3-r1, Log file:
>
> >>>  '/var/log/portage/media-video:vlc-3.0.3-r1:20180710-081824.log'
>
> What shall I do?
>

Rebuild libebml:
emerge -1 libebml

See 
https://forums.gentoo.org/viewtopic-p-8184582.html?sid=f451f5dcad08d0eba731189fa8480c77

Re: [gentoo-user] how to set python version for one user

[Alexander Kapshuk]

On Tue, Jul 10, 2018 at 11:23 AM  wrote:
>
> Hi,
>
> I need to set specific python version to a user and I don't want to set
> it up for whole system. Is it possible? If so how to do it. All I found
> is about setting for whole system.
>
> Thanks
>
> Pat
>
> 
> Freehosting PIPNI - http://www.pipni.cz/
>
>
How about this?
echo alias python='python2.7' >> ~user/.bash_profile

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Thu, Jun 14, 2018 at 7:56 PM Ian Zimmerman  wrote:
>
> On 2018-06-13 20:29, Alexander Kapshuk wrote:
>
> > 4.9.108 is out with some objtool fixes among other things. See the
> > change log for details.
> > https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.108
> >
> > Want to give this kernel a try and seen if it fixes the issues you were 
> > having?
>
> 4.9.108 didn't solve the problem.  But I installed 4.14.49 and it behaves.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

Good to hear. Thanks for letting us know.

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Tue, Jun 12, 2018 at 5:54 PM Ian Zimmerman  wrote:
>
> On 2018-06-12 09:56, Alexander Kapshuk wrote:
>
> > Any reason you're trying to load those modules by hand rather then
> > have them loaded for you automatically?
>
> The only one I try to "load by hand" (rather: via conf.d/modules) is
> fbcon, because IME that is how I actually get a framebuffer console.  Is
> there a better way?
>
> But there were other modules, including network drivers, that produced
> the same error, despite getting autoloaded.  Not all modules, though.
>
> > Did dmesg have any more info on the failing modules?
>
> I will report on this when I can play the reboot game again, which may
> be a few days yet.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

4.9.108 is out with some objtool fixes among other things. See the
change log for details.
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.108

Want to give this kernel a try and seen if it fixes the issues you were having?

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Tue, Jun 12, 2018 at 8:54 AM Ian Zimmerman  wrote:
>
> On 2018-06-12 08:23, Alexander Kapshuk wrote:
>
> > Looks like I'd have to build kernel 4.9.107 in an environment
> > resembling yours to try and reproduce the behavior in question.
> > What is the version of kmods you have installed on your system?
> > What's the output of 'emerge --info'?
>
> https://gist.github.com/nobrowser/314da0f994ce134e3d554cc4cfed266e
>
> BTW, why are you so interested in this?  It seems to me to be purely a
> kernel/kernel tools problem.  What is the gentoo angle?
>
> Of course I'm not complaining that you're trying to help - thanks a lot.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

I do programming for a living with an interest in kernel programming.
I'm not a Gentoo developer and I'm not doing this on behalf of the
Gentoo Foundation.
I was just l curious to find out what could have caused the issue
you're having and if possible to try and come up with a fix.

I can't promise I will be able to fix this for you. Chances are, the
next kmods and/or kernel upgrade will  have fixed this for you.

Any reason you're trying to load those modules by hand rather then
have them loaded for you automatically?
Did dmesg have any more info on the failing modules?

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Mon, Jun 11, 2018 at 6:09 PM Ian Zimmerman  wrote:
>
> On 2018-06-09 18:51, Alexander Kapshuk wrote:
>
> > readelf -h /path/to/module.ko
>
> ELF Header:
>   Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
>   Class: ELF64
>   Data:  2's complement, little endian
>   Version:   1 (current)
>   OS/ABI:UNIX - System V
>   ABI Version:   0
>   Type:  REL (Relocatable file)
>   Machine:   Advanced Micro Devices X86-64
>   Version:   0x1
>   Entry point address:   0x0
>   Start of program headers:  0 (bytes into file)
>   Start of section headers:  52808 (bytes into file)
>   Flags: 0x0
>   Size of this header:   64 (bytes)
>   Size of program headers:   0 (bytes)
>   Number of program headers: 0
>   Size of section headers:   64 (bytes)
>   Number of section headers: 23
>   Section header string table index: 22
>
> This was less frustrating than the other times as I didn't have to
> reboot back and forth, so you need not feel guilty about it.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

Hmm...

Looks like I'd have to build kernel 4.9.107 in an environment
resembling yours to try and reproduce the behavior in question.
What is the version of kmods you have installed on your system?
What's the output of 'emerge --info'?

In the meantime, see this email exchange [1] that  might be relevant
to the problem you're having.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857354#10

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Sat, Jun 9, 2018 at 5:26 PM Ian Zimmerman  wrote:
>
> On 2018-06-09 14:15, Alexander Kapshuk wrote:
>
> > I had a look at the source code for kmod-25. If I read it right, dmesg
> > should have records along the lines of:
> > kmod-25/libkmod/libkmod-module.c:886:   INFO(mod->ctx, "Failed
> > to insert module '%s': %m\n", path);
> >
> > modprobe returns Exec format error.
>
> > Now, if my understanding of the source code above is right, you either
> > have CONFIG_X86_32 set in your kernel, e.i. your Elf_Ehdr is set to
> > Elf32_Ehdr, or the module's header is for the architecture that is
> > different from what is expected by the kernel.
>
> The former is definitely false.  If the latter holds, it is not due to
> any action on my part, but due to how the module is built by the kernel
> build system (at the same time as the kernel proper).  Again, I strongly
> suspect this is due to all the "objtool" churn in 4.9.106 and later.
>
> I'm afraid I'm at the limit of my patience diving into this for now.
> You see, I have to remove the broken kernel from grub manually every
> time (and then re-add it for another test), otherwise it breaks
> unattended boots.
>
> Sorry about that.  Maybe in a few days I'll have time to sit down and
> track it properly.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

I appreciate that this has been a frustrating experience for you, but
when you get a change, could you please run 'readelf -h' on the module
concerned and show the output below:
readelf -h /path/to/module.ko
ELF Header:
Magic:
Class:
Machine:
Size of this header:

This will either confirm or refute my assumption about the ELF header
being the wrong size and causing the 'Exec format error' message to be
printed.

Thanks.

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Sat, Jun 9, 2018 at 8:56 AM Alexander Kapshuk
 wrote:
>
>
>
> On Sat, Jun 9, 2018, 07:34 Ian Zimmerman  wrote:
>>
>> On 2018-06-08 22:38, Alexander Kapshuk wrote:
>>
>> > On Fri, Jun 8, 2018, 22:30 Ian Zimmerman  wrote:
>> >
>> > > On 2018-06-08 22:00, Alexander Kapshuk wrote:
>> > >
>> > > > What's the output of:
>> > > > uname -r
>> > > > strings /path/to/your/module.ko | grep vermagic=
>> > >
>> > > Here are the results for 4.9.105 (working):
>> > >
>> > >  matica!6 ~$ uname -r
>> > > 4.9.105
>> > >  matica!7 ~$ strings
>> > >  /lib64/modules/4.9.105/kernel/drivers/video/console/fbcon.ko |
>> > >  fgrep -e 'vermagic='
>> > > vermagic=4.9.105 SMP
>> > >
>> > > Let me know if you need to see the ones for the broken kernel ...
>> > >
>> >
>> > Yes, we want to make sure the vermagic of the modules you're trying to load
>> > matches the output of uname -r of the running kernel.
>>
>> Ok, here:
>>
>> Script started on 2018-06-08 21:11:04-0700
>>  matica!501 ~# ls -l 
>> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon.ko
>> -rw-r--r-- 1 root root 54280 Jun  8 20:57 
>> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon.ko
>>  matica!502 ~# uname -r
>> 4.9.107
>>  matica!503 ~# strings 
>> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon
>> .ko | fgrep -e 'vermagic='
>> vermagic=4.9.107 SMP
>>  matica!504 ~# modprobe fbcon
>> modprobe: ERROR: could not insert 'fbcon': Exec format error
>>  matica!505 ~# exit
>>
>> Script done on 2018-06-08 21:14:46-0700
>>
>> Sorry to ruin the low-hanging hypothesis :-P
>>
>
> Did dmesg have anything useful to say other than exec format error?
> Have you tried insmod'ing the modules instead of modprobe'ing them?
>>
>>
>> --

I had a look at the source code for kmod-25. If I read it right, dmesg
should have records along the lines of:
kmod-25/libkmod/libkmod-module.c:886:   INFO(mod->ctx, "Failed
to insert module '%s': %m\n", path);

modprobe returns Exec format error.

errno -l | grep 'Exec format error'
ENOEXEC 8 Exec format error

/usr/include/asm-generic/errno-base.h:
#define   ENOEXEC  8  /* Exec format error */

Here's the execution path I've been able to follow:
insmod()->kmod_module_probe_insert_module()->kmod_module_insert_module()->init_module()->copy_module_from_user();

init_module(2):
http://man7.org/linux/man-pages/man2/init_module.2.html
ENOEXEC
  The binary image supplied in module_image is not an ELF image,
  or is an ELF image that is invalid or for a different
  architecture.

(1). kmod-25/tools/modprobe.c
ENOEXEC returned by kmod_module_probe_insert_module().
static int insmod(struct kmod_ctx *ctx, const char *alias,
const char *extra_options)
{
...
kmod_list_foreach(l, list) {
...
if (lookup_only)
printf("%s\n", kmod_module_get_name(mod));
else {
err = kmod_module_probe_insert_module(mod, flags,
extra_options, NULL, NULL, show);
}

if (err >= 0)
/* ignore flag return values such as a mod being blacklisted */
err = 0;
else {
switch (err) {
...
default:
ERR("could not insert '%s': %s\n", <- the error message reported by modprobe
kmod_module_get_name(mod),
strerror(-err));
break;
}
}

(2). kmod-25/libkmod/libkmod-module.c
KMOD_EXPORT int kmod_module_probe_insert_module(struct kmod_module *mod,
unsigned int flags, const char *extra_options,
int (*run_install)(struct kmod_module *m,
const char *cmd, void *data),
const void *data,
void (*print_action)(struct kmod_module *m,
bool install,
const char *options))
{
...
if (!(flags & KMOD_PROBE_DRY_RUN))
err = kmod_module_insert_module(m, flags,
options);
}
...
}

(3). KMOD_EXPORT int kmod_module_insert_module(struct kmod_module *mod,
unsigned int flags,
const char *options)
{
...
size = kmod_file_get_size(mod->file); <- the size of your modules elf file
...
err = init_module(mem, size, args);
...
}

(4). [init_module syscall]
kernel/module.c
SYSCALL_DEFINE3(init_module, void __user *, umod,
unsigned long, len, const char __user *, uargs)
{
int err;
struct load_info info = { };

err = may_init_module();
if (err)
return err;

pr_debug("init_module: umod=%p, len=%lu, uargs=%p\n",
   umod, len, uargs);

err = copy_module_from_user(umod, len, );
if (err)
return err;

return load_module(, uargs, 0);
}

(5). kernel/module.c
/* Sets info->hdr and info->len. */
static int copy_module_from_user(con

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Sat, Jun 9, 2018, 07:34 Ian Zimmerman  wrote:

> On 2018-06-08 22:38, Alexander Kapshuk wrote:
>
> > On Fri, Jun 8, 2018, 22:30 Ian Zimmerman  wrote:
> >
> > > On 2018-06-08 22:00, Alexander Kapshuk wrote:
> > >
> > > > What's the output of:
> > > > uname -r
> > > > strings /path/to/your/module.ko | grep vermagic=
> > >
> > > Here are the results for 4.9.105 (working):
> > >
> > >  matica!6 ~$ uname -r
> > > 4.9.105
> > >  matica!7 ~$ strings
> > >  /lib64/modules/4.9.105/kernel/drivers/video/console/fbcon.ko |
> > >  fgrep -e 'vermagic='
> > > vermagic=4.9.105 SMP
> > >
> > > Let me know if you need to see the ones for the broken kernel ...
> > >
> >
> > Yes, we want to make sure the vermagic of the modules you're trying to
> load
> > matches the output of uname -r of the running kernel.
>
> Ok, here:
>
> Script started on 2018-06-08 21:11:04-0700
>  matica!501 ~# ls -l
> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon.ko
> -rw-r--r-- 1 root root 54280 Jun  8 20:57
> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon.ko
>  matica!502 ~# uname -r
> 4.9.107
>  matica!503 ~# strings
> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon
> .ko | fgrep -e 'vermagic='
> vermagic=4.9.107 SMP
>  matica!504 ~# modprobe fbcon
> modprobe: ERROR: could not insert 'fbcon': Exec format error
>  matica!505 ~# exit
>
> Script done on 2018-06-08 21:14:46-0700
>
> Sorry to ruin the low-hanging hypothesis :-P
>
>
Did dmesg have anything useful to say other than exec format error?
Have you tried insmod'ing the modules instead of modprobe'ing them?

>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>
>

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Fri, Jun 8, 2018, 22:30 Ian Zimmerman  wrote:

> On 2018-06-08 22:00, Alexander Kapshuk wrote:
>
> > What's the output of:
> > uname -r
> > strings /path/to/your/module.ko | grep vermagic=
>
> Here are the results for 4.9.105 (working):
>
>  matica!6 ~$ uname -r
> 4.9.105
>  matica!7 ~$ strings
>  /lib64/modules/4.9.105/kernel/drivers/video/console/fbcon.ko |
>  fgrep -e 'vermagic='
> vermagic=4.9.105 SMP
>
> Let me know if you need to see the ones for the broken kernel ...
>

Yes, we want to make sure the vermagic of the modules you're trying to load
matches the output of uname -r of the running kernel.



> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>
>

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Fri, Jun 8, 2018 at 7:37 PM Ian Zimmerman  wrote:
>
> On 2018-06-08 09:22, Alexander Kapshuk wrote:
>
> > >  matica!501 ~# modprobe fbcon
> > > modprobe: ERROR: could not insert 'fbcon': Exec format error
>
> > Could this be a multilib issue? Does you kernel have
> > CONFIG_IA32_EMULATION enabled?
> > See https://forums.gentoo.org/viewtopic-p-7647744.html.
>
> CONFIG_IA32_EMULATION is definitely set in the _current_ working kernel
> (ie. 4.9.105), and I use the working config-* file as the start for the
> new one (with make oldconfig), so unless there was a radical change in
> the kernel build, this doesn't look like a possible cause.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

What's the output of:
uname -r
strings /path/to/your/module.ko | grep vermagic=

Re: [gentoo-user] Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Thu, Jun 7, 2018 at 11:45 PM Ian Zimmerman  wrote:
>
> I cannot get either 4.9.106 or 4.9.107 to work on my amd64 system at
> all.  It seems some (but not all) modules refuse to load:
>
> Script started on 2018-06-07 13:31:28-0700
>  matica!501 ~# modprobe fbcon
> modprobe: ERROR: could not insert 'fbcon': Exec format error
>  matica!502 ~# ls /usr/lib/modules/4.9.106/kernel/sound/
> core/ hda/  pci/  soundcore.ko
>  matica!502 ~# ls /lib/modules/4.9.106/kernel/sound/hda/
> snd-hda-core.ko
>  matica!503 ~# modprobe snd-hda-core
> modprobe: ERROR: could not insert 'snd_hda_core': Exec format error
>  matica!504 ~# exit
> Script done on 2018-06-07 13:32:56-0700
>
> I am pretty sure this is caused by:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=b790b4f22a165e85f0b53a3231764034e42c7ea6
>
> Wth can I do about it?  Wait for an updated kmod package?  How long will
> that take?
>
> I run without initramfs, gcc version is 6.4.0-r1
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

Could this be a multilib issue? Does you kernel have
CONFIG_IA32_EMULATION enabled?
See https://forums.gentoo.org/viewtopic-p-7647744.html.

Re: [gentoo-user] OT: Extracting year from data, but honour empty lines

[Alexander Kapshuk]

On Sat, May 12, 2018 at 2:16 AM, Daniel Frey  wrote:
> Hi all,
>
> I am trying to do something relatively simple and I've had something
> working in the past, but my brain just doesn't want to work today.
>
> I have a text file with the following (this is just a subset of about
> 2500 dates, and I don't want to edit these all by hand if I can avoid it):
>
> --- START ---
> December 2, 1994
> March 27, 1992
> June 4, 1994
> 1993
> January 11, 1992
> January 3, 1995
>
>
> March 12, 1993
> July 12, 1991
> May 17, 1991
> August 7, 1992
> December 23, 1994
> March 27, 1992
> March 1995
> --- END ---
>
> As you can see, there's no standard in the way the date is formatted.
> Some of them are also formatted -MM-DD and MM-DD-.
>
> I have a basic grep that I tossed together:
>
> grep -o '\([0-9]\{4\}\)'
>
> This does extract the year but yields the following:
>
> 1994
> 1992
> 1994
> 1993
> 1992
> 1995
> 1993
> 1991
> 1991
> 1992
> 1994
> 1992
> 1995
>
> As you can see, the two empty lines are removed but this will cause
> problems with data not lining up later on.
>
> Does anyone have a quick tip for my tired brain to make this work and
> just output a blank line if there's no match? I swear I did this months
> ago and had something working but I apparently didn't bother saving the
> script I made. Argh!
>
> Dan
>

Here's an awk and sed scripts for you to try:
cat dates
December 2, 1994
March 27, 1992
June 4, 1994
1993
January 11, 1992
January 3, 1995


March 12, 1993
July 12, 1991
May 17, 1991
August 7, 1992
December 23, 1994
March 27, 1992
March 1995

2018-05-12
05-12-2018

awk 'match($0,/[0-9][0-9][0-9][0-9]/){
print substr($0, RSTART, RLENGTH)
}
/^$/
' dates

1994
1992
1994
1993
1992
1995


1993
1991
1991
1992
1994
1992
1995

2018
2018

sed 's/.*\([0-9][0-9][0-9][0-9]\).*/\1/p
/^$/p
d' dates

1994
1992
1994
1993
1992
1995


1993
1991
1991
1992
1994
1992
1995

2018
2018

Re: [gentoo-user] Kernel compile error

[Alexander Kapshuk]

On Wed, Apr 25, 2018 at 10:03 AM, Klaus Ethgen  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi,
>
> I stumbled into the next problem.
>
> I do have a decent kernel compile knowledge but that seems to be gentoo
> specific.
>
> I have a old i686 machine where I installed gentoo on. Now when I did
> the kernel the first time, it worked well. everything fine exept some
> minor stuff (see below).
>--- /etc/kernels/kernel-config-x86-4.9.76-gentoo-r1 2018-04-25 
> 07:48:25.735961235 +0100
>+++ .config 2018-04-25 07:48:25.830960047 +0100
>@@ -480,7 +480,6 @@
> # CONFIG_PHYS_ADDR_T_64BIT is not set
> CONFIG_BOUNCE=y
> CONFIG_VIRT_TO_BUS=y
>-CONFIG_MMU_NOTIFIER=y
> # CONFIG_KSM is not set
> CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
> # CONFIG_TRANSPARENT_HUGEPAGE is not set
>@@ -1528,7 +1527,7 @@
> # CONFIG_DM_THIN_PROVISIONING is not set
> # CONFIG_DM_CACHE is not set
> # CONFIG_DM_ERA is not set
>-# CONFIG_DM_MIRROR is not set
>+CONFIG_DM_MIRROR=m
> # CONFIG_DM_RAID is not set
> # CONFIG_DM_ZERO is not set
> # CONFIG_DM_MULTIPATH is not set
>@@ -1805,8 +1804,8 @@
> #
> CONFIG_INPUT_MOUSEDEV=m
> # CONFIG_INPUT_MOUSEDEV_PSAUX is not set
>-CONFIG_INPUT_MOUSEDEV_SCREEN_X=1600
>-CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1200
>+CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
>+CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
> # CONFIG_INPUT_JOYDEV is not set
> CONFIG_INPUT_EVDEV=y
> # CONFIG_INPUT_EVBUG is not set
>@@ -2463,12 +2462,12 @@
> # CONFIG_AGP_ALI is not set
> # CONFIG_AGP_ATI is not set
> # CONFIG_AGP_AMD is not set
>-# CONFIG_AGP_AMD64 is not set
>+CONFIG_AGP_AMD64=y
> CONFIG_AGP_INTEL=y
> # CONFIG_AGP_NVIDIA is not set
>-# CONFIG_AGP_SIS is not set
>+CONFIG_AGP_SIS=y
> # CONFIG_AGP_SWORKS is not set
>-# CONFIG_AGP_VIA is not set
>+CONFIG_AGP_VIA=y
> # CONFIG_AGP_EFFICEON is not set
> CONFIG_INTEL_GTT=y
> CONFIG_VGA_ARB=y
>@@ -2489,7 +2488,7 @@
> # CONFIG_DRM_I2C_SIL164 is not set
> # CONFIG_DRM_I2C_NXP_TDA998X is not set
> CONFIG_DRM_RADEON=m
>-CONFIG_DRM_RADEON_USERPTR=y
>+# CONFIG_DRM_RADEON_USERPTR is not set
> # CONFIG_DRM_AMDGPU is not set
>
> #
>
> But now, when I try to compile the kernel, I get the following error:
>...
>make[2]: *** [scripts/kconfig/Makefile:39: silentoldconfig] Fehler 1
>make[1]: *** [Makefile:541: silentoldconfig] Fehler 2
>  SYSTBL  arch/x86/entry/syscalls/../../include/generated/asm/syscalls_32.h
>make: *** Keine Regel vorhanden, um das Ziel »include/config/auto.conf«,
>  benötigt von »include/config/kernel.release«, zu erstellen.  Schluss.
>make: *** Es wird auf noch nicht beendete Prozesse gewartet
>  SYSHDR  
> arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_32.h
>  SYSHDR  
> arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_64.h
>  SYSHDR  
> arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_x32.h
>* Gentoo Linux Genkernel; Version 3.4.52.4
>* Running with options: --btrfs --lvm --menuconfig 
> --kernel-cc=/usr/lib/ccache/bin/gcc all
>* Using genkernel.conf from /etc/genkernel.conf
>* Sourcing arch-specific config.sh from 
> /usr/share/genkernel/arch/x86/config.sh ..
>* Sourcing arch-specific modules_load from 
> /usr/share/genkernel/arch/x86/modules_load ..
>
>* ERROR: Failed to compile the "prepare" target...
>*
>* -- Grepping log... --
>*
>*
>* -- End log... --
>*
>* Please consult /var/log/genkernel.log for more information and any
>* errors that were reported above.
>*
>* Report any genkernel bugs to bugs.gentoo.org and
>* assign your bug to genker...@gentoo.org. Please include
>* as much information as you can in your bug report; attaching
>* /var/log/genkernel.log so that your issue can be dealt with effectively.
>*
>* Please do *not* report compilation failures as genkernel bugs!
>
> I even try to compile with exactly the same config that compiled some
> days before but got the same error.
>
> The installed kernel sources and genkernel are:
> [IP-] [  ] sys-kernel/genkernel-3.4.52.4-r2:0
> [IP-] [  ] sys-kernel/gentoo-sources-4.9.76-r1:4.9.76-r1
>
> As the error is completely without a meaning for me, maybe others have
> an Idea.
>
> Regards
>Klaus
> - --
> Klaus Ethgen   http://www.ethgen.ch/
> pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
> Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
> -BEGIN PGP SIGNATURE-
> Comment: Charset: ISO-8859-1
>
> iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlrgKDIACgkQpnwKsYAZ
> 9qyYvQwAtK+EA0Kv8Vt5443fml9mh0te6k/WUMlAps0u0Ds58NU+IBYebcLCasmM
> SG/SDjt/WSJCeb9LQ0w8W9xpi5NAn2HpUiKdpZHeyqiJ5EqHxE6qAMHbsdgSsybY
> 

Re: [gentoo-user] sddm no longer working

[Alexander Puchmayr]

Am Mittwoch, 4. April 2018, 17:20:17 CEST schrieb Jack:
> On 2018.04.04 11:14, Alexander Puchmayr wrote:
> > Hi there,
> > 
> > After last update, on one machine sddm-0.17.0-r1 no longer does not
> > anything anymore. Systemd starts the service, and systemctl status
> > shows that the sddm is running, and also ps jax shows a running sddm.
> > 
> > apollo ~ # systemctl status sddm
> > ● sddm.service - Simple Desktop Display Manager
> > 
> >Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor
> > 
> > preset: disabled)
> > 
> >Active: active (running) since Wed 2018-04-04 16:41:28 CEST; 2s ago
> >
> >  Docs: man:sddm(1)
> >  
> >man:sddm.conf(5)
> >  
> >  Main PID: 8350 (sddm)
> >  
> >CGroup: /system.slice/sddm.service
> >
> >└─8350 /usr/bin/sddm
> > 
> > Apr 04 16:41:28 apollo systemd[1]: Started Simple Desktop Display
> > Manager.
> > Apr 04 16:41:28 apollo sddm[8350]: Initializing...
> > Apr 04 16:41:28 apollo sddm[8350]: Logind interface found
> > Apr 04 16:41:28 apollo sddm[8350]: Starting...
> > 
> > But thats all. It does not create a log file (/var/log/sddm.log not
> > touched, no entry), it does not start X (no process). It seems like
> > sddm is starting and waiting for something I don't know.
> > 
> > Any ideas?
> > 
> > Thanks,
> > 
> > Alex
> 
> Can you start X manually?  Is there anything relevant in
> /var/log/Xorg.0.log?

Yes, I can start X manually, and it seems to work. But sddm does not even 
start X.

> Are all sddm config files OK?

I think so. They look the same as before the update (where it worked fine)

Alex

[gentoo-user] sddm no longer working

[Alexander Puchmayr]

Hi there,

After last update, on one machine sddm-0.17.0-r1 no longer does not anything 
anymore. Systemd starts the service, and systemctl status shows that the sddm 
is running, and also ps jax shows a running sddm. 

apollo ~ # systemctl status sddm
● sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor preset: 
disabled)
   Active: active (running) since Wed 2018-04-04 16:41:28 CEST; 2s ago
 Docs: man:sddm(1)
   man:sddm.conf(5)
 Main PID: 8350 (sddm)
   CGroup: /system.slice/sddm.service
   └─8350 /usr/bin/sddm

Apr 04 16:41:28 apollo systemd[1]: Started Simple Desktop Display Manager.
Apr 04 16:41:28 apollo sddm[8350]: Initializing...
Apr 04 16:41:28 apollo sddm[8350]: Logind interface found
Apr 04 16:41:28 apollo sddm[8350]: Starting...

But thats all. It does not create a log file (/var/log/sddm.log not touched, no 
entry), it does not start X (no process). It seems like sddm is starting and 
waiting for something I don't know.

Any ideas?

Thanks,
Alex

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Alexander Kapshuk]

On Tue, Mar 27, 2018 at 12:01 PM, Peter Humphrey  wrote:
> On Tuesday, 27 March 2018 01:24:09 BST Daniel Frey wrote:
>
>> I ran into this some time ago and one of the updates removed the /lib ->
>> /lib64 symlink.
>>
>> I simply ran `ln -s /lib64 /lib` and it was fine after that.
>
> Nice idea, Dan, but that isn't it in this case:
>
> # /bin/ls -ld /lib
> lrwxrwxrwx 1 root root 5 Mar 12 00:08 /lib -> lib64
>
> --
> Regards
> Peter
>
>

See if this post helps:
Failed to emerge sys-apps/sandbox-2.12:
https://forums.gentoo.org/viewtopic-t-1076582-start-0.html

Re: [gentoo-user] Nvidia kernel module API version mismatch

[Alexander Kapshuk]

On Thu, Mar 15, 2018 at 1:09 PM, Aleksander Okonski
 wrote:
> Hey,
>
> I have run into a strange problem with my nvidia drivers and gentoo. I am
> currently running kernel 4.14.14 and I upgraded my
> x11-drivers/nvidia-drivers to 390.42 from 390.25. Once the new drivers were
> installed I rebooted my laptop. Once rebooted I was unable to start the xorg
> server using startx and was greeted with errors. The /var/logs/xorg.0.log
> said that the problem was with the kernel module. Looking at dmesg I see
> that I am getting the error:
>
> NVRM: API mismatch: the client has the version 390.42, but this kernel
> module has version 390.25. please make sure that this kernel module and all
> NVIDIA driver components have the same version.
>
> I therefor thought that maybe I forgot to "emerge @module-rebuild" so I ran
> that and rebooted to make sure that everything was ok. However I am still
> getting the same problem.
>
> Looking at /usr/src/linux it is pointing to the correct kernel of 4.14.14
> and running "modinfo nvidia" it shows that "filename:
> /lib/modules/4/14/14-gentoo/video/nvidia.ko" and that version is 390.42.
> The other nvidia modules (nvidia-drm, nvidia-modeset, and nvidia-uvm) show
> that they are built for the correct kernel and that they are also version
> 390.42.
>
> I have tried to debug this issue however all the recourse that I was able to
> find mostly said to reboot or perform rmmod nvidia then modprobe nvidia.
> However when I try to rmmod nvidia it is dependent on nvidia-modeset and
> nvidia-drm. Trying to rmmod nvidia-drm will not work as I get the error
> "rmmod error: module nvidia_drm in in use".
>
> I therefor cannot understand why and where the error is coming from as it
> seems like the kernel has the correct nvidia modules loaded. Any ideas on
> how to fix it or any other suggestions?
>
> Thanks,
> Aleks

Just to clarify, does:
modinfo nvidia
display version 390.42 or 390.25?

Re: [gentoo-user] chromium-65.0.3325.146 compilation warnings

[Alexander Kapshuk]

On Mon, Mar 12, 2018 at 10:17 AM, Mick  wrote:
> I can see a few warnings pilling up on different systems when trying to emerge
> chromium-65.0.3325.146:
>
> warning: unknown warning option '-Wno-enum-compare-switch'; did you mean '-
> Wno-enum-compare'? [-Wunknown-warning-option]
> warning: unknown warning option '-Wno-tautological-unsigned-zero-compare' [-
> Wunknown-warning-option]
> warning: unknown warning option '-Wno-null-pointer-arithmetic'; did you mean
> '-Wno-null-arithmetic'? [-Wunknown-warning-option]
> warning: unknown warning option '-Wno-tautological-constant-compare'; did you
> mean '-Wno-tautological-pointer-compare'? [-Wunknown-warning-option]
> 4 warnings generated.
>
> Does this mean I should be using a different gcc or CFLAGS?
>
> They mostly are:
>
> CFLAGS="-march=native -O2 -pipe"
>
> --
> Regards,
> Mick

On my x86 system, I've been seeing similar warnings being generated by
clang when compiling the ffmpeg that comes with chromium.
I've also hit another bug related to that, where clang compilation
terminates with an error message along the lines of there being not
enough registers available.
There's a bug registered for that in chromium bugzilla, which I can't
reference at the moment. So far, no solution has been implemented, as
far as I could tell.

Re: [gentoo-user] [OT] Kinda "try ... catch" in a shell script...how

[Alexander Kapshuk]

On Sat, Mar 10, 2018 at 10:26 AM,   wrote:
> Hi,
>
> I have a coyple of files on my harddisk and on a mobile usb-disc.
>
> Their names are of that pattern:
>
>  something--something
>
> where 'soemthing' can be totally different from file to file and
> '' is a checksum, which does not match the checksum of the
> according file.
>
> I want to delete the files on my harddisk, which has a ''
> which matches the '' of the according file on the mobile
> harddisk.
>
> The problem arises from a line of the shellscript I wrote.
>
> # code to extract the checksum from the file and put into
> # a variable named crc
>
> if [ -f /*$crc* ] ; then
>
> # remove file on PC harddisk here
>
> fi
>
> As soon the file is not found, the script ends with an 'Not found'
> error, which '-f' is exactly for, because the expanding comes before
> the '-f'...
>
> So I need something else or a try-catch-thingy to make that work...but
> how?
>
> Or do I miss the forest for the trees here... ;)
>
> Thanks a lot for the forest in advance!
> Cheers
> Meino
>
>
>
>
>

If you were using a loop, you could do something like this:
for file in /path/to/files
do test -f $file || continue
rm $file
done

Care to post the entire script, so we could probably come up with the
right solution for you?

Re: [gentoo-user] Re: kernel choices for booting gentoo as guest in vbox vm

[Alexander Kapshuk]

On Fri, Feb 2, 2018 at 6:32 AM, Harry Putnam <rea...@newsguy.com> wrote:
> Alexander Kapshuk <alexander.kaps...@gmail.com> writes:
>
> [...]
>
>>> Can anyone tell me what they used to allow gentoo in vbox to boot?
>>>
>>>
>>>
>> Did you enable the recommended kernel config options as suggested here [1]?
>> [1] https://wiki.gentoo.org/wiki/VirtualBox
>
> I did go thru that page and `think' I checked them off but I came to
> that URL kind of late in the game... It would have no doubt went
> better if I'd caught that earlier on.
>
> It does appear to share some confusion with a couple of other pages.
> I don't have them to hand but one said flatly not to use `any' of the
> first bunch of framebuffer settings (1st and 2nd is based on how they
> are arranged in `menuconfig') and to only use the second set (a few
> lines below).
>
> They were saying that the kernel frame buffering will absolutely
> not work if one employs any of the settings from the first bunch.
>
>

The Kernel modesetting section of the xorg guide,
https://wiki.gentoo.org/wiki/Xorg/Guide, recommends disabling most of
the drivers listed in the 'Support for frame buffer devices' section
of .config.
I could be wrong, but I believe that applies to installing the kernel
on real hardware specifically.

For emulated environments, such as virtualbox, the instructions given
in the wiki article for virtualbox take precedence.
Virtualbox uses GPU frame buffers and has routines that convert GPU
memory layouts to kernel ones and back, as far as I can tell.

Re: [gentoo-user] kernel choices for booting gentoo as guest in vbox vm

[Alexander Kapshuk]

On Wed, Jan 31, 2018 at 2:44 PM, Harry Putnam  wrote:
> Installing gentoo as guest into vbox vm on solaris-11 (openindiana)
> HOST
> gentoo-17
> VBox 5.2.6
> Kernel 4.15.0
>
> My first boot resulted in resulted in a kernel panic... not able to
> mount root.
>
> I checked my /etc/fstab trying to make sure I didn't make a stupid
> mistake there... it appear to be sound. (Included at the end of post)
>
> I suspect it may be the result of a kernel choice... or rather the
> lack of one.  Something that would have been able to mount /
>
> I thought it would be ata_piix and made sure that was selected in
> kernel .config
>
> I'm thinking it may be be ata_generic, which I did not have selected.
> Which I have now enabled.  But I see now, that is for IDE.
>
> In a chroot now I can see lspci -k shows ata_piix in use .. but that
> would probably be because in vbox I have the gentoo install media on
> IDE secondary master.  But also shows sata controller ahci
>
> Which I do also have selected in .config.  However there a number of
> AHCI choices in the kernel config that were not selected.
>
> Can anyone tell me what they used to allow gentoo in vbox to boot?
>
>
>
Did you enable the recommended kernel config options as suggested here [1]?
[1] https://wiki.gentoo.org/wiki/VirtualBox

Re: [gentoo-user] Re: gcc 7.3 + kernel 4.15 = spectre_v2 fixed

[Alexander Kapshuk]

On Mon, Jan 29, 2018 at 7:50 PM, Ian Zimmerman  wrote:
> On 2018-01-29 20:11, Adam Carter wrote:
>
>> Comparing the contents of /sys/devices/system/cpu/vulnerabilities/spectre_v2
>>
>> With gcc 7.2 + kernel 4.14.15;
>> Intel system shows; Vulnerable: Minimal generic ASM retpoline
>> AMD system shows: Vulnerable: Minimal AMD ASM retpoline
>>
>> With gcc 7.3 + kernel 4.15.0;
>> Intel system shows; Mitigation: Full generic retpoline
>> AMD system shows' Mitigation: Full AMD retpoline
>
> Is there a simple way, with the upstream (kernel.org) sources, to force
> a compiler different from the system default?  If there is, it's not in the
> README, and a simple grep over the Makefiles also doesn't enlighten.
>
> I am not ready to activate a keyworded gcc for general use.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet, fetch the TXT record for the domain.
>

To compile the kernel with a different compiler, the method shown
below may be used, e.g.:
make CC=clang

See [1], for details:
Building the kernel with Clang:
[1] https://lwn.net/Articles/734071/

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Alexander Kapshuk]

On Tue, Jan 23, 2018 at 10:03 AM, Corbin Bird <corbinb...@charter.net> wrote:
>
>
> On 01/23/2018 01:42 AM, Alexander Kapshuk wrote:
>> On Tue, Jan 23, 2018 at 4:34 AM, Corbin Bird <corbinb...@charter.net> wrote:
>>> On 01/22/2018 11:56 AM, Rich Freeman wrote:
>>>> On Mon, Jan 22, 2018 at 12:11 PM, Alexander Kapshuk
>>>> <alexander.kaps...@gmail.com> wrote:
>>>>> On Mon, Jan 22, 2018 at 5:51 PM, Corbin Bird <corbinb...@charter.net> 
>>>>> wrote:
>>>>>> Anyone else getting this error? ( kernel 4.9.77 )
>>>>>>
>>>>>>>   CC  fs/ext4/mballoc.o
>>>>>>>   CC  fs/ext4/block_validity.o
>>>>>>>   CC  fs/ext4/move_extent.o
>>>>>>>   CC  fs/ext4/mmp.o
>>>>>>>   CC  fs/ext4/indirect.o
>>>>>>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>>>>>>> find jump dest instruction at .text+0x56c
>>>>>>>   CC  fs/ext4/extents_status.o
>>>>>>> /bin/sh: line 1: 31735 Segmentation fault  ./tools/objtool/objtool
>>>>>>> check "fs/ext4/extents_status.o"
>>>>>>> make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
>>>>>>> Error 139
>>>>>>> make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
>>>>>>> make: *** [Makefile:995: fs] Error 2
>>>>>> Corbin
>>>>>>
>>>>>>
>>>>> Based on the output you supplied, objtool isn't happy with
>>>>> fs/ext4/indirect.o and fs/ext4/extents_status.o.
>>>>> Did you do 'make clean' prior to building the kernel?
>>>>> If you did, it might be worth doing a 'make mrproper' before
>>>>> rebuilding the kernel.
>>>>> Don't forget to back up your .config before running mrproper.
>>>>>
>>>> While this is going to cause a bit more building, I personally tend to
>>>> redirect kernel build output.  I add O=/var/tmp/linux to all my make
>>>> commands, which leaves /usr/src untouched and builds faster besides
>>>> (tmpfs).
>>>>
>>>> The main downsides to this are:
>>>> 1.  Make can't re-use objects from previous builds, so rebuilds will
>>>> go slower.  Though, IMO this is worthwhile if re-using those objects
>>>> causes issues (which I assume is due to imperfect makefiles).
>>>> 2.  When building packages that install kernel modules the prepared
>>>> sources won't exist.  This requires going back and re-preparing them
>>>> (make O=/var/tmp/linux modules_prepare).  For packages like zfs-kmod
>>>> that use Module.symvers this is even more painful as you can only get
>>>> that by rebuilding the whole thing.
>>>>
>>> Tried both approaches ... the results :
>>>> make distclean
>>>> make mrproper
>>>> --> copy over .config
>>>> make modules_prepare
>>>> make && make modules_install
>>>>
>>>>   CC  fs/ext4/block_validity.o
>>>>   CC  fs/ext4/move_extent.o
>>>>   CC  fs/ext4/mmp.o
>>>>   CC  fs/ext4/indirect.o
>>>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>>>> find jump dest instruction at .text+0x56c
>>>>   CC  fs/ext4/extents_status.o
>>>> /bin/sh: line 1: 24095 Segmentation fault  ./tools/objtool/objtool
>>>> check "fs/ext4/extents_status.o"
>>>> make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
>>>> Error 139
>>>> make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
>>>> make: *** [Makefile:995: fs] Error 2
>>>>
>>>>
>>> Try 2 :
>>>> make distclean
>>>> make mrproper
>>>> --> copy over .config
>>>> make O=/var/tmp/linux modules_prepare
>>>> make O=/var/tmp/linux && make O=/var/tmp/linux modules_install
>>>>
>>>>   CC  fs/ext4/move_extent.o
>>>>   CC  fs/ext4/mmp.o
>>>>   CC  fs/ext4/indirect.o
>>>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>>>> find jump dest instruction at .text+0x56c
>>>>   CC  fs/ext4/extents_status.o
>>>> /bin/sh: line 1: 21028 Segmentation fault  ./tools/objtool/objtool
>