SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I went ahead and installed the Nvidia 304.88 driver for my 6150SE and everything worked perfectly thanks to SlackBuilds (and a special shout out to Edward Koenig). I didn't even have to add/edit any config files afterwards since everything just worked. As Woodsman outlined above I used the kernel and driver build scripts from 13.37 and simply changed the version number. The only minor hassle was locating the 304.88 source files for nvidia-installer, nvidia-settings and nvidia-xconfig but some noodling around on the Nvidia website found all of those.
The only minor hassle was locating the 304.88 source files for nvidia-installer, nvidia-settings and nvidia-xconfig but some noodling around on the Nvidia website found all of those.
Can I assume that this is normal slackpkg behavior after blacklisting nouveau and that I can just ignore it?
Quote:
bash-4.2# slackpkg upgrade-all
Checking local integrity... DONE
You have a broken /var/log/packages - with two versions of the same package.
The list of packages duplicated in your machine are shown below, but don't
worry about this list - when you select your action, slackpkg will show a
better list:
just installed nvidia 304.88 from nvidia's webiste now web browser crashes.
I have the 6150se graphics card on my tower and just installed the 304.88 graphics driver from nvidia's website. It seemed to go well, however now I can not open a web browser. As soon as I open firefox or seamonkey they immediately crash. Any ideas as to what is causing this?
Update: I upgraded to current with the 3.9.5 kernel and when I rebooted and tried to open firefox my system froze. I rebooted again and then firefox seemed to work. I wonder if it's going to freeze up occasionally?
Last edited by Bertman123; 06-22-2013 at 05:04 PM.
Woodsman you should probably submit a SlackBuild package to SlackBuilds.org to add another Legacy tier for Nvidia chipsets. A lot of laptops and workstations still use the 6x00/7x00 series graphics processors.
Nice to hear. After today's current change log announcement, and this thread, I wondered how well 304.88 would survive. I haven't done any testing in current in a long while but expect to do so soon. I have no desire to buy a new motherboard. Nonetheless, I always hold my breath a wee bit when current gets closer to release because I don't know what third party packages will break.
I tends to install the latest kernel and find an appropriate patch for NVidia and VMWare and post it on my blog just in case someone else might need it...
GIad it help when Pat decided to take 3.10.5 into Current
2. When Slackware 14.1 is released officially, the slackbuilds.org 304.88 maintainer incorporates the ArchLinux patch into the build script.
In the short term, adventurous 3.10.x users need to slip the ArchLinux patch into the slackbuilds.org build script?
Does this make sense?
Since 304.88 is considered legacy, they will only receive security fixes and for new kernel support, i don't really hoped too much for this, but still it's possible if they wanted.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.