On 10.07.2012 20:00, Joe Zeff wrote:
> On 07/10/2012 02:15 AM, Mateusz Marzantowicz wrote:
>> Thanks, a lot. But now one thing bothers me even more. Is it possible
>> that broken kernel which won't boot or cause any other serious problems
>> is released in Fedora 16 or 17? I know that in Rawhide something might
>> go wrong, but in 16, 17?
>
> My laptop is running F17 with a kernel from F14 because every F16
> kernel I've tried on it fails to boot with the exact same problem.
> Does that answer your question?

Sorry, but no. This only exposes serious problems with kernel quality in
Fedora. Personally I've never run in such problems and I hope I'll never
will. Regular Linux users should never be forced to deal with kernel
issues. I think it's RHEL policy, but not Fedora's for some reason.


Mateusz Marzantowicz
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 10.07.2012, Joe Zeff wrote:

> My laptop is running F17 with a kernel from F14 because every F16 kernel
> I've tried on it fails to boot with the exact same problem.

Do you have any information on this problem? What did you try to solve
it?

So far, I've never used any Fedora-kernel longer than for
installation, and have never encountered major problems with
linux-vanilla. Your problem could be hardware-dependend. Have you
tried a fresh 3.4.4 from kernel.org?


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 07/10/2012 11:43 AM, Heinz Diehl wrote:

Do you have any information on this problem? What did you try to solve
it?


See https://bugzilla.redhat.com/show_bug.cgi?id=769747 for details.
Note that I'm not the original reporter, and I seem to be the only one
who can't boot because of it. I reported this here when it first
struck, but nobody responded and you'd have no reason to remember it.
Any suggestions will be welcomed but remember: once I start booting into
a 3.x kernel, the only control I have over what happens is using
^Alt-Delete to reboot.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 10.07.2012, Joe Zeff wrote:

> See https://bugzilla.redhat.com/show_bug.cgi?id=769747 for details. Note
> that I'm not the original reporter, and I seem to be the only one who can't
> boot because of it.

I think you should compile a completely fresh 3.4.4. from kernel.org
and report this on linux-kernel@vger.kernel.org, if the problem
persists. You could use the Fedora .config from /boot as a starting
point, if you're not used to compile your own kernels.



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 07/10/2012 01:56 PM, Heinz Diehl wrote:

I think you should compile a completely fresh 3.4.4. from kernel.org
and report this onlinux-kernel@vger.kernel.org, if the problem
persists. You could use the Fedora .config from /boot as a starting
point, if you're not used to compile your own kernels.


I don't think I've compiled a kernel of my own since F6, and I don't see
any reason to do it now. The laptop is a secondary machine, only used
sporadically and never has anything on it that I'd be afraid to have
compromised except for passwords. Yes, I'd much rather be using the
latest kernel, but it's not that big a deal. Of course, if you'd
suggested some boot params to try, that'd be different.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 07/10/2012 02:33 PM, Edward M wrote:


just a suggestion:-)
this thread appears is getting hijacked, may want to start your own
thread.


Actually, I only mentioned it as an example of needing a backup kernel.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 07/10/2012 02:15 PM, Joe Zeff wrote:

On 07/10/2012 01:56 PM, Heinz Diehl wrote:

I think you should compile a completely fresh 3.4.4. from kernel.org
and report this onlinux-kernel@vger.kernel.org, if the problem
persists. You could use the Fedora .config from /boot as a starting
point, if you're not used to compile your own kernels.


I don't think I've compiled a kernel of my own since F6, and I don't
see any reason to do it now. The laptop is a secondary machine, only
used sporadically and never has anything on it that I'd be afraid to
have compromised except for passwords. Yes, I'd much rather be using
the latest kernel, but it's not that big a deal. Of course, if you'd
suggested some boot params to try, that'd be different.


just a suggestion:-)
this thread appears is getting hijacked, may want to start your own
thread.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 07/10/2012 02:31 PM, Joe Zeff wrote:

On 07/10/2012 02:33 PM, Edward M wrote:


just a suggestion:-)
this thread appears is getting hijacked, may want to start your own
thread.


Actually, I only mentioned it as an example of needing a backup kernel.
--


sorry, I misunderstood. but now i understand:-)

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Tue, Jul 10, 2012 at 10:20 PM, Joe Zeff <joe@zeff.us> wrote:
> On 07/10/2012 11:43 AM, Heinz Diehl wrote:
>>
>> Do you have any information on this problem? What did you try to solve
>> it?
>
>
> See https://bugzilla.redhat.com/show_bug.cgi?id=769747 for details. Note
> that I'm not the original reporter, and I seem to be the only one who can't
> boot because of it. I reported this here when it first struck, but nobody
> responded and you'd have no reason to remember it. Any suggestions will be
> welcomed but remember: once I start booting into a 3.x kernel, the only
> control I have over what happens is using ^Alt-Delete to reboot.

"rd.driver.blacklist=ums_realtek blacklist=ums_realtek" to prevent
loading in the initramfs and installer...

For the real root:

# echo "blacklist ums_realtek" > /etc/modprobe.d/realtek.conf
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 07/12/2012 04:14 PM, Harald Hoyer wrote:

On Tue, Jul 10, 2012 at 10:20 PM, Joe Zeff <joe@zeff.us> wrote:

On 07/10/2012 11:43 AM, Heinz Diehl wrote:


Do you have any information on this problem? What did you try to solve
it?



See https://bugzilla.redhat.com/show_bug.cgi?id=769747 for details. Note
that I'm not the original reporter, and I seem to be the only one who can't
boot because of it. I reported this here when it first struck, but nobody
responded and you'd have no reason to remember it. Any suggestions will be
welcomed but remember: once I start booting into a 3.x kernel, the only
control I have over what happens is using ^Alt-Delete to reboot.


"rd.driver.blacklist=ums_realtek blacklist=ums_realtek" to prevent
loading in the initramfs and installer...

For the real root:

# echo "blacklist ums_realtek" > /etc/modprobe.d/realtek.conf



One question before I try this: would this completely disable my card
reader? I ask because the USB port on my camera has stopped working and
that card reader's the only access I have right now to the photos.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org