[SOLVED] No boot after upgrade kernel-lts 4.4.12-1

Smallville · 2016-04-24 10:48:45

Hi all after i upgarde my kernel from linux-lts-4.1.21-1 to linux-lts-4.4.8-1 , my system stop booting.

I have this error: drm:radeon_init *error* no UMS support in radeon module!

I have to downgrade to linux-lts-4.1.21-1, and all works perfect.

My graphic card: lspci | grep VGA
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D]

im using vdpau drivers and mesa drivers.

Anyone can help ?
Thx

Last edited by Smallville (2016-06-28 13:35:44)

Lone_Wolf · 2016-04-24 15:39:20

sounds like something goes wrong when kernel 4.4.8 tries to use kernel modesetting.

Please get us the journal from the failed boot, "journalctl -b -n" ( n is a positive number, you'll have to try several values of n to get the correct log.)

Last edited by Lone_Wolf (2016-04-24 15:39:42)

Smallville · 2016-04-25 13:24:04

Lone_Wolf wrote:

sounds like something goes wrong when kernel 4.4.8 tries to use kernel modesetting.
Please get us the journal from the failed boot, "journalctl -b -n" ( n is a positive number, you'll have to try several values of n to get the correct log.)

Maybe i post wrong, i only have that error when i use nomodeset for boot to console for downgrade to linux-lts-4.1.21-1.
If i dont use nomodeset i have looping boot i cant see anything only black screen and a reboot after that.

Any ideas ?

Thx

Last edited by Smallville (2016-04-25 13:24:34)

JohnBobSmith · 2016-04-25 13:27:54

As much as I would like for you to have a newer working kernel, consider this: If you have a working system, with all hardware in check and great performance, you may NOT want (or need) to upgrade. It might save you some headaches.

Lone_Wolf · 2016-04-25 14:13:50

Maybe i post wrong, i only have that error when i use nomodeset for boot to console for downgrade to linux-lts-4.1.21-1.
If i dont use nomodeset i have looping boot i cant see anything only black screen and a reboot after that.

with amd card +nomodeset that error is normal .

for clarity :

when you boot with 4.4 lts kernel (without changing kernel parameters) , you get black screen AND system reboots automagickally ?

Are you booting to X/ Display manager or console ?

Smallville · 2016-04-26 20:29:32

Lone_Wolf wrote:

Maybe i post wrong, i only have that error when i use nomodeset for boot to console for downgrade to linux-lts-4.1.21-1.
If i dont use nomodeset i have looping boot i cant see anything only black screen and a reboot after that.
with amd card +nomodeset that error is normal .
for clarity :
when you boot with 4.4 lts kernel (without changing kernel parameters) , you get black screen AND system reboots automagickally ?

Yes, thats right i only see the black screen, and reboot all time.

Are you booting to X/ Display manager or console ?

Im booting to LightDM

Thx

Lone_Wolf · 2016-04-27 11:38:38

ok, try booting 4.4.x lts with systemd.unit=multi-user.target as kernel parameter .

If it also does reboot, try ystemd.unit=rescue.target

Smallville · 2016-05-10 17:05:59

Lone_Wolf wrote:

ok, try booting 4.4.x lts with systemd.unit=multi-user.target as kernel parameter .
If it also does reboot, try ystemd.unit=rescue.target

How i use that as kernel parameter ?

Thx

clfarron4 · 2016-05-10 19:42:42

Smallville wrote:

Lone_Wolf wrote:
ok, try booting 4.4.x lts with systemd.unit=multi-user.target as kernel parameter .
If it also does reboot, try ystemd.unit=rescue.target
How i use that as kernel parameter ?
Thx

If you are using a bootloader like GRUB, you should be able to "temporarily edit" the entry before you boot in and add that as a kernel parameter.

Smallville · 2016-05-13 22:00:37

Lone_Wolf wrote:

ok, try booting 4.4.x lts with systemd.unit=multi-user.target as kernel parameter .
If it also does reboot, try ystemd.unit=rescue.target

I have try that and is the same boot looping.
Its because my Amd apu ati craphic card ?

Thx

Lone_Wolf · 2016-05-14 14:54:07

Smallville,

i had a typo in that post, i hope you noticed it.

If you didn't, try with this : systemd.unit=rescue.target

If that also keeps rebooting, something very weird is going on.
If it was just the black screen , problems between kernel and graphic would be likely.

Smallville · 2016-05-22 03:07:45

Lone_Wolf wrote:

Smallville,
i had a typo in that post, i hope you noticed it.
If you didn't, try with this : systemd.unit=rescue.target
If that also keeps rebooting, something very weird is going on.
If it was just the black screen , problems between kernel and graphic would be likely.

I have try that commands on the line Boot, but dont have any new.
Still have the loop booting.

I have the kernel parameters screenshot Here ,if you can have a look to see if im writing in the right place i apreceate.

Thx for the attencion

Last edited by Smallville (2016-05-22 03:08:56)

lastchancetosee · 2016-05-22 07:56:20

That screenshot is of your normal parameters before you edited them, I think?
The boot line where you put kernel parameters is the one starting with 'linux':

linux /boot/vmlinuz-linux-lts root=...  rw systemd.unit=...

The first part is the path to the kernel you're booting, the rest is passed to the kernel as parameters.

Smallville · 2016-05-22 21:53:06

lastchancetosee wrote:

That screenshot is of your normal parameters before you edited them, I think?
The boot line where you put kernel parameters is the one starting with 'linux':
linux /boot/vmlinuz-linux-lts root=...  rw systemd.unit=...
The first part is the path to the kernel you're booting, the rest is passed to the kernel as parameters.

Thx for your answer. I was doing the kernel parameter right, and the computer keep on loop booting, no image no error just a black screen.

What could be ?

Thx

Last edited by Smallville (2016-05-22 21:54:11)

Lone_Wolf · 2016-05-23 11:26:56

This error is getting very weird if even rescue target reboots, are you sure the UUID you use for root is the correct one ?

please remove quiet from the "linux /boot/" line , then try booting again and tell us what the last thing you see on screen is .

Smallville · 2016-05-26 01:48:27

Lone_Wolf wrote:

This error is getting very weird if even rescue target reboots, are you sure the UUID you use for root is the correct one ?
please remove quiet from the "linux /boot/" line , then try booting again and tell us what the last thing you see on screen is .

I have remove the quiet from linux boot line and try the systemd.unit and is the same boot to a black screen no errors nothing only the boot looping the only thing i can write in the boot linux is the nomodeset command to enter in console to downgrade the linux-lts.
The UUID is the same when i run the linu inux-lts-4.1.21-1 or the inux-lts-4.4.8.1

Thx for your attention.

Lone_Wolf · 2016-05-28 16:33:24

Ok, since we haven't been able to get logs from failed boot, it's time to look at things from another angle.

The AMD richland appears to be an APU, which would mean you run an AMD processor +integrated videocard .

If that educated guess is correct, try this :

senden9 wrote:

For the other people there come here and read this solution: You can append this line in your kernel command line at your boot loader to get into your system
modprobe.blacklist=sp5100_tco

copied from https://bbs.archlinux.org/viewtopic.php?id=211365

Last edited by Lone_Wolf (2016-05-28 16:34:00)

Smallville · 2016-06-05 20:59:52

Lone_Wolf wrote:

Ok, since we haven't been able to get logs from failed boot, it's time to look at things from another angle.
The AMD richland appears to be an APU, which would mean you run an AMD processor +integrated videocard .
If that educated guess is correct, try this :
senden9 wrote:
For the other people there come here and read this solution: You can append this line in your kernel command line at your boot loader to get into your system
modprobe.blacklist=sp5100_tco
copied from https://bbs.archlinux.org/viewtopic.php?id=211365

Thx for your help.
Sorry for my late answer but i was trying differente thngs.

The modprobe_blacklist dont work ...

I pick a new hard drive and make a new installation and all working good with the last lts kernel ... My arch installation have maybe 2 years old... maybe a need to do a fresh install but i have so many things configurate.

What you think ?

thx

Lone_Wolf · 2016-06-06 14:37:00

For clarity :

A fresh install on a fresh harddrive on the problem system works fine with last linux-lts (4.4.11) package ?

If that's correct, 2 possible causes come to mind :
- a kernel bug in some linux-lts 4.4.x versions that has been corrected in later releases
- something went wrong during the upgrade,possibly when creating the initramfs .

Smallville · 2016-06-08 01:48:15

Lone_Wolf wrote:

For clarity :
A fresh install on a fresh harddrive on the problem system works fine with last linux-lts (4.4.11) package ?
If that's correct, 2 possible causes come to mind :
- a kernel bug in some linux-lts 4.4.x versions that has been corrected in later releases
- something went wrong during the upgrade,possibly when creating the initramfs .

Thx for your help.

With a fresh install on a fresh hdd i have the same problem, only boot once with image and no errrors.
I get the same bug with fresh install on my actual system ( no image after boot with kernel after 4.1.21-1 ) . The only kernel that works all perfect is linux-lts-4.1.21-1
I have try all i see on wiki even the iso combo like architect (this i can´t passe the boot i need to edit the kernel to boot with nomodeset)
The problem is my radeon card on kernel after 4.1.21-1 ..... what have changed ? Its frustrating with radeon cards ..... with nvidia all working great ( my laptop have nvidia and i have the last lts kernel all working great )

What i could try more ?

Thx

Last edited by Smallville (2016-06-08 01:49:58)

Lone_Wolf · 2016-06-11 18:30:47

try adding radeon.dpm=0 as boot parameter .

Can you also check with recent installer disks from some other distros , like ubuntu , mint , fedora ?

Smallville · 2016-06-14 21:47:59

Lone_Wolf wrote:

try adding radeon.dpm=0 as boot parameter .
Can you also check with recent installer disks from some other distros , like ubuntu , mint , fedora ?

First of all thx for all your help.

I have try other distros, linux mint boot without any problems, ubuntu need to setup the nomodeset first or dont boot to install and fedora i dont try.

On arch linux with boot parameter radeon.dpm=0 i can finally boot my arch linux with the last lts kernel (4.4.13-1-lts)
And now what is the problem ? How i fix this ? I need to type adeon.dpm=0 every time i boot ?

Thx

Lone_Wolf · 2016-06-16 22:56:43

AMD cards supports several kinds of powersaving, dpm is the best wrt power use and performance but doesn't work on all cards.

I expect dpm was enabled for your type of card in kernels post 4.1-lts .
you will need to disable radeon.dpm for every boot,but that can be done through your bootmanager (check wiki for the one you use).

Check wiki amd page for details about other powersaving methods .

Smallville · 2016-06-28 13:35:11

Lone_Wolf wrote:

AMD cards supports several kinds of powersaving, dpm is the best wrt power use and performance but doesn't work on all cards.
I expect dpm was enabled for your type of card in kernels post 4.1-lts .
you will need to disable radeon.dpm for every boot,but that can be done through your bootmanager (check wiki for the one you use).
Check wiki amd page for details about other powersaving methods .

Yap you are right they have enable the dpm on card after kernel 4.1 , i have edited my grub and all working good, but i dont have the dpm now but for now all working good.
Once again thx for all your help

Best regards

Arch Linux

#1 2016-04-24 10:48:45

[SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#2 2016-04-24 15:39:20

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#3 2016-04-25 13:24:04

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#4 2016-04-25 13:27:54

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#5 2016-04-25 14:13:50

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#6 2016-04-26 20:29:32

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#7 2016-04-27 11:38:38

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#8 2016-05-10 17:05:59

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#9 2016-05-10 19:42:42

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#10 2016-05-13 22:00:37

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#11 2016-05-14 14:54:07

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#12 2016-05-22 03:07:45

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#13 2016-05-22 07:56:20

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#14 2016-05-22 21:53:06

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#15 2016-05-23 11:26:56

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#16 2016-05-26 01:48:27

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#17 2016-05-28 16:33:24

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#18 2016-06-05 20:59:52

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#19 2016-06-06 14:37:00

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#20 2016-06-08 01:48:15

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#21 2016-06-11 18:30:47

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#22 2016-06-14 21:47:59

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#23 2016-06-16 22:56:43

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

#24 2016-06-28 13:35:11

Re: [SOLVED] No boot after upgrade kernel-lts 4.4.12-1

Board footer