Debian Configuration :: Fglrx Isn't Working With The Latest Liquorix Kernel
Nov 5, 2010
For quite a long time now, I haven't even needed to re-install video drivers most of the time. However, ever since version 2.6.36-0.dmz.4, they haven't been. I booted my system after installing that kernel, re-installed the video drivers, and when that didn't work, completely removed them and re-installed them, and it still didn't work. Well, I was told that the installation was successful but even after restarting it appeared that they weren't working. I installed 2.6.36-0.dmz.5 today and the same problem persists. I tried an older kernel version (2.6.36-4 something) and they worked fine.
I installed the latest kernel liquorix (2.6.35) but when i want to install the Nvidia driver downloaded on the Nvidia website (256.53), i have an error message because Nvidia doesn't found the kernel source tree.
I install linux-image-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb, linux-headers-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb and build-essential. I don't understand why the installation doesn't works.
I have ran the regular apt-get update && apt-get dist-upgrade and it pulls in newer versions of the liquorix kernel pretty often. Now whenever I boot up my system, I notice that there are now about three different 2.6.36.dmz liquorix kernels installed (I can't remember the exact numberings on that).
How can I remove all versions of the liquorix kernel except for the latest?
I searched the forum about installing the liquorix kernel but I cannot understand why the file /etc/apt/sources.list is not mentioned to invoke the liquorix repository.
Instead, I found: Alternative Performance Kernel for Debian wrote:For anyone interested, just add the following to a sources file (/etc/apt/sources.list.d/liquorix.list): deb [url] or for you scripters, echo "deb [url]
I'm using Squeeze and icedove and iceweasel and I've installed the package linux-image-2.6.36-2.dmz.2-liquorix-686. It works fine on my Dell 1521 Inspiron laptop with only one exception. If I'm surfing the web or checking my mail via a wired internet connection I'm fine... if I'm surfing the web or checking my mail via a wifi connection everything is fine... but if I happen to forget to connect to a wifi connection, and I'm in a situation where a wired connection is not available, I can start iceweasel (it doesn't do anything constructive), but checking my mail with icedove (simply starting the program) crashes my computer.
If I boot up with the 2.6.32-5 kernel, the one that's in the regular debian repository, I can not duplicate the crash. Somewhere I read that the liquorix kernels are optimized for a desktop computer. Is this my problem? Is it something else?
During the crash my screen goes to a text console and I see syslogd messages on the screen -- which I cannot reproduce here.
Got this while installing the kernel development tools on my Squeeze system being used as a router/firewall. Setting up update-inetd (4.36) ... Setting up cvs (1:1.12.13-12) ... Ignoring install-info called from maintainer script The package cvs should be rebuilt with new debhelper to get trigger support Ignoring install-info called from maintainer script The package cvs should be rebuilt with new debhelper to get trigger support Setting up autopoint (0.17-11) ...
Is that an issue that I need to address prior to building the latest kernel (220.127.116.11)?
This may sound ridiculous, but after installing Debian 5 (from CD 1) in my laptop, ASUS UL80VT, it fails to detect the Ethernet device. The device is "Atheros AR8131 PCI-E Ethernet Controller". I guess the problem comes with the old kernel of version 5. I was intending to compile the latest kernel anyway. But the problem is is there any heads up i need to download the kernel and trying to compile it? Is there anyone who uses Debian on UL80VT. If there is, does it works okay?In short I want to compile the latest kernel, hoping it will fix the Ethernet device. There are installers available with the latest kernel. But I want to do it on my own.
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
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'm running Debian Squeeze/current fine with the default kernel & ATi's Catalyset drivers. I'm struggling to get the display drivers to work with the bigmem kernel as I've got 4GB ram on my machine so might as well try to enable it.
I can have my system work with the normal Squeeze kernel by installing the normal kernel headers & then FGLRX drivers, but after additionally installing the bigmem kernel & headers (linux-image-2.6-686-bigmem & linux-headers-2.6-686-bigmem) I cannot get the system to reach X after removing & then re-installing the video drivers.
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 .
My system is hanging on screen suspension... And its not the usual hang on "sleep" or others similars, it will happen by only having the screen on stand-by ( eg xset +dpms)...
If I leave for a while the screen will shutdown as expected but computer will completely hang after an indefinite time, it will not respond to outside connections and the will be spinning faster than usual...
Only workaround is to have the screen power save option disabled, in my case, on the KDE settings...
I have tried the most common solution to have "nomodeset" as a kernel option to disable mode setting, but this doesn't seem to work...
Also tried to forcebly reproduce the issue with Code: Select allxset force dpms standby/suspend/off but nothing happens like that...
This issue also only appears with the fglrx driver, open-source works well.
I have been trying to install fglrx drivers for my ATI card with Debian testing (x86) but without any luck. I have tried what it says here http://wiki.debian.org/ATIProprietary but I only come up with a blank screen (and also invoke-rc.d gdm stop does not work either?) I have also followed the directions at [URL]....html and that doesn't work either (make error 127). I must be doing something totally wrong.
I am running Maverick via Wubi. I just completed a Kernel upgrade and when I restart into Ubuntu it just goes to a Bash prompt. I am not sure exactly what version I updated to so I haven't logged a bug report yet.
Also, doing /etc/init.d/start/ gdm3 says Starting GNOME display manager: gdm3 but it doesn't do anything. I tried pressing ctrl+f1 all the way to ctrl+f12 and nothing. What does work however is sudo gdm3 (with the "ati"/"radeon" driver --- nothing works at all with fglrx).
I am trying to get fglrx working because I want to fix this compiz issue I've been having here which could be related to the shortcomings of the "ati"/"radeon" driver: viewtopic.php?f=10&t=40991&p=312577#p312577
I got tired of not being able to run any 3D apps on my integrated Intel and went out and came home with a ATi Radeon HD 4650. Skip the bit about how I could have gotten an nVidia (they didn't have any HTPC compatible low-profile nVidias on shelf).
Actually the card works very well, it runs all the 3D apps I've thrown at it so far (and quite a bit faster too).
My problem is with video playback: it is jerky. The framerate stalls and then speeds up and is out of sync. When not out of sync, there is tearing. Yes I have tried turning Compiz off, didn't do anything. Weird thing is the CPU utilization is really low, so everything should be working.
I figured I would update the video drivers to the latest available on ATi website (following the instructions here) but I've ran into trouble with the installer:
How do I proceed from here? If you've got a fix for the video with the drivers in the repositories that is cool also. I don't necessarily need the latest drivers.
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 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.)
I have a HP Pavillion dv5 laptop with an ATI Mobility Radeon 4200 series. It always worked fine with Ubuntu for as long as I can remember. However, at one point, something happened and truly made a majestic mess of things. It might've been extra repos I enabled with Ubuntu Tweak - I do not know. But something made it so that my system would not boot any longer.
And when I say "won't boot", this is what I mean:
- Durning a normal bootup, any entries (except Windows) selected with GRUB (or BURG, not even sure which one I'm using anymore) will spawn the Ubuntu loading screen.
- then try to start X (or GDM) 5 times. The screen goes to dark, black and back to the Ubuntu loading screen. Then it just stays there until I spawn another TTY.
I have no idea what is happening or why. There are no errors in my logs, and I'm truly at a loss here.
I've linked three files: Xorg.0.log, the output of dmesg and the GDM log: