Hi Ryan,
Looks good to me :)
Regards,
Sumit Bhardwaj
On Monday 15 June 2015 11:37 AM, Ryan
Lerch wrote:
On 06/15/2015 03:00 PM, Sumit
Bhardwaj wrote:
Hi Ryan,
Thanks for the great suggestions. The pleasure is all mine,
Fedora has brought so many positive changes in my world of
computing, If I can do anything for the project, it's an honor
and a privilege.
I have tried to incorporate your suggestions in the article and
resubmitted it for review. Please have a look and let me know if
any further refinement would be good.
Thanks again.
Regards,
Sumit Bhardwaj
On Monday 15 June 2015 09:14 AM,
Ryan Lerch wrote:
Hi Sumit!
First up, thanks for submitting your first post to the Fedora
Magazine. I have done a quick review of your post, and here
are a few ideas / suggestions from me. (other editors, feel
free to pitch in ideas too)
First up, i'd probably be a bit more direct and informative
with the title, instead of "Fedora 22 Intel Graphics Woes :
Here's some help"
maybe something like "Solution for graphics issues on some
Intel graphics chipsets in Fedora 22" (just a suggestion, feel
free to change and or edit too :) )
Secondly, i'd probably remove the majority of the first
paragraph and lead with the issue itself (your third
paragraph) -- most people get to the magazine via third party
links, so starting with the info they came for always works
well. I'm thinking something like:
"""
Fedora 22 was [link to release annonce on fedora mag]released
recently[/link], and if you are using a Pre-Sandybridge era
Intel-based graphics chipset (For example, Intel 4 series
motherboards with G41 chipset and GMA X4500 graphics), chances
are that you might be facing graphics issues like shown in
below screenshot on Fedora 22.
[screenshot]
"""
Then after the screenshot, have your brief description of the
problem, covering the points that fedora switched to a new
accel method that doesnt work so well with older chipsets.
Then put the solution. I found the bug for this issue (https://bugzilla.redhat.com/show_bug.cgi?id=1226743)
which might be worth mentioning. And there updated kernels
(kernel-4.0.5-300.fc22 and kernel-4.0.5-200.fc21) that fix
this issue is already in updates-testing, so it is probably a
better solution to recommend that people install the new
package with the fix from updates testing, or wait for the
package to hit the proper repos (rather than editing a config
file that they may forget about and cause them issues in the
future.)
cheers,
ryanlerch
Just did a quick edit, and added a quick howto on getting the
packages from updates-testing (in case the reader doesnt know how
to), and added some emphasis on the note that the workaround is a
temp solution.
Does that look ok to you? feel free to revert if you don't agree
:)
cheers,
ryanlerch
|
