On 2011/07/19 13:22 (GMT+0300) Stan Goodman composed:
Sorry, I thought I was clear; apparently I was not. As I said, I had entered the URL with the browser (Firefox), and tried to<Save as> to the target directory, and received the error message.
Absent running FF as root, that would be expected behavior.
I did see that the directory's privileges required root for writing, but wanted to be certain that this was the only reason for the refusal, because of what seemed an unclear wording of the error message, so I asked, in the interest of clarity -- "better to be safe than sorry". My solution last
Without knowing you were trying to save with FF, it wasn't possible to be certain why you got the message you got.
night (wee hours), which seemed simple enough, was to save the file instead to the Desktop, and then, as root, to move it in a terminal to the target directory.
Saving somewhere other than the ultimate destination, then moving or copying it is usually prudent. That procedure provides some insurance against against overwriting a file for which you have no ready or any backup, and might dearly wish you had.
As I understand from a previous message from you, the presence of this new file makes it possible for YaST to see newer versions of Xorg; searching in YaST for "graphics", or "xorg", or "intel", I do not notice
Without adding that repo, YaST Software immediately after an installation was completed but before any updates were applied would show: xorg-x11-driver-video-7.6-52.4.x86_64.rpm currently installed, which from http://download.opensuse.org/distribution/11.4/repo/oss/suse/x86_64/ you can see was built in February. It would also show xorg-x11-driver-video-7.6-53.56.1.x86_64.rpm as the newer available version you probably have now which http://download.opensuse.org/update/11.4/rpm/x86_64/ shows was built in April. Compare those to the obviously very much newer xorg-x11-driver-video-7.6-229.1.x86_64.rpm from http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_11.4/x86_64/ that you'd get now by adding the new repo and updating, and you should see a pretty substantial likelihood that time's been ample to incorporate Sandy Bridge support, even if it hadn't been mentioned elsewhere in the thread that that is indeed the case.
anything that looks like a newer Xorg, so it's possible I have omitted a step. I won't progress to the matter of the kernel until I'm sure that the Xorg matter is resolved.
No thread participant has proffered any reason not to use a newer kernel whether or not the newer drivers solve your problem independently.
Meanwhile, I've got the page http://en.opensuse.org/SDB:Configuring_graphics_cards#Symptom on the browser, and will read it now. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org