View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0007693Kali LinuxKali Package Bugpublic2022-05-04 09:312025-07-14 09:37
Reporteranticlimax18 Assigned Todaniruiz  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionsuspended 
Product Version2022.1 
Summary0007693: Samsung BIOS Killer
Description

I have an OLD Laptop, Samsung NP300E5X-A0BIN.
This has a Samsung Phoenix Bios Scala3-R CRV UEFI

Steps To Reproduce

I downloaded the bare metal ISO and made a bootable USB through rufus.
Then Shrinked my SSD Drive to get 20 GB
Installed the Kali Linux through Kali GUI setup
Everything went well, except now the BIOS doesn't Go in SETUP(F2) or Recovery mode (F4).
I removed the SSD from the Laptop and Tried to Boot and enter the BIOS.
It just restarts without entering bios and then shows Boot Menu (F10) to select a boot device which has only 1 Entry "KALI"
F9 Works to boot into USB, F10 Works. Can't Enter BIOS SETUP. Kali installation destroys the bios.

Additional Information

One user tried to Clear CMOS and that user bricked this laptop because after clearing CMOS the BOOT MENU gets EMPTY.
This is an old known bug and I think there has been a patch out for this long time in the Linux community.
I cannot use any other storage devices. That isn't the main issue. The BIOS SETUP is gone. So I tried to flash it back.
I tried to Flash Bios back, some process of flashing happens but when I restart, nothing has changed.
The Bios remains inaccessible even without any drive.
I also noticed that the Phoenix WinFlash UEFI Flash tool backs up BIOS and its only of 3MB instead of 8MB. The Original BIOS File is of 8MB
Please provide a solution.

Activities

daniruiz

daniruiz

2022-05-04 15:28

manager   ~0016110

Thank you for your interest in Kali but this is not a bug report. It looks like that you need help and guidance to perform some task. We have community support forums on https://forums.kali.org/ or on IRC with the #kali-linux channel on irc.oftc.net), please post your questions there.

Issue History

Date Modified Username Field Change
2022-05-04 09:31 anticlimax18 New Issue
2022-05-04 15:28 daniruiz Note Added: 0016110
2022-05-04 15:28 daniruiz Assigned To => daniruiz
2022-05-04 15:28 daniruiz Status new => closed
2022-05-04 15:28 daniruiz Resolution open => suspended
2025-07-14 09:36 g0tmi1k Priority high => normal
2025-07-14 09:37 g0tmi1k Severity block => minor