Another idea you can do to prevent this is to not upgrade the kernel,
but update everything else that needs updating... if it ain't broke on
your hardware, don't fix it.
totally agreed, and once a system is in production, it gets updates
turned off. should have paid more attention to what I was updating, but
I'm still relatively new to 'Nix so it's a good lesson in the
ramifications of a kernel update.....
Kernel modules are built using the current working kernel's source
tree, so it's by default installed to the current kernel version
kernel directory (i.e. /lib/modules/`uname -r`)
Greek to me...but I'll look into it. any advice would be apreciated
though. It's currently working by booting into the previous kernel
though, so no panic.
Thanks all,
Nathaniel C. Steele
Assistant Chief Engineer/Technical Director
WTRM-FM / TheCrossFM
On 1/9/2013 12:36 AM, Christopher Cmolik (RIT Student) wrote:
With our ASI cards we have always had to make sure to recompile the
ASI kernel module for either hpklinux or the alsa snd_asihpi driver.
Kernel modules are built using the current working kernel's source
tree, so it's by default installed to the current kernel version
kernel directory (i.e. /lib/modules/`uname -r`)
Another idea you can do to prevent this is to not upgrade the kernel,
but update everything else that needs updating... if it ain't broke on
your hardware, don't fix it.
On Mon, Jan 7, 2013 at 8:26 PM, Wayne Merricks
<waynemerri...@thevoiceasia.com
<mailto:waynemerri...@thevoiceasia.com>> wrote:
Hi,
The kernel module will probably have to be rebuilt/reinstalled for
the newer kernel. I'm not sure if the tryphon repos have the ASI
stuff precompiled, if not you'll have to do it manually from
source. I've not used any ASI cards so can't really help you
further but its a normal linux thing that happens. Its the same
problem with the GPIO drivers and other things like the Virtual
Box kernel bits and bobs.
>From what I've read something called DKMS can be used to manage
kernel modules like this but that is the extent of my knowledge on
the subject. Might be worth checking out either way.
Regards,
Wayne
-----Original Message-----
From: rivendell-dev-boun...@lists.rivendellaudio.org
<mailto:rivendell-dev-boun...@lists.rivendellaudio.org> on behalf
of Nathan Steele
Sent: Mon 07/01/2013 22:45
To: User discussion about the Rivendell Radio Automation System
Subject: Re: [RDD] updated to 2.3.0, lost ASI cards
OK, the kernel update must have broke it, booting up in the next most
recent kernel version seems to have solved the problem.
I would like to know how to fix it on the current kernel, or how to
permantly make the system boot into the kernel version that works.
Of course I do not do updates after a system is in production (unless
needed) , but generally do all updates when building new system.
Thanks,
Nathaniel C. Steele
Assistant Chief Engineer/Technical Director
WTRM-FM / TheCrossFM
On 1/7/2013 5:15 PM, Nathan Steele wrote:
> I just did the 2.3.0 update on a system I was going to press into
> service this week. I went ahead and did the other updates it
wanted to
> do in addition to the rivendell update. this is a Broadcast
appliance
> install with two ASI 6012 cards installed and working prior to the
> update. lspci still shows the cards, but the rivendell hpi
config says
> the drivers are not installed.
>
> I tried insmod /lib/modules/2.6.18-194.26.1.el5/extra/asihpi.ko
and was
> returned the error "error inserting asihpi.ko : no such device"
(this
> was suggested when I was diagnosing a problem with these cards on a
> different system, which turned out to be a BIOS problem, but
figured I
> would go through the steps before asking for help again)
>
> I have tried rebooting, and just restarting rivendell, to no avail.
>
> any suggestions? can I roll back the updates? I can always start
over,
> this is not yet a production system, but was hoping to put it online
> this week. do you think the kernel update broke it?
>
> thanks
>
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
<mailto:Rivendell-dev@lists.rivendellaudio.org>
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
#######################
Scanned by MailMarshal
#######################
############
Attention:
The information contained in this message is confidential and intended
for the addressee(s) only. If you have received this message in error
or there are any problems, please notify the originator immediately.
The unauthorised use, disclosure, copying or alteration of this
message
is strictly forbidden. Christian Vision or any of its subsidiaries
will
not be liable for direct, special, indirect or consequential damages
arising from alteration of the contents of this message by a third
party
or as a result of any virus being passed on. Please note that we
reserve
the right to monitor and read any e-mails sent or received by the
company under the Telecommunications (Lawful Business Practice)
(Interception of Communications) Regulation 2000. Christian Vision is
registered in England as a limited company 2842414 and as a charity
1031031
############
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
<mailto:Rivendell-dev@lists.rivendellaudio.org>
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
--
*Chris Cmolik *|*RIT Information Technology '13*
Chief Engineer Emeritus, WITR Radio
[clc5...@rit.edu <mailto:clc5...@rit.edu>]
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
