Re: 2.6.14 kernel woes

2005-12-03 Thread David Baron
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 devices,

Re: 2.6.14 kernel woes

2005-12-03 Thread David Baron
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 devices,

Re: 2.6.14 kernel woes

2005-12-03 Thread David Baron
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

Re: 2.6.14 kernel woes

2005-11-28 Thread David Baron
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 devices,

Re: 2.6.14 kernel woes

2005-11-28 Thread Gene Heskett
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 of yet. Never

Re: 2.6.14 kernel woes

2005-11-28 Thread mikepolniak
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: Setting

Re: 2.6.14 kernel woes

2005-11-28 Thread Jim McCloskey
* 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 not made the

Re: 2.6.14 kernel woes

2005-11-28 Thread Randall J. Parr
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

Re: 2.6.14 kernel woes

2005-11-28 Thread Gene Heskett
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

2005-11-28 Thread Chris Boot
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 that

Re: Re: 2.6.14 kernel woes

2005-11-28 Thread Jim McCloskey
| 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 should

Re: Re: 2.6.14 kernel woes

2005-11-28 Thread d
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 | statically

2.6.14 kernel woes

2005-11-27 Thread David Baron
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

Re: 2.6.14 kernel woes

2005-11-27 Thread Curt Howland
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

Re: 2.6.14 kernel woes

2005-11-27 Thread Daniel Nilsson
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 Debian

Re: 2.6.14 kernel woes, PS

2005-11-27 Thread David Baron
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,

Re: 2.6.14 kernel woes

2005-11-27 Thread David Baron
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 did not

Re: 2.6.14 kernel woes

2005-11-27 Thread David Baron
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 did not

Re: 2.6.14 kernel woes

2005-11-27 Thread David Baron
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 both Debian

Re: 2.6.14 kernel woes

2005-11-27 Thread Randall J. Parr
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

Re: 2.6.14 kernel woes

2005-11-27 Thread Daniel Nilsson
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'm running stock

Re: Re: 2.6.14 kernel woes

2005-11-27 Thread Jim McCloskey
| 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 it off Sid?