On Saturday 15 August 2009 13:27:43 Bernard wrote:
> Hi to Everyone,
>
> On an attempt to install OSS instead of ALSA on my Debian Sarge, an
> error message pointed out that I missed kernel sources and headers on my
> system. OSS 4.1 therefore refused to compile.
>
> My kernel
Hi to Everyone,
On an attempt to install OSS instead of ALSA on my Debian Sarge, an
error message pointed out that I missed kernel sources and headers on my
system. OSS 4.1 therefore refused to compile.
My kernel is 2.6.20-16-386. On Sarge, kernels are 2.4..., but, about 18
months ago
On Wed, Jan 02, 2008 at 06:09:45PM +0530, Pranav Jadhav wrote:
> Hi ,
>
> I am using Linux -2.6.20 with iptables-1.3.8.
Show us your /etc/apt/sources.list
> I am getting the iptables error :
>
> "/sbin/iptables -I OUTPUT -p udp -m multiport --sport
> 23,22,161,80,
Hi ,
I am using Linux -2.6.20 with iptables-1.3.8.
I am getting the iptables error :
"/sbin/iptables -I OUTPUT -p udp -m multiport --sport
23,22,161,80,443,53,49 -m state --state NEW,ESTABLISHED,RELATED -o mgmt0
-j ACCEPT"
iptables: No chain/target/match by that name
ip
Not too long ago I was going to upgrade my kernel, I am currently
running 2.6.18.1, and downloaded the latest 2.6.20 tarball. I went
through the usual steps. I configured it carefully and then
compiled it via make-kpkg. Lastly I installed it with dpkg. When I
rebooted everything seemed okay
Because of the many questions how has this package been built and what it
does exactly I have written a small page that clarifies this. Its location
is :
http://grizach.servebeer.com/nvpatch/ http://grizach.servebeer.com/nvpatch/
Julian
--
View this message in context:
http://www.nabble.com/H
Hi
I am having some problems installing a paravirt RHEL guest on a deb amd64 xen
machine
uname -a = Linux debxen 2.6.20-1-xen-amd64 #1 SMP Tue Apr 24 22:23:22 UTC 2007
x86_64 GNU/Linux == xm info ==
host : debxen
release: 2.6.20-1-xen
Hugo Vanwoerkom wrote:
Hi,
linux-image-2.6.20-1-k7 (latest version in Sid) has a problem:
CONFIG_PARAVIRT=y
That means that the nvidia driver install will fail. For this reason:
http://www.nvnews.net/vbulletin/showthread.php?t=90214
post #9 by Zander.
Solution:
Install the linux-2.6 source
Stephen Cormier wrote:
> I do not get a .config in a freshly unpacked 2.6.20 from the kernel.org.
>
in the debian linux source package you actually get a .config
>> grep -i sata linux-source-2.6.20/.config
>> # CONFIG_BLK_DEV_IDE_SATA is not set
>>
>> where h
Hi,
Based on the previous post in this thread I created a patched version of the
driver archive that consists of fixed version of modpost as well as fixed
version of the Makefile for the driver's kernel module. This all wrapped in
a script that performs the steps automaticaly and tries to ensure s
http://www.nvnews.net/vbulletin/showthread.php?t=87541
I have reworked the solution for Debian based upon another forum thread:
http://www.nvnews.net/vbulletin/showthread.php?t=89844
1. Rebuild the linux-kbuild-2.6.20 .deb:
a. apt-get update
b. apt-get build-dep linux-kbuild-2.6.20
As user:
already then with the
> > SATA naming they changed you will need to re-compile with the proper
> > options set the oldconfig method does not pick this up. An example of the
> > change below.
> >
> > grep -i sata_nv /boot/config-2.6.8-11-amd64-generic
> > CONFIG_SCSI_
Hi,
linux-image-2.6.20-1-k7 (latest version in Sid) has a problem:
CONFIG_PARAVIRT=y
That means that the nvidia driver install will fail. For this reason:
http://www.nvnews.net/vbulletin/showthread.php?t=90214
post #9 by Zander.
Solution:
Install the linux-2.6 source package + modify the
o re-compile with the proper options set the oldconfig
> method does not pick this up. An example of the change below.
>
> grep -i sata_nv /boot/config-2.6.8-11-amd64-generic
> CONFIG_SCSI_SATA_NV=m
>
> grep -i sata_nv /boot/config-2.6.20-ck1-core2duo
> CONFIG_SATA_NV=y
mh..
o re-compile with the proper options set the oldconfig
> method does not pick this up. An example of the change below.
>
> grep -i sata_nv /boot/config-2.6.8-11-amd64-generic
> CONFIG_SCSI_SATA_NV=m
>
> grep -i sata_nv /boot/config-2.6.20-ck1-core2duo
> CONFIG_SATA_NV=y
mh..
On April 26, 2007 04:00:36 pm Lorenzo Bettini wrote:
> Stephen Cormier wrote:
> > On April 25, 2007 04:48:17 pm Lorenzo Bettini wrote:
> >> Hi
> >>
> >> I updated the linux sources (debian package) from 2.6.18 to 2.6.20.
> >> Copied the
Stephen Cormier wrote:
On April 25, 2007 04:48:17 pm Lorenzo Bettini wrote:
Hi
I updated the linux sources (debian package) from 2.6.18 to 2.6.20.
Copied the previous .config and issued a make oldconfig
However, the new kernel does not boot: it freezes with a kernel panic
when trying to mount
Greg Folkert wrote:
On Wed, 2007-04-25 at 19:48 -0400, Douglas Allan Tutty wrote:
On Wed, Apr 25, 2007 at 09:48:17PM +0200, Lorenzo Bettini wrote:
I updated the linux sources (debian package) from 2.6.18 to 2.6.20.
Copied the previous .config and issued a make oldconfig
However, the new
On Wed, 2007-04-25 at 19:48 -0400, Douglas Allan Tutty wrote:
> On Wed, Apr 25, 2007 at 09:48:17PM +0200, Lorenzo Bettini wrote:
> > I updated the linux sources (debian package) from 2.6.18 to 2.6.20.
> > Copied the previous .config and issued a make oldconfig
> >
> > H
On April 25, 2007 04:48:17 pm Lorenzo Bettini wrote:
> Hi
>
> I updated the linux sources (debian package) from 2.6.18 to 2.6.20.
> Copied the previous .config and issued a make oldconfig
>
> However, the new kernel does not boot: it freezes with a kernel panic
> when try
On Wed, Apr 25, 2007 at 09:48:17PM +0200, Lorenzo Bettini wrote:
> I updated the linux sources (debian package) from 2.6.18 to 2.6.20.
> Copied the previous .config and issued a make oldconfig
>
> However, the new kernel does not boot: it freezes with a kernel panic
> when tryi
Hi
I updated the linux sources (debian package) from 2.6.18 to 2.6.20.
Copied the previous .config and issued a make oldconfig
However, the new kernel does not boot: it freezes with a kernel panic
when trying to mount the root partition...
My laptop is a sony vaio...
On other computers
Hugo Vanwoerkom wrote:
Hi,
If you run the propriatory nvidia module for X in the just released
2.6.20-1-k7/686 you will get bitten by:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419943
It seems that the config uses CONFIG_PARAVIRT enabled and nvidia does
not like that.
It's ba
"modprobe i810"?
>> >
>> > IMHO i810.ko is something about drm,
>>
>> Something about drm?
>
> I do think so because of the location and dependency of the module:
>
> | spirit:/lib/modules/2.6.20-1-686/kernel/drivers/char/drm# modinfo i810.ko
> |
hing about drm?
I do think so because of the location and dependency of the module:
| spirit:/lib/modules/2.6.20-1-686/kernel/drivers/char/drm# modinfo i810.ko
| filename: i810.ko
| author: VA Linux Systems Inc.
| description:Intel i810
| license:GPL and additional ri
Hi,
If you run the propriatory nvidia module for X in the just released
2.6.20-1-k7/686 you will get bitten by:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419943
It seems that the config uses CONFIG_PARAVIRT enabled and nvidia does
not like that.
It's back to 2.6.18 or wait til
nse. Running
> ifup at this point I receive a message saying that eth1 is already
> configured. Running ifdown I get errors saying the network is not
> reachable.
>
> If I boot back into 2.6.18-4-686 the card works normally and acquires an
> IP address from the dhcp server.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/20/07 01:54, Wang Xu wrote:
> On Fri, Apr 20, 2007 at 01:42:29AM -0500, Kent West wrote:
>> Perhaps try "modprobe i810"?
>
> IMHO i810.ko is something about drm,
Something about drm?
> and for 865G chipset
On Fri, Apr 20, 2007 at 01:42:29AM -0500, Kent West wrote:
> Perhaps try "modprobe i810"?
IMHO i810.ko is something about drm, and for 865G chipset, it's
recommended to use i915 instead of i810/i830. And I have tried
i915 already, but nothing happened.
Thank you!
Wang Xu
--
To UNSUBSCRIBE, e
On 4/20/07, Wang Xu <[EMAIL PROTECTED]> wrote:
I have an intel 865G integrated VGA adapter, and it works fine with
kernel 2.6.18 and before. However, when I update it to 2.6.20, the
X server cannot be started, and give the following message
(EE) I810(0): cannot continue
(II) I810(0)
I have an intel 865G integrated VGA adapter, and it works fine with
kernel 2.6.18 and before. However, when I update it to 2.6.20, the
X server cannot be started, and give the following message
(EE) I810(0): cannot continue
(II) I810(0): VESA BIOS not detected
(EE) I810(0): VBE
s not
reachable.
If I boot back into 2.6.18-4-686 the card works normally and acquires an
IP address from the dhcp server.
The entire installation is Etch except for the 2.6.20-1-686 kernel as I
installed it to try to solve the ACPI problems and ATA hardware
recognition problems I was having wit
On Fri, 2007-04-13 at 15:17 -0400, Curt Howland wrote:
> It's so nice that kernel 2.6.20 has made it into Sid. It works very
> well.
>
> However, linux-kbuild-2.6.20 does not exist. So I cannot compile the
> custom kernel modules nvidia and madwifi to make a working syst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's so nice that kernel 2.6.20 has made it into Sid. It works very
well.
However, linux-kbuild-2.6.20 does not exist. So I cannot compile the
custom kernel modules nvidia and madwifi to make a working system.
Which makes me wonder, since
Roby wrote:
> module-assistant fails while building linux-wlan-ng against
> my 2.6.20 (or 2.6.20.2) kernel, complaining about INIT_WORK.
> I'm using the latest package (0.2.7+dfsg-2). What appears
> to be this same problem was announced in bug #406823 in
> January and fixe
module-assistant fails while building linux-wlan-ng against
my 2.6.20 (or 2.6.20.2) kernel, complaining about INIT_WORK.
I'm using the latest package (0.2.7+dfsg-2). What appears
to be this same problem was announced in bug #406823 in
January and fixed ... but not for me.
The error see
Got 2.6.20 running, connected. fine.
Did this on advice of posters here:
1. Delete network (netfilter, iptables stuff) from .config.
2. Do make, answer questions.
3. I realized I still had no conntrack stuff so ran make menuconfig and
selected these module.
4. Compiled.
It boots up fine
If you follow 'kerneltrap.org', 2.6.19 and 2.6.20 are bug-ridden. 2.6.19
shipped with bugs and 2.6.20 hasn't worked them all out yet. But if you enjoy
playing with the latest 'git' data, this is what happens. I usually wait until
a released version is a few weeks ol
So playing with make menuconfig: I can get this module and be missing half of
what was around in previous kernels or get the rest back and still be missing
ip_conntrack_ftp.ko. Either way, the thing will boot but will not connect. It
may not work with nvidia's driver either at this point.
So ma
t; >
>> > Any ideas? Do I need this and why?
>> >
>> > Google had something about setting: modprobe ip_conntrack_ftp
>> > ports=21,2121 if compiled as a module. So I set the previously unset
>> > constant=m and am recompiling. Where would I specify
is and why?
> >
> > Google had something about setting: modprobe ip_conntrack_ftp
> > ports=21,2121 if compiled as a module. So I set the previously unset
> > constant=m and am recompiling. Where would I specify the modprobe
> > arguments?
>
> I ran into this compiling
iptables init.d script has NO modprobe at all.
I found a modprobe for this module in /etc/rc.firewall and /etc/rc.firewall~
which relates to guarddog.
I can append the ports= there, see what happens in 2.6.18 reboot and 2.6.20
reboot. Might need to test uname -r for 2.6.20?
iptable and related s
=21,2121 if
compiled as a module. So I set the previously unset constant=m and am
recompiling. Where would I specify the modprobe arguments?
I ran into this compiling 2.6.20 with the .config of 2.6.19 and FireHol
complained as you describe.
I changed the .config as follows:
diff .config.2.6.20
On Thu, 22 Feb 2007 15:55:30 +0200
David Baron <[EMAIL PROTECTED]> wrote:
> Compiled it taking all the defaults on new features. It boots just fine but
> has fatal ip_tables errors over and over missing this item. Cannot connect to
> internet.
>
> Any ideas? Do I need this and why?
>
> Google
Compiled it taking all the defaults on new features. It boots just fine but
has fatal ip_tables errors over and over missing this item. Cannot connect to
internet.
Any ideas? Do I need this and why?
Google had something about setting: modprobe ip_conntrack_ftp ports=21,2121 if
compiled as a mo
On Tue, Feb 20, 2007 at 08:45:41AM -0800, Andrew Sackville-West wrote:
> On Tue, Feb 20, 2007 at 03:04:50PM +, Jon Dowland wrote:
> >
> > Etch being in freeze does not proclude new packages being
> > accepted into sid. Although I expect that the kernel team
> > are busy working on the kernels
On Tue, Feb 20, 2007 at 03:04:50PM +, Jon Dowland wrote:
>
> Etch being in freeze does not proclude new packages being
> accepted into sid. Although I expect that the kernel team
> are busy working on the kernels for Etch, and perhaps new
> kernels for sid are a low-priority.
my understanding
Greg Folkert wrote:
On Mon, 2007-02-19 at 06:03 -0600, Hugo Vanwoerkom wrote:
Greg Trounson wrote:
Any idea when kernel 2.6.20 is going to show up in Sid? The most recent
version I see in Sid is 2.6.18-4.
Both 2.6.18 and 2.6.19 have a critical cifs bug that makes any machine
that mounts
On Sun, Feb 18, 2007 at 07:17:58PM -0500, Greg Folkert
wrote:
> On Mon, 2007-02-19 at 13:15 +1300, Greg Trounson wrote:
> > Any idea when kernel 2.6.20 is going to show up in Sid?
^^^
> > The most recent version I see in
On Mon, 2007-02-19 at 06:03 -0600, Hugo Vanwoerkom wrote:
> Greg Trounson wrote:
> > Any idea when kernel 2.6.20 is going to show up in Sid? The most recent
> > version I see in Sid is 2.6.18-4.
> >
> > Both 2.6.18 and 2.6.19 have a critical cifs bug that makes a
-project.org/ etch main
deb-src http://debian.beryl-project.org/ etch main
in my sources.list, and running apt-get update; apt-get install beryl, I
have radeon driver + composite + kernel 2.6.20 + beryl up and running :)
Cheers,
Ivan
Inko IA wrote:
> Hi Ivan!
>
> I used on
Greg Trounson wrote:
Any idea when kernel 2.6.20 is going to show up in Sid? The most recent
version I see in Sid is 2.6.18-4.
Both 2.6.18 and 2.6.19 have a critical cifs bug that makes any machine
that mounts windows shares pretty much unusable.
thanks,
Greg
[EMAIL PROTECTED]:~$ uname
On Mon, 2007-02-19 at 13:15 +1300, Greg Trounson wrote:
> Any idea when kernel 2.6.20 is going to show up in Sid? The most recent
> version I see in
> Sid is 2.6.18-4.
>
> Both 2.6.18 and 2.6.19 have a critical cifs bug that makes any machine that
> mounts windows
&g
Any idea when kernel 2.6.20 is going to show up in Sid? The most recent version I see in
Sid is 2.6.18-4.
Both 2.6.18 and 2.6.19 have a critical cifs bug that makes any machine that mounts windows
shares pretty much unusable.
thanks,
Greg
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
t; I was running happily Debian Unstable for 3 years, when finally my hard
>> drive died, and I had to install Debian from scratch. I want to install
>> beryl
>>
>> http://wiki.beryl-project.org/wiki/Install/Debian
>>
>> Very nice outlook which obviously requires
l
>>
>> http://wiki.beryl-project.org/wiki/Install/Debian
>>
>> Very nice outlook which obviously requires 3D acceleration and (as
>> outlined on the page above) the
>> option:
>>
>> Section "Extensions"
>> Option "Composi
;Extensions"
Option "Composite" "Enable"
EndSection
I tried kernels 2.6.19 and 2.6.20 with the latest ati drivers (8.33.6-1)
and the ones included in Debian (2.28.8). In a short what I did is:
# ln -sf bash /bin/sh
# bash ./ati-driver-installer-8.33.6-x86.x86_64.run --bu
Hi,
Ivan Glushkov schrieb:
[..]
===> kernel 2.6.19 (with both driver versions), 3D acceleration works if
Section "Extensions"
Option "Composite" "Disable"
EndSection
But if I enable it I get:
% fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
Open
above) the
option:
Section "Extensions"
Option "Composite" "Enable"
EndSection
I tried kernels 2.6.19 and 2.6.20 with the latest ati drivers (8.33.6-1)
and the ones included in Debian (2.28.8). In a short what I did is:
# ln -sf bash /bin/sh
# bash ./ati-driver-i
arted with a net installed etch rc1 for amd64. I have ASUS
> > > > > > > M2N-MX mobo with SATA harddrive and IDE dvd writer. Install
> > > > > > > went okay, but no sound. Made a custom 2.6.20 kernel. Now I
> > > > > > > have sound but n
obo with SATA harddrive and IDE dvd writer. Install went
> > > > > > okay, but no sound. Made a custom 2.6.20 kernel. Now I have sound
> > > > > > but no cdrom! The trouble shows up in udev, but I'm not sure if
> > > > > > that's the r
> > > On Wed, Feb 07, 2007 at 03:20:55PM -0500, Prismatic Plasma wrote:
> > > > > I started with a net installed etch rc1 for amd64. I have ASUS M2N-MX
> > > > > mobo with SATA harddrive and IDE dvd writer. Install went okay, but
> > > > > no sound
gt; > > I started with a net installed etch rc1 for amd64. I have ASUS M2N-MX
> > > > mobo with SATA harddrive and IDE dvd writer. Install went okay, but
> > > > no sound. Made a custom 2.6.20 kernel. Now I have sound but no cdrom!
> > > > The trouble sh
t; > > mobo with SATA harddrive and IDE dvd writer. Install went okay, but no
> > > sound. Made a custom 2.6.20 kernel. Now I have sound but no cdrom! The
> > > trouble shows up in udev, but I'm not sure if that's the root of the
> > > problem.
> >
&
t; > sound. Made a custom 2.6.20 kernel. Now I have sound but no cdrom! The
> > trouble shows up in udev, but I'm not sure if that's the root of the
> > problem.
>
> Have you installed all the alsa- packages and run alsaconf? Do you mean
> that you did this with
On Wed, Feb 07, 2007 at 03:20:55PM -0500, Prismatic Plasma wrote:
> I started with a net installed etch rc1 for amd64. I have ASUS M2N-MX mobo
> with SATA harddrive and IDE dvd writer. Install went okay, but no sound.
> Made a custom 2.6.20 kernel. Now I have sound but no cdrom! Th
I started with a net installed etch rc1 for amd64. I have ASUS M2N-MX mobo
with SATA harddrive and IDE dvd writer. Install went okay, but no sound.
Made a custom 2.6.20 kernel. Now I have sound but no cdrom! The trouble
shows up in udev, but I'm not sure if that's the root of the pro
67 matches
Mail list logo
