updated mm with 0.27

warpme · Post by **warpme** » Thu Sep 26, 2013 10:27 am

Hi all,
Pert some ideas/questions from mytv-users ML I do quick build of current mm with updated things like:

mythtv 0.27-fixes
kernel 3.10.11
nvidia 319.49
qt 4.8.5
lirc 0.9.0
xfree-intel 2.21.15
libdrm 2.4.46
libva-intel-driver 1.2.1
cairo 1.12.14

Build is exactly like current GAR, target is pentium-mmx 32bit architecture.
I done only v.brief testing (basically boot image on my home environment).

You can give it try at:
https://www.dropbox.com/s/z11sfbg2s1vwy ... 83.tar.bz2
https://www.dropbox.com/s/bxgp4aq6t0drl ... ar.bz2.md5
https://www.dropbox.com/s/m719iya31yx6t ... 83.tar.bz2
https://www.dropbox.com/s/g7kr82z3yq6e8 ... ar.bz2.md5

Good luck!

m_theredhead · Post by **m_theredhead** » Sun Sep 29, 2013 4:34 pm

Thank you very much for the update.

I upgraded my backend this morning with the test 0.27 rpms from rpmfusion and updated my frontend with the packages your posted below.

They have seen minimal testing, but so far, they seem to be working well.

m_theredhead · Post by **m_theredhead** » Sun Sep 29, 2013 11:01 pm

Hello,

I decided to try to boot this image on every frontend I have. Most have worked fine, but I do have an ION frontend that is giving an error:

missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw

If I leave it alone for a few minutes, it does complete the boot and seems to work ok.

Under /lib/firmware, I just see the ath3k-1.fw and a radeon directory.

Michael

warpme · Post by **warpme** » Mon Sep 30, 2013 8:43 pm

@m_theredhead,

Did You try to add rtl8168d-2.fw firmware file load with help of MM_FIRMWARE_FILE_LIST ?

Basic instructions are here:
http://www.minimyth.org/document-minimy ... M_FIRMWARE

rtl8168d-2.fw file isn't included in image so it should be downloaded from conf-ro directory at boot time.

br

m_theredhead · Post by **m_theredhead** » Mon Sep 30, 2013 11:00 pm

Hello,

I had assumed this firmware was present in the older minimyth, but that assumption is proving to be incorrect.

I did try adding a line like:
MM_FIRMWARE_FILE_LIST=rtl_nic/rtl8168d-2.fw
or
MM_FIRMWARE_FILE_LIST=rtl8168d-2.fw

but both put the firmware into /lib/firmware. For this nic, it needs to be in /lib/firmware/rtl_nic and I am not sure how to get it to pull to that location.

JoeHenley · Post by **JoeHenley** » Tue Oct 01, 2013 4:18 am

For that, you're better off doing it via minimyth.pm:
--Put the rtl8168d-2.fw file in the conf directory
--Add something like:
$minimyth->confro_get('rtl8168d-2.fw', '/lib/firmware/rtl_nic/rtl8168d-2.fw');
chmod(0755, '/lib/firmware/rtl_nic/rtl8168d-2.fw');
to the minimyth.pm file.

Don't forget to restore the MM_FIRMWARE_FILE_LIST variable in minimyth.conf.

Good luck.

Joe Henley

m_theredhead · Post by **m_theredhead** » Tue Oct 01, 2013 5:09 am

Thanks for the response.

Those lines do indeed get the firmware into the right directory, but minimyth.pm runs far too late in the boot process to get installed during the nic initialization.

For now, I have taken to unpacking the rootfs and manually injecting the firmware so it is available at boot. Something like this:

#Inject rtl firmware
echo "Injecting rtl firmware"
cd ram-minimyth-${version}
mv rootfs rootfs.orig
mount rootfs.orig /mnt
mkdir /tmp/rootfs-${version}
rsync -aH /mnt/* /tmp/rootfs-${version}
umount rootfs.orig
mkdir /tmp/rootfs-${version}/lib/firmware/rtl_nic
cp -a /lib/firmware/rtl_nic/rtl8168d-2.fw /tmp/rootfs-${version}/lib/firmware/rtl_nic
pushd /tmp/rootfs-${version} > /dev/null 2>&1
mksquashfs . ${TREE}/minimyth-${version}/rootfs -noappend > /dev/null 2>&1
popd > /dev/null 2>&1
rm -rf /tmp/rootfs-${version}

I am not sure if I am using the best options for squashfs, but it is working. Does anyone know what the minimyth build process uses to create the squashfs rootfs?

warpme · Post by **warpme** » Tue Oct 01, 2013 2:23 pm

m_theredhead wrote:Thanks for the response.

I am not sure if I am using the best options for squashfs, but it is working. Does anyone know what the minimyth build process uses to create the squashfs rootfs?

It is something like this (makefile language)

Code: Select all

$(top_build)/stage/rootfs: $(top_build)/stage/image/rootfs $(top_build)/stage/image/rootfs.fakeroot
        @echo "making the squashfs version of the root file system"
        @mkdir -m 0755 -p $(@D)
        @rm -rf $@ $@~
        @fakeroot -i $<.fakeroot sh -c "mksquashfs $< $@~ -comp xz -no-exports -no-progress -no-fragments > /dev/null 2>&1"
        @chmod 0644 $@~
        @touch $@~
        @mv $@~ $@

I suspect firmware loading udev rule isn't correctly dealing with sub-directories.
I have to look on this when time allows....

kdewaal · Post by **kdewaal** » Fri Oct 11, 2013 10:46 am

Hi Warpme,

I've just installed the ram--0.27 version from your dropbox and it works competely perfect!
Thanks!

warpme · Post by **warpme** » Fri Oct 11, 2013 7:46 pm

Hi kdewaal

Glad it works well for You.
I spent some time+effort for stabilising mm for my needs and I'm happy that it is perfectly stable not only for me but also for others.
Next days I'll receive 3220T for test machine so I'll have chance to see how Intel GFX and vaapi are going.
Software stack conformant with Intel graphic stack is already there....

all the best!

m_kane · Post by **m_kane** » Sat Nov 30, 2013 3:32 pm

Warpme,
Thanks for your work with minimyth and sharing it with us.

I tried to run it in one of my frontends. Backend still running 0.24, but just tried if it will boot..
Unfortunately it stops booting with "init failed" message.
I did telnet in, and at last lines in /var/log/messages" it fetches lcdd.conf, and after that "init failed".
No any explanations.

Is there any way I could trace the problem?

My frontend is Amd athlon X2 3500+ cpu with nvidia chipset and GT220 display adapter.

warpme · Post by **warpme** » Sat Nov 30, 2013 8:03 pm

@m_kane,
May You pls send me full content of /var/log/messages and eventually /var/log/minimyth.err ?
br

m_kane · Post by **m_kane** » Sun Dec 01, 2013 10:54 am

warpme,

Thanks for your help. I could manage it to boot when I found minimyth.log file from /var/log/. Problem was lirc_imon driver. I now disabled it and mm boots to gui

Now I know that I can update. I must do a good update plan first to avoid downtime.

Could you tell me what gar version is used in your mm build? I think I should get same version and build it to backend.

Have you ever done restore to older myth? If my backend update to 0.27 fails for some reason, I should be able to go back to old 0.24.
Is it as simple as copying myth binaries back and restore database?

warpme · Post by **warpme** » Mon Dec 02, 2013 4:12 pm

m_kane wrote:warpme,

Thanks for your help. I could manage it to boot when I found minimyth.log file from /var/log/. Problem was lirc_imon driver. I now disabled it and mm boots to gui

I'm wonder - do You have imon hardware ?

m_kane wrote:Now I know that I can update. I must do a good update plan first to avoid downtime.

Could you tell me what gar version is used in your mm build? I think I should get same version and build it to backend.

It was build with latest available minimyth SVN (r9766).

m_kane wrote:Have you ever done restore to older myth? If my backend update to 0.27 fails for some reason, I should be able to go back to old 0.24.
Is it as simple as copying myth binaries back and restore database?

Yes. Exactly.
I prepared to "failed upgrades" by dual-boot setup with two the same 10G partitions where I have exact copies of my server. Before upgrade I do:
-RSYNC "production" to "testing"
-reboot to "testing"
-upgrade on "testing"
-work 3-5 weeks on "testing"
-if all OK I do RSYNC "testing" to "production" and reboot to "production"

If there any problems after upgrade - I can immediately go back to "production" - jut by reboot....

Regarding 0.27 - I don't think You will have any problems with it. For me it is best release ever and working in my production without any issues.

BTW: I'm working on Minimyth2 project and hope soon I'll have something to offer here

Good Luck!

m_kane · Post by **m_kane** » Tue Dec 03, 2013 2:53 pm

warpme wrote:I'm wonder - do You have imon hardware ?

Yes I do in one frontend. Two other frontends has also lcd, but I don't remember hardware type now.
Is there known problems with imon? I rememeber that I heard about that.

warpme wrote:I prepared to "failed upgrades" by dual-boot setup with two the same 10G partitions where I have exact copies of my server. Before upgrade I do:
-RSYNC "production" to "testing"
-reboot to "testing"
-upgrade on "testing"
-work 3-5 weeks on "testing"
-if all OK I do RSYNC "testing" to "production" and reboot to "production"

If there any problems after upgrade - I can immediately go back to "production" - jut by reboot....

Feels like great plan. Maybe I should build a new server also using that plan. For my production system it is pain to realize, as I don't want downtimes. Maybe I will do disk to disk copy from system and use that as backup.

warpme wrote:Regarding 0.27 - I don't think You will have any problems with it. For me it is best release ever and working in my production without any issues.

BTW: I'm working on Minimyth2 project and hope soon I'll have something to offer here

Sounds superb!

www.minimyth.org

updated mm with 0.27

updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27

Re: updated mm with 0.27