Re: Archos G9 devel image
PS: After letting it charge a little the devel image also recovered. Some part of the GUI (kwin or something) had crashed. So, the devel version, in general, works as well. :) On 02/23/2013 11:36 AM, Ruediger Gad wrote: Hi, attached I send two .ks files: one for creating a testing and one for creating a devel rootfs tarball. Please note that these .ks files will generate armv7hl installations instead of armv7l as can be downloaded from basyskom. Both use the pvr driver. I briefly tested the generated tarballs: The testing one seems to work ok. It booted fine and I could make a suspend/resume cycle without problems. The devel one boots and the GUI comes up. However, here the GUI got somewhat "stuck". Nothing responds except actions being triggered via the hardware buttons (volume, lock screen). I don't know if this may be caused by my device battery being nearly empty (At least I saw some message at bootup that may have caused the GUI to lock up.). I will test that later after letting the device charge a little. I generated the rootfs tarballs as follows: PATH=$PATH:/sbin sudo mic create fs plasma-active-archos-gen9-pvr-mer-devel-2013-02-23.ks --pack-to=plasma-active-archos-gen9-pvr-mer-devel-2013-02-23.tar.gz --pkgmgr=yum --arch=armv7hl Up to now, the bits for the armv7hl hardware adaptation are only hosted in my "private" repositories on cobs@meego: https://build.pub.meego.com/project/show?project=home%3Awonko%3Aarchos-g9-pa-adaptation https://build.pub.meego.com/project/show?project=home%3Awonko%3Aarchos-g9-pa-adaptation%3Apvr If there is the interest I (or someone else) could push this stuff into a little bit "more official" place. Would creating own projects for an Archos G9 armv7hl adaptation make sense? Imho integrating the changes with the existing Archos G9 armv7l adaptation would be pretty complicated as we would need to distinguish between soft and hard float for building some packages in a single common project. I could also upload the images somewhere if you like to test those yourself. Regards, Ruediger On 02/22/2013 09:10 AM, Hillel Lubman wrote: On 22/02/13 03:05, Yannick Kiekens wrote: As work-around to get latest devel stuff running on your device, just add the following repo to latest testing based archos gen9 image (try the pvr one): zypper ar -f http://repo.pub.meego.com/Project:/KDE:/Devel/CE_UX_PlasmaActive_armv7l/ develop This gave an error while doing the upgrade of kdebase (something about a directory that can't be deleted) I'll have more time to look at it this weekend To bad to hear about the support problems, it is nice hacking a tablet with vendor support. greatings Yannick Kiekens There was a similar issue with switching Nexus 7 build from testing to devel. See here in the comments: http://aseigo.blogspot.com/2013/01/plasma-active-stable-devel-and-bleeding.html may be it'll be helpful. Regards, Hillel Lubman. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active -- http://ruedigergad.com smime.p7s Description: S/MIME Cryptographic Signature ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Archos G9 devel image
Hi, attached I send two .ks files: one for creating a testing and one for creating a devel rootfs tarball. Please note that these .ks files will generate armv7hl installations instead of armv7l as can be downloaded from basyskom. Both use the pvr driver. I briefly tested the generated tarballs: The testing one seems to work ok. It booted fine and I could make a suspend/resume cycle without problems. The devel one boots and the GUI comes up. However, here the GUI got somewhat "stuck". Nothing responds except actions being triggered via the hardware buttons (volume, lock screen). I don't know if this may be caused by my device battery being nearly empty (At least I saw some message at bootup that may have caused the GUI to lock up.). I will test that later after letting the device charge a little. I generated the rootfs tarballs as follows: PATH=$PATH:/sbin sudo mic create fs plasma-active-archos-gen9-pvr-mer-devel-2013-02-23.ks --pack-to=plasma-active-archos-gen9-pvr-mer-devel-2013-02-23.tar.gz --pkgmgr=yum --arch=armv7hl Up to now, the bits for the armv7hl hardware adaptation are only hosted in my "private" repositories on cobs@meego: https://build.pub.meego.com/project/show?project=home%3Awonko%3Aarchos-g9-pa-adaptation https://build.pub.meego.com/project/show?project=home%3Awonko%3Aarchos-g9-pa-adaptation%3Apvr If there is the interest I (or someone else) could push this stuff into a little bit "more official" place. Would creating own projects for an Archos G9 armv7hl adaptation make sense? Imho integrating the changes with the existing Archos G9 armv7l adaptation would be pretty complicated as we would need to distinguish between soft and hard float for building some packages in a single common project. I could also upload the images somewhere if you like to test those yourself. Regards, Ruediger On 02/22/2013 09:10 AM, Hillel Lubman wrote: On 22/02/13 03:05, Yannick Kiekens wrote: As work-around to get latest devel stuff running on your device, just add the following repo to latest testing based archos gen9 image (try the pvr one): zypper ar -f http://repo.pub.meego.com/Project:/KDE:/Devel/CE_UX_PlasmaActive_armv7l/ develop This gave an error while doing the upgrade of kdebase (something about a directory that can't be deleted) I'll have more time to look at it this weekend To bad to hear about the support problems, it is nice hacking a tablet with vendor support. greatings Yannick Kiekens There was a similar issue with switching Nexus 7 build from testing to devel. See here in the comments: http://aseigo.blogspot.com/2013/01/plasma-active-stable-devel-and-bleeding.html may be it'll be helpful. Regards, Hillel Lubman. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active -- http://ruedigergad.com # -*-mic2-options-*- -f loop --save-kernel -*-mic2-options-*- # # Do not Edit! Generated by: # kickstarter.py # lang en_US.UTF-8 keyboard us timezone --utc Europe/Berlin rootpw mer desktop --autologinuser=mer user --name mer --groups audio,video --password mer repo --name=ce-utils --baseurl=http://repo.pub.meego.com/Mer:/Tools:/Testing/Mer_Core_armv7hl/ --save repo --name=mer-core --baseurl=http://releases.merproject.org/releases/latest/builds/armv7hl/packages/ --save repo --name=mer-core-debuginfo --baseurl=http://releases.merproject.org/releases/latest/builds/armv7hl/debug/ --save repo --name=mer-shared --baseurl=http://repo.pub.meego.com/CE:/MW:/Shared/Mer_Core_armv7hl/ --save #repo --name=mer-shared --baseurl=http://repo.merproject.org/obs/nemo:/devel:/mw/latest_armv7hl/ --save repo --name=mer-extras --baseurl=http://repo.pub.meego.com/Project:/KDE:/Mer_Extras/CE_MW_Shared_Mer_Core_armv7hl/ --save repo --name=plasma --baseurl=http://repo.pub.meego.com/Project:/KDE:/Devel/CE_UX_PlasmaActive_armv7hl/ --save repo --name=adaptation-archos-gen9 --baseurl=http://repo.pub.meego.com/home:/wonko:/archos-g9-pa-adaptation/Project_KDE_Devel_CE_UX_PlasmaActive_armv7hl/ --save repo --name=adaptation-archos-gen9-pvr --baseurl=http://repo.pub.meego.com/home:/wonko:/archos-g9-pa-adaptation:/pvr/Project_KDE_Devel_CE_UX_PlasmaActive_armv7hl/ --save %packages # ce_tools repository # # mer-core repository @Mer Core Utils # connman-test diffutils openssh-clients vim-enhanced tar @Mer Core # Mer Core defines following packages (06 dec 2011) # basesystem bash boardname coreutils deltarpm e2fsprogs file filesystem fontpackages-filesystem # kbd lsb-release meego-release nss pam passwd prelink procps readline rootfiles rpm setup # shadow-utils shared-mime-info systemd-sysv time udev usbutils util-linux xdg-user-dirs zypper @Mer Connectivity # Mer Connectivity defines following packages (06 dec 2011) # bluez connman crda iproute iputils net-tools ofono wireless-tools wpa_supplicant #remove connman
Re: Archos G9 devel image
On 22/02/13 03:05, Yannick Kiekens wrote: > > As work-around to get > > latest devel stuff running on your device, just add the following > repo to latest testing based > archos gen9 image (try the pvr one): > > zypper ar -f > http://repo.pub.meego.com/Project:/KDE:/Devel/CE_UX_PlasmaActive_armv7l/ > develop > > > > This gave an error while doing the upgrade of kdebase (something about > a directory that can't be deleted) > I'll have more time to look at it this weekend > > To bad to hear about the support problems, it is nice hacking a tablet > with vendor support. > > greatings > Yannick Kiekens > There was a similar issue with switching Nexus 7 build from testing to devel. See here in the comments: http://aseigo.blogspot.com/2013/01/plasma-active-stable-devel-and-bleeding.html may be it'll be helpful. Regards, Hillel Lubman. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Archos G9 devel image
> > As work-around to get > latest devel stuff running on your device, just add the following repo to > latest testing based > archos gen9 image (try the pvr one): > > zypper ar -f > http://repo.pub.meego.com/Project:/KDE:/Devel/CE_UX_PlasmaActive_armv7l/develop > This gave an error while doing the upgrade of kdebase (something about a directory that can't be deleted) I'll have more time to look at it this weekend To bad to hear about the support problems, it is nice hacking a tablet with vendor support. greatings Yannick Kiekens ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Archos G9 devel image
Hi, On 18.02.2013 20:48, Yannick Kiekens wrote: Hi, the following image: basyskom-plasma-active-archos-gen9-omapfb-tablet-mer-devel-130217-1801 does not appear to boot at all. Plasma active Three basyskom-plasma-active-three-archos-gen9-omapfb-tablet-mer-release works just fine. Last year running the weekly devel images has worked for me. I have no idea if older 2013 devel images work, as my G9 has been in repair for several months. What is the recommended image for testing current development? the current xserver of Mer project does not work anymore with omapfb and pvr x11 driver of archos gen9 hardware adaption project. The effort to update the archos gen9 pvr kernel stuff looks too huge. The testing image is still using the old xserver and pvr should work great because the suspend issue was solved/work-around by ruediger. I don't have any archos gen9 hardware anymore and I'm unsure if we should downgrade the xserver inside archos adaption project, change to new omapfb only or just stop support for this device. As work-around to get latest devel stuff running on your device, just add the following repo to latest testing based archos gen9 image (try the pvr one): zypper ar -f http://repo.pub.meego.com/Project:/KDE:/Devel/CE_UX_PlasmaActive_armv7l/ develop Sorry this is all we have ;( Cheers Maurice Greatings Yannick Kiekens ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Archos G9 devel image
Hi, the following image: basyskom-plasma-active-archos-gen9-omapfb-tablet-mer-devel-130217-1801 does not appear to boot at all. Plasma active Three basyskom-plasma-active-three-archos-gen9-omapfb-tablet-mer-release works just fine. Last year running the weekly devel images has worked for me. I have no idea if older 2013 devel images work, as my G9 has been in repair for several months. What is the recommended image for testing current development? Greatings Yannick Kiekens ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
