Jump to content

illogic-al

Members
  • Posts

    544
  • Joined

  • Last visited

Everything posted by illogic-al

  1. there is an ACPI how-to on tldp.org
  2. do you have an hdX=ide-scsi entry in your /etc/lilo.conf file or anything similar?
  3. are you using xmms to play these files? if so go to Preferences > Output Plugin > ALSA then click on the Configure/Preferences button. Then go to the Advanced settings tab and uncheck MMAP mode
  4. get the 5336 script from the nvidia sight. get the -13 kernel source rpm and then install the 5336 drivers in console mode (NO X) I've no idea where you got the NV.run file but maybe (just maybe) it's causing some problems.
  5. "5 6" "3 4" won't work but "6 7" will. Now you'll have your extra buttons but the scroll wheel will only scroll horizontally, not vertically unless you place the mouse pointer directly over the scroll bar. Very annoying so I put mine back to "4 5"
  6. sounds like an overclocking problem to me. that board isn't oc'ed is it?
  7. enable the legacy usb support and then try mandrake rescue disk again and see if lilo re-installs
  8. actually i just check the 10.0 INSTALL.txt and found this: so it would seem you are looking for hdcdrom_usb.img not usb_cdrom.img
  9. the only thing i can think of then is using swapping in a cdrom from another machine temporarily.
  10. it takes a while for x to boot on slow machines. a blue screen and wait cursor should be visible until KDE or gnome or whatever you chose starts up. How fast is your computer's processor? How long did you wait before determining that it wasn't booting?
  11. i think the problem is that you are trying to use an external USB drive as your boot device. I tried doing this for my motherboard with an external USB cdrom drive and could not get it to boot from disk. This is probably your problem. You need to find some way (bios) to get usb up and running before boot sequence initiates. I think my motherboard has a USB MSDOS mode or something like that. It didn't help with the USB cdrom but it may work with a hard drive.
  12. about time. I've been on the ET forums since last year lurking when i saw this. It's taken a helluva long time but hot damn! it's finally here!
  13. it had to be done Medium pimping baby. <--------
  14. http://forms.intergate.com/system.php?syst...id=IGATE-INTRNL maybe that'll help too
  15. sup gorgeous. ok open up a terminal and then type vi /etc/resolv.conf you can paste the above into the terminal and just hit enter. Then copy the contents of said file and paste in here. Oh to make sure you are actually connected to the net. I'd try checking with MCC first. Open up the Mandrake Control Center, Go to Network & Internet > Monitor Connections. If you see pretty little red and yellow lines, and and average recieveing AND Sending speed, then you are, in fact connected.
  16. came across this gem after i needed to split up the 3.6 gig ut2004 iso i had on my mom's computer to put on my own. to split up large files into smaller files and then join them back together all you have to do is cd to directory where you want the split files to go split -b 650m /path/to/file/being/split to join the files together again use the cat command cat xaa xab xac where xaa, xab etc are the name of the files after splitting In a console try man split or in konqueror type man: split to see more options :D
  17. Browse: [About the FAQ Forum] [Table of Contents] [FAQs] [Contribute] [RPM: About rpm usage (urpmi, rpmbuild...)] TR-05: How to Troubleshoot problems Here's a list of useful links to check out and things you should know, should something go wrong with your beloved PC. My second favorite troubleshooting hangout (no. 1 being here) is on IRC. Check the connecting to IRC how to to see how to connect. Freenode (an IRC network) hosts a large no. of open source project channels where you can get help. Usually all you have to do is type the name of the project preceded by the hash sign (#), e.g. #kde, #qt, #xchat, #nvidia. Some linux distributions have unofficial channels in freenode as well where you can go for help, e.g. #mandrake, #slackware, #fedora, #gentoo. There're also channels aimed at more general non-distro, non-app(lication) specific help, e.g. #linux, #musb. Be forewarned though, some of these channels are pretty crowded so you may have to ask your questions more than once. Troubleshooter No. 2 for me, which really should be the first, is the manuals/documentation which comes with most distros. The Linux Documentation Project is an excellent source of these. Also any distro worth its salt will have it's own documentation and help manuals. They are available with boxed (bought) products, online or both. More often than not these manuals/how tos have the answer to you're exact question. Provided documentation that comes with applications (not distros, but the apps themselves) can also be useful in troubleshooting. Provided documentation that comes with applications (not distros, but the apps themselves) can also be useful in troubleshooting. These can be accessed from man and info pages, the documentation found in the /usr/share/doc directory and in the Readmes accompanying source files. Man pages for a certain program can be accessed at a terminal by typing man name_of_program Similarly, info pages can be accessed by typing info name_of_program Documentation in the /usr/share/doc ($DOC) directory usually have names which somewhat correspond to the app being looked for e.g. $DOC/php_manual_en/ or $DOC/NVIDIA_GLX/. Information is usually obtained here in the form of webpages (html) or READMEs (text files). The README files accompanying most source packages, a.k.a tarballs, may also contain useful troubleshooting information. GOOGLE! < insert angelic harmony here > For the experienced troubleshooter, google can be the first thing to head for when in trouble or a last bastion for the hopeless. Either way, it is an invaluable resource. Whatever problems you're having, chances are somebody else has had them before. This means you can search for it on Google and be damn near guaranteed of finding something on it, including but not limited to solutions for the problem. Google also has a linux specific search engine called, imaginatively enough, Google Linux :) which can be found @ www.google.com/linux. For troubleshooting you can paste in parts of an error message to get results on sights with similar messages. Chances are a fix will be floating around somewhere. Google is also useful for solving rpm dependencies. N.B.: www.google.com/linux is NOT the same as www.google.com/linux/. Notice the trailing slash at the end... RPM stands for Redhat Package Management (or something like that). It is an alternative method to installing applications, much like exe(cutable)s as seen in windows. You may have noticed that most of the troubleshooting methods documented here involved a working system of some kind. Either the internet has to be working or you need to have bought a boxed product to get available documentation. Sucks if it's your ethernet card or modem that you're having problems with, don't it? Lesson for today? Buying a boxed product of you
  18. 1) IT'S A BUG, get updates 2) ineptitude? I just tried it. kmail started up, then korganizer started up in kontact. 3) it's a bug, get updates. 4) use the clean install then. just move your home directory to keep old settings. 5) ask mdk. that was caused by an mdk patch not kde people. But you could always just move it yourself. 6) yup 7) dunno 8) dunno 9) new stuff with kernel 2.6. google be thy freind fs=ext2:vfat is just a way of defining multiple filesystems 10) not unless you/other users manage to change mdk developers minds or someone decides to fork the project 11) This is now in the Meta Info tab 12) ack. too many questions. info overload! 13) that's not urpmi, that's rpmdrake. bug. 14) they had bad signatures. when yo removed and redownloaded you got ones with new signatures? 15) crashes are never supposed to happen. crash recovery on the other hand... yes. 16) remove old firebird rpm and get firefox rpm. 17) update your kernel and hotplug version. better yet, just do a clean install. 18) opengl is probably not working. get opengl support for your vid card. 19) Press ctrl+Alt+esc in KDE same effect. 20) because you haven't installed any? haven't upgraded properly? works with my pc. urpmi --auto-install or whatever wasn't a terribly good choice for this 9.2 -> 10.0 upgrade.
  19. it does work well with tv cards but I'dd advise against buying one of these if you have a K7S5A motherboard. I've been having "issues" since kernel 2.6 upgrade.
  20. as for software I'd go w/ tvtime. it's resource hungry but damn good at what it does. Zapping is also a good tv viewer for gnome, and KDETV and good one for KDE. tvtime is independent and work without either gtk or qt installed. also in my /etc/modprobe.preload file i have bttv in there. that modulee is for my ati tv wonder ve
  21. it's from KDE-look.org and it's called active heart there is a matching style as well
  22. how about trying /dev/hda10 /www ext3 exec 1 2 and seeing if that works. If not change back to original
×
×
  • Create New...