chris z

ok. let's back track a bit............... what version of mdk are you using? what kernel? if it's a 2.6.x kernel, do you by any chance have scsi emulation in your lilo.conf? 2.6 kernels don't use scsi emulation, so that might be buggering it up. look in /etc/lilo.conf at the "append=" line & if anything says "hd(X)=ide-scsi", remove that, save it, run lilo -v from terminal as root, reboot then try to burn again. if that's not the problem, then i'm almost ready to suggest uninstalling k3b & cdrecord, then try reinstalling them fresh & doing a fresh setup for k3b. if i think of anything else in the mean time, i'll post back. Chris

just guessing here at the moment, but did you try ps -aux from terminal as root? look for the process cdrecord to see if it's still running. if so, kill it, then try burning again. also, are you trying to burn as user or root? if it's user, try as root & see if you can burn. if so, did you add you (user) to the burning rights during the last part of k3b setup? that's all i can think of at the moment. if none of the above applies/works, start k3b from terminal (just type k3b & hit enter). post back with any errors it spits out. Chris

hi DragonMage.......... that app is the Klaptodaemon. it's part of the kdeutils-(version) package. so, install kdeutils. Chris

try running, from terminal as root............... sndconfig let it search for your sound card, accept the correct device it finds (if it found more than one), click the test button (it will probably be very quiet), then adjust your volume settings with aumix (kicker->multimedia->sound->aumix). save the settings. if aumix isn't there, then use MCC to install it first. Chris

did you try checking & setting the correct time via your bios? that's where the Mandrake time is read from, so if your bios clock is set wrong your Mandrake time will sync with that & also be wrong. Chris

try this............ open /etc/fstab with a text editor, look for the line that says /dev/fd0 (blah, blah, blah) & comment it out (like this............ #/dev/fd0 blah,blah,blah). save it, reboot, & mdk will (should) redetect the floppy drive as new hardware & set it up for you anew. Chris

to expand a bit to what Sarissi said........... he's correct. if you don't know how to disable scsi emulation, open your /etc/lilo.conf file with a text editor of your choice, look at the line that says "append=" & remove any line that looks like hdX=ide-scsi (where X is the name of the device). save the file, then in terminal as root type lilo -v (hit enter) for the changes to take effect. reboot. note, it's always a good idea to make a back up of the lilo.conf before you go mucking about with it. Chris

you need to add the executable (or a symlink to it) to your KDE autostart directory. a couple of ways to do this........... open Konqueror in superuser mode (you need to have root access to be able to copy from /bin directories). to do that, open a terminal su to root (type su at the prompt, then your password, then enter) then type...... kdesu knoqueror (hit enter) that will give you root powers in Konq. find the program's executable that you want to autostart, copy it, then go to your /home/(you)/.kde/Autostart directory & paste it there. (note......... the /.kde directory is hidden, so you have "show hidden files" enabled from the "view" menu.) better (easier) method. open konqueror file manager as normal user, navigate to the /.kde/Autostart directory, click edit->create new->link to application. name it, fill in the execute command (that would usually be something like /usr/bin/nameofapp) click "ok" when done. best (easiest) method (& you get to practice some command line to boot B) ). open a terminal & as normal user navigate to the Auotstart directory by doing......... cd .kde/Autostart (hit enter) (note......Auotstart is cap sensitive) then create a sym link to the application executable. to do so, you'd type..... ln -s /path/to/executable, hit enter. (example: ln -s /usr/bin/nameofapp). hope that helps. Chris

try using MCC (Mandrake Control Center)->hardware->mouse to change the settings. i think KDE uses it's mouse settings from MDK. Chris

do all themes crash it, or just liquid weather? if it's just liquid weather, then i'd blame that theme & say just use something else, or you could look at the *.theme file for it & see if anything looks funky there. (like a pointer to an image that don't exist, a bad command to a sensor, etc.) if it's happening with all themes, then which method did you use this time to install superkaramba, RPM or compile with the "on top" hack? if the second scenerio applies, then i'd suggest trying the opposite install method. IE:, if you compiled try the RPM & vice versa. Chris

yup. then, use the find / -name superkaramba command to locate any risiduals (there will be some) & delete them. Chris

ah. that problem. ok, here's the scoop. alot of superkaramba precompiled packages have a workaround for that built into them. the source files for it still don't, apparently. 2 options........ and you probably don't want to hear either of them.............. uninstall superkaramba & reinstall via a MDK precompiled rpm. i'm using cooker version 0.32b-2mdk & i don't have the always on top problem. but, i see there's a version 0.33-2mdk in cooker right now with a patch for that problem built in too. (note: i found the following info by Googling HERE) uninstall superkaramba, & before you compile, unpack the .tar file & use a text editor to open the karamba.cpp file contained therein. look for a line in that file that says.......... KWin::setType(winId(), NET::Dock); and change it to read.............. // KWin::setType(winId(), NET::Dock); save it, then compile. Chris

ok.....your first question. i installed superkaramba via a rpm. that's the default directory it installed to......... /usr/share/apps/superkaramba. maybe the compile installs it differently. not sure. if you're curious, in terminal, as root, type......... find / -name superkaramba it might take a little while, but that will show all instances of superkaramba on your computer. question 2........... you can have superkaramba start 2 ways (if you're using KDE. for another DE, i'm sure you can, but since i use KDE, that's the method i'll give you). method 1 (dirty way)......... open Kontrol Center->components->session manager. check "restore previous session"->apply. that way, if superkaramba is running when you shutdown/restart it will automatically run next time you start KDE. method 2 (slightly longer GUI method, but cleaner).............. open konqueror file manger. navigate to /home/(you)/.kde/Autostart (note, /.kde is hidden, so you must have hidden view enabled). click edit->create new->link to application. name it under the general tab, make the execute command point to /your/path/tosuperkaramba/nameof.theme->ok. if you do that, you don't need the restore previous session method to run it because you've just added a symlink to it in the KDE Autostart directory, which will run superkaramba upon KDE start up. method 2.1 (not quite as long CLI method, but more proper)................. open a terminal. as normal user cd to the KDE Autostart directory (cd /.kde/Autostart)-> type the following..... ln -s /your/path/tosuperkaramba/nameof.them->enter. you now just created a symlink to the theme to start automatically. Chris

i don't think it adds a menu entry if you compile it from source. to add a menu entry, right click kicker->menu editor->choose where you want it to go->add application->name it->use the follwing for a execute command........... superkaramba /usr/share/apps/superkaramba/themes/default.theme save. that's the default path for superkaramba........ ->/usr/share/apps/superkaramba Chris

i've found that some of the themes are quite buggy. i've had quite a few that wouldn't work, or only worked half arsed. i'm really not an expert with it by a long shot. it took me a while to figure out to edit the theme i'm running to get it looking & working right. it was sorta like editing html code in the theme file itself. just try various ones 'til you find something(s) you like. and, if you wanna play around with them, go to /usr/share/apps/superkaramba/themes (as root) & open any *.theme file to take a look at it. if you're going to try to edit or play around with one, i'd use a text editor (like kedit) 'cause it will automatically make a backup file for you. should you barf something up, just delete the *.theme file & rename the back up to it's original name. Chris

for some reason, unbeknownst to me, superkaramba installs a shortcut under kicker->applications->monitoring. if you click on that, it should run the default theme "default.theme". (how original, huh? :lol: ) it's basically a temp/cpu monitor & a Mandrake logo with a link to the MDK site. superkaramba takes some getting used to. the defualt themes are pretty lame (IMHO), but there's lots of nice ones to get from KDE-Look.org. some of the themes are easily edited to suit your needs. you can use them sorta like templates & replace them with your own fonts, png's, text, etc. for the sensor themes to work properly, you definitely need to tweak them & make sure you have the appropriate sensors installed. here's a screenie of my desktop running a highly modified theme called tmon-keramik.............. Chris

next time run.......... ps -aux it will give you more info. urpmi processes will say urpmi in the process line. there will also be a process or 2 pertaining to "curl" that you will need to kill. the ps -ax command isn't sufficient enough to show urpmi running, so it isn't in the list you posted. if it should still remain locked after killing the processes, then a reboot will unlock it. Chris

there is no control panel option to tweak nvidia things in linux, sorry to say. you must do all the tweaking via adding options to xf86config-4. i'm definitely not a pro at it by a long shot, but if you read through the nvidia docs it tells about which options you could try, where to put them, & what they should do. i think your speed is prolly as good as it's gonna get due to the fact the the board is a bit older (geforce3 vs. geforce4) & it's also limited by your processor speed (athlonXP 2600 here). Chris

when you ran the flash installer, did you specify the correct paths to your plugins directories? i don't use firefox, but i THINK it uses mozilla plugins. if i'm wrong, then when you install flash you must tell it to install to your firefox plugins directory when it asks for that. the default would be /usr/lib/firefox . there's no need to add /plugins to the path becuase it will automatically determine where the plugins directory is & put them there. also, if you have older flash plugins, delete them first. finally, after you do the above, you may need to open KCC->web browsing->plugins & scan for new plugins, click apply, then try flash in firefox. to see if it's detecting the plugin, click "help"->"about plugins". Chris

your sprint DSL cd will prolly be useless to you in linux becuase it's intended for a Windows installation. what you'll need to use is drakconnect. all you'll need to know is a few bits of info (ip address, provider name, static adsl, username, password). just use the wizard & it will walk you through it. a couple helpful hints................ make sure you don't have a firewall running when setting up the connection. also, for some reason, drakconnect doesn't always connect when you get that option at the final screen. to test your connection, open a terminal, su to root, then type........ adsl-start enter to start the connection adsl-stop (to stop) adsl-status (to see connection status) Chris

your drivers section looks ok. you might want to try editing out the Option "DPMS" line. (thanks tyme B) ). might be a silly question to ask, but since i'm silly, i'll ask............ you say you dloaded the nividia drivers. you did run the install script per the nvidia docs, didn't you? and, you did it with all instances of X killed, right? (like from init 3) i have a GEForceti4600 board. here's my output with the nvidia drivers installed................. [root@default chris]# glxgears 20685 frames in 5.0 seconds = 4137.000 FPS 20732 frames in 5.0 seconds = 4146.400 FPS 20847 frames in 5.0 seconds = 4169.400 FPS 20817 frames in 5.0 seconds = 4163.400 FPS 21955 frames in 5.0 seconds = 4391.000 FPS 21951 frames in 5.0 seconds = 4390.200 FPS Chris

so you're good now? you could always use userdrake (or kuser in kde) to add user groups, permissions, etc. chmod 777 in cli would prolly do the trick too. hope it's ok for ya now, though. Chris

you are trying to access them as root, aren't you? i mean, you should be able to view them as user, but not edit them as user. what are the permissions for them? the norm for /etc/directories should be rwxr-xr-x owned by root. rw-r--r-- owned by root for the /etc/config files. you could reset the permissions one by one if they're all screwed somehow. time consuming, but it should work. or, you can try the upgrade method method with the install cd's. that should set things back to normal. Chris

did you try the lsof command? might be worth a shot to see if something's using the device that you aren't aware of. Chris

settings->save view profile->give the view profile a name in the box that pops up, check (or uncheck) the "save url's" & "save window size" boxes as desired, click "save". Chris