[Meego-handset] Note to MeeGo CE Testers, check /etc/boardname validity
marko.saukko at cybercom.com
Mon Sep 26 05:12:39 UTC 2011
On 09/25/2011 07:12 PM, Marko Saukko wrote:
> we are experiencing a quite bad regression from something in the 1.3
> images with the boardname packaging (doesn't happen always though). This
> regression can cause e.g., audio, sensors and policy rules not working
> properly in the image.
> The problem is described in https://bugs.meego.com/show_bug.cgi?id=23366
> I would request all testers to check that their /etc/boardname file is
> properly set before filing any bugs so we don't get a flood of
> regressions that are caused by this single bug.
> === Steps to verify if the bug exists on your image ===
> Check if file /etc/boardname is present "ls /etc/boardname" on your
> system. If it is not then login as root and run "boardname" command and
> reboot the image.
> If the file is present then check that it is not empty, e.g., "cat
> /etc/boardname" if the file is empty then login as root remove the file
> "rm /etc/boardname" and run "boardname" command.
> After running the boardname command and getting the proper boardname
> value, reboot your device before continuing testing. Proper values are
> something like following:
> N900: arm_nokia_rx_51_board_*
> N950: arm_nokia_rm_680_board_*
> MeeGo-handset mailing list
> MeeGo-handset at lists.meego.com
forgot to mention that after the "boardname" cmd returns proper value
and you have rebooted once the issue should be gone.
More information about the MeeGo-handset