**** BEGIN LOGGING AT Sun Apr 18 03:00:04 2021 Apr 18 08:08:35 Spyro1248: if you used nanddump to save with OOB data then there should be a reasonably easy way to process it. Apr 18 10:44:34 Build [#57](https://buildbot.openwrt.org/master/images/#builders/31/builds/57) of `layerscape/armv8_64b` completed successfully. Apr 18 10:54:23 PaulFertser: I tried restoring the nanddump to the device, but no luck. I've bollixed something up there. Apr 18 10:57:14 Spyro1248: I'm talking about processing the dump on a host Apr 18 10:57:38 By removing OOB data, you just need to know how large it is and how often. Apr 18 11:11:16 PaulFertser: perhaps, but I'd prefer not to, its a lot of work for probably not much gain... Apr 18 11:20:22 Spyro1248: do you know about mtdram trick? You load kernel module with appropriate options and can probably put the dump on it, and then use binwalk normally etc. Apr 18 11:21:07 Not really sure but something like that might be possible. Apr 18 11:22:32 nandsim Apr 18 11:23:56 Oh, found nice tool: https://www.j-michel.org/blog/2014/05/27/from-nand-chip-to-files Apr 18 11:27:13 Spyro1248: that nandsim looks like it can really do it easily for you Apr 18 11:29:49 PaulFertser: I'd forgotten about nandsim... I might look at that later... (got a HH5a on the bench today... Apr 18 11:41:35 hurricos: I see you've been playing around with mpc85xx too.. I have a t1042 and t2081 based device, but I keep hitting walls with porting OpenWrt to them Apr 18 11:42:23 hurricos: fyi I managed to build u-boot and load it via oct-remote-boot using the PCI remote protocol Apr 18 11:44:46 hurricos: that P2041RDB, did you happen to run any network performance tests on it? Apr 18 11:48:55 Build [#55](https://buildbot.openwrt.org/master/images/#builders/64/builds/55) of `realtek/generic` completed successfully. Apr 18 13:38:42 Hi guys Apr 18 15:00:40 PaulFertser: the hh5a instructions are dangerously out of date and rely on off-site magic... Apr 18 15:01:17 Is there any way to find outr who is maintaining ports for which routers? Apr 18 15:02:48 PaulFertser: I did manage to install the hh5a I had here, by using the prepare script from the lede 17 image, and then loading a normal 19.07 kernel+initramfs, and using it to sysupgrade to 19.07 to install. Apr 18 15:03:11 Spyro1248: you can just check "git log" for files in questions, and wiki history for the pages. Apr 18 15:03:28 I have another HH5A here I'd like to repurpose, so I wantr to improve the install procedure. Apr 18 15:03:47 PaulFertser: so there's no "canonical" reference for port maintainers? Apr 18 15:03:59 Spyro1248: what kind of information do you have in mind? Apr 18 15:05:02 PaulFertser: nothing specific - its just my observation that each router will probably have one person who knows more than anyone else about its quirks - I want to talk to them... Apr 18 15:05:52 PaulFertser: eg. who did the initial "install kernel + initramfs" and where are the sources? how will I replicate it if I plan to update it to 19.07 or later? Apr 18 15:05:52 Spyro1248: usually whoever does the port is supposed to add installation instructions to the commit message in question. That's a rule for few years now, but it wasn't it the lede days. Apr 18 15:06:16 Spyro1248: and then people add information to the wiki... Apr 18 15:06:34 you refer to git, but by that, what repo do you mean? Apr 18 15:06:43 Spyro1248: most probably the idea was to prepare some minimal initramfs so that it would fit some constraint of the bootloader, idk. Apr 18 15:07:01 Spyro1248: just the OpenWrt git repo, git://git.openwrt.org/openwrt/openwrt.git Apr 18 15:07:21 PaulFertser: the hh5a install procedure seems special somehow - Ive not investigated thoroughly yet, but looks like the way they unlock the bootloader is odd. Apr 18 15:08:35 I need the sources to that Lede 17 install kernel, and Im not sure where to find them. Apr 18 15:08:40 Spyro1248: well, probably you'll have to reproduce that result by reading the commit and trying some things on your own. Apr 18 15:08:54 Spyro1248: I'd try with the current kernel to see what's happening. Apr 18 15:10:02 PaulFertser: you misunderstand - there is something *special* about the install image. see: https://github.com/mkresin/BTHH5a-installimage/releases Apr 18 15:10:30 its actually a stupid install procedure - I think it predates the install image having working networking or something Apr 18 15:10:53 all done from a USB stick, when it can be (as I just have) done via the network. Apr 18 15:11:37 Spyro1248: so it's https://github.com/mkresin/BTHH5a-installimage/commit/76e1aba99184bc84fc955dd36d1c0a0ce942afb7 basically? Apr 18 15:12:00 I just noticed its on github... I cant believe I didnt spot that, PMSL. Apr 18 15:14:41 PaulFertser: I assume the project has a buildbot that produces the official images? Apr 18 15:14:52 Spyro1248: OpenWrt -- yes Apr 18 15:14:55 PaulFertser: how / who decides whats going to go in there? Apr 18 15:15:36 ie. I'd like to update the code a bit so that hh5a gets an up to date install image that can just sysupgrade via the network... Apr 18 15:15:49 but Im not going to put the effort in if its not going to be accepted. Apr 18 15:16:17 Spyro1248: the maintainers. What's special about that script or version I'm seeing that it doesn't allow sysupgrade over the network? Apr 18 15:19:00 PaulFertser: I think its mainly too old - I tried using the Lede 17 image to sysupgrade to the 19.07 image, and it wouldnt do it. Apr 18 15:19:42 Spyro1248: I think it's worth providing an updated image, yes. OpenWrt has a notion of -factory images that are built by the regular build system and should be installable by vendor firmware. Apr 18 15:19:54 so having already run the "prepare" script under lede 17 that unlocked u-boot, I booted the 19.07 kernel+initramfs, and sysupgraded from there Apr 18 15:20:27 Spyro1248: whether in this particular case it's better to try to get it to the main repository or it's ok to keep it as mkresin did is not yet clear. Apr 18 15:21:05 I dont know that we will ever have factory images for hh5a, but the "pre install" image is vital, and out of date enough to prevent directly installing 19.07 Apr 18 15:22:09 Also, I found the word firmware to be confusingly overloaded on the hh5a page - its used to refer to the wifi and the router firmware and its not very obvious which unless you already know... Apr 18 15:27:53 Spyro1248: yeah, all good points Apr 18 15:33:06 Spyro1248: the install image has a lot of packages preinstalled which are usually not required Apr 18 15:34:10 Spyro1248: beside of that, the uboot as well the uboot env are encrypted. the basic task of the image is to decrypt the env and unlock the env Apr 18 15:35:10 using the encryption keys from a decrypted uboot. all stuff that doesnÄt belong into the main openwrt repository, since it's special one time use stuff Apr 18 15:38:11 mkresin: but its getting out of date Apr 18 15:38:41 sure, it might not be perfect. but good enough to get the initial job done Apr 18 15:39:08 at least for the 7500 people who downloaded the image so far Apr 18 15:39:13 PaulFertser: when performing a build from git - if you change branch, do you need to re-do step 2.3 shown here: https://openwrt.org/docs/guide-developer/quickstart-build-images Apr 18 15:39:38 mkresin: I've used it several times now - today I found out that you cant (apparently) install 19.07 from it. Apr 18 15:39:51 (not directly anyhow) Apr 18 15:40:42 hurricos: could you tell me in what git tree you found those patches for vsc848x and the memory accessor ? Apr 18 15:41:37 Spyro1248: which isn't what the guide tells you do to. it links to a 17.04 image, which should you have on a flash drive Apr 18 15:43:09 mkresin: indeed - it says to use one of "One of openwrt-lantiq-xrx200-bt_homehub-v5a-squashfs-sysupgrade.bin openwrt-18.06.x-lantiq-xrx200-bt_homehub-v5a-squashfs-sysupgrade.bin lede-lantiq-xrx200-BTHOMEHUBV5A-squashfs-sysupgrade.bin" Apr 18 15:43:23 which isnt confusing at all... Apr 18 15:43:47 At least on here it does (https://openwrt.org/toh/bt/homehub_v5a) Apr 18 15:44:40 anyhow - you only seem to need to use the 17 image to decrypt / unlock u-boot. after that, it was easy and fast to install 19.07 directly Apr 18 15:44:40 well, I'm talking about https://github.com/mkresin/BTHH5a-installimage/releases/tag/v1.0 Apr 18 15:44:51 mkresin: I'm not... Apr 18 15:45:19 It seems to me that most people would consider the OpenWRT wiki the canonical reference, but its wrong. Apr 18 15:45:21 yeah, but that is where you get the file from. Apr 18 15:45:44 Sure - Im not criticising your page - its internally consistent. Apr 18 15:45:52 the owrt wiki is not. Apr 18 15:46:53 would you be so kind to fix the owrt wiki page than Apr 18 15:47:05 mkresin: Im happy to. Apr 18 15:47:49 mkresin: Im thinking I might eliminate the need for the USB stick, though, by updating the install image Apr 18 15:47:58 I couldnt get networking to work on the 17 image Apr 18 15:48:41 in fact, it ought to be possible to build a much smaller install image with *just* the u-boot shenannigans on it... Apr 18 15:49:48 if I can get it to work with networking, I can eliminate the USB stick step altogether. Apr 18 15:50:49 please leave the reference to flash drive in place. It's required for the backup for example. the way it's now, it was tested multiple times Apr 18 15:51:17 the install image is as much trimmed as I was able to do. Apr 18 15:52:21 mkresin: if I can build an install image with networking working, surely its easier to have people just scp the data over? Apr 18 15:53:33 and where would you like to store the backup of the 128MB flash chip? Apr 18 15:53:39 Build [#30](https://buildbot.openwrt.org/openwrt-21.02/images/#builders/49/builds/30) of `bcm53xx/generic` completed successfully. Apr 18 15:54:36 mkresin: I'd do something like ssh root@router "nanddump " > original_hh5a_fw.bin Apr 18 15:54:54 mkresin: no intermediate file, and the whole image is transferred direct to my PC Apr 18 15:58:37 it's intended as an easy to use image. requiring ssh isn't easy anymore. at least not for the windows users Apr 18 16:00:56 if you're already using serial, surely ssh isnt beyond you? Apr 18 16:01:42 you miss the point of the target audience. sure no problems for us. but the way it is now, it's more or less idiot proof Apr 18 16:02:48 which was exactly my intention. since I'm not interested in getting spammed with support/help requests Apr 18 16:03:21 and it worked so far Apr 18 16:03:47 *worked out Apr 18 16:04:19 fair enough, but I found that step a pain in the arse TBH. Apr 18 16:05:09 in any case, you dont HAVE to use ssh. you could do a nand dump via the web interface in principle - even easier for the windows n00bs Apr 18 16:07:29 mkresin: is your install image a direct fork of lede dated 2017-11-03? (ie. can I add it as a remote to my openwrt repo without causing havoc?) Apr 18 16:09:12 yes it's a fork from the lede v17.01.4 tag Apr 18 16:09:20 mkresin: cheers :) Apr 18 16:10:30 mkresin: ooi, whats the logic behind taking a full backup of the router, rather than just the calibration data for the wifi? is it purely to allow it to be flashed to stock? Apr 18 16:11:10 Spyro1248: exactly. allow to go back to stock. Apr 18 16:11:31 mkresin: one more - where is the wifi calibration data hiding? Apr 18 16:14:35 Spyro1248: it's a volume in the ubi Apr 18 16:16:32 mkresin: cheers :) Apr 18 16:17:56 when you use the build system to build images - are the default settings (other than *which* router you pick) the same as those used to build the official images? Apr 18 16:18:07 or is there a set of official defconfigs? Apr 18 16:19:04 also, whats a reasonable build time for the whole lot? Apr 18 17:10:37 anyone got a spare HH5A psu ? Apr 18 17:10:59 I have a spare hub here for dev work, but no PSU - and its a bit of an oddball size connector... Apr 18 17:19:27 i was playing around with the x86 target and how it behaves if storage backing the image is read-only. instead of using the space beyond suqashfs marker as overlay, the overlay is created on a ramdisk. I would have expected no overlay being created at all. Is having a r/w overlay a hard requirement nowadays for running OpenWrt or am I missing (other) obvious reasoning for this behaviour? Apr 18 17:21:04 rw: overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work) Apr 18 17:21:07 ro: overlayfs:/tmp/root on / type overlay (rw,noatime,lowerdir=/,upperdir=/tmp/root/upper,workdir=/tmp/root/work) Apr 18 17:26:16 updated openwrt/upstream, https://sdwalker.github.io/uscan/index.html Apr 18 17:28:21 ah, all that magic is handled within (lib)fstools - no wonder grepping within openwrt.git didn't yield anything useful Apr 18 17:36:49 hurricos: I started playing around with your openwrt code for the snic10e, did major cleanup and managed to hack the vsc driver to get it to compile (it needs some more work though but let's see if I can try to boot an image now) Apr 18 17:36:54 hurricos: https://git.openwrt.org/?p=openwrt/staging/stintel.git;a=shortlog;h=refs/heads/snic10e-5.10 Apr 18 17:37:04 also based on 5.10 instead of 5.4 Apr 18 17:40:33 the only problem I'm having now is that I cannot abort autoboot in the u-boot built with the SDK Apr 18 17:45:09 any key I press reduces the number of the 10s countdown timer rather than aborting it Apr 18 17:45:10 sigh Apr 18 17:46:38 aha, I can fix that with an envfile containing autoboot=-1 Apr 18 17:46:39 yay Apr 18 17:49:17 great, managed to boot the image. now to fix the serial console still Apr 18 18:05:43 hi Apr 18 18:05:55 is someone here with owner rights for the openwrt package repo? Apr 18 18:06:15 Hello, what can I do for you? Apr 18 18:06:33 my account got removed from the devs because i didn't setup 2fa Apr 18 18:06:41 i did this now, can you please readd me Apr 18 18:06:56 That's question for aparcar[m]^ Apr 18 18:07:17 aparcar[m]: please help Apr 18 18:12:47 tripolar: your github handle is "tripolar" as well? Apr 18 18:14:50 ah I see it in the audit log Apr 18 18:15:23 tripolar: invite sent Apr 18 18:43:53 jow thanks Apr 18 18:46:00 jow where do i get the invitation? Apr 18 18:46:45 jow found it thanks Apr 18 18:54:11 have a nice day Apr 18 19:16:44 did we find the lone ranger that did not enable 2FA? :D Apr 18 20:05:44 @freenode_tripolar:matrix.org: good to have you back Apr 18 20:24:35 aparcar[m]: he's already gone Apr 18 20:24:54 ¯\_(ツ)_/¯ Apr 18 22:30:28 hurricos: so apparently there's a heisenbug :( Apr 18 22:33:07 hurricos: I added some pr_info statements similar to what you did, and without them, boot process freezes after: [ 193.546685] Interface 1 has 1 ports (XAUI) Apr 18 22:33:21 but with a few pr_info statements that bug disappears :/ Apr 19 00:12:50 Build [#29](https://buildbot.openwrt.org/openwrt-21.02/images/#builders/70/builds/29) of `x86/legacy` completed successfully. **** ENDING LOGGING AT Mon Apr 19 02:59:56 2021