<wpwrak>
congratulations ! :) now that they "know" you, it should be much easier
<wpwrak>
the passport scan is a bit of a routine thing. a lot of places want that for credit card payments from abroad. and of course, even more so if from "strange" countries :)
<rjeffries>
lekernel thanks for the Aleksander Zawada report. so cool. I shared your blog link on Google+
<DocScrutinizer>
aw, hey still here :-D
<aw>
DocScrutinizer, hi yes, strange.
<aw>
why total members are such few? strange!
<DocScrutinizer>
mega netsplit
<DocScrutinizer>
[2011-09-21 08:53:02] [Benutzer] There are 41 users and 6379 invisible on 1 servers
<DocScrutinizer>
I can tell you must be on kornbluth.freenode.net
<DocScrutinizer>
other servers are all the same, docscrutinizer51 not here but on another server with similar symptoms
<aw>
hmmm
<DocScrutinizer>
so it's not like "our" server got orphaned, it's like whole freenode fell apart
<DocScrutinizer>
grrr mega netsplit
<DocScrutinizer>
this is kornbluth, but on barjavel situation is all the same. Seems all servers got disconnected from each other
<DocScrutinizer>
[2011-09-21 09:13:30] <KindOne|kornblut> You can connect to one of the US servers, or just wait it out - http://freenode.net/irc_servers.shtml
<DocScrutinizer>
[2011-09-21 09:33:11] <KindOne|kornblut> looks like the EU hub went offline, this was not planned
<DocScrutinizer>
WB everybody
<viric>
argh.
<viric>
error building uboot's mkimage
<viric>
/nix/store/9b3q62czfh5zld9zg2p8sbk65hkbvpzi-binutils-2.21/bin/ld: errno: TLS definition in /nix/store/vxycd107wjbhcj720hzkw2px7s7kr724-glibc-2.12.2/lib/libc.so.6 section .tbss mismatches non-TLS reference in fit_image.o
<viric>
uboot people wrote fit_image thinking of a very specific libc?
<viric>
maybe thinking 'errno' is not in TLS?
<viric>
hm it's a matter of order in -I / -idirafter
<kyak>
viric: you can have a look in the git repo for who makes the nanomap
<viric>
ok ok. I thought maybe she would be here
<DocScrutinizer51>
wb everybody
<tuxbrain>
Hi all :)
<wolfspra1l>
tuxbrain: tuxbrain!
<viric>
hej tuxbrain
<kristianpaul>
wb tuxbrain
<wpwrak>
tuxbrain: btw, we can discuss this here :) other people may like spi, too
<tuxbrain>
sure, summarizing I have the goal to communicate NN and Arduino though SPI (using UBB) for the OSHWCON 2011 this weekend on Madrid. I ask for help to wpwrak to develop the NN part an console app (master) that can read/write strings trough spi and that can be piped. I will focus on the arduino part (slave) to do the same. we will start with fixed chars strings to avoid wasting time in defining ends of transmision etc protocols. but will be implemented
<tuxbrain>
in the future to be able to transmit whatever size strings or chunk of bytes.
<tuxbrain>
The main goal is to mount a NN here http://www.youtube.com/watch?v=NAiXv0Nvt0E and make the NN a brain/HMI enchancement, of course due this can be applied to any arduino board alot of other uses can florish from that.
<tuxbrain>
but to focus the objective before saturday is to have test at least the send/reiceve of for example a 4char string form MM to an Arduino board, and make it documented to make it reproducible with no need of in deep knowledge of the whole thing, just download the console app, c&p the arduino code, connect UBB-ISCP cable and work. Any help will be really really really appreciated
<wpwrak>
you need to edit the signal assignment at the beginning. you may also want to check the timing. finally, you must decide if setting the I/O's to input at the end is really what your device likes to happen.
<wpwrak>
(should be fine as long as nSS isn't on MMC_CLK. all the other MMC signals have a pull-up, which means that nSS is deasserted)
<wpwrak>
i shuold add that this is completely untested ;-)
<tuxbrain>
I will try along this week. I will report my success/fails
<wpwrak>
good luck ! :)
<wpwrak>
i'll be afk for a bit now
<RandomUser4>
Hello. Not sure this is the adequate channel but here goes. I've recently assembled a new computer. I have a problem: I can run each of both 2GB RAM sticks on their own but not both at the same time. Win 7 Home Premium x64. I've been reading a lot on the matter, but no clear solution so far
<RandomUser4>
The computer gets a BSOD some minutes after Windows logs in when both sticks are in, although yesterday I managed to run it for hours, until I turned it off, without any issue.
<Artlav>
Hello.
<Artlav>
On my nanonote the screen suddenly started flickering, starting from u-boot and on. What could be wrong?
<larsc>
what kind of flickering? low or high frequency? blacklight or screen contents?
<Artlav>
Content. In uboot the text lines jump up and down, later every second line moves a pixel up and back. High frequency.
<larsc>
hm
<Artlav>
In mc black lines run on the right side of the screen, and the impression is of shaking up and down.
<larsc>
does it change if you push the case above the keyboard down?
<larsc>
next to the power button
<Artlav>
It changes a little. Too much and all stops and screen starts to go white.
<larsc>
hm, looks like a problem with the screen connector
<larsc>
you could try to remove the front cover and try to check whether the cable is loose and reconnect it if necessary
<Artlav>
Anything unusual to take care of in disassembly?
<larsc>
nope. there are 4 screws which have to be removed
<larsc>
two at the outedges at the front two under the battery cover
<Artlav>
Does not seem to help. It stopped getting worse but didn't got better.
<wpwrak>
heh, bug reports with a youtube video. that's new :)
<Artlav>
Better than "screen flickers", no?
<wpwrak>
hmm, odd symptoms. may be a failing hsync line. let's see where it is located ...
<wpwrak>
not every exposed between ben and lcm. and on the lcm itself ...
<wpwrak>
nope, not very exposed there either
<wpwrak>
one possibility would be a hairline crack in the FPC. that would be fairly fatal problem :-(
<wpwrak>
you should be able to still get the ben to work for a while by pressing the cable at just the right spot and in the right way. but the crask is likely to get worse with time.
<Artlav>
No pressing or bending of the cable itself seems to affect anything. Can there be something wrong on the screen side of it?
<larsc>
it has the same type of connector on the screen side, so in theory yes
<wpwrak>
of course :) it seems a lot less likely, though. there is also a FPC in the screen. it's ben mainboard --FPC--> PCB in the display--FPC-->LCD module
<larsc>
but you'd have to pull the cable pretty hard to get it loose
<wpwrak>
larsc: you mean the FPC between ben main pcb and the LCD's PCB ? that one looks very much as if it was soldered to the PCB. of course, with enough force, it will come off ...
<larsc>
if you had a scope you could check the lcd signal for irregularities
<Artlav>
Nothing suspicious inside the screen part. No scope.
<Artlav>
Can there be some other reason? If i loosen the cable a little, all kinds of artefacts start to appear, but the flicker is always there. As if it was from somewhere else.
<wpwrak>
that would suggest the problem is at a different place. could be a bad solder joint or a hairline crack in a trace.
<wpwrak>
or some chip's driver failing. not sure how like that is, though. it must happen occasionally :)
<larsc>
it looks a bit as if there is jitter on the lcd clock and some edges are missed
<larsc>
eg. blue truns red
<Artlav>
Is there any documentation on prior nanonote hardware failure modes? Sounds like i have a unique case on my hands.
<larsc>
one thing you could try is to see if there is any change if you downclock the lcd clock
<larsc>
but that would require a custom kernel
<wpwrak>
lcd failure has occasionally been observed before. but i don't think we have a case where it's clear that it looked like that. (maybe it did, maybe it didn't)
<Artlav>
Custom kernel is not a big problem, what to do?
<wpwrak>
so the video is indeed quite useful :)
<wpwrak>
you could try to press on the contacts of the FPC connector on the ben's PCB with a non-conducting object
<larsc>
Artlav: in arch/mips/jz4740/qi_lb60.c reduce qi_lb60_video_modes.rate
<wpwrak>
that would reveal bad solder joints, cracks near the connector, and anything fishy inside the connector
<wpwrak>
you'd be looking for hsync or maybe the pixel clock
<wpwrak>
yeah, slowing things down could also be useful. you never know ...
<Artlav>
board-qi_lb60.c ? There is refresh in it, but no rate. refresh=30.
<larsc>
yes. refresh sorry
<Artlav>
Reduced to 20. Compiling...
<Artlav>
Funniest thing is Murphy's law - just as i seriously started combing the software and streamlining the stuff up, the hardware suddenly failed!
<Artlav>
What do you know, half of the problem is gone.
<Artlav>
It no longer goes up and down, but the lines are still here.
<larsc>
half of the problem?
<larsc>
hm
<Artlav>
The cord is a part too - now there is a clear relation between pressures on it and the amount of lines. But no pressure to remove them completely.
<larsc>
try to only apply pressure to the pins that go to the pcb
<wpwrak>
that's a very strange one. looking closer at the video, the background color varies but the forground text looks pretty stable
<wpwrak>
could there be conductive contamination ? metal dust or such ?
<larsc>
wpwrak: if you have a series of white pixels only the first and the last will change color
<wpwrak>
larsc: what i mean is there there's strong horizontal distortion (brightness and sometiomes color)Â Â in the background but none in the foreground. pretty weird.
<Artlav>
No longer sure about "clear" relationship. The lines seem to up and ebb by themselves whether i touch the cord or not.
<Artlav>
A sub-pixel shift. Starting from some line everything is shifted right by a subpixel - that's what these lines are.
<Artlav>
The text and background changes colour and shifts right a little.
<Artlav>
Starting from approximately 100 by x.
<Artlav>
Clean cut-off.
<Artlav>
There is a tiny black dot at the left side of each line.
<Artlav>
Almost as if a clock is skipped and a pixel missed, with the rest send in regular order.
<Artlav>
And it's not limited to video - the sound now have tiny chirps in it, the higher the pitch the worse.
<Artlav>
Maybe the problem is somewhere else entirely?
<wpwrak>
interesting .. what on earth did you do to your ben ? :)
<wpwrak>
does USB still work ?
<larsc>
it's probably interference surveilance van outside
<larsc>
it's probably interference from surveilance van outside
<Artlav>
USB - yes, kernel flashed OK.
<Artlav>
And to use the oldest phrase - i didn't do anything.
<wpwrak>
or that large flying saucer hovering over the house. they're probably adjusting the abduction beam.
<wpwrak>
(USB) that would suggest the system clock is okay
<Artlav>
Not to hardware anyway. I tried all kinds of software experiments, like 64Kb pages and dynamic ticks.
<Artlav>
And last UFO around here was a hot air balloon in the night.
<Artlav>
There seems to be a relation of line intensity to the CPU usage.
<wpwrak>
notes that suspicious flying objects are a frequent occurrence in Artlav's vicinity
<wpwrak>
maybe it's a power instability
<wpwrak>
hard to debug without a scope, though
<wpwrak>
well, you could put some resistor, say 33 Ohm, between 3.3 V and ground and see what happens.
<kristianpaul>
i havent seems anything like that, even when i dealed witht that lcm cable semi-loose for a month
<Artlav>
I tried it on USB cord and no battery, no changes.
<kristianpaul>
remenbering lcm have its own firmware right?
<wpwrak>
could be a problem on the secondary side of the regulator
<Artlav>
Sound problems cleared - software issue in gmu.
<wej>
what issue?
<Artlav>
No idea. chrooted into the old system - good sound. back - chirps in sound.
<Artlav>
In same system. So, not likely to be a hardware thing.
<Artlav>
Ok, 22 Om resistor between GND and + of battery slot did nothing.
<Artlav>
The lines seem to get more and more intense as the time go.
<wpwrak>
is the downstairs neighbour experimenting with strong magnets or such ? we had that once at the university ... our sysadmin, sun support, etc., were getting gray hair. i suggested that it was time to seek the help of an exorcist, ... then, a few days later, our sysadmin had lunch with the folks from the lab below ours and they told him about their cool experiments ...
<kristianpaul>
trying to be free gravity? ;)
<Artlav>
Unfortunately, the issue occurs on both ends of quite a large city, so surroundings are hardly the problem.
<kristianpaul>
:)
<Artlav>
Further downclocking do nothing.
<Artlav>
There is a definite CPU load relation - with video playback the whole right 2 thirds of the screen is in distorted flicker, with a picture viewer it's a bit of lines, with just the terminal its a few lines.
<Artlav>
The blanking go into all-white every odd time.
<Artlav>
Or not...
<Artlav>
If i look at a picture of a circle, then the center of the screen is in lines, while the up and bottom is not. More image - more lines.
<Artlav>
Yes, related to amount of image on the screen, and possibly related to CPU load.
<Artlav>
I guess the real question is - is it worth buying a new one now, or would there be a better version soon?
<Artlav>
Well, thanks all for helping and good night.
<wpwrak>
Artlav: nothing new coming anytime soon. so another ben seems to be best choice.
<ignatius->
Can anyone recommend a good MP3 player for the Ben?
<AwAyla>
ignatius-: GMU
<ignatius->
I'ved tried GMU. It doesn't play MP3s fast enough. It "skips"
<wej>
no, it plays mp3 just fine. if you have compiled the mp3 plugin that is
<ignatius->
Yes, I have.
<wej>
with any bitrate up to 320 kbit
<ignatius->
Hmm.
<wej>
then you did something wrong. my guess is that you have built the mp3 decoder with floating point math
<ignatius->
Ah. How do I circumvent that?
<wej>
by telling mpg123 to build with the fixed point decoder
<ignatius->
How do I do that?
<wej>
you need to tell the configure script to do that, otherwise it will compile with float, which does not work on a cpu without an fpu
<ignatius->
Ah.
<ignatius->
No configure script. Is there a CFLAG entry for that?
<wej>
the decoder comes with a configure script, i am 100 % sure of that
<ignatius->
So, where do I find a version with a configure script? Any idea?
<ignatius->
Thanks, BTW.
<wej>
there is no version of gmu with a configure script
<wej>
i am talking about the mpg123 decoder
<ignatius->
Ah. Ok. But, I thought GMU uses it's own mpg decoder? At least there is in the source tree... or appears to be..
<wej>
Gmu uses mpg123 for decoding mp3, if it is configured with mp3 support
<wej>
of course it has to implement support for that library
<ignatius->
Ok. So just recompile a version of mpg123, than?
<wej>
which is why there are files  for that in the Gmu source
<wej>
yes
<ignatius->
Ok. Thanks, man. I appreciate it.
<wpwrak>
hmm, fun spam: "New LED Candle bulb here:" "Advantages: 1.Patented product!"Â Â somehow their marketing doesn't seem to be very targeted :)
<mth>
ignatius-: buildroot passes this option to mpg123 configure: --with-cpu=generic_nofpu
<ignatius->
Ok. Yeah, the package version of "GMU" fails to compile. As do every other package for some reason.
<ignatius->
On my desktop, I mean. I'm compiling it on the Ben.
<qi-bot>
[commit] Werner Almesberger: m1/perf/sched.c: revamped to handle static registers correctly as well (master) http://qi-hw.com/p/wernermisc/8f82a0e
<qi-bot>
[commit] Werner Almesberger: m1/perf/: "spotless" target that also removes the "main" executable (master) http://qi-hw.com/p/wernermisc/23c7bd6