On Wed, 2014-06-25 at 16:16 -0500, Bruno Wolff III wrote:
> On Wed, Jun 25, 2014 at 14:10:31 -0700,
> Adam Williamson wrote:
> >On Wed, 2014-06-25 at 15:09 -0500, Bruno Wolff III wrote:
> >> On Wed, Jun 25, 2014 at 12:56:41 -0700,
> >> Adam Williamson wrote:
> >> >
> >> >http://koji.fedorapro
On 2014-06-25 16:50 (GMT-0400) Felix Miata composed:
On 2014-06-25 12:53 (GMT-0700) Adam Williamson composed:
Good spot - that may very well be your issue, yeah, since you're using a
CRT display. It would also explain why I can't reproduce the bug on my
Intel graphics system, which is a lapto
On Wed, Jun 25, 2014 at 14:10:31 -0700,
Adam Williamson wrote:
On Wed, 2014-06-25 at 15:09 -0500, Bruno Wolff III wrote:
On Wed, Jun 25, 2014 at 12:56:41 -0700,
Adam Williamson wrote:
>
>http://koji.fedoraproject.org/koji/taskinfo?taskID=7076318
>
>assuming it builds successfully (AdamW Pat
On Wed, 2014-06-25 at 15:09 -0500, Bruno Wolff III wrote:
> On Wed, Jun 25, 2014 at 12:56:41 -0700,
> Adam Williamson wrote:
> >
> >http://koji.fedoraproject.org/koji/taskinfo?taskID=7076318
> >
> >assuming it builds successfully (AdamW Patching C: Take Cover!), if you
> >could test with that it
On 2014-06-25 12:53 (GMT-0700) Adam Williamson composed:
Good spot - that may very well be your issue, yeah, since you're using a
CRT display. It would also explain why I can't reproduce the bug on my
Intel graphics system, which is a laptop.
The i915G at least also puts to sleep my 1440x900 L
On Wed, Jun 25, 2014 at 12:56:41 -0700,
Adam Williamson wrote:
http://koji.fedoraproject.org/koji/taskinfo?taskID=7076318
assuming it builds successfully (AdamW Patching C: Take Cover!), if you
could test with that it'd be good.
I'm installing it now. Should be about 30 minutes before I get
On Tue, 2014-06-24 at 22:50 -0500, Bruno Wolff III wrote:
> On Tue, Jun 24, 2014 at 19:22:05 -0700,
> Adam Williamson wrote:
> >
> >The most obvious thing is whether you have a SXXservice symlink
> >in /etc/rc*.d; that constitutes the service being 'enabled' so far as
> >SysV is concerned, and s
On Wed, 2014-06-25 at 14:59 -0400, Felix Miata wrote:
> On 2014-06-25 10:08 (GMT-0700) Adam Williamson composed:
>
> > On Wed, 2014-06-25 at 10:05 -0700, Adam Williamson wrote:
>
> >> I'm curious: why are you passing video= parameters on each one? Do
> >> any/all of them work if you don't pass th
On 2014-06-25 10:08 (GMT-0700) Adam Williamson composed:
On Wed, 2014-06-25 at 10:05 -0700, Adam Williamson wrote:
I'm curious: why are you passing video= parameters on each one? Do
any/all of them work if you don't pass that parameter?
...and does it work if you append an 'e':
video=10
On 25.06.2014 20:10, Felix Miata wrote:
On 2014-06-25 10:05 (GMT-0700) Adam Williamson composed:
So...these are three different machines?
3 out of 14 on which Rawhide is currently installed (test machines total 20+)
here, among which are represented various flavors of MGA (400 & 550), SiS
(Z7
On 25.06.2014 20:09, Adam Williamson wrote:
On Wed, 2014-06-25 at 19:58 +0200, poma wrote:
On 25.06.2014 19:08, Adam Williamson wrote:
On Wed, 2014-06-25 at 10:05 -0700, Adam Williamson wrote:
On Wed, 2014-06-25 at 12:02 -0400, Felix Miata wrote:
On 2014-06-25 08:12 (GMT-0700) Adam Williamson
On Wed, 2014-06-25 at 14:10 -0400, Felix Miata wrote:
> On 2014-06-25 10:05 (GMT-0700) Adam Williamson composed:
>
> > So...these are three different machines?
>
> 3 out of 14 on which Rawhide is currently installed (test machines total 20+)
> here, among which are represented various flavors of
On 2014-06-25 10:05 (GMT-0700) Adam Williamson composed:
So...these are three different machines?
3 out of 14 on which Rawhide is currently installed (test machines total 20+)
here, among which are represented various flavors of MGA (400 & 550), SiS
(Z7/Z9 XG20 core), Intel (810, 815, 845, 8
On Wed, 2014-06-25 at 19:58 +0200, poma wrote:
> On 25.06.2014 19:08, Adam Williamson wrote:
> > On Wed, 2014-06-25 at 10:05 -0700, Adam Williamson wrote:
> >> On Wed, 2014-06-25 at 12:02 -0400, Felix Miata wrote:
> >>> On 2014-06-25 08:12 (GMT-0700) Adam Williamson composed:
> >>>
> > Where di
On 25.06.2014 19:08, Adam Williamson wrote:
On Wed, 2014-06-25 at 10:05 -0700, Adam Williamson wrote:
On Wed, 2014-06-25 at 12:02 -0400, Felix Miata wrote:
On 2014-06-25 08:12 (GMT-0700) Adam Williamson composed:
Where did you see "X initialization fails"? I've been booting with 3 on
cmdline.
On Wed, 2014-06-25 at 10:05 -0700, Adam Williamson wrote:
> On Wed, 2014-06-25 at 12:02 -0400, Felix Miata wrote:
> > On 2014-06-25 08:12 (GMT-0700) Adam Williamson composed:
> >
> > >> Where did you see "X initialization fails"? I've been booting with 3 on
> > >> cmdline. Anyway, here's 2 of 3 dr
On Wed, 2014-06-25 at 12:02 -0400, Felix Miata wrote:
> On 2014-06-25 08:12 (GMT-0700) Adam Williamson composed:
>
> >> Where did you see "X initialization fails"? I've been booting with 3 on
> >> cmdline. Anyway, here's 2 of 3 drm.debug=15 dmesgs captured:
>
> >> http://fm.no-ip.com/Tmp/Linux/F/
On 2014-06-25 08:12 (GMT-0700) Adam Williamson composed:
Where did you see "X initialization fails"? I've been booting with 3 on
cmdline. Anyway, here's 2 of 3 drm.debug=15 dmesgs captured:
http://fm.no-ip.com/Tmp/Linux/F/dmsgI865Gf21k316rc2g01.txt
On Wed, Jun 25, 2014 at 11:12 PM, Adam Williamson wrote:
>> http://fm.no-ip.com/Tmp/Linux/F/dmsgI945Gf21k316rc2g01.txt
>
> What is this from? Thanks.
I think it's from dmesg.
Yours sincerely,
Christopher Meng
Noob here.
http://cicku.me
--
test mailing list
test@lists.fedoraproject.org
To unsu
On Wed, 2014-06-25 at 09:06 -0400, Felix Miata wrote:
> On 2014-06-24 23:34 (GMT-0700) Adam Williamson composed:
>
> >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1104371
> ...
> >> Are you sure what I described in that bug is different?
> >
> > Well, it's impossible to be *sure* unless you pr
On 24.06.2014 21:56, Felix Miata wrote:
On 2014-06-23 17:07 (GMT-0400) Felix Miata composed:
On 2014-06-23 11:34 (GMT-0700) Adam Williamson composed:
All 3.16 kernels before 3.16.0-0.rc2.git0.1 are just fundamentally
broken on i686, I think, unless you pass 'vdso=0'. I wouldn't bother
messin
On 2014-06-24 23:34 (GMT-0700) Adam Williamson composed:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1104371
...
Are you sure what I described in that bug is different?
Well, it's impossible to be *sure* unless you provide the necessary
logs, as I mentioned above.
No-one can pretend to
On Wed, Jun 25, 2014 at 3:24 AM, Adam Williamson wrote:
> On Tue, 2014-06-24 at 19:48 -0500, Bruno Wolff III wrote:
>> On Mon, Jun 23, 2014 at 13:52:10 -0500,
>> Bruno Wolff III wrote:
>> >On Mon, Jun 23, 2014 at 11:34:53 -0700,
>> > Adam Williamson wrote:
>> >>
>> >>All 3.16 kernels before 3.
On Tue, Jun 24, 2014 at 04:30:59PM -0700, Adam Williamson wrote:
>
> I think the "Could not find init script" errors are probably due to this
> 'dangling symlink' problem, and the fact that .service files are being
> generated is intentional - just the way systemd is handling remaining
> sysv serv
On Tue, 2014-06-24 at 23:54 -0400, Felix Miata wrote:
> On 2014-06-24 15:13 (GMT-0700) Adam Williamson composed:
>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1104371
>
> > Well, I wouldn't say scolded. Hans just asked you politely to file a new
> > bug, since you have clearly different hard
On 2014-06-24 15:13 (GMT-0700) Adam Williamson composed:
https://bugzilla.redhat.com/show_bug.cgi?id=1104371
Well, I wouldn't say scolded. Hans just asked you politely to file a new
bug, since you have clearly different hardware. The Intel i8xx adapters
are notoriously tricky hardware, and qu
On Tue, Jun 24, 2014 at 19:22:05 -0700,
Adam Williamson wrote:
The most obvious thing is whether you have a SXXservice symlink
in /etc/rc*.d; that constitutes the service being 'enabled' so far as
SysV is concerned, and so in that case it seems correct for systemd to
enable the runtime-generat
On Tue, 2014-06-24 at 19:48 -0500, Bruno Wolff III wrote:
> On Mon, Jun 23, 2014 at 13:52:10 -0500,
> Bruno Wolff III wrote:
> >On Mon, Jun 23, 2014 at 11:34:53 -0700,
> > Adam Williamson wrote:
> >>
> >>All 3.16 kernels before 3.16.0-0.rc2.git0.1 are just fundamentally
> >>broken on i686, I th
On Tue, 2014-06-24 at 19:45 -0500, Bruno Wolff III wrote:
> On Tue, Jun 24, 2014 at 16:30:59 -0700,
> Adam Williamson wrote:
> >
> >I think the "Could not find init script" errors are probably due to this
> >'dangling symlink' problem, and the fact that .service files are being
> >generated is i
On Mon, Jun 23, 2014 at 13:52:10 -0500,
Bruno Wolff III wrote:
On Mon, Jun 23, 2014 at 11:34:53 -0700,
Adam Williamson wrote:
All 3.16 kernels before 3.16.0-0.rc2.git0.1 are just fundamentally
broken on i686, I think, unless you pass 'vdso=0'. I wouldn't bother
messing with anything unless y
On Tue, Jun 24, 2014 at 16:30:59 -0700,
Adam Williamson wrote:
I think the "Could not find init script" errors are probably due to this
'dangling symlink' problem, and the fact that .service files are being
generated is intentional - just the way systemd is handling remaining
sysv services - a
On Tue, 2014-06-24 at 19:52 -0400, Felix Miata wrote:
> On 2014-06-24 16:35 (GMT-0700) Adam Williamson composed:
>
> > I'm using Firefox. The version field is a bit further down the form than
> > you might be looking, perhaps?
>
> That's it, a list made obtuse by so many things in between out of
On 2014-06-24 16:35 (GMT-0700) Adam Williamson composed:
I'm using Firefox. The version field is a bit further down the form than
you might be looking, perhaps?
That's it, a list made obtuse by so many things in between out of logical
order, and populated by a big bunch of lines with single d
On Tue, 2014-06-24 at 19:33 -0400, Felix Miata wrote:
> On 2014-06-24 16:12 (GMT-0700) Adam Williamson composed:
>
> >> I've been avoiding that lately because I search for an existing bug first,
> >> and someone's wisdom has seen fit to make that unduly difficult by
> >> excluding
> >> any option
On 2014-06-24 16:12 (GMT-0700) Adam Williamson composed:
I've been avoiding that lately because I search for an existing bug first,
and someone's wisdom has seen fit to make that unduly difficult by excluding
any option in the product list to select a particular release or Rawhide
rather than si
On Tue, 2014-06-24 at 16:13 -0700, Adam Williamson wrote:
> On Wed, 2014-06-25 at 00:11 +0100, Peter Robinson wrote:
> > >> >BTW, Adam, there are people running & testing Rawhide on i686! :)
> > >>
> > >> Yes, and I am backlogged getting bugs filed for issues I am having.
> > >> I have at least two
On Wed, 2014-06-25 at 00:11 +0100, Peter Robinson wrote:
> >> >BTW, Adam, there are people running & testing Rawhide on i686! :)
> >>
> >> Yes, and I am backlogged getting bugs filed for issues I am having.
> >> I have at least two different problems with 3.16 kernels that make them
> >> unusable f
On Tue, 2014-06-24 at 19:01 -0400, Felix Miata wrote:
> On 2014-06-24 15:13 (GMT-0700) Adam Williamson composed:
>
> > Hans just asked you politely to file a new bug
>
> I've been avoiding that lately because I search for an existing bug first,
> and someone's wisdom has seen fit to make that un
>> >BTW, Adam, there are people running & testing Rawhide on i686! :)
>>
>> Yes, and I am backlogged getting bugs filed for issues I am having.
>> I have at least two different problems with 3.16 kernels that make them
>> unusable for me.
>>
>> There might be a problem with systemd creating init fi
On 2014-06-24 15:13 (GMT-0700) Adam Williamson composed:
Hans just asked you politely to file a new bug
I've been avoiding that lately because I search for an existing bug first,
and someone's wisdom has seen fit to make that unduly difficult by excluding
any option in the product list to se
On Mon, 2014-06-23 at 17:07 -0400, Felix Miata wrote:
> On 2014-06-23 11:34 (GMT-0700) Adam Williamson composed:
>
> > All 3.16 kernels before 3.16.0-0.rc2.git0.1 are just fundamentally
> > broken on i686, I think, unless you pass 'vdso=0'. I wouldn't bother
> > messing with anything unless you're
On 2014-06-23 17:07 (GMT-0400) Felix Miata composed:
On 2014-06-23 11:34 (GMT-0700) Adam Williamson composed:
All 3.16 kernels before 3.16.0-0.rc2.git0.1 are just fundamentally
broken on i686, I think, unless you pass 'vdso=0'. I wouldn't bother
messing with anything unless you're using the r
On 2014-06-23 11:34 (GMT-0700) Adam Williamson composed:
All 3.16 kernels before 3.16.0-0.rc2.git0.1 are just fundamentally
broken on i686, I think, unless you pass 'vdso=0'. I wouldn't bother
messing with anything unless you're using the rc2 kernel, or passing
vdso=0.
That doesn't help here:
On 23.06.2014 20:44, Bruno Wolff III wrote:
On Mon, Jun 23, 2014 at 20:10:32 +0200,
poma wrote:
You're talking about systemd-214-3.fc21(2014-06-23), right?
systemd-214-2.fc21
I haven't tested systemd-214-3.fc21 yet to see if the problem is still there.
I'm spinning md1, what worries yo
On Mon, Jun 23, 2014 at 11:34:53 -0700,
Adam Williamson wrote:
systemd doesn't just 'create init files', I don't think. It *does* have
a concept of dependencies, which could account for this effect.
Something is creating ones during boot since about a month ago. They
are in a scratch locati
On Mon, Jun 23, 2014 at 20:10:32 +0200,
poma wrote:
You're talking about systemd-214-3.fc21(2014-06-23), right?
systemd-214-2.fc21
I haven't tested systemd-214-3.fc21 yet to see if the problem is still there.
I'm spinning md1, what worries you there?
https://bugzilla.redhat.com/show_bug
On Mon, 2014-06-23 at 12:36 -0500, Bruno Wolff III wrote:
> On Mon, Jun 23, 2014 at 19:13:36 +0200,
> poma wrote:
> >
> >BTW, Adam, there are people running & testing Rawhide on i686! :)
>
> Yes, and I am backlogged getting bugs filed for issues I am having.
> I have at least two different pro
On 06/23/2014 07:36 PM, Bruno Wolff III wrote:
On Mon, Jun 23, 2014 at 19:13:36 +0200,
poma wrote:
BTW, Adam, there are people running & testing Rawhide on i686! :)
Yes, and I am backlogged getting bugs filed for issues I am having.
I have at least two different problems with 3.16 kernels
On Mon, Jun 23, 2014 at 19:13:36 +0200,
poma wrote:
BTW, Adam, there are people running & testing Rawhide on i686! :)
Yes, and I am backlogged getting bugs filed for issues I am having.
I have at least two different problems with 3.16 kernels that make them
unusable for me.
There might b
On 06/23/2014 06:28 AM, Adam Williamson wrote:
On Mon, 2014-06-23 at 05:03 +0200, poma wrote:
Not only LightDM, but all tested display managers refuse to work.
There might be a general strike on i686 avenue. :)
Already reported, diagnosed and fixed upstream.
https://bugzilla.redhat.com/show_b
On Mon, 2014-06-23 at 05:03 +0200, poma wrote:
> Not only LightDM, but all tested display managers refuse to work.
> There might be a general strike on i686 avenue. :)
Already reported, diagnosed and fixed upstream.
https://bugzilla.redhat.com/show_bug.cgi?id=1110968 . I expect jwb will
backport
On 22.06.2014 04:34, poma wrote:
3.16.0-0.rc1.git4.1.fc21.i686 #1 Not tainted
LightDM, SDDM, GDM are failing.
Interestingly, there are no errors in Xorg.0.log,
(II) NOUVEAU(0): Output DVI-I-1 connected
startx works for user and startxfce4 for root. :)
journal:
systemd[1]: Starting Light Displa
52 matches
Mail list logo
