Linux and efifb

peterchristy955

New member
I bought a Lafite 14" i5 notebook about a year ago, and have been very pleased with it. I needed something compact for travelling, and yet powerful enough for video editing, and it fits the bill perfectly.

However, I have one small problem. I don't run windows, only Linux. My preferred distro is Slackware 64-bit (stable and fast). During the initial boot phase, Slackware uses either a vesa (for non-uefi systems) or uefi frame buffer until the kernel has fully loaded and the kernel-mode-setting kicks in. Unfortunately there seems to be a bug in the BIOS somewhere, as the screen remains blank until KMS has started.

Trawling through the system logs, I find "efifb: invalid framebuffer address" near the start of the boot log.

Normally this would not be an issue, as the system skips over this and just blanks the screen until KMS starts. However, if doing a clean install, this prevents de-bugging if anything is wrong with the installer! When I originally installed Slackware, I had to do a lot of lateral thinking to get around this! With a new stable release imminent (I'm currently running the development version, Slackware64-current), I would like to do a clean install once it is released. At present the installer hangs during the initial boot phase, and I can't debug it as I can't see what is happening!

It looks as if there is a bug in the BIOS that is failing to provide a proper address for the efifb frame buffer. Is an update available, and if so where can I get it? The version I have at present is 1.07.02TPCS

TIA,

--
Pete
 

ubuysa

The BSOD Doctor
Others have run into similar issues with Linux, you might want to look at other threads in this forum. Unfortunately for you, PCS do not support Linux on any build, only Windows I'm afraid, so the BIOS is setup only for Windows. Thus PCS will not be able to help you here at all and to make matters worse, if you flash a non-standard BIOS you will most likely void your warranty.
 

jerome_jm_martin

Bronze Level Poster
hi,

just thinking quickly : have you tried : nomodeset as a kernel parameter before booting ? if it's working, you will be able to finish the install.
 

peterchristy955

New member
Thanks for the responses! I know PCSpecialists don't support Linux, but I'm amazed that anyone can produce a "Windows only" BIOS in this day and age! Having said that, my first 64-bit computer was a laptop with an Insyde BIOS, and that was a nightmare too! I don't know who Insyde are, but boiling in oil is too good for them!

Yes, I've tried "nomodeset", to no avail. If you think about it, that forces the use of (in this case) efifb - which doesn't work because its reporting a bad address! And it won't boot any media that is not efi compliant.

To install Slackware, I first had to install Slackware-live (which does install without issue, other than the absence of the framebuffer), and then use slackpkg+ , pointed at the -current repository, to "update" the live distro to the standard one.

This does work, but seems to have left one or two residual configurations that are proving elusive to find. I was hoping that when 15 was released, I could do a clean install.

However, slackpkg+ does have an option to "clean" a system, and only leave what is also on whichever repository it is pointed at, so maybe I'll have to explore that route going forward.

In the meantime, I can only hope that a less buggy BIOS is released, or that someone can suggest a work-around for the efifb issue!

Cheers,

--
Pete
 

jerome_jm_martin

Bronze Level Poster
Hi,

for slack, i am not going to help you much, as I am more a debian user.

you are right about bioses, all of them are buggy (more or less) no matter who is the supplier or the manufacturer and it's a real pain...

I ve just bought a lafité iV 15'6, so far I am quite happy with it, nicely build.
But the big disappointment comes from the bios, heavily stripped down. mainly designed for intel tech and windows os.

Luckily mine does not have SATA mode hardcoded to raid therefore I can use the nvme drive.

also, I did switch off, TPM (faulty) and SGX guard (not necessary), there's minor issue with ax200 card, but nothing relevant.

and Yes that would be nice to have a well polished bios with no faulty implementation.

J.
 

peterchristy955

New member
I think I've finally found the issue - and its actually not the bios!

My laptop uses the Intel 620 graphics chip. This is known for having some issues with the Intel drivers in Linux, but in that regard, mine has been well-behaved.

However, during the initial stages of booting, only the efifb is available for screen output. It appears that the Intel 620 uses 64-bit addressing for the efifb, as opposed to the more common 32-bit - and not all bootloaders support 64-bit efifb addressing!

I managed to replace the stock bootloader with grub (excessively complicated, and a pig to configure!) and all of a sudden, everything worked like it should!

I've avoided grub like the plague after a few early bad experiences with it, but it looks like I'm going to have to bite the bullet now, and learn how to set it up properly!

Anyway, problem solved, I think!

--
Pete
 

SpyderTracks

We love you Ukraine
I think I've finally found the issue - and its actually not the bios!

My laptop uses the Intel 620 graphics chip. This is known for having some issues with the Intel drivers in Linux, but in that regard, mine has been well-behaved.

However, during the initial stages of booting, only the efifb is available for screen output. It appears that the Intel 620 uses 64-bit addressing for the efifb, as opposed to the more common 32-bit - and not all bootloaders support 64-bit efifb addressing!

I managed to replace the stock bootloader with grub (excessively complicated, and a pig to configure!) and all of a sudden, everything worked like it should!

I've avoided grub like the plague after a few early bad experiences with it, but it looks like I'm going to have to bite the bullet now, and learn how to set it up properly!

Anyway, problem solved, I think!

--
Pete
Well done, Pete, impressive, and good to know it's not a BIOS issue per se.
 

jerome_jm_martin

Bronze Level Poster
Hi pete,

glad to hear you've found the solution, playing with bootloaders is not fun at all, getting them to work as intended can be a real nightmare.
I also have fun stories with grub, lilo (a long time ago)...

J.
 

Stephen M

Author Level
Thanks for the info Pete and glad you got it working.

I have no issue with PCS not offering 'nix support, there are too many distros and it is still a minority interest - no one could justify the time and resources to try to do it but we are lucky on these fora to have a lot of good people who are providing support and a lot of useful advice.
 

ubuysa

The BSOD Doctor
Thanks for the info Pete and glad you got it working.

I have no issue with PCS not offering 'nix support, there are too many distros and it is still a minority interest - no one could justify the time and resources to try to do it but we are lucky on these fora to have a lot of good people who are providing support and a lot of useful advice.
You included! 🤓
 

cyberscape_7

New member
Others have run into similar issues with Linux, you might want to look at other threads in this forum. Unfortunately for you, PCS do not support Linux on any build, only Windows I'm afraid, so the BIOS is setup only for Windows. Thus PCS will not be able to help you here at all and to make matters worse, if you flash a non-standard BIOS you will most likely void your warranty.

I just wanted to check, I am currently looking at ordering a laptop from yourselves potentially looking to run linux on the device or dual boot for Windows. Am I right in saying the warranty would only be voided in the event that large changes are made? For example, flashing the BIOS as you said could void it, but making changes on the BIOS settings would be within the realm of acceptable behaviour?
 

ubuysa

The BSOD Doctor
I just wanted to check, I am currently looking at ordering a laptop from yourselves potentially looking to run linux on the device or dual boot for Windows. Am I right in saying the warranty would only be voided in the event that large changes are made? For example, flashing the BIOS as you said could void it, but making changes on the BIOS settings would be within the realm of acceptable behaviour?
Yes, you can make any changes to the BIOS setup that are available. PCS even let you open it up and add/replace your hardware. As long as you don't damage anything the warranty is good. You can flash a new BIOS too, as long as you get PCS's agreement first. Though obviously if they think the new BIOS may cause problems they won't agree.

Note that I don't work for PCS. Few of us on here do.
 

Stephen M

Author Level
As Ubuysa said and PCS despite not supporting Linux are very helpful and would give good advice about flashing the BIOS, although my view on BIOS flashing is that it should only be done as a last resort.

There is a good thread on these fora with a list of machine 'nix has worked on, plus some tips on getting it going. I have been a customer for almost 10 years and have successfully installed a 'nix distro on seven PCS machines, either my own or ones purchased for family and friends. I have never had a problem which could not be solved, although some did take a bit of swearing and banging my head against the wall but the general trend is that all distros are installing much easier now than they were a few years ago.

Things like going with "nomodeset" used to be a must now is rarely needed, there were driver glitches with some GPUs and unless the correct one was chosen the machine went into a log-in loop but I have not seen that for a couple of years now.

The major things that are still problematic are what I would term "cosmetic functions", things like back lights and the fingerprint scanner which are not really needed.

I would advise checking the list of laptops OK for 'nix and also posting your chosen specs here in case any of us can offer any advice.
 
Top