Zhao, You should be aware that the following is two commands: cd /var/lib/dkms/fglrx/8.723/build; sh make.sh --nohints --uname_r=2.6.31-14-generic --norootcheck These are: cd /var/lib/dkms/fglrx/8.723/build sh make.sh --nohints --uname_r=2.6.31-14-generic --norootcheck The first is a change directory command to directory /var/lib/dkms/fglrx/8.723/build. This command will only fail if this directory does not exist. The second is running make in this directory. The key input to make is the file Makefile. It is found in this directory. I assume it is the Kernel module for fglrx which make is is intended to build. Make is much more complex and could fail for many reasons. My guess is make is failing (I assume the /var/lib/dkms/fglrx/8.723/build directory exists). However diagnosing make problems is outside my expertise. I would also expect that the install is running with root privileges and therefore should not have any problems with write privileges creating files etc. Therefore I think your following comment is wrong: I thought maybe it is just too shy to make such a folder there. The contents of the /var/lib/dkms/fglrx/8.723/build directory on my system is (You will note the existence of the files make.sh and Makefile): bryan@tardis:/var/lib/dkms/fglrx/8.723/build$ ls -l total 6820 drwxr-xr-x 3 root root 4096 2010-05-07 21:44 2.6.x -rw-r--r-- 1 root root 290 2010-05-07 21:44 dkms.conf -rw-r--r-- 1 root root 4363 2010-05-07 21:44 drm_compat.h -rw-r--r-- 1 root root 21251 2010-05-07 21:44 drm.h -rw-r--r-- 1 root root 4920 2010-05-07 21:44 drm_os_linux.h -rw-r--r-- 1 root root 31451 2010-05-07 21:44 drmP.h -rw-r--r-- 1 root root 15405 2010-05-07 21:44 drm_proc.h -rw-r--r-- 1 root root 4834 2010-05-07 21:44 fglrxko_pci_ids.h -rw-r--r-- 1 root root 163326 2010-05-07 21:44 firegl_public.c -rw-r--r-- 1 root root 37809 2010-05-07 21:44 firegl_public.h -rw-r--r-- 1 root root 27696 2010-05-07 21:44 kcl_acpi.c -rw-r--r-- 1 root root 5775 2010-05-07 21:44 kcl_acpi.h -rw-r--r-- 1 root root 12172 2010-05-07 21:44 kcl_agp.c -rw-r--r-- 1 root root 2610 2010-05-07 21:44 kcl_agp.h -rw-r--r-- 1 root root 1578 2010-05-07 21:44 kcl_config.h -rw-r--r-- 1 root root 4568 2010-05-07 21:44 kcl_debug.c -rw-r--r-- 1 root root 7202 2010-05-07 21:44 kcl_debug.h -rw-r--r-- 1 root root 5923 2010-05-07 21:44 kcl_io.c -rw-r--r-- 1 root root 6271 2010-05-07 21:44 kcl_ioctl.c -rw-r--r-- 1 root root 2703 2010-05-07 21:44 kcl_ioctl.h -rw-r--r-- 1 root root 2943 2010-05-07 21:44 kcl_io.h -rw-r--r-- 1 root root 1529 2010-05-07 21:44 kcl_osconfig.h -rw-r--r-- 1 root root 9660 2010-05-07 21:44 kcl_pci.c -rw-r--r-- 1 root root 3558 2010-05-07 21:44 kcl_pci.h -rw-r--r-- 1 root root 7519 2010-05-07 21:44 kcl_str.c -rw-r--r-- 1 root root 2925 2010-05-07 21:44 kcl_str.h -rw-r--r-- 1 root root 1863 2010-05-07 21:44 kcl_type.h -rw-r--r-- 1 root root 3448 2010-05-07 21:44 kcl_wait.c -rw-r--r-- 1 root root 1793 2010-05-07 21:44 kcl_wait.h -rw-r--r-- 1 root root 3251624 2010-05-07 21:44 libfglrx_ip.a.GCC3 -rw-r--r-- 1 root root 3251624 2010-05-07 21:44 libfglrx_ip.a.GCC4 -rw-r--r-- 1 root root 87 2010-05-07 21:44 Makefile -rwxr-xr-x 1 root root 15958 2010-05-07 21:44 make.sh -rw-r--r-- 1 root root 2630 2010-05-07 21:44 make.sh.log This is about as much help as I can give. Regards, Bryan On 30/05/10 20:55, Zhao Zheng wrote: > Bryan, > > Thanks for the very quick reply. I have checked my install log. It looks like that it is saying it cannot find my kernel: > ------------------------------------------------------------------- > Creating symlink /var/lib/dkms/fglrx/8.723/source -> > /usr/src/fglrx-8.723 > > DKMS: add Completed. > You can use the --kernelsourcedir option to tell DKMS where it's located, or you could install the linux-headers-2.6.31-14-generic package. > [Error] Kernel Module : Failed to build fglrx-8.723 with DKMS > [Error] Kernel Module : Removing fglrx-8.723 from DKMS > ------------------------------------------------------------------------- > To know what --kernelsourcedir I could give, I checked man dkms. It says usually this kernel source is in /lib/modules/$kernel_version/build. However, I did not find this folder 'build' in my /lib/modules/2.6.31-14/ at all. I checked another kernel in my system. It has a build folder, but it is pointing to /usr/src/linux-hearders-2.6.32.22, not the one I would need for 2.6.31-14. In /usr/src there is no such folder. I am not sure if I can install this? The problem is, I cannot boot to the 2.6.32-22 kernel at all because I got only a black screen, even in recovery mode. > > I tried to just copy the build folder from /lib/modules/2.6.32-22/build to the one of 2.6.31-14. Now I get a different error in the install log: > --------------------------------------------------------------- > Creating symlink /var/lib/dkms/fglrx/8.723/source -> > /usr/src/fglrx-8.723 > > DKMS: add Completed. > > Kernel preparation unnecessary for this kernel. Skipping... > > Building module: > cleaning build area.... > cd /var/lib/dkms/fglrx/8.723/build; sh make.sh --nohints --uname_r=2.6.31-14-generic --norootcheck....(bad exit status: 1) > 0 > 0 > [Error] Kernel Module : Failed to build fglrx-8.723 with DKMS > [Error] Kernel Module : Removing fglrx-8.723 from DKMS > ------------------------------------------------------------------ > > So it now looks like dkms has problem when 'cd /var/lib/dkms/fglrx/8.723/build'. I checked my folder there in /var/lib/dkms, there is only one single file dkms_dbversion. I thought maybe it is just too shy to make such a folder there. So I created the folders /fglrx/8.723/build in my /var/lib/dkms. Now the install log (/usr/share/ati/fglrx-install.log) changed to: > -------------------------------------------------------------- > Errors during DKMS module removal > Errors during DKMS module removal > [Error] Kernel Module : Failed to add fglrx-8.723 to DKMS > ---------------------------------------------------------------- > > It is just not very logical to me. It failed to remove old module. Apparently I don't have one. But it is still not installing a new one. So in the end I still cannot have a working driver. Strange thing is the Catalyst Control Center still works. Problems besides the lagging windows are: (1) I cannot activate advanced desktop effects; (2) I cannot start blender any more; (3) all the build in games cannot be started. For example: > ------------------------- > zheng@zzdesk:~$ quadrapassel > The program 'quadrapassel' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadRequest (invalid request code or no such operation)'. > (Details: serial 27 error_code 1 request_code 136 minor_code 19) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() function.) > > > zheng@zzdesk:~$ blender > bt_audio_service_open: connect() failed: Connection refused (111) > bt_audio_service_open: connect() failed: Connection refused (111) > bt_audio_service_open: connect() failed: Connection refused (111) > bt_audio_service_open: connect() failed: Connection refused (111) > bt_audio_service_open: connect() failed: Connection refused (111) > bt_audio_service_open: connect() failed: Connection refused (111) > bt_audio_service_open: connect() failed: Connection refused (111) > bt_audio_service_open: connect() failed: Connection refused (111) > bt_audio_service_open: connect() failed: Connection refused (111) > bt_audio_service_open: connect() failed: Connection refused (111) > bt_audio_service_open: connect() failed: Connection refused (111) > bt_audio_service_open: connect() failed: Connection refused (111) > Compiled with Python version 2.6.5. > Checking for installed Python... got it! > X Error of failed request: BadRequest (invalid request code or no such operation) > Major opcode of failed request: 136 (GLX) > Minor opcode of failed request: 19 (X_GLXQueryServerString) > Serial number of failed request: 28 > Current serial number in output stream: 28 > --------------------------------- > > I also checked my healthy 64-bit Karmic in another partition. It also > does not have the 'build' folder in /lib/modules/$kernel_version/. I > noticed that it has an additional folder fglrx in /lib/modules/. I tried > to copy this one into my Lucid partition. Nothing really changed, but > somehow this copied fglrx folder is deleted during the installation of > the new driver. > > I also tried to use Synaptic. It always fails to install the fglrx. It always deletes the /etc/ati folder. So I have to make sure to at least copy something there to allow myself back into my system next time. A more interesting error message is: > ------------------------------------------- > /var/cache/apt/archives/fglrx_2%3a8.723.1-0ubuntu3_i386.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > A package failed to install. Trying to recover: > ------------------------------------------ > > I then checked this file it has just mentioned. Then I was suggested to > do sudo apt-get install -f. Then I get the same error as above. Now I am > really confused. Still not able to install the driver, maybe more > precisely it is the 'kernel module'? Moreover, I still have the black > screen in the kernel 2.6.32-22. In addition, there is always a black > vertical strip on the right hand side of my screen that I cannot use. I > don't have this in my healthy karmic. > > Sorry for this really long post. I am relatively new and cannot really > make sense of what I see. So maybe just listing what I have done would > help make the problem clear to the more experienced. > >