Re: Questions about building plasma active
Em Saturday 28 April 2012, Marco Martin escreveu: On Saturday 28 April 2012, Lamarque V. Souza wrote: Em Saturday 28 April 2012, Jonathan Schultz escreveu: Hello folks, Hi, I've just discovered this project so please bear with me if I ask questions to which the answers are already out there. I've just been trying to install KDE Active on a Motorola Xoom, which is a Tegra 2 device. The basyskom install scripts don't seem to work, but I was able to flash the boot image and install the filesystem on an SD card as per the directions. When I booted nothing happened. :( Literally, no messages, nothing. Sometimes on first boot the screeh becomes black for several minutes while nepomuk is indexing the file system. If there is disk activity you should wait (up to 7 minutes) and see if the desktop appears. this happens when the date of the shared desktop ontologies files are more recent than the nepomuk database dump (or if there isn't a db preloaded at all) Good to know that. -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Questions about building plasma active
Many thanks for the input. Mer Plasma Active builds use systemd as their init system and the above error looks like you don't have the required kernel options set in your kernel config to satisfy systemd. You were right on there. See http://wiki.merproject.org/wiki/Adaptation_Guide for options you need in your kernel. So now it gets a lot further into the boot process. I see one suspicious message: systemd-logind.service: main process exited, code=exited, status=1 Starting Login Service failed, see 'systemctl status systemd-logind.service for details. I see no way to get open a shell to look for those details. Then a few lines down: starting X server with /usr/bin/Xorg :0 -nolisten tcp -noreset -auth /home/mer/.Xauthority vt1 and there it freezes, presumably the X server fails to start. If I take the SD card out and look at /var/log/Xorg.0.log I see it ends with: [36.997] (WW) Falling back to old probe method for tegra [36.997] (II) Loading /usr/lib/xorg/modules/drivers/tegra_drv.so [36.997] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support Which looks like more kernel stuff, but nothing I can understand. Any further suggestions? Cheers, Jonathan ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Questions about building plasma active
Jonathon Hi, Good progress. What you are seeing now is probably a mismatch between the kernel and userspace tegra video bits and pieces. Try configuring X to use a simple framebuffer device instead of tegra_drv.so BR vgrade On Mon, Apr 30, 2012 at 12:55 PM, Jonathan Schultz jonat...@imatix.comwrote: Many thanks for the input. Mer Plasma Active builds use systemd as their init system and the above error looks like you don't have the required kernel options set in your kernel config to satisfy systemd. You were right on there. See http://wiki.merproject.org/**wiki/Adaptation_Guidehttp://wiki.merproject.org/wiki/Adaptation_Guidefor options you need in your kernel. So now it gets a lot further into the boot process. I see one suspicious message: systemd-logind.service: main process exited, code=exited, status=1 Starting Login Service failed, see 'systemctl status systemd-logind.service for details. I see no way to get open a shell to look for those details. Then a few lines down: starting X server with /usr/bin/Xorg :0 -nolisten tcp -noreset -auth /home/mer/.Xauthority vt1 and there it freezes, presumably the X server fails to start. If I take the SD card out and look at /var/log/Xorg.0.log I see it ends with: [36.997] (WW) Falling back to old probe method for tegra [36.997] (II) Loading /usr/lib/xorg/modules/drivers/**tegra_drv.so [36.997] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support Which looks like more kernel stuff, but nothing I can understand. Any further suggestions? Cheers, Jonathan ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Questions about building plasma active
Jonathan Hi, 'Failed to mount /dev: No such device' Mer Plasma Active builds use systemd as their init system and the above error looks like you don't have the required kernel options set in your kernel config to satisfy systemd. See http://wiki.merproject.org/wiki/Adaptation_Guide for options you need in your kernel. BR vgrade On Sun, Apr 29, 2012 at 2:23 AM, Jonathan Schultz jonat...@imatix.comwrote: Sometimes on first boot the screeh becomes black for several minutes while nepomuk is indexing the file system. If there is disk activity you should wait (up to 7 minutes) and see if the desktop appears. I cannot tell whether there is disk activity as it's all solid state. :) I'm not sure whether I should have been getting console output on boot. I tried it with liv2's kernel https://github.com/LIV2/LIV2-**Xoom-GNUhttps://github.com/LIV2/LIV2-Xoom-GNU(which works getting debian on the xoom) and the boot hung at: 'Failed to mount /dev: No such device' so I presume there is some kernel incompatibility going on. I do not own an Arm tablet to test the procedure myself. You should try wainting 10 minutes to see if the homescreen appears. Is there somewhere to go to talk to people doing arm builds? All our builds are rpm based but Kubuntu already packs Plasma Active: Ah, that's interesting. I see they are only doing i386 builds for the moment but maybe I can get on board that project. Cheers, Jonathan __**_ Active mailing list Active@kde.org https://mail.kde.org/mailman/**listinfo/activehttps://mail.kde.org/mailman/listinfo/active ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Questions about building plasma active
Sometimes on first boot the screeh becomes black for several minutes while nepomuk is indexing the file system. If there is disk activity you should wait (up to 7 minutes) and see if the desktop appears. I cannot tell whether there is disk activity as it's all solid state. :) I'm not sure whether I should have been getting console output on boot. I tried it with liv2's kernel https://github.com/LIV2/LIV2-Xoom-GNU (which works getting debian on the xoom) and the boot hung at: 'Failed to mount /dev: No such device' so I presume there is some kernel incompatibility going on. I do not own an Arm tablet to test the procedure myself. You should try wainting 10 minutes to see if the homescreen appears. Is there somewhere to go to talk to people doing arm builds? All our builds are rpm based but Kubuntu already packs Plasma Active: Ah, that's interesting. I see they are only doing i386 builds for the moment but maybe I can get on board that project. Cheers, Jonathan ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Questions about building plasma active
Hello folks, I've just discovered this project so please bear with me if I ask questions to which the answers are already out there. I've just been trying to install KDE Active on a Motorola Xoom, which is a Tegra 2 device. The basyskom install scripts don't seem to work, but I was able to flash the boot image and install the filesystem on an SD card as per the directions. When I booted nothing happened. :( Literally, no messages, nothing. But I have been able to install Debian and KDE/netbook using this information: http://forum.xda-developers.com/showthread.php?t=1192639 So my questions are: 1. Can anyone suggest how to figure out what's going wrong with basyskom's images? 2. What is involved in building plasma active from sources? Could it be installed as a Debian package? How much tweaking has gone into the kernel? Etc. Many thanks, Jonathan ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Questions about building plasma active
Em Saturday 28 April 2012, Jonathan Schultz escreveu: Hello folks, Hi, I've just discovered this project so please bear with me if I ask questions to which the answers are already out there. I've just been trying to install KDE Active on a Motorola Xoom, which is a Tegra 2 device. The basyskom install scripts don't seem to work, but I was able to flash the boot image and install the filesystem on an SD card as per the directions. When I booted nothing happened. :( Literally, no messages, nothing. Sometimes on first boot the screeh becomes black for several minutes while nepomuk is indexing the file system. If there is disk activity you should wait (up to 7 minutes) and see if the desktop appears. But I have been able to install Debian and KDE/netbook using this information: http://forum.xda-developers.com/showthread.php?t=1192639 So my questions are: 1. Can anyone suggest how to figure out what's going wrong with basyskom's images? I do not own an Arm tablet to test the procedure myself. You should try wainting 10 minutes to see if the homescreen appears. 2. What is involved in building plasma active from sources? Could it be installed as a Debian package? How much tweaking has gone into the kernel? Etc. You need to compile kde-workspace with the mobile profile and compile the master branch from the following KDE repositories: plasma-mobile, startactive, kde-runtime, contour, kactivities and share-like-connect. All our builds are rpm based but Kubuntu already packs Plasma Active: http://blogs.kde.org/node/4544 We have not created new patches for the kernel, we use the kernel used in Meego or Mer. They contain patches applied but not from us. -- Lamarque V. Souza http://www.basyskom.com/ ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
