On Sun, 17 Jun 2001, Christian Robottom Reis wrote:
Try to add options eepro100 options=0 to your /etc/modules.conf
to default the speed to 10Mbps if you're using 10BaseT.
I'm not using modules for this driver (can't see the point, really); does
this fix anything if I change it to 0x20
On Mon, 18 Jun 2001, Mohammad A. Haque wrote:
On Mon, 18 Jun 2001, Anuradha Ratnaweera wrote:
I started running 2.4.6-pre3 using the same configuration file as 2.4.5.
Diff shows no effective differences between two config files.
depmod complains unresolved symbols (do_softirq) in
Try to add "options eepro100 options=0" to your /etc/modules.conf
to default the speed to 10Mbps if you're using 10BaseT.
add to /etc/modules.conf ...
# options=0x30 100mbps full duplex
# options=0x20 100mbps half duplex
# options=0 10mbps half duplex
options eepro100 options=0
then run
Try to add options eepro100 options=0 to your /etc/modules.conf
to default the speed to 10Mbps if you're using 10BaseT.
add to /etc/modules.conf ...
# options=0x30 100mbps full duplex
# options=0x20 100mbps half duplex
# options=0 10mbps half duplex
options eepro100 options=0
then run
Got the following journaling error on 2.4.5 SMP during shutdown ...
Unmounting local file systems.
journal_begin called without kernel lock held
kernel BUG at journal.c:423!
invalid operand:
CPU1: 1
EIP:0010:[]
EFLAGS: 00010286
eax: 001d ebx: f0951f2c ecx: 0001
Got the following journaling error on 2.4.5 SMP during shutdown ...
Unmounting local file systems.
journal_begin called without kernel lock held
kernel BUG at journal.c:423!
invalid operand:
CPU1: 1
EIP:0010:[f8854140]
EFLAGS: 00010286
eax: 001d ebx: f0951f2c ecx:
This may sound stupid as Linus is working for Transmeta and
I did see under menuconfig that crusoe is supported.
Question is whether I need to recompile everything (kernel and binaries)
on my current 586 platform in order to move to Crusoe?
I'm thinking about getting the new Toshiba Libretto
This may sound stupid as Linus is working for Transmeta and
I did see under menuconfig that crusoe is supported.
Question is whether I need to recompile everything (kernel and binaries)
on my current 586 platform in order to move to Crusoe?
I'm thinking about getting the new Toshiba Libretto
I'm using 2.4.5-pre5 and before on 2.4.x (without -ac) and don't have such
problem.
boston:root:/tmp> mount -o loop ram /mnt
boston:root:/tmp> umount /mnt
boston:root:/tmp> strace losetup -d /dev/loop0
execve("/sbin/losetup", ["losetup", "-d", "/dev/loop0"], [/* 47 vars */])
= 0
brk(0)
I'm using 2.4.5-pre5 and before on 2.4.x (without -ac) and don't have such
problem.
boston:root:/tmp mount -o loop ram /mnt
boston:root:/tmp umount /mnt
boston:root:/tmp strace losetup -d /dev/loop0
execve(/sbin/losetup, [losetup, -d, /dev/loop0], [/* 47 vars */])
= 0
brk(0)
On Mon, 21 May 101, Allan Duncan wrote:
> This addition for 2.4.5-pre4 has caused a compile failure with a parsing error:
>
> drivers/ide/ide-pci.c:711
> if (!IDE_PCI_DEVID_EQ(d->devid, DEVID_CS5530)
>
> In my case CONFIG_BLK_DEV_CS5530 is not defined.
if
On Mon, 21 May 101, Allan Duncan wrote:
This addition for 2.4.5-pre4 has caused a compile failure with a parsing error:
drivers/ide/ide-pci.c:711
if (!IDE_PCI_DEVID_EQ(d-devid, DEVID_CS5530)
In my case CONFIG_BLK_DEV_CS5530 is not defined.
if (!IDE_PCI_DEVID_EQ(d-devid,
There's an error in ide-pci.c that prevented it from compiling 2.4.5-pre4.
Try this.
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
--- drivers/ide/ide-pci.c Sun May 20 11:56:48 2001
+++ drivers/ide/ide-pci.c.new Sun May 20 11:56:45 2001
@@ -708,7 +708,7 @@
/*
There's an error in ide-pci.c that prevented it from compiling 2.4.5-pre4.
Try this.
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
--- drivers/ide/ide-pci.c Sun May 20 11:56:48 2001
+++ drivers/ide/ide-pci.c.new Sun May 20 11:56:45 2001
@@ -708,7 +708,7 @@
/*
Where can I get the latest "mount" ?
# mount -t nfs lo:/ /mnt
NFS: NFSv3 not supported.
nfs warning: mount version older than kernel
#mount --version
mount: mount-2.11a
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
Where can I get the latest mount ?
# mount -t nfs lo:/ /mnt
NFS: NFSv3 not supported.
nfs warning: mount version older than kernel
#mount --version
mount: mount-2.11a
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
depmod -ae yields the following errors under 2.4.4-pre8
Any fix?
depmod: *** Unresolved symbols in
/lib/modules/2.4.4-pre8/kernel/drivers/char/drm/i810.o
depmod: rwsem_down_write_failed
depmod: rwsem_wake
depmod: *** Unresolved symbols in
depmod -ae yields the following errors under 2.4.4-pre8
Any fix?
depmod: *** Unresolved symbols in
/lib/modules/2.4.4-pre8/kernel/drivers/char/drm/i810.o
depmod: rwsem_down_write_failed
depmod: rwsem_wake
depmod: *** Unresolved symbols in
On Mon, 23 Apr 2001, Alan Cox wrote:
> 2.4.4pre6 only builds with gcc 2.96. If you apply the __builtin_expect fixes
> it builds and runs fine with 2.95. Not tried egcs. The gcc 3.0 asm constraints
> one I've yet to see a fix for.
So, should I upgrade to 2.96 from 2.95.3?
But, from
On Mon, 23 Apr 2001, Martin Dalecki wrote:
> > > depmod: *** Unresolved symbols in
>/lib/modules/2.4.3-ac11/kernel/drivers/md/lvm-mod.o
try this (after you have applied the patch for lvm 0.9.1_beta7) ...
Jeff
[[EMAIL PROTECTED]]
--- /u2/src/linux/drivers/md/lvm.c.org Mon Apr 23 21:11:32
On Mon, 23 Apr 2001, Martin Dalecki wrote:
depmod: *** Unresolved symbols in
/lib/modules/2.4.3-ac11/kernel/drivers/md/lvm-mod.o
try this (after you have applied the patch for lvm 0.9.1_beta7) ...
Jeff
[[EMAIL PROTECTED]]
--- /u2/src/linux/drivers/md/lvm.c.org Mon Apr 23 21:11:32 2001
On Mon, 23 Apr 2001, Alan Cox wrote:
2.4.4pre6 only builds with gcc 2.96. If you apply the __builtin_expect fixes
it builds and runs fine with 2.95. Not tried egcs. The gcc 3.0 asm constraints
one I've yet to see a fix for.
So, should I upgrade to 2.96 from 2.95.3?
But, from
cannot compile 2.4.4-pre6. This may have been reported, but I
haven't seen it.
Thanks,
Jeff.
ld -m elf_i386 -T /u2/src/linux/arch/i386/vmlinux.lds -e stext
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o
init/version.o \
--start-group \
cannot compile 2.4.4-pre6. This may have been reported, but I
haven't seen it.
Thanks,
Jeff.
ld -m elf_i386 -T /u2/src/linux/arch/i386/vmlinux.lds -e stext
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o
init/version.o \
--start-group \
great! working fine one.
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
On Wed, 18 Apr 2001, Alexander Viro wrote:
>
>
> On Wed, 18 Apr 2001, Jeff Chua wrote:
>
> > depmod: *** Unresolved symbols in /lib/modules/2.4.4-pre4/kernel/fs/nfsd/nfsd.o
> > depmod: nfsd_li
great! working fine one.
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
On Wed, 18 Apr 2001, Alexander Viro wrote:
On Wed, 18 Apr 2001, Jeff Chua wrote:
depmod: *** Unresolved symbols in /lib/modules/2.4.4-pre4/kernel/fs/nfsd/nfsd.o
depmod: nfsd_linkage_Rb56858ea
Grrr...
Add #include
I compiled 2.4.4-pre4 and use nfsd as a module. Got the following error:
depmod: *** Unresolved symbols in /lib/modules/2.4.4-pre4/kernel/fs/nfsd/nfsd.o
depmod: nfsd_linkage_Rb56858ea
Didn't have such problem on 2.4.4-pre3.
Jeff
[ [EMAIL PROTECTED] ]
-
To unsubscribe from this
I compiled 2.4.4-pre4 and use nfsd as a module. Got the following error:
depmod: *** Unresolved symbols in /lib/modules/2.4.4-pre4/kernel/fs/nfsd/nfsd.o
depmod: nfsd_linkage_Rb56858ea
Didn't have such problem on 2.4.4-pre3.
Jeff
[ [EMAIL PROTECTED] ]
-
To unsubscribe from this
Below are the errors generated from "make" for 2.4.4-pre2
I've no problem compiling 2.4.4-pre1.
___
gcc -D__KERNEL__ -I/u2/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
Below are the errors generated from "make" for 2.4.4-pre2
I've no problem compiling 2.4.4-pre1.
___
gcc -D__KERNEL__ -I/u2/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
RT_SYMBOL(strtok);
EXPORT_SYMBOL(strpbrk);
EXPORT_SYMBOL(simple_strtol);
--
___
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
On Tue, 10 Apr 2001, Nick Urbanik wrote:
> Jeff Chua wrote:
>
> > depmod version 2.4.5
> &
);
EXPORT_SYMBOL(strpbrk);
EXPORT_SYMBOL(simple_strtol);
--
___
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
On Tue, 10 Apr 2001, Nick Urbanik wrote:
Jeff Chua wrote:
depmod version 2.4.5
Compiled 2.4.4-pre1 but running
depmod version 2.4.5
Compiled 2.4.4-pre1 but running "depmod" generates a lot of these ...
depmod: *** Unresolved symbols in
/lib/modules/2.4.4-pre1/kernel/drivers/char/ltmodem.o
depmod: strstr
depmod: *** Unresolved symbols in
/lib/modules/2.4.4-pre1/kernel/drivers/char/serial.o
depmod version 2.4.5
Compiled 2.4.4-pre1 but running "depmod" generates a lot of these ...
depmod: *** Unresolved symbols in
/lib/modules/2.4.4-pre1/kernel/drivers/char/ltmodem.o
depmod: strstr
depmod: *** Unresolved symbols in
/lib/modules/2.4.4-pre1/kernel/drivers/char/serial.o
Does anybody have bad experience with gcc-2.95.3?
I'm using gcc-2.95.2 with linux 2.4.3 and have no problem with it.
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Does anybody have bad experience with gcc-2.95.3?
I'm using gcc-2.95.2 with linux 2.4.3 and have no problem with it.
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Sun, 1 Apr 2001, Trever L. Adams wrote:
> I am trying to find out if I am the only one who has pppd drop packets
> as bogus when the port is set at 115Kbps. I only get it at that speed.
> It causes stall outs etc.
>
works fine for me.
Jeff
-
To unsubscribe from this list: send the line
On Sun, 1 Apr 2001, Trever L. Adams wrote:
I am trying to find out if I am the only one who has pppd drop packets
as bogus when the port is set at 115Kbps. I only get it at that speed.
It causes stall outs etc.
works fine for me.
Jeff
-
To unsubscribe from this list: send the line
go to http://walbran.org/sean/linux/stodolsk/ and download the driver.
It's running on 2.4.2!
Jeff
On Fri, 23 Feb 2001, Trevor J. Clout wrote:
> Hi,
>
> I found you on this page
>http://www.appwatch.com/lists/linux-kernel/Week-of-Mon-20010115/017063.html
>
> How did you go getting a Lucent
go to http://walbran.org/sean/linux/stodolsk/ and download the driver.
It's running on 2.4.2!
Jeff
On Fri, 23 Feb 2001, Trevor J. Clout wrote:
Hi,
I found you on this page
http://www.appwatch.com/lists/linux-kernel/Week-of-Mon-20010115/017063.html
How did you go getting a Lucent
try to add the following to /etc/modules.conf ...
pre-install sg modprobe -k sr_mod
pre-install sr_mod modprobe -k ide-scsi
pre-install ide-scsi modprobe -k ide-cd
pre-install ide-cd modprobe -k ide-probe-mod
options ide-cd ignore="hdc"
... that's assuming you want to use hdc as the ide cdrw
try to add the following to /etc/modules.conf ...
pre-install sg modprobe -k sr_mod
pre-install sr_mod modprobe -k ide-scsi
pre-install ide-scsi modprobe -k ide-cd
pre-install ide-cd modprobe -k ide-probe-mod
options ide-cd ignore="hdc"
... that's assuming you want to use hdc as the ide cdrw
better off configure squid and use that as web cache.
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
- Original Message -
From: "Kevin Krieser" <[EMAIL PROTECTED]>
To: "Linux Kernel" <[EMAIL PROTECTED]>
Sent: Tuesday, January 30, 2001 8:24 AM
Subject: RE: Recommended swap for 2.4.x.
You mean my
better off configure squid and use that as web cache.
Thanks,
Jeff
[ [EMAIL PROTECTED] ]
- Original Message -
From: "Kevin Krieser" [EMAIL PROTECTED]
To: "Linux Kernel" [EMAIL PROTECTED]
Sent: Tuesday, January 30, 2001 8:24 AM
Subject: RE: Recommended swap for 2.4.x.
You mean my
r
Tested on IBM 240Z and it's running ok.
# cu -l ttyLT0
Connected.
ati
LT V.90 Data+Fax Modem Version 5.78
OK
Thanks,
Jeff.
Thanks,
Jeff Chua
[ [EMAIL PROTECTED] ]
On 15 Jan 2001, Alan Shutko wrote:
> [EMAIL PROTECTED] writes:
>
> > I haven't, and in fact keep a 2.2.14 kerne
Does anyone have any success in using Lucent winmodem under Linux 2.4.0?
There's a binary at http://www.linmodems.org/linux568.zip but it
only works under 2.2
Thanks,
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Does anyone have any success in using Lucent winmodem under Linux 2.4.0?
There's a binary at http://www.linmodems.org/linux568.zip but it
only works under 2.2
Thanks,
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
r
Tested on IBM 240Z and it's running ok.
# cu -l ttyLT0
Connected.
ati
LT V.90 Data+Fax Modem Version 5.78
OK
Thanks,
Jeff.
Thanks,
Jeff Chua
[ [EMAIL PROTECTED] ]
On 15 Jan 2001, Alan Shutko wrote:
[EMAIL PROTECTED] writes:
I haven't, and in fact keep a 2.2.14 kernel available (and in
,
Jeff Chua
[ [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/
,
Jeff Chua
[ [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/
,
Jeff Chua
[ [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/
,
Jeff Chua
[ [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/
from pcmcia-cs-3.1.22/PCMCIA-HOWTO
4.3.2. Comments about specific cards
o 16-bit PCMCIA cards have a maximum performance of 1.5-2 MB/sec.
That means that any 16-bit 100baseT card (i.e., any card that uses
the pcnet_cs, 3c574_cs, smc91c92_cs, or xirc2ps_cs driver) will
never
from pcmcia-cs-3.1.22/PCMCIA-HOWTO
4.3.2. Comments about specific cards
o 16-bit PCMCIA cards have a maximum performance of 1.5-2 MB/sec.
That means that any 16-bit 100baseT card (i.e., any card that uses
the pcnet_cs, 3c574_cs, smc91c92_cs, or xirc2ps_cs driver) will
never
Got problem booting on Celeron or when initrd filesystem>4MB.
Environment:
Linux 2.2.19pre3 or any 2.2.x
Linux 2.4.0-prerelease or any 2.4.x
Gcc 2.95.2
Glib 2.1.3
loadlin 1.6b
1) Pentium3
When the initrd ramdisk is greater than 4MB
Got problem booting on Celeron or when initrd filesystem>4MB.
Environment:
Linux 2.2.19pre3 or any 2.2.x
Linux 2.4.0-prerelease or any 2.4.x
Gcc 2.95.2
Glib 2.1.3
loadlin 1.6b
1) Pentium3
When the initrd ramdisk is greater than 4MB
Got problem booting on Celeron or when initrd filesystem4MB.
Environment:
Linux 2.2.19pre3 or any 2.2.x
Linux 2.4.0-prerelease or any 2.4.x
Gcc 2.95.2
Glib 2.1.3
loadlin 1.6b
1) Pentium3
When the initrd ramdisk is greater than 4MB
Got problem booting on Celeron or when initrd filesystem4MB.
Environment:
Linux 2.2.19pre3 or any 2.2.x
Linux 2.4.0-prerelease or any 2.4.x
Gcc 2.95.2
Glib 2.1.3
loadlin 1.6b
1) Pentium3
When the initrd ramdisk is greater than 4MB
MAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, November 20, 2000 11:21 AM
Subject: [PATCH,RFC] initrd vs. BLKFLSBUF
Hi Al,
Jeff Chua reported a while ago that BLKFLSBUF returns EBUSY on a RAM disk
that was obtained via initrd. I think the problem is that the effect of
the blkdev_ope
PROTECTED]
Sent: Monday, November 20, 2000 11:21 AM
Subject: [PATCH,RFC] initrd vs. BLKFLSBUF
Hi Al,
Jeff Chua reported a while ago that BLKFLSBUF returns EBUSY on a RAM disk
that was obtained via initrd. I think the problem is that the effect of
the blkdev_open(out_inode, ...) in dri
the only thing you've to be careful is to make sure you set
the correct options for the module (if you compiled it as module).
# options=0x30 100mbps full duplex
# options=0x20 100mbps half duplex
# options=0 10mbps half duplex
options eepro100 options=0
Otherwise, it'll cause a lot of
the only thing you've to be careful is to make sure you set
the correct options for the module (if you compiled it as module).
# options=0x30 100mbps full duplex
# options=0x20 100mbps half duplex
# options=0 10mbps half duplex
options eepro100 options=0
Otherwise, it'll cause a lot of
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
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
I got the following errors compiling the kernel 2.4.0-test12
mga_dma.c: In function `mga_irq_install':
mga_dma.c:821: structure has no member named `next'
make[3]: *** [mga_dma.o] Error 1
make[3]: Leaving directory `/u2/src/linux-2.4.0/drivers/char/drm'
i810_dma.c: In function
> Now, I also agree that we should be able to clean this up properly for
> 2.5.x, and actually do exactly this for the anonymous buffers, so that
> the VM no longer needs to worry about buffer knowledge, and fs/buffer.c
> becomes just another user of the writepage functionality. That is not
>
Now, I also agree that we should be able to clean this up properly for
2.5.x, and actually do exactly this for the anonymous buffers, so that
the VM no longer needs to worry about buffer knowledge, and fs/buffer.c
becomes just another user of the writepage functionality. That is not
all
I got the following errors compiling the kernel 2.4.0-test12
mga_dma.c: In function `mga_irq_install':
mga_dma.c:821: structure has no member named `next'
make[3]: *** [mga_dma.o] Error 1
make[3]: Leaving directory `/u2/src/linux-2.4.0/drivers/char/drm'
i810_dma.c: In function
Boot up using:
Loadlin-1.6a
Win98
ramdisk_size=18000
initrd=ram.gz (this is the gzip'ed root filesystem)
Kernel 2.2.x (up to 2.2.18)
- on P3 and Celeron
ram.gz must be <3862544 bytes
Kernel 2.4.x (up to 2.4.0-test12)
- on Celeron
ram.gz must be
Boot up using:
Loadlin-1.6a
Win98
ramdisk_size=18000
initrd=ram.gz (this is the gzip'ed root filesystem)
Kernel 2.2.x (up to 2.2.18)
- on P3 and Celeron
ram.gz must be 3862544 bytes
Kernel 2.4.x (up to 2.4.0-test12)
- on Celeron
ram.gz must be
ECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, November 20, 2000 11:21 AM
Subject: [PATCH,RFC] initrd vs. BLKFLSBUF
Hi Al,
Jeff Chua reported a while ago that BLKFLSBUF returns EBUSY on a RAM disk
that was obtained via initrd. I think the problem is that the e
ECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, November 20, 2000 11:21 AM
Subject: [PATCH,RFC] initrd vs. BLKFLSBUF
Hi Al,
Jeff Chua reported a while ago that BLKFLSBUF returns EBUSY on a RAM disk
that was obtained via initrd. I think the problem is that the e
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, November 20, 2000 11:21 AM
Subject: [PATCH,RFC] initrd vs. BLKFLSBUF
Hi Al,
Jeff Chua reported a while ago that BLKFLSBUF returns EBUSY on a RAM disk
that was obtained via initrd. I think the problem is that the effect of
the blkdev_open
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, November 20, 2000 11:21 AM
Subject: [PATCH,RFC] initrd vs. BLKFLSBUF
Hi Al,
Jeff Chua reported a while ago that BLKFLSBUF returns EBUSY on a RAM disk
that was obtained via initrd. I think the problem is that the effect of
the blkdev_open
>Is there support for using RAMDISK as the final root file system
>in 2.2.x versions, or is it there in the 2.4.x versions.
Works with 2.2x and up to 2.4.0 test12-pre3.bz2
Make sure you specify the following if you're using loadlin
root=/dev/ram
With anything above test12-pre3.bz2,
Is there support for using RAMDISK as the final root file system
in 2.2.x versions, or is it there in the 2.4.x versions.
Works with 2.2x and up to 2.4.0 test12-pre3.bz2
Make sure you specify the following if you're using loadlin
root=/dev/ram
With anything above test12-pre3.bz2,
AIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, November 20, 2000 11:21 AM
Subject: [PATCH,RFC] initrd vs. BLKFLSBUF
Hi Al,
Jeff Chua reported a while ago that BLKFLSBUF returns EBUSY on a RAM disk
that was obtain
PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, November 20, 2000 11:21 AM
Subject: [PATCH,RFC] initrd vs. BLKFLSBUF
Hi Al,
Jeff Chua reported a while ago that BLKFLSBUF returns EBUSY on a RAM disk
that was obtained via initrd. I think the problem is that
I'm posting this hoping that someone will fix this soon ...
On Sat, 28 Oct 2000, Jeff Chua wrote:
> freeram /dev/ram0
> File freeram.c: Line 41: ioctl /dev/ram0: Error 16: Device or resource
busy
this should not happen.
> I cannot free the old initrd root partition under 2.
I'm posting this hoping that someone will fix this soon ...
On Sat, 28 Oct 2000, Jeff Chua wrote:
freeram /dev/ram0
File freeram.c: Line 41: ioctl /dev/ram0: Error 16: Device or resource
busy
this should not happen.
I cannot free the old initrd root partition under 2.4.0-testx
401 - 480 of 480 matches
Mail list logo
