Just installed the latest kernel upgrades, rebooted, fired up KDE and got this message: "KDE detected that one or more internal sound devices were removed. Do you want KDE to permanently forget about these devices? The list of the devices KDE thinks can be removed: Capture: HDA Intel (AD198x Analog) Output: HDA Intel (AD198x Analog) Output: HDA Intel (AD198x Digital)"
It then asked, "yes, cancel, manage devices." When I clicked on "manage" it showed Esound as the only device, but it didn't work. So, was something was left out when the packages were compiled?
libgmp If you found slackpkg failed for this upgrade because of libgmp not found you will need to grab the gmp package and install manually. This way ought to work:
Quote: The open-source Linux operating system contains a serious security flaw that can be exploited to gain superuser rights on a target system. The vulnerability, in the Linux implementation of the Reliable Datagram Sockets (RDS) protocol, affects unpatched versions of the Linux kernel, starting from 2.6.30, where the RDS protocol was first included.
According to VSR Security, the research outfit that discovered the security hole, Linux installations are only vulnerable if the CONFIG_RDS kernel configuration option is set, and if there are no restrictions on unprivileged users loading packet family modules, as is the case on most stock distributions.
I have three system on Ubuntu 9.10. Two of them are at kernel level 2.6.31.20 and one seems to be stuck at 2.6.31.17. All three have about the same software sources. The only difference I can see is that the .17 system is on Grub2 and the other are Grub1 systems. I have tried updating via Synaptic but nothing can get the one system to get a kernal upgrade.
The .17 system seems to go through updates of packages but no kernel updates.
I am using Meerkat w/ the 2.6.35.24 kernel. I am extremely satisfied w/ the direction of Ubuntu and Canonical and am amazed at the focus and dedication of all involved, including the contributors and moderators here.
But I have a question regarding continually upgrading the distribution kernels while awaiting the next iteration (11.04). Is it advisable to upgrade every kernel when my system seems to run well without them? For instance, each kernel upgrade necessitates that I reinstall the NVIDIA driver, among a couple other minor problems. This is not that big a deal, but I would like to avoid it--it's just an irritation when I reboot to a black screen. But another irritation is continually ignoring the update notices.
this is a new problem with issues that started when I upgraded to 10.10. Originally, GRUB wouldn't load after that upgrade, but that was fixed here. Once GRUB was working properly, there was a problem with the 2.6.35-28 generic kernel. When I tried to boot through it, I would only get an ubuntu command line.
Luckily the older 2.6.32-22 generic kernel worked just fine and I could log in and load my ubuntu desktop with no issues. I decided to upgrade to 11.04 to see if that would correct whatever was going on. The installation was completed without any apparent issues, GRUB works, XP Pro works, and the older 2.6.32-22 generic kernel allows me to boot into 11.04.
Unfortunately, another new kernel, 2.6.38-8 generic, is not working properly. I snaped some pictures of what happens when I try to use this kernel:
[URL]
The first is GRUB/ The selection The second is the loading graphic The third is a command line where it freezes (note: this is not the same command line screen/environment that I was referring to with the 10.10 new kernel)
I have some pending upgrades, one of which includes kernel 2.6.32-22 but whenever the upgrade gets to running the update-grub command, it gets stuck on "Found memtest86+..." Here's the actual output...
[Code].....
It's been hanging like this for hours today, preventing me from getting any of the pending upgrades. I've cancelled it several times, deleted the dpkg lock files and tried it again only to have it hang all over again.
This morning I ran the automatic upgrade provided on the repositories, updating my kernel from 2.6.38-8 to 2.6.38-10.Unfortunately, upon reboot I discovered that a series of patches I'd applied in order to get my wireless card on my desktop working had been undone (see I had to run a modified version of the instruction set in order to get my wireless back on.My question: is there a way to trigger this every time the kernel upgrades? I'd hate to have to run this cumbersome set of commands manually every time.
I have just suscribed into this forum. I have a problem: my notebook (NOTEBOOK SATELLITE L300-SP5917A - INTEL CORE 2 DUO T6400 (2.00 GHZ - 2 MB L2 - 800MHZ FSB) - 15.4 WIDESCREEN TRUBRITE TFT LCD - 400 GB SATA 2 .5 5400 RPM - 3GB PC2-6400 DDR2) doesn't boot ubuntu after the last security upgrade. I have wubi installed.I have Windows Vista and Ubuntu in the boot menu. I select "Ubuntu" and that leads me to the GRUB shell. I'm new in linux. It seems that GRUB doesn't detect the kernel. Maybe the file menu.lst has been deleted, or something similar, but I can't make my ubuntu to boot.
I just did a fresh install of Slackware 13.0 on a Toshiba laptop, and the ONLY thing I did on it after creating a user and switching to init 4 was to run upgrades. After doing so several applications failed to launch, so I rebooted the machine. I get the following error followed by a login prompt:
Code:
/bin/sh: error while loading shared libraries: libtermcap.so.2: cannot open shaed object file: no such file or directory And nobody can log in, including root. I've got another laptop running 13.0 with all the latest upgrades and it runs fine.
Is there a script which will take the patches subdirectory of the latest Slackware distribution tree, and substitute the new patch txz files for the ones in the slackware subdirectory so that during an ISO install, the latest txz will be used, instead, and the ISO will be minimized by not having the older ones?
For a long time I've used a custom xsession that loads Mythtv without any sort of desktop environment. Every time I upgrade I've just backed up and restored my xsessions entry. I did the same when switching to 10.4 only to find that the custom xsession entry causes gdm to login WITHOUT a password.When I select the custom xsession in GDM I get logged in immediately without a password or confirmation. The expected behavior is that I'd select the xsession and not get logged in until after entering my password. I've done some trial and error with this issue and it seems that it boils down to a single line in the custom xsession file.
I've evaluated about 15 offline storage systems this week, and one of the best was spideroak, but there's a huge issue in their shared folder structure and procedure.When you make part of your data shareable you MUST share a folder from your original disk. This is a real pain. You cannot share specific files like you can on many others.To initiate sharing your establish your unique username for sharing (different preferably than your spideroak username) the share name, and the room key (password).While you might expect the share name to be part of the URL that guides you to the share which then accepts your password for access, thats not how it works. Instead spideroak gives you a URL that contains the PASSWORD and does not even mention the share name!!
Therefore anyone you give the URL to has direct access to the share you create (which is what you are trying to accomplish in general) but any browser THEY USE will remember the URL which contains the password, not the share name.THIS IS A HUGE SECURITY ISSUE since you have no control over how an authorized user is going to access your data and from where and most users are not sophisticated enough to guard against the default intrusion they are going to leave behind.
I refrained from posting this in the Kernel Vulns thread earlier, due to its zero-day status. But now that the issue has been Slashdotted, there's no use in keeping us from publicly discussing this vulnerability. The link to the article (from which I quote below) is here. Brad Spengler's original announcement on the Dailydave mailing list is here.Quote:A researcher has published exploit code for a new vulnerability he discovered in the Linux kernel. The vulnerability is an especially interesting one in that the researcher who discovered it, Brad Spengler, has demonstrated that he can use the weakness to defeat many of the add-on security protections offered by SELinux and AppArmor.
Since an Aptitude upgrade to my Debian Squeeze operating system (using video driver NVIDIA-Linux-x86-195.36.24) some weeks ago, which installed linux kernel 2.6-32-5-686, grub has been giving me two boot options (in addition to MS Windows). I expect that this is quite normal so far ...
However, if I try to boot using this new kernel, rather than kernel 2.6-32-3-686, I can only get the command line interface. Everything seems to work after boot with the new kernel, except (although the system seems to load kdm successfully) I cannot start X. Booting with the old kernel still takes me to the desktop as normal (I've set KDE to automatically bypass kdm, as I'm the only user of this standalone PC), and because of this I've been slow to address the issue with kernel 2.6-32-5-686, but since the problem doesn't seem to be going away with more recent upgrades, I suppose a request to the forum is the only way to go:
So, is the problem I'm having the same as was addressed in this thread? If not, would I only need to reinstall the same NVIDIA video driver so that it recognises the new kernel? If not, would installing NVIDIA-Linux-x86-256.35 solve the problem, and would I have to deinstall the old video driver first? Finally, if and when I solve the problem, can I safely deinstall the old 2.6-32-3-68 kernel?
I juset reinstalled my ubuntu and i can't update to the latest kernel. I'm stuck at 2.6.31-15. Also my grub is v1.94 Beta4 and can't upgrade it to grub2.
I know the latest kernel for 10.04 is 2.6.35.4, however all Synaptic shows is 2.6.32 versions.How do I get the latest kernels to show up in Synaptic? Barring that, is there a .deb package somewhere that installs it?
This is old P4 laptop, Intel845G graphics (which I know is very troublesome).However, it works fine with the 2.6.35.22, but the update to 2.6.35.23 kills X during the boot process. Everything else works fine.Anyone else experiencing any difficulty with X and this kernel update?
I am looking for instructions on how to install the latest 3.0.3 kernel, and I can't seem to find much. I downloaded the necessary files from kernel.org, and they are currently contained in my downloads folder.How do I install this, now? Is there an easier way, like a PPA option to download and install from?
I want to have a linux distro thata has the newest kernel thats out now ,which kernelss would yuou recommend? or how would you download the newest kernel for fedora 13? or ubuntu. im using a acer aspire netbook and want to get some things to work.
I've noticed a bad behaviour with the latest 2 Fedora kernel releases:
- it happens with 2.6.31.12-174.2.19.fc12.x86_64 and 2.6.31.12-174.2.3.fc12.x86_64
- but 2.6.31.9-174.fc12.x86_64 is OK
The problem is as follows: Any kind of terminal application (any X based terminal and the console itself) hangs on certain operations involving colors from what I've seen
E.g. 'ls -F --color' as predefined in Fedora works but 'ls -F --color -a' hangs. Midnight Commander also hangs but works on black and white.
My terminal is xterm-256color under X and linux under console.
Other observations:
- it happens on a AMD machine but not on an Intel i.e. not all hardware is affected (couldn't narrow it more)
- same machine, same software stack but with kernel 2.6.31.9-174.fc12.x86_64 works OK
The latest kernel(2.6.32.9-67) is causing problems for my laptop.What are the best practices for safely removing a kernel?( Yum wants to remove gcc and friends also...)How can one prevent Software Update from relisting the bad boy?
Anyone know what happened here or what I need to do? I'm running Fedora 12 and had the nvidia video driver setup and working perfectly from rpmfusion repo ... I just did a yum update and now my display is stuck on 800X600 ....
I have a Macbook Pro 5,5. I had Fedora 14 installed on it, updated to the latest version. I updated the kernel, and performed an update. Now, every time my system starts, it loads up the startup fedora bar, and it gets stuck at the bar being loaded 100%.I press ESC to see what is going on behind the scenes, and I notice that the problem is that atd cannot start up.
Is this the latest version. i don't know how old 11.4 is, but there weren't a great deal of updates. have added a few repos like packman etc.
Kept /home as the same and what a difference that made. i used to do a fresh install every time, it saved just about all my settings!!! just needed a few more programs and stuff but nothing major.
Really quick, clean install. just need to delete my old root partition for the old 11.3 system.
Would also just like to know are there many differences between 11.3 and 11.4?
I reported a bug at [URL].., then I had been asked to test the latest generic kernel in order to test whether the bug exist in latest kernel or not. I had read the information at [URL]... I installed the most current version of generic kernel. After that, I restart my computer and try to use the latest installed kernel. Then, the laptop freeze. Then, I restart my computer by turning off and on again, select the older kernel, successfully boot into Ubuntu to post this thread. What can I do since I am required to test the latest generic kernel?
Twice now I have received update notices informing me of header upgrades which I installed, both required a restart of the system. Usually when this happens there is an additional item in the grub menu. The last two times this has happened I didn't get an additional menu item. What is the latest stable version? I am currently running:
2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 x86_64 GNU/Linux
I did try a "sudo update-grub2" and the menu didn't change.
Linux paneasbox 2.6.35-27-generic #48-Ubuntu SMP Tue Feb 22 20:25:46 UTC 2011 x86_64 GNU/Linux I want to update my kernel to the latest version from kernel.org, which is the mainline 2.6.38-rc8 .
EDIT: I found this guide [URL].. and I will give it a try
