Ask Your Question
0

many problems to boot since last upgrade to 22 [closed]

asked 2016-03-07 11:59:06 -0600

medioem27 gravatar image

Hi I have many problems to boot my f22 after an upgrade from f21. I think the problem concern systemd. Simply I boot and fedora stuck before the console login. The following is the boot log taken from a live cd:

Jan 22 19:55:02 localhost kernel: Linux version 4.2.8-200.fc22.i686 (mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 5.3.1 20151207 (Red Hat 5.3.1-2) (GCC) ) #1 SMP Tue Dec 15 17:29:29 UTC 2015
Jan 22 19:55:02 localhost kernel: x86/fpu: Legacy x87 FPU detected.
Jan 22 19:55:02 localhost kernel: x86/fpu: Using 'lazy' FPU context switches.
Jan 22 19:55:02 localhost kernel: e820: BIOS-provided physical RAM map:
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bb5a6fff] usable
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bb5a7000-0x00000000bb5eefff] ACPI NVS
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bb5ef000-0x00000000bb5f9fff] ACPI data
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bb5fa000-0x00000000bb5fcfff] ACPI NVS
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bb5fd000-0x00000000bb620fff] reserved
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bb621000-0x00000000bb621fff] usable
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bb622000-0x00000000bb629fff] ACPI NVS
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bb62a000-0x00000000bb62cfff] reserved
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bb62d000-0x00000000bb631fff] ACPI NVS
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bb632000-0x00000000bb651fff] reserved
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bb652000-0x00000000bb694fff] ACPI NVS
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bb695000-0x00000000bb7fffff] usable
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000bde00000-0x00000000bfffffff] reserved
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jan 22 19:55:02 localhost kernel: BIOS-e820: [mem 0x0000000100000000-0x0000000137ffffff] usable
Jan 22 19:55:02 localhost kernel: Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
Jan 22 19:55:02 localhost kernel: SMBIOS 2.6 present.
Jan 22 19:55:02 localhost kernel: e820: last_pfn = 0xbb800 max_arch_pfn = 0x100000
Jan 22 19:55:02 localhost kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
Jan 22 19:55:02 localhost kernel: found SMP MP-table at [mem 0x000fcda0-0x000fcdaf] mapped at [c00fcda0]
Jan 22 19:55:02 localhost kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Jan 22 19:55:02 localhost kernel: init_memory_mapping: [mem 0x35800000-0x35bfffff]
Jan 22 19:55:02 localhost kernel: init_memory_mapping: [mem 0x00100000-0x357fffff]
Jan 22 19:55:02 localhost kernel: init_memory_mapping: [mem 0x35c00000-0x373fdfff]
Jan 22 19:55:02 localhost kernel: RAMDISK: [mem 0x35d42000-0x36e98fff]
Jan 22 19:55:02 localhost kernel: ACPI: Early table checksum verification disabled
Jan 22 19:55:02 localhost kernel: ACPI: RSDP 0x00000000000F0410 000024 (v03 DELL  )
Jan 22 ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by florian
close date 2017-12-24 00:10:34.945422

Comments

Can you boot any of the kernels listed in the bootmanager?

florian gravatar imageflorian ( 2016-03-24 10:00:29 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2017-12-23 18:58:56 -0600

paranoid_security gravatar image

Try booting all various kernels installed on your hard disk. If none works, backup to an your /home partition to an external device, format the HDD and reinstall the OS. Furthermore, I would recommend upgrading to Fedora 26 or even better 27. This is due to discontinued support (updates) of all versions prior to 26. If you wish longer support periods for your OS version, purchase Red Hat Enterprise Linux (RHEL). They offer 5 1/2 years updates and assistance for their products. RHEL starts at only $49/year for Desktops.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2016-03-07 11:59:06 -0600

Seen: 344 times

Last updated: Mar 07 '16