Are you a spammer

Please note, that the first 3 posts you make, will need to be approved by a forum Administrator or Moderator before they are publicly viewable.
Each application to join this forum is checked at the Stop Forum Spam website. If the email or IP address appears there when checked, you will not be allowed to join this forum.
If you get past this check and post spam on this forum, your posts will be immediately deleted and your account inactivated.You will then be banned and your IP will be submitted to your ISP, notifying them of your spamming. So your spam links will only be seen for an hour or two at most. In other words, don't waste your time and ours.

This forum is for the use and enjoyment of the members and visitors looking to learn about and share information regarding the topics listed. It is not a free-for-all advertising venue. Your time would be better spent pursuing legitimate avenues of promoting your websites.

Nvidia issues post here please.

Help & support for Ultimate Edition 2.6


Re: Nvidia issues post here please.

Postby stanca » Sat May 22, 2010 7:15 am

I guess the kernel developpers are moving too fast,maybe.I had the same issue in Fedora 13 Beta also.
Intel H61 ASrock H61M-VS Motherboard,
Cpu Intel Ci3 13-2100 3.10Ghz 64bit 3MB Box,
RAM 4GB DDR3 1333MHz Elixir,
Palit Nvidia Geforce 210 1GB DDR3 PCI-E.
Dual-boot Ultimate Edition 3.4 x86_64/Windows 8 x64.
Linux user # 492560.
"This is Linux land!In silent nights you can hear Windows machines rebooting!..."
http://www.youtube.com/user/laur1969 http://stanca-ultimateeditionromania.blogspot.com/#

Image
Image
Image
Image
User avatar
stanca
U.E. God
U.E. God
 
Posts: 1613
Joined: Sun Nov 02, 2008 11:48 am
Location: Bucharest,Romania,EU,44'25"N,26'07"E.
Age: 54
Operating System: Ultimate Edition Beta Tester



Re: Nvidia issues post here please.

Postby 2hot6ft2 » Sat May 22, 2010 5:09 pm

stanca wrote:I guess the kernel developpers are moving too fast,maybe.I had the same issue in Fedora 13 Beta also.

This also sounds like the same thing as on a fresh 64 bit install where the 2.6.32-22 kernel was compiled using a version that was different than the nvidia drivers.
Image
HP G60-125NR - AMD Turion X2 64 - nVidia GeForce 8200M G - 128 GB SSD Dual boot - Ultimate Edition, Win 10 Pro
HP G60-121WM - AMD Sempron SI-40 - nVidia GeForce 8200M G - 128 GB SSD - Dual boot - Ultimate Edition, Win 10 Pro
Custom build, Rosewill Challenger ATX Gaming Case, AMD Phenom II x4 955 C3 rev., MSI 870A-G54, 2x ATI HD4850 512MB /256bit GDDR3 & dual precision, GSkill 8GB 1600 RAM - Multi boot - Ultimate Edition, Win 10 Pro, Beta Testing
User avatar
2hot6ft2
Moderator
 
Posts: 533
Joined: Sun May 25, 2008 12:30 pm
Location: Alabama, USA
Operating System: Ultimate Edition 3.2 64 BIT



Re: Nvidia issues post here please.

Postby t-gil » Mon May 24, 2010 3:28 pm

Attempting to build out an HP dc7800p, intel core 2, 8gb mem, 160gb sata, nvidia quadro nvs 450, 4 phillips 190b monitors connected via DVI. Downloaded and burned ISO, no prob. Booted and ran off the DVD no prob, it even recognized the quadro card and let me know to install/activate the appropriate driver. Happy so far, looks like this is going to support the hardware platform, go for install. Install completes, still happy, time for the reboot.

Upon reboot, not so happy, no video. No sweat, I need to install the nvidia driver, off to nvidia land to download the latest driver for my card. Got it, now how to install on a system with no console, hhmmm, ssh to the rescue. Oops, ssh server not installed by default, no prob, apt-get intall ssh-server, done. SCP the nvidia driver file to the box, ssh into the box, service stop gdm (to kill the x server), telinit 3 (because I'm paranoid and nvidia typically likes this on other distros), run the install and KA-POW, kernel mod fails to load. The exact error message has been previously posted in this thread so I'm not going to bore you it (blah, blah, blah, different gcc, blah, blah, rivafb/nvidia/fb, blah, blah, blah).

OK, time to hit the forums and start digging, I'm not the first to run into this. Located LOTS of good info and possible fixes, still no joy. Should mention at this point that it's the 32 bit version (195.36.24) that's being installed on a PAE kernel. (TheeMahn's post in this thread from 05.02.10 states this should not be an issue on 32 bit, but that does not appear to be the case here). I've tried dumping the 2.6.32-22 kernel for the .21 version, still no joy.

Any thoughts on this one?
t-gil
U.E. Newbie
U.E. Newbie
 
Posts: 4
Joined: Mon May 24, 2010 1:09 pm
Operating System: Ultimate Edition 3.2 32 BIT



Re: Nvidia issues post here please.

Postby Admin-Amir » Mon May 24, 2010 4:09 pm

Hello t-gil welcome to the U.E Forum. <BREW> ;)

Please look on this Guide and follow the process - it will get the new driver for you after the process done.
Restart your machine,when you will be back to Desktop=>open terminal - Update/Upgrade,
Then close the terminal=>synaptic Refresh/Reload - mark all Upgrade - Apply.
Then go to the system=>Adnin=>Hardware Drivers=>see if you have the new Driver there - mark and Apply.

The process for you is here:
viewtopic.php?f=68&t=4821
Admin-Amir
 



Re: Nvidia issues post here please.

Postby t-gil » Mon May 24, 2010 4:37 pm

Thanks for the welcome and response Amir.

Successfully upgraded the kernel manually via ssh and the CLI. Rebooted and verified it's running the .34 kernel. The problem is that I've got no video output what-so-ever on the machine I'm working on so I can't see the desktop let alone log into it.

I tried the manual install of the nvidia driver and it now complains specifically about the gcc version mis-match. Do I need to downgrade gcc from 4.4 to 4.2 in order to get this driver compiled and installed?

Thanks again.
t-gil
U.E. Newbie
U.E. Newbie
 
Posts: 4
Joined: Mon May 24, 2010 1:09 pm
Operating System: Ultimate Edition 3.2 32 BIT



Re: Nvidia issues post here please.

Postby Admin-Amir » Mon May 24, 2010 4:45 pm

t-gil you very welcome. ;)


OK - 2 things here.
1- open Ubuntu Tweak=>3 party=> you have the Update to the Nvidia there to mark and Refresh.
Then when it is done - close Ubuntu Tweak => open terminal - Update/Upgrade,
see if it will upgrade the missing packages,if not - then install the missing packages from synaptic.
2- if under system=>Admin=>Hardware Drivers you have Apply the new Driver 3D and it did not down
the packages for your Card = yes install the missing packages from synaptic.
The Team has Approved that it cover good the Nvidia Cards.
Admin-Amir
 



Re: Nvidia issues post here please.

Postby t-gil » Mon May 24, 2010 4:51 pm

Thanks for the quick response Amir. I would love to try what you are suggesting but I think you are missing one of the key challanges I have. I have no GUI desktop to work with, the only access into this system that I have is via SSH, so whatever I try has to be done from the command line.

Can what you propose be accomplished from a shell prompt?
t-gil
U.E. Newbie
U.E. Newbie
 
Posts: 4
Joined: Mon May 24, 2010 1:09 pm
Operating System: Ultimate Edition 3.2 32 BIT



Re: Nvidia issues post here please.

Postby Admin-Amir » Mon May 24, 2010 5:02 pm

t-gil.

Have you try to use from the command prompt:

Code: Select all
sudo startx


Code: Select all
gdm start
Admin-Amir
 



Re: Nvidia issues post here please.

Postby t-gil » Tue May 25, 2010 8:15 am

Amir, sorry for the delay in response. If I remove the Quadro card and use the integrated video the system will boot normally to the login prompt and subsequently to the desktop. Once the Quadro card is installed, the integrated video is disabled and nothing beyond the grub menu is visually displayed on any monitor. As I have said before, the system does boot and is accessable via the network.

I spent some time this morning trolling through the syslog (something I should have done yesterday) and found what I have posted below. In summary, I think the problem is with the nouveaufb driver. It "appears" to recognize the card but is unsuccessful when initializing it which subsequently leads to the failure of gdm to launch.

Please correct me if I'm wrong, but if I were to disable the load of the nouveaufb driver, the system "should" boot as it does now, headless, and I "should" be able to login via ssh and run the manual nvidia install.

Am I on the right track here?


May 24 16:53:53 hostname kernel: [ 2.364110] ACPI Exception: AE_NOT_FOUND, Evaluating _DOD (20100121/video-1908)
May 24 16:53:53 hostname kernel: [ 2.364354] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input2
May 24 16:53:53 hostname kernel: [ 2.364481] ACPI: Video Device [GFX0] (multi-head: no rom: yes post: no)
May 24 16:53:53 hostname kernel: [ 2.386251] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
May 24 16:53:53 hostname kernel: [ 2.386325] e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
May 24 16:53:53 hostname kernel: [ 2.386793] [drm] Initialized drm 1.1.0 20060810
May 24 16:53:53 hostname kernel: [ 2.418607] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
May 24 16:53:53 hostname kernel: [ 2.418705] alloc irq_desc for 19 on node -1
May 24 16:53:53 hostname kernel: [ 2.418708] alloc kstat_irqs on node -1
May 24 16:53:53 hostname kernel: [ 2.418714] e1000e 0000:00:19.0: PCI INT B -> GSI 19 (level, low) -> IRQ 19
May 24 16:53:53 hostname kernel: [ 2.418781] e1000e 0000:00:19.0: setting latency timer to 64
May 24 16:53:53 hostname kernel: [ 2.418854] alloc irq_desc for 27 on node -1
May 24 16:53:53 hostname kernel: [ 2.418856] alloc kstat_irqs on node -1
May 24 16:53:53 hostname kernel: [ 2.418863] e1000e 0000:00:19.0: irq 27 for MSI/MSI-X
May 24 16:53:53 hostname kernel: [ 2.426239] nouveau 0000:03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
May 24 16:53:53 hostname kernel: [ 2.426307] nouveau 0000:03:00.0: setting latency timer to 64
May 24 16:53:53 hostname kernel: [ 2.428918] [drm] nouveau 0000:03:00.0: Detected an NV50 generation card (0x298d00a2)
May 24 16:53:53 hostname kernel: [ 2.433016] [drm] nouveau 0000:03:00.0: Attempting to load BIOS image from PRAMIN
May 24 16:53:53 hostname kernel: [ 2.433092] [drm] nouveau 0000:03:00.0: ... BIOS signature not found
May 24 16:53:53 hostname kernel: [ 2.433151] [drm] nouveau 0000:03:00.0: Attempting to load BIOS image from PROM
May 24 16:53:53 hostname kernel: [ 2.588439] usbcore: registered new interface driver hiddev
May 24 16:53:53 hostname kernel: [ 2.617995] [drm] nouveau 0000:03:00.0: ... appears to be valid
May 24 16:53:53 hostname kernel: [ 2.618057] [drm] nouveau 0000:03:00.0: BIT BIOS found
May 24 16:53:53 hostname kernel: [ 2.618116] [drm] nouveau 0000:03:00.0: Bios version 62.98.6e.00
May 24 16:53:53 hostname kernel: [ 2.618177] [drm] nouveau 0000:03:00.0: TMDS table revision 2.0 not currently supported
May 24 16:53:53 hostname kernel: [ 2.618248] [drm] nouveau 0000:03:00.0: Found Display Configuration Block version 4.0
May 24 16:53:53 hostname kernel: [ 2.618318] [drm] nouveau 0000:03:00.0: Raw DCB entry 0: 02000386 0f200010
May 24 16:53:53 hostname kernel: [ 2.618380] [drm] nouveau 0000:03:00.0: Raw DCB entry 1: 02000332 00020010
May 24 16:53:53 hostname kernel: [ 2.618440] [drm] nouveau 0000:03:00.0: Raw DCB entry 2: 040113a6 0f200010
May 24 16:53:53 hostname kernel: [ 2.618500] [drm] nouveau 0000:03:00.0: Raw DCB entry 3: 04011342 00020010
May 24 16:53:53 hostname kernel: [ 2.618561] [drm] nouveau 0000:03:00.0: DCB connector table: VHER 0x40 5 16 4
May 24 16:53:53 hostname kernel: [ 2.618622] [drm] nouveau 0000:03:00.0: 0: 0x00005046: type 0x46 idx 0 tag 0x07
May 24 16:53:53 hostname kernel: [ 2.618692] [drm] nouveau 0000:03:00.0: 1: 0x0000a146: type 0x46 idx 1 tag 0x08
May 24 16:53:53 hostname kernel: [ 2.618770] [drm] nouveau 0000:03:00.0: Adaptor not initialised
May 24 16:53:53 hostname kernel: [ 2.618829] [drm] nouveau 0000:03:00.0: Running VBIOS init tables
May 24 16:53:53 hostname kernel: [ 2.618891] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 0 at offset 0xDAA5
May 24 16:53:53 hostname kernel: [ 2.627343] input: Chicony USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input3
May 24 16:53:53 hostname kernel: [ 2.627478] generic-usb 0003:049F:0051.0001: input,hidraw0: USB HID v1.00 Keyboard [Chicony USB Keyboard] on usb-0000:00:1d.0-1/input0
May 24 16:53:53 hostname kernel: [ 2.668146] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 1 at offset 0xDEAA
May 24 16:53:53 hostname kernel: [ 2.696519] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 2 at offset 0xE67C
May 24 16:53:53 hostname kernel: [ 2.696639] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 3 at offset 0xE74A
May 24 16:53:53 hostname kernel: [ 2.708130] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table 4 at offset 0xEA00
May 24 16:53:53 hostname kernel: [ 2.708207] [drm] nouveau 0000:03:00.0: Parsing VBIOS init table at offset 0xEA65
.
.
.
May 24 16:53:53 hostname kernel: [ 2.732025] [drm] nouveau 0000:03:00.0: 0xCBB4: parsing output script 0
May 24 16:53:53 hostname kernel: [ 2.732093] [drm] nouveau 0000:03:00.0: 0xC8E8: parsing output script 0
May 24 16:53:53 hostname kernel: [ 2.732175] [drm] nouveau 0000:03:00.0: 0xCBB4: parsing output script 0
May 24 16:53:53 hostname kernel: [ 2.732235] [drm] nouveau 0000:03:00.0: 0xC8E8: parsing output script 0
May 24 16:53:53 hostname kernel: [ 2.732330] [drm] nouveau 0000:03:00.0: Detected 256MiB VRAM
May 24 16:53:53 hostname kernel: [ 2.872338] [TTM] Zone kernel: Available graphics memory: 427718 kiB.
May 24 16:53:53 hostname kernel: [ 2.872398] [TTM] Zone highmem: Available graphics memory: 1734184 kiB.
May 24 16:53:53 hostname kernel: [ 2.901196] [drm] nouveau 0000:03:00.0: 512 MiB GART (aperture)
May 24 16:53:53 hostname kernel: [ 2.901259] mtrr: type mismatch for dc000000,4000000 old: write-back new: write-combining
May 24 16:53:53 hostname kernel: [ 2.901597] [drm] nouveau 0000:03:00.0: Allocating FIFO number 1
May 24 16:53:53 hostname kernel: [ 2.907871] [drm] nouveau 0000:03:00.0: nouveau_channel_alloc: initialised FIFO 1
May 24 16:53:53 hostname kernel: [ 2.908866] [drm] nouveau 0000:03:00.0: Detected a DP output
May 24 16:53:53 hostname kernel: [ 2.908928] [drm] nouveau 0000:03:00.0: Detected a TMDS output
May 24 16:53:53 hostname kernel: [ 2.908987] [drm] nouveau 0000:03:00.0: Detected a DP output
May 24 16:53:53 hostname kernel: [ 2.909047] [drm] nouveau 0000:03:00.0: Detected a TMDS output
May 24 16:53:53 hostname kernel: [ 2.909107] [drm] nouveau 0000:03:00.0: Detected a DisplayPort connector
May 24 16:53:53 hostname kernel: [ 2.909220] [drm] nouveau 0000:03:00.0: Detected a DisplayPort connector
May 24 16:53:53 hostname kernel: [ 3.125416] [drm] nouveau 0000:03:00.0: allocated 1280x1024 fb: 0x40250000, bo f6b3ae00
May 24 16:53:53 hostname kernel: [ 3.125550] fb0: nouveaufb frame buffer device
May 24 16:53:53 hostname kernel: [ 3.125608] registered panic notifier
May 24 16:53:53 hostname kernel: [ 3.125667] [drm] Initialized nouveau 0.0.16 20090420 for 0000:03:00.0 on minor 0
May 24 16:53:53 hostname kernel: [ 3.125756] nouveau 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
May 24 16:53:53 hostname kernel: [ 3.125820] nouveau 0000:04:00.0: setting latency timer to 64
May 24 16:53:53 hostname kernel: [ 3.127959] [drm] nouveau 0000:04:00.0: Detected an NV50 generation card (0x298d00a2)
May 24 16:53:53 hostname kernel: [ 3.132272] [drm] nouveau 0000:04:00.0: Attempting to load BIOS image from PRAMIN
May 24 16:53:53 hostname kernel: [ 3.225632] [drm] nouveau 0000:04:00.0: ... appears to be valid
May 24 16:53:53 hostname kernel: [ 3.225693] [drm] nouveau 0000:04:00.0: BIT BIOS found
May 24 16:53:53 hostname kernel: [ 3.225752] [drm] nouveau 0000:04:00.0: Bios version 62.98.6e.00
May 24 16:53:53 hostname kernel: [ 3.225813] [drm] nouveau 0000:04:00.0: TMDS table revision 2.0 not currently supported
May 24 16:53:53 hostname kernel: [ 3.225884] [drm] nouveau 0000:04:00.0: Found Display Configuration Block version 4.0
May 24 16:53:53 hostname kernel: [ 3.225955] [drm] nouveau 0000:04:00.0: Raw DCB entry 0: 02000386 0f200010
May 24 16:53:53 hostname kernel: [ 3.226016] [drm] nouveau 0000:04:00.0: Raw DCB entry 1: 02000332 00020010
May 24 16:53:53 hostname kernel: [ 3.226076] [drm] nouveau 0000:04:00.0: Raw DCB entry 2: 040113a6 0f200010
May 24 16:53:53 hostname kernel: [ 3.226137] [drm] nouveau 0000:04:00.0: Raw DCB entry 3: 04011342 00020010
May 24 16:53:53 hostname kernel: [ 3.226197] [drm] nouveau 0000:04:00.0: DCB connector table: VHER 0x40 5 16 4
May 24 16:53:53 hostname kernel: [ 3.226258] [drm] nouveau 0000:04:00.0: 0: 0x00005046: type 0x46 idx 0 tag 0x07
May 24 16:53:53 hostname kernel: [ 3.226328] [drm] nouveau 0000:04:00.0: 1: 0x0000a146: type 0x46 idx 1 tag 0x08
May 24 16:53:53 hostname kernel: [ 3.226406] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 0 at offset 0xDAA5
May 24 16:53:53 hostname kernel: [ 3.276150] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 1 at offset 0xDEAA
May 24 16:53:53 hostname kernel: [ 3.300025] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 2 at offset 0xE67C
May 24 16:53:53 hostname kernel: [ 3.300106] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 3 at offset 0xE74A
May 24 16:53:53 hostname kernel: [ 3.308117] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 4 at offset 0xEA00
May 24 16:53:53 hostname kernel: [ 3.308195] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0xEA65
May 24 16:53:53 hostname kernel: [ 3.332034] [drm] nouveau 0000:04:00.0: 0xEA65: Condition still not met after 20ms, skipping following opcodes
May 24 16:53:53 hostname kernel: [ 3.332115] [drm] nouveau 0000:04:00.0: 0xCBB4: parsing output script 0
May 24 16:53:53 hostname kernel: [ 3.332177] [drm] nouveau 0000:04:00.0: 0xC8E8: parsing output script 0
May 24 16:53:53 hostname kernel: [ 3.332246] [drm] nouveau 0000:04:00.0: 0xCBB4: parsing output script 0
May 24 16:53:53 hostname kernel: [ 3.332305] [drm] nouveau 0000:04:00.0: 0xC8E8: parsing output script 0
May 24 16:53:53 hostname kernel: [ 3.332377] [drm] nouveau 0000:04:00.0: Detected 256MiB VRAM
May 24 16:53:53 hostname kernel: [ 3.501070] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
May 24 16:53:53 hostname kernel: [ 3.501134] mtrr: type mismatch for d8000000,4000000 old: write-back new: write-combining
May 24 16:53:53 hostname kernel: [ 3.501474] [drm] nouveau 0000:04:00.0: Allocating FIFO number 1
May 24 16:53:53 hostname kernel: [ 3.507782] [drm] nouveau 0000:04:00.0: nouveau_channel_alloc: initialised FIFO 1
May 24 16:53:53 hostname kernel: [ 3.508778] [drm] nouveau 0000:04:00.0: Detected a DP output
May 24 16:53:53 hostname kernel: [ 3.508848] [drm] nouveau 0000:04:00.0: Detected a TMDS output
May 24 16:53:53 hostname kernel: [ 3.508916] [drm] nouveau 0000:04:00.0: Detected a DP output
May 24 16:53:53 hostname kernel: [ 3.508986] [drm] nouveau 0000:04:00.0: Detected a TMDS output
May 24 16:53:53 hostname kernel: [ 3.509054] [drm] nouveau 0000:04:00.0: Detected a DisplayPort connector
May 24 16:53:53 hostname kernel: [ 3.509182] [drm] nouveau 0000:04:00.0: Detected a DisplayPort connector
May 24 16:53:53 hostname kernel: [ 3.747304] [drm] nouveau 0000:04:00.0: allocated 1280x1024 fb: 0x40250000, bo f6b26200
May 24 16:53:53 hostname kernel: [ 3.747430] fb1: nouveaufb frame buffer device
May 24 16:53:53 hostname kernel: [ 3.747501] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0 on minor 1
May 24 16:53:53 hostname kernel: [ 3.753961] [drm] nouveau 0000:03:00.0: 0xC906: parsing output script 1
May 24 16:53:53 hostname kernel: [ 3.753982] [drm] nouveau 0000:03:00.0: 0xC914: parsing output script 2
May 24 16:53:53 hostname kernel: [ 3.753997] [drm] nouveau 0000:03:00.0: 0xC746: parsing clock script 0
May 24 16:53:53 hostname kernel: [ 3.755063] Console: switching to colour frame buffer device 160x64
May 24 16:53:53 hostname kernel: [ 3.755082] [drm] nouveau 0000:03:00.0: 0xBE66: parsing clock script 1
May 24 16:53:53 hostname kernel: [ 3.771263] [drm] nouveau 0000:03:00.0: 0xC906: parsing output script 1
May 24 16:53:53 hostname kernel: [ 3.771292] [drm] nouveau 0000:03:00.0: 0xC914: parsing output script 2
May 24 16:53:53 hostname kernel: [ 3.771311] [drm] nouveau 0000:03:00.0: 0xC852: parsing clock script 0
May 24 16:53:53 hostname kernel: [ 3.771622] [drm] nouveau 0000:03:00.0: 0xBE66: parsing clock script 1
.
.
.
May 24 16:53:53 hostname gdm-simple-slave[979]: WARNING: Unable to load file '/etc/gdm/custom.conf': No such file or directory
.
.
.
May 24 16:53:53 hostname gdm-binary[869]: WARNING: Unable to find users: no seat-id found
.
.
.
May 24 16:53:54 hostname gnome-session[1263]: WARNING: Could not launch application 'ultimate-edition-gdm-window-manager.desktop': Unable to start application: Failed to execute child process "xfwm4" (No such file or directory)
May 24 16:53:54 hostname gnome-session[1263]: WARNING: Could not launch application 'ultimate-edition-gdm-background-picture.desktop': Unable to start application: Failed to execute child process "feh" (No such file or directory)
t-gil
U.E. Newbie
U.E. Newbie
 
Posts: 4
Joined: Mon May 24, 2010 1:09 pm
Operating System: Ultimate Edition 3.2 32 BIT



Re: Nvidia issues post here please.

Postby Admin-Amir » Tue May 25, 2010 9:56 am

Hello t-gil .

Thank you for posting back the log for us.
well the way I see it the problem come from somewhere with the Update/Upgrade of the Nvidia Card Driver.
I need you to add the Repo of the Ubuntu X to your system.

Code: Select all
sudo gedit /etc/apt/sources.list


Code: Select all
deb http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu lucid main
deb-src http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu lucid main


Then in the terminal:
Code: Select all
ppa:ubuntu-x-swat/x-updates


Then :

Code: Select all
sudo apt-get update


Code: Select all
sudo apt-get upgrade



t-gil - The issue here is not the Card - it is the Update/Upgrade that has to write the log file After the process.
So it looks like the main problem is with the Hidden option of the Card that has to be EDITED.

You can see here that the files that you need to work are there but not on your log:

Selection_001.png
1

something that I have thinking about if you have the same issue with the BOOT to your machine is:



boot_info_script is a bash script which searches all hard drives attached to the computer for information related to booting and displays it in a convenient format. Its primary use is for troubleshooting booting problems.
How to use the boot info script

The script:

boot_info_script055.sh
script
(68.93 KiB) Downloaded 196 times


* Boot into any Linux based operating system, LiveCD or LiveUSB with an Internet connection.
* Download the Boot Info Script
* Open a terminal (Applications>Accessories>Terminal in Gnome) and type

sudo bash [path/to/the/download_folder]/boot_info_script*.sh

For example if you downloaded the file to the desktop, use

sudo bash ~/Desktop/boot_info_script*.sh

* If your operation system does not use sudo, use

su
bash ~/Desktop/boot_info_script*.sh


* You will now have the file RESULTS.txt in the same directory as the script. But if the script is inside a system directory (like /usr or /etc) RESULTS.txt will be in the home directory.
* If you already have an existing RESULTS.txt, subsequent files will be called RESULTS1.txt, RESULTS2.txt,...
* Open RESULTS.txt in your favorite text editor.
* If you came here from a Linux forum, paste the content of RESULTS.txt into your next post. Make sure to use the appropriate formating. For example in the Ubuntu forums click on the code tags (the symbol #) before pasting RESULTS.txt.


So if you can please Give it A try to get it fix for you.
And Update the Team on what happens .
Admin-Amir
 

PreviousNext

Return to Ultimate Edition 2.6 (Including 2.6.5)

Who is online

Users browsing this forum: No registered users and 2 guests