<qwebirc85021>
Hi, I've just installed alsa-utils alsa-base etc in debian but when I try to use the sound system I get cannot open mixer: No such file or directory, any ideas
<qwebirc85021>
this is on the bnn btw
<mth>
is the program trying to use the alsa or the oss mixer?
<mth>
you can check with strace which device node it tries to open
<qwebirc85021>
well I was trying to use alsamixer so I guess alsa
<rafa>
kristianpaul: still traveling
<qwebirc85021>
do I need to copy the modules from the official release?  I have debian on the nand
<rafa>
kristianpaul: i will upload the stuff when at hoome
<rafa>
kristianpaul: also i think that we will add the wikireader plugin for the gtk1 dictionary in beta4 (without the wikipedia dump, the user will need to download that file)
<mth>
it depends on whether the kernel you're using has alsa in modules or built in
<mth>
does /proc/asound exist?
<qwebirc85021>
no
<rafa>
qwebirc85021: aplay -l  should tell you if you have some sound system in your linux. You can check that first
<qwebirc85021>
aplay: device_list:235 no soundcards found. . .
<rafa>
qwebirc85021: then you need to check your kernel .. which kernel are you using?
<rafa>
qwebirc85021: do you have extra modules which you can insmod?
<mth>
if there is no /proc/asound, the alsa drivers are not loaded
<rafa>
qwebirc85021: so before to try the alsa tools, etc.. you need to be sure that sound is built inside the kernel or as modules, AND (important) you have the /dev/snd/ /dev/.. etc sound device files created
<qwebirc85021>
I'm using the kernal from the tutorial to install for the adruino sketch
<mth>
rafa: I think in most distro's the modules get autocreated by the hotplug daemon when the drivers are loaded
<qwebirc85021>
there is no /dev/snd
<qwebirc85021>
I don't have connectivity on my nanonote right now but later I was going to do a apt-get dist-upgrade I wonder if that will install the necessary stuff
<rafa>
mth: modules? or you mean device files>
<rafa>
?
<qwebirc85021>
oh whell in the directory /dev/ there is no file or directory called snd
<mth>
rafa: sorry, yes device nodes are created
<qwebirc85021>
for those of you whose modules are built into the kernal where did you get your kernal
<qwebirc85021>
sorry
<qwebirc85021>
I mean who have
<qwebirc85021>
alsa built into the kernal
<qwebirc85021>
I have to go because I am at internet cafe and have to go home before weather gets too nasty because I forgot my coat today
<qwebirc85021>
you have all given me some good ideas and things to reaearch
<qwebirc85021>
research
<rafa>
qwebirc85021: i have sound modules
<rafa>
qwebirc85021: if you wantget back i can tell you how to build the kernel only if you need that
<qwebirc85021>
oh yes I think thats what I need to do
<qwebirc85021>
is there a wiki entry I can look at about building the kernal?
<qwebirc85021>
oh Really gotta go now,  I'll be back another time thanks for your help
<wolfspraul>
xiangfu: no, not china. I also have this problem on the buildhost machine in Bavaria :-)
<wolfspraul>
the problem is that for all new applications we are bringing into openwrt, the ones in openwrt-packages.git on the qi server, there is no functioning mirror
<wolfspraul>
so my plan is to upload all sources from the dl/ folder into downloads.qi-hardware.com/sources (same as OpenWrt)
<wolfspraul>
and then add a scripts/localmirrors file pointing to that URL
<wolfspraul>
what do you think? does this sound good?
<xiangfu>
sure.
<wolfspraul>
well we have to be careful that it is in line with the OpenWrt policies, general free software ideas and the GPL
<wolfspraul>
but I think it should be OK. if I misunderstand something in the mirror system let me know, I'll set it up like this for now
<wolfspraul>
xiangfu: hmm. maybe localmirrors is not good because it will always try that first, thinking 'local' == 'fastest'
<wolfspraul>
well there is no other way to get it in, unless we patch download.pl
<wolfspraul>
I will try scripts/localmirrors for now, I think the mirrors are only invoked if the true upstream URL fails, so might as well try the Qi server first...
<xiangfu>
wolfspraul: I found there is a "LOCALMIRROR" in 'menuconfig'
<xiangfu>
wolfspraul: yes. seems it will alwyas try localmirror first.
<DocScrutinizer>
well, isn't that the primary purpose of local mirrors?
<DocScrutinizer>
plus I seem to remember you have to rsync on a regular schedule
<DocScrutinizer>
weren't there extensive discussions about that on #openmoko-cdevel, about how to mirror the bearstech servers as they frequently were down?
<tuxbrain2>
countdown for NanoNote Nanoware Especial edition, 1h 15m left for launching.
<kristianpaul>
rafa: sure i have lots of dumps here :)
<jluis>
looking the video :)
<lekernel>
tuxbrain2, nice :)
<lekernel>
good that it has a GUI in the end, even if Xorg-based
<tuxbrain2>
hehehe, thanks lekernel :) comming from you this words are music to my ears :)
<tuxbrain2>
count down 20 mins
<tuxbrain2>
Tuxbrain<->Nanowar in sync for the launching
<viric>
tuxbrain2: felicitats! T'ha quedat de collons
<tuxbrain2>
gracies :)
<kristianpaul>
tuxbrain2: bien  por el video :)
<tuxbrain2>
must leave! spread spread
<aisa>
bartbes: are you online?  I want to ask you about the wordgrinder port in qi-packages.
<bartbes>
epic timing
<bartbes>
yes, I am
<aisa>
huzzah!
<bartbes>
or am I?
<aisa>
I see wordgrinder marked broken for 30 days.
<bartbes>
oh heh
<aisa>
the commit message says waiting for an upstream patch to curses.
<aisa>
can you give me the backstory?
<bartbes>
well, that upstream patch is there, I believe
<bartbes>
but in some mysterious way my patchfile broke
<bartbes>
and... I got distracted
<aisa>
May I offer to work on this port for you?
<bartbes>
well, why not
<bartbes>
actually
<bartbes>
you only need to fix the patch file
<bartbes>
and then it runs
<bartbes>
the menus themselves would need to be optimized
<bartbes>
but otherwise, it works
<aisa>
they are too large on this device?
<bartbes>
it has been on my nn for a month now ;)
<bartbes>
yeah
<bartbes>
though maybe the new console font fixes a lot of that
<aisa>
can you tell me what problem you had that caused you to mark it broken?
<aisa>
so I can be aware if I see it.
<bartbes>
well, I was waiting for that upstream patch
<bartbes>
which was applied about 3 days later, I believe
<aisa>
I'm running an old image, I may not have this fix.
<bartbes>
the fix is in one of the packages
<aisa>
I won't be able to update my image until next week, alas.
<aisa>
oh, better.  Which one?  curses?
<bartbes>
yes
<bartbes>
ncursesw was needed
<bartbes>
so I did some poking around
<bartbes>
got it to build
<bartbes>
worked on it with one of the openwrt guys
<bartbes>
til it integrated nicely with ncurses itself
<bartbes>
and then he committed it, though delayed
<bartbes>
iirc, that is
<bartbes>
:P
<aisa>
^_^
<bartbes>
if you want I can look into the patch file myself
<bartbes>
(basically I'd just create a new one)
<aisa>
I started already.  I remember reviewing the patch and seeing it was reasonably simple.
<bartbes>
it sure is
<bartbes>
I just needed to change the build configuration a little
<aisa>
After today I'm going to be away from my computer for four days.  I'll only have my NanoNote, and I'd like to have wordgrinder so I can experiment with writing on the NanoNote.
<aisa>
So hearing that it is a simple fix, I'm going to work on fixing it today to meet my deadline.
<aisa>
look!  A patch failure!
<aisa>
I know I can run package/$PACKAGE/prepare
<aisa>
but I sure would like to split that into untar/patch
<aisa>
so I can do the patch stage myself at times like this...
<aisa>
I haven't run it on my device yet, doing that now.
<aisa>
It compiles :-)
<bartbes>
also, how easy is it to run a gp2x game on the nn?
<aisa>
bartbes: I get a segfault somewhere initializing the terminal.
<bartbes>
did you install the new ncurses package?
<aisa>
it leaves the terminal a mess, so I have to log out.
<aisa>
I installed the one I built, libncurses5w.
<bartbes>
(and ncursesw)
<bartbes>
I mean plain ncurses too
<aisa>
I probably didn't get that one.
<bartbes>
(it built too, because it is a dep of ncursesw)
<aisa>
ok, libncurses updated from 5.7-2 to 5.7-3, same error.
<aisa>
though I should perhaps try rebooting the machine...
<aisa>
bartbes: it is the same, alas.
<bartbes>
:(
<bartbes>
I guess I should rebuild and see for myself then
<aisa>
Thank you, I would appreciate knowing how it behaves for you.
<bartbes>
well, if upstream did in fact change it in place
<bartbes>
the changes could be the thing killing it
<aisa>
Looking at the differences between your patch and mine,
<aisa>
there are only whitespace changes.
<aisa>
the reason your patch wasn't applying cleanly was difference in whitespace in context lines.
<bartbes>
I got that from reading the diff, yes
<aisa>
It doesn't prove this isn't true, but I do wonder if that was why it was updated in place,
<aisa>
to fix source code problems that didn't show up in the executable.
<bartbes>
orly?
<bartbes>
(not to be taken seriously)
<bartbes>
it would be weird, yes
<aisa>
it is a guess, and not a particularly useful one.
<bartbes>
well, it's compiling
<bartbes>
or well, preparing to compile
<bartbes>
which always seems like that's the thing taking the longest
<aisa>
I'm glad it is one step further than it was yesterday.
<bartbes>
... I forgot to select it
<aisa>
ha!  right.  That annoys me, that you say "do this to this package" and it comes back and says "you couldn't possibly mean that..."
<aisa>
SHUT UP COMPUTER AND DO AS I SAY!
<bartbes>
"WARNING: Totally ignoring what you said"
<bartbes>
now ehm
<bartbes>
where in the menu was it
<aisa>
utilities => editor
<aisa>
and remember lua too, in languages=>lua
<bartbes>
not.. there
<aisa>
./scripts/feeds install -a ?
<bartbes>
yeah, i guess that is needed then
<bartbes>
aisa: gtg, sorry
<aisa>
Thank you for your help today, I really appreciate it.
<bartbes>
thank you for allowing me to be productive without doing anything ;)
<aisa>
Anytime!
<wpwrak>
tuxbrain_away: heya ! i see that you got the counterweights ! :) one thing you want to check is the plastic glued on them. i'm not entirely sure of the glue i used. if any fell off, just glue them back on.
<rafa>
nanowar
<rafa>
amaizing stuff and band
<kristianpaul>
and jlime :)
<rafa>
yeh, hehe but it seems that the nanowar has a really complete multimedia stuff of the band
<rafa>
so it has a lot of hours of fun
<kristianpaul>
:p
<bartbes>
aisa: did I just read you have a problem with cmake?
<aisa>
in a manner of speaking, yes.
<bartbes>
well, I doubt I'm using any new features
<bartbes>
so please try lowering the version
<aisa>
I am running debian 5.0, which includes cmake 2.6
<aisa>
and nlove asks for 2.8.
<aisa>
oh, wonderful, I will try this.
<aisa>
It would be personally convenient to me if we could use a stable debian as a build platform,
<aisa>
but I realize this gets harder to do as the years go by.
<aisa>
years between releases, that is.
<bartbes>
the biggest problem I have with 'the debian way' is that you always get stuck with old packages
<bartbes>
which is especially annoying when talking about stuff like firefox
<bartbes>
(or chromium, which is developing even faster)
<aisa>
I strongly suspect I'll be running testing because of this,
<aisa>
I can't imagine a group of package maintainers settling for debian's release schedule.
<elricsfate>
hey guys
<elricsfate>
trying to reflash my ben using usb boot and I run to a problem on the last step
<elricsfate>
Usage: nprog (1) (2) (3) (4) (5)  (1)start page number  (2)image file name  (3)device index number  (4)flash index number  (5) image type must be:  -n:no oob  -o:with oob no ecc  -e:with oob and ecc
<elricsfate>
can someone PLEASE help??
<elricsfate>
anyone? :/
<rafa>
elricsfate: please
<rafa>
give us the complete command tht you are trying
<elricsfate>
any OS suggestions for the nano note? Thinking about switching over to Debian
<wpwrak>
rafa: the problem with usbboot is that there seems to be a bug in the parser. i got the same error. i worked around it by renaming the file. not sure if this is fixed already. the usbboot i have is from march.
<wpwrak>
xiangfu: heya ! do you know who's in charge of usbboot ?
<xiangfu>
wpwrak: me. :)
<wpwrak>
gotcha ! ;-))
<wpwrak>
there seems to be a problem with the parser. when someone follows the flash instructions, the last command, flashing the .ubi file, fails with
<wpwrak>
(looking up the error message ...)
<wpwrak>
"not enough argument."
<wpwrak>
interestingly, it works after renaming the .ubi file, e.g., to "foo"
<wpwrak>
now, i used the may 5 version. i looked at the changelog, and i saw that there was some command line parser change later in may.
<wpwrak>
do you think this solved also this issue ?