I use Debian Stretch (testing). After upgrading to kernel 4.4 the system doesn't see my main soundcard at all -- so, no sound. And now I also get this message every boot:
Code: Select allmodprobe: module microcode not found in modules.dep
Can I use the config for my current kernel (the jessie 3.16 one), and use it to build a more recent kernel (3.18)? Do I just copy across the config and try and build with it, or is there some tool that will bring across the existing config but also set up reasonable defaults for any new options in the newer kernel, and any other migrations that might need to be applied?
View 4 Replies View RelatedI've just upgraded my kernel to 2.6.32 and I cant use sound anymore!!! My card was detected ,here is the output of lspci |grep Audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
also frimware is installed ,gstreamer as well the sound is not on mute and it was working on the previous kernel .
I have a hand-built kernel in Lenny. It's much smaller and faster than the stock kernel and doesn't need an initrd, but I am not sure how to upgrade it in a way that will be compatible with the new udev package. The recommended procedure is to upgrade the kernel and udev together and then reboot before doing the rest of the upgrade, but obviously I can't do that.
There seem to be two possible procedures I could follow:
1) Upgrade kernel sources and rebuild and install the kernel, then reboot and upgrade udev. But then the new kernel would be booting with the old udev and I don't know if that would work.
2) Upgrade, rebuild and install the kernel, then upgrade udev without rebooting, ignoring the warning messages. Finally reboot into the new kernel.
since I'm new to the the forum and this is my first post I'd like to discuss a quite weird issue. Specifically, after upgrading my Debian system to Squeeze a few days ago, sound is completely lost. This means that I cannot hear any sound from anywhere (mp3, streming videos or anything else) except the system bell . I've done a research on the Internet, looking in other forums and discussions but still, nothing works for me. To begin with, I'm running Squeeze in an HP laptop with HDA Intel soundcard and chipset ALC268. When I'm running aplay -l I get this message:
Darkstar:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
[code]...
I recently installed debian squeeze 32bit on a second partition of my amd athlon 64 X2 dual core machine.Currently it is using linux-image-2.6.32-trunk-686 kernel.But linux-image-2.6.32-trunk-amd64 is available.on the repository.Is it a 64bit kernel or 32bit kernel optimized for amd64 architecture?
View 12 Replies View RelatedI am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
View 1 Replies View RelatedI Upgraded the system to 2.6.26-2-i686 doesn't boot:
error message on Grub is:
I upgraded my system from Wheezy to Jessie and now the audio is tinny. It sounds like a lot of the bass is being chopped off. This happens in YouTube's HTML5 video player, VLC and whatever player it is that Thunar launches for avi files.I'm using Xfce as my desktop, if that matters.I looked around for an equalizer app for pulseaudio but was surprised to find that the there isn't one, or at least not one which is still maintained.
View 0 Replies View RelatedI had a broken URL in my /etc/apt/sources.list file, apparently because the debian-multimedia.org site had some kind of server issue and they had to rebuild the site from the ground up. They must have changed their directory structure, because I began getting 404 Errors when upgrading packages. I eventually fixed the URL last week after it had been broken for three months, then I upgraded and rebooted. After that, sound stopped working, even system sounds. My speakers work, because I plugged them into another machine and they worked. I eventually discovered that the master volume was set to "mute", and so was the master volume in the alsamixer. However, even after changing it to 100% for both, sound still doesn't work. I even made sure to issue a "alsactl -store" command toeep the settings there after a reboot. I removed and reinstalled all the alsa and pulse audio packages, made sure that the emu10k1 driver was installed for my Soundblaster Audigy card, and made sure everything was unmuted. I have also tried a million other things that I've found on Google, but nothing seems to work. Any help would be greatly appreciated.
View 5 Replies View RelatedI have a problem with my custom kernel when I want to create the Nvidia kernel module.After this finished I installed the image and headers and created the Nvidia kernel module. Everything worked fine.However, if I remove the linux-source from my home directory then I can't create the kernel module.Even though I have the headers for the kernel installed.
View 2 Replies View RelatedI'm just completing an upgrade from wheezy to jessie and get the following error
Code: Select allProcessing triggers for initramfs-tools (0.120) ...
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
E: intel-microcode: unsupported kernel version!
With a message like this I'm wondering if it's safe to reboot as well as how to resolve.
Is this somehow related to the change to only update the microcode on boot as reported earlier in the upgrade?
Code: Select allintel-microcode: microcode will be updated at next boot
Added the following line to sources.list:
deb [URL] squeeze main non-free
After that I did an update and upgrade.
The following packages were kept back : ffmpeg libavcodec52 libavdevice52 libavformat52 libcairo2 libpostproc51 libswscale0 mplayer ( libcairo2 is on hold ).
To overcome this I did: apt-get install mplayer
The following extra packages will be installed:
liba52-0.7.4 libartsc0 libbs2b0 libdirac-decoder0 libfaac0 libggi2 libggiwmh0 libgii1
libmp3lame0 libopencore-amrnb0 libopencore-amrwb0 libvdpau1 libx264-104 libxvidcore4
It ends like: Unpacking replacement mplayer ...
dpkg: error processing /var/cache/apt/archives/mplayer_2%3a1.0~rc3++svn20100804-0.0_amd64.deb (--unpack):
trying to overwrite '/usr/share/pixmaps/mplayer.xpm', which is also in package mplayer-gui 2:1.0~rc3++final.dfsg1-1
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Processing triggers for man-db ...
Processing triggers for menu ...
Errors were encountered while processing:
/var/cache/apt/archives/mplayer_2%3a1.0~rc3++svn20100804-0.0_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Next thing I tried : apt-get dist-upgrade:
The following packages will be REMOVED:
libavfilter0
The following NEW packages will be installed:
libavcore0 libavfilter1 libavutil50 libva1
The following packages have been kept back:
libcairo2
The following packages will be upgraded:
ffmpeg libavcodec52 libavdevice52 libavformat52 libpostproc51 libswscale0 mplayer
Preparing to replace mplayer 2:1.0~rc3++final.dfsg1-1 (using .../mplayer_2%3a1.0~rc3++svn20100804-0.0_amd64.deb) ...
Unpacking replacement mplayer ...
dpkg: error processing /var/cache/apt/archives/mplayer_2%3a1.0~rc3++svn20100804-0.0_amd64.deb (--unpack):
trying to overwrite '/usr/share/pixmaps/mplayer.xpm', which is also in package mplayer-gui 2:1.0~rc3++final.dfsg1-1
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Processing triggers for menu ...
warning, in file '/var/lib/dpkg/updates/0006' near line 5 package 'libavcore0':
missing description
warning, in file '/var/lib/dpkg/updates/0006' near line 5 package 'libavcore0':
missing maintainer
warning, in file '/var/lib/dpkg/updates/0015' near line 5 package 'libavfilter1':
missing description
warning, in file '/var/lib/dpkg/updates/0015' near line 5 package 'libavfilter1':
missing maintainer
Errors were encountered while processing:
/var/cache/apt/archives/mplayer_2%3a1.0~rc3++svn20100804-0.0_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
I have a set of vm's with stable, testing, and sid to keep track of how things are going. When I did an apt-get dist-upgrade with squeeze last week, things seemed to OK (350 package updates) until the end. It didn't seem to like and / or was confused by a kernel dependency.
I am not too concerned yet. Because these are in vm's, I do a snapshot before any significant change. I can futz around with impunity because I have that backup.
I re-booted, and tried the apt-get dist-upgrade again with same results. I think I also tried apt-get -f install.
So I reverted to the snapshot, and will simply try again in the future. I recall that with lenny as testing, the font-desktop was really screwed up for about a period of 6 weeks.
However, just in case someone else runs into this:
1) a re-boot worked, but the failure of apt-get made me nervous enough to revert.
2) waiting for corrections has seemed to work in the past (with a single exception with a 4-disk SCSI software RAID10 update that failed to re-boot lenny successfully after what seemed to be a minor update -- that was on a real system, not a vm. I haven't gotten back to look at that.)
I recently updated my Debian jessie system (for the first time in a few months). It broke my video driver (fortunately a dpkg-reconfigure fixed that) and my wireless driver (forget how I fixed that...), and my sound. ALSA still thinks I have an output device, I've set volumes all the way up in alsamixer.
In vlc and firefox, I can't hear anything using the default audio out (which I think is pulseaudio), nor can I hear anything if I ask them to use ALSA output directly. I've tried rebooting, killing/manually starting pulseaudio, etc to no avail.
I think it was either the kernel upgrade (went from 3.10 to 3.13) or a configuration option in some sound subsystem that broke. To be clear, sound was working perfectly before the upgrade. My machine is an Ivy Bridge-era Zenbook.
I'm in need of a bit of assistance from you Debian users. I have two servers that I thought were identical installations, both running Debian Lenny. Tonight I started the upgrade to Squeeze on both servers and one of them went smooth. The other one started out good but fails on the postconfiguration of openssh-server. I'm getting the following message:
Code:
Setting up openssh-server (1:5.5p1-4) ...
Auto configuration failed
2524:error:0E079065:configuration file routines:DEF_LOAD_BIO:missing equal sign:conf_def.c:366:line 67
invoke-rc.d: initscript ssh, action "restart" failed.
[Code].....
It looks like there's an error in one of the files in openssh-server that prohibits it from installing correctly. However on the other server it all went well.
is it save to install linux kernel 2.6.35.2 on Debian Lenny 5.0.5 or stick with automatic updates...
View 14 Replies View RelatedOn Lenny, due to some compatibility issues: kernels before 2.6.26 don't recognize part of my vaio laptop's hardware, while the last drivers of my videocard (version: 260, card: nvidia gt 230m) suffer some incompatibility problem (this is one of the most problematic computers I ever had), so I have to use version 256, which doesn't work with kernels after (perhaps) 2.6.32. So, I suppose I have to check each kernel between that two versions and hope that one of them will be ok. I searched quite deeply over the net but didn't find anything related to debian, except for generic kernels [URL], but as someone told me that it's better if I only install stuff from the stable repository or backports. What can I do? Is there any backports archive or something like that? Otherwise, what should I do?
View 5 Replies View RelatedI'm fairly new to linux Red Hat. We are running Rhel 3 on our VM's. We ran into a issue, (Bug 121801 - athlon-smp kernel does not support >4GB of RAM. what the stepos are to upgrade the existing kernel to the new i686? .
View 3 Replies View RelatedI have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code:
# Linux bootable partition config begins
image = /other/spare4/boot/vmlinuz
[code]....
I recently bought an AMD R7 360 videocard and I'd like to use the free Radeon driver.
Problem is, PCI-ID 0x665f is not present in Jessie's 3.16 kernel sources. The hardware however is supported, it's just not recognized. So I'll have to get the Debain sources and patch include/drm/drm_pciids.h
From the 4.1rc1 kernel I know what to patch and where.
Debian page that explains how to use the Debian build system for recompiling the current kernel from Debian packages?
Upgraded Wheezy to Jessie, by changing my apt sources to point at stable instead of wheezy. Ran upgrade, and dist-upgrade, all fine etc.
Then tried to update the kernel by installing linux-image-amd64 package .. seemed to work fine, but after a reboot my kernel version still says 3.10.23
What have I missed?
Code: Select allroot@hostname:~# apt-cache search linux-image
linux-headers-3.16.0-4-amd64 - Header files for Linux 3.16.0-4-amd64
linux-image-3.16.0-4-amd64 - Linux 3.16 for 64-bit PCs
linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
[Code] .....
I have a MyBookLive where i installed a Debian 2.6 kernel. The system is running fine so far. Because of an error message when apt-get upgrade (udev) i tried to upgrade to 3.16. Here's what i did:
- apt-get install linux-image-xx
- apt-get install linux-source-xx
- extract the source
- copied the old .config from running 2.6 kernel over to the 3.16 directory
- make oldconfig
- make uImage
- make modules
- make modules_install
- copied uImage to /boot
No error messages because its a headless device - its just not booting up.
Since setting up a new rigg featuring an Asus Z170-A the internal soundcard does not play any sound. The integrated soundcard is a Realtek ALC892, as shown by aplay -l.
List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 1/1
[code]...
Additionally I find that on my laptop (where the sound works) "default Playback/recording through the PulseAudio sound server" when doing aplay -L. However no such thing mentioned on my stationary (where the issue is). Might there be some issues with the PuseAudio server?
Also the HDMI from my NVIDIA gfx card is identified. However removing the gfx card and using the onboard gfx does not change a thing.
I've also checked alsamixer and made sure that the soundcard is unmuted. I've looked around on google and among other tested the solution presented in URL...
I was wondering if anyone can assist me. I am looking to build a server with Debian as the host. When I installed Debian (Squeeze) the default kernel was "2.6.32-3-trunk-amd64". When I tried to install 'Virtualbox' application, I got a failure because I didn't have the 'kernel-headers' installed on my machine. I noticed there are no specific header package the 'trunk' kernel I was using. I have a few questions so I guess I should begin:
Is it safe to remove the 'trunk' kernel and boot my system on just the regular 2.6.32-3-amd64 kernel? Is this OK or not recommended? Please explain whatever is the correct answer. This is my 1st time using a 'Trunk' kernel so I don't know the in's and out's of it.
If I am using Debian 'Testing' for virtualization via 'Vbox', is there a specific kernel I "should" be using?
I have maked a new kernel (version is 2.6.24.7) in debian system which kernel is 2.6.26, and then when i start the new kernel which is 2.6.24.7, it tells me that:
View 1 Replies View RelatedMy girlfriend got a 'new' (second hand) laptop, a HP Compaq 6715s. When I tried to install Debian on it, the install went immensely slow - glacial, even. It was a very minimal install but it tooks hours to get to nowhere.
I found out online that this was because of a problem between the current kernel and the hard drive (or HD bus, something hardware-y to do with the disk) which meant file operations were extremely slow. I thought "easy, patiently install Debian and then install newer kernel". Except that after six hours, the install wasn't even halfway.
So I install Arch Linux with the 2.6.35 kernel: no problems with the drive speed at all. After a lot of researching (I only played around with Arch once, more than a year ago) I got the system into a usable state. But now wlan0 has suddenly disappeared, together with some other problems - and a usable laptop wasn't exactly what I had in mind, it was supposed to be awesome (or at least good). Which, with Debian, it would be
So... is it possible to make a Debian installation use a later version of a kernel? I'd want to install Debian with the 2.6.35 kernel, not install Debian and then afterwards update the kernel (because I don't have 24 hours to install an OS, if it'll ever even install).
I've found some stuff online but it might well have been written in the Cyrillic alphabet. All I understand, I think, is that in theory it's possible.
I installed Debian Squeeze from a net install to a raid 1 array. I have been having a lot of troubles related to being able to write to one or more of the mounted drives - even touch gives me errors.
The most interesting line from dmesg is:
Here is the full output from dmesg:
I found a thread that indicated that this bug was fixed in the next kernel version: 2.6.32-6. I am willing to upgrade the kernel to get rid of my problems. Is a squeeze kernel at 2.6.32-6 or higher available? If so, where? I have not compiled my own kernel, and am not very interested in getting into that.
Trying to compile the 2.6.36.2 kernel. Its not the first kernel I've compiled, but I've run into a problem I've not come accross before.
While compiling I get this error.
[Code]....
Looks like the headers sys/eventfd.h and linux/virtio_rng.h haven't been selected in my .config file. I just copied my old config from the last kernel I built. This was a while ago (2.6.30), but I thought I'd give it a go anyway.
what config option they are under or what I can do to get rid of this error?
This is Wheezy x86_64. I tried two different ways to install kernel 2.6.38 on my machine and both have failed. First thing I did was to follow this guide [URL]... el-26.html) and try to compile the latest stable from kernel.org. I don't know why, but it turns into kernel panic when I try to run it. Second thing I did was to install the liquorix 2.6.38, and that also fails, seeming to boot but hanging a second short from the login. I don't know what I'm doing wrong. Is there a special way to install kernels in Debian? This is the first time I tried compiling a kernel, so it's quite likely that the problem is sitting 6 inches from the computer screen. Also, how would I remove those kernels since they're obviously not working? I know I could remove them from the grub menu but I'm not sure how to completely delete them.
View 12 Replies View Related