I'm using Ubuntu 10.04 LTS. I'd like to use the latest kernel from repositories (at the present moment it's 2.6.35-23), that's why I've installed backports.
These are packages:linux-image-generic-lts-backport-maverick linux-headers-generic-lts-backport-maverick
But DKMS failed to build modules for fglrx: I think it's caused by old version of fglrx.
This is one of two new themes that just came with a "sudo apt-get upgrade" on my Lucid installation. Supposedly, the two themes are part of the same package, "Adium", and the themes look more like the Mac (or KDE) than anything else. The difference between the themes? One is dark, and one is light (The dark version is shown). This is roughly the same philosophy as Ubuntu Sun: Install light and dark themes as "leitmotiv for a lucid release". How do you think of this new theme in Ubuntu?
View 2 Replies View RelatedHow much time does it take (typically) for Canonical to release an updated version of the Ubuntu kernel? What I mean is that the 2.6.34 kernel is already out (on kernel.org), but we're still on 2.6.32.
View 5 Replies View RelatedYesterday, Linux Kernel was updated to version 2.6.31.14.The question is: will it be somewhere in Debian repos?
View 3 Replies View RelatedI have a Dell Studio 1537 Laptop with what lspci calls an "ATI Technologies Inc Mobility Radeon HD 3400" graphics card. Today I downloaded a daily image of Lucid, threw it on a USB drive, and booted it up. As I go to install the restricted driver for my graphics card, I notice that clicking on a panel item triggers the star burst effect. Come to find out that I can set desktop effects to "extra" and get smooth wobbly windows and everything.
Why are desktop effects working? I've always had to install FGLRX before, did the open source driver somehow get 3D support? Am I missing something? I almost feel like Compiz is performing better-- smoother, less tearing, etc.
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:
Here are 2 questions
1.In the last line of the debian kernel handbook 4.2.2 Applying patches
It is possible to apply extra patches to the source before starting the build. First, you should apply the existing patches by running:
You will then find the patched source in the subdirectories debian/build/source_arch_none (default) and debian/build/source_arch_featureset (featuresets added).
You should apply the extra patches in the appropriate subdirectory. where can I find the "extra patchies" and how to do?
2.Even though More than 8 hours have passed, 4.2.3 Building many packages
To build all possible packages for this architecture, run:
To build all architecture-dependent packages, run:
To build all architecture-independent packages, run:
The 1st command still working. what is the all possible packages? and what I am doing?
I am just trying to rebuild debian linux kernel 2.6.26-2, Did I misunderstand?
Can I use the current FGLRX drivers with a Mobility Radon X2300 card on an HP6910p with Lucid?
View 2 Replies View RelatedA kernel update just killed my ATI graphics driver.
Trying to install proprietary graphics driver fails and points at /var/log/jockey.log
This ends with
Code:
If I can't sort this out I'll have to try rebooting into the old kernel to get the graphics driver back. The dreadfully slow scrolling in the browser is starting.
Posting from my Windows 7 system. Once again an Ubuntu kernel update has broken X. Once again I cannot get into Grub2, despite putting in the hacks to lengthen the time it listens. I don't need instructions on how to fix it from Live CD. I'm going to try Gentoo or something, anything, different. I need a Linux distro that can survive regular updates and boot to desktop reliably.
View 1 Replies View RelatedEvery time the update-manager decides to upgrade the kernel my graphics driver is ****** up. I have had this problem in 10.04 and now in 10.10. Now I get dropped to the command prompt after an upgrade (I can also log in with fail-safe/low graphics mode). The problem is solved if I reinstall the package fglrx so nog big issue but it is rather annoying. What could be wrong? I am using ATI HD4770. I haven't tried open drivers yet.
View 7 Replies View RelatedExcerpt of Xorg.0.log output:
[Code]....
September 20 2010? Is there a newer kernel module for fglrx? How can I get and install it?
I have an HP tx2500 tablet pc running 9.04, which I was trying to configure the tablet for using the .fdi method on this page. After I redid the .fdi file, I rebooted, and it gave me a flashing screen, similar to the one i got when I tried to install 9.10.
I tried going into recovery mode and using xfix: bad idea. Then, I tried installing envy and reinstalling the drivers from there. That failed as well.
So now, when I try to manually remove the ati packages,(from command line in recovery mode) it doesn't let me, because of some problem with "fglrx-kernel-source" I can't configure, remove, or purge.
I have an ATI radeon HD 3400 series video card, and the open-source drivers make my computer run really hot. I tried installing FGLRX by using "Check For New Hardware Drivers", but it did not work, so I installed the ATI catalyst 10.5 package from AMD's website, and am using Xserver-xorg-core-1.7.6-2ubuntu7+backclear1 from k0ekk0ek's PPA so there is no lag when minimizing windows and such.
Everything was perfect until the 2.6.32-23 kernel update came along. I let it update, and rebooted, but the ATI driver no longer starts, even when I uninstall and reinstall it.
I am just using the 2.6.32-22 kernel for now, as the 2.6.32-23 kernel still runs hot without the ATI driver enabled. I would like to start using the new kernel at some point...
I am currently having an issue installing the FGLRX driver in slackware 13.1. I use a customer kernel due to buggy acpi on my toshiba laptop. The steps i took to compile my kernel are as followed. hu
make mrproper in /usr/src/linux directory
patch /usr/src/linux directory
copy kernel config from /boot directory
make menguconfig and load config
the make all
make modules install
i have also tried make install as well
then i mopy system.map the kernel file and config file into /boot directory
edit lilo
reboot ... everything works fine acpi works properly like before.. now the problem comes.. I try to install the fglrx drivers and i get the error message
Code:
Error:
kernel includes at /lib/modules/2.6.33.4-smp/build/include do not match current kernel.
they are versioned as ""
instead of "2.6.33.4-smp".
you might need to adjust your symlinks:
- /usr/include
- /usr/src/linux
ERROR: I don't have make module
Am I doing something wrong setting up my kernel. Issue on my gentoo box I have.
I've been reading about a temporary solution to the kernel/Fglrx issue caused by the last kernel update, but I haven't read about any permanent solution to this issue. Anyone know anything about a permanent solution (new kernel update?, new Fglrx driver?) to this compilation error?
View 6 Replies View RelatedI have an HP laptop running 11.3/KDE4.5.2, has integrated HD3200 ati graphics.
Yesterday, ATI version 10.10 fglrx driver was installed on the system, kernel was 2.6.34.7-0.4-desktop. I use the "build rpm" option with the downloads from ATI. All seemed running well.
I had installed the automatic recompile script posted by please_try_again after moving to 2.6.34.7-04, so today's new 2.6.34.7-0.5-desktop update was a chance to see it in action.
After the update and reboot, the X server restarted so I have to assume the automatic recompile script ran, although I did not see any messaging (place to look?).
However, some things did not seem "quite right". fgl_glxgears ran, but seemed slow (only 70 or so fps) pm-suspend failed to sleep the machine, I see the error message "s2ram_do: Device or resource busy" in /var/log/pm-suspend.log, which I think (?) is fglrx related but not sure why I think that. I moved to a root terminal, init 3, removed the fglrx rpm with yast, deleted the fglrx rpm and rebuilt a new one with ati....run. I then installed the new rpm (with yast), ran aticonfig --initial, then rebooted.
Basically, I am at the same level as above, fglrx installed and running, but slow and pm-suspend still not working.
So now I wonder if there is a new problem with the -5 kernel update, something like the excitement a couple weeks back when we had to patch the driver (or the kernel symbols) just to get a compile.
Can i assume someone has been able to cleanly update to 2.6.34.7-0.5 and get their fglrx running again?
An observation, which may or may not be related to my issues. The fglrx rpm installs a new /usr/lib64/dri/fglrx_dri.so, but in reviewing the log file /var/log/Xorg.0.log, it never appears to load. Two other *dri*.so modules do load. There is no "dri" section in Xorg.conf; I seem to recall there being one a while back, but much seems to be changing there.
That's it guys. I have successfully installed the proprietary ati drivers in past 6.34 and 6.35 kernels but not in latest .6.36. I'm wondering if this have something to do with compatibility or not.
Installation log shows me some errors I can't recognize:
Code:
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 .
The Kernel is 2.6.35.
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.
View 2 Replies View RelatedI'd like to install the 2.6.35 kernel while keeping Lucid (just not in the mood right now to get used to a new release). Can someone point me to a tutorial on how to go about this?
View 3 Replies View RelatedI have just run an upgrade and noticed Kernel update 2.6.32-22 for lucid. Anything new in that? Anyone have any details?
View 9 Replies View RelatedI have been running 64 bit Koala on an HP desktop with 8 GB for a few months. Now that Lucid is out and the kernel has stopped changing every three days, I thought I would do a clean install of 64 bit Lucid. Backed everything up, verified the .iso I downloaded a few days ago and burned a CD, and away we go. Everything seems clean, finds the old /home, asks for a restart. I say go.
Suddenly there are way more options on my grub menu. Every Linux option has an alternate with PAE, and the PAE option is the default boot. I didn't even think about it and let it take the default. The reboot hangs. I had to pull the plug to turn the machine off.
I reboot again with PAE. It hangs again. Pull the plug. Reboot without PAE and I'm golden. Google soon turns up all sorts of old advice to add noapic to the boot parameters on a PAE kernel. Instead I sat back and started thinking.
Am I doing with a kernel marked PAE in the first place? This is a 64 bit install. It doesn't need PAE. I look again at the .iso and it's 64 bit.
Code:
Looks like 64 bit to me.
Why I have PAE options that will not boot?
What is the latest kernel released for lucid? I have linux headers 2.6.32.21 and linux headers 2.6.22.386 but I do not think they are correct.
View 1 Replies View RelatedI am looking for an upstream kernel in hope that a few bugs are ironed out in my Lucid Kubuntu install. I tried about 2 weeks ago to get a precompiled kerel from the upstream kernel PPA [URL] but the problem is that it was built with gcc 4.2 and lucid comes with gcc 4.4 a little bit sub-moronic considering that Lucid won't accept modules built with a different compiler. I am also a little sub-moronic as I don't know how to tell if todays kernel is still being built with the 4.2 compiler, I downloaded the build.log file but I can't find any references to gcc 4.2 but as I said when I installed and tried build my Nvidia modules - no dice.
It says it needs either a kernel built with gcc 4.4 or something else. I would rebuild from scratch but I only have 1mb left for the next 10 days then my isp charges me 10c per meg, so I don't want to download the 400mb for the ncurses etc etc (thats the size it told me from aptitude to get just the additional packages and then i would need the kernel source...) They are still using gcc 4.2, and why? Where there is an official prebuilt kernel 64bit built with gcc 4.4???? or is this just another great bug that I must put up with.
I went to fire up Lucid this after noon and it gave me this error message. I didn't want to write all of that down so I took a picture. After several minutes it did nothing. I then decided to do a hard restart. This time it isn't giving a signal to the monitor. The monitor is less than half a year old, but I tried another. Still nothing. It show's no signal like it's not even hooked up to a machine. It doesn't even show the BIOS menu! I don't know if this is the cause or not but, I left my computer at my mothers house last night were they had a thunderstorm.
I have several applications like Virtual box and Mobloquer that took a hell of a long time to setup. Plus three guest operating systems, and some work that I didn't backup like videos. If we can get this up and running without re-installing.
Just wondering if anyone is using the Maverick kernel backport with Lucid? Just wanting to know how stable it is.
View 9 Replies View RelatedI just installed a fresh box with a Ubuntu Lucid 32bit.
Is it possible and safe to install Liquorix Kernel in this distro?
I've done that in debian squeeze installations, but never done that in Ubuntu and really don't know if it's possible.
I wonder if others have upgraded their Lucid kernel using the deb [URL]..repository. I have been using the repository for some time now without any apparent problems, and have gone from 2.6.36-1, through 2.6.37-10, and am now on 2.6.37-12.
All of these seem to work with no problems at all, but I am just wondering if other users can also report success, or if there are any trip-ups that might occur. I still keep updating the "standard" kernel from the main repos, ie 2.6.32-27, so I have that as a backup, but I'm just very curious about other people's findings.