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.
I have a system that was upgraded from Debian 7 to 8. Unfortunately it is not able to boot from the new kernel 3.16. Only the old 3.2 kernel is able to boot. I could transfer a backup, install it in Virtualbox, redo the upgrade and I can reproduce the error..The last error before "panic" is this line
Code: Select all 59.073579] Freeing unused kernel memory: 216K (ffff8800017ca000 - ffff880001800000) Loading, please wait... [ 59.226154] systemd-udevd[53]: starting version 215 [ 59.326564] random: systemd-udevd urandom read with 4 bits of entropy available Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... /init: .: line 210: can't open '/scripts/init-premount/ORDER' [ 59.552148] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
Intel Core i7-5500U with Intel HD Graphics.So I updated to the backports kernel and backports intel xorg drivers and I have the weirdest thing.Everything is stuttery even cinnamon desktop effects are no longer smooth. If I boot back to 3.16, everything is butter (except the screen corruption). Even my favorite wine game dropped 25% in fps.
I remember that on windows, if the cpu is too slow (pstate_min_speed), graphics is also stuttery. However, increasing /sys/devices/system/cpu /intel_ pstate/min_perf_pct even to 100% didn't do the trick. I suspect, that this measure is causing it: URL....
how to increase the performance again? I just found out, after running glxgears (with about 40 fps), that xrandr shows an available framerate of 40fps
xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1920x1080 60.00*+ 59.93 40.00
I guess that's what makes it feel slow. Do you know how to get that back up to 60 (fixed)? It seems like the screen refresh rate set in xrandr has no effect on the problem. When I boot, glxgears runs with 60 fps and everything is fine. After a while, it drops to 40 and the whole desktop keeps stuttering. if I change the resolution with xrandr and then change it back, it goes to 60 again for a while
I have a problem. I'm using the latest Debian stable, Lenny. I am trying to get my usb wifi card working. The Debian wiki advised me to upgrade my kernel to 2.6.30 using backports, because the drivers for my wifi chip are supposedly in the newer kernel.
So thats what I did. The install went fine. However, after rebooting the computer hangs when it is starting gdm. Only the desktop background appears with some fuzzy stripe over it, the mouse doesn't respond. Pressing ctrl+alt+f1 does nothing. I can only restart with ctrl+alt+del.
I can still use the computer with the old kernel. No problems there. I tryed disabling GDM and rebooting again with the new kernel. It boots up and works fine on command line. However when I type startx it hangs, just like before.
I'm not an expert, but I'm suspecting there might be problems with the graphic drivers in the new kernel. When I installed lenny at first, X started fine. However 3d acceleration was not functioning. I got help from IRC, I had to install some package to enable direct rendering. Don't remember which one anymore.
Here's what lspci gives for VGA: 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS
Testing distribution. Installed Linux 3.0 but left 2.6.32 on as backup. When I boot into the old kernel, wireless mostly works OK, but never when I boot with the new kernel.
Results of dmesg|grep wlan0 on 2.6:
[ 22.005102] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 28.196774] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 28.644779] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 30.688053] wlan0: direct probe to AP 00:19:5b:06:9f:ba (try 1) [ 30.694053] wlan0: direct probe responded
[Code]...
Noticing the Access Point looked like it needed the MAC address, I ran iwconfig wlan0 ap <MACADDRESS> and sometimes it will work, and wicd can connect to the access point. But sometimes the command fails to run.
I am running Debian squeeze. A while ago I upgraded my kernel to 2.6.38 from backports. Just now I thought it would be good to upgrade to 2.6.39 from backports. Upgrade went fine, but after rebooting I get a kernel panics rightaway.
"No filesystem could mount root, tried:" "Kernel panics = not syncing: VFA: Unable to mount root fs on unkown-block(0,0)."
This is the first time one of Linux installations halts/panics on booting, so I don't know what to do now. I tried booting the recovery entry from the grub boot menu, but same result.
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?
I 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".
I 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.
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.)
We have a Dell 1850 with Debian with 2.4.18 kernel running some critical applications, now the issue is we need to upgrade the memory to 8 GB but the memory is detected by the bios itself, Operating system is not able to detect it, it is showing 3096MB of memory,
After a lot of googling and the artical in linux.com/archive/articles/119287 :: Got more than a gig of RAM and 32-bit Linux? Here's how to use it i came to know the solution i.e
1)I need to install the Bigmem-kernel to detect the ram more than 4Gb,
2) or change some kernel parameters in configuration file and rebuild the kernel
Is there any another solution for this to update operating system to detect the more RAM
We have a Dell 1850 with Debian 3.0 (woody) with 2.4.18 kernel running some critical applications, now the issue is we need to upgrade the memory to 8 GB but the memory is detected by the bios itself, Operating system is not able to detect it, it is showing 3096MB of memory. i came to know the solution i.e I need to install the Bigmem-kernel to detect the ram more than 4Gb, Any another solution for this to update operating system to detect the more RAM.
I've just install debian squeeze version, or the testing one, but I am not really happy with it. Is not listening me all the time. If I install the debian stable I don't have internet connection. Is it possible to update the kernel somehow using the testing version?
On 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?
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)
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:
My 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.
I'm running testing, so yesterday I upgraded to the new kernel (2.6.38). Unluckly I can't get to the desktop, because the system just hangs (screen goes black then nothing happens). I have found that my problem is the radeon (open-source) driver. When the it tries to get to the desktop it enters an infinite loop, so the system hangs. The bug is better described here: [URL]. However, I don't know how to fix it. I would prefer not to go to the fglrx (proprietary) driver because of tearing issues.
I'm running Lenny with the default kernel 2.6.26. I recently got a wireless card supported by the ath9k driver, so I followed the instructions on this site:http://wiki.debian.org/ath9kwhich had me install a 2.6.32 kernel image from lenny-backports. Everything installed fine without errors, but when I rebooted after the install, after the kernel messages scrolled by and the screen would normally switch to the gdm login screen, all I got was a blank screen with some distorted squares. I used Ctrl-Alt-F1 to switched to a shell and everything looked fine, but when I Ctrl-Alt-F7ed back to X, I got another black screen with distorted images. Any idea what could have caused this from the kernel upgrade, and what I can do?Edit:Here is the end of my /var/log/Xorg.0.log after booting:
(EE) fglrx(0): PPLIB: PPLIB is not initialized!. (EE) fglrx(0): PPLIB: swlPPLibNotifyEventToPPLib() failed! (EE) fglrx(0): ulEventType = 0000000c, ulEventData = 00000001
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