Most of the motherboard gives beep tone or light indication when POST
completes.
If there is no sign of life( no beep or even a led blink) then probably the
MoBo not even attempted POST.
I suggest to double check that all motherboard power connectors are
connected .
Usually 4pin or 8pin 12v mother
BeMyStreet devient gratuit pour les pros.
Nous avons une bonne nouvelle pour vous ! BeMyStreet devient gratuit pour les
professionnels pour votre plus grand plaisir. Alors ne vous en privez surtout
pas, vendez en ligne facilement et profitez de tous les avantages BeMyStreet :
***Visibil
One time I hooked up the power switch to the wrong jumpers and it took me an
hour to figure it out.
I would suggest double checking everything to make sure there's nothing you
missed. And as Felix already mentioned, parts can be dead on arrival so that is
the next thing I would look for.
--
S
Hi,
My system (kernel / mcelog) frequently (numerous times a day) spits out
warnings such as these:
Feb 20 21:10:07 lila kernel: [ 7808.093821] CPU1: Core temperature above
threshold, cpu clock throttled (total events = 1760)
Feb 20 21:10:07 lila kernel: [ 7808.093832] CPU0: Core temperature abo
On Sun, Feb 19, 2017 at 03:44:54PM -0800, pe...@easthope.ca wrote:
> * From: Dan Ritter
> > This is an input-only card, ...
>
> > Hardware has become much cheaper and more powerful ...
>
> > To see the kernel docs on supported devices, ...
>
> Thanks Dan. Will check PC Galore and eBay.
>
On Mon, Feb 20, 2017 at 04:07:48PM -0500, David Niklas wrote:
> What I'm trying to do is to avoid running pieces unstable or testing
> software (except for the package I asked for (such as nano)), while
> still having a few newer packages.
The best way to achieve this is to use backports, if one e
Leslie Rhorer wrote:
> [ 20.327836] bnx2x :07:00.0: firmware: failed to load
> [ bnx2x/bnx2x-e2-7.8.19.0.fw (-2) 20.327840] bnx2x :07:00.0: Direct
> [ firmware load failed with error -2 20.327842] bnx2x :07:00.0:
> [ Falling back to user helper 20.328247] bnx2x:
> [ [bnx2x_func_hw_init
Dennis Wicks composed on 2017-02-20 15:00 (UTC-0600):
I built myself another computer and it wouldn't boot up. No
messages or anything. I finally discovered that I missed
plugging in the 12V power to the MoBo.
I've done that many times while building, replacing or troubleshooting. You
can't hur
Hello,
I've used Debian on and off but now I have a pocketchip from
https://nextthing.co/
and it uses debian and I'm not about to switch.
I follow several projects closely (nano, lynx, a few others), and what I
want to do is to tell apt to:
1. Download the latest and greatest source code of version
I built myself another computer and it wouldn't boot up. No
messages or anything. I finally discovered that I missed
plugging in the 12V power to the MoBo. I did that and it
still won't boot up, and still no messages diaplayed on the
screen or any other indication of life.
Have I ruined my pr
On 2017-02-20 10:15:16 -0500, Greg Wooledge wrote:
> On Mon, Feb 20, 2017 at 04:02:50PM +0100, Vincent Lefevre wrote:
> > Note: since window managers can also start X clients on start up,
> > a .xsession file may not be useful for everyone.
>
> It's a crazy mixed-up world.
I'd say that it's bette
On 2017-02-20 10:15:16 -0500, Greg Wooledge wrote:
> On Mon, Feb 20, 2017 at 04:02:50PM +0100, Vincent Lefevre wrote:
> > More precisely, if I understand correctly,
> >
> > 1. The DM can request some window manager (for instance, the user has
> >the choice between several ones, and he may also
On 2017-02-20 08:34:23 -0500, Greg Wooledge wrote:
> If you need a home directory that will work consistently across different
> operating systems, then I *strongly* suggest you stick with startx and
> make .xinitrc a symlink to .xsession for backwards compatibility.
This what I did in the past, b
On Mon, Feb 20, 2017 at 04:02:50PM +0100, Vincent Lefevre wrote:
> More precisely, if I understand correctly,
>
> 1. The DM can request some window manager (for instance, the user has
>the choice between several ones, and he may also choose the default
>session file, or whatever has been u
On 2017-02-20 08:19:28 -0500, Greg Wooledge wrote:
> OK, short version: forget .xinitrc ever existed.
*And* make sure that you do not have a .xinitrc file, otherwise it
can break things (at least when logging in on a text console).
> Use ~/.xsession unless that doesn't work. See
> https://wiki.de
Greg Wooledge wrote:
> Debian's Xsession is not the same as Red Hat's.
>
> If you need a home directory that will work consistently across different
> operating systems, then I *strongly* suggest you stick with startx and
> make .xinitrc a symlink to .xsession for backwards compatibility. Any
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 20, 2017 at 01:13:09PM +, Rob Brewer wrote:
> to...@tuxteam.de wrote:
>
> >
> > On Mon, Feb 20, 2017 at 01:32:37PM +0100, Vincent Lefevre wrote:
> >> On 2017-02-20 12:49:34 +0100, to...@tuxteam.de wrote:
> >
> > [...blah...]
> >
> >
On Mon, Feb 20, 2017 at 01:13:09PM +, Rob Brewer wrote:
> Thank you for your explanations, I must admit that I didn't expect it to be
> so involved. I seem to remember mapping out the X startup processes a number
> of years ago but I was running RedHat then, so I suppose it has changed a
> l
to...@tuxteam.de wrote:
>
> On Mon, Feb 20, 2017 at 01:32:37PM +0100, Vincent Lefevre wrote:
>> On 2017-02-20 12:49:34 +0100, to...@tuxteam.de wrote:
>
> [...blah...]
>
>> > See man (5) Xsession and poke a bit through the scripts in
>> > /etc/X11/Xsession.d/, then have a look at /etc/X11/Xsessi
On Mon, Feb 20, 2017 at 01:32:37PM +0100, Vincent Lefevre wrote:
> I don't see any contradiction to what I've said. Note that I haven't
> mentioned .xsessionrc at all, only .xinitrc, which is a different
> thing.
OK, short version: forget .xinitrc ever existed. Use ~/.xsession unless
that doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 20, 2017 at 01:32:37PM +0100, Vincent Lefevre wrote:
> On 2017-02-20 12:49:34 +0100, to...@tuxteam.de wrote:
[...blah...]
> > See man (5) Xsession and poke a bit through the scripts in
> > /etc/X11/Xsession.d/, then have a look at /etc/X1
On 2017-02-20 12:49:34 +0100, to...@tuxteam.de wrote:
> On Mon, Feb 20, 2017 at 12:08:00PM +0100, Vincent Lefevre wrote:
> > On 2017-02-19 19:52:24 +, Brian wrote:
> > > On Sun 19 Feb 2017 at 11:00:25 +0100, Vincent Lefevre wrote:
> > >
> > > > On 2017-02-18 20:59:44 +, Brian wrote:
> > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 20, 2017 at 12:08:00PM +0100, Vincent Lefevre wrote:
> On 2017-02-19 19:52:24 +, Brian wrote:
> > On Sun 19 Feb 2017 at 11:00:25 +0100, Vincent Lefevre wrote:
> >
> > > On 2017-02-18 20:59:44 +, Brian wrote:
> > > > The advice in s
On 2017-02-19 19:52:24 +, Brian wrote:
> On Sun 19 Feb 2017 at 11:00:25 +0100, Vincent Lefevre wrote:
>
> > On 2017-02-18 20:59:44 +, Brian wrote:
> > > The advice in startx(1) is sound but nothing stops you using a ,xinitrc.
> > > The command doesn't work in a ,xinitrc? Perhaps it is inco
24 matches
Mail list logo
