View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 21 posts ] 
Go to page Previous  1, 2

Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Fri Feb 06, 2015 7:58 am 
Offline
Joined: Sat Jun 24, 2006 6:02 pm
Posts: 7
Hiya

Still going fine after four days. Thanks for the updates.

Myth is up and running well.

I have an little atom board with onboard Nvidia ion graphics. I just did a pacman -S nvidia-304 and the screen popped up, and stayed over reboot. from what I could see into logs I think there was a problem with the drivers updating on the old kernel, and breaking. Worked fine when reinstalled on the newer kernel.

(PS enjoying having HDMI sound back with the updated nvidia drivers, as nvidia had broken it on ion for a year!).

cheers

Paul


Top
 Profile  
 
PostPosted: Fri Feb 06, 2015 8:31 am 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 992
Location: SC
Do you mind running
Code:
sudo xconfig.sh
and see what driver it chose?


Top
 Profile  
 
PostPosted: Sun Feb 08, 2015 4:36 pm 
Offline
Joined: Sat Jun 24, 2006 6:02 pm
Posts: 7
hiya

Sorry I couldn't connect for a bit/

output of xconfig.sh

Detected NVIDIA as the video card type
Checking for nvidia-340xx in cache or online
Checking for nvidia-340xx-libgl in cache or online
Checking for nvidia-340xx-utils in cache or online
Checking for opencl-nvidia-340xx in cache or online

and then

Installing nvidia-340xx driver

cheers

Paul


Top
 Profile  
 
PostPosted: Sun Feb 08, 2015 5:31 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 992
Location: SC
Thanks. So I am guessing it worked after a reboot and the 340 driver is the correct one for your card?


Top
 Profile  
 
PostPosted: Mon Feb 09, 2015 4:50 am 
Offline
Joined: Sat Jun 24, 2006 6:02 pm
Posts: 7
It seems the 340 is the right driver.

However when it wasn't working, it continued to not work over several reboots.

once reinstalled and reboot it was fine.

The only error in the logs was about a version mismatch between kernel and nvidia drivers, and this was from the update process.

Does the kernel need to be updated before the latest nvidia drivers are installed? the old kernel was still running when the new drivers tried (and failed?) to install. After reboot, have new kernel and then I could install drivers to match.

cheers

Paul


Top
 Profile  
 
PostPosted: Mon Feb 09, 2015 9:01 am 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 992
Location: SC
pconnor wrote:
Does the kernel need to be updated before the latest nvidia drivers are installed? the old kernel was still running when the new drivers tried (and failed?) to install. After reboot, have new kernel and then I could install drivers to match.
Yes the nvidia drivers do require the new kernel but pacman should have taken care of that and installed in the correct order with pacman -Syu. One issue with this upgrade is the that the nvidia drivers split some cards to the legacy 340 driver. To account for that on an upgrade the nvidia driver places a cron job to run xconfig.sh after pacman is complete. It is possible that if you rebooted immediately after pacman was done installing xconfig.sh didn't get a chance to run.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 21 posts ] 
Go to page Previous  1, 2



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu