Re: ia32 library repository

2008-04-25 Thread Alex Samad
Hi

I was wondering if there was any plans to ia32 mplayer, specifically to
get access to the windows 32bit dll's


alex

On Sat, Apr 05, 2008 at 04:35:16AM +0200, Javier Serrano Polo wrote:
> Hi all.
> 
> The scripts used have been packaged. If there aren't any important
> errors I'll contact ftp masters about next Friday.
> 
> Bye.
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
> 



signature.asc
Description: Digital signature


RE: problems reinstalling nvidia cards after crash of Xorg.conf compiz edit forced OS reinstall...

2008-04-25 Thread Michael Fothergill

I have fixed the problem of installing the nvidia kernel source.
 
I had written nonfree instead of non-free (forgot the hyphen!) in the 
respository description and so apt couldn't find the right packages in sid.
 
The problem I have now is one that has I think been mentioned in another post 
on this site where running dpkg-reconfigure xserver-xorg wouldn't let me choose 
the type of graphics card as nvidia as it  did the last time I got the nvidia 
card successfully installed and configured.  It stops after sniffing around at 
the keyboard and mouse stuff.  
 
It shuts up shop, writes a version of the xorg file with something weird like 
xorg.2008042508 after it and says it is worried about overwriting a special 
modification of the xorg configuration.
 
It then uses the vesa dumb graphics card setting to display the screen and 
ignores all the work I did installing the nvidia kernel.
 
I will keep hacking away at it and I will get there in the end.
 
Thanks for help from everyone on the site.  You are real gents.
 
Regards
 
Michael Fothergill> Date: Thu, 24 Apr 2008 15:40:44 -0500> From: [EMAIL 
PROTECTED]> To: [EMAIL PROTECTED]> Subject: Re: problems reinstalling nvidia 
cards after crash of Xorg.conf compiz edit forced OS reinstall...> > I'm not an 
exim expert...> > 1 if you don't need exim don't install it...> 2 there are a 
couple o flavors of exim try the other one...> > On 4/24/08, Michael Fothergill 
<[EMAIL PROTECTED]> wrote:> >> >> > > > 
> Date: Thu, 24 Apr 2008 13:20:37 -0500> > > From: [EMAIL PROTECTED]> > > To: 
debian-amd64@lists.debian.org> > > Subject: Re: problems reinstalling nvidia 
cards after crash of Xorg.conf compiz edit forced OS reinstall...> > >> > > you 
have a incomplete installation of exim, that needs to be corrected...> > >> > 
How do I go about fixing exim4 ?> >> > I tried reinstalling it from my dvd but 
it didn't help...> >> > Suggestions welcome.> >> > Regards> >> > Michael 
Fothergill> > 
_> > Search and 
win with BigSnapSearch.com> > http://www.bigsnapsearch.com> >> > > -- > Perhaps 
the depth of> love can be calibrated by the number of different selves that 
are> actively involved in a given relationship.> > Carl Sagan (Contact)> > 
Jaime Ochoa Malagón> Integrated Technology> Tel: (55) 52 54 26 10
_
100’s of prizes to be won at BigSnapSearch.com 
http://www.bigsnapsearch.com

Re: sensors

2008-04-25 Thread Lennart Sorensen
On Fri, Apr 25, 2008 at 08:06:40AM -0400, Lennart Sorensen wrote:
> Oh darn, I better go tell the hardware guys here that the chip we are
> using in our product isn't working. :)  We use the W83627HF-AW on
> purpose because it works and is supported.
> 
> The chip is supported perfectly, as long as you get the resistor values
> used on each voltage input and which voltage each input is supposed to
> have.
> 
> lm-sensors is irrelevant since the driver is actually part of the 2.6
> kernel.  lm-sensors just provides the user space tools to easily access
> the data from the driver (although you can get it all through /sys as
> well if you fell like it).

It might be possible if you have a magnifying glass to find the values
of the resistors close to the 83627, in which case it might be possible
to guess what the values should be in sensors.conf.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: sensors

2008-04-25 Thread Lennart Sorensen
On Fri, Apr 25, 2008 at 03:11:37AM -0700, Francesco Pietra wrote:
> Following a suggestion by Romain Delbeau (lm-sensors H8DC8 board), I 
> contacted Supermicro again. Their prompt answer:
> 
> H8QCE uses Winbond W83627HF-AW monitoring chip which currently is not 
> supported by lm-sensors utility. 
> 
> However you can use SuperDoctor II for Linux which has same capability as 
> lm-sensors
>  
> 
> ftp://ftp.supermicro.com/utility/Supero_Doctor_II/
> 
> 
> Why they did not provide this information at my first instance is a mystery.

Oh darn, I better go tell the hardware guys here that the chip we are
using in our product isn't working. :)  We use the W83627HF-AW on
purpose because it works and is supported.

The chip is supported perfectly, as long as you get the resistor values
used on each voltage input and which voltage each input is supposed to
have.

lm-sensors is irrelevant since the driver is actually part of the 2.6
kernel.  lm-sensors just provides the user space tools to easily access
the data from the driver (although you can get it all through /sys as
well if you fell like it).

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: sensors

2008-04-25 Thread Steffen Grunewald
On Fri, Apr 25, 2008 at 03:11:37AM -0700, Francesco Pietra wrote:
> Following a suggestion by Romain Delbeau (lm-sensors H8DC8 board), I 
> contacted Supermicro again. Their prompt answer:
> 
> H8QCE uses Winbond W83627HF-AW monitoring chip which currently is not 
> supported by lm-sensors utility. 

Sure, Supermicro knows better than the chip driver which chips are supported by 
lm-sensors :(

You have seen some sensors output from a 627 chip, haven't you?
They just might have told you their wiring... and let you find out the rest.

> Why they did not provide this information at my first instance is a mystery.

Why they don't know better, is a mystery for me :((

S

-- 
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: sensors

2008-04-25 Thread Francesco Pietra
Following a suggestion by Romain Delbeau (lm-sensors H8DC8 board), I contacted 
Supermicro again. Their prompt answer:

H8QCE uses Winbond W83627HF-AW monitoring chip which currently is not supported 
by lm-sensors utility. 

However you can use SuperDoctor II for Linux which has same capability as 
lm-sensors
 

ftp://ftp.supermicro.com/utility/Supero_Doctor_II/


Why they did not provide this information at my first instance is a mystery.



francesco

 


--- On Thu, 4/24/08, Lennart Sorensen <[EMAIL PROTECTED]> wrote:

> From: Lennart Sorensen <[EMAIL PROTECTED]>
> Subject: Re: sensors
> To: "Francesco Pietra" <[EMAIL PROTECTED]>
> Cc: debian-amd64@lists.debian.org, "Steffen Grunewald" <[EMAIL PROTECTED]>
> Date: Thursday, April 24, 2008, 7:59 AM
> On Thu, Apr 24, 2008 at 07:12:32AM -0700, Francesco Pietra
> wrote:
> > This simpler board is also on the Supermicro CD list.
> Do you suggest to extrapolate the settings to my 4-sockets
> board? Any guess how to set for the other two CPUs?
> 
> Well the voltage settings at least might be the same in
> terms of the
> multiplier and offset that is shown on that page.  And it
> did list 8 or
> so fan connectors with a divisor of 8 which might be right.
> 
> If the voltages you get make sense then they are probably
> right.  You
> should have 3.3V, 5V, 12V and usually -12V.  The CPU core
> voltage is
> usually in the 1.1 to 1.6V range depending on the CPU.
> 
> -- 
> Len Sorense


  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]