I'm using Squeeze amd64, installed latest kernel 2.6.38 from backport yesterday. Just now try to check for any update but failed, these messages show.
View 2 Replieswhen I try to update my Debian, I have the following internal error:Error message:Fetch failed: W:Failed to fetch [URL] Unable to find expected entry free/binary-i386/Packages in Meta-index file (malformed Release file?), W:Failed to fetch [URL] Unable to find expected entry free/binary-i386/Packages in Meta-index file (malformed Release file?)
, W:Failed to fetch [URL] Unable to find expected entry free/binary-i386/Packages in Meta-index file (malformed Release file?), E:Some index files failed to download, they have been ignored, or old ones used instead.
I do not know if this is really something I should worry about. I am running Debian testing on my laptop (HP Pavillon dv6). Today, the aptitude update---aptitude upgrade gave me a new kernel (2.6.39). However, if I boot with that kernel, I get a warning (do not know if that is the way I should call this) telling me that the machine failed to get the i915 symbols so turbo graphics will be disabled.I have not done any serious test, but at first sight I do not notice any difference performance-wise with respect to the previous kernel. what am I supposed to do to fix this?
View 8 Replies View RelatedI 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 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 have done a update from Lenny to Squeeze with the update manager within Gnome. And there was a error 126 and the update broke off leaving me with a non working system. The system does start into Debian Squeeze to the command line. Users are in place and a login is possible. X does not work and there a lot of broken and defect packages. I want to repair my system. Is a restore without losing the configuration possible?
View 14 Replies View Relateddowngrade 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?
Should I use some of the snapshots from [url]?
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)?
View 7 Replies View RelatedI 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 ?
View 6 Replies View RelatedI 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:
[Code]...
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
[code]....
I updated today and naturally removed the old nVidia driver, compiled it again after a reboot, and then rebooted again for good measure. I can log into KDE4, but all I get is a cursor and a solid black background. I deleted the ~/.kde, ~/.local, and quite a few other directories from my normal user account using the shell so KDE would reconfigure my settings when I logged in again, but it's the same problem. I went into ~/.kde/share/config/kwinrc and added the "Compositing" section with "Enabled=false" to rule out compositing. Now when I log into the system I get the default KDE4 wallpaper and a mouse cursor, but nothing else. I believe the latest update broke KDE4, or am I missing something? I have recreated my xorg.conf as well, and only set it to use the nVidia driver. So what can I do now?
View 3 Replies View RelatedAre the 1.3 Wine packages availible at [url] compatible with the Squeeze kernel? What about future updates to the packages there?
View 3 Replies View RelatedI 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.
View 6 Replies View RelatedHave my proxy running on Lenny and tried to upgrade to squeeze. Originally the system was installed on Etch and upgrading to Lenny was no problem. In the system i have two RAID1 volumes, md0 for / and md1 for /home. For upgrading i added the sources to my apt.conf and startet dist-upgrade. During the installation procedure, when installing udev I was advised to install the new kernel first and continue upgrade after booting the kernel. so I installed the kernel by "apt-get install linux-image-2.6-686. When generating initramfs there was a message, that there are no arrays defined in /etc/mdadm/mdadm.conf I took a look and there were none. mdadm seems to have been update before.
I then added the lines for RAID definition and added the data for UUID The UUID I got from the output of "mdadm --detail /dev/md0"
What I don't understand: blkid gives the same UUIDs for the first partitions of the RAID and a different UUID for /dev/md0 and /dev/md1 than mdadm --detail The update of initramfs for kernel 2.6.32 then gives this result:
update-initramfs -u -k 2.6.32-3-686
update-initramfs: Generating /boot/initrd.img-2.6.32-3-686
W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module e100
W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module e100
[code].....
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'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 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 RelatedHi,I'm using a Dell Lattitude D620 laptop. I just installed the latest kernel 2.6.38 in my Squeeze amd64 :
Output of uname -r
2.6.38-bpo.2-amd64
Now I'm running on new kernel,everything seems fine except my wifi ( now I'm connected through ethernet ). Before I do the process with the guide in http://wiki.debian.org/wl to activate my wifi,I'd like to ask for some advice here,is this latest kernel support my wifi card? If yes,how to activate it?
Output of lspci :
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
[code]....
I have just updated my Squeeze system. The update included a newer version of network-manager (and it can not be more than a few hours old). After the update all network functionality on my machine (via knetwork-manager) is broken. The GUI applet has no effect.
Hence can anyone help me: a) Downgrade network-manager by one version; b) Find out what is causing knetworkmanager to break; c) See if the problem is with knetworkmanager or network-manager.
I installed linux-image-4.1.0-trunk, when I boot into the kernel there's no wireless available. Dmesg indicates seems like the firmware is loaded, although firmware-iwlwifi is installed:
...
[ 11.047031] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-7265D-13.ucode (-2)
[ 11.047039] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7265D-13.ucode failed with error -2
I ran my daily update of Debian Stretch using Synaptic, and when done had an un-installed update for ifupdown remaining marked in the list. By right clicking I was able to get Synaptic to say it would install the update, along with quite a few other updates. In the process of doing this, my screen went dark and stayed dark. On reboot, I get the Grub menu to select which Linux system I want to boot, but whichever one I choose, including older ones, I get to a command line, not the Gnome GUI.
I tried to complete the update of ifupdown using apt-get, only to discover that my machine no longer has any network connection, let alone Internet.
How do I begin to troubleshoot this?
From the securing-debian-howto [URL] ...
"4.2.2 Security update of the kernel
First, make sure your kernel is being managed through the packaging system."
which suggests...
Code: Select all$ dpkg -S ‘readlink -f /vmlinuz‘
When I try to confirm by running the above, I get a lot of characters of output but the last line reads...
Code: Select alldpkg-query: no path found matching pattern /vmlinuz‘
How do I make sure my kernel is being managed through a packaging system?
I've just installed debian sid and see that I've the kernel 2.6.32. I was a bit surprise as on ubuntu I had the 2.6.35 and debian sid is supposed to be more up to date that ubuntu (maybe I'm wrong).So I checked what were the packages available :
mart@mart-laptop:~$ uname -a
Linux mart-laptop 2.6.32-5-686-bigmem #1 SMP Sat Oct 30 23:25:58 UTC 2010 i686 GNU/Linux
mart@mart-laptop:~$ sudo aptitude search ^linux-image
[code]...
how to install Dropbox for Debian Squeeze from source.Please read everything before you begin. I prepared it as I installed Dropbox for my own system. Please Note: I use sudo, you may have to use root or 'su' from the command line. If you don't know the difference between sudo and su, then you shouldn't try this until you know. At the time I did this, the lastest dropbox version was 0.6.7.
View 7 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 .
The VirtualBox website have a 64 bit deb for installation available for AMD64 Lenny but not for Squeeze. Is it okay to install the Lenny package on Squeeze or would this cause a problem?
View 4 Replies View RelatedI installed Debian Squeeze (choosing no when prompted to add support for non-free or contrib sources) and noticed that the fan of my Nvidia 9600 GT video card is constantly running at full speed. I thought this meant that the default driver is not properly working. I would like to configure my system so that the video card fan is not being pushed so hard.
I downloaded the latest Nvidia (propietary) driver, stopped gdm3, and ran the driver installer. The installer failed because it said the Nouveau kernel driver was currently in use and incompatible with the Nvidia driver. I chose not to allow the installer to update my modprobe configuration directory. nvidia-installer log file '/var/log/nvidia-installer.log'
[Code]...
It looks at though the xorg.conf.new file has the nv driver in use, but the Nvidia installer says the Nouveau driver is being used. I ran a line in terminal (i forget the exact line) to test the xorg.conf.new file in the /root/ directory. The result was No Screens Found.
Next, I tried to remove the xserver-xorg-video-nouveau package using aptitude, but it displayed a message indicating that xserver-xorg-video-all depends on it. I decided not to remove the xserver-xorg-nouveau package. Any suggestions on how to proceed in order to configure X with a free driver (nv, vesa, or nouveau) so that the video card is handled properly?