LinuxMCE Forums

General => Installation issues => Topic started by: bawbag31 on March 27, 2007, 06:53:43 pm

Title: Why only vesa?
Post by: bawbag31 on March 27, 2007, 06:53:43 pm
Why does the avwizard use vesa as it's graphics driver?  I have tried with the latest driver from the nvidia web site installed, but the linuxmce setup changes it to vesa.  I thought maybe linuxmce needs the driver to be installed from the repositories, so I tried that.  No good.  I actually saw the script UN-install the drivers then fall back to vesa.  What gives?  I have a GForce 6800GT card that should shine through with linuxmce (from what I can gather) but with vesa drivers I can't even use my native resolution (1440x900) never mind the OpenGL and Alpha stuff.
Title: Re: Why only vesa?
Post by: arbrandes on March 27, 2007, 07:52:13 pm
I can confirm this weird behavior, except with a 6600GT.  The A/V Wizard does not seem to be able to select the correct video driver.
Title: Re: Why only vesa?
Post by: asgard on March 27, 2007, 10:43:27 pm
Could you paste the output of 'lshwd -id' here? Probably there are some vendorid:productid combination that is unknown/misinterpreted by lswhd, lshwd being the application who is uses to detect the video card used in xorg.conf.pluto.
Title: Re: Why only vesa?
Post by: webpaul1 on March 27, 2007, 10:53:50 pm
yeah, nvidia 6xxx/7xxx with nvidia's proprietary driver is the 'officially sanctioned' combo that *should* always work, and when it detects that combo, the /usr/pluto/bin/XConfigure.sh should force the driver to nvidia and install the proprietary driver.
Title: Re: Why only vesa?
Post by: bawbag31 on March 27, 2007, 11:17:28 pm
Thanks for the replies!

Here is the output of lshwd -id

00:00.0 1106:0282:147b:1415 Host bridge: VIA Technologies Inc.|K8T880Pro CPU to PCI Bridge (amd64-agp)
00:00.1 1106:1282:0000:0000 Host bridge: VIA Technologies Inc.|K8T880Pro CPU to PCI Bridge (unknown)
00:00.2 1106:2282:0000:0000 Host bridge: VIA Technologies Inc.|K8T880Pro CPU to PCI Bridge (unknown)
00:00.3 1106:3282:0000:0000 Host bridge: VIA Technologies Inc.|K8T880Pro CPU to PCI Bridge (unknown)
00:00.4 1106:4282:0000:0000 Host bridge: VIA Technologies Inc.|K8T880Pro CPU to PCI Bridge (unknown)
00:00.7 1106:7282:0000:0000 Host bridge: VIA Technologies Inc.|K8T880Pro CPU to PCI Bridge (unknown)
00:01.0 1106:b188:0000:0000 PCI bridge: VIA Technologies Inc.|PCI-to-PCI Bridge (AGP 2.0/3.0) (amd64-agp)
00:07.0 1106:3044:1106:3044 FireWire (IEEE 1394)|OHCI: VIA Technologies Inc.|OHCI Compliant IEEE 1394 Host Controller (ohci1394)
00:0a.0 1102:0005:1102:1003 Multimedia audio controller: (unknown)
00:0b.0 1814:0201:1814:2560 Network controller: RaLink|Ralink RT2500 802.11 Cardbus Reference Card (rt2500)
00:0e.0 1106:3119:147b:1415 Ethernet controller: VIA Technologies Inc.|VT3119 Gigabit Ethernet Controller (via-velocity)
00:0f.0 1106:3149:147b:1415 IDE interface: VIA Technologies Inc.|VT6420 SATA RAID Controller (sata_via)
00:0f.1 1106:0571:147b:1415 IDE interface: VIA Technologies Inc.|VT82C586 IDE (via82cxxx)
00:10.0 1106:3038:147b:1415 USB Controller|UHCI: VIA Technologies Inc.|VT82C586B USB (uhci_hcd)
00:10.1 1106:3038:147b:1415 USB Controller|UHCI: VIA Technologies Inc.|VT82C586B USB (uhci_hcd)
00:10.2 1106:3038:147b:1415 USB Controller|UHCI: VIA Technologies Inc.|VT82C586B USB (uhci_hcd)
00:10.3 1106:3038:147b:1415 USB Controller|UHCI: VIA Technologies Inc.|VT82C586B USB (uhci_hcd)
00:10.4 1106:3104:147b:1415 USB Controller|EHCI: VIA Technologies Inc.|VT8235 USB Enhanced Controller (ehci-hcd)
00:11.0 1106:3227:147b:1415 ISA bridge: VIA Technologies Inc.|VT8237 PCI-to-ISA Bridge (i2c-viapro)
00:11.5 1106:3059:147b:1415 Multimedia audio controller: VIA Technologies Inc.|L7VTA v1.0 Motherboard (KT400-8235) (snd-via82xx)
00:18.0 1022:1100:0000:0000 Host bridge: Advanced Micro Devices|K8 HyperTransport Technology Configuration (unknown)
00:18.1 1022:1101:0000:0000 Host bridge: Advanced Micro Devices|K8 Address Map (unknown)
00:18.2 1022:1102:0000:0000 Host bridge: Advanced Micro Devices|K8 DRAM Controller (unknown)
00:18.3 1022:1103:0000:0000 Host bridge: Advanced Micro Devices|K8 Miscellaneous Control (amd64-agp)
01:00.0 10de:0045:0000:0000 VGA compatible controller: nVidia Corp.|NV40 [GeForce 6800 GT] (nv)
---:--- 0000:0000:0000:0000 Mouse: Generic PS/2 Wheel Mouse (msintellips/2)

I hope it helps.
Title: Re: Why only vesa?
Post by: k84 on March 28, 2007, 06:32:03 pm
Hi, Can report i have exactly the same issues with my Pci Express nvidia 6600gt board *Gainward.
Can paste the id\s later if it is needed/helpfull to track the problem.

Edit:

00:00.0 8086:2580:1028:0181 Host bridge: Intel Corp.|Memory Controller Hub (intel-agp)
00:01.0 8086:2581:0000:0000 PCI bridge: Intel Corp.|Memory Controller Hub PCI Express Port (unknown)
00:1c.0 8086:2660:0000:0000 PCI bridge: Intel Corp.|I/O Controller Hub PCI Express Port 0 (unknown)
00:1d.0 8086:2658:1028:0181 USB Controller|UHCI: Intel Corp.|I/O Controller Hub USB (unknown)
00:1d.1 8086:2659:1028:0181 USB Controller|UHCI: Intel Corp.|I/O Controller Hub USB (unknown)
00:1d.2 8086:265a:1028:0181 USB Controller|UHCI: Intel Corp.|I/O Controller Hub USB (unknown)
00:1d.3 8086:265b:1028:0181 USB Controller|UHCI: Intel Corp.|I/O Controller Hub USB (unknown)
00:1d.7 8086:265c:1028:0181 USB Controller|EHCI: Intel Corp.|I/O Controller Hub USB2 (unknown)
00:1e.0 8086:244e:0000:0000 PCI bridge|Subtractive decode: Intel Corp.|82820 815e (Camino 2) Chipset PCI (hw_random)
00:1f.0 8086:2640:0000:0000 ISA bridge: Intel Corp.|I/O Controller Hub LPC (i810-tco)
00:1f.1 8086:266f:1028:0181 IDE interface: Intel Corp.|I/O Controller Hub PATA (piix)
00:1f.2 8086:2651:1028:0181 IDE interface: Intel Corp.|82801FB/FW (ICH6/ICH6W) SATA Controller (ata_piix)
00:1f.3 8086:266a:1028:0181 SMBus: Intel Corp.|I/O Controller Hub SMBus (i2c-i801)
01:00.0 10de:0140:10b0:0403 VGA compatible controller: nVidia Corp.|GeForce 6600 GT (nv)
03:08.0 8086:1064:1028:0181 Ethernet controller: Intel Corp.|Ethernet Controller (e100)

There it is :D
Title: Re: Why only vesa?
Post by: asgard on March 29, 2007, 12:01:26 am
Hi, Can report i have exactly the same issues with my Pci Express nvidia 6600gt board *Gainward.
Can paste the id\s later if it is needed/helpfull to track the problem.

Yes, please
Title: Re: Why only vesa?
Post by: fdawg4l on March 29, 2007, 09:18:23 am
Same issue for me and my 6200 AGP. 


'''
00:00.0 10de:01e0:0000:0000 Host bridge: nVidia Corp.|nForce2 AGP Controller (nvidia-agp)
00:00.1 10de:01eb:10de:0c17 RAM memory: nVidia Corp.|nForce2 Memory Controller (unknown)
00:00.2 10de:01ee:10de:0c17 RAM memory: nVidia Corp.|nForce2 Memory Controller (unknown)
00:00.3 10de:01ed:10de:0c17 RAM memory: nVidia Corp.|nForce2 Memory Controller (unknown)
00:00.4 10de:01ec:10de:0c17 RAM memory: nVidia Corp.|nForce2 Memory Controller (unknown)
00:00.5 10de:01ef:10de:0c17 RAM memory: nVidia Corp.|nForce2 Memory Controller (unknown)
00:01.0 10de:0080:10de:0c11 ISA bridge: nVidia Corp.|MCP2A ISA bridge (unknown)
00:01.1 10de:0084:10de:0c11 SMBus: nVidia Corp.|MCP2A SMBus (i2c-nforce2)
00:02.0 10de:0087:10de:0c11 USB Controller|OHCI: nVidia Corp.|MCP2A USB Controller (unknown)
00:02.1 10de:0087:10de:0c11 USB Controller|OHCI: nVidia Corp.|MCP2A USB Controller (unknown)
00:02.2 10de:0088:10de:0c11 USB Controller|EHCI: nVidia Corp.|MCP2A USB Controller (unknown)
00:08.0 10de:008b:0000:0000 PCI bridge: nVidia Corp.|MCP2A PCI Bridge (unknown)
00:09.0 10de:0085:10de:0c11 IDE interface: nVidia Corp.|MCP2A IDE (amd74xx)
00:1e.0 10de:01e8:0000:0000 PCI bridge: nVidia Corp.|nForce2 AGP Host to PCI Bridge (agpgart)
01:07.0 1011:0024:0000:0000 PCI bridge: Digital Equipment Corp.|DECchip 21152 (unknown)
01:08.0 13f6:0111:13f6:0111 Multimedia audio controller: C-Media Electronics Inc.|CM8738 (snd-cmipci)
01:0b.0 10ec:8139:10ec:8139 Ethernet controller: Realtek Semiconductor|RT8139 (8139too)
02:04.0 1131:7146:11bd:000f Multimedia controller: Philips Semiconductors|DV500 Overlay (dpc7146)
02:08.0 123f:8120:123f:8120 Multimedia controller: C-Cube Microsystems|E4? (unknown)
02:0c.0 104c:8020:11bd:000f FireWire (IEEE 1394)|OHCI: Texas Instruments|TSB12LV26 OHCI-Lynx PCI IEEE 1394 Host Controller (ohci1394)
03:00.0 10de:0221:196e:02ba VGA compatible controller: nVidia Corp.|GeForce 6200 (nv)
'''
Title: Re: Why only vesa?
Post by: k84 on March 30, 2007, 01:23:50 am
I GOT IT WORKING!
IT\s pretty easy but NOT plug and play.

What\s taken me about 2full days, was actually pretty easy and is now working smoothley.

This is not a walkthrough but a explanation of what i did, and how YOU can get it working..

This is just based on what i think, and my own sucess story:
First this probably only works if you know that the linux nvidia drivers work for you.

1) issue this command lshwd -id
if you get as most of us did VGA COMPATIBLE card........ (nv) <-- the important part, notice it uses the nv driver not the nvidia which it should.
2) so i did an strace and checked what lshwd opens, it opens a file called Cards found in /usr/share/hwdata/Cards
3) This is nasty, but this is what i did, changed all values saying nv to nvidia
e.g DRIVER nv
to
DRIVER nvidia

about 4 entries.

4) next what i now noticed is that the lshwd command says to use vesa driver on my card, WHAT?
doing another strace says that it seems to look for the nvidia driver which is not found, then it probably fallsback to vesa which mostly is a safe driver.

5) last step, go to www.nvidia.com download the latest linux drivers install them
6) Run /usr/pluto/bin/AVWizard_Run.sh and setup your nvidia card with FULL ALPHA BLENDING

HAVE A NICE DAY,

i got it working 5min ago and i am pretty over excited, so i\ve probably missed something, please feel free to contact me :)
if you dont get it working, i\ll try to help.


BEST REGARDS
Kurt.
Title: Re: Why only vesa?
Post by: fdawg4l on March 30, 2007, 05:01:53 am
That's a no go for me.  I tried doing the changes you suggested (editing the hwdata file), ensured that the nvidia kernel drivers were installed for my kernel, and still every time I reboot, it uses the vesa driver.

Is there some way to skip the autodetection and set the driver options manually?  All I need is the driver set to nvidia and the option "TVStandard" set to "HD1080i".

I don't understand why this is so difficult.  I've reinstalled ubuntu twice followed by MCE and still it refuses to budge past vesa at 640x480.
Title: Re: Why only vesa?
Post by: k84 on March 30, 2007, 05:29:49 am
Hi,

If you issue this command and send me the file, i can try to take a look at it.
if you take a look at the file afterwards (the output.txt) does it state that for instance nvidia_drv is not found?
If so, that would explain why it falls back to vesa.

strace lshwd -id 2> output.txt

What output do you now have?
lshwd -id

If you\ve done everything correct, and everything is working for you  it should say (nvidia) After VGA compatbile card.

Tell me how it goes.
Best regards
kurt.

 
Title: Re: Why only vesa?
Post by: mking on April 02, 2007, 01:04:59 am
How do you modify the cards file? I don't have the right permissions. I'm a Linux newbe...and I'm trying to get my Geforce 6600 Gt driver to work.
Title: Re: Why only vesa?
Post by: k84 on April 02, 2007, 01:31:40 am
before you modify you have to become root user
to do this:

type: sudo su
then enter the password for your user.

You should now have become root user, and have permission to edit the file.

Title: Re: Why only vesa?
Post by: efiniti on April 03, 2007, 06:13:45 am
thanks k84!  it worked for me.  :)

well not at first, but I did a reinstall and right before I restarted the ubuntu box after installing linuxmce I made sure to edit that file.  once i rebooted i ran through the wizard and I successfully choose UI2. 
Title: Re: Why only vesa?
Post by: wolfbite on April 03, 2007, 10:28:53 am
sudo su
password
nano -w /etc/X11/xorg.conf
page dn to bottom then come up looking for "vesa"
change to "nvidia"

press f2 then y then enter
done
Title: Re: Why only vesa?
Post by: bawbag31 on April 03, 2007, 12:37:36 pm
OK, I can confirm that this method worked a charm for me.  I now have full alpha blending, and it looks great.  Thanks for the fix/workaround, k84!  I am now working on getting a resolution of 1440x900 (16:10) ...
Title: Re: Why only vesa?
Post by: k84 on April 03, 2007, 01:01:30 pm
Good to hear you got it running efiniti1 and bawbag31.

wolfbite, the problem is that linuxmce constantly changes it back. and tries it's own drivers vesa or nv.
Title: Re: Why only vesa?
Post by: k84 on April 04, 2007, 06:24:23 am
Hi,

After some restarting, and more testing ( to check if the system works, and is more the less reliable ) an unpleasant thing happened today, when linuxmce was "Starting up", i noticed it downloaded updates, and installed them/Applied them automatically.

Guess what got the transparancy issue again, got a little frustrated so i browsed the /usr/pluto/bin directory and found a file called DownloadUpdates.sh, and added another exit;

Did the same thing with ApplyUpdates.sh (just to be sure).

Then i ran the NVIDIA .run file again (from nvidia.com) and did a reboot, hopefully things will be more reliable now.

Didnt use much time researching, but guess it updated my kernel and rendered the nvidia kernel module useless, or it removed some of the nvidia files. either way, the fix wasn't hard.

I want a system which doesnt update itself upon bootup,  i'll just do apt-get update myself and write it on my calender for every other week or so :)

Title: Re: Why only vesa?
Post by: mking on April 04, 2007, 06:46:09 pm
I tried the above procedure...and it did not work for me.  I think it does not work because the Nvidia install 9755 install may not have worked.  Originally the only way I could get the NVidia driver to install was to run it in maintenance mode RunLevel 1. The install warned me that it should be done in RunLevel 3. Here's the problem...I cannot run in RunLevel 3 because a telinit 3 will boot me to the Unbuntu GUI. I would like to set the RunLevel to 3 in maintenance mode without the system booting me into Unbuntu. I believe if I can get into RunLevel 3 and then install the NVidia-Linux-x86-1.0-9755.pkg1.run driver...it should go well. Then I should be able to follow the procedure descibed in this thread and finally boot into Unbuntu, goto the Screen Resolution and set it to something other that 640x480. Then I will install the LinuxMCE.

My main question here is how to boot into maintenance mode and set the RunLevel to 3.

Note: Telinit 3 ...does not work.
         There is no inittab file to change.




Title: Re: Why only vesa?
Post by: sixback on April 04, 2007, 11:02:25 pm

I have a 6800 AGP.  I've installed the latest Nvidia Driver in su/runlevel 1.
Seemed to work fine. I have two issues however.

Ubuntu desktop always defaults to 1024x768 when my native monitor res is 1280x1024
I change the res with the nvidia server settings applet, apply and write the xorg.conf file but the change doesn't stick on the following reboot even though the xorg.conf looks correct. I have manually tried editing the xorg.conf too.

On LinuxMCE start, I see the Nvidia driver splash screen flash, judging from the size of the mouse cursor the res looks to be 1280x1024 but the orbitor quickly displays a error message to check the transparency manager to make sure it is loaded. Click OK get grey screen of death.

Will editing the cards file and running avwizard sh script fix this?

Thanks

Title: Re: Why only vesa?
Post by: bawbag31 on April 07, 2007, 01:01:52 am
@mking

Hi,
My favorite method of installing the driver is to change xorg.conf BEFORE trying to install any nvidia drivers.  ie driver nv becomes driver nvidia (if none of this makes sense, reply and I'll give more details).  Then, assuming you have installed everything you need to build a kernel module and the nvidia driver installer is in your home directory, you can ...

Logout then hit ctrl-alt-backspace to restart your xserver
(this will fail, and choosing no to viewing the error messages will drop you to a text mode login promt)

Log in

Type 'sudo sh ./NVIDIA*.run' and enter your password again

This method has always worked for me.
Title: Re: Why only vesa?
Post by: k84 on April 07, 2007, 07:56:03 pm
sixback, yes i bet your issues will be fixed using the method i've described, feel free to PM me if you got any questions.
bawbag31: That sounds correct if you are using a generic linux distro, but have you tried this with linuxMCE (it basically takes over your system, xorg configuration included), and changes the file upon startup

e.g to change resoloution in linuxMCE avwizard OR the admin page /(click media director) should be the correct way, then full regen orbiter/all.
And you also would need to quick reload router i think.

Pluto's xorg file is called xorg.conf.pluto /etc/X11/xorg.conf.pluto

Hope this helps anyone.
Title: Re: Why only vesa?
Post by: bawbag31 on April 07, 2007, 08:33:49 pm
It's worth mentioning that when I installed LinuxMCE I chose the 'use primarily as a PC' option.  I used the above method for installing the latest nvidia driver in ubuntu BEFORE installing LinuxMCE (I also installed Beryl to make sure compositing was working).  Once it is installed, the nvidia driver is usable by both ubuntu and LinuxMCE.  It seems to me that if you run LinuxMCE on top of ubuntu, there are two seperate xservers running.  Ubuntu uses xorg.conf (Ctrl-Alt-F7) and LinuxMCE uses xorg.conf.pluto (Ctrl-Alt-F11).  You should change BOTH of these to nvidia.  As for the resolutions, I tried changing xorg.conf.pluto to 1440x900 (my monitor's native resolution) and it did indeed work ... almost - it doesn't change the size of the UI to match.  I am still lamenting the fact that custom resolutions are not an option.

I should also point out that the home-built nvidia module cannot live along side the one available in the distro repositories.  You need to make sure that nvidia-glx, nvidia-kernel-common and the linux-restricted-modules packages are NOT installed.

I should also point out that if you try to select nvidia as the driver through the admin web page, it will start downloading an installing the above mentioned packages and break X.  A simple 'sudo apt-get remove nvidia-glx nvidia-kernel-common' should fix things again.
Title: Re: Why only vesa?
Post by: SciFi on April 09, 2007, 05:05:06 pm
Hi

I cant even begin to tell you how frustrated i am right now!. I have spent over 6 hours now trying to get the nviida driver to work :(.

Yesterday i begun installing Linuxmce after looking at the video floating around on youtube.com. I have been running Gentoo linux with mythtv
for maybe 3-4 years now and thought i would try this. The guy on the video said that "Just pop in the installation cd and away we go" i guess not!

Nevermind, i hope someone can help me :)

I have set up a real core server (not a hybrid) it is running on a asus pundit machine with an intergrated sis graphics card.

From the core i boot a diskless pc that contains my Nvidia 6200 agp card.

the diskless machine workes with Ui1 and is using the opensource nv driver. If i try to use another UI, X starts but only with the grey screen and mouse pointer. I have tried renstalling the restricted modules a couple of times and edited the /usr/share/hwdata/Cards file, but to no vail. Tried also to compile the binary driver from the core machine but the nvidia-installer bugs out because i dont have a nvidia card in that machine :(.

Please someone, How can i get the nvidia driver to work with my diskless system?

Best regards Staffan
Title: Re: Why only vesa?
Post by: k84 on April 09, 2007, 09:06:45 pm
Can you paste output from: lshwd -id
from your diskless system?

Title: Re: Why only vesa?
Post by: SciFi on April 09, 2007, 09:36:34 pm
Hi

This is from my MD

00:00.0 8086:2570:1043:80f2 Host bridge: Intel Corp.|82865G [Springdale-G] Chipset Host Bridge (intel-agp)
00:01.0 8086:2571:0000:0000 PCI bridge: Intel Corp.|82865G/PE/P Processor to AGP Controller (unknown)
00:1d.0 8086:24d2:1043:80a6 USB Controller|UHCI: Intel Corp.|USB Controller (uhci_hcd)
00:1d.1 8086:24d4:1043:80a6 USB Controller|UHCI: Intel Corp.|USB Controller (uhci_hcd)
00:1d.2 8086:24d7:1043:80a6 USB Controller|UHCI: Intel Corp.|USB Controller (uhci_hcd)
00:1d.3 8086:24de:1043:80a6 USB Controller|UHCI: Intel Corp.|82801EB USB EHCI Controller #2 (uhci_hcd)
00:1e.0 8086:244e:0000:0000 PCI bridge: Intel Corp.|82820 815e (Camino 2) Chipset PCI (hw_random)
00:1f.0 8086:24d0:0000:0000 ISA bridge: Intel Corp.|82801EB ISA Bridge (LPC) (i810-tco)
00:1f.1 8086:24db:1043:80a6 IDE interface: Intel Corp.|82801EB ICH5 IDE (ata_piix)
00:1f.3 8086:24d3:1043:80a6 SMBus: Intel Corp.|82801EB SMBus (i2c-i801)
01:00.0 10de:0221:0000:0000 VGA compatible controller: nVidia Corp.|GeForce 6200 (nv)
02:05.0 11ab:4320:1043:811a Ethernet controller: Marvell Semiconductor Inc.|88E8001 Gigabit Lan PCI Controller (skge)
02:0a.0 1102:0002:1102:0020 Multimedia audio controller: Creative Labs|SB Live! (audio) (snd-emu10k1)
02:0a.1 1102:7002:1102:0020 Input device controller: Creative Labs|SB Live! (joystick) (emu10k1-gp)
---:--- 0000:0000:0000:0000 Mouse: Generic PS/2 Wheel Mouse [/dev/psaux] (msintellips/2)
Title: Re: Why only vesa?
Post by: k84 on April 09, 2007, 10:40:12 pm
01:00.0 10de:0221:0000:0000 VGA compatible controller: nVidia Corp.|GeForce 6200 (nv)

Try to edit the Cards file on that system, like i've described some posts earlier,
since this system is showing that it will install/use the "nv" driver

"A successfull" edit of the Cards file should give you nvidia
Title: Re: Why only vesa?
Post by: efiniti on April 10, 2007, 08:19:24 am
has anyone else tried going into the admin page, going to media director, and selecting the core/hybrid to GeForce?  I think the core tries to download nvidia-glx and i assume configure it.  Course I doubt you'd get anywhere though.
Title: Re: Why only vesa?
Post by: SciFi on April 10, 2007, 09:29:36 am

Thank you for replying k84

I have tried to edit the Cards file many times, but if i exchange all nv with nvidia the modules cant be found and it uses the vesa driver instead.

I seem to have a bigger problem thought. I did not manage to get mythtv working with Linuxmce, and it seems that hardly anyone has gotten it going. The frontend just quits with no logs saying why it quits. If i canĀ“t get it going tonight i must revert back to my old mythtv system because i havent been able to watch tv now for a couple of days :(

Best regards Staffan
Title: Re: Why only vesa?
Post by: k84 on April 10, 2007, 01:25:27 pm
Hi,

If you read my steps carefully you should see that lshwd -id changes from nv to nvidia, and it will fallback to vesa if it can't find the files, this is when you install the NVIDIA*  file.


Hope you get it running
Title: Re: Why only vesa?
Post by: SciFi on April 10, 2007, 02:15:15 pm
Hi again

The problem is i cant install the drivers on either the core or media director. The drivers needs to be compiled and you cant install the compiled modules on the core because it does not have an nvidia card. And on the md a dont have the headers files + compiler for building the drivers. trying to install the restricted modules does not seem to work either.

I might try to copile the drivers on the core than manualy copy the modules to the md.

/Staffan
Title: Re: Why only vesa?
Post by: SciFi on April 10, 2007, 07:46:31 pm

Update

I managed to get the nvidia binary driver working by compiling it on the core then manually copy the modules + files to the media director :)

Now the big problem, getting mythtv to work

/Staffan
Title: Re: Why only vesa?
Post by: thynk on April 19, 2007, 10:57:55 am
I've got the same problem, hacking the Cards file didn't help.  I have a very generic GeForce 6500 256 that lshwd doesn't see as a valid card.  I've already manually installed the drivers before hand (with Envy) , edited the xorg.conf.pluto file but it kills it every time I edit it.  AVWizardDone = 1 is set in pluto.conf

Is there a way to hack the $%T$@$@SSS#@ Xconfigure script to force it to the nvidia driver? or not make changes to the .conf file (as I'm writing this, I am trying it out with exit; in the Xconfigure script  seems to be working so far, but it would be nice if it would play just a little bit nicer with unknown cards :-)

edit:after killing off the Xconfigure.sh script to keep it from editing the xorg.conf.pluto file I get the following errors...
Code: [Select]
1       04/19/07 04:35:46       /usr/pluto/bin/Start_X.sh (server)      Starting X server (client: /usr/bin/xfwm4; parms: --conpositor=off)
1       04/19/07 04:35:47       /usr/pluto/bin/Start_X.sh (server)      X server: backround; AlphaBlending: 1
1       04/19/07 04:35:48       Xconfigure (server)     Display Driver: nvidia
1       04/19/07 04:35:50       /usr/pluto/bin/Start_X.sh (server)      Starting X server (client: /usr/bin/xfwm4; parms: --conpositor=off)
1       04/19/07 04:35:51       /usr/pluto/bin/Start_X.sh (server)      X server: backround; AlphaBlending: 1
3       04/19/07 04:35:52       LaunchOrbiter (server)  xfwm4 failed to start
1       04/19/07 04:35:53       Xconfigure (server)     Display Driver: nvidia
1       04/19/07 04:35:56       /usr/pluto/bin/Start_X.sh (server)      Starting X server (client: /usr/bin/xfwm4; parms: --conpositor=off)
1       04/19/07 04:35:57       /usr/pluto/bin/Start_X.sh (server)      X server: backround; AlphaBlending: 1
3       04/19/07 04:35:58       19 (spawning-device)    Device died... count=33/50 dev=19
1       04/19/07 04:36:08       19 (spawning-device)    Starting... 34
1       04/19/07 04:36:08       19 (spawning-device)    Found ./LaunchOrbiter.sh

Here is the output from lshwd -id
Code: [Select]
dcerouter_13640:~# lshwd -id
00:00.0 10de:03ea:1849:03ea RAM memory: nVidia Corporation|MCP61 Memory Controller (unknown)
00:01.0 10de:03e0:1849:03e0 ISA bridge: nVidia Corporation|MCP61 LPC Bridge (unknown)
00:01.1 10de:03eb:1849:03eb SMBus: nVidia Corporation|MCP61 SMBus (unknown)
00:01.2 10de:03f5:1849:03eb RAM memory: nVidia Corporation|MCP61 Memory Controller (unknown)
00:02.0 10de:03f1:1849:03f1 USB Controller|OHCI: nVidia Corporation|MCP61 USB Controller (unknown)
00:02.1 10de:03f2:1849:03f2 USB Controller|EHCI: nVidia Corporation|MCP61 USB Controller (unknown)
00:04.0 10de:03f3:0000:0000 PCI bridge|Subtractive decode:  (unknown)
00:05.0 10de:03f0:1849:0862 Non-VGA unclassified device: nVidia Corporation|MCP61 High Definition Audio (unknown)
00:06.0 10de:03ec:1849:03ec IDE interface: nVidia Corporation|MCP61 IDE (amd74xx)
00:07.0 10de:03ef:1849:03ef Bridge: nVidia Corporation|MCP61 Ethernet (unknown)
00:08.0 10de:03f6:1849:03f6 IDE interface: nVidia Corporation|MCP61 SATA Controller (sata_nv)
00:09.0 10de:03e8:0000:0000 PCI bridge:  (unknown)
00:0b.0 10de:03e9:0000:0000 PCI bridge:  (unknown)
00:0c.0 10de:03e9:0000:0000 PCI bridge:  (unknown)
00:0d.0 10de:03d1:1849:03d1 VGA compatible controller:  (vesa)
00:18.0 1022:1100:0000:0000 Host bridge: Advanced Micro Devices|K8 [Athlon64/Opteron] HyperTransport Technology Configuration (unknown)
00:18.1 1022:1101:0000:0000 Host bridge: Advanced Micro Devices|K8 [Athlon64/Opteron] Address Map (unknown)
00:18.2 1022:1102:0000:0000 Host bridge: Advanced Micro Devices|K8 [Athlon64/Opteron] DRAM Controller (unknown)
00:18.3 1022:1103:0000:0000 Host bridge: Advanced Micro Devices|K8 [Athlon64/Opteron] Miscellaneous Control (amd64-agp)
01:08.0 10ec:8139:10bd:0320 Ethernet controller: Realtek Semiconductor|EP-320X-R (8139too)
02:00.0 10de:0160:0000:0000 VGA compatible controller: nVidia Corp.|Unknown (generic) (vesa)
---:--- 0000:0000:0000:0000 Mouse: Generic PS/2 Wheel Mouse [/dev/psaux] (msintellips/2)
Title: Re: Why only vesa?
Post by: k84 on April 19, 2007, 02:22:49 pm
Hi there,

I guess the first time you laucned the lshwd -id it stated that it would use driver NV for your "VGA compatible card" as you can read in my walkthrough i had same issue, and now it's trying to use the VESA driver since it can not find the NVIDIA drivers to use,

Have you tried installing them now?
www.nvidia.com


Best Regards
K84

Title: Re: Why only vesa?
Post by: thynk on May 06, 2007, 03:48:34 am
I guess the first time you laucned the lshwd -id it stated that it would use driver NV for your "VGA compatible card" as you can read in my walkthrough i had same issue, and now it's trying to use the VESA driver since it can not find the NVIDIA drivers to use,

The issue turned that lshwd -id wasn't picking the right diver for this card because it always came back as unknown.  I fixed this by tracing down where in the code it was selecting the driver and hacked a few lines in /usr/pluto/bin/Utils.sh to read

     
Code: [Select]
   local VideoDriver=$(lshwd | grep ' VGA ' | head -1 | sed 's/^.*(\([^()]*\)).*$/\1/')
        case "$VideoDriver" in
                nv|vesa) PackageIsInstalled nvidia-glx && VideoDriver="nvidia" ;;
                radeon|ati) PackageIsInstalled fglrx-driver && VideoDriver="fglrx" ;;
                "") VideoDriver="nvidia" ;; # just-in-case default
        esac

Another issue was trying to install while using the PCI-E card, I had to do a fresh install of 6.10 and install LMCE, hack the script, reinstall the drivers (only worked when installed with Envy), switch the system over to the 6500 and manually edit my xorg.conf file (for some reason the nvidia-settings didn't configure the 6500, so I had to look up what the pci-e slot was and change it there).

Lots of hassle, I'd like to see the next revision be a little smarter and check for already installed video drivers instead of forcing it's own on the system.

HTH someone else!

Stu


Title: Re: Why only vesa?
Post by: siberian on May 22, 2007, 09:47:02 am
This worked great in getting my nVidia card up and running and actually accepting the 720P, thanks Kurt!!

Now I just have the infamous 'nVidia wont output Component video' problem to debug. Back to google..

John-

I GOT IT WORKING!
IT\s pretty easy but NOT plug and play.

...

HAVE A NICE DAY,


BEST REGARDS
Kurt.
Title: Re: Why only vesa?
Post by: spartacus13b on June 02, 2007, 03:41:26 am
I have a Dell XPS system that had Windows Vista on it until 2 days ago. Vista crashed on me so I decided to install linuxmce instead.

I am running into the following problem, I install everything on my systems and then once I am done with the wizard the screen gos black and shows some distorted images on it.

I have an Intel 945 graphics adaptter built into my machine. And it seems to recognise it just fine.

however when I do lshwd it tells me it is using vesa as the driver.

How can I fix this


Please keep in mind that I am brand new to this so I only know a few commands......
Title: Re: Why only vesa?
Post by: dale3h on June 16, 2007, 02:26:03 am
I haven't had any success with the nvidia drivers to use UI2. The first time I installed LinuxMCE, I already had the Automatix2 nVidia drivers installed, and it looked great, dual monitors working with max resolution, but I wanted UI2 with alpha blending. So I set out on a journey to get it working!

I'm on my 9th install of Kubuntu/LinuxMCE. Each time I install LinuxMCE, I start with a fresh copy of Kubuntu. I might want to ghost this partition soon if this is going to be many more times before I get it working.

Anywho, I took the necessary steps that Kurt suggested, installing the latest Nvidia drivers from their website. When I reboot, it just sits at a black window with a flashing cursor. So I hit Ctrl+Alt+F1 to get to another console, and I restore my xorg.conf, startx, and voila, I'm back in.

Then I did some comparing of the xorg.conf that failed and the xorg.conf that was good. The only difference was:

Non-Working xorg.conf: Did not contain DRI; used nvidia driver; did not specify BusID under "Device" heading
Working xorg.conf: Contained DRI; used vesa driver; specified a BusID under the "Device" heading: BusID      "PCI:1:0:0"

Click here to view working [vesa driver] xorg.conf (http://dale3h.com/xorg_conf_vesa.txt)
Click here to view non-working [nvidia driver] xorg.conf (http://dale3h.com/xorg_conf_nvidia.txt)

Now when I try to modify just that driver line to say "nvidia", then I type "startx" it results in:
Click here to view non-working [nvidia driver] startx log (http://dale3h.com/x_log_bad.txt)

When I change it back to "vesa" and then type "startx" it results in:
Click here to view working [vesa driver] startx log (http://dale3h.com/x_log_good.txt)

And finally, my lshwd -id output:
Code: [Select]
00:00.0 1106:3189:1106:3189 Host bridge: VIA Technologies Inc.|VT8377 CPU to PCI Bridge (via-agp)
00:01.0 1106:b168:0000:0000 PCI bridge: VIA Technologies Inc.|PCI-to-PCI Bridge (AGP) (unknown)
00:0e.0 13f6:0111:10fd:a715 Multimedia audio controller: C-Media Electronics Inc.|CM8738 (snd-cmipci)
00:0f.0 1103:0004:1103:0001 RAID bus controller: Triones|HPT366 (hptraid)
00:10.0 1106:3038:1106:3038 USB Controller|UHCI: VIA Technologies Inc.|VT82C586B USB (uhci_hcd)
00:10.1 1106:3038:1106:3038 USB Controller|UHCI: VIA Technologies Inc.|VT82C586B USB (uhci_hcd)
00:10.2 1106:3038:1106:3038 USB Controller|UHCI: VIA Technologies Inc.|VT82C586B USB (uhci_hcd)
00:10.3 1106:3104:1106:3104 USB Controller|EHCI: VIA Technologies Inc.|VT8235 USB Enhanced Controller (ehci-hcd)
00:11.0 1106:3177:1106:3177 ISA bridge: VIA Technologies Inc.|VT8233A PCI to ISA Bridge (via-ircc)
00:11.1 1106:0571:1106:0571 IDE interface: VIA Technologies Inc.|VT82C586 IDE [Apollo] (via82cxxx)
00:12.0 1106:3065:1106:0102 Ethernet controller: VIA Technologies Inc.|VT6102 [Rhine II 10/100] [߷] (via-rhine)
01:00.0 10de:00f6:1682:217e VGA compatible controller: nVidia Corp.|GeForce 6600 GS (nvidia)
---:--- 0000:0000:0000:0000 Mouse: Generic PS/2 Wheel Mouse [/dev/psaux] (msintellips/2)

Most people would give up after 3 bad installs...but not me. I went out and bought a 42" 1080p LCD just so I could have a decent TV for LinuxMCE. It wasn't until the 4th of 5th install that I actually got to see the LinuxMCE interface running.

Any advice/help is very much appreciated.