I want to install spca5xx-source from the repositories, but it tells me that I need the kernel headers.
According to 'uname -r', the installed kernel is 2.6.17-10-generic, but all the kernel headers are 2.4.27-2.
Please, where can I get the 2.6.17-10-generic headers from, or can I use one of the 2.4.27-2 ones?
It's to get my webcam working in Mint. I've used the tarball from mxhaard.free.fr before, but thought that using the supplied source package might be better
Many thanks for any help.
Keith
Kernel and headers
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Kernel and headers
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Kernel and headers
How did you achieve that ???keithp wrote: According to 'uname -r', the installed kernel is 2.6.17-10-generic, but all the kernel headers are 2.4.27-2.
synaptic ... "Add / Remove software ..." Screenshot listing all available kernel headers:keithp wrote:Please, where can I get the 2.6.17-10-generic headers from
Definitely NOkeithp wrote: or can I use one of the 2.4.27-2 ones?
My theory is you did something really "unfortunate" do your /etc/apt/sources.list and maybe added some non-Ubuntu repositories, maybe original repos for Debian Stable ...? Would you please post your /etc/apt/sources.list here so we can take a look?
Regards,
Scorp123
scorp123 and zolly.
Thank you both for your help.
Right, I have started again with a new installation of Bea 2.1, on my experimenting hard drive. (I have several drives on trays so there is no multiple booting). It is just a straight installation from the CD.
Going into "menu" at the start of booting, confirms that the installed kernel is 2.6.17-10-generic.
I then did an apt-get update and checked in synaptic. All the listed kernels, headers, and so on, are 2.4.27-2. There is nothing 2.6.17 listed.
The apt repositories are exactly as installed in the installation (nothing added and nothing taken away!). Here they are:
## comments (##) in front of any line to remove it from being checked.
## Use the following sources.list at your own risk.
deb http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse
## MAJOR BUG FIX UPDATES produced after the final release
deb http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse
## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main
# AMAROK 1.4.4
deb http://kubuntu.org/packages/amarok-144 edgy main
That is the present situation so any further help you can give me will be very gratefully received!
Cheers
Keith
Thank you both for your help.
Right, I have started again with a new installation of Bea 2.1, on my experimenting hard drive. (I have several drives on trays so there is no multiple booting). It is just a straight installation from the CD.
Going into "menu" at the start of booting, confirms that the installed kernel is 2.6.17-10-generic.
I then did an apt-get update and checked in synaptic. All the listed kernels, headers, and so on, are 2.4.27-2. There is nothing 2.6.17 listed.
The apt repositories are exactly as installed in the installation (nothing added and nothing taken away!). Here they are:
## comments (##) in front of any line to remove it from being checked.
## Use the following sources.list at your own risk.
deb http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted universe multiverse
## MAJOR BUG FIX UPDATES produced after the final release
deb http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-updates main restricted universe multiverse
## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
deb http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu edgy-backports main restricted universe multiverse
## CANONICAL COMMERCIAL REPOSITORY (Hosted on Canonical servers, not Ubuntu
## servers. RealPlayer10, Opera, DesktopSecure and more to come.)
deb http://archive.canonical.com/ubuntu edgy-commercial main
# AMAROK 1.4.4
deb http://kubuntu.org/packages/amarok-144 edgy main
That is the present situation so any further help you can give me will be very gratefully received!
Cheers
Keith
OK, that's good. So we are not going to run into unexpected things then. Just go into synaptic and first uninstall the linux headers that you currently have on your system ... this should work, unless we run into some really exotic dependency problem. Then when 2.4.xx stuff is gone select the kernel headers as shown in my screenshot up there. They should have a version number that reflects the version of your Linux kernel, 2.6.16.xx something.keithp wrote:The apt repositories are exactly as installed in the installation (nothing added and nothing taken away!)
Unless we run into some really funny problem this should be very easy and you should have the right kernel headers in no time ...
Regards,
Scorp123
scorp123.
Sorry for the delay in replying, but things have been very busy over the week-end.
I have found the cause of the problem. It is nothing to do with LinuxMint, it is entirely my fault.
When I wrote that all the kernels in my Synaptic were in the 2.4.## series, I was looking at the "kernels" list and not the "linux" list. Look at the correct part of Synaptic and they are all 2.6.##. All the ones you have marked in your screen-shot are also installed in my Mint. Very sorry about that!
I can't get the spca5xx-source package to work, but I have got the webcam working using the gspcav1-20061216.tar.gz package from mxhaard.free.fr.
I have no idea why my old installation didn't work when I had tried it with this driver, but a new installation works without any problem. Perhaps with all my experiments, I had completely messed up the old installation.
Very many thanks for your help and again, apologies.
A Very Happy New Year to you and all the others in the forum.
Keith
Sorry for the delay in replying, but things have been very busy over the week-end.
I have found the cause of the problem. It is nothing to do with LinuxMint, it is entirely my fault.
When I wrote that all the kernels in my Synaptic were in the 2.4.## series, I was looking at the "kernels" list and not the "linux" list. Look at the correct part of Synaptic and they are all 2.6.##. All the ones you have marked in your screen-shot are also installed in my Mint. Very sorry about that!
I can't get the spca5xx-source package to work, but I have got the webcam working using the gspcav1-20061216.tar.gz package from mxhaard.free.fr.
I have no idea why my old installation didn't work when I had tried it with this driver, but a new installation works without any problem. Perhaps with all my experiments, I had completely messed up the old installation.
Very many thanks for your help and again, apologies.
A Very Happy New Year to you and all the others in the forum.
Keith