/srv/irclogs.ubuntu.com/2011/12/14/#ubuntu-arm.txt

twblilstevie: any idea what the trick is to make bluetooth work?  Specifically, http://paste.ubuntu.com/769608/01:14
lilstevietwb: 1) make sure the bluetooth hcd is in /lib/firmware01:17
lilstevie2) service bsp-tf101 start01:17
lilstevie3) cross your fingers and all extremities that it works properly01:17
lilsteviebluetooth is a pita01:17
lilstevieand does not always work01:17
twb:-(01:18
lilstevieoh main thing, make sure BCM4329.hcd is bcm4329.hcd01:18
lilsteviereminant of the old method capitalizes it, when it needs to be lower case01:19
twbDid that already01:19
lilstevieok01:19
lilsteviecheck if brcm_patchram_plus is running01:19
twbbsp-tf101 is configured to start by default, so why wouldn't it have worked already?01:19
twbYes, it's running01:19
lilsteviejust making sure01:20
lilstevienow do you have x?01:20
twbatm yes01:20
twbbut started from xinit, not a dm01:20
lilstevieok look at the bluetooth icon in the systray01:20
twbha ha, systray01:20
twbI said I have X not unity :P01:21
lilsteviehaha :p01:21
twbmainly I started X to get keyboard repeat, but it's being funny there too -- which is why I'm trying to get my bt kb working01:21
lilstevieok01:22
twbWhere "funny" means e.g. I hold Ctrl+p, and it types ^P over and over -- and keeps typing it if I release p, until I also release Ctrl01:22
lilsteviewell I know I can see the bt stuff from the gnome bluetooth manager01:22
lilsteviebut I also can from hcitool01:23
lilsteviehave you rebooted since fixing up the hcd?01:23
twbI'll try restarting that bsp thing01:23
twbYeah, definitely restarted since01:23
lilsteviethat won't really help :/01:23
lilsteviebrcm_patchram is a pita01:23
lilstevieand I haven't fully set the bsp package to handle restarting01:23
lilsteviestop the bsp package01:24
twbhow?01:24
lilsteviemake sure brcm_patchram is killed01:24
twbRighto01:24
lilstevieservice bsp-tf101 stop?01:24
twbYou know I could help yo make that an upstart job if you prefer01:24
lilstevieit is brcm_patchram actually that is the problem01:24
lilsteviebrcm_patchram sometimes needs to be forcefully killed01:25
lilsteviein fact those times when you shutdown the system, and it never seems to turn off, but just sit there.... thats brcm_patchram01:25
lilstevie:p01:25
twbOh I wondered about that01:25
twbWhen it sits as "killing all processes" ?01:26
lilstevieyep01:26
twbLAME01:26
lilsteviethats it refusing to die01:26
lilstevienow, once you have successfully killed the process, hopefully a kill -9 will do it01:26
lilstevieyou need to rfkill block it01:27
lilstevieotherwise you can't reclaim the interface01:27
twbWhy not put the rfkill in the sto rule?01:27
lilsteviethats fine, but I am not comfortable doing a -9 kill in the stop rule01:28
twbOK, then I will do it locally :P01:28
lilstevieand the rfkill must be done after the kill01:28
twbafter the kill -15 ?01:28
lilstevieyes01:28
twbThat's fucked up01:28
lilstevieotherwise the iface goes into some crazy land of fail01:28
TheMusoIs this under the 2.6.38 kernel or the android derived kernel?01:29
lilstevieboth01:30
lilstevie2.6.38 is a little more forgiving01:30
lilsteviebut brcm_patchram trashes the interface on being killed01:30
lilstevieI would like to redesign it to me more daemonish01:30
lilstevie:p01:31
lilstevielike something that will accept being asked to release01:31
lilstevierather than being shot in the head01:31
lilsteviecause the problem is that you shoot brcm_patchram in the head, and leave its initialized interface behind01:31
lilsteviebrcm_patchram will not reinitialize an interface01:32
lilstevieand an initialized interface will not be reinitialized again01:32
twbSo this is YOUR code?01:32
lilstevieno01:32
twbNot some crazy closed thing?01:32
lilsteviethis is broadcomm code01:32
lilsteviebut open broadcomm code01:33
twbAh, O01:33
twbOK01:33
twbGoddamn keyboard01:33
lilstevieanyway, after killing brcm_patchram softblocking, and unblocking cause the interface to reset because brcm_patchram wasn't there to hold its hand01:34
twbbtw is rfill supposed to be unblocked when bsp thingo starts?01:34
lilstevieshould be yes01:34
twbOK that is probably why it isn't working for me01:34
twbBecause whenever I look it's soft blocked, probably because it does that at boot01:34
lilsteviehm01:34
lilsteviemaybe I put the old version of the init.d script in there then01:35
lilstevieit should unblock it on boot01:35
lilsteviebut the old version didn't01:35
twbI've trashd your version now so I can't check :P01:35
lilstevieoh lol01:35
lilsteviewell anyway, brcm_patchram requires the interface be unblocked when it is invoked01:36
twbHeh, now I have a dozen brcm_patchram_plus's running01:38
twbI might also just patch the halt script to ignore if that proc is still running...01:39
=== twb` is now known as twb
twblilstevie: after reboot hcitool scan is working02:23
twblilstevie: I think you shipped the unblock-less version of the script02:23
lilstevieoops02:24
lilsteviesorry :p02:24
lilsteviejust so you know, the bluetooth is still very hit and miss02:25
twbUnderstood02:26
lilsteviejust don't get your hopes up02:26
lilstevieI have successfully synced my mouse to the bluetooth a grand total of once02:27
lilstevieand used it that is02:27
lilstevieI have synced the mouse many times02:27
lilstevieonly once was it usable02:28
twbI'm gonna get a fucked up back if I can't get a kb workin02:28
twbStill have my old USB one, might use that02:28
lilstevieheh02:29
twbs/fucked up/more fucked up/02:29
lilstevielol02:31
twbwow bluetooth crashed02:41
twbhttp://paste.ubuntu.com/769642/02:41
twbhttp://paste.ubuntu.com/769644/ is the init script I'm using -- lilstevie do you think I should be blocking/unblocking only one of the two bt devices?02:43
lilstevieshouldn't make a difference02:45
desrtany word yet about the transformer prime?02:46
lilstevieno02:46
lilstevieit is not looking good though02:47
desrtbootloader locked down?02:47
lilsteviehttp://androidroot.mobi/2011/12/13/thoughts-on-android-tablet-security/02:47
lilsteviewell we haven't had one in our hands yet02:47
lilsteviebut the dlupdate shows that this time even the blobs are signed02:47
desrtlame.02:49
desrthave to wait for a better tegra3 system to come along, i guess02:49
twbbluetoothd[4662]: input/server.c:connect_event_cb() Incoming connection from E8:06:88:52:C7:74 on PSM 1702:51
twbbluetoothd[4662]: input/server.c:connect_event_cb() Incoming connection from E8:06:88:52:C7:74 on PSM 1902:51
twb*** glibc detected *** bluetoothd: free(): invalid next size (fast): 0x2a7e6eb0 ***02:51
twbSo, uh, bluetoothd is doing a bad free() in oneiric?02:51
lilsteviehm02:54
twbFWIW, keyboard repeat on tty is fine on an external USB keyboard02:59
twbSo it must be something in the kb controller02:59
twbFeels weird to have a full-width keyboard for the first time in years03:00
lilstevieheh I'd believe it03:00
lilsteviethe EC driver is hacky as shit03:01
twbEC?03:01
lilstevieevent controller03:01
lilsteviecontrolls the keyboard and mouse03:02
twbSo like evdev03:03
lilstevieno03:04
lilsteviecause it is hardware03:04
twbRighto03:04
lilsteviethe asusec is the controller for the keyboard and mouse03:05
twbAh, that fucker03:05
lilstevieand a few other little things03:05
twbQuite often in the previous install it would spew printks so fast I couldn't do anything but hard-reboot03:05
TheMusoI was wondering what asusec was for.03:07
TheMusoNice to know.03:08
lilsteviethe asusec does a little more03:08
lilsteviebut that is the main thing03:08
TheMusoyup03:14
twbDoes tf101 have a hardware AES module?  And if so, does ubuntu leverage it?03:15
twbSome of my programs (e.g. mutt) seem to be hanging a lot, and my first guess is they're churning TLS03:16
twbHm, or it could just be that python is really crap03:17
twb10602 twb       20   0  8800 3568 1680 R    2  0.5   0:00.09 python -c import netrc; print netrc.netrc().authenticators('imap.cyber.com.au')[0]03:17
lilstevieyes, and not really at this point I guess03:17
lilstevienever tried03:17
lilsteviebut there is hardware aes03:18
twbSince bt isn't working atm I'm doing this: update-rc.d bsp-tf101 disable03:20
twbSo at least I can halt reliably for now03:20
lilstevieheh03:20
lilsteviefair enough03:20
lilsteviethe other stuff in the bsp is for CrOS kernel so it wont affect you03:20
twbSo next week when I come in yelling that it isn't starting, that is why ;-)03:20
lilsteviehaha ok03:21
twblilstevie: is there a way to detect (programmatically) if the dock is attached?04:15
infinityI'd assume the extra devices show up in /sys somewhere?04:19
twbhttp://paste.ubuntu.com/769703/ little /etc/cron.hourly/battery job I wrote to get a feel for battery consumption rate04:20
twbinfinity: unfortunately no, they still appear and if you cat them it complains to all the login ttys04:20
twbinfinity: so right now I think that cron job will print gank all over my screen occasionally04:20
twb(I also have a battery monitor in .screenrc, but that's not logging, so I can't look at the rate-of-change.)04:21
twbtegra-i2c tegra-i2c.3: no acknowledge; tps6586x 4-0034: failed reading at 0x20; Failed to set dvfs regulator vdd_cpu; Failed to set regulator vdd_cpu for clock cpu to 1000 mV; cpu-tegra: Failed to set cpu frequency to 1000000 kHz04:24
twb^^ any idea whart those dmesg's are about?  It sounds like it's failing to save my battery04:24
twblilstevie: btw why was apmd installed instead of acpid?04:29
twblilstevie: is apmd an OMAPism?04:29
twbAnd more importantly, is suspend-to-RAM working yet?04:30
lilsteviethere is no acpi on arm04:43
lilstevieand no suspend functions do not work04:43
lilsteviewell more correctly waking up from suspend functions does not work properly04:43
twblilstevie: well, acpi_listen can see hardware keys being pressed04:52
twbThat's how I'm triggering shutdowns right now04:52
twb(re suspend -- OK, thanks.)04:52
infinitylilstevie: Hrm, suspend is working on the ac100.  Perhaps some bits need merging between trees?04:53
lilstevietwb: my point is acpi is not really all there for arm04:54
lilstevieinfinity: no04:54
lilstevieinfinity: already spoke to ogra et al. with that04:54
lilsteviethe ac100 used some nvec stuff for it04:54
lilsteviewe don't use nvec04:54
infinityAh.04:54
twblilstevie: OK, hardware-wise I see your point.  From a practical perspective, should I uninstall acpid and install something "better"?04:54
lilstevieand, the issue with suspend is the framebuffer04:55
twb(The goal being to respond to power/volup/voldn and kb media buttons like brightup/brightdn)04:55
lilstevietwb: evdev does that :p04:55
twbI mean without resorting to gnome-power-manager or kpowerwhatever04:56
lilstevieoh i see04:56
twbIn the x86 world you just install acpid and acpi-support, but for some reason oneiric doesn't even seem to *have* an acpi-support package04:56
lilsteviewell that is a bit more difficult04:56
lilstevieand yes, that is because we don't have acpi tables04:56
twblilstevie: right now acpid is WORKING, which is partly why I'm confused.04:56
lilstevieas in, not at all04:56
lilsteviewe have a kernel maintained device tree04:57
lilsteviewhich will fill in a few of the blanks04:57
lilsteviebut not enough04:57
twbtwb@elba[Desktop]$ config.guess ==> armv7l-unknown-linux-gnu04:57
twbtwb@elba[Desktop]$ acpi_listen ==> video/brightnessup BRTUP 00000086 0000000004:57
lilstevieinfinity: anyway, after suspend, the framebuffer keeps getting suspended04:57
lilstevieinfinity: under CrOS_2.6.38 it is worse :p it doesn't even wake up04:58
lilstevieand twb right, there are some standard features which will04:59
twbAh, OK05:00
TheMusoDoes android actually suspend the tf though when you leave it or press the power button?05:00
twbSo the kernel is basically faking it05:00
lilstevieTheMuso: yes05:00
TheMusoAh ok.05:00
TheMusoVery responsive in coming back then.05:00
lilstevieTheMuso: the difference is minimal05:01
lilsteviesometimes when you wake it up it is instant, that did not go all the way to LP005:01
lilsteviewhen there is about 1-1.5sec lag, that is waking up from WB0/LP005:01
TheMusoah ok.05:03
twbAre they registers or what?05:04
twbHmm, http://www.faqs.org/patents/app/20090204837 ?05:04
lilsteviekinda05:05
lilsteviePMIC05:05
lilsteviewhich has control registers05:06
twbbtw, can I use any old mains<-->usb power brick?05:07
lilstevieno05:07
twbBugger05:08
twbI want a second one to leave in the office rather than carrying it with me every day05:08
lilsteviehow typical05:09
lilstevietrying to debug the suspend issue05:09
lilsteviecant trig the damn bug05:09
lilstevieactually05:10
lilsteviethats a good thing05:10
TheMusolol05:10
lilsteviethis is the first time I have done it dockless05:10
TheMusoTHat means something.05:10
lilsteviemaybe the bug is in the dock resume :p05:10
TheMusoOr something USB.05:10
TheMusoWHich doesn't surprise me.05:10
lilsteviehah05:10
twbWhat interconnect does the dock use anyway?  I just kinda assumed it was power + usb05:11
lilsteviea very complex interconnect05:11
twbplus a few other random pins, of course05:11
twblilstevie: custom asus one, or custom tegra one?05:11
lilstevieusb+gpio+power+i2c+i2s05:11
twb(As if USB isn't complex enough interconnect on its own :P)05:12
lilsteviethe keyboard runs off a combination of GPU+i2c05:12
lilstevieer05:13
lilstevieGPIO05:13
twbheh05:13
TheMusoOh wow, I thought the keyboard would be USB.05:13
lilsteviethe mouse is i2c and i2s05:14
TheMusoEven more weird.05:14
lilsteviewell not really05:15
twbmouse as in touchpad?05:15
lilstevieit implements a ps/2 like interface over that05:15
lilstevieyes05:15
TheMusoI guess they wanted to keep the USB free for the USB ports.05:15
lilsteviewell technically the USB controller is in the dock ;)05:15
TheMusoYeah, another UBhub...05:15
twbif I was doing it, I'd have just run the keyboard and touchpad as USB off a UHCI controller in the dock05:15
TheMusousb hub...05:15
lilsteviethe keyboard is based of nvex05:16
twbHow many ports can your typical UHCI controller have soldered onto it?  Four?  Eight?05:16
lilstevienvec*05:16
lilsteviegpio is the primary interface05:16
twbIf it was four you could just have two ports on the dock, plus one for the kb and one for the tp05:17
lilstevieTheMuso: can you tack on to that blueprint that I need to reverse the off state for the lid switch05:18
lilstevie:p05:18
lilstevieand also, right on queue05:18
TheMusolilstevie: What does it have to do with that daemon05:18
lilsteviedock+suspend == bad times05:18
lilstevieTheMuso: nothing, just it is dock related :p05:18
TheMusolilstevie: Fair enough. You hsould have write access to the whiteboard of the blueprint...05:19
TheMusoBut I can add it.05:19
lilstevieyeah I just CBF :p05:19
lilstevieI really should do a kernel blueprint05:19
TheMusoYeah that would be good, I would like to know what you have planned.05:20
lilstevieheh :)05:20
lilsteviethat kinterruptive stuff also is interconnected with the dock :(05:21
lilstevieno trace of it in my dmesg, connect dock, bam05:21
TheMusolilstevie: added.05:21
lilstevieta05:21
lilstevieok, so will not suspend with the usb cord plugged in :p05:22
TheMusolol I love it when one gets side tracked from something else because the point of discussion is interesting enough to dig deeper into a problem. :)05:24
lilstevieheh :p05:25
lilsteviewell I have been meaning to dig deeper into suspend05:26
lilsteviecause man will that push batt life to extreme levels05:26
TheMusoYep.05:26
lilstevief*** it05:29
lilstevieI cant trigger the damn bug again05:29
lilsteviethis is annoying, it is what happens every time05:29
TheMusoheh05:30
lilstevieand when i do trigger it, I am nowhere near a computer that will allow me to remote access it and get detailed logs rather than a 500ms flash05:30
lilstevieholy crap05:31
lilstevieI don't believe it05:31
twbI want to run sleepd05:31
lilstevieplugging in the usb cable, hooked to the computer stops the bug05:32
twbWhich basically just does pm-suspend if it hasn't seen keyboard input for ten minutes05:32
lilstevieunplug, bang it is back05:32
twbActually I should install it now and just configure it to turn off the backlight05:32
twbSince that's like 30% of the power drain05:32
TheMusolilstevie: weird.05:33
TheMusoAnyway, gotta run.05:33
lilstevieTheMuso: weird is right, plug usb cable in, resume bug goes away05:34
lilstevieunplug it, within 30s bug starts back05:34
lilstevielater TheMuso05:34
lilsteviegot it05:41
lilstevieTheMuso: when you are around; figured out why it locks when the usb plug is in05:42
lilstevieTheMuso: when the usb plug is in it prevents suspend. when unplugged it gets into a suspend/wake loop05:43
lilstevienow just need to figure out why wake from suspend goes into a suspend/wake loop05:43
twbmplayer says: mplayer: Symbol `ff_codec_bmp_tags' has different size in shared object, consider re-linking06:28
twbsudo mplayer http://radio1.internode.on.net:8000/117 ==> mplayer: relocation error: mplayer: symbol __aeabi_f2ulz, version LIBAVCODEC_53 not defined in file libavcodec.so.53 with link time reference06:29
twb>sad face<06:30
twbHmm, that's mplayer106:35
* twb tries mplayer206:35
twbSame issue with mplayer206:38
lilstevieok I am kinda getting a little confused06:42
micahgtwb: which releasE?06:42
lilsteviealso mplayer would be terrible on unaccelerated hw06:42
micahgthere was a compiler issues which had libav emitting extra symbols on oneiric IIRC06:43
twbI only want audio06:43
twbIt's just my scripts are set up to assume mplayer atm06:43
lilsteviemicahg: this is on oneiric06:43
micahgah, mplayer might need a rebuild if it's failing06:43
twbI could probably learn xmms2 or something but today ICBF06:43
lilstevieok, so this is what is happening06:43
twblilstevie: won't *all* video be sucky without hw accel -- not just mplayer?06:44
lilstevieas soon as the wake lock is removed (by unplugging the usb cable) suspend: sys_sync; suspend: enter suspend06:44
lilstevietwb: actually06:44
lilstevieall video will be sucky even with acceleration06:44
twbWhy?06:45
lilstevieuntil you start doing processing on the AVP06:45
lilsteviecause tegra sucks ass06:45
twbk06:45
twbMy simple-minded brain reduces that down to "hardware acceleration"06:45
lilstevieok, so basically as soon as every last piece of hw has come back from suspend; it calls back to suspend 0.o06:46
lilstevieno idea why06:46
lilstevietwb: it is a little more complex than that, the GPU is weak06:46
twbto save power duh :P06:46
lilstevietwb: yeah but it resumes from the recalled suspend after 0.310sec06:47
twbeh I am coming from matrox and intel06:47
lilstevie^^measured by the kernel timer06:47
lilstevietwb: no what i mean is the tegra GPU is really weak06:47
twbeven weaker than an i915?06:47
lilstevieunless video gets preprocessed by the AVP06:47
twbWow06:47
twbhum, ok06:48
lilsteviefor mpeg vid06:48
lilsteviethats what all those .axf files are in /lib on android06:48
lilsteviethey are programs for the avp to aid decoding06:48
twbpresumably that's only useful if you're watching video, tho06:49
twbnot e.g. playing doom06:49
lilstevieyes06:50
lilsteviecorrect06:50
twbRighto06:50
twbbtw for some reason when I rebooted out of android, the caps lock light was on, and it won't turn off06:57
twb(Which is a surprise to me; I didn't even know there WAS a light.)06:57
lilstevielol06:57
twbmicahg: there's this libavcodec-extra-53 that Provides libavcodec53, is it also likely to be buggered?07:11
micahgtwb: idk07:11
* twb tries07:11
twbanswer: it does07:13
twbEr, "libavcodec-extra-53 is also buggered"07:13
lilsteviehm07:16
lilsteviehttp://pastie.org/301442907:17
twblilstevie: how do you get that out?  netconsole?07:18
twb(assume you're still banging against suspend issues.)07:18
lilsteviebecause once you plug in the USB it triggers wake lock07:18
twbAh07:19
lilstevieit seems to fully wake up07:19
lilsteviethen bam out of nowhere suspends again07:19
twbDoes the suspend key have a down and an up event?07:20
lilsteviewhich is what that portion of the dmesg is07:20
lilstevieit isn't that :p07:20
twbMaybe it suspends before the up even arrives, so it thinks you're still holding it down07:20
twbOK07:20
lilstevieI called suspend from the power menu :)07:20
twbWhat happens if you throw away the GUI and call it from /sys ? ;-P07:20
lilstevieno idea really :p07:21
lilsteviethe only way I know to suspend from /sys isn't in the kernel07:21
twbMight be /proc I forget07:22
twbSomething like echo mem > /sys/power/state07:25
lilstevieyeah07:26
twbAnd if you cat it it tells you someting like "swap mem" to mean it supports suspend to both disk and ram07:26
twbOf course that's JUST suspending, and pm-utils and friends do all sorts of crazy shit in addition to that to work around failtastic hw07:26
lilstevieonly supports mem07:26
twblike halting bt and turning all the LEDs off and rmmoding things07:27
twbIt wouldn't surprise me in the slightest if one of those things was actually CAUSING the resume problems07:27
lilstevielol07:28
lilstevieI will try it07:28
lilstevie:)07:28
lilsteviejust need to call reboot07:28
twbI bet you get new and excitingly different problems07:28
lilsteviesomething has to be calling suspend07:28
twbJust remember to turn off the GUI and esp. gnome-power-manager first07:28
lilstevieheh07:28
lilstevieservice lightdm stop07:29
lilstevieproblem solved07:29
twbYou could just "stop lightdm"07:29
lilsteviefwiw identical result07:32
lilsteviewell surface is identical07:32
lilsteviewill check out the dmesg in 2 secs07:32
twbk07:33
lilstevieyep same result07:38
twbAw07:39
twbWell at least we know it's not any of the helper code now07:39
lilstevieyeah07:39
lilsteviewhich I already figured anyway :)07:39
lilsteviethe most I can see at the moment is a kernel owned task is calling the suspend07:40
lilstevieas part of the end of waking up from suspend07:40
twbSo-rry07:40
lilstevie:p07:41
twbYou can just tell me to STFU if I'm not helping07:41
lilstevieworth a try though to confirm07:41
lilstevieSTFU every little idea helps07:42
twbmaybe... it only happens when you hold the tablet upside down!07:43
lilstevielol07:43
lilsteviewell I may have been misinterpreting the log07:44
twbWTF07:57
twbfestival --tts book, half a sentence in it goes "=== PAUSE ==="07:57
twbThat has never happened before07:57
twbGoddammit, no bedtime stories for me tonight08:01
twbThe actual thing pausing is aplay AFAICT08:02
twbHmm, why does free -m say I only have 728MB of RAM?08:04
twbSurely it doesn't need >256MB reserved for the GPU or something? :-/08:04
twbAnyway, home time.08:05
_ThomasHmm, I have this usb wifi stick that works with open access points, but when I try to connect to encrypted ones, it fails to connect10:38
_Thomas(I'm trying to connect using the network wizzard)10:38
_Thomaserh, Network Manager10:38
ogra_is that with one of the official ubuntu images from cdimage ?10:41
_Thomasogra_: No it's linaro's ubuntu-based image, but it's using most of it's packages from the ubuntu pool10:43
ogra_that doesnt matter, they are built differently (using metapackages instaed of tasks which can result in different package/dependency selection)10:44
ogra_so you might miss something10:44
ogra_do you see any messages in dmesg ?10:45
_Thomasogra_: yes, I got some messages in dmesg10:55
ogra_pastebin them10:55
ogra_it could also be a missing kernel config option or so10:55
ogra_or missing firmware etc10:55
ogra_btw, what HW is that ?10:56
_Thomasogra_: http://pastebin.com/Qwrs3a3e10:58
_Thomasrtl818710:58
ogra_do you see it loading the right firmware (thats not in your dmesg, a full copy would have been better than a snippet)10:59
ogra_and do you have linux-firmware installed ?11:00
_ThomasI can yank out the stick, and put it back in again11:00
ogra_yeah, check if you see anything about firmware and also check if you have that package installed11:00
ogra_and again, what hardware is that ?11:01
_ThomasRTL8187, as I said above :)11:02
xranby_Thomas: which board are you using?11:03
xranbykernel source tree etc11:03
ogra_right11:04
_Thomasmy own board, kernel source tree is linux-samsung tree11:04
xranbyah right. you make the libEGL for that not yet released samsung board?11:05
_Thomas:)11:05
xranbyit is the Origen board?11:06
_Thomasxranby: No, but it's the same AP11:07
xranby_Thomas: can you check if the same bug exist on the Origen boarD?11:08
* ogra_ would guess its either a missing kernel option or some package missing 11:08
_Thomasxranby: Kind of hard, since I don't have any origen boards11:09
_Thomasogra_: Maybe, but I don't see what could be missing from the kernel11:10
ogra_i dont either since i dont know your kernel ... the ubuntu kernels have a good bunch of common options they all share and that specifically is true for external devices like USB ...11:11
ogra_(and independent of arch etc)11:12
_ThomasBut could this be USB related, given that the device is detected, and works with open APs?11:13
ogra_unlikely ... but it could for example be driver related11:13
_ThomasAnd with the regards to cfg80211, I've enabled almost everything (only debugging parts not enabled)11:13
ogra_probably you should :)11:14
ogra_might get you some more insight (even though it seriously spams dmesg)11:14
_Thomaswith regards to the driver itself, there was no options to choose from11:15
_Thomasother than mode / integrated / none11:15
_Thomasmode=module11:15
_Thomasand I chose to compile as module11:15
ogra_no, but there might be patches we have in ubuntu and you are missing11:15
_Thomasthat is true11:15
_ThomasI'm running 3.2-rc111:16
ogra_what kernel version is that ?11:16
_Thomasfairly recent11:16
ogra_ah, same we have for panda and omap311:16
ogra_that should do11:16
ogra_not sure about possible patches though, #ubuntu-kernel might be able to talk about these11:16
_ThomasI tested the same USB-stick on regular ubuntu 11.04 (x86, that is)11:17
_Thomaswith same issue11:17
ogra_aha11:17
_ThomasI had forgot about that until now :D11:17
_ThomasShould all sticks download firmware?11:20
_Thomasbecause there's nothing about firmware in the loggs11:20
_Thomasnot even about failed download/upload or anything11:21
ogra_it might not report it if its successfull11:21
_Thomasok, so it's safe to rule out firmware, then11:21
ogra_ogra@horus:~$ ls /lib/firmware/rtlwifi/11:21
ogra_rtl8192cfw.bin  rtl8192cufw.bin  rtl8192defw.bin  rtl8192sefw.bin  rtl8712u.bin11:21
ogra_thats what i have on my machine in oneiric11:22
_Thomasno 8187 there11:22
ogra_no, but often firmware files apply to multiple devices11:22
ogra_if you actually have the same prob on other HW with the same device i would go to #ubuntu-kernel and ask there11:23
ogra_oh, and there is bug 80290211:25
ubot2Launchpad bug 802902 in linux "Realtek rtl8187b wireless chipset slow speed" [Undecided,Confirmed] https://launchpad.net/bugs/80290211:25
ogra_the last comment is intresting11:25
_ThomasI don't have the b-version of the chipset, it seems11:30
=== apachelogger_ is now known as apachelogger
=== doko_ is now known as doko
ogra_doko, just playing with the ac100 you gave me .... as i thought, the kbd cable was only half plugged in12:17
ogra_armhf feels quite a bit snappier on the desktop i must say12:17
lilstevieogra_: heh yeah hf is amazing12:22
lilstevieis libreoffice working on hf yet?12:22
ogra_nope, didnt build yet12:22
ogra_patches accepted12:22
lilstevieah ok12:22
ogra_;)12:22
dokoogra_, including the mmap fix?12:23
ogra_doko, no idea if janimo included that in the precise upload from yesterday12:24
ogra_i'll upgrade to the 3.0 kernel soon12:24
dokojanimo, ^^^ ?12:24
ogra_for now i want to see how much rendering improves by using hf12:24
ogra_firefox seems to scroll a lot smoother12:25
dokolool, could you care about the flash-installer merge?12:34
ogra_doko, we are still discussiong it12:34
ogra_its not clear yet if we will switch at all12:35
dokoahh, ok, so not mine12:35
ogra_oh, wait you mean adobe flash?12:35
ogra_or flash-kernel12:35
ogra_(flash-installer is adobe, no ?)12:37
ogra_infinity, are you around today or still ill ?13:29
* ogra_ is about to roll an nvidia-tegra driver for precise restricted/multiverse and could need a package review in NEW then13:30
xranbyogra_: have you obtained a armhf version?13:40
ogra_no13:40
ogra_up to nvidia to provide one13:40
ogra_i dont see aaronp in #ac100 anymore, else i would have asked him13:41
ograarmhf rocks :)14:09
lilstevieheh14:11
xranbyogra: yes yes i find it nifty14:11
ogranow a binary driver would really be lovely14:11
xranbyogra: right now im also using 256kb default stack by setting * soft stack 256      in /etc/security/limits.conf14:12
xranbyand my armhf system ticks on fine without any zram swap tricks14:12
ograjust that line ?14:13
ogra* soft stack 25614:13
ogra?14:13
xranbyyes14:13
* ogra adds it14:13
ograanything i need ot restart for it to take effect ?14:13
xranbyit makes  pthread's use 256kb stack by default instead of 8Mb for each thread14:14
ograwell, i guess i'll reboot14:14
xranbyin my humble optinion: since a ubuntu unity2d system + browser open runs around 321 running threads the default pthread stack size do matter14:19
xranbyogra: how does things look on your side?14:19
ograwhat should be the difference with thet security conf setting14:19
ograthere is no feelable difference it seems14:19
xranbynewly started programs threads should use less memory fore each thread by default14:20
xranbyprograms can still opt in for more stack for each thread.. as i have understood it14:20
ograhm. k14:20
ograwe'll see over time i guess14:20
ograhmm, actually seems to eat less ram14:21
xranbyogra: now ulimit -a should report stack size 256kb14:21
xranbyyes, thats the idea14:22
xranbyprograms start to use less ram automagically14:22
ograit does indeed14:22
ograi wonder what the implications would be if we set it by default14:22
xranbydont set it too low. if the default are 64kb then unity will not work      around 128kb   jsome woud have trouble unzipping  stuff   256 looks fine for most applications that i have tested14:24
ograk14:25
ograwell, what i mean is ... there doesnt seem to be any default value in the file14:25
ograand i wonder if there is a reason for this14:25
xranbythe default have increased during the last years,  i think the default are set in eglibc source14:26
ograah, not a kernel thing then14:26
xranbysome years ago the default thread size on x86 was 2Mb  now its 8Mb for most architectures14:26
dmartogra, xranby: does changing the stack limit make much of a difference in practice?  I though the memory wasn't really allocated in advance... this just controls how much VMA space is reserved for stack growth14:26
ogradoko, any thoughts on the above14:26
ogradmart, well, htop shows a *lot* less ram used14:27
ograwith the stuff i have open atm i would usually hit 400M or so14:27
ograand it only reports about 28014:27
dmartInteresting.  What is that actually measuring, though?14:28
ograhtop ... i think it sums up RES14:28
ogranot sure though14:28
dmartInteresting if so14:29
lilstevieI just got LP0 suspend working on tf10114:43
lilstevie:D14:43
ograawesome !14:43
dmartogra: try http://pastebin.ubuntu.com/770100/14:43
dmartThis should help to give an idea of just the thread overhead14:43
dmartWith 8M stacksize, I get an overhead of about 8.4K per thread14:44
dmart(measuring PSS with smem)(14:44
lilstevieogra: it was something basic too14:45
lilstevieogra: wakelocks were interfering; damn android14:45
ogradmart, ok, i get 768 with my current setup14:45
ograi bet i cant change the value without a reboot14:46
dmart768 what?14:46
xranbyogra: ulimit -s 409614:46
xranbyetc14:46
ogradmart, it prints 768 threads created.14:46
dmartJust increase THREAD_COUNT ... the choice of value was totally arbitrary14:47
xranbyogra: ulimit -s 819214:47
dmartoddly though, on an ARM board it only creates 157 thread14:47
xranbythats the ubuntu default14:47
xranbydmart: why is that odd?14:47
ograwith 4096 i get only 451 threads14:47
xranbydmart: if you use 8Mb for each thread14:47
ogra8192 gets me an error14:48
ograseems i'm exceeding the limit14:48
dmartAh, OK, the kernel may require 8MB of backing per thread14:48
xranbydmart: it simply means that you have exausted the process adress space quickly by consuming 1.2gb of ram14:48
xranbydmart: run ulimit -s 25614:48
xranbyand then rerun the test14:48
dmartxranby: ah, yes of course14:49
ograbah, and now i cant set anything else but 256 anymore14:49
dmartxranby: this shouldn't affect the memory load on the system overall14:49
dmartafaik14:49
ograthats not really consistent14:49
xranbyit does.. if one application consume all ram on the system + all swap as your 768threads*8Mb14:50
xranbywould do14:50
xranbythen no program can fork14:50
xranbyand leave your system in a locked up state14:50
dmartxranby: right, with ulimit -s 256 I get 768 threads.  But we're not consuming RAM here, just virtual address space in that particular process.14:50
dmartxranby: that only happens if overcommit is enabled, and if all those threads actually use 8MB of stack14:51
ograwell, running the same stuff on my oneiric armel installed device it starts swapping already14:51
dmart99% of threads don't use anything like 8MB of stack14:51
dmart(which is just as well)14:51
ograon this armhf install and with the ulimit set to 256 it only uses 00M14:51
ogra300M14:52
dmartI guess my question is: why does changing the default stack size actually make a difference?14:52
xranbydmart: do pthread zero the stack?14:55
xranbyi have to check14:55
dmartxranby: normally, zeroing the stack would be unnecessary.  Maybe there are some specific processes allocting their threads' memory explicitly via another mechanism14:56
dmartIf so, then changing the default stack size system-wide might make a big difference to the memory consumption of some processes but not others14:56
dmartxranby: I can't see anything in the pthread_create manpage about pre-zeroing of stacks, and it obviously doesn't happen for my silly test14:58
xranbydmart: freebsd have for a long time used a default of 64Kb pthread stack size15:01
xranbydmart: i think your question are all valid.. i really dont know why the memory gets consumed15:01
dmartogra: maybe you could run smem with the two stacksize defaults, and see where the memory consumption changes15:02
xranbyin linux where we allow all programs to overcommit we usually like solutions that allow programs to grab a large block of memory and rely on the linux OOM kilelr to kill the most suitable overcommiter15:03
dmartindeed...15:03
ogrageez15:11
ograi have a load of 1815:11
ograand there goes firefox15:11
ograseems it didnt like the 25th tab i opened15:12
* ogra wonders why janimo's ac100 3.0 upload doesnt show up yet ... it should be published by now15:16
ograapt only offers me linux-image-2.6.38-1002-ac10015:17
xranbyogra: interesting indeed they are seen here https://launchpad.net/ubuntu/+source/linux-ac100/3.0.8-1.1/+build/300792415:20
ograprobably stuck in the NEW queue15:21
xranbyjanimo: https://bugs.launchpad.net/ubuntu/+source/linux-ac100/+bug/904313 any possible config issue?15:54
ubot2Launchpad bug 904313 in linux-ac100 "boot failure using linux-image-3.0.8-1-ac100_3.0.8-1.1 armhf precise" [Undecided,New]15:54
infinityogra: I'm around today.15:55
ograk15:56
infinityogra: Still feeling ill, but I only have two days left at work, I figure I'll tough it out. :P15:56
ograi was a bit distracted from the driver15:56
ograso i didnt do much about it yet, but will15:56
ograplaying with armhf on the ac100 is exciting :=15:56
ogra:)15:56
* ogra installs the 3.0.8 kernel from janimo 15:57
xranbyi have got my system bootable again by reverting back to the 2.6.38-1002-ac100 kernel15:58
ograWOAH !15:58
ograupdate-initramfs: Generating /boot/initrd.img-3.0.8-1-ac10015:58
ogra*** stack smashing detected ***: /bin/sh terminated15:58
ograAborted (core dumped)15:58
ograE: /usr/share/initramfs-tools/hooks/udev failed with return 134.15:59
ogrageez, that looks bad15:59
ograxranby, might not be the kernel at all15:59
xranbyhmm i see15:59
infinityYou see weird things on your ac100 that no one else does.  I'm convinced you have bad RAM.15:59
xranbyinfinity: me or ogra?16:00
ograwell, i poked around in /etc/security/limits.conf, might be related :)16:00
ograogra@amun:~/Downloads$ sudo update-initramfs -u -k 3.0.8-1-ac10016:00
ograupdate-initramfs: Generating /boot/initrd.img-3.0.8-1-ac10016:00
ograWriting boot image to /dev/mmcblk0p4 ... done.16:01
ograa manual run works fine16:01
ogralets see if it comes back up again16:01
* ogra reboots16:01
infinityxranby: ogra.16:02
ogra_nope, same issue here16:02
ogra_hangs at the toshiba logo16:03
ogra_janimo, did you actually test that kernel before uploading it ?16:03
* ogra_ curses ... i just prodded pitti to let it out of NEW, now the images wont boot :(16:04
infinityOops.16:04
infinitymeta's been updated too? :/16:04
ogra_indeed assuming janimo at least booted it once16:04
ogra_no, neta isnt yet16:04
ogra_luckily16:04
infinityOkay, so not world-ending yet.16:04
ogra_indeed16:05
infinityCause only people who know it's there will upgrad.16:05
infinitye16:05
ogra_yep16:05
infinityCompare configs from 2.6.38 and 3.0.8 and see if there are any obvious differences?16:06
ogra_there will surely be16:06
ogra_let me boot back into .38 first16:06
* ogra twiddles thumbs waiting for man-db16:09
ograinfinity, http://paste.ubuntu.com/770198/16:12
ograbah, sigh ... DM is gone again16:14
ogra-CONFIG_BLK_DEV_DM=m16:14
ogra+# CONFIG_BLK_DEV_DM is not set16:14
ograhalf of bluetooth too16:15
infinityYeah, but nothing in there jumps out as an obvious reason for it not booting either. :/16:15
ograwhat is +CONFIG_CPU_RMAP=y ?16:16
infinityNot sure, but it looks gone completely.16:16
infinitySince it's not replaced in the diff with a # not set16:16
ograyep16:16
marvin24ogra: maybe +CONFIG_CMDLINE_FROM_BOOTLOADER=y16:46
ogra_well, we get it from there16:46
ogra_at least we did in the past16:46
marvin24if it get the memory wrong, it will crash at logo (or shortly after)16:46
ogra_ah16:46
ogra_k16:46
ogra_i'll let a package build run over night16:46
* ogra_ isnt near any cross build machine atm16:47
marvin24wait until I checked it myself (I'm back home in an hour)16:47
ogra_k16:47
infinityogra: "Overnight"?  linux-ac100 should build in a couple of hours on a Panda or ac100, tops.16:51
ogra_yeah, but i wont start a build right now16:51
infinity(Assuming you export DEB_BUILD_OPTIONS="parallel=2")16:51
=== prpplague^2 is now known as prpplague
Sycro5_I'm having trouble getting a bluetooth USB dongle to pair with devices on the Pandaboard.  I'm running Ubuntu 11.10 and can scan for devices successfully but cannot pair with them.  With the onboard bluetooth, I am not even able to turn bt on, which is why i've resorted to the bt USB dongle.  Looking for some help getting the pairing working with the dongle, but am happy to revert back to the onboard bt if someone has any sugges18:28
ogra_i think there is a daemon missing thats not in the ubuntu archive ... search on launchpad there is a bug about bluetooth on panda18:29
ogra_it points to the upstream sourfce for that daemon iirc18:29
Sycro5_Yes, I've read that but don't fully understand it.  Does this mean that there is no way to get bluetooth working period?18:30
ogra_you have to build that daemon from source until it is packages18:31
ogra_*packaged18:31
Sycro5_hmm...do you know of any resources that describe how to do that?18:33
ogra_there should be info about this in the upstream source18:34
ogra_a README or INSTALL doc18:34
Sycro5_I'm very inexperienced in compiling this type of thing.  Do you think I can find a package that someone's already fixed?18:42
ogra_i dubt that18:44
Sycro5_bummer.  Well thank you for your help18:53
infinity        chroot /root dpkg --purge ac100-tarball-installer20:21
infinity        cp /root/usr/share/ac100-tarball-installer/zram.conf /root/etc/init/ || true20:21
infinityogra_: What's wrong with this picture? :P20:22
janimoinfinity, what's wrong whit it besides it being shell script :P ?20:31
infinityjanimo: The part where he tries to copy a file after he deletes it. :)20:37
infinityWhich, I guess, it why it needs the || true...20:38
infinity*cough*20:38
GrueMasterLooks like a perfect example of working code to me (of course I have spent a lot of time reviewing jasper).20:42
ogra_infinity, whats wrong ? it checks the error handling of cp just fine :P22:19
infinityogra_: You're kidding, I hope? ;)22:20
ogra_indeed :)22:20
infinityPhew.  I'm sick.  Don't toy with me.22:20
ogra_go back to your eglibc ...22:21
infinityYeah, yeah.22:21
infinityI uploaded a fix for ac100.22:21
ogra_saw that, thanks22:21
infinity(noticed the cp failure flash by while I was reinstalling with armhf)22:21
ogra_was on my list, i hadnt bothered to look at the code yet22:21
ogra_yeah, i saw it too today and i know about it since release day22:22
infinityHeh.22:22
ogra_(that it doesnt get installed i knew)22:22
infinityThat's okay.  I have another bug that's going to drive me nuts now (and I suspect I'll find it and fix it on my holidays because I'm OCD).22:22
infinityMy ARM machines all get several copies of udevd running until I restart udev.22:23
infinityDon't have the same behaviour on x86.22:23
infinityAnd those multiple udevs are doing angry things to CPU time.22:23
ogra_yeah, i noticed in my ac100 install today that it installed to mmcblk0p14 ...22:23
ogra_while the installed system sees only up to p722:24
ogra_(which actually is the rootfs)22:24
infinityThat's normal, isn't it?22:24
ogra_i would blame the udev in initrd to not being carried over properly or some such22:24
ogra_that the initrd sees twice as many block devices ?22:24
ogra_i doubt thats normal22:25
infinityEither way.  udev madness is on my TODO for "later".22:25
infinityI noticed it a long time ago on my mx53, but I was running the ancient Freescale kernel and blamed it on that. :/22:25
infinityJust noticed it more recently on other machines with distro kernels.22:25
infinityI guess I should have looked into it back then.22:26
ogra_hmm, i never noticed any udev weirdness until now22:26
infinityIt's been happening on my quickstart forever.22:26
infinityAlways have to restart udev after boot to kill off all the extra ones.22:26
ogra_ah, so pre-precice22:26
infinityYeah, my QS is running oneiric.22:27
infinityPanda and ac100 are precise.22:27
infinityAll show the problem.22:27
ogra_yeah, that sounds like a stick signalfd or some other weird stuff22:27
ogra_*stuck22:27
infinitySomething weird indeed.22:28
ogra_hmm, checking my fresh install i see 3 instances of udevd22:29
ogra_the latter two with a four digit pid ... the first one with 23622:30
ogra_seems the magic that scott did to carry over the running udevd from the initrd is broken22:31
ogra_yup and restarting gets me a single process22:33
infinityMight not be arm-specific, but perhaps just a weird race that slow hardware exposes.22:39
infinityI'll poke it "later".22:39
infinityBut tonight, I need to finish this eglibc merge and get it in, so I can deal with possible fallout tomorrow.22:39
GrueMasterI'll make sure to test it once it lands so you will have plenty of fallout to keep you semi-active.  :P22:45
infinityGrueMaster: Heh.  Well, it's a pretty big merge, I'm more worried about x86 fallout, to be honest.  But I'll get some time tonight to test before I upload.22:47
* GrueMaster wishes maverick on omap4 would just go away. Getting automated installs working with the same ip address everytime is a pita.22:52
GrueMasterWhen dealing with a panda pool that is.22:52
lilstevieholy crap23:03
lilstevieTheMuso: battery life with LP0 is stupedious, was in LP0 for 7 hours without dropping a single percent23:04
lilstevietablet battery 100% dock at 73%23:05
infinityGrueMaster: Can't you just cheat with a backported uBoot?23:09
GrueMasterNo, the kernel driver freaks out.  I'm already using uboot from oneiric so I can test on newer pandas (maverick only supported A1 due to lookup tables in uboot).23:10
GrueMasterAnd it is the kernel smsc95xx driver that needs to be fixed.  Natty+ uses the cpu die-id to generate a unique mac.23:11
GrueMaster(although that is only on panda, same driver on beagleXM but patch for die-id isn't upstream).23:11
infinityMaverick was 10.10?  So, you get to drop support when 12.04 ships?23:16
infinityAlmost there!23:16
GrueMasterYep.23:16
TheMusolilstevie: Wow so you fixed the bug?23:21
lilstevieyep23:22

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!