[Gta04-owner] [hwvalidation] cpu at 100% on boot (multiboot)
Dr. H. Nikolaus Schaller
hns at goldelico.com
Sat Oct 6 10:39:30 CEST 2012
Am 06.10.2012 um 00:56 schrieb Boudewijn:
> Hi list,
> I got the HW validation distro on p5 of my SD card, and use the distro-switcher in QtMoko to boot it.
> Upon landing on the lxde-desktop, the CPU climbs to 100% within a few seconds after displaying the wallpaper and widgets ("clean install", so only the CPU monitor). I can see the CPU climbing, because the widget starts black and becomes green all over quite quickly. Perhaps the CPU is already close to 100% while starting the widget, and uses last bits of processing to update the rectangle to become all green over time.
I remember that we ran into this problem when bringing up the first GTA04 boards. If I remember correctly, it has something to do with the X server's input devices.
So the xorg.conf has been modified to ensure that the touch screen is seen only once in the list of Xinput drivers.
Otherwise something in the X-Server goes into a busy waiting loop.
> I suspect there's a kernel mismatch, since I just extracted the tarball to this partition, using QtMoko's boot partition. One of the things not available, is USB (my laptops registers the phone on boot, but nothing after that)
This may not work with a different kernel that presents the touch screen driver differently to user space.
> How can I mix the two? I recall this being discussed before, but can't find the message anymore. Would it suffice to copy the right files to /boot of the HW validation distro?
> Here's the partition table:
> Disk /dev/mmcblk0: 8270 MB, 8270118912 bytes
> 4 heads, 16 sectors/track, 252384 cylinders
> Units = cylinders of 64 * 512 = 32768 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
> Device Boot Start End Blocks Id System
> /dev/mmcblk0p1 * 3 2048 65472 c W95 FAT32 (LBA)
> /dev/mmcblk0p2 2049 67584 2097152 83 Linux
> /dev/mmcblk0p3 67585 133120 2097152 83 Linux
> /dev/mmcblk0p4 133121 252384 3816448 5 Extended
> /dev/mmcblk0p5 133153 198688 2097152 83 Linux
> /dev/mmcblk0p6 198721 215104 524288 82 Linux swap / /dev/mmcblk0p7 215137 252384 1191936 b W95 FAT32
> p1 = boot
> p2 = QtMoko
> p3 = SHR
> p5 = HW validation
> p7 might be(come) QtMoko docs
> the contents in p1 are from QtMoko:
> root at neo:/media/hwval/boot# ls /media/p1/ -lah
> total 3.5M
> drwxr-xr-x 3 root root 1.0K Jan 1 1970 .
> drwxr-xr-x 7 root root 4.0K Sep 30 00:16 ..
> -rwxr-xr-x 1 root root 24K Sep 30 00:54 MLO
> -rwxr-xr-x 1 root root 9.1K Sep 30 00:54 boot.scr
> -rwxr-xr-x 1 root root 889 Sep 30 00:54 bootargs.scr
> drwxr-xr-x 2 root root 512 Oct 6 00:31 gta04-init
> -rwxr-xr-x 1 root root 221K Sep 30 00:54 menu.rgb16z
> -rwxr-xr-x 1 root root 39K Sep 30 00:54 splash.rgb16z
> -rwxr-xr-x 1 root root 264K Sep 30 00:54 u-boot.bin
> -rwxr-xr-x 1 root root 2.9M Oct 6 00:48 uImage
> -rwxr-xr-x 1 root root 9.1K Sep 30 00:54 user.scr
> -rwxr-xr-x 1 root root 15K Sep 30 00:54 x-load.flash
> There's nothing in /boot of the HW validation distro:
> root at neo:/media/hwval/boot# ls -hal
> total 8.0K
> drwxr-xr-x 2 root root 4.0K Jun 19 2010 .
> drwxr-xr-x 24 502 502 4.0K Oct 6 00:32 ..
> root at neo:/media/hwval/boot#
> Thanks in advance and best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gta04-owner