Date: Thu, 29 Nov 2007 08:59:05 +0000
From: "I.E.Broadbent" <ieb@klokwurx.co.uk>
To: debian-user <debian-user@lists.debian.org>
Subject: Re: Problems booting AMD64 Dual Core
Message-Id: <1196326755.6291.37.camel@SmartStuf-Dev1>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
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 specs or even learn to read... I looked on gigabytes site
but I misseed this) that Patriot modules (which is what we have used for
this) are not listed as being tested/approved by gigabyte. It could be
that they are drawing too much current and that would explain the
stuttering, and also why when Thierry upped the power it worked. (You
might not have used Patriot chips Thierry...but it could be that they
too were out of recommended bounds for power needs.)
I'm going to get the Patriot units swapped for 4 'listed' modules and
see what happens then.... will update the list with the results... but
if this is the root then others may want to take note that the Gigabyte
board/set-up seems to be power-critical (sensitive) if all slots are
populated.
Ian
...........................
On Thu, 2007-11-29 at 08:13 +0000, I.E.Broadbent wrote:
> 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
> > >
> > > Hi, I got a similar problem, which was soulve by increasing the voltage on the
> > > memories sticks. No idea if it can help, sorry, but it's worth a try.
> > > Thierry
> > >
> > >
> > I'm currently building a similar box, so this is topical.
> >
> > If you are running identical boxes, with identical installs, and you
> > only have trouble on one, it's a fault in one lot of hardware or in a
> > config difference.
> >
> > You are running what I would consider the bare minimum of ram for a 64
> > box, but if you have one box running ok on that, that's not the problem
> > either.
> >
> > I'm not familiar with the board - I'm building with an Asus one with a
> > 6000 AMD CPU, but Gigabyte make good boards and that shouldn't be the
> > problem either.(Did anybody have access to the build area and pick
> > things up "just for a look?" - even doing this to a ram chip could be
> > enough).
>
> No, ...just me.... and I've swapped over modules from another (running
> properly) machine to check and it's the same... it's a real swine this
> one....
> I'm intrigued that you consider 4 gig to be the minimum setup for such a
> setup... having read this I then took two modules from the 'running' box
> to see how it would fair... and although it was noticeable it wasn't
> demonstrating the 'stuttering' of the other.... so I am fairly confident
> that it's not the fact that 4 gig isn't enough... one of the issues
> seems to be unrelated to the volume of RAM (certainly between 2 and 4
> gig-worth)... It's the fact that the damned thing won't boot at all with
> 4 slots populated (with any size of RAM).
>
> I'm going to try tweaking the voltage as suggested by Thierry and see
> what happens (knowing my luck of late I'll probably fry the blasted
> things.)
>
>
> Ian
>
>
> > Regards,
> >
> > David.
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
Date: Thu, 29 Nov 2007 14:25:31 +0530
From: "Sridhar M.A." <mas@mylug.org>
To: Debian Users <debian-user@lists.debian.org>
Subject: Font size under X
Message-ID: <20071129085531.GA7628@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
I am facing a peculiar problem. Currently am running debian unstable.
The fonts under X are too small. I can get around this problem by
playing with the dpi setting under gnome, but I feel that is not the
correct way of doing it.
What surprises me is that of the 4 machines I am using (all debian sid),
only two exhibit this problem. Both of those machines have a CRT monitor
while the other two have an LCD monitor.
Searched for any similar bug reports and found none. Does anyone have
any pointers to this problem?
Regards,
--
Sridhar M.A.
Landru! Guide us!
-- A Beta 3-oid, "The Return of the Archons", stardate 3157.4
Date: Thu, 29 Nov 2007 17:09:39 +0700
From: Klein Moebius <klein.moebius@gmail.com>
To: debian-user@lists.debian.org
Subject: How to get colors and spinners in boot messages?
Message-ID: <20071129100939.GA3747@klein.moebius.net>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN"
Content-Disposition: inline
--J/dobhs11T7y2rNN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
OK, here goes. I would really like to be able to modify my bootup
messages to have some color, similar to what a Knoppix boot does. Maybe
not as garish, something to my taste.
I've looked at bootsplashes, but they tend to be bulky and usually ugly
in execution. The bootsplash package requires a kernel patch and
initrd, and I'm limited to initramfs by certain other restrictions.
So: How do I modify boot console to add color and stuff?
Regards,
Klein
--J/dobhs11T7y2rNN
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTo/jd43JlErxgiQRAu10AJ9mM6BYacTobMUFKzdcv2tWUqmmRwCgjI4m
l/tJ7GMx1KV7fFyBblVSj/k=
=awsG
-----END PGP SIGNATURE-----
--J/dobhs11T7y2rNN--
Date: Thu, 29 Nov 2007 10:33:00 +0100
From: Romain JACQUET <romain.jacquet.dev@free.fr>
To: debian-user@lists.debian.org
Subject: aptitude failed to install fglrx-driver on unstable
Message-ID: <474E874C.3060706@free.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
When I try a "aptitude install fglrx-driver", aptitude claims that there
is no candidate version!
aptitude install fglrx-driver
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
No candidate version found for fglrx-driver
No candidate version found for fglrx-driver
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
aptitude why fglrx-driver
No justification for fglrx-driver could be constructed.
aptitude show fglrx-driver|grep Version
Version: 8.43.2-1
I really do not understand. Any solutions to install fglrx-driver?
Thanks in advance.
Date: Thu, 29 Nov 2007 11:11:39 +0100
From: Miro Dietiker <miro.dietiker.maillist@md-systems.ch>
To: debian-user@lists.debian.org
Subject: apache2 freezes @sarge
Message-ID: <474E905B.5050508@md-systems.ch>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Hi list
I trapped into an apache2 freeze thing (debian sarge, apache2
libapache2-mod-php4)
After certain time (from few minutes to many hours) apache simply freezes.
Freeze meaning here: Processes still present but no processing time on
them. Each request is not responded but queued (showing status bar till
timeout).
When i restart apache2 anything is fine again - at least for some minutes.
Trying to trace it down to some buggy script execution i checked logs
and found nothing similar between those events.
This is a live installation and we're suffering... System load at ~1.0
.. 2.0
The issue started at one specific day, where we didn't change anything
by intention. Replacing the whole hardware also didn't help.
Is there someone to show me ways to debug this issue or any idea?!
(Personal contacts also apreciated.)
I'm happy to hear any input about this one.
--
Miro Dietiker
Date: Thu, 29 Nov 2007 10:55:25 +0100
From: Florian Kulzer <florian.kulzer+debian@icfo.es>
To: debian-user@lists.debian.org
Subject: Re: Font size under X
Message-ID: <20071129095525.GA5328@pc0197>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Thu, Nov 29, 2007 at 14:25:31 +0530, Sridhar M.A. wrote:
> I am facing a peculiar problem. Currently am running debian unstable.
> The fonts under X are too small.
What do you mean by that? Did you check the absolute sizes with a ruler?
One "point" should correspond to 1/72 of an inch; a 12pt font, for
example, should have a height of 1/6 of an inch (4.2 mm) on your screen.
> I can get around this problem by
> playing with the dpi setting under gnome, but I feel that is not the
> correct way of doing it.
I would simply use the correct DPI setting, calculated from the width
and height of your screen and the number of pixels in each direction.
You can also specify the dimensions of your screen explicitly in the
Monitor Section of your xorg.conf (Option "DisplaySize"). This should
override incorrect settings if X gets the wrong idea from DDC-probing
the monitor.
It might furthermore be necessary to put
Xft.dpi: 96
into your ~/.Xresources to ensure consistent font sizes for all
applications. (Replace "96" with the correct DPI value for your screen.)
> What surprises me is that of the 4 machines I am using (all debian sid),
> only two exhibit this problem. Both of those machines have a CRT monitor
> while the other two have an LCD monitor.
Compare the output of
xdpyinfo | grep resolution
xrdb -query | grep Xft
on the different machines.
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
End of debian-user-digest Digest V2007 Issue #2908
**************************************************
Received on Thu Nov 29 05:39:01 2007