On installing the Nvidia driver using Nvidia's 173 legacy installer I noticed a load of errors which are recorded in the log below. The driver appears to be working. Is this something that I should be concerned about?Quote:
ERROR: Unable to open '/usr/X11R6/lib64/xorg/modules/extensions/libglx.so' for
reading (No such file or directory)
ERROR: Unable to open
[code]....
I want to use my video card, but after upgrade i got this message:
You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server.
will be apreciaTED, after running from terminal I got this
CODE:
rey@rey-desktop:~$ sudo nvidia-xconfig
[sudo] password for rey:
Using X configuration file: "/etc/X11/xorg.conf".
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error. VFS: Cannot open root device "302" or unknown-block (3,2) append a correct "root=" boot option;here are the available partitions;
0800 78150744 sda driver:sd
0801 47428608 sda1 <-- this is my Windows partition
0802 30719552 sda2 <-- this is my Linux partition
0b00 1048575 sr0 driver:sr
0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2) I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp
#mount /dev/device /slacktemp
#chroot /slacktemp
#cd /slacktemp/etc <-- for me it told me that doesn't exist
#vi lilo.conf <-- couldn't do nothing and was frozen
#lilo -v -t -b /dev/device
#lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
I'm using Debian Wheezy on amd64 using the binary nVidia drivers from the Debian repository. When I started up my computer yesterday, everything worked fine. Then I started installing a bunch of updates going back a week since I had it turned off for a week. This seems to have messed with my nVidia drivers. I could run GNOME at 1080p just fine, but I couldn't run prboom-plus or glxgears since they would give me errors about not being able to find a screen. Strangely enough, Wine could run both Proun and Bulletstorm without a problem.
I looked at synaptic and tried to install nvidia-glx to solve my driver problems, but it gave me an error about not having the correct version of libgl1-nvidia-glx. I try installing that and it wants to remove 140 programs first! Of course I refuse to let it do so. Then I figure it might have to do with some other program that these programs are dependent on. So I check the package dependencies and lo and behold, they all require libgl1-mesa-glx. I try removing that and synaptic also says that I have to remove those 140 programs with it. I give up and try playing the Half-Life 2 demo via Wine. When it hangs I restart my computer. However, while rebooting, I got this nice error message from X that said that apparently I don't have any nVidia drivers anymore.
I would prefer not to use sgfxi to do driver updates. One of the reasons I switched to the repository's drivers is because I was tired of having to reinstall my drivers every time there was a kernel update in testing.
Tried using vesa in xorg.conf, it also didn't work. Detailed X output said something about being able to find a screen but it wasn't usable.
I have been running F11 for some time now. I install updates regularly and to this time have had no issues. Now it comes up with error.
Code:
[root@red 2305 ~]
$ yum update
Loaded plugins: protectbase, refresh-packagekit
0 packages excluded due to repository protections
Setting up Update Process
Resolving Dependencies
--> Running transaction check .....
--> xorg-x11-drv-nvidia conflicts with xorg-x11-drv-catalyst
Error: xorg-x11-drv-nvidia conflicts with xorg-x11-drv-catalyst
Error: xorg-x11-drv-catalyst conflicts with xorg-x11-drv-nvidia
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
[root@red 2306 ~]
I do not believe that I even have the 'xorg-x11-drv-catalyst' mentioned here installed:
Code:
[root@red 2315 ~]
$ yum list all | grep installed | grep catalyst
[root@red 2316 ~]
This returns nothing so why the error?
Sometimes, in Firefox, after looking a video and closing the corresponding tab, a still picture of the video appears in other tabs, even in some other applications than Firefox (e.g. Terminal). I've installed the nvidia drivers on Fedora 14. They seem to work properly.
View 1 Replies View RelatedI installed slackware 13.1 x86_64 bit with multilib, and its been about a month already, I'm really enjoying slackware but I am being troubled with my nvidia card, and I need to get my 3D acceleration working. And I've been looking around the net for information and kept on trying to make my nvidia card to work but to no avail. I cant get X to start, once I put in a xorg.conf stating to use the nvidia card. After troubleshooting for almost 2 weeks and now at my wits end, I now come humbly looking for help in linuxquestions slackware community forum.I've installed nvidia 64 bit kernel, drivers from slackbuilds (version 256.44). The laptop model I'm trying to get it working is an -ASUS K52J Intel Core i3 2.40Ghz with 2GB RAM and with an Nvidia Geforce 310M with 1GB dedicated VRAM.
View 14 Replies View RelatedI started a thread asking for advice in the hardware forum. I didn't want to post a duplicate thread, but I was unable to get it moved here, so I'm kindly asking you slackers to help me install the aforementioned driver.
View 1 Replies View RelatedI have a Dell Vostro 3300, i5 460 processor with a NVIDIA 310M Graphics Card. I'm doing a KUBUNTU 10.10 (Maverick) install with the following results. The Live CD boots just fine to, "TEST," or "Install." Installation goes fine. However, the graphics card being used is the Intel i915. I have tried installing the NVIDIA drivers directly from the, "Additional Drivers," tool and after the reboot I get through the boot screen to the console. I try to manually startx and I get the errors, "no device found," "no screens found." The second install I tried purging and blacklisting the nouveau drivers and entering safe mode. Then using apt-get install nvidia-current. After that, nvidia-xconfig. Same results.
The third attempt I re-installed and this time downloaded the drivers from the Nvidia site (version 256.53). Blacklisted nouveau, remove all nvidia, updated initramfs, etc. The install went fine however I still end up at a console after boot with the same messages as above. No device found, no screens found. I've tried searching through the forum and web and have tried things like adding the modset option along with many other hacks, tips and fixes. still, no go.I can live with the Intel graphics for now although I lose 512MB of memory. Unfortunately there is no way to disable or change this set-up in the BIOS. I've seen quite a few bug reports at Launchpad:
1. Is this something I should just wait til a fix comes? Will a fix come?
2. Is there, or will there be an official Updated Ubuntu Guide for Maverick to install NVIDIA drivers with this tecnology?
3. Lastly, is there anything else I should try??
As Pat stated in the Changelog, Slackware-13.1 don't ship the nouveau X driver (yet).But it's not hard to get it either.
1. Upgrade your kernel to 2.6.34
2. Get and install the driver:
Code:
git clone git://anongit.freedesktop.org/git/nouveau/xf86-video-nouveau/
cd xf86-video-nouveau
./autogen.sh
make
[code]....
PS. There is no source tarball yet for this driver.If you want to upgrade:
Code:
cd xf86-video-nouveau
git fetch
git rebase origin
[code]....
in preparation for the update to Slackware64 13.1 I did a complete backup of my system with dd.
I used the Slackware 13.0 (not 64 bit) DVD to boot and executed the command:
# dd if=/dev/sda of=/dev/sdb
The command finished without any errors as expected. First I tried to boot the destination hard disk to check if the backup was successful and I can start with updating the source disk to 13.1. But at boot time I got the message that the last file system check is 197 day ago, the file system check started automatically and found errors which it could not correct. At this point I thought it was maybe a copy or a hard disk error and tried to boot the source disk. But the behaviour was exactly the same on the source disk. With the source disk I followed then the recommendation, logged in with root password and executed the recommended command which was something like e2fsck -v -h /dev/sda1. Then the system did a file system check and scrolled a lot of numbers over the screen. After a while it reported that it's ready and the system needs a restart.
I switched off and on again. Then the system bootet as usual, and seems to run okay at the moment. But now I'm unsure if really everything is okay.
What I'm confused of is, why the system reported that the last file system check was 197 days ago and why this was just after the dd backup. Shouldn't the automatic file system check at boot time run more often as every 197 days or mounts? I didn't change any default settings (as far as I know). The file system of the root partition is ext4 and my computer normally is switched on and off once every day.
My question now is, if this behaviour can have something to do with the dd backup.
Is my system after the file system check okay again, or should I expect further problems?
The system is 13.1. Updated using slackpkg. All other software, with the exception of closed source Vbox, is installed via SB.orgDid a slackpkg update this morning for firefox 3.5.8 and there was also a glib upgrade (likely culprit). Now it seems that most of my software does not work. Did I do the upgrade wrong?
Code:
frank@hdwise:~$ firefox
/usr/lib/firefox-3.6.8/firefox-bin: symbol lookup error: /usr/lib/libgnome-2.so.0: undefined symbol:
[code]....
I recently upgraded my VLC and Avidemux from AlienBOB's Repo.
With VLC media player 1.1.0-rc2, i get the following error when i try to play a video:
Code:
Warning: call to rand()
Warning: call to rand()
Warning: call to rand()
Warning: call to rand()
Warning: call to rand()
[Code]....
I have installed slack 13 and I want to configure the sistem to send automaticaly an email to an gmail account when I have some errors like power down for some minutes or a program crash. Can some one tell me exactly what i must do ?
View 5 Replies View Relatedi upgraded my netbook to slack-current (32bit) and now When booting up dmesg shows these errors:
Code:
[ 10.770199] [drm] detected 63M stolen memory, trimming to 32M
[ 10.770267] i915 0000:00:02.0: irq 43 for MSI/MSI-X
[ 10.770280] [drm] set up 32M of stolen space
[ 10.770468] [drm:init_ring_common] *ERROR* render ring head not reset to zero ctl 00000000 head 02001000 tail 00000000 start 02001000
[Code]....
This happened with generic stock kernel and is also happening with 2.6.36.2 zen kernel. Is it something serious? Kde compositing still works, except it locked up few times when i was testing how windows wobble in kde, but not recently.
So I don't like the new Amarok as much as the 1.4 version, so I want to install the older release. I download the source files, extract it and go into the directory. I type ./configure and recieve an error about kde-config not being installed, but "ln kde4-config kde-config" (or something like that) solved that problem. But now I encounter this problem after ./configure:
Code:
I already have a version of Qt installed (it's necessary for KDE, is it not?), but it's not between 3.3 and 4.0. I've read online about how if you install both the 3.3 and the version included on Slackware 13.1 of Qt there would be problems. I also read that you could find the necessary Qt files in the sources discs, but I'm not sure what files to install:
Code:
This is Slackware 13.1, by the way.
Do I have to shamefully resign my pride to Amarok 2.3 or can I install 1.4 in some way? And if you've gotten this far, thanks for reading and potentially responding.
I'm trying to install virtualbox on slackware 13 and I'm running into header issues I think...it says it can't find libcap..any ideas? I downloaded libcap from slackbuild and tried to run make but I get errors (the second code block)
Code:
VirtualBox-2.1.4_OSE/kBuild/bin/solaris.sparc32/kmk_echo
VirtualBox-2.1.4_OSE/kBuild/bin/solaris.sparc32/kmk_cp
VirtualBox-2.1.4_OSE/kBuild/bin/solaris.sparc32/kmk_install
VirtualBox-2.1.4_OSE/kBuild/env.sh
patching file VBox.sh
Checking for environment: Determined build machine: linux.x86, target machine: linux.x86, OK.
code....
I've been trying to compile and install different terminal emulators:Eterm, aterm, and libAfterImage for urxvt.
I've been getting all these errors, and it seems odd to me. I did some fiddling awhile back enabling KMS with my radeon, install custom packages for xf86-ati, mesa, and libdrm. Could that or some other fiddling have broken these dependencies?
Here is an excerpt, with the full error log attached and here:url
Code:
In file included from libungif/../xwrap.h:5,
from libungif/../asim_afterbase.h:23,
from libungif/../afterbase.h:36,
from libungif/gif_hash.h:24,
from libungif/gif_lib_private.h:5,
code....
An error accoured during the root filesystem check.
Installed fresh Slack 13.0 version, at 7GB virtual hdd, with cfdisk, created two primary partitions, 500 mb for swap, whats left, to second partition, made it bootable, installed full software package, used all default selections, only refused to configure network. At first restart, I got a screen with many statements, that looks like errors, and a last one, that looks like critical error.
An image I have been working on Windows my whole life and only worked with already installed linux systems a bit. Installed RedHat and FreeBSD on VirtualPC previously and succesfully. Now, I stumble upon this error and cant think of next step.
on a fresh install of slackware -current x64, the first thing that i did was download and install opera. now, whenever i start kde, and run opera, X crashes with lots of crazy errors, usually in the format of:
/usr/bin/akonadi*whatever* cannot connect to x server :0
/usr/bin/akonadi*whatever* has crashed too many times and will not be restarted.
and then i get spat back out at the CLI. opera works fine in the other Desktop Environments, and i'm posting from xfce right now, so i know its an issue with akonadi. i would like to use KDE as my default desktop, but i dont want to use it without all of its features
I've been trying to build mjpegtools 1.9.0 on multilib current and it fails everytime with: PHP Code:
[Code]....
I've searched for maybe a newer version than 1.9.0 and it doesn't seem to exist. I'm not sure what direction to go with this.
I'm doing a bit of housekeeping and tidying up of programs I no longer need/use, and as some of these were installed using sbopkg I thought I would also tidy those. However when attempting to view obsolete sources via the utilities sub-menu, sbopkg seems to crash to a cli interface from the ncurses one and spews continuously the error below. This thern continues until I CTRL+C the process which of course then leaves the sbopkg pid file still showing active in /var/run. Anyone else come across this, and a possible way to prevent it.
/usr/sbin/sbopkg: cannot make pipe for command substitution: Too many open files
stty: standard input: Bad file descriptor
/usr/sbin/sbopkg: line 569: read: read error: 0: Bad file descriptor
stty: standard input: Bad file descriptor
/usr/sbin/sbopkg: redirection error: cannot duplicate fd: Too many open files
Using online Debian guide, installed latest nvidia-current, glx etc which seems to be 195.xx Machine boots to GUI but monitor setting menu doesnt respond nor is there an nvidia specific one. xorg.conf shows 'nvidia' driver but I suspect I am still on 'nouveau' since the synapatic package manager doesn't show an nvidia xserver-xorg-video choice.
Second question, any trailheads for using wheezy based drivers (i.e. nvidia's latest 270.xx) with squeeze?
I can't figure out how to install the nvidia drivers for my nvidia 8800 GT video card. I've followed some other posts and all the posts seemed either incomplete, or led me down a path of which eventually broke my installation, that I needed to reinstall the entire ubuntu system.Again, it may not have been broken, i just didnt know how to get back in to the gui version of ubuntu, the instructions took me to the console terminal
1.) I've installed the ubuntu 10.10 64bit for i386 in an oracle virtualBox..
2.) downloaded from nvidia.com "NVIDIA-Linux-x86_64-260.19.44.run"
3.) Stuck don't know what to do.
i am having a problem with my just recently upgraded ubuntu 10.10 ive search google and forums for well over 4 hours with no luck so im asking here. Now i know nvidia 96 has problems with xorg 1.9 but i installed the updated nvidia 96 driver that supports xorg 1.9 through maverick-proposed and i dont have nvidia control panel under system->preferences and if i types sudo nvidia-settings in terminal i get it says im not running an nvidia driver but the hardware driver reports it as activated but not in use and nvidia settings also tells me to run nvidia-xconfig but it says this when i do sudo: nvidia-xconfig: command not found
View 6 Replies View RelatedI'm trying to run kmail on Slackware -Current. Kmail starts then akonadi server runs checks.
Then follow many errors:
I've reinstalled MySQL and it seems to be working but there is this error repeatedly:
I've done some Google searches but I'm not able to find a solution to get akonadi to work.
[url]
I upgraded from 13.0 to 13.1 and now I have strange behaviors with the printer. It is an Epson Stylus Photo RX640. It was working well with the vanilla Gutenprint 5.2.2 that came in Slack 13.0. The printer is shared and used from other slackware boxes and a mac. Upgrade to 13.1 (gutenprint gets to be 5.2.4) ...
Now when I print from the machine that has the printer attached I get full black pages, and cups shows errors. The Mac is still able to print well (probably because it is using its own PPD and passing through directly to the printer). I then removed gutenprint, and then removed the 5.2.2 PPDs (that were still in the system). Reinstalled gutenprint from the Slackware 13.1 distro. And the problem persists.
[Code]....
My problem is to get postfix working with a smarthost, to send mails from home with dynamic IP, and which needs authentication. I did exactly the same with Slackware 12.2 (postfix 2.6.2) and it worked. Now I tried to do with 2.6.2 (actual running version is 2.7.0 with the same problem) on Slackware 13 64bit. Following error message occurs around every minute in the maillog:
[code]...
I'm getting (1)various errors spat out on STDOUT while running X and (2)a hard fault in Openoffice.
(1)
> Warning: Duplicate shape name ""
> Using last definition
[code]....
with slackware 13.0 for one user xfce4 hangs and doesn't start..xsession.errors claim it can't open display. It works fine for other users. Also if I access the machine in question as the same user but remotely using remote X (X-terminal on my LAN) it works fine.Sometimes if I wait and count to 30 it comes up but a lot of the features don't work.During the last week have posted this question on the compuserve linux forum and also in the xfce site forum with no solutions.seems there must be something in that user's directory which is hanging it up. I keep the same /home/users directory on a separate partition so when I upgrade for new versions of slackware the /home/users remain the same - I symlink home to that partition so upgrades are somewhat seemless.
View 3 Replies View Related