**** BEGIN LOGGING AT Wed Jan 26 02:59:57 2011 **** ENDING LOGGING AT Wed Jan 26 04:23:39 2011 **** BEGIN LOGGING AT Wed Jan 26 06:04:15 2011 Jan 26 06:13:40 exit Jan 26 10:31:17 rsalveti, GrueMaster efl launcher I gave back a few hours after I saw it failed to upload. LP does not do that by default, and I am not sure why it failed in the first place Jan 26 12:00:21 janimo_: oh, ok, good to know Jan 26 14:13:07 http://www.fit-pc.com/trimslice/ Jan 26 14:13:10 nice ! Jan 26 14:13:30 ogra: heise reader ;-) Jan 26 14:13:35 heh Jan 26 14:13:38 yeah Jan 26 14:32:29 Now that's a proper computer, in an appropriately shiny plastic case. Jan 26 15:21:39 sorry for the noob question, when starting qemu, is there something i can place in: "qemu-system-arm -M versatilepb -cpu cortex-a8 -kernel ./vmlinuz -hda .img -m 256 -append "root=/dev/sda mem=256M devtmpfs.mount=0 rw" " to prevent the decktop from loadind (just give me command shell) thnx Jan 26 15:24:07 between the quotes after append add text as a keyword Jan 26 15:24:43 the login manager checks for that before firing up Jan 26 15:30:22 ogra: sorry for being thick, if your talking to me im lost i dont understand what you mean, could you give me an example? and if you were not responding back to me im sorry. Jan 26 15:30:47 change rw" to rw text" Jan 26 15:30:58 in the line above Jan 26 15:31:18 ogra thnx: i owe you coffie Jan 26 15:41:38 ogra: can i ask you one more thing? My machines hostname is Homefix, after running .img on my phone the promt is "dad@localhost" instead of "dad@Homefix. I have my /etc/hosts file setup correctly "127.0.0.1 localhost Homefix".I have /etc/hostname setup correctly "Homefix" is my problem here in the chroot startup script here: Jan 26 15:41:40 echo "Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4" Jan 26 15:41:49 echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf Jan 26 15:42:03 echo "nameserver 8.8.4.4" >> $mnt/etc/resolv.conf Jan 26 15:42:11 echo "Setting localhost on /etc/hosts " Jan 26 15:42:20 echo "127.0.0.1 localhost" > $mnt/etc/hosts Jan 26 15:42:32 echo "127.0.0.1 localhost" > $mnt/etc/hosts Jan 26 15:42:34 ? Jan 26 15:42:46 localhost always needs to be there Jan 26 15:42:54 ok thns Jan 26 15:43:20 adding a line like: 127.0.1.1 Homefix Jan 26 15:43:35 to /etc/hosts should give you the desired outcome Jan 26 15:45:30 ok thought i did that try again thnks Jan 26 15:46:03 (note the 1.1 at the end of that IP) Jan 26 15:46:08 no i didnt just noticed the 1,0 Jan 26 15:46:20 1.1 Jan 26 15:58:26 ogra I promise only 1 more quest. How come when starting the chroot in my android terminal, i get the promt "root@localhost" the i login as dad and get, "dad@localhost", I start vncserver as dad@..., then sesssion starts, i use vnsviewer set up as dad for "nik", localhost for "hostname", my vnc password then connect. I get to desktop logged in as root and the root desttop. I have setup Jan 26 15:58:26 HOME=/home/dad and USER=dad in the startup scripts (that are here:http://forum.xda-developers.com/showthread.php?t=913622)<<<<< those entries are entered as "root", I changed my entries to "dad" and added export USER=dad to "bootubuntu"............ Jan 26 15:58:52 ogra: is ther a way to get looged in as dad instead of root? Jan 26 15:59:25 chroot always makes you root in the target fs Jan 26 15:59:33 k Jan 26 15:59:37 but you can run "su dad" Jan 26 15:59:42 that should make you dada Jan 26 15:59:46 heh Jan 26 15:59:50 dad i mean Jan 26 15:59:52 haha Jan 26 16:00:35 i just log in as dad in the chrooted term. Jan 26 16:08:32 can i take a rootstock build 1G .img , turn it into a 3G image? Jan 26 16:09:20 * persia notes that chroot takes a --userspec argument if one wants to be non-root for some reason. Jan 26 16:10:33 oh, i didnt know that :) Jan 26 16:11:10 It's exceedingly rarely useful: primarily only when embedding the chroot call in some other utility. Jan 26 16:11:31 persia, btw Jan 26 16:11:33 Description: The Unity 2D interface for non-accelerated graphics cards Jan 26 16:11:33 This package installs a fully usable Unity 2D session and provides the Jan 26 16:11:33 common configuration files and defaults. Installing this package will Jan 26 16:11:33 offer the Unity 2D session in your login manager. Jan 26 16:11:33 . Jan 26 16:11:34 Unity 2D is designed to run smoothly without and graphics acceleration. Jan 26 16:11:51 thats my final text now Jan 26 16:11:54 No. Jan 26 16:12:09 It expects 2D acceleration, it just doesn't require 3D acceleration. Jan 26 16:12:09 waiting for kaleo to process the merge request Jan 26 16:12:15 it doesnt Jan 26 16:12:21 Try running it on unaccelerated framebuffer and you *will* feel pain. Jan 26 16:12:32 xfbdev doesnt have any 2d accel Jan 26 16:12:51 thats what i'm doing here Jan 26 16:12:55 persia: I do run it on unaccelerated 2D fame buffer. Jan 26 16:12:58 Yes it does: it was added to trunk in 2004 Jan 26 16:13:52 its happened again, i was having problems not getting a "prompt" in the terminal of the chrooted image i made a with rootctock....tried again last night it worked but the image was too small. tried again made it 3G but now no prompt...eGGgghh..... any suggestions why i canot get a prompt in the terminal with one image but not another? Jan 26 16:13:58 GrueMaster, Really? Not xfbdev? Jan 26 16:14:16 Not in VM. Jan 26 16:14:34 It is using the Xsvga driver iirc. Jan 26 16:14:37 Oh, indeed. And the performance there is acceptable? Jan 26 16:14:50 Seems to be. Jan 26 16:15:01 * persia is impressed. Jan 26 16:15:11 well, it is very likely that people not having 3d accel end up with fbdev Jan 26 16:15:24 ogra, So, three things about the Description then: Jan 26 16:15:29 i think thats our default fallback for cards without any driver Jan 26 16:16:31 1) The short description (after "Description:") should complete the cloze ${package} is a ${short-description}. Repeating "Unity 2D" is frowned upon (although you've used it a bit differently, so might argue you mean "Unity" and "2D" separate from "Unity 2D") Jan 26 16:17:18 2) The prefatory phrase "This package" is useless drivel, and confusing for package mangagement tools that don't give the user the package name. Start exciting and juicy. Jan 26 16:17:32 (hint: inserting "The Unity 2D interface" may help) Jan 26 16:17:56 3) s/and/any/ in the last sentence. Jan 26 16:17:57 i thought there were reasons why these complaints were removed from lintian Jan 26 16:18:11 I thought they were removed to make people like me less picky. Jan 26 16:18:11 uh, yeah Jan 26 16:18:43 i'll change that with the upload after the merge was done Jan 26 16:18:54 Heh, sure. No rush. Jan 26 16:18:55 i dont want to file a new merge request right now Jan 26 16:19:04 You can just update them, you know. Jan 26 16:19:15 (there's even some handy UI in LP for that) Jan 26 16:19:17 there are other typos in the control file i need to fix anyway Jan 26 16:19:30 wait, there are other people as picky as you, persia? :P Jan 26 16:19:34 which i planned to do in a subsequent upload Jan 26 16:19:47 GrueMaster, IRS Jan 26 16:19:50 ;) Jan 26 16:19:52 GrueMaster, I believe myself to only be in the 92nd percentile of pickiness. Jan 26 16:20:01 heh Jan 26 16:28:07 can i turn a 1g rootstock image into a 3G (made filesize too small) Jan 26 16:47:35 persia, Jan 26 16:47:37 Description: Unity interface for non-accelerated graphics cards Jan 26 16:47:37 The Unity 2D interface installs a fully usable 2D session and provides the Jan 26 16:47:37 common configuration files and defaults. Installing this package will Jan 26 16:47:37 offer a session called Unity 2D in your login manager. Jan 26 16:47:37 . Jan 26 16:47:38 Unity 2D is designed to run smoothly without any graphics acceleration. Jan 26 16:47:42 better ? Jan 26 17:11:40 ogra I fixed it but why would i one image require "mount --bind /dev $mnt/dev" in the startup scriptand another made the same way not need it? could it have somthing to do with the programs i install in qemu? I just dont get it? Jan 26 17:13:51 no idea, i dont know who made these startup scripts Jan 26 17:14:17 generally you should bind mount /dev into the chroot to be able to access devices though Jan 26 18:07:32 ogra: http://www.engadget.com/2011/01/25/compulab-makes-a-tiny-tegra-2-computer-for-the-lilliputian-commu/ Jan 26 18:07:35 ogra: seen that? Jan 26 18:07:46 yep Jan 26 18:07:58 http://www.fit-pc.com/trimslice/ Jan 26 18:07:58 nice ! Jan 26 18:08:05 ;) Jan 26 18:08:52 ogra: man, that looks nice Jan 26 18:08:57 sadly the kernel situation for tegra is very very far from being usable Jan 26 18:09:01 * prpplague can't wait to order one Jan 26 18:09:18 ogra: that will change when people get a trimslice and start doing dev Jan 26 18:09:24 i suspect they will come with a 2.6.29 or 2.6.32 kernel Jan 26 18:09:50 that wont help with the proprietary drm driver or xserver Jan 26 18:10:12 as long as nvidia doesnt work with the community and compiles against some decent kernel or xorg Jan 26 18:10:51 ogra: ahh wasn't aware of the proprietary drm driver stuff Jan 26 18:10:56 currently to make X work accelerated on tegra you need to apply their overlay FS (a tarball) with ancient xorg versions and libs Jan 26 18:11:23 and their kernel module is only compiled for two or three old kernel versions Jan 26 18:11:59 ogra: ahh but that is for accelerated, without works right? Jan 26 18:12:04 i wish they would provide a shim so we could use dkms to just build it against the kernel we ship Jan 26 18:12:14 sure, plain framebuffer works fine Jan 26 18:12:23 thats what i use on the ac100 Jan 26 18:12:50 but its sad that i cant use the full power of the device due to silly management decisions at the manufacturer Jan 26 18:14:04 their whole sound, powermanagement and cup speed control is done by a proprietary daemon in userspace Jan 26 18:14:11 *cpu speed Jan 26 18:14:48 i really love TI for its openess Jan 26 18:14:52 ogra: I have seen some alsa patches recently for the tegra. Hopefully they will be in 2.6.38 or 39. Jan 26 18:15:08 hehe, I'd say they will get something for 40 Jan 26 18:15:10 GrueMaster, wont help, the codecs are binary inside the daemon Jan 26 18:15:11 or even alter on Jan 26 18:15:24 with luck omap 4 is going to be kind of fine for 38/39 Jan 26 18:15:33 GrueMaster, the kernel side only provides hooks for them Jan 26 18:16:39 :-( Jan 26 18:17:20 i wouldnt mind all that if nvdidia would at least provide binaries against decent versions of all that Jan 26 18:17:43 but what they offer is massively outdated Jan 26 18:19:20 ogra: yea omap4 should be pretty robust, just love that trimslice package Jan 26 18:19:56 yup Jan 26 18:20:43 ogra: What I'm seeing is patches in the last few weeks directly from nvidia to alsa. From what I can tell, they are exposing the gpio's to the codec and tweaking the codec driver as well. Jan 26 18:21:14 right, but the binary bits come from the userspace daemon Jan 26 18:21:37 i have sound devices on the ac100 too ... they just dont route to anything unless i get the daemon running Jan 26 18:22:04 (silence and pules at 100% cpu) Jan 26 18:22:08 *pulse Jan 26 18:22:12 That is the non-alsa driver. They removed it post 2.6.36. Jan 26 18:22:41 hi, has anybody compiled qt4-x11 with -opengl es2 support yet? Jan 26 18:22:58 pH5, rsalveti works in that Jan 26 18:23:11 not sure there is a ppa with the packages Jan 26 18:23:15 pH5: yup, currently debugging that with sgx Jan 26 18:23:20 yup, we have, let me get the link Jan 26 18:23:45 https://launchpad.net/~rsalveti/+archive/qt-neon-gles Jan 26 18:23:47 natty and maverick Jan 26 18:24:06 ogra, rsalveti: ow, great. thanks! Jan 26 18:24:23 np Jan 26 18:24:25 nice, it has gigabit Jan 26 18:24:32 the ppa ? Jan 26 18:24:36 :P Jan 26 18:24:39 :) Jan 26 18:51:44 Howdy all Jan 26 18:51:56 I have some questions about the wireless system Jan 26 18:52:23 ask then :) Jan 26 18:52:29 I'm attempted to setup a pandaboard as a router, with a bridge between the built in ethernet and wifi Jan 26 18:52:57 unfortunately, it seems like the wireless isn't supported Jan 26 18:53:03 it is Jan 26 18:53:12 did you install the ti addons ? Jan 26 18:53:21 when I define it via /etc/networks/interfaces as master Jan 26 18:53:34 oh, I did, it worked as a client before I start playing with networking Jan 26 18:53:58 ah, i haven used the wlan without NM yet Jan 26 18:54:16 but i suspect you need wpa_supplicant setup or some such Jan 26 18:55:06 The line that conserns me is "no (wireless) mapping found for key: wireless-mode Jan 26 18:56:40 wait, you said master, you mean AP mode ? Jan 26 18:56:57 wpasuplicant is installed, and I think I have it set as an open ap Jan 26 18:57:08 yes, that is correct. master as in ap Jan 26 18:57:30 i know rsalveti provided AP mode to me in dallas through his panda so it definitely works somehow Jan 26 18:57:48 but that might have been through NM as well Jan 26 18:57:56 ogra: that was n900 Jan 26 18:58:05 the panda network ? Jan 26 18:58:08 but using nm at my host Jan 26 18:58:11 yup Jan 26 18:58:23 i thought you used the panda for the ap stuff ... ok Jan 26 18:58:27 never tried to use the panda wifi chip as ap Jan 26 18:58:34 me neither Jan 26 18:58:54 the driver wasn't stable at that time Jan 26 18:59:00 lots of kernel panics all around Jan 26 18:59:07 i also dont know if the driver from the ppa is actually built against mac80211 Jan 26 18:59:20 then you could use hostapd Jan 26 18:59:30 maybe you will get better results with current upstream one Jan 26 18:59:38 definitely Jan 26 18:59:51 What is that, do you have a link? Jan 26 19:00:48 http://groups.google.com/group/pandaboard/browse_thread/thread/291bf9cbd8c36d15 Jan 26 19:01:01 that ppa should have newer stuff Jan 26 19:01:18 sudo add-apt-repository ppa:tiomap-dev/omap-trunk Jan 26 19:01:33 * KC9SJQ looks Jan 26 19:01:48 not sure if it already has the new wifi driver though Jan 26 19:02:00 might be that this is only upstream Jan 26 19:03:19 * KC9SJQ adds to mirror and updates Jan 26 19:05:00 I'll let that chug while I get a sandwich. Jan 26 19:05:05 Thanks for the help. Jan 26 19:16:10 okay lets see what explodes when I boot this puppy Jan 26 19:26:27 ogra, The new description looks good to me. Publish it :) Jan 26 19:26:38 persia, heh, to late Jan 26 19:26:44 already sitting in NEW Jan 26 19:27:05 i need to talk kaleo into a new upstream release before i can MIR them though Jan 26 19:27:19 i dont want to have bits in debian/patches for the MIR Jan 26 19:27:29 but thats for tomorrow Jan 26 19:27:47 * ogra really likes bzr builddeb --split :) Jan 26 19:32:00 --split is *not* the right way to do it. I forget why, but that was the conclusion from the discussion between NCommander and james_w. Jan 26 19:39:29 persia, --split is what upstream insists to be used, they also insist to have the debian dir in the branch, only tarball releases wont have it Jan 26 19:40:57 Dunno. Talk to one of the folks I listed above. I just remember hearing it wasn't the right way to do it after that conversation. Jan 26 19:41:30 well, it works great and makes life a lot easier Jan 26 19:42:02 It does something messy and bad when attempting to handle coordination between the branch importer and the upstream branch. Jan 26 19:42:16 But my understanding of UDD is too weak to know precisely what. Jan 26 19:42:37 The key bit is that I believe it blocks direct cherrypick from upstream to the import branch. Jan 26 19:42:51 well, i'll go with upstream if they insist, who am i to complain if it makes my life easier Jan 26 19:43:08 ah, well, there is no import branch Jan 26 19:43:17 There will be as soon as it passes NEW. Jan 26 19:43:25 thats the main argument, they want a single branch per project Jan 26 19:44:04 Seriously, go get some UDD Kool-Aid. You'll be in a lot better shape to discuss this with upstream. Jan 26 19:44:20 It will be better for you and better for them to take advantage of the import branch. Jan 26 19:44:24 doesnt help me with upstream, really Jan 26 19:44:46 you mean they should merge back from the package branch ? Jan 26 19:44:51 into trunk Jan 26 19:45:56 I mean that because bzr doesn't support parallel trees, it won't support operations between the import branch and the upstream branches if you use --split. Jan 26 19:46:20 As in an error message with `bzr merge`. Simply no support for it at all. Jan 26 19:46:27 no, you need to merge the import branch before doing a new upstream indeed Jan 26 19:46:49 hmm ? Jan 26 19:46:55 why shouldnt it merge anymore Jan 26 19:47:06 the content stayed consistent Jan 26 19:47:08 You *can't* if you created with --split. If upstream creates an artifact tarball, it can be done, but with --split, the tarball is semi-random, and the history is unrecoverable. Jan 26 19:47:22 But I don't know enough about this: please ask someone knowledgeable. Jan 26 19:47:34 bzr doesn't use the content as part of merging. Jan 26 19:48:04 Yes, that sounds odd, but it's true. If you ask the bzr folk, they'll tell, you about the parallel merge problem, and how it's the very first thing they fix after changing the on-disk format of bzr. Jan 26 19:48:17 But until the data format is fixed, it's not possible. Jan 26 19:48:29 Has to do with inode tracking and other internal complexities. Jan 26 19:49:10 the point is that there are no merges at all happening from anything after the package was uploaded Jan 26 19:49:42 packaging changes are done in a local branch, merged into trunk, then trunk is pulled and built with --split Jan 26 19:49:49 Don't argue with me: even if you were capable of convincing me, it wouldn't help. Talk to someone who understands UDD. Jan 26 19:49:53 UDD isnt involved at all atm Jan 26 19:50:02 I just don't know enough to argue with you about this. Jan 26 19:50:10 i dont argue Jan 26 19:50:20 Sorry: s/argue/debate/ Jan 26 19:50:23 but you tell me the way that is used breaks with UDD Jan 26 19:50:28 * persia didn't intend any indication of emotional involvement Jan 26 19:50:39 and i tell you that UDD isnt involved in the current setup Jan 26 19:50:53 so i dont need to talk to UDD people yet :) Jan 26 19:51:04 If UDD is used and inherited from upstream history, it becomes easy to cherrypick individual commits, and have those applied as distro-patches, etc. Jan 26 19:51:13 Otherwise it's all manual manipulation. Jan 26 19:51:28 thats what it is atm Jan 26 19:51:47 Since there *will* be a packaging branch, and since people *will* submit merge requests from their branches fixing bugs, it makes sense to try to make sure that things can be pulled/pushed back and forth. Jan 26 19:52:01 and there are no such things like distro patches given the fact that everything happens in trunk Jan 26 19:52:21 Mind you, I'm a fan of manual manipulation. I tend to use bzr as a way to track the patches I applied, rather than as a VCS, but still. Jan 26 19:52:28 i think upstream will change their mind if the first external distro shows up to use their stuff Jan 26 19:52:45 ogra, Saying there are no distro patches implies you have control over the set of folks commiting branches and uploading, which isn't the case. Jan 26 19:52:50 and they have to keep distinct branches for ubuntu and "others" Jan 26 19:53:06 we do have that control atm Jan 26 19:53:32 it wont staxy that way and i didnt want to argue with upstream Jan 26 19:53:40 so i went with what they asked for Jan 26 19:57:29 Anyway, talk to the UDD people, just so you see the points. I can't explain why --split isn't preferred in a sensible way. Jan 26 19:57:44 k Jan 26 20:49:15 Hmm, update failed Jan 26 20:50:23 error building module pvr-omap4-kernel Jan 26 20:55:37 error: 'struct platform_device' declared inside parameter list Jan 26 20:56:57 any thoughts? Jan 26 21:22:22 KC9SJQ: what kernel are you using? Jan 26 21:22:58 I can't tell anymore, my board now won't boot. Jan 26 21:23:29 it should have been the official one from the ubuntu arm repositories Jan 26 21:24:15 I guess I'll have to rebuild the card Jan 26 21:24:41 It appears to start booting, and then gets stuck with some fsck info on the screen Jan 26 21:27:24 hm Jan 26 21:27:41 I know the pvr kernel module is compatible with our tree Jan 26 21:27:47 as the needed patches are applied Jan 26 21:28:00 if you're using a different one, then you need to make sure you get everything Jan 26 21:28:20 KC9SJQ: you can easily boot our default kernel by installing it at your sd card Jan 26 21:28:23 So far, I've been trying to do it via the idiot method, add a repository and update Jan 26 21:28:24 using qemu and chroot Jan 26 22:10:03 Kernel 2.6.35-903-omap4 Jan 26 22:11:08 What is "your kernel" and how can I get it? Jan 26 22:17:25 The linux-image-omap4 package should always depend on the latest omap4 kernel in Ubuntu. Jan 26 22:21:03 That should be the default, and I haven't changed it Jan 26 22:21:30 yeah, "linux-image-omap4 is already the newest version" Jan 26 22:22:21 I wonder if I'm missing the headers or something Jan 26 22:22:48 if the module is missing a unspecified dependancy Jan 26 22:28:14 Odd. It ought just work. Jan 26 22:30:04 * KC9SJQ shrungs Jan 26 22:30:24 does the omap-trunk ppa automatically rebuild on a particular basis? Jan 26 22:30:40 Maybe it's a legitimate bug which will be fixed soon Jan 26 22:32:52 The PPA won't rebuild on a regular basis. But some of the team that maintains the PPA might upload occasionally. Jan 26 22:33:25 There's no way to file bugs on PPA packages, but you might be able to look at the name of the last uploader in the changelog, and find them in this channel. Jan 26 23:02:47 persia: the reason was --split is braindead. Proper way to do it is pristine-tar Jan 26 23:03:30 Right, which requires a tarball. Anyway :) Jan 26 23:04:17 persia: at some point I was going to through the 0.1 orig.tar.gz tarball I made via split into pristine-tar Jan 26 23:04:44 woo Jan 26 23:04:48 My build finally finished Jan 26 23:30:37 * NCommander thinks we have a compiler regression ... **** ENDING LOGGING AT Thu Jan 27 02:59:57 2011