I seem to need to finally upgrade my kernel to 2.2.17. I have been
posponding this as long as possible, not because of the fine Debian
upgrade package, but because of expected networking trouble whilst
having to part with ipmasq.
Now it seems I need to take the dive (In comes the first
Win2000
On Sat, Nov 18, 2000 at 07:22:46AM +0100, Erik van der Meulen wrote:
I have a Linux 2.2 (upgraded from 2.1 apart from the kernel) box that
i assume you mean `Debian' and not `Linux' Linux is just a kernel,
GNU/Linux is the operating system, Debian is the distribution. i
assume you now have a
I upgraded a box to potato and now samba doesn't work. I've looked in
the samba archives and the postings I found suggest that this is because
the newer versions of samba use a setresuid call (or don't) and get a
bad return value (http://us1.samba.org/listproc/samba-ntdom/1639.html).
One user says
:The recipient's address is unknown.
Subject: samba: anyone else get Can't become connected user! with
potato
version 2.0.4b-3 kernel 2.0.34?
I upgraded a box to potato and now samba doesn't work. I've looked in
the samba archives and the postings I found suggest that this is because
We're using DEC Celebris GL6200 with 21143 tulip cards, and the
only version of the driver that seems to work is v0.91 from the
NASA website. This is also true on my 2.1 installation, which
is not having quite as substantial a problem, but then it isn't
running exactly the same suite of daemons
Hi,
I am having problems patching the source from the kernel-source-2.0.34
deb up to kernel 2.0.36. I downloaded the patchfiles from
ftp.uk.kernel.org and applied them using
bunzip2 -c patch-2.0.35.bz2 | patch -p0
It basically fails, complaining about several previously applied
patches
Winter wrote:
Hi,
I am having problems patching the source from the kernel-source-2.0.34
deb up to kernel 2.0.36. I downloaded the patchfiles from
ftp.uk.kernel.org and applied them using
bunzip2 -c patch-2.0.35.bz2 | patch -p0
It basically fails, complaining about several previously
On Sun, 23 May 1999, Ian Winter wrote:
Most of the patches do work though. From reading the README.Debian it
looks like it might be related to the patches Debian have previously
applied.
That probably is it.
Also, before i patch i always backup my old .config and 'make mrproper' to
get
On Sun, May 23, 1999 at 11:16:19AM -0500, Gregory T. Norris wrote:
Are you trying to apply the patch to the pristine kernel source, or to
the debianized version? The .deb version has various patches applied
already (for additional hardware support, bugfixes, etc.), and so will
very likely
thanks for the quick repsonse...I was unable to get to the machine for a
week...
here's the output you asked for
output of ping
ping: sendto:operation not performed
ping: wrote: 202.186.1.10 64 chars, ret=-1
output of route -n
Kernel IP routing table
Destination
Gateway
Genmask Flags
kernel-image-2. custon.1.0 Linux kernel binary image.
ii kernel-package 4.11 Debian Linux kernel package build
scripts.
ii kernel-source-2 2.0.34-4 Linux kernel source.
HELP! Please! I need to get to the CD ROM other that through
the MS
Hola:
Yo creía que en el kernel 2.0.34 no se soportaba Fat32, pero leyendo un
documento de como instalar el patch para soportarlo decía que se incluían
desde el kernel arriba dicho. ¿es eso cierto?
Probé a montar una unidad Fat32 con mount -t vfat /dev/hda1 /mnt y podía
leer los directorios y
On Fri, Apr 09, 1999 at 08:12:37PM +0200, Oscar Ferrero Guerra wrote:
Hola:
Yo creía que en el kernel 2.0.34 no se soportaba Fat32, pero leyendo un
documento de como instalar el patch para soportarlo decía que se incluían
desde el kernel arriba dicho. ¿es eso cierto?
Sip, de hecho
Andei recompilando o Kernel e no final do make zImage recebi a
seguintemensagem:
make: *** [vmlinuz] Erro 1
nao consigo passar do make zImage, ele nao cria o vmlinuz no diretorio
alguem pode me dar uma luz
[]'s
Nelsinho
Andei recompilando o Kernel e no final do make zImage recebi a
seguintemensagem:
make: *** [vmlinuz] Erro 1
nao consigo passar do make zImage, ele nao cria o vmlinuz no diretorio
alguem pode me dar uma luz
[]'s
Nelsinho
Oi Nelson,
tente instalar o pacote kernel-package. Ele gera um pacote do kernel com
um comando:
make-kpkg --revision=custom1.0 kernel_image.
depois e so instalar com dpkg -i kernel_image2.0.34.deb
Abracos,Paulo Henrique
Quoting Nelson Novaes
:
-
# insmod -p isofs
/lib/modules/2.0.34/fs/isofs.o: unresolved symbol load_nls_default_R86e263f4
/lib/modules/2.0.34/fs/isofs.o: unresolved symbol unload_nls_R3f17924a
/lib/modules/2.0.34/fs/isofs.o: unresolved symbol load_nls_Rbc00b63b
/lib/modules/2.0.34/fs/isofs.o: unresolved symbol
to mount a cd, I get an error saying
that the kernel does not support iso9660 filesystems. kerneld is running.
If I do insmod isofs I get the following errors:
-
# insmod -p isofs
/lib/modules/2.0.34/fs/isofs.o: unresolved symbol
is running.
If I do insmod isofs I get the following errors:
-
# insmod -p isofs
/lib/modules/2.0.34/fs/isofs.o: unresolved symbol load_nls_default_R86e263f4
/lib/modules/2.0.34/fs/isofs.o: unresolved symbol unload_nls_R3f17924a
/lib/modules
Hello!
When I tried to patch my kernel I encounter a lot of error messages, I'm not
sure if I can continue, hoping somebody with more experience can give me some
suggestion. I've collected the error messages and attatched it to this mail.
All what I did is (as root):
cp
Hi,
I ran into strange problems with rvplayer. 2 computers are running Linux
2.0.34 Debian slink. On one of those rvplayer is working on another one -
does not. I'm testing it on welcome.rm file, which comes with the package.
On broken rvplayer computer there is just rvplayer window
On Mon, Nov 30, 1998 at 01:28:50PM -0800, Steve Lamb wrote:
Because I was a Slackware person before I was a Debian person. I don't
like how the headers are split from the code. I've never cared to learn the
Debian way when make dep ; make clean ; make zlilo ; shutdown -r now
works so
On Mon, Nov 30, 1998 at 03:40:49PM -0700, Gary L. Hennigan wrote:
The short of it is, learn to use make-kpkg. It'll make life a LOT
easier on your new Debian system.
It's also a lot easier to compile kernels for other systems with it.
I have some 486 systems for which I prefer to build on
On Mon, 30 Nov 1998, Steve Lamb wrote:
: On Mon, Nov 30, 1998 at 12:43:32PM -0600, Nathan E Norman wrote:
: : We'll find out shortly. I'm FTPing the sources from sunsite.
Never did
: : like the Debian way of doing the Kernel.
:
: Why not?
:
: Because I was a Slackware
-Original Message-
From: Nathan E Norman [mailto:[EMAIL PROTECTED]
I grew up with Slackware too; I find the ability to put the
kernel and
its associated modules in a deb file, but then I use one machine to
compile kernels for the various machines we have, since it's much
faster.
We'll find out shortly. I'm FTPing the sources from sunsite. Never did
like the Debian way of doing the Kernel.
GULP This seems a bit drastic, make zlilo works for me with 2.0.34. It
almost seems like you have not installed all the right development bits. Have
you got a copy
On Mon, Nov 30, 1998 at 01:39:25PM +1100, Richard Lyon wrote:
We'll find out shortly. I'm FTPing the sources from sunsite. Never
did like the Debian way of doing the Kernel.
GULP This seems a bit drastic, make zlilo works for me with 2.0.34.
It almost seems like you have
drastic, make zlilo works for me with 2.0.34.
| It almost seems like you have not installed all the right development
| bits. Have you got a copy of these missing header files anywhere on your
| machine?
|
| Drastic? Why? Seems sensable to me.
[snip]
Personally, I rarely use the stock
On Sun, 29 Nov 1998, Steve Lamb wrote:
: On Sun, Nov 29, 1998 at 10:22:24AM +0100, Egon Schmid wrote:
: Oh sorry, I have never tried to build a kernel the Debian way. So I have
: to symlink the header files according the README. Could it be that there
: is something wrong?
:
: We'll
On Mon, Nov 30, 1998 at 12:43:32PM -0600, Nathan E Norman wrote:
: We'll find out shortly. I'm FTPing the sources from sunsite. Never
did
: like the Debian way of doing the Kernel.
Why not?
Because I was a Slackware person before I was a Debian person. I don't
like how the
Steve Lamb [EMAIL PROTECTED] writes:
| On Mon, Nov 30, 1998 at 12:43:32PM -0600, Nathan E Norman wrote:
| : We'll find out shortly. I'm FTPing the sources from
| sunsite. Never did
| : like the Debian way of doing the Kernel.
|
| Why not?
|
| Because I was a Slackware person before
On Mon, Nov 30, 1998 at 03:40:49PM -0700, Gary L. Hennigan wrote:
The make zlilo approach is problematic if you have something else
that depends on a specific kernel version (Read the file
/usr/doc/kernel-package/Rationale.gz for 11 or so reasons you want to
use make-kpkg).
All of which
Anyone else get this when doing a make zlilo with 2.0.34?
ld -m elf_i386 -Ttext 0x1000 -e startup_32 -o vmlinux head.o misc.o piggy.o
make[2]: Leaving directory
/usr/src/kernel-source-2.0.34/arch/i386/boot/compres
sed'
gcc -I/usr/src/kernel-source-2.0.34/include -O2 -fomit-frame-pointer
Install the kernel header files.
-Egon
On Sun, 29 Nov 1998, Steve Lamb wrote:
Anyone else get this when doing a make zlilo with 2.0.34?
ld -m elf_i386 -Ttext 0x1000 -e startup_32 -o vmlinux head.o misc.o piggy.o
make[2]: Leaving directory
/usr/src/kernel-source-2.0.34/arch/i386/boot
On Sun, Nov 29, 1998 at 10:02:00AM +0100, Egon Schmid wrote:
Install the kernel header files.
I hate to say it, but I am not that stupid. Neither is dselect.
*** Opt develkernel-heade 2.0.34-42.0.34-4Header files related
*** Opt develkernel-sourc 2.0.34-42.0.34-4
header files.
I hate to say it, but I am not that stupid. Neither is dselect.
*** Opt develkernel-heade 2.0.34-42.0.34-4Header files related
*** Opt develkernel-sourc 2.0.34-42.0.34-4Linux kernel source.
On Sun, Nov 29, 1998 at 10:22:24AM +0100, Egon Schmid wrote:
Oh sorry, I have never tried to build a kernel the Debian way. So I have
to symlink the header files according the README. Could it be that there
is something wrong?
We'll find out shortly. I'm FTPing the sources from sunsite.
Hi,
I have compiled the a custom 2.0.34 Kernel from the
hamm sources, on a hamm system. I installed with
make zlilo. On startup I get errors about unresolved
symbols in the vfat modules.
Any ideas, whats going wrong ???
(by the way, there were some typos in the sources,
one in af_inet
Hi,
I run an ASUS P2B-LS motherboard with AIC 7890 SCSI , so I had
to install a special kernel image (2.0.34) from ~doko/aic7xxx.
But I have also a 3com cyclone card (3C905B) which doesn't work.
I recompiled 3c59x.c with kernel-sources-2.0.34, but it still gives
ff:ff:ff:ff:ff:ff station
Hi,
I run an ASUS P2B-LS motherboard with AIC 7890 SCSI , so I had
to install a special kernel image (2.0.34) from ~doko/aic7xxx.
But I have also a 3com cyclone card (3C905B) which doesn't work.
I recompiled 3c59x.c with kernel-sources-2.0.34, but it still gives
ff:ff:ff:ff:ff:ff
3com cyclone has been reported to work with kernel 2.0.35. But I
am stuck until AIC7890 will be supported in 2.0.x ?
Does this mean I am locked ? Anyone has a tip or suggestion ?
Both support for aic7890 and ethernet are drivers; you can download the updates
for aic7890/3com 3c590b
Buenas, tenia instalado la version 1.3 de Debian con el Kernel 2.0.29
que me soportaba mi controladora Scsi Tekram DC-390, cuando instale
la Debian 2.0 , SORPRESA !! el nuevo Kernel 2.0.34 no soprta mi
controladora, me da un error disconect queue ... y me da un
Kernel Panic !!! , como es posible
Buenas, tenia instalado la version 1.3 de Debian con el Kernel 2.0.29
que me soportaba mi controladora Scsi Tekram DC-390, cuando instale
la Debian 2.0 , SORPRESA !! el nuevo Kernel 2.0.34 no soprta mi
controladora, me da un error disconect queue ... y me da un
Kernel Panic !!! , como es posible
thoth wrote:
Ignacio J. Alonso wrote:
La actualización ha supuesto la desaparición total de los warning
sobre pci y me ha permitido montar las unidades (DOS) d e y f (hda5
hda6 y hda7) que tenía creadas en una partición extendida de DOS-W95,
antes con el nucleo 2.0.33 no podia ¿¿¿???
El Tue, Oct 13, 1998 at 10:16:16AM +, Octavio Rodriguez Perez dijo:
mount -t vfat32 /dev/hdb1 /win
y me daba el error de que no reconocia ese tipo de sistema de ficheros.
¿Sera que se escribe de otra forma?
mount -t vfat /dev/hdb1 /win
--
Ugo Enrico Albarello López de
Ignacio J. Alonso wrote:
Hola a todos,
A cabo de actualizarme al nucleo 2.0.34 (todavía en bo) por que necesitaré
acceso a FAT32 dentro de poco, el problema es que no he visto ningún sitio
donde decirle al nucleo lo de la FAT32 ¿a caso lo lleva por defecto y no hay
que decirle nada en el
Hola a todos,
A cabo de actualizarme al nucleo 2.0.34 (todavía en bo) por que necesitaré
acceso a FAT32 dentro de poco, el problema es que no he visto ningún sitio
donde decirle al nucleo lo de la FAT32 ¿a caso lo lleva por defecto y no hay
que decirle nada en el config?
La actualización ha
Hi,
On Mon, 3 Aug 1998 12:21:14 -0400 (EDT), Camm Maguire
[EMAIL PROTECTED] said:
Over the weekend, The following errors started showing up:
-
Aug 1 17:03:01 debian kernel: Problem: block on freelist at 0174d610
a few days ago.
The kernel (2.0.34) was untouched and had been running smoothly for
months. This machine runs diald/pppd/IP masquerade as a corporate
gateway to the Internet. Over the weekend, The following errors
started showing up
Greetings! I just upgraded this machine to Debian 2.0 a few days ago.
The kernel (2.0.34) was untouched and had been running smoothly for
months. This machine runs diald/pppd/IP masquerade as a corporate
gateway to the Internet. Over the weekend, The following errors
started showing up
Matthew Collins wrote:
[...]
I have a hard enough time remembering the name of things I've
installed. :)
I know the feeling. Try typing `dpkg -l' and you will see what you
installed.
Eric
--
E.L. Meijer ([EMAIL PROTECTED]) | tel. office +31 40 2472189
Eindhoven Univ. of
Hi,
Hmm. I think I shall put a note at the bottom of the man page
pointing to the /usr/doc/kernel-package area. I have gotten too used
to looking at /usr/doc, apparently. I have tried to put a fairly
complete tutorial about kernel compilation in
Hi,
E == E L Meijer \(Eric\) E.L. writes:
E What about putting a Readme.debian in the /usr/src/linux dir of the
E debian kernel-source package, in which you tell people about compiling
E kernels the debian way? I think that would be really helpful to new
E debian users. It seems that the
On 16 Jul 1998, Manoj Srivastava wrote:
: Hi,
: E == E L Meijer \(Eric\) E.L. writes:
:
: E What about putting a Readme.debian in the /usr/src/linux dir of the
: E debian kernel-source package, in which you tell people about compiling
: E kernels the debian way? I think that would be really
Hi,
kernel-source-2.0.33_2.0.33-9.deb (found in my hamm mirror)
-rw-r--r-- root/root 844 1998-05-01 04:38
usr/src/kernel-source-2.0.33/README.Debian
That points to stuff in /usr/doc/kernel-source-2.0.33/, which
has more docs. I mean, I am running out of places to put
uses default (/vmlinuz) and that is it.
Rubbish. Please do not spread FUD. I have, at times, a round
dozen kernel images on my machine, all compiled with
kernel-package. I even have 2-3 2.0.34 images *ON AT THE SAME TIME*.
Look at my lilo.conf, 5 (count it, five) different options
On 14 Jul 1998 18:21:21 -0500, you wrote:
Rubbish. Please do not spread FUD. I have, at times, a round
dozen kernel images on my machine, all compiled with
kernel-package. I even have 2-3 2.0.34 images *ON AT THE SAME TIME*.
Look at my lilo.conf, 5 (count it, five) different options
On Wed, Jul 15, 1998 at 08:46:35AM +, Matthew Collins wrote:
On 14 Jul 1998 18:21:21 -0500, you wrote:
Does make-kpkg run config for you? It dosn't say.
It does not run config...you have to run make [menu,x]config yourself
I run make config
first, and the run make-kpkg. Off it goes
On Wed, 15 Jul 1998, Matthew Collins wrote:
[ snip ]
: All the functionallity you describe sounds really good, I (and many
: others by the sounds of things) might be missing the point here, but
: how do we USE this marvelous package? Is there any documentation,
: because the man pages are
On Wed, 15 Jul 1998 09:04:42 -0500 (CDT), you wrote:
RTFM kernel-package docs. All Debian documentation is in
/usr/doc/packagename ... at the very least, there will be a copyright
file there :)
[snip]
kernel-package is the coolest thing ever. It has a ton of options,
works with Debian
Hi,
Hmm. I think I shall put a note at the bottom of the man page
pointing to the /usr/doc/kernel-package area. I have gotten too used
to looking at /usr/doc, apparently. I have tried to put a fairly
complete tutorial about kernel compilation in
/usr/doc/kernel-package/README.gz
Hi,
can anybody tell me how to enable iso9660 support in a 2.0.34
kernel. There doesn't seem to be an option when I do 'make menuconfig'.
Nico
--
--
Nico De Ranter
Sony Service Center (PSDC-B/DNSE-B)
Sint Stevens Woluwestraat 55 (Rue de Woluwe-Saint-Etienne)
1130 Brussel (Bruxelles), Belgium
On Tue, Jul 14, 1998 at 09:21:28AM +0200, Nico De Ranter wrote:
Hi,
can anybody tell me how to enable iso9660 support in a 2.0.34
kernel. There doesn't seem to be an option when I do 'make menuconfig'.
In menu filesystems set on Native language support (Unicode, codepages)
you get iso
On Tue, Jul 14, 1998 at 09:21:28AM +0200, Nico De Ranter wrote:
Hi,
can anybody tell me how to enable iso9660 support in a 2.0.34
kernel. There doesn't seem to be an option when I do 'make menuconfig'.
In menu filesystems set on Native language support (Unicode, codepages)
you get
On Tue, Jul 14, 1998 at 09:53:11AM +0200, Nico De Ranter wrote:
Ah, I didn't know iso and fat where languages :-)
Changed in 2.0.35 anyway, just out.
Hamish
--
Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish.
*-Nico De Ranter (14 Jul)
| On Tue, Jul 14, 1998 at 09:21:28AM +0200, Nico De Ranter wrote:
|
| Hi,
|
| can anybody tell me how to enable iso9660 support in a 2.0.34
| kernel. There doesn't seem to be an option when I do 'make menuconfig'.
|
| In menu filesystems set on Native
Nico,
During your 'make menuconfig', enable the NLS support and you will get
the option for
ISO9660, FAT, VFAT, etc...
Steve Mayer
[EMAIL PROTECTED]
Nico De Ranter wrote:
Hi,
can anybody tell me how to enable iso9660 support in a 2.0.34
kernel. There doesn't seem to be an option when I
Nico,
During your 'make menuconfig', enable the NLS support and you will get
the option for ISO9660, FAT, VFAT, etc...
I recompiled mine and I still cannot get the ISO, FAT or VFAT to mount. I also
cannot load this module manually? I have not looked into this too hard, but I
have
Ya know,
The 'kernel-package' package automates all of this for you. I had troubles
getting
modules to work even though I thought I did all the steps (make dep ; make
clean ;
make bzImage ; make modules ; make modules_install ; depmod -a. Then symlinking
the
new kernel and running lilo. The
...I believe I am confused...
I do not mind a little automation, but currently in my lilo.conf I have 3 linux
kernels that I use.
Linux [default]
Old [Previous Image]
Experment [Pointing to /usr/src/linux/arch/i386/boot/zImage]
This kernel-package util seems as if it takes this functionality
Hola,
que diferencias hay entre entre el Kernel 2.0.34 standard y el Debian? En
que directorio está?
Saludos,
J. Parera
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
el .diff.gz vale)... en debian-user no he visto quejas tan amplias
como las tuyas respecto al 2.0.34... ;-)
Saludos,
Marcelo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Mon, 6 Jul 1998, Shaleh wrote:
gcc: Internal compiler error: program cc1 got fatal signal 11
sig11 (signal 11) is often a sign of a hardware problem. Either you
machine is over/under clocked, over heating, has a memory glitch or
something. Sig 11 can also be one of the problems that
I've been running Debian 1.3.1 with kernel 2.0.29
I decided to upgrade to kernel 2.0.34 but it fails during make zImage with
an error message. Can anyone help?
Here's the error message and a few of the lines before it:
gcc -D__KERNEL__ -I/usr/src/linux-2.0.34/include -Wall -Wstrict-prototypes
gcc: Internal compiler error: program cc1 got fatal signal 11
sig11 (signal 11) is often a sign of a hardware problem. Either you
machine is over/under clocked, over heating, has a memory glitch or
something. Sig 11 can also be one of the problems that appears and then
never re-appears.
--
On Mon, 6 Jul 1998, Shaleh wrote:
gcc: Internal compiler error: program cc1 got fatal signal 11
sig11 (signal 11) is often a sign of a hardware problem. Either you
machine is over/under clocked, over heating, has a memory glitch or
something. Sig 11 can also be one of the problems that
*-Patrick Olson ( 6 Jul)
|
| I've been running Debian 1.3.1 with kernel 2.0.29
|
| I decided to upgrade to kernel 2.0.34 but it fails during make zImage with
| an error message. Can anyone help?
|
| Here's the error message and a few of the lines before it:
|
| gcc -D__KERNEL__ -I/usr/src
I just installed Debian 2.0 Beta from CD but am still using my old
kernel (2.0.29). The apt-get -f dist-upgrade downloaded source 2.0.34 for
me, but the cd contains version 2.0.34-2. Any recommendations on which
one I should use? Thanks,
Tom
--
Unsubscribe? mail -s unsubscribe
I just installed 2.0.34-3 source and make config did not mention the
DOS flesystems also tried rm .config but they do not show up.
kernel compiled and installed just fine and runs flawlessly but of
course my
mount -t vfat /dev/hdb6 /DATAFILES
command failes with ... vfat not supported
, so that
you
know it leads to more options.
Chris
Robert Alexander wrote:
I just installed 2.0.34-3 source and make config did not mention the
DOS flesystems also tried rm .config but they do not show up.
kernel compiled and installed just fine and runs flawlessly but of
course my
Robert Alexander wrote:
I just installed 2.0.34-3 source and make config did not mention the
DOS flesystems also tried rm .config but they do not show up.
kernel compiled and installed just fine and runs flawlessly but of
course my
mount -t vfat /dev/hdb6 /DATAFILES
command
I installed the 2.0.34 kernel source package and did a make menuconfig
and when it comes time to select the filesystems to include support for,
a ton of them appear to be missing, most notably msdos and vfat. When I
installed hamm, I configured vfat support during the installation and it
worked
On Wed, 1 Jul 1998, Christopher Barry wrote:
I installed the 2.0.34 kernel source package and did a make menuconfig
and when it comes time to select the filesystems to include support for,
a ton of them appear to be missing, most notably msdos and vfat. When I
installed hamm, I configured
*-Ian Stuart ( 2 Jul)
| On Wed, 1 Jul 1998, Christopher Barry wrote:
|
| I installed the 2.0.34 kernel source package and did a make menuconfig
| and when it comes time to select the filesystems to include support for,
| a ton of them appear to be missing, most notably msdos and vfat. When I
Hi,
I have a problem with the mentioned combination. When i run pon to
establish a ppp-connection pppd immediately exits with the error message
tcgetatt (5)
During booting it says ppp Version 2.2.0. But i installed ppp2.3.5. Now,
do i need to upgrade my kernel ? I´ve seen some patches in var.
On Mon, 15 Jun 1998 [EMAIL PROTECTED] wrote:
Does anyone know when the .deb package for the 2.0.34 kernel source
will be available? Will it be soon, or should I go ahead use a tgz? (What are
the disadvantages of this as opposed to using the .deb file?)
There's a kernel source package
anyone know when the .deb package for the 2.0.34 kernel source
will be available? Will it be soon, or should I go ahead use a tgz? (What
are
the disadvantages of this as opposed to using the .deb file?)
There's a kernel source package at llug.sep.bnl.gov in pub/debian/Incoming
(probably other
On Mon, 15 Jun 1998 [EMAIL PROTECTED] wrote:
What is the significance of packages being in Incoming?
Is it safe to d/l and use them from there, or do things in Incoming have
further processing to undergo before being ready for use?
If I have it straight:
New packages are uploaded to
Does anyone know when the .deb package for the 2.0.34 kernel source
will be available? Will it be soon, or should I go ahead use a tgz? (What are
the disadvantages of this as opposed to using the .deb file?)
Thanks,
Timothy
--
E-Mail: [EMAIL PROTECTED
Marcelo E. Magallon wrote:
El caso es que no tiene ninguna. Lo que falta por indicar es soporte SCSI
para que: disco duro, cdrom, misc, tape? Creo que proceso de compilacion
ve que nada va a usar SCSI asi que no lo pone... creo.
Si que tengo.
la grabadora de CD es IDE/ATAPI pero tengo un ZIp
Just installed kernel 2.0.34 (had 2.0.33-9) in hamm/frozen and
nls_iso8859-1 failed to load. Finally put it ahead of cp_437 in
modules and it loaded after this. Was fine in 2.0.33-9. Is there an
oddity with my hamm/frozen?
Also have Midnight Commander 4.1.35 with Pause after run active. If
I run
On Tue, 9 Jun 1998, Antonio Calvo Rodriguez wrote:
Estoy intentando compilar el kernel 2.0.34 con la opcion de
emulacion-scsi
para que me controle una grabadora HP 7100i pero me he encontrado con el
siguiente
problema.
Tras configurar con make menuconfig
y al hace make-kpkg
sale el error
On Wed, Jun 10, 1998 at 09:22:00AM +0200, Jordi Roman Mejias wrote:
Pero en el fichero .config si tengo definido CONFIG_SCSI
#
# SCSI support
#
CONFIG_SCSI=m
Da igual que ponga y o m ya que el error es el mismo.
A parte de decirle que incluyes el soporte SCSI, tienes que
On Tue, Jun 09, 1998 at 08:30:36PM +0200, Miquel van Smoorenburg wrote:
In article [EMAIL PROTECTED],
Hamish Moffatt [EMAIL PROTECTED] wrote:
bash-2.00# ifconfig eth0 203.14.18.1 netmask 255.255.255.128 broadcast
203.14.18.127
SIOCSIFNETMASK: Invalid argument
It doesn't work on 2.0.32
On Tue, 9 Jun 1998, Hamish Moffatt wrote:
bash-2.00# ifconfig eth0 203.14.18.1 netmask 255.255.255.128 broadcast
203.14.18.127
SIOCSIFNETMASK: Invalid argument
It doesn't work on 2.0.32 either, I just discovered.
Thanks to everyone who has replied. Any other ideas?
It's a long shot
Estoy intentando compilar el kernel 2.0.34 con la opcion de
emulacion-scsi
para que me controle una grabadora HP 7100i pero me he encontrado con el
siguiente
problema.
Tras configurar con make menuconfig
y al hace make-kpkg
sale el error siguiente:
---
gcc -D__KERNEL__ -I/usr/src/kernel-source
I just upgraded a Debian 1.3 (bo) machine to 2.0.34, and when I do
ifconfig eth0 203.14.18.1 netmask 203.14.18.128 broadcast 203.14.18.127
(in /etc/init.d/network), I get
SIOCSIFNETMASK: Invalid argument
then ifconfig reports the mask is set to 255.255.255.0, which is wrong.
So I get wrong
Hamish Moffatt wrote:
I just upgraded a Debian 1.3 (bo) machine to 2.0.34, and when I do
ifconfig eth0 203.14.18.1 netmask 203.14.18.128 broadcast 203.14.18.127
(in /etc/init.d/network), I get
SIOCSIFNETMASK: Invalid argument
then ifconfig reports the mask is set to 255.255.255.0
I just upgraded a Debian 1.3 (bo) machine to 2.0.34, and when I do
ifconfig eth0 203.14.18.1 netmask 203.14.18.128 broadcast 203.14.18.127
That isnt a valid netmask I think you mean 255.255.255.128 ;)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
I just upgraded a Debian 1.3 (bo) machine to 2.0.34, and when I do
ifconfig eth0 203.14.18.1 netmask 203.14.18.128 broadcast 203.14.18.127
^
^
(in /etc/init.d/network), I get
SIOCSIFNETMASK
1 - 100 of 111 matches
Mail list logo
