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.
Ok, I'm new here, and I just got a Slackware 10.0 box updated with Swaret, but during the update, some things messed up (including x11, which I had to un-install and manually install again... then ran xorgconfig)... now that it's running again, I am experiencing some odd issues...
I attached a screenshot of what I see. The thing is, for example, if I scroll on a webpage, it still dislpays the same thing on the screen, like if it didn't refresh that area of the screen, I hit Ctrl + A and all updates. For example, in this box for writing a message there are no issues as I am typing, but if I was reading a thread, I'd had to do the Ctrl + A thing...
This is basically a stock install with the only new thing that it has a 2.6.10 kernel that I compiled (which ran perfectly before I updated the packages with swaret).
For one.... maybe you should just set the version in swaret.conf to just 10.0, not current.
That said... I would do a reinstall of your X and X related libs. .. and if that does not work... nuke it all with a fresh install, still using swaret but just update to the latest 10 release not current.
I've gotten similar looking things while testing anather distro.
Although mine was more blurred (traces) when I scrolled down,
rather then the missing parts of windows like yours. But refeshing
the window fixed it - until I did something else.
I resolved it by changing video cards (it was a test box so I really wasn't
concerned about it). So you might want to try to run through xorgconfig again.
OR check on video drivers - something along that line.
I'm gonna try re-installing most the packages in the /var/swaret/repos/ subdirectories which were the ones downloaded... I don't know if it's me, but the x11 was hosed thanks to not finding the 'default fixed font' so I un-installed it and re-installed it myself from the same packages, and it worked.
I wouldn't like doing another re-install of the OS (this one is the 21st try this week) and then trying to update again to get the same results, I am very carefull with .new files and always research what dependencies a package might need.
Now, the 'change the card' suggestion... I don't have a PCI card, the mobo does not have a AGP port, and the video adapter that it uses is the i810e. It is a somewhat old motherboard with a PIII 866Mhz and 192MB of RAM.
And to think I was happy with the stock Slackware 9.1 install and I just wanted to get my WMP11 v4 to work with Linux...
Any other recomendations are welcome before I try to do the un/re-install of the packages?
Distribution: slamd64 2.6.12 Slackware 2.4.32 Windows XP x64 pro
Posts: 383
Rep:
If you read the change logs you would know that after the update of x11 you have to run xorgconfig, due to a change in drivers. Alsa don't work because you prolly didn't update the kernel. Use your cd and reinstall alsa-*-1.0.5-i486.tgz also koffice don't get updated by swaret by default so update that too. I am running slackware-current with the 2.6.9 kernel with no problems
If you read the change logs you would know that after the update of x11 you have to run xorgconfig, due to a change in drivers.
Quote:
[...] some things messed up (including x11, which I had to un-install and manually install again... then ran xorgconfig)... [...]
Quote:
Alsa don't work because you prolly didn't update the kernel. Use your cd and reinstall alsa-*-1.0.5-i486.tgz also koffice don't get updated by swaret by default so update that too. I am running slackware-current with the 2.6.9 kernel with no problems
ALSA works fine here. Infact, I am listening to a mp3 right now.
Originally posted by tormented_one awesome, I always have probs with alsa. Sorry I sounded rude. It was late and I was grouchy. And now that I read it I came across bad sorry
I thought you just had a bad day... nothing personal.
I am still awaiting to get some stuff done (I think I may be getting a bigger drive, a new board and a faster processor... or perhaps a new computer to toy with ) and I'll try a fresh install and a MANUAL upgrade of all the packages. Might take some time, but I will know if anything goes wrong.
Thanks for the tips, though I really think it was a upgrade issue (if xorg died and I had to re-install it so it work, the obviously upgrade was hosed).
alsa note,
check your /etc/modprobe.conf
etc
for I've seen alsaconf
place multiple sections in there if you are using non standard IRQs or legacy sound cards.
I re-installed the OS and upgraded all packages manually and the issue is not present.
Now I am re-downloading the 2.6.10 kernel and gonna do my magic once more.
I will check out the alsa configurations IF I get the other machine for me, since I will not be using the onboard audio, I would be using a SoundBlaster Audigy Gamer on it.
Distribution: slamd64 2.6.12 Slackware 2.4.32 Windows XP x64 pro
Posts: 383
Rep:
you could use both sound devices if you want. Just a thought. I know with windows this is impossible. But good ole linux lets us use two or more sound cards as long as they do not use the same driver. I had an audiodrive 1869 isa and a pci soundblaster card working at the same time.
Distribution: slamd64 2.6.12 Slackware 2.4.32 Windows XP x64 pro
Posts: 383
Rep:
i used one for my pc speakers and one for my rack sterio. I could then use my wireless connect on my laptop to control the song....etc. I just connect and play the mp3's I could mute one or the other Just me tinkering around. Also beats buying a $300 wireless digital media centre.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.