07/06/12 ROM breaks resolver??
Frederick Bambrough (1372) 837 posts |
BB -xM Rev C The ROM from 7th seems to stop both Hermes & Newshound with an unable to resolve error. Reverting to the 04/06/12 ROM returns correct operation. |
Chris Gransden (337) 1207 posts |
As a workaround you can just do a ‘rmreinit resolver’. |
Frederick Bambrough (1372) 837 posts |
Ta, that works but I’m not sure why I’d want to workaround. This issue doesn’t seem to affect NetSurf, which seems happy with either version. ‘Confused of Clapham’ |
Chris Gransden (337) 1207 posts |
I believe NetSurf uses it’s own name resolution so doesn’t use the Resolver module. Looks like it is to do with the order of the modules in the rom.I’ve just built a rom with EtherUSB moved to before Resolver. This seems to fix it. |
Jeffrey Lee (213) 6048 posts |
I did add a couple of modules to the ROM in order to get OS_SerialOp working, so it looks like Resolver will have become unintentionally unplugged for anyone who previously had BootNet unplugged. |
Frederick Bambrough (1372) 837 posts |
Rmreinit resolver doesn’t survive a reboot, if that’s relevant here. Only unplugged modules are Freeway & ShareFS. |
Frederick Bambrough (1372) 837 posts |
Am I correct in thinking this is now fixed? Having removed my obey file to init resolver, seems fine. |
Jeffrey Lee (213) 6048 posts |
Nobody explicitly fixed it. However the addition of the SDFS modules will have shuffled things around again, so now you’ll have some other module unplugged instead (looks like it should be BootCommands, but if that was unplugged then your boot sequence would probably get stuck). RMReinit should RMReinsert any modules that are unplugged, so if that wasn’t being saved over reboot then I guess you don’t have a CMOS widget installed? In which case the SDCMOS module should allow you to sort things out properly. Unless Resolver was never unplugged at all, and there’s some other reason why it was failing on boot. I haven’t run into any problems myself, so I’m not sure what the problem could be. |
Frederick Bambrough (1372) 837 posts |
I do have the widget installed. Resolver wasn’t unplugged. I thought from Chris’ comments above that perhaps the resolver issue was due to a re-ordering of the modules. Everything’s working fine now. I just wondered if that was a result of an intentional fix or an unintentional fix by virtue of some other activity. I presume the latter. |