On Tue, 2003-07-29 at 11:12, Adrian Zimmer wrote:
> As to lspci, I did take your advice but the results seemed to tell
> me nothing useful. Here they are is. Maybe, you will see something
> interesting:
>
> >From 2.2.20-idepci
>
> 00:10.0 Ethernet controller: Accton Technology Corporation EN
As to lspci, I did take your advice but the results seemed to tell
me nothing useful. Here they are is. Maybe, you will see something
interesting:
>From 2.2.20-idepci
00:10.0 Ethernet controller: Accton Technology Corporation EN-1216 Ethernet Adapter
(rev 11)
Subsystem: Accton Techn
On Tue, 2003-07-29 at 09:35, Adrian Zimmer wrote:
> No, no; ifconfig says the interface is up and running with both
> kernel images. Obviously *a* tulip module is installed (one way
> or the other). Happens to be two different ones.
>
> I compiled tulip in to 2.4.18 whereas I don't know how t
No, no; ifconfig says the interface is up and running with both
kernel images. Obviously *a* tulip module is installed (one way
or the other). Happens to be two different ones.
I compiled tulip in to 2.4.18 whereas I don't know how the prepackaged
2.2.20-idepci worked. I'd kinda like to tr
Adrian Zimmer wrote:
> with 2.2.20 I get
>
> eth0: Accton EN1217/EN2242 (ADMtek Comet) rev 17 at 0xc6022000, 00:D0:59:24:04:C0,
> IRQ 11.
> eth0: MII transceiver #1 config 3000 status 786d advertising 01e1.
>
> whereas with 2.4.18 I get
>
> eth0: ADMtek Comet rev 17 at 0x1c00, 00:D0:59:24:04:
Thanks, I had already seen in dmesg and ifconfig that the ethernet
was configured. There is a difference that I had not thought
consequential:
with 2.2.20 I get
eth0: Accton EN1217/EN2242 (ADMtek Comet) rev 17 at 0xc6022000, 00:D0:59:24:04:C0, IRQ
11.
eth0: MII transceiver #1 config 3000 sta
On Mon, 2003-07-28 at 15:46, Adrian Zimmer wrote:
> I have version 2.2.20 (idepci downloaded) running OK (at runlevel 2).
>
> I have version 2.4.18 (compiled myself under 2.2.20) running sort-of OK
> (again runlevel 2).
>
> One difference is that my self-configured/compiled version isn't est
"Shango" == Shango Oluwa <[EMAIL PROTECTED]> writes:
Shango> Why, if 2.4.x is more recent & secure, is my Debian 3
Shango> (woody) CD distribution built with kernel 2.2.20 ?
and in response to several good explanations "Shango" asks:
Shango> Is kernel 2.4.21 considered safe f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jul 06, 2003 at 09:12:42PM +0100, Shango Oluwa wrote:
> Why, if 2.4.x is more recent & secure, is my Debian 3 (woody) CD
> distribution built with kernel 2.2.20 ?
Cause 2.4 wasn't out long enough to be well tested before Woody came out.
- --
El Sun, 06 Jul 2003 21:12:42 +0100 Shango Oluwa <[EMAIL PROTECTED]> escribió:
> Why, if 2.4.x is more recent & secure, is my Debian 3 (woody) CD distribution
> built with kernel 2.2.20 ?
Obviously you haven't looked at the latest security issues in 2.4.X kernels.
BTW; the default 2.4.18-bf2.4 at
On Sunday 06 July 2003 23:18, Shango Oluwa wrote:
> - I have also considered LRP but that distribution seems to be
> crumbling and unsupported
The guy who did the LRP just recently gave up, so you aren't likely to see
anything new from that thing soon.
--
Got Backup?
--
To UNSUBSCRIBE, ema
Nicos wrote:
Mostly because the 2.4 series had some serious (as in "don't use for
production machines") problems when Woody was locked.
Understood.
Is kernel 2.4.21 considered safe for a production machine now?
I'm configuring an internet router and have been advised to use 2.4.21
- I have also c
On Sunday 06 July 2003 22:12, Shango Oluwa wrote:
> Why, if 2.4.x is more recent & secure, is my Debian 3 (woody) CD
> distribution built with kernel 2.2.20 ?
Mostly because the 2.4 series had some serious (as in "don't use for
production machines") problems when Woody was locked.
--
Got Backup
On Mon, 14 Oct 2002 14:44:57 -0700
Eric Richardson <[EMAIL PROTECTED]> wrote:
> I did a web page that kindof summarizes the differences between 2.2 > > and 2.4 on
>a laptop.
>
> http://www.milagrosoft.com/products/software/debian-woody.html
I will give this a try at the weekend! Thanks very
Keith O'Connell wrote:
> Hi,
>
> I have a problem with my laptop which I would appreciate some guidance with. It is a
>Dell Inspiron 3700 (hardly cutting edge now!)
>
> I installed Woody on it with the default 2.2 kernel and the various packages I want
>and it runs fine. I then use dselect to
On Sun, 13 Oct 2002 10:29:34 -0400
Seneca <[EMAIL PROTECTED]> wrote:
> On Sun, Oct 13, 2002 at 02:11:13PM +0100, Keith O'Connell wrote:
> > I have a problem with my laptop which I would appreciate some guidance with. It is
>a Dell Inspiron 3700 (hardly cutting edge now!)
> >
> > I installed Woo
On Sun, Oct 13, 2002 at 02:11:13PM +0100, Keith O'Connell wrote:
> I have a problem with my laptop which I would appreciate some guidance with. It is a
>Dell Inspiron 3700 (hardly cutting edge now!)
>
> I installed Woody on it with the default 2.2 kernel and the various packages I want
>and it
> If I'm not mistaken, I read that the 2.2.x Kernel and later no longer made
> you add:
>
> append="mem=128M"
>
> ..to lilo.conf to get it to use more than 64MB of RAM (in my case, 128MB).
>
2.2.x is not 100% correct - it became superflous with 2.2.10 or something
like that - at least on my sys
> I finally broke down and decided to compile a 2.2.13 kernel despite
> the fact that my 2.0.36 kernel continues to work perfectly.
>
Just curious, why did you decide to `upgrade'? I'm trying to decide
whether I should do the same.
--
Matthew Roberts
Gregory T. Norris <[EMAIL PROTECTED]> wrote:
> You need to select "OSS sound modules" first, then the SB16 stuff will
> show up.
You're kidding.
How on Earth is someone supposed to know that, except by asking you
folks? SoundBlaster support wasn't in OSS in 2.0.x.
Thank you very much.
--
Carl
You need to select "OSS sound modules" first, then the SB16 stuff will
show up.
On Fri, Dec 24, 1999 at 10:42:17PM -0500, Carl Fink wrote:
> I finally broke down and decided to compile a 2.2.13 kernel despite
> the fact that my 2.0.36 kernel continues to work perfectly.
>
> Well, 2.2.13 worked ok
Hi,
It works.
You should update a few packages, especially the user-space nfsd.
Have a look on Documentation/Changes. Up to date is 2.2.13
Ciao,
Holger
--
"I'd love to go out with you, but I'm staying home to work on my
cottage cheese sculpture."
make sure your running 2.1r3 of slink and you should have -no- trouble,
anything earlier *might* be missing a package. some things like lsof i
had to recompile for myself.
nate
On Wed, 24 Nov 1999, andreas [iso-8859-1] p?lsson wrote:
andrea >Hello.
andrea >
andrea >I have a Slink system which
A long time ago, in a galaxy far, far way, someone said...
> I have a Slink system which runs very fine with the 2.0.38 kernel. No
> problems or shutdowns at all.
Ok.
>
> Now I want to use the 2.2.x kernel because of some features, but I want
> to know first if it is possible to run v2.2.x kern
> "andreas" == andreas pålsson <[EMAIL PROTECTED]> writes:
andreas> The other option is to run Potato, since I just need the
andreas> base and enough tools to compile the 2.2 kernel. But
andreas> this system _must_ be stable and I fear Potato ain't
andreas> really there yet.
Hello.
Nice see that it is possible and thanks for the tip.
Looking at the URL you gave me and the installed versions of my packages
I only saw that "Util-linux" was 2.9g but 2.9t was required. Seems like
no big deal.
I have no problem in compiling and installing programs, but I would like
to st
andreas pЕlsson <[EMAIL PROTECTED]> writes:
> I have a Slink system which runs very fine with the 2.0.38 kernel. No
> problems or shutdowns at all.
> Now I want to use the 2.2.x kernel because of some features, but I want
> to know first if it is possible to run v2.2.x kernel on a Slink system.
>
On Tue, Aug 31, 1999 at 02:06:09PM -0600, Rogerio A. de Paula wrote:
> I upgraded the kernel to 2.2.x version (I tried different ones), but now I
> always get a warning message from mount saying that the compiled version
> of mount is older than the kernel (although I've already recompiled
> mount!
On Mon, 19 Jul 1999, Ian Stuart wrote:
> There's a package "kernel-package" (warning, dependent on Perl, so you
> won't be able to do apt-based install under Potato).
It's been updated, so it should install correctly no matter if you have
perl-5.004 or perl-5.005 installed.
Evan S wrote:
> I'm just wondering, if I want to upgrade to 2.2.10 in potato, how do I
> do that? I want to apt-get the source code so I can enable sound and
> such, do you know what command I do? And what steps are involved?
There's a package "kernel-package" (warning, dependent on Perl, so you
wo
*- On 30 Jun, Bill White wrote about "Kernel 2.2 and slink."
> Hi. I'm sorry for bothering, but I am thinking of upgrading my 2.0.36
> kernel to 2.2. I am running a fairly stock installation of slink, but with
> more recent kde and gnome packages. I seem to remember some talk on this
> list abou
ZIP drive support is under SCSI (it is a SCSI low-level driver).
Why not upgrade to 2.2.9, I believe there were sound issues in 2.2.1.
* Ryan Novosielski - [EMAIL PROTECTED] - http://www.bergen.org/~ryanov
+ inSite e'zine - http://www.teenvoice.com - EMail: [EMAIL PROTECTED]
+ AAST Master 98 - ht
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
> >
> > I heard that the new kernel is very modular. Does this mean I can have a
> > lean mean kernel and include only the modules I need? Is SMP turned on by
> > default? If so would it make sense to turn it off for single processor
> > systems so as
>
> I heard that the new kernel is very modular. Does this mean I can have a
> lean mean kernel and include only the modules I need? Is SMP turned on by
> default? If so would it make sense to turn it off for single processor
> systems so as to get better performance?
>
a) get 2.2.5 or higher, 2
In reply to Johnny Thompson:
> I had the same problem.. IP masquerade isn't re-reading
> the firewall rules after the link goes down. Creating a
> null /etc/{wherever}ipmasqueradeislocatedinthisdirectory/ppp
> .file.
>
> touch /etc/ipmasq/ppp .. That should solve your problem.. ;)
>
> If
Like a dolt, I didn't even recognize this. I had the exact same problem
that Kris has described, and after a reinstall, I noticed it went away
"automagically". Of course, I don't have ipmasq installed this time.
*doh!*
BTW, HTML-mail SUCKS. :)
Sean
Johnny Thompson wrote:
I had the same proble
I had the same problem.. IP masquerade isn't re-reading the firewall rules
after the link goes down. Creating a null /etc/{wherever}ipmasqueradeislocatedinthisdirectory/ppp
file.
touch /etc/ipmasq/ppp .. That should solve your problem.. ;)
If that doesn't work, uninstall ipmasq because you prob
In reply to John Pearson:
>These [Exim things in ps ax output] should run briefly when you start
>your session, and then be gone.
>
>If they are still running it may be that there is a problem with exim's
>setup that is preventing it from quitting in a timely manner, or it may
>just be a further s
{blush} You can tell I follow the digest now... darn. Apologies for the
waste of bandwidth, but it's for archive continuity (and so people actually
know wts(meg) I was going on about). Re-send, in reply to "Sean"
<[EMAIL PROTECTED]>, with the correct subject:
>
Nope. inetd has been well and
On 17-May-99 Sean wrote:
> A quick kludge that might fix your problem (it fixed it on my machine under
> hamm, and after I get done upgrading to slink, I'm going to try it there) is
> to kill inetd. I think the problem revolves around the netbase script in
> the /etc/init.d folder trying to use i
A quick kludge that might fix your problem (it fixed it on my machine under
hamm, and after I get done upgrading to slink, I'm going to try it there) is
to kill inetd. I think the problem revolves around the netbase script in
the /etc/init.d folder trying to use ifwadm(or something like that) inst
At 19:35 16/05/1999 +, you wrote:
>After I got everything installed, I
>immediately downloaded, installed and ran apt-get, and promptly upgraded to
>Slink, just as I had done when Slink first went stable. And now I can't use
>any of the >2.0.x kernels AND have ppp work. I've tried everything
Kris writes:
> # cat /etc/resolv.conf
> domain globalnet.co.uk # <- Tried with, without,
> search globalnet.co.uk # <- and combinations of.
> nameserver 194.126.82.5
> nameserver 194.126.86.9
The 'domain' and 'search' directives won't affect your problem (In fact
they are rarely needed at all).
Sean
-Original Message-
From: Kris <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Date: Sunday, May 16, 1999 10:58 AM
Subject: Re: Kernel 2.2.x: PPP routing problem?
>At 08:32 16/05/1999 +, you wrote:
> >I have a working ppp on kernel 2.2.9. my pppd command
At 08:32 16/05/1999 +, you wrote:
>I have a working ppp on kernel 2.2.9. my pppd command is
>
>exec /usr/sbin/pppd /dev/ttyS0 115200 lock modem crtscts \
> asyncmap 0 defaultroute connect $DIALER_SCRIPT
>pppd --version
>(pppd version 2.3 patch level 5)
>
>egrep -v '#|^ *$' /etc/ppp/opt
At 20:21 15/05/1999 +, you wrote:
>Ppp is known to have problems with 2.2.X.
Indeed it does. *thwap*
>How about the far end of the ppp link?
Nope; the only thing I can ping or otherwise communicate with is localhost
& the dynamic IP which I'm assigned (from /var/log/ppp.log).
>Option nam
Subject: Kernel 2.2.x: PPP routing problem?
Date: Sat, May 15, 1999 at 05:46:14PM +0100
In reply to:Kris
Quoting Kris([EMAIL PROTECTED]):
> Problem: PPP works fine under kernel 2.0.36; under 2.2.x it connects, but
> it seems like no packets go in or out. tcpdump only shows what
Kris writes:
> Problem: PPP works fine under kernel 2.0.36; under 2.2.x it connects, but
> it seems like no packets go in or out.
Ppp is known to have problems with 2.2.X.
> ...not _any_ remote IPs (including my nameservers).
How about the far end of the ppp link?
> -am and -vj make no differen
*- On 28 Jan, Jyrki Malinen wrote about "Kernel 2.2.xx"
> When Kernel 2.2.xx will be included to Debian/GNU Linux release, and to
> what release version, potato?
>
The default kernel image for slink will still be 2.0.36 but a source
package for 2.2.0 will be included in slink. Slink is not 100%
[EMAIL PROTECTED] (Marc Haber) writes:
> I am still running hamm on my machines and would like to delay the
> update to slink until it's finally released.
>
> I would like, however, to try the 2.2 kernel in a few days. Which
> packets do I need to upgrade to the slink version to make 2.2 run? I
>
On 07 Jan 1999 14:05:13 +0100, you wrote:
>I believe that everything needed for linux 2.2.0 is avaible in slink.
I am still running hamm on my machines and would like to delay the
update to slink until it's finally released.
I would like, however, to try the 2.2 kernel in a few days. Which
packe
The two options I used to get around it...
1) cd /lib/modules ; mv 2.0.0 2.2.0-pre6 ; depmod -a
or
2) upgrade kernel-package to the version in potato, which will create
the module-directory under the correct name
On Sat, Jan 09, 1999 at 05:52:48PM +1100, Hamish Moffatt wrote:
> There mu
On Sat, Jan 09, 1999 at 05:52:48PM +1100, Hamish Moffatt wrote:
> There must be a trick to this.
>
> I just installed kernel 2.2.0-pre6. modutils doesn't insert anything;
> depmod -a says
>
> [5:50pm] [EMAIL PROTECTED]:~# depmod -a
> can't open /lib/modules/2.2.0-pre6/modules.dep
>
> which is be
I doubt that kernel 2.2.0 will actually be included in slink (due to it's
frozen status), but slink should work just fine with it. I've been using
the later 2.1/2.2.0-pre kernels for the last few months witout any
problems.
The only two changes I've had to make are:
1) Add an entry in /etc/cromt
On Thu, Jan 07, 1999 at 01:32:27PM +0100, Thomas Janke wrote:
>
> The new LINUX-Kernel will be available soon.
> Is Debian ready for the new kernel?
> Will Slink be?
>
I'm running 2.2.0pre4 on Slink right now with no apparent problems, so
even though Slink won't likely ship with 2.2, you can upgr
On Thu, Jan 07, 1999 at 01:32:27PM +0100, Thomas Janke wrote:
> The new LINUX-Kernel will be available soon.
> Is Debian ready for the new kernel?
> Will Slink be?
Yes, also it will not ship with it as default kernel (probably not ship with
it at all). I do not know all issues, but what I know sou
> The new LINUX-Kernel will be available soon.
> Is Debian ready for the new kernel?
> Will Slink be?
>
Slink is "frozen". That means only bugfixes get in,
no new improvements. This applies to kernels as well
as applications.
So 2.2.0 won't likely be in slink. It may appear in the
next version
Thomas Janke <[EMAIL PROTECTED]> writes:
> The new LINUX-Kernel will be available soon.
Lets hope so...
> Is Debian ready for the new kernel?
> Will Slink be?
Slink will not include the new kernel. Linux 2.2.0 is pretty much new
code compared to 2.0.X and will probaly not go into a frozen
distr
58 matches
Mail list logo
