Re: 2.6.14 kernel woes

On Monday 28 November 2005 01:55, Jim McCloskey wrote: >> What version of udev are you running? The standard kernel documentation >> says that you should use nothing earlier and 058. Stable has 056, >> >> Jim >> >>I have not made the jumpt as of yet. Never could figure out how to use >> it.

Re: 2.6.14 kernel woes

On Monday 28 November 2005 01:55, Jim McCloskey wrote: >> What version of udev are you running? The standard kernel documentation >> says that you should use nothing earlier and 058. Stable has 056, >> >> Jim >>I have not made the jumpt as of yet. Never could figure out how to use it. >Still doin

Re: 2.6.14 kernel woes

On Monday 28 November 2005 01:55, Jim McCloskey wrote: >> What version of udev are you running? The standard kernel documentation >> says that you should use nothing earlier and 058. Stable has 056, >> >> Jim >>I have not made the jumpt as of yet. Never could figure out how to use it. >Still doin

Re: Re: 2.6.14 kernel woes

On Tue, Nov 29, 2005 at 12:22:13AM +, Jim McCloskey wrote: > |> >This is not true. I'm happily running 2.6.14.3, on an FC2 box, > |> >which pre-dates udev. And its no problem at all. Everything Just > |> >Works (TM). > |> > |> One thing you _cannot_ do is run devfs though, it's udev or > |> sta

Re: Re: 2.6.14 kernel woes

|> >This is not true. I'm happily running 2.6.14.3, on an FC2 box, which |> >pre-dates udev. And its no problem at all. Everything Just Works |> >(TM). |> |> One thing you _cannot_ do is run devfs though, it's udev or |> statically managed /dev. devfs was removed in 2.6.13 I think. Yes, sorry, I

Re: 2.6.14 kernel woes

On 28 Nov 2005, at 22:40, Gene Heskett wrote: On Monday 28 November 2005 11:44, Jim McCloskey wrote: * David Baron ([EMAIL PROTECTED]) wrote: |> On Monday 28 November 2005 01:55, Jim McCloskey wrote: |> > What version of udev are you running? The standard kernel |> > documentation says th

Re: 2.6.14 kernel woes

On Monday 28 November 2005 11:44, Jim McCloskey wrote: >* David Baron ([EMAIL PROTECTED]) wrote: > |> On Monday 28 November 2005 01:55, Jim McCloskey wrote: > |> > What version of udev are you running? The standard kernel > |> > documentation says that you should use nothing earlier and 058.

Re: 2.6.14 kernel woes

mikepolniak wrote: On 12:21 Sun 27 Nov , Randall J. Parr wrote: David Baron wrote: I now get /var/log/boot messages like - Sun Nov 27 08:01:27 2005: ^[[33m*^[[39;49m /etc/network/options is deprecated. Just remove /etc/network/options This mad

Re: 2.6.14 kernel woes

* David Baron ([EMAIL PROTECTED]) wrote: |> On Monday 28 November 2005 01:55, Jim McCloskey wrote: |> > What version of udev are you running? The standard kernel documentation |> > says that you should use nothing earlier and 058. Stable has 056, |> > |> > Jim |> |> I have no

Re: 2.6.14 kernel woes

On 12:21 Sun 27 Nov , Randall J. Parr wrote: > David Baron wrote: > > I now get /var/log/boot messages like > - > Sun Nov 27 08:01:27 2005: ^[[33m*^[[39;49m /etc/network/options is > deprecated. Just remove /etc/network/options > Sun Nov 27 08:01:27 2005: Set

Re: 2.6.14 kernel woes

On Monday 28 November 2005 07:52, David Baron wrote: >On Monday 28 November 2005 01:55, Jim McCloskey wrote: >> What version of udev are you running? The standard kernel >> documentation says that you should use nothing earlier and 058. >> Stable has 056, >> >> Jim > >I have not made the jumpt as o

Re: 2.6.14 kernel woes

On Monday 28 November 2005 01:55, Jim McCloskey wrote: > What version of udev are you running? The standard kernel documentation > says that you should use nothing earlier and 058. Stable has 056, > > Jim I have not made the jumpt as of yet. Never could figure out how to use it. Still doing devic

Re: Re: 2.6.14 kernel woes

|> > > I wonder if the "stock" kernels are having the same problems? |> > |> > I'm running stock 2.6.14 on a couple of machines, works perfectly well |> > on both Debian stable and testing... Same here, on 3 different machines (one with the ck6 patch-set). |> Did you compile it yourself or take i

Re: 2.6.14 kernel woes

On Sun, Nov 27, 2005 at 08:55:21PM +0200, David Baron wrote: > On Sunday 27 November 2005 20:51, [EMAIL PROTECTED] > wrote: > > > If 2.6 ever stabilizes, maybe then there will be time to take care of > > > details. > > > > > > I wonder if the "stock" kernels are having the same problems? > > > > I

Re: 2.6.14 kernel woes

David Baron wrote: Here is a snipet from a logcheck booting this goody: Nov 27 17:18:38 d_baron kernel: Inspecting /boot/System.map-2.6.14-2-686-smp Nov 27 17:18:38 d_baron kernel: Loaded 21450 symbols from /boot/System.map-2.6.14-2-686-smp. Nov 27 17:18:38 d_baron kernel: Symbols match kerne

Re: 2.6.14 kernel woes

On Sunday 27 November 2005 20:51, [EMAIL PROTECTED] wrote: > > If 2.6 ever stabilizes, maybe then there will be time to take care of > > details. > > > > I wonder if the "stock" kernels are having the same problems? > > I'm running stock 2.6.14 on a couple of machines, works perfectly well > on bo

Re: 2.6.14 kernel woes

On Sunday 27 November 2005 19:24, you wrote: > 2.6.14 in Sid won't allow DMA to be turned on for my diskdrives. As > you can imagine, ext3 with a 5 second commit means that for every 5 > seconds, the machine locks up for a full second to do it's disk > transfers. > > Very nasty. This problem, I di

Re: 2.6.14 kernel woes

On Sunday 27 November 2005 19:24, you wrote: > 2.6.14 in Sid won't allow DMA to be turned on for my diskdrives. As > you can imagine, ext3 with a 5 second commit means that for every 5 > seconds, the machine locks up for a full second to do it's disk > transfers. > > Very nasty. This problem, I di

Re: 2.6.14 kernel woes, PS

> I do want to thank them for including frame buffer support in > 2.6.14-2, which wasn't working in -1 because of the new yippi (or > whatever) initrd build system. First thing I do is make the initrd the old-fashioned way. Yaird does not work correctly if the linux disk is not the first disk, e

Re: 2.6.14 kernel woes

On Sun, Nov 27, 2005 at 12:24:30PM -0500, Curt Howland wrote: > > If 2.6 ever stabilizes, maybe then there will be time to take care of > details. > > I wonder if the "stock" kernels are having the same problems? I'm running stock 2.6.14 on a couple of machines, works perfectly well on both Deb

Re: 2.6.14 kernel woes

2.6.14 in Sid won't allow DMA to be turned on for my diskdrives. As you can imagine, ext3 with a 5 second commit means that for every 5 seconds, the machine locks up for a full second to do it's disk transfers. Very nasty. 2.6.12 worked very well indeed. I'm a little bit concerned that the D

2.6.14 kernel woes

Here is a snipet from a logcheck booting this goody: Nov 27 17:18:38 d_baron kernel: Inspecting /boot/System.map-2.6.14-2-686-smp Nov 27 17:18:38 d_baron kernel: Loaded 21450 symbols from /boot/System.map-2.6.14-2-686-smp. Nov 27 17:18:38 d_baron kernel: Symbols match kernel version 2.6.14. Nov 2

Re: wireless and kernel woes

On Tue, Jul 20, 2004 at 08:06:39AM +0800, John Summerfield wrote: | Derrick 'dman' Hudson wrote: | | >On Mon, Jul 19, 2004 at 12:16:42PM -0700, [EMAIL PROTECTED] | >wrote: | >| | >| The situation: bought an Averatec notebook couple of weeks ago (AMD | >| Athlon-M, 256K, builtint 10/100 and wirel

Re: wireless and kernel woes

Derrick 'dman' Hudson wrote: On Mon, Jul 19, 2004 at 12:16:42PM -0700, [EMAIL PROTECTED] wrote: | | The situation: bought an Averatec notebook couple of weeks ago (AMD | Athlon-M, 256K, builtint 10/100 and wireless, CDRW-DVD combo, etc) You don't say what wireless adapter this is or what driver y

Re: wireless and kernel woes

On Mon, Jul 19, 2004 at 12:16:42PM -0700, [EMAIL PROTECTED] wrote: | | The situation: bought an Averatec notebook couple of weeks ago (AMD | Athlon-M, 256K, builtint 10/100 and wireless, CDRW-DVD combo, etc) You don't say what wireless adapter this is or what driver you need. I recommend a PCI or

Re: wireless and kernel woes

On Mon, 19 Jul 2004 12:16:42 -0700, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > So, does anyone have any suggestions for how to get out of this > Catch-22? Did you keep a copy of the known good kernel, and is it in you LILO/GRUB boot menu? If so, you should be able to boot into that kernel,

Re: wireless and kernel woes

[EMAIL PROTECTED] said: > > The situation: bought an Averatec notebook couple of weeks ago (AMD > Athlon-M, 256K, builtint 10/100 and wireless, CDRW-DVD combo, etc) Which wireless card is this? `lspci` will probably help... > install ndis-wrappers package. Doesn't load as built against >

wireless and kernel woes

The situation: bought an Averatec notebook couple of weeks ago (AMD Athlon-M, 256K, builtint 10/100 and wireless, CDRW-DVD combo, etc) Installed sarge using the latest beta of the installer. A few hiccups (particularly with X not being configured properly and KDE not installed at all) but everyth

kernel woes?

logcheck sniffed these out of my system logs lately -- does it indicate anything serious? Feb 23 20:44:38 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:44:38 server kernel: KERNEL: assertion ((1

install kernel woes

Hi list, I should maybe be posting this to debian-user, but I'm not sub'd there, and I'm hoping one of y'all may have some experience with this hardware configuration. I've built a custom kernel for my hardware, (compaq proliant 2500R with compaq smart2 array controller, and have put it on th

Re: Minor? kernel woes...

On Sat, Nov 18, 2000 at 06:19:12PM -0800, brian moore wrote: :That's normal. Fix it by rm'ing it. 2.4 doesn't support :'/dev/sndstat'. Oh :) :> I did complile in the correct card driver (twice), I get the same :> behavior for /dev/pppox0. : :Never heard of that device. It's for PPP encapsulat

Re: Minor? kernel woes...

On Sat, Nov 18, 2000 at 09:01:51PM -0500, Jonathan D. Proulx wrote: > Hi, > > Perhaps I should go to a kernel list with this, but... > > Just installed 2.4.0-test10 and now a bunch of my devices are behaving > oddly, such as: > > [EMAIL PROTECTED] drivers]$ cat /dev/sndstat > cat: /dev/sndstat:

Minor? kernel woes...

Hi, Perhaps I should go to a kernel list with this, but... Just installed 2.4.0-test10 and now a bunch of my devices are behaving oddly, such as: [EMAIL PROTECTED] drivers]$ cat /dev/sndstat cat: /dev/sndstat: No such device [EMAIL PROTECTED] drivers]$ ls -l !$ ls -l /dev/sndstat crw-rw

kernel woes

I'm trying to get a 2.2.10 kernel going on my slink box.. it's dual proc pent 200's .. the kernel is big all static.. so I bzipped it.. and it just kinda freezes.. anyone on how to get kmod working so that I can cut the size of this kernel down? does kmod use the same configs as kerneld?? or

Re: Help! Kernel woes. -- SoundBlaster

This link from Marcus Brinkmann helped me a lot when I did my soundblaster setup: it's nice and easy to follow: http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/soundblaster.html (hope he doesn't mind me posting his ref.) HTH Rich Jonathan J. Lupa wrote: > > Hello! > > I just went through

RE: Help! Kernel woes. -- SoundBlaster

Hello! I just went through this fight with my AWE32... there are some docs out there that will really help. For reference: zless /usr/doc/HOWTO/Sound-HOWTO.gz And the big gun: zless /usr/doc/HOWTO/mini/Soundblaster-AWE.gz All the stuff in there about ISA PnP should apply. ( I'm not sure how kern

Re: Help! Kernel woes.

On Thu, Apr 15, 1999 at 01:43:29AM -0400, William R Pentney wrote: > > Did you compile it in kernel or as modules. I also have a SB16, and > > found that it was a bit unobvious how to configure it in > > menuconfig... Did you get to the step of specifying the DMA, IRQ > > etc.etc.? Which driver did

Re: Help! Kernel woes.

William R Pentney wrote: > > > > I have tried recompiling a 2.2 kernel, and now I have two problems: > > > > > > 1) The new kernel isn't recognizing my network card. I used the "PCI > > > NE2000" option; it worked before on a 2.0.34 kernel I compiled on a > > > floppy. Might I be missing an import

Re: Help! Kernel woes.

William R Pentney <[EMAIL PROTECTED]> writes: > On 15 Apr 1999, Arcady Genkin wrote: > It is a Dayna PCI card, for 10baseT networks. I used the PCI NE2000 option > with success when I installed it. It also worked when I attempted to > install a 2.0.34 kernel (which unfortunately did not accept my

Re: Help! Kernel woes.

On 15 Apr 1999, Arcady Genkin wrote: > William R Pentney <[EMAIL PROTECTED]> writes: > > > I have tried recompiling a 2.2 kernel, and now I have two problems: > > > > 1) The new kernel isn't recognizing my network card. I used the "PCI > > NE2000" option; it worked before on a 2.0.34 kernel I co

Re: Help! Kernel woes.

William R Pentney <[EMAIL PROTECTED]> writes: > I have tried recompiling a 2.2 kernel, and now I have two problems: > > 1) The new kernel isn't recognizing my network card. I used the "PCI > NE2000" option; it worked before on a 2.0.34 kernel I compiled on a > floppy. Might I be missing an import

Help! Kernel woes.

I have tried recompiling a 2.2 kernel, and now I have two problems: 1) The new kernel isn't recognizing my network card. I used the "PCI NE2000" option; it worked before on a 2.0.34 kernel I compiled on a floppy. Might I be missing an important option? 2) I still can't use sound. I have a SoundB

Kernel woes

I've been using the 2.0.34 kernel for some time and have had a smallish problem. I have quite a lot of stuff that comes with the Debian distribution installed, and am also running with Appletalk enabled (and Netatalk installed). The IP address and routes are set correctly in /etc/init.d/network, s