mdg

Have you tried using an older nvidia driver like the 1.0-5336 or 1.0-5328? There might be a compatibility problem with your hardware and Mdk 10

Try editing out the "code=437" line in fstab and see if that makes a difference. What is that option for anyway?

Take a look at this link, discussing the same problem as yours

You could also just stop using windows, I mean, realy, do you need it that bad?

That might be a good place to start, but it won't solve the problem. I have this issue when booting between slackware and Mdk too.

My "solution" is just move the screen into place each time

According to this article, Asus is not keen on Linux or open-source in general

http://www.mozillaquest.com/Linux04/Asus_Sucks_Story-02.html

I don't buy Asus products anyway because I think they're overpriced, but I'd rather buy from a company that supports open source

Do "lsmod" in terminal to see what modules are being loaded and post the results.

In general, you need to install your kernel source, as root

installpkg kernel-source-2.4.26-noarch-4.tgz

if you're using the default kernel.

Download the nvidia drivers (NVIDIA-Linux-x86-1.0-6106-pkg1.run) from this page and install with

sh NVIDIA-Linux-x86-1.0-6106-pkg1.run

as root.

Edit /etc/X11/xorg/conf to look like this:

In the "Modules" section, uncomment the Load "GLX" line

In the "Graphics Device Section", change "driver to "nvidia"

I think you said you had done all this, but you mentioned "rivafb", which sounds like an old nvidia card, maybe the wrong file was downloaded

Hope you make some headway with this

I have the same card (chipset) as you running slack 10 with nvidia drivers. If you don't have the nvidia drivers set up you should still be able to run X using the default configuration

I don't know which Mag Innovision you have, but the lowest model has frequency 30-70kHz horizontal and 50-130Hz vertical.

Edit your /etc/Xorg.conf file and put those values in the monitor section. You could probably put in higher values, but leave that until you know which model monitor you have.

If you have nvidia drivers working, change the Xorg.conf file accordingly (module "nvidia", enable GLX, etc). I'm not in Linux right now, so I can't be more specific. If you don't have nvidia working, use the "nv" or "vesa" module with GLX disabled.

See if that makes a difference. If not, post again

Enlightenment for me too, running on KDE base

Try to run "updatedb" with root privileges, of course, but just before that unmount the slack partition.

OK, that took care of the "locate" mixup.Thanks

I used chroot on a different partition some time ago (details are hazy), and since then I've had a few problems.

My Mdk partition is hdb1 and I have a slackware partition on hdb8. Whenever I use locate to find a file in Mdk, it searches the slack partition too.

Also, I had a xauthority error in Mdk, where I lost write ability to my homedir, so I rebooted to slack to research the problem on the net and found the same error there too.

The two partitions seem to be bound together. How can I separate them?

fstab for reference

/dev/hdb1 / ext3 defaults 1 1
none /dev/pts devpts mode=0620 0 0
/dev/hdb5 /home ext3 defaults 1 2
/dev/hda5 /mnt/92home ext3 defaults 1 2
none /mnt/cdrom supermount dev=/dev/hdd,fs=auto,--,user,defaults 0 0
none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,umask=0,user,iocharset=iso8859-1,sync,codepage=850 0 0
/dev/hdb4 /mnt/mepishome ext3 defaults 1 2
/dev/hdb3 /mnt/mepisroot ext3 defaults 1 2
/dev/hdb9 /mnt/slackhome reiserfs defaults 1 2
/dev/hdb8 /mnt/slackroot reiserfs defaults 1 2
/dev/hdb10 /mnt/slacktest reiserfs defaults 1 2
/dev/hda1 /mnt/windows vfat umask=0,iocharset=iso8859-1,codepage=850 0 0
none /proc proc defaults 0 0
/dev/hdb6 /usr ext3 defaults 1 2
/dev/hdb7 swap swap defaults 0 0

[moved from Software by spinynorman]

As root

/etc/init.d/networking restart

or

ifconfig eth0 down
ifconfig eth0 up

If you're using KDE, go to the KDE Control Center-Accessibility-Keyboard Shortcuts

Select the Command Shortcuts tab

In the window below, choose Multimedia-Graphics-Ksnapshot

In the bar below thw window, choose Custom

When the pop-up window pops up, hit the key you want to be the shortcut (print screen) and do Apply, OK, etc

The same method applies to any other shortcuts you might want to add

It's always a good idea to post the solution - that way you help someone else who may have the same problem B)

Maybe you compiled your / filesystem as a module in the kernel. eg if you're using reiserfs for your / partition, it must be compiled into the kernel, not as a module

I think it's a two part solution. Go to MCC and look for the "Display Manager" section (I don't remember where it is in 9.1). Choose "KDM"

Then in KDE Control Center-Components-Session Manager, check "Confirm Logout" and choose whatever other options you want there. Changes will only take place after reboot.

The dragon is part of KDE desktop manager

Kuickshow does the job for me

it hangs at all stages during install and also after reboot on HD

what is wrong with it ?

Have you checked that your cd's are good? If you downloaded them, check that the md5sum is OK. Also what speed did you burn them? It's possible that you have bad cd's.

are we going to wait for an update soon ?

I have been waiting to install a thruroughly tested distro

and I got it

this is bad publicity for Mandrake and I am sorry for it

Some more information on what errors you're getting would be helpful. 10 Official works fine on my computer and many others, any problems you're having doesn't necessarily mean the distro has something wrong with it

Have you tried using a different driver for your soundcard? What kind of card do you have?

Installing lm_sensors with a 2.6 kernel is a bit different from the 2.4 kernel. There is a lot of information on their website

Here's a few things to check if the sensors are not working (from the lm_sensors site):

# Did sensors-detect find sensors?

# Did you do what sensors-detect said?

# Did you modprobe your sensor modules?

# Did you modprobe your I2C adapter modules?

# Did you modprobe i2c-isa if you have ISA sensor chips?

# Check lsmod.

You already have tightvnc installed and it's conflicting with the RH rpm.

I'm using tightvnc with no problems on Mdk 10. Try uninstalling first the RH rpm and then uninstall tightvnc - it may have been damaged by the --force install you did. Then reinstall the tightvnc Mdk 10 rpm.

Type (as user, not su): vncserver :1 on the machine you will be viewing, and supply a password when prompted

On the other machine (after installing there too), type vncviewer 192.168.1.1:1, or whatever the IP of the other box is, and you should be set

If you're looking at OC'ing, remember all Athlon 64 multipliers are locked. The 64 FX is the only one which allows you to raise and/or lower the multi from the default setting. The normal 64's only let you lower the setting

urpmi will resolve dependencies for you. It's worth getting it set up properly and it's not hard to do.

Once you have it set up, you just need to type "urpmi <packagename>" as root and it will install the package as well as any other file needed for it to run

Go to the Easy Urpmi site and get it going

AFAIK, once you format to a different file system, you lose all data on that partition. To change the file system, you need to format the drive

On the offchance that I'm wrong, you can edit /etc/fstab as root, look for your "windows" entry and change the file system to NTFS. Here's my windows entry:

/dev/hda1 /mnt/windows vfat umask=0,iocharset=iso8859-1,codepage=850 0 0

Change "vfat" to "NTFS"

Have you checked your floppy cable and power cable? Maybe something worked loose. Is the drive set up correctly in the bios?

I think it's in the kdeedu package

etc - etcetera

fstab - f stab

fsck - f sack

usr - user

sbin - s bin

var - like "bar"

mnt - mount

tmp - temp

shp - sheep

:P