Problem with kernel 3.13

Questions about software.
tomix86
Posts: 11
Joined: 22 Mar 2014 09:19

Problem with kernel 3.13

Postby tomix86 » 29 Mar 2014 10:29

After installing the kernel 3.13 the system does not load up. Stops in different places, usually "/dev ... ... disable audio 0 support". Checked on several kernel 3.13.

My computer:
Lenovo Z575
AMD A6-3400M 1.4 GHz,
4096 MB, DDR3-1333,
AMD Radeon HD 6720G2 - 2048 MB,
Realtek ALC272 @ ATI SB800 - High Definition Audio Controller,
Realtek PCIe FE Family Controller GigaBit (10/100/1000MBit),
Ralink RT3090 802.11b/g/n WiFi Adapter (b g n ),
Broadcom 2.1 Bluetooth.

None advice that I found do not work :(
Please help....

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Problem with kernel 3.13

Postby zerozero » 29 Mar 2014 10:48

can you still boot with a previous kernel listed in grub?

how and from where did you installed the 3.13 kernel?
bliss of ignorance

tomix86
Posts: 11
Joined: 22 Mar 2014 09:19

Re: Problem with kernel 3.13

Postby tomix86 » 29 Mar 2014 10:54

From the previous kernel in grub can run.
Checked kernel with Debian Jessy and repo test SolydXK.
Installed with synaptic.

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Problem with kernel 3.13

Postby zerozero » 29 Mar 2014 11:11

ok, share, please the output of

Code: Select all

aptitude search linux-image linux-headers | grep ^i
bliss of ignorance

tomix86
Posts: 11
Joined: 22 Mar 2014 09:19

Re: Problem with kernel 3.13

Postby tomix86 » 29 Mar 2014 11:58

Code: Select all

laptop-linux ~ $ aptitude search linux-image linux-headers | grep ^i
i   linux-headers-3.10-3-amd64      - Header files for Linux 3.10-3-amd64       
i   linux-headers-3.10-3-common     - Common header files for Linux 3.10-3      
i   linux-headers-3.11-2-amd64      - Header files for Linux 3.11-2-amd64       
i A linux-headers-3.11-2-common     - Common header files for Linux 3.11-2      
i A linux-headers-3.13-1-amd64      - Header files for Linux 3.13-1-amd64       
i A linux-headers-3.13-1-common     - Common header files for Linux 3.13-1      
i   linux-headers-amd64             - Header files for Linux amd64 configuration
i   linux-image-3.11-2-amd64        - Linux 3.11 for 64-bit PCs                 
i A linux-image-3.13-1-amd64        - Linux 3.13 for 64-bit PCs                 
i   linux-image-amd64               - Linux for 64-bit PCs (meta-package)    

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Problem with kernel 3.13

Postby zerozero » 30 Mar 2014 07:48

it's not that, the output looks fine to me.

have you made any changes to the sound settings?
[the error that you post is very short and doesn't give us much to work on]
bliss of ignorance

tomix86
Posts: 11
Joined: 22 Mar 2014 09:19

Re: Problem with kernel 3.13

Postby tomix86 » 30 Mar 2014 08:27

nothing was changed, in other kernel works ok. similar error is here https://bugs.debian.org/cgi-bin/bugrepo ... bug=739992

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Problem with kernel 3.13

Postby zerozero » 30 Mar 2014 08:57

good finding! it might be related with that bug;
we have to watch how it goes there and if a solution is found.
bliss of ignorance

User avatar
kobros
Posts: 194
Joined: 28 Nov 2013 14:48
Location: Netherlands

Re: Problem with kernel 3.13

Postby kobros » 30 Mar 2014 10:36

No such problems with this 3.13 kernel in MX-14 :

Code: Select all

$ uname -a
Linux lappy 3.13-0.bpo.1-686-pae #1 SMP Debian 3.13.5-1~bpo70+1 (2014-03-15) i686 GNU/Linux
 
Linux User #312596.
Mepis/Debian/antiX/MX/Win7

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Problem with kernel 3.13

Postby zerozero » 30 Mar 2014 11:02

yep, but kobros that is a stable backported kernel (bpo): different beast entirely ;)
bliss of ignorance

User avatar
kobros
Posts: 194
Joined: 28 Nov 2013 14:48
Location: Netherlands

Re: Problem with kernel 3.13

Postby kobros » 30 Mar 2014 19:54

zerozero wrote:yep, but kobros that is a stable backported kernel (bpo): different beast entirely ;)
I am not convinced. This is a direct quotation from kernel.org :
Mainline
Mainline tree is maintained by Linus Torvalds. It's the tree where all new features are introduced and where all the exciting new development happens. New mainline kernels are released every 2-3 months.
Stable
After each mainline kernel is released, it is considered "stable." Any bug fixes for a stable kernel are backported from the mainline tree and applied by a designated stable kernel maintainer. There are usually only a few bugfix kernel releases until next mainline kernel becomes available -- unless it is designated a "longterm maintenance kernel." Stable kernel updates are released on as-needed basis, usually 2-3 a month.
A backported kernel is -basically- a mainline kernel plus bugfixes backported from the current mainline kernel applied.

My point being that the backported 3.13 kernel used in MX-14 (which is newer than the one used in SolydXK) already has some bugfixes applied and (at least on my laptop with integrated graphics) does not suffer from the problem described. That problem may have been fixed in it....
Linux User #312596.
Mepis/Debian/antiX/MX/Win7

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Problem with kernel 3.13

Postby zerozero » 30 Mar 2014 20:17

but what kernel.org considers <stable> is different from what debian considers <stable>; and quoting Linus about <stable> kernels is missing the point about debian stable, debian stable kernels, debian backports and debian kernel backports.

===
on another note:
a reading on the official debian backports homepage wouldn't hurt anyone
Backports are packages taken from the next Debian release (called "testing"), adjusted and recompiled for usage on Debian stable. Because the package is also present in the next Debian release, you can easily upgrade your stable+backports system once the next Debian release comes out. (In a few cases, usually for security updates, backports are also created from the Debian unstable distribution.)
and also
Backports cannot be tested as extensively as Debian stable, and backports are provided on an as-is basis, with risk of incompatibilities with other components in Debian stable. Use with care!
you can't have the cake and eat it :) Stable is different from Stable+Backports (specially if they are not tidily controlled)
bliss of ignorance

User avatar
kobros
Posts: 194
Joined: 28 Nov 2013 14:48
Location: Netherlands

Re: Problem with kernel 3.13

Postby kobros » 30 Mar 2014 20:57

you can't have the cake and eat it :) Stable is different from Stable+Backports (specially if they are not tidily controlled)
I did not state or imply that they're the same. I used the [quoted] kernel.org distinction ("Mainline=development, Stable=released version"), not the Debian branch release distinctions.
The MX-14 kernel (the 3.13 5 one; there's also the default 3.12.9 kernel) is properly controlled by the Debian Kernel Team.
Backported packages for Mepis and/or MX-14 are built and released after proper testing and in a strictly controlled way.

My point still stands: if there's a problem with kernel 3.13.1 which does not appear in 3.13.5 (wheezy backport, released March 15, 2014), then there's a fair possibility that it's been fixed with one or more bug fixes included in that 3.13.5~bpo kernel.
Linux User #312596.
Mepis/Debian/antiX/MX/Win7

User avatar
kobros
Posts: 194
Joined: 28 Nov 2013 14:48
Location: Netherlands

Re: Problem with kernel 3.13

Postby kobros » 30 Mar 2014 22:19

There may be a solution/fix available for the 3.13 kernel problem with discrete video cards for Jessie (as of today)

http://forum.mepiscommunity.org/viewtop ... 97&t=35897
Linux User #312596.
Mepis/Debian/antiX/MX/Win7

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Problem with kernel 3.13

Postby zerozero » 30 Mar 2014 23:14

tomix
have you used

Code: Select all

radeon.dpm=1
as boot option [or configured in /etc/default/grub?]
this bug report https://bugs.debian.org/cgi-bin/bugrepo ... bug=741619 seems to indicate problems with that
bliss of ignorance

tomix86
Posts: 11
Joined: 22 Mar 2014 09:19

Re: Problem with kernel 3.13

Postby tomix86 » 31 Mar 2014 15:47

Code: Select all

radeon.dpm=1
At the 3.11 kernel is enabled, it works ok.
I ran Ubuntu 14.04 LTS LiveCD (without installation) contains the kernel 3.13, and the problem is the same - freezes on startup.
I think that the fault of the kernel...

User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Problem with kernel 3.13

Postby zerozero » 31 Mar 2014 15:54

booting from 3.11 can you post the output of

Code: Select all

cat /etc/default/grub
bliss of ignorance

tomix86
Posts: 11
Joined: 22 Mar 2014 09:19

Re: Problem with kernel 3.13

Postby tomix86 » 31 Mar 2014 16:11

Code: Select all

laptop-linux ~ $ cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT="0"
#GRUB_HIDDEN_TIMEOUT="0"
GRUB_HIDDEN_TIMEOUT_QUIET="true"
GRUB_TIMEOUT="3"
GRUB_DISTRIBUTOR="`cat /etc/solydxk/info | grep GRUB_TITLE | cut -d= -f2 2> /dev/null || echo SolydXK`"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.dpm=1"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXPAYLOAD_LINUX="800x600"
GRUB_GFXMODE="640x480"

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"


User avatar
zerozero
Posts: 5373
Joined: 10 Feb 2013 23:37
Location: West Midlands, England
Contact:

Re: Problem with kernel 3.13

Postby zerozero » 31 Mar 2014 16:27

i think i start to understand where the problem is:
according to this
http://kernelnewbies.org/Linux_3.13#hea ... f0e16898df
and this
https://wiki.archlinux.org/index.php/AT ... management
DPM is enabled by default in 3.13 so you (probably) are seeing an incompatibility with the settings that you have added to the kernel boot options.

==
as a quick test remove

Code: Select all

radeon.dpm=1
from

Code: Select all

/etc/default/grub
do

Code: Select all

sudo update-grub
and try to boot 3.13 again
bliss of ignorance

tomix86
Posts: 11
Joined: 22 Mar 2014 09:19

Re: Problem with kernel 3.13

Postby tomix86 » 31 Mar 2014 17:05

I checked already and did not work, stops mostly (sometimes later)

Code: Select all

[drm] disable audio 0 support
also checked

Code: Select all

radeon.sound=0
and

Code: Select all

radeon.sound=1

I did it in Grub customizer but it probably does not matter that it does not in the terminal

Besides Ubuntu running directly from the live cd is just as

[sorry for my english :)]


Return to “Software”

Who is online

Users browsing this forum: Bing [Bot] and 7 guests