PDA

View Full Version : HOWTO: Kernel Compilation for Newbies


Pages : [1] 2

tseliot
November 1st, 2005, 04:52 PM
DAPPER USERS, please follow this guide:
http://doc.gwos.org/index.php/Kernel_Compilation_Dapper


THIS GUIDE IS FOR BREEZY

This guide is aimed at the newbies who are willing to learn something about kernel compilation or just who need a new kernel for incompatibility issues (e.g. DMA issues). This is a STEP-BY-STEP guide, so don't be afraid of compiling your first kernel, it's a piece of cake. Moreover if you need to compile any kernel module (nvidia modules, ndiswrapper, etc.) I will also explain how to do it.

It takes a while (even an hour) to complete the process described below, so make sure you have enough time to spend.

Make sure you have all the repositories enabled

BEFORE YOU START

If you have an Nvidia or ATI graphic card and you are using a proprietary driver (i.e. if you have installed the graphic driver before) please do this, otherwise get straight to step 1:

Open Terminal or Konsole and type these commands:

(if you are using GNOME, the graphic interface that comes with Ubuntu)
sudo gedit /etc/X11/xorg.conf

Otherwise

(if you are using KDE, the graphic interface that comes with Kubuntu)
sudo kate /etc/X11/xorg.conf

Scroll down the text until you find this section (this is my configuration):

Section "Device"
Identifier "ATI Technologies, Inc. Radeon 330M/340M/350M (RS200 IGP)"
Driver "ati"
BusID "PCI:1:5:0"

Substitute the word in red with “vesa” or “nv” (NVIDIA's opensource driver) or “ati” (ATI's opensource driver), make it look like this:
Section "Device"
Identifier "ATI Technologies, Inc. Radeon 330M/340M/350M (RS200 IGP)"
Driver "vesa"
BusID "PCI:1:5:0"

Save and exit. Restart the computer and go to the next step.

When you have the new kernel working you might want to reinstall the proprietary drivers for your graphic card. Have a look at my guide for the NVIDIA drivers: use method 2 if you want to install them manually OR compile the module with your kernel (as described below) and follow method 1 in my guide.

1) Open Terminal or Konsole and type these commands

uname -r (so as to see what kernel you are using)

NOTE: if you want to compile a vanilla kernel from kernel.org have a look at the end of the guide.Otherwise proceed with step 2.

2)
IF YOU USE UBUNTU BREEZY or HOARY:
sudo apt-get install linux-tree (this will download Ubuntu kernel sources and patches for kernel 2.6.12)

IF YOU USE DAPPER:

sudo apt-get install linux-tree

3) Open Terminal or Konsole (if it's not open yet) and type these commands:

sudo apt-get update
sudo apt-get install build-essential
sudo apt-get install kernel-package
sudo apt-get install gcc (this will install gcc-4.0 for kernel 2.6.13 or superior)
sudo apt-get install gcc-3.4
sudo apt-get install libncurses5
sudo apt-get install libncurses5-dev
sudo apt-get install libqt3-mt-dev
sudo apt-get install bin86
sudo passwd root
(and set the root password which you will need later)

cd /usr/src
sudo tar --bzip2 -xvf linux-source-2.6.12.tar.bz2
sudo ln -s /usr/src/linux-source-2.6.12 /usr/src/linux
cd /usr/src/linux

NOTE: if the computer says "file exists" when you try type this command "sudo ln -s /usr/src/linux-source-2.6.12 /usr/src/linux", you have to type "sudo rm /usr/src/linux" (this will remove the old link). Now you wont' have this error and the command "sudo ln -s /usr/src/linux-source-2.6.12 /usr/src/linux" will work.


sudo make oldconfig (so as not to compile the entire kernel from scratch)

If it makes you any questions just press Enter (so as to select the recommended answer)

sudo make menuconfig

4) Now you have to use the keyboard to move the cursor over the function or submenu you want and press Enter to select it.

Select the 4th option: Processor type and features

If you have a multiprocessor system you might want to enable "Symmetric multi-processing support" (SMP): select it with your keyboard and press the spacebar to enable it (a "*" will appear beside it). If you don't have it don't enable it.

Select Processor Family and choose the right one (i386 in my case) depending on the output of the command “uname -r” you have used before

Press the right arrow and select exit

If you have more than 900MB RAM then you'll definitely need this, otherwise (or if you are using Ubuntu 64 bit) skip this step:
Scroll down the text until you find “High Memory Support”.
Select it.
You'll have three possible choices:
Off
4GB (if you have no more than 4GB RAM)
64GB (if you have more than 4GB RAM)
Select one of these functions and press enter.
Press the right arrow and select exit

The following operation is required if you want to enable DMA directly in your kernel. You might want to try this if none of the methods found in this forum works for you, Otherwise skip it and go to Step 5.
NOTE: if you have old hardware which doesn't support DMA you won't be able to access this hardware with your new kernel. If this happens go straight to Step 8.

Select Device drivers

then

Select ATA/ATAPI/MFM/RLL support

Scroll down the text until you find (and highlight with the keyboard) “Enable DMA only for disks” and disable it by pressing N (now the “*” beside it should disappear, this means it is not selected any more)

Press the right arrow and select exit

5) Keep on selecting Exit until it asks you whether you want to save your new configuration or not. Answer yes.

Now you are back to the command line, type:

6) su
CC=gcc-3.4
export CC
exit
CC=gcc-3.4
export CC


7) DO THIS ONLY IF YOU NEED SOME RESTRICTED MODULE otherwise go to Point 8

There will be no restricted modules for the kernel you are going to compile. However if you need them you can pick the modules you need and compile them together with your kernel.

Get the source package/s (from Ubuntu's repositories or from the web) and extract it under /usr/src

For example if you need ndiswrapper and or the nvidia drivers:

sudo apt-get install ndiswrapper-utils

sudo apt-get install ndiswrapper-source

sudo apt-get install nvidia-kernel-source
OR
sudo apt-get install nvidia-legacy-kernel-source (if you have a old card which belongs to the list in the “Nvidia Legacy Cards” section at the end of the guide)

[If you have got the package from the web (and not from the repositories) extract the file wherever you want and then type: sudo mv /path_to_the_folder_of_the_extracted_file /usr/src ]


cd /usr/src/

sudo tar --bzip2 -xvf ndiswrapper-source.tar.bz2

sudo tar -xvf nvidia-kernel-source.tar.gz
OR
sudo tar -xvf nvidia-legacy-kernel-source.tar.gz(if you have a old card which belongs to the list in the “Notes section” at the end of the guide)

Repeat the commands you've just typed for any other module you want to add (you can add as many modules as you need)

When you have finished to extract any other additional module you have to type the following command in order to compile your kernel image, headers and modules.

cd /usr/src/linux

sudo make-kpkg clean

sudo make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers modules_image

NOTE: you can put whatever you want instead of “custom”

8 ) If you have followed point 7, skip this step and proceed to step 9
cd /usr/src/linux

sudo make-kpkg clean

sudo make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers

NOTE: you can put whatever you want instead of “custom”

e.g. sudo make-kpkg --initrd –-append-to-version=-alberto kernel_image kernel_headers


The system will ask you this question:

“By default, I assume you know what you are doing, and I
apologize for being so annoying. Should I abort[Ny]?”

Answer no by either typing N and then pressing Enter, or just by pressing Enter (as N is the recommended answer)

Well now you'll have to wait at least 45min. The process will use 100% of your CPU so try to leave your computer alone, go have a tea or something else just to keep you away from your computer for a while.

9) After the (long) process type this in the command line (Terminal or Konsole)

cd /usr/src

ls

You'll see a list of the names of the files in the folder as well as the names of your new kernel image , kernel headers (and modules if you have followed Point 7); they should look (approximately)like these ones:

kernel-image-2.6.12-custom_10.00.Custom_i386.deb
kernel-headers-2.6.12-custom_10.00.Custom_i386.deb

(you will also see the modules like the ones below if you have followed Point 7)
ndiswrapper-modules-2.6.12-custom_1.1-4ubuntu2+10.00.Custom_i386.deb
nvidia-kernel-2.6.12-custom_1.0.7667-0ubuntu3+10.00.Custom_i386.deb

Now install them by typing these commands (change the name of the files according to the ones you have seen after the output of the command “ls”):

sudo dpkg -i kernel-image-2.6.12-custom_10.00.Custom_i386.deb

sudo dpkg -i kernel-headers-2.6.12-custom_10.00.Custom_i386.deb

sudo dpkg -i name_of_the_module (only if you have followed point 7) (there might be several modules so you have to use this command for every module you have compiled)
e.g.
sudo dpkg -i ndiswrapper-modules-2.6.12-custom_1.1-4ubuntu2+10.00.Custom_i386.deb
sudo dpkg -i nvidia-kernel-2.6.12-custom_1.0.7667-0ubuntu3+10.00.Custom_i386.deb

REMEMBER NOT TO UNINSTALL your previous kernel (just in case anything goes wrong) (i.e. don't do anything else apart from following the instructions)

10) Ok, now it's time to see if they work.

Restart your computer.

Then if you want to see if DMA is active (if you have enabled it in the kernel as described before) type (in Terminal or Konsole):

sudo hdparm -d /dev/hda (to check if your harddisk has DMA enabled)
sudo hdparm -d /dev/cdrom (to check if your cd-reader has DMA enabled)

Don't you worry if it gives you an error as output but the performance of your harddisk and cdreader have improved (try to transfer a file from a CD to your harddisk and see if it the system slows down).

If everything is ok, then Congratulations you have compiled your first kernel successfully!

11 ) If anything went wrong (I don't know a reason for which it would) you could switch back to your previous kernel: while your computer is booting press "ESC" repeatedly while your computer is booting until GRUB menu appears and you can choose kernel 2.6.12 again (using your keyboard arrows). Once you enter Ubuntu type these commands in order to uninstall the new kernel (remember to put the name of the kernel you have created)

follow this example and put the name of the kernel you have created instead of “custom”

sudo dpkg -r kernel-image-2.6.12-custom

sudo dpkg -r kernel-headers-2.6.12-custom

(in my case, sudo dpkg -r kernel-image-2.6.12-alberto)

NOTE you DON'T have to type the full name of the file .deb which you created

e.g. put “kernel-image-2.6.12-custom” instead of “kernel-image-2.6.12-custom_10.00.Custom_i386.deb”

And restart your computer.

Enjoy!

Alberto

--------------------------------------------------------------------------

NOTE: HOWTO compile from a vanilla kernel from kernel.org

If you want to compile from a vanilla kernel from kernel.org something need to be changed in my guide:

Skip Point 2
You have to download it from www.kernel.org (try the latest stable kernel source)

When you get to Point 3 of the guide and you get to the following lines you have to modify them in this way:

cd /home/your_username_folder/directory_where_you_put_the_downloaded_kernel (instead of cd /usr/src) (e.g. "cd /home/alberto/download" in my case)
sudo tar --bzip2 -xvf linux-source-2.6.12.tar.bz2 /usr/src (use the name of the file you downloaded)
sudo ln -s /usr/src/linux-source-2.6.12 /usr/src/linux (use the name of the file you downloaded)
cd /usr/src/linux

OPTIONAL PATCH (if you don't need it you can continue with the instructions of Point 3)

At this point if you want to patch your vanilla kernel you have to:

1)Download the patch (I recommend you Kolivas' patches: go to http://ck.kolivas.org/patches/2.6/ and choose the folder with the name which matches your kernel version (e.g. if you are going to compile "kernel 2.6.14" get to http://ck.kolivas.org/patches/2.6/2.6.14/). You will see other folders with different versions of the patch: I suggest you to select the latest version (2.6.14-ck3 in this case). Then you have to choose the file "patch-2.6.14-ck3.bz2" if you have a desktop computer (or laptop) or "patch-2.6.14-cks3.bz2" if you have a server.

NOTE about KOLIVAS patch: if you want to use Kolivas patches you have to download the 1st stable version of a series of kernels and apply the latest patch to it. I'd better explain it with an example: if you are interested in 2.6.14.x series you have to download the source of 2.6.14 (NOT of 2.6.14.4 or 2.6.14.3, etc.) and to apply the latest Kolivas patch (as it will include the patches which make the difference between e.g. version 2.6.14 and 2.6.14.4)

2)cd /usr/src/linux

3)sudo bzcat /home/your_user_name/folder_in_which_you_downloaded_the_file/patch-2.6.14-ck3.bz2 | patch -p1
(put the name of the file you have downloaded instead of the word I have put in red)

And in Point 4 (this is the 1st thing to do at the beginning of point 4):

Get to "File Systems".

Select your filesystem (ext3, reiserfs, etc.) with the cursor.( ext3 is the filesystem used by Ubuntu by default, so if you chose automatic partitioning when you installed Ubuntu Hoary then "ext3" is definitely your filesystem)

Then press the spacebar on the desired filesystem (a "*" will appear beside it). (Make sure there's a "*" beside it instead of a "M". In this way the support for you filesystem will be built directly in the kernel instead of being built as a module and you will not get a "kernel panic")

For example:
select "ext3 journalling filesystem support" and press the spacebar (a "*" will appear beside it).

Press the right arrow and select exit.

Then you can go on with the instructions of Point 4.

If you want to compile a kernel 2.6.13 or higher you have to skip Point 6.

The rest of the HOWTO is ok.

--------------------------------------------------------------------------

NVIDIA LEGACY CARDS

Below are the legacy GPUs that are no longer supported in the unified driver.
These GPUs will continue to be maintained through the special legacy NVIDIA
GPU driver releases.

NVIDIA chip name Device PCI ID
------------------------------- -------------------------------
RIVA TNT 0x0020
RIVA TNT2/TNT2 Pro 0x0028
RIVA TNT2 Ultra 0x0029
Vanta/Vanta LT 0x002C
RIVA TNT2 Model 64/Model 64 Pro 0x002D
Aladdin TNT2 0x00A0
GeForce 256 0x0100
GeForce DDR 0x0101
Quadro 0x0103
GeForce2 GTS/GeForce2 Pro 0x0150
GeForce2 Ti 0x0151
GeForce2 Ultra 0x0152
Quadro2 Pro 0x0153

IronWolve
November 4th, 2005, 04:59 AM
I tell you, this is horrible. It either locks the system, or says "no screen"...

Why is it so damn hard to get a nvidia 7800 to work in ubuntu... (Dell 9100, dual core 2.8ghz, 1920x1200 native lcd resolution)... I dont even need acceleration, just native resolution, but vesa wont support that.

(nv driver locks system too)

Any ideas? :confused:

tseliot
November 4th, 2005, 05:54 AM
I tell you, this is horrible. It either locks the system, or says "no screen"...

Why is it so damn hard to get a nvidia 7800 to work in ubuntu... (Dell 9100, dual core 2.8ghz, 1920x1200 native lcd resolution)... I dont even need acceleration, just native resolution, but vesa wont support that.

(nv driver locks system too)

Any ideas? :confused:
You should use nvidia driver 7676, I think the problem is the "nv" (the open source driver) in xorg, which perhaps doesn't support your graphic card yet. The nv driver was buggy for one of my cards (GeForce 6200 TC PCI-E).

If you have compiled the modules using this guide you are trying to use driver 7667. It probably won't work for you.

1) Set the driver to vesa (it doesn't matter if it doesn't support the resolution you need, it's only a way to use the graphical interface)

2) Try my guide (HOWTO: Latest NVIDIA drivers) (use method2) and use drivers 7676 (FOLLOW EVERY STEP)

3) Post any kind of problems you have in this other thread of mine: http://www.ubuntuforums.org/showthread.php?t=75074

phanboy_iv
November 7th, 2005, 12:36 PM
Um...I'm trying to install a 2.6.14 from kernel.org.
Everything works until I get to step #7. When I type "sudo make-kpkg clean",

I get

sudo: make-kpkg: command not found

This is probably a simple problem:That's why it's so annoying that I don't know how to fix it.
I installed all the packages that this guide listed, and followed it closely.
I probably shouldn't even be doing kernel compilation if I can't solve this problem myself.

Oh, well, I don't care. This is interesting. I'm gonna do it. Asking people for help and experimenting is the
only way to learn.

Help would be appreciated.

slimb
November 7th, 2005, 01:27 PM
Um...I'm trying to install a 2.6.14 from kernel.org.
Everything works until I get to step #7. When I type "sudo make-kpkg clean",


make kpkg is part of "kernel-package" installed in the early steps. you may want to make sure you have that installed properly (do another apt-get install kernel-package) and you should be set.

phanboy_iv
November 7th, 2005, 02:05 PM
make kpkg is part of "kernel-package" installed in the early steps. you may want to make sure you have that installed properly (do another apt-get install kernel-package) and you should be set.

I KNEW it was something simple I shoulda known.
Thanks much.
Now, let's try this again......

eraclito
November 7th, 2005, 02:21 PM
Now you are back to the command line, type:

6) su
CC=gcc-3.4
export CC
exit
CC=gcc-3.4
export CC


what is this?
i never did it, and i wonder what it does...

and what about Kolivas' patches? on the url you gave there no info...

eraclito

tseliot
November 7th, 2005, 05:47 PM
what is this?
i never did it, and i wonder what it does...

and what about Kolivas' patches? on the url you gave there no info...

eraclito
Sometimes exporting the compiler you want to use (gcc-3.4 or 4.0) doesn't work if you do it with the "sudo" command. For this reasons you will use "su" according to the steps described above (it won't damage or modify your system in any way).

About Kolivas' patches: get to the folder with a name which matches your kernel version (e.g. if you are going to compile "kernel 2.6.14" get to http://ck.kolivas.org/patches/2.6/2.6.14/). You will see other folders with different versions of the patch: I suggest you to select the latest version (2.6.14-ck3 in this case). Then you have to choose the file "patch-2.6.14-ck3.bz2" if you have a desktop computer (or laptop) or "patch-2.6.14-cks3.bz2" if you have a server.

Ok, I will add this to the guide, thanks for the feedback.

eraclito
November 7th, 2005, 06:33 PM
About Kolivas' patches: get to the folder with a name which matches your kernel version (e.g. if you are going to compile "kernel 2.6.14" get to http://ck.kolivas.org/patches/2.6/2.6.14/). You will see other folders with different versions of the patch: I suggest you to select the latest version (2.6.14-ck3 in this case). Then you have to choose the file "patch-2.6.14-ck3.bz2" if you have a desktop computer (or laptop) or "patch-2.6.14-cks3.bz2" if you have a server.


thanks, but i was asking what the patches can do, why i have to use them (sorry but i want undertend what i do, to improve my linux knowledge...)

eraclito

Drifter
November 8th, 2005, 04:30 AM
tseliot, when I get to step 8 and type: sudo make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers modules_image
I get these errors:kernel/sched.c:1231: error: redefinition of ‘cache_delay’
kernel/sched.c:1211: error: previous definition of ‘cache_delay’ was here
kernel/sched.c:1238: error: redefinition of ‘preempt’
kernel/sched.c:1218: error: previous definition of ‘preempt’ was here
{standard input}: Assembler messages:
{standard input}:524: Error: symbol `cache_delay' is already defined
make[2]: *** [kernel/sched.o] Error 1
make[1]: *** [kernel] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.14cK1'
make: *** [stamp-build] Error 2

what am I doing wrong I can never get past this step.

tseliot
November 8th, 2005, 11:07 AM
thanks, but i was asking what the patches can do, why i have to use them (sorry but i want undertend what i do, to improve my linux knowledge...)

eraclito
You can have a look at Kolivas' webpage: http://members.optusnet.com.au/ckolivas/kernel/

tseliot
November 8th, 2005, 11:11 AM
tseliot, when I get to step 8 and type: sudo make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers modules_image
I get these errors:kernel/sched.c:1231: error: redefinition of ‘cache_delay’
kernel/sched.c:1211: error: previous definition of ‘cache_delay’ was here
kernel/sched.c:1238: error: redefinition of ‘preempt’
kernel/sched.c:1218: error: previous definition of ‘preempt’ was here
{standard input}: Assembler messages:
{standard input}:524: Error: symbol `cache_delay' is already defined
make[2]: *** [kernel/sched.o] Error 1
make[1]: *** [kernel] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.14cK1'
make: *** [stamp-build] Error 2

what am I doing wrong I can never get past this step.

I haven't tried all the patches Kolivas has made (and I'm terribly busy right now) but I ask you to delete the directory (type sudo rm /usr/src/linux-2.6.14cK1) and try another patch (ck3) because it might work better. I will test it myself as soon as I have some free time (I have complete my thesis during this week)

Drifter
November 8th, 2005, 03:45 PM
I haven't tried all the patches Kolivas has made (and I'm terribly busy right now) but I ask you to delete the directory (type sudo rm /usr/src/linux-2.6.14cK1) and try another patch (ck3) because it might work better. I will test it myself as soon as I have some free time (I have complete my thesis during this week)

It tells me no such file or directory when I type sudo rm /usr/src/linux-2.6.14ck1
sorry to bother u just let me know when u have time and thanks.

tseliot
November 8th, 2005, 04:23 PM
It tells me no such file or directory when I type sudo rm /usr/src/linux-2.6.14ck1
sorry to bother u just let me know when u have time and thanks.

Forgive me, my mind is a mess in these days. The right command is:

sudo rm -r /usr/src/linux-2.6.14ck1

Drifter
November 8th, 2005, 08:53 PM
Forgive me, my mind is a mess in these days. The right command is:

sudo rm -r /usr/src/linux-2.6.14ck1

It now says this:

rm: cannot remove `/usr/src/linux-2.6.14ck1': No such file or directory

i3dmaster
November 8th, 2005, 11:44 PM
Great Howto, thanks very much!

joysarba
November 9th, 2005, 09:50 AM
Hi tseliot,

I tried the steps but something seems to have gone awry
> uname -r
2.6.12-9-386
> sudo apt-get install linux-tree
Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package linux-tree

I got the same error for
> sudo apt-get install kernel-package
> sudo apt-get install gcc-3.4
> sudo apt-get install libncurses5-dev

Have been at it for the last couple of hours but no luck....

tseliot
November 9th, 2005, 10:53 AM
Hi tseliot,

I tried the steps but something seems to have gone awry
> uname -r
2.6.12-9-386
> sudo apt-get install linux-tree
Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package linux-tree

I got the same error for
> sudo apt-get install kernel-package
> sudo apt-get install gcc-3.4
> sudo apt-get install libncurses5-dev

Have been at it for the last couple of hours but no luck....

Please post your /etc/apt/sources.list (copy and paste it here)

joysarba
November 9th, 2005, 12:40 PM
Please post your /etc/apt/sources.list (copy and paste it here)
Thanks for pointing me in the right direction tseliot. I added a couple of new repositories and it worked. Thanks!

Drifter
November 9th, 2005, 09:26 PM
How do u enable all repositories, or how do u know if you have them enabled

tseliot
November 10th, 2005, 08:01 AM
How do u enable all repositories, or how do u know if you have them enabled
There are two ways to do that:

1) This is the method which is described in The Unofficial Ubuntu starter guide (choose the following menus: System/help/Ubuntu 5.10 starter guide)

This is the graphical method

3. How do I add Universe and Multiverse?

By default, Ubuntu comes pre-configured with basic and security update repositories. To enable the extra Universe and Multiverse repositories:

1. Start Synaptic by selecting System → Administration → Synaptic Package Manager from the desktop menu system.
2. In Synaptic choose Settings-> Repositories.
3. Click the Settings button.
4. Tick Show disabled software sources, then click Close.
5. On the Repositories dialog box click Add. There are three separate repositories; Breezy Badger, Security Updates and Updates. Select each repository and check Officially supported, Restricted copyright, Community maintained (Universe) and Non-free (Multiverse). Ensure you click OK between each repository to save your changes.
6. You should now see checkboxes next to each repository, scroll through the list and ensure they are all checked.

4. How do I add backports?

Backports are newer versions of applications made available for the current stable release of Ubuntu.

1. Start Synaptic by selecting System → Administration → Synaptic Package Manager from the desktop menu system.
2. In Synaptic choose Settings-> Repositories.
3. Click on Add and then Custom.
4. Paste the following line into the box:

deb http://archive.ubuntu.com/ubuntu breezy-backports main universe multiverse restricted

5. Click Ok and then click Yes when it asks you to reload. Backports is now available.

2) I do it in the following way (This is the textual mode):

type:

sudo gedit /etc/apt/sources.list (or sudo nano /etc/apt/sources.list)

remove the "##" before any line which begins with "deb http" or "deb-src"

e.g.

Before the operation
##deb http://archive.ubuntu.com/ubuntu breezy-updates main restricted
##deb-src http://archive.ubuntu.com/ubuntu breezy-updates main restricted

after the operation

deb http://archive.ubuntu.com/ubuntu breezy-updates main restricted
deb-src http://archive.ubuntu.com/ubuntu breezy-updates main restricted


Then save the file and exit.

Open Synaptic/Kynaptic and press the Reload button

nostracosa
November 14th, 2005, 09:04 PM
can u check why is this happening please? Ty in advance..

----@----:/usr/src$ sudo make-kpkg clean
We do not seem to be in a top level linux kernel source directory
tree. Since we are trying to make a kernel package, that does not make
sense. Please change directory to a top level linux kernel source
directory, and try again. (If I am wrong, and this is indeed a top
level linux kernel source directory, then I have gotten sadly out of
date with current kernels, and you should upgrade kernel-package)

This happens even if i introduce the "sudo make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers modules_image" command

" top level linux kernel source directory"?

If u could give me a solution it would be great _o_

MichaelM
November 14th, 2005, 09:15 PM
Try issuing the command from /usr/src/linux .

nostracosa
November 14th, 2005, 09:18 PM
ty i've tried to assume it from /usr/src/linux-source-2.6.10 and it worked ;)!

it's compiling now!

ty for the help!

Tseliot, ty for the tutorials.

mdr
November 14th, 2005, 10:38 PM
Great Howto, thanks very much!

seconded by me

nostracosa
November 15th, 2005, 06:41 PM
Can i remove the kernel that was there before i have installed the compiled one?

ty in advance

phanboy_iv
November 15th, 2005, 08:32 PM
I don't think so and I wouldn't. Keep the old kernel there just in case. You can remove it afterwards
if you must.

nrwilk
November 15th, 2005, 08:46 PM
I want to recompile my kernal in order to get hibernate functionality. How would I go about including that in the compile?

When I run the hibernate command in the terminal, I get the following:

Your kernel does not have any recent Software Suspend 2 support compiled in.
Please follow the HOWTO linked from http://softwaresuspend.berlios.de/ for
instructions on how to compile Software Suspend into your kernel.
hibernate: Aborting.


I just want to be able to leave it on at night, but it's too loud as is. I also want to get more aquainted with kernel compilation anyway.

I'd also like to be able to mount and use my iPod via firewire on the linux box. Any tips to get this supported in a kernel I'd compile?

EDIT: I found what looks to be a very detailed how-to on this subject here

http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html

Does this one apply to the kernel source that would download from our repositories?

beijingjj
November 16th, 2005, 03:01 AM
I've had this happen with just about any distro I've ever used, including Ubuntu which I'm using now.

Out of the box install everything works. Then I install the latest kernel and strange things start happening, for example:

1. I have to manually load the modules for my wireless card (ipw2200).
2. Either I put "psmouse.proto=imps" as a kernel boot option and my touchpad works but my trackpoint doesn't, or I don't put that option and the trackpoint works but some of the features of the touchpad don't work.
3. Touchpad scrollings no longer works.

All of the scripts and config files are the same, all I've done is update the kernel, so I would like to understand where these differences come from. In this particular case I've even added my wireless card module to /etc/modules but still have to manually load it for it to work.

Although I am happy to find work-arounds to get these things working again I'd really like to understand why this is happening.

Thanks in advance!

Locutus
November 16th, 2005, 05:20 AM
Thanks for a really excellent HOWTO. This was something which has scared me for over 4 years. I can now say that I have successfully compiled my own kernel. Everything works great! My system even feels a little faster, but maybe I am just imagining it. Thanks again!

Kind Regards,

Locutus

tseliot
November 16th, 2005, 08:28 AM
Can i remove the kernel that was there before i have installed the compiled one?

ty in advance
Yes you can but I suggest you NOT to do it.

The graphical way:

Open Synaptic and put "kernel" in the search field.

Find your kernel and mark it for complete removal

Then click Apply

OR

The command line way:

sudo dpkg -r name_of_the_kernel (without the .deb extension)

tseliot
November 16th, 2005, 08:41 AM
I want to recompile my kernal in order to get hibernate functionality. How would I go about including that in the compile?

When I run the hibernate command in the terminal, I get the following:

Your kernel does not have any recent Software Suspend 2 support compiled in.
Please follow the HOWTO linked from http://softwaresuspend.berlios.de/ for
instructions on how to compile Software Suspend into your kernel.
hibernate: Aborting.


If you need software suspend you have to follow the part of my guide which is about compiling Vanilla kernels. (i.e. You have to patch a vanilla kernel)

You should go to http://softwaresuspend.berlios.de/ and download a kernel patch according to the version of the vanilla kernel you have downloaded.

Then follow the guide in order to know how to patch the kernel and then how to compile it again.

Before you start do this:

sudo rm /usr/src/linux



I'd also like to be able to mount and use my iPod via firewire on the linux box. Any tips to get this supported in a kernel I'd compile?

I have never used a firewire peripheral so I'm afraid I can't help you. I think you should ask in the hardware support section of the forum.

EDIT: I found what looks to be a very detailed how-to on this subject here

http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html

Does this one apply to the kernel source that would download from our repositories?

This is just an explanation of kernel compilation in general

tseliot
November 16th, 2005, 09:45 AM
I've had this happen with just about any distro I've ever used, including Ubuntu which I'm using now.

Out of the box install everything works. Then I install the latest kernel and strange things start happening, for example:

1. I have to manually load the modules for my wireless card (ipw2200).
2. Either I put "psmouse.proto=imps" as a kernel boot option and my touchpad works but my trackpoint doesn't, or I don't put that option and the trackpoint works but some of the features of the touchpad don't work.
3. Touchpad scrollings no longer works.

All of the scripts and config files are the same, all I've done is update the kernel, so I would like to understand where these differences come from. In this particular case I've even added my wireless card module to /etc/modules but still have to manually load it for it to work.

Although I am happy to find work-arounds to get these things working again I'd really like to understand why this is happening.

Thanks in advance!

The main reason of your problem with the wireless card is that when you compile a kernel you don't build the "restricted modules" which are required by you particular hardware. On the contrary the kernels you can find in synaptic also have these "restricted modules" available for download.

This means that you need to build the modules for your hardware together with you kernel.

As I've written in the guide you have to extract the source code of the drivers you need under /usr/src (every compressed file will create its own folder in there)

Then just follow the guide and look at the part about the optional modules.

About the source codes:
For ipw2200 go tohttp://packages.debian.org/cgi-bin/download.pl?arch=all&file=pool%2Fcontrib%2Fi%2Fipw2200%2Fipw2200-source_1.0.8-1_all.deb&md5sum=f63ad19892465e9767f0895849d863a4&arch=all&type=main

About your touchpad: I fear it's a kernel bug. Have a look at the following page:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112473

nrwilk
November 16th, 2005, 02:47 PM
If you need software suspend you have to follow the part of my guide which is about compiling Vanilla kernels. (i.e. You have to patch a vanilla kernel)

You should go to http://softwaresuspend.berlios.de/ and download a kernel patch according to the version of the vanilla kernel you have downloaded.
Does this mean that I'll be missing the modules that you are referring to in the post after your reply to me? Can I download them from adept/synaptic and use them with a vanilla kernel?

It seems that the compilation requires the user to figure out and gather a lot of options and modules that would have to be compiled into the new kernel. If I seem over-hesitant, I'm sorry. How can I find out about things that I have the option of compiling into my kernel? What if I find something I missed? Go through the process again? Are there any neccessary modules I'd need to get the vanilla kernal to work fully with (K)ubuntu?

tseliot
November 16th, 2005, 03:00 PM
Does this mean that I'll be missing the modules that you are referring to in the post after your reply to me? Can I download them from adept/synaptic and use them with a vanilla kernel?

It seems that the compilation requires the user to figure out and gather a lot of options and modules that would have to be compiled into the new kernel. If I seem over-hesitant, I'm sorry. How can I find out about things that I have the option of compiling into my kernel? What if I find something I missed? Go through the process again? Are there any neccessary modules I'd need to get the vanilla kernal to work fully with (K)ubuntu?

1) You have to download the patch from that website (it's not available in the Ubuntu's repositories) and to apply it as explained in my guide. For example if you want to compile a vanilla kernel 2.6.14 you have to use the following patch http://www.suspend2.net/downloads/all/suspend2-2.2-rc11-for-2.6.14.tar.bz2

2) If you want to see the peripherals you are using with your current kernel version you have to type:

lspci

(you can post the output here if you wish by copying and pasting it here)

In this way we can know what you need to be compiled in your next kernel (and which currently works with your current kernel)

3) You shouldn't worry about the rest. In my guide I suggest to use the command "sudo make oldconfig" which makes you use the configuration of your current kernel in the new one.

nrwilk
November 16th, 2005, 04:41 PM
Thanks so much for your tips and help, tseliot. Both directly to me here, and also via your how-tos, which I know to be of immense help to many people here. I also used your proprietary nvidia installation howto, and it made the installation a breeze (heh).

I always feel like I'm asking for too much help with these kind of questions, but I guess that's what this forum is for, right?

Here's my ouput from lspci:
0000:00:00.0 Memory controller: nVidia Corporation: Unknown device 005e (rev a3)
0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 0050 (rev a3)
0000:00:01.1 SMBus: nVidia Corporation: Unknown device 0052 (rev a2)
0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 005a (rev a2)
0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 005b (rev a3)
0000:00:04.0 Multimedia audio controller: nVidia Corporation: Unknown device 0059 (rev a2)
0000:00:06.0 IDE interface: nVidia Corporation: Unknown device 0053 (rev a2)
0000:00:07.0 IDE interface: nVidia Corporation: Unknown device 0054 (rev a3)
0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 0055 (rev a3)
0000:00:09.0 PCI bridge: nVidia Corporation: Unknown device 005c (rev a2)
0000:00:0a.0 Bridge: nVidia Corporation: Unknown device 0057 (rev a3)
0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:0c.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:0d.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:0e.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:01:06.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
0000:01:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
0000:05:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0141 (rev a2)


Does the lspci command also list ports and services that are not being used at the time the command is issued? For example, I have no firewire devices connected right now, but I know that they work (except for the iPod). My external firewire harddrive works.


Also, what version kernel source should I download from kernel.org?
The site says this:
The latest stable version of the Linux kernel is: 2.6.14.2
should I go for the latest?

Again, thanks so much for all the help!

tseliot
November 16th, 2005, 04:50 PM
Thanks so much for your tips and help, tseliot. Both directly to me here, and also via your how-tos, which I know to be of immense help to many people here. I also used your proprietary nvidia installation howto, and it made the installation a breeze (heh).

I always feel like I'm asking for too much help with these kind of questions, but I guess that's what this forum is for, right?

Here's my ouput from lspci:
0000:00:00.0 Memory controller: nVidia Corporation: Unknown device 005e (rev a3)
0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 0050 (rev a3)
0000:00:01.1 SMBus: nVidia Corporation: Unknown device 0052 (rev a2)
0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 005a (rev a2)
0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 005b (rev a3)
0000:00:04.0 Multimedia audio controller: nVidia Corporation: Unknown device 0059 (rev a2)
0000:00:06.0 IDE interface: nVidia Corporation: Unknown device 0053 (rev a2)
0000:00:07.0 IDE interface: nVidia Corporation: Unknown device 0054 (rev a3)
0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 0055 (rev a3)
0000:00:09.0 PCI bridge: nVidia Corporation: Unknown device 005c (rev a2)
0000:00:0a.0 Bridge: nVidia Corporation: Unknown device 0057 (rev a3)
0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:0c.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:0d.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:0e.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:01:06.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
0000:01:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
0000:05:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0141 (rev a2)


What version kernel source should I download from kernel.org?
The site says this:

should I go for the latest?

Again, thanks so much for all the help!

Well it looks like you don't need any other module.

And yes, the latest (stable) kernel version (2.6.14.2) is fine.

Good luck!

MemoryDump
November 17th, 2005, 05:14 PM
1 question so far.. should DMA is be set to active? I have a 160GIG SATA drive and 2 IDE dvd-rom/burners as well.

thxs
-MD

tseliot
November 17th, 2005, 05:19 PM
1 question so far.. should DMA is be set to active? I have a 160GIG SATA drive and 2 IDE dvd-rom/burners as well.

thxs
-MD
Usually only old peripherals don't support DMA. Don't you worry, I think you can enable it in the kernel. However you had better not uninstall your old kernel in case anything goes wrong (in general not because of DMA)

MemoryDump
November 17th, 2005, 05:29 PM
doh! I guess I'll have to recompile again and enable it!
Once I've compiled once do I have re-compile everything again? Is there a faster way to speed this up somehow? (again once I've compile fully at least once)

thxs for the quick reply
-MD

my lspci output.. I guess I could tweak my kernel a little more then?
0000:00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
0000:00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller (rev 02)
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02)
0000:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02)
0000:00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R350 [Radeon 9800 Pro]
0000:01:00.1 Display controller: ATI Technologies Inc Radeon R350 [Radeon 9800 Pro] (Secondary)
0000:02:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
0000:02:05.0 Ethernet controller: 3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12)
0000:02:09.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
0000:02:09.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 04)
0000:02:09.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
0000:02:0c.0 Communication controller: Conexant HSF 56k HSFi Modem (rev 01)

dubz
November 17th, 2005, 07:04 PM
hi,

According to my knowledge of kernel compilation, you cannot take any shortcuts as you will emerge with half a kernel!!! ... bad idea .

As for your output.... smaller kernel = faster kernels with better performance and faster boot time.

i might be wrong,but that is why forums exist.

thanks.

tseliot
November 18th, 2005, 06:52 AM
doh! I guess I'll have to recompile again and enable it!
Once I've compiled once do I have re-compile everything again? Is there a faster way to speed this up somehow? (again once I've compile fully at least once)

thxs for the quick reply
-MD

my lspci output.. I guess I could tweak my kernel a little more then?

Yes, you have to compile it again.

If you want to tweak it a bit you should look for the modules which are used for each of your peripherals and disable the support for the peripherals you don't own.

e.g. you have a "Host bridge: Intel Corp. 82865G/PE/P DRAM Controller"

go under "Device drivers"/"ATA/ATAPI/MFM/RLL SUPPORT"/

You will need the "Intel PIIXn chipsets support" enabled. You can disable the modules belonging to other brands (e.g. ATI, Compaq, etc.). DO NOT disalble generic modules, do it only for the modules you can clearly recognise as NOT relevant to your chipset.

You should do tha same for your other peripherals. It will be a good exercise for you.:)

Diod
November 18th, 2005, 03:55 PM
The kernel compiled great, but these are two problems i MUST solve.
When it tries activating the sound system, it says /dev/dsp not found. And also 2 of the 3 drives do NOT mount.
One is SATA and the other is ATA, the one that does mount is ATA.
The kernel im trying to get working correctly is 2.6.14.2

When i dl the alsa driver package and try installing it it says this:

checking for input subsystem in kernel... yes
checking for directory to store kernel modules... /lib/modules/2.6.14.2-custom/kernel/sound
checking for verbose printk... on
checking for debug level... none
checking for ISA support in kernel... "yes"
checking for processor type... k7
checking for i386 machine type... default
checking for ISA DMA API... "yes"
checking for SMP... "no"
checking for Video device support in kernel... "yes"
checking for ISA PnP driver in kernel... yes
checking for PnP driver in kernel... yes
checking for Kernel ISA-PnP support... "yes"
checking for strlcpy... "yes"
checking for snprintf... "yes"
checking for vsnprintf... "yes"
checking for scnprintf... "yes"
checking for sscanf... "yes"
checking for vmalloc_to_page... "yes"
checking for old kmod... "no"
checking for PDE... "yes"
checking for pci_set_consistent_dma_mask... "yes"
checking for pci_dev_present... "yes"
checking for msleep... "yes"
checking for msleep_interrupt... "yes"
checking for msecs_to_jiffies... "yes"
checking for tty->count is the atomic type... "no"
checking for video_get_drvdata... "yes"
checking for io_remap_pfn_range... "yes"
checking for kcalloc... "yes"
checking for kstrdup... "yes"
checking for kzalloc... "yes"
checking for create_workqueue with flags... "no"
checking for saved_config_space in pci_dev... "yes"
checking for new pci_save_state... "yes"
checking for register_sound_special_device... "yes"
checking for driver version... 1.0.10
checking for sequencer support... yes
checking for OSS/Free emulation... yes
checking for RTC callback support in kernel... may be buggy, skipped
checking for HPET support... "yes"
checking for Procfs support... "yes"
checking for USB support... "yes"
checking for class_simple... "no"
checking for old driver suspend/resume callbacks... "yes"
checking for removal of page-reservation for nopage/mmap... "no"
checking for nested class_device... "no"
checking for new unlocked/compat_ioctl... "yes"
checking for PC-Speaker hook... "no"
checking for kernel PCMCIA
checking for PCMCIA support... "yes"
checking for PC9800 support in kernel... "no"
checking for parallel port support... "yes"
checking for which soundcards to compile driver for... intel8x0
configure: creating ./config.status
config.status: creating version
config.status: creating Makefile.conf
config.status: creating snddevices
config.status: creating utils/alsa-driver.spec
config.status: creating utils/buildrpm
config.status: creating toplevel.config
config.status: creating utils/alsasound
config.status: creating utils/alsasound.posix
config.status: creating include/pci_ids_compat.h
config.status: creating include/config.h
config.status: include/config.h is unchanged
config.status: creating include/config1.h
config.status: include/config1.h is unchanged
config.status: creating include/version.h
config.status: include/version.h is unchanged
config.status: creating include/autoconf-extra.h
config.status: include/autoconf-extra.h is unchanged
Hacking autoconf.h...
make dep
make[1]: Entering directory `/home/diod/alsa-driver-1.0.10'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/acore'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/acore/ioctl32'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore/ioctl32'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/acore/oss'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore/oss'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/acore/seq'
make[4]: Entering directory `/home/diod/alsa-driver-1.0.10/acore/seq/instr'
make[4]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore/seq/instr'
make[4]: Entering directory `/home/diod/alsa-driver-1.0.10/acore/seq/oss'
make[4]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore/seq/oss'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore/seq'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/i2c'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/i2c/other'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/i2c/other'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/i2c'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers/mpu401'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers/mpu401'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers/opl3'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers/opl3'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers/opl4'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers/opl4'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers/pcsp'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers/pcsp'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers/vx'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers/vx'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/isa'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/ad1816a'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/ad1816a'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/ad1848'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/ad1848'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/cs423x'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/cs423x'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/es1688'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/es1688'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/gus'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/gus'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/msnd'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/msnd'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/opti9xx'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/opti9xx'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/sb'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/sb'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/wavefront'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/wavefront'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/synth'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/synth/emux'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/synth/emux'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/synth'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/ac97'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/ac97'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/ali5451'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/ali5451'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/asihpi'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/asihpi'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/au88x0'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/au88x0'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/ca0106'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/ca0106'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/cs46xx'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/cs46xx'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/echoaudio'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/echoaudio'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/emu10k1'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/emu10k1'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/hda'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/hda'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/ice1712'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/ice1712'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/korg1212'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/korg1212'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/mixart'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/mixart'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/nm256'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/nm256'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/pcxhr'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/pcxhr'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/pdplus'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/pdplus'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/riptide'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/riptide'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/rme9652'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/rme9652'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/trident'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/trident'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/vx222'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/vx222'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/ymfpci'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/ymfpci'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/usb'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/usb/usx2y'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/usb/usx2y'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/usb'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pcmcia'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pcmcia/pdaudiocf'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pcmcia/pdaudiocf'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/pcmcia/vx'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/pcmcia/vx'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pcmcia'
make[1]: Leaving directory `/home/diod/alsa-driver-1.0.10'
make -C /lib/modules/2.6.14.2-custom/source SUBDIRS=/home/diod/alsa-driver-1.0.10 O=/lib/modules/2.6.14.2-custom/build modules
make[1]: Entering directory `/usr/src/linux-2.6.14.2'
CC [M] /home/diod/alsa-driver-1.0.10/acore/memalloc.o
CC [M] /home/diod/alsa-driver-1.0.10/acore/sound.o
CC [M] /home/diod/alsa-driver-1.0.10/acore/init.o
LD [M] /home/diod/alsa-driver-1.0.10/acore/snd.o
LD [M] /home/diod/alsa-driver-1.0.10/acore/snd-timer.o
LD [M] /home/diod/alsa-driver-1.0.10/acore/snd-pcm.o
LD [M] /home/diod/alsa-driver-1.0.10/acore/snd-page-alloc.o
CC [M] /home/diod/alsa-driver-1.0.10/pci/intel8x0.o
LD [M] /home/diod/alsa-driver-1.0.10/pci/snd-intel8x0.o
CC [M] /home/diod/alsa-driver-1.0.10/pci/ac97/ac97_codec.o
LD [M] /home/diod/alsa-driver-1.0.10/pci/ac97/snd-ac97-bus.o
LD [M] /home/diod/alsa-driver-1.0.10/pci/ac97/snd-ac97-codec.o
Building modules, stage 2.
MODPOST
LD [M] /home/diod/alsa-driver-1.0.10/acore/snd-page-alloc.ko
LD [M] /home/diod/alsa-driver-1.0.10/acore/snd-pcm.ko
LD [M] /home/diod/alsa-driver-1.0.10/acore/snd-timer.ko
LD [M] /home/diod/alsa-driver-1.0.10/acore/snd.ko
LD [M] /home/diod/alsa-driver-1.0.10/pci/ac97/snd-ac97-bus.ko
LD [M] /home/diod/alsa-driver-1.0.10/pci/ac97/snd-ac97-codec.ko
LD [M] /home/diod/alsa-driver-1.0.10/pci/snd-intel8x0.ko
make[1]: Leaving directory `/usr/src/linux-2.6.14.2'
utils/link-modules /home/diod/alsa-driver-1.0.10

ALSA modules were successfully compiled.

find /lib/modules/2.6.14.2-custom/kernel/sound -name 'snd*.*o' | xargs rm -f
make[1]: Entering directory `/home/diod/alsa-driver-1.0.10/acore'
mkdir -p /lib/modules/2.6.14.2-custom/kernel/sound/acore
cp snd-page-alloc.ko snd-pcm.ko snd-timer.ko snd.ko /lib/modules/2.6.14.2-custom/kernel/sound/acore
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/acore/ioctl32'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore/ioctl32'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/acore/oss'
mkdir -p /lib/modules/2.6.14.2-custom/kernel/sound/acore/oss
cp snd-mixer-oss.ko snd-pcm-oss.ko /lib/modules/2.6.14.2-custom/kernel/sound/acore/oss
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore/oss'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/acore/seq'
mkdir -p /lib/modules/2.6.14.2-custom/kernel/sound/acore/seq
cp snd-seq-device.ko snd-seq-midi-event.ko snd-seq.ko /lib/modules/2.6.14.2-custom/kernel/sound/acore/seq
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/acore/seq/instr'
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore/seq/instr'
make[3]: Entering directory `/home/diod/alsa-driver-1.0.10/acore/seq/oss'
mkdir -p /lib/modules/2.6.14.2-custom/kernel/sound/acore/seq/oss
cp snd-seq-oss.ko /lib/modules/2.6.14.2-custom/kernel/sound/acore/seq/oss
make[3]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore/seq/oss'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore/seq'
make[1]: Leaving directory `/home/diod/alsa-driver-1.0.10/acore'
make[1]: Entering directory `/home/diod/alsa-driver-1.0.10/i2c'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/i2c/other'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/i2c/other'
make[1]: Leaving directory `/home/diod/alsa-driver-1.0.10/i2c'
make[1]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers/mpu401'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers/mpu401'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers/opl3'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers/opl3'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers/opl4'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers/opl4'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers/pcsp'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers/pcsp'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/drivers/vx'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers/vx'
make[1]: Leaving directory `/home/diod/alsa-driver-1.0.10/drivers'
make[1]: Entering directory `/home/diod/alsa-driver-1.0.10/isa'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/ad1816a'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/ad1816a'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/ad1848'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/ad1848'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/cs423x'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/cs423x'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/es1688'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/es1688'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/gus'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/gus'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/msnd'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/msnd'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/opti9xx'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/opti9xx'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/sb'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/sb'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/isa/wavefront'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa/wavefront'
make[1]: Leaving directory `/home/diod/alsa-driver-1.0.10/isa'
make[1]: Entering directory `/home/diod/alsa-driver-1.0.10/synth'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/synth/emux'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/synth/emux'
make[1]: Leaving directory `/home/diod/alsa-driver-1.0.10/synth'
make[1]: Entering directory `/home/diod/alsa-driver-1.0.10/pci'
mkdir -p /lib/modules/2.6.14.2-custom/kernel/sound/pci
cp snd-intel8x0.ko /lib/modules/2.6.14.2-custom/kernel/sound/pci
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/ac97'
mkdir -p /lib/modules/2.6.14.2-custom/kernel/sound/pci/ac97
cp snd-ac97-bus.ko snd-ac97-codec.ko /lib/modules/2.6.14.2-custom/kernel/sound/pci/ac97
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/ac97'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/ali5451'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/ali5451'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/asihpi'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/asihpi'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/au88x0'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/au88x0'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/ca0106'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/ca0106'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/cs46xx'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/cs46xx'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/echoaudio'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/echoaudio'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/emu10k1'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/emu10k1'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/hda'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/hda'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/ice1712'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/ice1712'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/korg1212'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/korg1212'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/mixart'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/mixart'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/nm256'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/nm256'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/pcxhr'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/pcxhr'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/pdplus'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/pdplus'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/riptide'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/riptide'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/rme9652'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/rme9652'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/trident'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/trident'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/vx222'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/vx222'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pci/ymfpci'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci/ymfpci'
make[1]: Leaving directory `/home/diod/alsa-driver-1.0.10/pci'
make[1]: Entering directory `/home/diod/alsa-driver-1.0.10/usb'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/usb/usx2y'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/usb/usx2y'
make[1]: Leaving directory `/home/diod/alsa-driver-1.0.10/usb'
make[1]: Entering directory `/home/diod/alsa-driver-1.0.10/pcmcia'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pcmcia/pdaudiocf'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pcmcia/pdaudiocf'
make[2]: Entering directory `/home/diod/alsa-driver-1.0.10/pcmcia/vx'
make[2]: Leaving directory `/home/diod/alsa-driver-1.0.10/pcmcia/vx'
make[1]: Leaving directory `/home/diod/alsa-driver-1.0.10/pcmcia'
/sbin/depmod -a 2.6.14.2-custom -F /lib/modules/2.6.14.2-custom/source/System.map
if [ -L /usr/include/sound ]; then \
rm -f /usr/include/sound; \
ln -sf /home/diod/alsa-driver-1.0.10/include/sound /usr/include/sound; \else \
rm -rf /usr/include/sound; \
install -d -m 755 -g root -o root /usr/include/sound; \
for f in include/sound/*.h; do \
install -m 644 -g root -o root $f /usr/include/sound; \
done \
fi
rm: cannot remove `/usr/include/sound': Toegang geweigerd
install: Kan de eigenaar en/of groep van `/usr/include/sound' niet veranderen: Bewerking niet toegestaan
install: cannot change permissions of `/usr/include/sound': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ac97_codec.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ad1816a.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ad1848.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ainstr_fm.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ainstr_gf1.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ainstr_iw.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ainstr_simple.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ak4114.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ak4117.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ak4531_codec.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ak4xxx-adda.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/asequencer.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/asoundef.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/asound_fm.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/asound.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/control.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/core.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/cs4231.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/cs46xx_dsp_scb_types.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/cs46xx_dsp_spos.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/cs46xx_dsp_task_types.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/cs46xx.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/cs8403.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/cs8427.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/driver.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/emu10k1.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/emu10k1_synth.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/emu8000.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/emu8000_reg.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/emux_legacy.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/emux_synth.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/es1688.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/gus.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/hdsp.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/hdspm.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/hwdep.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/i2c.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/info.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/initval.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/memalloc.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/minors.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/mixer_oss.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/mpu401.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/opl3.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/opl4.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/pcm.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/pcm-indirect.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/pcm_oss.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/pcm_params.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/rawmidi.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/sb16_csp.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/sb.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/seq_device.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/seq_instr.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/seq_kernel.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/seq_midi_emul.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/seq_midi_event.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/seq_oss.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/seq_oss_legacy.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/seq_virmidi.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/sfnt_info.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/snd_wavefront.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/soundfont.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/sscape_ioctl.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/tea575x-tuner.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/tea6330t.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/timer.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/trident.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/uda1341.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/util_mem.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/version.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/vx_core.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/wavefront_fx.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/wavefront.h': Bewerking niet toegestaan
install: cannot change ownership of `/usr/include/sound/ymfpci.h': Bewerking niet toegestaan
make: *** [install-headers] Fout 1


In my previous kernel it worked perfectly

When i do mount -a it says
mount: /dev/hdc5 al aangekoppeld of /media/backup2/ bezig
mount: /dev/hdd2 al aangekoppeld of /media/backup3/ bezig

al aangekoppeld of bezig = already mounted or busy

tseliot
November 18th, 2005, 04:45 PM
The kernel compiled great, but these are two problems i MUST solve.
When it tries activating the sound system, it says /dev/dsp not found. And also 2 of the 3 drives do NOT mount.
One is SATA and the other is ATA, the one that does mount is ATA.
The kernel im trying to get working correctly is 2.6.14.2

When i dl the alsa driver package and try installing it it says this:



In my previous kernel it worked perfectly

When i do mount -a it says


al aangekoppeld of bezig = already mounted or busy

1) Could you tell me the model of your motherboard?

2) type:
lspci

and post the output here

Diod
November 18th, 2005, 05:21 PM
I removed the kernel using the lines in the first post. But now i cant even seem to load with my normal kernel, it keeps getting stuck after checking battery status(im using a desktop so i dont even know why it checks it) when i use "failsafe mode" and startx it fails starting x.

tseliot
November 18th, 2005, 05:26 PM
I removed the kernel using the lines in the first post. But now i cant even seem to load with my normal kernel, it keeps getting stuck after checking battery status(im using a desktop so i dont even know why it checks it) when i use "failsafe mode" and startx it fails starting x.

try this in Recovery mode:

sudo nano /etc/X11/xorg.conf

Then find the section Device and make sure the word I put in red is “vesa”:

Section "Device"
Identifier "NVIDIA Corporation NV40 [GeForce 6200 TurboCache]"
Driver "vesa"
BusID "PCI:1:0:0"

CTRL+O to save (yes, use the same name and overwrite the file)
CTRL+X to exit

Then try "startx"

Diod
November 18th, 2005, 05:42 PM
ok got it to boot now.(the old kernel, damn im lucky i didnt delete it :p)
I installed the nvidia drivers from the package from nvidia.com when i was using the newer kernel. So do i just reinstall that package again, but on the older kernel?

tseliot
November 18th, 2005, 06:05 PM
ok got it to boot now.(the old kernel, damn im lucky i didnt delete it :p)
I installed the nvidia drivers from the package from nvidia.com when i was using the newer kernel. So do i just reinstall that package again, but on the older kernel?

Yes, you have to reinstall the drivers every time you change your kernel

Diod
November 18th, 2005, 06:36 PM
Yes, you have to reinstall the drivers every time you change your kernel

I have uninstalled the drivers i installed with the package i got from nvidia.com and installed the ones u can get trough apt-get.

But im still wondering how to fix everything that went wrong.
I got the sound to work because i installed the NFORCE3 drivers from nvidia.com
But i couldnt look at all my partitions. In the old kernel i can(2.6.12-9-k7).
But i still want to get a custom kernel tbh

tseliot
November 18th, 2005, 06:40 PM
I have uninstalled the drivers i installed with the package i got from nvidia.com and installed the ones u can get trough apt-get.

But im still wondering how to fix everything that went wrong.
I got the sound to work because i installed the NFORCE3 drivers from nvidia.com
But i couldnt look at all my partitions. In the old kernel i can(2.6.12-9-k7).
But i still want to get a custom kernel tbh

1) can you tell me the filesystems (ext3, reiserfs, etc.) of the harddisk you couldn't access?

2) can you post the output of "lspci"?

Diod
November 18th, 2005, 06:51 PM
lspci:

0000:00:00.0 Host bridge: nVidia Corporation: Unknown device 00e1 (rev a1)
0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 00e0 (rev a2)
0000:00:01.1 SMBus: nVidia Corporation: Unknown device 00e4 (rev a1)
0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 00e7 (rev a1)
0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 00e7 (rev a1)
0000:00:02.2 USB Controller: nVidia Corporation: Unknown device 00e8 (rev a2)
0000:00:05.0 Bridge: nVidia Corporation: Unknown device 00df (rev a2)
0000:00:06.0 Multimedia audio controller: nVidia Corporation: Unknown device 00ea (rev a1)
0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 00e5 (rev a2)
0000:00:09.0 IDE interface: nVidia Corporation: Unknown device 00ee (rev a2)
0000:00:0a.0 IDE interface: nVidia Corporation: Unknown device 00e3 (rev a2)
0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 00e2 (rev a2)
0000:00:0e.0 PCI bridge: nVidia Corporation: Unknown device 00ed (rev a2)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0045 (rev a1)
0000:02:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
0000:02:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)


Im using a MSI K8N Neo2 Platinum(sry, i didnt see ur question about my mobo till now).

These where the drives i couldnt access:

NTFS(SATA)
FAT(ATA)

The one i could access was the drive with my linux partitions on (it has these partitions: 2 x ext3, swap and NTFS

I also noticed strange behaviour by amarok, it wouldnt start up at all.

nrwilk
November 18th, 2005, 09:48 PM
at the end of step 3, I'm getting the following error:
/usr/src/linux$ sudo make oldconfig
make: *** No rule to make target `oldconfig'. Stop.

I get it when I try this too:

/usr/src/linux$ sudo make menuconfig


I untarred the linux-2.6.14.2 tarball into the /usr/src directory, and I symlinked it in /usr/src/linux. I am issuing those commands from /usr/src/linux.

Any ideas?

ramba
November 19th, 2005, 05:12 AM
I have tried to compile a couple of kernels and every time I get some warnings in the process about some static this and that and integer not declared or something like that. Should I just ignore this or are kernels meant to compile clean and with no exceptions? :confused:

tseliot
November 19th, 2005, 05:13 AM
at the end of step 3, I'm getting the following error:
/usr/src/linux$ sudo make oldconfig
make: *** No rule to make target `oldconfig'. Stop.

I get it when I try this too:

/usr/src/linux$ sudo make menuconfig


I untarred the linux-2.6.14.2 tarball into the /usr/src directory, and I symlinked it in /usr/src/linux. I am issuing those commands from /usr/src/linux.

Any ideas?

Make sure you have installed each of these packages:

sudo apt-get install build-essential
sudo apt-get install kernel-package
sudo apt-get install gcc (this will install gcc-4.0 for kernel 2.6.13 or superior)
sudo apt-get install gcc-3.4
sudo apt-get install libncurses5
sudo apt-get install libncurses5-dev
sudo apt-get install libqt3-mt-dev

tseliot
November 19th, 2005, 05:14 AM
I have tried to compile a couple of kernels and every time I get some warnings in the process about some static this and that and integer not declared or something like that. Should I just ignore this or are kernels meant to compile clean and with no exceptions? :confused:

There might be some warnings nonetheless the kernel should work.

tseliot
November 19th, 2005, 05:24 AM
lspci:

0000:00:00.0 Host bridge: nVidia Corporation: Unknown device 00e1 (rev a1)
0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 00e0 (rev a2)
0000:00:01.1 SMBus: nVidia Corporation: Unknown device 00e4 (rev a1)
0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 00e7 (rev a1)
0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 00e7 (rev a1)
0000:00:02.2 USB Controller: nVidia Corporation: Unknown device 00e8 (rev a2)
0000:00:05.0 Bridge: nVidia Corporation: Unknown device 00df (rev a2)
0000:00:06.0 Multimedia audio controller: nVidia Corporation: Unknown device 00ea (rev a1)
0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 00e5 (rev a2)
0000:00:09.0 IDE interface: nVidia Corporation: Unknown device 00ee (rev a2)
0000:00:0a.0 IDE interface: nVidia Corporation: Unknown device 00e3 (rev a2)
0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 00e2 (rev a2)
0000:00:0e.0 PCI bridge: nVidia Corporation: Unknown device 00ed (rev a2)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0045 (rev a1)
0000:02:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
0000:02:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)


Im using a MSI K8N Neo2 Platinum(sry, i didnt see ur question about my mobo till now).

These where the drives i couldnt access:

NTFS(SATA)
FAT(ATA)

The one i could access was the drive with my linux partitions on (it has these partitions: 2 x ext3, swap and NTFS

I also noticed strange behaviour by amarok, it wouldnt start up at all.

Just one last thing:

1) can you post the content of your "/etc/modules"?
2) please type "lsmod" post the output

Alc0h0lic
November 19th, 2005, 06:36 AM
My laptop keeps actually turning off while compiling the kernel. I've been able to finish it (I think it continued where it left off before turning off), but I had to reboot like 10 times before it was done. Im also pretty sure it isn't some thermal issue or something like that cause I have no problems at all with my laptop turning off when doing other stuff. Also when I boot it up right away after it turns off (without letting it cool off), it runs just fine as long as I don't do any kernel compilation.

tseliot
November 19th, 2005, 06:42 AM
My laptop keeps actually turning off while compiling the kernel. I've been able to finish it (I think it continued where it left off before turning off), but I had to reboot like 10 times before it was done. Im also pretty sure it isn't some thermal issue or something like that cause I have no problems at all with my laptop turning off when doing other stuff. Also when I boot it up right away after it turns off (without letting it cool off), it runs just fine as long as I don't do any kernel compilation.

Kernel compilations use a 100% of the power of your CPU. Did you start the compilation with the power cable plugged in?

Alc0h0lic
November 19th, 2005, 06:46 AM
Kernel compilations use a 100% of the power of your CPU. Did you start the compilation with the power cable plugged in?
Yep, I wouldn't have been able to restart it those 9 times if my battery was dead :P

tseliot
November 19th, 2005, 06:52 AM
Yep, I wouldn't have been able to restart it those 9 times if my battery was dead :P

You should set your computer not to shutdown or (standby) when the power cable is plugged in.

I don't remember how to do that but I can see in my notebook.

Alc0h0lic
November 19th, 2005, 06:57 AM
You should set your computer not to shutdown or (standby) when the power cable is plugged in.

I don't remember how to do that but I can see in my notebook.
Well there's some stuff about it in the System->Screensaver menu, but I tried turning it off, and it didn't help. I also tried playing gnometris to keep my laptop busy, but it would still turn off.

tseliot
November 19th, 2005, 07:09 AM
Well there's some stuff about it in the System->Screensaver menu, but I tried turning it off, and it didn't help. I also tried playing gnometris to keep my laptop busy, but it would still turn off.
I really don't know how to help you with that. Perhaps yuo should ask the "Hardware support" section.

BTW did the kernel compile properly?

Alc0h0lic
November 19th, 2005, 07:25 AM
I really don't know how to help you with that. Perhaps yuo should ask the "Hardware support" section.

BTW did the kernel compile properly?
Yea it compiled fine eventually. I'm using the kernel now and I haven't had any problems with it (and got dothan cpu freq scaling to work, which it doesn't in the default kernel)

Diod
November 19th, 2005, 08:01 AM
This is whats in modules:

lp
mousedev
psmouse
sbp2
sr_mod
nvidia


This is when i do lsmod:

Module Size Used by
binfmt_misc 11592 1
rfcomm 38748 0
l2cap 25156 5 rfcomm
bluetooth 48580 4 rfcomm,l2cap
powernow_k8 12424 0
cpufreq_userspace 4380 1
cpufreq_stats 5316 0
freq_table 4484 2 powernow_k8,cpufreq_stats
cpufreq_powersave 1792 0
cpufreq_ondemand 6108 0
cpufreq_conservative 7012 0
ipt_limit 2304 8
iptable_mangle 2816 0
ipt_LOG 7040 8
ipt_MASQUERADE 3392 0
iptable_nat 23060 1 ipt_MASQUERADE
ipt_TOS 2432 0
ipt_REJECT 5440 1
ip_conntrack_irc 71760 0
ip_conntrack_ftp 72784 0
ipt_state 1856 6
ip_conntrack 43128 5 ipt_MASQUERADE,iptable_nat,ip_conntrack_irc,ip_con ntrack_ftp,ipt_state
iptable_filter 2880 1
ip_tables 19648 9 ipt_limit,iptable_mangle,ipt_LOG,ipt_MASQUERADE,ip table_nat,ipt_TOS,ipt_REJECT,ipt_state,iptable_fil ter
video 15812 0
tc1100_wmi 6788 0
sony_acpi 5388 0
pcc_acpi 11200 0
hotkey 9380 0
dev_acpi 11268 0
i2c_acpi_ec 5568 0
button 6544 0
battery 9412 0
container 4480 0
ac 4804 0
ipv6 252480 15
joydev 10048 0
floppy 59412 0
pcspkr 3460 0
rtc 12408 0
ohci1394 34804 0
shpchp 97252 0
pci_hotplug 27636 1 shpchp
nvsound 1543224 0
snd_intel8x0 33344 4
snd_ac97_codec 84028 1 snd_intel8x0
snd_pcm_oss 53152 0
snd_mixer_oss 19392 1 snd_pcm_oss
snd_pcm 89032 5 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 24260 3 snd_pcm
snd 55172 10 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
soundcore 9696 2 nvsound,snd
snd_page_alloc 10696 2 snd_intel8x0,snd_pcm
nvnet 72228 0
i2c_nforce2 6784 0
i2c_core 21328 2 i2c_acpi_ec,i2c_nforce2
amd64_agp 12296 1
nls_iso8859_1 4096 1
vfat 13696 1
fat 53020 1 vfat
nls_cp437 5760 3
ntfs 109104 2
dm_mod 58044 1
tsdev 7872 0
evdev 9728 0
nvidia 3711172 12
agpgart 34888 2 amd64_agp,nvidia
sr_mod 17252 0
sbp2 23176 0
ieee1394 101752 2 ohci1394,sbp2
psmouse 30212 0
mousedev 11680 1
parport_pc 35460 1
lp 12420 0
parport 36104 2 parport_pc,lp
md 45648 0
ext3 137352 2
jbd 55128 1 ext3
mbcache 9348 1 ext3
thermal 13064 0
processor 22908 2 powernow_k8,thermal
fan 4548 0
usbhid 35552 0
r8169 25740 0
forcedeth 21568 0
ehci_hcd 34312 0
ohci_hcd 20740 0
usbcore 118204 4 usbhid,ehci_hcd,ohci_hcd
sd_mod 19216 5
ide_disk 18560 4
ide_cd 41732 0
cdrom 39904 2 sr_mod,ide_cd
ide_generic 1472 0
sata_nv 9412 8
libata 54020 1 sata_nv
scsi_mod 135944 4 sr_mod,sbp2,sd_mod,libata
amd74xx 14044 1
ide_core 139028 4 ide_disk,ide_cd,ide_generic,amd74xx
unix 27248 434
vesafb 8088 0
capability 4808 0
commoncap 6912 1 capability
vga16fb 12680 1
vgastate 9792 1 vga16fb
softcursor 2496 2 vesafb,vga16fb
cfbimgblt 3008 2 vesafb,vga16fb
cfbfillrect 3968 2 vesafb,vga16fb
cfbcopyarea 4672 2 vesafb,vga16fb
fbcon 39104 72
tileblit 2432 1 fbcon
font 8320 1 fbcon
bitblit 5696 1 fbcon

tseliot
November 19th, 2005, 10:29 AM
This is whats in modules:

lp
mousedev
psmouse
sbp2
sr_mod
nvidia


This is when i do lsmod:

Module Size Used by
binfmt_misc 11592 1
rfcomm 38748 0
l2cap 25156 5 rfcomm
bluetooth 48580 4 rfcomm,l2cap
powernow_k8 12424 0
cpufreq_userspace 4380 1
cpufreq_stats 5316 0
freq_table 4484 2 powernow_k8,cpufreq_stats
cpufreq_powersave 1792 0
cpufreq_ondemand 6108 0
cpufreq_conservative 7012 0
ipt_limit 2304 8
iptable_mangle 2816 0
ipt_LOG 7040 8
ipt_MASQUERADE 3392 0
iptable_nat 23060 1 ipt_MASQUERADE
ipt_TOS 2432 0
ipt_REJECT 5440 1
ip_conntrack_irc 71760 0
ip_conntrack_ftp 72784 0
ipt_state 1856 6
ip_conntrack 43128 5 ipt_MASQUERADE,iptable_nat,ip_conntrack_irc,ip_con ntrack_ftp,ipt_state
iptable_filter 2880 1
ip_tables 19648 9 ipt_limit,iptable_mangle,ipt_LOG,ipt_MASQUERADE,ip table_nat,ipt_TOS,ipt_REJECT,ipt_state,iptable_fil ter
video 15812 0
tc1100_wmi 6788 0
sony_acpi 5388 0
pcc_acpi 11200 0
hotkey 9380 0
dev_acpi 11268 0
i2c_acpi_ec 5568 0
button 6544 0
battery 9412 0
container 4480 0
ac 4804 0
ipv6 252480 15
joydev 10048 0
floppy 59412 0
pcspkr 3460 0
rtc 12408 0
ohci1394 34804 0
shpchp 97252 0
pci_hotplug 27636 1 shpchp
nvsound 1543224 0
snd_intel8x0 33344 4
snd_ac97_codec 84028 1 snd_intel8x0
snd_pcm_oss 53152 0
snd_mixer_oss 19392 1 snd_pcm_oss
snd_pcm 89032 5 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 24260 3 snd_pcm
snd 55172 10 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
soundcore 9696 2 nvsound,snd
snd_page_alloc 10696 2 snd_intel8x0,snd_pcm
nvnet 72228 0
i2c_nforce2 6784 0
i2c_core 21328 2 i2c_acpi_ec,i2c_nforce2
amd64_agp 12296 1
nls_iso8859_1 4096 1
vfat 13696 1
fat 53020 1 vfat
nls_cp437 5760 3
ntfs 109104 2
dm_mod 58044 1
tsdev 7872 0
evdev 9728 0
nvidia 3711172 12
agpgart 34888 2 amd64_agp,nvidia
sr_mod 17252 0
sbp2 23176 0
ieee1394 101752 2 ohci1394,sbp2
psmouse 30212 0
mousedev 11680 1
parport_pc 35460 1
lp 12420 0
parport 36104 2 parport_pc,lp
md 45648 0
ext3 137352 2
jbd 55128 1 ext3
mbcache 9348 1 ext3
thermal 13064 0
processor 22908 2 powernow_k8,thermal
fan 4548 0
usbhid 35552 0
r8169 25740 0
forcedeth 21568 0
ehci_hcd 34312 0
ohci_hcd 20740 0
usbcore 118204 4 usbhid,ehci_hcd,ohci_hcd
sd_mod 19216 5
ide_disk 18560 4
ide_cd 41732 0
cdrom 39904 2 sr_mod,ide_cd
ide_generic 1472 0
sata_nv 9412 8
libata 54020 1 sata_nv
scsi_mod 135944 4 sr_mod,sbp2,sd_mod,libata
amd74xx 14044 1
ide_core 139028 4 ide_disk,ide_cd,ide_generic,amd74xx
unix 27248 434
vesafb 8088 0
capability 4808 0
commoncap 6912 1 capability
vga16fb 12680 1
vgastate 9792 1 vga16fb
softcursor 2496 2 vesafb,vga16fb
cfbimgblt 3008 2 vesafb,vga16fb
cfbfillrect 3968 2 vesafb,vga16fb
cfbcopyarea 4672 2 vesafb,vga16fb
fbcon 39104 72
tileblit 2432 1 fbcon
font 8320 1 fbcon
bitblit 5696 1 fbcon


Ok, you have to set the driver to "vesa" in your /etc/X11/xorg.conf

boot in your new kernel (reinstall it if you had uninstalled it)

then type this:

sudo modprobe sata_nv

then

lsmod

and see if you can find "sata_nv" in the list

Then make it load at boot:

sudo nano /etc/modules

and add this line (at the end)
sata_nv

CTRL+O to overwrite the file
CTRL+X to exit

Restart your computer.

Now it should detect your SATA drive.

Tell me if it works.

nrwilk
November 19th, 2005, 01:25 PM
Make sure you have installed each of these packages:

sudo apt-get install build-essential
sudo apt-get install kernel-package
sudo apt-get install gcc (this will install gcc-4.0 for kernel 2.6.13 or superior)
sudo apt-get install gcc-3.4
sudo apt-get install libncurses5
sudo apt-get install libncurses5-dev
sudo apt-get install libqt3-mt-dev

All of them say "<package> is already the newest version."

I started from the beginning, and I got the error again.

tseliot
November 19th, 2005, 01:35 PM
All of them say "<package> is already the newest version."

I started from the beginning, and I got the error again.

Open terminal:

1) cd /usr/src

ls

and post the output

Then

2) cd /usr/src/linux

ls

and post the output

nrwilk
November 19th, 2005, 01:39 PM
Wow, quick response!

Here it is:

fealos@localhost:/usr/src$ ls /usr/src
linux linux-2.6.14.2 linux-headers-2.6.12-9 linux-headers-2.6.12-9-386 linux-source-2.6.12.tar.bz2
fealos@localhost:/usr/src$ ls /usr/src/linux
linux-2.6.14.2
fealos@localhost:/usr/src$

tseliot
November 19th, 2005, 01:47 PM
Wow, quick response!

Here it is:

fealos@localhost:/usr/src$ ls /usr/src
linux linux-2.6.14.2 linux-headers-2.6.12-9 linux-headers-2.6.12-9-386 linux-source-2.6.12.tar.bz2
fealos@localhost:/usr/src$ ls /usr/src/linux
linux-2.6.14.2
fealos@localhost:/usr/src$
Ok, I've found the problem.
type:
cd /usr/src/linux/linux-2.6.14.2
mv * /usr/src/linux

Now everything will work.

nrwilk
November 19th, 2005, 02:07 PM
It's working now.

Thanks so much for the help!

Was it something I did wrong?

nrwilk
November 19th, 2005, 03:55 PM
well, when I restart and try to load the new kernel, it hangs at
"checking battery level..."

Same as it used to do when I was trying to install the nvidia drivers.

EDIT:
I logged into my new kernel's recovery mode, and checked xorg.conf, which had my device trying to run under "nvidia" instead of "nv".

Changed it in vi, and logged back in, and now it works. Yay!

Now, off to install the nvidia proprietary drivers.

tseliot
November 19th, 2005, 04:26 PM
It's working now.

Thanks so much for the help!

Was it something I did wrong?
Yes, I think you have a doubled folder (one inside the other):
/usr/src/linux-2.6.14.2/linux-2.6.14.2

so you should keep only the first directory /usr/src/linux-2.6.14.2/ and move there all the files which I made you put into the "linux" folder)
cd /usr/src/linux
sudo mv * /usr/src/linux-2.6.14.2/

Delete the doubled folder
sudo rm -f /usr/src/linux-2.6.14.2/linux-2.6.14.2

Then you should remove the symlink i.e. the "linux" folder
sudo rm -f linux

make a new one:
sudo ln -s /usr/src/linux-2.6.14.2 linux

then check that everything went fine

cd /usr/src/linux
ls
and make sure you see many files listed

nrwilk
November 19th, 2005, 05:14 PM
well, the file inside of my linux directory wasn't a directory. that was a symlink from the linux-2.6.14.2 directory which was in the /usr/src directory.

I got it from this step out of the vanilla section:
cd /home/your_username_folder/directory_where_you_put_the_downloaded_kernel (instead of cd /usr/src) (e.g. "cd /home/alberto/download" in my case)
sudo tar --bzip2 -xvf linux-source-2.6.12.tar.bz2 /usr/src (use the name of the file you downloaded)
sudo ln -s /usr/src/linux-source-2.6.12 /usr/src/linux (use the name of the file you downloaded)
cd /usr/src/linux

after following the instructions you gave just now, I have, in the /usr/src/linux directory, a link called "linux".

On another note, may I make a suggestion for this guide?

tseliot
November 19th, 2005, 05:32 PM
well, the file inside of my linux directory wasn't a directory. that was a symlink from the linux-2.6.14.2 directory which was in the /usr/src directory.

I got it from this step out of the vanilla section:


after following the instructions you gave just now, I have, in the /usr/src/linux directory, a link called "linux".

On another note, may I make a suggestion for this guide?
I'll try to extract kernel 2.6.14.2 and I'll see myself what happens

r4ik
November 19th, 2005, 07:16 PM
I used the k7 for my AMD Duron and i am getting close to what i want.
Thank you !

tseliot
November 20th, 2005, 04:57 AM
I used the k7 for my AMD Duron and i am getting close to what i want.
Thank you !
You're welcome.

BTW does my guide work in Dapper Drake?

tseliot
November 20th, 2005, 04:58 AM
I'll try to extract kernel 2.6.14.2 and I'll see myself what happens
I haven't had any problem, so I'll not change the guide.

dubz
November 20th, 2005, 06:45 AM
why dont more of you compile the kernel by hand?
It's seems to be much easier to me(buts thats just me)

check this outhttps://wiki.ubuntu.com/KernelByHandHowto?highlight=%28kernel%29

beijingjj
November 20th, 2005, 07:30 AM
I'm having a weird problem. I'm trying to compile my vanilla kernel from kernel.org but whenever it tries to compile a wireless card module I get this error:

CC [M] drivers/net/wireless/orinoco.o
drivers/net/wireless/orinoco.c:95:27: error: net/ieee80211.h: No such file or directory

followed by a slew of undeclared errors. So I did this:

# locate ieee80211.h
/usr/src/kernel-headers-2.6.14/include/net/ieee80211.h


then I edited the code for orinoco.c and changed this line
#include <net/ieee80211.h>
to read like this
#include "/usr/src/kernel-headers-2.6.14/include/net/ieee80211.h"
and now I can compile.

I'm confused by why this is happening. I took the ubuntu config file for 2.6.12-9 and used that with make oldconfig to get my current .config for this latest kernel. Is it something in Ubuntu's config file that's throwing things off?

tseliot
November 20th, 2005, 10:25 AM
I'm confused by why this is happening. I took the ubuntu config file for 2.6.12-9 and used that with make oldconfig to get my current .config for this latest kernel. Is it something in Ubuntu's config file that's throwing things off?
Thanks for reporting the error and the solution.

I really don't know what can be causing that problem as I'm not a developer or some high class Linux geek. Perhaps some modules are deprecated now in new kernels and this might cause problems. It's just a guess. I hope somebody can clarify this issue.

beijingjj
November 20th, 2005, 10:43 AM
I think maybe it was a rogue installation of ieee80211 from sourceforge which I had installed when trying to get my ipw2200 driver to load automatically. I blew away my entire kernel source tree and re-untarred it, used the same .config file, and it compiled OK.

Do you know why, when I boot from a vanilla kernel, my synaptics touchpad behaves differently? When I boot from the Ubuntu kernel I can use the "synclient -l" command but when I boot from the kernel.org kernel I can not (it says: Can't access shared memory area. SHMConfig disabled?

No matter which kernel I boot into, it is using the same xorg.conf file, and the synaptics driver, I've recently learned, is independent of the kernel (it resides in /usr/X11R6/lib/modules/input/synaptics_drv.o). I therefore can't for the life of me figure out what is different between these two scenarios. The only difference I've noticed is when the kernel.org kernel is booting the "hotplug" and "hal" services don't say "OK" (but also don't say "failed"). Could this be related?

tseliot
November 20th, 2005, 12:29 PM
Do you know why, when I boot from a vanilla kernel, my synaptics touchpad behaves differently? When I boot from the Ubuntu kernel I can use the "synclient -l" command but when I boot from the kernel.org kernel I can not (it says: Can't access shared memory area. SHMConfig disabled?
Sorry but I haven't tried a new kernel on my laptop (which has a touchpad) yet, so I can't help you with that.

No matter which kernel I boot into, it is using the same xorg.conf file, and the synaptics driver, I've recently learned, is independent of the kernel (it resides in /usr/X11R6/lib/modules/input/synaptics_drv.o). I therefore can't for the life of me figure out what is different between these two scenarios.
The point is that you have to recompile the modules (for example for the drivers of your graphic card) for each kernel of yours. Moreover the kernels are built with different compilers according to your kernel version (e.g. gcc-3.4 for kernels like 2.6.12, and gcc-4.0 for kernel 2.6.13 or higher).

Rob2687
November 20th, 2005, 02:37 PM
I'm trying to comple the 2.6.14 kernel with Nitro patch. Everything was going fine right up until the end when it was doing the ndiswrapper module part.
Here is the last part of the process...

Gah! This is the farthest I've ever gotten in to compile process without it erroring out. Any ideas what's wrong? :(

make[3]: Entering directory `/usr/src/modules/ndiswrapper'
rm -rf ndiswrapper.ko ndiswrapper.o hal.o iw_ndis.o loader.o misc_funcs.o ndis.o ntoskernel.o pe_linker.o proc.o wrapper.o usb.o d ivdi3.o usb.o x86_64_stubs.o \
divdi3.o .*.ko.cmd .*.o.cmd ndiswrapper.mod.[oc] *~ .tmp_versions
make[3]: Leaving directory `/usr/src/modules/ndiswrapper'
make[2]: Nothing to be done for `kdist_config'.
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs lib/modules/2.6.14-nitro2-nitro/misc
# build and install the module
/usr/bin/make KPKG_EXTRAV_ARG=EXTRAVERSION=-nitro2-nitro KSRC=/usr/src/linux \
KVER=2.6.14-nitro2-nitro \
INST_DIR=debian/ndiswrapper-modules-2.6.14-nitro2-nitro/lib/modules/2.6.14-nitro2-nitro/misc/ install
make[3]: Entering directory `/usr/src/modules/ndiswrapper'
/usr/bin/make -C /usr/src/linux SUBDIRS=/usr/src/modules/ndiswrapper \
NDISWRAPPER_VERSION=1.1 \
EXTRA_VERSION= modules
make[4]: Entering directory `/usr/src/linux-2.6.14'
CC [M] /usr/src/modules/ndiswrapper/hal.o
CC [M] /usr/src/modules/ndiswrapper/iw_ndis.o
CC [M] /usr/src/modules/ndiswrapper/loader.o
/usr/src/modules/ndiswrapper/loader.c: In function ‘register_devices’:
/usr/src/modules/ndiswrapper/loader.c:861: warning: assignment from incompatible pointer type
CC [M] /usr/src/modules/ndiswrapper/misc_funcs.o
CC [M] /usr/src/modules/ndiswrapper/ndis.o
/usr/src/modules/ndiswrapper/ndis.c:1637:5: warning: "LINUX_KERNEL_VERSION" is not defined
CC [M] /usr/src/modules/ndiswrapper/ntoskernel.o
CC [M] /usr/src/modules/ndiswrapper/pe_linker.o
/usr/src/modules/ndiswrapper/pe_linker.c:104:5: warning: "DEBUG" is not defined
CC [M] /usr/src/modules/ndiswrapper/proc.o
CC [M] /usr/src/modules/ndiswrapper/wrapper.o
/usr/src/modules/ndiswrapper/wrapper.c:286:46: error: macro "halt" passed 1 arguments, but takes just 0
/usr/src/modules/ndiswrapper/wrapper.c: In function ‘miniport_halt’:
/usr/src/modules/ndiswrapper/wrapper.c:286: warning: statement with no effect
make[5]: *** [/usr/src/modules/ndiswrapper/wrapper.o] Error 1
make[4]: *** [_module_/usr/src/modules/ndiswrapper] Error 2
make[4]: Leaving directory `/usr/src/linux-2.6.14'
make[3]: *** [default] Error 2
make[3]: Leaving directory `/usr/src/modules/ndiswrapper'
make[2]: *** [binary-modules] Error 2
make[2]: Leaving directory `/usr/src/modules/ndiswrapper'
make[1]: *** [kdist_build] Error 2
make[1]: Leaving directory `/usr/src/modules/ndiswrapper'
Module /usr/src/modules/ndiswrapper failed.
Hit return to Continue

robert@ubuntu:/usr/src/linux$ ls


It finished the two kernel .deb files but there is just no ndiswrapper module .deb file :(

tseliot
November 20th, 2005, 03:02 PM
I'm trying to comple the 2.6.14 kernel with Nitro patch. Everything was going fine right up until the end when it was doing the ndiswrapper module part.
Here is the last part of the process...

Gah! This is the farthest I've ever gotten in to compile process without it erroring out. Any ideas what's wrong? :(

make[3]: Entering directory `/usr/src/modules/ndiswrapper'
rm -rf ndiswrapper.ko ndiswrapper.o hal.o iw_ndis.o loader.o misc_funcs.o ndis.o ntoskernel.o pe_linker.o proc.o wrapper.o usb.o d ivdi3.o usb.o x86_64_stubs.o \
divdi3.o .*.ko.cmd .*.o.cmd ndiswrapper.mod.[oc] *~ .tmp_versions
make[3]: Leaving directory `/usr/src/modules/ndiswrapper'
make[2]: Nothing to be done for `kdist_config'.
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs lib/modules/2.6.14-nitro2-nitro/misc
# build and install the module
/usr/bin/make KPKG_EXTRAV_ARG=EXTRAVERSION=-nitro2-nitro KSRC=/usr/src/linux \
KVER=2.6.14-nitro2-nitro \
INST_DIR=debian/ndiswrapper-modules-2.6.14-nitro2-nitro/lib/modules/2.6.14-nitro2-nitro/misc/ install
make[3]: Entering directory `/usr/src/modules/ndiswrapper'
/usr/bin/make -C /usr/src/linux SUBDIRS=/usr/src/modules/ndiswrapper \
NDISWRAPPER_VERSION=1.1 \
EXTRA_VERSION= modules
make[4]: Entering directory `/usr/src/linux-2.6.14'
CC [M] /usr/src/modules/ndiswrapper/hal.o
CC [M] /usr/src/modules/ndiswrapper/iw_ndis.o
CC [M] /usr/src/modules/ndiswrapper/loader.o
/usr/src/modules/ndiswrapper/loader.c: In function ‘register_devices’:
/usr/src/modules/ndiswrapper/loader.c:861: warning: assignment from incompatible pointer type
CC [M] /usr/src/modules/ndiswrapper/misc_funcs.o
CC [M] /usr/src/modules/ndiswrapper/ndis.o
/usr/src/modules/ndiswrapper/ndis.c:1637:5: warning: "LINUX_KERNEL_VERSION" is not defined
CC [M] /usr/src/modules/ndiswrapper/ntoskernel.o
CC [M] /usr/src/modules/ndiswrapper/pe_linker.o
/usr/src/modules/ndiswrapper/pe_linker.c:104:5: warning: "DEBUG" is not defined
CC [M] /usr/src/modules/ndiswrapper/proc.o
CC [M] /usr/src/modules/ndiswrapper/wrapper.o
/usr/src/modules/ndiswrapper/wrapper.c:286:46: error: macro "halt" passed 1 arguments, but takes just 0
/usr/src/modules/ndiswrapper/wrapper.c: In function ‘miniport_halt’:
/usr/src/modules/ndiswrapper/wrapper.c:286: warning: statement with no effect
make[5]: *** [/usr/src/modules/ndiswrapper/wrapper.o] Error 1
make[4]: *** [_module_/usr/src/modules/ndiswrapper] Error 2
make[4]: Leaving directory `/usr/src/linux-2.6.14'
make[3]: *** [default] Error 2
make[3]: Leaving directory `/usr/src/modules/ndiswrapper'
make[2]: *** [binary-modules] Error 2
make[2]: Leaving directory `/usr/src/modules/ndiswrapper'
make[1]: *** [kdist_build] Error 2
make[1]: Leaving directory `/usr/src/modules/ndiswrapper'
Module /usr/src/modules/ndiswrapper failed.
Hit return to Continue

robert@ubuntu:/usr/src/linux$ ls


It finished the two kernel .deb files but there is just no ndiswrapper module .deb file :(

Perhaps you should try the latest source of ndiswrapper.

Delete the folder with your kernel (sudo rm -f /usr/src/linux-2.6.14.2 or whatever you called it)

Then follow the guide again but use this version of ndiswrapper (1.5) http://prdownloads.sourceforge.net/ndiswrapper/ndiswrapper-1.5.tar.gz?download

Then compile the kernel and tell me if it works (I need feedback)

Rob2687
November 20th, 2005, 03:18 PM
Perhaps you should try the latest source of ndiswrapper.

Delete the folder with your kernel (sudo rm -f /usr/src/linux-2.6.14.2 or whatever you called it)

Then follow the guide again but use this version of ndiswrapper (1.5) http://prdownloads.sourceforge.net/ndiswrapper/ndiswrapper-1.5.tar.gz?download

Then compile the kernel and tell me if it works (I need feedback)

So I just extract that 1.5 version in the /usr/src?
Because the ndiswrapper-source from apt-get has the /modules/ndiswapper/ folder, but the 1.5 version has some different stuff in there.

Edit: I'm going to try with the 1.5 source deb from the debian packages site.

tseliot
November 20th, 2005, 04:54 PM
So I just extract that 1.5 version in the /usr/src?
Because the ndiswrapper-source from apt-get has the /modules/ndiswapper/ folder, but the 1.5 version has some different stuff in there.

Edit: I'm going to try with the 1.5 source deb from the debian packages site.
If it doesn't work you can use the following guide (from the Ubuntu Wiki):
https://wiki.ubuntu.com//SetupNdiswrapperHowto
and use the latest version of ndiswrapper instead of the one suggested in the guide.
Look at the "Compiling from source" section

Rob2687
November 20th, 2005, 05:27 PM
It worked with the Debian source deb. :)

Just download this:
http://packages.debian.org/unstable/misc/ndiswrapper-source
Install it with:
sudo dkpg -i ndiswrapper-source_1.5-1_all.deb
cd /usr/src
tar -xvf ndiswrapper-source.tar.bz2

Continue with the rest of the instructions.

Once it's all compiled and the two kernel debs are installed, reboot. Then install the ndiswrapper module deb in /usr/src and this deb as well http://packages.debian.org/unstable/misc/ndiswrapper-utils

I had to reboot again after installing the ndiswrapper-utils to get it to work.
Only problem so far is that it doesn't report signal strength anymore but that's a minor thing.


Btw: If anyone is having problems with synaptics touch pad after install 2.6.14. Checkout this thread
http://www.linuxquestions.org/questions/showthread.php?s=&threadid=378381
Basically you have to modprobe evdev and add it to /etc/modules

petterah
November 20th, 2005, 05:33 PM
I tell you, this is horrible. It either locks the system, or says "no screen"...

Why is it so damn hard to get a nvidia 7800 to work in ubuntu... (Dell 9100, dual core 2.8ghz, 1920x1200 native lcd resolution)... I dont even need acceleration, just native resolution, but vesa wont support that.

(nv driver locks system too)

Any ideas? :confused:

Hi, i don't know if it is a desktop system, or a laptop, but my dell 2405 fpw lcd needed manual modeline in xorg.conf to get the native 1920x1200 resolution with the nvidia OSS driver, maybe this can help, search google for modeline. Mine is:

Modeline "1920x1200" 154.0 1920 1968 2000 2080 1200 1203 1209 1235

PS! This is for my Dell 2405 FPW, it may not work with other 1920x1200 lcd screens...

nrwilk
November 20th, 2005, 09:39 PM
I haven't had any problem, so I'll not change the guide.

I'm sorry, I wasn't suggesting that you change the guide because of this problem, I was suggesting an addition on another subject.

I was going to suggest that either in this or in the nvidia driver guide you include a note that if one has compiled a kernel >= 2.6.13, one can skip the steps to compile the nvidia driver with gcc3.4. Since 4.0 is used to compile the kernel, you can use 4.0 for the driver too.

Back to the problem I had, I think I just misinterpretted your instructions. Can we please have a breakdown of the files and directories, and where they should be just before we issue the make command to compile the kernel?

Here's what I got:
untar the source in /usr/src
copy all the files in the resulting directory into /usr/src/linux

I know theres a symlink in there somewhere, but I'm unsure of what those steps in step 3 are doing. Maybe we can have a breakdown of what we should have and where so we know what we should be doing. (also this way us noobs can learn a bit more about how these things work in general).

Thanks so much for this guide! I've got the kernel working, but I'm going to remove it and recompile because I forgot to patch the source BEFORE compiling with the suspend patch, hehe, silly me!

Thanks again!

Rob2687
November 21st, 2005, 12:04 AM
Is it okay to delete the linux-source-2.6.*.* and linux symlink after everything is done?
It takes up quite a bit of space.

tseliot
November 21st, 2005, 10:23 AM
Is it okay to delete the linux-source-2.6.*.* and linux symlink after everything is done?
It takes up quite a bit of space.
Yes you can delete it but keep in mind that some installers (e.g. the one of the nvidia drivers) may require it. However you can reinstall the sources later when you need them.

tseliot
November 21st, 2005, 10:39 AM
I'm sorry, I wasn't suggesting that you change the guide because of this problem, I was suggesting an addition on another subject.

I was going to suggest that either in this or in the nvidia driver guide you include a note that if one has compiled a kernel >= 2.6.13, one can skip the steps to compile the nvidia driver with gcc3.4. Since 4.0 is used to compile the kernel, you can use 4.0 for the driver too.

Back to the problem I had, I think I just misinterpretted you instructions. Can we please have a breakdown of the files and directories, and where they should be just before we issure the make command to compile the kernel?

Here's what I got:
untar the source in /usr/src
copy all the files in the resulting directory into /usr/src/linux

I know theres a symlink in there somewhere, but I'm unsure of what those steps in step 3 are doing. Maybe we can have a breakdown of what we should have and where so we know what we should be doing. (also this way us noobs can learn a bit more about how these things work in general).

Thanks so much for this guide! I've got the kernel working, but I'm going to remove it and recompile because I forgot to patch the source BEFORE compiling with the suspend patch, hehe, silly me!

Thanks again!

Ok, after you have installed the sources from synaptic or downloaded them from kernel.org

you extract the file to /usr/src

Then you make sure everything went ok.
cd /usr/src
ls

you should see the following files and folder (more folders may be listed)

linux-source-2.6.12
linux-source-2.6.12.tar.bz2


Then make sure there is not a doubled folder i.e. there is not another "linux-source-2.6.12" folder inside /usr/src/linux-source-2.6.12"

Therefore:
cd /usr/src/linux-source-2.6.12
ls

If something like this is listed then it's ok:
arch drivers mm stamp-build
cluster fs Module.symvers stamp-configure
conf.vars include net stamp-debian
COPYING init README stamp-headers
CREDITS ipc README.Debian stamp-image
crypto kernel REPORTING-BUGS stamp-kernel-configure
debian lib scripts System.map
Debian.src.changelog MAINTAINERS security usr
Documentation Makefile sound vmlinux

Now we make the symlink i.e. "linux" will be our link to the path /usr/src/linux-source-2.6.12. "linux" is not a real folder, it's just a link.

Make sure the "linux" doesn't already exist i.e. remove it:
sudo rm -f /usr/src/linux

Then:

sudo ln -s /usr/src/linux-source-2.6.12 /usr/src/linux
cd /usr/src/linux

And continue with the guide.

I hope I have made things a bit clearer.

nrwilk
November 21st, 2005, 12:46 PM
haha! That was my problem. I made the symlink INSIDE of a folder named "linux". Thanks a lot for this breakdown! I'm now confident in my kernel compiling abilities. At least, as long as I have this trusty how-to by my side.

Did you see my suggestion to add a line about nvidia compilation with gcc4.0 if you've compiled a kernel >= 2.6.13?

tseliot
November 21st, 2005, 05:23 PM
haha! That was my problem. I made the symlink INSIDE of a folder named "linux". Thanks a lot for this breakdown! I'm now confident in my kernel compiling abilities. At least, as long as I have this trusty how-to by my side.
Thanks and enjoy your new kernel :)

Did you see my suggestion to add a line about nvidia compilation with gcc4.0 if you've compiled a kernel >= 2.6.13?
It's a good suggestion but I don't want to confuse newbies. However the solution to the problem is provided in point 2 of the PROBLEMS SECTION of the guide.

ezphilosophy
November 24th, 2005, 01:22 PM
Tseliot, you are quite busy! I almost don't want to ask the question..... :)
At step 8, it starts and gets about 10 min. into it and it gives me this:

LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
Inconsistent kallsyms data
Try setting CONFIG_KALLSYMS_EXTRA_PASS
make[1]: *** [vmlinux] Error 1
make[1]: Leaving directory `/usr/src/linux-source-2.6.12'
make: *** [stamp-build] Error 2
ez@ezphilosophy:/usr/src/linux$


Any ideas?

tseliot
November 24th, 2005, 01:47 PM
Tseliot, you are quite busy! I almost don't want to ask the question..... :)
At step 8, it starts and gets about 10 min. into it and it gives me this:

LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
Inconsistent kallsyms data
Try setting CONFIG_KALLSYMS_EXTRA_PASS
make[1]: *** [vmlinux] Error 1
make[1]: Leaving directory `/usr/src/linux-source-2.6.12'
make: *** [stamp-build] Error 2
ez@ezphilosophy:/usr/src/linux$


Any ideas?
Did you set anything like experimental modules, or something which is not mentioned in the guide? (after "sudo make menuconfig")

tseliot
November 24th, 2005, 01:53 PM
Try this:
sudo make menuconfig

get to

General setup/ Configure standard kernel features (for small systems) /

and select "Do an extra kallsyms pass" and press the spacebar to enable it.

Then Save and exit

sudo make-kpkg clean

And compile the kernel again

ezphilosophy
November 24th, 2005, 01:57 PM
Did you set anything like experimental modules, or something which is not mentioned in the guide? (after "sudo make menuconfig")

No, nothing.
First, I changed the video driver to "nv"
Processor type 386
I enabled DMA

I skipped the rest (modules and high memory support)

The only thing that was inconsistent is that when I did step 8, I copied and pasted the command, but went to edit the "custom" part, and suddenly it started running. I didn't realize I hit anything so I went ahead and pressed ctrl+c to break it. I went back to see what happened but it was too far up. I went ahead and started it again (using the name "custom"). It didn't work (the same error as I originally described) so I went through and did the how-to again starting with step 3, tar the linux source. Of course, at the end, I got exactly the same error.

tseliot
November 24th, 2005, 01:58 PM
No, nothing.
First, I changed the video driver to "nv"
Processor type 386
I enabled DMA

I skipped the rest (modules and high memory support)
Try my 2nd advice and it should work.

Let me know how it goes.

ezphilosophy
November 24th, 2005, 03:36 PM
Success!! Thanks man!

Any chance this will make a difference with the Nvidia problem?

http://ubuntuforums.org/showthread.php?t=85805&highlight=nvidia+reboot

Also, maybe not the appropriate place to ask, but do I need to reinstall the nvidia drivers? If I used your method 2 before, do I need to uninstall it again? If so, how? It doesn't show up in synaptic that I installed them.

tseliot
November 24th, 2005, 03:58 PM
Success!! Thanks man!

Any chance this will make a difference with the Nvidia problem?

http://ubuntuforums.org/showthread.php?t=85805&highlight=nvidia+reboot
I have no idea as I have never had such a problem. You should see it yourself.
Also, maybe not the appropriate place to ask, but do I need to reinstall the nvidia drivers? If I used your method 2 before, do I need to uninstall it again? If so, how? It doesn't show up in synaptic that I installed them.
Yes, you have to reinstall the nvidia drivers for every kernel you have. This means that you have to use Method2 for your new kernel.

Asazuke
November 30th, 2005, 08:00 PM
Amazing! I never thought I'd be able to do something as intimidating as Compiling my Kernel. Thank you tseliot for another great HOWTO. Keep up the great work.

tseliot
December 1st, 2005, 10:21 AM
Amazing! I never thought I'd be able to do something as intimidating as Compiling my Kernel. Thank you tseliot for another great HOWTO. Keep up the great work.
Thanks again and enjoy your new kernel :)

Houman
December 4th, 2005, 07:23 PM
hi there;
thank youf or this great howto, i just had a small question;

after changing "ati" to "vesa" my resulotion is incorrect, what should i do :S

Also i understand that everytime a kernel chanegs the source for the ipw2200 driver has to be recompiled against the new kernel, but this means i wont be able to use my wireless connection in the old kernel right? is there a way to remedy this?

regards;
Houman

Rob2687
December 4th, 2005, 07:40 PM
I never change it to vesa and it seems to work okay for me O_o

Houman
December 4th, 2005, 08:05 PM
hi rob; (im from thornhill ontario, :P)

if i dont change the ati (which is in fact just the binary drivers that came with breezy) my custom kernel just hangs , i also tried fglrx binary drivers, same story,

I dont understand why binary drivers wont work for the custom kernel but work for the stock kernel, :|

also when i compiled my ipw2200 drivers for the stock kernel i couldnt use them in the custom kernel, so i removed them and did a compile against the custom kernel, and now i can use them both in the custom kernel and the stock kernel :|

Im very confused, if anyone can give me website or a tutorial or any links so i can read up on this stuff (modules and kernel compiles...) cuz its really confusing me :|

regards;

tseliot
December 5th, 2005, 10:11 AM
hi there;
thank youf or this great howto, i just had a small question;

after changing "ati" to "vesa" my resulotion is incorrect, what should i do :S

Also i understand that everytime a kernel chanegs the source for the ipw2200 driver has to be recompiled against the new kernel, but this means i wont be able to use my wireless connection in the old kernel right? is there a way to remedy this?

regards;
Houman
1) I said to change the driver because you have to recompile the modules if you use a proprietary driver. In your case there's no need to change it to vesa. Stick to "ati".
EDIT: I've seen your latest post. I don't know why the "ati" (opensource) driver doesn't work. It depends on the xserver rather than on your kernel. It's weird and that driver (in theory and according to my experience) SHOULD work

2) You have to compile the modules (for ipw2200 in your case) for each kernel. This means that if you installed the drivers for your old kernel you will find them as they were if you boot in it. [Every kernel has its "modules" folder]
In other words YES, you will be able to use your wireless connection also in your old kernel.

Houman
December 5th, 2005, 12:53 PM
Dear tseliot;

thank you so much for your response, things are a bit more clear now :) eventhough i still dont knwo whats the problem with the ati driver at least i can make sense of whats happening;

actually i used to run debian before and i did a cutom kernel and i played with my configs a little too much, (i used that old config file to compile myu new kernel) so its likely something is not working right because of a mistake i made in the drivers section or something of the sort;

its hard to see the errors i get because it hangs at boot and i cant even get to dmesg ;

thansk again for a great howto;

Houman

tseliot
December 5th, 2005, 02:00 PM
Dear tseliot;

thank you so much for your response, things are a bit more clear now :) eventhough i still dont knwo whats the problem with the ati driver at least i can make sense of whats happening;

actually i used to run debian before and i did a cutom kernel and i played with my configs a little too much, (i used that old config file to compile myu new kernel) so its likely something is not working right because of a mistake i made in the drivers section or something of the sort;

its hard to see the errors i get because it hangs at boot and i cant even get to dmesg ;

thansk again for a great howto;

Houman
Thanks for appreciating my work.
Anyhow I don't recommend you to use the config file of a Debian kernel. I'm not saying that it won't work but I can't assure it will work properly.

garba
December 5th, 2005, 07:18 PM
this is a very good guide tseliot, forgive me for being picky, but I can't understand why people keep doing this /usr/src/linux symlink thing... it's pointless, actually the reason behind doing it in the first place was unorthodox (you can find a famous post by torvalds about this)... besides, you can untar the kernel source package in your home dir and build it, there's no need to be root to compile a kernel, though I find it reasonable to keep the build in /usr/src for reference of course

TheCondor
December 5th, 2005, 09:16 PM
Awesome guide. :)

Thank you very much, I finally managed to compile my own kernel after so many tries.

Excellent job :)

EDIT

I cant get my Nvidia card to work though, and i did all the steps required to install the drivers. :(

I get the module Nvidia not found error in the log.

tseliot
December 6th, 2005, 09:51 AM
this is a very good guide tseliot, forgive me for being picky, but I can't understand why people keep doing this /usr/src/linux symlink thing... it's pointless, actually the reason behind doing it in the first place was unorthodox (you can find a famous post by torvalds about this)... besides, you can untar the kernel source package in your home dir and build it, there's no need to be root to compile a kernel, though I find it reasonable to keep the build in /usr/src for reference of course
I suppose it's just a way of doing things. It's not the only one. But that's the way I learnt to compile kernels and this guide is aimed at newbies, therefore I want it to be as "copy & paste" as possible.

j813
December 8th, 2005, 11:17 AM
Does this work for 64bit version?
Is it possible to convert a .rpm to .deb then dpkg it?
Thanks

tseliot
December 8th, 2005, 11:19 AM
Does this work for 64bit version?
Is it possible to convert a .rpm to .deb then dpkg it?
Thanks
1) Yes, it works for 64bit as well
2) Do you want to convert a kernel from rpm to deb or what?

j813
December 8th, 2005, 11:21 AM
Exactly
Will be easier
Possible?

tseliot
December 8th, 2005, 11:31 AM
Exactly
Will be easier
Possible?
Don't do it. I should trust debs converted from rpms in general. The kernel is the most important thing you have therefore you might not want to use a converted package.

What do you need from that rpm? Some special feature, maybe I can help you.

j813
December 8th, 2005, 11:37 AM
It's just that the .rpms is easier to install, by double clicking.

tseliot
December 8th, 2005, 11:49 AM
It's just that the .rpms is easier to install, by double clicking.
Remember that you have to compile kernels only if you have any problems which are related to the kernel. Otherwise you can install the kernel for your architecture (k8,etc.) in Synaptic or Kynaptic or Adept. That's a matter of mouse clicks.

dk_pa
December 8th, 2005, 10:39 PM
I have been reading through various threads about compiling Kernels because of my ITE8212 ATA RAID Controller. Anyway...I'm not sure how to tell what modules are restricted and what are not...so I thought before I did this I would post the result of lspci and maybe someone can inform me if I am using any restricted modules. I know I'll have to reinstall my ATI Drivers, but that's not a big deal of course.

0000:00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
0000:00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
0000:00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
0000:00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
0000:00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
0000:00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
0000:00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
0000:00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
0000:00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
0000:00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
0000:00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
0000:01:0a.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
0000:01:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)0000:01:0c.0 RAID bus controller: Integrated Technology Express, Inc. IT/ITE8212 Dual channel ATA RAID controller (PCI version seems to be IT8212, embedded seems (rev 11)
0000:01:0d.0 RAID bus controller: Silicon Image, Inc. (formerly CMD Technology Inc) SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
0000:01:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)0000:02:00.0 VGA compatible controller: ATI Technologies Inc Radeon R300 ND [Radeon 9700 Pro]
0000:02:00.1 Display controller: ATI Technologies Inc Radeon R300 [Radeon 9700 Pro] (Secondary)


On a side note, I did notice that my card is listed in there and it is shown in the device manager but I can't seem to see anything attached to it. I dont know if the drives would be somewhere other than sda or hdb or somethign like that or should I seem them "as is" if things were working properly to begin with? If there is another answer rather than recompiling the kernel I am more than willing to listen =)

Thanks

tseliot
December 9th, 2005, 06:39 AM
I have been reading through various threads about compiling Kernels because of my ITE8212 ATA RAID Controller. Anyway...I'm not sure how to tell what modules are restricted and what are not...so I thought before I did this I would post the result of lspci and maybe someone can inform me if I am using any restricted modules. I know I'll have to reinstall my ATI Drivers, but that's not a big deal of course.



On a side note, I did notice that my card is listed in there and it is shown in the device manager but I can't seem to see anything attached to it. I dont know if the drives would be somewhere other than sda or hdb or somethign like that or should I seem them "as is" if things were working properly to begin with? If there is another answer rather than recompiling the kernel I am more than willing to listen =)

Thanks
you need the drivers for linux for your chipset http://www.ite.com.tw/product_info/file/pc/LinuxDriver_it8212_092005-09.zip

I'll give you further instructions as soon as I have some spare time (I'm going to get my degree next wednesday)

zarathustra
December 9th, 2005, 09:15 AM
Does anyone have a USR wireless card, or anything that uses a TI chipset and needs the acx drivers? I don't think these are in the kernel, and the mm patches no longer have them. I don't know what Ubuntu uses to get the card working, and I lose it with a custom kernel installation. Is there any way to get it working with the new kernel?

dk_pa
December 10th, 2005, 12:45 AM
I took care of my problem. I updated to the 2.6.14 kernel with the ck6 patch following the other guide here on the forums. I didnt have to reinstall my video card drivers or anything tho (seems odd to me). Thanks for the help =)

tseliot
December 10th, 2005, 05:15 AM
I took care of my problem. I updated to the 2.6.14 kernel with the ck6 patch following the other guide here on the forums. I didnt have to reinstall my video card drivers or anything tho (seems odd to me). Thanks for the help =)
Thanks for reporting.

canopus4320
December 12th, 2005, 11:45 PM
tseliot, it worked nicely for me, thanks!!! i've followed your howto and i feel my box much more responsive, mainly xorg, it feels like 4 or 5 times faster

raheesom
December 13th, 2005, 02:59 PM
I'm running a dual Opteron with ext2 (boot part), ext3 (root, home), lvm (home).

I've tried downgrading the default Breezy kernel to 2.6.9 but had driver module issues with it, so I thought I'd compile a vanilla kernel from kernel.org.

I've followed your steps in the howto above without problem.
My problem comes when booting the new kernel!

My root filesystem is /dev/md1, home is an lvm volume.

/dev/md1 / ext3 defaults,errors=remount-ro 0 1
/dev/md0 /boot ext2 defaults 0 2
/dev/mapper/HOMEVolGrp-HOME1Vol /home ext3 defaults 0

When I boot, the kernel can't find /dev/md1 and shoves me to a shell.
I first had the MD support as a module (bad oversight) so I recompiled the kernel with MD in the kernel. Same error.

While I keep looking for a solution, does anything come to your mind?

raheesom@rahubuntu:/boot/grub$ uname -a
Linux rahubuntu 2.6.12-10-amd64-generic #1 Fri Nov 18 11:51:07 UTC 2005 x86_64 GNU/Linux

Reg
Rupert

tseliot
December 14th, 2005, 12:21 PM
I'm running a dual Opteron with ext2 (boot part), ext3 (root, home), lvm (home).

I've tried downgrading the default Breezy kernel to 2.6.9 but had driver module issues with it, so I thought I'd compile a vanilla kernel from kernel.org.

I've followed your steps in the howto above without problem.
My problem comes when booting the new kernel!

My root filesystem is /dev/md1, home is an lvm volume.

/dev/md1 / ext3 defaults,errors=remount-ro 0 1
/dev/md0 /boot ext2 defaults 0 2
/dev/mapper/HOMEVolGrp-HOME1Vol /home ext3 defaults 0

When I boot, the kernel can't find /dev/md1 and shoves me to a shell.
I first had the MD support as a module (bad oversight) so I recompiled the kernel with MD in the kernel. Same error.

While I keep looking for a solution, does anything come to your mind?

raheesom@rahubuntu:/boot/grub$ uname -a
Linux rahubuntu 2.6.12-10-amd64-generic #1 Fri Nov 18 11:51:07 UTC 2005 x86_64 GNU/Linux

Reg
Rupert
1) Why do you need kernel 2.6.9? And what's the purpose of your kernel recompilation?
2) You used a vanilla kernel. Did you compile the support for ext3 and ext2 in the kernel(not as modules)?

3) post (as an attach) your /boot/config-rahubuntu 2.6.12-10-amd64-generic (or it might have a similar name)

4) post the output of "lspci"

r4ik
December 14th, 2005, 06:28 PM
Exuse me did not read everything in this post.
This is what happenned.
Did the steps til the long list passed by then i got stuck.
In other words i could not proceed.
So i rebooted fingers crossed and found a a much faster machine on the same (old) kernel.
Did not have to do the folowing steps at all.
Any ideas?
Thnx.

Rob2687
December 14th, 2005, 06:48 PM
Exuse me did not read everything in this post.
This is what happenned.
Did the steps til the long list passed by then i got stuck.
In other words i could not proceed.
So i rebooted fingers crossed and found a a much faster machine on the same (old) kernel.
Did not have to do the folowing steps at all.
Any ideas?
Thnx.

What do you mean you got stuck? Any error messages?

Nothing will change unless you have installed the .deb files that are created. All you're doing is creating those here.

r4ik
December 14th, 2005, 06:54 PM
It just did not proceed no errors.
To be more specific it stopped after this.


sudo apt-get update
sudo apt-get install build-essential
sudo apt-get install kernel-package
sudo apt-get install gcc (this will install gcc-4.0 for kernel 2.6.13 or superior)
sudo apt-get install gcc-3.4
sudo apt-get install libncurses5
sudo apt-get install libncurses5-dev
sudo apt-get install libqt3-mt-dev
sudo passwd root

After that i could type everything i wanted but the terminal would not accept it.

MichaelM
December 14th, 2005, 07:17 PM
Just checking: Did the terminal stop accepting your typing after you had finished setting your root password, or at the promptEnter new UNIX password:

r4ik
December 14th, 2005, 07:20 PM
After i set the new password.
It accepted typing but nothing happenned after any command.

Rob2687
December 14th, 2005, 09:14 PM
Just skip the root password part then. When you get step 6, instead of doing just su do sudo su instead.

r4ik
December 15th, 2005, 03:24 AM
Late answer sorry for that but had to go to sleep.
Thanks for your suggestion but i started
the machine this morning and its still fast.
So i am not going to touch the kernel again because
i am very happy with the way it performs now.
This AMD 800 comes very close to my P4 2.4 on windows now.
Works for me!
Thnx for your time.

tseliot
December 15th, 2005, 10:00 AM
Exuse me did not read everything in this post.
This is what happenned.
Did the steps til the long list passed by then i got stuck.
In other words i could not proceed.
So i rebooted fingers crossed and found a a much faster machine on the same (old) kernel.
Did not have to do the folowing steps at all.
Any ideas?
Thnx.
I really don't know the reason for the speedup.
You didn't change your kernel after all :confused:

r4ik
December 15th, 2005, 02:51 PM
It IS faster maybe a provider thing.
Anounced a speedup dont know if that has
anything to do with it.(my guess is not)
I am going to do the compilation again see what
it does.

r4ik
December 15th, 2005, 03:30 PM
This is what i get now
Suggestions please?

sudo rm /usr/src/linux
rm: cannot remove

Rob2687
December 15th, 2005, 03:33 PM
sudo rm -r /usr/src/linux

r4ik
December 15th, 2005, 04:09 PM
This is what i get now did i make a mistake or what happenned?

We do not seem to be in a top level linux kernel source directory
tree. Since we are trying to make a kernel package, that does not make
sense. Please change directory to a top level linux kernel source
directory, and try again. (If I am wrong, and this is indeed a top
level linux kernel source directory, then I have gotten sadly out of
date with current kernels, and you should upgrade kernel-package)

tseliot
December 15th, 2005, 04:29 PM
This is what i get now did i make a mistake or what happenned?

We do not seem to be in a top level linux kernel source directory
tree. Since we are trying to make a kernel package, that does not make
sense. Please change directory to a top level linux kernel source
directory, and try again. (If I am wrong, and this is indeed a top
level linux kernel source directory, then I have gotten sadly out of
date with current kernels, and you should upgrade kernel-package)
Could you post every exact step you took?
e.g cd /usr/src/linux etc.

curtis
December 15th, 2005, 04:30 PM
This is what i get now did i make a mistake or what happenned?

We do not seem to be in a top level linux kernel source directory
tree. Since we are trying to make a kernel package, that does not make
sense. Please change directory to a top level linux kernel source
directory, and try again. (If I am wrong, and this is indeed a top
level linux kernel source directory, then I have gotten sadly out of
date with current kernels, and you should upgrade kernel-package)
Are you sure you are in /usr/src/linux?
And also, when you type 'ls' do you get a listing of files and not a broken system link?

r4ik
December 15th, 2005, 04:45 PM
r4ik@compu:~$ ls
automatix.log firefox frozen.htm
Desktop Firefox_wallpaper.png install_flash_player_7_linux
r4ik@compu:~$

This is my ls output.
Posting exactly every step i took is almost impossible thing to do but im sure i did everything by the book.
If you want me to i will run it again.

tseliot
December 15th, 2005, 04:55 PM
r4ik@compu:~$ ls
automatix.log firefox frozen.htm
Desktop Firefox_wallpaper.png install_flash_player_7_linux
r4ik@compu:~$

This is my ls output.
Posting exactly every step i took is almost impossible thing to do but im sure i did everything by the book.
If you want me to i will run it again.
Well I mean:
cd /usr/src/linux
ls (and post the output)

r4ik
December 15th, 2005, 05:05 PM
r4ik@compu:~$ cd /usr/src/linux
r4ik@compu:/usr/src/linux$ ls
arch drivers linux-source-2.6.12.tar.bz2 REPORTING-BUGS
cluster fs MAINTAINERS scripts
COPYING include Makefile security
CREDITS init mm sound
crypto ipc net usr
Debian.src.changelog kernel README
Documentation lib README.Debian
r4ik@compu:/usr/src/linux$

Here is the output.
Cant make anything out of it.

tseliot
December 15th, 2005, 05:27 PM
r4ik@compu:~$ cd /usr/src/linux
r4ik@compu:/usr/src/linux$ ls
arch drivers linux-source-2.6.12.tar.bz2 REPORTING-BUGS
cluster fs MAINTAINERS scripts
COPYING include Makefile security
CREDITS init mm sound
crypto ipc net usr
Debian.src.changelog kernel README
Documentation lib README.Debian
r4ik@compu:/usr/src/linux$

Here is the output.
Cant make anything out of it.
1) Why is "linux-source-2.6.12.tar.bz2" in that folder?
2) It is likely that you didn't extract the file with the sources correctly.
Please remove that folder and extract the file again and post the output of "ls"

EDIT: make sure you remove not only "/usr/src/linux" but also "/usr/src/linux-source-2.6.12"

r4ik
December 15th, 2005, 05:54 PM
Removed it with Synaptic still there ??
Perhaps another way to do it?

r4ik@compu:~$ cd /usr/src/linux
r4ik@compu:/usr/src/linux$ ls
arch drivers linux-source-2.6.12.tar.bz2 REPORTING-BUGS
cluster fs MAINTAINERS scripts
COPYING include Makefile security
CREDITS init mm sound
crypto ipc net usr
Debian.src.changelog kernel README
Documentation lib README.Debian
r4ik@compu:/usr/src/linux$

tseliot
December 15th, 2005, 06:19 PM
Removed it with Synaptic still there ??
Perhaps another way to do it?

r4ik@compu:~$ cd /usr/src/linux
r4ik@compu:/usr/src/linux$ ls
arch drivers linux-source-2.6.12.tar.bz2 REPORTING-BUGS
cluster fs MAINTAINERS scripts
COPYING include Makefile security
CREDITS init mm sound
crypto ipc net usr
Debian.src.changelog kernel README
Documentation lib README.Debian
r4ik@compu:/usr/src/linux$
sudo rm -r /usr/src/linux-source-2.6.12
and follow ONLY these steps:
Then install linux source from synaptics
cd /usr/src
sudo tar --bzip2 -xvf linux-source-2.6.12.tar.bz2

then follow the guide

r4ik
December 15th, 2005, 06:35 PM
r4ik@compu:~$ sudo rm -r /r4ik/src/linux-source-2.6.12
rm: cannot remove `/r4ik/src/linux-source-2.6.12': Onbekend bestand of map
r4ik@compu:~$

Unknown.
My mistake try again

r4ik
December 15th, 2005, 06:39 PM
Nope wasnt directory unknown.

tseliot
December 15th, 2005, 06:42 PM
r4ik@compu:~$ sudo rm -r /r4ik/src/linux-source-2.6.12
rm: cannot remove `/r4ik/src/linux-source-2.6.12': Onbekend bestand of map
r4ik@compu:~$

Unknown.
My mistake try again
Please type the commands as they are written:
don't replace "usr" with your username (usr is a folder)

sudo rm -r /usr/src/linux-source-2.6.12
and follow ONLY these steps:
Then install linux source from synaptics
cd /usr/src
sudo tar --bzip2 -xvf linux-source-2.6.12.tar.bz2

r4ik
December 15th, 2005, 06:55 PM
r4ik@compu:~$ sudo rm -r /usr/src/linux-source-2.6.12
Password:
rm: cannot remove `/usr/src/linux-source-2.6.12': Onbekend bestand of map
r4ik@compu:~$

Cant do anything about it sorry.
Unknown.

tseliot
December 15th, 2005, 07:07 PM
r4ik@compu:~$ sudo rm -r /usr/src/linux-source-2.6.12
Password:
rm: cannot remove `/usr/src/linux-source-2.6.12': Onbekend bestand of map
r4ik@compu:~$

Cant do anything about it sorry.
Unknown.
sudo rm -f /usr/src/linux-source-2.6.12

OR if it doesn't work

sudo nautilus (or "sudo konqueror" if you use KDE) (so as to use the gui filemanager)
get to /usr/src
right click on the "linux-source-2.6.12" folder and select "move to trash"

Then close nautilus (or konqueror) and do

cd /usr/src
sudo tar --bzip2 -xvf linux-source-2.6.12.tar.bz2

r4ik
December 15th, 2005, 07:23 PM
r4ik@compu:~$ sudo rm -f /usr/src/linux-source-2.6.12
r4ik@compu:~$ cd /usr/src
r4ik@compu:/usr/src$
r4ik@compu:/usr/src$ sudo tar --bzip2 -xvf linux-source-2.6.12.tar.bz2
tar: linux-source-2.6.12.tar.bz2: Kan niet open: Onbekend bestand of map
tar: Fout is niet herstelbaar: er wordt nu afgesloten
tar: Child returned status 2
tar: Afsluitcode uitgesteld na eerdere fouten
r4ik@compu:/usr/src$

cant open unknown dir. tar:no recovery close down after previous mistakes (short translation)

r4ik
December 15th, 2005, 07:43 PM
I have to go now can get four hours of sleep before work.
Thanks for your time.
Perhaps a solution will pop up later.
Have a nice day.
Night that is since you are located in Italy.

tseliot
December 15th, 2005, 07:44 PM
r4ik@compu:~$ sudo rm -f /usr/src/linux-source-2.6.12
r4ik@compu:~$ cd /usr/src
r4ik@compu:/usr/src$
r4ik@compu:/usr/src$ sudo tar --bzip2 -xvf linux-source-2.6.12.tar.bz2
tar: linux-source-2.6.12.tar.bz2: Kan niet open: Onbekend bestand of map
tar: Fout is niet herstelbaar: er wordt nu afgesloten
tar: Child returned status 2
tar: Afsluitcode uitgesteld na eerdere fouten
r4ik@compu:/usr/src$

cant open unknown dir. tar:no recovery close down after previous mistakes (short translation)
sudo apt-get install linux-source

cd /usr/src
ls (POST THE OUTPUT if you have any problems)
You should be able to see the following file among the other elements of the list:
linux-source-2.6.12.tar.bz2

Then:
sudo tar --bzip2 -xvf linux-source-2.6.12.tar.bz2

anatole
December 16th, 2005, 05:50 AM
thank you very much, this was an excellent help to get my it8212 gigaraid to work by setting up kernel 2.6.14.4...
i have one problem now, however. when i boot with the new kernel, one of my two hard disks cannot be accessed. my hard drives are organized like this:
/dev/hda1 - windows partition ntfs
/dev/hda2 - ext3 partition

/dev/hdb1 - linux swap partition
/dev/hdb2 - linux root partition (ext3)
/dev/hdb3 - fat32 partition
/dev/hdb4 - another ext3 partition

so, my hda partitions don't get mounted during boot (despite they are listed in fstab), nor can i mount them later (i get the "already mounted or <mounttarget> is busy" message, however, theyre not mounted according to umount and mtab, and i cannot mount them to even a freshly created directory). the two hard disks are on the same standard IDE slot, so i cannot really understand why this is happening. any help?

tseliot
December 16th, 2005, 01:04 PM
thank you very much, this was an excellent help to get my it8212 gigaraid to work by setting up kernel 2.6.14.4...
i have one problem now, however. when i boot with the new kernel, one of my two hard disks cannot be accessed. my hard drives are organized like this:
/dev/hda1 - windows partition ntfs
/dev/hda2 - ext3 partition

/dev/hdb1 - linux swap partition
/dev/hdb2 - linux root partition (ext3)
/dev/hdb3 - fat32 partition
/dev/hdb4 - another ext3 partition

so, my hda partitions don't get mounted during boot (despite they are listed in fstab), nor can i mount them later (i get the "already mounted or <mounttarget> is busy" message, however, theyre not mounted according to umount and mtab, and i cannot mount them to even a freshly created directory). the two hard disks are on the same standard IDE slot, so i cannot really understand why this is happening. any help?
1) If you use GNOME please select the following things from the menu:
System/Administration/Disks

Select the harddisk you can't access
click on the partition tab and tell me what it's written there.

2) I haven't tried 2.6.14.4 yet but did you try with another (older) version of the kernel?

anatole
December 16th, 2005, 01:19 PM
1) If you use GNOME please select the following things from the menu:
System/Administration/Disks

Select the harddisk you can't access
click on the partition tab and tell me what it's written there.

they differ from the working ones at the line "Status:" - it says inaccessible with hda1 and hda2; when i click one "enable" , nothing happens.


2) I haven't tried 2.6.14.4 yet but did you try with another (older) version of the kernel?

i didn't. i will try with 2.6.13, however, if i'll have the time (there would be no point for me in using kernel 2.6.12, as it does not support my raid), and if what i posted above doesn't help.

tseliot
December 16th, 2005, 02:16 PM
they differ from the working ones at the line "Status:" - it says inaccessible with hda1 and hda2; when i click one "enable" , nothing happens.



i didn't. i will try with 2.6.13, however, if i'll have the time (there would be no point for me in using kernel 2.6.12, as it does not support my raid), and if what i posted above doesn't help.
I have never used two harddisks using raid. Sorry for my ignorance in that field :(

For this reason I recommend you to start a new thread in the "Hardware Help" section

r4ik
December 16th, 2005, 02:19 PM
For tseliot.
I havent been able to install the kernel.
System just will not install it.(noob thing has nothing to do with the howto)
I managed to install the k7 (synaptic) and i will keep it for a while.
Thanks again for your time and maybe i will return to the
subject when i am more able to compile kernels.
r4ik.

anatole
December 16th, 2005, 02:19 PM
you misunderstood me, the hard drives are on one completely standard ide slot.
the raid support is needed for the cdrom drivers (there are only place on my motherboard there for them) and with the new kernel they work perfectly.

so, the funny thing is, the two hard drives are on the same slot, not raid but ide, and one works, another doesn't...

tseliot
December 16th, 2005, 02:53 PM
For tseliot.
I havent been able to install the kernel.
System just will not install it.(noob thing has nothing to do with the howto)
I managed to install the k7 (synaptic) and i will keep it for a while.
Thanks again for your time and maybe i will return to the
subject when i am more able to compile kernels.
r4ik.
Ok. I'm sure you will be able to do it in a near future.

Anyhow if you want to post the output of the error when you try to install the kernel I can try to help you.

tseliot
December 16th, 2005, 02:58 PM
you misunderstood me, the hard drives are on one completely standard ide slot.
the raid support is needed for the cdrom drivers (there are only place on my motherboard there for them) and with the new kernel they work perfectly.

so, the funny thing is, the two hard drives are on the same slot, not raid but ide, and one works, another doesn't...
Perhaps now that your Cd readers are enabled the system changed the "label" of the other harddisk so that your fstab can be reporting the wrong name of your harddisk.

Please post the output of the following command:
dmesg

anatole
December 16th, 2005, 03:03 PM
Perhaps now that your Cd readers are enabled the system changed the "label" of the other harddisk so that your fstab can be reporting the wrong name of your harddisk.

Please post the output of the following command:
dmesg

here it is:
attila@nanaki:~$ dmesg
ocate resource for EISA slot 8
[17179571.840000] EISA: Detected 0 cards.
[17179571.840000] NET: Registered protocol family 2
[17179572.488000] input: AT Translated Set 2 keyboard on isa0060/serio0
[17179572.500000] IP route cache hash table entries: 65536 (order: 6, 262144 bytes)
[17179572.500000] TCP established hash table entries: 262144 (order: 8, 1048576 bytes)
[17179572.500000] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[17179572.500000] TCP: Hash tables configured (established 262144 bind 65536)
[17179572.500000] TCP reno registered
[17179572.500000] TCP bic registered
[17179572.500000] NET: Registered protocol family 8
[17179572.500000] NET: Registered protocol family 20
[17179572.500000] Using IPI Shortcut mode
[17179572.500000] ACPI wakeup devices:
[17179572.500000] PCI0 PEX0 PEX1 PEX2 PEX3 PEX4 PEX5 HUB0 USB0 USB1 USB2 USB3 USBE AC97 MC97 AZAL
[17179572.500000] ACPI: (supports S0 S1 S4 S5)
[17179572.500000] Freeing unused kernel memory: 220k freed
[17179572.512000] vga16fb: initializing
[17179572.512000] vga16fb: mapped to 0xc00a0000
[17179572.728000] Console: switching to colour frame buffer device 80x30
[17179572.728000] fb0: VGA16 VGA frame buffer device
[17179573.892000] NET: Registered protocol family 1
[17179573.904000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[17179573.904000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[17179573.904000] ICH7: IDE controller at PCI slot 0000:00:1f.1
[17179573.904000] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 17
[17179573.904000] ICH7: chipset revision 1
[17179573.904000] ICH7: not 100% native mode: will probe irqs later
[17179573.904000] ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
[17179573.904000] ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
[17179573.904000] Probing IDE interface ide0...
[17179574.196000] hda: ST380021A, ATA DISK drive
[17179574.476000] hdb: SAMSUNG SP1604N, ATA DISK drive
[17179574.532000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[17179574.532000] Probing IDE interface ide1...
[17179575.108000] SCSI subsystem initialized
[17179575.108000] libata version 1.12 loaded.
[17179575.108000] ata_piix version 1.04
[17179575.108000] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 18
[17179575.108000] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[17179575.108000] ata1: SATA max UDMA/133 cmd 0xD000 ctl 0xD402 bmdma 0xE000 irq 18
[17179575.108000] ata2: SATA max UDMA/133 cmd 0xD800 ctl 0xDC02 bmdma 0xE008 irq 18
[17179575.272000] ATA: abnormal status 0x7F on port 0xD007
[17179575.272000] ata1: disabling port
[17179575.272000] scsi0 : ata_piix
[17179575.436000] ATA: abnormal status 0x7F on port 0xD807
[17179575.436000] ata2: disabling port
[17179575.436000] scsi1 : ata_piix
[17179575.440000] Probing IDE interface ide1...
[17179576.008000] hda: max request size: 128KiB
[17179576.008000] hda: Host Protected Area detected.
[17179576.008000] current capacity is 156299375 sectors (80025 MB)
[17179576.008000] native capacity is 156301488 sectors (80026 MB)
[17179576.008000] hda: Host Protected Area disabled.
[17179576.008000] hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
[17179576.008000] hda: cache flushes not supported
[17179576.008000] hda: hda1 hda2
[17179576.028000] hdb: max request size: 1024KiB
[17179576.036000] hdb: 312581808 sectors (160041 MB) w/2048KiB Cache, CHS=19457/255/63, UDMA(100)
[17179576.036000] hdb: cache flushes supported
[17179576.036000] hdb: hdb1 hdb2 hdb3 hdb4
[17179576.200000] Attempting manual resume
[17179576.232000] usbcore: registered new driver usbfs
[17179576.232000] usbcore: registered new driver hub
[17179576.232000] USB Universal Host Controller Interface driver v2.3
[17179576.232000] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 19
[17179576.232000] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[17179576.232000] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[17179576.232000] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[17179576.232000] uhci_hcd 0000:00:1d.0: irq 19, io base 0x0000bc00
[17179576.236000] hub 1-0:1.0: USB hub found
[17179576.236000] hub 1-0:1.0: 2 ports detected
[17179576.340000] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 18
[17179576.340000] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[17179576.340000] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[17179576.340000] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[17179576.340000] uhci_hcd 0000:00:1d.1: irq 18, io base 0x0000b000
[17179576.340000] hub 2-0:1.0: USB hub found
[17179576.340000] hub 2-0:1.0: 2 ports detected
[17179576.444000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 17
[17179576.444000] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[17179576.444000] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[17179576.444000] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[17179576.444000] uhci_hcd 0000:00:1d.2: irq 17, io base 0x0000b400
[17179576.444000] hub 3-0:1.0: USB hub found
[17179576.444000] hub 3-0:1.0: 2 ports detected
[17179576.548000] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16
[17179576.548000] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[17179576.548000] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[17179576.548000] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
[17179576.548000] uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000b800
[17179576.548000] hub 4-0:1.0: USB hub found
[17179576.548000] hub 4-0:1.0: 2 ports detected
[17179576.672000] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 19
[17179576.672000] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[17179576.672000] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[17179576.672000] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
[17179576.672000] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xe1104000
[17179576.676000] PCI: cache line size of 128 is not supported by device 0000:00:1d.7
[17179576.676000] ehci_hcd 0000:00:1d.7: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
[17179576.676000] hub 5-0:1.0: USB hub found
[17179576.676000] hub 5-0:1.0: 8 ports detected
[17179576.684000] usb 2-2: new full speed USB device using uhci_hcd and address 2
[17179576.820000] tg3.c:v3.42 (Oct 3, 2005)
[17179576.820000] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 18 (level, low) -> IRQ 17
[17179576.820000] PCI: Setting latency timer of device 0000:03:00.0 to 64
[17179576.844000] eth0: Tigon3 [partno(BCM95789) rev 4101 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:14:85:8a:42:9d
[17179576.844000] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
[17179576.844000] eth0: dma_rwctrl[76180000]
[17179577.244000] usb 5-4: new high speed USB device using ehci_hcd and address 2
[17179577.984000] usb 4-1: new low speed USB device using uhci_hcd and address 2
[17179578.380000] usb 4-2: new low speed USB device using uhci_hcd and address 3
[17179578.880000] usbcore: registered new driver hiddev
[17179578.896000] input: USB HID v1.10 Keyboard [1267:0103] on usb-0000:00:1d.3-1
[17179578.916000] input: USB HID v1.10 Device [1267:0103] on usb-0000:00:1d.3-1
[17179578.956000] input: USB HID v1.00 Mouse [1241:1166] on usb-0000:00:1d.3-2
[17179578.956000] usbcore: registered new driver usbhid
[17179578.956000] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[17179578.980000] Initializing USB Mass Storage driver...
[17179578.980000] scsi2 : SCSI emulation for USB Mass Storage devices
[17179578.980000] usb-storage: device found at 2
[17179578.980000] usb-storage: waiting for device to settle before scanning
[17179578.980000] usbcore: registered new driver usb-storage
[17179578.980000] USB Mass Storage support registered.
[17179579.288000] ACPI: CPU0 (power states: C1[C1])
[17179579.288000] ACPI: Processor [CPU0] (supports 2 throttling states)
[17179579.564000] Attempting manual resume
[17179579.580000] kjournald starting. Commit interval 5 seconds
[17179579.580000] EXT3-fs: mounted filesystem with ordered data mode.
[17179580.548000] md: md driver 0.90.2 MAX_MD_DEVS=256, MD_SB_DISKS=27
[17179580.548000] md: bitmap version 3.39
[17179583.188000] Adding 248968k swap on /dev/hdb1. Priority:-1 extents:1 across:248968k
[17179583.428000] EXT3 FS on hdb2, internal journal
[17179584.024000] Vendor: Apple Model: iPod Rev: 1.62
[17179584.024000] Type: Direct-Access ANSI SCSI revision: 00
[17179584.052000] usb-storage: device scan complete
[17179585.540000] parport: PnPBIOS parport detected.
[17179585.540000] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[17179585.640000] lp0: using parport0 (interrupt-driven).
[17179585.668000] SCSI device sda: 7999487 512-byte hdwr sectors (4096 MB)
[17179585.672000] sda: Write Protect is off
[17179585.672000] sda: Mode Sense: 64 00 00 08
[17179585.672000] sda: assuming drive cache: write through
[17179585.680000] mice: PS/2 mouse device common for all mice
[17179585.688000] SCSI device sda: 7999487 512-byte hdwr sectors (4096 MB)
[17179585.704000] sda: Write Protect is off
[17179585.704000] sda: Mode Sense: 64 00 00 08
[17179585.704000] sda: assuming drive cache: write through
[17179585.704000] sda: sda1 sda2
[17179586.680000] Attached scsi removable disk sda at scsi2, channel 0, id 0, lun 0
[17179589.816000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
[17179591.968000] device-mapper: dm-linear: Device lookup failed
[17179591.968000] device-mapper: error adding target to table
[17179591.976000] device-mapper: dm-linear: Device lookup failed
[17179591.976000] device-mapper: error adding target to table
[17179591.980000] device-mapper: dm-linear: Device lookup failed
[17179591.980000] device-mapper: error adding target to table
[17179591.988000] device-mapper: dm-linear: Device lookup failed
[17179591.988000] device-mapper: error adding target to table
[17179591.996000] device-mapper: dm-linear: Device lookup failed
[17179591.996000] device-mapper: error adding target to table
[17179591.996000] device-mapper: dm-linear: Device lookup failed
[17179591.996000] device-mapper: error adding target to table
[17179592.000000] device-mapper: dm-linear: Device lookup failed
[17179592.000000] device-mapper: error adding target to table
[17179592.000000] device-mapper: dm-linear: Device lookup failed
[17179592.000000] device-mapper: error adding target to table
[17179592.000000] device-mapper: dm-linear: Device lookup failed
[17179592.000000] device-mapper: error adding target to table
[17179592.004000] device-mapper: dm-linear: Device lookup failed
[17179592.004000] device-mapper: error adding target to table
[17179592.004000] device-mapper: dm-linear: Device lookup failed
[17179592.004000] device-mapper: error adding target to table
[17179592.004000] device-mapper: dm-linear: Device lookup failed
[17179592.004000] device-mapper: error adding target to table
[17179592.008000] device-mapper: dm-linear: Device lookup failed
[17179592.008000] device-mapper: error adding target to table
[17179592.008000] device-mapper: dm-linear: Device lookup failed
[17179592.008000] device-mapper: error adding target to table
[17179592.008000] device-mapper: dm-linear: Device lookup failed
[17179592.008000] device-mapper: error adding target to table
[17179592.012000] device-mapper: dm-linear: Device lookup failed
[17179592.012000] device-mapper: error adding target to table
[17179612.536000] NTFS driver 2.1.24 [Flags: R/O MODULE].
[17179612.552000] kjournald starting. Commit interval 5 seconds
[17179612.552000] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
[17179612.556000] EXT3 FS on hdb4, internal journal
[17179612.556000] EXT3-fs: mounted filesystem with ordered data mode.
[17179613.952000] Linux agpgart interface v0.101 (c) Dave Jones
[17179614.132000] agpgart: Detected an Intel 945G Chipset.
[17179614.148000] agpgart: AGP aperture is 256M @ 0x0
[17179614.392000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[17179614.640000] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[17179615.384000] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
[17179615.384000] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[17179616.100000] hw_random hardware driver 1.0.0 loaded
[17179616.508000] IT8212: IDE controller at PCI slot 0000:04:06.0
[17179616.508000] ACPI: PCI Interrupt 0000:04:06.0[A] -> GSI 22 (level, low) -> IRQ 20
[17179616.508000] IT8212: chipset revision 19
[17179616.508000] it821x: controller in pass through mode.
[17179616.508000] IT8212: 100% native mode on irq 20
[17179616.508000] ide2: BM-DMA at 0xa000-0xa007, BIOS settings: hde:pio, hdf:pio
[17179616.508000] ide3: BM-DMA at 0xa008-0xa00f, BIOS settings: hdg:pio, hdh:pio
[17179616.508000] Probing IDE interface ide2...
[17179617.244000] hde: HL-DT-STDVD-ROM GDR8163B, ATAPI CD/DVD-ROM drive
[17179618.028000] hdf: HL-DT-ST DVDRAM GSA-4160B, ATAPI CD/DVD-ROM drive
[17179618.084000] ide2 at 0x9010-0x9017,0x9402 on irq 20
[17179618.096000] Probing IDE interface ide3...
[17179620.244000] Real Time Clock Driver v1.12
[17179620.284000] input: PC Speaker
[17179620.524000] hde: ATAPI 52X DVD-ROM drive, 256kB Cache
[17179620.524000] Uniform CD-ROM driver Revision: 3.20
[17179620.604000] hdf: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
[17179621.044000] ts: Compaq touchscreen protocol output
[17179623.164000] tg3: eth0: Link is up at 100 Mbps, full duplex.
[17179623.164000] tg3: eth0: Flow control is on for TX and on for RX.
[17179623.928000] NET: Registered protocol family 10
[17179623.928000] Disabled Privacy Extensions on device c02cd820(lo)
[17179623.928000] IPv6 over IPv4 tunneling driver
[17179624.772000] ACPI: Power Button (FF) [PWRF]
[17179624.772000] ACPI: Power Button (CM) [PWRB]
[17179624.788000] Using specific hotkey driver
[17179624.824000] ibm_acpi: ec object not found
[17179624.848000] toshiba_acpi: Unknown parameter `hotkeys_over_acpi'
[17179632.392000] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[17179632.392000] apm: overridden by ACPI.
[17179633.792000] acpi-cpufreq: CPU0 - ACPI performance management activated.
[17179633.940000] eth0: no IPv6 routers present
[17179635.120000] Bluetooth: Core ver 2.7
[17179635.120000] NET: Registered protocol family 31
[17179635.120000] Bluetooth: HCI device and connection manager initialized
[17179635.120000] Bluetooth: HCI socket layer initialized
[17179635.152000] Bluetooth: L2CAP ver 2.7
[17179635.152000] Bluetooth: L2CAP socket layer initialized
[17179635.176000] Bluetooth: RFCOMM ver 1.5
[17179635.176000] Bluetooth: RFCOMM socket layer initialized
[17179635.176000] Bluetooth: RFCOMM TTY layer initialized
[17179651.356000] UDF-fs: No VRS found
[17179651.652000] ISO 9660 Extensions: Microsoft Joliet Level 3
[17179651.864000] ISOFS: changing to secondary root
[17179697.824000] Warning: /proc/ide/hd?/settings interface is obsolete, and will be removed soon!
[17179824.124000] cdrom: This disc doesn't have any tracks I recognize!
[17184892.468000] SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled
[17184892.468000] SGI XFS Quota Management subsystem
[17184892.488000] JFS: nTxBlock = 8099, nTxLock = 64796
[17185112.792000] UDF-fs: No VRS found
[17185112.816000] ISO 9660 Extensions: Microsoft Joliet Level 3
[17185113.044000] ISOFS: changing to secondary root

tseliot
December 16th, 2005, 03:24 PM
here it is:
attila@nanaki:~$ dmesg
ocate resource for EISA slot 8
[17179571.840000] EISA: Detected 0 cards.
[17179571.840000] NET: Registered protocol family 2
[17179572.488000] input: AT Translated Set 2 keyboard on isa0060/serio0
[17179572.500000] IP route cache hash table entries: 65536 (order: 6, 262144 bytes)
[17179572.500000] TCP established hash table entries: 262144 (order: 8, 1048576 bytes)
[17179572.500000] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[17179572.500000] TCP: Hash tables configured (established 262144 bind 65536)
[17179572.500000] TCP reno registered
[17179572.500000] TCP bic registered
[17179572.500000] NET: Registered protocol family 8
[17179572.500000] NET: Registered protocol family 20
[17179572.500000] Using IPI Shortcut mode
[17179572.500000] ACPI wakeup devices:
[17179572.500000] PCI0 PEX0 PEX1 PEX2 PEX3 PEX4 PEX5 HUB0 USB0 USB1 USB2 USB3 USBE AC97 MC97 AZAL
[17179572.500000] ACPI: (supports S0 S1 S4 S5)
[17179572.500000] Freeing unused kernel memory: 220k freed
[17179572.512000] vga16fb: initializing
[17179572.512000] vga16fb: mapped to 0xc00a0000
[17179572.728000] Console: switching to colour frame buffer device 80x30
[17179572.728000] fb0: VGA16 VGA frame buffer device
[17179573.892000] NET: Registered protocol family 1
[17179573.904000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[17179573.904000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[17179573.904000] ICH7: IDE controller at PCI slot 0000:00:1f.1
[17179573.904000] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 17
[17179573.904000] ICH7: chipset revision 1
[17179573.904000] ICH7: not 100% native mode: will probe irqs later
[17179573.904000] ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
[17179573.904000] ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
[17179573.904000] Probing IDE interface ide0...
[17179574.196000] hda: ST380021A, ATA DISK drive
[17179574.476000] hdb: SAMSUNG SP1604N, ATA DISK drive
[17179574.532000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[17179574.532000] Probing IDE interface ide1...
[17179575.108000] SCSI subsystem initialized
[17179575.108000] libata version 1.12 loaded.
[17179575.108000] ata_piix version 1.04
[17179575.108000] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 18
[17179575.108000] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[17179575.108000] ata1: SATA max UDMA/133 cmd 0xD000 ctl 0xD402 bmdma 0xE000 irq 18
[17179575.108000] ata2: SATA max UDMA/133 cmd 0xD800 ctl 0xDC02 bmdma 0xE008 irq 18
[17179575.272000] ATA: abnormal status 0x7F on port 0xD007
[17179575.272000] ata1: disabling port
[17179575.272000] scsi0 : ata_piix
[17179575.436000] ATA: abnormal status 0x7F on port 0xD807
[17179575.436000] ata2: disabling port
[17179575.436000] scsi1 : ata_piix
[17179575.440000] Probing IDE interface ide1...
[17179576.008000] hda: max request size: 128KiB
[17179576.008000] hda: Host Protected Area detected.
[17179576.008000] current capacity is 156299375 sectors (80025 MB)
[17179576.008000] native capacity is 156301488 sectors (80026 MB)
[17179576.008000] hda: Host Protected Area disabled.
[17179576.008000] hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
[17179576.008000] hda: cache flushes not supported
[17179576.008000] hda: hda1 hda2
[17179576.028000] hdb: max request size: 1024KiB
[17179576.036000] hdb: 312581808 sectors (160041 MB) w/2048KiB Cache, CHS=19457/255/63, UDMA(100)
[17179576.036000] hdb: cache flushes supported
[17179576.036000] hdb: hdb1 hdb2 hdb3 hdb4
[17179576.200000] Attempting manual resume
[17179576.232000] usbcore: registered new driver usbfs
[17179576.232000] usbcore: registered new driver hub
[17179576.232000] USB Universal Host Controller Interface driver v2.3
[17179576.232000] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 19
[17179576.232000] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[17179576.232000] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[17179576.232000] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[17179576.232000] uhci_hcd 0000:00:1d.0: irq 19, io base 0x0000bc00
[17179576.236000] hub 1-0:1.0: USB hub found
[17179576.236000] hub 1-0:1.0: 2 ports detected
[17179576.340000] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 18
[17179576.340000] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[17179576.340000] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[17179576.340000] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[17179576.340000] uhci_hcd 0000:00:1d.1: irq 18, io base 0x0000b000
[17179576.340000] hub 2-0:1.0: USB hub found
[17179576.340000] hub 2-0:1.0: 2 ports detected
[17179576.444000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 17
[17179576.444000] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[17179576.444000] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[17179576.444000] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[17179576.444000] uhci_hcd 0000:00:1d.2: irq 17, io base 0x0000b400
[17179576.444000] hub 3-0:1.0: USB hub found
[17179576.444000] hub 3-0:1.0: 2 ports detected
[17179576.548000] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16
[17179576.548000] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[17179576.548000] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[17179576.548000] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
[17179576.548000] uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000b800
[17179576.548000] hub 4-0:1.0: USB hub found
[17179576.548000] hub 4-0:1.0: 2 ports detected
[17179576.672000] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 19
[17179576.672000] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[17179576.672000] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[17179576.672000] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
[17179576.672000] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xe1104000
[17179576.676000] PCI: cache line size of 128 is not supported by device 0000:00:1d.7
[17179576.676000] ehci_hcd 0000:00:1d.7: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
[17179576.676000] hub 5-0:1.0: USB hub found
[17179576.676000] hub 5-0:1.0: 8 ports detected
[17179576.684000] usb 2-2: new full speed USB device using uhci_hcd and address 2
[17179576.820000] tg3.c:v3.42 (Oct 3, 2005)
[17179576.820000] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 18 (level, low) -> IRQ 17
[17179576.820000] PCI: Setting latency timer of device 0000:03:00.0 to 64
[17179576.844000] eth0: Tigon3 [partno(BCM95789) rev 4101 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:14:85:8a:42:9d
[17179576.844000] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
[17179576.844000] eth0: dma_rwctrl[76180000]
[17179577.244000] usb 5-4: new high speed USB device using ehci_hcd and address 2
[17179577.984000] usb 4-1: new low speed USB device using uhci_hcd and address 2
[17179578.380000] usb 4-2: new low speed USB device using uhci_hcd and address 3
[17179578.880000] usbcore: registered new driver hiddev
[17179578.896000] input: USB HID v1.10 Keyboard [1267:0103] on usb-0000:00:1d.3-1
[17179578.916000] input: USB HID v1.10 Device [1267:0103] on usb-0000:00:1d.3-1
[17179578.956000] input: USB HID v1.00 Mouse [1241:1166] on usb-0000:00:1d.3-2
[17179578.956000] usbcore: registered new driver usbhid
[17179578.956000] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[17179578.980000] Initializing USB Mass Storage driver...
[17179578.980000] scsi2 : SCSI emulation for USB Mass Storage devices
[17179578.980000] usb-storage: device found at 2
[17179578.980000] usb-storage: waiting for device to settle before scanning
[17179578.980000] usbcore: registered new driver usb-storage
[17179578.980000] USB Mass Storage support registered.
[17179579.288000] ACPI: CPU0 (power states: C1[C1])
[17179579.288000] ACPI: Processor [CPU0] (supports 2 throttling states)
[17179579.564000] Attempting manual resume
[17179579.580000] kjournald starting. Commit interval 5 seconds
[17179579.580000] EXT3-fs: mounted filesystem with ordered data mode.
[17179580.548000] md: md driver 0.90.2 MAX_MD_DEVS=256, MD_SB_DISKS=27
[17179580.548000] md: bitmap version 3.39
[17179583.188000] Adding 248968k swap on /dev/hdb1. Priority:-1 extents:1 across:248968k
[17179583.428000] EXT3 FS on hdb2, internal journal
[17179584.024000] Vendor: Apple Model: iPod Rev: 1.62
[17179584.024000] Type: Direct-Access ANSI SCSI revision: 00
[17179584.052000] usb-storage: device scan complete
[17179585.540000] parport: PnPBIOS parport detected.
[17179585.540000] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[17179585.640000] lp0: using parport0 (interrupt-driven).
[17179585.668000] SCSI device sda: 7999487 512-byte hdwr sectors (4096 MB)
[17179585.672000] sda: Write Protect is off
[17179585.672000] sda: Mode Sense: 64 00 00 08
[17179585.672000] sda: assuming drive cache: write through
[17179585.680000] mice: PS/2 mouse device common for all mice
[17179585.688000] SCSI device sda: 7999487 512-byte hdwr sectors (4096 MB)
[17179585.704000] sda: Write Protect is off
[17179585.704000] sda: Mode Sense: 64 00 00 08
[17179585.704000] sda: assuming drive cache: write through
[17179585.704000] sda: sda1 sda2
[17179586.680000] Attached scsi removable disk sda at scsi2, channel 0, id 0, lun 0
[17179589.816000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
[17179591.968000] device-mapper: dm-linear: Device lookup failed
[17179591.968000] device-mapper: error adding target to table
[17179591.976000] device-mapper: dm-linear: Device lookup failed
[17179591.976000] device-mapper: error adding target to table
[17179591.980000] device-mapper: dm-linear: Device lookup failed
[17179591.980000] device-mapper: error adding target to table
[17179591.988000] device-mapper: dm-linear: Device lookup failed
[17179591.988000] device-mapper: error adding target to table
[17179591.996000] device-mapper: dm-linear: Device lookup failed
[17179591.996000] device-mapper: error adding target to table
[17179591.996000] device-mapper: dm-linear: Device lookup failed
[17179591.996000] device-mapper: error adding target to table
[17179592.000000] device-mapper: dm-linear: Device lookup failed
[17179592.000000] device-mapper: error adding target to table
[17179592.000000] device-mapper: dm-linear: Device lookup failed
[17179592.000000] device-mapper: error adding target to table
[17179592.000000] device-mapper: dm-linear: Device lookup failed
[17179592.000000] device-mapper: error adding target to table
[17179592.004000] device-mapper: dm-linear: Device lookup failed
[17179592.004000] device-mapper: error adding target to table
[17179592.004000] device-mapper: dm-linear: Device lookup failed
[17179592.004000] device-mapper: error adding target to table
[17179592.004000] device-mapper: dm-linear: Device lookup failed
[17179592.004000] device-mapper: error adding target to table
[17179592.008000] device-mapper: dm-linear: Device lookup failed
[17179592.008000] device-mapper: error adding target to table
[17179592.008000] device-mapper: dm-linear: Device lookup failed
[17179592.008000] device-mapper: error adding target to table
[17179592.008000] device-mapper: dm-linear: Device lookup failed
[17179592.008000] device-mapper: error adding target to table
[17179592.012000] device-mapper: dm-linear: Device lookup failed
[17179592.012000] device-mapper: error adding target to table
[17179612.536000] NTFS driver 2.1.24 [Flags: R/O MODULE].
[17179612.552000] kjournald starting. Commit interval 5 seconds
[17179612.552000] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
[17179612.556000] EXT3 FS on hdb4, internal journal
[17179612.556000] EXT3-fs: mounted filesystem with ordered data mode.
[17179613.952000] Linux agpgart interface v0.101 (c) Dave Jones
[17179614.132000] agpgart: Detected an Intel 945G Chipset.
[17179614.148000] agpgart: AGP aperture is 256M @ 0x0
[17179614.392000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[17179614.640000] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[17179615.384000] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
[17179615.384000] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[17179616.100000] hw_random hardware driver 1.0.0 loaded
[17179616.508000] IT8212: IDE controller at PCI slot 0000:04:06.0
[17179616.508000] ACPI: PCI Interrupt 0000:04:06.0[A] -> GSI 22 (level, low) -> IRQ 20
[17179616.508000] IT8212: chipset revision 19
[17179616.508000] it821x: controller in pass through mode.
[17179616.508000] IT8212: 100% native mode on irq 20
[17179616.508000] ide2: BM-DMA at 0xa000-0xa007, BIOS settings: hde:pio, hdf:pio
[17179616.508000] ide3: BM-DMA at 0xa008-0xa00f, BIOS settings: hdg:pio, hdh:pio
[17179616.508000] Probing IDE interface ide2...
[17179617.244000] hde: HL-DT-STDVD-ROM GDR8163B, ATAPI CD/DVD-ROM drive
[17179618.028000] hdf: HL-DT-ST DVDRAM GSA-4160B, ATAPI CD/DVD-ROM drive
[17179618.084000] ide2 at 0x9010-0x9017,0x9402 on irq 20
[17179618.096000] Probing IDE interface ide3...
[17179620.244000] Real Time Clock Driver v1.12
[17179620.284000] input: PC Speaker
[17179620.524000] hde: ATAPI 52X DVD-ROM drive, 256kB Cache
[17179620.524000] Uniform CD-ROM driver Revision: 3.20
[17179620.604000] hdf: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
[17179621.044000] ts: Compaq touchscreen protocol output
[17179623.164000] tg3: eth0: Link is up at 100 Mbps, full duplex.
[17179623.164000] tg3: eth0: Flow control is on for TX and on for RX.
[17179623.928000] NET: Registered protocol family 10
[17179623.928000] Disabled Privacy Extensions on device c02cd820(lo)
[17179623.928000] IPv6 over IPv4 tunneling driver
[17179624.772000] ACPI: Power Button (FF) [PWRF]
[17179624.772000] ACPI: Power Button (CM) [PWRB]
[17179624.788000] Using specific hotkey driver
[17179624.824000] ibm_acpi: ec object not found
[17179624.848000] toshiba_acpi: Unknown parameter `hotkeys_over_acpi'
[17179632.392000] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[17179632.392000] apm: overridden by ACPI.
[17179633.792000] acpi-cpufreq: CPU0 - ACPI performance management activated.
[17179633.940000] eth0: no IPv6 routers present
[17179635.120000] Bluetooth: Core ver 2.7
[17179635.120000] NET: Registered protocol family 31
[17179635.120000] Bluetooth: HCI device and connection manager initialized
[17179635.120000] Bluetooth: HCI socket layer initialized
[17179635.152000] Bluetooth: L2CAP ver 2.7
[17179635.152000] Bluetooth: L2CAP socket layer initialized
[17179635.176000] Bluetooth: RFCOMM ver 1.5
[17179635.176000] Bluetooth: RFCOMM socket layer initialized
[17179635.176000] Bluetooth: RFCOMM TTY layer initialized
[17179651.356000] UDF-fs: No VRS found
[17179651.652000] ISO 9660 Extensions: Microsoft Joliet Level 3
[17179651.864000] ISOFS: changing to secondary root
[17179697.824000] Warning: /proc/ide/hd?/settings interface is obsolete, and will be removed soon!
[17179824.124000] cdrom: This disc doesn't have any tracks I recognize!
[17184892.468000] SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled
[17184892.468000] SGI XFS Quota Management subsystem
[17184892.488000] JFS: nTxBlock = 8099, nTxLock = 64796
[17185112.792000] UDF-fs: No VRS found
[17185112.816000] ISO 9660 Extensions: Microsoft Joliet Level 3
[17185113.044000] ISOFS: changing to secondary root

Another question:
Did you patch the kernel (if yes, specify which)?

anatole
December 16th, 2005, 03:27 PM
Another question:
Did you patch the kernel (if yes, specify which)?

no. to be honest i didn't quite understand why would i want to patch the newest stable kernel :) this was my first kernel compilation afterall.

tseliot
December 16th, 2005, 03:33 PM
no. to be honest i didn't quite understand why would i want to patch the newest stable kernel :) this was my first kernel compilation afterall.
Kolivas patches contain improvements. Please try the patch (yes, delete the folder with the kernel source you used and recompile your kernel from scratch, follow the guide), it might solve your problem

anatole
December 16th, 2005, 05:05 PM
Kolivas patches contain improvements. Please try the patch (yes, delete the folder with the kernel source you used and recompile your kernel from scratch, follow the guide), it might solve your problem
tried it. the patching (both with ck3 and ck7, i tried those) makes errors, then so the kernel complilng... :/

tseliot
December 16th, 2005, 05:17 PM
tried it. the patching (both with ck3 and ck7, i tried those) makes errors, then so the kernel complilng... :/
I know, I apologise for not mentioning a little detail:
If you need to use Kolivas Patch you have to apply it to kernel 2.6.14 (not on 2.6.14.4) because the patch already contains the improvements of the latest version.

In other words:
1) Download the following patch http://ck.kolivas.org/patches/2.6/2.6.14/2.6.14-ck7/patch-2.6.14-ck7.bz2

2) Download the kernel source: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.14.tar.bz2


and try again

anatole
December 16th, 2005, 06:01 PM
I know, I apologise for not mentioning a little detail:
If you need to use Kolivas Patch you have to apply it to kernel 2.6.14 (not on 2.6.14.4) because the patch already contains the improvements of the latest version.

In other words:
1) Download the following patch http://ck.kolivas.org/patches/2.6/2.6.14/2.6.14-ck7/patch-2.6.14-ck7.bz2

2) Download the kernel source: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.14.tar.bz2


and try again


it fails with:
kernel/resource.c:480: warning: '__check_region' is deprecated (declared at kernel/resource.c:468)
CC kernel/sysctl.o
kernel/sysctl.c: In function 'register_proc_table':
kernel/sysctl.c:1413: error: 'struct proc_dir_entry' has no member named 'set'
kernel/sysctl.c: In function 'do_rw_proc':
kernel/sysctl.c:1471: error: 'struct proc_dir_entry' has no member named 'set'
kernel/sysctl.c:1493: error: 'struct proc_dir_entry' has no member named 'set'
make[2]: *** [kernel/sysctl.o] Error 1
make[1]: *** [kernel] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.14'
make: *** [stamp-build] Error 2

tseliot
December 16th, 2005, 06:12 PM
it fails with:
kernel/resource.c:480: warning: '__check_region' is deprecated (declared at kernel/resource.c:468)
CC kernel/sysctl.o
kernel/sysctl.c: In function 'register_proc_table':
kernel/sysctl.c:1413: error: 'struct proc_dir_entry' has no member named 'set'
kernel/sysctl.c: In function 'do_rw_proc':
kernel/sysctl.c:1471: error: 'struct proc_dir_entry' has no member named 'set'
kernel/sysctl.c:1493: error: 'struct proc_dir_entry' has no member named 'set'
make[2]: *** [kernel/sysctl.o] Error 1
make[1]: *** [kernel] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.14'
make: *** [stamp-build] Error 2

Weird...
Can you post the output of "lspci" and "lsmod"?

anatole
December 16th, 2005, 06:17 PM
Weird...
Can you post the output of "lspci" and "lsmod"?
lspci:
0000:00:00.0 Host bridge: Intel Corp.: Unknown device 2770 (rev 81)
0000:00:01.0 PCI bridge: Intel Corp.: Unknown device 2771 (rev 81)
0000:00:1b.0 0403: Intel Corp.: Unknown device 27d8 (rev 01)
0000:00:1c.0 PCI bridge: Intel Corp.: Unknown device 27d0 (rev 01)
0000:00:1c.2 PCI bridge: Intel Corp.: Unknown device 27d4 (rev 01)
0000:00:1d.0 USB Controller: Intel Corp.: Unknown device 27c8 (rev 01)
0000:00:1d.1 USB Controller: Intel Corp.: Unknown device 27c9 (rev 01)
0000:00:1d.2 USB Controller: Intel Corp.: Unknown device 27ca (rev 01)
0000:00:1d.3 USB Controller: Intel Corp.: Unknown device 27cb (rev 01)
0000:00:1d.7 USB Controller: Intel Corp.: Unknown device 27cc (rev 01)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev e1)
0000:00:1f.0 ISA bridge: Intel Corp.: Unknown device 27b8 (rev 01)
0000:00:1f.1 IDE interface: Intel Corp.: Unknown device 27df (rev 01)
0000:00:1f.2 IDE interface: Intel Corp.: Unknown device 27c0 (rev 01)
0000:00:1f.3 SMBus: Intel Corp.: Unknown device 27da (rev 01)
0000:01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 014f (rev a2)
0000:03:00.0 Ethernet controller: Broadcom Corporation: Unknown device 169d (rev 11)
0000:04:06.0 Unknown mass storage controller: Integrated Technology Express, Inc. IT/ITE8212 Dual channel ATA RAID controller (PCI version seems to be IT8212, embedded seems (rev 13)

lsmod:
bluetooth 41988 4 rfcomm,l2cap
acpi_cpufreq 6664 1
cpufreq_userspace 4444 1
cpufreq_stats 5124 0
freq_table 4484 2 acpi_cpufreq,cpufreq_stats
cpufreq_powersave 1920 0
cpufreq_ondemand 6172 0
cpufreq_conservative 6948 0
video 16260 0
button 6672 0
battery 9732 0
container 4608 0
ac 4996 0
ipv6 220032 14
tsdev 7232 0
ide_cd 36996 1
cdrom 33568 1 ide_cd
pcspkr 3680 0
rtc 11704 1 snd_rtctimer
it821x 8068 0 [permanent]
tpm_atmel 5760 0
tpm_nsc 6528 0
tpm 9632 2 tpm_atmel,tpm_nsc
hw_random 5268 0
snd_hda_intel 16640 4
snd_hda_codec 77056 1 snd_hda_intel
snd_pcm_oss 45856 0
snd_mixer_oss 16000 2 snd_pcm_oss
snd_pcm 77832 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_page_alloc 10248 2 snd_hda_intel,snd_pcm
shpchp 80740 0
pci_hotplug 24756 1 shpchp
intel_agp 21148 1
agpgart 31688 1 intel_agp
ntfs 86896 0
nls_iso8859_1 4224 1
nls_cp437 5888 2
vfat 11904 1
fat 46364 1 vfat
dm_mod 49980 1
snd_seq_dummy 3844 0
snd_seq_oss 29056 0
snd_seq_midi 8608 0
snd_rawmidi 22432 1 snd_seq_midi
snd_seq_midi_event 6656 2 snd_seq_oss,snd_seq_midi
snd_seq 44304 7 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 21636 4 snd_rtctimer,snd_pcm,snd_seq
snd_seq_device 8204 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
snd 47460 15 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
soundcore 9184 2 snd
psmouse 33156 0
mousedev 10528 1
sd_mod 16784 1
parport_pc 32324 1
lp 10820 0
parport 31944 2 parport_pc,lp
md_mod 56656 0
thermal 13576 0
processor 23100 2 acpi_cpufreq,thermal
fan 4868 0
usb_storage 64704 2
usbhid 31968 0
tg3 88580 0
ehci_hcd 29832 0
uhci_hcd 28304 0
usbcore 105600 5 usb_storage,usbhid,ehci_hcd,uhci_hcd
ide_disk 16256 6
ide_generic 1408 0 [permanent]
ata_piix 9092 0
libata 43784 1 ata_piix
scsi_mod 126312 3 sd_mod,usb_storage,libata
piix 9220 0 [permanent]
generic 4612 0 [permanent]
ide_core 112480 7 ide_cd,it821x,usb_storage,ide_disk,ide_generic,pii x,generic
unix 24496 314
vga16fb 11848 1
vgastate 8320 1 vga16fb
softcursor 2304 1 vga16fb
cfbimgblt 3072 1 vga16fb
cfbfillrect 3840 1 vga16fb
cfbcopyarea 3584 1 vga16fb
fbcon 35712 72
tileblit 2432 1 fbcon
font 8320 1 fbcon
bitblit 4992 1 fbcon

thanks for all the effort by the way :)

tseliot
December 17th, 2005, 05:45 AM
lspci:
0000:00:00.0 Host bridge: Intel Corp.: Unknown device 2770 (rev 81)
0000:00:01.0 PCI bridge: Intel Corp.: Unknown device 2771 (rev 81)
0000:00:1b.0 0403: Intel Corp.: Unknown device 27d8 (rev 01)
0000:00:1c.0 PCI bridge: Intel Corp.: Unknown device 27d0 (rev 01)
0000:00:1c.2 PCI bridge: Intel Corp.: Unknown device 27d4 (rev 01)
0000:00:1d.0 USB Controller: Intel Corp.: Unknown device 27c8 (rev 01)
0000:00:1d.1 USB Controller: Intel Corp.: Unknown device 27c9 (rev 01)
0000:00:1d.2 USB Controller: Intel Corp.: Unknown device 27ca (rev 01)
0000:00:1d.3 USB Controller: Intel Corp.: Unknown device 27cb (rev 01)
0000:00:1d.7 USB Controller: Intel Corp.: Unknown device 27cc (rev 01)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev e1)
0000:00:1f.0 ISA bridge: Intel Corp.: Unknown device 27b8 (rev 01)
0000:00:1f.1 IDE interface: Intel Corp.: Unknown device 27df (rev 01)
0000:00:1f.2 IDE interface: Intel Corp.: Unknown device 27c0 (rev 01)
0000:00:1f.3 SMBus: Intel Corp.: Unknown device 27da (rev 01)
0000:01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 014f (rev a2)
0000:03:00.0 Ethernet controller: Broadcom Corporation: Unknown device 169d (rev 11)
0000:04:06.0 Unknown mass storage controller: Integrated Technology Express, Inc. IT/ITE8212 Dual channel ATA RAID controller (PCI version seems to be IT8212, embedded seems (rev 13)

lsmod:
bluetooth 41988 4 rfcomm,l2cap
acpi_cpufreq 6664 1
cpufreq_userspace 4444 1
cpufreq_stats 5124 0
freq_table 4484 2 acpi_cpufreq,cpufreq_stats
cpufreq_powersave 1920 0
cpufreq_ondemand 6172 0
cpufreq_conservative 6948 0
video 16260 0
button 6672 0
battery 9732 0
container 4608 0
ac 4996 0
ipv6 220032 14
tsdev 7232 0
ide_cd 36996 1
cdrom 33568 1 ide_cd
pcspkr 3680 0
rtc 11704 1 snd_rtctimer
it821x 8068 0 [permanent]
tpm_atmel 5760 0
tpm_nsc 6528 0
tpm 9632 2 tpm_atmel,tpm_nsc
hw_random 5268 0
snd_hda_intel 16640 4
snd_hda_codec 77056 1 snd_hda_intel
snd_pcm_oss 45856 0
snd_mixer_oss 16000 2 snd_pcm_oss
snd_pcm 77832 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_page_alloc 10248 2 snd_hda_intel,snd_pcm
shpchp 80740 0
pci_hotplug 24756 1 shpchp
intel_agp 21148 1
agpgart 31688 1 intel_agp
ntfs 86896 0
nls_iso8859_1 4224 1
nls_cp437 5888 2
vfat 11904 1
fat 46364 1 vfat
dm_mod 49980 1
snd_seq_dummy 3844 0
snd_seq_oss 29056 0
snd_seq_midi 8608 0
snd_rawmidi 22432 1 snd_seq_midi
snd_seq_midi_event 6656 2 snd_seq_oss,snd_seq_midi
snd_seq 44304 7 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
snd_timer 21636 4 snd_rtctimer,snd_pcm,snd_seq
snd_seq_device 8204 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
snd 47460 15 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
soundcore 9184 2 snd
psmouse 33156 0
mousedev 10528 1
sd_mod 16784 1
parport_pc 32324 1
lp 10820 0
parport 31944 2 parport_pc,lp
md_mod 56656 0
thermal 13576 0
processor 23100 2 acpi_cpufreq,thermal
fan 4868 0
usb_storage 64704 2
usbhid 31968 0
tg3 88580 0
ehci_hcd 29832 0
uhci_hcd 28304 0
usbcore 105600 5 usb_storage,usbhid,ehci_hcd,uhci_hcd
ide_disk 16256 6
ide_generic 1408 0 [permanent]
ata_piix 9092 0
libata 43784 1 ata_piix
scsi_mod 126312 3 sd_mod,usb_storage,libata
piix 9220 0 [permanent]
generic 4612 0 [permanent]
ide_core 112480 7 ide_cd,it821x,usb_storage,ide_disk,ide_generic,pii x,generic
unix 24496 314
vga16fb 11848 1
vgastate 8320 1 vga16fb
softcursor 2304 1 vga16fb
cfbimgblt 3072 1 vga16fb
cfbfillrect 3840 1 vga16fb
cfbcopyarea 3584 1 vga16fb
fbcon 35712 72
tileblit 2432 1 fbcon
font 8320 1 fbcon
bitblit 4992 1 fbcon

thanks for all the effort by the way :)
Unless I'm missing something I guess everything's ok.
I can only ask you 2 things:
1) Have a look at your bios and see if all the devices are detected (but I think they are)
2) Start a new thread in the "Hardware help" section because I have never experienced your problem therefore I can't think of a solution.

Rob2687
December 17th, 2005, 02:41 PM
If you need to use Kolivas Patch you have to apply it to kernel 2.6.14 (not on 2.6.14.4) because the patch already contains the improvements of the latest version.

You should mention that specifically in the guide. I remember the first few times I tried to compile with those patches I had that problem until I read it on another forum.

tseliot
December 17th, 2005, 03:51 PM
You should mention that specifically in the guide. I remember the first few times I tried to compile with those patches I had that problem until I read it on another forum.
I know, I did that yesterday

MichaelM
December 17th, 2005, 04:20 PM
Question:
Is there any advantage (speed or otherwise) to compiling things (like drivers which aren't needed in the bootstrap process) directly into the kernel instead of as modules?

tseliot
December 17th, 2005, 04:37 PM
Question:
Is there any advantage (speed or otherwise) to compiling things (like drivers which aren't needed in the bootstrap process) directly into the kernel instead of as modules?
Perhaps it can increase the speed of the kernel compilation. If you want a real speed boost (shorter boot times) you can disable the support for all the drivers which are not relevant to your configuration (e.g. disable the support for chipsets of other motherboards, etc.)

ubuntu4everyone
December 18th, 2005, 07:04 AM
Ok, i followed this tutorial and its great, so i made a script to do it all for us, just set the execute permission and in terminal when you are in the directory of the script type ./tweak. This is designed tu be run as a su'ed root, for exalmple

user@ubuntu$su
root@ubuntu$./tweak

by the way whay when you download this rename it from .txt to .sh

hope this helps.

:) :cool:

tseliot
December 18th, 2005, 07:54 AM
Ok, i followed this tutorial and its great, so i made a script to do it all for us, just set the execute permission and in terminal when you are in the directory of the script type ./tweak. This is designed tu be run as a su'ed root, for exalmple

user@ubuntu$su
root@ubuntu$./tweak

by the way whay when you download this rename it from .txt to .sh

hope this helps.

:) :cool:
Ok, that's a nice script but ,you know, I have two suggestions:
1) This line... :
sudo make-kpkg --initrd --append-to-version=-tweaked_image kernel_headers modules_image

...shouldn't be like the following?
sudo make-kpkg --initrd --append-to-version=-tweaked kernel_image kernel_headers modules_image

I don't know if it's the same (but maybe I'm wrong).

2) This suggestion is thought just to bother you ;) :
Could you add the possibility to download the nvidia kernel source (make the users choose between "nvidia" and "nvidia-legacy") and to extract it.
The "modules_image" in the command in point 1 will do the rest.

3) I can't program (never tried but I can learn) therefore I have to ask you the following things (I have some projects on my mind):
a) How did you do the script?
b) Which programming language should I learn in order to do scripts like yours (yes I am that ignorant :p )?
c) Could you address me to a good guide?

ubuntu4everyone
December 18th, 2005, 09:18 AM
Ok, that's a nice script but ,you know, I have two suggestions:
1) This line... :
sudo make-kpkg --initrd --append-to-version=-tweaked_image kernel_headers modules_image

...shouldn't be like the following?
sudo make-kpkg --initrd --append-to-version=-tweaked kernel_image kernel_headers modules_image

I don't know if it's the same (but maybe I'm wrong).

2) This suggestion is thought just to bother you ;) :
Could you add the possibility to download the nvidia kernel source (make the users choose between "nvidia" and "nvidia-legacy") and to extract it.
The "modules_image" in the command in point 1 will do the rest.

3) I can't program (never tried but I can learn) therefore I have to ask you the following things (I have some projects on my mind):
a) How did you do the script?
b) Which programming language should I learn in order to do scripts like yours (yes I am that ignorant :p )?
c) Could you address me to a good guide?

Hi,
I checked the program, and the current code is fine, also in regards to the nvida idea i will try, but i am still learning shell script. so i will learn more and then add it

the language i am using is called shell scripting, this is a good tut : http://www.freeos.com/guides/lsst/

hope this helps

tseliot
December 18th, 2005, 09:49 AM
thanks :)

Cuppa-Chino
December 18th, 2005, 02:10 PM
hi, just short question:

@ubuntu:~$ sudo apt-get install libncurses5
Reading package lists... Done
Building dependency tree... Done
libncurses5 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
johnny@ubuntu:~$ sudo apt-get install libncurses5-dev
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libncurses5-dev: Depends: libncurses5 (= 5.4-9ubuntu4) but 5.5-1ubuntu2 is to be installed
E: Broken packages


shall I force the installation despite not having a match between the two versions?
thx

tseliot
December 18th, 2005, 03:49 PM
hi, just short question:

@ubuntu:~$ sudo apt-get install libncurses5
Reading package lists... Done
Building dependency tree... Done
libncurses5 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
johnny@ubuntu:~$ sudo apt-get install libncurses5-dev
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libncurses5-dev: Depends: libncurses5 (= 5.4-9ubuntu4) but 5.5-1ubuntu2 is to be installed
E: Broken packages


shall I force the installation despite not having a match between the two versions?
thx
please post your /etc/apt/sources.list

Cuppa-Chino
December 18th, 2005, 04:11 PM
please post your /etc/apt/sources.list

here goes:
#deb cdrom:[Ubuntu 6.04 _Dapper Drake_ - Alpha i386 (20051214)]/ dapper main restricted
deb-src http://archive.ubuntu.com/ubuntu breezy main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://archive.ubuntu.com/ubuntu breezy-updates main restricted
deb-src http://archive.ubuntu.com/ubuntu breezy-updates main restricted

## Uncomment the following two lines to add software from the 'universe'
## repository.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## universe WILL NOT receive any review or updates from the Ubuntu security
## team.
deb-src http://archive.ubuntu.com/ubuntu breezy universe

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu breezy-security main restricted
deb-src http://security.ubuntu.com/ubuntu breezy-security main restricted

deb http://security.ubuntu.com/ubuntu breezy-security universe
deb-src http://security.ubuntu.com/ubuntu breezy-security universe

deb http://archive.ubuntu.com/ubuntu/ breezy universe main restricted multiverse

deb http://wine.sourceforge.net/apt/ binary/

deb http://public.planetmirror.com/pub/plf/ubuntu/plf/ breezy free non-free

deb ftp://ftp.free.fr/pub/Distributions_Linux/plf/ubuntu/plf/ breezy free non-free
deb-src ftp://ftp.free.fr/pub/Distributions_Linux/plf/ubuntu/plf/ breezy free non-free

deb http://deb.opera.com/opera/ etch non-free
## deb http://seveas.ubuntulinux.nl/ breezy-seveas breezy-backports breezy-custom breezy-extras freenx madwifi
## deb-src http://seveas.ubuntulinux.nl/ breezy-seveas breezy-backports breezy-custom breezy-extras freenx madwifi

deb http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse
deb http://ubuntu-backports.mirrormax.net/ breezy-extras main restricted universe multiverse
## created by arniebackports


tried creating with the wrong version but that did not work:
johnny@ubuntu:/usr/src/linux$ sudo make menuconfig HOSTLD scripts/kconfig/mconf
/usr/bin/ld: cannot find -lncurses
collect2: ld returned 1 exit status

>> Unable to find the Ncurses libraries.
>>
>> You must install ncurses-devel in order
>> to use 'make menuconfig'

make[2]: *** [scripts/lxdialog/ncurses] Error 1
make[1]: *** [menuconfig] Error 2
make: *** [menuconfig] Error 2

tseliot
December 18th, 2005, 04:31 PM
here goes:
#deb cdrom:[Ubuntu 6.04 _Dapper Drake_ - Alpha i386 (20051214)]/ dapper main restricted
deb-src http://archive.ubuntu.com/ubuntu breezy main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://archive.ubuntu.com/ubuntu breezy-updates main restricted
deb-src http://archive.ubuntu.com/ubuntu breezy-updates main restricted

## Uncomment the following two lines to add software from the 'universe'
## repository.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## universe WILL NOT receive any review or updates from the Ubuntu security
## team.
deb-src http://archive.ubuntu.com/ubuntu breezy universe

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu breezy-security main restricted
deb-src http://security.ubuntu.com/ubuntu breezy-security main restricted

deb http://security.ubuntu.com/ubuntu breezy-security universe
deb-src http://security.ubuntu.com/ubuntu breezy-security universe

deb http://archive.ubuntu.com/ubuntu/ breezy universe main restricted multiverse

deb http://wine.sourceforge.net/apt/ binary/

deb http://public.planetmirror.com/pub/plf/ubuntu/plf/ breezy free non-free

deb ftp://ftp.free.fr/pub/Distributions_Linux/plf/ubuntu/plf/ breezy free non-free
deb-src ftp://ftp.free.fr/pub/Distributions_Linux/plf/ubuntu/plf/ breezy free non-free

deb http://deb.opera.com/opera/ etch non-free
## deb http://seveas.ubuntulinux.nl/ breezy-seveas breezy-backports breezy-custom breezy-extras freenx madwifi
## deb-src http://seveas.ubuntulinux.nl/ breezy-seveas breezy-backports breezy-custom breezy-extras freenx madwifi

deb http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse
deb http://ubuntu-backports.mirrormax.net/ breezy-extras main restricted universe multiverse
## created by arniebackports


tried creating with the wrong version but that did not work:
johnny@ubuntu:/usr/src/linux$ sudo make menuconfig HOSTLD scripts/kconfig/mconf
/usr/bin/ld: cannot find -lncurses
collect2: ld returned 1 exit status

>> Unable to find the Ncurses libraries.
>>
>> You must install ncurses-devel in order
>> to use 'make menuconfig'

make[2]: *** [scripts/lxdialog/ncurses] Error 1
make[1]: *** [menuconfig] Error 2
make: *** [menuconfig] Error 2

1)You should not keep the backports enabled all the time. Comment out the backports and anything which is other than the official repositories.

2)Anyhow, why do you have this line?
#deb cdrom:[Ubuntu 6.04 _Dapper Drake_ - Alpha i386 (20051214)]/ dapper main rest

Cuppa-Chino
December 18th, 2005, 04:41 PM
1)You should not keep the backports enabled all the time. Comment out the backports and anything which is other than the official repositories.

2)Anyhow, why do you have this line?
#deb cdrom:[Ubuntu 6.04 _Dapper Drake_ - Alpha i386 (20051214)]/ dapper main rest

1) did that does not change anything still have libncurses 5.5.1 & still get:
libncurses5-dev:
Depends: libncurses5 (=5.4-9ubuntu4) but 5.5-1ubuntu2 is to be installed

2) had a dapper CD in the drive and that is how that got there

please help me

tseliot
December 18th, 2005, 05:09 PM
1) did that does not change anything still have libncurses 5.5.1 & still get:
libncurses5-dev:
Depends: libncurses5 (=5.4-9ubuntu4) but 5.5-1ubuntu2 is to be installed

2) had a dapper CD in the drive and that is how that got there

please help me
Ok, make your sources.list look EXACTLY like mine:
deb-src http://archive.ubuntu.com/ubuntu breezy main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://archive.ubuntu.com/ubuntu breezy-updates main restricted
deb-src http://archive.ubuntu.com/ubuntu breezy-updates main restricted

## Uncomment the following two lines to add software from the 'universe'
## repository.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## universe WILL NOT receive any review or updates from the Ubuntu security
## team.
deb-src http://archive.ubuntu.com/ubuntu breezy universe

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
## deb http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse
## deb-src http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu breezy-security main restricted
deb-src http://security.ubuntu.com/ubuntu breezy-security main restricted

deb http://security.ubuntu.com/ubuntu breezy-security universe
deb-src http://security.ubuntu.com/ubuntu breezy-security universe

deb http://archive.ubuntu.com/ubuntu/ breezy universe main restricted multiverse

Then uninstall libncurses5-dev (i.e. "Mark it for Complete Removal in Synaptics") if you already have it

And force the installation of the libncurses you need
sudo apt-get install --force-overwrite libncurses5 libncurses5-dev

Cuppa-Chino
December 18th, 2005, 05:14 PM
sorry to be a pain but:

@ubuntu:~$ sudo apt-get install -force-overwrite libncurses5 libncurses5-dev
E: Option -force-overwrite: Configuration item specification must have an =<val>.


is what is happening for me

tseliot
December 18th, 2005, 05:37 PM
sorry to be a pain but:

@ubuntu:~$ sudo apt-get install -force-overwrite libncurses5
E: Option -force-overwrite: Configuration item specification must have an =<val>.


is what is happening for me
EDIT:Ok, try this

sudo apt-get install -force-downgrade libncurses5 [5.4-9]

Cuppa-Chino
December 18th, 2005, 06:04 PM
still no luck...

@ubuntu:~$ sudo apt-get install -force-overwrite libncurses5
E: Option -force-overwrite: Configuration item specification must have an =<val>.
@ubuntu:~$
@ubuntu:~$ sudo apt-get install -force-downgrade libncurses5 [5.4-9]
E: Option -force-downgrade: Configuration item specification must have an =<val>.

tseliot
December 18th, 2005, 06:29 PM
still no luck...

@ubuntu:~$ sudo apt-get install -force-overwrite libncurses5
E: Option -force-overwrite: Configuration item specification must have an =<val>.
@ubuntu:~$
@ubuntu:~$ sudo apt-get install -force-downgrade libncurses5 [5.4-9]
E: Option -force-downgrade: Configuration item specification must have an =<val>.

Ok, I've never done that. I'll look for a solution using google.
I'll let you know

tseliot
December 18th, 2005, 06:38 PM
Try this:

sudo apt-get install -force-overwrite libncurses5=5.4-9ubuntu4

EDIT: if it doesn't work you have to open Synaptic select "Edit" and then "Fix Broken Packages" then click on the "Apply button"

Cuppa-Chino
December 18th, 2005, 07:09 PM
found a copy of both libncurses5-dev_5.5-1ubuntu2_i386.deb and ibncurses5_5.4-9ubuntu4_i386.deb
stanford mirror (http://mirror.stanford.edu/yum/pub/ubuntu/pool/main/n/ncurses/?C=M;O=D)

have installed libncurses5-dev_5.5-1ubuntu2_i386.deb and will see if it works

I get the menu!

I spent lots of time in the menu but could not really get anywhere from there....

took the modules I wanted:

7) DO THIS ONLY IF YOU NEED SOME RESTRICTED MODULE otherwise go to Point 8
ndiswrapper & wpa_supplicant - extracted them in usr/src and then tried to sudo make-kpkg clean there but kernel complained
could find an answer so I tried doing it in usr/src/linux

/usr/bin/make -f /usr/share/kernel-package/rules real_stamp_clean
make[1]: Entering directory `/usr/src/linux-headers-2.6.12-10-686-smp'
test ! -f .config || cp -pf .config config.precious
test -f Makefile && \
/usr/bin/make ARCH=i386 distclean
make[2]: Entering directory `/usr/src/linux-headers-2.6.12-10-686-smp'
fs/hostfs/Makefile:11: arch/um/scripts/Makefile.rules: No such file or directorymake[4]: *** No rule to make target `arch/um/scripts/Makefile.rules'. Stop.
make[3]: *** [fs/hostfs] Error 2
make[2]: *** [_clean_fs] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.12-10-686-smp'
make[1]: [real_stamp_clean] Error 2 (ignored)
test ! -f config.precious || mv -f config.precious .config
test ! -f stamp-patch || /usr/bin/make -f /usr/share/kernel-package/rules unpatch_now
test -f stamp-building || test -f debian/official || rm -rf debian
# work around idiocy in recent kernel versions
test ! -e scripts/package/builddeb.dist || \
mv -f scripts/package/builddeb.dist scripts/package/builddeb
test ! -e scripts/package/Makefile.dist || \
mv -f scripts/package/Makefile.dist scripts/package/Makefile
rm -f modules/modversions.h modules/ksyms.ver debian/files conf.vars scripts/cramfs/cramfsck scripts/cramfs/mkcramfs applied_patches debian/buildinfo stamp-build stamp-configure stamp-source stamp-image stamp-headers stamp-src stamp-diff stamp-doc stamp-buildpackage stamp-libc-kheaders stamp-debian stamp-patch stamp-kernel-configure
rm -rf debian/tmp-source debian/tmp-headers debian/tmp-image debian/tmp-doc
make[1]: Leaving directory `/usr/src/linux-headers-2.6.12-10-686-smp'


then just as I have been trying all evening tried to get the kernel running:
sudo make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers modules_image

make[2]: *** No rule to make target `init/main.o', needed by `init/built-in.o'. Stop.
make[1]: *** [init] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.12-10-686-smp'
make: *** [stamp-build] Error 2

is what came from my sudo make-kpkg --initrd –append-to-version=-alberto kernel_image kernel_headers command...

it looks like I will have to try this another day - seems that I end up in my installed 686smp kernel there somewhere, did I maybe not link the directories right? I did not have an error message though....

tseliot
December 19th, 2005, 08:14 AM
found a copy of both libncurses5-dev_5.5-1ubuntu2_i386.deb and ibncurses5_5.4-9ubuntu4_i386.deb
stanford mirror (http://mirror.stanford.edu/yum/pub/ubuntu/pool/main/n/ncurses/?C=M;O=D)

have installed libncurses5-dev_5.5-1ubuntu2_i386.deb and will see if it works

I get the menu!

I spent lots of time in the menu but could not really get anywhere from there....
1) Which menu? The one which appears when you do sudo make menuconfig?
took the modules I wanted:
2) which modules did you enable and why?

3) About ndiswrapper: it should work with kernel 2.6.12. Therefore do this:
cd /usr/src
ls (and post the output)

ShirishAg75
December 20th, 2005, 05:14 AM
Hi all,
I had done a compilation of the kernel long time ago. Was using Mandrake then at that time. No forums or stuff so it was difficult. Had to use help of friends. Anyway nice thread & happy to see the content of the thread. Read through the whole of 20 pages & have few questions. My questions are in parts:-
First of, my output from lspci & lsmod :-
lspci
0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM Controll er/Host-Hub Interface (rev 03)
0000:00:02.0 VGA compatible controller: Intel Corp. 82845G/GL[Brookdale-G]/GE Ch ipset Integrated Graphics Device (rev 03)
0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) US B UHCI Controller #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) US B UHCI Controller #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) US B UHCI Controller #3 (rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 82)
0000:00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Bridge (rev 0 2)
0000:00:1f.1 IDE interface: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) UltraATA-100 I DE Controller (rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4 -L/ICH4-M) AC'97 Audio Controller (rev 02)
0000:03:01.0 Modem: PCTel Inc: Unknown device 2189 (rev 04)
0000:03:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C /8139C+ (rev 10)

lsmod :-
Module Size Used by
isofs 32824 1
udf 75524 0
ipv6 217408 6
i915 17920 1
drm 58004 2 i915
tc1100_wmi 6916 0
video 16004 0
battery 9604 0
container 4608 0
i2c_acpi_ec 5760 0
i2c_core 19728 1 i2c_acpi_ec
button 6672 0
pcc_acpi 11392 0
sony_acpi 5516 0
ac 4996 0
dev_acpi 11396 0
hotkey 9508 0
floppy 52692 0
pcspkr 3652 0
rtc 11832 0
snd_intel8x0 30144 2
snd_ac97_codec 72188 1 snd_intel8x0
snd_pcm_oss 46368 1
snd_mixer_oss 16128 1 snd_pcm_oss
snd_pcm 78344 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 21764 1 snd_pcm
snd 48644 8 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_timer
soundcore 9184 2 snd
snd_page_alloc 10120 2 snd_intel8x0,snd_pcm
tpm_nsc 6528 0
tpm_atmel 5504 0
tpm 9504 2 tpm_nsc,tpm_atmel
shpchp 80612 0
pci_hotplug 24628 1 shpchp
intel_agp 21276 1
agpgart 32328 3 drm,intel_agp
nls_iso8859_1 4224 8
nls_cp437 5888 9
vfat 12288 8
fat 46492 1 vfat
dm_mod 50364 1
tsdev 7616 0
evdev 9088 0
psmouse 26116 0
mousedev 10912 1
parport_pc 31812 1
lp 11460 0
parport 32072 2 parport_pc,lp
md 40656 0
reiserfs 217200 2
thermal 13192 0
processor 23100 1 thermal
fan 4740 0
8139cp 18432 0
8139too 23552 0
mii 5248 2 8139cp,8139too
ehci_hcd 29448 0
uhci_hcd 28048 0
usbcore 104316 3 ehci_hcd,uhci_hcd
ide_cd 36996 1
cdrom 33952 1 ide_cd
ide_disk 16128 12
ide_generic 1664 0
piix 9476 1
ide_core 125268 4 ide_cd,ide_disk,ide_generic,piix
unix 24624 605
vesafb 8088 0
capability 5000 0
commoncap 6784 1 capability
vga16fb 12232 1
vgastate 8320 1 vga16fb
softcursor 2432 2 vesafb,vga16fb
cfbimgblt 2944 2 vesafb,vga16fb
cfbfillrect 3840 2 vesafb,vga16fb
cfbcopyarea 4480 2 vesafb,vga16fb
fbcon 34176 72
tileblit 2560 1 fbcon
font 8448 1 fbcon
bitblit 5248 1 fbcon


Also something from /boot/grub :- There is no compilation as of yet just whatever installation happened through apt-get

title Ubuntu, kernel 2.6.12-10-386
root (hd0,11)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hda12 ro quiet splash
initrd /boot/initrd.img-2.6.12-10-386
savedefault
boot

title Ubuntu, kernel 2.6.12-10-386 (recovery mode)
root (hd0,11)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hda12 ro single
initrd /boot/initrd.img-2.6.12-10-386
boot

#title Ubuntu, kernel 2.6.12-9-386
#root (hd0,11)
#kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/hda12 ro quiet splash
#initrd /boot/initrd.img-2.6.12-9-386
#savedefault
#boot

#title Ubuntu, kernel 2.6.12-9-386 (recovery mode)
#root (hd0,11)
#kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/hda12 ro single
#initrd /boot/initrd.img-2.6.12-9-386
#boot

title Ubuntu, memtest86+
root (hd0,11)
kernel /boot/memtest86+.bin
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows XP Professional
root (hd0,0)
savedefault
makeactive
chainloader +1

ShirishAg75
December 20th, 2005, 05:23 AM
Now question time
1. I've a p4 1.8 ghz I remember using i686 while compiling on mandrake. Why is this not used ? The processor family is i386 but would like to use the best that can be done.
Would like to use ubuntu kernel rather than anything from kernel.org or kovlias patches simply for the fact that it's my first kernel compilation on ubuntu/debian.
2. uname -r gives 2.6.12-10-386 so how do I uninstall the kernel 2.6.12-9-38 as well as the recovery mode.
3. What is this ndiswrapper module, something to do with wireless or what? I saw this being mentioned again & again.
4. My usage would be just a good desktop, gaming, internet, multimedia & some graphics. Memory is 128 MB DDR but would be upgrading to 1 GB but in few months not now, hence what steps should I take in memory high support?
Thnx in advance. Hope to get some answers haven't started any compilations as yet, would do the same after some advice/suggestions from u. Would like to disable stuff which I don't use like digital cameras, no firewire support would like to have USB support as think to have a USB thumbdrive in couple of months.

tseliot
December 20th, 2005, 12:33 PM
Now question time
1. I've a p4 1.8 ghz I remember using i686 while compiling on mandrake. Why is this not used ? The processor family is i386 but would like to use the best that can be done.
Why don't you install kernel for 686 processors in Synaptic/Kynaptic? Have a look at this guide Picking the Kernel thats Right for You (Possible Speed Increase) (http://ubuntuforums.org/showthread.php?t=85917)

Would like to use ubuntu kernel rather than anything from kernel.org or kovlias patches simply for the fact that it's my first kernel compilation on ubuntu/debian.
I agree with you because this is what I usually do.

2. uname -r gives 2.6.12-10-386 so how do I uninstall the kernel 2.6.12-9-38 as well as the recovery mode.
About your old kernel (2.6.12-9-386): the easiest way to remove it is to:
open Synaptic/Kynaptic
type "linux" in the search field and press search
you will get a list, look for "linux-image-2.6.12-9-386" and mark it for complete removal

OR

a fastest way to do that is:
sudo dpkg -r linux-image-2.6.12-9-386

3. What is this ndiswrapper module, something to do with wireless or what? I saw this being mentioned again & again.
If you have a wireless modem which needs Windows drivers to work you need ndiswrapper. (I've never used it)

4. My usage would be just a good desktop, gaming, internet, multimedia & some graphics. Memory is 128 MB DDR but would be upgrading to 1 GB but in few months not now, hence what steps should I take in memory high support?
4GB of RAM is the maximum supported by default by Ubuntu Breezy's kernels and I suggest you to leave it as it is.

Thnx in advance. Hope to get some answers haven't started any compilations as yet, would do the same after some advice/suggestions from u. Would like to disable stuff which I don't use like digital cameras, no firewire support would like to have USB support as think to have a USB thumbdrive in couple of months.
You can disable the support for firewire but it don't think it will make any difference. USB support is enabled by default.
Do not disable the support for the modules you are not sure to be useless for your computer.

ShirishAg75
December 20th, 2005, 03:42 PM
First of all thnx for taking the time to answer the questions above. Made me edit & give an Avatar & give some more info. about myself.
Simply installing the new 686 kernel should've some improvements but can that also be compiled to have some more better performance? If so how to go about doing that, using the same guide or something different? Would of course let u know if there are any improvements after installing the newer kernel. thnx in advance.

tseliot
December 20th, 2005, 05:09 PM
First of all thnx for taking the time to answer the questions above. Made me edit & give an Avatar & give some more info. about myself.
Simply installing the new 686 kernel should've some improvements but can that also be compiled to have some more better performance. If so how to go about doing that. Would of course let u know after installing the newer kernel . thnx in advance.
If you want to compile a faster kernel you have to disable all the modules which are not useful to your hardware. In other words look at lspci and look for the Linux modules which are required by each device of yours. Then disable the modules (after you do the "sudo make menuconfig" thing in the guide) which you are sure to be related to devices (chipsets, etc.) other than yours.
This can be a good chance to learn something about Linux kernels.

Anyhow I wouldn't be able to help you now as I'm too stressed. I need some rest.

Bloot
December 20th, 2005, 06:15 PM
Anybody found a solution to make automount devices work when compiling 2.6.14 + kernels?.

ShirishAg75
December 20th, 2005, 06:34 PM
Hi all,
First of all did download the new image, it was 2 files & approximately took 25 MB space compressed space & 75 temporary space. Using the new kernel, it seems little bit more faster but still not good enough. Although couple of things need to be disabled through BUM but still don't think will have much effect.
Another question that came to me. Whenever one asks for :-
sudo apt-get update
sudo apt-get install build-essential
sudo apt-get install kernel-package
1. Does the system know what kernel I'm using 2.6.12-10-686 kernel right now, how does it know that it shouldn't download let's say 2.6.12-10-386 or any other kernel? It would be interesting to understand that.
2. Just to understand all the entries in the lspci output are modules that are required or is there a difference when some of them show 0 in the used by column. A part of me says yes & a part says no hence the question :)
Thnx again

tseliot
December 21st, 2005, 05:43 AM
Anybody found a solution to make automount devices work when compiling 2.6.14 + kernels?.
I haven't tested kernel 2.6.14 too much. Anyhow if I find a solution I'll post it.

tseliot
December 21st, 2005, 05:52 AM
Hi all,
First of all did download the new image, it was 2 files & approximately took 25 MB space compressed space & 75 temporary space. Using the new kernel, it seems little bit more faster but still not good enough. Although couple of things need to be disabled through BUM but still don't think will have much effect.
Another question that came to me. Whenever one asks for :-
sudo apt-get update
sudo apt-get install build-essential
sudo apt-get install kernel-package
1. Does the system know what kernel I'm using 2.6.12-10-686 kernel right now, how does it know that it shouldn't download let's say 2.6.12-10-386 or any other kernel? It would be interesting to understand that.
Those packages are the same for every architecture (i386, 686, etc.)

2. Just to understand all the entries in the lspci output are modules that are required or is there a difference when some of them show 0 in the used by column. A part of me says yes & a part says no hence the question :)
Thnx again
Ok have a look at your lspci. Put the name of each device (one per time) in Google's search engine together with the word "linux" (or "module").
In this way you will know the modules which each piece of your hardware needs.

The next step is to do the "sudo make menuconfig" thing and explore it. Each module you can enable (or disable) has a description of its function. if you select a module and press the "?" symbol on your keyboard you can have a detailed description. Then if you are sure you don't need the module (for example for a 3dfx card or an nforce controller) you can disable it.
In other words you have to learn what your computer really needs.

Bloot
December 21st, 2005, 07:47 AM
I haven't tested kernel 2.6.14 too much. Anyhow if I find a solution I'll post it.

Thanks, it's annoying to build a new kernel and then be unable to mount any devices but the floppy.

ShirishAg75
December 21st, 2005, 07:49 AM
/snip
About your old kernel (2.6.12-9-386): the easiest way to remove it is to:
open Synaptic/Kynaptic
type "linux" in the search field and press search
you will get a list, look for "linux-image-2.6.12-9-386" and mark it for complete removal

OR

a fastest way to do that is:
sudo dpkg -r linux-image-2.6.12-9-386
/snip

Hi there,
Thanx for pointing stuff out. Will look at the same. the dpkg -r didn't do it for me. What helped was doing the same in synaptic. Tried the same way today morning when I wanted to remove the 2.16.12.10-386 kernel but that didn't help. I marked it for total removal but still the entry was there in grub. Which atleast to me feels like the whole thing hasn't been removed. After quite a bit searching came to the apt manual which gives this command :-
apt-get --purge remove linux-image-2.6.12.10-386 I think this is the command which gets invoked when we do the same in Synaptic. I did the job wonderfully & was able to take the entries out of grub also. Also did an
apt-get autoclean It's been fascinating to see how things work in this universe :)

ShirishAg75
December 21st, 2005, 10:06 AM
Hi there,
This is the last time I ask u before setting down to the actual dirty work. In lspci the output usually comes such as :-
0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03)

Now this tells me this is the RAM controller & uses Intel 82845 chipset who is responsible for it. Now what is the rev 03. I tried putting many times the query such as :-
Q1. intel 82845G/GL DRAM Controller linux & there are many results but don't know how to narrow it down to know what module it is. For e.g. http://lists.debian.org/debian-boot/2005/10/msg00841.html he has a machine much closer to me atleast with the lspci output & he was able to do it in a 2.4 kernel so know that the modules are there.

Q2. What is the difference between a driver & a module? I also have made a complete note of the modprobe as well as lspci on a page so when doing this it should be helpful. Would like to understand what I'm searching for.

Another thing in u'r guide u have given
sudo make oldconfig
Q3.Should I be using this step also or not & what does this step do?
As always thanx in advance.

tseliot
December 21st, 2005, 01:00 PM
Hi there,
This is the last time I ask u before setting down to the actual dirty work. In lspci the output usually comes such as :-
0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03)

Now this tells me this is the RAM controller & uses Intel 82845 chipset who is responsible for it. Now what is the rev 03. I tried putting many times the query such as :-
Q1. intel 82845G/GL DRAM Controller linux & there are many results but don't know how to narrow it down to know what module it is. For e.g. http://lists.debian.org/debian-boot/2005/10/msg00841.html he has a machine much closer to me atleast with the lspci output & he was able to do it in a 2.4 kernel so know that the modules are there.
I guess there's no need to do anything because kernel 2.6.12 supports your chipset.

Q2. What is the difference between a driver & a module? I also have made a complete note of the modprobe as well as lspci on a page so when doing this it should be helpful. Would like to understand what I'm searching for.
You can compile the support for a device (the driver) in the kernel or as a module (which you can disable and enable whenever you like)

Another thing in u'r guide u have given
sudo make oldconfig
Q3.Should I be using this step also or not & what does this step do?
As always thanx in advance.
oldconfig let you use the settings of your current kernel for the kernel you are going to compile.

ShirishAg75
December 21st, 2005, 05:14 PM
oldconfig let you use the settings of your current kernel for the kernel you are going to compile.
Now don't know whether that's good or not.
Further it seems the Realtek ethernet chipset 8139C+ fast ethernet is also supported generically. I say this as I didn't have to install a single driver till date. Things just had to be configured.
Just downloading the 1st part. downloading linux-tree. It's a 44.3 MB of download with the linux-source itself being a 40 mb download. That's quite a bit. Also would be downloading the suggested packages libncurses-dev, kernel-package, libqt3-dev tonight as well as the recommended package gcc-3.4. Atleast complete all the downloads business tonight itself & then start trying to play around tomorrow.

ShirishAg75
December 22nd, 2005, 06:25 PM
success, using my kernel surfing & doing stuff. It really has changed the countours of how the system was responding before. Pretty cool. Another thing it's always nice to see one's name in the kernel :) instead of alberto made shirish here.
One thing though. Made couple of bloopers. 1st had started the whole thing as sudo su hence while at the export step missed the CC=gcc3.4 & it had compiled with gcc=4.0 I guess then gave the command again & ran the whole group of commands as u had given.

1.Further had saved the config file also. I gave it a name shirish.config how should I find it or where would it be?

2. It did give some errors while booting up. Although all the functions are happening properly. So what/where things are wrong or could've gone wrong? Any ideas? I'm sure there is some log which keeps the tab of the booting process. If possible wanna look at the log.

tseliot
December 22nd, 2005, 07:10 PM
success, using my kernel surfing & doing stuff. It really has changed the countours of how the system was responding before. Pretty cool. Another thing it's always nice to see one's name in the kernel :) instead of alberto made shirish here.
One thing though. Made couple of bloopers. 1st had started the whole thing as sudo su hence while at the export step missed the CC=gcc3.4 & it had compiled with gcc=4.0 I guess then gave the command again & ran the whole group of commands as u had given.

1.Further had saved the config file also. I gave it a name shirish.config how should I find it or where would it be?
If you have installed the new kernel you have to get to /boot and copy the file "config-name_of_your_kernel" to the folder you wish.
2. It did give some errors while booting up. Although all the functions are happening properly. So what/where things are wrong or could've gone wrong? Any ideas? I'm sure there is some log which keeps the tab of the booting process. If possible wanna look at the log.
Have a look at /var/log/syslog.0

ShirishAg75
December 23rd, 2005, 08:37 AM
(/snip)
sudo passwd root
(and set the root password which you will need later) why do I need this? I want to keep my system simple. Just one password for user as well as root. So is it o.k. if I do su or sudo su here?

cd /usr/src
sudo tar --bzip2 -xvf linux-source-2.6.12.tar.bz2
sudo ln -s /usr/src/linux-source-2.6.12 /usr/src/linux I always remove the symbolic link in case present before. Nice & easy till here.

cd /usr/src/linux
make menuconfig
changed it as I'm su here. Saved the file & everything's A o.k. till here.

(/snip)

Now you are back to the command line, type:
6) su
CC=gcc-3.4
export CC
exit
CC=gcc-3.4
export CC
This is the step where I get confused as to where I'm. Now here I don't need to be su as I'm the super user here.The moment I exit I become the normal user let's say shirishag75 so it would be:-

root@ubuntu:/usr/src/linux# CC=gcc-3.4
root@ubuntu:/usr/src/linux# export CC
root@ubuntu:/usr/src/linux# exit
exit
shirishag75@ubuntu:~$ CC=gcc-3.4
shirishag75@ubuntu:~$ export CC
shirishag75@ubuntu:~$ sudo make-kpkpg clean
Password:
sudo: make-kpkpg: command not found

shirishag75@ubuntu:~$ sudo cd/usr/src/linux
sudo: cd/usr/src/linux: command not found

Now this last procedure is the most frustating of all. See if this can be simplified more without putting the sudo passwd root routine as well as this changing back & forth or the reasons why we're doing it. Otherwise atleast I didn't understand is the user making the export & if ues why isn't the command after that of
sudo make-kpkg clean being processed.
Sorry for being a pain in the a** but this either needs to be cleaned up or provided with some info. as what's happening.
Thanx in advance.

tseliot
December 23rd, 2005, 11:51 AM
(/snip)
sudo passwd root
(and set the root password which you will need later) why do I need this? I want to keep my system simple. Just one password for user as well as root. So is it o.k. if I do su or sudo su here?

cd /usr/src
sudo tar --bzip2 -xvf linux-source-2.6.12.tar.bz2
sudo ln -s /usr/src/linux-source-2.6.12 /usr/src/linux I always remove the symbolic link in case present before. Nice & easy till here.

cd /usr/src/linux
make menuconfig
changed it as I'm su here. Saved the file & everything's A o.k. till here.

(/snip)

Now you are back to the command line, type:
6) su
CC=gcc-3.4
export CC
exit
CC=gcc-3.4
export CC
This is the step where I get confused as to where I'm. Now here I don't need to be su as I'm the super user here.The moment I exit I become the normal user let's say shirishag75 so it would be:-

root@ubuntu:/usr/src/linux# CC=gcc-3.4
root@ubuntu:/usr/src/linux# export CC
root@ubuntu:/usr/src/linux# exit
exit
shirishag75@ubuntu:~$ CC=gcc-3.4
shirishag75@ubuntu:~$ export CC
shirishag75@ubuntu:~$ sudo make-kpkpg clean
Password:
sudo: make-kpkpg: command not found

shirishag75@ubuntu:~$ sudo cd/usr/src/linux
sudo: cd/usr/src/linux: command not found

Now this last procedure is the most frustating of all. See if this can be simplified more without putting the sudo passwd root routine as well as this changing back & forth or the reasons why we're doing it. Otherwise atleast I didn't understand is the user making the export & if ues why isn't the command after that of
sudo make-kpkg clean being processed.
Sorry for being a pain in the a** but this either needs to be cleaned up or provided with some info. as what's happening.
Thanx in advance.
If you want you can use the same password of your username for your root account (It's not recommended for security reasons).

You made a mistake (a typo)
You wrote:
sudo make-kpkpg clean

But the correct command is:
sudo make-kpkg clean

ShirishAg75
December 23rd, 2005, 07:11 PM
If you have installed the new kernel you have to get to /boot and copy the file "config-name_of_your_kernel" to the folder you wish.

Have a look at /var/log/syslog.0
1. Strange looked at /var/log/syslog.0 & the last entry was of
Dec 22 02:25:30 localhost exiting on signal 15 after that there's no entry.

2.Further more Nautilus seems to be behaving strangely. Now it's not able to go to directories other than mine even as root. It crashes sometimes randomly sometimes one after other.

3. The horizontal bar which tells that Ubuntu is loading up & hides the textual loading up is gone. Now the text messages are seen.
this is the line from /boot/grub/menu.lst . Is this just a simple thing of just deleting the quiet in between splash or something which
maybe I deselected in the menuconfig.
/boot/vmlinuz-2.6.12-shirish root=/dev/hda12 ro quiet splash

Lastly, now with the new kernel If I try again to build a kernel it should take quite a less time shouldn't it. As now it would try to use the p4 power+ RAM. Whenever I do I would be skipping the make oldconfig step as I would want things to be efficient as well as stable also. Would be looking for u'r comments to what to watch out for while trying this next time :) Thanx all the same.

ShirishAg75
December 24th, 2005, 06:06 AM
Did try once before u answer but wasn't able to be successful. Another thing how much time/frequency does the kernel change. I've looked at some of the posts where u've been talking of the vanilla kernel & that is 2.6.14 so how much time lag is there between the kernels coming up at www.kernel.org (http://www.kernel.org) & they being posted in the repositeries.

tseliot
December 24th, 2005, 07:51 AM
1. Strange looked at /var/log/syslog.0 & the last entry was of
Dec 22 02:25:30 localhost exiting on signal 15 after that there's no entry.

2.Further more Nautilus seems to be behaving strangely. Now it's not able to go to directories other than mine even as root. It crashes sometimes randomly sometimes one after other.

3. The horizontal bar which tells that Ubuntu is loading up & hides the textual loading up is gone. Now the text messages are seen.
this is the line from /boot/grub/menu.lst . Is this just a simple thing of just deleting the quiet in between splash or something which
maybe I deselected in the menuconfig.
/boot/vmlinuz-2.6.12-shirish root=/dev/hda12 ro quiet splash

Lastly, now with the new kernel If I try again to build a kernel it should take quite a less time shouldn't it. As now it would try to use the p4 power+ RAM. Whenever I do I would be skipping the make oldconfig step as I would want things to be efficient as well as stable also. Would be looking for u'r comments to what to watch out for while trying this next time :) Thanx all the same.
Weird... why don't you stick with the kernel which comes with Ubuntu by default?

ShirishAg75
December 24th, 2005, 08:18 AM
because it's damn slow. Compared with how it's working now with the new one, it used to take ages for the thing to start compared to this one. Just if I got some more control over what's happening & what to look out for.

tseliot
December 24th, 2005, 10:42 AM
because it's damn slow. Compared with how it's working now with the new one, it takes ages for the thing to start compared to this one. Just if I got some more control over what's happening & what to look out for.
I don't know what you changed in the new kernel (with respect to Ubuntu's default kernel) so unless you tell me I can't help you.

ShirishAg75
December 24th, 2005, 06:26 PM
Sorry, English is not my first language & it was written on the spur of the moment. Anyway have changed/edited the post now. What I meant was the one which is working now is faster than the 2.6.10-686 which was there in the default kernel. The issue is I don't understand much of the make menuconfig thing as well as the exporting compiler issue. For e.g. why does the user also have to give the CC=export gcc-3.4 & the whole thing.
Another thing which I didn't tell u is that I was also using id3master's
How to speed up ubuntu process & inadverantly messed up the one of the syslogd entries. so would start play around a little, shut down the machine & then again the whole process couple of times & then see if I can find something in /var/log/whatever comes next.
Another thing which I wanted to ask u was which is superior in ALSA & OSS. Would u recommend both/ or one of the two more than the other & the reasons for the same. Feeling sleepy now going to sleep :)

ShirishAg75
December 24th, 2005, 06:29 PM
double posting bloopers.

Rob2687
December 24th, 2005, 11:55 PM
With the 2.6.14 kernel, it seems to be mounting stuff but not really mounting them. If I put in a CD or USB thumbdrive, they are accessable through /media/cdrom0 and /media/USB DRIVE but it isn't accessable through Computer or anything.

tseliot
December 25th, 2005, 06:10 AM
With the 2.6.14 kernel, it seems to be mounting stuff but not really mounting them. If I put in a CD or USB thumbdrive, they are accessable through /media/cdrom0 and /media/USB DRIVE but it isn't accessable through Computer or anything.
I don't use kernel 2.6.14 but I have heard other people complaining about mounting issues. I hope they can be solved in 2.6.15

tseliot
December 25th, 2005, 06:28 AM
Sorry, English is not my first language & it was written on the spur of the moment. Anyway have changed/edited the post now. What I meant was the one which is working now is faster than the 2.6.10-686 which was there in the default kernel.
Do you use Ubuntu Hoary or Breezy? Or did you upgraded Hoary to Breezy? (kernel 2.6.10 came by default with Hoary)
The issue is I don't understand much of the make menuconfig thing as well as the exporting compiler issue. For e.g. why does the user also have to give the CC=export gcc-3.4 & the whole thing.
CC=export gcc-3.4 means that you tell your computer to use gcc-3.4 instead of the one which comes by default with Ubuntu Breezy (gcc-4.0).
Every kernel needs its particular version of gcc (the compiler) e.g. kernels 2.6.12-x need gcc-3.4 while kernels 2.6.14-x need gcc-4.0
In my guide I suggest to export CC 2 times (both as root and as common user) because sometimes it won't accept the command if prompted only by a common user (it happened to me 2 days ago).
Another thing which I didn't tell u is that I was also using id3master's How to speed up ubuntu process & inadverantly messed up the one of the syslogd entries. so would start play around a little, shut down the machine & then again the whole process couple of times & then see if I can find something in /var/log/whatever comes next.
Sorry but I can't help you with that.
Another thing which I wanted to ask u was which is superior in ALSA & OSS. Would u recommend both/ or one of the two more than the other & the reasons for the same. Feeling sleepy now going to sleep :)
I think ALSA is superior but OSS is required for a few things (games,etc.)
You can install alsa-oss from synaptic (so as to emulate OSS by using ALSA for compatibility reasons)

ShirishAg75
December 25th, 2005, 09:14 AM
Do you use Ubuntu Hoary or Breezy? Or did you upgraded Hoary to Breezy? (kernel 2.6.10 came by default with Hoary)

Ubuntu 5.10 no upgradations using the official shipit install CD & by default it installed the 2.6.10 kernel. Should it have installed one of the 2.6.14 by default?

CC=export gcc-3.4 means that you tell your computer to use gcc-3.4 instead of the one which comes by default with Ubuntu Breezy (gcc-4.0).
Every kernel needs its particular version of gcc (the compiler) e.g. kernels 2.6.12-x need gcc-3.4 while kernels 2.6.14-x need gcc-4.0
In my guide I suggest to export CC 2 times (both as root and as common user) because sometimes it won't accept the command if prompted only by a common user (it happened to me 2 days ago).

When one is giving this export command as su as well as common user remains in the RAM or not? Because as common user the moment I say exit it throws me out to my home directory & then unable to get to /usr/src/linux from where the command has to be given. Is there somehow that the moment su exists it doesn't throw me to my home directory so I can execute the export command in the /usr/src/linux directory itself.

Sorry but I can't help you with that.

I think ALSA is superior but OSS is required for a few things (games,etc.)
You can install alsa-oss from synaptic (so as to emulate OSS by using ALSA for compatibility reasons)

Thanx, will try that.

tseliot
December 25th, 2005, 10:18 AM
Ubuntu 5.10 no upgradations using the official shipit install CD & by default it installed the 2.6.10 kernel. Should it have installed one of the 2.6.14 by default?
Ubuntu Breezy 5.10 comes with kernel 2.6.12 by default. Ubuntu Hoary 5.04 with kernel 2.6.10. Ubuntu Dapper 6.04 will come with 2.6.15.

If you have a Breezy installation you should have kernel 2.6.12. Otherwise there's something wrong (unless you upgraded Hoary to Breezy)

When one is giving this export command as su as well as common user remains in the RAM or not? Because as common user the moment I say exit it throws me out to my home directory & then unable to get to /usr/src/linux from where the command has to be given. Is there somehow that the moment su exists it doesn't throw me to my home directory so I can execute the export command in the /usr/src/linux directory itself.
It's not important in which directory you are when you type the export command. If you follow EVERY step my guide (copy and paste the commands I suggest) everything will work.

ShirishAg75
December 25th, 2005, 02:04 PM
you were right it's 2.6.12-10 the default kernel which comes with the Ubuntu. Any info. on getting some more understanding of the make menuconfig thing. Some link which tells some of the options which are there.

tseliot
December 25th, 2005, 02:21 PM
you were right it's 2.6.12-10 the default kernel which comes with the Ubuntu. Any info. on getting some more understanding of the make menuconfig thing. Some link which tells some of the options which are there.
Try this website:
http://www.kernelnewbies.org/

Anyhow I don't know all the functions of a kernel and perhaps only a kernel hacker can fully understande them.

ephman
December 29th, 2005, 11:17 PM
hi,

i'm having a bit of a problem with a restricted module i need to intall, madwifi. i follow the instructions. i download the source (since i used subversion i didn't have to decompress), and moved the directory to /usr/src/, then i:

sudo make-kpkg clean, and then
sudo make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers modules_image

see the .deb's for image and the headers, but not the .deb for madwifi? am i missing something?

thanks for the bandwidth,
ephman

Rob2687
December 29th, 2005, 11:31 PM
You can just make and make install madwifi separately

ephman
December 29th, 2005, 11:42 PM
hi,

i'm just curios why it didn't create the .deb for madwifi when it should have? am i making a mistake anywhere?

thanks,
ephman

Rob2687
December 29th, 2005, 11:48 PM
The madwifi source should be in /usr/src/modules
I'm not sure that just using svn to get the source will give you the proper stuff to make a madwifi module.

You can try installing the debian madwifi source package from the Debian repos and extract it then make the modules.

ephman
December 30th, 2005, 12:08 AM
cool thanks that makes sense.

go leafs go...


ephman

lynwis
January 10th, 2006, 02:43 PM
hi, i compiled the kernel yesterday, and everything seems to be alright, but i don't really understand this thing about compiling restricted-modules.

I wanted to install the ati drivers; with the binary kernel i just got them via apt-get, running:
>apt-get install xorg-driver-fglrx

but now i understand this won't work with my custom kernel, so i tried to download the source for that driver, with:
> apt-get source xorg-driver-fglrx

but i get an archive named "linux-restriced-modules", containing more folders.
I tried to put the entire folder in /usr/src/ , to compile it as a module with the kernel, as you said in the how-to, but it didn't work.
There's also a subfolder named "ati" in the archive, with files that i think are needed for compiling fglrx and the other stuff, but i don't know what to do, since there seems to be no makefile or anything... (and i don't have much experience with compiling packages...)

well, in the end i just wanted to know what should i do to install the ati drivers (for radeon 9700) for the new compiled kernel

ps: thanks for the how-to, i hope my english is understandable

tseliot
January 10th, 2006, 02:54 PM
hi, i compiled the kernel yesterday, and everything seems to be alright, but i don't really understand this thing about compiling restricted-modules.

I wanted to install the ati drivers; with the binary kernel i just got them via apt-get, running:
>apt-get install xorg-driver-fglrx

but now i understand this won't work with my custom kernel, so i tried to download the source for that driver, with:
> apt-get source xorg-driver-fglrx

but i get an archive named "linux-restriced-modules", containing more folders.
I tried to put the entire folder in /usr/src/ , to compile it as a module with the kernel, as you said in the how-to, but it didn't work.
There's also a subfolder named "ati" in the archive, with files that i think are needed for compiling fglrx and the other stuff, but i don't know what to do, since there seems to be no makefile or anything... (and i don't have much experience with compiling packages...)

well, in the end i just wanted to know what should i do to install the ati drivers (for radeon 9700) for the new compiled kernel

ps: thanks for the how-to, i hope my english is understandable
Those weren't ati proprietary drivers therefore you have to remove them from /usr/src (or wherever you put them).

The right drivers are the following:
sudo apt-get install fglrx-kernel-source

A new file will appear in /usr/src

Extract it in the following way:
cd /usr/src
sudo tar -xzvf fglrx-kernel-source.tar.gz

Then compile the kernel (a new kernel) following the rest of the guide.

If you don't want to compile a new kernel then you might want to try the following guide: HOW-TO: ATI fglrx driver 8.16.20 (http://www.ubuntuforums.org/showthread.php?t=75378&highlight=ATI+drivers)

OR this one for the latest version of the driver HOW-TO: ATI fglrx driver latest version (http://ubuntuforums.org/showpost.php?p=423584)

Titan1958
January 14th, 2006, 07:34 PM
Thanks a lot!

It works straight forward for me. Short 'n Sweet!

I have compiled my 1st kernel woo woo :)

Azion
January 14th, 2006, 09:10 PM
Is there a performance increase for compiling the kernel?

ashrack
January 15th, 2006, 05:27 AM
Is there a performance increase for compiling the kernel?
On my notebook I get noticable faster startup and some increase in overall performance. I believe its because of the slow HDD that notebooks have :(
But on my main desktop machine, I only noticed about 2sec faster bootup time.

Bottom line, if U have a good machine(check my sig) than theres no need for compiling it. I personally compile 4 fun. SInce I like to know whats happening under the hud.

greyhound4334
January 20th, 2006, 01:57 AM
Hi,

I've gotten myself somewhat messed up.

I wanted to install a 2.6.15 series kernel. I've always run stock ubuntu kernels before, and I'm not 100% sure what "extra" stuff ubuntu patches into the vanilla kernel.org kernels, so I had what I thought was a great brainstorm: let's see if there's a 2.6.15 kernel source package in dapper with all the ubuntu stuff.

Lo and behold, change my sources.list to dapper, apt-get update, and there's a lovely 2.6.15 kernel source with ubuntu patches for the taking.

So I downloaded the source and pretty much followed this installation guide (nice job, thank you for putting it up!).

But now I'm having some oddball module loading problems with ivtv (tv capture card driver for MythTV) that I'm wondering about. Might there have been some subtle problems with building 2.6.15 that lead to this problem?

I'm pursuing this with the ivtv folks, but in the mean time, I wanted to backtrack a bit and ask these questions:

1. Is my approach valid (i.e., does it make sense to download the dapper kernel source and build it in a breezy installation)?
2. If not (or if the answer is unknown), how about a different approach: if I download a vanilla kernel from kernel.org, is there any "easy" way to apply the ubuntu patches to it?
3. On a related note, found the CK patchset (I think you referenced it here), but I was wondering how that relates to any Ubuntu patches, if anyone knows. More concretely, can I apply both the CK patchset AND the ubuntu patchset?

Thanks in advance for any help on this.

Cheers,
john

tseliot
January 20th, 2006, 05:02 AM
1. Is my approach valid (i.e., does it make sense to download the dapper kernel source and build it in a breezy installation)?
In theory you shouldn't do it. However I did it several times (when I used Hoary) and nothing bad happened.

2. If not (or if the answer is unknown), how about a different approach: if I download a vanilla kernel from kernel.org, is there any "easy" way to apply the ubuntu patches to it?
I really don't know how to do that

3. On a related note, found the CK patchset (I think you referenced it here), but I was wondering how that relates to any Ubuntu patches, if anyone knows. More concretely, can I apply both the CK patchset AND the ubuntu patchset?
I think they are different patches and you should use either one or the other.

BTW did you try to download the sources of the driver of your card. You might need to use the latest version and compile it together with the kernel as a kernel module (as I explain in the guide).

greyhound4334
January 20th, 2006, 12:40 PM
In theory you shouldn't do it. However I did it several times (when I used Hoary) and nothing bad happened.
Yeah, everything else seems fine. And I'm only mildly suspicious of the kernel build process as a factor in my ivtv problem. But thought I'd verify my assumptions. All things being equal, I agree - I think I'd rather not try to mix-and-match the sources this way.


I really don't know how to do that

OK. But do you know anything about the "ubuntu patches"? Right now they're a total mystery to me, and I'm a little leery of running without them. I suppose I could try it and see what happens, but I'm afraid of running into a problem downstream when something that used to work suddenly doesn't.


I think they are different patches and you should use either one or the other.

Makes sense to me.


BTW did you try to download the sources of the driver of your card. You might need to use the latest version and compile it together with the kernel as a kernel module (as I explain in the guide).
Yes. Err... maybe. I'm not sure. :) I followed the method of your guide that explained how to download the installer and run it, which seemed to download source and compile and link it. I used the latest version. Whatever I did, the nVidia drivers seemed to work fine at the end.

Thanks for your guide(s) and for the help. I'd really feel more comfortable if I could learn more about the ubuntu patches!

Cheers,
john

tseliot
January 20th, 2006, 01:26 PM
Yes. Err... maybe. I'm not sure. :) I followed the method of your guide that explained how to download the installer and run it, which seemed to download source and compile and link it. I used the latest version. Whatever I did, the nVidia drivers seemed to work fine at the end.

If you follow this part of the guide "7) DO THIS ONLY IF YOU NEED SOME RESTRICTED MODULE" and use it to install the latest version (which you have to get from a website and not from the repositories) of the ivtv driver (you don't need to compile also the nvidia drivers together with the kernel). You have to download the latest ivtv source code and put it in the modules folder in your /usr/src and follow the guide.


[QUOTE=greyhound4334]I'd really feel more comfortable if I could learn more about the ubuntu patches!
Me too.

greyhound4334
January 20th, 2006, 01:57 PM
If you follow this part of the guide "7) DO THIS ONLY IF YOU NEED SOME RESTRICTED MODULE" and use it to install the latest version (which you have to get from a website and not from the repositories) of the ivtv driver (you don't need to compile also the nvidia drivers together with the kernel). You have to download the latest ivtv source code and put it in the modules folder in your /usr/src and follow the guide.

Very interesting. Let me make sure I understand you correctly. I'm fairly novice at kernel building and all, so I'm groping a bit.

I think you're saying that I should treat the ivtv modules as a "restricted module" in your terms, much the same way you describe how to treat the nvidia proprietary driver in this way, right?

I *do* build the ivtv stuff from source, and I *think* it links in to the kernel headers for my kernel, but maybe that's not the same? I'm a bit confused on this part, so I want to make sure I'm understanding you correctly.

Note that I built a 2.12 series kernel from source before, and followed the standard ivtv installation process (as I just described, NOT as you describe it -- the essential difference, I think, being that you want me to put it in the /usr/src/modules directory and have it built as part of make-kpkg) and it worked fine.

Maybe you could comment on what I just wrote so I can be sure I understand your suggestion.

Thanks for taking the time with this problem! I'm very grateful.

Cheers,
john

tseliot
January 20th, 2006, 02:16 PM
Very interesting. Let me make sure I understand you correctly. I'm fairly novice at kernel building and all, so I'm groping a bit.

I think you're saying that I should treat the ivtv modules as a "restricted module" in your terms, much the same way you describe how to treat the nvidia proprietary driver in this way, right?
You're right but the method I have suggested is useless unless you find a version of the source of the driver which compiles fine with kernel 2.6.15.

Once find the right source of the driver you should follow the standard ivtv installation process(which is faster and easier than mine). Therefore I retire my suggestion. You know, I'm studying for my 1st exam of the 2nd level degree and my brain is frying (literally) :p

greyhound4334
January 20th, 2006, 02:56 PM
Thanks. And good luck with the exams!

HenryTheGreat
January 26th, 2006, 07:55 PM
I must thank you tseliot; I followed your instructions and I compiled my first kernel (2.6.15)!! :D :D \\:D/

chinaski
January 29th, 2006, 01:42 PM
hi,

is this How-To suitable also for Kubuntu BB AMD64-Bit?

tseliot
January 29th, 2006, 02:45 PM
hi,

is this How-To suitable also for Kubuntu BB AMD64-Bit?
Yes, sure. You can use it for both Ubuntu 32bit and 64bit.

chinaski
January 29th, 2006, 04:44 PM
good :)

thank you tseliot, grazie ;)

dolson
January 31st, 2006, 02:17 PM
Updating /boot/grub/menu.lst ... done

Setting up kernel-image-2.6.12-dolson (1.0) ...
FATAL: Module dm_mod not found.


What is that about??

tseliot
January 31st, 2006, 04:16 PM
Updating /boot/grub/menu.lst ... done

Setting up kernel-image-2.6.12-dolson (1.0) ...
FATAL: Module dm_mod not found.


What is that about??
It's device-mapper. Does the kernel work properly?

dolson
January 31st, 2006, 10:23 PM
Well, I think that I figured out why I get that. Or not why, but how/when.

At the time I was running the install command, I was running a vanilla kernel that I compiled with very very customized options (I disable everything that doesn't apply to my system pretty much), and was trying to use the Breezy source to make a slight customized version of the official kernel.

I think that when running the vanilla kernel, I get that message for some reason. I think this because I made a sandbox and tested the same procedure while running the default 386 kernel, and that message did not appear.

Yes, the kernel works fine. So I think it's something weird that happens when running the vanilla kernels.

I just thought I'd ask in your thread because I used a very similar method to yours (near identical, really), and thought perhaps it was something that happened every time.

tseliot
February 1st, 2006, 07:16 AM
Yes, the kernel works fine. So I think it's something weird that happens when running the vanilla kernels.

I just thought I'd ask in your thread because I used a very similar method to yours (near identical, really), and thought perhaps it was something that happened every time.
It never happened to me. Anyhow you have to be sure that all you disable in the kernel isn't related to your hardware. For example the 1st time I installed Gentoo I disabled the support for my network card:p the kernel was fast though..