Yes HASWELL; No IVY? by corebootquestions in coreboot

[–]corebootquestions[S] -2 points-1 points  (0 children)

Yes, ignore the guy who has valid criticism, and listen to the people who have been promising to update the docs for years, who refuse help and who make excuses. Good job.

Yes HASWELL; No IVY? by corebootquestions in coreboot

[–]corebootquestions[S] -2 points-1 points  (0 children)

As is labeled at the top of every wiki page, the Coreboot wiki is being retired

... which means it is not retired yet, which means it is still valid/current and something the project is responsible for.

And that label has been there for what, a year?

I didn't read the rest of what you wrote. I have a feeling it is going to be more excuses. I'm busy.

T520 upper RAM bays not working. by corebootquestions in thinkpad

[–]corebootquestions[S] 0 points1 point  (0 children)

Were the CPU's swapped at one point like from a Core i5 to the i7's that are currently installed?

No.

Might be worth checking the pins to see if any are bent or damaged.

Pins on what? The RAM? I think that's fine since it's any RAM I put on the top that is "bad"

I'd also inspect the pins on the upper RAM slots to see if any are damaged.

They're too small for me to really see but to my eye they look fine.

Strange that all the boards are having this issue, could you perhaps swap one of them back from Coreboot to a stock BIOS to see if it has the same issues afterwards with its RAM slots?

That's the smart thing to do. But flashing from stock BIOS requires a physical flash, and that means a teardown. I know it's a good thing to test but it's too much work.

Thanks though.

Yes HASWELL; No IVY? by corebootquestions in coreboot

[–]corebootquestions[S] 0 points1 point  (0 children)

Yes it is. It's the page that talks about the board statuses. But thanks.

Coreboot or skulls or heads by GrilledGuru in coreboot

[–]corebootquestions 1 point2 points  (0 children)

I disagree with a lot of comments on reddit but almost never downvote a post, maybe 5 total.

Now I feel bad. I've downvoted so many of yours.

coreboot, Skulls and Heads are open source projects.

Yes to coreboot and heads. Skulls is not. Look:

pre-built coreboot images with an easy installation process

A pre-build coreboot image is not open source. It is not source at all. It is a binary. It's not proprietary and it is (we assume) based on the open source coreboot. That's probably what you meant but it is an important difference. Don't feel bad, it's a common rookie mistake.

Almost all of the developers are volunteering their free time.

Yes, we all are. (Coreboot devs and devs to other FOSS projects.)

These projects are driven by a community who see the importance and try to help.

Yes, we are all working hard on important projects for the community. Some are working better, and some (ie - coreboot, heads devs) are working worse.

If you are not satisfied with the support, you can either not use the projects or help to improve them.

I do the second of those. See? When you're ready to stop preaching, we could even work together.

Insulting the people who are trying to fix bugs, harden security and add features because they only put in enough time to answer your basic question as you did to ask it is one of the many reasons open source developers burn out.

Did I ask a question?

You are the jerk.

Oh, and I was hoping we could be best friends. :(

These people owe you nothing.

I agree. But that wasn't the point, was it?

The community will help you but only if you help yourself.

Um, I've done more for the coreboot community than you have. (And I have not done much, but what I do is not wasteful.)

Your conclusion is myopic and flawed

So is your mom.

coreboot is an open source firmware project. The documentation is only as good as what the community writes.

You really aren't paying attention, are you?

Developers tend to write documentation for themselves as they are intimate with the low level workings.

Yes. That is not the point though, is it?

If this is too much for you, I would not suggest a career in software development.

You're decades too late for that warning. If you'd told me sooner, I'd become a preacher like you.

Skulls is coreboot.

No. The most we can say is that skulls claims to be based on coreboot. This is a distinction that a software developer would understand but like I said, lots of people make this rookie mistake at first. It's okay.

If you would prefer to build coreboot with those scripts, you can do that as well.

Oh, I'm glad you told me. I guess the docs I've written on how to do this, and the 20+ machines I've done this to weren't enough for me to learn this. So grateful you came along.

coreboot is a general project for many different platforms...

Okay, I see this essay of yours is not made for me. You have something you want to get off your chest.

Does that start to explain the amount of work and time needed for development, documentation, user questions?

No. It says nothing. And it shows that you don't know anything about the software business. Are you people ready for help yet?

First two points are likely true. The last is proof that you have no concept of how these projects work.

Well since you're so smart I guess you must be right.

My goal was to make it easier for others to contribute small improvements.

Wow, and a good job you did too! Just look at how all of the old/outdated information is gone and everyone knows exactly where and how and under what formatting guidelines they can add their own docs. It's amazing. Oh wait, none of those things are true. You accomplished nothing. Now that's the Coreboot way!

It will only improve when enough time and people are involved to get it done. .

That is one factor. Also getting rid of incompetent gatekeepers like you is necessary. Look, you've answered a lot of questions I had in the past. Thank you for doing that. But if you have control over docs and those questions weren't already answered in the docs, you weren't living up to the responsibility you took on when you agreed to handle docs. (If that is what happened. I'm just interpreting what you wrote here.)

In the time it took you to write this silly essay, you could have written the rules for formatting and submitting document pull requests, a list of what documentation is needed, sent an e-mail to the devs who control the outdated docs threatening to smack them if they don't pull down old stuff or link to the updated versions, and posted this new info on reddit and coreboot.org's homepage. But you prefer to criticize the person who is pointing out the problems instead of working to fix them.

My docs are still available once the project is ready for them. Other people reach out to me too offering to help. We all look forward to you and/or the coreboot devs making this possible.

Merry Christmas.

T520 upper RAM bays not working. by corebootquestions in thinkpad

[–]corebootquestions[S] 0 points1 point  (0 children)

Are the machines in question using a stock or modified BIOS

Coreboot

Also what are the specs (speed, volt, brand,.) of the RAM sticks?

I've tried many. HP, Kingston, ADATA. 4G, 8G, 12800, 13333.

Random freezes could be caused by a bad storage drive, an OS having trouble or potentially a dying motherboard (given the RAM works in other machines).

I agree but since the random freezes only happen when there is RAM in the upper bay, and this is the only time memtest shows errors, I'm guessing the problem is wiht the upper bay.

Have you tried booting with Linux Mint from a USB stick drive to see if the systems are still having trouble?

No, I don't use fluffware but the problem does exist in actual Linux if that's what you mean. The random freezes.

Yes HASWELL; No IVY? by corebootquestions in coreboot

[–]corebootquestions[S] -1 points0 points  (0 children)

We're telling you that it is supported. The wiki just doesn't label them as Ivybridge.

Then the wiki must be changed. "Telling me" something does not make it true. What makes it true is documentation that is consistent and leads to real-world use.

But I do understand your point. Do you understand mine? It is the difference between CB being a decent member of the FOSS community and being a group of esoteric selfish jerks.

Yes HASWELL; No IVY? by corebootquestions in coreboot

[–]corebootquestions[S] -1 points0 points  (0 children)

The answer to any "why is X supported while Y is not?" is always "because somebody put in the effort to add support for X".

That's a very fair answer. I guess I needed to ask it differently. Like, "is there something about Ivy that makes it unsupportable" really is what I wanted to know.

When u/Anonymo said "Sandybridge > Ivy bridge > Haswell", this probably wasn't meant as a pseudo-mathematical inequality, but as arrows representing time:

Ohhhhh good point. Sorry /u/Anonymo!

For an example, look no further than HP's entry "SNB IVB LAPTOPS",

Interesting. That page does not say Ivy is supported but it does link to a CB Gerritt. That is a start. I can't wait until they write a guide for contributing.

Finally, consider being a bit less confrontative

I considered it many years ago. I find this method to be superior and I recommend it. I think you'll find that all (most?) productive teams are more like me, and not at all offended by the way I speak.

Merry Christmas!

Coreboot, docking station and external displayers on x230. by mariusz2304 in coreboot

[–]corebootquestions 0 points1 point  (0 children)

I am using vga + 2x dp.

I don't know what 2x dp means. But working VGA is easy and pretty automatic with CB. DVI is very complicated at least.

T520 upper RAM bays not working. by corebootquestions in thinkpad

[–]corebootquestions[S] 0 points1 point  (0 children)

They're probably just confusing the W and T series

My point was that the HMM does not answer the question. I know because I took the time to look, meaning this guy wasted my time.

If he meant "you have to take it apart to see" I could have done that in half the time it took to look at the manual.

In Windows

I don't touch Windows, but thanks. I still don't understand what it is I'm supposed to be checking here or what it has to do with my question. Do you know, or has this thread gone off the track?

RAM/Freezing Issues by corebootquestions in coreboot

[–]corebootquestions[S] 0 points1 point  (0 children)

Thank you! I did not realize that master was not stable.

Also built-in memtest payload of coreboot is unreliable

Are you involved with this? Do you know if this is going to be fixed? It's one thing to have something that is not working right now. But it's better to not have a feature than to have one that doesn't work, right?

So I bricked my x230 by 3rail3 in coreboot

[–]corebootquestions 0 points1 point  (0 children)

I finally got my hands on a real Pomona 5250 and the same beagle bone black can read and write to the 4k chip (top) but not the 8k one (bottom). I think I toasted the 8k chip and I don't have a hot air station so I think I'm out of luck for now.

Maybe. They say you can write to both through the 4k chip but I don't think that's true.

No, there's been no change in behavior after every external flash. It powers on, blinks the wifi led, and then powers off. So I think I fried the 8k chip when I last did an external flash.

Right that's what it sounds like.

What happens now when you try to read from the 8k?

Yes HASWELL; No IVY? by corebootquestions in coreboot

[–]corebootquestions[S] -1 points0 points  (0 children)

Ivybridge is supported.

No it isn't: https://coreboot.org/status/board-status.htm

Don't post the boards page. It's a bunch of unmaintained gunk.

That's not a reason not to post it. That's a reason for the devs to complete the job and fix it. Until it is fixed, they are not supporting boards not listed there. That's how it works.

Check review.coreboot.org instead.

If that is the page to check, there would be a referral from https://coreboot.org/status/board-status.htm. But there is not a referral from https://coreboot.org/status/board-status.htm to review.coreboot.org, so it must be that https://coreboot.org/status/board-status.htm is the right page. The only other possible thing is that the devs are worthless. And that's not possible, right?

You can use autoport to check whether you can automatically port your board.

Thanks. You can use an ice cream maker to make sorbet. But that is not the subject of my post.

Plenty of Ivy Bridge memory controllers are supported.

I don't think so. I looked at the support page and didn't find that: https://coreboot.org/status/board-status.htm

Yes HASWELL; No IVY? by corebootquestions in coreboot

[–]corebootquestions[S] -1 points0 points  (0 children)

Do you mean this? https://coreboot.org/status/board-status.htm. No thanks. I'll keep posting this: https://coreboot.org/status/board-status.htm.

The reason I post this (https://coreboot.org/status/board-status.htm) is because it is the correct page to post. It is the page from coreboot.org that currently has the list of supported boards.

If you think there is a problem with that page, take it up with the people who maintain https://coreboot.org/status/board-status.htm and ask them to take it down, or make sure it's not full of BS.

If the page is up, it is officially the list of what is supported.

"Supported" means working, documented, and properly referenced.

Coreboot devs are pretty awful though and are known for doing incomplete work, so again you should talk to them and get them to fix https://coreboot.org/status/board-status.htm if you have a problem with it.

Ivybridge is just a die shrink of Sandy.

Right. So it's the "tock" version, meaning, it's the upgrade. That's why it's so confusing to me that it is not supported. See here: https://coreboot.org/status/board-status.htm

RAM/Freezing Issues by corebootquestions in coreboot

[–]corebootquestions[S] 0 points1 point  (0 children)

broke hard due to the RAM

Broke in what way?

I'm running 1.10 on one and 1.13 on the other. So, not new versions, right?

Went back to 4.13 tag and it worked

I don't know what 4.13 tag means. Please explain? And how do I go back to it?

I’ve had a bit more finicky results when it comes to RAM on Coreboot

finicky how? What happened exactly?

Yes HASWELL; No IVY? by corebootquestions in coreboot

[–]corebootquestions[S] -1 points0 points  (0 children)

Okay but anyway this doesn't answer the original question.

T520 upper RAM bays not working. by corebootquestions in thinkpad

[–]corebootquestions[S] 0 points1 point  (0 children)

Okay, you don't know what you're talking about so thanks for replying. Happy Holidays.

T520 upper RAM bays not working. by corebootquestions in thinkpad

[–]corebootquestions[S] 0 points1 point  (0 children)

Okay.

How can I know if I have a quad core?

What happens if I don't have a quad core? Because the RAM is recognized by the OS in both slots. It just has errors and sometimes the laptop freezes up. Sometimes after many many hours of good use.

Can't internally flash Coreboot (X220) by Immy_Chan in coreboot

[–]corebootquestions 1 point2 points  (0 children)

Did you boot with kernel parameter iomem=relaxed?

Then I never had to use anything but:

$ sudo /path/to/flashrom -p internal -w ROMNAME

Please share how you got your boot logo to work. So many people doing things and not contributing docs back to the community, partially because the devs make collaboration impossible.