martouf

Jabird: they're both right. Maillion is right because at one time AT&T vigorously defended its Unix and related trademarks. Hashing up the name was a way to make the reference but without having to add the symbol and "Unix is a trademark of AT&T" footnote. Tokes is right because collectively referring to all the various flavors of 'nix' with a wildcard is simple and efficient. Xenix AIX HP/UX IRIX Linux System V Unix BSD Unix . . . and so on.

there's three different video drivers to sample: 1. VESA 2. Nvidia non-proprietary (as in LibreSoftware) 3. Nvidia proprietary (as in direct from Nvidia and licensed) which one are you using now? any hints of video driver problems in the log file produced by "X -probeonly :1" ?

maybe you're experiencing the nostalgia of the 1024 cylinder barrier? that is, the boot partition must occur before and be completely contained within the first 1024 cylinders of the disk.

oldspiceap: actually, the unpacking and compilation of a tarball is best done as a regular user. root privileges should be needed only at install time. for instance: (as regular user) $ ftp tarballhost.org $ tar xzvf tarball.gz $ cd tarballdir $ ./configure $ make $ make -n install (rinse and repeat if you're not happy with the results or the destination for the install or the included program options) . . (now that you're happy with it all) $ su Password: seekret # make install # exit $ tarballname

tip o'the hat to blackpage for the documentary answer a more concise and concrete answer to "what does strip do?" is it strips out all helpful debugging information embedded in the program image. If all your programs are bug-free, then you can go ahead and strip them all. 8) Either that, or when you are certain you won't be doing a postmortem on the program even if it does crash, then you strip it.

you're going to need to run 'xev' to figure out the button numbers for the special buttons you want to use. then you're going to need to put the button numbers into a ZAxisMapping option in the proper InputDevice stanza in XF86Config. Reverse the button numbers if the motion is backwards.

the only temporal references I find for the problem you mention are 'August 2002' and driver v0.12b (December 2002). BTW, the most recent driver is 0.15rc2 (July 28 2004). The best answer to your question is the All-Purpose Technical Answer: It Depends. use your wlan card, abuse your network bandwidth -- and if it doesn't hang, then you have your answer! 8)

what's your blocksize and blockcount? try adding 'bs=1k count=1440' parameters. IOW, try "dd if=/tmp/SUSE.img of=/dev/fd0 bs=1k count=1440" oh, and since you're writing directly to the device: do not mount it beforehand. umounting a mounted filesystem causes stuff to be written to the filesystem. you don't want this. you want only the bytes from the SUSE.img file written to the floppy disk and none other.

your problem doesn't strike me as Something Which Can Be Fixed By Reinstallation. Sorry. can you be certain there aren't any error messages hinting at the problem on vty10 (type CTRL-ALT-F10 to check on this while X is running)? If there aren't any messages on vty10, then login on vty2 and see if you can run 'xkbreset'. <-- no, scratch that .. you'd need to be typing this in a konsole! Grrr.. all the things I'm thinking to try are things needed a freaking working keyboard. ;( Can you not even type anything in the KDE/Start -> "Run Command" ??

1. what happens if you try to load from "/tmp/cdrom" instead of Local CDROM? 2. I didn't encounter any articles online from Red Hat or elsewhere about a string length limitation in the 'ks' parameter. I did encounter, however, articles about folks having troubles after having used a Windows editor (not vi) on the ks.cfg file. check with 'cat -t -v ks.cfg' and ensure there aren't a bunch of "^M" (CR, ASCII 13) chars at line ends. 3. the logic of the %post section appears to me to not prompt for a CD-ROM if the mounted CDROM at the time of %post has a ks.cfg file on it. Are the 3 CDROMs constructed so that the 3rd one (if not also the 2nd one) does not have a ks.cfg file on it? and the 4th (vendor) CD does have a ks.cfg on it? It's been a long week, so my thinking is a bit fuzzy. Wish I could put my 'finger' right on the problem.

whatever you do, DO NOT do the 'dd' command suggested by Laffen unless you really want to trash much more than the MBR. 'bs=1000 count=1000' means 1000*1000 bytes written -- and the MBR just by itself is 512 bytes. You'll trash the MBR, the partition table and the first part of the filesystem.

oh. ok! didn't know there was such a thing, other than the full version of the included-with-Windows defragger. The whole disable VM, reboot, defrag, reenable VM, reboot is a workaround for the pagefile problem.

ok. Is the CDROM drive the only device on the IDE bus? If so, have you tried to do without the jumper? I recall in the past HD and CDROMs which would work only without the jumper if they are the only device on the bus.

you might want to start by getting a copy of one of the Asia-Pacific focused distros like TurboLinux (see www.turbolinux.com for more info).

no, what you're digging into sure isn't "basic stuff". you're sailing near the edge of the map where it says: "dragons be here" 8) while I'll grant you may not understand why I'm asking this question it may help lead to a solution: are your CDROMs all SCSI attached and not ATAPI devices connected via an IDE bus?

avoid starting your partitioning job when a thunderstorm is approaching Know the runtime of your UPS and plan accordingly. You can live more dangerously if you have saved a full image of your HD first. jimf43: I don't understand why you recommend more than the included-with-Windows defragger? isn't it enough? true, it may take running it two or three times before the filesystem is fully compacted. In fact, if you've got plenty of RAM, you may need to disable virtual mem, reboot, defrag, and reenable virtual mem to effect full compaction.

right, the keyboard isn't really dead if it seems dead in the GUI but works just fine in the virtual terminal (CTRL-ALT-F2). 1. it seems the mixer settings aren't getting saved or you're leaving the mic unmuted as a default (which is probably a Bad Thing) after setting your sound system the way you like it (go ahead and mute the mic), run as root 'alsactl store' and your setting should be saved in /etc/asound.state .. make sure the permission bits are -rw-r--r-- with 'ls -l /etc/asound.state'. 2. the keyboard quitting on you after a power mode change speaks to me of the keyboard input getting captured by a Power Monitor Applet in the toolbar (caused by a window/app focus change). right after you login, can you right-click the power monitor applet and tell it to quit? OTOH, try booting with the kernel parameter 'apm=no' and see what happens when you cause a power mode change.

(anyone recognize the uname output?) My guess is you're running a Debian derived distro. Any Debian experts out there able to direct ULIKEIT to the proper text mode sound system configuration tool? If your distro has 'sndconfig', then give it a try. Otherwise, look for 'alsaconf'. Beyond those pointers, I dunno. If my Knoppix set-up suggests different info, then I'll post it here.

try running 'strip' on the xmms executable, and then compare sizes again.

ok. don't worry about not having an analog cable. I brought up the two inputs idea only because I've experienced a slap-the-forehead moment once when I was messing around with display adjustments and thought the LCD panel had gone dead. It wasn't until I sat back to review the situation that I noticed the LCD panel had switched to the unattached analog input. :x If I understand your situation correctly, you've just installed MDK and you're having display problems? There's nothing on the MDK system which needs to be saved because you haven't had a chance yet to make something to save with it? In that case, what's probably going to be easiest for you is to rerun the install process but select the display driver manually when you are afforded the opportunity. Can you tell me/us more about your system (specifically about the display card)?

one of my systems has an LCD connected to a Radeon 9600TX using the DVI output connector, so yes, Linux is compatible with DVI output in that sense. sounds like you don't have the correct display driver selected for your system. Either that, or your LCD display is getting confused at the moment the display briefly blanks when it switches from text mode to GUI mode. Does your LCD have two inputs? Does it automagically select its input? Can you manually adjust the input?

hey, relax! I'm not just picking on you. danleff got me started on the "just what are you paying for?" by saying Linux addicts don't like talking about Linspire becau$e it co$t$ a few buck$. It's all danleff's fault, see? 8) 'course you can turn the DefRef thing back on me and point out when you send money to Microsoft, you're not paying for software either. You're paying for a license to use the copy you have.

is your window manager really KDE (as suggested by you saying you're having trouble opening a konsole)? that's weird. your keyboard input is going somewhere other than the newly opened xterm/shell/konsole.. hmm... does the keyboard seem OK if you try to check on your system from a virtual terminal? that is, with X Windows running, type CTRL-ALT-F2 to pull up tty2 and log in. (to return to X, type ALT-F7)

if the game runs OK under winex/cedega, then: yes the MP game needs network connectivity to be MP and the network is blind to which OS you're running.

DefRef: you're not paying for the Linux OS or the software. You're paying for the delivery and maintenance of the OS, software, software repository, packaging and advertising, etc. Everything except the OS and the software - it's free (as in unshackled).