-core.c
{ "Samsung SSD 870*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
ATA_HORKAGE_ZERO_AFTER_TRIM |
ATA_HORKAGE_NO_NCQ_ON_ATI },
This fixed the disk corruption errors at the cost of dramatically
reducing performance. (I'm not sure why because manual fstrim didn't
impr
;
> { "Samsung SSD 870*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
> ATA_HORKAGE_ZERO_AFTER_TRIM |
> ATA_HORKAGE_NO_NCQ_ON_ATI },
>
> This fixed the disk corruption errors at the cost of dramatically
> reducing performance. (I'm not sure why because manual fs
>>> You should not be running trim in a container/virtual machine
>> Why not? That's, in my case, basically saying "you should not be running
>> trim on a drive exported via iscsi" Perhaps I shouldn't be but I'd like
>> to understand why. Enabling thin_provisioning and fstrim works and gets
>> mapp
On 2/26/24 16:31, Tim Woodall wrote:
On Mon, 26 Feb 2024, Gremlin wrote:
re running fstrim in a vm.
The Host system takes care of it
I guess you've no idea what iscsi is. Because this makes no sense at
all. systemd or no systemd. The physical disk doesn't have to be
something the host system
On Mon, 26 Feb 2024, Gremlin wrote:
re running fstrim in a vm.
The Host system takes care of it
I guess you've no idea what iscsi is. Because this makes no sense at
all. systemd or no systemd. The physical disk doesn't have to be
something the host system knows anything about.
Here's a threa
On 2/26/24 14:40, Tim Woodall wrote:
On Mon, 26 Feb 2024, Gremlin wrote:
Are you using systemd ?
No, I'm not
You should not be running trim in a container/virtual machine
Why not? That's, in my case, basically saying "you should not be running
trim on a drive exported via iscsi" Perhaps I
On Mon, 26 Feb 2024, Gremlin wrote:
Are you using systemd ?
No, I'm not
You should not be running trim in a container/virtual machine
Why not? That's, in my case, basically saying "you should not be running
trim on a drive exported via iscsi" Perhaps I shouldn't be but I'd like
to understan
ort
Feb 17 17:01:49 xen17 vmunix: [ 3.805074] ata1.00: disabling queued
TRIM support
from libata-core.c
{ "Samsung SSD 870*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
ATA_HORKAGE_ZERO_AFTER_TRIM |
ATA_HORKAGE_NO_NCQ_ON_ATI },
This fixed the disk corruption errors at the cost of
05074] ata1.00: disabling queued TRIM
support
from libata-core.c
{ "Samsung SSD 870*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
ATA_HORKAGE_ZERO_AFTER_TRIM |
ATA_HORKAGE_NO_NCQ_ON_ATI },
This fixed the disk corruption errors at the cost of dramatically
reducing performance. (I'
u (nounset), and/or -x (xtrace) options; or
their equivalents, if you are not using Bourne shell.
2. Add printf's to dump progress and debugging information to a file
while the script runs.
3. Add assertions to check for disk corruption, performance problems,
and any other else that concerns
On 1/21/24 05:46, Tim Woodall wrote:
The disk that I'm using when I saw the above error is a straight LVM ->
iscsi -> ext3 mounted like this:
/dev/xvdb on /mnt/mirror/ftp/mirror type ext3 (rw,noatime)
I should stay out of this, but feel compelled to ask why ext3?
It had a very short run, a l
On Sat, 20 Jan 2024, David Christensen wrote:
On 1/20/24 08:25, Tim Woodall wrote:
Some time ago I wrote about a data corruption issue. I've still not
managed to track it down ...
Please post a console session that demonstrates, or at least documents, the
data corruption.
Console session
On 1/20/24 08:25, Tim Woodall wrote:
> Some time ago I wrote about a data corruption issue. I've still not
> managed to track it down ...
Please post a console session that demonstrates, or at least documents,
the data corruption.
Please cut and paste complete console sessions into your posts
This is rather long - so if you're replying to just one bit, please
consider trimming the parts that you're not responding to to make
everybody's life a little bit better!
Some time ago I wrote about a data corruption issue. I've still not
managed to track it down but I have two new datapoints o
u running with DMA enabled?
>
> Some versions of the kernel have a bug with some IDE controllers
> that leads to severe disk corruption.
>
> If it's an IDE disk you probably want to turn off IDE DMA as
> early as possible in the boot process (I think it's "ide=nod
with some IDE controllers
that leads to severe disk corruption.
If it's an IDE disk you probably want to turn off IDE DMA as
early as possible in the boot process (I think it's "ide=nodma"
in the kernel boot command line).
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROT
On Fri, 8 Oct 2004 [EMAIL PROTECTED] wrote:
> The discussion concerning this thread tells me that my own
> understanding of the issues at play is far below that of certain other
> posters. However, I will humbly wonder aloud if the IDE cable is firmly
> seated in the connectors at both
On Thu, Oct 07, 2004 at 07:57:05AM -0700, [EMAIL PROTECTED] wrote:
>
> Whether or not this is related to debian is not clear, but it's possible.
>
> I've currently set fsck to run pretty much on every other boot.
>
> And just about every time it runs , it informs me that it fixed file
> system e
Alvin Oga wrote:
So this problem has a history. I had previously been seeing
corruption in the /dev directory and only the /dev directory.
get a clean /dev from a clean system ..
retoring /dev from a suspect corrupt system will only make things worst
1. the /dev directory seems to be somewhat d
hi ya brian
On Thu, 7 Oct 2004 [EMAIL PROTECTED] wrote:
> I have 1 IDE cable with nothing but 1 HD and 1 CDROM on it. I keep
> things simple to avoid exactly such problems.
take off the cdrom .. and i bet your problems will disappear
and new disk does not imply it's a gooouuudd drive..
you
> "Andrea" == Andrea Vettorello <[EMAIL PROTECTED]> writes:
Andrea> On Thu, 7 Oct 2004 09:43:36 -0700, [EMAIL PROTECTED]
Andrea> <[EMAIL PROTECTED]> wrote:
>> well that was silly. the fs is just ext2 2.6.8 kernel
>>
>> I haven't tried smartmontools. I will :-)
>>
Andrea> I'
On Thu, Oct 07, 2004 at 07:57:05AM -0700, [EMAIL PROTECTED] wrote:
> Whether or not this is related to debian is not clear, but it's possible.
>
> I've currently set fsck to run pretty much on every other boot.
>
> And just about every time it runs , it informs me that it fixed file
> system erro
> "Henrique" == Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
Henrique> On Thu, 07 Oct 2004, [EMAIL PROTECTED] wrote:
>> I've currently set fsck to run pretty much on every other boot.
Henrique> Install the memtest86+ package, activate it in lilo/grub,
Henrique> reboot.
H
On Thu, 7 Oct 2004 09:43:36 -0700, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> well that was silly.
> the fs is just ext2
> 2.6.8 kernel
>
> I haven't tried smartmontools. I will :-)
>
I've read at least two different claims of fs corruption with kernel
2.6.8-1 and reiserfs (i'm running b
> "Alvin" == Alvin Oga <[EMAIL PROTECTED]> writes:
Alvin> On Thu, 7 Oct 2004 [EMAIL PROTECTED] wrote:
>> I've currently set fsck to run pretty much on every other boot.
Alvin> why
because it likes to fail, so I figure something must be wrong, so I'm
running it more often.
Alvin> it
well that was silly.
the fs is just ext2
2.6.8 kernel
I haven't tried smartmontools. I will :-)
Brian
> "Andrea" == Andrea Vettorello <[EMAIL PROTECTED]> writes:
Andrea> On Thu, 7 Oct 2004 07:57:05 -0700, [EMAIL PROTECTED]
Andrea> <[EMAIL PROTECTED]> wrote:
>> Whether or not this
On Thu, 07 Oct 2004, [EMAIL PROTECTED] wrote:
> I've currently set fsck to run pretty much on every other boot.
Install the memtest86+ package, activate it in lilo/grub, reboot.
Let it test your main memory for at least 12h.
> 3. Could this be a bug in fsck ? Why doesn't fsck actually tell me
On Thu, 7 Oct 2004 [EMAIL PROTECTED] wrote:
> I've currently set fsck to run pretty much on every other boot.
why
it will figure it out for itself
> And just about every time it runs , it informs me that it fixed file
> system errors and reboots the system.
how do you shutdown ? ( exactly wh
On Thu, 7 Oct 2004 07:57:05 -0700, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Whether or not this is related to debian is not clear, but it's possible.
>
> I've currently set fsck to run pretty much on every other boot.
>
> And just about every time it runs , it informs me that it fixed fi
Whether or not this is related to debian is not clear, but it's possible.
I've currently set fsck to run pretty much on every other boot.
And just about every time it runs , it informs me that it fixed file
system errors and reboots the system.
However all other indicators of disk operation are
Hi,
I've just had a system crash (possibly a power glitch), and one of my
disks seems corrupted.
>From dmesg (or /var/log/syslog):
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 >
hde: hde1 hde2 hde3
hdf: hdf1 hdf2 hdf3 hdf4 < >
hdg: hdg1 hdg2
Jonathan Brandmeyer wrote:
> ...
> A detailed read of /usr/share/doc/lilo/Manual.txt reveales this telling
> entry:
> --quote--
> Two disks, Linux on second disk, first disk has no extended partition
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> If there is neither a
On Tue, 04 Feb 2003 03:20:07 +0100, "Jonathan Brandmeyer"
<[EMAIL PROTECTED]> wrote:
snip
>What if I am going about this the wrong way? Suppose that MBR(s)
is/are
>damaged? Will fsck(8) detect this type of damage? My reading of the
man
>page says that it doesn't.
>
>Thanks,
>Jonathan
ASFAIK .
On Tue, 2003-02-04 at 21:00, Anita Lewis wrote:
--snip--
> I still think you could just put boot=/dev/hda in
> lilo.conf and run it happily. If windows will boot with other=/dev/hda1
> using the floppy, then I see no reason why you could not install it LILO
> into the mbr of that first drive. Hav
--- Jonathan Brandmeyer <[EMAIL PROTECTED]>
wrote: > And permanantly broken.
>
> A detailed read of /usr/share/doc/lilo/Manual.txt
> reveales this telling
> entry:
> --quote--
> Two disks, Linux on second disk, first disk has no
> extended partition
> - - - - - - - - - - - - - - - - - - - - - - -
And permanantly broken.
A detailed read of /usr/share/doc/lilo/Manual.txt reveales this telling
entry:
--quote--
Two disks, Linux on second disk, first disk has no extended partition
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If there is neither a Linux partition nor an
On Tue, Feb 04, 2003 at 06:30:05PM -0500, Jonathan Brandmeyer wrote:
> /boot/boot-menu.b: no such file or directory. Hmm...
> >
> > +
> > I have other things under that, and when I boot, I get a red menu with the
> > list to choose from. It waits a while and then goes off to l
On Tue, 2003-02-04 at 17:40, Anita Lewis wrote:
> Ok, that's a step in the right direction. We know that the lilo.conf is
> working. If you hit TAB during the LILO startup before it goes off into
> Linux, You will probably see windows as a choice and you could type that in
> and go to xp.
>
On Tue, Feb 04, 2003 at 05:02:23PM -0500, Jonathan Brandmeyer wrote:
> >
> > boot=/dev/fd0
> >
> > in place of boot=/dev/hda
>
> Actually, I have been using /dev/hdb1 without problems until recently.
>
> > Then put a floppy in and run /sbin/lilo. Leave the floppy in and boot.
> If
> > that works
- Original Message -
From:
>
> I'm thinking there is another way to make sure that you are using the LILO
> that is getting written. Try writing it to a floppy. Edit /etc/lilo.conf
and
> put
>
> boot=/dev/fd0
>
> in place of boot=/dev/hda
Actually, I have been using /dev/hdb1 without p
Jonathan Brandmeyer said:
>
> Done. I should have recognized the size discrepancy. My new partitions for
> hdb4 and hdb5 are:
> /dev/hdb43922 - 7299type5Extended
> /dev/hdb53922 - 4180type83Linux (unformatted)
>
> Also re-ran Lilo, and this did not solve the problem. As t
- Original Message -
From: <[EMAIL PROTECTED]>
> /dev/hdb1*162497983+ 83Linux
> /dev/hdb26386996030 82 Linux swap
> /dev/hdb3 187392130001387+83 Linux
> /dev/hdb439224164 1951897+
Jonathan Brandmeyer said:
> The drive is 60GB. You are saying that the extended partition should
> consume all of the space that may be parceled out as logical partitions,
> Right? I am going to try it and see.
>
> Thanks,
> Jonathan
Yes, if you do not have the extended consume all the remaining
Jonathan Brandmeyer said:
> The drive is 60GB. You are saying that the extended partition should
> consume all of the space that may be parceled out as logical partitions,
> Right? I am going to try it and see.
>
> Thanks,
> Jonathan
Yes, if you do not have the extended consume all the remaining
ent: Tuesday, February 04, 2003 10:31 AM
Subject: Re: Disk Corruption
> Quoted -
> Here is the information from fdisk -l
> device boot Start EndBlocks IDSystem
> /dev/hda1*1243419551073+ 7HPFS/NTFS
>
> /de
Quoted -
Here is the information from fdisk -l
device boot Start EndBlocks IDSystem
/dev/hda1*1243419551073+ 7HPFS/NTFS
/dev/hdb1*162497983+ 83Linux
/dev/hdb2638699603
Here is my lilo.conf (comments omitted) if it helps. This configuration has
not changed in a while, and it used to work fine. I don't think that the
problem is in here but...
lba32
boot=/dev/hdb1
root=/dev/hdb1
compact
install=/boot/boot.b
delay=20
map=/boot/map
vga=normal
image=/vmlinuz
lab
ajlewis wrote:
> If you cannot get mounted on anything and can't find a partition table
with
> 'fdisk /dev/hdb' then you might want to try gpart or rescuept for finding
> the partition info and then rewriting the table with fdisk.
--snip--
> Forget this! I was thinking of booting with a rescue di
On Mon, Feb 03, 2003 at 06:30:39AM -0500, Jonathan Brandmeyer wrote:
> > if you can see all the directories and mount all your partitions
>
> > from an emergency boot disk, try re-running lilo and booting
>
> > again.
>
> No luck. I re-ran LILO this morning, and nothing changed.
>
> Any other
"I would first try booting from the emergency boot floppy. See if you can
access any of the partitions. If you can, then you still have a partition
table there. In that case, I would try running fsck on the / partition -
when it is NOT mounted."
Forget this! I was thinking of booting with a re
In linux.debian.user, you wrote:
> Something VERY BAD has happened. When I attempted to format the disk, with
> mkfs.ext3, it reported that the partition table for that partition said 0
> size, and I should reboot the computer to re-read the partion table. When I
> rebooted, instead of LILO, I sa
Jonathan Brandmeyer wrote:
> dmesg shows this interesting entry:
> Partition check:
> hda: hda1
> hdb: hdb1 hdb2 hdb3 hdb4
>
> and the view in cfdisk is:
> Size: 60040544256 bytes
> hdb1BootPrimaryLinux ext2509.97
> hdb2PrimaryLinux swap1019.94
>
> if you can see all the directories and mount all your partitions
> from an emergency boot disk, try re-running lilo and booting
> again.
No luck. I re-ran LILO this morning, and nothing changed.
Any other ideas?
Jonathan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
Jonathan Brandmeyer said:
> What if hdb4 is actually a primary partition that I cannot see? This
> would violate the partitioning rules, wouldn't it?
hdb4 should be an extended partition. an extended partition is
required to support logical drives.
using normal fdisk should show more results.
heya,
just an idea,
if you can see all the directories and mount all your partitions
from an emergency boot disk, try re-running lilo and booting
again.
hth
sean
On Sun, Feb 02, 2003 at 11:45:13PM -0500, Jonathan Brandmeyer wrote:
> > Something VERY BAD has happened. When I attempted
> Something VERY BAD has happened. When I attempted to format the disk,
with
> mkfs.ext3, it reported that the partition table for that partition said 0
> size, and I should reboot the computer to re-read the partion table. When
I
> rebooted, instead of LILO, I saw an endless stream of "01 " repe
Jonathan Brandmeyer said:
> Something VERY BAD has happened. When I attempted to format the disk,
> with mkfs.ext3, it reported that the partition table for that partition
> said 0 size, and I should reboot the computer to re-read the partion
> table. When I rebooted, instead of LILO, I saw an en
Something VERY BAD has happened. When I attempted to format the disk, with
mkfs.ext3, it reported that the partition table for that partition said 0
size, and I should reboot the computer to re-read the partion table. When I
rebooted, instead of LILO, I saw an endless stream of "01 " repeating
wi
Hello
WARNING : don't follow thread, perhaps out of subject.
briefly, I've got same chipset, excepted a "spurious" message at boot, have
no problems, 48Mo/s with DMA on ata5 'if remember fine) on HD and good rate
on (RW-)CD's.
Running 2.4.20 but 2.4.18 fine (customs kernel)
Hop'it'elp
David Du
Pigeon wrote:
On Sun, Jan 19, 2003 at 05:53:54PM -0700, Al Davis wrote:
I have since installed Debian, with 2.4.20-bf2.4, and now I
wonder if it is safe to re-enable DMA.
I have a VIA 82C686 southbridge, and 2.4.20 enables its "VIA
southbridge workaround" when it boots. So presumably the pr
Pigeon said:
> I think there are a lot of VIA chipsets out there but most people
> don't have problems; presumably some other factor is needed to make the
> bug show up. Wonder what?
not entirely related but thought to mention ..
about a year and a half ago I was looking for a MB to get an Athlo
On Sun, Jan 19, 2003 at 05:53:54PM -0700, Al Davis wrote:
> I was getting disk corruption with an older kernel (2.4.8 or
> 2.4.18, Mandrake). A colleague said it might have something
> to do with a hardware bug (south bridge VIA VT82C686). He also
> said there was a fix in recent
in Ausus and it ran like a champ.
Daniel Barclay wrote:
Pigeon wrote:
On Sat, Jan 18, 2003 at 11:27:28AM -0500, Daniel Barclay wrote:
I'm getting disk corruption if I try to enable DMA mode for my IDE
disks.
...
If you have a VIA chipset try making sure that VIA chipset suppo
Ron Johnson wrote:
>
> On Sun, 2003-01-19 at 15:48, Bob Proulx wrote:
> > ...
> ...
> But the A7M266-D doesn't use a Via chipset.
> >From http://usa.asus.com/mb/socketa/a7m266-d/overview.htm :
> "The A7M266-D leverages the technology of the AMD 760MPX chipset"
>
> A quick google, and the *first*
Pigeon wrote:
>
> On Sat, Jan 18, 2003 at 11:27:28AM -0500, Daniel Barclay wrote:
> > I'm getting disk corruption if I try to enable DMA mode for my IDE
> > disks.
...
> If you have a VIA chipset try making sure that VIA chipset support is
> included in the kerne
On Sun, 2003-01-19 at 15:48, Bob Proulx wrote:
> Wayne Topa wrote:
> > Al Davis([EMAIL PROTECTED]) is reported to have said:
> > > How do I find out?
> > > I am using the one on the woody bf2.4 cd.
> >
> > lspci will show if you have VIA and
> >
> > grep VIA /usr/src/linux/.config will show if yo
On Sun, 2003-01-19 at 15:43, Bob Proulx wrote:
> Ron Johnson wrote:
> > Well, 1st, do you know which chipset the A7V266-D runs?
> > Btw, the ASUS web site only mentions the A7V266-C.
> > http://usa.asus.com/mb/socketa/a7v266-c/overview.htm
>
> Try this url for the dual model. (D is for dual.)
>
On Sun, Jan 19, 2003 at 03:10:23PM -0600, Ron Johnson wrote:
> On Sun, 2003-01-19 at 13:42, Al Davis wrote:
> > > On Sat, Jan 18, 2003 at 11:27:28AM -0500, Daniel Barclay
> > wrote:
> > > > I'm getting disk corruption if I try to enable DMA mode for
> >
boot/config-2.4.18-bf2.4
> CONFIG_BLK_DEV_VIA82CXXX=y
> CONFIG_VIA_RHINE=m
> CONFIG_AGP_VIA=y
> CONFIG_SOUND_VIA82CXXX=m
Thanks. That is what I was looking for.
My real reason for asking ...
I was getting disk corruption with an older kernel (2.4.8 or
2.4.18, Mandrake). A colleague said it might h
Wayne Topa wrote:
> Al Davis([EMAIL PROTECTED]) is reported to have said:
> > How do I find out?
> > I am using the one on the woody bf2.4 cd.
>
> lspci will show if you have VIA and
>
> grep VIA /usr/src/linux/.config will show if you have enabled it.
If you are using the bf24 kernel then the c
Ron Johnson wrote:
> Well, 1st, do you know which chipset the A7V266-D runs?
> Btw, the ASUS web site only mentions the A7V266-C.
> http://usa.asus.com/mb/socketa/a7v266-c/overview.htm
Try this url for the dual model. (D is for dual.)
http://usa.asus.com/mb/socketa/a7m266-d/overview.htm
Bob
Al Davis([EMAIL PROTECTED]) is reported to have said:
>
> > On Sat, Jan 18, 2003 at 11:27:28AM -0500, Daniel Barclay
> wrote:
> > > I'm getting disk corruption if I try to enable DMA mode for
> > > my IDE disks.
>
> On Saturday 18 January 2003 04:1
Al Davis wrote:
On Sat, Jan 18, 2003 at 11:27:28AM -0500, Daniel Barclay
wrote:
I'm getting disk corruption if I try to enable DMA mode for
my IDE disks.
On Saturday 18 January 2003 04:14 pm, Pigeon wrote:
If you have a VIA chipset try making sure that VIA chipset
support is includ
On Sun, 2003-01-19 at 13:42, Al Davis wrote:
> > On Sat, Jan 18, 2003 at 11:27:28AM -0500, Daniel Barclay
> wrote:
> > > I'm getting disk corruption if I try to enable DMA mode for
> > > my IDE disks.
>
> On Saturday 18 January 2003 04:14 pm, Pigeon wr
> On Sat, Jan 18, 2003 at 11:27:28AM -0500, Daniel Barclay
wrote:
> > I'm getting disk corruption if I try to enable DMA mode for
> > my IDE disks.
On Saturday 18 January 2003 04:14 pm, Pigeon wrote:
> If you have a VIA chipset try making sure that VIA chipset
>
On Sat, Jan 18, 2003 at 11:27:28AM -0500, Daniel Barclay wrote:
> I'm getting disk corruption if I try to enable DMA mode for my IDE
> disks.
>
> I get mesages like:
> hdc: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func. only: 14
>
I'm getting disk corruption if I try to enable DMA mode for my IDE
disks.
I get mesages like:
hdc: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func. only: 14
hdc: status error: status=0x58 { DriveReady, SeekComplete, DataRequest }
hdc: drive not read
#include
* nate [Thu, Jan 16 2003, 10:53:16AM]:
> the problem is probably easier resolved by using another IDE controller,
> I highly reccomend the Promise ATA/100 and ATA/66 series(have not tried
> the ATA/133). DMA problems are most often caused by buggy IDE controllers
SO GO AND TRY before yo
ere are a number of messages on the Linux kernel mailing list about
IDE disk corruption, and there a number of patches for various versions
of the 2.4.1x kernel, but it's not clear which patches fixes known
problems vs. which try to add new functionality to the otherwise-stable
2.4 kernel series.
D
Daniel Barclay said:
>
> I've been having a heck of a time with repeated IDE disk corruption when I
> try to enable DMA mode, and with trying to figure out which versions of
> the stable (2.4) kernel actually are stable.
>
> What is the recommended combination of base kernel
I've been having a heck of a time with repeated IDE disk corruption
when I try to enable DMA mode, and with trying to figure out which
versions of the stable (2.4) kernel actually are stable.
What is the recommended combination of base kernel versions and
patches to avoid IDE disk corruptio
On Sun, 2002-06-16 at 02:02, Jerome Lacoste wrote:
> I also had to modify /
I had to modify /etc/gdm/sessions/Gnome
to remove the gnome-session parameter --purge-delay=15000
This may have had an importance, but that was the only way I could get
gnome to work from gdm. Perhaps if there an upgra
Hi all,
I had a hang while doing an upgrade. I think it was during the upgrade
of the pcmcia-cs pacjage.
Note: the only pcmcia card I have is a Schlumberger smart card reader
unsupported under Linux).
Unfortuntely after the hard reset I was obliged to do, I ended up having
big troubles with my ex
Hello,
I've installed Debianalready twice and then got clue, how to organize big
disk (10 G) with windows and Debian.
Installed debian with altered geometry at boot (linux hda=4912,63,64) like
is written in debian FAQ.
But then accidentally debian was newly booted without this parameters. When
I
84 matches
Mail list logo
