During boot time KERNEL complains about BIOS "version not recognized". The only issue I notice is that my laptop freezes if I try to put it in "hibernate" mode. From dmidecode output: BIOS Information Vendor: LENOVO Version: A2CN34WW(V2.02) Release Date: 02/28/2015 Address: 0xE0000 Runtime Size: 128 kB ROM Size: 8192 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) Japanese floppy for Toshiba 1.2 MB is supported (int 13h) 5.25"/360 kB floppy services are supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) 8042 keyboard services are supported (int 9h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.34 Firmware Revision: 2.34 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: LENOVO Product Name: 80E3 Version: Lenovo G50-45 Serial Number: 1053977701475 UUID: 5D57984A-ABD9-E411-A961-68F728B775CB Wake-up Type: Power Switch SKU Number: LENOVO_MT_80E3_BU_idea_FM_Lenovo G50-45 Family: IDEAPAD Please let me know if more information is needed/wanted. P.S.: The same laptop works fine with kernels 4..6.7, 4.6.0 and 4.5.2. Thanks, SoZe
(In reply to Jose Soares Junior from comment #0) > During boot time KERNEL complains about BIOS "version not recognized". please attach the dmesg output containing this message. > The only issue I notice is that my laptop freezes if I try to put it in > "hibernate" mode. Not sure if it's related. > P.S.: The same laptop works fine with kernels 4..6.7, 4.6.0 and 4.5.2. I guess you mean Hibernation works well in 4.5 and 4.6 kernel, right? does the BIOS message still exist in these two kernels? what's the earliest kernel that hibernation fails?
ping...
Bug closed as there is no response from the bug reporter. Please feel free to reopen it if you can provide the information requested.