Re: [gentoo-user] EAPI packages

[David Haller]

Hello,

On Tue, 16 Aug 2016, hw wrote:
>David Haller schrieb:
[..]
>> Yep. BTDT. I had a then 4-4.5 year old gentoo quite broken by being
>> partly updated until portage/emerge broke and much else didn't work
>> anymore (gcc/make/python/emerge). So, I booted something else, mounted
>> gentoo somewhere (say /mnt), unpacked a fresh stage3 _into_ that
>> mountpoint into /stage3 (i.e. "/mnt/stage3"), chrooted there (with the
>> usual /sys, /proc, /dev bind-mounts) and then ran stuff from the
>> /stage3/ tree[1] until the basic stuff (mainly above mentioned 4) was
>> fixed.
>
>How would it fix the system you chrooted from?  Doesn?t it remain limited
>to the chrooted environment?

The chrooted-to was the gentoo to be updated. I just booted something
else with a recent enough kernel. So, it was:

/   = 
/mnt= Gentoo-/
/mnt/stage3 = current Gentoo-stage-3

Then the usual bindmounts of /proc, /sys, /dev and chroot into /mnt.

So, I was in / of Gentoo with /stage3 the unpacked stage3-tarball.

Then some "magic", by setting PATH and LD_LIBRARY_PATH to use stage3
for the first stuff until I got glibc, gcc, python, portage etc.
in / itself up-to-date.

export PATH=/stage3/sbin:/stage3/usr/sbin:/stage3/bin:/stage3/usr/bin:$PATH
export LD_LIBRARY_PATH="/stage3/lib64:/stage3/usr/lib64"
and IIRC
export 
PYTHONPATH"/stage3/usr/lib64/python2.7:/stage3/usr/lib/python2.7:$PYTHONPATH"

If I typed 'which emerge' it showed to be the current version from
stage3 and could handle the updated portage-tree and new EAPI.

I thought this easier than the way shown in the wiki where you chroot
to the stage3. Actually, I guess I'm wrong when you just do an

  alias emerge='/usr/bin/emerge --root=/mnt/host --config-root=/mnt/host'

after you chrooted to the /stage3 as per
https://wiki.gentoo.org/wiki/Upgrading_Gentoo#Updating_old_systems

>> From then on it mostly went "smooth", by the "textbook",
>> considering. Yeah, lots of conflicts and whatnot because of moves,
>> renames and new deps etc.pp. It was a bit tedious, but not difficult.
>> 
>> And this general tip came out of it: unmerging stuff helps to break
>> tangles. Like slashing the Gordian Knot ;)
>
>When I unmerge stuff, that stuff doesn?t work anymore, so I?d have to
>do that at night.

Well, when it's just one or two packages, that usually doesn't take
that long.

>There was a version in between, and the update failed.  The output of
>emerge is very confusing and doesn?t tell me much, if anything, and
>I haven?t had the time to finish the update yet.  That?s going on
>for a month or two now, and it?s still not updated.

IIRC that was because modules were moved into perl-core, i.e.
disappeared as seperate modules and stuff might have still had them
as deps.

-dnh

-- 
I'm broken. Please show this to someone who can fix can fix
-- A message in a TeX system
  (Kudos to H J Haataja for the sig)

Re: [gentoo-user] XOrg / XRanR segfault starting X

[David Haller]

Hello,

On Thu, 18 Aug 2016, james wrote:
>other tools:: 'lshw'

or sys-apps/hwinfo

HTH,
-dnh

-- 
"I'm nobody's puppet!"-- Rygel XIV

[gentoo-user] portage in git: egencache not honoring --jobs, only using single core

[Holger Hoffstätte]

Hopefully easy question about portage via git (from Github); didn't
find anything in bugzilla.

Have been using it for a while and everything works, but the
slow metadata cache updates are annoying, so I dug into the script
call chain, ended up in egencache and for the life of me can't figure
out why it only uses a single core, despite the fact that $(nproc)
is passed as --jobs argument. Even calling it manually with --jobs=8
only uses a single core, regardless of python version (tried 2.7
and 3.5).

Does this work for anyone, or is it a known bug/lack of
implementation?

Holger

Re: [gentoo-user] Re: Question about genkernel's default kernel config

[Rich Freeman]

On Thu, Aug 18, 2016 at 6:41 PM, Raymond Jennings  wrote:
> On Mon, Aug 15, 2016 at 1:32 AM, Rich Freeman  wrote:
>>
>> And since it uses udev it is fairly robust against things like adding
>> a drive and now the kernel re-letters everything.
>
> Did you seriously just post that on a gentoo list?
>

Yes

> I assume you mean /dev/sd? and not A: B: C:
>

Yes.  What else would you call it?

-- 
Rich

Re: [gentoo-user] VirtualBox spamming dmesg

[Peter Humphrey]

On Thursday 18 Aug 2016 17:33:03 J. Roeleveld wrote:
> On August 18, 2016 6:22:41 PM GMT+02:00, Peter Humphrey 
 wrote:
> >Recently I've noticed large numbers of logging messages going to dmesg
> >from vboxpci. It keeps announcing that it's created or is freeing IOMMU
> >domains. Vbox is being used by BOINC projects, which install new .vdi
> >files as they start new jobs, then delete them on completion.
> >
> >Is there a way to shut it up? I can't see anything useful on
> >virtualbox.org.
> 
> Which virtualbox version?
> Saw something about kern.log filling up which was resolved with 5.0.10

This is 5.1.0. I would go to 5.1.2 but vLHC, one of the BOINC projects, has 
trouble with it.

-- 
Rgds
Peter

Re: [gentoo-user] Re: Question about genkernel's default kernel config

[Raymond Jennings]

On Mon, Aug 15, 2016 at 1:32 AM, Rich Freeman  wrote:

> And since it uses udev it is fairly robust against things like adding
> a drive and now the kernel re-letters everything.
>

Did you seriously just post that on a gentoo list?

I assume you mean /dev/sd? and not A: B: C:

:P

Re: [gentoo-user] VirtualBox spamming dmesg

[J. Roeleveld]

On August 18, 2016 6:22:41 PM GMT+02:00, Peter Humphrey  
wrote:
>Hello list,
>
>Recently I've noticed large numbers of logging messages going to dmesg
>from 
>vboxpci. It keeps announcing that it's created or is freeing IOMMU
>domains. 
>Vbox is being used by BOINC projects, which install new .vdi files as
>they 
>start new jobs, then delete them on completion.
>
>Is there a way to shut it up? I can't see anything useful on
>virtualbox.org.

Which virtualbox version?
Saw something about kern.log filling up which was resolved with 5.0.10

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[gentoo-user] VirtualBox spamming dmesg

[Peter Humphrey]

Hello list,

Recently I've noticed large numbers of logging messages going to dmesg from 
vboxpci. It keeps announcing that it's created or is freeing IOMMU domains. 
Vbox is being used by BOINC projects, which install new .vdi files as they 
start new jobs, then delete them on completion.

Is there a way to shut it up? I can't see anything useful on virtualbox.org.

-- 
Rgds
Peter

Re: [gentoo-user] Can't create valid btrfs on NVMe

[Rich Freeman]

On Thu, Aug 18, 2016 at 9:45 AM, Neil Bothwick  wrote:
>
> 4.1.30 - then I realised that sysrescd defaults to an older kernel (my
> rescue version in /boot always boots to the alt kernel). I tried the alt
> kernel, which is 4.4.17, and it worked!
>

Hmm, that longterm is starting to look somewhat mature.  I might
consider switching over myself.  Usually I try to give them a good six
months before I consider them ready for btrfs (they have a tendency to
introduce regressions in new kernel versions; I gave up on tracking
non-longterm ages ago).

-- 
Rich

Re: [gentoo-user] Can't create valid btrfs on NVMe

[Rich Freeman]

On Thu, Aug 18, 2016 at 8:57 AM, J. Roeleveld  wrote:
> On Wednesday, August 17, 2016 11:26:13 PM Neil Bothwick wrote:
>> I'm putting together a new desktop using a Samsung SM951 NVMe drive. I
>> booted sysrescd, partitioned the drive and ran
>>
>> mkfs.btrfs /dev/nvme0n1p3
>> mount /dev/nvme0n1p3 /mnt/custom
>>
>> df -T, mount and findmnt all show this is mounted as a btrfs filesystem,
>> e.g.
>>
>> /dev/nvme0n1p3 on /mnt/custom type btrfs (rw,relatime,ssd,space_cache)
>>
>> I can create files in here but cannot do anything btrfs-y
>>
>> % btrfs filesystem show /mnt/custom
>> ERROR: not a valid btrfs filesystem: /mnt/custom
>>
>> % btrfs subvolume create /mnt/custom/test
>> Create subvolume '/mnt/custom/test'
>> ERROR: cannot create subvolume: Inappropriate ioctl for device
>>
>> Google has been no help at all.
>
> I've got a similar drive in my desktop and it actually works.
> Difference: I am using Ext4.
>
> Can you try Ext4 and see if it works?
> Next test: Does it work with a non-NVMe drive?
>
> Also, which kernel version?

I think you guys are going down the wrong road.  The kernel drivers
are almost certainly working for the drive, otherwise the filesystem
wouldn't work at all, and I'm sure a million ext4 users would have
noticed a problem by now.

This is almost certainly a bug in btrfs-progs, or maybe the btrfs
filesystem driver in the kernel.

I'd suggest raising this on the btrfs mailing list, where it is going
to get a lot more attention from the people who develop btrfs.  There
are a few of us who use it around here, but I'd have to spend a day
tweaking the btrfs-progs source to have a guess at where this is
bailing out.  I suspect somebody over there would have an answer
almost immediately.

-- 
Rich

Re: [gentoo-user] Can't create valid btrfs on NVMe

[Neil Bothwick]

On Thu, 18 Aug 2016 09:38:03 -0400, Rich Freeman wrote:

> This is almost certainly a bug in btrfs-progs, or maybe the btrfs
> filesystem driver in the kernel.

The latter, a later kernel appears to have done the trick.
 
> I'd suggest raising this on the btrfs mailing list, where it is going
> to get a lot more attention from the people who develop btrfs.  There
> are a few of us who use it around here, but I'd have to spend a day
> tweaking the btrfs-progs source to have a guess at where this is
> bailing out.  I suspect somebody over there would have an answer
> almost immediately.

As our resident btrfs expert, I was expecting you to come up with an
immediate answer ;-)


-- 
Neil Bothwick

The nice thing about Windows is - It does not just crash,
it displays a dialog box and lets you press OK first.


pgp942xsfDvwI.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Can't create valid btrfs on NVMe

[Neil Bothwick]

On Thu, 18 Aug 2016 14:57:04 +0200, J. Roeleveld wrote:

> I've got a similar drive in my desktop and it actually works.
> Difference: I am using Ext4.

Yes, it works on ext4 here.
 
> Can you try Ext4 and see if it works? 
> Next test: Does it work with a non-NVMe drive?

That's my next test, but I've used sysrescd to set up btrfs before, so I
doubt that's the cause.
 
> Also, which kernel version?

4.1.30 - then I realised that sysrescd defaults to an older kernel (my
rescue version in /boot always boots to the alt kernel). I tried the alt
kernel, which is 4.4.17, and it worked!

Many thanks, Joost. It always helps to have someone point out the one
obvious point I've overlooked!


-- 
Neil Bothwick

I am Ken Dodd of the Borg... What a fine day to be assimilated missus!!


pgp8YDaKxwCLe.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Can't create valid btrfs on NVMe

[J. Roeleveld]

On Wednesday, August 17, 2016 11:26:13 PM Neil Bothwick wrote:
> I'm putting together a new desktop using a Samsung SM951 NVMe drive. I
> booted sysrescd, partitioned the drive and ran
> 
> mkfs.btrfs /dev/nvme0n1p3
> mount /dev/nvme0n1p3 /mnt/custom
> 
> df -T, mount and findmnt all show this is mounted as a btrfs filesystem,
> e.g.
> 
> /dev/nvme0n1p3 on /mnt/custom type btrfs (rw,relatime,ssd,space_cache)
> 
> I can create files in here but cannot do anything btrfs-y
> 
> % btrfs filesystem show /mnt/custom
> ERROR: not a valid btrfs filesystem: /mnt/custom
> 
> % btrfs subvolume create /mnt/custom/test
> Create subvolume '/mnt/custom/test'
> ERROR: cannot create subvolume: Inappropriate ioctl for device
> 
> Google has been no help at all.

Neil,

I've got a similar drive in my desktop and it actually works.
Difference: I am using Ext4.

Can you try Ext4 and see if it works? 
Next test: Does it work with a non-NVMe drive?

Also, which kernel version?

--
Joost

Re: [gentoo-user] XOrg / XRanR segfault starting X

[james]

On 08/18/2016 02:07 AM, J. Roeleveld wrote:

On August 18, 2016 6:59:53 AM GMT+02:00, Dave Trombley 
 wrote:

Hi all!

New to Gentoo, just followed the handbook install for amd64 and then
for
XOrg.

   I'm seeing the server segfault on 'startx'.   Here is the console
output (and I've attached the logfile).

   X.Org X Server 1.17.4
Release Date: 2015-10-28
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.6-gentoo x86_64 Gentoo
Current Operating System: Linux snow 4.4.6-gentoo #3 SMP PREEMPT Thu
Aug 18
04:18:24 Local time zone must be set-- x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.6-gentoo
root=UUID=8cb564c3-38fb-4b05-bc60-eaccf543e3ab ro
Build Date: 17 August 2016  07:13:48PM

Current version of pixman: 0.32.8
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 18 04:53:29 2016
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] drm report modesetting isn't supported.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x58c856]
(EE) 1: /usr/bin/X (0x40+0x190b09) [0x590b09]
(EE) 2: /lib64/libc.so.6 (0x7f34667ed000+0x33370) [0x7f3466820370]
(EE) 3: /usr/bin/X (RRSetChanged+0x50) [0x4f0c50]
(EE) 4: /usr/bin/X (RRScreenSetSizeRange+0x54) [0x4f5184]
(EE) 5: /usr/bin/X (xf86RandR12CreateScreenResources+0x295) [0x4b7d65]
(EE) 6: /usr/bin/X (0x40+0xab130) [0x4ab130]
(EE) 7: /usr/bin/X (0x40+0x3bff4) [0x43bff4]
(EE) 8: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f346680d620]
(EE) 9: /usr/bin/X (_start+0x29) [0x426639]
(EE)
(EE) Segmentation fault at address 0xa0
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting


  Any ideas?   I can't figure out why kernel modesetting isn't working
(the newer versions of Linux don't have explicit modesetting config
items
and the framebuffer drivers are totally disabled, as per the install
docs),
but the larger problem is that segfault.   Any ideas on how to even
start
to address this?

  -David


Few extra missing details.

Which GPU are you using? I see both Intel and ATI.
Can you provide your kernel config.
Which Video drivers did you build with xorg?



lspci and 'lspci -v' among other hardware discovery tools might help you
get the firmware and exact kernel options needed for your kernel
built correctly.

I always put the video codes into the kernel, but some have success with
setting up those codes, via a loadable modules.

other tools:: 'lshw'

hth,
James

Re: [gentoo-user] Can't create valid btrfs on NVMe

[james]

On 08/18/2016 05:06 AM, Peter Humphrey wrote:

On Thursday 18 Aug 2016 15:56:50 Adam Carter wrote:

On Thu, Aug 18, 2016 at 8:26 AM, Neil Bothwick  wrote:

I'm putting together a new desktop using a Samsung SM951 NVMe drive. I
booted sysrescd, partitioned the drive and ran

mkfs.btrfs /dev/nvme0n1p3
mount /dev/nvme0n1p3 /mnt/custom

df -T, mount and findmnt all show this is mounted as a btrfs filesystem,
e.g.

/dev/nvme0n1p3 on /mnt/custom type btrfs (rw,relatime,ssd,space_cache)

I can create files in here but cannot do anything btrfs-y

% btrfs filesystem show /mnt/custom
ERROR: not a valid btrfs filesystem: /mnt/custom

% btrfs subvolume create /mnt/custom/test
Create subvolume '/mnt/custom/test'
ERROR: cannot create subvolume: Inappropriate ioctl for device

Google has been no help at all.


I'm assuming tools are expecting SATA (or SCSI) and need an update or
alternative for nvm;

# hdparm -i /dev/nvme0n1

/dev/nvme0n1:
 HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device
 HDIO_GET_IDENTITY failed: Inappropriate ioctl for device

Maybe SCSI emulation could work around it?
CONFIG_BLK_DEV_NVME_SCSI


I don't have Neil's e-mail here - another KMail problem?

Neil, have you tried inspecting your drive with sys-apps/nvme-cli? I don't
have any experience to relate as I haven't worked out how to use it yet, but
it may help you.





Did you see the doc::
NVMeSSD_User_Installation_Guide_whitepaper-0.pdf

That's some fancy piece of hardware, that says it requires special drivers::

Chipset Intel 5520 or later generation chipset
Slots
• Require PCIe Gen3 x4 link width slot (For Max Performance)
• Support PCIe Gen1/Gen2 slot


The following operating systems are supported, with some requiring 
additional drivers:

• Windows Server® 2008R2 (64bit)
• Windows Server 2012/2012 R2 (64bit)
• Windows 7, 8, 8.1 (32/64bit)
• Red Hat® Enterprise Linux (RHEL) 7.0 (64bit)
• Red Hat Enterprise Linux (RHEL) 6.4/6.5 (64bit)
• SUSE® Linux Enterprise (SLES) 11SP3 (64bit)
• Ubuntu® 12.04.02 LTS Server (64bit)
• Ubuntu® 12.04.04 LTS Server (64bit)
• Solaris 11 SP2 (64bit)


Installing the Driver on a Linux System
RHEL 6.4 / 6.5 64bit
1. Turn the power on and log on to the system with the admin account.
2. Copy the driver file package to the installation folder.
3. Install the rpm with the command below. After installing, the NVMe 
driver will automatically load when the system is booted.

# rpm --ivh nvme-kmp-default-1.17_3.0.76_0.11-0.x86.64.rpm
(The file name could change depending on the driver version.)
4. To upgrade from v1.9, execute the following command:
# rpm --Uvh nvme-kmp-default-1.17_3.0.76_0.11-0.x86.64.rpm
5. To uninstall the package, execute the following command:
# rpm --e nvme-kmp-default-1.17_3.0.76_0.11-0.x86.64.rpm


Verifying the Installation of the software package in the Linux System
1. Turn the system power on, and then start the terminal window.
2. Run “Modinfo mtip32xx.” If the NVMe driver has been installed 
successfully, the version and module information are shown.
3. Run “fdisk –l | grep rssd*”; the NVMe SSD is shown as 
“/dev/rssddrive”.

Starting Re-Drive and Checking the NVMe SSD State
1. Click the “Identify” tab and Name Space Button.
2. The NVMe SSD information is displayed.

Using the NVMe SSD as a boot Drive (etc etc etc)

You might have to go digging around the kernel modules to find drivers, 
specs and such...



good_hunting::hth,
James

Re: [gentoo-user] Can't create valid btrfs on NVMe

[Peter Humphrey]

On Thursday 18 Aug 2016 15:56:50 Adam Carter wrote:
> On Thu, Aug 18, 2016 at 8:26 AM, Neil Bothwick  wrote:
> > I'm putting together a new desktop using a Samsung SM951 NVMe drive. I
> > booted sysrescd, partitioned the drive and ran
> > 
> > mkfs.btrfs /dev/nvme0n1p3
> > mount /dev/nvme0n1p3 /mnt/custom
> > 
> > df -T, mount and findmnt all show this is mounted as a btrfs filesystem,
> > e.g.
> > 
> > /dev/nvme0n1p3 on /mnt/custom type btrfs (rw,relatime,ssd,space_cache)
> > 
> > I can create files in here but cannot do anything btrfs-y
> > 
> > % btrfs filesystem show /mnt/custom
> > ERROR: not a valid btrfs filesystem: /mnt/custom
> > 
> > % btrfs subvolume create /mnt/custom/test
> > Create subvolume '/mnt/custom/test'
> > ERROR: cannot create subvolume: Inappropriate ioctl for device
> > 
> > Google has been no help at all.
> 
> I'm assuming tools are expecting SATA (or SCSI) and need an update or
> alternative for nvm;
> 
> # hdparm -i /dev/nvme0n1
> 
> /dev/nvme0n1:
>  HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device
>  HDIO_GET_IDENTITY failed: Inappropriate ioctl for device
> 
> Maybe SCSI emulation could work around it?
> CONFIG_BLK_DEV_NVME_SCSI

I don't have Neil's e-mail here - another KMail problem?

Neil, have you tried inspecting your drive with sys-apps/nvme-cli? I don't 
have any experience to relate as I haven't worked out how to use it yet, but 
it may help you.

-- 
Rgds
Peter

Re: [gentoo-user] 2000 emails - printing, sorting by date

[Stroller]

> On 18 Aug 2016, at 08:16, Håkon Alstadheim  wrote:
> 
> Have you looked at app-misc/muttprint ? Never tried it, but looks to fit
> the bill. You will need various command-line tools that mutt-print will
> use to parse mails and generate graphics.

Ah! Many thanks. That's exactly the sort of thing I had in mind. I'll have a 
look at installing it now.

Stroller.

Re: [gentoo-user] 2000 emails - printing, sorting by date

[Håkon Alstadheim]

Den 18. aug. 2016 08:39, skrev Stroller:
>
>> On 17 Aug 2016, at 15:12, Daniel Quinn > > wrote:
>>
>> I’m a Python guy, so my answer to this would be "use Python" :-)
>>
>> [The ReportLab
>> library](https://www.reportlab.com/docs/reportlab-userguide.pdf) is
>> extremely powerful and can be used to generate a PDF for every email
>> or a pdf for all emails.  I've not used it myself, but I hear it's
>> very good.
>>
>> … 
>>
>> At that point you have a sorted list of email objects which you can
>> then use ReportLab to generate a PDF.
>
>
> That's a little more complicated than I hoped for.
>
Have you looked at app-misc/muttprint ? Never tried it, but looks to fit
the bill. You will need various command-line tools that mutt-print will
use to parse mails and generate graphics.

Re: [gentoo-user] 2000 emails - printing, sorting by date

[Stroller]

> On 17 Aug 2016, at 15:12, Daniel Quinn  wrote:
> 
> I’m a Python guy, so my answer to this would be "use Python" :-)
> 
> [The ReportLab 
> library](https://www.reportlab.com/docs/reportlab-userguide.pdf 
> ) is extremely 
> powerful and can be used to generate a PDF for every email or a pdf for all 
> emails.  I've not used it myself, but I hear it's very good.
> 
> … 
> 
> At that point you have a sorted list of email objects which you can then use 
> ReportLab to generate a PDF.


That's a little more complicated than I hoped for.

I've not used Python before. Although I'd not be opposed to learning it, it's 
not clear to me how I'd get ReportLab to generate a PDF from an email. 

I was not expecting to involve myself with decisions about fonts and heading 
sizes. I thought, perhaps optimistically, that there must be a command-line 
program to take a text email file and (discarding the unneeded headers) print 
it (to `lpr` or a postscript file) in formatting like the attached, just like 
my desktop email client does.

It surprises me to think that pretty-printing an email from the command-line is 
something that's not been done before, but my searches are not finding relevant 
results.

Stroller.

Re: [gentoo-user] XOrg / XRanR segfault starting X

[J. Roeleveld]

On August 18, 2016 6:59:53 AM GMT+02:00, Dave Trombley 
 wrote:
>Hi all!
>
>New to Gentoo, just followed the handbook install for amd64 and then
>for
>XOrg.
>
>I'm seeing the server segfault on 'startx'.   Here is the console
>output (and I've attached the logfile).
>
>X.Org X Server 1.17.4
>Release Date: 2015-10-28
>X Protocol Version 11, Revision 0
>Build Operating System: Linux 4.4.6-gentoo x86_64 Gentoo
>Current Operating System: Linux snow 4.4.6-gentoo #3 SMP PREEMPT Thu
>Aug 18
>04:18:24 Local time zone must be set-- x86_64
>Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.6-gentoo
>root=UUID=8cb564c3-38fb-4b05-bc60-eaccf543e3ab ro
>Build Date: 17 August 2016  07:13:48PM
>
>Current version of pixman: 0.32.8
>Before reporting problems, check http://wiki.x.org
>to make sure that you have the latest version.
>Markers: (--) probed, (**) from config file, (==) default setting,
>(++) from command line, (!!) notice, (II) informational,
>(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>(==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 18 04:53:29 2016
>(==) Using system config directory "/usr/share/X11/xorg.conf.d"
>(II) [KMS] drm report modesetting isn't supported.
>(EE)
>(EE) Backtrace:
>(EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x58c856]
>(EE) 1: /usr/bin/X (0x40+0x190b09) [0x590b09]
>(EE) 2: /lib64/libc.so.6 (0x7f34667ed000+0x33370) [0x7f3466820370]
>(EE) 3: /usr/bin/X (RRSetChanged+0x50) [0x4f0c50]
>(EE) 4: /usr/bin/X (RRScreenSetSizeRange+0x54) [0x4f5184]
>(EE) 5: /usr/bin/X (xf86RandR12CreateScreenResources+0x295) [0x4b7d65]
>(EE) 6: /usr/bin/X (0x40+0xab130) [0x4ab130]
>(EE) 7: /usr/bin/X (0x40+0x3bff4) [0x43bff4]
>(EE) 8: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f346680d620]
>(EE) 9: /usr/bin/X (_start+0x29) [0x426639]
>(EE)
>(EE) Segmentation fault at address 0xa0
>(EE)
>Fatal server error:
>(EE) Caught signal 11 (Segmentation fault). Server aborting
>
>
>   Any ideas?   I can't figure out why kernel modesetting isn't working
>(the newer versions of Linux don't have explicit modesetting config
>items
>and the framebuffer drivers are totally disabled, as per the install
>docs),
>but the larger problem is that segfault.   Any ideas on how to even
>start
>to address this?
>
>   -David

Few extra missing details.

Which GPU are you using? I see both Intel and ATI.
Can you provide your kernel config.
Which Video drivers did you build with xorg?

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] XOrg / XRanR segfault starting X

[Adam Carter]

On Thu, Aug 18, 2016 at 2:59 PM, Dave Trombley 
wrote:

> Hi all!
>
>New to Gentoo, just followed the handbook install for amd64 and then
> for XOrg.
>
> I'm seeing the server segfault on 'startx'.   Here is the console
> output (and I've attached the logfile).
>
> X.Org X Server 1.17.4
> Release Date: 2015-10-28
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 4.4.6-gentoo x86_64 Gentoo
> Current Operating System: Linux snow 4.4.6-gentoo #3 SMP PREEMPT Thu Aug
> 18 04:18:24 Local time zone must be set-- x86_64
> Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.6-gentoo
> root=UUID=8cb564c3-38fb-4b05-bc60-eaccf543e3ab ro
> Build Date: 17 August 2016  07:13:48PM
>
> Current version of pixman: 0.32.8
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 18 04:53:29 2016
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> (II) [KMS] drm report modesetting isn't supported.
> (EE)
> (EE) Backtrace:
> (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x58c856]
> (EE) 1: /usr/bin/X (0x40+0x190b09) [0x590b09]
> (EE) 2: /lib64/libc.so.6 (0x7f34667ed000+0x33370) [0x7f3466820370]
> (EE) 3: /usr/bin/X (RRSetChanged+0x50) [0x4f0c50]
> (EE) 4: /usr/bin/X (RRScreenSetSizeRange+0x54) [0x4f5184]
> (EE) 5: /usr/bin/X (xf86RandR12CreateScreenResources+0x295) [0x4b7d65]
> (EE) 6: /usr/bin/X (0x40+0xab130) [0x4ab130]
> (EE) 7: /usr/bin/X (0x40+0x3bff4) [0x43bff4]
> (EE) 8: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f346680d620]
> (EE) 9: /usr/bin/X (_start+0x29) [0x426639]
> (EE)
> (EE) Segmentation fault at address 0xa0
> (EE)
> Fatal server error:
> (EE) Caught signal 11 (Segmentation fault). Server aborting
>

My log has;
# grep -i kms /var/log/Xorg.0.log
[   303.319] (II) [KMS] Kernel modesetting enabled.
[   303.393] (II) AMDGPU(0): KMS Pageflipping: enabled

# zgrep -i kms /proc/config.gz
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_KMS_FB_HELPER=y

So try enabling those and rebuild and reinstall your kernel.

Other than that, when you update xorg you also need to 'emerge
@x11-module-rebuild' afterwards, but unless you've been emerging things out
of order that's probably not this issue this time. If you're not sure, just
do it anyway if its still broken after the kernel update.

I have had a single instance where I needed to rebuild xorg due to suit a
new kernel, but that was a long time ago.