oshunluvr

What source did you use? The one I had hooked up didn't have the plugins or manager packages and when I found them via pbone they conflicted with the first quinnstorm package EDIT: Ok I found one that was current (carroll.cac.psu.edu). I also needed csm-0.12-4mdv. I will report back

Firstly - why the upgrade? 2007 is still unstable. There are more than a couple problems you might well wait for the full release in a few weeks. Secondly - Mandriva upgrade installs are notoriously buggy and usually end up with a full re-install. I guess your two computers are similiar or you'd be having more problems like this one. Thirdly (?) - If you do an upgrade and your system becomes unusable, what then? If you can do without this computer - why not do a full install? If you can't do without it - why upgrade? To your issue; it's going to depend on what you did with your original install. My guess from the limited info: Your original install had one or more mounted locations on another drive(s). You should be able to edit /etc/fstab and remove or comment ( with a leading "#" ) all references to no-longer existing drives. You need to know the device labels for your drive in your current setup so you don't render your system unbootable. I assume none of the needed partitions for your old install were on other drives. If so, it's unlikely you'd be able to boot to it. I'm going to assume you know nothing so excuse me if I seem to be talking down - I just don't know what you already know... Device labels in your fstab for hard drives look like this: /dev/hda1 /dev/hdb5 /dev/sdb9 The full entries look like: "/dev/hda5 /mnt/2006 ext3 defaults 1 1" The different labels mean : "hda" means the master drive on the first ide channel, "hdd5" means the fifth partition on the slave drive on the second ide channel. the "s" in "sdb" refers to scsi drives (on my system the sata drives are peusdo scsi). Most likely in a one HD one CD setup your hard drive is "hda" and the cdrom is "hdb". There won't be any drive id's in your fstab without numbers because the three letters refer to the physical drive and the number refers to the partition. Only partitons can be mounted. Partition "1" will always (almost) refer to the first primary partition and is normally the place to install to. The first partition in an extended partiton is usually 5 (I guess because you can have four primary partitions so those numbers are reserved). Do these things: Boot to the system you are trying to ungrade. From the gui open a console. Type "mount". this will list all mounted devices. The one you're booting to should look like "/dev/hda1 on / type ext3 (rw)" and the cooresponding fstab entry looks like "/dev/hda1 / ext3 defaults 1 1" . The partition number or drive might be a little different. The key is the "/" standing by itself. Then edit "/etc/fstab" using your favorite editor (you'll need to be superuser) and place a "#" in front of any hard drive references that didn't show up when you typed mount. DON'T comment out the floppy or cd's or anything else (swap, proc)- just the missing formally mounted hard drive references. If all this is too intimidating - post your fstab and the results of "mount". I may have left something out - your results may vary!!! BTW, if you had other partitons that were required to run this system that now are still in the old computer - you may be screwed. Short of restoring the system to it's orginal physical state - moving the subject partitions to one drive - correcting all the errors - and THEN upgrading... ...you'd be better off starting over... You can keep most of your personal stuff from your home directory.

Discovered this today: Using "sunna" full cd install, lilo, kdm. I installed and setup five users without 3ddesktop because with RC1 "mona" I was unable to log in with kdm after I installed 3ddesktop. I logged in as several of the users (not all) - no problem. I then installed 3ddesktop and thought everything was fine. Today I booted to 2007, logged as one of my users - no problem. THEN after I logged out as that user and tried to log in as another user - NOTHING. The screen goes to a blue background with the little circling cursor and then dumps you back to the KDM log in screen. Restarted X, no change. Rebooted - same behavior but I could log in as a different user, but only as one user - same as above. I haven't had time to wade through all the log files, but I will report if I see anything meaningful.

urpmi'd id3lib - no change Checked permissions - me owner, set to can read and write - no change I did notice today when I click the "Fill-in Tags Using Musicbrainz" the button changes to a dimmed "Generating audio fingerprint..." Probably just always says that but you never know what will matter... If it's behaving the same in another distro it must be a amarok/musicbrainz issue huh? What kernel are you using? 2.6.17-5mdv smp enabled on a P4 640j oc'd to 4.12ghz, 1 gig.

My latest bug find: Amarok 1.4.3 installed with "sunna" and musicbrainz won't work. I have all depends installed (libtunepimp et.al.) and I have even installed the -devel packages to no avail. When I open an mp3 file and select Edit Track Information, then click on File-In Tags Using Musicbrainz, I get nothing. The button itself dims as if selected but then nothing else happens, no errors, nothing. Cancel works ok. Any ideas

I have tried to wade through the hundred or so settings in gset-compiz but can't find one to control mazimize or shade behavior which are the real issues I'm having. There is a plugin for minimize but not maximize. Wierd... I'm feeling like it's a dual screen vs. 3ddesktop issue. i.e. what I want doesn't yet exist. More research under way...

I am having a simliar problem. I have been using twinview with my nvidia 6600 card on dual dvi dell monitors for a couple of years. I did a clean install of "sunna" without 3ddesktop and used my xorg.conf (looking very much like yours) maximize worked as before. Now with 3ddesktop and the current install I am having a few issues. The maximize worked great with 2006. See my other post regarding this issue: https://mandrivausers.org/index.php?showtopic=34972 edit: I have never used the xinerama option, only twinview cause I like XGL running.

post your /log/var/Xorg.0.log and /etc/X11/xorg.conf files

You know, I had been there before but I still can't find the settings I'm looking for.

Dude, if you want some help you're going to have to be more specific and help yourself as well. The entries are time stamped and thes is a clock on your computer. Note the time the error occurs and look at those entries in your log files. Are you installing packages with your eyes closed? If not, what are the names of the packages. They don't all have the same files in them or have the same dependancies or conflicts. Saying "some" package and looking for someone to fix an error with no details is like asking a car mechanic to fix your car over the phone. We can't guess at what's wrong or what you're trying to do.

Ok, now that I have 3ddesktop running - friggin' kewl! - I have noticed some differences in window behaviors on my system that I don't like. I use nvidia and twinview and have been since Mandrake 10.0. 1. Maximizing a window use to fill the monitor on which the window was located, now it spans both monitors. 2. Double clicking the window title bar use to "shade" the window, now it maximizes. 3. A newly opened window pops up to the right of the last active window until spanned all the way across both monitors, rather than tiled and then cascaded on the monitor on which the mouse pointer is on. Once the new windows have spaned both monitors, then it starts cascading them on monitor 1. Keep in mind I haven't changed any settings via KDE>System Administration>Window Behavior or Configure Desktop>Display>MultiMonitor Support So far, changing these settings hasn't made any difference either. It seems the 3ddesktop is ignoring the system settings. I realize this is a new thing and will be improved. Does anyone know where the 3d settings are and can they be edited?

Ok, someone suggested the nvidia brand drivers don't work with 3ddesktop. So I wiped again and did a full install from "sunna" RC2 cd's. This set uses kernel 2.6.17-5mdv .Then I did urpmi.addmedia and installed the dkms-nvidia drivers from the plf source. I also figured out while playing around with the previous install that the "Configure 3ddesktop" function in the "Configure your Computer" program doesn't appear to install all the needed componants. So I did a urpmi install of compiz, mesa-demos, 3ddesktop, and task-3ddestop and VOILA! I have 3ddesktop again. Also at 100x100dpi I'm getting 13000fps plus from glxgears. Now on to font improvements...

You should see timestamped messages in "/var/log/messages" It would look something like: Sep 17 05:23:57 localhost perl: [RPM] kdebase-nsplugins-3.5.4-32mdv2007.0 installed Sep 17 05:23:58 localhost perl: [RPM] kdebase-nsplugins-3.5.4-20mdv2007.0 removed This is from my messages file form a recent upgrade install

I only have one user on my "Mona"-installation, apart from "root". I'm interested in where this goes - I'm having a similar experience. I'm not good enough at linux to know what I'm doing. I had xgl and 3ddesktop working fine with "tyr" but now I've upgraded to "mona" and lost the ability to have 3ddesktop. When I turn it on, I can't get past the log in screen. It just pauses for a couple minutes with a mouse cursor over a background screen and then returns to "log in". Best I can tell, the mona default kernel 2-6-17 and nvidia 8774 drivers aren't happy with each other. I'm debating now if I should install an older kernel or just waitfor an updated driver.

thanks - I didn't want to continue with the old heading because the thread had left that topic.

I had this happen once. Seems if I remember the problem was when the rpm install failed, urpmi didn't delete the .rpm file. If you know the name of the .rpm file, do a search for it on your hard drive and delete it. Then re-rum urpmi and it will download it again and attempt a new install. I can't remember the default location for d/l'd rpms. Maybe I read your post wrong. You're saying you install OK. but it wants to delete some package and can't? I suggest learnign to use urpmi at the command line. You get more meaningful errors messages that way. Post the actual filenames you're dealing with so someone can help you figure this out. The more specifics the better.

Maybe, but I have read (and experienced) the dkms driver isn't compatable with the 2.6.17 kernel. Maybe it wasn't the driver and it was the xorg file. Anyone else having these troubles? BTW, even though I'm logging in now (with no 3ddesktop), I still get the can't Find faces error. Time to dig into kdmrc

OK, I had been using "tyr" for awhile. Did an "upgrade" install from cd's. Now I can't log in to x. When I try to log in, it just returns to the log in screen in a minute or so. I have done the following: Installed and then removed dkms-nvidia ( I read somewhere that 2.6.17 doesn't work with the dkms package yet). Installed kernel-source and then the nvidia-8774 drivers from their website. Got errors related to "need Xorg SDK/Development package", but install completed. I can't find a package named xorg-sdk anything. After fiddling around with directory pointers I got x to load without errors (including glx). Logged in as root from tty using "startx" once, then tried to start "dm" and had same results as above. Now no more logging in - just waits for a minute or two then returns to kdm log in screen. So I wiped and fresh installed 2007.0 RC1. I d/l'd and installed 8774 nvidia drivers from nvidia. Got same errors as before re: Xorg SDK/Development (still don't know what the hell that is)., but appeared to work. Logged in fine, but 3D not installed. Configured xorg (twinview). Noticed that .../libglx.so entry isn't there and "Option "glx"" is. (opposite in 2006). If I change it back - no log in. So maybe that was the problem before - new drivers old conf. BUT - I installed 3ddesktop and mesa and dependencies. Then enabled 3d effects. Logged out, logged back in - no 3d effects, whacked screen resolution (large fonts and pixelated wiindows). Logged back out and then couldn't log in. Removed mesa and 3d packages and I was back in business but no 3d. nvidia-settings says I have glx. glxgears is not found. remember : all this worked fine on the beta 3 release "tyr" Best I can tell at this point the nvidia driver and the 2.6.17-4mdv kernel don't like each other. Anyone getting 3ddesktop working with this kernel and drivers or the dkms/plf drivers?

Use /dev/usbmouse or /dev/input/mice with USB mice (IMPS/2). To check if Linux knows about your usb mouse: ls /dev/input Try cat /dev/input/whatever and move your mouse (garbage will appear if it's the right one). Press ctrl-c to cancel cat. In /etc/X11/xorg.conf, use Identifier "USB Mice" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/input/whatever" Option "ZAxisMapping" "4 5" Option "Buttons" "5" EndSection Scroll wheels actually report to xorg as buttons and they must be the highest numbered ones. So if you have a three button mouse (the default), use "ZAxisMapping" "4 5". If you have more than three buttons, use the "Button" option as in the example and use the appropriate numbers for the wheel. You may also need to add "SendCoreEvents" to the InputDevice line in the Server section InputDevice "USB Mice" "SendCoreEvents" p.s. I stole this info from other sources - it worked for me - good luck

Update: So I wiped and fresh installed 2007.0 RC1. I d/l'd and installed 8774 nvidia drivers from nvidia. Got same errors as before re: Xorg SDK/Development (still don't know what the hell that is)., but appeared to work. Logged in fine, but 3D not installed. Configured xorg (twinview). Noticed that .../libglx.so entry isn't there and "Option "glx"" is. (opposite in 2006). If I change it back - no log in. So that was the problem before - new drivers old conf. BUT - I installed 3ddesktop and mesa and dependencies. Then enabled 3d effects. Logged out, logged back in - no 3d effects, whacked screen resolution (large fonts and pixelated wiindows). Logged back out and then couldn't log in. Removed mesa and 3d packages and I was back in business but no 3d. nvidia-settings says I have glx. glxgears is not found. remember : all this worked fine on the beta 3 release "tyr" Best I can tell at this point the nvidia driver and the 2.6.17-4mdv kernel don't like each other.

OK, I had been using "tyr" for awhile. Decided to upgrade to RC1 today. Did an "upgrade" install from cd's. Now I can't log in to x. First I thought it was kdm, but the only kdm error logging is "can't find user faces" (or something like that). kdm inital menu loads, but when I try to log in, it just returns to the log in screen in a minute or so. Then I decided it was x: I have done the following: Installed and then removed dkms-nvidia ( I read somewhere that 2.6.17 doesn't work with the dkms package yet). Installed kernel-source and then the nvidia-8774 drivers from their website. Got errors related to "need Xorg SDK/Development package", but install completed. I can't find a package named xorg-sdk anything. After fiddling around with directory pointers I got x to load without errors (including glx). Logged in as root from tty using "startx" once, then tried to start "dm" and had same results as above. Now no more logging in - just waits for a minute or two then returns to kdm log in screen. Currently, I'm of the opinion that the upgrade install may be part of the problem. I am thinking I may just wipe and install clean. All this is happening on a different drive partition from my main one so it's not a big deal. I had only been using tyr for a week or so. Anyone have any insight as to the issue here? The reinstall may take less time than any more research!

What I've noticed is if I try and enable multible desktops, the system resets it to 1, but the rotating cube desktop is really four virtual desktops anyway - which is my preferred setup. Now I'm trying to figure out how to enable the mouse wheel to rotate the desktop cube as I have become accustom to using that method of switching desktops. If anyone cares: I'm using 2007 Beta 3 "Tyr" 3-cd release installed on P4-640j (overclocked to 4.133), nVidia 6600 gt oc with dual 19" Dell dvi monitors. I'm getting 13000 fps plus from glxgears. Since 2006 I have had no problems using the DKMS packaged nvidia drivers. This method makes driver updates really easy compared to kernel recompile. You may have to wait a month longer for the dkms-nvidia package to be available, but big deal. www.SeerofSouls.com gets them rather quickly. I did not disable "RenderAccel" yet, but may just to see if it makes any difference. I have manually set my screen resolution to 100x100 dpi and now I'm attempting to improve font look by setting up 100dpi fonts and sub-hinting.

Steve - on another note - the nVidia driver... If you've updated to 8762 the modeline entries have changed. Since this is off topic I won;t go into detail, but if you're still needing help with this - contact me and I'll fill you in.

I'm a noob, but learning. I have an HP ZD7000us that has a Broadcom BCM4306 802.11b/g Wireless LAN Controller (rev 02) internal card. I did a new install of Mandriva One (to replace 10.1) and then updated to KDE 3.5.3 and updated to kernel 2.6.16-1mdk--i586-up-1GB. When I did this ndiswrapper brokereporting "loadndisdriver: main(629): version 1.2 doesn't match driver version 0". I tried your instructions to the letter EXCEPT: There was no file "bcm43xx-fwcutter" in the archive so I ran "make" first. The additional step of "export..." was required. I appears that I am up and running - still some testing to do reguarding settings and the like but it seems to be running. I am wondering now if the on/off button will respond correctly and I may need to build a script to restart the card - not a major hurdle. It seems to be dumping a lot of messages to the log so I'll have to look into what's going on there. Thanks for your detailed instructions. It really helps a lot of beginners when the steps are laid out without assuming the reader gets what you mean. I'll report back with my end results.

Here's my two cents... dkms is supposed to allow you to update drivers and such without going through an entire kernel compile process. However - dkms will require you to un- and re- install packages whenever you update your kernel. Not a big deal but you need to do it. It seems there may be problem with your kernel source and module files. I have had several mandrake/mandriva distros not updating symlinks properly and such. I know I'm going to repeat some stuff you've already done/read...I suggest the following: Make sure your kernel-source and kernel match - then check the "linux" symlink under "/usr/src" and make sure it points to the proper directory, i.e. the one with the same name/number as your kernel. If it doesn't delete it and make a new symlink to the correct one. If you still get the above error you may want to reinstall the kernel and source after unloading dkms-nvidia (see below) In the same directory (/usr/src) you should see a nvidia-XXXX (your old or current drivers) directory and a nvidia-8762-0.1.20060plf (the new ones). dkms uses its own install program to setup it's modules. You need to uninstall the packages using dkms and THEN update your kernel AND kernel source and THEN install the dkms packages you use (I use nvidia and kqemu). To access dkms open a konsole, log in as root and type "dkms status" and it will list all packages that are loaded correctly on your system AND which ones are INSTALLED (refering to dkms). If if shows nvida-7676 (or whatever old driver you were using) then type "dkms remove -m nvidia -v 7676 --all" and then "urpme dkms-nvidia-7676" or whatever the whole package name is. This process applies to all dkms packages you don't want to use anymore. When you are going to update your kernel - first do "dkms uninstall" (not remove) for all your packages, then do your kernel updating and then "dkms install" your packages. If you "dkms remove" you will need to re-download the package again - basically use "remove" to delete a dkms package you plan on not using again or updating and "uninstall" to just take the package out of the kernel module build list. I suggest doing a web search on dkms and learning a little about it. Also if you don't use "dkms remove" to delete a package, urpme will fail and you won't be able to remove it later. Good luck and I hope my advice doesn't crash your system! Web searches are a great tool! p.s. I am running two Mandriva systems - my 2006 Powerpack system runs the 8762 drivers no problem and my laptop Mandriva One new install with KDE 3.5.3 won't load glx. I am working on it as I type this. Desktop - P4 640j 3.2, Mandriva 2006 Powerpack, kernel 2.6.12-22smpmdk, nVidia 6600 GT OC, KDE 3.4 Laptop - P4 2.66, Mandriva 2006 One, kernel 2.6.16.1-1mdk, nVidia GeForce 448, KDE 3.5.3