Standard Mpeg-1 Video player

[Jordan Dean]

Has anyone found a player / codec that is in the standard SL repositories
that will playback mpeg 1 encoded video.  (Totem does not have the codec in
the two sets of gstreamer plugins that are provided).
 
Thanks,
 
Jordan Dean

 

RE: Standard Mpeg-1 Video player

[Jordan Dean]

>> On 09/06/2011 03:14 PM, Jordan Dean wrote:
>>> Has anyone found a player / codec that is in the standard SL 
>>> repositories that will playback mpeg 1 encoded video.  (Totem does 
>>> not have the codec in the two sets of gstreamer plugins that are
provided).
>>> Thanks,
>>> Jordan Dean
>> Can you provide a link to an example mpeg-1 encoded file to test?
>> 
>   On SL5.6 we use VLC.
> 
>   yum --enablerepo=dag install vlc
> 
> -- 
> Best regards,
>   Robert FRANCHISSEUR


Is Dag's repo considered a standard SL repo?

Christopher Tooley
ctoo...@uvic.ca
Systems, HEP/Astronomy UVic


For my purposes, the only thing that would be considered standard would be
specifically from the SL repos, we would also use the same thing on our TUV
machines.

It appears however that this is not possible due to concerns about mpeg-1
licenses / licensing.  We'll just figure out what we want to do instead, I
was hoping that I was just missing something.

-Jordan

RE: need help installing nvidia driver on new laptop

[Jordan Dean]

I've barely been keeping up with all of the trial and error.  If you are not
opposed to using the NVidia Linux drivers that you download directly from
them, this is what I would suggest, please note, there is a new step that
you did not have to do in 6.0 that is now required for 6.1 (at least on the
machines we're using).
 
echo 'blacklist nouveau' >> /etc/modprobe.d/blacklist.conf
vi /etc/grub.conf  add rdblacklist=nouveau  to kernel line
*NEW STEP*  yum remove xorg-x11-drv-nouveau
reboot (you should not see ANY mention of nouveau in the message log, if you
do, it's not going to work)
init 3 
./NVIDIA-Linux.
reboot
nvidia-settings (if you need to adjust stuff).
 
 
you MUST MUST MUST remove nouveau, this is new behavior in 6.1 not sure why
but that's what I had to do to make my old process work.
 
 
-Jordan

  _  

From: owner-scientific-linux-us...@listserv.fnal.gov
[mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Andrew
Z
Sent: Tuesday, September 13, 2011 7:37 AM
To: Kevin Thomas
Cc: Phil Perry; SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Subject: Re: need help installing nvidia driver on new laptop


I recently removed my xorg.conf and x refused to start. Ob the screen I saw
blinking and then. Well nothing.
Maybe if you put some basic conf it will help?
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.


Kevin Thomas  wrote: 

I just read over that, but I didn't get much out of it other than "the intel
stuff worked" (there wasn't really any explanation on that) and that bumblee
is the proclaimed solution, unless I'm missing something.  I don't know what
you mean by the latest and greatest driver. Are you referring to Intel or
Nvidia? I don't even have an xorg.conf file on my system.

On 09/12/2011 09:36 PM, Andrew Z wrote: 

h. Did you see this : https://bbs.archlinux.org/viewtopic.php?id=124918
?
(silly question, but i'll still try) - are you sure you have the latest and
greatest driver?

get rid of xorg.conf  and see if you get anything.


On Mon, Sep 12, 2011 at 7:31 PM, Kevin Thomas  wrote:


Here's the relevant lines from /var/log/messages:

Sep 11 21:09:55 xps kernel: [drm] nouveau :01:00.0: Disabling fbcon
acceleration...
Sep 11 21:09:55 xps kernel: [drm] nouveau :01:00.0: Unpinning
framebuffer(s)...II) intel(0): Modeline "800x600"x60.3   40.00  800 840 968
1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601
603 625 +hsync +vsync (35.2 kHz)
(II) intel(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 486
494 517 +hsync +vsync (31.0 kHz)
(II) intel(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492
525 -hsync -vsync (31.5 kHz)
(II) intel(0): EDID for output VGA2
(II) intel(0): EDID for output HDMI2
(II) intel(0): EDID for output DP1 


On 09/11/2011 11:07 PM, Andrew Z wrote: 

Kevin,
I'm sure you went over this. Already, but maybe you can tell us what last
(relevant ) lines are in messages are and what X.log has?
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.


Kevin Thomas    wrote: 

You are correct that when you install the kmod-nvidia package, it 

automatically disables nouveau and blacklists it for you, but I didn't 

know there was a new nvidia xorg.conf file created.  After I installed 

the kmod-nvidia package again, I restarted and modified the kernel 

arguements to include the intel.disable=1 arguement, but the result was 

the sameeventually the screen flickered a few times and it stopped 

booting, although I could still open a terminal via alt+F2.  I'm not 

sure what to try next. Someone requested some command output from me in 

a different email, which I provided, but I'm lost now.  I didn't think 

it would be this difficult.



Kevin



On 09/11/2011 01:10 PM, Phil Perry wrote:

> On 11/09/11 18:39, Chris Pemberton wrote:

>

>> Some good info over at the archlinux forums:

>>

>> https://bbs.archlinux.org/viewtopic.php?pid=881549

>>

>> http://linux-hybrid-graphics.blogspot.com/

>>

>> To test the nvidia driver: blacklist the nouveau and intel graphic

>> modules, disable kernel mode-setting, and boot to runlevel 3 (all via

>> the kernel command line args below). Then run nvidia's xorg creation

>> tool (nvidia-xconfig). Give X a try and see if it works.

>>

>> nouveau.disable=1 intel.disable=1 nomodeset 3 <--append this to grub

>> kernel line

>>

>

> The elrepo.org kmod-nvidia package already disables nouveau 

> mode-setting (nouveau.modeset=0), blacklists the nouveau driver and 

> runs nvidia-xconfig to create a suitable xorg.conf

file.

>

> Perhaps in the case of these hybrid systems we also need to blacklist 

> the Intel driver too as suggested above. Do we know which Intel driver 

> is being loaded?

>

> Once you have worked out what works for you through testing, you 

> should file a bug at http://elrepo.org/bugs/ and we can get these 

> fixes incorp