[09:33] <ogra_> persia, did you find a working nvflash yet ?
[09:36] <persia> No, but I'm not sure that's the issue.
[09:36] <persia> nvflash claims it can't see the USB device.
[09:37] <persia> Looking at syslog, it seems that when I attach, two USB devices show, and then both disconnect.
[09:37]  * persia reproduces to get a viewable snippet
[09:38] <persia> hrm.  Reproduction failed.  I wonder what changed.
[09:39] <ogra_> well, are you sure the device was actually in flash mode ?
[09:39] <ogra_> the usb device will only show up if its in that mode
[09:41] <persia> Right, but it was the immediate disconnect that was the issue.  As long as it stays connected, it ought be OK.
[09:41] <ogra_> yep
[09:45] <persia> Ugh.  I tried to backup partition 0, and it failed, and now I get protocol errors.  I guess this will be a bit of fun trial and error.
[09:46] <ogra_> there is no 0 partition ;)
[09:46] <ogra_> it starts at 2
[09:46] <persia> hence needing to power cycle :)
[09:47] <ogra_> nvfalsh has a get partition table command
[09:47] <persia> There's no 1 either?
[09:47] <ogra_> no 1 either
[09:47] <persia> What's that command?
[09:47]  * persia doesn't have a manpage :(
[09:47] <ogra_> dont ask me what they are smoking at toshiba :)
[09:47] <ogra_> it should have a help command
[09:47] <persia> nvflash help ?
[09:48] <ogra_> --help i think
[09:48] <ogra_> with all the LD_PRELOAD mess
[09:48] <persia> Indeed it does.
[09:50] <ogra_> --getpartitiontable
[09:50] <ogra_> with a textfile as output
[09:50] <persia> Yep.  So, I don't really like this tool.
[09:51] <ogra_> nobody does
[09:51] <persia> 1) It's non-free.  2) It doesn't qualify for multiverse.  3) It's not packaged.  4) It has no manpage, and poorly formatted --help.  5) it has some of the worst subcommand grammar I've ever encountered.
[09:52] <ogra_> heh, yeah
[09:52] <ogra_> sadly we need it
[09:52] <ogra_> i dont know of any alternative yet
[09:52] <ogra_> i wonder how trimsclice does it
[09:53] <ogra_> they have largely the same board in their device
[09:53] <ogra_> and u-boot is missing input support yet
[09:53] <ogra_> and even then you would have to flash u-boot first
[09:54] <persia> Lovely.  I seem to get to run nvflash once per powercycle.
[09:54] <ogra_> you can use the --resume command
[09:54] <ogra_> replace the --bl flastboot.bin with it
[09:54] <ogra_> it can only upload the bootloader once
[09:55] <persia> Aha!  And --resume lets me run another command without getting "usb read error (71): Protocol error" ?
[09:55] <ogra_> i think so
[09:55] <ogra_> try it
[09:56] <persia> Hmm.  Less than ideal.  This power cycle the bootloader failed to install :/
[09:57] <ogra_> well, luckily you only have to do it once
[09:58] <persia> --resume seems to work.
[09:59] <persia> No, I'm super-extra-paranoid: I have to do it ~15 times, plus any that are unsuccessful.
[10:00] <ogra_> i mean once you flashed successfull you dot have to do it anymore
[10:00] <ogra_> though i would recommend also flashing a fallback kernel to part 5
[10:00] <ogra_> in case you mess up anything you can still boot from it
[10:01] <persia> Why?  Is there some way to select the partition from which one boots?
[10:01] <ogra_> yes
[10:01] <ogra_> if you hold down the home key during power up you get into fastboots recovery menu
[10:01] <persia> If one bricks the device, can one restore with nvflash?
[10:01] <ogra_> if you press 1 there it boots from part 5
[10:01] <ogra_> yes
[10:01] <ogra_> the device is unbrickable
[10:02] <ogra_> as long as you can restore the partitioning you will always get it back to life
[10:03] <persia> That's nice.
[10:03] <ogra_> part 5 is sadly only 5M big
[10:03] <ogra_> so there is no space for nifty initrds
[10:03] <persia> On most of my devices there is some flash that, if overwritten, will make the device completely useless.
[10:03] <ogra_> tegra seems to be similar to omap here ... the rom code will always work
[10:04] <persia> I suspect that is true for this, except that there is no way to write that flash (who said updating device firmware was a good idea)
[10:04] <ogra_> and it seems the flash mode lives there
[10:04] <persia> Oh, nifty.  So it's not like BIOS flash, or the boot NOR on mx5 devices (yes, you can work around the boot NOR with the DIP switches, but they aren't exposed in real devices)
[10:05] <ogra_> right
[10:05] <persia> Seems that --resume only works once, and after two operations, I really have to power cycle.  Oh well.
[10:06] <ogra_> do you do a full backup ?
[10:06] <persia> That's my plan.  My hardware is different from yours, and my software is very different.
[10:06] <ogra_> yeah, makes sense
[10:07] <persia> (unless you have the REGZA control suite by default, etc.)
[10:07] <ogra_> lol, no
[10:07] <ogra_> what do you do with that, remote control your TV ?
[10:07] <persia> That's what I thought :)
[10:07] <persia> Rather, participate in your entertainment network.
[10:08] <ogra_> ah, REGZA is more than a TV brand in .jp ?
[10:08] <persia> At one level you can consider this a remote control for your TV, but you can also do things like switch the audio track from your TV to your stereo to your laptop headphones, control video streaming from your PVR to your TV or your laptop, and switch seamlessly, etc.
[10:09] <ogra_> ah
[10:09] <persia> REGZA is Toshiba's home entertainment brand.  They do TVs, PVRs, Speaker systems, Keitais, Tablets, etc.
[10:09] <ogra_> ah, i didnt know that
[10:09] <ogra_> i only know trhe term from my TV :)
[10:10] <persia> I haven't seen a REGZA Stereo, but the protocol should work with Onkyo or Denon hardware.
[10:10] <persia> Yeah.  The nifty stuff takes a while to export: someone has to figure out how to explain it to foreigners.
[10:10] <ogra_> heh
[10:11] <persia> No, seriously.  Here they just stick a couple stickers on it, and the guy in the shop says "It connects to your network", and nobody asks questions.
[10:11] <persia> Other places people want to know why they should pay more for feature X.
[10:12]  * persia suspects this has something to do with not having a law against selling electronics more than three years old
[10:13] <XorA> hey persia
[10:13] <persia> XorA, Hey.
[10:14] <XorA> Im amused as I just bought an item that is now 30 years old
[10:16] <XorA> now I just need to build a circuit to adapt its video output to actually work with something modern so I can see it working :-D
[10:17]  * persia laughs
[10:21] <persia> Grr...  Partition 8 consistently fails.
[10:21] <ogra_> is that the biggest one ?
[10:22] <ogra_> i think nvflash has a prob with partitions bigger than 4G ... usually thats only the user data partition anyway and empty ...
[10:22] <persia> Not by a long way.  Biggest is 6774016 sectors.  8 is only 153600
[10:24] <ogra_> weird
[10:25] <persia> Yeah, well, it's the oddities that make me do a full backup before I even boot the device.
[10:29]  * ppisati tried the mmu patch for kexec but still fails..
[10:44] <persia> ogra_, The partitions I can't read are labeled APP, UDA, and UDB.  Do you know what these codes mean?
[10:44] <ogra_> APP is android apps i think, did you look whats indside ?
[10:45] <ogra_> ah, no. you said you didnt boot yet
[10:46] <ogra_> (though the part table is completely shifted anyway in userspace ... you will never see part 2-6 in android
[10:46] <ogra_> )
[10:47] <persia> UDA and UDB would be User Data A and User Data B?
[10:47] <ogra_> so you have to guess which ones are APP, UDA, UDb
[10:47] <ogra_> might be
[10:48] <persia> Ugh.  8 gives a consistent format error, maybe some sort of copy protection.  12 and 14 just time out attempting to copy.
[10:48] <ogra_> 14 should be mmcblk0p7 in userspace
[10:48] <ogra_> that falls under the "biggest partition" stuff i mentioned above
[10:49] <ogra_> no need to back it up
[10:49] <ogra_> should be empty
[10:49] <persia> I suspect so: it's 13,230M
[10:49] <ogra_> yeah
[10:50] <persia> But the 300M APP partition seems like something I want backed up, and I got just over a GB from the 1235 UDA parittion on one try, although most tries have been lower.
[10:52] <ogra_> oh, if your device should offer you to upgrade to android 2.2, dont do it if you want to keep the dual boot option
[10:52] <ogra_> if you should boot it into android before installing
[10:53] <persia> I don't intend to ever boot Android on it, unless I have to verify a hardware issue for the warranty.
[10:56] <persia> Connecting to a full speed hub rather than a high speed hub seems to help, although it takes *MUCH* longer.
[10:57] <ogra_> HUB ?!?
[10:57]  * ogra_ just connects directly
[10:58] <persia> You connect directly to the controller?  What sort of device exposes that?  I've never seen one.
[10:58] <ogra_> i connect a mini usb cable between my x86 laptop and the ac100
[10:58] <ogra_> without extra hubs attached
[11:00] <persia> Right.  How many USB ports does your laptop have?
[11:00] <ogra_> 3
[11:00] <ogra_> and i usually connect to a full speed port
[11:01] <persia> Then you probably have 2 hubs in your laptop.  The first providing those three ports and uplink to the second, and the second conneting to internal devices.
[11:01] <ogra_> right, i thought you referred to an external hub
[11:01] <persia> I was on high speed, which is something like 30x as fast, but it kept crashing.  Now I'm on full speed, which works better.
[11:01] <ogra_> k
[12:01] <persia> ogra_, Aha!  I encountered the 4G issue.  You don't happen to know if there is a 64-bit nvflash floating around somewhere, do you?
[12:02] <hrw> hmm... sheet.zoho.com is default viewer of xls files under ubuntu?
[12:02] <persia> hrw, In some environments (like those where openoffice/libreoffice was considered too heavy/slow/broken)
[12:03] <hrw> arm for example
[12:03] <persia> From what I understand, natty libreoffice works, but it's kinda slow.  natty koffice is a bit faster, but predates the revival/rebranding.
[12:04] <hrw> my daughter just sent panda x11 session to logout... power of power key ;:D
[12:04] <persia> heh
[13:04] <ZebraDroid_> Hey all, Could someone suggest anything?  I'm running ubuntu on my arm tablet, I've built and installed touchscreen drivers and the cursor now follows my touch.  The only problem is, no click event is launched on touch release/tap.  Is there any way I could configure this? Thanks
[13:04] <persia> Which tablet?
[13:05] <ZebraDroid_> Vega
[13:05] <persia> Try `xinput list` to find the id of your touchscreen
[13:06] <ZebraDroid_> Yup, I have that
[13:06] <persia> `xinput list-props <device>` will tell you what it belives it can do.
[13:06] <persia> `xinput watch-props <device>` will let you see what it is sending.
[13:07] <ZebraDroid_> ok, thanks
[13:08] <persia> Depending on how the driver is implemented, you may need to have it send tap events, you may need to trap and process tap events to turn them into button activations, you may need to fiddle with input-utils to make sure the kernel has the right bits for the event driver...
[13:08] <ZebraDroid_> hmm ok
[13:09] <ZebraDroid_> It seems that despite moving my pointer, watch-props isn't providing any feedback. (I've tried all of the pointer devices and the touchscreen identifier specified in xorg.conf isn't in the list)
[13:12] <persia> Right.  I presume you're well past the xev stage, so diving in: does your driver provide a kernel event interface?
[13:17] <ZebraDroid_> Umm, not too sure.  This is the first time I've had to compile and install drivers manually so I'm kinda feeling my way around still.  Through inspection of the source it seems it provides the click event via a call to xf86EventButtonPressP (or something similar  to that)
[13:17] <persia> Then it's just an X driver, making xinput the best tool for analysis.
[13:17] <persia> Check your X log to make sure it's being loaded.
[13:22] <ZebraDroid_> It seems to attempt to load it, but fails to initialise a touchscreen device and unloads due to EV_SYN missing. I can only assume it loads in some description of state as prior to installation, the cursor would just jump to 0,0 on touch.  Post installation it follows touch
[13:24] <persia> Hrm.  I'm not sure.  You might ask the team in #ubuntu-x, although they may send you back here if there are architecture-specific confusions.
[13:24] <persia> (or someone else might know, if you wait a while)
[13:25] <ogra_> isnt there also #ubuntu-touch ?
[13:25] <persia> Is there?  I hadn't encountered it before, but yeah, if it exists, it's a better place :)
[13:26] <persia> Indeed there is!
[13:26] <ZebraDroid_> Great, I'll ask there - thanks for the help ^^
[13:26] <ogra_> they focus more on enabling multitouch in existing drivers though
[13:26] <persia> Well going from 0 to N is multi, right?
[13:26] <ogra_> so they might not know much about new ones
[13:27] <ogra_> the prob smells a bit like evdev would just select a mouse driver for the device
[13:28] <persia> Or any other class of incorrect autodetect.
[13:28] <ogra_> yep
[13:29] <persia> ogra_, My notes have a confusion: I'm writing boot-2.6.37-1-ac100-SD.img to partition 6, right?
[13:29] <ogra_> yes
[13:29] <persia> OK.  The command was listed once with a 6 and once with a 5, so I just wanted to double check.
[13:30] <persia> Oh my.  Partition 14 reduced to 0.1% of raw size with gzip :)
[13:31] <ogra_> heh
[13:32] <persia> OK.  partition flashed.  Device OFF.  USB disconnect.  SD insert.  Close eyes and cross fingers...
[13:32] <ogra_> :)
[13:32]  * ogra_ crosses
[13:33] <persia> Yeah.  ALSA errors then bootsplash.  Thanks a lot!
[13:33] <ogra_> awesome !
[13:33] <ogra_> the rest should be trivial
[13:34] <persia> Yep.
[13:35] <persia> Heh.  Jasper.
[13:35] <ogra_> jasper ?
[13:35] <ogra_> there shouldnt be any jasper in these images
[13:36] <persia> This is casper?  What's giving me initial configuration?
[13:36] <ogra_> oem-config ?
[13:36] <ogra_> there should be neither casper nor jasper
[13:37] <persia> Oh.  It's an OEM image.  I suppose that makes sense.
[13:37] <ogra_> right
[13:37] <ogra_> its directly derived from the omap3 one
[13:37] <persia> (although it's a bit annoying now knowing that I have to go through this config process twice)
[13:37] <ogra_> thats why i said you should set a rootpw or edit /etc/shadow
[13:38] <ogra_> for the SD boot
[13:38] <ogra_> this will be automated by an init script for the actual image
[13:38] <ogra_> so you only need to cp the tarball onto a formatted SD
[13:38] <persia> Really, we should use the installer.
[13:39] <persia> But as we discussed before, this requires tracking down why cp is slow.
[13:39] <ogra_> no
[13:39] <ogra_> i think the oem team has a udeb that can install tarballs
[13:39] <persia> Yes.  Really yes.  I'm inflexible on this.  Maintenance overhead.
[13:39] <ogra_> that might be an option
[13:39] <ogra_> but i'm really not going through setting d-i to work with universe kernels etc
[13:39] <persia> It's all part of the same suite that includes live-helper.
[13:40] <persia> No, but NCommander has a WI to do that for a different spec.
[13:40] <persia> So you don't have to worry about it.
[13:40] <ogra_> so it will stay live/oem
[13:40] <ogra_> NCommander, has no WI to make d-i work with universe bits
[13:41] <ogra_> there is only one d-i related workitem ... and thats just a partitioning reciepe for partman
[13:42] <persia> It's on a foundations spec.
[13:42] <ogra_> universe ?
[13:42] <persia> Yes.
[13:42] <ogra_> that would need a complete redesign
[13:42] <ogra_> d-i needs the kernel in main
[13:43] <ogra_> and all other bits it uses to create images
[13:43] <persia> You were *at* the UDS discussion about it.  Now isn't the time to complain.
[13:44] <ogra_> well, *shrug*
[13:44] <persia> So, anyway, assuming the component issue is resolved, and the speed issue is resolved, I'll insist on proper installer images.
[13:44] <ogra_> i wont change the ac100 image, since i find wasting hours of user time for copying or formatting tasks completely pointless
[13:44] <persia> But that's not soon: make them however you want until then.
[13:45] <ogra_> and i wont change them in the future either ...
[13:45] <persia> Please read what I wrote above again?  Your objection is already included.
[13:45] <ogra_> it adds massive complexity for maintenance as well as for the enduser
[13:46] <persia> Really it doesn't.  It *streamlines* maintenance and provides a consistent experience for end users.
[13:46] <ogra_> we have oem-config exactly for this task ... i dont plan on moving away from it
[13:46] <persia> Mind you, currently it's painfully slow, which needs sorting.
[13:46] <persia> It's also impossible, which needs sorting.
[13:46] <ogra_> there is more than slowness
[13:46] <ogra_> you have to do a d-i rebuild for every kernel version change
[13:47] <ogra_> that doesnt scale to universe kernels
[13:47] <ogra_> (it is already annoying enough for the non mainline kernels we have in main ... which was one of the most pressing reasons for preinstalled oem images)
[13:48] <persia> So, this will be sorted.
[13:48] <ogra_> not by me, mind you
[13:48] <persia> No, not by you.
[13:48] <ogra_> and as mentioned above, you will need a lot to convince me to move away from oem images
[13:48] <persia> But when everyone else has done their bit, these images will switch to using an installer.
[13:48] <ogra_> not mine
[13:48] <D34X> I have a Lanya smart book X6-7A with an SSD and I was wondering if putting ubuntu on it would be any different.  It doesn't have a normal load up like another computer would, it just pops up the SmartBook screen and does the 25 second loading process.  Would I put a live load in a USB and go from there?
[13:48] <persia> Whether you do this or not at that point can be discussed later.
[13:49] <persia> D34X, What's the processor?
[13:49] <ogra_> i find it a massive waste of manopower to even put time into that
[13:49] <D34X> persia - ARM 926
[13:49] <ogra_> its fine for server but i dont see even the slightest reason to push us back into stonegae with the desktop images
[13:50] <persia> D34X, Ubuntu doesn't support that processor.  You might try Debian.
[13:50] <D34X> Poo....
[13:51] <persia> ogra_, I feel the opposite.  I have no interest in remaining in an age of hardware-dependent images.  I want generic solutions, that work for arbitrary hardware.  We are getting much closer with the tools to be able to do this, and when we can, I'll have no interest in supporting less generic solutions.
[13:52] <ogra_> where would a generic image help on the ac100 ?
[13:52] <persia> well, let's assume we are able to construct a generic tree that supports all Tegra2 devices.
[13:52] <ogra_> and whom would a generic image help on a specific board that can only run this specific image ?
[13:52] <ogra_> LOL
[13:52] <persia> Then we should only maintain that image.
[13:52] <ogra_> that will never happen
[13:52] <persia> Why LOL?
[13:52] <persia> It will.  This is the *point*.
[13:53] <ogra_> because nvidia doesnt care at all and the board specific implementations collide heavily
[13:53] <persia> If this was not a goal (and a believeably achievable goal), we wouldn't do doing any of this.
[13:53] <ogra_> well, you wont see such a kernel for a long long time
[13:54] <ogra_> it might happen at some point indeed ... like it did for the beagle after what ... 4 years or was it five
[13:54] <persia> I'll continue to expect it tomorrow, and be disappointed with anyone that feels otherwise, simply because if we don't believe it will happen, we won't help make it happen, and we'll be discouraging the folk that are trying.
[13:54] <ogra_> the only organization working on that (linaro) has no support at all for tegra
[13:55] <ogra_> and there is no movement from either side
[13:55] <persia> That's true today.  I'm not convinced it has always been true nor that it will always be true.
[13:56] <ogra_> *if* you get such support (which is already unlikely because every odm seems to implement its own bootloader solution) it will happen long after your ac100 collects dust in your basement
[13:56] <persia> All I ask of you is that if the valid bugs you raise can be sorted, and we can make generic solutions, you help with those, rather than refusing.  If you're right, and it's a long time before we get there, the cost to you of agreeing is nothing.
[13:56] <ogra_> oh, i surely wont block any progress either way
[13:57] <ogra_> i just wont change my images :)
[13:57] <ogra_> even in a generic setup i would go for oem images for desktop
[13:57] <persia> For all architectures?
[13:57] <ogra_> at least on devices wheer you have things like hardcoded partition tables etc
[13:58] <ogra_> its just pointless to count on d-i for two features we dont use/need at all
[13:58] <persia> I'd rather have a generic installer that could recognise those devices, and skip bothering the user about partitioning, but rather just do the right thing.
[13:58] <persia> I think you aren't understanding what I'm saying.
[13:58] <ogra_> thats what an initrd script can do as well
[13:58] <ogra_> in an easier way for the user
[13:58] <persia> I don't intend to show the user anything pointless: that's poor interaction.
[13:58] <ogra_> and with zero maintenance for the developer
[13:59] <persia> With two pieces of code to maintain, to have bugs, to have security issues, and two places to fix them all, and inconsistency to confuse the support and advocacy teams,etc.
[13:59] <ogra_> i only care for one place really ...
[14:00] <persia> So someone else has to care for another?  No opportunity for collaboration?
[14:01] <ogra_> i wont pull d-i into the installation
[14:01] <ogra_> d-i has its areas where it makes sense ... in this particular install to totally doesnt and only gets in the way
[14:01] <persia> You do know that live-helper is a d-i component, so you'll be doing that anyway for all the preinstall images that use livecd-rootfs today, right?
[14:01] <ogra_> not during install time
[14:01] <ogra_> only during build time
[14:03] <ogra_> what i would prefer to see would be a generic oem images initramfs hook
[14:04] <ogra_> so that you hand over filesystem and target device on the cmdline or some such and a tarball gets unpacked to the target after verifying teh taball md5 sum  ...
[14:04] <ogra_> without all the crap i need to do for d-i
[14:04] <persia> Have you looked at live-helper?  It does something very similar to that.
[14:04] <persia> And it does it from within d-i
[14:05] <ogra_> no, i havent yet, i will have to before A1 though
[14:05] <persia> And it can do it without bothering the user with lots of d-i prompting.
[14:05] <persia> You may want to: I believe it both represents that which you protest against and that which you wish existed, simultaneously.
[14:05] <ogra_> it bothers me as maintainer with the complexity i add through d-i
[14:06] <ogra_> i dont want to a) maintain d-i b) have d-i booted at all for these kind of images
[14:06] <ogra_> having to maintain a ton of d-i components vs a 10 line initramfs shell script is really not wnat i'm after
[14:08] <persia> Who said anything about "a ton of d-i components"?
[14:09] <persia> And d-i is just some initramfs scripts.
[14:10] <persia> So, for instance, if someone wrote partman-ac100, it could simply return, never prompting the user, and adding hints to everything else about how/where to install everything.
[14:10] <persia> So, for instance, if someone wrote partman-ac100, it could simply return, never prompting the user, and adding hints to everything else about how/where to install everything.
[14:10] <ogra_> d-i is a huge complex pile of stuff
[14:10] <ogra_> of which i dont need 99%
[14:11] <persia> Then don't put those bits in your image.
[14:11] <persia> It's *designed* to be flexible, modular, etc.
[14:12] <ogra_> i know
[14:13] <ogra_> you wont convince me
[14:14] <persia> I'm not trying to convince you.  I'm trying to inform you that as a result of the change to live-helper, *every* image will become a d-i image.
[14:14] <ogra_> now that would be really bad
[14:14] <persia> And I'm trying to tell you that you needn't fear this change, and that it's not that different from what you do now.
[14:14] <ogra_> and i doubt thats true
[14:14] <persia> That's what the shift to live-helper means.
[14:14] <ogra_> you think we will drop casper ?
[14:14] <persia> No.
[14:14] <ogra_> see
[14:15] <persia> I think we'll wrap casper in a filesystem that we deliver with d-i through the live-helper support infrastructure.
[14:15] <ogra_> heh
[14:15] <ogra_> after we ported l-h to upstart indeed :)
[14:15] <ogra_> given that upstart will now run the whole initrd
[14:16] <ogra_> oh, and indeed all of d-i too
[14:16] <ogra_> sorry, but i dont see us changing the whole structure on one release
[14:16] <persia> Writing a single compatibility upstart job is trivial, so there's no blocking porting effort.
[14:17] <ogra_> we'll see
[14:17] <persia> Slowly moving more of the early boot stuff to upstart can happen over time.
[14:17] <ogra_> i expect that in function and form of casper or the live initrd there wont be many changes
[14:17] <persia> Really, go read about live-helper.  Learn how it works.
[14:18] <persia> I think you'll be pleased as much as you're annoyed.
[14:18]  * persia decides thrudhr has a nice ring to it
[14:18] <ogra_> i wont be pleased for sure :)
[14:23] <hrw> how to change boot.scr without regenerating it by hand? panda
[14:25] <Neko> .. use my awesome flash-kernel boot.script->boot.scr demangler :D
[14:25] <OlivierN> hrw: or like this
[14:25] <OlivierN> sudo mkimage -A arm -T script -C none -n "Ubuntu boot script" -d boot.script boot.scr
[14:25] <Neko> guys does anyone have knowledge of a quick way to disable these horrible new scrollbars?
[14:26] <persia> Don't install overlay-scrollbar?
[14:26] <Neko> both kinds.. gedit seems to have a kind of floating on the side scrollbar and other apps just have a kind of little orange line
[14:26] <Neko> I want traditional ones back
[14:26] <hrw> Neko: for efikas it uses /boot/boot.script
[14:27] <hrw> Neko: as base of boot.scr
[14:27] <Neko> I don't think I have a choice not to install overlay-scrollbar
[14:27] <Neko> hrw, run flash-kernel again it should do it on all boards?
[14:27] <persia> Why not?  The rdepends list is short.
[14:28] <hrw> Neko: right..
[14:28] <Neko> but you want to do it "not by hand", you can't... you have to invoke it somehow with manual labor
[14:29] <Neko> persia, I just removed the package and I still get orange-line scrollbars
[14:31] <persia> Hrm.  That's unexpected.  That package is supposed to be where the orange widget lives.
[14:32] <persia> If you want different defaults, use a different seed.
[14:32] <Neko> the whole point is I am trying to replace the metapackages so we can basically define a behavior for our not-quite-ubuntu natty build
[14:32] <Neko> except, if I take these out, the scrollbar thing still happens
[14:33] <Neko> ahhh here we are
[14:33] <Neko> you need to remove liboverlay-scrollbar-0.1-0 too
[14:33] <persia> Then I'm wrong.  I thought it was that.  Maybe grep for "scrollbar" in the natty-changes mbox to see what else got patched.
[14:33] <persia> Ah, you found it.  Excellent.
[14:33] <Neko> it's just reaaaaally difficult to hit those little orange lines with a netbook trackpad
[14:34] <Neko> also since firefox and thunderbird are blacklisted we get different behavior per app which is just not desirable
[14:34] <Neko> I wonder how this affects unity though
[14:34] <persia> Try it with one of the tiny little "optical pointers".  It becomes essentially impossible.
[14:35] <Neko> weurghhh
[14:35] <Neko> saving a file in gedit defaults to a directory called "chrome"
[14:37] <Neko> maybe because I am root.. but that's strange
[14:42] <ZeZu> Is it not possible to remove X / completely from the ARM version ?  Everything I try just prompts it to want to download another desktop setup ...
[14:43] <persia> ZeZu, It certainly is possible.  I don't have X installed on my beagle.
[14:44] <persia> You will have to either 1) start from a minimal image (you might be interested in the natty headless developer images), or 2) spend a lot of time making sure you have every reverse dependency removed.
[14:48] <ZeZu> I figured it would be something along those lines ...  dependency mess ,  do you have the sgx drivers installed on your beagle ?
[14:50] <ZeZu> I didn't have nearly as many issues w/ beagle as i do w/ panda ...  the pvr kernel drivers refuse to cross compile w/ 2.6.39-rc7
[14:51] <ogra_> if your .39 kernel is properly packaged they wont ;)
[14:52] <persia> ZeZu, I don't have the sgx drivers on my beagle (no monitor, no need)
[14:54] <ogra_> oh, wait you said cross ...
[14:54] <ZeZu> indeed
[14:54] <ogra_> i fear there even a properly packaged kernel wont help
[14:54] <ogra_> i dont think dkms gets along well with cross building
[14:54] <ogra_> sounds like a good future project for hrw *g*
[14:55] <ZeZu> yes well i found out the hard way ... actually you have to pass ARCH=arm or else it tries to build bits and pieces for host system ...
[14:56] <ZeZu> define properly packaged btw,  might help ... i do recall having to package the headers differently when building for beagle, but i don't think it used dkms at that time
[14:58] <hrw> ogra_: D:
[17:14] <avinashhm> hi , does any one have a u-boot for omap4 panda board, where we 'saveenv' works ? .. any help pls
[17:15] <avinashhm> j /#panda
[17:15] <persia> avinashhm, Does it not work for the u-boot in the Ubuntu images?
[17:16] <avinashhm> persia, sorry .. wasn't aware of the ubuntu images .. can u point me to .. i ll try
[17:18] <persia> Most recent images at http://cdimage.ubuntu.com/releases/11.04/release/
[17:18] <persia> You can choose between a full environment (optimised for netbooks, but suitable for desktops), or a headless image as a base for arbitrary development.
[17:19] <persia> ogra_, Do you know why there aren't any .torrent files for the omap images?
[17:20] <avinashhm> persia, thanks man .. i ll pick up these net book image and check out ...
[17:26] <GrueMaster> avinashhm: When you say "saveenv", are you trying to save the u-boot environment between reboots?  The panda doesn't have any emmc or nand for storing u-boot settings.
[17:27] <avinashhm> GrueMaster, can't we store to MMC .. just asking , i am not sure ?
[17:28] <GrueMaster> Not from uboot.  But you can modify the /boot/boot.script in our images and reflash it to the boot partition with flash-kernel.
[17:28] <GrueMaster> (or modify it manually and reapply the u-boot crc with mkimage).
[17:28] <persia> heh.  kernel segfault during debootstrap.  Extra points!
[17:30] <micahg> janimo: poke re chromium> any luck?
[17:44] <avinashhm> GrueMaster, ok .. i ll try to modify boot.script then .. thanks man
[18:03] <NCommander> rsalveti: have the PXE boot patches landed in the Linaro u-boot tree?
[18:10] <rsalveti> NCommander: not that I know, jcrigby should know better
[18:10] <jcrigby> NCommander, no not yet
[18:11] <NCommander> jcrigby: any idea when it will land?
[18:12] <jcrigby> NCommander, I could push them to the linaro-next if that is useful to you
[18:12] <NCommander> jcrigby: indeed it would be
[18:12] <jcrigby> or are we talking pushed to archive?
[18:13] <jcrigby> ok, I'll do that
[18:13] <NCommander> jcrigby: when it hits the linaro u-boot, it will get piced by the archive next time we update it
[18:13] <persia> jcrigby, For pushed-to-archive, if you can get a candidate package ready, it's easy to get someone else to help drop it in.
[18:16] <jcrigby> NCommander, persia ok I'll prepare a 2011.05 release based on current upstream rc and the PXE patches
[18:17] <NCommander> jcrigby: thanks, that's a huge help
[18:20] <rsalveti> jcrigby: it'd be good to include the tftp patches, but probably need more work at the ones that enables ehci for omap4
[18:21] <jcrigby> rsalveti, the patches don't break anything so we can include them for those that want to experiment?
[18:21] <rsalveti> I know we have ehci support for omap3 already, so I believe we can also make it work with beagle xM
[18:22] <jcrigby> rsalveti, yes that would be great
[18:22] <rsalveti> jcrigby: sure, it's not touching anything outside usb, ehci and smsc driver
[18:22] <rsalveti> guess we can also include them
[18:26] <persia> Thanks!  That helps us play.
[18:50] <janimo> micahg, none so far, but I did not spend time on it since the UDS
[18:53] <micahg> janimo: k, thanks
[20:47] <dcordes> did anybody try webm in firefox in natty arm ?