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.
The problem is that recently I have been suffering from insomnia so it's a catch-22.
I can't sleep because I'm so excited about the upcoming release of Slackware, and Pat won't release it until I fall asleep
I noticed something strange today, and i thought to mention it.
I was viewing the gallery of a friend of mine and suddenly, the screen got filled with artifacts like something corrupted the gpu's memory. As screen drawing continued things were getting worse. Here are some captures.
At this point i exited X because i couldn't make out anything on the screen. In console everything worked fine, so I rmmod/insmod the nvidia module and tried starting X again but it didn't help.
After a reboot, things worked again for very short time and then the system hang up. At first, i thought my card is dying but when using nouveau everything works fine.
It seems to me that the problem is triggered by firefox 4.0 because i tried many other programs and none hang the system. Also firefox 4.0rc1 didn't hang. The problem is only triggered by the firefox 4.0 when using the binary nvidia driver and only when viewing pictures on tabs. linuxquestions,slashdot,etc work fine but when i view my friend's gallery it crashes. I also tried a site with "educational pictures" :P and it crashes there too.
At 2 out of the 10-12 times, the screen got corrupted and the other times the system hang up with the following messages
Code:
NVRM: Xid (0000:01:00): 6, PE0001
NVRM: Xid (0000:01:00): 8, Channel 00000001
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
I searched google and found out that many people have the same problem. Firefox 4.0 has "hardware acceleration" and because of troubles only some drivers like the binary nvidia are whitelisted. I use the latest 270.30 driver (on 64bit if it matters) so maybe it is a combination of nvidia + firefox + something else (cairo perhaps ?) that triggers it.
If someone experiences the same problem, the "fix" is just to disable the hardware acceleration for now. Edit -> Preferences -> Advanced -> "Use hardware acceleration when available".
Distribution: Slackware 14 (Server),OpenSuse 13.2 (Laptop & Desktop),, OpenSuse 13.2 on the wifes lappy
Posts: 781
Rep:
Another strange problem after Tuesdays update, which might also be some sort of security issue. Upshot is that I can no longer carry out internet banking using FF4, Konqueror or Seamonkey, and the problem seems to be around javascripts which my bank use to allow access to account details (I think, but am probably wrong).
In effect, on the account summary page, my accounts are listed with a preceeding arrows, which you click on to get a drop down detail of individual transactions. But since the update, clicking on the arrow now does nothing, and in the status bar you get a javascript (void)0 message.
Just wondering if any else here might have experienced the same issue?
Perhaps.
I know from past experience that Mr. Volkerding does not follow any particular schedule when it comes to releasing Slackware-stable. PV will release 13.37 when it is ready.
I am happy to wait.
It's hard to arrive "there" when "there" keeps moving -- 2.6.37.5 just snuck out. (And 2.6.38.1, which is a very similar patchset. At first glance, they don't look highly compelling.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.