Ubuntu Debs

[Brian Johnson]

Hey,
So over this weekend i've spent some time putting together some deb
files for ubuntu gutsy and hardy. The deb files are built using the
v4l2 branch plus a couple of other patches from this list that are not
currently committed. These include Vasily's I420 performance patch,
and Frank's patches for adding sharpness control and separating out
the bridge image adjustment functions. The debs are for the 2.6.22-14
kernel in gutsy and 2.6.24-17 in hardy.

I've currently set up my own apt repository at
http://innercirclemedia.com/apt to use this repository run the
following commands from the terminal:
wget -q http://innercirclemedia.com/apt/E96E8AC2.gpg -O- | sudo apt-key add -

Hardy
sudo wget http://innercirclemedia.com/apt/hardy.list -O
/etc/apt/sources.list.d/sn9c20x.list
Gutsy
sudo wget http://innercirclemedia.com/apt/gutsy.list -O
/etc/apt/sources.list.d/sn9c20x.list

sudo aptitude update

To install the driver use the following where <kernel flavour> is the
flavour of your kernel usually this will be generic

Hardy
sudo aptitude install sn9c20x-module-2.6.24-17-<kernel flavour>
Gutsy
sudo aptitude install sn9c20x-module-2.6.22-14-<kernel flavour>

I currently only have 32bit versions since i'm not suing a 64bit os
but you should still be able to checkout the source and then run
dpkg-buildpackage to build 64bit versions of these. If you do that sen
me the generated files and i can add them into the repository.

[Stefan]

It's going to sound like a stupid question, but how do I update to the
2.6.24-17 kernel in Ubuntu? I sure I don't have the right repositories
enabled.

I'm currently running 2.6.24-16:

stefan@stefan-laptop:/etc/apt$ uname -r
2.6.24-16-generic
stefan@stefan-laptop:/etc/apt$ sudo apt-get install linux-
image-2.6.24-17
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package linux-image-2.6.24-17

This is what my source.list looks like:

stefan@stefan-laptop:/etc/apt$ cat /etc/apt/sources.list
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade
to
# newer versions of the distribution.

#deb cdrom:[Kubuntu-KDE4 8.04 _Hardy Heron_ - Release i386
(20080423.3)]/ hardy main multiverse restricted universe
deb http://au.archive.ubuntu.com/ubuntu/ hardy main restricted
deb-src http://au.archive.ubuntu.com/ubuntu/ hardy main restricted

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

## 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 http://au.archive.ubuntu.com/ubuntu/ hardy universe
deb-src http://au.archive.ubuntu.com/ubuntu/ hardy universe

## 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
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://au.archive.ubuntu.com/ubuntu/ hardy multiverse
deb-src http://au.archive.ubuntu.com/ubuntu/ hardy multiverse

## 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://au.archive.ubuntu.com/ubuntu/ hardy-backports main
restricted universe multiverse
deb-src http://au.archive.ubuntu.com/ubuntu/ hardy-backports main
restricted universe multiverse

deb http://au.archive.ubuntu.com/ubuntu/ hardy-security main
restricted
deb-src http://au.archive.ubuntu.com/ubuntu/ hardy-security main
restricted
deb http://au.archive.ubuntu.com/ubuntu/ hardy-security universe
deb-src http://au.archive.ubuntu.com/ubuntu/ hardy-security universe
deb http://au.archive.ubuntu.com/ubuntu/ hardy-security multiverse
deb http://au.archive.ubuntu.com/ubuntu/ hardy-updates multiverse
universe
deb-src http://au.archive.ubuntu.com/ubuntu/ hardy-security multiverse

Thanks for the help.
Stefan

On May 20, 12:04 am, "Brian Johnson" <brij...@gmail.com> wrote:
> Hey,
> So over this weekend i've spent some time putting together some deb
> files for ubuntu gutsy and hardy. The deb files are built using the
> v4l2 branch plus a couple of other patches from this list that are not
> currently committed. These include Vasily's I420 performance patch,
> and Frank's patches for adding sharpness control and separating out
> the bridge image adjustment functions. The debs are for the 2.6.22-14
> kernel in gutsy and 2.6.24-17 in hardy.
>

> I've currently set up my own apt repository athttp://innercirclemedia.com/aptto use this repository run  the

> following commands from the terminal:

> wget -qhttp://innercirclemedia.com/apt/E96E8AC2.gpg-O- | sudo apt-key add -

[GWater]

Stefan schrieb:

> It's going to sound like a stupid question, but how do I update to the
> 2.6.24-17 kernel in Ubuntu?
>

Why? It's just a new package not a new kernel version.

GWater

[Brian Johnson]

The 2.6.24-17 kernel is actually in the hardy-preposed repository you
can add it to sources.list with the following line
deb http://us.archive.ubuntu.com/ubuntu/ hardy-proposed restricted
main multiverse universe

Also i added a set of metapackages based on kernel flavour called
sn9c20x-module-<flavour>

so now to install the package you should install the proper
metapackage which is set to depend on the right kernel and
sn9c20x-module packages

Gwater the -17 part of the pacakges name specifies the ABI
(Application Binary Interface) version of the ubuntu kernel. when
those numbers change it implies a change in the kernel's ABI so
modules should only be used with the ABI they were compiled against

[Hazor]

The following packages have unmet dependencies:
sn9c20x-module-2.6.24-17-generic: Depends: linux-image-2.6.24-17-
generic but it is not installable
E: Broken packages

^That's why. I'm also having that problem. I've learned my way around
linux, but beyond installing the nvidia drivers have done nothing to
the kernel, and that was all automated for me, soo.. if anyone
wouldn't mind giving a bit of instruction, I would be very thankful.

[Hazor]

On May 20, 9:36 am, GWater <grewa...@googlemail.com> wrote:

[Stefan]

Right, I've managed to install the 2.6.24-17 kernel by adding the
proposed repository to my /etc/apt/sources.list (actually System |
Administration | Software Sources --> Third-Party Software | Add "deb

http://us.archive.ubuntu.com/ubuntu/ hardy-proposed restricted main

multiverse universe", then update via Update Manager). I'm going to
try installing the Microdia Deb packages once I get home.

The main problem I've been having all along is with installation of
the NVidia drivers for my 8400GS - the kernel is recompiled during the
NVidia installation process and this causes insmod/modprobe of
microdia driver to fail for some reason. Reverting back to stock
kernel breaks the NVidia driver. Anyone had any luck with nvidia-glx-
new and microdia?

Stefan

[Brian Johnson]

strange, I use an nvidia 7600 Go in m laptop and don't have any
problems with nvidia-glx-new and the microdia driver.

[Stefan]

I can't get compositing to work under nvidia-glx-new. If I install it
and set "Driver" to "nvidia" in /etc/X11/xorg.conf, when I reboot
there is some problem detecting the monitor or something and I'm put
back into 800x600. If I switch back to "nv", I can get back to full
resolution (1920x1080), but clearly compositing won't work because
"nv" doesn't support it.

If I install the NVidia drivers (including the automated kernel
recompile), I can get compositing to work fine, but then can't get
Microdia drivers to "insmod" with the classic error:

insmod: error inserting ‘microdia.ko’: -1 Unknown symbol in module

I would hugely appreciate it if you could give me an idea of how I
should go about getting this working. I think it's a problem with the
way I've installed nvidia*. Maybe I should start from scratch with the
nvidia drivers (nvidia* purge and fresh kernel package and nvidia-glx-
new/nvidia-settings install).

On May 21, 3:03 pm, "Brian Johnson" <brij...@gmail.com> wrote:
> strange,  I use an nvidia 7600 Go in m laptop and don't have any
> problems with nvidia-glx-new and the microdia driver.
>

> On Tue, May 20, 2008 at 8:39 PM, Stefan <stefanadelb...@gmail.com> wrote:
>
> > Right, I've managed to install the 2.6.24-17 kernel by adding the
> > proposed repository to my /etc/apt/sources.list (actually System |
> > Administration | Software Sources --> Third-Party Software | Add "deb

> >http://us.archive.ubuntu.com/ubuntu/hardy-proposed restricted main

[Brian Johnson]

When you are using the nvidia driver from nvidia-glx-new try looking
at the output from the /var/logs/Xorg.0.log file to see what the
nividia driver is doing. that might hlp in finding out why the X
driver is not working correctly.

[Stefan]

I've managed to get the Microdia package installed at home, but am now
having a problem getting the webcam working when staring Cheese.

Here's the dmesg output:

[ 5599.542828] Linux video capture interface: v2.00
[ 5599.544575] microdia: Microdia USB2.0 webcam driver startup
[ 5599.544621] usbcore: registered new interface driver
usb_microdia_driver
[ 5599.544624] microdia: v0.0.0 : Microdia USB Video Camera
[ 5634.013258] usb 1-6: new high speed USB device using ehci_hcd and
address 4
[ 5634.148451] usb 1-6: configuration #1 chosen from 1 choice
[ 5634.148637] microdia: Microdia USB2.0 Webcam - Product ID 624F.
[ 5634.148640] microdia: Release: 0101
[ 5634.148641] microdia: Number of interfaces : 1
[ 5634.162534] microdia: Microdia USB2.0 Camera is now controlling
video device /dev/video0
[ 5706.047542] microdia: Buffers Allocated 2
[ 5706.091330] microdia: I2C slave 0x50 returned error during write to
address 0x00
[ 5706.091336] microdia: start stream: command 10c1 failed (-1000)!

I think this has to do with an error reported in post "Help with the
624F (http://groups.google.com/group/microdia/browse_thread/thread/
986c577e9a815e1/425f6258fd759a2f?lnk=gst&q=help
+624f#425f6258fd759a2f)". I'm going to try building the driver from
scratch with the fix.

On May 21, 4:50 pm, "Brian Johnson" <brij...@gmail.com> wrote:
> When you are using the nvidia driver from nvidia-glx-new try looking
> at the output from the /var/logs/Xorg.0.log file to see what the
> nividia driver is doing. that might hlp in finding out why the X
> driver is not working correctly.
>

> On Wed, May 21, 2008 at 1:20 AM, Stefan <stefanadelb...@gmail.com> wrote:
>
> > I can't get compositing to work under nvidia-glx-new. If I install it
> > and set "Driver" to "nvidia" in /etc/X11/xorg.conf, when I reboot
> > there is some problem detecting the monitor or something and I'm put
> > back into 800x600. If I switch back to "nv", I can get back to full
> > resolution (1920x1080), but clearly compositing won't work because
> > "nv" doesn't support it.
>
> > If I install the NVidia drivers (including the automated kernel
> > recompile), I can get compositing to work fine, but then can't get
> > Microdia drivers to "insmod" with the classic error:
>
> > insmod: error inserting 'microdia.ko': -1 Unknown symbol in module
>
> > I would hugely appreciate it if you could give me an idea of how I
> > should go about getting this working. I think it's a problem with the
> > way I've installed nvidia*. Maybe I should start from scratch with the
> > nvidia drivers (nvidia* purge and fresh kernel package and nvidia-glx-
> > new/nvidia-settings install).
>
> > On May 21, 3:03 pm, "Brian Johnson" <brij...@gmail.com> wrote:
> >> strange,  I use an nvidia 7600 Go in m laptop and don't have any
> >> problems with nvidia-glx-new and the microdia driver.
>
> >> On Tue, May 20, 2008 at 8:39 PM, Stefan <stefanadelb...@gmail.com> wrote:
>
> >> > Right, I've managed to install the 2.6.24-17 kernel by adding the
> >> > proposed repository to my /etc/apt/sources.list (actually System |
> >> > Administration | Software Sources --> Third-Party Software | Add "deb

> >> >http://us.archive.ubuntu.com/ubuntu/hardy-proposedrestricted main

[Stefan]

I tried installing the packages with the new kernel and was
successful, but had problems starting Cheese. I was getting an error
that I had seen before which can apparently be fixed as described in
post "Help with the 624f" (http://groups.google.com/group/microdia/
browse_thread/thread/986c577e9a815e1/425f6258fd759a2f?lnk=gst&q=help
+624f#425f6258fd759a2f).

I then built the drivers from scratch (v4l-experimental branch)
against the updated kernel after I had applied the fix and now get
this dmesg output and Cheese doesn't seem to be able to start the cam:

[ 41.802643] microdia: Microdia USB2.0 webcam driver startup
[ 41.802676] microdia: Microdia USB2.0 Webcam - Product ID 624F.
[ 41.802678] microdia: Release: 0101
[ 41.802679] microdia: Number of interfaces : 1
[ 41.816880] microdia: Microdia USB2.0 Camera is now controlling
video device /dev/video0
[ 42.067979] usbcore: registered new interface driver
usb_microdia_driver
[ 42.067982] microdia: v0.0.0 : Microdia USB Video Camera
[ 108.579730] microdia: Buffers Allocated 2
[ 108.621779] microdia: I2C slave 0x50 returned error during write to
address 0x00

Back to square one!

On May 21, 4:50 pm, "Brian Johnson" <brij...@gmail.com> wrote:
> When you are using the nvidia driver from nvidia-glx-new try looking
> at the output from the /var/logs/Xorg.0.log file to see what the
> nividia driver is doing. that might hlp in finding out why the X
> driver is not working correctly.
>

> On Wed, May 21, 2008 at 1:20 AM, Stefan <stefanadelb...@gmail.com> wrote:
>
> > I can't get compositing to work under nvidia-glx-new. If I install it
> > and set "Driver" to "nvidia" in /etc/X11/xorg.conf, when I reboot
> > there is some problem detecting the monitor or something and I'm put
> > back into 800x600. If I switch back to "nv", I can get back to full
> > resolution (1920x1080), but clearly compositing won't work because
> > "nv" doesn't support it.
>
> > If I install the NVidia drivers (including the automated kernel
> > recompile), I can get compositing to work fine, but then can't get
> > Microdia drivers to "insmod" with the classic error:
>
> > insmod: error inserting 'microdia.ko': -1 Unknown symbol in module
>
> > I would hugely appreciate it if you could give me an idea of how I
> > should go about getting this working. I think it's a problem with the
> > way I've installed nvidia*. Maybe I should start from scratch with the
> > nvidia drivers (nvidia* purge and fresh kernel package and nvidia-glx-
> > new/nvidia-settings install).
>
> > On May 21, 3:03 pm, "Brian Johnson" <brij...@gmail.com> wrote:
> >> strange,  I use an nvidia 7600 Go in m laptop and don't have any
> >> problems with nvidia-glx-new and the microdia driver.
>
> >> On Tue, May 20, 2008 at 8:39 PM, Stefan <stefanadelb...@gmail.com> wrote:
>
> >> > Right, I've managed to install the 2.6.24-17 kernel by adding the
> >> > proposed repository to my /etc/apt/sources.list (actually System |
> >> > Administration | Software Sources --> Third-Party Software | Add "deb

> >> >http://us.archive.ubuntu.com/ubuntu/hardy-proposedrestricted main

[Stefan]

I tried installing the packages with the new kernel and was
successful, but had problems starting Cheese. I was getting an error
that I had seen before which can apparently be fixed as described in
post "Help with the 624f" (http://groups.google.com/group/microdia/
browse_thread/thread/986c577e9a815e1/425f6258fd759a2f?lnk=gst&q=help
+624f#425f6258fd759a2f).

I then built the drivers from scratch (v4l-experimental branch)
against the updated kernel after I had applied the fix and now get
this dmesg output and Cheese doesn't seem to be able to start the cam:

[ 41.802643] microdia: Microdia USB2.0 webcam driver startup
[ 41.802676] microdia: Microdia USB2.0 Webcam - Product ID 624F.
[ 41.802678] microdia: Release: 0101
[ 41.802679] microdia: Number of interfaces : 1
[ 41.816880] microdia: Microdia USB2.0 Camera is now controlling
video device /dev/video0
[ 42.067979] usbcore: registered new interface driver
usb_microdia_driver
[ 42.067982] microdia: v0.0.0 : Microdia USB Video Camera
[ 108.579730] microdia: Buffers Allocated 2
[ 108.621779] microdia: I2C slave 0x50 returned error during write to
address 0x00

Back to square one!

On May 21, 4:50 pm, "Brian Johnson" <brij...@gmail.com> wrote:
> When you are using the nvidia driver from nvidia-glx-new try looking
> at the output from the /var/logs/Xorg.0.log file to see what the
> nividia driver is doing. that might hlp in finding out why the X
> driver is not working correctly.
>

> On Wed, May 21, 2008 at 1:20 AM, Stefan <stefanadelb...@gmail.com> wrote:
>
> > I can't get compositing to work under nvidia-glx-new. If I install it
> > and set "Driver" to "nvidia" in /etc/X11/xorg.conf, when I reboot
> > there is some problem detecting the monitor or something and I'm put
> > back into 800x600. If I switch back to "nv", I can get back to full
> > resolution (1920x1080), but clearly compositing won't work because
> > "nv" doesn't support it.
>
> > If I install the NVidia drivers (including the automated kernel
> > recompile), I can get compositing to work fine, but then can't get
> > Microdia drivers to "insmod" with the classic error:
>
> > insmod: error inserting 'microdia.ko': -1 Unknown symbol in module
>
> > I would hugely appreciate it if you could give me an idea of how I
> > should go about getting this working. I think it's a problem with the
> > way I've installed nvidia*. Maybe I should start from scratch with the
> > nvidia drivers (nvidia* purge and fresh kernel package and nvidia-glx-
> > new/nvidia-settings install).
>
> > On May 21, 3:03 pm, "Brian Johnson" <brij...@gmail.com> wrote:
> >> strange,  I use an nvidia 7600 Go in m laptop and don't have any
> >> problems with nvidia-glx-new and the microdia driver.
>
> >> On Tue, May 20, 2008 at 8:39 PM, Stefan <stefanadelb...@gmail.com> wrote:
>
> >> > Right, I've managed to install the 2.6.24-17 kernel by adding the
> >> > proposed repository to my /etc/apt/sources.list (actually System |
> >> > Administration | Software Sources --> Third-Party Software | Add "deb

> >> >http://us.archive.ubuntu.com/ubuntu/hardy-proposedrestricted main

[Brian Johnson]

hmm yeah i just tested and cheese seems not to work in either master
or v4l2-experimental at the moment. If i reset the v4l2-experiemental
branch back to the commit where i applied the original set of patches
to create that branch cheese starts wokring again so there must be a
commit that was applied to master and later merged into
v4l2-experimental that broke things when using cheese. I'll have to
see if i can track that down at some point. for the momemnt try using
mplayer instead that should at least work.

mplayer tv:// -tv driver=v4l2:width=640:height=480:outfmt=i420:fps=30

[Brian Johnson]

Alright i've found out which commit was causing problems and i've
attached a patch that reverts that commit using this cheese should
work again.

[Dave Neuer]

On Wed, May 21, 2008 at 10:35 AM, Brian Johnson <bri...@gmail.com> wrote:
> Alright i've found out which commit was causing problems and i've
> attached a patch that reverts that commit using this cheese should
> work again.

Rather than applying that patch, can we find out why Cheese doesn't
work with it?

the 624f is NOT a VGA cam, it supports 1280x1024.

Dave

[Brian Johnson]

I know the camera supports supports SXGA. The problem with that patch
is that when you actually try to use 1280x1024 taht driver decides
calculates teh frame_size based on that resolution since the frames
being returned from the camera are still 640x480 the driver never
finishes filling the frame buffer and therefore never in v4l2 no
buffers are ever made availbel and the app just sits in teh DQBUF
ioctl waiting for a frame it will never get. I think the correct
solution for this would actually involve figuring out how to tell the
camera hardware to switch resolutions properly.

[Dave Neuer]

On Wed, May 21, 2008 at 11:43 AM, Brian Johnson <bri...@gmail.com> wrote:
>
> I know the camera supports supports SXGA. The problem with that patch
> is that when you actually try to use 1280x1024 taht driver decides
> calculates teh frame_size based on that resolution since the frames
> being returned from the camera are still 640x480 the driver never
> finishes filling the frame buffer and therefore never in v4l2 no
> buffers are ever made availbel and the app just sits in teh DQBUF
> ioctl waiting for a frame it will never get. I think the correct
> solution for this would actually involve figuring out how to tell the
> camera hardware to switch resolutions properly.

ACK.

The patch was mine, but I didn't realize that there was no resolution
switching (so, are all of our supported cam models only doing VGA,
then)?

I suppose we could revert the commit while we try to figure out what
the resolution switching protocol is (though, I was under the
impression that somebody had worked that out a long time ago -- I'll
have to go digging in the archives to see why I thought that).

Dave

[Dave Neuer]

BTW, I did test the code before I committed it, but only in the master
branch, and only with camorama -- where it did work.

Dave

[Dave Neuer]

On Wed, May 21, 2008 at 11:43 AM, Brian Johnson <bri...@gmail.com> wrote:
>
> when you actually try to use 1280x1024 taht driver decides
> calculates teh frame_size based on that resolution

That is a bug, right? We should never calculate the frame size based
on the max resolution a cam can support, we should keep track of the
requested resolution, and set the frame size based on that. In the
absence of the ability to actually successfully request any resolution
other than 640x480 we can just make that the global default resolution
and init the "requested" resolution to that value.

That's a better fix than reverting the patch, IMO, since the latter
loses valuable information (in this case, the max resolution the cam
can actually support).

If that sounds reasonable I'll try to whip a patch up as soon as I get
the time; since I don't have much time these days, if someone wants to
beat me to it, feel free :-)

Dave

[Brian Johnson]

problem with that is that again without hardware resolution switching
if you request say 320x240 you will end up setting a framesize smaller
then the frames being returned by the camera, wich will cause problems
as well in the driver. since the completion routine checks to see how
much data is being put into the buffer and if you are trying to go
beyond your declared framesize it will give you framebuffer overflow
errors. We really need to figure out how to do the hardware resolution
swithci in order to fix this stuff up right.

[Dave Neuer]

On Wed, May 21, 2008 at 12:18 PM, Brian Johnson <bri...@gmail.com> wrote:
>
> problem with that is that again without hardware resolution switching
> if you request say 320x240 you will end up setting a framesize smaller
> then the frames being returned by the camera, wich will cause problems
> as well in the driver.

That's why I suggested hard-coding the "requested" value right now at
640x480 (sorry if I was unclear about that).

> We really need to figure out how to do the hardware resolution
> swithci in order to fix this stuff up right.

Agreed. But in the meantime, it would be nice to have accurate info
about the cam models AND have the driver work at least as well as the
best it has ever worked.

Dave

[Ravan]

Hi Brian,

I would like to attempt building the packages for AMD64 but am new to
this. Can you help me on my way a little? How do I check out the
source? I added your repo to my sources list, refreshed but cannot
find any source packages in Synaptic... If I can get this figured out,
I will be happy to send you the resulting 64bit deb package.

System: Hardy AMD64 with 2.6.24-17-generic kernel.

Thanks for any info

--ravan

On May 19, 4:04 pm, "Brian Johnson" <brij...@gmail.com> wrote:
> Hey,
> So over this weekend i've spent some time putting together some deb
> files for ubuntu gutsy and hardy. The deb files are built using the
> v4l2 branch plus a couple of other patches from this list that are not
> currently committed. These include Vasily's I420 performance patch,
> and Frank's patches for adding sharpness control and separating out
> the bridge image adjustment functions. The debs are for the 2.6.22-14
> kernel in gutsy and 2.6.24-17 in hardy.
>

> I've currently set up my own apt repository athttp://innercirclemedia.com/aptto use this repository run  the

> following commands from the terminal:

> wget -qhttp://innercirclemedia.com/apt/E96E8AC2.gpg-O- | sudo apt-key add -
>
> Hardy

> sudo wgethttp://innercirclemedia.com/apt/hardy.list-O
> /etc/apt/sources.list.d/sn9c20x.list
> Gutsy
> sudo wgethttp://innercirclemedia.com/apt/gutsy.list-O

[Brian Johnson]

I'm not sure if you can download source packages through synaptic. I
use apt-get from the command line. to try and build this do the
following
# apt-get source sn9c20x-module-2.6.24
# cd sn9c20x-module-2.6.24-2.6.24
# dpkg-buildpackage
Those commands should hopefully compile and create the necessary deb
files. one thing it will try to build a package for all kernel
flavours the amd64 supports so you'll watn to install all the
available linux-headers packages for your your architecture first.
let me know if you have any other problems

[Ravan]

Wow, ALL linux-header packages? That's really a lot... even those (to
me) obscure LBM and LUM versions?

On May 22, 2:48 am, "Brian Johnson" <brij...@gmail.com> wrote:
> I'm not sure if you can download source packages through synaptic. I
> use apt-get from the command line.  to try and build this do the
> following
> # apt-get source sn9c20x-module-2.6.24
> # cd sn9c20x-module-2.6.24-2.6.24
> # dpkg-buildpackage
> Those commands should hopefully compile and create the necessary deb
> files. one thing it will try to build a package for all kernel
> flavours the amd64 supports so you'll watn to install all the
> available linux-headers packages for your your architecture first.
> let me know if you have any other problems
>

> On Wed, May 21, 2008 at 8:27 PM, Ravan <ravanha...@gmail.com> wrote:
>
> > Hi Brian,
>
> > I would like to attempt building the packages for AMD64 but am new to
> > this. Can you help me on my way a little? How do I check out the
> > source? I added your repo to my sources list, refreshed but cannot
> > find any source packages in Synaptic... If I can get this figured out,
> > I will be happy to send you the resulting 64bit deb package.
>
> > System: Hardy AMD64 with 2.6.24-17-generic kernel.
>
> > Thanks for any info
>
> > --ravan
>
> > On May 19, 4:04 pm, "Brian Johnson" <brij...@gmail.com> wrote:
> >> Hey,
> >> So over this weekend i've spent some time putting together some deb
> >> files for ubuntu gutsy and hardy. The deb files are built using the
> >> v4l2 branch plus a couple of other patches from this list that are not
> >> currently committed. These include Vasily's I420 performance patch,
> >> and Frank's patches for adding sharpness control and separating out
> >> the bridge image adjustment functions. The debs are for the 2.6.22-14
> >> kernel in gutsy and 2.6.24-17 in hardy.
>

> >> I've currently set up my own apt repository athttp://innercirclemedia.com/apttouse this repository run  the

[Ravan]

Ok, tried your suggestion (without ... ) and the dpkg-buildpackage
process ended in:

dpkg-deb: building package `sn9c20x-module-openvz' in `../sn9c20x-
module-openvz_2.6.24-17.2_amd64.deb'.
signfile sn9c20x-module-2.6.24_2.6.24-17.2.dsc
gpg: skipped "Brian Johnson <bri...@gmail.com>": secret key not
available
gpg: [stdin]: clearsign failed: secret key not available

dpkg-genchanges >../sn9c20x-module-2.6.24_2.6.24-17.2_amd64.changes
dpkg-genchanges: including full source code in upload
dpkg-buildpackage: full upload; Debian-native package (full source is
included)
dpkg-buildpackage: warning: Failed to sign .dsc and .changes file

But leaving a whole bunch of deb packages in my home dir... So if it
is all OK, I can send them to ya. Shall I send them via e-mail ?

I suppose I would have to reboot using the 2.6.24-16 kernel to be able
to generate packages for that one. Correct?

On May 22, 2:48 am, "Brian Johnson" <brij...@gmail.com> wrote:

> I'm not sure if you can download source packages through synaptic. I
> use apt-get from the command line.  to try and build this do the
> following
> # apt-get source sn9c20x-module-2.6.24
> # cd sn9c20x-module-2.6.24-2.6.24
> # dpkg-buildpackage
> Those commands should hopefully compile and create the necessary deb
> files. one thing it will try to build a package for all kernel
> flavours the amd64 supports so you'll watn to install all the
> available linux-headers packages for your your architecture first.
> let me know if you have any other problems
>

> On Wed, May 21, 2008 at 8:27 PM, Ravan <ravanha...@gmail.com> wrote:
>
> > Hi Brian,
>
> > I would like to attempt building the packages for AMD64 but am new to
> > this. Can you help me on my way a little? How do I check out the
> > source? I added your repo to my sources list, refreshed but cannot
> > find any source packages in Synaptic... If I can get this figured out,
> > I will be happy to send you the resulting 64bit deb package.
>
> > System: Hardy AMD64 with 2.6.24-17-generic kernel.
>
> > Thanks for any info
>
> > --ravan
>
> > On May 19, 4:04 pm, "Brian Johnson" <brij...@gmail.com> wrote:
> >> Hey,
> >> So over this weekend i've spent some time putting together some deb
> >> files for ubuntu gutsy and hardy. The deb files are built using the
> >> v4l2 branch plus a couple of other patches from this list that are not
> >> currently committed. These include Vasily's I420 performance patch,
> >> and Frank's patches for adding sharpness control and separating out
> >> the bridge image adjustment functions. The debs are for the 2.6.22-14
> >> kernel in gutsy and 2.6.24-17 in hardy.
>

> >> I've currently set up my own apt repository athttp://innercirclemedia.com/apttouse this repository run  the

[Brian Johnson]

Ok i've got the packages and will add them to the repository when i
get a chance. To build for a different kernel doesn't really require
rebooting into that kernel you just need the headers for that kernel
installed so it will compile against the right kernel headers. Also
the way these debian packages scripts work it pull the kernel version
to use from the changelog file so you would need to redo that file for
teh correct kernel version you wanted to use.

[Brian Johnson]

hardy 64bit debs should now be available courtesy of Ravan.

[Ravan]

could you give a short step-by-step for this? i have all 2.6.24-16
kernel headers installed but the dpkg-buildpackeage will only build
for 2.6.24-17 ... what changelog file do i need to edit/redo -- and
how ?

On May 23, 3:30 am, "Brian Johnson" <brij...@gmail.com> wrote:
> Ok i've got the packages and will add them to the repository when i
> get a chance.  To build for a different kernel doesn't really require
> rebooting into that kernel you just need the headers for that kernel
> installed so it will compile against the right kernel headers. Also
> the way these debian packages scripts work it pull the kernel version
> to use from the changelog file so you would need to redo that file for
> teh correct kernel version you wanted to use.
>

> On Thu, May 22, 2008 at 7:18 PM, Ravan <ravanha...@gmail.com> wrote:
>
> > Ok, tried your suggestion (without ... ) and the dpkg-buildpackage
> > process ended in:
>
> > dpkg-deb: building package `sn9c20x-module-openvz' in `../sn9c20x-
> > module-openvz_2.6.24-17.2_amd64.deb'.
> >  signfile sn9c20x-module-2.6.24_2.6.24-17.2.dsc

> > gpg: skipped "Brian Johnson <brij...@gmail.com>": secret key not

> >> >> I've currently set up my own apt repository athttp://innercirclemedia.com/apttousethis repository run  the

[Brian Johnson]

the changelog file is in the debian directory if you look at that file
there are currently tw entries inside you are looking for the lines
that look like this
sn9c20x-module-2.6.24 (2.6.24-16.2) hardy; urgency=low

its the bit in parenthesis that tell it which kernel version to use
you should change the -17 to a -16 for both those lines

[Ravan]

the 2.6.24-16 debs should be in your mailbox now :)

On May 25, 4:57 pm, "Brian Johnson" <brij...@gmail.com> wrote:
> the changelog file is in the debian directory if you look at that file
> there are currently tw entries inside you are looking for the lines
> that look like this
> sn9c20x-module-2.6.24 (2.6.24-16.2) hardy; urgency=low
>
> its the bit in parenthesis that tell it which kernel version to use
> you should change the -17 to a -16 for both those lines
>

> >> >> >> I've currently set up my own apt repository athttp://innercirclemedia.com/apttousethisrepository run  the

[Zernik]

Don't expect too many downloads of them - my Hardy kernel updated
automatically to 2.6.24-17 this morning.

Zernik

> > >> >> >> I've currently set up my own apt repository athttp://innercirclemedia.com/apttousethisrepositoryrun  the