On 06/13/2011 04:33 PM, Daniel J Walsh wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/11/2011 03:11 PM, Lucas wrote:
On 06/11/2011 11:00 PM, Andre Robatino wrote:
Lucasmacachutoat gmail.com writes:
I use systemd-28-3.fc16.i686 and updated it when it became available,
but
Ok, it looks like I have managed to fix it.
I have blacklisted b43 and removed rpc and some other things.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Sat, Jun 11, 2011 at 01:27:44PM -0700, Garrett Holmstrom wrote:
On 2011-06-11 12:11, Lucas wrote:
Actually it does relabel by it self after boot with option selinux=0
That sounds rather useful. How does it know whether or not it was
previously booted with selinux=0?
booting with
On Fri, Jun 10, 2011 at 01:19:25PM -0500, Bruno Wolff III wrote:
The 3.0 kernels are not working for me. (A cpu lockup is reporting during
boot.) I am wondering if things are broken for everyone where I should
probably just wait for updates and try again, or if I should get a picture
of the
I can only boot if selinux is disabled - selinux=0 in grub. Otherwise boot
always stops in
different moments.
I can't figured out which problem is this - selinux or systemd?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Sat, Jun 11, 2011 at 9:29 AM, Lucas macach...@gmail.com wrote:
I can only boot if selinux is disabled - selinux=0 in grub. Otherwise boot
always stops in
different moments.
I can't figured out which problem is this - selinux or systemd?
--
Does this sound like it?
On 06/11/2011 08:35 PM, Tom London wrote:
On Sat, Jun 11, 2011 at 9:29 AM, Lucasmacach...@gmail.com wrote:
I can only boot if selinux is disabled - selinux=0 in grub. Otherwise boot
always stops in
different moments.
I can't figured out which problem is this - selinux or systemd?
--
On Sat, Jun 11, 2011 at 20:47:41 +0400,
Lucas macach...@gmail.com wrote:
I use systemd-28-3.fc16.i686 and updated it when it became available, but
still have real problems
with boot.
If it stops it happens definitely in systemd job - when it is starting
services.
And I can't find any
On 06/11/2011 08:42 PM, Bruno Wolff III wrote:
On Sat, Jun 11, 2011 at 20:47:41 +0400,
Lucasmacach...@gmail.com wrote:
I use systemd-28-3.fc16.i686 and updated it when it became available, but
still have real problems
with boot.
If it stops it happens definitely in systemd job - when
Lucas macachuto at gmail.com writes:
I use systemd-28-3.fc16.i686 and updated it when it became available,
but still have real problems
with boot.
If it stops it happens definitely in systemd job - when it is starting
services. And I can't find any errors.
More important that I have
On 06/11/2011 11:00 PM, Andre Robatino wrote:
Lucasmacachutoat gmail.com writes:
I use systemd-28-3.fc16.i686 and updated it when it became available,
but still have real problems
with boot.
If it stops it happens definitely in systemd job - when it is starting
services. And I can't find
On 2011-06-11 12:11, Lucas wrote:
Actually it does relabel by it self after boot with option selinux=0
That sounds rather useful. How does it know whether or not it was
previously booted with selinux=0?
--
devel mailing list
devel@lists.fedoraproject.org
The 3.0 kernels are not working for me. (A cpu lockup is reporting during
boot.) I am wondering if things are broken for everyone where I should
probably just wait for updates and try again, or if I should get a picture
of the traceback and file a bug?
--
devel mailing list
On Fri, Jun 10, 2011 at 11:19 AM, Bruno Wolff III br...@wolff.to wrote:
The 3.0 kernels are not working for me. (A cpu lockup is reporting during
boot.) I am wondering if things are broken for everyone where I should
probably just wait for updates and try again, or if I should get a picture
of
On Fri, Jun 10, 2011 at 12:19 PM, Bruno Wolff III br...@wolff.to wrote:
The 3.0 kernels are not working for me. (A cpu lockup is reporting during
boot.) I am wondering if things are broken for everyone where I should
probably just wait for updates and try again, or if I should get a picture
of
On Fri, Jun 10, 2011 at 11:54 AM, Jerry James loganje...@gmail.com wrote:
On Fri, Jun 10, 2011 at 12:19 PM, Bruno Wolff III br...@wolff.to wrote:
The 3.0 kernels are not working for me. (A cpu lockup is reporting during
boot.) I am wondering if things are broken for everyone where I should
On Fri, Jun 10, 2011 at 01:19:25PM -0500, Bruno Wolff III wrote:
The 3.0 kernels are not working for me. (A cpu lockup is reporting during
boot.) I am wondering if things are broken for everyone where I should
probably just wait for updates and try again, or if I should get a picture
of the
On Fri, Jun 10, 2011 at 15:09:02 -0400,
Clyde E. Kunkel clydekunkel7...@cox.net wrote:
Couldn't tell you about lockups since if root is on anything with raid
underlying, dracut drops to a shell. You are on the bz:
https://bugzilla.redhat.com/show_bug.cgi?id=710646
Hopefully, someone
On Fri, Jun 10, 2011 at 20:17:46 +0100,
Richard W.M. Jones rjo...@redhat.com wrote:
Works very well for me, but:
- Make sure you're running kernel-3.0-0.rc2.git0.2.fc16 with the
ftrace bug fixed (thanks Kyle).
Done.
- Make sure you upgrade module-init-tools *before* installing the 3.0
On Fri, 2011-06-10 at 15:06 -0500, Bruno Wolff III wrote:
On Fri, Jun 10, 2011 at 20:17:46 +0100,
Richard W.M. Jones rjo...@redhat.com wrote:
Works very well for me, but:
- Make sure you're running kernel-3.0-0.rc2.git0.2.fc16 with the
ftrace bug fixed (thanks Kyle).
Done.
-
It was for me until this morning. Virtual box killed it (beware of vb).
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
21 matches
Mail list logo
