Jump to content

chris z

  • Posts

  • Joined

  • Last visited

Everything posted by chris z

  1. did you click "apply" after unchecking the option? have you restarted KDE? if not, do those 2 things. it works for me in MDK 10.0 w/KDE3.2. Chris
  2. i've had the same "rivafb" message while installing Nvidia drivers with every 2.6 kernel in 10.0. i just ignore them & continue with the install & have no problems. i'm pretty sure this has been mentioned elsewhere, but there are several options you can add to your "device" section in XF86Config-4. see below....... Section "Device" Identifier "device1" VendorName "NVidia" BoardName "NVIDIA GeForce4 (generic)" Driver "nvidia" Option "DPMS" Option "NvAGP" "3" Option "NoLogo" "1" i have mine set at "3" which tells it to use kernel AGP support first, then Nvidia AGP if the kernel version doesn't work. other numerical options you can use are......... "0" (no AGP) "1" (nvidia AGP only) "2" (kernel AGP only) try different settings there & see if the freeze ups stop. you don't need to exit X to add these options. just edit your XF86Config-4 file with any text editor, then restart X for changes to take affect. Chris
  3. just to let anyone who cares know, i solved this one, albeit with a dirty sort of hack.............. after screwing around with config files 'til my eyes were buggy & using various MCC internet tools ad naseum, i finally decided to try another "upgrade", this time just upgrading 10.0 on top of the current 10.0. after all was said & done, i rebooted, reinstalled my nvidia drivers, typed adsl-start from terminal in KDE & wala! problem gone! so, the cure to this ailment is simply boot from the install CD & choose "upgrade"........... again. oh...........one thing that may have made a difference this time around. during the initial upgrade from 9.2, when it came to the final config screen, i didn't bother checking the internet config settings. it didn't show an error & i was neglect in checking if all was ok there. this time, even though it wasn't showing an error again, i did check. i found all my settings were still intact "except" for where my provider name belonged. that was blank. now if that was the case the first time around & the cause of this, i don't know. but, better safe than sorry, eh? hope this might help anybody else that should run into this problem. thanks for the help you offered Gowator. i appreciate it. Chris
  4. tyme......... i have all updates applied/installed. my hostname has been "default" (without) quotes since day one & still is, so that hasn't changed. gowator.......... i have no idea what you mean by...... echo <yourhost> > /etc/hostname echo <yourdomain> /etc/dnsdomainname will that give me info of some sort? and, could you explin what pppoeconf is/does? nevr heard of it nor used it. in the mean time, i'm gonna compare some /etc files form my 9.2 to the 10.0 stuff to see if i can find a difference somewhere. Chris
  5. thanks for the reply, anna. i thought i might have set a record for views with no replies before you chimed in. :P no, harddrake isn't the problem, even though it was a good thought. my eth0 card is detected on boot without any errors. the network comes up on boot & so does loopback. that's the perplexing part. everything that should, loads at boot without an error. if i had an error message, then at least it would point me to the proper location to look for something wrong. i played a bit with some config & script files in /etc last night, to no avail, so i'm still stuck here. thanks again, though........ Chris
  6. just a bump up. also, i edited my original post. after a bit of research i realized that ADMtek makes the Linksys card so it's not detecting my onboard card, it's seeing the correct one. still no luck here figuring out why the settings don't stick. Chris
  7. hey all, i finally got around to installing MDK10.0 (better late then never, eh?) everything is working fine except for one nagging issue. everytime i boot into it i have to run DrakConnect (or now as it's called, MCC->network & internet->make new connection) in order to connect to the internet. all my IP settings are always present & saved in there, but i just can't connect unless i run this first. my normal connection method is to run adsl-start from cli. if i try that before running DrakConnect, it just gives me a timeout message & doesn't connect. if i run DrakConnect first then issue the adsl-start command, it connects fine. i get no errors. it just tries to connect for several seconds, then "TIMED OUT". i've tried setting it to connect on boot, but the same things happens during boot............"TIMED OUT". has anybody else encountered this & is there a fix? oh, i have a Linksys Etherfast 10/100 card on eth0. there is something fishy that i do notice. when i look at the "manage connections" module in MCC, it shows "adsl" as default "device selected" but i can also change it to eth0 where it shows my Linksys card. should it show adsl & the card or should it be just one device listing be in there? any help will be much appreciated. if you need me to post any more info, please let me know. Chris
  8. chris z

    desktop links

    3 things come to mind.......... right click the desktop link, select "properties" you made & check the following....... your executable path to make sure you didn't make a typo with the command. below that, make sure the "run in terminal" & "run as different user" boxes aren't checked. check your "permissions" & make sure it isn't set to root & all appropriate "read" "write" "exec" boxes are checked. Chris
  9. it's Kontrol Center->lookNfeel->system notifications, then look for the button in the lower right corner that says "player settings". pick a system sound notification from the list that you want to quiet down, click the player settings button, adjust the volume their, or disable it all together & use the "external player" option which will let you use another sound app to play the sounds. click "apply" when done. Chris
  10. i'm not at the linux box right now, but the settings are somewhere in Kontrol Center. maybe in "sound" or "look & feel". look for settings for "notifications". if somebody doesn't narrow it down or you can't find it before i get home, i'll post back with the exact info later tonight. Chris
  11. that is the correct nvidia driver at the link you posted, unless you have an Itanium processor, then get the IA64 instead. you need to install the nvidia drivers. you can get them HERE . download the file called NVIDIA-Linux-x86-1.0-XXXX-pkg1.run & save it to your hardrive somewhere, then follow the instructions below to install............ (XXXX=current version number) PLEASE NOTE:you must have the kernel source installed in order for the nvidia drivers to function! 1. start the computer & choose the "failsafe" option to boot from. (this will boot you into text mode & dump you at a login prompt) 2. at the login prompt, type your user name (enter) password (enter) 3. type su (enter) password (enter) this will put you in root mode. then type...... init 3 (hit enter) to kill xserver. relogin as root. 4. navigate to the directory where you have the nvidia installer script. 5. type ls (enter) that will list the contents of the directory (in case you have more than one file on there. you're going to need to know the install script file name, in full.) 6. type the following. this is CapSenSItIve....... sh NVIDIA-LINUX-x86-1.0-XXXX-pkg1.run (XXXX=current version number) 7. accept the agreement, then answer yes to the prompts. it will load the drivers & when it's done it will dump you back at the prompt. 8. we're going to use VI to edit your xf86config file. follow the steps exactly as i type them. again, it's CapSensiTIve. 9. type vim /etc/X11/XF86Config-4 (enter) 10. type i (this is for insert mode so you can isert the proper driver line) 11. use your arrow keys & scroll to the section where it says Section "Module". under that, make sure there's a line that says Load "glx" # 3d layer . if there isn't, add it as the last line, then hit esc . 12. if it says either or both of the following under the "Module" section (Load "DRI" Load "Glcore"), remove them by typing i & using the arrow keys to navigate to them & the space or backspace bar(s) to remove them. hit esc . 13. type i & use your arrow keys to navigate to where it says Section "Device". navigate to where it says Driver "nv" or Driver "vesa" & make it read Driver "nvidia" .........that's Driver(space)(quotes)nvidia(quotes) 14. hit the esc key. 15. type :wq (enter) ..........that's (colon)wq then hit the enter key. 16. type reboot you're computer will now reboot, choose linux from lilo as you normally would. if all went well (& it should have) you'll see a nvidia splash screen just before your GUI login. also, one note. sometimes the nvidia drivers can cause random lockups. if you find that happening, use your favourite text editor, open that same XF86Config-4 file, & directly under where you changed Driver "nvidia", add the follwoing line.......... Option "NvAGP" "3" (that's Option(space)(quotes)NvAGP(quotes)(space)(quotes)3(quotes). that will try to use the kernel agp drivers first, then nvidia agp if the kernel drivers don't work. other numerical options you can use with that are........ "0" (uses no agp support) "1" (uses nvidia agpart only) "2" (tries kernel agpart only) save it, then restart X or reboot. smoke 'em if ya got 'em. Chris
  12. you didn't by any chance set your security level to high, like "high" "higher" or "paranoid", did you? that could cause probs with regular users logging in. go to MCC->security->draksec & if your security level isn't set to "standard", set it to that, reboot. Chris
  13. you need to edit your lilo.conf file & add an entry for your Windows partition. the easiest way to do so (IMHO) is (if your using KDE) open Konqueror in SuperUser mode. (open a terminal, su to root, type konqueror, hit enter) navigate to your /etc directory. use your favourite text editor to open the lilo.conf file located in /etc. add the following entry somewhere in that file......... other=/dev/hdXNUMBER label="windows" table=/dev/hdX where other= /dev/hdXNUMBER is X=the letter of your hard drive (usually "a") & NUMBER=the number of your Windows partition (can be any number, depending on which partition Windows resides on). label= can be any name you want to show up in the lilo menu choices for Windows. and table=/dev/hdX is X= the letter of your hard drive. for instance, my old dual boot with Win98 looks like this........ other=/dev/hda1 label="windows" table=/dev/hda here's the excerpt from my lilo to show where it goes......... image=/boot/vmlinuz label="failsafe" root=/dev/hda5 initrd=/boot/initrd.img append="failsafe acpi=ht resume=/dev/hda3 devfs=nomount" read-only other=/dev/hda1 label="windows" table=/dev/hda other=/dev/fd0 label="floppy" unsafe after you edit lilo.conf, save it, then in terminal as root type........ lilo -v hit enter. reboot for changes to take effect. if you're using Gnome or another DE, the same method applies, but you need to use whatever the appropriate file manger for that DE would be to access the lilo.conf file for editing. Chris
  14. w00t! glad to hear you got it working! looks like you did the important leg work. good job! :D Chris
  15. ok. let's start over from the beginning. when you say you got the kernel upgrade, are you sure it was a kernel upgrade or was it a kernel-source upgrade? they are 2 different things. IE: you can be running kernel 2.6.3-7 but actually have sources for 2.6.3-13. looking at your /boot, you have no vmlinuz-2.6.3-13mdk to boot to. that's telling me that you just installed the sources for 2.6.3-13, but not a kernel itself. in terminal, as root, type uname -a & tell me what kernel it says you are currently running. if it says 2.6.3-7, then you need to get the 2.6.3-13 kernel itself for that last entry to work. Chris
  16. install the sources for 2.6.3-13............ (see my post above the one you just made) Chris
  17. ok........brain fart here, sorry. you said you upgraded the kernel. so, the main linux boot option in lilo should be your new kernel. did you also upgrade the kernel source? look in /usr/src & see if there's a kernel named 2.6.3-13mdk. if there isn't, then that last entry is pointing to a nonexistant kernel. if your old kernel (2.6.3-7mdk) is in /usr/src, then that's what that last lilo entry should point to. sorry, i'm at work, gotta run. check what's in /usr/src & adjust from there. get the 2.6.3-13mdk sources if you didn't already. Chris
  18. you need to rearrange some lines. here's how your entry should look........... don't forget to run lilo -v afterwards. Chris
  19. the "append=******" line in that last entry has an incorrect spacing before devfs=. it should read like......... append="devfs=blah,blah........" no space between the " & devfs. fix that, rerun lilo -v, reboot. gotta watch your p's & q's (& spacing) when editing lilo. :P Chris
  20. in all honesty, looking at the lilo man pages is your best bet for various lilo commands & parameters.............. man lilo in terminal as root. here's about the best thing i could come up with by Googling that explains things......... Lilo boot parameters just click the "next" button on that page & the few following pages for an assortment of parameters that you can use & definitions of what they do. Chris
  21. the easiest way to edit/modify lilo is just opening the /etc/lilo.conf file as root (either with kdesu & a text editor or in terminal with vi), IMHO. if you use KDE, you can also modify it via Kontrol Center->system->boot loader & click the "administrator mode" button. just remember to run lilo -v in terminal as root after you edit it, no matter which method you use, then reboot for changes to take effect. Chris
  22. that's your lilo.conf file. it all looks fine to me. did you edit the lilo.conf file in any way? if so, you have to go to a terminal as root & type........... lilo -v , then hit enter & reboot. if you didn't edit the lilo file, then don't worry about scsi. unless, of course, you are using the 2.4 kernel which 10.0 gives you the option of doing. in terminal as root type.............. uname -a & tell me what version of the kernel you are currently running. if it shows a 2.4.x kernel then we're back to the scsi stuff. if it shows 2.6.x then there's no need for it. if it does show you are running the 2.6.x kernel, then i am thoroughly stumped. it might have to do with a k3b incompatability with fluxbox. i'm not sure. i don't use fluxbox so i never tried to burn with k3b in it. for spits & giggles, try booting into KDE & running k3b & see if it works also. if it's not a 2.4 kernel issue & you still can't burn in KDE, then i'm gonna have to pass this on to somebody else unless i have an epihpany of sorts, because i honestly can't think of any other reasons for k3b to not be working if you have tried everything i suggested so far. if something else does come to me, i'll post it. please post back with your running kerenl version. Chris
  23. do the following after editing the kicker menu............ in terminal run update-menus -v restart KDE. another thing to check.............. when you're in the menu editor, click the "menu style" button & make sure the only option checked is "all applications", then click on "environment" & make sure "kde" is checked. then save your changes. Chris
  24. and yet another thought from the deep, dark recesses of my mind......... if nothing has worked for you thus far, you could also try a complete unistall of all things cd burning related. that list would include the following........ k3b cdrecord cdrtools (may not have this, but check anyway) cdrdao (for disc at once recording) cdparanoia (to prevent overburns, buffer overflows, etc.) mkisofs (iso burning software) then reinstall all of the above, starting with cdrecord, then on down the list, installing k3b last. i'm not sure, but i think some of the above are dependant upon each other, so you may get 1 or more as depends with the other. EDIT: here's another something for you to try. can you burn audio with any other cd burning apps? xcdroast? gcombust? can you burn data? try it with another app. if you can burn with another app, then we could at least (almost) be certain that it's a k3b specific problem & not the cd burning software, since they all use the same software to burn. they're just different GUI front ends. that, my friend, is the last thing i can come up with. as always, if anything else pops into my head, you'll be the second to know. Chris
  25. i'm almost out of ideas........... since you say you had k3b running fine in an earlier install of 10.0, that almost leads me to believe that scsi is not the culprit. without boring you too much with details, scsi emulation was needed on versions of pre 2.6.x kernels for (e)ide drives. basically, it told the kernel to use modules that emulated an scsi type device on an (e)ide drive. if you want to know what ide/scsi are, here's the definitions......... ok, enough with the history lesson. just to make sure it's not an ide/scsi issue, use Konqueror in superuser mode (from terminal, as root, type konqueror then hit enter). go to your /etc/ directory & look for a text file called lilo.conf. open it with any text editor. several lines down the file, look for a line that starts with "append= blah, blah, blah........." in that line, look for something that might say "hd(X)=ide-scsi" (where X would be the letter of your cdburner. it could be A, B, C, etc.). if you have that line in your "append=" section, remove the "hd(x)=ide-scsi" part ONLY. if you remove it, leave a space between whatever went before & came after it. save the lilo.conf file, then in terminal as root type lilo -v & hit enter. reboot, then try to burn. if that does not apply, here's 2 other thoughts. look in both your /home/(you)/.kde/share/config/ & /root/home/.kde/share/config/ directories for a text file called k3b. (it might be k3brc..........i'm at work & can't check right now). delete those files if they exist, then try k3b. they are kde specific settings files for k3b, so you won't be harming the program. they will rebuild next time you start k3b. if that didn't work, then look in /home/(you)/ & /root/home/ for a k3b directory & delete those. those are your k3b personal settings directories. if you delete those, you'll have to run k3b as root & go through the setup procedure again. other than that, i'm currently stumped. if anything else comes to mind, i'll post back. please post with any further successes or failures/problesm you are having. Chris
  • Create New...