headers
Seyyed Mohtadin Hashemi | 1 Jun 2012 05:28
Picon
Gravatar

Re: Only 3.6gb of 64gb RAM recognized by 64bit squeeze

On Wed, 2012-05-30 at 20:18 -0500, Stan Hoeppner wrote:
> On 5/30/2012 8:55 AM, Seyyed Mohtadin Hashemi wrote:
> > On Tue, 2012-05-29 at 15:48 -0500, Stan Hoeppner wrote:
> >> On 5/29/2012 4:08 PM, Seyyed Mohtadin Hashemi wrote:
> >>> On Tue, 2012-05-15 at 21:26 +0200, Seyyed Mohtadin Hashemi wrote:
> >>>> On Tue, May 15, 2012 at 8:51 PM, Stan Hoeppner
> >>>> <stan <at> hardwarefreak.com> wrote:
> >>>>         On 5/15/2012 12:26 PM, Seyyed Mohtadin Hashemi wrote:
> >>>>         > On Tue, May 15, 2012 at 4:30 AM, Henrique de Moraes Holschuh
> >>>>         <hmh <at> debian.org
> >>>>         >> wrote:
> >>>>         >
> >>>>         >> On Mon, 14 May 2012, Stan Hoeppner wrote:
> >>>>         >>> On 5/13/2012 7:02 PM, Henrique de Moraes Holschuh wrote:
> >>>>         >>>> On Fri, 11 May 2012, Seyyed Mohtadin Hashemi wrote:
> >>>>         >>>>> On 5/10/2012 1:16 PM, Stan Hoeppner wrote:
> >>>>         >>>>>> If this doesn't fix the issue, and memtest and other
> >>>>         utils can see
> >>>>         >> all
> >>>>         >>>>>> 64GB just fine, then I'd say you're dealing with a BIOS
> >>>>         bug.
> >>>>         >>>>>
> >>>>         >>>>> The very top of /var/log/dmesg has the kernel debug
> >>>>         output about the
> >>>>         >> memory
> >>>>         >>>>> map.  It might well tell us very quickly who is the
> >>>>         culprit, if the
> >>>>         >> user
> >>>>         >>>>> with the problem can post it for the best working case
> >>>>         and the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Seyyed Mohtadin Hashemi | 1 Jun 2012 05:45
Picon
Gravatar

SOLVED: Only 3.6gb of 64gb RAM recognized by 64bit squeeze

Summary:
Debian Squeeze 64-bit was not able to use more than 3.6GB RAM. Linux
showed the problem as MTRR not covering all available RAM. 
MTRR problems can be fixed by kernel if MTRR repair is enabled, e.g. in
the 3.2 kernel. However, the using the backported 3.2 kernel resulted in
kernel panic. 

As RAM had been tested extensively with memtest, the problem was
hypothesized to be because of faulty motherboard or BIOS. 
One RMA of MB later, and everything is working with the 3.2 kernel and
"noapic irqpoll acpi=force" boot flags.

I did have a small problem: Sometimes I would get "RAM R/W test fail" at
BIOS POST. I tested if the individual DIMMs could POST, only one gave
the "RAM R/W test fail". After removing the 'faulty' DIMM + a healthy
DIMM, the system works smoothly. I have not had time to test the
'faulty' DIMM in another computer yet to see if it really is faulty.

Thank you all for your help!
Permalink | Reply | 0 comments |
headers
Michael Aldridge | 1 Jun 2012 01:44
Picon

Re: Intel 82830 in motion computing slate

I got it working but I have no idea how.  After a couple of reboots it started working...

On May 31, 2012, at 4:55 PM, Stan Hoeppner wrote:

> On 5/31/2012 12:10 PM, Michael Aldridge wrote:
>> I went ahead and retried disabling mode setting with grub, but still no graphics.  I am correct in thinking
that it should be on tty6 right?  the KDM definitely thinks it is running, but I can't seem to find it.
> 
> Please reply to the list or reply to all.  Others on the list have far
> more experience with this than me.  I simply was the first to reply.
> 
> -- 
> Stan
Permalink | Reply | 0 comments |
headers
Hor Jiun Shyong | 1 Jun 2012 03:19
Picon

Re: libmx-1.0-2 : Depends: libmx-common (= 1.4.5-1) but 1.4.6-1 is installed

On 05/30/2012 10:23 PM, Arnt Karlsen wrote:
> ..ok, since you're not pointing me back to your post, I assume
> you solved it, and since your solution may help somebody else
> here, you may want to post your solution with a nice tag like
> "[Solved], was:"$your-subject-on-your-original-post. ;o)
>

The problem was not solved. There wasn't any feedback to my last post as 
below:

>
> Is this bug (Bug#665000: SUMO2: blank screen after load "radeon" 
> module) related to my issue? As I am using Sumo chip too AMD Llano 
> A6-3670 APU with Radeon(tm) HD Graphics stepping 00
>
> root <at> szechuan:~#: dmesg | grep -i sumo
> [ 7.451590] [drm] initializing kernel modesetting (SUMO 0x1002:0x964A 
> 0x1043:0x84C8).
> [ 7.453403] [drm] Loading SUMO Microcode 

-- 
Regards,
Jiun Shyong 俊雄

Blog: jiunshyong.dyndns.org
twitter.com/jiunshyong
facebook.com/jiunshyong
Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee.

--

--
(Continue reading)

Permalink | Reply | 1 comment |
headers
Hor Jiun Shyong | 1 Jun 2012 03:42
Picon

Re: libmx-1.0-2 : Depends: libmx-common (= 1.4.5-1) but 1.4.6-1 is installed

On 05/31/2012 09:32 AM, Vincent Lefevre wrote:
> Such messages can occur due to some error when dpkg tries to install
> a package. For instance, the user tried to upgrade both libmx-1.0-2
> and libmx-common from 1.4.5-1 to 1.4.6-1, but the installation of
> libmx-1.0-2 1.4.6-1 failed (e.g. because it would lead to some file of
> some other package overwritten). So, the system is in an inconsistent
> state.
>

Temporarily I have removed libmx-common, libmx-1.0-2 and all dependencies.

-- 
Regards,
Jiun Shyong 俊雄

Blog: jiunshyong.dyndns.org
twitter.com/jiunshyong
facebook.com/jiunshyong
Knowing is not enough, we must apply. Willing is not enough, we must do - Bruce Lee.

--

-- 
To UNSUBSCRIBE, email to debian-user-REQUEST <at> lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org
Archive: http://lists.debian.org/4FC81E0B.4000706 <at> gmail.com
Permalink | Reply | 1 comment |
headers
Stephen Powell | 1 Jun 2012 04:30
Favicon

Re: how are you kids compiling kernels these days?

On Thu, 31 May 2012 06:18:06 -0400 (EDT), Tom H wrote:
> 
> One of this list's regulars has a very good page:
> 
> http://users.wowway.com/~zlinuxman/Kernel.htm
> 

Thanks for the vote of confidence, Tom.  By the way, I think a lot
of the confusion in this thread comes from the fact that a linux
kernel source package in Debian is classified as a *binary* package.
Therefore, it is not installed with "apt-get source", and you must
be root to install it.  For example,

   # aptitude install linux-source-3.2

There is a corresponding Debian source package for this binary
package, of course, and it is called, believe it or not,
linux-2.6!  You can install this Debian source package, if you
want, by means of

   $ apt-get --only-source source linux-2.6

At the time of this writing, the version of this source package
in the Wheezy archive is 3.2.18-1, which contains kernel source
code from upstream kernel version 3.2.18.

This issue, and many other "gotchas", are documented on the above-
mentioned web page.  If you plan to use make-kpkg or "make deb-pkg"
to build the kernel, the "binary" package is the one you want
to install.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ralf Mardorf | 1 Jun 2012 07:03

Re: Screen unresponsive

On Thu, 2012-05-31 at 23:59 +0200, Abou Al Montacir wrote:
> On Tue, 2012-03-13 at 17:04 +0000, Darac Marjal wrote:
> > It would suggest to me that your
> > graphics card (the GPU) is no longer attached to the PCI bus. Probably
> > the best case scenario is that this is a physical problem: Open up your
> > computer, pull out the card and push it back in, making sure it's fully
> > seated.
> 
> I don't think this is related to HW issue

I also don't think that it's related to the hardware, but assumed it
should be due to bad hardware connections, take care when you screw the
card to the box, that the card doesn't change it's position inside the
socket. The case of a computer is often the weak point of the hardware.

Time to open a new thread ...

Regards,
Ralf
Permalink | Reply | 0 comments |
headers
Ralf Mardorf | 1 Jun 2012 07:03

Computer case

Hi :)

any recommendation for a computer case that can be used with Debian
stable ;)?
Ok, it's slightly OT, I'm sorry for that. However, experiences with
cases regarding to noise (and heat), accuracy of fit for cards are
interesting for me, others might be interested in space (and vertical
stability).

Regards,
Ralf
Permalink | Reply | 41 comments |
headers
Yury O. Tabolin | 1 Jun 2012 07:48
Picon

Re: Slow tape read-write after upgrade

On Thu, 31 May 2012 15:39:04 +0000, Camaleón wrote:

 > "st" kernel module seems to be segfaulting. I would try to reproduce the
 > error from a clean Squeeze installation to discard a problem coming from
 > the upgrade and if it's still present, I'd report it in BTS.

But not the module "st" segfaulting, and process "scsi_id", that applies 
to the package "udev". May be problem is in it? The module "st" runs 
after loading, but with reduced speed. Now I compile module "st" with 
debug option, here the debug log:

Jun  1 09:39:51 s1 kernel: [2048057.202152] st: Version 20081215, fixed 
bufsize 32768, s/g segs 256
Jun  1 09:39:51 s1 kernel: [2048057.204377] st 2:1:4:0: Attached scsi 
tape st0
Jun  1 09:39:51 s1 kernel: [2048057.204400] st 2:1:4:0: st0: try direct 
i/o: yes (alignment 4 B)
Jun  1 09:39:52 s1 kernel: [2048057.912574] scsi_id[23200]: segfault at 
0 ip (null) sp 00000000ff8260e0 error 14
Jun  1 09:39:53 s1 kernel: [2048059.259879] scsi_id[23197]: segfault at 
0 ip (null) sp 00000000ffb33250 error 14
Jun  1 09:40:00 s1 kernel: [2048065.675895] st0: Block limits 1 - 
16777215 bytes.
Jun  1 09:40:00 s1 kernel: [2048065.678045] st0: Mode sense. Length 11, 
medium 0, WBS 10, BLL 8
Jun  1 09:40:00 s1 kernel: [2048065.678068] st0: Density 44, tape 
length: 0, drv buffer: 1
Jun  1 09:40:00 s1 kernel: [2048065.678088] st0: Block size: 0, buffer 
size: 4096 (1 blocks).
Jun  1 09:40:00 s1 kernel: [2048065.707199] st0: Error: 8000002, cmd: 8
(Continue reading)

Permalink | Reply | 2 comments |
headers
Mark Panen | 1 Jun 2012 07:53
Picon

Re: Computer case

On 01/06/2012 07:03, Ralf Mardorf wrote:
> Hi :)
>
> any recommendation for a computer case that can be used with Debian
> stable ;)?
> Ok, it's slightly OT, I'm sorry for that. However, experiences with
> cases regarding to noise (and heat), accuracy of fit for cards are
> interesting for me, others might be interested in space (and vertical
> stability).
>
> Regards,
> Ralf
>
>

Here are some cases which actually make Debian go faster especially the 
high end ones :-)

http://www.thermaltake.com/chassis.aspx

--

-- 
Cheers
Mark
Permalink | Reply | 2 comments |

Gmane