Hello, i have a problem with my M$ Wireless Mouse (it's a part of the Microsoft Wireless Optical Desktop 1000, which includes also a keyboard, that's working fine) The problem that i get is that i moves great BUT the left click seems to be "pressed" all the time. If i move it while i am on X (KDE) it shows the menu about cascading windows or something and if leave my pointer on an icon it'll click it without actually clicking on it
My question is that does anyone has fixed this problem?
How do you enable this USB_HID module (should i edit the xorg.conf)?
On the setup i configured my mouse as USB mouse..then i tried everything without any result (changing to /dev/input/mice etc.)
Thanx for any help in advance! This forum rocks!

Hi

does anyone have any up-to-date information on ATI graphics cards? because this site -> ati.com/products/catalyst/linux.html seems to contradict what is on at the moment. If anyone has any information on why this might not work it would be appreciated.

Mark

Great guide, first time now i've ever had a printer configured in linux, and i've used it on and off for the last 9ish years lol.

Cheers Shilo.

Regards

Derek

I'm with you on this. I seem to be missing something. Also, ATI said there's not fglrxconfig any longer. I don't have ATI X Config, but I do have aticonfig. aticonfig seems to be used to configure the xorg.conf file. Another thing, it's not clear on how to look at the kernel to make sure the things mentioned are there or not.

One last thing, should we be using the 30MB ATI installer I saw on the site?

Just what I suspected, the X1000 series of ATI Radeon cards are not yet supported by ATI Linux drivers.

First clue: I looked through the Xorg log in /var/log and didn't see my card's chipset in there.

Second clue: I did a search on Google Linux and my suspicions were confirmed

http://www.google.com/linux?hl=en&lr...00&btnG=Search

No wonder it will not load X for me! LOL

Oh, I just recently bought an Visiontek ATI X1300 256MB video card.

Can I use SWareT without installing Dropline? I installed it already on my system, but it won't update from the Linux Packages.net ftp. I am using slack 10.2, should I change the address from ftp.linuxpackages.net/pub/slackware-9.1 to 10.2? Also you said to use ftp4. I'm a bit lost

EDIT: Well I skipped -update and tried just --upgrade -a and it is updating my packages now from a Dutch ftp site not listed in the config file.

EDIT: Heh, a quick look on LinuxPackages.net found a nice mirror list. Problem solvered methinks

hsimah-

My advice is to forget about LinuxPackages.net as a repo. SWareT doesn't consider where the packages that you have installed came from. Packages from Slackware definately work. There is a large user base utilizing those packages. By including LinuxPackages.net as a repo, you will replace packages that are known to work with packages that MAY work (they will have a much smaller user base to test). You may also introduce additional dependencies.

This differs from the advice I give in this post and on my website, but until SWareT has a feature to replace packages only from similar repos (i.e. Official Slackware package w/ Official SLackware packge, LP package with LP package) it is much better to leave LP out as a repo.

This advice is especially true if you are using SWareT with the "-a" flag.

It is also important to understand the use of "swaret --dep". This will tell you about unresolved deps.

Ah ok, thanks very much. I am having a little trouble with swaret again now. I have a list of libraries needed after running --dep. I found several that I needed, like cairo etc, by searching around, but there are some I havent found anything on yet. The thing that makes me wonder is I removed some KDE packages I didnt want, like kdeaccessibility, kdeesu, kde multimedia etc and I think they have the libraries needed for other KDE packages, like kdeaddons which I left. Does this mean I will have to reinstall and keep these unwanted packages?

I am not sure if I want to keep KDE as my GUI, it seems rather bloated with crap I'll never use.

Edit: Also, what do I do with the .new config files? I have been running my system for a while now so they might not be the default ones. I haven't edited anything yet, so can I just copy over all the .new ones to be used (keeping backups of the ond ones).

Start a new thread on this and it will get a lot more exposure. It is a good idea to stick with official Slackware packages when hunting deps. There is a package browser on the main Slackware site that helps with this. It is also a good idea to make sure you are cautious with Slackware versions.

I look at it like this. You have two packages, Package_A and Package_B. You don't think you want Package_A. You know you want Package_B. If Package_B depends on Package_A, then you actually want both packages. You may think you never want to use Package_A, but if Package_B depends on Package_A, you are (in some small way) using Package_A every time you use Package_B.

So short answer, yes, you need those packages, nut only if you are sure that the other packages depend on them.

If HDD space isn't an issue, it's easier to just leave it and not use it.

This is what I do:

This should find all of the "new" config files. Now, you need to know a thing or two. For instance, /etc/passwd should not be replaced with /etc/passwd.new. Same for shadow and groups. I usualyy just move the .new versions of those to .orig so I know what the originals looked like. It's good to take a peek anyway, though, to see if new groups or system users (that you may need) have been added to the default install.

For all others, It is best to use diff to reconcile differences. Just moving the .new files blows away all of the configurations that you've worked so hard on.

Let me give a psuedo-example. Let's say you have a file /etc/something.conf and another /etc/something.conf.new. You will want to back up the new config:

Then look at the differences:

This will tell you all the differences between the two files. At this point, I like to edit either file (or both, depending on the differences) until the two files are identical. This will ensure that any new formatting or options are being used properly and that you retain your original configuration.

This can be long work, but it is worth it IMHO. Hopefully this brief explanation makes sense.

Thanks heaps for posting that.

I did that thing with the .new config files. I used the screen function (its awesome!) And went through them all. Most were the same, with the exception of DIR_COLORS and unfortunately I used the new one so I have lost all my pretty console colours. Oh well, I'll figure it out soon enough.

As with the libraries, I managed to find them all eventually. Most were to do with KDE and the stuff within it I had removed. HDD space isn't an issue, but I am bothered by unnecessary stuff - Like all the Vaio crap thats on my laptop. That's just how I am though.

I don't belive you said that..
I can see you are not a real Slackware user...
Do a full install is the only way to have a poor Slackware installation!!!

if you are going to install slackware that way, it's better for you to install mandriva!!!

lolz i think thats a good thing to do. do a full install then afterwhich remove the unnecessary pkgs one by one. by doing this you would know how to recover if something goes wrong because you know what you removed.

Doing a full install of course is good for all novice and intermediate Slackware users, unless biello you are so advanced that you know how each package affects others behaviour and all each package dependencies.
It sounds very strange for me how can somebody criticize shilo for not being real Slackware user after his post/howto getting around 160 000 views and his superb website.
Maybe could your express your opinion what being a real Slackware user means? It would be very interesting to listen.
And how could a full install make Slackware poor?

It's the best thing for newbies to do ( a full install). Even now, I can't recall how many times I've done the 'expert', and forgot some obscure package. Since it's comparativly small( <3GB) 'full' install, it doesn't bother me to "install it all, and sort it out later"

Obviously biello is perfect, so everybody bow to biello's great, never wrong knowledge, obvious by his great amout of postings and.....Wait...What postings?

Sounds like it just wants a rise out of us.

Like I'd trade my perfectly working Slackware for Mandriva.....

Guys, please don't continue responding to biello's troll.
The only way to handle a troll is not to respond. Let the
moderators do their job. You will run the risk of a flame
war, and getting this thread closed. It's helped a lot of
guys new to Slackware, so let's keep it clean!