Re: [RDD] Newbie with a New Install

[Cowboy]

On Tuesday 08 March 2016 07:23:30 pm Jamie Dennis wrote:
> Kernel panic – not syncing: Attempted to kill init! 
> 
> And then it stops.
> 
> I’m beginning to think it is something with a BIOS setting but I don’t know.
> 

 Nope.
 Can't have a kernel panic until there's a kernel TO panic.
 You're well beyond BIOS at that point.

 More likely, the device driver wasn't built into the kernel, so the
 kernel can't read the device to load the module that is the driver.

-- 
Cowboy

http://cowboy.cwf1.com

"No self-respecting fish would want to be wrapped in that kind of
paper."
-- Mike Royko on the Chicago Sun-Times after it was
   taken over by Rupert Murdoch
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell to EAS Link

[Cowboy]

 Going back to the original question

>> From: "Ryan Kin" 

>> >> Is there a way so that Rivendell to trigger EAS events without the EAS
>> >> having to interrupt Rivendell during traffic, music, etc.?

 If you have GPIO on Rivendell, and your EAS box will allow you to do that
 by providing closures, then yes.

 It would be a matter of constructing the carts, and "playing" them
 appropriately.

-- 
Cowboy

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Rivendell to EAS Link

[Aaron Savage]

Since I got jumped on by a few people about what I said.

1.  I never said the eas box was out of line.  I just said certain elements
were delayed.  If the delay was missed then it would play. EAS box still
has final say.

2.  Just for clarification...I also missed that this was the 1822 and not
the digital.  Thanks Ryan for  pointing that out.

3.  Point of order.  Dasdec and Digital Endec have integrated automation
systems into their programming.  I am not disputing any rules.  I am not
commenting on the legality.  Save that for another list.

Aaron



On Tue, Mar 8, 2016 at 4:14 PM, Aaron Savage  wrote:

> I see what you are trying to accomplish.  I have a few warnings that are
> delayed a few minutes only to allow operator time.  However, the big ones
> like EAN, Tsunami, Earthquake, and Amber alerts should always pre-empt.
> There are systems that talk directly to the Sage Digital to make this
> possible.   I have not seen any of this being pursued in Rivendell.  It
> does sond like a nice feature.
>
>
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Rivendell with audio switcher

[Jim Stewart]

I'm guessing the RPI's GPIO's do not show up in Rivendell.  What I would do is 
have a separate task, which can be a simple shell script if you'd like that 
checks for a GPI change, then executes the command line rmlsend command to call 
a Rivendell macro to do what you want.  To command the switcher via GPO (if 
that turns out how you need to command it), it can use the macro command to 
call a shell script that executes a simple command to set a GPO line as well.



I have done some simple GPIO stuff on RPI's for other purposes in the past.  
Unfortunately I only know how to pole the location of the GPI state in a 
polling loop.  I don't know if it is possible to have this driven from an 
interrupt instead, which would be better.  I'm not near the code I used for all 
this at the moment, but could help you later if needed.



I agree that if you are only triggering ID's, I would opt for a simpler 
solution, perhaps even buy something like a Denon SD card player that can be 
triggered to play tracks from contact closures, but of course a RPI can 
certainly do all this too with simple scripts.



I have a computer at one of our transmitter sites do all kinds like this such 
as providing "alternate programming" if the Internet-fed STL link fails, 
automatically detecting and switching to a backup studio feed (and back again), 
all while logging all this for later inspection.  I did all this using ".bat" 
(batch file) Windows scripts (painfully I might add) because that machine also 
runs a Windows-only software audio processor/stereo generator program build the 
composite stereo signal to feed the FM transmitter.



I think I would use some sort of watchdog timer fed by repeated "keep alive" 
commands from the RPI that would reboot the RPI in case something goes wrong 
because  I'm not sure I would trust them, especially in harsh transmitter site 
environments, but then again I tend to overclock my RPI's which surely makes 
them less than reliable for me.  You might even consider underclocking it a 
little!



Date: Tue, 8 Mar 2016 13:56:34 -0500

From: Seth Stevenson mailto:rcflye...@gmail.com>>

To: 
rivendell-dev@lists.rivendellaudio.org

Subject: [RDD] Rivendell with audio switcher

Message-ID:


mailto:CAE22iEDeOVbEKRe0+AvjFXCG6M1zMdbBeDvEU=unbxbatvw...@mail.gmail.com>>

Content-Type: text/plain; charset="utf-8"



I work for a large network with about 45 stations. All our programming is 
originated in one location and delivered to the stations via satellite feeds. A 
dish at each site receives the audio to the transmitters and towers which are 
co-located. All the programming is the same for each station. For local ID's 
and PSA's we use a Burk LX-1 switcher. For ID at the top of the hour, our ENCO 
DAD fires a command to the switcher which activates a CD player and plays the 
ID. Then a command is given to switch back to sat. Same thing throughout the 
day for local PSA's. We are non-commercial, so no commercials. We want to move 
away from the CD players. I am trying to get them to move to Rivendell on a 
Raspberry Pi to due this. What is the best way to set up GPIO for Rivendell to 
due this? It needs to have a playlist of say 20-30 ID's that rotate in a loop. 
Once one is played then it needs to stop until the next switcher command to 
play the next cut. The log needs to be reloaded at midnight for the next day as 
well. I know this should be fairly easy with macros, but need some input. I 
will not be the final person implementing it, but I'm the only one familiar 
with Rivendell, so am trying to "sell" it for this project. Thanks. By the way, 
I do have Rivendell already running on a test Raspberry PI.

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Newbie with a New Install

[Jim Stewart]

Linux starts out booting using BIOS calls to the "bootable device" (hard drive, 
etc).  This all done by a bootloader itself.   Once the kernel and initramfs is 
loaded into memory, the processor switches to a more advanced mode (from "real" 
compatibility mode) and starts executing the kernel.  At this point it is up to 
the drivers in Linux to be able to find its file system.  I'm guessing it is 
NOT.  This could be that there is not a driver loaded for the hardware that 
contains the file system, or perhaps the BIOS has done some sort of switch of 
boot device order such that the kernel is now looking in the wrong place for 
its file system.   The later can be dealt with by adding some direction to the 
boot loader to boot on the correct device.  Since you are booting on USB, there 
is a lot that could go wrong here as the USB hardware itself could be missing a 
driver, and likely is.  Typically the driver for this would be compiled as a 
separate module then loaded into the initramfs file system for the kernel to 
load.  Your CentOS might not have done this, at least for the actual USB port 
device hardware you have, which means you would have to add it yourself and 
rebuild the initramfs (and finally the change the file system on the USB 
storage device you are using).  This is a little involved to do.



In any case, look further back on the boot messages (use "shift - page up" to 
scroll up the page if needed) and check that a driver for the hardware that the 
file system did get loaded and the storage device itself did get found and is 
what the kernel is looking for.  For example, look for /dev/sda1 if that is 
what it thinks it should boot on and make sure that device didn't end up being 
set as /dev/sdb1 instead!  If there is no mention of a "sdx" device then my 
original theory that the driver never got load would prevail.  In this case I 
would resort to installing the file system on a traditional non-USB device (as 
in a SATA device) to get things going quickly.





Date: Tue, 8 Mar 2016 19:23:30 -0500

From: Jamie Dennis mailto:radiodocto...@gmail.com>>

To: 
"rivendell-dev@lists.rivendellaudio.org"


mailto:rivendell-dev@lists.rivendellaudio.org>>

Subject: Re: [RDD] Newbie with a New Install

Message-ID: 
<56df6d01.08de8c0a.327c5.b...@mx.google.com>

Content-Type: text/plain; charset="utf-8"



Well, I tried the CentOS 7 Live DVD installed on a bootable USB created by 
unetbootin-windows-613 and I get a ?

Kernel panic ? not syncing: Attempted to kill init!



And then it stops.



I?m beginning to think it is something with a BIOS setting but I don?t know.





Thanks,

-Jamie

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev