**** BEGIN LOGGING AT Thu May 31 02:59:58 2012 May 31 07:10:47 lilstevie, does rooting always mean 1) downgrading to a firmware that has a vulnerability if the firmware is newer + 2) applying an old root method? May 31 07:12:18 janimo: on what hardware? May 31 07:12:49 twb, I am interested in tf101g May 31 07:13:11 but for devices with no unlocked bootloader I guess the same generic methdos should apply? May 31 07:14:53 g is the "prime" one? May 31 07:16:49 No, prime is tf201. May 31 07:18:34 the asus site docs say theupdater cannot to downgrades so am not sure how the old root tricks fooled it into it May 31 07:19:07 anyway I was a fool to upgrade to ICS before making sure rooting requires a specific version of the firmware present May 31 07:20:22 I deliberately bought the one with a known SBK May 31 07:30:26 twb, I bought the only model still on stock, but before making sure it should be rootable :(. I vaguely remembered all transformers are unlocked or rootable now May 31 07:34:44 newer ones allegedly are if you ring up asus and ask for the key May 31 07:34:58 In return for which they refuse all warranties for that particular S/N May 31 08:16:48 twb, hmm, you mean I could ring up asus and ask for a secure boot key? Or what key do you mean? I would happily do that if realistic May 31 08:17:17 altough I am not sure tf101g qualifies as new enough, it is still last year's model May 31 08:18:28 janimo: that was on the primes, I heard May 31 08:18:55 Where "ring up" means some wanktacular web form, I assume May 31 08:18:55 yeah, I eard primes are ulockable indeed May 31 08:19:51 btw the xda and various other web resources related to rooting are the most disorganized fountains of knowledge I ave ever seen May 31 08:20:41 it is relatively little possible information to be conveyed spread across numerous threads and lots of participants May 31 08:23:47 Well they are web fora May 31 08:24:04 i.e. fugly HTML usenet for people who are too stupid to configure a newsreader May 31 08:56:14 twb: 'fora'? Shame, you are one of them. May 31 09:01:40 My high school did not offer latin, sorry May 31 09:02:12 https://en.wiktionary.org/wiki/forum#Noun May 31 09:03:20 fowler (1e) makes no comment. May 31 09:03:55 Nor does Strunk & White (unsurprisingly, it being quite short) May 31 09:07:07 Heh, I just noticed the "usage notes" on that URL come from fowler 2e, that travesty May 31 09:32:04 rbasak, hmm, where is that binary header you mention in the review ? the merge page doesnt show anything like that May 31 09:32:35 oh, i'm blind, ignore me May 31 09:32:56 ogra_: np. I'm just doing highbank now. Could you hold off on a merge please? May 31 09:33:03 ogra_: I'm basing my patch on dannf's. May 31 09:33:38 sure, i'll fix the header during merge though, no need to wait for the US to get up :) May 31 09:34:13 * ogra_ wonders why no image has the new flash-kernel, but they all still build May 31 09:34:38 looks like we have a to loose dependency chain here, they should fail without it May 31 10:22:05 ogra_, is flash-kernel getting unified with the debian one this cycle? May 31 10:23:13 janimo, well, as much as we can at least, depends if we get highbank and armadaxp into debian in time :) May 31 10:23:26 for all the other arches yes though May 31 10:23:32 sounds good May 31 10:23:44 ogra_, what about the jasper/liveCd stuff, is that migration started? May 31 10:23:50 your hack for updating the bootkloader has to go elsewhere too May 31 10:24:07 no, but we plan to do this switch too this cycle May 31 10:40:48 ogra_: is the hardware database for the new f-k uploaded yet? (I'm not sure which package its in) May 31 10:41:09 it is in f-k itself May 31 10:41:29 infinity wanted to split it out into an arch all package though May 31 10:42:22 NCommander, dannf has done an armadaxp patch and rbasak works on highbank May 31 10:42:39 so dont worry, its all taken care of May 31 10:42:53 ogra_: wait, I thought the entire point of this was so f-k could be synced, yet the HW database is in the new package?! May 31 10:43:45 first step: sync and make sure all images work again (preferably by not changing flash-kernel but by adapting other packages to match the new world order) May 31 10:44:11 next step: make sure our f-k changes land in debian May 31 10:44:19 last step: split out the db May 31 10:44:37 ogra_: then repeat steps one and two. Doesn't it make mor esense to split out the DB first :-) May 31 10:45:10 no idea, i think it makes most sense to discuss it with debian and have them do the split ;) May 31 10:45:13 /usr/sbin/dpkg-reconfigure: flash-kernel is broken or not fully installed May 31 10:45:21 but apt-get -f install does nothing and there's no other indication of a problem May 31 10:45:22 Any hints? May 31 10:45:36 I need to run, back in an hour :-/ May 31 10:45:48 try to dpkg -i the deb May 31 10:46:10 rbasak: is that with the new f-k? I wasn't aware you were taking the new f-k enablement May 31 10:46:14 alöso the main/universe issues arent solved yet, did you install the necessary packages ? May 31 10:46:28 NCommander, yes, he works on highbank support May 31 10:46:49 rbasak: I'd much prefer having a boot menu, but I realize this has become a time sink now, so ATM, let's roll with the bootz method you had, then I'll get it fixed for the precise SRU/updated for quantal May 31 13:38:10 ogra_: I have a working flash-kernel on highbank now. But one error: http://paste.ubuntu.com/1016144/. This appears to be coming from linux-base because it doesn't recognize flash-kernel as a bootloader. Do we know about this already? Presumably it'll affect all the other boards too? May 31 13:39:17 well, flash-kernel isnt a bootloader May 31 13:39:39 That's fine. But linux-base needs to not complain :) May 31 13:41:32 well, linux-base also need to move to main, i dont expect the switch to work without hassle (never did) ;) May 31 13:42:05 i'll look into it, atm i'm rather trying to find out why the images dont fail if f-k is missing May 31 13:46:43 I think this should be a Debian issue as well, which is why I'm confused. May 31 13:47:05 f-k depends on l-b, but l-b will complain unless grub or lilo or a bunch of other bootloaders is installed May 31 13:47:06 did you set Bootloader-sets-root in your db entry ? May 31 13:47:11 Yes May 31 13:47:16 to what ? May 31 13:47:23 to "yes". May 31 13:47:29 To override the one supplied by U-Boot, which doesn't know May 31 13:47:46 Previously flash-kernel could write a kernel cmdline into boot.scr, but now it appears that it can't do that any more May 31 13:47:54 But Bootloader-sets-root: yes will work for now May 31 13:48:17 yes means it creates a file in the initrd which needs to contain a UUID May 31 13:48:45 sigh, thats horrible perl in the linux-base postinst May 31 13:48:46 more specifically it overrides the root= kernel parameter May 31 13:49:11 well, yes, if the file exists in the initrd it will use the value in there May 31 13:49:46 Perhaps I could try setting bootargs to omit root= in boot.scr, then I won't need that. May 31 13:50:52 * rbasak tries it May 31 13:50:56 hmm, i wonder where "DebianKernel::BootloaderConfig" comes from May 31 13:51:05 that seems to be the bit complaining May 31 13:51:41 if (!is_fresh_installation() && version_lessthan($ARGV[1], '2.6.32-18')) { May 31 13:51:41 DebianKernel::BootloaderConfig::check($deb_arch); May 31 13:51:41 } May 31 13:51:54 that seems to be the code snippet that causes the complaint May 31 13:55:52 and the real issue seems to be that "my @config_files " doesnt have anything for u-boot at all May 31 13:56:53 lool, any idea ? ^^^^ May 31 14:02:41 rbasak, hmm, looking closer it doews exactly what its supposed to be, what you see there is a note not an error May 31 14:03:46 ogra_: it stops the install with priority=critical. Not sure why, since the note is priority=high. May 31 14:05:01 well, but we should be able to preseed it differently to quieten it May 31 14:07:22 Shouldn't it be clever enough to detect flash-kernel and shut up? May 31 14:07:37 The warning is meaningless when flash-kernel is in use May 31 14:08:49 flash-kernel has nothing to do with it (as i said, its not a bootloader) May 31 14:09:09 the code looks for known bootloader configs and doesnt know about u-boot May 31 14:09:41 if i read it right it should be possible to switch that off by preseeding linux-base/disk-id-convert-auto to flase May 31 14:10:04 *false May 31 14:10:59 rbasak, do you have a virgin env around you could test that in ? May 31 14:11:27 I can test a preseed option, yes. May 31 14:11:42 or just hack the template of the package :) May 31 14:12:29 which i think we should do if the package moves to main, having it check the bootloader configs just for reading out the latest kernel version from /boot doesnt really make sense May 31 14:12:34 This is stupid though. I know that flash-kernel isn't a bootloader. But when we're using flash-kernel, then that depends on linux-base, and we know that no bootloader is required. So linux-base should not complain. It should detect flash-kernel as an exception to its warning, such that if flash-kernel is present it does not need to check for a bootloader and does not need to warn the user. May 31 14:12:56 well, i beg to disagree :) May 31 14:13:08 The message is "The boot loader configuration for this system was not recognized.". If flash-kernel is present, the boot loader configuration can be recognised. It's recognised as do-not-care. May 31 14:13:35 linux-base should learn about u-boot ... not about flash-kernel May 31 14:13:35 OK, well I'll file a Debian bug and see what they say about it. May 31 14:13:49 flash-kernel is where u-boot knowledge is kept. May 31 14:14:03 not always May 31 14:14:07 Specifically, in that DB now. How else is linux-base to discover the situation? May 31 14:14:31 specifically in debian where you are not required to use it at all for arm images May 31 14:14:32 If linux-base is taking it upon itself to figure out the situation, it should be able to figure out the situation correctly. May 31 14:14:42 right May 31 14:14:53 but it looks for bootloaders not for flashing tools May 31 14:15:11 flash-kernel is no longer a flashing tool May 31 14:15:21 thats its purpose May 31 14:15:45 just because we abuse it differently doesnt change its purpose in debian May 31 14:16:18 what i dont get in the beginning is why linux-base checks that stuff at all May 31 14:16:33 its only a tool to get you the latest kernel version in /boot May 31 14:19:19 just reading up a bit: I'd say that linux-base should be figuring out the situation correctly, so it should be looking for both bootloaders _and_ flashing tools May 31 14:19:20 rbasak, given we carry ubuntu changes in linux-base anyway 8and will go on doing so as long as debian ships perf in there) we should just change the preseed default May 31 14:19:37 I'm testing the preseed as we speak May 31 14:19:51 i will upload a change if that works and we should be done May 31 14:20:15 we really dont want it to touch any bootloader configs in any ubuntu arch anyway May 31 14:26:26 janimo: downgrades are typically disallowed meaning new exploits are required May 31 14:30:27 ogra_: no luck with the preseed. I tried "linux-base/disk-id-convert-auto boolean false" - was that right? May 31 14:34:25 ogra_: the flash-kernel change is working though, and ready: https://code.launchpad.net/~racb/ubuntu/quantal/flash-kernel/highbank2/+merge/108173 May 31 14:38:41 rbasak, awesome, i'll take care for linux-base, dont worry about it May 31 14:38:54 thanks ogra_! May 31 14:39:30 lilstevie, I was just looking at 'Wolf'd method' (sounds like some math theorem) on xda-forums which according to some allows ICS downgrades May 31 14:40:12 rbasak, could be be a bit more verbose in the README entry ? May 31 14:40:32 like "Calxeda highbank systems" or something like that ? May 31 14:41:15 ogra_: I started off doing that, then I realised that the machine type in the db needed to match /proc/cpuinfo, and I made the README match that too. I'm not sure if they're doing that with the other machines or not? May 31 14:41:54 no, i dont think armadaxp actually says "Marvell Armada XP Development Board (Ubuntu)" in cpuinfo :) May 31 14:42:02 :-) May 31 14:42:06 Go ahead and change if you like May 31 14:42:11 will do May 31 14:43:08 janimo: pm me please :) May 31 15:01:55 rbasak, merged and uploaded May 31 15:02:01 thanks ogra_! May 31 15:48:45 rbasak, linux-base uploaded with the postinst removed completely ... bug 1006717 is the MIR in case you want to follow it May 31 15:48:46 Launchpad bug 1006717 in linux-base "[MIR] linux-base" [Undecided,Incomplete] https://launchpad.net/bugs/1006717 May 31 15:49:01 thanks ogra_! May 31 15:49:40 (and i dont think its worth filing a debian bug for linux-base ... it makes totally non-ubuntuish assumptions all over the place :) ) May 31 17:28:31 ogra_: the "Marvell Armada XP Development Board" in flash-kernel (12.04) was copy/paste from cpuinfo. Just FYI. May 31 17:32:19 GrueMaster, well, it doesnt have (Ubuntu) appended in cpuinfo i bet May 31 17:32:49 i just think the README entry should get you an idea about the HW May 31 17:33:10 and "highbank" is somewhat not telling you anything :) May 31 17:36:34 I couldn't tell you what was in cpuinfo at this point. I'm a bit removed from the project. :P May 31 17:36:34 But iirc, I was the one that added the entry to flash-kernel, and it was a straight copy/paste. May 31 17:37:53 Since cpuinfo is largely just raw text from the arm soc code (i.e. not derived from silicon), it could have been (knowing Marvell). May 31 17:38:00 well, the db definitely needs the exact match ... the readme not so much May 31 17:38:15 Yes, agreed. May 31 17:39:01 Anyway, thought I'd add my $.02 worth. Back to my real job. May 31 17:39:11 heh, have fun May 31 18:14:43 ogra_: oh.. did i add Ubuntu to the wrong field? May 31 18:15:11 * dannf made that change post-test, after merging onto the ubuntu tree - might've screwed that up May 31 18:16:03 oh, nope - that's in the README. w/ that i was following suit w/ the precise's flash kernel which appeared to mark Ubuntu-only additions w/ (Ubuntu) May 31 18:16:12 but that's not in my debian tere May 31 18:55:56 Leave May 31 22:04:12 lilstevie, managed to downgrade using wolf May 31 22:04:25 wolf's method. great.now on to rooting May 31 23:33:18 janimo: :) **** ENDING LOGGING AT Fri Jun 01 02:59:58 2012