Bug#663653: fglrx-driver loads intel driver which doesn't find a configured screen
On Tue, Jul 24, 2012 at 10:14:06PM +0200, Paul Menzel wrote:
> Dear Pedro, dear Thomas,
>
>
> Am Dienstag, den 24.07.2012, 11:31 +0200 schrieb Paul Menzel:
>
> > thank you very much for your answer. Unfortunately Thomas probably did
> > not get your reply since you did not put him into CC. You can avoid that
> > problem by downloading all messages belonging to that report
> >
> > $ sudo aptitude install devscripts
> > $ bts show --mbox 663653
> >
> > and import the mbox file under `~/.devscripts-cache/bts/663653.mbox`
> > into Icedove. Then just do a reply to all to the appropriate message.
> > That would be awesome.
> >
> >
> > Am Donnerstag, den 22.03.2012, 02:51 +0000 schrieb Pedro Ângelo:
> >
> > > I have a similar problem on a laptop with hybrid ati/intel dual graphics.
> >
> > What laptop do you have? Maybe also attach or paste the output of
> > `lspci`.
> >
> > > I've managed to get it working by blacklisting the i915 module and got
> > > to where you were at with a blank screen but an ok xorg.log
> >
> > Could you attach `/var/log/Xorg.0.log` please?
> >
> > > I tried fiddling with the brightness controls on the laptop and it
> > > worked, so you might try that.
> >
> > Oh, so the brightness was just turned down. Nice one! Great you found
> > it.
> >
> > > I hope this SNA support eventually lands on testing to see if I can use
> > > the laptop without all these fiddly configs.
> >
> > `xserver-xorg-video-intel` 2:2.19.0-4 in Debian Wheezy/testing is
> > compiled with SNA support. You have to enable it though. For example
> > create `/etc/X11/xorg.conf.d/99-local.conf` with the following content.
> >
> > Section "Device";
> > Identifier "Device0";
> > Driver "intel";
> > Option "AccelMethod" "sna"
> > EndSection
>
> I think you need to remove all ; at the end of the lines.
>
> Section "Device"
> Identifier "Device0"
> Driver "intel"
> Option "AccelMethod" "sna"
> EndSection
>
>
> Thanks,
>
> Paul
>
>
> > PS: I still do not know what the error is. Could someone give a short
> > explanation, please?
I have tried to get my laptop working on the weekend after some heavy updates.
Turned the beast around to google about it with the correct name specs.
So I needed to close the lid. When I opened it back, X was there.
I am getting the same behaviour with the intel or the fglrx driver.
Display is pitch black. Close the thing, open it again and voila, we have
got kdm waiting for login.
So this one is usable under linux/X after all.
Sorry for not replaying earlier ...
Regards Thomas
Reply to: