Ted Dog wrote:how to duplicate problem I wrote about, check email, and surf this forum, without rebooting for little over a day and a half, downloaded a file from this forum, and reply to a few posts.
The 'event' happen on this thread, during typing in a textbox..
Ted Dog, which browser (FF/SM)? Are you using Adblock? If not, please use it and see if it makes any difference?
Opps that post was deleted (not by me) it was very wonky (typos galore) since the textbox was being blotted with white bars, and text chunks shifting in/out of view, the very bad time, posted the one above after that one did not have as many corruptions. Got a screen shot, but based on your reply it was not going to be anything you have not described. The white out block JUST occurred AS I was spell checking the word described, in the last sentance, Happened again when I misspelled sentence. Cool it is looking like an issue with spell checker..
If you are a good speeller if my never happen, I guess
I've got this time to time but usually not that bad. I think it is graphics driver related.
L18L wrote:Yes the culprit is definitely the gma500_gfx module only.
in the running system makes it all black...
Anyway.. resolution is 1600x1200px (should be 1920x1080)
So I am hoping another kernel will help.
Since you are using UEFI, I would presume that you card is relatively new and therefore not supported properly by the kernel, thus the problems. GMA500 and GMA600 are not Intel designs despite the name, they are closer to Imagination POWERSGX (which is as closed as a GPU you can get), even those in the ARM world are complaining.
I suggest that with pfix=nox and/or nomodeset xorgwizard (and modprobe <video>) should not start. At the moment it looks like just xwin is not started.
"pfix=nox" stops xwin from being run; "nomodeset" stops the KMS drivers from being activated; they are meant for different things. If your card isn't supported by the kernel and you've got lockups like Gobbi, then "pfix=nox" will not help, "nomodeset" may still help. Even with "nomodeset" you may still get a desktop successfully (using "vesa" driver for BIOS systems and "fbdev" driver for UEFI), if it doesn't happen automatically, you can use xorgwizard to tell Xorg to use the correct driver.
I have copied some locales from
/usr/share/locales/i18n/locales
Or you can use the glibc_locales from the package repo.
Localisation is a big thing for Fatdog64, *nothing* is localised yet. Localisation of Fatdog64 scripts consist of two parts:
a) localisation of the GTK gui (this requires addition of 6 lines of gtk-server commands).
b) localisation of the scripts itself (this is similar to Puppy)
Gobbi wrote:I did two things:
1 . Booted with pfix=nox loglevel=7 then modprobe radeon then xwin . This gave a lot of vertical narrow black and white stripes on my screen and the system frozen .
2 . As you suggested I removed the radeon-dmf.conf file before starting X adding loglevel=7 . Did modeprobe radeon and the last lines on the black screen were :
I assume you mean that when you remove radeon-dpm.conf, it works. So your card isn't compatible with DPM. Well DPM support is new, so yes we expect problems, and hopefully it will get better with time.
I tested the glib-2.36-630.pet and it solved that glitch , but if it can make more damage on other occasions I can live with the old one since I only make those settings in the beginning and restarting X put back the normal screen.
Not saying that it will cause problems, I'm just saying that glib is used by so many other apps, it may have unexpected kinks unless it gets tested for all of those apps - and we haven't done so. If it works with you, you can keep it installed and use it to see if any other apps suddenly becomes broken. You can always uninstall it. If it works well we may move it to the main repo.
BTW on that broken folder in ibiblio I saw Seamonkey 2.20 witch I use it with no problem on fatdog 620 .Did it also give problems ? I'd like to know more...
Why use SM 2.20 when SM 2.21 is available on the official repo
![Smile :)](./images/smilies/icon_smile.gif)
(And yes, this SM 2.21 should work on earlier Fatdogs too).
Installed the pet which contains the transset-df command line tool , did a visit to the owner's site and saw how to use it but , it seems fatdog's WM openbox has no such thing as transparency , or it needs other themes , I don't know .
You need to start "xcompmgr" first before you can use transset-df. Here:
https://wiki.archlinux.org/index.php/xcompmgr
Atle wrote:But if you look in the right lower corner, you see that there is 1,4 gb free savefile space. To me this looks more like permissions, but i am open for having made a mistake.
yes, this could be permission problem. Open /root/spot/Downloads - do you see the partial file that you've been trying to download? How do you install it - to flash drive? When you create the savefile, did you move agree to "move the Downloads folder" out of the savefile? What's the filesystem where the Downloads folder is located? Do this (in terminal):
Do you get an error message? If you do then yes it is a permission problem.
LateAdopter wrote: ran xorgwizard and the dialog box opened with the highlight on ATI so I clicked on Radeon and then clicked OK. This is what I got in the terminal.
Thanks, I've identified the culprit. Fix is on the way.
cheers!