Comment 6 for bug 124411

Revision history for this message
Brian Murray (brian-murray) wrote :

I completely understand that this process may not be intuitive but the correct thing to do instead of opening a new bug report would be to indicate that the original bug also exists in linux-source-2.6.22. I have done this to the original bug report by clicking the "Also affects distribution" link. I then choose Ubuntu as the distribution and added that it affected package linux-source-2.6.22. I am going to mark this bug as a duplicate of that one. If you could please add your dmidecode information to the original bug report as that does not have anyone's dmidecode information that would be helpful.