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

Pages: 1 ... 11 12 [13] 14 15
181
Installation issues / Re: Gyration Remote keys all wacky
« on: March 07, 2011, 03:30:14 am »
I followed the instructions under "Current Workaround" on the wiki page below with no success.

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

The make seemed to go fine. I looked in /lib/modules/2.6.27-17-generic/kernel/drivers/hid and saw the hid.ko had been recently modified. So everything looked good except my Gyration 3101 still does not work. I noticed when selecting the template that GYR3101US was deprecated. Did that occur during the last few weeks and cause working remotes to stop working? By the way, I bought this in the US but I just noticed that my manual says GYR3101CA (Canada Version). Don't know if my remote is also the CA version or if that makes a difference.

John

182
This is turning out to be MUCH tougher than I thought. I've received a few emails from MOSCHIP including one with a new version of their driver that locked up my system until I booted into recovery mode and uninstalled the driver. It's strange that I don't see many posts here talking about serial cards. It seems like much of the functionality of LinuxMCE hinges upon the ability to connect the core to various media and home automation devices. Is everyone using USB connections or USB/RS232 adapters? I thought serial adapters were problematic.
Anyway, here is the makefile supplied by MOSCHIP. I think there is a problem in the "install" section midway through the file. It's basically trying to modprobe the drivers at startup by running a script called "mcs9865" copied to init.d. The problem is that mcs9865 is not a script - it's just a text file. When it tries to run, it SNAFUs the system. Below find the makefile and the mcs9865 file (these two lines are the entire contents of the file). Maybe someone can tell me how to fix this. Or what card to buy. I'd be very thankful.

John

Makefile
Code: [Select]
KDIR:=/lib/modules/$(shell  uname -r)/build/

DEBIAN_VERSION_FILE:=/etc/debian_version
DEBIAN_DISTRO:=$(wildcard $(DEBIAN_VERSION_FILE))

obj-m +=mcs9865.o
obj-m +=mcs9865-isa.o

default:
$(RM) *.mod.c *.o *.ko .*.cmd *.symvers
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
load:
insmod mcs9865.ko
unload:
rmmod mcs9865

install:
cp mcs9865.ko mcs9865-isa.ko /lib/modules/$(shell uname -r)/kernel/drivers/serial/
depmod -A
chmod +x mcs9865
cp mcs9865 /etc/init.d/
ifeq ($(DEBIAN_DISTRO), $(DEBIAN_VERSION_FILE))
ln -s /etc/init.d/mcs9865 /etc/rcS.d/Smcs9865 || true
else
ln -s /etc/init.d/mcs9865 /etc/rc3.d/Smcs9865 || true 
ln -s /etc/init.d/mcs9865 /etc/rc5.d/Smcs9865 || true
endif
modprobe mcs9865
modprobe mcs9865-isa

uninstall:
modprobe -r mcs9865
modprobe -r mcs9865-isa
rm /lib/modules/$(shell uname -r)/kernel/drivers/serial/mcs9865*
depmod -A
rm -f /etc/init.d/mcs9865
ifeq ($(DEBIAN_DISTRO), $(DEBIAN_VERSION_FILE))
rm -f /etc/rcS.d/Smcs9865
else
rm -f /etc/rc3.d/Smcs9865
rm -f /etc/rc5.d/Smcs9865
endif

clean:
$(RM) *.mod.c *.o *.ko .*.cmd *.symvers *.order *.markers
$(RM) -r .tmp_versions

mcs9865
Code: [Select]
modprobe mcs9865
modprobe mcs9865-isa

183
Users / Re: Stay in KDE Desktop More Than 5 Minutes And MCE Goes Away
« on: March 03, 2011, 07:36:29 pm »
Thanks for this. I opened the file manager, browsed to "/usr/pluto/bin/ActivateOrbiterFromKDE.sh", and just dragged a shortcut to the desktop. Works like a champ and my life is much easier!

John

184
Installation issues / Re: Gyration Remote keys all wacky
« on: March 03, 2011, 07:33:05 pm »
Beeker, I'll pile on to say that my experience matches yours. Multiple occurances of "AutoAddDevices" "False" and the remote does not function.

John

185
Users / Re: ttyD Serial Ports Not Recognized
« on: March 02, 2011, 09:37:19 pm »
I just gave that a try. The BIOS only lets me turn off my single onboard port or change its default address. I think the linux kernel sets up S0-S3 by default? I also think that the MOSCHIP driver is responsible for creating the ttyD ports. I've emailed their tech support with no luck yet. Based on the fact that the ports work in minicom, I think I have a naming problem. So maybe two solutions:

1. Rename the ttyD ports to ttyS (tried it, but I might not be using setserial correctly - see code in first post)
2. Modify LMCE to recognize ttyD ports (don't really know where to look to do this  - anyone?)

John

186
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$

187
Installation issues / Re: Need help installing LinuxMCE 8.10
« on: February 21, 2011, 10:31:44 pm »
I'll make a guess that you are installing from DVD using the tutorial?

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

You have to perform step 2 under "Internet Installation" and delete everything from sources.list and replace it with the supplied list of old releases. Then you can perform the DVD install steps.

John

188
Any serial cards to recommend? The plans for my complete system currently call for at least five ports. I picked the Syba card because it said it supported Linux and I like the DB9 connectors on the card (rather than the octopus arrangement)
1. Denon amp
2. TV
3. Insteon
4. Security
5. Sprinkler

I'm trying to follow the rules. Tschak says to avoid usb-to-serial cables (http://forum.linuxmce.org/index.php?topic=10862.0).

John

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

190
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

191
Installation issues / Re: LG Plasma Displays Kubuntu But Not MCE
« on: February 13, 2011, 04:55:46 pm »
This turned out to be more involved than I thought, but Purps was right - I needed to specify the refresh rate. I put the full story in a long post in a new thread.

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

192
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

193
Installation issues / Re: LG Plasma Displays Kubuntu But Not MCE
« on: January 09, 2011, 06:05:09 am »
I Googled edid.bin and see references to bugs and messed up resolutions with NVIDIA drivers. It seems that a few people have solved this problem by manually generating a valid edid.bin file, then manually forcing xorg to use this.

http://forums.nvidia.com/index.php?showtopic=73027

I think I'll give this a try on Monday. All else fails I might go looking for a DVI Detective.

John

194
Installation issues / Re: LG Plasma Displays Kubuntu But Not MCE
« on: January 08, 2011, 03:46:05 pm »
My test monitor is HDMI so I know about the initial blank screen until you press 1. That works with the monitor but not the TV. I even tried connecting the monitor, pressing 1 to get the wizard, then swapping the monitor with the TV to see if the wizard would even show up. The TV would always display "No Input".
I found this thread that talks about an EDID problem.

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

I decided it was worth a try so I modified xorg.conf Under Section "Screen"

Code: [Select]
Subsection "Device"
Modes "1024x768" #this might be different for you, but it should match the modeline name in the monitor section
EndSubSection

The above resolution is native for my plasma (1024x768, 60Hz). After I made this change and rebooted, I could see the wizard on the TV for the first time. However, setting the above resolution in the wizard resulted in a "No Input". I started to try all the resolutions and discovered that 480p worked.
I'm still researching this problem and would appreciate input. I'd like to get things running at the full native resolution of the screen. Maybe I have a timing issue, but I don't know enough about xorg.conf to specify 60Hz.


195
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

Pages: 1 ... 11 12 [13] 14 15