Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - S4Howie

Pages: [1] 2
Installation issues / Re: Video Card Recommendations?
« on: March 13, 2017, 09:48:16 pm »
I just want to say i have never had problems with any nvidia card install at either core ore client setup. I used old ones like 7300 and 7600GT. I use a GT210 atm in 1 MD which installed without any problems at first setup,screen was a PhillipsTV 1080i,in Audio/Video Wizard i set HDMI/1920x1080/60Hz in Audio Section choose HDMI too,there will be no sound then but its ok,later there is no isuess with sound, just mythtv needs some audio setting adjustments.

Another MD i have has Intel Graphic Chipset on board,setup was also no problem. Boot up for the first time into A/V Wizard,choose the wanted resolution,and everythings fine. Its running UI2 in 1080i aswell.

On my Core/Hybrid i have a intel Server Mainboard with a Matrox Graphic Chipset,even this showd me a picture from the very first install. Its just UI1 but it runs,resolution is 800x600 cause i dont really use it as an MD.

So i can advice everybody with a generic pc setup as md choose a nvidia 7600GT and newer over any other card if you want it working without issues. Or choose a mainboard with Intel Graphics onboard if you want a budget UI2 out of the box.


Installation issues / Re: update problems/mistakes made(solved)
« on: March 12, 2017, 10:32:10 pm »
posde that worked!!
Since i had deleted the MD i need to do following:

Step1: Setup new md,reload the core,let the md boot and update and reboot till its stuck in tftp boot then power off
Step2: re-link the older (3.x) init.rd and vmlinuz files and reboot
Step3: MD comes up again but shows no picture
Step4: apt-get install --reinstall linux-image-3.16.0-77-generic over core console and reboot
Step5: having a lot of joy seeing the MD boot again over pxe(but no picture no xserver)
Step6: since i have a nvidia card installing the latest nvdia package and driver reboot several times
Step7: drink a beer and enjoy your reborn MD with showing picture again

Thank you once again posde,i would be lost without you guys.
awesome work and support,keep LinuxMCE alive pls

Installation issues / Re: update problems/mistakes made
« on: March 09, 2017, 09:26:20 pm »
Thanks for the fast awnsers.

@phenigma build is 14.04 Version: on the core

   pluto.conf from core is:
PK_Device = 1
MySqlDBName = pluto_main
Display = 0
PlutoVersion =
LogLevels = 1,5,7,8
AutostartMedia = 1
AVWizardDone = 1
Bookmark_Media = 4,5
RA_CheckRemotePort = 1
MySqlHost = localhost
MySqlUser = root
MySqlPassword =
DCERouter = localhost
MySqlPort = 3306
DCERouterPort = 3450
Activation_Code = 1111
PK_Installation = 1047743
PK_Users = 1
PK_Distro = 21
UseVideoWizard = 1
AutostartCore = 1
LTS_HES = -lts-utopic
FirstBoot = false
TimeZoneSet = 1
DesktopActivated = 1
OfflineMode = false
AVWizardOverride = 0
DVDKeysCache = /home/.dvdcss

@posde Yes excactly the newer init.rd is a bit over 32 MB,looks like you are all right with this.
             But i dont understand how to switch back now?

Thank you

Installation issues / update problems/mistakes made(solved)
« on: March 09, 2017, 05:10:55 am »
In a nighly crazyness i acidently applied the LTS security updates on 1 MD.It told me Warning i should apply security updates to my hardware stack to get LTS support.But now this MD is somekind of broken. If i want to boot up it loads the vmlinuz but then it
stoping and telling me Could not find ramdisk image;   XX/initrd.img

If i look into the tftp folder the symlinks are there for initrd.img. I tried to copy the symlinks from a folder of another MD then the broken MD boots up but its then updating itself again and rebooting and then again telling Could not find ramdisk image;   XX/initrd.img

so i went into LinuxMCE admin to MD Section and rebuild the image. The rebuild MD boots up but its then updating itself again and rebooting and then again telling Could not find ramdisk image;   XX/initrd.img

I even deleted the MD,setup a new with all new Device names. It boots up applying itself updates reboots and same again Could not find ramdisk image;   XX/initrd.img.

Is there a way to get it back normal?Why even after delete and new setup it seems to apply the security updates?How can i stop that now?And just let it do the normal updates when i setup a new 1 or rebuild the image?I hope there is a way.

Thanks so far

Installation issues / Re: Problem with switching OS on MD
« on: February 26, 2017, 04:19:59 pm »
Thank you posde,i was very busy last days,but finaly i could get my MD back up running,with your help.

As for the Gitlab thing,I am not really familiar with that,never used it befor. The link you provide ask me for Username/password.
But there is no sign up Button just sign in. I was going then to the Gitlab site and made a useracc there,but it wont let me log in with that
Username on the LinuxMCE Git. I dont know further now. How to get a proper Username?


Installation issues / Re: Diskless Client MythTV Setup
« on: February 26, 2017, 03:28:02 pm »
It is quite a while since i setup my system,but as far as i remember i have not had problems with mythtv setup on a client,in the Language screen you just choose the Language you want to have and on the next screen you can then enter the mythcore IP and the Database you want to use and the password for it. End the settings and mythtv reloads and everything is fine. The Database name and password you can see in the cores mythtv setup.
Hope this helps for your next client setup.


Installation issues / Problem with switching OS on MD
« on: February 18, 2017, 12:38:42 am »
I have 1 MD using with an internal HDD and Windows 10 on it,so far it was never a problem to switch between the MD or Windows 10. The MD is configurated to boot over Network and when its up and running,you hit the Start as OS on Harddrive Button in Orbiter Power Section and the MD restarts but the PXE Bootfile it gets from the Core then lets it jump over Network Boot and boots up from Harddrive the Windows 10. If u want to switch back u hit the Boot as MD Button in an Orbiter.Then restart your Windows and the MD comes back again cause now the PXE Bootfile let it boot over Network again. But here is the problem the MD stays in 1 Mode until u switch and in some of the last updates i cant tell which one exact im sry the Boot up as MD Button is not shown anymore in all Orbiters at my setup 14.04 latest updates.
Can someone help,would be nice to have my MD boot up again,it is the 1 im using most in my living room and now its stuck in Windows10 mode.

Thanks Howie

Installation issues / Re: mythtv probleme
« on: March 28, 2016, 01:35:53 am »
Sounds like you have just 1 capture card installed which provide you 2 Encoders. This is happening at my install with a WinTV Nexus-S DVB-S Capture Card.
You can choose in mythsetup how many recoders that capture card is providing and the default is 2.
But Encoder2 isnt a fully Encoder when Encoder 1 is in use,it can only provide the channels which come on the same transponder from DVB-S.

I have 2x capture cards installed,1 in the core and 1 in a md.But i cant get the 1 in the md to run.I have prober firmware installed from linuxtv and i can choose it in the setup as new card,i can choose the LNB and have a lock on a channel scan.But in mythweb statuspage the Encoder is always listed as currently not connected.


Installation issues / Re: 14.04 Raid Array Damaged
« on: March 05, 2016, 07:20:14 pm »
Because of the speed i wantto buy a faster machine anyway soon. But for now i im impressed how good it works from a USB Stick.I have just LinuxMCE installed there,while Mythtv records now to the internal HDD.So no problem having 2 recodings and watching Live TV at the same time.

For now my Mediadatabase isnt that big so it might work for some time.My Media is stored on a Windows Server and shared per Samba,the USB stick will not been used for storing any Media.


And i forgot to say the Mythweb address changed to ---> dcerouter/html/mythweb


Hi maverik,

i dont know if i can help you,but i saw a error in your last post.

<Directory "/var/www/html/mythweb/data">
Options +FollowSymLinks +IncludesNoExec
<Directory "var/www/hml/mythweb" >

the last directory is wrong. It should be "var/www/html/mythweb",there is a t missing.Maybe its a typo or something wrong at your conf.


Installation issues / Re: 14.04 Raid Array Damaged
« on: March 05, 2016, 02:58:01 pm »
What do you mean with bringing the system to a crawl?

Do you mean the system makes to many reads and writes on the USB that the Stick will be damaged very soon?Or do you mean the USB port will be in a to heavy load all the time?

I installed it for testing yet on USB,and it running fine so far.I choosed a 64bg 130MB/s access rate Stick,i installed 14/04 first and did a net install over it.In my Bios i choosed to handle the stick as USB-HDD and it is first in Boot,so i could also install the MBR just on the Stick,Grub is installed nice there.I can now switch between HDD and USB Boot just by changing the first Boot device in Bios.And because of the 2 seperate Installs and MBRs it always chooses the right one as default.Very nice.

Im curious about how long that will live on a USB Stick.


Installation issues / Re: 14.04 Raid Array Damaged
« on: March 04, 2016, 08:46:06 pm »
I can not test this atm, i realized the cpu and memory of my old PC i was running the Core is way to slow to handle all my MDs in a decent way.I waited for hours just to regen 1 Orbiter. But it was my testing Object anyway. I have a other Core running which is way faster,i want to install 14.04 on a USB Stick there to have the internal HDD just been busy with TV Recoding and no System Load.So far i have the system running on the internal HDD an i see some little stucks from time to time when i watch Live TV in 2 or 3 MDs.BTW its just a green Seagate.5300UpM.

Im going to buy 1 other PC soon,a decent machine which can handle what i need fast.In there im going to install a Raid again.Until than this project is sleeping.


Installation issues / Re: 14.04 Raid Array Damaged
« on: March 04, 2016, 02:38:20 pm »
Hi phenigma,thank you for the information of the bug. I think im far away from knowing all to help with patches in near future. I know just the Linux Basics and Google is my best friend here too,i dont have knowledge of any writing. I am imperessed of myself how far i have even come with 14.04. You guys made a fantastic job.Thank you


Installation issues / 14.04 Raid Array Damaged
« on: March 03, 2016, 09:43:41 pm »
I created a raid array in my System. But if i take a look at the Webadmin Raid Section it tells me the Raid is Damaged.

I think everything is correct all drives are there,all are formated and partionated.

Here is fdisk -l:

dcerouter_1047678:~# fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
81 heads, 63 sectors/track, 191411 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd545b967

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048   976773167   488385560   83  Linux

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
81 heads, 63 sectors/track, 191411 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x663227a6

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048   976773167   488385560   83  Linux

Disk /dev/md127: 1000.2 GB, 1000213577728 bytes
2 heads, 4 sectors/track, 244192768 cylinders, total 1953542144 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0xc1649732

      Device Boot      Start         End      Blocks   Id  System
/dev/md127p1            2048  1953542143   976770048   83  Linux

Disk /dev/sdc: 124.2 GB, 124218507264 bytes
255 heads, 63 sectors/track, 15102 cylinders, total 242614272 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000001

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *          63   219303314   109651626   83  Linux
/dev/sdc2       219303315   242613629    11655157+  82  Linux swap / Solaris

My Sytem is:
/sda is 1 Raid Disk
/sdb is 2 Raid Disk
/md127 is the raid
/sdc is the systemdisk(not in raid)

Mdadm detail tells me:
dcerouter_1047678:~# mdadm --detail /dev/md127
mdadm: excess program on PROGRAM line: /usr/pluto/bin/ - ignored
        Version : 1.2
  Creation Time : Thu Mar  3 20:07:05 2016
     Raid Level : raid0
     Array Size : 976771072 (931.52 GiB 1000.21 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Thu Mar  3 20:07:05 2016
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

     Chunk Size : 512K

           Name : dcerouter:0  (local to host dcerouter)
           UUID : 212d1c96:296dc5ec:a9969cfb:8db856e7
         Events : 0

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1

But if i take a look in the Webadmin it tells me Raid is Damaged.39   CORE   Storage   Software Raid 0   /dev/md127p1   2   931.52GiB   DAMAGED
What is wrong?


Pages: [1] 2