On Sat, 25 Aug 2012, Dave Anderson wrote:
If there's no interest in this info, I won't burn an afternoon
collecting it. If there is interest, answers to my questions would be
useful.
Dave
>A year or so ago, as part of selecting a notebook to buy, I gathered
>dmesg info from all of the notebooks I could find in local stores
>(booting from and saving data to a USB stick) and sent it to
>[email protected] as well as using it myself. Since I expect that it
>would be useful to the developers to have this info for the current crop
>of notebooks, I plan to do another data-gathering session sometime in
>the next few weeks. I'll be using an amd64 snapshot and, as FAQ 4.10
>requests, will gather both 'dmesg' and 'sysctl hw.sensors' output using
>both the sp and mp kernels for each system.
>
>Since the data collection will be scripted it will be easy to also
>gather other information; pcidump, usbdevs and acpidump come to mind.
>What would be useful for the developers? I've got a store which has
>several dozen demo notebooks and will let me gather data from them, but
>there won't be an opportunity to go back -- I need to get all of the
>useful info at once.
>
>So, my questions to the developers:
>
>1) Does it matter which amd64 snapshot I use? Are there any recent or
>forthcoming ones which are especially good or bad for this purpose?
>
>2) What additional information should I collect? Exact commands and
>options, please. I don't mind installing tools which aren't in base,
>but the output needs to go to, or be able to be redirected to, a file.
>
>3) Other than the dmesg/sensor info which will go to [email protected],
>where should I send the additional info? If there's no suitable place,
>I can just keep it around and let anyone who needs it ask me for it.
>
> Dave
--
Dave Anderson
<[email protected]>
