I followed the documentation for upgrading lenny -> squeeze. After reboot I get 2.6.26 not 2.6.32. I also ran 'update grub' before reboot. Here is what I have:
jurka@arkiv-x:~$ dpkg -l linux-image-2.6.*
ii linux-image-2.6.26-1-686 2.6.26-13lenny2
Linux 2.6.26 image on PPro/Celeron/PII/PIII/P4
ii linux-image-2.6.26-2-686 2.6.26-26lenny2
Linux 2.6.26 image on PPro/Celeron/PII/PIII/P4
ii linux-image-2.6.32-5-686 2.6.32-30
Linux 2.6.32 for modern PCs
When I start the laptop, booting squeeze, after the screen printed"waiting for /dev to be fully populated... conflict with acpi region smbi..." (and maybe some other msg followed) the laptop will suddenly power off and automatic restart, after several times restart, I may have good luck to log into the squeeze KDE interface. The problem also occur when I choose booting in recovery mode How can I fix this annoying problem, or where can I check the fail booting log before the restart log overwrite it?
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?
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.
I'm attempting to dual boot my computer with Slackware, Debian and Windows. I've installed Lilo to the mbr from Slackware, i've edited my lilo.conf file so I can boot Debian. When I boot debian though, it says it's boot kernel 2.6.37 which is the slackware kernael it fails to load the modules. I think my problem is in the lilo.conf file in the debian line, "image = /boot/vmlinuz", if I've understood correctly I should put the debian kernals name after that line, I've done as I saw on the internet, but it comes up with, "kernel can not be found" or something similar to that. I think it's looking for it in a slackware directory. Is there a place on the debian dvds (i've all eight) I can get the kernel?
I'm trying to compile the 2.6.38 kernel (from the Wheezy sources) on my Squeeze laptop and get the following error: "dpkg-buildpackage: error: debian/rules build gave error exit status 2" After doing apt-get build-dep linux-image-2.6.38-2-amd64 and apt-get source linux-image-2.6.38-2-amd64 I did dpkg-buildpackeg and here is what happened:
downgrade my squeeze installation to kernel 2.6.32-29 (I think I have -30 now).
- what is the proper way to downgrade to that version of the kernel (I got my current kernel version when I installed squeeze few days ago and the official repo does not seem to have the -29 version anymore)?
- how to prevent that future automatic updates "upgrade" me again to the non-working version?
Laptop Amilo L1300, installed Debian Squeeze from netinstall from scratch a month ago. Installed Xfce as a DE afterwards.
This laptop usually has problem with: ACPI, Wifi and tons of other stuff usually Kernel related and is really picky about kernel version!
Now - with Lenny it worked without problems, but it had gnome and ext3 so I took a gamble and did a fresh install of Squeeze with Xfce with Ext4 filesystem and overall performance of the computer was faster and more responsive.
For wireless I have to use[url]
It all worked 100% until a week ago (roughly).
I do not use synaptic nor update manager, so I updated the system via terminal (as root of course) "apt-get update" and "apt-get upgrade". And I noticed it will upgrade kernel. I went through the upgrade process, as I thought it's all a 2.6.32-5-686 kernel version and it will not brake anything since it IS a stable branch of Debian and it will not install new kernel. Of course it did not install 2.6.34 or anything like that...
After the update I began experiencing problems, first with mouse pointer, it became invisible and goes back visible and resume from suspend, also wireless randomly disconnects and sometimes won't reconnect to wifi network, as I found out it's all kernel related problems (googled it up). I do not know how to go back to previous kernel version, since in Grub2 menu it only points to one and only kernel version, as I reckon it's the same version but with bugfixes? Or should I say buy UNfixes. I tried using a liquorix kernel 2.6.32 but as he works, has problem with ACPI as I presume since it freezes the system on random occasions.
Please, what EXACT version of kernel was in Squeeze like 3 weeks ago? And how can install that particular version of kernel, since it was the only one that worked besides the one from Lenny.
"uname -r" says: 2.6.32-5-686
That's what it always said.
Is it possible I had, dunno 2.6.32.28 and it was updated to, dunno, 2.6.32.29 or some later one?
I managed to google up this:[url]
And how can I go back to 2.6.32.28 kernel for instance?
I have squeeze with Gnome and 2.6.32-5-686 kernel. Due to problems with graphics card (kernel bugs), I'd like to update the kernel. The problem is, 2.6.32-5-686 seems to be at the moment last kernel for squeeze.Is it any way to update just a kernel and stay with squeeze or I must upgrade squeeze to the testing (wheezy)?
I just did an update of my Debian system from lenny to squeeze as described here. I got some errors during the install, saying that glibc couldn't be updated. I did an apt-get -f install, which gives me the following warning: WARNING: this version of the GNU libc requires kernel version 2.6.18 or later. Please upgrade your kernel before installing glibc.
The installation of a 2.6 kernel could ask you to install a new libc first, this is NOT a bug, and should NOT be reported. In that case, please add lenny sources to your /etc/apt/sources.list and run: apt-get install -t lenny linux-image-2.6 Then reboot into this new kernel, and proceed with your upgrade dpkg: error processing /var/cache/apt/archives/libc6_2.10.2-2_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Errors were encountered while processing:
Finally ran the upgrade from lenny to squeeze and ran into a few issues. I have to admit this is the first dist-upgrade I've ever had go this badly (kernel issues, xorg issues, mysql transition problems, mythtv... Yikes!).Anyway, the first problem I'm trying to fix is getting dpkg to like the new squeeze kernel. Here's the errors
Code: Errors were encountered while processing: linux-image-2.6.32-5-686
Yesterday, I ran a security update that upgraded my Squeeze kernel from 2.6.32-48squeeze8 to 2.6.32-48squeeze9.
Ever since then, my suspend to ram (STR) function is broken.
The machine will suspend normally, but will not resume. When I try to awaken the machine, I can hear the fan in the tower start up (the subject machine is a desktop computer, please see below for specifics), but the machine seems to be otherwise dead (e.g. the monitor stays blank, pressing the "caps lock" key on my keyboard does not activate said keyboard's "caps lock" led, Ctrl-Alt-F[x] has no effect, etc). My only recourse at that point is a hardware reset (ouch!).
I tried running Code: Select allpm-suspend from a terminal, with no joy. Same result running Code: Select allecho -n "mem" > /sys/power/state from a terminal.
I checked the /var/log/pm-suspend.log file and noticed that each Code: Select all...performing suspend line used to (before said kernel upgrade) be directly followed by a Code: Select all...Awake. line, but, now, all said Code: Select all...performing suspend lines are followed by an Code: Select allInitial commandline parameters... line.
Before this, STR has worked well ever since I first loaded Squeeze on this machine back in 2012.
Code: Select allSqueeze 6.0.10; 2.6.32-5-amd64
Intel i7-980 Gulftown CPU Asus P6X58D Premium Motherboard EVGA GeForce GTS-450 Graphics Card G.SKILL Ripjaw DDR3-1600, PC3-12800, 1.5v RAM (6x4GB sticks, 24GB total) Crucial RealSSD C300 128GB SSD Western Digital Caviar Black 1TB HDD Corsair HX850 PSU
I just wanted to know if i download Debian Squeeze linux-source-2.6.32 from packages.debian.org and try and compile it in debian lenny using lenny's packages will the build succeed ?
I run the 2.6.32-5-686 kernel on Squeeze and the bad nvidia drivers. A recent update, and pardon for not noting which, broke 3d games on my box.
From a terminal neverputt yields the following error:
ignatius@lapbox 14:56 [ ~ ]:$ neverputt X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 137 (NV-GLX) Minor opcode of failed request: 4 () Resource id in failed request: 0x2600013
[Code].....
I can mv xorg.conf to xorg.conf-pre and nexuiz will fire-up. Without 3d of course. I spent an hour or so last week going over my xorg.conf but it just ain't broke!
Someone else saw it, too, and reported it but his post remains alone in the thread as of 10 minutes ago. Anyone else seen this?
I don't play games much at all, but sometimes I just wanna frag muthafuckas and now I can't.
I recently installed Debian Squeeze on Acer Aspire 5542 , it has a Ati Radeon HD 4200 graphics card
I want to install the fglrx drivers , I apt-get install fglrx-driver, fglrx-glx & fglrx-control , The packages & dependencies download fine but when apt tries to install them the fglrx-modules-dkms fails .
I messed up my install so now I can't boot it. I get errors. I doubt I'll be able to fix it. I messed up the upgrade of the kernel images... I'm not sure whether there's something I could do in the Grub config file... I have one other Linux OS I can use in the meantime (plus Windows OS) so I thought maybe boot that up and check the Debian partition in case there's any files I want to save/keep. If I re-install, is Debian Squeeze LXDE still a good choice? I'm going to install something different in the partition where the other Linux OS is. Right now, it's grub is handling the boot loader. The computer is an old laptop, a Thinkpad T41. The HDD is 160GB.
I'm attempting to install ndiswrapper-dkms package. The installation fails due to the following error:Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. dpkg reports that the source is installed
[code]....
I've been searching google for the past couple of days but haven't found anything specific. Any ideas to get me going in the right direction?
uname -a reports
Linux debtop 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 GNU/Linux
I've got a fresh install of Squeeze on a 32bit host and I have been unable to boot into XEN/dom0.The Xen Kernel is "linux-image-2.6.32-5-xen-686" (pvops) and Hypervisor is xen-hypervisor-4.0-i386.The system default installed with grub2.It boots quite happily in normal mode, using the above Kernel, but just reboots itself if I try run it as Xen/dom0. (reboots within a second of pressing <enter> ... there is no messages displayed on the screen that I have noticed)The relevant menu (generated by /etc/grub.d/20_linux_xen) entry for running Xen is as below;
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386' --class debian --class gnu-linux --class gnu --class os --class xen { insmod part_msdos
It was no surprise that I needed to reinstall the nvidia driver after a 2.6.32-5-686 kernel update a couple days ago, but I was surprised that it didn't work. I've had to drop back to a kernel I compiled a few weeks ago, which is basically the stock 2.6.32-5-686 from that time, with a timer frequency of 1000 and desktop preemption. Vid card is GeForce PCX 5750 Using NVIDIA-Linux-x86-173.14.22-pkg1.run
This is the command I used: env CC=/usr/bin/gcc-4.3 sh NVIDIA-Linux-x86-173.14.22-pkg1.run (After it didn't work, I ran it with --uninstall and tried installing again. No luck with that.)
Here's the nvidia installer log (sorry about the encoding. I don't know what happened with that): [URL] rivafb, nvidiafb and rivatv are not loaded.
I don't see it in this one, but on a previous attempt, I saw an error message that said no nvidia graphics card was found. I've been suspicious that the card is slowly dying, based on problems like gray blocks on the screen or (in an older lenny install) persistence of the contents of a window appearing inside a terminal, when I switch desktops from the one where the browser is open to the one where the terminal is open. Scrolling the artifact off-screen and back, or window-shading the terminal and then un-shading it causes it to re-draw correctly.
i recently buy an MSI 770-45 motherboard with 4gb (2x2gb) Gskill 1600Mhz Ram. The CPU is an athlon2 x4 620, everything tested and working fine except i can`t get lenny or squeeze 64bit linux running because of kernel panics when creating ext3/ext4 partitions during install or running fsck on the system i installed on another PC and moved to this one. The boot shows a screen related to IOMMU problem saying must enable it in bios but no option related to it and no memory remapping also. The question is how i can get IOEMMU working with 4gb of RAM (if i remove one of the two modules everything is fine). I`ve tryed ioemmu=memapper/off/noagp/soft and any thing i found on the web, moving to test debian installation was my last hope really before starting to use the 32bit one, i am planning to add more RAM which with this version is just can`t be.
i'm trying to get my WLan working, i do have a Broadcom BCM4312 lpphy WLan-Adapter (pci-id according to lspci -vnn is 14e4:4315) in my Lenove ideapad S12. My System is Debian Lenny, but in order for the WLan-Adapter to work I installed the 2.6.32-3-686 Kernel from debian squeeze (using apt-pinning). I than installed the b43-firmware as described in the debian wiki [URL]. I updated the init-ramfs, everything is working as expected, except for WLan.
It shows up using iwconfig, i can get it up and down using ifconfig (or ifup, ifdown). I can't do a scan using iwlist - it says: % iwlist wlan0 scan > Failed to read scan data : Resource temporarily unavailable
It always fails, but not with the same error message. Sometimes it also comes up with > device or resource busy
Using dmesg I see reports about a fatal DMA error, resulting in a controller RESET. It says it's loading firmware 478.104 .
I've installed Debian Squeeze on my server several days ago. During install process installer asked me to provide USB flash drive with firmware aic94xx-seq.fw. All went fine. Today I installed all updates to my system with "U" in aptitude. Aptitude installed kernel update 2.6.32-5 and created initrd accordingly. But now I can't boot up my system because it can't find LVM volumes on harddrive connected to Adaptec RAID card. How can I boot my system now? I have USB with firmware.
I have netboot CD. Unfortunately when I tried to edit boot records in grub I found that there is no my old kernel anymore. The only kernel grub sees is the new vmlinuz kernel and new initrd How take make my server alive?
I installed 2.6.38 from backports. It boots OK, and among the start-up messages it says it has started kdm, but then it offers only a console login prompt, no GUI. I assumed (perhaps optimistically?) that newer kernels would be backward-compatible, and that any dependencies on other software would be enforced by the package mechanisms. Running amd64, Squeeze, KDE.
