On Mon, Apr 16, 2012 at 02:01:11PM +0200, Matthias Apitz wrote: > El día Monday, April 16, 2012 a las 11:26:06AM +0200, Martin Jansa escribió: > > > > The result is unusable: > > > > > > - the screens of the first-boot dialogues are not readable > > > - the desktop comes up with very small icons and even changing them to > > > Icon size 'massive' does not make reabable what is written below the > > > icons > > > - all fonts are very small in all menues > > > > Looks like wrong selection of scaling in 1st time wizard (2.0 is best > > value for my eyes). > > > > Yes, I can confirm this; later the day I flashed 046 and used this; the > fonts are fine now;
OK,
>
> > > - neither AUX nor Porwer button does anything visible
> > > - USB network does not come up (yes, I know it is now 192.168.7.x)
> > > - the keys of the keyboard a very small too;
> > > - it does not even seems to charge on USB plug-in (at least the Power
> > > button has no light and in the desktop nothing visible)
> > >
> > > Please let me know what I could do or check;
>
> concerning USB networking in 046:
>
> I have had to do some things on the host side to bring the interface up
> there; and than it turned out that the usb0 interface in the FR was down
> and had no IP addr; I set this from the FR terminal and could SSH to the
> FR;
check "systemctl status networking.service" maybe it will show some hints
about why networking wasn't started for you after boot.
Working output looks like this (note that errors about eth0 not available
is because wlan was down so eth0 entry from my /etc/network/interfaces could
not be used which is not fatal for usb networking):
SHR root@gjama ~ $ systemctl status networking.service
networking.service - LSB: Raise network interfaces and configure them
Loaded: loaded (/etc/init.d/networking)
Active: active (exited) since Wed, 04 Apr 2012 22:55:47 +0200; 1
weeks and 1 days ago
CGroup: name=systemd:/system/networking.service
Apr 04 22:55:43 gjama wpa_supplicant[238]: Libgcrypt warning: missing
initialization - please fix the application
Apr 04 22:55:45 gjama networking[208]: Configuring network interfaces... Could
not read interface eth0 flags: No such device
Apr 04 22:55:45 gjama networking[208]: Failed to initialize driver interface
Apr 04 22:55:46 gjama networking[208]: ifconfig: SIOCGIFFLAGS: No such device
Apr 04 22:55:46 gjama networking[208]: ifconfig: SIOCSIFADDR: No such device
Apr 04 22:55:46 gjama networking[208]: route: SIOCADDRT: No such device
> do you want me to file a Track issue about this for 046? in the FR
> desktop the Setting-menues (Power, Position, ...) do nothing;
>
> shr_elm_softkey wasnot running; I started this by hand;
This could be related to latest changes of HOME fix, double shr_elm_softkey
execution etc.
Please check, that you have:
SHR root@gjama ~ $ cat /home/root/.e/e/applications/startup/.order
shr_elm_softkey.desktop
And that you've finished both 1st time wizards (one is from E17 itself and then
2nd shr-wizard is executed and that creates this .order file)
It could be another timing issue, because on my uSD card with latest EFL I get
/home/root/.e/e/applications/startup/.order created before E17 is fully started
and .order used to start apps (so I don't need shr-wizard to start
shr_elm_softkey
for me on 1st boot), but maybe for you it was vice-versa, but with this file
you
should get shr_elm_softkey on 2nd and later boots.
http://git.shr-project.org/git/?p=shr-wizard.git;a=commit;h=986663e39eb9c6917cd219e5a8ad8c74f20877bb
> should I fille Track issues too and/or put this into the Wiki?
Best way is to report in Trac and then add ticket numbers to test report on
that wiki (as described on that wiki :))
> > shr-image-om-gta02-20120404212944 is from staging 044 and USB charging
> > and networking worked for few people including me as reported on
> > http://www.shr-project.org/trac/wiki/StagingTests
> > but jffs2/ubifs images seems buggy when written with dfu-tool (they
> > always worked for me when written with nandwrite from SHR running on
> > uSD, but I usually use uSD).
> >
> > So maybe you can compare content of image written to /dev/mtdblock6 when
> > written with dfu-tool and nandwrite and maybe try different dfu-tool
> > version or report it to dfu-tool devs if it's really dfu-tool issue.
>
> about which 'dfu-tool' you are talking; I have flashed always with
yes sorry dfu-util not dfu-tool..
> 'dfu-util' from FreeBSD:
>
> $ dfu-util -V
> dfu-util - (C) 2007-2008 by OpenMoko Inc.
> This program is Free Software and has ABSOLUTELY NO WARRANTY
> dfu-util version 0.1+svnUnversioned directory
Latest version is 0.5 see
http://dfu-util.gnumonks.org/
I'm not using dfu-util so I've messed the name and I'm not sure when or why it
started
to generate broken fs, but I've got reports also about directories being writen
as symlinks
to some other dir and other really scary stories (and then the same .jffs2
written with
nandwrite working fine).
> what would be best for you, go on testing 046 or go back to latest
> public core version from shr-core/images? I can do both because it does
> not affect my daily FR phone;
Best way to help is to find the worst issues before it gets to
"public feed" == shr-core/images == shr-2011.07/images.
So please test shr-core-staging/latest images and feeds as described here:
http://www.shr-project.org/trac/wiki/Stabilizing
And fill your issues to trac&StagingTests page.
Cheers,
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
_______________________________________________ Shr-devel mailing list Shr-devel@lists.shr-project.org http://lists.shr-project.org/mailman/listinfo/shr-devel
