On Sat, Oct 05, 2019 at 04:38:23AM +0100, Ken Moffat via blfs-dev wrote:
> On Fri, Oct 04, 2019 at 01:51:15AM +0100, Ken Moffat via blfs-dev wrote:
> >
> > > The hack is actually for Xorg's own modesetting driver, but if it
> > > also fixes things for ati/amdgpu then all will be good.
> > >
> >
On Fri, Oct 04, 2019 at 01:51:15AM +0100, Ken Moffat via blfs-dev wrote:
>
> > The hack is actually for Xorg's own modesetting driver, but if it
> > also fixes things for ati/amdgpu then all will be good.
> >
>
> I'm attaching a headed version of the patch: AFAICS it is less
> dangerous than th
On Thu, Oct 03, 2019 at 08:35:37PM +0100, Ken Moffat via blfs-dev wrote:
> On Wed, Oct 02, 2019 at 09:53:21PM -0500, Douglas R. Reno wrote:
> >
> > https://ch1p.io/blog/1/ (WARNING: The Security Certificate expired on 10/1.
> > The site and the links within (attached) are safe.)
> > https://stacko
On Thu, Oct 03, 2019 at 08:30:38PM +0100, Ken Moffat via blfs-dev wrote:
> On Thu, Oct 03, 2019 at 09:17:03AM +0200, Pierre Labastie via blfs-dev wrote:
> > On 03/10/2019 02:48, Ken Moffat via blfs-dev wrote:
> > > [...]
> > >
> > > Thanks, I'm inclined to bellieve that I'm barking up the wrong tr
On Thu, Oct 03, 2019 at 09:17:03AM +0200, Pierre Labastie via blfs-dev wrote:
> On 03/10/2019 02:48, Ken Moffat via blfs-dev wrote:
> > [...]
> >
> > Thanks, I'm inclined to bellieve that I'm barking up the wrong tree.
> >
> > My current xorg-server build configures and runs make as user lfs,
> >
On Wed, Oct 02, 2019 at 09:53:21PM -0500, Douglas R. Reno wrote:
>
> Good evening folks
>
> I found the following things out while looking online for solutions to this
> problem earlier. It seems to be due to the way that permissions are handled
> on card0, since AMDGPU/ATI drivers need access to
On 03/10/2019 02:48, Ken Moffat via blfs-dev wrote:
> [...]
>
> Thanks, I'm inclined to bellieve that I'm barking up the wrong tree.
>
> My current xorg-server build configures and runs make as user lfs,
> because I eventually discovered that my normal build-as-root was
> forcing suid install. S
On 2019-10-02 18:49, Ken Moffat via blfs-dev wrote:
On Wed, Oct 02, 2019 at 05:40:28PM -0500, Bruce Dubbs via blfs-dev
wrote:
On 10/2/19 3:41 PM, Ken Moffat via blfs-dev wrote:
> On Tue, Oct 01, 2019 at 10:25:58PM -0500, Bruce Dubbs via blfs-dev wrote:
> > On 10/1/19 9:23 PM, Ken Moffat via blfs
On Wed, Oct 02, 2019 at 11:28:10PM +, DJ Lucas via blfs-dev wrote:
> On October 2, 2019 3:41:05 PM CDT, Ken Moffat via blfs-dev
> wrote:
>
(snipping most)
> >[37.282] (--) AMDGPU(0): Chipset: "Unknown AMD Radeon GPU" (ChipID
> >= 0x15d8)
>
>
> Is this an add-on card, or Mobo? Searching
On Wed, Oct 02, 2019 at 05:40:28PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 10/2/19 3:41 PM, Ken Moffat via blfs-dev wrote:
> > On Tue, Oct 01, 2019 at 10:25:58PM -0500, Bruce Dubbs via blfs-dev wrote:
> > > On 10/1/19 9:23 PM, Ken Moffat via blfs-dev wrote:
> > > > On Wed, Sep 25, 2019 at 02:05
On October 2, 2019 3:41:05 PM CDT, Ken Moffat via blfs-dev
wrote:
>
>[37.281] (II) AMDGPU: Driver for AMD Radeon:
>All GPUs supported by the amdgpu kernel driver
>[37.281] (II) modesetting: Driver for Modesetting Kernel Drivers:
>kms
>[37.281] (++) using VT number 1
>
>[3
On 10/2/19 3:41 PM, Ken Moffat via blfs-dev wrote:
On Tue, Oct 01, 2019 at 10:25:58PM -0500, Bruce Dubbs via blfs-dev wrote:
On 10/1/19 9:23 PM, Ken Moffat via blfs-dev wrote:
On Wed, Sep 25, 2019 at 02:05:57PM -0500, Bruce Dubbs via blfs-dev wrote:
On 9/25/19 12:07 PM, Ken Moffat via blfs-dev
On Tue, Oct 01, 2019 at 10:25:58PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 10/1/19 9:23 PM, Ken Moffat via blfs-dev wrote:
> > On Wed, Sep 25, 2019 at 02:05:57PM -0500, Bruce Dubbs via blfs-dev wrote:
> > > On 9/25/19 12:07 PM, Ken Moffat via blfs-dev wrote:
> > > >
> > >
> > > For comparison
On 10/1/19 9:23 PM, Ken Moffat via blfs-dev wrote:
On Wed, Sep 25, 2019 at 02:05:57PM -0500, Bruce Dubbs via blfs-dev wrote:
On 9/25/19 12:07 PM, Ken Moffat via blfs-dev wrote:
For comparison, attached are two elogind builds. The 90 build is a direct
xorg build and completes xorg at about l
On Wed, Oct 02, 2019 at 03:23:54AM +0100, Ken Moffat wrote:
(second attempt, hopefully this time with the attachment)
> On Wed, Sep 25, 2019 at 02:05:57PM -0500, Bruce Dubbs via blfs-dev wrote:
> > On 9/25/19 12:07 PM, Ken Moffat via blfs-dev wrote:
> > >
> >
> > For comparison, attached are tw
On Wed, Sep 25, 2019 at 02:05:57PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 9/25/19 12:07 PM, Ken Moffat via blfs-dev wrote:
> >
>
> For comparison, attached are two elogind builds. The 90 build is a direct
> xorg build and completes xorg at about line 88. The 9a build followed a
> jhalfs g
On Wed, Sep 25, 2019 at 06:07:48PM +0100, Ken Moffat via blfs-dev wrote:
>
> I think the elogind circular dependency might be what matters most
As Bruce surmised, it made no difference. I completed the build,
then rebooted to ensure that elogind would definitely come up.
The initial confirmatio
On Wed, Sep 25, 2019 at 06:07:48PM +0100, Ken Moffat via blfs-dev wrote:
> On Mon, Sep 23, 2019 at 11:23:35AM -0500, Douglas R. Reno via blfs-dev wrote:
> > Hi folks,
> >
> >
> > Around 5 minutes ago, I finished installing X on my elogind system. I
> > started late last night. I just started X an
On 9/25/19 12:07 PM, Ken Moffat via blfs-dev wrote:
On Mon, Sep 23, 2019 at 11:23:35AM -0500, Douglas R. Reno via blfs-dev wrote:
Hi folks,
Around 5 minutes ago, I finished installing X on my elogind system. I
started late last night. I just started X and found that I do have a working
keyboa
On 9/25/19 12:07 PM, Ken Moffat via blfs-dev wrote:
On Mon, Sep 23, 2019 at 11:23:35AM -0500, Douglas R. Reno via blfs-dev wrote:
Hi folks,
Around 5 minutes ago, I finished installing X on my elogind system. I
started late last night. I just started X and found that I do have a working
keyboar
On Mon, Sep 23, 2019 at 11:23:35AM -0500, Douglas R. Reno via blfs-dev wrote:
> Hi folks,
>
>
> Around 5 minutes ago, I finished installing X on my elogind system. I
> started late last night. I just started X and found that I do have a working
> keyboard and mouse, and elogind-daemon
Hi people,
On Mon, Sep 23, 2019 at 12:56:28PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 9/23/19 12:21 PM, Ken Moffat via blfs-dev wrote:
> > On Mon, Sep 23, 2019 at 06:01:21PM +0100, Ken Moffat via blfs-dev wrote:
> > >
> > > For the moment I'll just repeat my earlier comment that on haswell
> > > with elo
On 9/23/19 12:21 PM, Ken Moffat via blfs-dev wrote:
On Mon, Sep 23, 2019 at 06:01:21PM +0100, Ken Moffat via blfs-dev wrote:
For the moment I'll just repeat my earlier comment that on haswell
with elogind graphics I got X but no perms on keyboard or mouse
^
|
On Mon, Sep 23, 2019 at 06:01:21PM +0100, Ken Moffat via blfs-dev wrote:
>
> For the moment I'll just repeat my earlier comment that on haswell
> with elogind graphics I got X but no perms on keyboard or mouse
^
|
and integrated
--
thread 'main' panicked at 'gir
On Mon, Sep 23, 2019 at 11:23:35AM -0500, Douglas R. Reno via blfs-dev wrote:
> Hi folks,
>
>
> Around 5 minutes ago, I finished installing X on my elogind system. I
> started late last night. I just started X and found that I do have a working
> keyboard and mouse, and elogind-daemon said the fo
Hi folks,
Around 5 minutes ago, I finished installing X on my elogind system. I
started late last night. I just started X and found that I do have a
working keyboard and mouse, and elogind-daemon said the following at the
console (copied out of /var/log/sys.log for ease of use):
Sep 23 11:0
26 matches
Mail list logo
