lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130312160249.GA32182@codeblau.de>
Date:	Tue, 12 Mar 2013 17:02:49 +0100
From:	felix-linuxkernel@...e.de
To:	linux-kernel@...r.kernel.org
Subject: Who is responsible for radeon driver bugs?

The radeon driver does not work on my laptop.
I sent a bug report here a week ago, but got no responses.
What is the right place to send bug reports for the radeon driver?

The bug is that LVDS output does not work.  This is, according to lspci,
a 5000M series Madison Radeon.

When I insmod the module, the screen stays in text mode and appears
locked up.

If something is connected to the HDMI port, I get a framebuffer console
there.  LVDS stays in broken text mode though.

When I start X, the HDMI screen turns dark and stays dark and the LVDS
screen also stays dark and I have to reboot.

The driver loads the REDWOOD firmware OK.

Who is responsible for this?  Where do I send my bug report?

Thanks,

Felix
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ