On 15.07.2012 23:12, werner wrote:
> Even if rdev isn't often used, it should kept working, as it's included in
> many other programs, and principally in the installers.
rdev doesn't _exist_ anymore in current software,
including installers.
/mjt
--
To unsubscribe from this list: send the line
On 15.07.2012 23:12, werner wrote:
Even if rdev isn't often used, it should kept working, as it's included in
many other programs, and principally in the installers.
rdev doesn't _exist_ anymore in current software,
including installers.
/mjt
--
To unsubscribe from this list: send the line
On 12.07.2012 16:08, werner wrote:
> There is a big problem since 3.5-rc1 which potentially mess the installations
>
> rdev don't give longer back the root device like /dev/sda1 , but in the
> bios form like 0x80010300
Note rdev returns information which is written to
There is a big problem since 3.5-rc1 which potentially
mess the installations
rdev don't give longer back the root device like
/dev/sda1 , but in the bios form like 0x80010300
rdev is essential for the installation programs and for
the installation f.ex. of lilo . It's not conveniente
There is a big problem since 3.5-rc1 which potentially
mess the installations
rdev don't give longer back the root device like
/dev/sda1 , but in the bios form like 0x80010300
rdev is essential for the installation programs and for
the installation f.ex. of lilo . It's not conveniente
On 12.07.2012 16:08, werner wrote:
There is a big problem since 3.5-rc1 which potentially mess the installations
rdev don't give longer back the root device like /dev/sda1 , but in the
bios form like 0x80010300
Note rdev returns information which is written to kernel image
Hi everybody,
I have several questions about ioremap:
1) I have two 16 bit sram memory devices. To force it works I had to use
ioremap with memorysize*2, because
I was able to write to the 1 and 2 byte, 5,6, 9,10, 13,14 and so on.
Please explain why my ioremap space is non-continous,
how to
Hi everybody,
I have several questions about ioremap:
1) I have two 16 bit sram memory devices. To force it works I had to use
ioremap with memorysize*2, because
I was able to write to the 1 and 2 byte, 5,6, 9,10, 13,14 and so on.
Please explain why my ioremap space is non-continous,
how to
On Thu, Jun 28, 2001 at 05:35:14PM -0400, Ryan W. Maple wrote:
> Check out: http://bugs.debian.org/85478
>
> "When klogd's LogLine() function encounters a null byte in state
>PARSING_TEXT, it will loop infinitely. More precisely, copyin()
>will treat the null byte as a delimiter -
On Thu, 28 Jun 2001, Justin Guyett wrote:
> On Thu, 28 Jun 2001, Ralf Baechle wrote:
>
> > Some versions of the 3c59x driver emit a NUL character on bootup which makes
> > klogd suck CPU. This is fixed in 2.4.5, dunno about 2.4.4.
>
> sysklogd 1.4.1 changelog lists a no busyloop fix.
Check
On Thu, 28 Jun 2001, Ralf Baechle wrote:
> Some versions of the 3c59x driver emit a NUL character on bootup which makes
> klogd suck CPU. This is fixed in 2.4.5, dunno about 2.4.4.
sysklogd 1.4.1 changelog lists a no busyloop fix.
justin
-
To unsubscribe from this list: send the line
On Thu, Jun 28, 2001 at 06:49:46PM -, james bond wrote:
> 1-systeme hangs when i try ton compile anything
>
> i've compiled the kernel 2.4.4 , once i finish and boot the first time on
> 2.4.4 everything goses ok ,
> only too problemes
> 1st- klogd takes 100% CPU time
Some versions of
On Thu, 28 Jun 2001, Alan Cox wrote:
> > i've compiled the kernel 2.4.4 , once i finish and boot the first time on
> > 2.4.4 everything goses ok ,
> > only too problemes
> > 1st- klogd takes 100% CPU time
>
> Old old versions of klogd had bugs where they would do that. If there is
> a
> i've compiled the kernel 2.4.4 , once i finish and boot the first time on
> 2.4.4 everything goses ok ,
> only too problemes
> 1st- klogd takes 100% CPU time
Old old versions of klogd had bugs where they would do that. If there is
a continuous problem it may also do so - does 'dmesg' show
1-systeme hangs when i try ton compile anything
i've compiled the kernel 2.4.4 , once i finish and boot the first time on
2.4.4 everything goses ok ,
only too problemes
1st- klogd takes 100% CPU time
2nd- cat /proc/cpuinf --guives me too CPU'S without putin any info about
the CPU 1
like
1-systeme hangs when i try ton compile anything
i've compiled the kernel 2.4.4 , once i finish and boot the first time on
2.4.4 everything goses ok ,
only too problemes
1st- klogd takes 100% CPU time
2nd- cat /proc/cpuinf --guives me too CPU'S without putin any info about
the CPU 1
like
On Thu, 28 Jun 2001, Alan Cox wrote:
i've compiled the kernel 2.4.4 , once i finish and boot the first time on
2.4.4 everything goses ok ,
only too problemes
1st- klogd takes 100% CPU time
Old old versions of klogd had bugs where they would do that. If there is
a continuous
On Thu, Jun 28, 2001 at 06:49:46PM -, james bond wrote:
1-systeme hangs when i try ton compile anything
i've compiled the kernel 2.4.4 , once i finish and boot the first time on
2.4.4 everything goses ok ,
only too problemes
1st- klogd takes 100% CPU time
Some versions of the
On Thu, 28 Jun 2001, Ralf Baechle wrote:
Some versions of the 3c59x driver emit a NUL character on bootup which makes
klogd suck CPU. This is fixed in 2.4.5, dunno about 2.4.4.
sysklogd 1.4.1 changelog lists a no busyloop fix.
justin
-
To unsubscribe from this list: send the line
On Thu, 28 Jun 2001, Justin Guyett wrote:
On Thu, 28 Jun 2001, Ralf Baechle wrote:
Some versions of the 3c59x driver emit a NUL character on bootup which makes
klogd suck CPU. This is fixed in 2.4.5, dunno about 2.4.4.
sysklogd 1.4.1 changelog lists a no busyloop fix.
Check out:
On Thu, Jun 28, 2001 at 05:35:14PM -0400, Ryan W. Maple wrote:
Check out: http://bugs.debian.org/85478
When klogd's LogLine() function encounters a null byte in state
PARSING_TEXT, it will loop infinitely. More precisely, copyin()
will treat the null byte as a delimiter - unlike
i've compiled the kernel 2.4.4 , once i finish and boot the first time on
2.4.4 everything goses ok ,
only too problemes
1st- klogd takes 100% CPU time
Old old versions of klogd had bugs where they would do that. If there is
a continuous problem it may also do so - does 'dmesg' show
On Thu, 12 Oct 2000, Jeff Garzik wrote:
> "Richard B. Johnson" wrote:
> > --- linux-2.2.17/drivers/scsi/BusLogic.h.orig Thu Oct 12 11:22:44 2000
> > +++ linux-2.2.17/drivers/scsi/BusLogic.hThu Oct 12 11:47:07 2000
> > @@ -1509,6 +1509,7 @@
> > void
"Richard B. Johnson" wrote:
> --- linux-2.2.17/drivers/scsi/BusLogic.h.orig Thu Oct 12 11:22:44 2000
> +++ linux-2.2.17/drivers/scsi/BusLogic.hThu Oct 12 11:47:07 2000
> @@ -1509,6 +1509,7 @@
> void BusLogic_AcquireHostAdapterLock(BusLogic_HostAdapter_T *HostAdapter,
>
On Thu, 12 Oct 2000, Matthias Andree wrote:
> > Note that the sync-rate of target 6, the device I added, has been
> > turned down to try to eliminate any hardware problems. Also note
> > that the entire drive has been read/written with the BusLogic BIOS
> > diagnostic setup utility.
>
> That
> Note that the sync-rate of target 6, the device I added, has been
> turned down to try to eliminate any hardware problems. Also note
> that the entire drive has been read/written with the BusLogic BIOS
> diagnostic setup utility.
That BIOS setup tool might just use asynchronous I/O for
On Thu, 12 Oct 2000, Guest section DW wrote:
> On Wed, Oct 11, 2000 at 05:11:39PM -0400, Richard B. Johnson wrote:
>
> > Linux version 2.2.17
> > I tried to add a new Hard disk. It's s Seagate ST39102LW 8.1 Gb.
>
> Hmm. Your C/H/S multiplies out to 9.1 GB.
> On the other hand, Seagate
On Thu, 12 Oct 2000 00:24:51 +0200, Guest section DW blurted forth:
> On Wed, Oct 11, 2000 at 05:11:39PM -0400, Richard B. Johnson wrote:
>
> > In the BIOS setup of the BusLogic adapter, I was able to format
> > and verify the disk with no problems whatsoever.
> >
> > fdisk seemed to
On Thu, 12 Oct 2000 00:24:51 +0200, Guest section DW blurted forth:
On Wed, Oct 11, 2000 at 05:11:39PM -0400, Richard B. Johnson wrote:
In the BIOS setup of the BusLogic adapter, I was able to format
and verify the disk with no problems whatsoever.
fdisk seemed to work okay. I
On Thu, 12 Oct 2000, Guest section DW wrote:
On Wed, Oct 11, 2000 at 05:11:39PM -0400, Richard B. Johnson wrote:
Linux version 2.2.17
I tried to add a new Hard disk. It's s Seagate ST39102LW 8.1 Gb.
Hmm. Your C/H/S multiplies out to 9.1 GB.
On the other hand, Seagate ST39102LW has
Note that the sync-rate of target 6, the device I added, has been
turned down to try to eliminate any hardware problems. Also note
that the entire drive has been read/written with the BusLogic BIOS
diagnostic setup utility.
That BIOS setup tool might just use asynchronous I/O for anything,
On Thu, 12 Oct 2000, Matthias Andree wrote:
Note that the sync-rate of target 6, the device I added, has been
turned down to try to eliminate any hardware problems. Also note
that the entire drive has been read/written with the BusLogic BIOS
diagnostic setup utility.
That BIOS setup
"Richard B. Johnson" wrote:
--- linux-2.2.17/drivers/scsi/BusLogic.h.orig Thu Oct 12 11:22:44 2000
+++ linux-2.2.17/drivers/scsi/BusLogic.hThu Oct 12 11:47:07 2000
@@ -1509,6 +1509,7 @@
void BusLogic_AcquireHostAdapterLock(BusLogic_HostAdapter_T *HostAdapter,
On Thu, 12 Oct 2000, Jeff Garzik wrote:
"Richard B. Johnson" wrote:
--- linux-2.2.17/drivers/scsi/BusLogic.h.orig Thu Oct 12 11:22:44 2000
+++ linux-2.2.17/drivers/scsi/BusLogic.hThu Oct 12 11:47:07 2000
@@ -1509,6 +1509,7 @@
void
On Wed, Oct 11, 2000 at 05:11:39PM -0400, Richard B. Johnson wrote:
> Linux version 2.2.17
> I tried to add a new Hard disk. It's s Seagate ST39102LW 8.1 Gb.
Hmm. Your C/H/S multiplies out to 9.1 GB.
On the other hand, Seagate ST39102LW has 9105018880 bytes,
so probably the 8 was a typo (and
I tried to add a new Hard disk. It's s Seagate ST39102LW 8.1 Gb.
In the BIOS setup of the BusLogic adapter, I was able to format
and verify the disk with no problems whatsoever.
fdisk seemed to work okay. I made partitions.
mke2fs would fail (hang the system) while writing inodes.
The BusLogic
I tried to add a new Hard disk. It's s Seagate ST39102LW 8.1 Gb.
In the BIOS setup of the BusLogic adapter, I was able to format
and verify the disk with no problems whatsoever.
fdisk seemed to work okay. I made partitions.
mke2fs would fail (hang the system) while writing inodes.
The BusLogic
On Wed, Oct 11, 2000 at 05:11:39PM -0400, Richard B. Johnson wrote:
Linux version 2.2.17
I tried to add a new Hard disk. It's s Seagate ST39102LW 8.1 Gb.
Hmm. Your C/H/S multiplies out to 9.1 GB.
On the other hand, Seagate ST39102LW has 9105018880 bytes,
so probably the 8 was a typo (and you
38 matches
Mail list logo
