Am Samstag, den 22.08.2009, 21:48 -0400 schrieb Isaac Freeman:
> [x-posted to debian-am...@lists.debian.org,
> debian-b...@lists.debian.org, debian-u...@lists.debian.org]
>
> All, sorry for the wide distribution, but I wasn't sure which list
> this belonged on; feel free to reply only to me, or to
Andrew Reid wrote:
On Sunday 23 March 2008 01:57, Freddy Freeloader wrote:
I assume I'm running into problems with udev not naming
the devices consistently but am not quite sure of my diagnosis or how to
fix it if that is the problem.
I don't think udev rules will fix it, since the
On Sunday 23 March 2008 01:57, Freddy Freeloader wrote:
> I assume I'm running into problems with udev not naming
> the devices consistently but am not quite sure of my diagnosis or how to
> fix it if that is the problem.
I don't think udev rules will fix it, since the udev rules
are on the ro
On Sun, Mar 23, 2008 at 05:14:44PM -0700, Freddy Freeloader wrote:
> Douglas A. Tutty wrote:
> >On Sat, Mar 22, 2008 at 10:57:30PM -0700, Freddy Freeloader wrote:
> >
> >>I'm building a server based on an Asus M2N-LR mobo, a 3Ware 9550SXU RAID
> >>card, 8 gigs of ram and a dual core Opteron. Th
Douglas A. Tutty wrote:
On Sat, Mar 22, 2008 at 10:57:30PM -0700, Freddy Freeloader wrote:
I'm building a server based on an Asus M2N-LR mobo, a 3Ware 9550SXU RAID
card, 8 gigs of ram and a dual core Opteron. The hard drives are all
sata Raptors with 4 of the 5 drives in a RAID 10 array. I
On Sat, Mar 22, 2008 at 10:57:30PM -0700, Freddy Freeloader wrote:
> I'm building a server based on an Asus M2N-LR mobo, a 3Ware 9550SXU RAID
> card, 8 gigs of ram and a dual core Opteron. The hard drives are all
> sata Raptors with 4 of the 5 drives in a RAID 10 array. I'm running Etch.
>
> T
Douglas A. Tutty wrote:
snip
Note that I run an Athlon64 3800+ with one 1 GB stick. Runs just fine.
4GB is not a "minimum size"
There are a lot of CPUs around now that people are installing into
things like personal PCs and word processor/spreadsheet work stations
that will operate just fin
On Thu, Nov 29, 2007 at 07:23:24PM +0900, David wrote:
> I.E.Broadbent wrote:
> >AN UPDATE:
> >
> >Especially to Thierry, Dave, Doug, ... some further news I have
> >just had a note from the chap that supplies my bits'n'bobs
> >(BTW ...anybody know of a reliable UK wholesaler of medium quantit
I.E.Broadbent wrote:
AN UPDATE:
Especially to Thierry, Dave, Doug, ... some further news I have
just had a note from the chap that supplies my bits'n'bobs
(BTW ...anybody know of a reliable UK wholesaler of medium quantities
for DRAM/Processors/hardware/etc?) ... he has spotted (must get
AN UPDATE:
Especially to Thierry, Dave, Doug, ... some further news I have
just had a note from the chap that supplies my bits'n'bobs
(BTW ...anybody know of a reliable UK wholesaler of medium quantities
for DRAM/Processors/hardware/etc?) ... he has spotted (must get myself
a new pair of sp
On Thu, 2007-11-29 at 08:29 +0900, David wrote:
> Thierry Chatelet wrote:
> > On Wednesday 28 November 2007 22:24, I.E.Broadbent wrote:
> >> Anyone have any comments or suggestions please.
> >>
> >> Anyone heard of any problems with the CPU's or Boards mentioned above?
> >>
> >> Thanks, Ian
> >
>
On Wed, Nov 28, 2007 at 09:24:49PM +, I.E.Broadbent wrote:
> I built two boxes last week...
> both (almost) identical
> CPU - Both AMD Socket-AM2 64bit Dual Core (one 4300 and one 4600)
> Memory - both identical - 4 x 1gig modules per motherboard
> Motherboard - both identical - Gigabyte S-
Thierry Chatelet wrote:
On Wednesday 28 November 2007 22:24, I.E.Broadbent wrote:
Anyone have any comments or suggestions please.
Anyone heard of any problems with the CPU's or Boards mentioned above?
Thanks, Ian
Hi, I got a similar problem, which was soulve by increasing the voltage on the
On Wednesday 28 November 2007 22:24, I.E.Broadbent wrote:
> Anyone have any comments or suggestions please.
>
> Anyone heard of any problems with the CPU's or Boards mentioned above?
>
> Thanks, Ian
Hi, I got a similar problem, which was soulve by increasing the voltage on the
memories sticks. No
On Dec 28, 9:00 am, "Jaume Alonso" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm a Debian testing user. A few days ago I recompiled the kernel (2.6.18)
> and I installed it in the "Debian way" (by creating a .deb package of the
> kernel and installing it). But I've got a problem: when I boot the sy
Try to run as root:
# update-modules
and see if it goes away!
Cassiano Leal
Marko Randjelovic wrote:
Jaume Alonso wrote:
Hello,
I'm a Debian testing user. A few days ago I recompiled the kernel
(2.6.18) and I installed it in the "Debian way" (by creating a .deb
package of the kernel and i
Jaume Alonso wrote:
Hello,
I'm a Debian testing user. A few days ago I recompiled the kernel
(2.6.18) and I installed it in the "Debian way" (by creating a .deb
package of the kernel and installing it). But I've got a problem: when
I boot the system with the new kernel, appears a lot of times
IL PROTECTED]>
> Date: 8-set-2005 19.45
> Subject: Re: Problems booting kernel-image-2.6.8-2-k7
> To: Alessandro Di Rubbo <[EMAIL PROTECTED]>
>
>
> 2005/9/8, Alessandro Di Rubbo <[EMAIL PROTECTED]>:
> > If I boot the system using kernel 2.6, after the mes
On Wed, 24 Dec 2003 01:04:17 -0600, Grant Bierman wrote:
> After re-installing debian via knoppix on my parents computer, and
> dist-updating. I installed grub again and at the time thought it was all
> configured right.
>
>
> But when it once re-started after the storm pass through the other n
> "Alberto" == Alberto Cabello Sanchez <[EMAIL PROTECTED]> writes:
Alberto> I just installed potato r3 on P75, 16 MB RAM and all worked
Alberto> fine. But booting from hard drive seems impossible to me.
I suspect a hardware problem. Try running `badblocks /dev/hda'
--
G. ``Iggy'' Geens - IC
Problem was solved yesterday with installation of GRUB as bootloader, so it
remains only as something rare, but not critical. I will continue investigating
a bit more.
Lilo output is normal, I think:
[EMAIL PROTECTED]:~# lilo
Added Linux *
[EMAIL PROTECTED]:~#
My lilo.conf reads (yes, it is a ha
> I just installed potato r3 on P75, 16 MB RAM and all worked fine.
> But booting from hard drive seems impossible to me. I have lilo
> well config, and it boots well from floppy, but I always get
> an error among this ones when booting from hard drive:
> * "crc error".
> * "Out of memory".
>
At 10:20 AM 1/13/01 -0500, you wrote:
Linux boots no problems as usual. NT does not.
When I boot NT I get a Blue screen of death with the error message
c135 and that winsrv.dll cannot find a DLL it needs.
Upon furthur investigation I have determined that somehow the second
NTFS partition is g
On Mon, 3 Mar 1997, Dale Scheetz wrote:
> On Tue, 25 Feb 1997, Karl Sackett wrote:
>
> > I've been trying to upgrade my kernel using kernel-source-2.0.27. I
> > put the new kernel on a floppy, boot from the floppy, and instead of
> > loading the new kernel I get this on my display:
> >
> > Lo
On Tue, 25 Feb 1997, Karl Sackett wrote:
> I've been trying to upgrade my kernel using kernel-source-2.0.27. I
> put the new kernel on a floppy, boot from the floppy, and instead of
> loading the new kernel I get this on my display:
>
> Loading..
>
> 8000
> AX: 02FF
> BX:
> CX: 000B
> DX:
Actually it looks like your root device isn't set up properly .. are you
using a boot disk .. if you are check out the rdev command it enables you
to set your root partition. If it is not set correctly then you will get
the following error.
Michael
>
> Hi,
>
> > VFS: Cannot open root devic
Hi,
> VFS: Cannot open root device 03:02
your IDE driver is missing or can't find the disk. Is there any lines about
IDE disks on the screen?
Greetings
Bernd
27 matches
Mail list logo
