Messages

Any ideas?

Bummer! I was hopeful there you had...I had tried several things myself but to no avail...(I'm on the ASUS M3N78-EM)

Ideas? Sure I have a rock solid one I'm currently implementing... to wait for 0810 

R

LOL, looks like I'm doing the same at the moment - is the issue you are having the same - ie. you can see the device in aplay -l and so on but still no sound?

...
After that it worked fine, I can't say what caused it
...

Paul: Just to confirm...Are you saying that you got audio over HDMI working?

Hi Ray,

No, I have not got HDMI audio working - sorry for the confusion, we were referring to a problem I was having in another thread.

Any ideas?

Hey Bitmonkey !

Maybe you can help me out...

I got the same problems on my md´s now as you wrote in another thread..

Only Floorplan is shown...

could you tell my how you got it working again..

Cheers
Bodi79

Sorry to have to tell you this, but I worked at it for a while and eventually ended up reinstalling my core. After that it worked fine, I can't say what caused it, but if it's happening on multiple MDs for you after working before I guess it might be worth trying to debug further, I capitulated and decided to reinstall the lot since it wasn't a huge problem for me to do that as nothing was working yet anyway - hope you find an easier fix.

Paul

Hey Bitmonkey !

I´ll do some more research on your Mainboard, maybe i´ll find something.

Did you check that the Alsa Upgrade sticked.. and the Nvidia Version is really 185.. cause i didn´t get any Audio before that at all..

Just curious..

Something else.. is it an MD or Core?

Bodi79

Hi, Thanks for getting back.

It's an MD, it's netbooting from the core.

To get the alsa upgrade to stick I had to install locate, find all the instances of nvidia.ko and delete them. Unless I did that cat /proc/drivers/nvidia/version would show 180.11 even after a seemingly successful upgrade.

Curiously enough the HDMI audio would show up in aplay -l even though it seemed as though the newer drivers had not installed - at first I didn't even notice that 180.11 was being reported as the version. Unfortunately I can't remember if the HDMI audio device showed up before I ever tried an upgrade, so perhaps this is expected with 180.11 and it just doesn't work properly, or otoh perhaps some odd combination of new and old drivers was installed, but I can definitely report that at some point I had a HDMI audio device showing in aplay -l and IEC958 mixers showing in alsamixer whilst cat /proc/drivers/nvidia/version was still showing the original 180.11 version. Deleting all the old modules until modprobe nvidia failed sorted it out though, and after that I installed using the nvidia .run file and now cat /proc/drivers/nvidia/version reports the expected new 185.foo.bar version number.

Paul

Hi,

Thanks for the reply.

My motherboard is a Gigabyte GA-M85M-US2H, I can't find any option in the BIOS regarding codecs, only the option to turn on or off the onboard HDMI.

Paul

I am having trouble with HDMI audio - I initially ran the AVWizard, had no audio despite selecting HDMI, pretty much expected this since I'd read about needing to upgrade nvidia drivers and alsa. I have upgraded nvidia drivers to 185.18.29 and alsa to 1.0.20, then I re-tried the AVWizard, still no sound. Went to a command line and did some testing with aplay can't get any sound, although to me everything looks OK using the tests/troubleshooting steps I've found here and on other forums regarding getting this working.

My motherboard has onboard NVidia, with HDMI out and can do audio over HDMI (audio over hdmi works fine with the same setup under WinXP, so the hardware is definitely working).

I am trying aplay -Dplughw:0,3 /usr/share/sounds/foo.bar which returns "Playing raw data foo.bar : unsigned 8 bit, rate 8000 Hz, Mono
It looks like it should be playing but nothing is heard from the speakers on the TV.

alsamixer shows various channels - master, pcm, front and center are all unmuted and set to high settings, IEC958, IEC958 D and IEC958 1 are present, they are not muted, their volumes are set to 00 and are not adjustable - I presume this is normal since they are digital outputs?

aplay -l shows:
Card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
Subdevices 1/1
Subdevice #0: subdevice #0

Surely that's the correct device, and when I aplay to hw:0,3 it should just feed the digital audio straight to that output, but doesn't seem to work.

Any ideas?

Thanks for the reply, have tried and no luck, so I'm going to rebuild my core.

thanks for the help.

Thanks for the reply, but I have already tried deleting and rebuilding the MD once - I will try again anyway and report back once that's done.

I had an idea - there is another thread here where I was having problems with media not being detected by the core due to the folder structure on my share: http://forum.linuxmce.org/index.php?topic=8600.0

I wonder if this is something to do with it - I only just noticed the reply on that thread by colinjones about debugging the autodetection so I will take a look at that later today, however for now it would help if you could clarify if my folders look ok to you. The server is a linux box running samba. I have a share called media which the core sees, the folders within it are;

public/data/audio/
public/data/pictures/
public/data/video/
public/data/pvr
user_1/data/audio
user_1/data/pictures
user_1/data/video
user_1/data/pvr
user_2/data/audio
etc.

for user_1, user_2 and user_3.


Does this look right?

Also, I wonder if it's possible to get these user_1, user_2 etc. directories to have the users names for easy recognition rather than the current generic names? Would I just alter the symlinks in the users home directories on the core? Would I also have to alter the symlinks in the MD images in /usr/pluto/diskless/ (I haven't actually checked if there _are_ symlinks in the diskless images, perhaps users mount their home directories from the core?)

Since I've never had a working install it's difficult for me to tell if this is a major problem or not - it seems like it could be 2 minutes of updating symlinks or otoh lots could be broken and I wouldn't know the difference.

Perhaps, of course, I am barking up the wrong tree and it has nothing to do with the folders, since the core can see the media?

Hi,

Just to clarify.

On the MD when you goto Menu no Floorplan, Manage Drives, Playlists, Pictures, Audio, Video, TV submenu appears?

And you have rebooted the MD?

Yes, that's right - when hovering over anything other than media the submenu for that item appears. Only for media does nothing appear. I have rebooted the MD, regen'd the orbiter and rebooted the core as well.

Thanks for the replies guys.

It didn't work at first, for some reason I had to fully reboot the core before I could regen the orbiter (it just wouldn't respond in the web interface, nothing happened when I clicked the button, I waited 20 minutes and the MD still had the grey screen on boot). After a reboot of the core it has worked though.

However I now have a new problem - no media showing in the orbiter. It just shows the media button but if you hover over or click on it no menu appears. All the other menus lights/climate/security etc. look fine and I can see the sample photos in the background of the UI, but have no access to my media. All the media is accessible from the hybrid/core UI fine. Any ideas?

thanks

Hi,

I just installed an MD, the mainboard is as ; http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=3081 and the graphics is an onboard Nvidia 8100.

Netboot install goes fine, I have no problem running the AV wizard and everything seems to set up OK, but then after the AVWizard the machine just hangs at a grey screen with a mouse pointer, as though X is starting but nothing is starting after that. Rebooting just gives more of the same.

Here's the xorg.conf from the MD;

Section "ServerLayout"         Identifier      "XFree86 Configured"         Screen    0     "Screen0"       0 0         InputDevice     "Mouse0"        "CorePointer"         InputDevice     "Keyboard0"     "CoreKeyboard" EndSection Section "Files" #       RgbPath         "/usr/X11R6/lib/X11/rgb"         ModulePath      "/usr/lib/xorg/modules"         FontPath        "/usr/share/fonts/X11"         FontPath        "/usr/X11R6/lib/X11/fonts/misc/"         FontPath        "/usr/X11R6/lib/X11/fonts/Speedo/"         FontPath        "/usr/X11R6/lib/X11/fonts/Type1/"         FontPath        "/usr/X11R6/lib/X11/fonts/CID/"         FontPath        "/usr/X11R6/lib/X11/fonts/75dpi/"         FontPath        "/usr/X11R6/lib/X11/fonts/100dpi/" EndSection Section "Module"         Load    "dbe"         Load    "extmod"         Load    "record"         Load    "xtrap"         Load    "speedo"         Load    "type1"         Load    "glx"         Load    "int10"         Load    "v4l" EndSection Section "InputDevice"         Identifier      "Mouse0"         Driver          "mouse"         Option          "Protocol"              "auto"         Option          "Device"                "/dev/input/mice"         Option          "ZAxisMapping"  "4 5" EndSection Section "Monitor"         Identifier      "Monitor0"         VendorName      "Unknown Monitor Vendor"         ModelName       "Unknown Monitor Model"         Modeline        "1920x1080" 148.5 1920 1960 2016 2200 1080 1082 1088 1125         HorizSync       20-500         VertRefresh     59-61 EndSection Section "Device"         ### Available Driver options are:-         ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",         ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"         ### [arg]: arg optional         #Option         "NoAccel"                               # [<bool>]         #Option         "SWcursor"                              # [<bool>]         #Option         "ColorKey"                              # <i>         #Option         "CacheLines"                    # <i>         #Option         "Dac6Bit"                               # [<bool>]         #Option         "DRI"                                   # [<bool>]         #Option         "NoDDC"                                 # [<bool>]         #Option         "ShowCache"                             # [<bool>]         #Option         "XvMCSurfaces"                  # <i>         Identifier      "Card0"         Driver          "nvidia"         VendorName      "Unknown Vendor Name"         BoardName       "Unknown Board Name"         Option          "LinearAlloc"           "16384"         #BusID          "PCI:0:2:0" #       Option          "NoDDC"                         "true"         Option "XvmcUsesTextures" "true"         Option "renderAccel" "true"         Option "NoDDCValue"         Option "UseEDID" "false"         Option "ExactModeTimingsDVI" "true"         Option "NoLogo" "true"         Option "NoBandWidthTest" "true"         Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"         Option "DynamicTwinView" "false"         Option "UseEvents" "true"         Option "AllowGLXWithComposite" "true"         Option "AddARGBGLXVisuals" "true"         Option          "ConnectedMonitor" "DFP" EndSection Section "Screen"         Identifier      "Screen0"         Device          "Card0"         Monitor         "Monitor0"         DefaultDepth    24         SubSection "Display"                 Modes           "1920x1080"                 Virtual         1920 1080         EndSubSection         Option "XvmcUsesTextures" "true"         Option "renderAccel" "true"         Option "NoDDCValue"         Option "UseEDID" "false"         Option "ExactModeTimingsDVI" "true"         Option "NoLogo" "true"         Option "NoBandWidthTest" "true"         Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"         Option "DynamicTwinView" "false"         Option "UseEvents" "true"         Option "AllowGLXWithComposite" "true"         Option "AddARGBGLXVisuals" "true"         Option  "TVStandard"    "1080p" EndSection Section "ServerFlags"         Option  "AllowMouseOpenFail"    "true"         Option  "AutoAddDevices"        "false"         Option  "BlankTime"             "0"         Option  "StandbyTime"   "0"         Option  "SuspendTime"   "0"         Option  "OffTime"               "0"         Option  "AIGLX"                 "Off" EndSection Section "ServerFlags"         Option "AutoAddDevices" "False" EndSection Section "ServerFlags"         Option "AutoAddDevices" "False" EndSection Section "ServerFlags"         Option "AutoAddDevices" "False" EndSection Section "ServerFlags"         Option "AutoAddDevices" "False" EndSection Section "ServerFlags"         Option "AutoAddDevices" "False" EndSection Section "Extensions"         Option "Composite" "true"         Option "RENDER" "true" EndSection Section "ServerFlags"         Option "AutoAddDevices" "False" EndSection

Any pointers?

thanks

Thanks for the replies - I cracked it, it's just that the directory structure I had manually had to set up was wrong (no data folder, just pictures/videos etc under username) - odd that mce didn't create it, but it works now so thanks.

Paul

To clarify, this is a completely standard setup - two nics, mce being firewall, dhcp, gateway etc.
I have changed _nothing_ about the network setup.

hmm.

Following on from my previous post about storage, I took the advice of posters here and went for a plain samba share. I created my share but linuxmce did not auto detect it, so I followed the advice at http://wiki.linuxmce.org/index.php/Howto:_Using_Network_Shares and manually added the file server as a child device of the core, I then did sudo /usr/pluto/bin/Configure_1837.sh -d <device number> to get the server scanned and as expected the orbiter popped up messages asking me what I wanted to use the share for, I selected to use it and use the linuxmce directory structure, I then entered the username and password to use.

I waited a while but no directory structure was created, so I manually created a pictures directory and put some pictures in there, but nothing has been detected by linuxmce - i've reloaded the router and rebooted the core.

I've tested connecting by mounting the volume from the core and it works fine, I've checked that I typed the username and password correctly by deleting the child device and recreating it again so I got asked again for the password, so I am certain it is correct.

What could be happening here, and how do I debug it?

thanks