I don't know if this is a Netscape problem, or an XFree86 4.0.1 problem, or a
kernel problem. I hadn't noticed it with previous kernels so I thought I should
mention it.
I'll download the latest kernel source tonight and try it out.
I'm using 2.4.0-test13-pre4 with XFree86 4.0.1 and Netscape
Followup to: <[EMAIL PROTECTED]>
By author:"Barry K. Nathan" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> In any case, tulips have been more problematic for me than 8139, pcnet32,
> or 3c905c (whose reliability are all comparable IME). I've never tried
> eepro100, though. (Also,
Followup to: [EMAIL PROTECTED]
By author:"Barry K. Nathan" [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
In any case, tulips have been more problematic for me than 8139, pcnet32,
or 3c905c (whose reliability are all comparable IME). I've never tried
eepro100, though. (Also, I'm
I don't know if this is a Netscape problem, or an XFree86 4.0.1 problem, or a
kernel problem. I hadn't noticed it with previous kernels so I thought I should
mention it.
I'll download the latest kernel source tonight and try it out.
I'm using 2.4.0-test13-pre4 with XFree86 4.0.1 and Netscape
Thanks for the prompt response.
Regards
Sid.
Alan Cox wrote:
>
> > The problem showed up on the stroke of test13-pre4-ac2 and stuff from
> > Alan has been merged in. I went from pre4-ac2 to pre5 (AOK) and now
> > attempting pre7...
>
> Its defin
On Sun, Dec 31, 2000 at 03:18:21AM +, Ton Hospel wrote:
> I was talking about avoiding that the same device gets multiple mounted
> at the SAME place, e.g. when doing mount -a, which is often used as a
> quick way to get the new entries in /etc/fstab
You get EBUSY if you try.
-
To
On Sun, Dec 31, 2000 at 03:18:21AM +, Ton Hospel wrote:
I was talking about avoiding that the same device gets multiple mounted
at the SAME place, e.g. when doing mount -a, which is often used as a
quick way to get the new entries in /etc/fstab
You get EBUSY if you try.
-
To unsubscribe
Thanks for the prompt response.
Regards
Sid.
Alan Cox wrote:
The problem showed up on the stroke of test13-pre4-ac2 and stuff from
Alan has been merged in. I went from pre4-ac2 to pre5 (AOK) and now
attempting pre7...
Its definitely coming from the AX.25 related
In article <[EMAIL PROTECTED]>,
Alexander Viro <[EMAIL PROTECTED]> writes:
> On Sat, 30 Dec 2000, Ton Hospel wrote:
>
>> It should still need a special flag or something, since it's
>> impossible for userspace to check this atomically.
>
> To check _what_? Having the same tree mounted
> The problem showed up on the stroke of test13-pre4-ac2 and stuff from
> Alan has been merged in. I went from pre4-ac2 to pre5 (AOK) and now
> attempting pre7...
Its definitely coming from the AX.25 related changes. Please send me your
.config and I'll go squash this one
The problem showed up on the stroke of test13-pre4-ac2 and stuff from
Alan has been merged in. I went from pre4-ac2 to pre5 (AOK) and now
attempting pre7...
ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext
arch/i386/kernel
/head.o arch/i386/kernel/init_task.o init
On Sat, 30 Dec 2000, Ton Hospel wrote:
> It should still need a special flag or something, since it's
> impossible for userspace to check this atomically.
To check _what_? Having the same tree mounted in several places is
allowed. End of story. Atomicity of any kind is a non-issue - if you
In article <[EMAIL PROTECTED]>,
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Sat, 23 Dec 2000 [EMAIL PROTECTED] wrote:
>>
>> 1. multiple mount of devices possible 2.4.0-test1 - 2.4.0-test13-pre4
>>
>> 2. its still possible to mount device
Andrew Morton wrote:
> The 3c905C is a well manufactured and very feature-rich NIC which at
> present appears to have fewer problem reports than eepro100, 8139 or tulip.
3c905c is a bit expensive, though. pcnet32 cards also work very well for
me, and are less expensive. The 905c could be a
Andrew Morton <[EMAIL PROTECTED]> écrit :
[...]
> The 3c905C is a well manufactured and very feature-rich NIC which at
> present appears to have fewer problem reports than eepro100, 8139 or tulip.
I guess that the lack of problem reports for the epic chipset comes from
a smaller user base. FWIW,
Linus Torvalds wrote:
>
> I bet that others will have other recommendations, but so far I have at
> least personally had good luck with the eepro100.
The 3c905C is a well manufactured and very feature-rich NIC which at
present appears to have fewer problem reports than eepro100, 8139 or tulip.
Linus Torvalds wrote:
I bet that others will have other recommendations, but so far I have at
least personally had good luck with the eepro100.
The 3c905C is a well manufactured and very feature-rich NIC which at
present appears to have fewer problem reports than eepro100, 8139 or tulip.
Andrew Morton [EMAIL PROTECTED] écrit :
[...]
The 3c905C is a well manufactured and very feature-rich NIC which at
present appears to have fewer problem reports than eepro100, 8139 or tulip.
I guess that the lack of problem reports for the epic chipset comes from
a smaller user base. FWIW, I
Andrew Morton wrote:
The 3c905C is a well manufactured and very feature-rich NIC which at
present appears to have fewer problem reports than eepro100, 8139 or tulip.
3c905c is a bit expensive, though. pcnet32 cards also work very well for
me, and are less expensive. The 905c could be a better
In article [EMAIL PROTECTED],
Linus Torvalds [EMAIL PROTECTED] writes:
On Sat, 23 Dec 2000 [EMAIL PROTECTED] wrote:
1. multiple mount of devices possible 2.4.0-test1 - 2.4.0-test13-pre4
2. its still possible to mount devices several times.
IMHO it shouldnt be possible like
On Sat, 30 Dec 2000, Ton Hospel wrote:
It should still need a special flag or something, since it's
impossible for userspace to check this atomically.
To check _what_? Having the same tree mounted in several places is
allowed. End of story. Atomicity of any kind is a non-issue - if you
have
The problem showed up on the stroke of test13-pre4-ac2 and stuff from
Alan has been merged in. I went from pre4-ac2 to pre5 (AOK) and now
attempting pre7...
ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext
arch/i386/kernel
/head.o arch/i386/kernel/init_task.o init
The problem showed up on the stroke of test13-pre4-ac2 and stuff from
Alan has been merged in. I went from pre4-ac2 to pre5 (AOK) and now
attempting pre7...
Its definitely coming from the AX.25 related changes. Please send me your
.config and I'll go squash this one
drivers/net
In article [EMAIL PROTECTED],
Alexander Viro [EMAIL PROTECTED] writes:
On Sat, 30 Dec 2000, Ton Hospel wrote:
It should still need a special flag or something, since it's
impossible for userspace to check this atomically.
To check _what_? Having the same tree mounted in several
AIL PROTECTED] (Linus Torvalds)
Subject: Re: Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again
Date: 28 Dec 2000 22:15:17 -0800
Organization: Transmeta Corporation
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
Prece
> I don't want to have any more network card problems.
> I'm tired of this crappy 8139.
hmmm... The only cards I'll buy are 8139 based (SMC EZNet 10/100).
They have worked great on every OS i've tried and only cost 14 bucks
at my local CompUSA. I love em to pieces... The newer ones are only
> I really need to get rid of this 8139 card. Since
> yall are the oracle, which nice 100mbs card is fine
> hardware and is coupled with a well debugged driver?
>
> I don't want to have any more network card problems.
> I'm tired of this crappy 8139.
I have an 8139 card and it's on a 2.4 testN
I really need to get rid of this 8139 card. Since
yall are the oracle, which nice 100mbs card is fine
hardware and is coupled with a well debugged driver?
I don't want to have any more network card problems.
I'm tired of this crappy 8139.
I have an 8139 card and it's on a 2.4 testN kernel
I don't want to have any more network card problems.
I'm tired of this crappy 8139.
hmmm... The only cards I'll buy are 8139 based (SMC EZNet 10/100).
They have worked great on every OS i've tried and only cost 14 bucks
at my local CompUSA. I love em to pieces... The newer ones are only
like
PROTECTED] (Linus Torvalds)
Subject: Re: Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again
Date: 28 Dec 2000 22:15:17 -0800
Organization: Transmeta Corporation
References: [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Precedence: bulk
X-Mailing-List
In article <[EMAIL PROTECTED]>,
Mike Elmore <[EMAIL PROTECTED]> wrote:
>
>I really need to get rid of this 8139 card. Since
>yall are the oracle, which nice 100mbs card is fine
>hardware and is coupled with a well debugged driver?
There are always problems with some hardware, but my personal
All,
You are some damn smart people.
Whatever evil was happening is fixed in test13-pre5.
I pounded it with 3 successive full backups of my
multigig nfs mounted home directory to my Onstream
drive while downloading a kernel and doing multiple
>100M file copies over nfs at the same time while
Try pre5
Later,
David S. Miller
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Elmore
[EMAIL PROTECTED]
"Never confuse activity with accomplishment."
-unknown
ksymoops 2.3.5 on i686 2.4.0-test13-pre4. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test13-pre4
http://distro.conectiva.com.br/
--- linux-2.4.0-test13-pre4/mm/filemap.c.orig Wed Dec 27 16:48:23 2000
+++ linux-2.4.0-test13-pre4/mm/filemap.cThu Dec 28 17:12:42 2000
@@ -1900,7 +1900,7 @@
/* Make sure this doesn't exceed the process's max rss. */
error = -EIO;
- rlim_
upgraded to test13-pre4. When I ran "depmod -a", I got a lot of errors
about unresolved symbols for the drm modules ...
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-test13-pre4/kernel/drivers/char/drm/i810.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-test13-p
upgraded to test13-pre4. When I ran "depmod -a", I got a lot of errors
about unresolved symbols for the drm modules ...
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-test13-pre4/kernel/drivers/char/drm/i810.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-test13-p
http://distro.conectiva.com.br/
--- linux-2.4.0-test13-pre4/mm/filemap.c.orig Wed Dec 27 16:48:23 2000
+++ linux-2.4.0-test13-pre4/mm/filemap.cThu Dec 28 17:12:42 2000
@@ -1900,7 +1900,7 @@
/* Make sure this doesn't exceed the process's max rss. */
error = -EIO;
- rlim
Elmore
[EMAIL PROTECTED]
"Never confuse activity with accomplishment."
-unknown
ksymoops 2.3.5 on i686 2.4.0-test13-pre4. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test13-pre4
Try pre5
Later,
David S. Miller
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
All,
You are some damn smart people.
Whatever evil was happening is fixed in test13-pre5.
I pounded it with 3 successive full backups of my
multigig nfs mounted home directory to my Onstream
drive while downloading a kernel and doing multiple
100M file copies over nfs at the same time while
In article [EMAIL PROTECTED],
Mike Elmore [EMAIL PROTECTED] wrote:
I really need to get rid of this 8139 card. Since
yall are the oracle, which nice 100mbs card is fine
hardware and is coupled with a well debugged driver?
There are always problems with some hardware, but my personal
.
The box is running 2.4.0-test13-pre4.
Have another problem where if i switch the 8139 to eth0 it
simply doesn't work, but I sent that to Jeff.
On to this problem...
The masquerade box has a partition with my mp3's on it that
I mount up on my workstation on the local lan.
I was listening to a mp3
When I do a "shutdown -h now" in Slackware 7.1 with the
2.4.0-test13-pre4 kernel, sometimes after the words "Power down" appear
I get the message:
ACPI: S5 Failed
(I think that's the phrasing, of course since it only happens when I
shutdown for the night my memo
This seems to be a problem that was introduced with the big ACPI update
as pointed out earlier by Andrew Morton. Try disabling ACPI (since your
BIOS does not seem to have ACPI support anyway it should not be a
disadvantage) and see if PCMCIA support works again on bootup.
Jens
On Wed, Dec 27,
Hi!
Kernel 2.4.0-test13-pre4 (without any patches) does not see some of the PCI
devices with my setup here. The machine is a IBM Netfinity 7100 Quad-Xeon with
a Serverworks Chipset.
The RAID-Controller (a IBM ServeRAID-4L) is not detected. Kernel 2.2.17
detects it. I also checked -test10
When I boot with the following inserted:
Socket 0:
product info: "3Com Corporation", "3CCFE575BT", "LAN Cardbus Card", "001"
manfid: 0x0101, 0x5157
function: 6 (network)
Socket 1:
product info: "PCMCIA ", "56K V.90 Fax Modem (LK) ", "FM560LK "
manfid: 0x0175, 0x
When I boot with the following inserted:
Socket 0:
product info: "3Com Corporation", "3CCFE575BT", "LAN Cardbus Card", "001"
manfid: 0x0101, 0x5157
function: 6 (network)
Socket 1:
product info: "PCMCIA ", "56K V.90 Fax Modem (LK) ", "FM560LK "
manfid: 0x0175, 0x
Hi!
Kernel 2.4.0-test13-pre4 (without any patches) does not see some of the PCI
devices with my setup here. The machine is a IBM Netfinity 7100 Quad-Xeon with
a Serverworks Chipset.
The RAID-Controller (a IBM ServeRAID-4L) is not detected. Kernel 2.2.17
detects it. I also checked -test10
This seems to be a problem that was introduced with the big ACPI update
as pointed out earlier by Andrew Morton. Try disabling ACPI (since your
BIOS does not seem to have ACPI support anyway it should not be a
disadvantage) and see if PCMCIA support works again on bootup.
Jens
On Wed, Dec 27,
When I do a "shutdown -h now" in Slackware 7.1 with the
2.4.0-test13-pre4 kernel, sometimes after the words "Power down" appear
I get the message:
ACPI: S5 Failed
(I think that's the phrasing, of course since it only happens when I
shutdown for the night my memo
On Mon, Dec 25, 2000 at 04:34:37PM -0800, Linus Torvalds wrote:
>
>
> On Mon, 25 Dec 2000, Jasper Spaans wrote:
> >
> > I am having some reproducible crashes with 2.4.0-test13-pre4, whenever I
> > do some 'heavy' nfs-ing.. decoded oops:
>
> It looks like
On Mon, Dec 25, 2000 at 04:34:37PM -0800, Linus Torvalds wrote:
On Mon, 25 Dec 2000, Jasper Spaans wrote:
I am having some reproducible crashes with 2.4.0-test13-pre4, whenever I
do some 'heavy' nfs-ing.. decoded oops:
It looks like most of what you have is modules. Is netfilter
On Mon, 25 Dec 2000, Jasper Spaans wrote:
>
> I am having some reproducible crashes with 2.4.0-test13-pre4, whenever I
> do some 'heavy' nfs-ing.. decoded oops:
It looks like most of what you have is modules. Is netfilter enabled as a
module too? Can you reproduce it without modules
Hi!
I am having some reproducible crashes with 2.4.0-test13-pre4, whenever I
do some 'heavy' nfs-ing.. decoded oops:
ksymoops 2.3.4 on i686 2.4.0-test13-pre4. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test13-pre4
On Mon, Dec 25 2000, Mohammad A. Haque wrote:
> Fix confirmed. Am i supposed to get some DriveSense errors? I probably
> am just don't recall.
Good. The whole idea of cdrom_log_sense is to be able to cleanly
limit the (often) sense-less (yes, haha :) ide-cd verbosity. Some of the
css stuff are
Sorry, I meant DriveReady SeekComplete Error
"Mohammad A. Haque" wrote:
> Fix confirmed. Am i supposed to get some DriveSense errors? I probably
> am just don't recall.
--
=
Mohammad A. Haque
Fix confirmed. Am i supposed to get some DriveSense errors? I probably
am just don't recall.
Jens Axboe wrote:
> Yes I know about this one, I've attached the patch here again. Linus,
> could you apply?
>
> --- drivers/ide/ide-cd.c~ Sat Dec 23 23:59:52 2000
> +++ drivers/ide/ide-cd.c
On Mon, Dec 25 2000, Mohammad A. Haque wrote:
> Jens, I made sure to reverse the udf patch I mentioned in another thread
> (all it really is merging changes from linux-udf cvs into the current
> kernel). So this is from a clean test13-pre4 w/ some netfilter fixes.
Ok, looks unrelate
Jens, I made sure to reverse the udf patch I mentioned in another thread
(all it really is merging changes from linux-udf cvs into the current
kernel). So this is from a clean test13-pre4 w/ some netfilter fixes.
ksymoops 0.7c on i686 2.4.0-test13-pre4. Options used
-V (default)
-K
test12 with
> accessing my dvd to using oms. Now updating to test13-pre4
> I get a complete lock up of my whole system when executing oms.
>
> I can access the drive via mounting it... with no trouble what ever.
>
> Here is a snip from my message file No clue what to test for he
Odd happening here. Been running good as gold through test12 with
accessing my dvd to using oms. Now updating to test13-pre4
I get a complete lock up of my whole system when executing oms.
I can access the drive via mounting it... with no trouble what ever.
Here is a snip from my message file
Odd happening here. Been running good as gold through test12 with
accessing my dvd to using oms. Now updating to test13-pre4
I get a complete lock up of my whole system when executing oms.
I can access the drive via mounting it... with no trouble what ever.
Here is a snip from my message file
On Mon, Dec 25 2000, Mohammad A. Haque wrote:
Jens, I made sure to reverse the udf patch I mentioned in another thread
(all it really is merging changes from linux-udf cvs into the current
kernel). So this is from a clean test13-pre4 w/ some netfilter fixes.
Ok, looks unrelated however.
EIP
Fix confirmed. Am i supposed to get some DriveSense errors? I probably
am just don't recall.
Jens Axboe wrote:
Yes I know about this one, I've attached the patch here again. Linus,
could you apply?
--- drivers/ide/ide-cd.c~ Sat Dec 23 23:59:52 2000
+++ drivers/ide/ide-cd.cSun
Sorry, I meant DriveReady SeekComplete Error
"Mohammad A. Haque" wrote:
Fix confirmed. Am i supposed to get some DriveSense errors? I probably
am just don't recall.
--
=
Mohammad A. Haque
On Mon, Dec 25 2000, Mohammad A. Haque wrote:
Fix confirmed. Am i supposed to get some DriveSense errors? I probably
am just don't recall.
Good. The whole idea of cdrom_log_sense is to be able to cleanly
limit the (often) sense-less (yes, haha :) ide-cd verbosity. Some of the
css stuff are
Hi!
I am having some reproducible crashes with 2.4.0-test13-pre4, whenever I
do some 'heavy' nfs-ing.. decoded oops:
ksymoops 2.3.4 on i686 2.4.0-test13-pre4. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test13-pre4
On Mon, 25 Dec 2000, Jasper Spaans wrote:
I am having some reproducible crashes with 2.4.0-test13-pre4, whenever I
do some 'heavy' nfs-ing.. decoded oops:
It looks like most of what you have is modules. Is netfilter enabled as a
module too? Can you reproduce it without modules, in case
sers...
same as sym-links ... no new feature...
Reinhard.
> On Sat, 23 Dec 2000 [EMAIL PROTECTED] wrote:
>
> >
> > 1. multiple mount of devices possible 2.4.0-test1 - 2.4.0-test13-pre4
> >
> > 2. its still possible to mount devices several times.
> >IMHO
Hello!
> eax: 20202037 ebx: d3a406c0 ecx: cf683024 edx: c734a2a0
Ough... found eventually. skb->dev turns out to be not initialized. 8)8)
This patchlet surely fixes the bug. (plus writes are ordered)
Alexey
--- ../vger3-001222/linux/net/core/skbuff.c Fri Dec 22 19:37:54 2000
+++
Hello!
eax: 20202037 ebx: d3a406c0 ecx: cf683024 edx: c734a2a0
Ough... found eventually. skb-dev turns out to be not initialized. 8)8)
This patchlet surely fixes the bug. (plus writes are ordered)
Alexey
--- ../vger3-001222/linux/net/core/skbuff.c Fri Dec 22 19:37:54 2000
+++
ame as sym-links ... no new feature...
Reinhard.
On Sat, 23 Dec 2000 [EMAIL PROTECTED] wrote:
1. multiple mount of devices possible 2.4.0-test1 - 2.4.0-test13-pre4
2. its still possible to mount devices several times.
IMHO it shouldnt be possible like 2.2.18
with umount in /p
Just got an oops uner test13-pre4 when I tried to access a new nfs
export. Looks like the ip defrag monster doesn't want to go away =)
ksymoops 0.7c on i686 2.4.0-test13-pre4. Options used
-V (default)
-K (specified)
-L (specified)
-o /lib/modules/2.4.0-test13-pre4/ (default
On Sat, 23 Dec 2000, ebi4 wrote:
> ld: cannot open drivers/ieee1394/ieee1394.a: No such file or directory
> make: *** [vmlinux] Error 1
I sent the following patch to Linus already. It should fix the problem.
--Kai
diff -ur linux-2.4.0-test13-pre3/drivers/ieee1394/Makefile
ebi4 wrote:
>ld: cannot open drivers/ieee1394/ieee1394.a: No such file or directory
>make: *** [vmlinux] Error 1
Changing the order of a few lines in linux/drivers/ieee1394/Makefile fixes
this problem. Here is the patch:
Steven
diff -u linux/drivers/ieee1394/Makefile.orig
it is not a problem, it is a feature. (and a useful one!)
On Sat, 23 Dec 2000 [EMAIL PROTECTED] wrote:
>
> 1. multiple mount of devices possible 2.4.0-test1 - 2.4.0-test13-pre4
>
> 2. its still possible to mount devices several times.
>IMHO it shouldnt be possi
1. multiple mount of devices possible 2.4.0-test1 - 2.4.0-test13-pre4
2. its still possible to mount devices several times.
IMHO it shouldnt be possible like 2.2.18
with umount in /proc/mounts is still the real information,
in /etc/mtab all corresponding mountpoints are deleted.
3
ld: cannot open drivers/ieee1394/ieee1394.a: No such file or directory
make: *** [vmlinux] Error 1
: Gene Imes http://www.ozob.net :
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read
In article <[EMAIL PROTECTED]> you wrote:
> net/network.o(.text+0x3ff92): undefined reference to `atm_lane_init'
> net/network.o(.text+0x40039): undefined reference to `atm_mpoa_init'
Hi,
The patch below should fix that.
Greetings,
Arjan van de Ven
--- linux/net/atm/Makefile Fri Dec
Hello,
With 2.4.0-test13-pre4 i noticed
"Networking options"
LAN Emulation (LANE) support
Multi-Protocol Over ATM (MPOA) support
results with 'make bzImage' in:
make[1]: Leaving directory `/usr/src/linux-2.4.0-test13-4/arch/i386/lib'
ld -m elf_i386 -T /usr/src/linux
Daniel Stone wrote:
>linux-2.4.0-test12 + reiserfs + test13-pre4 + reiserfs makefile fix (only
>changes fs/reiserfs/Makefile) + netfilter patch-o-matic stuff (only touches
>net/ipv4/netfilter) + test13-pre4-ac2.
I was able to patch and build 2.4.0test13pre4-ac2. I did not see th
succeeded at 511 (offset 9 lines).
> >> > 1 out of 2 hunks FAILED -- saving rejects to file
> >> > arch/i386/kernel/smp.c.rej
> >> >
> >> > Works fine if I reverse it and then put it back in. ?
> >>
> >> Its a bug in my patch - get 1
gt;> > 1 out of 2 hunks FAILED -- saving rejects to file
>> > arch/i386/kernel/smp.c.rej
>> >
>> > Works fine if I reverse it and then put it back in. ?
>>
>> Its a bug in my patch - get 13pre4ac2 ..
>
> Um.
> Subject: Re: test13-pre4-ac2 - pa
s to file arch/i386/kernel/smp.c.rej
> >
> > Works fine if I reverse it and then put it back in. ?
>
> Its a bug in my patch - get 13pre4ac2 ..
Um.
Subject: Re: test13-pre4-ac2 - part of diff fails
It's _IN_ 13-4ac2.
d
-
To unsubscribe from this list: send the line "unsubscribe
> patching file arch/i386/kernel/smp.c
> Reversed (or previously applied) patch detected! Assume -R? [n]
> Apply anyway? [n] y
> Hunk #1 FAILED at 278.
> Hunk #2 succeeded at 511 (offset 9 lines).
> 1 out of 2 hunks FAILED -- saving rejects to file arch/i386/kernel/smp.c.rej
>
> Works fine if
Since I've installed 2.4.0 test13-pre4, I see the following errors
in my log:
sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
and xmcd reports:
CD audio: ioctl error on /dev/scd0: cmd=CDROMVOLCTRL errno=95
This was working fine with 2.4.0 test12-pre5, which was the previous
kernel
Since I've installed 2.4.0 test13-pre4, I see the following errors
in my log:
sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
and xmcd reports:
CD audio: ioctl error on /dev/scd0: cmd=CDROMVOLCTRL errno=95
This was working fine with 2.4.0 test12-pre5, which was the previous
kernel
patching file arch/i386/kernel/smp.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n] y
Hunk #1 FAILED at 278.
Hunk #2 succeeded at 511 (offset 9 lines).
1 out of 2 hunks FAILED -- saving rejects to file arch/i386/kernel/smp.c.rej
Works fine if I
if I reverse it and then put it back in. ?
Its a bug in my patch - get 13pre4ac2 ..
Um.
Subject: Re: test13-pre4-ac2 - part of diff fails
It's _IN_ 13-4ac2.
d
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please re
/i386/kernel/smp.c.rej
Works fine if I reverse it and then put it back in. ?
Its a bug in my patch - get 13pre4ac2 ..
Um.
Subject: Re: test13-pre4-ac2 - part of diff fails
It's _IN_ 13-4ac2.
I applied test13-pre4-ac2 here, and it applied cleanly.
Are you applying it to a clean tree
arch/i386/kernel/smp.c.rej
Works fine if I reverse it and then put it back in. ?
Its a bug in my patch - get 13pre4ac2 ..
Um.
Subject: Re: test13-pre4-ac2 - part of diff fails
It's _IN_ 13-4ac2.
I applied test13-pre4-ac2 here, and it applied cleanly.
Are you applying
Daniel Stone wrote:
linux-2.4.0-test12 + reiserfs + test13-pre4 + reiserfs makefile fix (only
changes fs/reiserfs/Makefile) + netfilter patch-o-matic stuff (only touches
net/ipv4/netfilter) + test13-pre4-ac2.
I was able to patch and build 2.4.0test13pre4-ac2. I did not see the problem
Hello,
With 2.4.0-test13-pre4 i noticed
"Networking options"
M LAN Emulation (LANE) support
M Multi-Protocol Over ATM (MPOA) support
results with 'make bzImage' in:
make[1]: Leaving directory `/usr/src/linux-2.4.0-test13-4/arch/i386/lib'
ld -m elf_i386 -T /usr/src/linux
In article [EMAIL PROTECTED] you wrote:
net/network.o(.text+0x3ff92): undefined reference to `atm_lane_init'
net/network.o(.text+0x40039): undefined reference to `atm_mpoa_init'
Hi,
The patch below should fix that.
Greetings,
Arjan van de Ven
--- linux/net/atm/Makefile Fri Dec 22
ld: cannot open drivers/ieee1394/ieee1394.a: No such file or directory
make: *** [vmlinux] Error 1
: Gene Imes http://www.ozob.net :
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read
1. multiple mount of devices possible 2.4.0-test1 - 2.4.0-test13-pre4
2. its still possible to mount devices several times.
IMHO it shouldnt be possible like 2.2.18
with umount in /proc/mounts is still the real information,
in /etc/mtab all corresponding mountpoints are deleted.
3
it is not a problem, it is a feature. (and a useful one!)
On Sat, 23 Dec 2000 [EMAIL PROTECTED] wrote:
1. multiple mount of devices possible 2.4.0-test1 - 2.4.0-test13-pre4
2. its still possible to mount devices several times.
IMHO it shouldnt be possible like 2.2.18
with umount
ebi4 wrote:
ld: cannot open drivers/ieee1394/ieee1394.a: No such file or directory
make: *** [vmlinux] Error 1
Changing the order of a few lines in linux/drivers/ieee1394/Makefile fixes
this problem. Here is the patch:
Steven
diff -u linux/drivers/ieee1394/Makefile.orig
On Sat, 23 Dec 2000, ebi4 wrote:
ld: cannot open drivers/ieee1394/ieee1394.a: No such file or directory
make: *** [vmlinux] Error 1
I sent the following patch to Linus already. It should fix the problem.
--Kai
diff -ur linux-2.4.0-test13-pre3/drivers/ieee1394/Makefile
1 - 100 of 121 matches
Mail list logo
