Re: [gentoo-user] Kernel 4.19.50 constant kernel hard locks / solved

[Corbin Bird]

On 6/16/19 5:34 AM, Adam Carter wrote:
> On Sat, Jun 15, 2019 at 6:15 AM Corbin Bird  <mailto:corbinb...@charter.net>> wrote:
> 
> Disclosure :
> 1 : The CPU is a AMD FX-9590 ( Fam15h )
> 2 : Kernel command line parameter "eagerfpu=on" is being used.
> 
> This kernel option was causing constant kernel hard locks.
> -
> General setup --> [ ] CPU isolation.
> -
> Anything that accessed the FPU would cause the CPU's ( SMP ) to "loose
> sync".
> 
> 
> Just to clarify; do i have this right?
> 
> General setup --> [ ] CPU isolation. -> this is the broken setting
> 
> General setup --> [*] CPU isolation. -> this works (and is the default)
> 
> AFAICT in 5.x onward all the lazy FPU code is gone so its just eager.
> 

  General setup --> [*] CPU isolation.

( this is when the lock-ups can be expected / CPU isolation Enabled )

Corbin

Re: [gentoo-user] Profile 17.1 change errors, who's bug is it?

[Corbin Bird]

On 6/14/19 3:36 PM, Rich Freeman wrote:
> On Fri, Jun 14, 2019 at 4:14 PM Corbin Bird  wrote:
>>
>> Deleted those libs in /usr/lib32 and recompilied 'binutils-libs'.
>> Got new libs in /usr/lib AND --> /usr/lib32.
> 
> Is it actually installing these in lib32, or are you just seeing them
> via the compatibility symlink?  The emerge log would tell you where it
> is installing them, or qlist will as well (from portage-utils).
> 
> Did you actually switch your profile as instructed?
> 
> You might want to attach your portage log and output of emerge --info.
> 

The log just shows a 'summary'. Need to change that.

Actually wrote the instructions down, from the 'news' item.

Thinking about the color coding of the console ( at way too early in the
morning, after a long day ) makes me want to say 'symlinks'.

Most of the info requested is attached in a zip file.

Corbin
<>

[gentoo-user] Profile 17.1 change errors, who's bug is it?

[Corbin Bird]

Who's bug is this error?

Remember the instructions : ( Gentoo news item )
-
emerge -1v /lib32 /usr/lib32
-
Every time that command was run it would recompile 'sys-devel/binutils'.

Why?

It was finding 'libiberty, liboppcodes, libbfd' from
'sys-libs/binutils-libs' in /usr/lib32.

Deleted those libs in /usr/lib32 and recompilied 'binutils-libs'.
Got new libs in /usr/lib AND --> /usr/lib32.

Deleted the libs in /usr/lib32. AGAIN.

As long as I don't re-compile/upgrade 'binutils, binutils-libs' or
invoke 'binutils-config', no 'libiberty, liboppcodes, libbfd' in /usr/lib32.

Is this a Portage, binutils, binutils-libs, or binutils-config bug?

Corbin

[gentoo-user] Kernel 4.19.50 constant kernel hard locks / solved

[Corbin Bird]

Disclosure :
1 : The CPU is a AMD FX-9590 ( Fam15h )
2 : Kernel command line parameter "eagerfpu=on" is being used.

This kernel option was causing constant kernel hard locks.
-
General setup --> [ ] CPU isolation.
-
Anything that accessed the FPU would cause the CPU's ( SMP ) to "loose
sync".

With the recent profile change, a lot of 32bit software had to be
re-compiled.

GCC locked up constantly while compiling "libssp".
The packages 'gmp,mpfr,mpc,isl,ffii' also caused lock-ups.
The audio/video codecs had lock-ups during the re-compile if any
assembler was used.
FFMPEG also locked up if 'hardcoded tables' was used, as well.

If you have a working FPU/Math Co-Processor, be very wary of this option.

Corbin

Re: [gentoo-user] Help with emerge error msg

[Corbin Bird]

Just as a test set the 'icu inspector' USE FLAGS for net-libs/nodejs,
Then try this command, it should show how many packages would be pulled
in and their USE FLAGS :

emerge -pvt net-libs/nodejs

On 3/9/19 4:24 PM, allan gottlieb wrote:
> In trying to emerge chromium I received an error msg saying that
> net-libs/nodejs needed the "inspector" USE flag.
> 
> I added
>   >=net-libs/nodejs-8.12.0 inspector
> to
>  /etc/portage/package.use  chromium
> 
> Now I receive the msg
> 
> !!! The ebuild selected to satisfy ">=net-libs/nodejs-7.6.0[inspector]" has 
> unmet requirements.
> - net-libs/nodejs-8.12.0::gentoo USE="inspector npm snapshot ssl -debug -doc 
> -icu -systemtap -test" ABI_X86="(64)" CPU_FLAGS_X86="sse2" 
> PYTHON_TARGETS="python2_7"
> 
>   The following REQUIRED_USE flag constraints are unsatisfied:
> inspector? ( icu )
> 
>   The above constraints are a subset of the following complete expression:
> python_targets_python2_7 inspector? ( icu ssl ) npm? ( ssl )
> 
> (dependency required by "www-client/chromium-72.0.3626.96::gentoo" [ebuild])
> (dependency required by "chromium" [argument])
> 
> This seems more serious than a simple request to add the icu USE flag to
> nodejs.  Can someone please explain how I should proceed?
> 
> Thanks in advance,
> allan
> 
> 

Re: [gentoo-user] Flags for amd 6180se opteron

[Corbin Bird]

According to GCC :
CPUs based on AMD Family 10h cores with x86-64 instruction set support.
(This supersets MMX, SSE, SSE2, SSE3, SSE4A, 3DNow!, enhanced 3DNow!,
ABM and 64-bit instruction set extensions.)


Best way to get that info :
( simplest way ) cat /proc/cpuinfo
( long form ) gcc -c -Q -march=native --help=target
( short form ) gcc -### -march=native /usr/include/stdlib.h

partial output of cat /proc/cpuinfo :

flags : 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 constant_tsc rep_good nopl nonstop_tsc cpuid
extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1
sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt
lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb
hw_pstate ssbd ibpb vmmcall bmi1 arat npt lbrv svm_lock nrip_save
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

partial output of gcc -### -march=native /usr/include/stdlib.h :

"-march=bdver2" -mmmx -mno-3dnow -msse -msse2 -msse3 -mssse3 -msse4a
-mcx16 -msahf -mno-movbe -maes -mno-sha -mpclmul -mpopcnt -mabm -mlwp
-mfma -mfma4 -mxop -mbmi -mno-sgx -mno-bmi2 -mno-pconfig -mno-wbnoinvd
-mtbm -mavx -mno-avx2 -msse4.2 -msse4.1 -mlzcnt -mno-rtm -mno-hle
-mno-rdrnd -mf16c -mno-fsgsbase -mno-rdseed -mprfchw -mno-adx -mfxsr
-mxsave -mno-xsaveopt -mno-avx512f -mno-avx512er -mno-avx512cd
-mno-avx512pf -mno-prefetchwt1 -mno-clflushopt -mno-xsavec -mno-xsaves
-mno-avx512dq -mno-avx512bw -mno-avx512vl -mno-avx512ifma
-mno-avx512vbmi -mno-avx5124fmaps -mno-avx5124vnniw -mno-clwb
-mno-mwaitx -mno-clzero -mno-pku -mno-rdpid -mno-gfni -mno-shstk
-mno-avx512vbmi2 -mno-avx512vnni -mno-vaes -mno-vpclmulqdq
-mno-avx512bitalg -mno-movdiri -mno-movdir64b --param "l1-cache-size=16"
--param "l1-cache-line-size=64" --param "l2-cache-size=2048" "-mtune=bdver2"

For CPU_FLAGS_X86 :
-mmmx means USE FLAG "mmx"
-msse == sse
-msse2 == sse2
... etc.

Reference Links :
https://wiki.gentoo.org/wiki/GCC_optimization
https://gcc.gnu.org/onlinedocs/gcc-8.3.0/gcc/x86-Options.html#x86-Options

On 3/9/19 3:51 AM, mad.scientist.at.la...@tutanota.com wrote:
> can any one suggest flags for the make.conf file, i'm trying to build on
> an hp dl585 g7 with 4 amd 6180se, 12 core, cpu world says k10
> microarchetecture, Maranello platform.
> 
> When this works, I'll be upgrading to 6380 CPUs.  All help appreciated.
> 
> 
> "We the People Dare to Create a More Perfect Union" 

Re: [gentoo-user] layman config file setup?

[Corbin Bird]

On 3/8/19 7:15 PM, Walter Dnes wrote:
>  
>   So I ran "layman -d ALL" followed by "layman -a palemoon".  Now...
> 
> [i660][root][~] cat /var/lib/layman/palemoon/profiles/repo_name 
> palemoon
> 
> ... but I still get the same warning!  Some more info...
> 

Apologies, if this a stupid question ... did you sync layman also?

( i.e. "layman -S", --NOT-- using emerge )

Layman has to be sync'd separately from portage/emerge.
( its a separate database system )

emerge will not find the updated ebuilds, from the overlays, without
layman being sync'd.

Also, the following dirs need the usual entries :
/etc/portage/package.use
/etc/portage/package.accept_keywords ( i.e. www-client/palemoon ~amd64 )

> 
>   What does your /etc/layman/overlays/ directory contain?
> 

... Same as yours.

Please check the contents of this file :
/etc/portage/repos.conf/layman.conf

content of /etc/portage/repos.conf/layman.conf :
[palemoon]
priority = 50
location = /var/lib/layman/palemoon
layman-type = git
sync-type = laymansync
sync-uri = https://github.com/deu/palemoon-overlay.git
auto-sync = Yes

Hope this helps.

Re: [gentoo-user] layman config file setup?

[Corbin Bird]

Have you added an overlay using layman?

Gentoo's List : https://overlays.gentoo.org/

Add  : layman -a
Sync : layman -S

I use the Palemoon overlay :
/var/lib/layman/palemoon/profiles/repo_name

contents of repo_name :
palemoon

When you add the overlay the directories and files are created in
/var/lib/layman/*

Hope this helps.

On 3/7/19 4:11 PM, Walter Dnes wrote:
>   I've set up layman, and it appears to work, but I seem to be missing a
> config entry somewhere.  Whenever I run emerge I get...
> 
> =
> WARNING: One or more repositories have missing repo_name entries:
> 
> /var/lib/layman/profiles/repo_name
> 
> NOTE: Each repo_name entry should be a plain text file containing a
> unique name for the repository on the first line.
> =
> 
>   What and where do I need to enter?  I don't even have a
> /var/lib/layman/profiles/ directory.
> 

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

[Corbin Bird]

I don't think a straight 'drop-in/replacement' will boot.

The CPU scheduler does change from 'fam10h' to 'fam15h'.
The '3DNow!' && 'enhanced 3DNow!' ( used in fam10h ) instructions are
dropped / removed in fam15h.

Doing the 'emerge -e @world' with '-march=generic' is probably the only
guaranteed to work solution.

If you take this route set the CPU_FLAGS_X86= to MMX, SSE, SSE2 with no
3DNow!, enhanced 3DNow! ( gcc flags / CFLAGS -mno-3dnow, -mno-3dnowa )

Just remember to change the kernel configuration also.

Reference Links :
https://en.wikipedia.org/wiki/Phenom_II
https://en.wikipedia.org/wiki/List_of_AMD_FX_microprocessors

On 12/6/18 2:58 PM, Dale wrote:
> Hi,
> 
> My concern is this tho.  I have my old CPU still installed and
> everything is compiled based on that.  So, I'm stable with the old CPU. 
> However, when I shutdown, take out the old CPU and install the new one,
> I'm concerned it may not boot at all because of the change or may boot
> but be very unstable.  I recall years ago being able to set up the flags
> in such a way that it can run on virtually any CPU but it's been a long
> time ago and I don't know if it is needed or not.  My hope was, someone
> did a very similar upgrade and can say for sure if it works or if I need
> to do things before changing the CPUs to make sure I can boot and be
> stable.  If I can just get a stable console, I can do a emerge -e world
> and get the OS inline with the CPU.  I'm just concerned whether I will
> have that or not. 
>

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

[Corbin Bird]

My two cents worth :

Update gcc before changing any hardware.

With gcc somewhat current, try this on the replacement CPU.
This gives a listing of all CPU supported compiler flags.
Including -mtune / -march :)

gcc -c -Q -march=native --help=target

sample of output :

  -msse4[enabled]
  -msse4.1  [enabled]
  -msse4.2  [enabled]
  -msse4a   [enabled]
  -msse5
  -msseregparm  [disabled]
  -mssse3   [enabled]
  -mstack-arg-probe [disabled]
  -mstack-protector-guard=  tls
  -mstackrealign[disabled]
  -mstringop-strategy=  [default]
  -mstv [enabled]
  -mtbm [enabled]
  -mtls-dialect=gnu
  -mtls-direct-seg-refs [enabled]
  -mtune-ctrl=  
  -mtune=   bdver2
  -muclibc  [disabled]
  -mveclibabi=  [default]
  -mvect8-ret-in-mem[disabled]
  -mvzeroupper  [enabled]
  -mx32 [disabled]
  -mxop [enabled]
  -mxsave   [enabled]
  -mxsavec  [disabled]
  -mxsaveopt[disabled]
  -mxsaves  [disabled]


This will give you the L1 / L2 cache/line/size parameters :

gcc -### -march=native /usr/include/stdlib.h

sample of output :

gcc version 7.3.0 (Gentoo 7.3.0-r3 p1.4)
COLLECT_GCC_OPTIONS='-march=native'
 /usr/libexec/gcc/x86_64-pc-linux-gnu/7.3.0/cc1 -quiet
/usr/include/stdlib.h "-march=bdver2" -mmmx -mno-3dnow -msse -msse2
-msse3 -mssse3 -msse4a -mcx16 -msahf -mno-movbe -maes -mno-sha -mpclmul
-mpopcnt -mabm -mlwp -mfma -mfma4 -mxop -mbmi -mno-sgx -mno-bmi2 -mtbm
-mavx -mno-avx2 -msse4.2 -msse4.1 -mlzcnt -mno-rtm -mno-hle -mno-rdrnd
-mf16c -mno-fsgsbase -mno-rdseed -mprfchw -mno-adx -mfxsr -mxsave
-mno-xsaveopt -mno-avx512f -mno-avx512er -mno-avx512cd -mno-avx512pf
-mno-prefetchwt1 -mno-clflushopt -mno-xsavec -mno-xsaves -mno-avx512dq
-mno-avx512bw -mno-avx512vl -mno-avx512ifma -mno-avx512vbmi
-mno-avx5124fmaps -mno-avx5124vnniw -mno-clwb -mno-mwaitx -mno-clzero
-mno-pku -mno-rdpid --param "l1-cache-size=16" --param
"l1-cache-line-size=64" --param "l2-cache-size=2048" "-mtune=bdver2"
-quiet -dumpbase stdlib.h -auxbase stdlib -o /tmp/ccQiaXih.s
"--output-pch=/usr/include/stdlib.h.gch"


Reference Link : https://wiki.gentoo.org/wiki/GCC_optimization

On 12/6/18 3:27 AM, Dale wrote:
> 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
> 
> Those were put there ages ago, likely when I built and installed Gentoo
> on this rig.  Do I need to change those to something that is compatible
> with both CPUs and then change to the new CPU after it is installed?  Or
> will the new CPU be close enough that it won't matter?  Right now, I
> don't know for sure what the new CPU supports or doesn't. 
> 

Re: [gentoo-user] Scanners, sane and driver support question

[Corbin Bird]

A family member still uses a old SCSI Mustek flat bed scanner.
( Paragon 1200 SP ?? / last windows driver was for Win2K ).

Works just fine. The Linux drivers are old, but nothing wrong with them.

On 11/10/18 6:35 PM, Dale wrote:
> Howdy,
> 
> I'm on the hunt for a scanner, flatbed type, and have been browsing Ebay
> and the sane project list of supported devices.  I'm leaning toward HP
> on this.  While looking at say a ScanJet 6200C, it says the drivers are
> no longer maintained but complete.  It leads me to this question.  Does
> that mean they are complete and fixes will no longer be made even if
> something breaks them and they need a little tweaking OR they are
> complete and if a bug pops up, they will be fixed as needed but all
> functions work?  I can see the logic either way on this.  I'm leaning
> toward the side that if something pops up that requires a little
> tweaking, it will be done by someone.  The drivers are just feature
> complete. 
> 
> Does anyone else have the same thinking or is buying one of these
> scanners a bad idea if the drivers were to break and the scanner was
> rendered no longer usable? 
> 
> Thanks.
> 
> Dale
> 
> :-)  :-) 
> 

Re: [gentoo-user] A config file for the magical combo of....

[Corbin Bird]

On 07/02/2018 01:36 PM, Mick wrote:

> On Monday, 2 July 2018 19:20:29 BST Corbin Bird wrote:
>> On 07/01/2018 03:04 PM, Mick wrote:
>>> What do you mean "would not load"?  From the live ISO?
>>>
>>> I had no such problem here on a bare metal install (no Windows) with
>>> sysrescuecd.  You have to make sure the sysrescuecd is booting in UEFI
>>> mode
>>> before you proceed with the installation.
>>>
>> ( Clarification ) The UEFI implementation installed on my MB would not
>> load the VFAT driver.
> What error messages, indications, behaviour do you get and at what stage?
>
>
> Well, the Gentoo Live-CD may not be the best image to boot your hardware 
> with.  
> I'd give systemrescuecd a spin, it has never failed me so far, although a few 
> years ago I had to perform some tricks to get it to boot into UEFI mode.
>
Answers to questions :

The VFAT driver in question is built-in to UEFI.
It is not the Linux kernel module you may be thinking of.

UEFI was a long list of built-in drivers.
Old BIOS based systems had a 1 or 2 Megabyte EPROM in use for the BIOS.
UEFI has 32, 64, or 128 Megabyte EPROMs on the motherboard == driver
storage space.

Remember DOS and all those drivers that had to be setup, just to get
basic hardware working?
UEFI is the equivalent of all those drivers being packaged into the
EPROM, with auto-config enabled.

The EFI Shell has a specific command that will "print-to-screen" all
loaded UEFI drivers.
That command was showing only the NTFS filesystem driver loading.

After Windows was installed on a second drive, the UEFI VFAT driver
started loading.
( the Windows Boot Loader had installed itself into the UEFI )

My MB has the latest firmware from the factory.
Linux has to be run with "efi=old_map" appended to the kernel parameters.
( Windows 8.1 UEFI memory map )

I was using the standard Gentoo install ISO, Minimal Installation CD.
Link : https://www.gentoo.org/downloads/
Memory is fuzzy ... I think I did try it in UEFI mode.

Next time I will try the systemrescuecd in UEFI mode instead.

Corbin

Re: [gentoo-user] A config file for the magical combo of....

[Corbin Bird]

On 07/01/2018 03:04 PM, Mick wrote:

> What do you mean "would not load"?  From the live ISO?
>
> I had no such problem here on a bare metal install (no Windows) with 
> sysrescuecd.  You have to make sure the sysrescuecd is booting in UEFI mode 
> before you proceed with the installation.
>
>
>> So ... Windows setup UEFI just fine. Gentoo is using GPT/GRUB.
>> Every time I boot, the "Boot Menu" gets used to choose the OS.
>>
>> Corbin
> I am booting without a boot loader straight from UEFI as this not a multiboot 
> system.  So, unless I interrupt it pressing F2 to get into UEFI menu, it will 
> boot into the default OS image, which is the latest I have setup with 
> efibootmgr.
>

( Clarification ) The UEFI implementation installed on my MB would not
load the VFAT driver.

I did use a Gentoo install ISO to do the setup. The CSM is set to UEFI.
( If I turn off the CSM, it disables both UEFI && Legacy for the Video /
Drive Controller. )

The VFAT partition was unreadable by the MB / UEFI firmware, without the
UEFI VFAT driver loading.

Corbin

Re: [gentoo-user] A config file for the magical combo of....

[Corbin Bird]

On 07/01/2018 12:05 PM, Andrew Lowe wrote:

> Hi all,
>   I'm trying to get a new computer working. I've decided to go the UEFI
> route but something is being a bit obstinate. Would anyone have the
> combination of a Gigabyte motherboard, x470 Ultra, with an AMD Ryzen 7
> 2700 CPU? Set up to run UEFI?
>
>   I'm having all sorts of trouble trying to get things running and if
> anyone would happen to have a working kernel config for the above combo,
> and is willing to share, it would be greatly appreciated.
>
>   Regards,
>   Andrew
>

One small thing I noticed doing a Gentoo setup on UEFI ...

The VFAT driver ( in UEFI ) never loaded until Windows was installed on
a drive.
Almost as if the driver was checking for Windows before loading ...

Every attempt to do a Gentoo UEFI install FAILED, because the VFAT
driver would not load.

So ... Windows setup UEFI just fine. Gentoo is using GPT/GRUB.
Every time I boot, the "Boot Menu" gets used to choose the OS.

Corbin

[gentoo-user] AMD Ucode Correction, Fam15h

[Corbin Bird]

FYI to all with an interest in AMD Ucode.
AMD fixed the 'lwp' instruction(s) in a latter ucode update.

--

2018-05-18

linux-firmware: Update AMD cpu microcode
* Add AMD cpu microcode for processor family 17h
* Update AMD cpu microcode for processor family 15h
* Update the AMD cpu microcode license copyright
* Add a Version for both microcode family 15h and 17h

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=77101513943ef198e2050667c87abf19e6cbb1d8

( sys-kernel/linux-firmware-20180518:0 )

On an AMD FX-9590 , the 'lwp' instruction(s) disappeared.

--

2018-05-25

Update AMD cpu microcode for family 15h
* Processor Revision ID 0x00610f01 was accidently not included in the
previous
  submitted microcode container file.
* Update the Version for family 15h microcode .bin file


https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=7518922bd5b98b137af7aaf3c836f5a498e91609

( sys-kernel/linux-firmware-20180525:0 )

On an AMD FX-9590 , the 'lwp' instruction(s) reappeared.

--

Thanks to the person who fixed this little 'oops'.

Re: [gentoo-user] AMD microcode problem - Fam15h ( FYI )

[Corbin Bird]

On 05/27/2018 06:12 AM, Adam Carter wrote:
> Also, are you saying that the sequence of events for you was;
> - booted with new microcode, and lwp was missing from /proc/cpuinfo
> - you had instability
> - you rebuilt with -mno-lwp
> - stability returned
.
- quickpackage'd 'sys-kernel/linux-firmware' v20180507
- cat'd the /proc/cpuinfo file to oldcpuinfo.text ( in home directory )
- updated 'sys-kernel/linux-firmware' from v20180507 to v20180518
- compilied the updated / new kernel released, and modules, then
installed them
- booted with new microcode
- cat'd the new /proc/cpuinfo to newcpuinfo.text ( in home directory )
and lwp was missing from /proc/cpuinfo
- began experiencing 'kernel hard locks'
- next day, updated kernel version released, added '-mno-lwp' to
'make.conf' CFLAGS, built it && installed it
- rebooted, stability returned

Corbin

Re: [gentoo-user] AMD microcode problem - Fam15h ( FYI )

[Corbin Bird]

On 05/25/2018 08:50 PM, Adam Carter wrote:
>
> > For me dmesg says;
> > [    1.538275] microcode: CPU0: patch_level=0x06000852
> >
> > but i still have lwp in /proc/cpuinfo. Are you at 0x06000852 ?
> .
> This is my dmesg output :
> .
> [    1.111448] microcode: microcode updated early to new
> patch_level=0x06000852
>
>
> Ok then it looks like the mno-lwp is responsible for lwp's absence in
> your /proc/cpuinfo.
>
> FWIW, no stability problems for me so far. (FX-8350 + 4.16.11).
>
.
I should have clarified ... the '-mno-lwp' was added as a result of the
comparison of the two /proc/cpuinfo files.I was very curious about WHAT
exactly the microcode update did.

The CPU I am using is a FX-9590.

Question : Is there a PSP in your CPU?

Corbin

Re: [gentoo-user] AMD microcode problem - Fam15h ( FYI )

[Corbin Bird]

On 05/24/2018 05:32 PM, Adam Carter wrote:
>
> For me dmesg says;
> [    1.538275] microcode: CPU0: patch_level=0x06000852
>
> but i still have lwp in /proc/cpuinfo. Are you at 0x06000852 ?
.
This is my dmesg output :
.
[    1.111448] microcode: microcode updated early to new
patch_level=0x06000852
[    1.111574] microcode: CPU0: patch_level=0x06000852
[    1.111691] microcode: CPU1: patch_level=0x06000852
[    1.111809] microcode: CPU2: patch_level=0x06000852
[    1.111925] microcode: CPU3: patch_level=0x06000852
[    1.112117] microcode: CPU4: patch_level=0x06000852
[    1.112236] microcode: CPU5: patch_level=0x06000852
[    1.112354] microcode: CPU6: patch_level=0x06000852
[    1.112469] microcode: CPU7: patch_level=0x06000852
[    1.112609] microcode: Microcode Update Driver: v2.01
, Peter Oruba
.
current /proc/cpuinfo ( kernel v4.9.102 ):
--
processor    : 0
vendor_id    : AuthenticAMD
cpu family    : 21
model        : 2
model name    : AMD FX(tm)-9590 Eight-Core Processor
stepping    : 0
microcode    : 0x6000852
.
flags        : 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 constant_tsc rep_good nopl nonstop_tsc extd_apicid
aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2
popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm
sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt fma4 tce
nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate ssbd ibpb
vmmcall bmi1 amd_ibpb arat npt lbrv svm_lock nrip_save tsc_scale
vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
.
bugs        : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2
spec_store_bypass
.
old /proc/cpuinfo : ( pre-microcode update / kernel v4.9.99 )
--
processor    : 0
vendor_id    : AuthenticAMD
cpu family    : 21
model        : 2
model name    : AMD FX(tm)-9590 Eight-Core Processor
stepping    : 0
microcode    : 0x600084f
.
flags        : 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 constant_tsc rep_good nopl nonstop_tsc extd_apicid
aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2
popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm
sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce
nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall
bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid
decodeassists pausefilter pfthreshold
.
bugs        : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2
.
Just noticed the "ssbd" flag ADDED in the new /proc/cpuinfo.
.
Corbin

[gentoo-user] AMD microcode problem - Fam15h ( FYI )

[Corbin Bird]

FYI :

Did the microcode update, compiled and installed the 4.9.101 kernel with it.
After rebooting, I started having kernel hard lock problems.

Before compiling / installing kernel 4.9.102, I made an addition to the
CFLAGS var in make.conf : -mno-lwp
( 'lwp' is 'Light Weight Profiling' )

No kernel hard locks after the reboot.

Lesson Learned :
The kernel needs to be compiled, installed, system rebooted,
re-compiled, re-installed and re-booted again.
Otherwise the kernel compile process doesn't adjust to the removal of
instruction sets.
The 'make.conf' entry is to catch any other uses, system wide.


Config Info :

Using 'sys-kernel/gentoo-sources' USE flags : experimental modules symlink

-march=bdver2

kernel .config settings :
# CONFIG_PROFILING is not set
CONFIG_HAVE_OPROFILE=y
CONFIG_OPROFILE_NMI_TIMER=y
CONFIG_KPROBES=y


Corbin

Re: [gentoo-user] Where are the AMD microcode updates for spectre?

[Corbin Bird]

On 05/22/2018 03:41 AM, Adam Carter wrote:
> On Tue, May 22, 2018 at 2:47 PM, taii...@gmx.com
>  > wrote:
>
> The fam15h microcode update adds IBPB
>
>   * Indirect Branch Prediction Barrier (IBPB)
>     * PRED_CMD MSR is available:  YES
>     * CPU indicates IBPB capability:  YES  (IBPB_SUPPORT feature bit)
>
>
> My fam15 with kernel 4.16.10 and linux-firmware-20180518 confirms IBPB
> has been added;
>
> $ grep . /sys/devices/system/cpu/vulnerabilities/*
> /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected
> /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> pointer sanitization
> /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full
> AMD retpoline, IBPB
>
> FWIW i saw a bunch of spectre fixes in 4.16.9
> https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.16.9
.
I cat'd /proc/cpuinfo before and after the firmware upgrade.

The new smaller Fam15h firmware adds "ibpb" and removes "lwp".

Couldn't / Didn't really find a definition of WHAT the 'lwp'
instruction(s) does.

Is 'lwp' used for anything?

Corbin

Re: [gentoo-user] [Maybe OT]: Instability of system

[Corbin Bird]

On 05/20/2018 03:54 PM, Alan Mackenzie wrote:
> Hello, Gentoo.
>
> I'm having problems with my machine hanging or rebooting spontaneously.
> It's doing this, perhaps, every three or four weeks.  I think that when
> I'm in X, the system usually reboots, when I'm on a tty, it hangs.
---
> Other than that, suggestions as to what to do would be welcome.
>
> Thanks!
>
---
Lots of good suggestions already ... might want to check this as well :
.
The UEFI Memory Map
.
The Asrock mobo I have original came out certified for Win 8.1
Win 10 has a different UEFI memory map.
OpenRC re-triggers the "init" binary every 4 or 5 minutes, unless I put
"efi=old_map" in the kernel boot param.
.
( Linux/Gentoo, Kernel 4.9.x is looking for  Win 10 UEFI memory map. )
.
Compiling is a PITA with constant re-inits.
.
Corbin

Re: [gentoo-user] Where are the AMD microcode updates for spectre?

[Corbin Bird]

On 05/20/2018 06:46 PM, Adam Carter wrote:
> How often does the linux-firmware package update? On a schedule or as
>
> needed?
>
>
> There's a version bump request bug in for these and new AMDGPU
> firmware. Hopefully it will get processed quickly.
>
> https://bugs.gentoo.org/656136
.
Thank You, for the info.

I noticed something odd about the microcode however ...
> amd-ucode/microcode_amd_fam15h.bin    7876 -> 5356 bytes
.
The size dropped by 2Kb?
So is the "fix" actually disabling fixes for other problems?
.
Reference Link :
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=77101513943ef198e2050667c87abf19e6cbb1d8
.
Corbin

Re: [gentoo-user] Where are the AMD microcode updates for spectre?

[Corbin Bird]

On 05/20/2018 03:59 AM, Adam Carter wrote:
>
>
> This has indeed been pretty frustrating.
>
> As far as I can tell there is no official AMD microcode update
> page, or any
> kind of official release notes.  I'm not sure where linux-firmware
> actually
> gets the microcode files from (I'm sure they wouldn't load if they
> weren't
> genuine though).  I can find no documentation as to what any of these
> updates actually do.
>
> It sounds like AMD intends for the microcode updates to be
> distributed via
> firmware updates, in which case the fixes would be done before
> boot.  That
> is a good thing of course, but they should still release the microcode
> files themselves, and also have release notes for something like this.
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=77101513943ef198e2050667c87abf19e6cbb1d8
>
>
> Bulldozer and Zen updates!

Thanks for the info.

How often does the linux-firmware package update? On a schedule or as
needed?

Corbin

Re: [gentoo-user] which microcode gets loaded?

[Corbin Bird]

On 05/13/2018 10:39 PM, tu...@posteo.de wrote:

> Hi,
>
> from a previous thread I learned which micorcode file needs
> to be loaded for the "fight against Spectre and Melddown"...
>
> Now two question came up for me:
> 1.) WIth this particular micorcode loaded: Do I need to activate
> the Spectre/Meldtown fix in the kernel itsself?
> 2.) Which microcode file gets loaded?
>
> cat /proc/cpuinfo (from one of the six cores):
> processor : 4
> vendor_id : AuthenticAMD
> cpu family: 16
> model : 10
> model name: AMD Phenom(tm) II X6 1090T Processor
> stepping  : 0
> microcode : 0x1bf
> cpu MHz   : 1755.530
> cache size: 512 KB
> physical id   : 0
> siblings  : 6
> core id   : 4
> cpu cores : 6
> apicid: 4
> initial apicid: 4
> fpu   : yes
> fpu_exception : yes
> cpuid level   : 6
> wp: yes
> flags : 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 cpuid 
> extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic 
> cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt cpb 
> hw_pstate vmmcall npt lbrv svm_lock nrip_save pausefilter
> bugs  : tlb_mmatch apic_c1e fxsave_leak sysret_ss_attrs null_seg 
> amd_e400 spectre_v1 spectre_v2
> bogomips  : 7224.41
> TLB size  : 1024 4K pages
> clflush size  : 64
> cache_alignment   : 64
> address sizes : 48 bits physical, 48 bits virtual
> power management: ts ttp tm stc 100mhzsteps hwpstate cpb
>
>
> from dmesg (microcode-related lines):
> [1.517265] microcode: CPU0: patch_level=0x01bf
> [1.517367] microcode: CPU1: patch_level=0x01bf
> [1.517450] microcode: CPU2: patch_level=0x01bf
> [1.517538] microcode: CPU3: patch_level=0x01bf
> [1.517628] microcode: CPU4: patch_level=0x01bf
> [1.517716] microcode: CPU5: patch_level=0x01bf
> [1.517824] microcode: Microcode Update Driver: v2.2.
>
> from linux-firmware (related lines):
> /lib/firmware/amd-ucode/microcode_amd.bin
> /lib/firmware/amd-ucode/microcode_amd_fam15h.bin
> /lib/firmware/amd-ucode/microcode_amd.bin.asc
> /lib/firmware/amd-ucode/microcode_amd_fam16h.bin  ***
> /lib/firmware/amd-ucode/microcode_amd_fam17h.bin
> /lib/firmware/amd-ucode/microcode_amd_fam16h.bin.asc  ***
> /lib/firmware/amd-ucode/microcode_amd_fam15h.bin.asc
>
> (***) I think, these microcodes do I need...
>
> Thanks for any help in advance!
> Cheers
>  Meino
>
>
>
>
>
.

No Spectre/Meltdown fixes in these files, apparently.

Simple experiment(s) to confirm the ucode file to use : ( repetitive, but 
simple )

Build a kernel with NO ucode, boot, note the patch_level.
Build a kernel with microcode_amd.bin ucode ONLY, boot, note the patch_level.
Build a kernel with microcode_amd_fam15h ucode ONLY, boot, note the patch_level.
Build a kernel with microcode_amd_fam16h ucode ONLY, boot, note the patch_level.
Build a kernel with microcode_amd_fam17h ucode ONLY, boot, note the patch_level.

Results :
When I did this on a Phenom II 980 x4, the only time the patch level changed 
was with "microcode_amd.bin" ucode.  
When I do this on a FX-9590, the only time the patch level changes is when 
"microcode_amd_fam15h.bin" ucode is used.

Corbin

Re: [gentoo-user] Where are the AMD microcode updates for spectre?

[Corbin Bird]

On 05/12/2018 07:21 PM, Adam Carter wrote:

> Gentoo does have the newer microcode blobs stashed on a server (
>
> somewhere ).
>
> That does pull in the blobs for :
>
> Fam10h ( microcode_amd.bin )
>
> Fam15h ( microcode_amd_fam15h.bin )
>
> Fam16h ( microcode_amd_fam16h.bin )
>
> Fam17h ( microcode_amd_fam17h.bin )
>
>
> These files haven't changed since at least late January, so no Spectre
> fixes yet.
>
.
This is odd.
And Microsoft is distributing the newest blobs through 'Windows Update'
for Windows 10 ( Microcode Loader )?
.
If the MB makers aren't updating their UEFI builds for CURRENT products,
how do we get hold of them?
.
Corbin

Re: [gentoo-user] Where are the AMD microcode updates for spectre?

[Corbin Bird]

On 05/12/2018 03:20 PM, taii...@gmx.com wrote:
> ^title
> AMD has released them for all of the recent CPU's and I simply must have
> them.
>
> It seems the last update to amd-ucode on linux-firmware was in 2016,
> does anyone know whom I would contact about this who has the juice to do
> it? I need fam15h.
>
> AMD is being annoying and not releasing them to the plebians only OEM
> partners - I assume perhaps to encourage people to buy new hardware as
> most OEM's won't release BIOS updates for older boards.
>
> Thanks.
.

Emerge this package : "sys-kernel/linux-firmware"

You can find the blobs in : /lib/firmware/amd-ucode/

If you already have "sys-kernel/linux-firmware" emerged and the blobs
aren't showing, un-merge it, and the re-emerge it.

.

Gentoo does have the newer microcode blobs stashed on a server (
somewhere ).

That does pull in the blobs for :

Fam10h ( microcode_amd.bin )

Fam15h ( microcode_amd_fam15h.bin )

Fam16h ( microcode_amd_fam16h.bin )

Fam17h ( microcode_amd_fam17h.bin )

.

If you have an AMDGPU and use the "amdgpu" driver, firmware will be here
: /lib/firmware/amdgpu

.

Corbin

Re: [gentoo-user] Re: Mammoth emerge ...

[Corbin Bird]

.
Chromium switched to 'clang++ v5.x' as its primary compiler.
Why?
The Chromium devs are using 'c++' features supported in gcc v8+.
.
So ... first compile run is with 'gcc' ... then Chromium is re-compiled
with 'clang++'.
That is what I am seeing ( console && log wise ).
2 Compile runs ... twice the time.
.
No gold linker setup on my system.
Just how is 'clang++' supposed to work with 'ld.bfd'?
.
As far as I can tell, all optimization depending on '-march= / -mtune= '
is still discarded, as well.
( clang / clang ++, does not seem to accept the '-march= / -mtune= / -O2
/ -pipe' switches either. )
.
Corbin

Re: [gentoo-user] Dell Precision Workstation Overheating

[Corbin Bird]

Suggestion :

 ... upgrade the cooling capacity.

The CPU in my box is a AMD FX-9590. TDP is 220 watts. Running at 4.7 Ghz.

With cooling for TDP 250 watts, it ran hot under load.

With cooling for TDP 900 watts, it rarely gets close to 110 F under
heavy load.


On 04/20/2018 09:11 AM, R0b0t1 wrote:
> On Fri, Apr 20, 2018 at 7:21 AM, Mick <michaelkintz...@gmail.com> wrote:
>> On Friday, 20 April 2018 12:55:13 BST Corbin Bird wrote:
>>> Oak Ridge National Laboratory uses these processors ( Rhea Cluster ) and
>>> has numerous heat failures.
>>>
>>> Due to poor cooling ... surprised?
>>>
>>> The cooling is not working right. Something is still wrong.
>>>
>>> On 04/19/2018 09:33 PM, R0b0t1 wrote:
>>>> Dell Precision T7600, two 16 thread Xeons, 192GB of RAM, two Quadro
>>>> cards and a Tesla card.
>>>>
>>>> The system is a few years old at this point. Old enough that the
>>>> thermal compound could have hardened, which is why I replaced it.
>> If the problem started suddenly, rather than getting progressively worse over
>> time, it may have something to do with kernel drivers, or some change in
>> firmware.
>>
> As far as I know it has always been like this. It may be why it was
> hardly used before it came into my care. Looking at the server I could
> blame poor design; the inside is rather cramped, despite the care
> taken with the internal baffles. They may not have run a good flow
> simulation.
>
> Mr. Bird's observation seems to support this.
>
>> If the cause is mechanical, I'd also suggest checking the heat sink contact
>> surface.  Some heat sinks are poorly manufactured and require flattening with
>> wet 'n dry sandpaper to get a flat enough surface and improve their contact
>> with the CPU.  I've seen 15°C improvement in a Zalman CPU cooler after excess
>> metal was removed from copper pipes, which were manufactured proud.  Hardcore
>> O/C's flatten the CPU too, but I'd avoid anything as radical because it can 
>> go
>> badly wrong if you remove more than the surface varnish from the chip.
>>
>> In the interim, opening the side panel may also help in hot weather.
>>
> The internals are custom made to fit the motherboard, cards, and drive
> slots. It may work better if I move it to another tower but it will be
> a while before I can find one. I will look at the interface between
> the heatsink and processor again, but it looked fine.
>
>
> How concerned should I be about overheating machine check errors? I
> used to think that it was best to avoid them, as the threshold was
> high enough that very small parts of the die could overshoot and fail,
> but I was informed that is not the case. Besides the throttling (which
> is fairly bad) I am not sure if there are any drawbacks to the
> overheating.
>
> I am wondering what the point of 32 threads is if you can't use them at 100%.
>
> Cheers,
>  R0b0t1

Re: [gentoo-user] Dell Precision Workstation Overheating

[Corbin Bird]

Oak Ridge National Laboratory uses these processors ( Rhea Cluster ) and
has numerous heat failures.

Due to poor cooling ... surprised?

The cooling is not working right. Something is still wrong.

On 04/19/2018 09:33 PM, R0b0t1 wrote:
> Dell Precision T7600, two 16 thread Xeons, 192GB of RAM, two Quadro
> cards and a Tesla card.
>
> The system is a few years old at this point. Old enough that the
> thermal compound could have hardened, which is why I replaced it.

Re: [gentoo-user] Dell Precision Workstation Overheating

[Corbin Bird]

What are the Dell system specs?

( Heatsink on a CPU?  How old is this system ? )

On 04/19/2018 08:22 PM, R0b0t1 wrote:
> I was compiling Gentoo, as is custom, but found my old new server to
> be thermal cycling wildly. The fans will turn on full blast and
> machine check errors will be generated if I use approximately more
> than one third to half of the cores. The cores then throttle
> themselves, only to immediately overheat once the throttle lifts. This
> seems to persist on Windows, though Windows seems to be much more
> conservative in its CPU usage, and triggers MCEs less.
>
> Any suggestions? I repasted the CPU and heatsink interface, and the
> machine is not loaded with dust. It was hardly ever used. The MCEs
> seem to be a "normal" part of operation, though less normal on
> Windows.
>
> Is there a way to at least mimic the conservative CPU usage that
> Windows exhibits?
>
> Cheers,
>  R0b0t1
>

Re: [gentoo-user] How to flash an LSI SAS controller from IR to IT mode on linux with sas2flsh

[Corbin Bird]

On 03/21/2018 03:20 PM, taii...@gmx.com wrote:

> On 03/21/2018 04:44 PM, Corbin Bird wrote:
>
>> Curious ... you cannot use 'FreeDOS' even as a bootable cdrom?
>> Its very easy to open the image, tuck in two files and one new
>> directory, then close and burn the image.
> I have not figured out where to place them on the iso so that they are
> accessible nor alternatively how to load the drivers and mount a cdrom.
> Do you know how?
.
Okay. Refresh complete.

This should work if 16bit support / BIOS PAL is in good order on the
target system.

The 'FreeDOS' install cd is bootable.
It loads a 'generic' cdrom driver automatically.

Write down the flash commands EXACTLY as spec'd in the LSI docs.

Use 'isomaster' for a GUI ISO image utility. Very convenient. It's in
the Gentoo repository.

Get this file ( FreeDOS v1.1 source )
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/fd11src.iso

create a directory on your HD, call it 'firmware'
place all the needed LSI files in it.
Example HBA && files ( LSI 2004 / 9211-41 )
-- 2114IR.BIN
-- 2114IT.BIN
-- MPTSAS2.ROM
-- SAS2FLSH.EXE


Open the image ( fd11src.iso ) with ISO Master.
Bottom Widow of ISO Master. 2 dirs showing. double-click FREEDOS.
Top Window, find your firmware dir, highlight it, click the 'add to the
ISO' button
Save (as) the ISO to 'lsiboot' somewhere on you HD.
Exit ISO Master.
burn 'lisboot.iso' to cd.
boot the cdrom

choose the following options ( in order ) :
Install to C: Drive
C
2
English
press the [Enter] key
Run FreeDOS from CD-ROM

Command Prompt will show [ F:\ ]
cd firmware [Enter]

let the sas2flsh'ing commence.

Corbin

Re: [gentoo-user] How to flash an LSI SAS controller from IR to IT mode on linux with sas2flsh

[Corbin Bird]

On 03/21/2018 03:20 PM, taii...@gmx.com wrote:

> On 03/21/2018 04:44 PM, Corbin Bird wrote:
>
>> Curious ... you cannot use 'FreeDOS' even as a bootable cdrom?
>> Its very easy to open the image, tuck in two files and one new
>> directory, then close and burn the image.
> I have not figured out where to place them on the iso so that they are
> accessible nor alternatively how to load the drivers and mount a cdrom.
> Do you know how?
>
.
I've done it in the past.
Give me an hour to refresh the memory / retest the process / write the
process down.

Corbin

Re: [gentoo-user] How to flash an LSI SAS controller from IR to IT mode on linux with sas2flsh

[Corbin Bird]

On 03/20/2018 02:02 PM, taii...@gmx.com wrote:
> On 03/19/2018 08:02 PM, mad.scientist.at.la...@tutanota.com wrote:
>> A virtual machine is useful largely because it isolates the VM from the real 
>> hardware, therefore it's not likely you can update firmware from a VM (you 
>> really shouldn't be able to).
> Actually you can update firmware from a VM, I have done it many times
> on many different PCI-e cards and I already updated the IR mode
> firmware to the latest version in a linux VM (but you need DOS to go
> IR>IT)
>
> It is part of the reason as to why SR-IOV was created besides the
> performance benefits you also get security benefits with restricted
> registers and the inability to flash a malicious firmware from a guest
> if you attach a VF to the VM instead of the PF.
>
> I don't have any UEFI machines as I hate UEFI (all my machines run
> coreboot with the grub payload)
>> The reason they still want us to upgrade with dos is it's a lowest common 
>> denominator, i.e. every one has it or can get it (freedos).  it also helps 
>> that it's a minimal enviroment.
>>
>> In any case, I suggest you run a REAL freedos on a Real machine, so that you 
>> can update real not virtual firmware.  i.e. no Virtual Machine.
> The issue is not being able to use linux as well and having a bare
> metal freedos won't help my disk driver issue there still won't be a
> way to load the files.
.
Curious ... you cannot use 'FreeDOS' even as a bootable cdrom?
Its very easy to open the image, tuck in two files and one new
directory, then close and burn the image.

FreeDOS comes with a 'generic' PATA / SATA driver for cdrom drives.

Correction :
(but you need DOS to go IR>IT) ---> the EFI Shell also can do it.

Corbin

Re: [gentoo-user] How to flash an LSI SAS controller from IR to IT mode on linux with sas2flsh

[Corbin Bird]

On 03/19/2018 07:02 PM, mad.scientist.at.la...@tutanota.com wrote:
>
> A virtual machine is useful largely because it isolates the VM from
> the real hardware, therefore it's not likely you can update firmware
> from a VM (you really shouldn't be able to).
>
> The reason they still want us to upgrade with dos is it's a lowest
> common denominator, i.e. every one has it or can get it (freedos).  it
> also helps that it's a minimal enviroment.
>
> In any case, I suggest you run a REAL freedos on a Real machine, so
> that you can update real not virtual firmware.  i.e. no Virtual Machine.
>
> mad.scientist.at.large (a good madscientist)
> -- 
> God bless the rich, the greedy and the corrupt politicians they have
> put into office.   God bless them for helping me do the right thing by
> giving the rich my little pile of cash.  After all, the rich know what
> to do with money.
>
>
> 19. Mar 2018 17:21 by taii...@gmx.com :
>
> I am told to create a DOS usb flash drive with windows but I am
> un-able to do that.
> I have tried getting the required files in to a VM FreeDOS
> installation but I haven't been able to figure out how to do that,
> there is no actual way to load the cdrom drivers.
>
> Jesus christ it is 2018 and they still want us to use dos to flash
> hardware >:'[
>
.
If you are using a UEFI system, use the EFI shell.

HBA successfully updated : LSI 2004 / 9211-4i

Downloads from LSI / Avago / Broadcom :
 Installer_P20_for_UEFI
 firmware for your HBA

Use the EFI Shell Installer ( sas2flash.efi ) and follow its directions.

Corbin

Re: [gentoo-user] [OT] audio controller compatible with Linux

[Corbin Bird]

On 02/23/2018 03:21 PM, the...@sys-concept.com wrote:
> Can anybody suggest an audio controller / speakers that is compatible
> with Linux (something that does not need Mac, iPhone or Windows etc).
> For example, if I play the music on my Linux system or listen to an
> audio I would like to stream it throughout the house.
>
> It can be wired or wireless. I have audio/video cables running from
> basement to every room in a house, so wiring is not a problem.
>
.
I turned an old computer into a 'music box' for my parents.
Gentoo system with X Windows , Exaile, and Asunder.
I put a good soundcard in it and ran the audio output to the stereo
system receiver.
Added two drives for 4 Gg of audio file storage, as well.
No networking for it. Standalone system.
( My parents are not interested in learning how to update a Gentoo box. )

No problems.

They got rid of the Cable TV / ISP providers music channels.
No need for them now.

Corbin

Re: [gentoo-user] New install .. no high res console during boot.

[Corbin Bird]

On 01/31/2018 07:38 AM, Harry Putnam wrote:
> Setup:
> Installing gentoo-17 as guest in Vbox vm on solaris-11 HOST 
>(openindiana (powered by Illumos))
>
> VBox 5.6.2
> Kernel-4.15.0
> grub2
>
> I'm a litte confused about how to enable a high res framebuffer
> console.
>
> At gentoo pages:
> https://wiki.gentoo.org/wiki/Xorg/Guide#Kernel_modesetting
>
> I've followed the directions there as far as I could.
>
> lspci on a chroot does not show a driver for the:
>   Innotek Systemberatung Gmbh VirtualBox Graphics Adapter.
>
> And I find nothing about Innotek searching with '/' in menuconfig.
> So could not make any specific settings like those shows on the gentoo
> wiki pages for nVidia and AND/ATI
>
> Other pages such as https://wiki.gentoo.org/wiki/Fbsplash seem to
> indicate I would need to create an initramfs.
>
> The first page cited near the top of post .. tells you NOT to set some
> of the things the citation containing fbsplash (above) tell you to set.
>
> Such as  <*> Userspace VESA VGA
>  [*] Vesa VGA
>
> Is something outdate in one of those pages?
>
> Can someone using the kernel framebuffer explain how to do it on
> gentoo guest of vm?
>
>
>
.
Searched for that "device" and found a few interesting links:
> https://askubuntu.com/questions/435940/do-i-need-linux-drivers-for-virtual-box
> https://www.virtualbox.org/manual/ch04.html
.
If Linux has no access to the actual hardware ... the old "VGA=" hex
codes might work :
> https://www.linuxquestions.org/questions/debian-26/lilo-vga-modes-152575/
I have never tried the codes on "Userspace VESA VGA".
Might want to leave that out for a test run.

.
Corbin 

Re: [gentoo-user] UEFI-fails to boot

[Corbin Bird]

On 01/28/2018 04:35 AM, Dan Johansson wrote:
>>>   ASPEED's AST2500 Display To Be Supported By Linux 4.11's DRM
>>>
>>> https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/x-org-drm/935002-aspeed-s-ast2500-display-to-be-supported-by-linux-4-11-s-drm
> Thanks for that link, I will have to look into that.
> Although I will not be using X on this box, as it is a server, it looks
> like I need to configure DRM.
>
> KR
>
.
This will give you some idea of what version of kernel to aim for :
> index : ~airlied/linux
> https://cgit.freedesktop.org/~airlied/linux/log/?qt=grep=AST2400=1
.
This link forced VESA / frame buffer without 'drm'.
> Xorg support for Aspeed AST2400 VGA controller [solved]
> http://forums.system-rescue-cd.org/viewtopic.php?t=5351
.
Corbin

Re: [gentoo-user] UEFI-fails to boot

[Corbin Bird]

On 01/27/2018 10:06 AM, Dan Johansson wrote:
> According to the supermicro homepage The following Windows versions are
> supported: 7 SP1, 8 Enterprise, 8.1 Enterprise, 10, Server 2008 R2 SP1,
> Server 2012 and Server 2012 R2.
>
> No PCI/PCIe cards installed (yet).
> No special Video driver in the kernel except CONFIG_FB_EFI=y as
> suggested by Johnson Steward.
> The MB has a integrated VGA output.
>
> KR
>
.
Thank you for that info.
.
What kind of integrated VGA?
( example Intel i915, i965, etc. )
.
The reason I ask is that the EFI framebuffer you have enabled should be
built into a specific video driver.
My system has an "amdgpu" video card.
The EFI framebuffer driver for the console is enabled.
The specific video driver called "amdgpu" is also enabled.
The EFI framebuffer is built as a sub-component of the specific video
driver "amdgpu".
.
Sample dmesg output :
> [    6.223405] [drm] amdgpu kernel modesetting enabled.
> [    6.223573] [drm] initializing kernel modesetting (POLARIS10
> 0x1002:0x67DF 0x1682:0x9480 0xC7)
> [    6.882691] Console: switching to colour frame buffer device 240x67
> [    6.900623] amdgpu :01:00.0: fb0: amdgpudrmfb frame buffer device
.
If you haven't already run this command, please do so :  lspci | grep -i VGA
.
If the video device is a 'Aspeed AST', the version number of the
kernel you are using makes a big difference.
>
>
>   ASPEED's AST2500 Display To Be Supported By Linux 4.11's DRM
>
> https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/x-org-drm/935002-aspeed-s-ast2500-display-to-be-supported-by-linux-4-11-s-drm
.
For Intel video devices, this wiki may help :
> https://wiki.gentoo.org/wiki/Intel
.
Corbin

Re: [gentoo-user] Downloading podcasts via the command line?

[Corbin Bird]

On 01/27/2018 06:38 AM, Stroller wrote:
> Can anyone recommend a command line podcast downloader, please?
>
> Ideally I want to run it in a cronjob, saving .mp3 files which can be 
> uploaded to my Google Drive (using net-misc/drive).
>
> My priority is NPR's Planet Money podcasts - I think they're available via 
> RSS, as are BBC Radio 4's Money Box.
>
> Links:
> • https://www.npr.org/sections/money/
> • http://www.bbc.co.uk/programmes/b006qjnv/episodes/downloads
>
> I've also been recommended Money to the Masses which is available by Libsyn, 
> whatever that is - it seems to have download and RSS options.
>
> Thanks in advance for any recommendations,
>
> Stroller.
>
>
.

Libsyn is basically a podcast download archive service. Its part of SoundCloud.

> https://www.libsyn.com/
You will need the correct link to find the podcasts your looking for.
.
Corbin

Re: [gentoo-user] UEFI-fails to boot

[Corbin Bird]

On 01/26/2018 04:00 AM, Dan Johansson wrote:
> On 26.01.2018 02:25, Johnson Steward wrote:
>> Well, check if you have CONFIG_FB_EFI enabled in your config.
> Good idea, but sadly, nope, that was not it.
>
> KR
.
Questions that may sound strange ...
What version of Windows does your motherboard support?
Do you use any add on ( PCI / PCIe ) cards that do not support UEFI and
load a BIOS?
Have you configured a specific type of video card in the kernel?
.
The reasons why I ask this :
The UEFI driver for video changes type & version between Win 7 & Win 8.
An LSI 9211-4i ( Raid Controller / SAS  ) loads only a BIOS ... and
interferes with the Win 8 UEFI Video driver.
( It interferes enough with the Win 8 UEFI Video driver, that Win 7 will
work with it. )
It also means no console video until init is ( almost ) completed.
That is when the chosen specific video card frame buffer takes over.
.
Corbin

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

[Corbin Bird]

On 01/23/2018 11:06 PM, Adam Carter wrote:
>
> FYI, this is from 4.14.15's ChangeLog, doesn't appear to be in 4.9.78
> though.
>
> commit f41b2d7ee791e845147a3e3cafb25493dca6870a
> Author: Josh Poimboeuf >
> Date:   Mon Jan 15 08:17:07 2018 -0600
>
> objtool: Fix seg fault with gold linker
> 
> commit 2a0098d70640dda192a79966c14d449e7a34d675 upstream.
> 
> Objtool segfaults when the gold linker is used with
> CONFIG_MODVERSIONS=y and CONFIG_UNWINDER_ORC=y.
> 
> With CONFIG_MODVERSIONS=y, the .o file gets passed to the linker before
> being passed to objtool.  The gold linker seems to strip unused ELF
> symbols by default, which confuses objtool and causes the seg fault when
> it's trying to generate ORC metadata.
> 
> Objtool should really be running immediately after GCC anyway, without a
> linker call in between.  Change the makefile ordering so that objtool is
> called before the linker.
.
FYI :
Found the culprit ... ( very late last night )
.
sys-kernel/gentoo-sources has a USE Flag of 'experimental'
The experimental patch enables additional choices for CPU.
The last kernel version with no problem was 4.9.76-r1
The choice that worked before was : AMD Piledriver
That induces the error now.
.
When I compiled with CPU set to :
K-8 --> no problem
Generic x86_64 --> no problem
.
That was the only change made in 'menuconfig' before every test compile.
.
Now I know why all the warnings from the 'objtool', during compile, also
disappeared.
( With CPU set to either : K-8, Generic x86_64 )
> Objtool should really be running immediately after GCC anyway, without a
> linker call in between.  Change the makefile ordering so that objtool is
> called before the linker.
Thinking the 'experimental patch' may be needing some attention.
.
So ... now I am looking at filling a bug report ( if appropriate ) on
Gentoo's bug tracker.
.
Thanks to every one who chipped in with suggestions.
.
Corbin

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

[Corbin Bird]

On 01/23/2018 11:35 AM, Rich Freeman wrote:
> Abandoning ext4 over retpolines/etc seems a bit drastic.  My guess is
> that there is a bug in the latest kernel that will get fixed, or maybe
> a bug in gcc (which needs to be patched for spectre anyway).
>
> These Spectre changes are being merged and it has been a real mess.
> The vulnerability is relatively serious so there is a lot of pressure
> to do something, but the changes aren't trivial so they could contain
> bugs or expose compiler bugs.
>
> FWIW upstream 4.9.77 builds just fine for me,
>
> If you want to mess with building alternate kernels to debug this here
> are some instructions I created for this:
>
> As a test you might consider the following:
>
> mkdir /someplace
> cd /someplace
> git clone -b linux-4.9.y
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> .
> mkdir /var/tmp/linux
> cp /path/to/config /var/tmp/linux/.config
> make O=/var/tmp/linux oldconfig
> make O=/var/tmp/linux -j#
>
> That will build the latest stable upstream kernel.
>
> Depending on what you find you can do:
> git checkout v4.9.76
> rm -r /var/tmp/linux
> mkdir /var/tmp/linux
> cp /path/to/config /var/tmp/linux/.config
> make O=/var/tmp/linux oldconfig
> make O=/var/tmp/linux -j#
>
> That will see if 4.9.76 fails.  You could also substitute any version
> you want (including a 4.14 kernel, or an earlier 4.9 kernel).  This
> will give you a sense of whether your toolchain is just entirely
> broken, or if there is an issue with the objtool changes.
>
> Note that you can build away as much as you want without having to
> install any of this - so it won't affect your system at all.  In fact,
> the instructions above will work just fine if you run them as
> non-root, as long as you clone the git sources and put the temp
> directory someplace your non-root user has access to.
>

Tried this ... and here are the steps followed and results :
Note :
CPU defined as K8, NO vendor support for Intel or Centaur, AMD only.
gcc && binutils are both current stable, both r1's. Tested and working.
Both Disabled in 'menuconfig' :
>  [ ] Avoid speculative indirect branches in kernel
>  [ ] Remove the kernel mapping in user mode
The steps followed :
-
mkdir /opt/compile
cd /opt/compile
git clone -b linux-4.9.y
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
renamed 'linux-stable' to 'linux-4.9.77'
ln -s /opt/compile/linux-4.9.77 linux
cd /opt/compile/linux
make menuconfig
mkdir /var/tmp/linux
cp /opt/compile/linux/.config /var/tmp/linux/.config
make O=/var/tmp/linux oldconfig
make O=/var/tmp/linux -j9
-
The results ( first pass ) :

>   HOSTCC  arch/x86/tools/relocs_64.o
>   HOSTCC  arch/x86/tools/relocs_common.o
>   Using /opt/compile/linux-4.9.77 as source for kernel
>   /opt/compile/linux-4.9.77 is not clean, please run 'make mrproper'
>   in the '/opt/compile/linux-4.9.77' directory.
> make[1]: *** [/opt/compile/linux-4.9.77/Makefile:1021: prepare3] Error 1
> make[1]: *** Waiting for unfinished jobs
>   HOSTLD  arch/x86/tools/relocs
> make[1]: Leaving directory '/var/tmp/linux'
> make: *** [Makefile:150: sub-make] Error 2

So ... I ran 'make mrproper' in '/opt/compile/linux-4.9.77/'
The result :

>   HOSTCC  arch/x86/tools/relocs_64.o
>   HOSTCC  arch/x86/tools/relocs_common.o
>   Using /opt/compile/linux-4.9.77 as source for kernel
>   /opt/compile/linux-4.9.77 is not clean, please run 'make mrproper'
>   in the '/opt/compile/linux-4.9.77' directory.
> make[1]: *** [/opt/compile/linux-4.9.77/Makefile:1021: prepare3] Error 1
> make[1]: *** Waiting for unfinished jobs
>   HOSTLD  arch/x86/tools/relocs
> make[1]: Leaving directory '/var/tmp/linux'
> make: *** [Makefile:150: sub-make] Error 2

Something is not right 
  HOSTCC  arch/x86/tools/relocs_64.o
  HOSTCC  arch/x86/tools/relocs_common.o
  HOSTLD  arch/x86/tools/relocs
Is this the 'Spectre/Meltdown' patches again?!?

Corbin

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

[Corbin Bird]

On 01/23/2018 11:59 AM, Wol's lists wrote:
> On 23/01/18 17:35, Rich Freeman wrote:
>>> Wonderful ... just finished a complete reload of Gentoo. Now have to
>>> redo it again ...
>>> ... the mistake? I used ext2/ext3 for the fs.
>>>
>> Abandoning ext4 over retpolines/etc seems a bit drastic.  My guess is
>> that there is a bug in the latest kernel that will get fixed, or maybe
>> a bug in gcc (which needs to be patched for spectre anyway).
>
> Did you use the ext2/ext3 driver? I believe it's been abandoned?
>
> The ext4 driver is compatible with 2/3 file systems, so as I
> understand it all development effort goes into the ext4 driver, and
> any problems with the older drivers is likely to be met with "upgrade
> your driver".
>
> So if you were using that driver, it could be suffering bit-rot.
>
> Cheers,
> Wol
>
Sometime back the kernel devs decided to 'remove' the ext2 / ext3 fs
drivers.
The ext2 / ext3 fs drivers are NOT available.
Any choice of ext2 / ext3 forces the use of the ext4 fs driver.
If I could use the real ext2 / ext3 fs drivers ...
... I would in the blink of an eye.

ext2 / ext3 are the definition of 'stable' file systems.
ext4  unstable, still in development, prone to breakage.

Corbin

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

[Corbin Bird]

> The 4.9.77 announcement upstream did introduce a number of objtool
> changes. See below.
> https://lkml.org/lkml/2018/1/17/198
> Josh Poimboeuf (4):
>   objtool, modules: Discard objtool annotation sections for modules
>   objtool: Detect jumps to retpoline thunks
>   objtool: Allow alternatives to be ignored
>   objtool: Fix retpoline support for pre-ORC objtool
>
> I can't seem to remember seeing reports of the issue you're having on
> the LMKL, since 4.9.77 was announced.
> As you said, try re-emerging the gentoo kernel, make mrproper, no need
> for distclean, which does run mrproper as part of its operation, and
> see if that helps.
> Alternatively, you could try building the upstream version of 4.9.77,
> and see if that works. Let me know if you need instructions on how to
> proceed with that.
>

FYI :
Just tried a different compile.
Switched off expert and flipped the CPU to "Generic x86_64" ( no other
changes ).

It compiled. ??

So ... what you choose for CPU in the kernel determines if the
ext2/ext3/ext4 fs driver will compile.

Been using Gentoo / "sys-kernel/gentoo-sources" w/experimental for 3+
years now.
First time the CPU choice has caused a problem.

Suspect that a mismatch of the "Spectre / Meltdown" patches that have
somehow gotten into the ext4 fs driver and the code for specific CPUs.

Wonderful ... just finished a complete reload of Gentoo. Now have to
redo it again ...
... the mistake? I used ext2/ext3 for the fs.

Corbin

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

[Corbin Bird]

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
>>> check "fs/ext4/extents_status.o"
>>> make[3]: *** [/usr/src/linux-4.9.77-gentoo/scripts/Makefile.build:294:
>>> fs/ext4/extents_status.o] Error 139
>>> make[2]: *** [/usr/src/linux-4.9.77-gentoo/scripts/Makefile.build:544:
>>> fs/ext4] Error 2
>>> make[1]: *** [/usr/src/linux-4.9.77-gentoo/Makefile:995: fs] Error 2
>>> make[1]: Leaving directory '/var/tmp/linux'
&g

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

[Corbin Bird]

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
> check "fs/ext4/extents_status.o"
> make[3]: *** [/usr/src/linux-4.9.77-gentoo/scripts/Makefile.build:294:
> fs/ext4/extents_status.o] Error 139
> make[2]: *** [/usr/src/linux-4.9.77-gentoo/scripts/Makefile.build:544:
> fs/ext4] Error 2
> make[1]: *** [/usr/src/linux-4.9.77-gentoo/Makefile:995: fs] Error 2
> make[1]: Leaving directory '/var/tmp/linux'
> make: *** [Makefile:150: sub-make] Error 2
Try 2 gave an error warning about needing an 'make mrproper' ... the error :
>
>   CHK include/config/kernel.release
>   UPD include/config/kernel.release
>   Using /usr/src/linux-4.9.77-gentoo as source for kernel
>   /usr/src/linux-4.9.77-gentoo is not clean, please run 'make mrproper'
>   in the '/usr/src/linux-4.9.77-gentoo' directory.
> make[1]: *** [/usr/src/linux-4.9.77-gentoo/Makefile:1021: prepare3]
> Error 1
> make[1]: Leaving directory '/var/tmp/linux'
> make: *** [Makefile:150: sub-make] Error 2
So ... I followed directions :
> Darkstar /usr/src/linux # cd /usr/src/linux-4.9.77-gentoo
> Darkstar /usr/src/linux-4.9.77-gentoo # make mrproper
>   CLEAN   scripts/basic
>   CLEAN   scripts/kconfig
>   CLEAN   .config

Still get the same error ...

Corbin

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

[Corbin Bird]

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

Re: [gentoo-user] Re: Kernel 4.14.14 has meltdown / spectre info in /sys

[Corbin Bird]

On 01/18/2018 02:43 PM, Rich Freeman wrote:
> cat /sys/devices/system/cpu/vulnerabilities/meltdown

Strange, get this response from kernel 4.9.76-r1
> Darkstar ~ # cat /sys/devices/system/cpu/vulnerabilities/meltdown
> cat: /sys/devices/system/cpu/vulnerabilities/meltdown: No such file or
> directory

/proc/cpuinfo has not changed.
> Darkstar ~ # cat /proc/cpuinfo
> processor    : 0
> vendor_id    : AuthenticAMD
> cpu family    : 21
> model        : 2
> model name    : AMD FX(tm)-9590 Eight-Core Processor
> stepping    : 0
> microcode    : 0x600084f
> cpu MHz        : 4700.000
> cache size    : 2048 KB
> bugs        : fxsave_leak sysret_ss_attrs null_seg

Did you compile your kernel with "vendor support" for Intel enabled?

Corbin

Re: [gentoo-user] emerge error for dev-lisp/clisp-2.49-r9

[Corbin Bird]

On 01/14/2018 02:39 PM, Quico Jurado wrote:
> Hello,
>
> After doing doing the upgrade to my 17.0 profile
> (`default/linux/amd64/17.0/desktop'), and recompiling all my packages
> I ran into a problem while installing clisp. Basically is bailing out
> on the configure stage, this is the relevant output of the configure
> script (suppressed some output to reduce the noise):
>
> gcc version 6.4.0 (Gentoo 6.4.0-r1 p1.3)
> configure:3901: $? = 0
> configure:3890: gcc -V >&5
> gcc: error: unrecognized command line option '-V'
> gcc: fatal error: no input files
> compilation terminated.
> configure:3901: $? = 1
> configure:3890: gcc -qversion >&5
> gcc: error: unrecognized command line option '-qversion'; did you mean
> '--v
> ersion'?
> gcc: fatal error: no input files
> compilation terminated.
> configure:3901: $? = 1
> configure:3921: checking whether the C compiler works
> configure:3943: gcc -march=native -O2 -pipe -fno-pie
> -Wa,--noexecstack  -I/usr/include/db4.8 -Wl,-O1 -Wl,--as-needed
> conftest.c  >&5
> configure:3947: $? = 0
> configure:3996: result: yes
> ...
> configure:4062: checking whether we are cross compiling
> configure:4070: gcc -o conftest -march=native -O2 -pipe -fno-pie
> -Wa,--noexecstack  -I/usr/include/db4.8 -Wl,-O1 -Wl,--as-needed
> conftest.c  >&5
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../x86_64-pc-linux-gnu/bin/ld:
> /var/tmp/portage/dev-lisp/clisp-2.49-r9/temp/ccPeB6Vb.o: relocation
> R_X86_64_32 against `.rodata.str1.1' can not be used when making a
> shared object; recompile with -fPIC
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../x86_64-pc-linux-gnu/bin/ld:
> final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status
> configure:4074: $? = 1
> configure:4081: ./conftest
> configure: line 4083: ./conftest: No such file or directory
> configure:4085: $? = 127
> ...
> configure:4096: error: cannot run C compiled programs.
> If you meant to cross compile, use `--host'.
>
> Any help to work this out is much appreciated.
>
> Thanks,

>From the ebuild :
>     # Bug 618170. If anyone has a better idea...
>     append-flags -fno-pie

This ebuild is using "EAPI=5".
Looks like it hasn't been updated in a while.

Profile 17 FORCES the use of PIE/PIC.
( -fPIC, -fPIE are appended to the gcc commands )

I suspect that the Profile 17 forced flags would have to be disabled
somehow.
Have no idea if that is possible.

Corbin

Re: [gentoo-user] Re: glibc emerge error

[Corbin Bird]

On 01/12/2018 04:14 PM, Nikos Chantziaras wrote:
> echo "$VULKAN_SDK/lib" > /etc/ld.so.conf.d/vulkan-loader.conf 

Found out what was giving me an extra slash in the output "...x86_64//lib"
The $VULKAN_SDK PATH had a slash at the end.

Works now. Thank you.

Corbin

Re: [gentoo-user] Microcode updates for "old" Intel CPU's

[Corbin Bird]

On 01/12/2018 12:42 PM, Mick wrote:
> On Friday, 12 January 2018 17:47:46 GMT Rich Freeman wrote:
>> On Fri, Jan 12, 2018 at 11:23 AM, Corbin Bird <corbinb...@charter.net> 
> wrote:
>>> On 01/11/2018 05:02 PM, Rich Freeman wrote:
>>>> IMO Spectre is going to drive some microcode updates for relatively
>>>> recent CPUs, compiler improvements, and some hand-tuning of
>>>> particularly critical code.
>>> The microcode updates pushed out for AMD by Gentoo seem to be only for :
>>> Fam16h, Fam17h CPUs.
>> FWIW even the 17h microcode doesn't seem to be updating on my Ryzen:
>>
>> dmesg | grep microco
>> [0.989279] microcode: CPU0: patch_level=0x08001129
>> [0.989421] microcode: CPU1: patch_level=0x08001129
>> [0.989565] microcode: CPU2: patch_level=0x08001129
>> [0.989708] microcode: CPU3: patch_level=0x08001129
>> [0.989857] microcode: CPU4: patch_level=0x08001129
>> [0.990001] microcode: CPU5: patch_level=0x08001129
>> [0.990183] microcode: CPU6: patch_level=0x08001129
>> [0.990332] microcode: CPU7: patch_level=0x08001129
>> [0.990475] microcode: CPU8: patch_level=0x08001129
>> [0.990619] microcode: CPU9: patch_level=0x08001129
>> [0.990764] microcode: CPU10: patch_level=0x08001129
>> [0.990905] microcode: CPU11: patch_level=0x08001129
>> [0.991095] microcode: Microcode Update Driver: v2.2.
> My AMD:
>
> [0.025000] smpboot: CPU0: AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G 
> (family: 0x15, model: 0x30, stepping: 0x1)
>
> is similarly failing to show signs of early microcode update, as it always 
> did:
>
> $ dmesg | grep -i microcode
> [1.348991] microcode: CPU0: patch_level=0x06003106
> [1.349718] microcode: CPU1: patch_level=0x06003106
> [1.350434] microcode: CPU2: patch_level=0x06003106
> [1.351158] microcode: CPU3: patch_level=0x06003106
> [1.351879] microcode: Microcode Update Driver: v2.2.
>
>
>> That said, there still isn't any AMD documentation around the
>> microcode updates that I've been able to find, so I have no idea what
>> the correct patch level is even supposed to be.  I just know that I'm
>> not getting a message about early updates.  I do have linux 4.4.13
>> which includes the family 17h patch.
> I'm on 4.14.12-gentoo now.
>
>
>> The other odd thing is that a firmware update was released for my
>> motherboard (ASRock AB350 Pro4) on the 10th, and if I flash it grub
>> will no longer boot the linux kernel, and it is pretty slow overall,
>> but it will still boot memtestx86 just fine.  I figured I'd wait a few
>> days and see if there is any further info on it.
> No Asus MoBo firmware updates here ... but would they be even required/
> necessary for the CPU bugs?

In the old days, Windows / DOS, did not have any "microcode update
loader". For those old versions of Windows / DOS, an updated BIOS was
the only way to update the CPU microcode.

I have seen something calling itself the "microcode update loader" in
Win 7 x64. Have no idea what it is really doing.

---

The Fam16h and Fam17h microcode updates were new to Gentoo?
I don't recall ever seeing them before.

Corbin

Re: [gentoo-user] Re: glibc emerge error

[Corbin Bird]

On 01/11/2018 08:29 AM, Nikos Chantziaras wrote:
> On 11/01/18 15:28, Corbin Bird wrote:
>>> Why are you setting LD_LIBRARY_PATH system-wide to begin with? Don't
>>> do that.
>>
>> Unfortunately, I had to ( and didn't realize the implications. )
>> In .bashrc :
>>> export LD_LIBRARY_PATH=$VULKAN_SDK/lib:$LD_LIBRARY_PATH
>>
>> Required by the Vulkan Loader ( Mesa && Chromium ).
>
> I think this is what the /etc/ld.so.conf.d/ directory is there for.
> Have you tried something like this instead:
>
>   echo "$VULKAN_SDK/lib" > /etc/ld.so.conf.d/vulkan-loader.conf
>   env-update
>
>

Will try this method and see what happens.

Checked a file already there. In the "05gcc-x86_64-pc-linux-gnu.conf"
there were no $PATH variables.
Put explicit paths in instead.

This will be interesting.

Corbin

Re: [gentoo-user] Microcode updates for "old" Intel CPU's

[Corbin Bird]

On 01/11/2018 05:02 PM, Rich Freeman wrote:
> On Thu, Jan 11, 2018 at 5:41 PM, Mick  wrote:
>> Most vendors only sell Intel in their laptops.  I could build a desktop I
>> guess, but Ryzen is also affected by Spectre.  With Intel's burning platform 
>> I
>> want to jump off, but I'm not sure if spending money at this stage will
>> materially improve my PC security ... or if it is wiser to wait for the next
>> round of 'improved' CPUs.
>>
> I wouldn't let Spectre drive you to hold off on buying a CPU.  If
> you're happy with what you have stick with it.  If not get what makes
> the most sense, which is probably Ryzen at this point unless your
> particular workload benefits from the marginal single-thread
> performance of Intel even after any Meltdown handicaps.
>
> IMO Spectre is going to drive some microcode updates for relatively
> recent CPUs, compiler improvements, and some hand-tuning of
> particularly critical code.
>

FYI :

The microcode updates pushed out for AMD by Gentoo seem to be only for :
Fam16h, Fam17h CPUs.

Fam15h, Fam10h, no change.
"dmesg" output unchanged, before and after updating.
( Yes, the firmware update is built-in to the kernel. )

[    0.114108] smpboot: CPU0: AMD FX(tm)-9590 Eight-Core Processor
(family: 0x15, model: 0x2, stepping: 0x0)
[    0.114113] Performance Events: Fam15h core perfctr, AMD PMU driver.

[   10.296207] microcode: microcode updated early to new
patch_level=0x0600084f
[   10.296915] microcode: CPU0: patch_level=0x0600084f
[   10.297658] microcode: CPU1: patch_level=0x0600084f
[   10.298338] microcode: CPU2: patch_level=0x0600084f
[   10.299093] microcode: CPU3: patch_level=0x0600084f
[   10.299813] microcode: CPU4: patch_level=0x0600084f
[   10.300502] microcode: CPU5: patch_level=0x0600084f
[   10.301193] microcode: CPU6: patch_level=0x0600084f
[   10.301849] microcode: CPU7: patch_level=0x0600084f
[   10.302601] microcode: Microcode Update Driver: v2.01
, Peter Oruba

Re: [gentoo-user] Re: glibc emerge error

[Corbin Bird]

On 01/10/2018 01:53 PM, Nikos Chantziaras wrote:
> On 10/01/18 19:55, Corbin Bird wrote:
>> Is anyone else having a sys-libs/glibc emerge compile failure?
>>
>>> checking for python3... python3
>>> checking LD_LIBRARY_PATH variable... contains current directory
>>> configure: error:
>>> *** LD_LIBRARY_PATH shouldn't contain the current directory when
>>> *** building glibc. Please change the environment variable
>>> *** and run configure again.
>>>   * ERROR: sys-libs/glibc-2.25-r10::gentoo failed (configure phase):
>>>   *   failed to configure glibc
>>
>> sys-libs/glibc-2.25-r9 was set to masked / prompting this upgrade /
>> re-compile:
>>
>> https://packages.gentoo.org/packages/sys-libs/glibc
>>
>> Same error regardless of the version of glibc I attempt to emerge.
>
> Why are you setting LD_LIBRARY_PATH system-wide to begin with? Don't
> do that.
>
>

Unfortunately, I had to ( and didn't realize the implications. )
In .bashrc :
> export LD_LIBRARY_PATH=$VULKAN_SDK/lib:$LD_LIBRARY_PATH

Required by the Vulkan Loader ( Mesa && Chromium ).

Corbin

Re: [gentoo-user] glibc emerge error

[Corbin Bird]

On 01/10/2018 12:22 PM, Matthias Hanft wrote:
> Corbin Bird wrote:
>> Is anyone else having a sys-libs/glibc emerge compile failure?
>>> *** LD_LIBRARY_PATH shouldn't contain the current directory when
>>> *** building glibc. Please change the environment variable
>>> *** and run configure again.
>> Same error regardless of the version of glibc I attempt to emerge.
> Sure - this error always comes up here, too. Just enter
>
> export LD_LIBRARY_PATH=
>
> immediately before emerge, and it works.
>
> -Matt
>
> PS: And if you get some message concerning some variables which
> are too big (or something like that), enter
>   mount -t tmpfs none /var/tmp/portage
> just before emerge (and "umount /var/tmp/portage" afterwards).
> I have to do this for the emerge of a few packages - I think
> it's because of my 17 TB filesystem.
>
>

Thanks, that fixed it.

Corbin

[gentoo-user] glibc emerge error

[Corbin Bird]

Is anyone else having a sys-libs/glibc emerge compile failure?

> checking for python3... python3
> checking LD_LIBRARY_PATH variable... contains current directory
> configure: error:
> *** LD_LIBRARY_PATH shouldn't contain the current directory when
> *** building glibc. Please change the environment variable
> *** and run configure again.
>  * ERROR: sys-libs/glibc-2.25-r10::gentoo failed (configure phase):
>  *   failed to configure glibc

sys-libs/glibc-2.25-r9 was set to masked / prompting this upgrade /
re-compile:

https://packages.gentoo.org/packages/sys-libs/glibc

Same error regardless of the version of glibc I attempt to emerge.

Corbin

Re: [gentoo-user] Microcode updates for "old" Intel CPU's

[Corbin Bird]

On 01/09/2018 01:56 AM, Mick wrote:
> On Monday, 8 January 2018 17:47:03 GMT Corbin Bird wrote:
>> On 01/07/2018 02:46 PM, taii...@gmx.com wrote:
>>> I have several sandy/ivybridge CPU's and I was wondering if anyone
>>> knows as to if intel is releasing microcode updates for them.
>>>
>>> It sure would be funny if intel wanted you to buy a new CPU to fix a
>>> problem that was their fault to begin with.
>> Do you remember the x87 bugs discovered in the original i586 Pentiums?
>> Never fixed.
>> Still built into every Intel CPU.
>> Intel does NOT replace "defective-by-design" hardware.
>> Instead, every OS is required to "software emulate" the FPU.
>>
>> Search for "errata-not-bug".
>> Intel's term for their screw-ups in their CPUs.
>>
>> Intel is only releasing patch code for the last five years of products.
>>
>> And ... if you read up on the "e-mails" being posted ...
>> ... It looks as if Intel is NOT going to fix this in future CPUs either.
>> Instead, every OS will be required to "work-around-this".
>>
>> Perhaps the reason "someone" tried to implicate this effects ALL CPU
>> architectures?
>> ( IBM RISC 6000, PowerPC, DEC Alpha, IBM System/390, Sun SPARC64, for
>> example )
>>
>> Intel did try to make their "patch" mandatory for AMD CPUs ( with NO
>> disable switch ).
>> Why?
>> Think about it.
>>
>> Corbin
> So what affordable and available CPUs should one be looking into for a new 
> desktop build?
>
> Also, laptops?
>

At this point, the only sure bet, is a non x86, x86_64, ARM, ARM64 CPU.

Don't know enough to make a recommendation on a particular CPU arch at
this point.

Try asking taii...@gmx.com  or Ian Zimmerman ( both on gentoo-users
mailing list ) about PPC/PPC64.

Re-post of saved e-mail :
> On 12/25/2017 06:33 PM, Ian Zimmerman wrote:
>
>> On 2017-12-24 14:44, taii...@gmx.com wrote:
>>
>>> POWER 9: TALOS 2 (server/workstation, brand new and very high
>>> performance - the only brand new hardware that is legitimately libre)
>> This is interesting, but can it run gentoo?  There's a handbook edition
>> for PPC64, but that's not quite the same, is it?
> It is.
> PPC64 is big endian, PPC64LE is little endian.
>
> POWER8/9 are Bi-Endian so you can use both (most linux distros only
> support little)
>
> PPC64 compile covers PowerPC and POWER.
>
>
> TALOS 2 is an end user obtainable derivative of the Romulus POWER 9
> development board, there are a variety of modifications and it is more
> open source than Romulus - you can also pay for it with bitcoin.
> It supports dual sforza CPU's which have up to 24 cores per socket
> with SMT4 (4 threads at the same time per core) 

Re: [gentoo-user] microcode applied?

[Corbin Bird]

On 01/07/2018 09:24 PM, Adam Carter wrote:
> Does the absence of a "microcode updated" message in dmesg imply that
> the microcode was not updated?
>
> I believe my fam10/barcelona AMD CPU will use
> amd-ucode/microcode_amd.bin but there's no update message.
>
> I've checked the config against another system that works and cant see
> any errors. Is there a way to turn on debugging?

Sample "dmesg" output for a Fam15h AMD ( Kernel 4.9.xx ) :
> [   10.336395] microcode: microcode updated early to new
> patch_level=0x0600084f
> [   10.337132] microcode: CPU0: patch_level=0x0600084f
> [   10.337839] microcode: CPU1: patch_level=0x0600084f
> [   10.338631] microcode: CPU2: patch_level=0x0600084f
> [   10.342083] microcode: CPU3: patch_level=0x0600084f
> [   10.342756] microcode: CPU4: patch_level=0x0600084f
> [   10.343468] microcode: CPU5: patch_level=0x0600084f
> [   10.344117] microcode: CPU6: patch_level=0x0600084f
> [   10.344786] microcode: CPU7: patch_level=0x0600084f
> [   10.345615] microcode: Microcode Update Driver: v2.01
> , Peter Oruba
Output is very similar for Fam10h AMDs as well ( Phenom II x4 980 )

Re: [gentoo-user] Microcode updates for "old" Intel CPU's

[Corbin Bird]

On 01/07/2018 02:46 PM, taii...@gmx.com wrote:
> I have several sandy/ivybridge CPU's and I was wondering if anyone
> knows as to if intel is releasing microcode updates for them.
>
> It sure would be funny if intel wanted you to buy a new CPU to fix a
> problem that was their fault to begin with.
>
>
Do you remember the x87 bugs discovered in the original i586 Pentiums?
Never fixed.
Still built into every Intel CPU.
Intel does NOT replace "defective-by-design" hardware.
Instead, every OS is required to "software emulate" the FPU.

Search for "errata-not-bug".
Intel's term for their screw-ups in their CPUs.

Intel is only releasing patch code for the last five years of products.

And ... if you read up on the "e-mails" being posted ...
... It looks as if Intel is NOT going to fix this in future CPUs either.
Instead, every OS will be required to "work-around-this".

Perhaps the reason "someone" tried to implicate this effects ALL CPU
architectures?
( IBM RISC 6000, PowerPC, DEC Alpha, IBM System/390, Sun SPARC64, for
example )

Intel did try to make their "patch" mandatory for AMD CPUs ( with NO
disable switch ).
Why?
Think about it.

Corbin

Re: [gentoo-user] Fail to configure polari and gnome-documents with portage.

[Corbin Bird]

On 01/04/2018 10:31 AM, Personal wrote:
> Hi list.
>
> I can't install polari and gnome-documents using portage. Using
> ./configure by myself there is no problem. I post the polari output:
>
 Emerging (1 of 1) net-irc/polari-3.22.2::gentoo
>  * polari-3.22.2.tar.xz BLAKE2B SHA512 size ;-)
> ...
>   [ ok ]
 Unpacking source...
 Unpacking polari-3.22.2.tar.xz to /var/tmp/portage/net-irc/polari-
> 3.22.2/work
 Source unpacked in /var/tmp/portage/net-irc/polari-3.22.2/work
 Preparing source in /var/tmp/portage/net-irc/polari-
> 3.22.2/work/polari-3.22.2 ...
>  * Disabling deprecation warnings
> ...
> [ ok ]
>  * Running elibtoolize in: polari-3.22.2/
>  *   Applying ppc64le/2.4.4 patch ...
>  * Running elibtoolize in: polari-3.22.2/build-aux/
>  *   Applying portage/1.2.0 patch ...
>  *   Applying sed/1.5.6 patch ...
>  *   Applying as-needed/2.4.3 patch ...
 Source prepared.
 Configuring source in /var/tmp/portage/net-irc/polari-
> 3.22.2/work/polari-3.22.2 ...
>  * econf: updating polari-3.22.2/build-aux/config.sub with
> /usr/share/gnuconfig/config.sub
>  * econf: updating polari-3.22.2/build-aux/config.guess with
> /usr/share/gnuconfig/config.guess
> ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-
> linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --
> datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --
> disable-dependency-tracking --disable-silent-rules --
> docdir=/usr/share/doc/polari-3.22.2 --htmldir=/usr/share/doc/polari-
> 3.22.2/html --libdir=/usr/lib64 --disable-maintainer-mode --disable-
> schemas-compile --enable-compile-warnings=minimum
> checking for a BSD-compatible install...
> /usr/lib/portage/python2.7/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 whether UID '250' is supported by ustar format... yes
> checking whether GID '250' is supported by ustar format... yes
> checking how to create a ustar tar archive... gnutar
> checking whether make supports nested variables... (cached) yes
> checking whether to enable maintainer-specific portions of Makefiles...
> no
> checking for x86_64-pc-linux-gnu-pkg-config... /usr/bin/x86_64-pc-
> linux-gnu-pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for gobject-introspection... yes
> checking whether to enable debugging... no
> 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 how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -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 minix/config.h usability... no
> checking minix/config.h presence... no
> checking for minix/config.h... no
> checking whether it is safe to define __EXTENSIONS__... yes
> checking for a sed that does not truncate output... /bin/sed
> checking whether C compiler accepts -Werror=unknown-warning-option...
> no
> checking whether C compiler accepts -fno-strict-aliasing... yes
> checking whether C compiler accepts -Wall... yes
> checking whether C compiler accepts -Wextra... yes
> checking whether C compiler accepts -Wundef... yes
> checking whether C compiler accepts -Wnested-externs... yes
> checking whether C compiler accepts -Wwrite-strings... yes
> checking whether C compiler accepts -Wpointer-arith... yes
> checking whether C compiler accepts -Wmissing-declarations... yes
> checking whether C compiler accepts -Wmissing-prototypes... yes
> checking whether C compiler accepts -Wstrict-prototypes... yes
> checking whether C compiler accepts -Wredundant-decls... 

Re: [gentoo-user] Expect a ~15% average slowdown if you use an Intel processor

[Corbin Bird]

On 01/04/2018 08:17 AM, Rich Freeman wrote:
> On Thu, Jan 4, 2018 at 8:44 AM, Corbin Bird <corbinb...@charter.net> wrote:
>> According to the Project Zero documentation  having BPF JIT enabled
>> is the key to the exploit.
>>
>> The way the docs read ... can it be assumed that by having BPF JIT
>> disabled on an AMD, that blocks this exploit?
>>
> I'm still working through the details, but AMD seems to only be
> vulnerable to variant 1 (based on AMD's reports), and for Linux that
> requires that BPF JIT be both built into the kernel (compile-time),
> and enabled in sysctl (net.core.bpf_jit_enable).  From what I can tell
> variant 1 requires that the vulnerable code actually be executed in
> the kernel security context.  I'm sure a fix to BPF will be made to
> close that.  There might also be some other code that can be tricked
> in the kernel but there are no reports of this.
>
> For variant 2 (not exploitable on AMD), it sounds like the BPF code
> need merely be present in kernel virtual memory while running in user
> security context.  That would mean that it would need to be built at
> compile-time, and loaded (if in a module), but it wouldn't have to be
> enabled in sysctl.  I didn't see any mention of it but I would think
> that the PTI fixes might close this hole on Intel, since then when the
> CPU is in user security context the BPF code would not be present in
> virtual memory.  Intel posted a separate compile-time fix to lkml
> yesterday as well, with an amusing response from Linus in his usual
> style, and an even more amusing subsequent joke about needing to add a
> perl interpreter to the kernel.
>
> Variant 1 does exploit CPU behavior, but I suspect it could be fixed
> with a change to gcc to recognize these kinds of indirect memory
> references and ensure they're not executed speculatively.  That fix
> would be applicable to anything that runs untrusted code in a sandbox,
> such as browsers.  That variant isn't about crossing CPU privilege
> boundaries so much as getting code that is legitimately being run to
> leak state through the cache as a backchannel.
>
> Note: I'm not an expert on any of this stuff, and if somebody wants to
> chime in with details/adjustments to the above I'm all ears.
>

So  kill all BPF JIT support / leave BPF JIT out of the kernel / no
kernel modules either == attack Variant #1 fails.
The "current workaround" ( for AMD CPU's ) is how I read it.

Thanks for the info.

Corbin

Re: [gentoo-user] Expect a ~15% average slowdown if you use an Intel processor

[Corbin Bird]

On 01/03/2018 09:34 PM, Adam Carter wrote:
>
> Project Zero (Google) found it;
> 
> https://googleprojectzero.blogspot.com.au/2018/01/reading-privileged-memory-with-side.html
> 
> 
>
>
> Phoronix has done some benchmarks on the impact of the kernel
> based workaround ([Kernel] Page Table Isolation (PSI) nee Kaiser)
> 
> https://www.phoronix.com/scan.php?page=article=linux-more-x86pti=1
> 
> 
>
>
> *
> *
> Re:AMD  - Looks like Linus agrees that PTI is not required for AMD
> CPUs. Note that the project zero blog mentions that some AMD chips are
> subject to some issues*. *There's three CVEs*.
> *
> *
> *
> From:
> https://www.phoronix.com/scan.php?page=news_item=Linux-Tip-Git-Disable-x86-PTI*
> *
> *"Update:* Linus Torvalds has now ended up pulling
> 
> the latest PTI fixes that also include the change to disable page
> table isolation for now on all AMD CPUs. The commit is in mainline for
> Linux 4.15 along with a few basic fixes and ensuring
> PAGE_TABLE_ISOLATION is enabled by default. "

According to the Project Zero documentation  having BPF JIT enabled
is the key to the exploit.

The way the docs read ... can it be assumed that by having BPF JIT
disabled on an AMD, that blocks this exploit?

Corbin

Re: [gentoo-user] No beep.

[Corbin Bird]

On 08/14/2017 01:22 PM, Alan Mackenzie wrote:
> Hello, Gentoo.
> 
> I've almost got my new(ish) machine up and running.  In particular, I've
> got an email server (s/qmail) running on it, the most difficult part of
> bringing up a new box.
> 
> However, during the building, I discovered to my disgust that there was
> no loudspeaker in my new case.  So, none of the helpful booting beeps
> that the motherboard uses to tell us that something's wrong.  Still, I
> got past that stage.
> 
> But just typing into a virtual tty, sometimes the system (should) beep.
> It doesn't.  It should.
> 
> It should, because I compiled the kernel with CONFIG_SND_HDA_INPUT_BEEP
> and CONFIG_SND_HDA_INPUT_BEEP_MODE set to 1.
> 
> My loudspeakers are working, as shown by running speaker-test.  I'm
> using the kernel I think I am, verified by checking those two config
> settings in /proc/config.gz.
> 
> Would somebody please suggest to me where I am going wrong, here?
> 
> Thanks!
> 

Apologies, if this is just a stupid question ...

Did you purchase / install the old BIOS / Case speaker?
... yes, that 80's piece of speaker tech :)

Newer motherboards and cases don't come with one.
Had to spend ... $3 for a new one.
(U)EFI won't go BEEP! without one.

Corbin

Re: [gentoo-user] managing chromium exceptions

[Corbin Bird]

On 06/04/2017 09:39 AM, Daniel Frey wrote:
> On 06/04/2017 02:17 AM, Jorge Almeida wrote:
>> I just had the experience of visiting a linux-related site
>> (http://libv.livejournal.com/22968.html) and seeing a panel with ads
>> about house appliances (from a site I had actually visited before).
>> The panel actually blocks part of the page, and is impossible to
>> remove. This is caused by some javascript linked to some crap-factory
>> named criteo.com.
>> I'm using chromium, but I just checked that the same happens with
>> Firefox, so the fault lies with
>> http://libv.livejournal.com and not with Google (for once)
>>
>> Now, I tried to edit the settings of chromium to block javascript from
>> criteo.com. Guess what, the "manage exceptions..." dialog opens a
>> popup window with an example for the aptly named domain example.com,
>> and _doesn't allow any change at all_! No way to add an exception, nor
>> to remove it (not that there's much to remove)
>>
>> Ah, the state of browsers for linux!
>>
>> Please tell me I'm not the only one to whom such beautiful things happen.
>>
>> Jorge Almeida
>>
> 
> Bad news...
> 
> I have Chrome installed, and I went to the first linked website and
> added a Block exception for criteo.com no problem.
> 
> Dan
> 

Using Chromium and uMatrix / uBlock Origin Plugins, no problem with the
page. No ads or Java errors.
( No, not the 'www-plugins/chrome-binary-plugins'. )

Corbin

Re: [gentoo-user] Re: Issues with AMD_IOMMU

[Corbin Bird]

On 05/21/2017 06:12 PM, Adam Carter wrote:
> 
> 
> > [0.991863] iommu: Adding device :06:00.0 to group 12
> > [0.991982] iommu: Adding device :07:04.0 to group 12
> > [1.063849] AMD-Vi: Found IOMMU at :00:00.2 cap 0x40
> > [1.063962] AMD-Vi: Interrupt remapping enabled
> > [1.064145] AMD-Vi: Lazy IO/TLB flushing enabled
> > [1.065331] perf: AMD NB counters detected
> 
> 
> I'm similar, but have a couple of extra entries. I've read a little bit
> about them, but so far am unable to determine if their existence
> indicates a better or worse kernel config.
> 
> [1.036309] AMD-Vi: Lazy IO/TLB flushing enabled
> [1.036419] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
> [1.036529] software IO TLB [mem 0xba61a000-0xbe61a000] (64MB) mapped
> at [a3b87a61a000-a3b87e619fff]
> [1.036744] perf: AMD NB counters detected
> 
> And the Linux AGP Driver ( in-kernel ) is working now.
> 
> Now this is showing properly with lspci :
> 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD/ATI] RD890S/RD990 I/O
> Memory Management Unit (IOMMU)
> 
> 
> Same.

The (SWIOTLB) should not be the default.

What kernel parameters for IOMMUs are you using now?

The listed result I posted is with nothing related to IOMMUs in the
kernel parameters, and NO GART IOMMU support compiled.


Corbin

Re: [gentoo-user] Re: Issues with AMD_IOMMU

[Corbin Bird]

On 05/19/2017 01:39 AM, Adam Carter wrote:
> On Wed, May 17, 2017 at 12:25 AM, Corbin Bird <corbinb...@charter.net
> <mailto:corbinb...@charter.net>> wrote:
> 
> On 05/16/2017 01:34 AM, Adam Carter wrote:
> > Answer #1 :
> >
> >
> > Asrock, Extreme6, 990FX, UEFI, AMD FX-9590
> > Gigabyte, GA-MA790FX-UD5P, 790FX, BIOS, AMD PhenomII x4 980
> >
> >
> > Hi Corbin,
> >
> > I noticed i didnt have x2apic enabled on my 990FX / FX-8350 system, so
> > i've rebuilt/rebooted etc, but;
> >
> > # zgrep X2APIC /proc/config.gz
> > CONFIG_X86_X2APIC=y
> > # dmesg | grep -i x2apic
> > #
> >
> > On my skylake box
> > # dmesg | grep -i x2apic
> > [0.044148] DMAR-IR: Queued invalidation will be enabled to support
> > x2apic and Intr-remapping.
> > [0.045802] DMAR-IR: Enabled IRQ remapping in x2apic mode
> > [0.045908] x2apic enabled
> > [0.046011] Switched APIC routing to cluster x2apic.
> >
> > What x2apic messages do you get on your 990FX / FX-9590 system?
> 
> 
> Interesting kernel parameter for you to try :
> ( from '/usr/src/linux/Documentation/kernel-parameters.txt' )
> 
> x2apic_phys [X86-64,APIC] Use x2apic physical mode instead of
> default x2apic cluster mode on platforms
> supporting x2apic.
> 
> With that switch I have not been getting any output in 'dmesg' about
> this at all.
> 
> 
> I tried adding x2apic_phys, but dmesg output did not change.
> 
> From wikip;
> "In 2012, AMD announced their /Advanced Virtual Interrupt Controller/
> (/AVIC/) targeting interrupt overhead reduction in virtualization
> environments.^[33]
> <https://en.wikipedia.org/wiki/X86_virtualization#cite_note-33> This
> technology has materialize in hardware and (as announced) does not
> support x2APIC <https://en.wikipedia.org/wiki/X2APIC>.^[34]
> <https://en.wikipedia.org/wiki/X86_virtualization#cite_note-34> In 2016,
> AVIC is available on the AMD family 15h models 6Xh (Carrizo) processors
> and newer.^[35]"
> <https://en.wikipedia.org/wiki/X86_virtualization#cite_note-35>
>  
> So;
> FX-8350 processors (bulldozer gen2) dont have AVIC
> Carrizo processors (bulldozer gen4), have AVIC, but AVIC doesnt support
> x2apic
> seems reasonable to conclude that there's no x2apic on bulldozer gen2,
> and that's why there's nothing in dmesg about it.
> 
> 
> Question :
> Do you have this enabled in your kernel ...
> >   [ ]   Support for Intel IOMMU using DMA Remapping Devices
> 
> 
> On the Skylake box, yes, FX box, no.

Thanks for the info. Will kill the kernel parameter on my box.

---

Tried an experiment, recompiled the kernel, no GART IOMMU support.
This was not enabled either.
 < > AMD IOMMU Version 2 driver

CPU FX-9590, 990FX Chipset

Now getting this instead :

> [0.988027] PCI: CLS 64 bytes, default 64
> [0.988362] iommu: Adding device :00:00.0 to group 0
> [0.988530] iommu: Adding device :00:02.0 to group 1
> [0.988689] iommu: Adding device :00:0a.0 to group 2
> [0.988872] iommu: Adding device :00:0d.0 to group 3
> [0.989029] iommu: Adding device :00:11.0 to group 4
> [0.989194] iommu: Adding device :00:12.0 to group 5
> [0.989318] iommu: Adding device :00:12.2 to group 5
> [0.989484] iommu: Adding device :00:13.0 to group 6
> [0.989615] iommu: Adding device :00:13.2 to group 6
> [0.989780] iommu: Adding device :00:14.0 to group 7
> [0.989943] iommu: Adding device :00:14.1 to group 8
> [0.990128] iommu: Adding device :00:14.3 to group 9
> [0.990292] iommu: Adding device :00:14.4 to group 10
> [0.990458] iommu: Adding device :00:14.5 to group 11
> [0.990637] iommu: Adding device :00:15.0 to group 12
> [0.990763] iommu: Adding device :00:15.1 to group 12
> [0.990935] iommu: Adding device :00:16.0 to group 13
> [0.991058] iommu: Adding device :00:16.2 to group 13
> [0.991252] iommu: Adding device :01:00.0 to group 14
> [0.991387] iommu: Adding device :01:00.1 to group 14
> [0.991560] iommu: Adding device :02:00.0 to group 15
> [0.991742] iommu: Adding device :03:00.0 to group 16
> [0.991863] iommu: Adding device :06:00.0 to group 12
> [0.991982] iommu: Adding device :07:04.0 to group 12
> [1.063849] AMD-Vi: Found IOMMU at :00:00.2 cap 0x40
> [1.063962] AMD-Vi: Interrupt remapping enabled
>

Re: [gentoo-user] Re: Issues with AMD_IOMMU

[Corbin Bird]

On 05/15/2017 09:59 PM, taii...@gmx.com wrote:
> On 05/15/2017 12:58 AM, Ian Zimmerman wrote:
> 
>>> The 990FX / 790FX Chipset doesn't have a GART / AGP Aperature or IOMMU
>>> in it.  The CPU contains the original K8 IOMMU ( v1 ) engineered /
>>> converted from a GART.
>>>
> The 8 and 9 series (not 7) does have an IOMMU, AMD-Vi v1.26.
> 
> I have two 890 series (but the server flavor - SR5690 chipset) boards
> with an IOMMU and it works great, I play games in a VM with an attached
> graphics card on my libre firmware KGPE-D16 and devices are DMA restricted.
> 
> Most consumer boards don't properly implement this feature, in fact I
> have never seen one that did which is why I bought my coreboot (libre
> init variant) D16.
> It wouldn't be that difficult to port coreboot to your board if you want
> this to work FYI.
> 

Thank you for that info.

Corrections based on fact are appreciated.

---

How does one 'port' coreboot?

Last time I went to the coreboot site, I didn't see anything really
helpful to me.

Doesn't the 'CPU voltage table firmware blob' require signing NDA's?


Corbin

Re: [gentoo-user] Re: Issues with AMD_IOMMU

[Corbin Bird]

On 05/16/2017 01:34 AM, Adam Carter wrote:
> Answer #1 :
> 
> 
> Asrock, Extreme6, 990FX, UEFI, AMD FX-9590
> Gigabyte, GA-MA790FX-UD5P, 790FX, BIOS, AMD PhenomII x4 980
> 
> 
> Hi Corbin,
> 
> I noticed i didnt have x2apic enabled on my 990FX / FX-8350 system, so
> i've rebuilt/rebooted etc, but;
> 
> # zgrep X2APIC /proc/config.gz
> CONFIG_X86_X2APIC=y
> # dmesg | grep -i x2apic
> #
> 
> On my skylake box
> # dmesg | grep -i x2apic
> [0.044148] DMAR-IR: Queued invalidation will be enabled to support
> x2apic and Intr-remapping.
> [0.045802] DMAR-IR: Enabled IRQ remapping in x2apic mode
> [0.045908] x2apic enabled
> [0.046011] Switched APIC routing to cluster x2apic.
> 
> What x2apic messages do you get on your 990FX / FX-9590 system?


Interesting kernel parameter for you to try :
( from '/usr/src/linux/Documentation/kernel-parameters.txt' )

x2apic_phys [X86-64,APIC] Use x2apic physical mode instead of
default x2apic cluster mode on platforms
supporting x2apic.

With that switch I have not been getting any output in 'dmesg' about
this at all.

Question :
Do you have this enabled in your kernel ...
>   [ ]   Support for Intel IOMMU using DMA Remapping Devices  


Corbin

Re: [gentoo-user] Re: Issues with AMD_IOMMU

[Corbin Bird]

On 05/15/2017 09:33 PM, Ian Zimmerman wrote:
> On 2017-05-15 14:33, Corbin Bird wrote:
> 
>> Gigabyte has long been known to ship 'broken for Linux' e820 firmware.
>> 'e820' is basically the APG Aperature setup in the firmware.
>> Gigabyte kills OR overrides the IOMMU support in the firmware, to setup
>> the AGP Aperature.
>>
>> Closed source / binary video drivers WANT an AGP Aperature.
> 
> So is _that_ what it's all about?  Is the default assumption that I run
> non-free video drivers?  Why?  I _never_ use these, and if you bet on me
> using them in the future and win the bet, you can probably make a cool
> million or two.
> 
>> The kernel wants an IOMMU on x86_64, as an IOMMU.
> 
> But it has one!  The GART_IOMMU.  It was even added specifically for
> Linux, according to kernel.org discussions I remember seeing but can't
> locate now.
> 
> I also found [1] , which I think is the clearest and most human-oriented
> explanation of this issue, yet.  And ... the recommendation is pretty
> much the opposite of yours.  The ball is in your court, sir.
> 
>>> CONFIG_X86_X2APIC=y
> 
> I did this long ago, and it has no effect - still only one is found,
> according to dmesg.  As I wrote in the earlier thread.
> 
> Also, the Kconfig help for this option says it does something quite
> different.  
> 
>>> CONFIG_X86_MPPARSE=y
> 
> Ok, this one I have not set so far.  Will read up on it and try,
> 
> [1]
> http://bogdan.org.ua/2009/09/30/iommu-this-costs-you-64-mb-of-ram.html
> 

That link, read the rest of it.

It says to leave it alone, let the kernel use it as an IOMMU.



I once compiled and tried to run a 64bit kernel with NO IOMMU support,
NO virt/vm support, used kernel parameters to kill all forms of IOMMU
... would not run at all ( hard lock / kernel panic ).

The error output made it very clear that an IOMMU was REQUIRED for
x86_64 ( 64bit ).



On AMD, with NO IOMMU kernel parameters, output in '/var/log/dmesg':
NOTE : IOMMU is enabled in the UEFI firmware.

> [0.00] AGP: Checking aperture...
> [0.00] AGP: No AGP bridge found
> [0.00] AGP: Node 0: aperture [bus addr 0xb400-0xb5ff] (32MB)
> [0.00] Aperture pointing to e820 RAM. Ignoring.
> [0.00] AGP: Your BIOS doesn't leave an aperture memory hole
> [0.00] AGP: Please enable the IOMMU option in the BIOS setup
> [0.00] AGP: This costs you 64MB of RAM
> [0.00] AGP: Mapping aperture over RAM [mem 0xb400-0xb7ff] 
> (65536KB)

> [0.926772] PCI: CLS 64 bytes, default 64
> [0.926983] PCI-DMA: Disabling AGP.
> [0.927215] PCI-DMA: aperture base @ b400 size 65536 KB
> [0.927336] PCI-DMA: using GART IOMMU.
> [0.927448] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture

Corbin

Re: [gentoo-user] Re: Issues with AMD_IOMMU

[Corbin Bird]

On 05/14/2017 11:58 PM, Ian Zimmerman wrote:
> On 2017-05-14 20:07, Corbin Bird wrote:
> 
>> Background / System Info : 2 systems.
>> Chipset 990FX, FX-9590 ( -march=bdver2 / Fam15h )
>> Chipset 790FX, PhenomII 980 ( -march=amdfam10 / Fam10h )
>> Gentoo x86_64, multilib, Kernel 4.9.x
>> IOMMU enabled in UEFI, BIOS.
> 
>> General Info : ( if you don't know already ... )
>>
>> The 990FX / 790FX Chipset doesn't have a GART / AGP Aperature or IOMMU
>> in it.  The CPU contains the original K8 IOMMU ( v1 ) engineered /
>> converted from a GART.
>>
>> Standard output in '/var/log/dmesg'.
>>
>>> [0.00] AGP: No AGP bridge found
>>> [0.926911] PCI-DMA: Disabling AGP.
>>> [0.927142] PCI-DMA: aperture base @ b400 size 65536 KB
>>> [0.927263] PCI-DMA: using GART IOMMU.
>>> [0.927376] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
> 
> I know we have been over this in an earlier thread "Another x11
> problem", but I am still very confused.
> 
> What BIOS do you have, on the computer that is BIOS based?  I assume you
> have one BIOS based and one EFI based, although you don't really say
> that.  I am asking because the setup screen of my BIOS (Award modular)
> doesn't mention any of these things at all.
> 
> Another source of my confusion is that my computer appears to work _now_
> without setting any additional kernel options.  The problem I had (X11
> turning the screen all black and never coming back) seems to have fixed
> itself with an upgrade of either kernel, X11, or radeon firmware, I
> don't remember which (and I probably never knew for sure which).
> 
> There are some 2 or 3 BIOS upgrades for my motherboard (GA-880GM-D2H)
> but they are all ancient anyway, from 2011 - the same year I built the
> computer, and the description Gigabyte gives sounds irrelevant to this
> stuff, so I never changed the BIOS.
> 
> I have looked at the kernel docs you recommend, but they leave a lot to
> be desired in the clarity department.  For example, the general
> kernel-parameters doc lists a iommu=pt option, without explanation but
> tagged with [X86][IA-64].  But the x86_64/boot-options doc doesn't
> mention this value at all.
> 
> I guess my high-level confusion is that I don't understand the
> relationships between all these bits of hardware, and I also don't
> understand why the automatic setup that Linux does wouldn't result in a
> normally working system.  So there's no aperture, so steal 64M of
> addresses from RAM.  Big deal, no?  What's the problem?
> 
> Finally, in your last article in that earlier thread you said that I
> should turn on multiple APICs in the kernel.  But I can find no kernel
> option for that.  What's the exact CONFIG_* symbol to tweak?
> 
> Thanks.
> 



Answer #1 :

Asrock, Extreme6, 990FX, UEFI, AMD FX-9590
Gigabyte, GA-MA790FX-UD5P, 790FX, BIOS, AMD PhenomII x4 980

Update the BIOS on that motherboard. Gigabyte doesn't state everything
done by their BIOS updates. The IOMMU enable option was added to the
BIOS at a later date on the GA-MA790FX-UD5P.

Gigabyte has long been known to ship 'broken for Linux' e820 firmware.
'e820' is basically the APG Aperature setup in the firmware.
Gigabyte kills OR overrides the IOMMU support in the firmware, to setup
the AGP Aperature.

Closed source / binary video drivers WANT an AGP Aperature.
The kernel wants an IOMMU on x86_64, as an IOMMU.
Squabbling over memory, and I/O, used for what, by whom, yes?

That is why I mentioned 'the monkey wrench'.



Answer #2 :

Here is what to look for, ( x2 APIC answer )

> 
> kernel 4.9.x, make menuconfig ... ( look just under "Symmetric 
> multi-processing support" )
> 
>  Processor type and features  ---> 
>   │ │  [*] Symmetric 
> multi-processing support  
>  │ │  
>   │ │  [*] Support x2apic 
>   
> │ │  
>   │ │  [*] Enable MPS 
> table 
> │ │  
>   │ │  [ ] Support for 
> extended (non-PC) x86 platforms   
>│ │  
>   │ │  [ ] Intel Low 
> Power Subsystem Support   
>

Re: [gentoo-user] Issues with AMD_IOMMU

[Corbin Bird]

On 05/14/2017 12:31 AM, Adam Carter wrote:
> Tried kernels 4.10.13 and 4.11, with
> CONFIG_GART_IOMMU=y
> CONFIG_IOMMU_HELPER=y
> CONFIG_IOMMU_API=y
> CONFIG_IOMMU_SUPPORT=y
> CONFIG_IOMMU_IOVA=y
> CONFIG_AMD_IOMMU=y
> CONFIG_AMD_IOMMU_V2=m
> Chipset is 990FX, and AFAICT the V2 is for the APU (bdver3 and 4 vintage).
> 
> When I enable the IOMMU in the BIOS I get stack traces. Is anyone using
> AMD_IOMMU successfully? If so, any tips?

-

Background / System Info : 2 systems.
Chipset 990FX, FX-9590 ( -march=bdver2 / Fam15h )
Chipset 790FX, PhenomII 980 ( -march=amdfam10 / Fam10h )
Gentoo x86_64, multilib, Kernel 4.9.x
IOMMU enabled in UEFI, BIOS.

-


General Info : ( if you don't know already ... )

The 990FX / 790FX Chipset doesn't have a GART / AGP Aperature or IOMMU
in it.
The CPU contains the original K8 IOMMU ( v1 ) engineered / converted
from a GART.

Standard output in '/var/log/dmesg'.

> [0.00] AGP: No AGP bridge found

> [0.926911] PCI-DMA: Disabling AGP.
> [0.927142] PCI-DMA: aperture base @ b400 size 65536 KB
> [0.927263] PCI-DMA: using GART IOMMU.
> [0.927376] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture

-

Suggestion :

read the Kernel Parameter docs. The automatic setup may need tweaking.

You have to do a manual setup if you want, both, a working IOMMU and an
AGP Aperature. Firmware can throw a major monkey wrench into that type
of setup however.

> /usr/src/linux/Documentation/kernel-parameters.txt

This doc has the x86_64 IOMMU options listed ...
> /usr/src/linux/Documentation/x86/x86_64/boot-options.txt


Question :

APU?
I was under the impression that those CPU's used a different chipset,
not the 990FX.


Corbin

Re: [gentoo-user] gcc with graphite flag?

[Corbin Bird]

On 04/28/2017 02:08 AM, Walter Dnes wrote:
>   In the past, there used to be dire warnings about the difficulty of
> installing gcc with graphite.  Have things become easier with 5.4.0?
> Here's a "dry run" output...
> 
> 
> [i660][waltdnes][~] USE="graphite" emerge -pv gcc
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> [ebuild  N ] dev-libs/isl-0.15:0/15::gentoo  USE="-static-libs" 1,375 KiB
> [ebuild   R] sys-devel/gcc-5.4.0-r3:5.4.0::gentoo  USE="cxx fortran 
> graphite* nptl sanitize vtv (-altivec) (-awt) -cilk -debug -doc 
> (-fixed-point) -gcj -go (-hardened) (-jit) (-libssp) -mpx (-multilib) -nls 
> -nopie -nossp -objc -objc++ -objc-gc -openmp -regression-test -vanilla" 0 KiB
> 
> Total: 2 packages (1 new, 1 reinstall), Size of downloads: 1,375 KiB
> 
> 


On my Gentoo box ...

[ebuild   R] sys-devel/gcc-5.4.0-r3:5.4.0::gentoo  USE="cxx fortran
gcj graphite (multilib) nls nptl objc objc++ objc-gc openmp sanitize vtv
(-altivec) (-awt) -cilk -debug -doc (-fixed-point) -go (-hardened)
(-jit) (-libssp) -mpx -nopie -nossp -regression-test -vanilla" 0 KiB


"cloog" has been removed, going from GCC 4.9.4 -> GCC 5.4.0

No problems with "graphite" in either version of GCC, on my Gentoo box.

Corbin

Re: [gentoo-user] Re: Argh, palemoon again ** 3 [Was: GCC 5.4.0]

[Corbin Bird]

On 04/26/2017 11:03 PM, Walter Dnes wrote:
> On Wed, Apr 26, 2017 at 06:01:20AM +0800, Bill Kenworthy wrote
> 
>> That flag isn't mentioned here.
> 
>   I checked the source code.  It forces the old ABI, so it should work,
> compiled with GCC 5.4.0, even on a Gcc 4.9.4 system...
> 
> [CentOS65][pmbuilder][~/pmmaster] grep -r GLIBCXX_USE_CXX11_ABI pmsrc
> pmsrc/configure:   CXXFLAGS="$CXXFLAGS -D_GLIBCXX_USE_CXX11_ABI=0"
> pmsrc/configure:   HOST_CXXFLAGS="$HOST_CXXFLAGS -D_GLIBCXX_USE_CXX11_ABI=0"
> pmsrc/configure.in:   CXXFLAGS="$CXXFLAGS -D_GLIBCXX_USE_CXX11_ABI=0"
> pmsrc/configure.in:   HOST_CXXFLAGS="$HOST_CXXFLAGS 
> -D_GLIBCXX_USE_CXX11_ABI=0"
> 

Walter,

That flag "-D_GLIBCXX_USE_CXX11_ABI=0" is a CPPFLAG. It is only
recognized by GCC 5.1.x and higher. And it only works on GCC built with
dual ABI support. Gentoo doesn't support the dual ABI builds.

Info links :
https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_macros.html
https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html#abi.versioning.__GLIBCXX__
https://gcc.gnu.org/onlinedocs/libstdc++/manual/configure.html

On my system, I went ahead with the switch to GCC 5.4.0.

The "-D_GLIBCXX_USE_CXX11_ABI=1" CPPFLAG forces GCC to check IF the new
ABI should be applied FIRST. NO FORCING the ABI on software that doesn't
use it.

Putting CPPFLAGS="-D_GLIBCXX_USE_CXX11_ABI=1" in make.conf killed almost
all the erorrs in the revdep-rebuild process.

Putting that in as a CFLAGS or CXXFLAGS switch caused lots of errors in
revdep-rebuild.

Thought you might want to know.

Corbin

Re: [gentoo-user] Something is blocking an addition of fonts

[Corbin Bird]

On 03/10/2017 07:24 PM, Harry Putnam wrote:
> Setup: VBox vm running gentoo(amd64) guest on a win-10 (64bit) host
>  Hardware: HP xw8600 - 2x Xeon  CPU X5450 @ 3.00GHz - 32 GB ram
> 
> I've added some fonts from outside portage this way:
> 
>  (Sorry that what follows is a bit of a confusing mess)
> 
> mkdir /usr/share/fonts/terminus
> loaded the fonts into termininus
> 
> Ran:
>mkfontdir /usr/share/fonts/terminus
> Ran:
>  xset fp rehash
> 
> Which is supposed to tell the X fonts tools about the new
> set of fonts with out having to restart X.
> 
> I thought a bit and wondered if I might should have added the new
> directory to the font path.. I don't really think so since the default
> path covers the new one but stillso:
> 
> Ran:
>   xset +fp  /usr/share/fonts/terminus
> 
> That is supposed to prepend that path to the existing path.
> 
> Checked with:
> 
>   xset q
> 
> And I see the new directory
> 
>   Font Path:
> /usr/share/fonts/terminus_hp3-170310/,/usr/share/fonts/misc/,built-ins
> 
> 
> The new fonts show up with `fc-list'
> 
> OK, all seems to be working... 
> 
> Until I actually try to use them.
> 
> xterm -fa ter-u14b_iso-8859-1.pcf
> (output wrapped for mail)
> 
> Warning: Cannot convert string
> "-adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-*" to type
> FontStruct
> 
> Warning: Missing charsets in String to FontSet conversion
> 
> It appears the xterm is trying to load a font from somewhere else even
> though I asked for  `ter-u14b_iso-8859-1.pcf'
> 
> I'm not at all sure where the -adobe-helvetica if being called.
> 
>   sudo grep -r 'adobe-helvetica'  /usr/share/fonts
>
> 
> However there are piles of fonts with `adobe' in the name:
> 
>   sudo grep -r adobe /usr/share/fonts|wc-l
> 173
> 
> They appear to be mostly like this:
> 
>/usr/share/fonts/corefonts/fonts.scale:verdanaz.ttf
>-microsoft-verdana-bold-i-normal--0-0-0-0-p-0-adobe-standard
> 
> Thought it might be from .Xresoures but there are no fonts there with
> adobe in the name
> 
>`grep adobe .Xresources' 
> 
> Anybody here recognize what the problem might be?
> 
> There are a few helvetica in the .. only one is english:
> 
>/usr/share/fonts/misc/fonts.alias:variable \
>  -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-1
> 
> And two japanese helveticas
> 
> So I can't even tell where that adobe font is coming from
>   
> 
> 

The "terminus" font is in the Gentoo repo.

Try emerging "media-fonts/terminus-font" && activating with "eselect
fontconfig".

USE flags for the font you might be interested in :

center-tilde
-->Place the '~' character vertically centered on the line instead of to
the top.

pcf
-->Install Portable Compiled Font (PCF) (required for X11)

pcf-unicode-only
-->Remove non-unicode PCF fonts that could be problematic. See bug #520222.

psf
-->Install PC Screen Font (PSF) with unicode data (for linux console)

Corbin

[gentoo-user] ISP extortion [ Partially Resolved ]

[Corbin Bird]

Thanks for all the responses.
--

AirVPN seems to solve a most if not all of the filtering / blocking
issues. ( Don't try their pre-built client / PATHs are wrong. )
--

"emerge-webrsync" was setup with GPG signature checking.

What the ISP is doing looks to be ?attaching? / ?embeding? a "process",
that attempts to execute on my machine. What it did was corrupt
ebuilds/metadata/hashes while syncing the local tree.

This command would crash, no error, no output, every single time :
"emerge -pv --update --newuse --tree --deep --with-bdeps=y @world"

They obviously didn't achieve what they wanted. From then on, the HTTP
request made by "emerge-webrsync" was blocked one way. My Gentoo box was
able to talk AT Gentoo's webrsync servers. Didn't receive anything back
from the servers. ( all packets dropped? )

--

Converted to "rsync" for using "emerge --sync" instead.

"emerge --sync" complained about having to "clean up the mess" after the
VPN was running. The "clean up" seems to have succeeded.

--

Will act on the ( lawyer, deposit ) suggestions. And a new e-mail provider.

This may sound screwy ... with the VPN, the web browser and web sites
are working/responding so much better.

Corbin

Re: [gentoo-user] ISP extorsion - how to negate / get around?

[Corbin Bird]

On 03/10/2017 07:28 PM, Rich Freeman wrote:
> On Fri, Mar 10, 2017 at 2:50 PM, Corbin Bird <corbinb...@charter.net> wrote:
>>
>> My ISP ( Charter ) merged with Time-Warner. New name "Spectrum"
>>
>> 1 # : Now I have intermittent connectivity.
> 
> Nothing you can do about that if it really is connectivity.
> 
>>
>> 2 # : And with the death of FCC privacy rules, the new ISP is forcing me
>> to update their records ( for sale-of purposes ). This includes phone (
>> all ), SSN, bank account numbers, and credit card numbers.
>>
>> 3 # : the ISP attempting to force agreement to "no communications
>> allowed with the FCC". Also is attempting to force agreement to
>> "Arbitration with the ISP as the Arbiter" for all complaints.
>>
>> 4 # : billing is only online now. Not allowed to see a Account
>> Statement, or receive any "receipt for payment" until I comply with ISP
>> demands.
> 
> While I certainly agree with your frustrations on these, I suspect
> your options are pretty limited if they really are a monopoly.  You
> may just have to live with these if you don't want to do something
> exotic for internet access.
> 
>> 5 # : external e-mail clients ( Thunderbird, Claws-Mail, etc. ) are now
>> starting to have problems. ISP solution -> must use their web based
>> e-mail app only ( only works with Windoze, surprise! ).
>>
>> 6 # : ISP is starting to filter customers web access. The ISP is
>> deciding what sites customers are allowed to see. ( look up the practice
>> called "ransom" ).
> 
> I would see if a VPN works for you.  It would solve these problems at
> least.  Of course, they could do something to block the VPN, but I
> believe some services can work over SSL/etc unless your ISP is
> carefully blacklisting them.
> 
>>
>> NOTE : The ?hijack technique? will corrupt the portage trees if you use
>> "emerge-webrsync".
>>
> 
> Can you define "corrupt" here?  Looking at the source emerge-webrsync
> should at the least do a digest check if available (and if it isn't
> available I'd be interested in that), and if you set the webrsync-gpg
> FEATURE flag in make.conf it should also check the gpg signature.
> Unless your ISP is doing a Gentoo-specific MITM the first should
> detect problems, and unless our gpg checking is completely broken the
> latter should detect anything the ISP tries to do to the file.  They
> could of course prevent you from syncing, but tampering shouldn't be
> an issue.
> 

Now using a VPN.

The "emerge-webrsync" setup that I had been using did have the "gpg"
check functioning.

It is looking like they are attempting to attach or embed a "process" of
some sort, that executes on the local machine.

The first attempt at ?blocking? "emerge-webrsync" did something to the
tarball contents ( ebuilds or metadata damaged ).

Running this command started crashing without error :
"emerge -pv --update --newuse --tree --deep --with-bdeps=y @world"

The second attempt at ?blocking? was to completely block the HTTP
requests generated by "emerge-webrsync".

Going to a VPN, and "emerge --sync" seems to have gotten around them so far.

NOTE : the first "emerge --sync" made lots of complaints indicating the
portage trees had been damaged.

Corbin

[gentoo-user] ISP extorsion - how to negate / get around?

[Corbin Bird]

Have a serious problem, might cost me any Internet access.

My ISP ( Charter ) merged with Time-Warner. New name "Spectrum"

1 # : Now I have intermittent connectivity.

2 # : And with the death of FCC privacy rules, the new ISP is forcing me
to update their records ( for sale-of purposes ). This includes phone (
all ), SSN, bank account numbers, and credit card numbers.

3 # : the ISP attempting to force agreement to "no communications
allowed with the FCC". Also is attempting to force agreement to
"Arbitration with the ISP as the Arbiter" for all complaints.

4 # : billing is only online now. Not allowed to see a Account
Statement, or receive any "receipt for payment" until I comply with ISP
demands.

5 # : external e-mail clients ( Thunderbird, Claws-Mail, etc. ) are now
starting to have problems. ISP solution -> must use their web based
e-mail app only ( only works with Windoze, surprise! ).

6 # : ISP is starting to filter customers web access. The ISP is
deciding what sites customers are allowed to see. ( look up the practice
called "ransom" ).

7 # : no other broadband ISP in the regional area. No alternatives.

They are using a hijack technique that I don't know the name of,
attempting to force compliance.

NOTE : The ?hijack technique? will corrupt the portage trees if you use
"emerge-webrsync".

Is there any way to ... fix? work-around? ... this idiocy?



Background info :

The old cable modem suddenly stopped working. The ISP sent out a clone
of a Cisco DPC2316 ( Technicolor ), complete with hacked / trashed /
closed firmware. So I returned the rented cable modem ( bought my own ).
The Technicolor clone was using a built-in Java based "???" to
redirect / filter at the modem.

Switched to Google Public DNS. Doesn't effect the ?hijack technique?.

The "uMatrix/uBlock Origin" plugins ( Firefox/ Palemoon ) stop the
?hijack technique? in the web browser. Always shows up as an ipv4
address, embedded in a "frame", that resolves to "*-charter-*".

Re: [gentoo-user] Helvetica fonts

[Corbin Bird]

On 03/06/2017 01:27 PM, the...@sys-concept.com wrote:
> Which package contain "Helvetica" font?
> 
> I'm using "flpsed" and apparently it is using Helvetica font, which
> "eselect fontconfig list" is not showing anything that resemble "helvet"
> "eix helvet" is not showing anything either.
> 
> The fonts in "flpsed" display are very rugged/pixelated, it is hard to
> look at them.
> 

This font package works for Helvetica deps in Mozilla / Firefox && CUPS.

"media-fonts/liberation-fonts"


Reference Link :
https://packages.gentoo.org/packages/media-fonts/liberation-fonts


Corbin

Re: [gentoo-user] Re: fonts mostly inaccessable to xterm

[Corbin Bird]

On 03/05/2017 06:52 PM, Harry Putnam wrote:
> Corbin Bird <corbinb...@charter.net> writes:
> 
>>
>> Have you tried : xterm -fa "9x15B-ISO8859-1"?
> 
> I mentioned that the -fa switch was not working at all.
> 
> I've since discovered that the xterms I had were compiled with useflag
> truetype disabled .. so `-truetype' Which meant xterm was compiled
> without support for -fa
> 
>> Note : that works on XTerm v325 ( tested ).
> 
> I've recompiled xterm with useflag truetype enabled and now I have the
> -fa flag so I can run the command you mentioned above now.
> 
> That is a nice looking font... a little big on my view but
> 
> I see something a bit off here... trying to get a smaller font of the
> same type I went clear down to 4x6... but those all look just like
> the "9x15B-ISO8859-1"
> 
>   xterm -fa 4x6-ISO8859-1
> 
> Does not say anything by way of error or explanation just shows a
> terminal with the same font displayed as "9x15B-ISO8859-1"
> 
> That can't be a desirable outcome.
> 
> It must just be displaying the same size from 9x 8x 7x 6x 5x 4x. and
> doing so silently.
> 
> I'm not running a font server.
> 
>> The Xorg Xft font server docs specifically show how to set the "default"
>> font in Xterm. Look for the section 'Configuring applications'
>>
>> Reference Link :
>>
>>> https://www.x.org/releases/X11R7.7/doc/xorg-docs/fonts/fonts.html
> 
> Thanks for the link... much as I been googling I'm surprised I did not
> see that one already... it looks quite thorough.
> 
> 


The Xft server is really 'fontconfig'. No daemon running at all.

---

Compile with both USE flags "truetype unicode" and the local USE flag
"toolbar".

That will give you control of the font size.
( xterm -> VT Fonts, uxterm -> Unicode Fonts )

---

Reference Links :
( Use flags )
https://packages.gentoo.org/packages/x11-terms/xterm

( XTerm FAQ )
http://invisible-island.net/xterm/xterm.faq.html

( Frequent problems )
http://invisible-island.net/xterm/xterm.faq.html#frequent_problems

( Scaled Fonts )
http://invisible-island.net/xterm/xterm.faq.html#scaled_font

Corbin

Re: [gentoo-user] Re: fonts mostly inaccessable to xterm

[Corbin Bird]

On 03/05/2017 01:58 PM, Harry Putnam wrote:
> Corbin Bird <corbinb...@charter.net> writes:
> 
> [...]
> 
>> Please clarify ... ... if this is a console only boot ( in vm ), 
>> ... if this is a GUI Desktop ( in vm ), and/or specific xterm ( i.e
>> "x11-terms/xterm" ).
> 
> This is a full X host running lxde for desktop The xterm I speak of
> is the real McCoy .. the one Thomas Dickey has maintained since mid
> to late 90s.
> 
> In this case: x11-terms/xterm version 327 But I just noticed when 
> pretend emerge just now to see what the use flags were... I see it 
> defaults to -truetype use flag... which may be significant.
> 
> I'm re-emerging with USE=truetype might make some difference.
> 
> But still would not explain the fonts that are not true type failing 
> to load.
> 
> Do you know if some EXTRA_ECONF or something is needed to make xterm 
> recognize its -fa switch?
> 
> I've seen in several places that -fa font-name is used instead of
> -fn font-name
> 
> Here xterm calls it a bad switch or something like and fails to load 
> the font.
> 
> xterm -fa "9x15B-ISO8859-1.pcf" xterm: bad command line option "-fa"
> 
> xterm -fn "9x15B-ISO8859-1.pcf" xterm: cannot load font
> '9x15B-ISO8859-1.pcf'
> 
> And without the quotes:
> 
> xterm -fn 9x15B-ISO8859-1.pcf xterm: cannot load font
> '9x15B-ISO8859-1.pcf'
> 
> 
> 

Have you tried : xterm -fa "9x15B-ISO8859-1"?

Note : that works on XTerm v325 ( tested ).

The Xorg Xft font server docs specifically show how to set the "default"
font in Xterm. Look for the section 'Configuring applications'

Reference Link :

> https://www.x.org/releases/X11R7.7/doc/xorg-docs/fonts/fonts.html

Font Directory :
/usr/share/fonts/misc/


Corbin

Re: [gentoo-user] fonts mostly inaccessable to xterm

[Corbin Bird]

On 03/05/2017 06:41 AM, Harry Putnam wrote:
> Setup: VBox vm running gentoo(amd64) guest on a win-10 (64bit) host
>  Hardware: HP xw8600 - 2x Xeon  CPU X5450 @ 3.00GHz - 32 GB ram
> 
> I've been trying to get fonts to load into xterm most of the day.
> 
> I'm not getting anywhere.
> 
> for example:
> /usr/share/fonts shows all these:
> 
> 100dpi  corefonts  encodingsinconsolata-hellenic  misc   util
> 75dpi   cyrillic   inconsolata  liberation-fonts  urw-fonts
> 
> Probably going at this ass backwards but it seems just about none of
> thes are accessabel to an xterm
> 
> xlsfonts shows many `misc fixed' fonts that can be loaded into xterm.
> 
> But I have not found how to load any of the others.
> 
> For example: fc-list shows a whole different list of fonts.
> I tried several and none of those were loadable into xterm.
> 
> Trying by there names inside the directories above I have found none
> are recognized by xterm
> 
> Looking at the fonts.dir files .. at least most of those names look
> familiar in the format I'm used to such as this:
> 
>-misc-fixed-bold-r-normal--15-120-100-100-c-90-iso8859-1
> That one is found with xlsfonts.
> 
> Something like this from inconsolata fonts.dir file:
> 
>-misc-inconsolata-medium-r-normal--0-0-0-0-m-0-iso8859-1
> 
>   xterm -fn -misc-inconsolata-medium-r-normal--0-0-0-0-m-0-iso8859-1
> xterm: cannot load font 
> '-misc-inconsolata-medium-r-normal--0-0-0-0-m-0-iso8859-1'
> xterm: cannot load font 
> '-misc-inconsolata-medium-r-normal--0-0-0-0-m-0-iso8859-1'
> 
> trying the other kind of names there:
> 
>xterm -fn Inconsolata-Regular.ttf
>  xterm: cannot load font 'Inconsolata-Regular.ttf'
>  xterm: cannot load font 'Inconsolata-Regular.ttf'
> 
> Leave it at that for the moment...
> 
> googling for hours on this I find xterm can understand a different
> switch  `xterm -fa bla-bla'
> 
> However, xterm as installed from portage does not understand that
> switch at all.
> 
> Some of the googling mentioned that xterm has to have that ability
> compiled in, so I wondered if our xterm is compiled for that option?
> 
> And further if anyone knows what that compile option might be?
> 
> Can anyone offer some guidance here...
> 
> How to get a few of those fonts to be loadable into an xterm?
> 
> 

Please clarify ...
... if this is a console only boot ( in vm ),
... if this is a GUI Desktop ( in vm ),
and/or specific xterm ( i.e "x11-terms/xterm" ).

Corbin

Re: [gentoo-user] webkit-gtk-2.14.2 cant find sqlite3 symbols

[Corbin Bird]

On 02/27/2017 03:44 PM, kelly hirai wrote:
> corbin,
>
> i've finally discovered the problem with this.
>
> it turns out that there were a set of stale .so files in
> /usr/iocal/bin/ installed in the year 2015. i discovered this by running:
>
> ebuild /usr/portage/net-libs/webkit-gtk/webkit-gtk-2.14.5.ebuild
> configure
>
> the resulting ninja files showed that's where it was sourcing
> libsqlite3.so. moving it out of the way solved the issue. its a
> complete mystery why it would look for libs in a bin directory or why
> portage would prefer /usr/local over the standard paths.
>
> anyway, thanks for your thoughts and sorry for the long turnaround.
>
> kelly
>
>
>
> On 02/07/2017 06:23 PM, Corbin Bird wrote:
>> On 02/07/2017 09:55 AM, kelly hirai wrote:
>>>
>>> On 02/06/2017 06:31 PM, Corbin Bird wrote:
>>>> On 02/06/2017 01:09 PM, kelly hirai wrote:
>>>>> hello fellow gentoo-users,
>>>>>
>>>>> for about a month now, i have not been able to make
>>>>> webkit-gtk-2.14.[2,3] compile. it terminates at the linking step
>>>>> complaining it cant find some sqlite functions.
>>>>>
>>>>> ./configure phase reports sqlite3 availability
>>>>>
>>>>> -- Checking for module 'sqlite3'
>>>>> --   Found sqlite3, version 3.13.0
>>>>> -- Found Sqlite: /usr/include
>>>>>
>>>>> but when it comes time to do the linking it cant find it:
>>>>>
>>>>> FAILED: : && /usr/bin/x86_64-pc-linux-gnu-g++  -fPIC -march=native
>>>>> -O2
>>>>> -pipe -fno-strict-aliasing -std=c++1y -Wl,--no-undefined -Wl,-O1
>>>>> -Wl,--as-needed -Wl,--no-keep-memory -fuse-ld=gold
>>>>> -Wl,--disable-new-dtags -fuse-ld=gold -Wl,--disable-new-dtags
>>>>> -Wl,--version-script,/var/tmp/portage/net-libs/webkit-gtk-2.14.2/work/webkitgtk-2.14.2/Source/cmake/gtksymbols.filter
>>>>>
>>>>>
>>>>> -shared -Wl,-soname,libwebkit2gtk-4.0.so.37 -o
>>>>> lib/libwebkit2gtk-4.0.so.37.14.9 @CMakeFiles/WebKit2.rsp && :
>>>>> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
>>>>>
>>>>>
>>>>> void
>>>>> std::__once_call_impl<std::_Bind_simple<WebCore::initializeSQLiteIfNecessary()::{lambda()#1}
>>>>>
>>>>>
>>>>> ()> >(): error: undefined reference to 'sqlite3_initialize'
>>>>> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
>>>>>
>>>>>
>>>>> void
>>>>> std::__once_call_impl<std::_Bind_simple<WebCore::initializeSQLiteIfNecessary()::{lambda()#1}
>>>>>
>>>>>
>>>>> ()> >(): error: undefined reference to 'sqlite3_errstr'
>>>>> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
>>>>>
>>>>>
>>>>> WebCore::SQLiteDatabase::setCollationFunction(WTF::String const&,
>>>>> std::function): error:
>>>>> undefined reference to 'sqlite3_create_collation_v2'
>>>>> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
>>>>>
>>>>>
>>>>> WebCore::SQLiteDatabase::removeCollationFunction(WTF::String const&):
>>>>> error: undefined reference to 'sqlite3_create_collation_v2'
>>>>> collect2: error: ld returned 1 exit status
>>>>>
>>>>> the symbols seem to be in the library:
>>>>>
>>>>> strings /usr/lib32/libsqlite3.so | grep  create_collation_
>>>>> sqlite3_create_collation_v2
>>>>>
>>>>> strings /usr/lib64/libsqlite3.so | grep  create_collation_
>>>>> sqlite3_create_collation_v2
>>>>>
>>>>> i'm stumped here. i don't see any explicit linking flags. the
>>>>> @CMakefiles/WebKit2.rsp doesn't make sense to me, maybe its in there?
>>>>>
>>>>> k.
>>>> Please post the USE flags set for all the following : 
>>>> "dev-db/sqlite:3"
>>>> and "net-libs/webkit-gtk:2", "net-libs/webkit-gtk:3",
>>>> "net-libs/webkit-gtk:4

Re: [gentoo-user] media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r5 won't compile

[Corbin Bird]

On 02/18/2017 12:41 PM, Mick wrote:
> I'm stuck on this problem today.  I ran @preserved-rebuild and this pops up:
>
> # required by @preserved-rebuild (argument)
> # /usr/portage/profiles/package.mask:
> # Mart Raudsepp  (16 Feb 2017)
> # Old gstreamer 0.10 version, which is security vulnerable.
> # Use gstreamer:1.0 with media-plugins/gst-plugins-libav
> # instead (despite the name, it uses media-video/ffmpeg too).
> # Masked for removal in 30 days. Bug #594878
> =media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r5
>
> It then asks me to add gst-plugins-ffmpeg to package.unmask, which I allow it 
> to do.  Continuing with @preserved-rebuild then it fails like so:
> 
> /data/tmp_var/portage/media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-
> r5/work/gst-ffmpeg-0.10.13_p201211/ext/ffmpeg/gstffmpegcodecmap.c:2590:32: 
> error: 'PIX_FMT_YUVA420P' undeclared (first use in this function)
>  context->pix_fmt = PIX_FMT_YUVA420P;
> ^
> /data/tmp_var/portage/media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-
> r5/work/gst-ffmpeg-0.10.13_p201211/ext/ffmpeg/gstffmpegcodecmap.c:2593:32: 
> error: 'PIX_FMT_YUV411P' undeclared (first use in this function)
>  context->pix_fmt = PIX_FMT_YUV411P;
> ^
> /data/tmp_var/portage/media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-
> r5/work/gst-ffmpeg-0.10.13_p201211/ext/ffmpeg/gstffmpegcodecmap.c:2596:32: 
> error: 'PIX_FMT_YUV422P' undeclared (first use in this function)
>  context->pix_fmt = PIX_FMT_YUV422P;
> ^
> /data/tmp_var/portage/media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-
> r5/work/gst-ffmpeg-0.10.13_p201211/ext/ffmpeg/gstffmpegcodecmap.c:2599:32: 
> error: 'PIX_FMT_YUV410P' undeclared (first use in this function)
>  context->pix_fmt = PIX_FMT_YUV410P;
> ^
> make[3]: *** [Makefile:544: libgstffmpeg_la-gstffmpegcodecmap.lo] Error 1
> make[3]: Leaving directory '/data/tmp_var/portage/media-plugins/gst-plugins-
> ffmpeg-0.10.13_p201211-r5/work/gst-ffmpeg-0.10.13_p201211-
> abi_x86_64.amd64/ext/ffmpeg'
> make[2]: *** [Makefile:389: all-recursive] Error 1
> make[2]: Leaving directory '/data/tmp_var/portage/media-plugins/gst-plugins-
> ffmpeg-0.10.13_p201211-r5/work/gst-ffmpeg-0.10.13_p201211-
> abi_x86_64.amd64/ext'
> make[1]: *** [Makefile:482: all-recursive] Error 1
> make[1]: Leaving directory '/data/tmp_var/portage/media-plugins/gst-plugins-
> ffmpeg-0.10.13_p201211-r5/work/gst-ffmpeg-0.10.13_p201211-abi_x86_64.amd64'
> make: *** [Makefile:410: all] Error 2
>  * ERROR: media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r5::gentoo failed 
> (compile phase):
>  *   emake failed
>  *
>  * If you need support, post the output of `emerge --info '=media-plugins/gst-
> plugins-ffmpeg-0.10.13_p201211-r5::gentoo'`,
>  * the complete build log and the output of `emerge -pqv '=media-plugins/gst-
> plugins-ffmpeg-0.10.13_p201211-r5::gentoo'`.
>  * The complete build log is located at '/var/log/portage/media-plugins:gst-
> plugins-ffmpeg-0.10.13_p201211-r5:20170218-094809.log'.
>  * The ebuild environment file is located at '/data/tmp_var/portage/media-
> plugins/gst-plugins-ffmpeg-0.10.13_p201211-r5/temp/environment'.
>  * Working directory: '/data/tmp_var/portage/media-plugins/gst-plugins-
> ffmpeg-0.10.13_p201211-r5/work/gst-ffmpeg-0.10.13_p201211-abi_x86_64.amd64'
>  * S: '/data/tmp_var/portage/media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-
> r5/work/gst-ffmpeg-0.10.13_p201211'
> 
>
> So, what now?  Am I supposed to remove/rebuild anything manually?  The 
> gst-plugins-ffmpeg package does not seem to have any reverse dependencies:
> ===
>  # emerge --depclean -p -v media-plugins/gst-plugins-ffmpeg
> Calculating dependencies... done!
 Calculating removal order...
 These are the packages that would be unmerged:
>  
>  media-plugins/gst-plugins-ffmpeg
> selected: 0.10.13_p201211-r5 
>protected: none
>  omitted: none
>
> All selected packages: =media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r5
>
 'Selected' packages are slated for removal.
 'Protected' and 'omitted' packages will not be removed.
> =
>

>gst-plugins-ffmpeg  v1.8.3 / 1.10.3 doesn't work with ffmpeg at
all, period.

Did you try this?
> # Old gstreamer 0.10 version, which is security vulnerable.
> # Use gstreamer:1.0 with media-plugins/gst-plugins-libav
> # instead (despite the name, it uses media-video/ffmpeg too).

You might have to adjust the use flags on "media-video/ffmpeg".

 media-video/ffmpeg  USE = +static-libs +postproc

:)

Re: [gentoo-user] mesa-12.0.1 fails to emerge

[Corbin Bird]

On 02/08/2017 12:47 AM, Mick wrote:
> On Tuesday 07 Feb 2017 18:24:06 Corbin Bird wrote:
>> On 02/07/2017 05:02 PM, Mick wrote:
>>> How could I go beyond this point?
>>>
>>> =
>>> /var/tmp/portage/media-
>>> libs/mesa-12.0.1/work/mesa-12.0.1/src/gallium/state_track
>>> ers/clover/llvm/invocation.cpp:212:75: error: no matching function for
>>> call to ‘
>>> clang::CompilerInvocation::setLangDefaults(clang::LangOptions&,
>>> clang::InputKind
>>> , llvm::Triple, clang::LangStandard::Kind)’
>>> =
>>>
>>> Extract from compile log attached.
>>>
>>> I am running sys-devel/clang-runtime-3.9.1 like so:
>>>  Installed versions:  3.9.1(21:25:30 07/02/17)(openmp -libcxx
>>>  ABI_MIPS="-
>>>
>>> n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32")
>> ---
>> If you would please, post if the USE flag "opencl" is set in
>> "make.conf", or in "package.use" for any packages.
>>
>>
>> Corbin
> Yes!  It had sneaked in make.conf.  I removed it and am re-emerging now.
>
> Thanks.  :-)
---
Your Welcome.

Easy way to find the def of that USE flag ( it gave away the error ) :

~ # equery u media-libs/mesa
 + + opencl   : Enable the Clover Gallium OpenCL state tracker.

Easy way to check what else currently installed that may be using that
USE flag :

~ # equery h opencl
 * Searching for USE flag opencl ...
[IP-] [  ] media-gfx/imagemagick-6.9.7.4:0/6.9.7.4
[IP-] [  ] media-libs/mesa-17.0.0_rc2:0
[IP-] [  ] media-libs/x264-0.0.20160712:0/148
[IP-] [  ] sys-apps/hwloc-1.11.2:0/5

Corbin

Re: [gentoo-user] mesa-12.0.1 fails to emerge

[Corbin Bird]

On 02/07/2017 05:02 PM, Mick wrote:
> How could I go beyond this point?
>
> =
> /var/tmp/portage/media-
> libs/mesa-12.0.1/work/mesa-12.0.1/src/gallium/state_track
> ers/clover/llvm/invocation.cpp:212:75: error: no matching function for call 
> to 
> ‘
> clang::CompilerInvocation::setLangDefaults(clang::LangOptions&, 
> clang::InputKind
> , llvm::Triple, clang::LangStandard::Kind)’
> =
>
> Extract from compile log attached.
>
> I am running sys-devel/clang-runtime-3.9.1 like so:
>
>  Installed versions:  3.9.1(21:25:30 07/02/17)(openmp -libcxx ABI_MIPS="-
> n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32")
>
---
If you would please, post if the USE flag "opencl" is set in
"make.conf", or in "package.use" for any packages.


Corbin

Re: [gentoo-user] AMDGPU

[Corbin Bird]

On 02/07/2017 01:49 PM, Mick wrote:
> On Tuesday 07 Feb 2017 09:41:19 Peter Humphrey wrote:
>> On Tuesday 07 Feb 2017 06:34:43 Mick wrote:
>>> On Monday 06 Feb 2017 17:11:30 Corbin Bird wrote:
>>>> On 02/06/2017 04:20 PM, Mick wrote:
>>>>> On Monday 06 Feb 2017 21:39:08 jdm wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Just followed the amdgpu wiki guide to get my new graphics card up
>>>>>> and
>>>>>> running. Excellent wiki guide and had no issues. Now running with
>>>>>> shiny graphics and throwing all that Steam has to offer at it.
>>>>>>
>>>>>> Many Thanks to the wiki authors.
>>>>>>
>>>>>> Will we always have to include binary blobs into the kernel for AMD
>>>>>> cards? This feels kind of odd for me so wondering if this will be
>>>>>> included as a package or a kernel driver at some point or what the
>>>>>> future direction is for AMD graphics with Linux.
>>>>>>
>>>>>> It may not be alien but not done this before so curious.
>>>>>>
>>>>>> John
>>>>> Invariably all modern CPUs, video cards, NICs, etc. are shipped with
>>>>> firmware which are usually emerged with sys-kernel/linux-firmware (or
>>>>> manually) and then loaded with an initrd, or by building them in the
>>>>> kernel.  Regarding AMDGPUs please note the Wiki strings of firmware
>>>>> blobs
>>>>> are not 100% correct. I noticed dmesg was complaining about missing
>>>>> blobs
>>>>> on a Kaveri APU although I>
>>>>>
>>>>> had all the complete Kaveri string included in the kernel.  I had to
>> add:
>>>>>   radeon/bonaire_uvd.bin radeon/BONAIRE_uvd.bin
>> radeon/BONAIRE_vce.bin
>>
>>>>> to keep it happy.
>>>>>
>>>>> BTW, for AMDGPUs you will also need to add CPU microcode blob strings.
>>>> Please explain : "BTW, for AMDGPUs you will also need to add CPU
>>>> microcode blob strings."
>>>  
>>>  https://wiki.gentoo.org/wiki/AMD_microcode
>> He'd be better off with https://wiki.gentoo.org/wiki/AMDGPU .
> I've always treated the two as complementary.  For the CPU cores the AMD 
> microcode is needed and this ought to go first in the kernel line.  For the 
> GPU cores the latter URL and firmware blob strings are needed.
>
>> That page didn't exist when I was setting this up, so I had to go through a
>> series of lookups to find that my device is a Tonga, but that route seems
>> not to work any more.
> Same here, but I forgot what I had to do back then (more than two years ago). 
>  
>

This web page is a good guide : ( for radeon / radeonsi cards )

https://wiki.gentoo.org/wiki/AMDGPU

Alas, if your video card is Polaris 10 / 11 based ... problems.

Thanks for for the pointer to the CPU microcode page. Didn't know that is how 
Gentoo handles it.

Re: [gentoo-user] webkit-gtk-2.14.2 cant find sqlite3 symbols

[Corbin Bird]

On 02/07/2017 09:55 AM, kelly hirai wrote:
>
>
> On 02/06/2017 06:31 PM, Corbin Bird wrote:
>> On 02/06/2017 01:09 PM, kelly hirai wrote:
>>> hello fellow gentoo-users,
>>>
>>>for about a month now, i have not been able to make
>>> webkit-gtk-2.14.[2,3] compile. it terminates at the linking step
>>> complaining it cant find some sqlite functions.
>>>
>>> ./configure phase reports sqlite3 availability
>>>
>>> -- Checking for module 'sqlite3'
>>> --   Found sqlite3, version 3.13.0
>>> -- Found Sqlite: /usr/include
>>>
>>> but when it comes time to do the linking it cant find it:
>>>
>>> FAILED: : && /usr/bin/x86_64-pc-linux-gnu-g++  -fPIC -march=native -O2
>>> -pipe -fno-strict-aliasing -std=c++1y -Wl,--no-undefined -Wl,-O1
>>> -Wl,--as-needed -Wl,--no-keep-memory -fuse-ld=gold
>>> -Wl,--disable-new-dtags -fuse-ld=gold -Wl,--disable-new-dtags
>>> -Wl,--version-script,/var/tmp/portage/net-libs/webkit-gtk-2.14.2/work/webkitgtk-2.14.2/Source/cmake/gtksymbols.filter
>>>
>>> -shared -Wl,-soname,libwebkit2gtk-4.0.so.37 -o
>>> lib/libwebkit2gtk-4.0.so.37.14.9 @CMakeFiles/WebKit2.rsp && :
>>> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
>>>
>>> void
>>> std::__once_call_impl<std::_Bind_simple<WebCore::initializeSQLiteIfNecessary()::{lambda()#1}
>>>
>>> ()> >(): error: undefined reference to 'sqlite3_initialize'
>>> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
>>>
>>> void
>>> std::__once_call_impl<std::_Bind_simple<WebCore::initializeSQLiteIfNecessary()::{lambda()#1}
>>>
>>> ()> >(): error: undefined reference to 'sqlite3_errstr'
>>> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
>>>
>>> WebCore::SQLiteDatabase::setCollationFunction(WTF::String const&,
>>> std::function): error:
>>> undefined reference to 'sqlite3_create_collation_v2'
>>> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
>>>
>>> WebCore::SQLiteDatabase::removeCollationFunction(WTF::String const&):
>>> error: undefined reference to 'sqlite3_create_collation_v2'
>>> collect2: error: ld returned 1 exit status
>>>
>>> the symbols seem to be in the library:
>>>
>>> strings /usr/lib32/libsqlite3.so | grep  create_collation_
>>> sqlite3_create_collation_v2
>>>
>>> strings /usr/lib64/libsqlite3.so | grep  create_collation_
>>> sqlite3_create_collation_v2
>>>
>>> i'm stumped here. i don't see any explicit linking flags. the
>>> @CMakefiles/WebKit2.rsp doesn't make sense to me, maybe its in there?
>>>
>>> k.
>> Please post the USE flags set for all the following :  "dev-db/sqlite:3"
>> and "net-libs/webkit-gtk:2", "net-libs/webkit-gtk:3",
>> "net-libs/webkit-gtk:4". ( Yes, webkit-gtk has three slots. 3 slots = 3
>> possible different sets of use flags. )
>>
>> Corbin
>>
> thanks for looking at this Corbin. :)
>
> [I] net-libs/webkit-gtk
>  Available versions:
>  (3)2.4.11-r1(3/25)
>  (2)2.4.11-r200
>  (4)2.12.5(4/37)^t ~2.14.2(4/37)^t ~2.14.3(4/37)^t
>{(+)X aqua coverage debug doc +egl +geoloc +geolocation gles2
> gnome-keyring +gstreamer +introspection +jit libnotify nsplugin
> +opengl spell test wayland +webgl
>  Installed versions:
> 2.4.11-r1(3)(01:04:58 PM 01/13/2017)(X egl geolocation
> gnome-keyring gstreamer introspection jit opengl spell webgl -aqua
> -coverage -debug -gles2 -test -wayland)
> 2.12.5(4)^t(01:07:41 AM 12/13/2016)(X egl geolocation
> gnome-keyring gstreamer introspection jit libnotify opengl spell webgl
> -aqua -coverage -doc -gles2 -nsplugin -test -wayland)
>
> [I] dev-db/sqlite
>  Available versions:  (3) 3.12.0 ~3.12.1 ~3.12.2 3.13.0 ~3.14.1
> ~3.14.2 ~3.15.1 ~3.15.2 ~3.16.2
>{debug doc icu +readline secure-delete static-libs tcl test
> tools ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64"
> ABI_X86="32 64 x32"}
>  Installed versions:  3.13.0(3)(11:35:43 AM 02/06/2017)(readline
> -debug -doc -icu -secure-delete -static-libs -tcl -test -tools
> ABI_MIPS="-n32 -n64 -o32&

Re: [gentoo-user] AMDGPU

[Corbin Bird]

On 02/07/2017 12:34 AM, Mick wrote:
> On Monday 06 Feb 2017 17:11:30 Corbin Bird wrote:
>> On 02/06/2017 04:20 PM, Mick wrote:
>>> On Monday 06 Feb 2017 21:39:08 jdm wrote:
>>>> Hi,
>>>>
>>>> Just followed the amdgpu wiki guide to get my new graphics card up and
>>>> running. Excellent wiki guide and had no issues. Now running with
>>>> shiny graphics and throwing all that Steam has to offer at it.
>>>>
>>>> Many Thanks to the wiki authors.
>>>>
>>>> Will we always have to include binary blobs into the kernel for AMD
>>>> cards? This feels kind of odd for me so wondering if this will be
>>>> included as a package or a kernel driver at some point or what the
>>>> future direction is for AMD graphics with Linux.
>>>>
>>>> It may not be alien but not done this before so curious.
>>>>
>>>> John
>>> Invariably all modern CPUs, video cards, NICs, etc. are shipped with
>>> firmware which are usually emerged with sys-kernel/linux-firmware (or
>>> manually) and then loaded with an initrd, or by building them in the
>>> kernel.  Regarding AMDGPUs please note the Wiki strings of firmware blobs
>>> are not 100% correct. I noticed dmesg was complaining about missing blobs
>>> on a Kaveri APU although I> 
>>> had all the complete Kaveri string included in the kernel.  I had to add:
>>>   radeon/bonaire_uvd.bin radeon/BONAIRE_uvd.bin radeon/BONAIRE_vce.bin
>>>
>>> to keep it happy.
>>>
>>> BTW, for AMDGPUs you will also need to add CPU microcode blob strings.
>> Please explain : "BTW, for AMDGPUs you will also need to add CPU
>> microcode blob strings."
>  https://wiki.gentoo.org/wiki/AMD_microcode
>
> More recent CPUs may not yet have microcode updates available for them.  
> Compare the before and after dmesg output to see if the patch level changes.
>
> HTH.

Thank you. I learned something :)

Re: [gentoo-user] webkit-gtk-2.14.2 cant find sqlite3 symbols

[Corbin Bird]

On 02/06/2017 01:09 PM, kelly hirai wrote:
> hello fellow gentoo-users,
>
>   for about a month now, i have not been able to make
> webkit-gtk-2.14.[2,3] compile. it terminates at the linking step
> complaining it cant find some sqlite functions.
>
> ./configure phase reports sqlite3 availability
>
> -- Checking for module 'sqlite3'
> --   Found sqlite3, version 3.13.0
> -- Found Sqlite: /usr/include
>
> but when it comes time to do the linking it cant find it:
>
> FAILED: : && /usr/bin/x86_64-pc-linux-gnu-g++  -fPIC -march=native -O2
> -pipe -fno-strict-aliasing -std=c++1y -Wl,--no-undefined -Wl,-O1
> -Wl,--as-needed -Wl,--no-keep-memory -fuse-ld=gold
> -Wl,--disable-new-dtags -fuse-ld=gold -Wl,--disable-new-dtags
> -Wl,--version-script,/var/tmp/portage/net-libs/webkit-gtk-2.14.2/work/webkitgtk-2.14.2/Source/cmake/gtksymbols.filter
> -shared -Wl,-soname,libwebkit2gtk-4.0.so.37 -o
> lib/libwebkit2gtk-4.0.so.37.14.9 @CMakeFiles/WebKit2.rsp && :
> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
> void
> std::__once_call_impl ()> >(): error: undefined reference to 'sqlite3_initialize'
> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
> void
> std::__once_call_impl ()> >(): error: undefined reference to 'sqlite3_errstr'
> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
> WebCore::SQLiteDatabase::setCollationFunction(WTF::String const&,
> std::function): error:
> undefined reference to 'sqlite3_create_collation_v2'
> lib/libWebCoreGTK.a(lib/../Source/WebCore/CMakeFiles/WebCore.dir/platform/sql/SQLiteDatabase.cpp.o):SQLiteDatabase.cpp:function
> WebCore::SQLiteDatabase::removeCollationFunction(WTF::String const&):
> error: undefined reference to 'sqlite3_create_collation_v2'
> collect2: error: ld returned 1 exit status
>
> the symbols seem to be in the library:
>
> strings /usr/lib32/libsqlite3.so | grep  create_collation_
> sqlite3_create_collation_v2
>
> strings /usr/lib64/libsqlite3.so | grep  create_collation_
> sqlite3_create_collation_v2
>
> i'm stumped here. i don't see any explicit linking flags. the
> @CMakefiles/WebKit2.rsp doesn't make sense to me, maybe its in there?
>
> k.
Please post the USE flags set for all the following :  "dev-db/sqlite:3"
and "net-libs/webkit-gtk:2", "net-libs/webkit-gtk:3",
"net-libs/webkit-gtk:4". ( Yes, webkit-gtk has three slots. 3 slots = 3
possible different sets of use flags. )

Corbin

Re: [gentoo-user] AMDGPU

[Corbin Bird]

On 02/06/2017 04:20 PM, Mick wrote:
> On Monday 06 Feb 2017 21:39:08 jdm wrote:
>> Hi,
>>
>> Just followed the amdgpu wiki guide to get my new graphics card up and
>> running. Excellent wiki guide and had no issues. Now running with
>> shiny graphics and throwing all that Steam has to offer at it.
>>
>> Many Thanks to the wiki authors.
>>
>> Will we always have to include binary blobs into the kernel for AMD
>> cards? This feels kind of odd for me so wondering if this will be
>> included as a package or a kernel driver at some point or what the
>> future direction is for AMD graphics with Linux.
>>
>> It may not be alien but not done this before so curious.
>>
>> John
> Invariably all modern CPUs, video cards, NICs, etc. are shipped with firmware 
> which are usually emerged with sys-kernel/linux-firmware (or manually) and 
> then loaded with an initrd, or by building them in the kernel.  Regarding 
> AMDGPUs please note the Wiki strings of firmware blobs are not 100% correct.  
> I noticed dmesg was complaining about missing blobs on a Kaveri APU although 
> I 
> had all the complete Kaveri string included in the kernel.  I had to add:
>
>   radeon/bonaire_uvd.bin radeon/BONAIRE_uvd.bin radeon/BONAIRE_vce.bin
>
> to keep it happy.
>
> BTW, for AMDGPUs you will also need to add CPU microcode blob strings.
Please explain : "BTW, for AMDGPUs you will also need to add CPU
microcode blob strings."

Re: [gentoo-user] bash-completion question(s)

[Corbin Bird]

On 02/02/2017 01:19 PM, Neil Bothwick wrote:
> On Tue, 31 Jan 2017 12:34:50 -0600, Corbin Bird wrote:
>
>> The package "sys-boot/grub:2" popped this warning during updates :
>>
>>> Problems with installed bash completions were found:
>>>
>>> grub: 'have' command is deprecated and must not be used.
>>> grub: incorrect name, no completions for 'grub' command defined.
>>> grub-mkconfig: missing alias (symlink) for completed command.
>>> grub-mkpasswd-pbkdf2: missing alias (symlink) for completed
>>> command. grub-mkrescue: missing alias (symlink) for completed command.
>>> grub-reboot: missing alias (symlink) for completed command.
>>> grub-editenv: missing alias (symlink) for completed command.
>>> grub-set-default: missing alias (symlink) for completed command.
>>> grub-mkimage: missing alias (symlink) for completed command.
>>> grub-sparc64-setup: missing alias (symlink) for completed command.
>>> grub-bios-setup: missing alias (symlink) for completed command.
>>> grub-script-check: missing alias (symlink) for completed command.
>>> grub-probe: missing alias (symlink) for completed command.
>>> grub-mkfont: missing alias (symlink) for completed command.
>>> grub-install: missing alias (symlink) for completed command.  
>> No "grub" entries found at all in "/usr/share/bash-completions".
> Did you install it with USE=multislot? That would cause all those
> commands to be named grub2-* instead of grub-*, which may confuse the
> bash completions.
>
>

The USE flags it was installed with :

sys-boot/grub:2 efiemu fonts mount nls sdl themes truetype -debug
-device-mapper -doc -multislot -static -test

results of "emerge --search grub"
> * sys-boot/grub Latest version available: 2.02_beta3-r1 Latest version
> installed: 2.02_beta3-r1 Size of files: 7,623 KiB Homepage:
> https://www.gnu.org/software/grub/ Description: GNU GRUB boot loader
> License: GPL-3 fonts? ( GPL-2-with-font-exception ) themes? (
> BitstreamVera ) * sys-boot/grub-static Latest version available:
> 0.97-r12 Latest version installed: [ Not Installed ] Size of files:
> 1,145 KiB Homepage: https://www.gnu.org/software/grub/ Description:
> GNU GRUB Legacy boot loader (static build) License: GPL-2



--

I did a --unmerge && emerged "app-shells/bash-completion" again. Now I
have a 'grub' config file for bash-completions.

The following are missing :

grub-mkpasswd-pbkdf2
grub-editenv
grub-sparc64-setup
grub-bios-setup

-

Should have known. Install order is critical. Everything else first, 
"bash-completions" last.

Thank you for for getting the mental gears moving again.

Re: [gentoo-user] bash-completion question(s)

[Corbin Bird]

On 02/02/2017 04:38 AM, Dale wrote:
> Corbin Bird wrote:
>> The package "sys-boot/grub:2" popped this warning during updates :
>>
>>> Problems with installed bash completions were found:
>>>
>>> grub: 'have' command is deprecated and must not be used.
>>> grub: incorrect name, no completions for 'grub' command defined.
>>> grub-mkconfig: missing alias (symlink) for completed command.
>>> grub-mkpasswd-pbkdf2: missing alias (symlink) for completed command.
>>> grub-mkrescue: missing alias (symlink) for completed command.
>>> grub-reboot: missing alias (symlink) for completed command.
>>> grub-editenv: missing alias (symlink) for completed command.
>>> grub-set-default: missing alias (symlink) for completed command.
>>> grub-mkimage: missing alias (symlink) for completed command.
>>> grub-sparc64-setup: missing alias (symlink) for completed command.
>>> grub-bios-setup: missing alias (symlink) for completed command.
>>> grub-script-check: missing alias (symlink) for completed command.
>>> grub-probe: missing alias (symlink) for completed command.
>>> grub-mkfont: missing alias (symlink) for completed command.
>>> grub-install: missing alias (symlink) for completed command.
>> No "grub" entries found at all in "/usr/share/bash-completions".
>>
>> Is it correct to assume any "bash-completions" are strictly personal
>> choice and NOT technically required?
>>
> I emerged grub here to see if I would get any of those messages.  I
> didn't.  It merged cleanly as far as I can tell.  This is the version I
> have:
>
> sys-boot/grub-2.02_beta3-r1
>
> As far as your question, the package itself should work with or without
> bash-completion.  As far as I know, it only affects using tab to
> complete commands/options. 
>
> Dale
>
> :-)  :-) 
>


I should have mentioned the package "app-shells/bash-completion" was
installed. My mistake.

So, I will treat "bash-completions" as optional.

For your efforts and time, Thank You.

[gentoo-user] bash-completion question(s)

[Corbin Bird]

The package "sys-boot/grub:2" popped this warning during updates :

> Problems with installed bash completions were found:
>
> grub: 'have' command is deprecated and must not be used.
> grub: incorrect name, no completions for 'grub' command defined.
> grub-mkconfig: missing alias (symlink) for completed command.
> grub-mkpasswd-pbkdf2: missing alias (symlink) for completed command.
> grub-mkrescue: missing alias (symlink) for completed command.
> grub-reboot: missing alias (symlink) for completed command.
> grub-editenv: missing alias (symlink) for completed command.
> grub-set-default: missing alias (symlink) for completed command.
> grub-mkimage: missing alias (symlink) for completed command.
> grub-sparc64-setup: missing alias (symlink) for completed command.
> grub-bios-setup: missing alias (symlink) for completed command.
> grub-script-check: missing alias (symlink) for completed command.
> grub-probe: missing alias (symlink) for completed command.
> grub-mkfont: missing alias (symlink) for completed command.
> grub-install: missing alias (symlink) for completed command.

No "grub" entries found at all in "/usr/share/bash-completions".

Is it correct to assume any "bash-completions" are strictly personal
choice and NOT technically required?

Re: [gentoo-user] a couple of preserved-rebuild problems -- how to fix

[Corbin Bird]

On 01/30/2017 09:31 AM, Alan McKinnon wrote:
> On 30/01/2017 17:15, Corbin Bird wrote:
>> On 01/30/2017 08:56 AM, Alan McKinnon wrote:
>>> On 30/01/2017 16:55, John Covici wrote:
>>>> On Mon, 30 Jan 2017 09:32:46 -0500,
>>>> Alan McKinnon wrote:
>>> [snip]
>>>
>>>
>>>> But I found binutils-config and just switched from 2.25-r1 to 2.27, so
>>>> I will see what happens.
>>>> So, after removing the old versions of binutils, the preserved-rebuild
>>>> problem went away!
>>>>
>>>> Thanks all for all your help on that .  Now I have to somehow deal
>>>> with the gst-plugins-ffmpeg.
>>> Have you considered dumping gstreamer and going with vlac and a
>>> different backend  :-)
>>>
>>>
>> ? vlac ? If you would please, explain this acronym.
>>
>
> Oops typo.
>
> vlc
>
Thank you.

That makes a lot more sense. :)

Re: [gentoo-user] a couple of preserved-rebuild problems -- how to fix

[Corbin Bird]

On 01/30/2017 08:56 AM, Alan McKinnon wrote:
> On 30/01/2017 16:55, John Covici wrote:
>> On Mon, 30 Jan 2017 09:32:46 -0500,
>> Alan McKinnon wrote:
> [snip]
>
>
>> But I found binutils-config and just switched from 2.25-r1 to 2.27, so
>> I will see what happens.
>> So, after removing the old versions of binutils, the preserved-rebuild
>> problem went away!
>>
>> Thanks all for all your help on that .  Now I have to somehow deal
>> with the gst-plugins-ffmpeg.
>
> Have you considered dumping gstreamer and going with vlac and a
> different backend  :-)
>
>
? vlac ? If you would please, explain this acronym.

Re: [gentoo-user] a couple of preserved-rebuild problems -- how to fix

[Corbin Bird]

On 01/29/2017 08:02 AM, John Covici wrote:
> On Sun, 29 Jan 2017 08:41:59 -0500,
> Responses in line.
>
> Alan McKinnon wrote:
>> On 29/01/2017 12:11, John Covici wrote:
>>> Hi.  I am having a couple of preserved rebuild problems which I have
>>> no idea how to fix.
>> Ugh. Those problems are horrid to fix
>>
>>> The first one is like this:
>> package: sys-libs/binutils-libs-2.27
>>>  *  - /usr/lib64/libbfd-2.25.1.so
>>>   *  used by
>>>   /usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so
>>>   (sys-devel/binutils-2.25.1-r1)
>>>
>>> And no matter how many times I recompile the suggested package(s)  it
>>> remains.  Why is this happening and how can I fix?
>> Let's establish first what portage thinks the problem is. What is the
>> output of
>>
>> ldd /usr/lib64/binutils/x86_64-pc-linux-gnu/2.25.1/libopcodes-2.25.1.so
>>
> linux-vdso.so.1 (0x7fff91936000)
>  libbfd-2.25.1.so => /usr/lib64/libbfd-2.25.1.so
>  (0x7fd3deeb7000)
>libc.so.6 => /lib64/libc.so.6
>  (0x7fd3deb1e000)
>libz.so.1 => /lib64/libz.so.1
>  (0x7fd3de906000)
>libdl.so.2 => /lib64/libdl.so.2
>  (0x7fd3de702000)
>/lib64/ld-linux-x86-64.so.2
>  (0x55f4cd0d2000)
>
>> and just for fun
>>
>> ldd /usr/lib64/libbfd-2.25.1.so
> linux-vdso.so.1 (0x7ffeac123000)
>  libz.so.1 => /lib64/libz.so.1 (0x7fbaf1838000)
>libdl.so.2 => /lib64/libdl.so.2
> (0x7fbaf1634000)
>  libc.so.6 => /lib64/libc.so.6 (0x7fbaf129a000)
>/lib64/ld-linux-x86-64.so.2
> (0x5643cb966000)
>  
>> Plus, what are your USE flags for binutils.
> I seem to have several binutils -- here is what I have:
>  Installed versions:  2.25.1-r1(2.25.1)(01:06:59 AM
>   01/11/2017)(cxx nls zlib -multitarget -static-libs -test
>   -vanilla) 2.26.1(2.26.1)(07:16:43 AM 12/27/2016)(cxx nls
>   -multitarget -static-libs -test -vanilla) 2.27(2.27)(07:23:40 AM
>   12/27/2016)(cxx nls -multitarget -static-libs -test -vanilla)
>   
>>> Now the second one is more complicated:
>> package: media-video/ffmpeg-3.2.2
>>>  *  - /usr/lib64/libswscale.so.3
>>>   *  - /usr/lib64/libswscale.so.3.1.101
>>>*  used by /usr/lib64/gstreamer-0.10/libgstffmpegscale.so
>>>(media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3)
>>> *  - /usr/lib64/libpostproc.so.53
>>>  *  - /usr/lib64/libpostproc.so.53.3.100
>>>  *  used by /usr/lib64/gstreamer-0.10/libgstpostproc.so
>>>  (media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3)
>>>   *  - /usr/lib64/libavcodec.so.56
>>>*  - /usr/lib64/libavcodec.so.56.60.100
>>> *  used by /usr/lib64/gstreamer-0.10/libgstffmpeg.so
>>> (media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3)
>>>  *  used by /usr/lib64/gstreamer-0.10/libgstpostproc.so
>>> (media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3)
>>>  *  - /usr/lib64/libavformat.so.56
>>>   *  - /usr/lib64/libavformat.so.56.40.101
>>>*  used by /usr/lib64/gstreamer-0.10/libgstffmpeg.so
>>>(media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3)
>>> *  - /usr/lib64/libavutil.so.54
>>>  *  - /usr/lib64/libavutil.so.54.31.100
>>>  *  used by
>>>  /usr/lib64/gstreamer-0.10/libgstffmpeg.so
>>>  (media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3)
>>>   *  used by
>>>   /usr/lib64/gstreamer-0.10/libgstffmpegscale.so
>>>   (media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3)
>>>*  used by
>>>/usr/lib64/gstreamer-0.10/libgstpostproc.so
>>>(media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3)
>>> *  - /usr/lib64/libswresample.so.1
>>>  *  - /usr/lib64/libswresample.so.1.2.101
>>>
>>> Now when I try to recompile it wants to upgrade, but the upgrade does
>>> not emerge and there are so many depricated warnings and errors that I
>>> have a link to the build log instead
>>>
>>> https://covici.com/owncloud/index.php/s/LOysHMSxcFDfLDD
>>>
>>> There is no ebuild for the original version in the tree, so I am
>>> stumped here.
>> This one rings a bell but I can't recall exactly what.
>>
>> I have several times in the past resolved these by brute force,
>> unmerging the problem package and the thing it depends or or links to,
>> then rebuilding both.
>>
>> Are you by chance running a mixed stable/testing system here?
>>
> No, just testing.  I could unmerge and 

Re: [gentoo-user] Problem with gdbus-codegen

[Corbin Bird]

On 01/26/2017 11:15 AM, Peter Humphrey wrote:
> Corbin Bird <corbinb...@charter.net> wrote :
>
>
>> If you would please, run this command and post the output ( a test in
>> other words ).
>>
>>> emerge -pvt dev-util/gdbus-codegen:0
> It wants to downgrade again, with the same output as I posted last time.
>
A package version / dependency blocker?

This command might ID the culprit.

> equery g dev-util/gdbus-codegen:0

Example results :

>  * dependency graph for dev-util/gdbus-codegen-2.48.2
>  `--  dev-util/gdbus-codegen-2.48.2  amd64
>`--  dev-lang/python-2.7.12  (>=dev-lang/python-2.7.5-r2) amd64  [xml]
>`--  dev-lang/python-3.4.5  (dev-lang/python) amd64  [xml]
>`--  dev-lang/python-3.5.2  (dev-lang/python) ~amd64  [xml]
>`--  dev-lang/python-exec-2.4.4  (>=dev-lang/python-exec-2) amd64 
> [python_targets_python2_7(-)? python_targets_python3_4(-)?
> python_targets_python3_5(-)? -python_single_target_python2_7(-)
> -python_single_target_python3_4(-) -python_single_target_python3_5(-)]
>`--  app-arch/xz-utils-5.2.3  (app-arch/xz-utils) amd64
>`--  dev-libs/glib-2.48.2  (>=dev-libs/glib-2.48.2) amd64
> [ dev-util/gdbus-codegen-2.48.2 stats: packages (7), max depth (1) ]

>  * dependency graph for dev-util/gdbus-codegen-2.50.2
>  `--  dev-util/gdbus-codegen-2.50.2  [~amd64 keyword]
>`--  dev-lang/python-2.7.12  (>=dev-lang/python-2.7.5-r2) amd64  [xml]
>`--  dev-lang/python-3.4.5  (dev-lang/python) amd64  [xml]
>`--  dev-lang/python-3.5.2  (dev-lang/python) ~amd64  [xml]
>`--  dev-lang/python-exec-2.4.4  (>=dev-lang/python-exec-2) amd64 
> [python_targets_python2_7(-)? python_targets_python3_4(-)?
> python_targets_python3_5(-)? -python_single_target_python2_7(-)
> -python_single_target_python3_4(-) -python_single_target_python3_5(-)]
>`--  app-arch/xz-utils-5.2.3  (app-arch/xz-utils) amd64
>`--  dev-libs/glib-2.50.2  (>=dev-libs/glib-2.50.2) [~amd64 keyword]
> [ dev-util/gdbus-codegen-2.50.2 stats: packages (7), max depth (1) ]

I didn't know that the USE flag "xml" was required by
"dev-util/gdbus-codegen" on the "dev-lang/python" packages.

Learned a new approach to determine dependency blockers. Thank You :)

Re: [gentoo-user] Problem with gdbus-codegen

[Corbin Bird]

On 01/26/2017 09:35 AM, Peter Humphrey wrote:
> (Sent via webmail while I continue wrestling with KMail...)
>
> Alan McKinnon  wrote :
>
>> Does explicitly emerging gdbus-codegen-2.50.2 then re-running a world
>> emerge give a different result?
> peak ~ # emerj -1 =gdbus-codegen-2.50.2
> Calculating dependencies  ... done!
>
> emerge: there are no ebuilds to satisfy "=gdbus-codegen-2.50.2".
> peak ~ # eix -e gdbus-codegen
> [I] dev-util/gdbus-codegen
>  Available versions:  2.44.1 2.46.2 2.48.2 (~)2.50.0 (~)2.50.1 (~)2.50.2 
> {PYTHON_TARGETS="python2_7 python3_4 python3_5"}
>  Installed versions:  2.50.2(18:06:24 10/01/17)(PYTHON_TARGETS="python2_7 
> python3_4 -python3_5")
>  Homepage:http://www.gtk.org/
>  Description: GDBus code and documentation generator
>
> Something's screwed up here. I ran eclean-dist this morning and it listed 
> 90-odd packages with versions not in the database, which was not true. 
> Running eix-update again made no difference.
>
> I'm considering building a new system, but amd64 instead of ~amd64. I only 
> set the latter when this was a new box and too many packages needed to be the 
> ~ versions to be manageable otherwise.
>

If you would please, run this command and post the output ( a test in
other words ).

> emerge -pvt dev-util/gdbus-codegen:0

Re: [gentoo-user] Re: Problem matching latest kernel with latest Nvidia

[Corbin Bird]

On 01/10/2017 01:29 PM, Nikos Chantziaras wrote:
> On 01/10/2017 06:31 PM, Corbin Bird wrote:
>> You might want to add "static-libs" to the use flags as well. Another
>> useful utility gets built by it.
>
> There doesn't seem to be anything installed by it, except a static lib
> (libXNVCtrl.a) and some header files (/usr/include/NVCtrl). No
> executables.
>
>

Thanks for that info. You did jog the memory.

"sys-apps/hwloc" USE = gl ... is dependent on that lib being built
static. ( NVCtrl )

USE = gl  :  Enable GL display device discovery (NVCtrl)
USE = opencl : Enable OpenCL device discovery (AMD only)

Re: [gentoo-user] Problem matching latest kernel with latest Nvidia

[Corbin Bird]

On 01/10/2017 10:46 AM, J. Roeleveld wrote:
> On January 10, 2017 5:31:19 PM GMT+01:00, Corbin Bird 
> <corbinb...@charter.net> wrote:
>> On 01/10/2017 04:22 AM, J. Roeleveld wrote:
>>> On January 10, 2017 10:01:12 AM GMT+01:00, Philip Webb
>> <purs...@ca.inter.net> wrote:
>>>> 170109 Nikos Chantziaras wrote:
>>>>> On 01/09/2017 10:09 AM, Philip Webb wrote:
>>>>>> I had a previous thread re Kernel 4.9.0 + Nvidia 375.26 (now
>>>> stable).
>>>>>> I tried recompiling that kernel with DRM disabled,
>>>>>> & remerged Nvidia 375.26 , but X won't start.
>>>>> The nvidia driver isn't "automatic". It's not used by X.Org by
>>>> default.
>>>>> X.Org only uses its own drivers by default.
>>>>> For the nvidia driver, you need a conf file.
>>>>> Something like this in /etc/X11/xorg.conf.d/nvidia.conf:
>>>>> http://pastebin.com/raw/0y3NMndp
>>>> I didn't need this with earlier versions of Nvidia-drivers,
>>>> but I've copied your template & am willing to give it a try.
>>>> It looks as if there are several lines which wouldn't fit my
>> machine.
>>>>> The nvidia driver has a tool to help with this too,
>>>>> it's called `nvidia-xconfig`.
>>>> It doesn't seem to be available on my machine :
>>>>
>>>>  root:515 xorg.conf.d> which nvidia-xconfig
>>>> which: no nvidia-xconfig in
>>>> (/sbin:/usr/sbin:/usr/local/sbin::/bin:/usr/bin:/usr/local/bin:)
>>>>  root:517 xorg.conf.d> nvidia-xconfig
>>>>   bash: nvidia-xconfig: command not found
>>>>
>>>> Thanks to the others who replied.  One asked for USE flags : here
>> they
>>>> are :
>>>>
>>>>  root:518 xorg.conf.d> eix nvidia-drivers
>>>>   ...
>>>> Installed versions:  361.28^msd{tbz2}([2017-01-09 02:41:57])(X
>> driver
>>>> gtk3 kms -acpi -multilib -pax_kernel -static-libs -tools -uvm
>>>> KERNEL="linux -FreeBSD")
>>>>
>>>> Those are for the version which works & which I've had to restore,
>>>> but I didn't change them for 375.26 .
>>>>
>>>> Further suggestions are very welcome.
>>> Add the "tools" USE flag to get nvidiasettings and similar.
>>>
>>> Am going to try a later version of drivers and kernel myself later.
>>>
>>> --
>>> Joost
>> You might want to add "static-libs" to the use flags as well. Another
>> useful utility gets built by it.
> Which one would that be?
> I would not expect any tools or utilities to be added when selecting static 
> libraries.
>
> --
> Joost

I can't remember the specific name of it, had to do with ?OpenCL? or ?CUDA?
Other posters on this list using "x11-drivers/nvidia-drivers" could tell
you exactly why.
I should have saved those e-mails, but didn't. :(

-
The link has the whole list all libs && utilities that are built /
installed.

Reference / Doc Link :
ftp://download.nvidia.com/XFree86/Linux-x86/375.26/README/README.txt