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.


Topics - m3freak

Pages: [1] 2
1
Users / md RAID 1 not being auto mounted
« on: March 17, 2012, 12:54:25 am »
I had created a RAID 1 md device via LinuxMCE's admin interface, but it never behaved correctly when the core was rebooted.  Since I had already put data on it, I decided to stop the device, and then removed it from the interface.

I manually assembled the md device from the two 1 TB drives and put the config in /etc/mdadm/mdadm.conf:

Code: [Select]
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=a8280191:5f65eba2:bd9f1658:0a1d2015

I rebooted the core.  This time the raid device came up correctly.  LinuxMCE detected the raid and added it to the RAID list in the web interface with the status set to OK.

The problem is LinuxMCE has marked the two drives as REMOVED - wtf?!  I think this is the reason why the raid device isn't being auto mounted and why I'm not seeing the "new storage added" on my MD's onscreen orbiter.

The kernel says the device and the raid members are ok:

Code: [Select]
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb[0] sdc[1]
      976761472 blocks [2/2] [UU]
     
unused devices: <none>

Code: [Select]
/dev/md0:
        Version : 00.90
  Creation Time : Wed Feb  8 14:06:21 2012
     Raid Level : raid1
     Array Size : 976761472 (931.51 GiB 1000.20 GB)
  Used Dev Size : 976761472 (931.51 GiB 1000.20 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Mar 16 19:49:29 2012
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : a8280191:5f65eba2:bd9f1658:0a1d2015 (local to host dcerouter)
         Events : 0.30190

    Number   Major   Minor   RaidDevice State
       0       8       16        0      active sync   /dev/sdb
       1       8       32        1      active sync   /dev/sdc

How can I fix this?  Should I do some meddling in the DB?

2
Users / Onkyo TX-SR876 A/V receiver - need a custom template
« on: March 10, 2012, 02:47:15 am »
I didn't see a template for my Onkyo receiver, a TX-SR876.  The generic template for Onkyo/Integra A/V receivers doesn't work well for mine, not to mention not all of the inputs/ouputs are included.

I have a document describing the serial commands for a TX-SR875. I want to use it to build a new device template for my receiver since the 876 isn't all that different.  How should I go about it?  Am I supposed to copy an existing template or start new?  If I'm copying, how do I actually do that?  I poked around for a while and didn't see anything obvious on how to copy the existing Onkyo/Integra template.

3
Users / RAID 1 created via admin GUI behaving unexpectedly
« on: February 22, 2012, 05:44:14 pm »
I used LinuxMCE's admin interface to create a RAID 1 set out of two 1 TB drives: /dev/sdb1 and /dev/sdc1.

After LinuxMCE created the array, /dev/md0, formatted the drive and synchronized the array, I rebooted the core.  After the reboot, /dev/md0 was nowhere to be seen.  Instead, I saw /dev/md_d1.  In addition, LinuxMCE's admin page for RAID reported the array as having failed.

I stopped /dev/md_d1, and assembled /dev/md0.  /dev/md1 was back online with no errors or other issues.  The data on it was accessible again at the same location LinuxMCE had set up after auto detecting it the first time around.

I tried another reboot with the same results.

After fixing it by hand again, I took a peek at mdadm.conf and found it didn't have an entry for the array.  Why?  :: cries ::

One additional piece of info: even though the array is active and synchronized, LinuxMCE's admin page is reporting only /dev/sdb1 to be present.  If I look at the "Advanced" details for the array, the "No of disks" field has "1".

Something obviously didn't go right during the creation.  How can I fix this?

4
Users / Media Director no longer boots
« on: February 20, 2012, 03:56:42 pm »
My lone MD stopped booting a few days ago.  It still gets an IP, but when it comes to downloading the initrd and kernel, it bombs out.  Well, the actual order of fail is:

1. tries to download the kernel image that was built for it (can't)
2. then it moves on to the default (no go)
3. finally tries a local boot, but since there's no local install, the PXE boot stops.

I haven't done anything to the MD config itself.  I did however update the core.  Maybe the update did something.

I can see the tftp request on the core in /var/log/syslog.  The core answers properly (I think).  

What could be wrong?

5
Users / RAID 1 array doesn't survive reboots
« on: February 12, 2012, 04:40:06 pm »
In LinuxMCE 10.04, I created a RAID 1 array.  Things looked cool, so I copied some media to it.  I rebooted the core.  The RAID 1 array didn't come back, and LinuxMCE reported the array as failed.  Sweet!

I checked /proc, and instead of seeing md1, I saw md_d1.  WTF.

I'm pretty sure I can recover it - again.  Yes, it's failed twice, and both times was because of a reboot of the core.

I think this is a bug.  Where do I report this (though maybe the devs already know)?

6
Users / LMCE 10.04: Web orbiter buttons don't do anything
« on: February 11, 2012, 03:46:39 pm »
I created a web orbiter to be used from Firefox running on my desktop.  The generation appears to complete properly.

When I bring the orbiter up in my browser and then for example click on the media button, a little circle pops up and spins a couple of times, followed by a screen flash.  That's it.

Interesting.

If I change the skin, I lose buttons.  For example the media button never gets rendered.  Sometimes changing the skin doesn't actually change anything on the screen.  That is, I still see the old skin on the screen.

What gives?  :-[

7
Users / Tagging tv shows error
« on: February 11, 2012, 02:57:42 am »
So I ran auto  tagger to tag a TV show.  After I confirmed the episodes were identified properly, I clicked on the "OK" button or whatever it was to start the tagging and then this came up on the screen:

Duplicate entry '3353-0-0-0' for key 'PRIMARY'

I did a brief search and found this:

http://www.softwareprojects.com/resources/programming/t-how-to-fix-mysql-duplicate-entry-for-key-primary-o-1844.html

Is my DB hosed?

8
Users / Erase metadata
« on: February 11, 2012, 02:21:27 am »
I tried auto tagging some tv shows, but the results were mixed.  One show worked out fine - everything in the folder was tagged properly, pictures added, etc.  Another show is found properly, but when I apply the tags, only one episode gets tagged.  Nothing is done for the rest, and I can't figure out why.

I want start the tagging over for the tv show that's causing problem.  I can see how to delete attributes from the admin page, but one attribute for every single episode simple won't erase.  Every time I delete the attribute, the admin reports back it was deleted successfully, but the stupid thing never disappears from the screen.

I'm going to assume I can hit the DB directly to get rid of the info.  Does anyone know which tables I need to look at?  If I should avoid this, how should I go about trouble shooting the above problem?

I'm using 10.04.

9
Users / Can't connect to samba shares on 10.04
« on: February 09, 2012, 04:57:43 pm »
I'm using smbclient from a Fedora desktop to test connecting to the samba shares configured on my core.  So far, no luck. I've tried:

1. reseting the users's smb password (according to wiki)
2. restarted smb daemon (no errors)
3. checked the smb.conf for errors (non found)
4. tried connecting from external fedora PC and from core itself

The shares I tried connecting with include the ones that were configured when I installed the system, and the new one that was created for the RAID 1 array I setup through LinuxMCE's admin interface.

Is my smb.conf actually configured correctly?  Here it is:

Code: [Select]
## @FileType: Pluto Sectioned Config File ##
## @Version: 2 ##
## @KeepSections: ##
## @RemoveSections: ##

[global]
## BEGIN : Domain and Hostname
workgroup = LinuxMCE
server string = %h server (Samba %v)
## END : Domain and Hostname
smb ports = 139
log level = 2
invalid users = root
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
encrypt passwords = true
socket options = TCP_NODELAY
dns proxy = no
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .
username map = /etc/samba/usermap.txt
        unix extensions = no
        wide links = yes
security = user
########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;   printing = bsd
;   printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
   printing = cups
   printcap name = cups

[public]
comment = public files
browseable = yes
writable = yes
create mask = 0777
directory mask = 0777
path = /home/public/data
public = no

[home]
comment = shared home files
browsable = yes
writable = yes
## BEGIN : Home Hosts Allow
### END : Home Hosts Allow
path = /home
public = no
guest ok = no
force user = root
        force group = public
        create mask = 0774
        directory mask = 0775
        inherit acls = yes
        inherit uid = yes
        inherit owner = yes
        inherit permissions = yes

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

## BEGIN : User Shares


[ranbir]
comment = ranbir's private files
browseable = yes
writable = yes
create mask = 0770
directory mask = 0770
path = /home/user_1
public = no

## END : User Shares


## BEGIN : InternalStorageDevices


[Storage57$]
comment = Storage Device 57
browseable = yes
writable = yes
create mask = 0770
directory mask = 0770
path = /mnt/device/57
public = no
guest ok = no
force user = root
force group = root


[Storage60$]
comment = Storage Device 60
browseable = yes
writable = yes
create mask = 0770
directory mask = 0770
path = /mnt/device/60
public = no
guest ok = no
force user = root
force group = root

## END : InternalStorageDevices

I have no idea what Storage60$ is.



10
Users / Upgrade failing in 10.04
« on: February 06, 2012, 12:18:51 am »
I tried updating my 10.04 install, but it's failing with this error (snippet):

Code: [Select]
Bareword found where operator expected at /usr/pluto/bin/update2utf8.pl line 6, near "// We"
(Missing operator before We?)
syntax error at /usr/pluto/bin/update2utf8.pl line 6, near "// We try "
Execution of /usr/pluto/bin/update2utf8.pl aborted due to compilation errors.
dpkg: error processing pluto-system-database (--configure):
 subprocess installed post-installation script returned error exit status 255
dpkg: dependency problems prevent configuration of pluto-std-plugins:
 pluto-std-plugins depends on pluto-system-database (>= 2.0.0.45); however:
  Package pluto-system-database is not configured yet.
 pluto-std-plugins depends on pluto-system-database (<< 2.0.0.46); however:
  Package pluto-system-database is not configured yet.
dpkg: error processing pluto-std-plugins (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pluto-dcerouter:
 pluto-dcerouter depends on pluto-std-plugins (>= 2.0.0.45); however:
  Package pluto-std-plugins is not configured yet.
 pluto-dcerouter depends on pluto-std-plugins (<< 2.0.0.46); however:
  Package pluto-std-plugins is not configured yet.
 pluto-dcerouter depends on pluto-system-database (>= 2.0.0.45); however:
  Package pluto-system-database is not configured yet.
 pluto-dcerouter depends on pluto-system-database (<< 2.0.0.46); however:
  Package pluto-system-database is not configured yet.
dpkg: erNo apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                                  No apport report written because the error message indicates its a followup error from a previous failure.
              ror processing pluto-dcerouter (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pluto-system-database
 pluto-std-plugins
 pluto-dcerouter
E: Sub-process /usr/bin/dpkg returned an error code (1)

I ran 'apt-get upgrade' a couple of times - same result.  Any ideas on how I could fix this?

11
Users / HOW-TO: HDMI sound on a Jetway Mini-top (ION 2)
« on: February 05, 2012, 05:34:25 am »
I'm a busy guy.  It's been very, very hard for me to find the time to learn enough about the innards of LinuxMCE to tackle the problem of the non-working HDMI sound on my Jetway Mini-top.  However, a week ago after several months of wimpy twiddling and random bashing of the keyboard, I finally figured out how to get HDMI sound working in the crappy 10.04 release (note: I do not like Ubuntu, but don't take that to mean I don't like LinuxMCE.  I will be randomly raging against Upoontu, so don't cry).

I have no idea if what I'm about to spell out will work on the current stable LinuxMCE release. I gave up on it while ago because of stupidness (e.g. my second NIC not working without manually building a new driver).  I also pieced together most of what needed to be done from several different sources. However, figuring out the order and the repeated testing, plus some key pieces to the final solution were all my doing.  If I wasn't already very well experienced with Linux systems, I would have been completely lost.  Overall it was not fun, but man was I happy when it all came together.

So...

PRO TIP: make sure the Mini-top's (or whatever it is you're using for your MD) HDMI port is actually plugged into something and that something is powered ON!

NOTE: All these steps were performed on the MD after I logged into it via SSH.  I did not do a "chroot" to the MD's directory on the core (i.e. /usr/pluto/diskless/XX).

1. In /etc/modprobe.conf/blacklist, add at the bottom the following:
Code: [Select]
blacklist snd-usb-audio
This was important.  I needed to blacklist this module to prevent it from breaking the MD's boot process and to ensure ONLY the nvidia HDMI audio was enabled.

2. In /etc/modprobe.conf/alsa-base.conf, add this, again at the bottom of the file:
Code: [Select]
alias snd-card-0 snd-hda-intel
options snd-hda-intel enable_msi=0 probe_mask=0xfff2

This alias bullshit I pulled from memory....from way, way back in the early days of Fedora when I had to battle with alsa to get sound working.  I'm not sure it's actually needed here, but I put the crap in anyway.  The second line came from the xbmc forums and the xbmc wiki - so awesome.

3. Upgrade alsa.  I used this page as a guide:

http://monespaceperso.org/blog-en/2010/05/02/upgrade-alsa-1-0-23-on-ubuntu-lucid-lynx-10-04/

I only upgraded alsa-driver and alsa-libs. There's no need to update alsa-utils.

4. Reboot

5, Upgrade the nvidia drivers.  Nothing special to note here.

6. Reboot

7. Install this package:
Code: [Select]
apt-get install linux-backports-modules-alsa-$(uname -r)
This was the biggest piece of the puzzle.  Without this package, the nvidia soundcard would not be detected by alsa.  I have no idea how the shit I figured this crap out.  I think I read about it somewhere on the net.  I know for sure it wasn't at all in reference to LinuxMCE, the ION2 or HDMI sound.  FUCK!

8. Reboot

9. Edit, /usr/pluto/bin/AVWizard_AudioConnector.sh, like so:
Code: [Select]
#!/bin/bash

. /usr/pluto/bin/AVWizard-Common.sh
. /usr/pluto/bin/Utils.sh

Param="$1"
case "$Param" in
        'Analog Stereo')
                XineConfSet audio.output.speaker_arrangement 'Stereo 2.0' "$XineConf"
                XineConfSet audio.device.alsa_front_device plughw:0 "$XineConf"
                XineConfSet audio.device.alsa_default_device plughw:0 "$XineConf"
        ;;
        'SPDIF Coaxial'|'SPDIF Optical')
                XineConfSet audio.output.speaker_arrangement 'Pass Through' "$XineConf"
                XineConfSet audio.device.alsa_front_device asym_spdif "$XineConf"
                XineConfSet audio.device.alsa_default_device asym_spdif "$XineConf"
                XineConfSet audio.device.alsa_passthrough_device "iec958:AES0=0x6,AES1=0x82,AES2=0x0,AES3=0x2" "$XineConf"
        ;;
        'HDMI')
                XineConfSet audio.output.speaker_arrangement 'Pass Through' "$XineConf"
                #XineConfSet audio.device.alsa_front_device asym_hdmi "$XineConf"
                XineConfSet audio.device.alsa_front_device nvidia_hdmi "$XineConf"
                #XineConfSet audio.device.alsa_default_device asym_hdmi "$XineConf"
                XineConfSet audio.device.alsa_default_device nvidia_hdmi "$XineConf"
                XineConfSet audio.device.alsa_passthrough_device "hdmi:AES0=0x6,AES1=0x82,AES2=0x0,AES3=0x2" "$XineConf"
        ;;
esac
/usr/pluto/bin/SetupAudioVideo.sh

Makes sure Xine uses the nvidia HDMI card (configured below).

10. At the bottom of /usr/pluto/templates/asound.conf, add this:
Code: [Select]
pcm.nvidia_hdmi {
        type hw
        card 0
        device 3
}

This configures the HDMI "card" for use with alsa.

8. Edit, the Setup_AsoundConf() function in /usr/pluto/bin/SetupAudioVideo.sh like so:
Code: [Select]
Setup_AsoundConf()
{
        local AudioSetting="$1"
        local SoundCard

        SoundCard=$(GetDeviceData "$PK_Device" "$DEVICEDATA_Sound_Card"|cut -f2 -d";")
        SoundCard=$(TranslateSoundCard "$SoundCard")
        if [[ -z "$SoundCard" ]]; then
                SoundCard=0
        fi
        sed -r "s,%MAIN_CARD%,$SoundCard,g" /usr/pluto/templates/asound.conf >/etc/asound.conf

        case "$AudioSetting" in
                *[CO]*)
                        # audio setting is Coaxial or Optical, i.e. S/PDIF
                        #echo 'pcm.!default asym_spdif' >>/etc/asound.conf
                        echo 'pcm.!default nvidia_hdmi' >> /etc/asound.conf
                        EnableDigitalOutputs
                ;;
                *H*)
                        # audio setting is HDMI
                        #echo 'pcm.!default asym_hdmi' >>/etc/asound.conf
                        echo 'pcm.!default nvidia_hdmi' >> /etc/asound.conf
                        EnableDigitalOutputs
                ;;
                *)
                        # audio setting is Stereo or something unknown
                        echo 'pcm.!default asym_analog' >>/etc/asound.conf
                ;;
        esac
}

That makes the nvidia HDMI card configured in the previous step the default output for sound.

9. Reboot

When the MD came back up, "aplay -L" correctly reported the NVidia HDMI sound card, and because of the mask (in alsa-base.conf), only one soundcard was shown.  You should see the same.

Now everything works.  mp3s, MKVs, AVIs, stereo sound, multichannel, dolby, DTS, LPCM...you name it.  Sound over HDMI works flawlessly.  Also, my changes to a couple of the scripts have assured reboots won't adversely affect sound over HDMI.

The only problem is I'm sure a future update will likely blow some of my changes away.  I hope the devs can incorporate what I've done into the setup scripts, thereby truly automating this particular MD's LinuxMCE setup.

Oh, one final note: I'll make sure the wiki article has a better flow for the steps (a couple are out of logical order, though the way I wrote the above how-to won't prevent HDMI sound from being correctly setup).

I hope this helps someone!

12
Users / How much HD space do I need for Core + MDs?
« on: January 29, 2012, 09:51:59 pm »
I picked up an Intel 40GB SSD to use as the boot drive for my 10.04 Core.  At the moment I'm using an old 80GB IDE drive.  I want to make the drive swap because my testing of the Core is complete and since I'm mostly pleased with the results, I think it's time to move the OS bits to a better HD.

Before I rip open the box and install the SSD, I want to be sure the 40GB SSD is big enough.  My plans:

1. I'm going to have a separate md RAID 5 set (going to use an existing one from a Fedora 15 box) for media storage
2. Core + 2 MDs to start
3. Will add five more MDs down the road, maybe more

Can 40 GB accommodate that or should I get a bigger SSD?

13
Users / How the #@$# do I customize asound.conf?
« on: November 12, 2011, 06:21:55 pm »
I edited asound.conf in /usr/pluto/diskless/29/usr/pluto/templates, rebooted my MD, and still don't get any sound via the HDMI connection.  This is what the MD's asound.conf looks like now:

Code: [Select]
pcm_slave.spdif_convert48k {
pcm "spdif:%MAIN_CARD%"
rate 48000
}

pcm.spdif_playback {
type plug
slave spdif_convert48k
}

pcm_slave.hdmi_convert48k {
pcm "hdmi:%MAIN_CARD%"
rate 48000
}

pcm.hdmi_playback {
type plug
slave hdmi_convert48k
}

pcm.asym_spdif {
type asym
playback.pcm "spdif_playback"
capture.pcm "plughw:%MAIN_CARD%"
}

pcm.asym_hdmi {
type asym
playback.pcm "hdmi_playback"
capture.pcm "plughw:%MAIN_CARD%"
}

pcm.asym_analog {
type asym
playback.pcm "plug:dmix:%MAIN_CARD%"
capture.pcm "plughw:%MAIN_CARD%"
}

pcm.hdmi {
type hw
card 0
device 7
}

Can someone PLEASE tell what the hell to do?  Which file am I supposed to edit?  WTH am I supposed to put in it?  I can't find shit on the wiki, and nothing in the forums gives me a fix that survives reboot.

I admin massive Linux systems running a huge variety of applications and services, and yet LinuxMCE has completely stumped me.  WTF.  :(


14
Users / Customize /etc/asound.conf
« on: October 24, 2011, 02:36:12 am »
How do I customize /etc/asound.conf on my MDs so that the changes survive reboots?

The auto generated asound.conf doesn't give my any sound over HDMI.  This is what it looks like:

Code: [Select]
pcm_slave.spdif_convert48k {
pcm "spdif:0"
rate 48000
}

pcm.spdif_playback {
type plug
slave spdif_convert48k
}

pcm_slave.hdmi_convert48k {
pcm "hdmi:0"
rate 48000
}

pcm.hdmi_playback {
type plug
slave hdmi_convert48k
}

pcm.asym_spdif {
type asym
playback.pcm "spdif_playback"
capture.pcm "plughw:0"
}

pcm.asym_hdmi {
type asym
playback.pcm "hdmi_playback"
capture.pcm "plughw:0"
}

pcm.asym_analog {
type asym
playback.pcm "plug:dmix:0"
capture.pcm "plughw:0"
}
pcm.!default asym_hdmi

If I comment the "pcm.!default asym_hdmi" and put the following default lines in, sound over HDMI works:

Code: [Select]
pcm.!default {
type hw
card 0
device 7
}

So, how do I make that change stick?

15
Users / Media Director - grey screen, no sound
« on: August 22, 2011, 11:56:23 pm »
I have a Jetway Ecomini I'm planning to use as a Media Director.  I have it connected to my A/V receiver via HDMI.  I ran through the AV Wizard, and when it completed, I saw some large text on a grey background get printed to the TV.  Several seconds later the messages stopped and I'm now left with a mouse pointer and a grey background.  I think I should be able to see the onscreen orbiter at this point.  Any suggestions?

The other problem is when I ran the sound test (chose HDMI), I didn't hear anything.  In fact, my receiver actually reported it wasn't receiving any sound.  I guess that means the MD wasn't sending anything.  I had chosen analog audio before and that worked just fine.  I don't know why audio isn't working.

Pages: [1] 2