Topics

16

Installation issues / Snapshot 24279 Install Problems

« on: July 30, 2011, 12:25:05 am »

I'm trying to find a good snapshot that supports Asterisk for my new VOIP adapter. I tried the latest recommended snapshot (24098) but learned from posde that it had a bug.

http://forum.linuxmce.org/index.php/topic,11851.0.html

You are experiencing a bug which has been rectified in the latest snapshot. Try apt-get update and upgrade - if it does not work, you can manually screw around with removing some deb packages (asterisk-config removal with dpkg and forceall) and an install of freepbx after that, or if it is easier for you, just download the latest snapshot.

This quote was posted on 26 July which means I had to use snapshot 24279 or later. As of now (29 July) there are no other snapshots. Unfortunately snap 24279 hung on installation when downloading the Myth plugin. When I try to reboot the start goes into an infinite loop "Adding sambahelper to smbpasswd".
It seems similar to the bad snapshot identified in this post from a year ago.

http://forum.linuxmce.org/index.php?topic=10421.0

On a positive note, I was able to get my phone line installed before my installation crashed.

John

17

Installation issues / [SOLVED again] Telecom Setup with SPA3102 and Broadvoice

« on: July 28, 2011, 07:28:10 pm »

Edit 1 Sept 2011. My main error is easily seen in reply 5 under step 3. I thought I was configuring my ATA phone, but I mistakenly entered the info into the orbiter phone. That's bad. I wrote a tutorial that I hope helps anyone trying to set up an ATA.
http://wiki.linuxmce.org/index.php/Cisco/Linksys/Sipura_Analog_Telephone_Adapters


I'm having difficulty getting my phone up and running. Hardware is set up as pictured. The external network has yellow cabling. It goes from the DSL modem at left, to the wireless router, to the first NIC in the core (behind the pegboard). The internal network has grey cabling. It goes from the second NIC to the switch, then out to my devices. The blue cable goes from the switch to the "internet" port in the SPA3102. I've connected the ancient telephone to the "phone" port. The "line" and "ethernet" ports are not used.



I reinstalled LMCE with the latest snapshot yesterday. The hardware was connected as shown in the hope that the wizard would detect everything and lead me through the installation. Unfortunately I used the wrong username and password. Not sure if this is the root cause of my problems. I deleted the device and restarted the wizard. This time I used the correct password, but when I pick up the phone I just get a busy signal.
The LMCE admin page has lots of different screens for phone systems and I'm not sure where to start troubleshooting. The "phone lines" device does not have a number. I tried to edit and insert my number, but it would not save. Also, I'm not even sure if LMCE knows I'm using an SPA3102.

Any help is appreciated,

John

18

Installation issues / [SOLVED] Satellite TV Sound Workaround

« on: July 01, 2011, 11:34:52 pm »

I finally got around to moving the DirecTV DVR box (HR22) from the 2nd floor near the TV to the equipment rack in the basement. I will eventually try to integrate this fully into LinuxMCE, but she with whom I live is getting tired of my development efforts. I had to make it work immediately. For control, I merely changed the settings for the DVR and remote control from IR to RF. The range of the remote is good, allowing us to operate the DVR from the second floor couch. For video, I have a 25 ft component video cable running directly from the sat box to the TV.

The trouble is no sound. I ordered a 25 ft RCA cable to enable the tv speakers, but that will arrive next week and will sound like crap. In the meantime, the sat box is sitting right next to the Denon receiver in the basement. I connected the DirecTV audio to the Denon using the DBS input, but I don't know how to tell LMCE that this connection exists. What I would like to happen is the following. I use the tv remote to switch video inputs from DVI to Component (bypassing the core as fas as video is concerned). Then I control the sat box using its own RF remote (also bypassing the core). For sound, I would like to use the gyration remote to tell the core to change the Denon's input from V-Aux to DBS and to control volume. There is a working serial connection between the core and Denon.

Can someone steer me in the right direction? Eventually I'll get a Hauppauge Colossus and an IR blaster to bring everything under control of the core, but this is postponed for reasons of marital harmony.

John

19

Users / Best Toys To Expand LinuxMCE - Beginner Wants To Take It Up A Notch

« on: March 27, 2011, 04:35:48 pm »

When I first decided to try LMCE I wanted to keep costs to a minimum until I proved that I could actually get a system up and running. My system so far is:
- Hybrid Core with HDTV capture (OTA)
- 330G internal storage for videos and music
- Denon Receiver with in-wall speakers
- Insteon modem (1 light switch but more planned)
- 1-wire temp sensor (1 sensor but more planned)
- Gyration remote

It hasn't always been easy, but with help from the forums I've been able to get most things working (Insteon and 1-wire aren't up yet, but I'm working on it). Now I'm looking for input on the most cost effective ways to make the system more fun and more usable.
- Orbiters. Currently, my only control is the Gyration remote. My wife has an iPhone and an eeePC notebook (Windows) that I plan to set up as orbiters, but I've heard one of the best upgrades is to get a web pad with a touch screen.
- Telephone. This could pay for itself because I'm now paying 45US for a landline that I could eliminate. I checked into Broadvoice which looks like it is about 11US. I'm no expert on phone systems, but it looks like there are roughly two paths. I could get a VOIP phone like the Cisco 7970, or I could get an analog telephone adapter like the SPA3102 and use the phones I already own (I'm leaning this way).
- Security system. GE Caddx has rs232 connection and is inexpensive.  

What do you think? Am I considering good upgrades? Are there better products than the ones I'm listed? Are there cost effective upgrades that I'm overlooking?

John

20

Installation issues / Connecting A USB DVD Drive

« on: March 20, 2011, 09:47:41 pm »

I'll start with an apology. I think that forum etiquette requires member to give as much as they get, and I'm in negative numbers at the moment. All I can say is that my ultimate goal is to have a working system, contribute to the wiki, and take on some development responsibilities.
Now that my remote is working, I'd like to be able to play a DVD. I've installed libdvdcss2 and I can play a DVD in my basement using the drive installed in my hybrid core. However, my main TV is on the second floor. Next to my TV, I have a USB DVD drive connected to a hub, connected to a USB extender, connected to the core. Some might doubt that such a scheme could work, but it worked great a few weeks ago. I could use the menu overlay to pick "manage disk drives" and I would see the DVD on the core, and also the USB drive. I could insert and watch a movie using either drives. Now all I see is the drive installed in my core.
I looked in the wiki manual to see how I could fix it and found "Normally everything is setup for you automatically. If you're experiencing problems, go to Wizard > Devices > Media Directors and be sure the appropriate media players are checked and a disk drive is checked." I did this and looked for a place to put a checkmark, but there was no such option.

http://



Uploaded with ImageShack.us

21

Users / Offer To Help: Updating The Quick Start Guide

« on: March 16, 2011, 08:56:32 pm »

First let me say that I have the utmost respect and enthusiasm for Linux MCE and those who developed it. That being said, I'm off to what I'd consider a rocky start. Rather than complain about stuff that I'm certain will turn out to be operator error, I'd like to do something constructive. I think the root cause of my problems is that information is just too hard to find on the LMCE site.
I would like to make a LinuxMCE Quick Start Guide. I would keep this current and complete, including screenshots and videos as necessary. There would be minimum links to other pages.  Obviously, we would have to limit the scope to keep this from becoming an overwhelming task.
I think most newbies will probably want to test drive LMCE in a relatively limited way using hardware they already own, as much as possible. I'll go out on a limb and say that everyone considering LMCE already has an amplifier, speakers, and a TV or monitor that would work. They probably already own a suitable computer (or can get one for a few hundred dollars). Many already own a laptop that could be used as an orbiter. There are probably a lot of people who could put together a usable starting point merely by purchasing an NVIDIA video card, TV capture card, USBUIRT, and a remote control. It is for these people using this type of equipment that I propose to write the Quick Start Guide. It would focus on using LMCE as a media center. I'd be tempted to stop there, but LMCE is more than just a media center, so I would cover lighting as well. Once a newbie has built a working system to this point, he/she is no longer a newbie and can graduate to more advanced topics not covered in the Quick Start. Below is an initial framework.

Quick Start Guide To LMCE
Topology considerations
Select Hardware – Hybrid Core, Amplifier, Display, Controller, Networking, Interconnecting cables
Prepare for installation (download, burn ISO, Schedules Direct)
Initial installation and Wizard
Control LMCE (with keyboard, with remote, with laptop orbiter)
Control Amp through LMCE (serial, IR)
Control TV through LMCE (serial, IR)
Music (rip from CD, add pre-ripped files)
DVDs (watch live, rip to disk, add pre-ripped)
OTA TV (watch live, record/playback)
Web TV
Add storage (internal disk, NAS)
Lighting


I'm offering to write this, but as I said, I'm off to a rocky start and will need a hint or two.

John

22

Installation issues / Insteon How-To?

« on: March 15, 2011, 10:47:45 pm »

I bought my Insteon 2412S modem and I've replaced the porch light switch with a 2476S. I've scoured everything I can find on how to get LMCE to recognize and control the porch light and I'm out of ideas.

There is a wiki on setting up a new template, but this seems outdated.

http://wiki.linuxmce.org/index.php/Setting_Up_PLM_Template

When I try to follow the instructions I see that there are already templates. Actually 2 templates: "Insteon PLM" seems to have plug/play info but no ruby code, "Insteon PLM DCE" seems to have ruby code but no plug/play. I tried the "PLM DCE" and as soon as I selected the template, Sarah came up and started loading software. Then it tried a DCE reload and hung while trying to generate the still incomplete Insteon device - I hadn't even had a chance to select the serial port yet.

I looked at this wiki but it seems Insteon is already installed.

http://wiki.linuxmce.org/index.php/Running_the_Insteon_PLM_Driver_for_the_First_Time

I would love a good shove in the right direction. What are the first steps? Which is the best template? Do I try to link the modem and light switch before or after setting things up in LMCE?

23

Users / ttyD Serial Ports Not Recognized

« on: March 02, 2011, 09:11:34 pm »

After installing a Syba SY-PCI15001 card and the latest driver from MOSCHIP I now have an additional 6 serial ports. However, two of the new ports show up as ttyD, and are apparently not recognized by LinuxMCE. Is there a way around this?

js@dcerouter:~/MCS9865_V1.0.0.11$ setserial -g /dev/tty[SD]*
/dev/ttyD0, UART: 16550A, Port: 0xdc00, IRQ: 19            
/dev/ttyD1, UART: 16550A, Port: 0xd880, IRQ: 18            
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4              
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3            
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4            
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3            
/dev/ttyS4, UART: 16550A, Port: 0xd800, IRQ: 16            
/dev/ttyS5, UART: 16550A, Port: 0xd480, IRQ: 16            
/dev/ttyS6, UART: 16550A, Port: 0xd400, IRQ: 16                                          
/dev/ttyS7, UART: 16550A, Port: 0xd080, IRQ: 16

I can use S0 (motherboard) and S4-S7 from the Syba card. The ttyD ports do not show up in the wizard when I install my Denon amp. S1-S3 are legacy addresses, I think, from the time when motherboards had many built-in serial ports. I tried to rename D0 to S2 using setserial. S2 subsequently appeared as a choice in the wizard, but it would not work. After this failure, I tried to reconnect on S0 using web admin (select S0, save, reload router). This did not work, nor would any of my other good ports until I deleted the device (AVR2310) and reinstalled to S0 using the wizard. After doing this, I could again use the web admin method to easily change between all my working ports.
By the way, I tested all the 6 ports on the card (including ttyD0 and D1) using minicom to talk with another computer through a null cable. Everything checked out fine.

Any insights are appreciated,

John

Code: [Select]

js@dcerouter:~/MCS9865_V1.0.0.11$ make           
rm -f *.mod.c *.o *.ko .*.cmd *.symvers         
make -C /lib/modules/2.6.27-17-generic/build/ SUBDIRS=/home/js/MCS9865_V1.0.0.11 modules                                                                       
make[1]: Entering directory `/usr/src/linux-headers-2.6.27-17-generic'         
  CC [M]  /home/js/MCS9865_V1.0.0.11/mcs9865.o                                 
/home/js/MCS9865_V1.0.0.11/mcs9865.c: In function ‘receive_chars’:             
/home/js/MCS9865_V1.0.0.11/mcs9865.c:644: warning: comparison of distinct pointer types lacks a cast                                                           
/home/js/MCS9865_V1.0.0.11/mcs9865.c:718: warning: comparison of distinct pointer types lacks a cast                                                           
  CC [M]  /home/js/MCS9865_V1.0.0.11/mcs9865-isa.o                             
  Building modules, stage 2.                                                   
  MODPOST 2 modules                                                             
  CC      /home/js/MCS9865_V1.0.0.11/mcs9865-isa.mod.o                         
  LD [M]  /home/js/MCS9865_V1.0.0.11/mcs9865-isa.ko                             
  CC      /home/js/MCS9865_V1.0.0.11/mcs9865.mod.o                             
  LD [M]  /home/js/MCS9865_V1.0.0.11/mcs9865.ko                                 
make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-17-generic'           
                                               
js@dcerouter:~/MCS9865_V1.0.0.11$ sudo insmod mcs9865.ko                       
[sudo] password for js:                                                         
js@dcerouter:~/MCS9865_V1.0.0.11$ sudo insmod mcs9865-isa.ko                   

js@dcerouter:~/MCS9865_V1.0.0.11$ setserial -g /dev/tty[SD]*
/dev/ttyD0, UART: 16550A, Port: 0xdc00, IRQ: 19             
/dev/ttyD1, UART: 16550A, Port: 0xd880, IRQ: 18             
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4             
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3             
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4             
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3             
/dev/ttyS4, UART: 16550A, Port: 0xd800, IRQ: 16             
/dev/ttyS5, UART: 16550A, Port: 0xd480, IRQ: 16             
/dev/ttyS6, UART: 16550A, Port: 0xd400, IRQ: 16                                           
/dev/ttyS7, UART: 16550A, Port: 0xd080, IRQ: 16

js@dcerouter:~/MCS9865_V1.0.0.11$ sudo setserial /dev/ttyS2 UART 16550A Port 0xdc00 IRQ 19
js@dcerouter:~/MCS9865_V1.0.0.11$ setserial -g /dev/tty[SD]*                             
/dev/ttyD0, UART: 16550A, Port: 0xdc00, IRQ: 19                                           
/dev/ttyD1, UART: 16550A, Port: 0xd880, IRQ: 18                                           
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4                                           
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3                                           
/dev/ttyS2, UART: 16550A, Port: 0xdc00, IRQ: 19                                           
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3                                           
/dev/ttyS4, UART: 16550A, Port: 0xd800, IRQ: 16                                           
/dev/ttyS5, UART: 16550A, Port: 0xd480, IRQ: 16                                           
/dev/ttyS6, UART: 16550A, Port: 0xd400, IRQ: 16                                           
/dev/ttyS7, UART: 16550A, Port: 0xd080, IRQ: 16

js@dcerouter:~/MCS9865_V1.0.0.11$ sudo setserial /dev/ttyD0 UART unknown Port 0x0000 IRQ 0
js@dcerouter:~/MCS9865_V1.0.0.11$ setserial -g /dev/tty[SD]*                             
/dev/ttyD0, UART: unknown, Port: 0x0000, IRQ: 0                                           
/dev/ttyD1, UART: 16550A, Port: 0xd880, IRQ: 18                                           
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4                                           
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3                                           
/dev/ttyS2, UART: 16550A, Port: 0xdc00, IRQ: 19                                           
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3                                           
/dev/ttyS4, UART: 16550A, Port: 0xd800, IRQ: 16                                           
/dev/ttyS5, UART: 16550A, Port: 0xd480, IRQ: 16                                           
/dev/ttyS6, UART: 16550A, Port: 0xd400, IRQ: 16                                           
/dev/ttyS7, UART: 16550A, Port: 0xd080, IRQ: 16

js@dcerouter:~/MCS9865_V1.0.0.11$ lspci -v
00:00.0 Host bridge: nVidia Corporation MCP79 Host Bridge (rev b1)
        Subsystem: ASUSTeK Computer Inc. Device 8356             
        Flags: bus master, 66MHz, fast devsel, latency 0         

00:00.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
        Subsystem: ASUSTeK Computer Inc. Device 8356                   
        Flags: bus master, 66MHz, fast devsel, latency 0               

00:03.0 ISA bridge: nVidia Corporation MCP79 LPC Bridge (rev b2)
        Subsystem: ASUSTeK Computer Inc. Device 8356           
        Flags: bus master, 66MHz, fast devsel, latency 0       
        I/O ports at 4f00 [size=256]                           

00:03.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
        Subsystem: ASUSTeK Computer Inc. Device 8356                   
        Flags: 66MHz, fast devsel                                     

00:03.2 SMBus: nVidia Corporation MCP79 SMBus (rev b1)
        Subsystem: ASUSTeK Computer Inc. Device 8356 
        Flags: 66MHz, fast devsel, IRQ 15             
        I/O ports at 4900 [size=64]                   
        I/O ports at 4d00 [size=64]                   
        I/O ports at 4e00 [size=64]                   
        Capabilities: <access denied>                 

00:03.3 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
        Subsystem: ASUSTeK Computer Inc. Device 8356                   
        Flags: 66MHz, fast devsel                                     

00:03.4 RAM memory: nVidia Corporation Device 0a98 (rev b1)
        Subsystem: ASUSTeK Computer Inc. Device 8356       
        Flags: 66MHz, fast devsel                         

00:03.5 Co-processor: nVidia Corporation MCP79 Co-processor (rev b1)
        Subsystem: ASUSTeK Computer Inc. Device 8356               
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23   
        Memory at fad80000 (32-bit, non-prefetchable) [size=512K]   
        Kernel driver in use: nvidia                               
        Kernel modules: nvidia                                     

00:04.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1) (prog-if 10)
        Subsystem: ASUSTeK Computer Inc. Device 8356                                         
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21                             
        Memory at fad7f000 (32-bit, non-prefetchable) [size=4K]                               
        Capabilities: <access denied>                                                         
        Kernel driver in use: ohci_hcd                                                       
        Kernel modules: ohci-hcd                                                             

00:04.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1) (prog-if 20)
        Subsystem: ASUSTeK Computer Inc. Device 8356                                         
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23                             
        Memory at fad7ec00 (32-bit, non-prefetchable) [size=256]                             
        Capabilities: <access denied>                                                         
        Kernel driver in use: ehci_hcd                                                       
        Kernel modules: ehci-hcd                                                             

00:06.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1) (prog-if 10)
        Subsystem: ASUSTeK Computer Inc. Device 8356                                         
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20                             
        Memory at fad7d000 (32-bit, non-prefetchable) [size=4K]                               
        Capabilities: <access denied>                                                         
        Kernel driver in use: ohci_hcd                                                       
        Kernel modules: ohci-hcd                                                             

00:06.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1) (prog-if 20)
        Subsystem: ASUSTeK Computer Inc. Device 8356                                         
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22                             
        Memory at fad7e800 (32-bit, non-prefetchable) [size=256]                             
        Capabilities: <access denied>                                                         
        Kernel driver in use: ehci_hcd                                                       
        Kernel modules: ehci-hcd                                                             

00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1)
        Subsystem: ASUSTeK Computer Inc. Device 82fe                         
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21             
        Memory at fad78000 (32-bit, non-prefetchable) [size=16K]             
        Capabilities: <access denied>                                       
        Kernel driver in use: HDA Intel                                     
        Kernel modules: snd-hda-intel                                       

00:09.0 PCI bridge: nVidia Corporation MCP79 PCI Bridge (rev b1) (prog-if 01)
        Flags: bus master, 66MHz, fast devsel, latency 0                     
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=64       
        I/O behind bridge: 0000d000-0000dfff                                 
        Memory behind bridge: fae00000-faefffff                             
        Prefetchable memory behind bridge: dff00000-dfffffff                 
        Capabilities: <access denied>                                       

00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1)
        Subsystem: ASUSTeK Computer Inc. Device 8356                   
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21       
        Memory at fad7c000 (32-bit, non-prefetchable) [size=4K]       
        I/O ports at c480 [size=8]                                     
        Memory at fad7e400 (32-bit, non-prefetchable) [size=256]       
        Memory at fad7e000 (32-bit, non-prefetchable) [size=16]       
        Capabilities: <access denied>                                 
        Kernel driver in use: forcedeth                               
        Kernel modules: forcedeth                                     

00:0b.0 IDE interface: nVidia Corporation MCP79 SATA Controller (rev b1) (prog-if 85 [Master SecO PriO])
        Subsystem: ASUSTeK Computer Inc. Device 8356                                                   
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 221                                       
        I/O ports at c400 [size=8]                                                                     
        I/O ports at c080 [size=4]                                                                     
        I/O ports at c000 [size=8]                                                                     
        I/O ports at bc00 [size=4]                                                                     
        I/O ports at b880 [size=16]                                                                     
        Memory at fad76000 (32-bit, non-prefetchable) [size=8K]                                         
        Capabilities: <access denied>                                                                   
        Kernel driver in use: ahci                                                                     
        Kernel modules: ahci                                                                           

00:0c.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
        Flags: bus master, fast devsel, latency 0                       
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0   
        Capabilities: <access denied>                                   
        Kernel driver in use: pcieport-driver                           
        Kernel modules: shpchp                                         

00:10.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
        Flags: bus master, fast devsel, latency 0                       
        Bus: primary=00, secondary=03, subordinate=03, sec-latency=0   
        I/O behind bridge: 0000e000-0000efff                           
        Memory behind bridge: faf00000-fbffffff                         
        Prefetchable memory behind bridge: 00000000e0000000-00000000f9ffffff
        Capabilities: <access denied>                                       
        Kernel modules: shpchp                                             

00:15.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
        Flags: bus master, fast devsel, latency 0                       
        Bus: primary=00, secondary=04, subordinate=04, sec-latency=0   
        Capabilities: <access denied>                                   
        Kernel driver in use: pcieport-driver                           
        Kernel modules: shpchp                                         

01:05.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
        Subsystem: DViCO Corporation Device d500                                       
        Flags: bus master, medium devsel, latency 64, IRQ 17                           
        Memory at dffff000 (32-bit, prefetchable) [size=4K]                           
        Capabilities: <access denied>                                                 
        Kernel driver in use: bttv                                                     
        Kernel modules: bttv                                                           

01:05.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
        Subsystem: DViCO Corporation Device d500                                 
        Flags: bus master, medium devsel, latency 64, IRQ 17                     
        Memory at dfffe000 (32-bit, prefetchable) [size=4K]                     
        Capabilities: <access denied>                                           
        Kernel driver in use: bt878                                             
        Kernel modules: bt878                                                   

01:06.0 Serial controller: NetMos Technology PCI 9865 Multi-I/O Controller (prog-if 02)
        Subsystem: Device a000:1000
        Flags: bus master, medium devsel, latency 64, IRQ 19
        I/O ports at dc00 [size=8]
        Memory at faeff000 (32-bit, non-prefetchable) [size=4K]
        Memory at faefe000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: <access denied>
        Kernel driver in use: mcs9865-serial

01:06.1 Serial controller: NetMos Technology PCI 9865 Multi-I/O Controller (prog-if 02)
        Subsystem: Device a000:1000
        Flags: bus master, medium devsel, latency 64, IRQ 18
        I/O ports at d880 [size=8]
        Memory at faefd000 (32-bit, non-prefetchable) [size=4K]
        Memory at faefc000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: <access denied>
        Kernel driver in use: mcs9865-serial

01:06.2 Communication controller: NetMos Technology PCI 9865 Multi-I/O Controller
        Subsystem: Device a000:3004
        Flags: bus master, medium devsel, latency 64, IRQ 16
        I/O ports at d800 [size=8]
        I/O ports at d480 [size=8]
        I/O ports at d400 [size=8]
        I/O ports at d080 [size=8]
        Memory at faefb000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: <access denied>
        Kernel driver in use: serial-isa

03:00.0 VGA compatible controller: nVidia Corporation GeForce 9300 / nForce 730i (rev b1)
        Subsystem: ASUSTeK Computer Inc. Device 8356
        Flags: bus master, fast devsel, latency 0, IRQ 22
        Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at f8000000 (64-bit, prefetchable) [size=32M]
        I/O ports at ec00 [size=128]
        [virtual] Expansion ROM at fafe0000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: nvidia
        Kernel modules: nvidia, nvidiafb

js@dcerouter:~/MCS9865_V1.0.0.11$


24

Installation issues / [SOLVED] Getting 6 Port Serial Card To Work

« on: February 17, 2011, 06:20:12 am »

Does anyone have experience with the Syba SY-PCI15001 serial card with the Netmos 9865 chipset? I installed the Linux driver but nogo. Then I found this post

http://ubuntuforums.org/showthread.php?t=1663575

where a guy got it working in Ubuntu, but nojoy with his instructions either.

25

Users / (SOLVED/worked around) Stay in KDE Desktop More Than 5 Minutes And MCE Goes Away

« on: February 17, 2011, 06:11:17 am »

When I select KDE Desktop from the LMCE main screen, I can sometimes get back to LMCE, but sometimes I can't. The KDE screen has the six windows at the bottom. If I stay only a short while in KDE, I can return to MCE by clicking on window #5. If I work for ten minutes or so, then it seems MCE goes away. Clicking on window #5 brings back the Flickr pics but no MCE interface. I go back to window #1 and try to shutdown, but then I get the Kubuntu loading bar like I'm starting up. The bar gets almost to the right side then hangs. I end up having to push and hold the power button. I hate to abuse such fine software in this way. What is the more graceful solution?

John

26

Installation issues / NVIDIA Driver - Troubleshooting Black Screen, Low Resolution

« on: February 06, 2011, 05:12:13 pm »

Executive Summary
Selecting a 60Hz resolution in the AV Wizard gives me an undisplayable 85Hz refresh rate. I think two things are causing this. First, the NVIDIA driver is failing to weed out modes that are beyond the capability of my hardware. Second, the wizard is adding my desired resolution to xorg.conf, but it is not specifying the refresh rate. The driver responds by choosing what it thinks is the "best" refresh rate, and I get a black screen. This might be happening to others who get a black screen after running the Wizard.

I have two questions for the experts. First, when checking modes, why does the driver note “VertRefresh out of range” then ignore it and declare the mode valid? UseEdid is set “true”, so out-of-range modes should be rejected. Second, why does the wizard not include the selected refresh rate when it inserts the mode into xorg.conf?


Detailed Version
I'm fairly new to MCE so I hope I'm not spreading disinformation. Main sources are the NVIDIA readme as well as the log and configuration files.

/var/log/Xorg.0.log
/etc/X11/xorg.conf
http://us.download.nvidia.com/XFree86/Linux-x86/195.36.15/README/programmingmodes.html
http://us.download.nvidia.com/XFree86/Linux-x86/195.36.15/README/xconfigoptions.html


NVIDIA Resolution Overview
One of the jobs of the NVIDIA driver is to offer a set of different modelines that can be selected to provide your desired screen resolution and refresh rate. The driver does not generate these modelines from scratch; it collects candidates from a variety of sources and evaluates whether each one will work with your system. The driver will supply standard Xserver and VESA modelines to the candidate list. The display section of xorg.conf can also supply modeline candidates. Finally, the monitor can supply modeline candidates through its EDID (Extended Display Identification Data). The EDID contains information about the monitor that your computer accesses through the VGA, DVI, or HDMI cable. The user can filter out some of these candidates by specifying options in xorg.conf.

The driver looks at each candidate modeline and declares it to be either “valid” or “rejected”. It makes this judgment based upon information gathered from the monitor (through EDID), from the graphics card, and from options specified in xorg.conf. Valid modelines are given unique names and put into a list. The naming convention is as follows ...

"1024x768"              : 1024 x  768 @  85.0 Hz  (from: X Server, VESA)
"1024x768_85"        : 1024 x  768 @  85.0 Hz  (from: X Server, VESA)
"1024x768_75"        : 1024 x  768 @  75.0 Hz  (from: X Server, VESA)
"1024x768_70"        : 1024 x  768 @  70.1 Hz  (from: X Server, VESA)
"1024x768_60"        : 1024 x  768 @  60.0 Hz  (from: X Server, VESA)

...and so on through all the remaining resolutions. The driver rank orders these valid modelines from best (85Hz) to worst (60Hz). It takes the best modeline (1024x768_85), duplicates it, and renames it with the refresh rate omitted. That way if you select “1024x768” and don't specify the refresh rate, you'll get the best available (in this case 85Hz). Remember that these are just the names, not the actual modelines themselves. A complete modeline looks like this...

ModeLine "1024x768_85.00" 78.75 1024 1040 1136 1312 768 769 772 800 -hsync -vsync

There are a few different ways to select the mode (resolution) you want. On your home office computer, you might open  “NVIDIA X Server Settings” from the menu bar. In LinuxMCE the AV Wizard allows you to choose your mode. The end result of both of these methods is to write the desired mode into the “screen” section of xorg.conf.  Most of this is a fairly automated process. You can also manually edit the xorg.conf file.

AV Wizard Generates Wrong Resolution
First, the hardware I'm using is...
P5N7A-VM
E5200 CPU
NVIDIA GeForce 9300 (integrated)
LG DU-42PX12X plasma (built 2004, 1024x768 native resolution, DVI cable)

After a fresh install of the latest snapshot, I selected 1024x768 60Hz (recommended by the TV manual) in the AV Wizard. This resulted in a black screen. The best resolution that would display was 640x480. I disconnected my TV, connected a PC monitor, and rebooted to arrive again at the wizard. Choosing 1024x768_60 gave a working display on the monitor, but it also showed the warning “input signal out of range”. Apparently the monitor was able to adapt to an out of range signal. Finishing the setup and checking /etc/X11/xorg.conf (see below) showed that the wizard inserted a modeline ("1024x768" 60.80 1024 1056 1128 1272 768 768 770 796) in the "Monitor" section. In the section “Screen” it inserted a line calling for mode "1024x768" to be displayed.

Reviewing /var/log/Xorg.0.log (see below) showed three things of interest. First, the modeline supplied by the wizard is tested and rejected. Second, the VESA-supplied 85Hz mode is accepted (along with other modes that are beyond the TV capabilities). The driver identifies that the VertRefresh is out of range, but ignores this and declares the mode valid. Third, looking in the valid modepool, the 85Hz mode is the best valid mode and is renamed “1024x768”. This name matches the name from the “Screen” section of the wizard-supplied xorg.conf. So even though I requested a 60Hz mode, I was getting an 85Hz mode that the TV cannot display.

Manually replacing the wizard-supplied modeline with a valid one did not help because xorg.conf was still requesting the mode “1024x768” and that mode was still the driver-selected best mode of 85Hz. Only when I manually edited xorg.conf to specifically request "1024x768_60" did I get the correct resolution for the TV.

Code: [Select]

#From xorg.conf

Section "Monitor"

    Identifier     "Monitor0"

    VendorName     "Unknown"

    ModelName      "Unknown"

    Option         "DPMS"

Modeline "1024x768" 60.80 1024 1056 1128 1272 768 768 770 796

HorizSync 20-500

VertRefresh 59-61

EndSection



Section "Device"

    Identifier     "Device0"

    Driver         "nvidia"

    VendorName     "NVIDIA Corporation"

Option "XvmcUsesTextures" "true"

Option "renderAccel" "true"

Option "NoDDCValue"

Option "UseEDID" "true"

Option "ExactModeTimingsDVI" "true"

Option "NoLogo" "true"

Option "NoBandWidthTest" "true"

Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes, NoEdidModes"

Option "DynamicTwinView" "false"

Option "UseEvents" "true"

Option "ConnectedMonitor" "DFP"

EndSection



Section "Screen"

    Identifier     "Screen0"

    Device         "Device0"

    Monitor        "Monitor0"

    DefaultDepth    24

SubSection "Display"

Modes "1024x768"

Virtual 1024 768

EndSubSection

SubSection "Device"

Modes "1024x768"

EndSubSection


Code: [Select]

#From Xorg.0.log

(II) Feb 04 10:28:53 NVIDIA(0):   Validating Mode "1024x768":

(II) Feb 04 10:28:53 NVIDIA(0):     1024 x 768 @ 60 Hz

(II) Feb 04 10:28:53 NVIDIA(0):     Mode Source: X Configuration file ModeLine

(II) Feb 04 10:28:53 NVIDIA(0):       Pixel Clock      : 60.80 MHz

(II) Feb 04 10:28:53 NVIDIA(0):       HRes, HSyncStart : 1024, 1056

(II) Feb 04 10:28:53 NVIDIA(0):       HSyncEnd, HTotal : 1128, 1272

(II) Feb 04 10:28:53 NVIDIA(0):       VRes, VSyncStart :  768,  768

(II) Feb 04 10:28:53 NVIDIA(0):       VSyncEnd, VTotal :  770,  796

(II) Feb 04 10:28:53 NVIDIA(0):       H/V Polarity     : +/+

(II) Feb 04 10:28:53 NVIDIA(GPU-0):     BestFit Scaled and BestFit AspectScaled are identical;

(II) Feb 04 10:28:53 NVIDIA(GPU-0):         collapsing BestFit AspectScaled.

(II) Feb 04 10:28:53 NVIDIA(GPU-0):     BestFit Centered and BestFit Scaled are identical;

(II) Feb 04 10:28:53 NVIDIA(GPU-0):         collapsing BestFit Scaled.

(WW) Feb 04 10:28:53 NVIDIA(GPU-0):     BestFit Centered ViewPort 1024x768 exceeds hardware

(WW) Feb 04 10:28:53 NVIDIA(GPU-0):         capabilities.

(WW) Feb 04 10:28:53 NVIDIA(0):     Mode is rejected: Unable to construct hardware-specific

(WW) Feb 04 10:28:53 NVIDIA(0):     mode timings.
...section deleted for brevity...
Validating Mode "1024x768":

(II) Feb 04 10:28:53 NVIDIA(0):     1024 x 768 @ 85 Hz

(II) Feb 04 10:28:53 NVIDIA(0):     Mode Source: VESA

(II) Feb 04 10:28:53 NVIDIA(0):       Pixel Clock      : 94.50 MHz

(II) Feb 04 10:28:53 NVIDIA(0):       HRes, HSyncStart : 1024, 1072

(II) Feb 04 10:28:53 NVIDIA(0):       HSyncEnd, HTotal : 1168, 1376

(II) Feb 04 10:28:53 NVIDIA(0):       VRes, VSyncStart :  768,  769

(II) Feb 04 10:28:53 NVIDIA(0):       VSyncEnd, VTotal :  772,  808

(II) Feb 04 10:28:53 NVIDIA(0):       H/V Polarity     : +/+

(II) Feb 04 10:28:53 NVIDIA(0):     VertRefresh (85.0 Hz) out of range (56.000-76.000 Hz);

(II) Feb 04 10:28:53 NVIDIA(0):         however, ignoring VertRefresh check for DFP frontend

(II) Feb 04 10:28:53 NVIDIA(0):         mode validation

(II) Feb 04 10:28:53 NVIDIA(GPU-0):     BestFit Scaled and BestFit AspectScaled are identical;

(II) Feb 04 10:28:53 NVIDIA(GPU-0):         collapsing BestFit AspectScaled.

(II) Feb 04 10:28:53 NVIDIA(GPU-0):     BestFit Centered and BestFit Scaled are identical;

(II) Feb 04 10:28:53 NVIDIA(GPU-0):         collapsing BestFit Scaled.

(II) Feb 04 10:28:53 NVIDIA(GPU-0):     BestFit Centered         1024x768

(II) Feb 04 10:28:53 NVIDIA(GPU-0):       Horizontal Taps        0

(II) Feb 04 10:28:53 NVIDIA(GPU-0):       Vertical Taps          0

(II) Feb 04 10:28:53 NVIDIA(GPU-0):       Base SuperSample       x1

(II) Feb 04 10:28:53 NVIDIA(GPU-0):       Base Depth             32

(II) Feb 04 10:28:53 NVIDIA(GPU-0):       Distributed Rendering  1

(II) Feb 04 10:28:53 NVIDIA(GPU-0):       Overlay Depth          32

(II) Feb 04 10:28:53 NVIDIA(0):     Mode is valid.
...section deleted for brevity...
(II) Feb 04 10:28:53 NVIDIA(0): --- Modes in ModePool for HSG HF207 (DFP-0) ---

(II) Feb 04 10:28:53 NVIDIA(0): "nvidia-auto-select" : 1024 x  768 @  85.0 Hz  (from: VESA)

(II) Feb 04 10:28:53 NVIDIA(0): "1024x768"           : 1024 x  768 @  85.0 Hz  (from: VESA)

(II) Feb 04 10:28:53 NVIDIA(0): "1024x768_85"        : 1024 x  768 @  85.0 Hz  (from: VESA)

(II) Feb 04 10:28:53 NVIDIA(0): "1024x768_75"        : 1024 x  768 @  75.0 Hz  (from: VESA)

(II) Feb 04 10:28:53 NVIDIA(0): "1024x768_70"        : 1024 x  768 @  70.1 Hz  (from: VESA)

(II) Feb 04 10:28:53 NVIDIA(0): "1024x768_60"        : 1024 x  768 @  60.0 Hz  (from: VESA)

(II) Feb 04 10:28:53 NVIDIA(0): "1024x768_87i"       : 1024 x  768 @  87.0 Hz Interlace  (from: VESA)
...section deleted for brevity...
(II) Feb 04 10:28:53 NVIDIA(0): Assigned Display Device: DFP-0

(II) Feb 04 10:28:53 NVIDIA(0): Requested modes:

(II) Feb 04 10:28:53 NVIDIA(0):     "1024x768"

(II) Feb 04 10:28:53 NVIDIA(0): Validated modes:

(II) Feb 04 10:28:53 NVIDIA(0): MetaMode "1024x768":

(II) Feb 04 10:28:53 NVIDIA(0):     Bounding Box: [0, 0, 1024, 768]

(II) Feb 04 10:28:53 NVIDIA(0):     HSG HF207 (DFP-0): "1024x768"

(II) Feb 04 10:28:53 NVIDIA(0):         Size          : 1024 x 768

(II) Feb 04 10:28:53 NVIDIA(0):         Offset        : +0 +0

(II) Feb 04 10:28:53 NVIDIA(0):         Panning Domain: @ 1024 x 768

(II) Feb 04 10:28:53 NVIDIA(0):         Position      : [0, 0, 1024, 768]

(**) Feb 04 10:28:53 NVIDIA(0): Virtual screen size configured to be 1024 x 768


27

Installation issues / (SOLVED) LG Plasma Displays Kubuntu But Not MCE

« on: January 08, 2011, 03:09:38 am »

I've got my MCE setup running well on my workbench connected to a digital monitor. This afternoon I tried to get it to work with my LG DU-42PX12X plasma TV (which has a DVI connection and is made to work with a PC). I can watch Kubuntu boot, but when MCE starts the screen goes blank. I figured that this was a resolution problem that could be fixed with the A/V wizard. I reconnected the PC monitor and rebooted using the shift key to start the wizard. My TV manual says that the optimum setting with a PC is 1024x768, 60Hz. I selected that setting on the wizard and my monitor displayed it correctly. I then unplugged the DVI cable to the monitor and plugged in the DVI from the TV and the screen was again blank.
I know my MCE installation is good. I know my LG plasma and DVI cable are good because they display Kubuntu as it boots. Does anyone know what might be the problem?

John

28

Installation issues / [SOLVED] NVIDIA proprietary driver

« on: January 07, 2011, 09:22:05 pm »

While digging around in the Kubuntu desktop, I looked at  "System/Hardware Drivers" and noticed that the NVIDIA proprietary driver was not in use. I have often read that this driver was better, enabling more desirable features than the standard Linux driver. There was a tempting "activate" button that I almost hit, but decided to check the forum and wiki beforehand. I didn't see much on the forums, but I found a section on display drivers in the tutorials.

http://wiki.linuxmce.org/index.php/Display_Drivers

This outlines a more complicated way of manually loading the driver. Should I use this procedure from the tutorial or is it outdated? Should I press the activate button on the Kubuntu desktop or will that break the system? Should I be messing with the proprietary driver at all?

As my signature shows, I have an ASUS P5N7A-VM with onboard GeForce 9300 chipset. Thanks in advance.

John

29

Users / [SOLVED] External USB DVD not working

« on: January 15, 2010, 10:45:46 pm »

I'm trying to install a new external ASUS USB DVD player so that I can relocate my hybrid to the basement and still play movies. The problem is that the new external drive is recognized, but not usable. The MCE install seemed to go just fine and the internal DVD (also ASUS) plays movies after installing libdvdcss2. Here are some of my symptoms.

- When I select "Media:Manage Drives" from the user interface I see 2 disk drives
- Hitting "eject" on the first drive opens the door on the external drive (the other eject button opens the door on the internal drive)
- When I insert a movie in the external drive a box appears in the upper left corner that continually alternates between enabling and disabling the device
- The external drive does not mount from the KDE desktop when I insert a data DVD
- The drive also doesn't work on my desktop with Ubuntu 910, but works great on my windows laptop.

John

30

Users / Advice On New System

« on: September 03, 2009, 12:56:47 am »

Hello All,

I'd like a confidence check on my proposed setup. I have much of the equipment and I'm getting ready to start wiring. If you want to see our home renovation you can check my blog (greenrenovation.wordpress.com).Some details of the planned system are below, along with a few questions...
First, I hear that integrating DirecTV is troublesome, but the spouse needs tennis channel. The only thing on the market is the HD PVR and drivers are in early stages. I also hear that it puts a decoding strain on a media director so I went with a new e5200 computer. I'm using an older core because the PVR handles the encoding chores. Any comments on my selections?
Second, I think my wiring needs will be met by two cat5e cables to each major location. I can't see how I'd use coax since all my video will be HD. Should I put in some more/different wiring?

The Plan
It's a green home so I'd like to keep power usage to a minimum
Overall goals
   Stream DirecTV
   Watch DVD
   Stream music
   Control a small number of lighting scenarios
   Control sprinklers
   Control HVAC
   Stream HDTV
   Voice alarm for streetsweeping day to avoid the monthly $50 ticket!
   Home security with front and back video cameras
My wiring closet will be in the basement - lots of room and it's cool down there
   Core running LinuxMCE0810 (Intel D865PERL, GeForce 5200, 3Ghz P4)
   stereo amp with speaker wire run to the kitchen above
   Insteon modem
   DirecTV set top box
   Hauppauge HD PVR
   Elk M1
Living Room
   Media Director (ASUS P5N7A-VM, integrated GeForce 9300, E5200, net boot)
   Denon AVR3805 with RS232
   LG Plasma with RS232
   5.1 speakers in wall
   Microsoft Gyration remote
Upstairs Loft (not purchased but similar to living room setup)

Thanks,
John