From: Fernando Rodriguez <frodriguez.developer@outlook.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
Date: Sun, 30 Aug 2015 18:15:02 -0400 [thread overview]
Message-ID: <BLU436-SMTP184E5755D96EFC3C26B55178D6C0@phx.gbl> (raw)
In-Reply-To: <BLU436-SMTP98BF36044331D8245E93DC8D6C0@phx.gbl>
On Sunday, August 30, 2015 6:11:00 PM Fernando Rodriguez wrote:
> On Sunday, August 30, 2015 10:51:57 PM Peter Weilbacher wrote:
> > Hi Fernando,
> >
> > On Sun, 30 Aug 2015, Fernando Rodriguez wrote:
> >
> > > 1. Add loglevel=7 to your kernel parameters and see what it prints
before
> it
> > > hangs.
> >
> > That helped, it showed me something about drm, so...
> >
> > > 3. From your kernel parameters I assume you're using the radeon free
> driver
> > > right? If that's the case disable it (don't compile it in or just delete
> the
> > > module) and try to boot wiith a framebuffer.
> >
> > ... this was a good suggestion. Switching off DRM/Radeon gets me a
> > kernel that boots. However, with that config I cannot run X (which then
> > complains about missing kernel mode switching). If I follow
> > wiki.gentoo.org/wiki/Xorg/Guide#Kernel_modesetting I again arrive at the
> > kernel settings that I previously had and which didn't work with 4.1.x.
> >
> > Any more suggestions?
> > Peter.
> >
>
> At least you norrowed down, that was the idea.
> I would suspect a new bug, so post to the radeon mailing list. Doing the git
> bisect first will make it easier for them so they'll be more willing to help.
I
> would try booting without those radeon paremeters first.
>
> You could try the proprietary driver but the one in the portage tree will
not
> build with a kernel >3.18.19 but if you search b.g.o there are patches to
make
> it build. Or you could try my ebuild but I'm not sure that it will build
> either since I'm using 3.18.20 now:
>
> https://github.com/fernando-rodriguez/portage-overlay/tree/master/x11-drivers/ati-drivers
And you should still try suggestion #2 because it's very likely to only affect
one specific configuration.
--
Fernando Rodriguez
next prev parent reply other threads:[~2015-08-30 22:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 13:08 [gentoo-user] Problems booting vanilla kernel 4.1.x Peter Weilbacher
2015-08-23 13:23 ` Alexander Kapshuk
2015-08-25 16:40 ` Peter Weilbacher
2015-08-25 17:54 ` Alexander Kapshuk
2015-08-29 12:09 ` Peter Weilbacher
2015-08-29 14:30 ` Alexander Kapshuk
2015-08-30 8:45 ` Peter Weilbacher
2015-08-30 19:16 ` Fernando Rodriguez
2015-08-30 20:51 ` Peter Weilbacher
2015-08-30 21:54 ` [gentoo-user] " James
2015-08-30 22:11 ` [gentoo-user] " Fernando Rodriguez
2015-08-30 22:15 ` Fernando Rodriguez [this message]
2015-08-31 19:19 ` Peter Weilbacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLU436-SMTP184E5755D96EFC3C26B55178D6C0@phx.gbl \
--to=frodriguez.developer@outlook.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox