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 - m3freak

Pages: 1 ... 4 5 [6] 7 8 9
76
Users / Re: News: Linuxmce 0810 Final is released
« on: September 13, 2011, 02:13:23 am »
Should I reinstall or will a doing an update and then upgrade be enough? (I've been running the RC...well, I have the RC installed...I don't have a working MD yet)

77
Users / Re: another hdmi audio issue?
« on: September 11, 2011, 08:15:07 pm »
help... hdmi still not working... alsamixer shows "Nvidia GPU 0b HDMI/DP", but not as default i have to hit F6 to see that card and everything is unmuted... Ive installed the lastest nvidia drivers.

Shouldnt alsamixer show HDA NVidia first instead of HDA Intel?

I can't get HDMI audio working on MD either.  My MD has an ION 2.  My aplay output looks similar to yours.  My alsamixer says nothing us muted, but the volume is at 0.  I can't turn it up - it just refuses to budge from 0.

The wiki instructions you mentioned don't make any sense, at all.  I bet the person that wrote them was using a GUI, but neglected to mention it in the wiki article.

All I can think of to try next is to update the nvidia drivers.

78
Users / Re: Media Director - grey screen, no sound
« on: August 23, 2011, 04:02:11 am »
I was wrong about the BIOS - there is no option for disabling HDMI audio there.  So, it's just not working because I'm likely missing the needed module.

I took a look at the wiki page about nvidia audio.  My MD does not output the same info:

Code: [Select]
lspci -vv

01:00.1 Audio device: nVidia Corporation Device 0be3 (rev a1)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 10
Region 0: Memory at fe97c000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [60] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000  Data: 0000
Capabilities: [78] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Latency L0 <512ns, L1 <1us
ClockPM+ Suprise- LLActRep- BwNot-
LnkCtl: ASPM L0s L1 Enabled; RCB 128 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-

Code: [Select]
aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: default [USB PnP Sound Device          ], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Code: [Select]
aplay -L

front:CARD=default,DEV=0
    USB PnP Sound Device          , USB Audio
    Front speakers
surround40:CARD=default,DEV=0
    USB PnP Sound Device          , USB Audio
    4.0 Surround output to Front and Rear speakers
surround41:CARD=default,DEV=0
    USB PnP Sound Device          , USB Audio
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=default,DEV=0
    USB PnP Sound Device          , USB Audio
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=default,DEV=0
    USB PnP Sound Device          , USB Audio
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=default,DEV=0
    USB PnP Sound Device          , USB Audio
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=default,DEV=0
    USB PnP Sound Device          , USB Audio
    IEC958 (S/PDIF) Digital Audio Output
null
    Discard all samples (playback) or generate zero samples (capture)

The alsamixer doesn't show anything muted.


79
Users / Re: NEWS: rc Time
« on: August 23, 2011, 02:33:07 am »
apt-get update and apt-get upgrade brings you to rc1 level

I did this.  The update appeared to complete without issue.  I'll see if things break for me, but at the moment I don't have a complete system configured anyway. :/

80
Users / Re: Media Director - grey screen, no sound
« on: August 23, 2011, 01:22:48 am »
After letting the MD sit for over two hours, I rebooted the bloody thing.  This time, after the same bit of text messages were flashed on the TV, I saw a "regenerating orbiter" message and the percentage completed.  The number went up and down a few times, but eventually a config screen of some type popped up.  It looks like it's for audio and video.

I think a video is supposed to be playing in the black box on the screen, but I don't see anything.  I also still don't have any audio.  However, I think I might HDMI audio disabled in the BIOS. I'm going to reboot the MD and check.

81
Users / Re: Media Director - grey screen, no sound
« on: August 23, 2011, 12:27:30 am »
I think you may have two problems:

1.  An orbiter, especially on a low power machine can take quite a while to regenerate.  I would wait a while (a good while).

I didn't know I'd have to wait.  I didn't see any messages saying that I should wait, either.  I have seen in the wiki that the Web Orbiter could take a while to generate.  Having said that, I don't see anything running on the MD or on the Core that would indicate the onscreen orbiter is being generated.

2.  with regards to sound I would see if the digital channel in ALSA is muted, sometimes this happens. (try the 'unmuting channels' section of http://wiki.linuxmce.org/index.php/Audio_over_HDMI

I'll check that.

One other thing that came to mind was with regard to AV wizard, I had to pick HDMI 2 to get mine to work because HDMI 1 is DVI

I chose DVI/HDMI 2.  The "Connector" field for the MD in the admin GUI says "DVI-2" was selected.  However, for sound, I see an "S".  Does that mean Stereo?  What should it be for HDMI audio?

Good Luck
[/quote]

82
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.

83
Users / Re: 0810 Web oorbiter - no buttons!!
« on: August 04, 2011, 07:03:07 pm »
hmm... Well I'm all out of ideas.  I've had my fair share of problems with LMCE but I can say this was one thing that just worked.  The only time I get what you're getting is when I try to access the orbiter while it is being regenerated.

You may have done this already and it maybe pointless but at this point I would delete the orbiter, reload, restart the core, create the orbiter, follow the progress in the orbiter page, give it another ten minutes after that has completed, reload again, restart the core, then try again. 

Sorry dude...

I'll give all of that a go.  And, no worries - I'll just reinstall.  My previous MD problems were fixed after moving to a new snapshot.   Maybe I have to do that again for the orbiters.   :-\

84
Users / Re: 0810 Web oorbiter - no buttons!!
« on: August 04, 2011, 05:43:16 pm »
I just noticed your log changed.  The first one was no route to host which is basically a bad address...usually.  The second is different.  You're hitting the core but you're being rejected.

portmapper is refusing connections. The exports look okay to me:

Code: [Select]
## BEGIN : InternalStorageDevices

## END : InternalStorageDevices


## BEGIN : CommonDiskless

/home                   192.168.80.0/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/orbiter      192.168.80.0/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/keys         192.168.80.0/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/deb-cache    192.168.80.0/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/var          192.168.80.0/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/var/spool/asterisk     192.168.80.0/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)

## END : CommonDiskless


## BEGIN : DisklessMDRoots

## END : DisklessMDRoots

nfs and portmapper are running.  Here's the output of "rpcinfo -p":

Code: [Select]
program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100004    2   udp    647  ypserv
    100004    1   udp    647  ypserv
    100004    2   tcp    648  ypserv
    100004    1   tcp    648  ypserv
    100009    1   udp    650  yppasswdd
 600100069    1   udp    653  fypxfrd
 600100069    1   tcp    654  fypxfrd
    100024    1   udp  38766  status
    100024    1   tcp  52276  status
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100021    1   udp  41824  nlockmgr
    100021    3   udp  41824  nlockmgr
    100021    4   udp  41824  nlockmgr
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100021    1   tcp  40917  nlockmgr
    100021    3   tcp  40917  nlockmgr
    100021    4   tcp  40917  nlockmgr
    100005    1   udp  36377  mountd
    100005    1   tcp  47148  mountd
    100005    2   udp  36377  mountd
    100005    2   tcp  47148  mountd
    100005    3   udp  36377  mountd
    100005    3   tcp  47148  mountd

I'm thinking authentication but it's unlikely, especially since the page loads.  So my second thought it the firewall.  Since you can ping the core which kind of indicated the firewall is down, try changing the port for the proxy orbiter.  Try 3462, but I personally would jump to 3468 and work my way backwards until it broke again.

Tried several different port numbers - no change.

  Although with the firewall down the core shouldn't be rejecting packets sent to any port.  That forces the question... Are you certain you disabled the firewall?  I'm with Purps, plug that PC into the LMCE network and see what happens. 

Yes, firewall is definitely disabled.  I'm assuming the web admin for the firewall isn't lying. :)

85
Users / Re: 0810 Web oorbiter - no buttons!!
« on: August 04, 2011, 04:48:42 pm »
Yes. You can create one straight away, regardless of what media/rooms are present. You need at least one room of course, but you'll always have that because that's where the core is!

Good to know.

Incidentally, you can select a room for the orbiter in web admin, as this changes the default room for that orbiter, but this isn't necessary for a working orbiter.

I wasn't sure about this either.  I'll leave this out for now then.  However, if I did want to set the room, would I do it for the parent device (Generic Web Orbiter), or the child device (Proxy Orbiter), or both?

86
Users / Re: 0810 Web oorbiter - no buttons!!
« on: August 04, 2011, 04:46:38 pm »
Did you TRY plugging a PC or device into LMCE's internal network? I'm not clever enough to explain why it might not be working with your current network setup, but in the name of diagnosing the problem, it would be an idea to try this.

Tried - exact same result.  The log stayed the same, too.

FYI: the laptop I used was assigned the IP 192.168.80.130.

87
Users / Re: 0810 Web oorbiter - no buttons!!
« on: August 04, 2011, 02:15:47 pm »
Did you TRY plugging a PC or device into LMCE's internal network? I'm not clever enough to explain why it might not be working with your current network setup, but in the name of diagnosing the problem, it would be an idea to try this.

No.  I'll try right now.

Question: can a Web Orbiter be created without having done anything else, such as defining rooms, adding media, etc.?  I don't know if the icons are created based on how my system is currently configured.

88
Users / Re: 0810 Web oorbiter - no buttons!!
« on: August 04, 2011, 02:56:28 am »
Did you change the name of your core to core or are you using DNS to resolve that name? 

"core" is in DNS.  I left the hostname on the core alone (dcerouter).

I'm not accusing you of randomly changing things, but from my experience it was the things that seemed insignificant that caused the most problems.  I'm pretty sure if you changed the name of your core you'll have a problem loading the xp orbiter... I think...

Then I wonder what I may have done.

I still can't get the web orbiter to work. I've regenerated it 30 times.

89
Users / Re: 0810 Web oorbiter - no buttons!!
« on: August 03, 2011, 11:54:25 pm »
I'm not sure what all this IP talk is about either. The machine itself will have an IP associated with it, of course, but the orbiters are independent of that, are they not? After you have entered the orbiter URL, and logged in, you can choose any web orbiter you have created.

Cheers,
Matt.

I'm confused, too.  I don't know why the Web Orbiter would get an IP.  I was scratching my head about that one.

So, I've recreated the Web Orbiter.  The IPs that were being added aren't now.  I think I know what may have triggered the weird behaviour before, but it's just speculation on my part, so I'll leave it out of this thread for now.

I browsed to the web orbiter's URL which in my case is http://core/linuxmce-admin/weborbiter.php, logged in, and selected the only Web Orbiter I have so far in my system. Once again, my screen is blank except for some buttons (Home, Back, Refresh, Exit, Logout).  Also, /var/log/pluto/0_web_orbiter.log has this, over and over again:

03-08-2011 17:39:37
Attempting to create socket on host 192.168.80.1 port 3461 ... OK.
socket_connect() failed.
Reason: (111) Connection refused
Closing socket ... OK.

I'm going to guess a service that should be running isn't.  Or, something else is broken.

BTW, I'm not randomly changing things or doing anything else odd.  I'm following the wiki articles for the few things I've tried to do so far.

90
Users / Re: 0810 Web oorbiter - no buttons!!
« on: August 03, 2011, 11:22:12 pm »
I don't know, someone correct me if i'm wrong, but I don't think you configured the proxy orbiter correctly.  My web orbiters don't  have IP addresses assigned to them and they all work just fine.  Did you follow these instructions? http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0

Don't forget rule number 1.

I forgot rule number 1.  No, seriously....I forgot it.  RAM fail.  (this is where you laugh)

I did follow those instructions.  I'm recreating the web orbiter now.  I deleted the old one.  Let's see if things work out any differently now.

Pages: 1 ... 4 5 [6] 7 8 9