![]() |
2011-02-07
, 22:04
|
Posts: 29 |
Thanked: 5 times |
Joined on Dec 2010
@ New Delhi, India
|
#712
|
No, sorry, this is absolutely useless, it has everything until the point where it starts getting interesting. The part missing is what follows in log starting from end of this log when the actual problem with h-e-n connecting happens, until - and including - the trailing part you posted before.
Honestly we can't debug a problem from a log taken when the problem doesn't happen. What's needed is a full log of an example of the problem, not an arbitrary log of system startup until the point where we would start to get into trouble and then stopping there.
/j
![]() |
2011-02-07
, 22:19
|
Posts: 3,074 |
Thanked: 12,964 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#713
|
![]() |
2011-02-07
, 22:44
|
|
Posts: 2,222 |
Thanked: 12,651 times |
Joined on Mar 2010
@ SOL 3
|
#714
|
sorry for the patchy posts. please find attached the complete log in the attachments
hope you can help
thanks
![]() |
2011-02-08
, 12:08
|
|
Posts: 4,365 |
Thanked: 2,467 times |
Joined on Jan 2010
@ Australia Mate
|
#715
|
![]() |
2011-02-08
, 12:17
|
|
Posts: 2,222 |
Thanked: 12,651 times |
Joined on Mar 2010
@ SOL 3
|
#716
|
want to know if anyones got a wireless mouse or keyboard working. ive tried it with no luck..
![]() |
2011-02-08
, 12:30
|
|
Posts: 220 |
Thanked: 66 times |
Joined on Aug 2010
@ Melbourne, Australia
|
#717
|
![]() |
2011-02-08
, 12:51
|
|
Posts: 4,365 |
Thanked: 2,467 times |
Joined on Jan 2010
@ Australia Mate
|
#718
|
Please read complete problems thread, there are reports about success.
please read post #9
((hint: a wireless mouse and kbd usually isn't much different to a cable variant))
Thanks
/j
![]() |
2011-02-09
, 16:14
|
Posts: 37 |
Thanked: 3 times |
Joined on Jan 2011
@ Polska
|
#719
|
![]() |
2011-02-10
, 15:25
|
Posts: 29 |
Thanked: 5 times |
Joined on Dec 2010
@ New Delhi, India
|
#720
|
I see it's hard to get a complete log from dmesg. Sorry my fault.
Please
install sysklogd, [ apt-get install sysklogd ]
reboot,
check if you got a proper /var/log/syslog file [ tail /var/log/syslog ]
start h-e-n,
if you bother, insert a note about the fact to syslog [ logger '###########h-e-n gui started#######' ]
plug in your problematic device,
click speed, vbus in h-e-n GUI
if you bother, insert a note about the fact to syslog [ logger '###########h-e-n vbus clicked#######' ]
wait 15 seconds
click enumerate in h-e-n GUI
wait another 15 sec
close h-e-n
send the file here [ cp /var/log/syslog someplace/h-e-n_syslog.txt; attach someplace/h-e-n_syslog.txt to a post here ]
don't forget to reset the syslog file every now and then ( once a week? [ echo >/var/log/syslog ]), or uninstall sysklogd pkg eventually. If you don't either, your rootfs will fill up eventually, that's not a good thing long term.
Thanks again for helping with this, and sorry for my lack to notice what's the problem with those logs.
cheers
jOERG
Honestly we can't debug a problem from a log taken when the problem doesn't happen. What's needed is a full log of an example of the problem, not an arbitrary log of system startup until the point where we would start to get into trouble and then stopping there.
/j
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N