Re: [coreboot] T450S + Coreboot
Taiidan, > I doubt those guys have the skill to do so but for those who do - you'd > spend tens of thousands in order to have a port for an old machine that > still is stuck with ME and hardware init done entirely by binary blobs. It is not about the skill or money involved in the process, it is about the *possibility* of even running coreboot on said machine, which is most likely zero. > I would save your money and instead buy an ivy/sandybridge thinkpad (can > nerf the ME - but not disable which is impossible) AFAIK, you can still run me_cleaner on a Broadwell laptop. I don't think the ME is the main reason to get a XX20/XX30 Thinkpad over newer models. Mike, > microcode - is optional I assume you refer to microcode *updates*, not the microcode that is hard-coded inside the CPU. Still, I fail to understand why there is so much worry about microcode updates, as if they were going to open a backdoor of some sorts. To me, the only gain of not updating the microcode is in the number of bugs. I do understand temporarily delaying the updates of known unstable microcode versions while awaiting for a fix, though. > as far as I know its impossible to completely replace ME, only to trim > its' firmware as much as possible and hope for the best that it > doesn't have some undocumented "backdoor restore" mechanism that could > restore the original uncut blob under some conditions. Undoubtedly, > Intel ME is a backdoor, e.g. because it contains some antitheft > features which could be used to control your computer remotely: shut > it down, wipe or retrieve data from it, etc This makes me feel I should recall what Nico told you earlier: "please don't spread FUD on this list." Regards, Angel Pons -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] T450S + Coreboot
Hello Brian, As far as I am concerned, Haswell or newer ThinkPads ship with Intel Boot Guard enabled in Verified Mode. This prevents coreboot from running on them. I assume this is the case on your machine as well, thus I advise you to check before proceeding, to avoid wasting time. Best regards, Angel Pons On Tue, Aug 28, 2018, 00:48 Brian Herman wrote: > im sorry i should really read the documentation first i want to create the > support for a t450s ill do that this weekend > > Sent from my iPhone > > > On Aug 27, 2018, at 8:34 AM, Mike Banon wrote: > > > > Sorry but T450S is not supported by coreboot. > > Here is a list of laptops that ARE supported: > > https://www.coreboot.org/Supported_Motherboards/old > > On Mon, Aug 27, 2018 at 4:23 AM Brian Herman > > wrote: > >> > >> I am in contact with a person with the means to reprogram a T450S. > >> https://www.allservice.ro/forum/viewtopic.php?t=1311 > >> What would I have to do to make coreboot work? > >> I think I would have to have two laptops or at least motherboards right? > >> -- > >> coreboot mailing list: coreboot@coreboot.org > >> https://mail.coreboot.org/mailman/listinfo/coreboot > > -- > coreboot mailing list: coreboot@coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot > -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] How to send a patch?
Hello Jorge, You can submit the patch yourself, check out https://doc.coreboot.org/lessons/index.html as a reference. Regards, Angel Pons Pons On Mon, Aug 20, 2018, 19:22 Jorge Fernandez Monteagudo wrote: > Hi > > I would like to contribute with some questions I've found trying to > running an AMD Bettong board. > > Attached is a little patch to enable the SATA and to set the > domain_acpi_name... If someone could review it and upload it to > repository... > > Thanks! > -- > coreboot mailing list: coreboot@coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] undefined reference to '__udivmoddi4'
Hello Norman, As far as I know, coreboot runs in 32-bit mode on the x86 architecture, even if the hardware supports x86_64. This does not prevent running x86_64 OSes. Therefore, and as the first document you linked says, you should build the i386 toolchain and build coreboot with it. Kind regards, Angel Pons Pons On Sun, Aug 19, 2018 at 8:43 PM, wrote: > Hello, > > I am trying to build coreboot for a Lenovo Thinkpad x201. > > I followed the instructions from the following documents: > https://doc.coreboot.org/lessons/lesson1.html > https://www.coreboot.org/Build_HOWTO > > When using the crossgcc-x64 toolchain building works fine but linking > fails with the following error: > coreboot/src/console/vtxprintf.c:102: undefined reference to > '__udivmoddi4' > > As far is i could find out this error should not even get thrown for x64, > since `__udivmoddi4` is an optimization for i386. [0] > > Building (and linking) with the crossgcc-i386 toolchain works fine though. > But I guess x64 features will then be missing in the build. > > Is there currently a way to build a x64 version of coreboot or do I have > to go with i386 for now? > > [0] https://stackoverflow.com/questions/51457851/building- > coreboot-undefined-reference-udivmoddi4 > > best regards > > Norman Wilms > > -- > coreboot mailing list: coreboot@coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot > -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Warnings/Errors while building coreboot toolchain
Hello, Could you please specify what coreboot branch are you using and what board are you building coreboot for? If your board is not in coreboot's tree, could you please link it? Regards, Angel Pons On Tue, Aug 14, 2018, 12:20 wrote: > I liked to build an image for an Intel G41 based mainboard and got that > in the build log: > > > coreboot toolchain v1.52 June 11th, 2018 > dsdt.aml 1525:CreateDwordField (PBUF, 0, PIO0) > Remark 2089 - Object is not referenced ^ (Name [PIO0] is > within a method [_GTM]) > > dsdt.aml 1526:CreateDwordField (PBUF, 4, DMA0) > Remark 2089 - Object is not referenced ^ (Name [DMA0] is > within a method [_GTM]) > > dsdt.aml 1527:CreateDwordField (PBUF, 8, PIO1) > Remark 2089 - Object is not referenced ^ (Name [PIO1] is > within a method [_GTM]) > > dsdt.aml 1528:CreateDwordField (PBUF, 12, DMA1) > Remark 2089 - Object is not referenced ^ (Name [DMA1] is > within a method [_GTM]) > > dsdt.aml 1529:CreateDwordField (PBUF, 16, FLAG) > Remark 2089 - Object is not referenced ^ (Name [FLAG] is > within a method [_GTM]) > > dsdt.aml 1534:CreateDwordField (Arg0, 0, PIO0) > Remark 2089 - Object is not referenced ^ (Name [PIO0] is > within a method [_STM]) > > dsdt.aml 1535:CreateDwordField (Arg0, 4, DMA0) > Remark 2089 - Object is not referenced ^ (Name [DMA0] is > within a method [_STM]) > > dsdt.aml 1536:CreateDwordField (Arg0, 8, PIO1) > Remark 2089 - Object is not referenced ^ (Name [PIO1] is > within a method [_STM]) > > dsdt.aml 1537:CreateDwordField (Arg0, 12, DMA1) > Remark 2089 - Object is not referenced ^ (Name [DMA1] is > within a method [_STM]) > > dsdt.aml 1538:CreateDwordField (Arg0, 16, FLAG) > Remark 2089 - Object is not referenced ^ (Name [FLAG] is > within a method [_STM]) > > dsdt.aml 1562:CreateDwordField (PBUF, 0, PIO0) > Remark 2089 - Object is not referenced ^ (Name [PIO0] is > within a method [_GTM]) > > dsdt.aml 1563:CreateDwordField (PBUF, 4, DMA0) > Remark 2089 - Object is not referenced ^ (Name [DMA0] is > within a method [_GTM]) > > dsdt.aml 1564:CreateDwordField (PBUF, 8, PIO1) > Remark 2089 - Object is not referenced ^ (Name [PIO1] is > within a method [_GTM]) > > dsdt.aml 1565:CreateDwordField (PBUF, 12, DMA1) > Remark 2089 - Object is not referenced ^ (Name [DMA1] is > within a method [_GTM]) > > dsdt.aml 1566:CreateDwordField (PBUF, 16, FLAG) > Remark 2089 - Object is not referenced ^ (Name [FLAG] is > within a method [_GTM]) > > dsdt.aml 1571:CreateDwordField (Arg0, 0, PIO0) > Remark 2089 - Object is not referenced ^ (Name [PIO0] is > within a method [_STM]) > > dsdt.aml 1572:CreateDwordField (Arg0, 4, DMA0) > Remark 2089 - Object is not referenced ^ (Name [DMA0] is > within a method [_STM]) > > dsdt.aml 1573:CreateDwordField (Arg0, 8, PIO1) > Remark 2089 - Object is not referenced ^ (Name [PIO1] is > within a method [_STM]) > > dsdt.aml 1574:CreateDwordField (Arg0, 12, DMA1) > Remark 2089 - Object is not referenced ^ (Name [DMA1] is > within a method [_STM]) > > dsdt.aml 1575:CreateDwordField (Arg0, 16, FLAG) > Remark 2089 - Object is not referenced ^ (Name [FLAG] is > within a method [_STM]) > > -- > coreboot mailing list: coreboot@coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot > -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
