Technology

34449 readers

473 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.

Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.

Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago

MODERATORS

MinutePhrase@lemmy.ml

Putting CoreBoot on a Dell Latitude E6320? (lemmy.ml)

submitted 1 year ago by Bigou@lemmy.ml to c/technology@lemmy.ml

2 comments fedilink hide all child comments

Hello peoples! I have a bit of a problem and hope you can help me with it.

I have an old Dell Latitude E6320 who worked greatly until yesterday. Since then, he seems to fail at POST. (Not sure, since he just show a splash-screen with a big "DELL" logo, under which is written "Latitude E6320" and the version of its UEFI. (Wrongfully called BIOS by the computer.)

If I try to access the BIOS, all or part of the screen turn black. (The non-black part, when there is one, still show the corresponding portion of the UEFI's boot-screen.)

To me it doesn't seem to be a hardware problem, more like a corruption of the UEFI itself. (Don't ask me how that's possible when I didn't even try to flash it, I have no idea.)

I would like to know if it's possible to compile CoreBoot or any of its derivate for it (and then flash it) or, failing that, if there is a way to try and change its UEFI config from a separate computer, in case it was just a corruption of some of the UEFI's parameters rather than the UEFI itself.

Hope someone will be able to help save that laptop, I would hate to trow away a good computer, perfectly suiting my needs.

#Dell_Latitude #Latitude_E6320 #Dell_E6320 #CoreBoot #save_my_PC #save_my_laptop

top 2 comments

sorted by: hot top controversial new old

[–] drone328@midwest.social 2 points 1 year ago (1 children)

I'm not an expert, but it sounds like a hardware problem. I've experienced something similar when a ram stick failed. If you have multiple ram stucks, can you remove one and try booting? This helped me diagnose in the past. UEFI I don't think goes bad too often, but ram fails a lot and is easy to check. Sorry that I can't help with your coreboot question.

[–] Bigou@lemmy.ml 3 points 1 year ago

I asked the same question on Reddit, and peoples there seems to agree with you. Even if I could make my PC start again, an UEFI corruption isn't something that would happen without a component on the motherboard dying first. (In fact, the firmware might not be corrupted at all.)

A parameter corruption is a bit more susceptible to happen, (not by much, mind you) but would correct itself if I remove the CMOS battery long enough.

As for the RAM, I tried with another pair I had lying around, but it might not be compatible with this computer. (It is supposed to support RAM sticks of 8GB max, but I know some computers don't like when there is more than 4chips on each stick, and those 8GB ones have 8chips by stick.) I'll try each of its original 4GB sticks on each of its RAM emplacement this W.-E. I will post the result of all those last tests here, naturally.

Thanks for taking the time to read and give your opinion on my problem, it's greatly appreciated.