kristi

I like the sound of that - Shuttle mobo with MODULE-X!!!!!!!

Sellis, what's your mobo and sensor chip? Yeah, this is one of the reasons that I don't mess with much other than the CPU temp - I check the voltages (rarely) in the bios on the "health" screen. Onec you determine that a PS has good voltages, they are unlikely to change. That is, of course, ignoring the ps, whose fans stopped, and put out pretty clouds of acrid smoke - voltages were still good, though, right up till the last sec, then It recycled the mobo and tried to go again. I've also had problems with fans on sensors, where the fan trips the sensor, but if I look at the fan it is doing quite nicely. Some fans also require a divider of 2 or 4 or something to read accurately - this is determined by the highly reliable guessometric system. Some boards I have had (mention no names had terrible (low) voltage regulation - couldn't OC the memory worth a damn. This mobo is tops, though - takes abuse and keeps on ticking! Kristi

Just ignore it. You'll notice that you can change the label of each - just change it to what's right. Some windows sensor proggies used to just say "sensor1, sensor2,..." I think they are right for this mobo, but my old kts5a or whatever the heck it was, was reversed. It's getting hard not to look at the motherboard pile over at the local Micro Center when I wander over there. I'd love to go 64bit and sata, but I need it like a hole in the head, but TOYS!!!!!!!!!

Hey John, big congrats on the 70!!! :D Kristi

Thanks for the feedback scarecrow!!! - glad you got it going!!!!! :D I think Adam uses that dkms thing. - I'll try to learn it eventually, but my head is a bit saturated at the moment

devries okay! cool!!! :D Odly I do not cut and paste or add those to any file yet mine seems to work correctly - I wonder why?????????? EDIT: duh! - oh, because it automatically puts the both at the bottom of /etc/sysconfig/lm_sensors ! there is a small bold note at the bottom of your post, but I don't know how to view your desktop... waaaaaaaa :D Kristi EDIT - oh, I got it - way out at the forum view there's a paperclip by the topic - is that the only way to get it? 70's huh!!! what are you cooling with and what's your room ambient? mine is running 43C/109F at the moment. The room is 78F. Spring is here! I have a xp2600Barton core with a zallman all copper on top of it. you say "system monitor (cpu, ram swap)" - what program is that - can I run it on kde? Nice looking taskbar! :D

yeah, those 2 were often reversed in windows monitors I used. Just swap them around! :D Kristi

This is very interesting to me - I have a "4" button mouse - Logitech optical mouseman with the usual stuff on top and one button on the left side. I always have Mandriva set it up as MS/Explorer/PS2, and I get: Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "ExplorerPS/2" Option "Device" "/dev/mouse" Option "ZAxisMapping" "6 7" EndSection This results in a wheel that scrolls sideways, so I just change it to Option "ZAxisMapping" "4 5" and then the wheel scrolls perfectly (vertically), and the wheel also works perfectly as a switch to set scroll (where you move the mouse and it scrolls wherever you go). The left and right top buttons have always worked perfectly as in windows. So I am reading this trying to figure a way to add the use of the left side button. I seem to recall that a real MS Explorer has 2 left side buttons and 1 right side button (?) Would this mean that the correct Buttons value for me would be "5"? I'm off to bed but I have googled and gotten some info and will be pondering this tomorrow. Nice post!!! :D Kristi EDIT: interesting! : xmodmap -pp shows There are 5 pointer buttons defined. Physical Button Button Code 1 1 2 2 3 3 4 4 5 5 /etc/X11/xinit.d/mouse_buttons contains xmodmap -e 'pointer = 1 2 3 6 7 4 5' --------------------------------------- further EDIT experimentation no button option or button=5 & Zaxis= 4 5 => vertical scroll and mouse button select ,,,ditto,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, & Zaxis-6 7 => horiz scroll (I forget if mouse button selects button=7 & Zaxis= 4 5 => horiz scroll ...ditto..... & Zaxis=6 7 => vert scroll ------------------------- It would apear that by my selecting PS2/other/MS Explorer on install, I get the "1236745" string. However, it is apparent that it also counte the number of buttons I actually have and gives me "5". Were you actually able to get the side buttons to DO anything.? I think you were only talking about trying to get whell-press select... (?) Kristi Oh, okay, I see ...........

Ahhh - YES, exactly!!! Thanks! Kristi

google search on "asus p4t sensor chip" yields: AS99127F http://mbm.livewiredev.com/comp/asus.html

Theo, very nice desktop!!!!!!! :D here's mine: My Desktop

Thanks for that one - I am very much a newbie when it comes to knowing about commands like that!!! :D Kristi

This is a different branch of "sensors". /etc/sensors.conf is the config file for sensord, a program which you will find running in root, and which dumps great gobs of info (unless you have massaged sensors.conf) to the kernel logs. From the top of /etc/sensors.conf: It is a different critter. In your case, I do not think you need any of the info from my post. But your post opens the other door to the other way to get sensor info, and to get it in a way that it can be logged for later use. Here, too, it is to notice that if you are using the system logs ( /var/log/kernel/<whatever> ) to monitor any output OTHER than that from sensorsd, you may want to check all the lines in /etc/sensors.conf, and thus minimize the load on the logs, not for the sake of the system, but for the sake of finding other info you may be looking for (like the firewall guarddog). ksensors, kcupload, and knetload do not use the system logs. On a completely different note, Theo, I *love* xpenguins!!!!!!! Thanks for your note! Kristi

SENSORS: after installing lm_sensors with MMC go to a ROOT console and do "sensors-detect". [i have a Shuttle AN35N/Ultra, Nforce 2, 32bit mobo with an IT8712 sensor chip] It will give a bunch of info and then say We can start with probing for (PCI) I2C or SMBus adapters. You do not need any special privileges for this. Do you want to probe now? (YES/no): The word in caps is the default of what it will do if you whang on the enter key. Hit enter. # ..... more words, then We will now try to load each adapter module in turn. Load `i2c-nforce2' (say NO if built into your kernel)? (YES/no): Hit enter # ....... more words then To continue, we need module `i2c-dev' to be loaded. If it is built-in into your kernel, you can safely skip this. i2c-dev is not loaded. Do you want to load it now? (YES/no): Hit enter. # ......more words then Next adapter: SMBus nForce2 adapter at 5100 Do you want to scan it? (YES/no/selectively): type no and hit enter. (I know my sensors are not on that port) # ...more words then Next adapter: SMBus nForce2 adapter at 5000 Do you want to scan it? (YES/no/selectively): type no and hit enter. (I know my sensors are not on that port) # ...more words then Next adapter: cx88[0] Do you want to scan it? (YES/no/selectively): type no and hit enter (( god no - that's my TV!!! you definitely don't want my TV!!!))((are you paying attention?). # ...more words then Some chips are also accessible through the ISA bus. ISA probes are typically a bit more dangerous, as we have to write to I/O ports to do this. This is usually safe though. Do you want to scan the ISA bus? (YES/no): hit enter to accept this since I know the IT8712 chip is on the ISA bus. # ...more words then Some Super I/O chips may also contain sensors. Super I/O probes are typically a bit more dangerous, as we have to write to I/O ports to do this. This is usually safe though. Do you want to scan for Super I/O sensors? (YES/no): type no and hit enter UNLESS you know that your sensor chip is connected to the super sensors (mine are not). # ...more words then Now follows a summary of the probes I have just done. Just press ENTER to continue: hit enter and you will get Driver `it87' (should be inserted): Detects correctly: * ISA bus address 0x0290 (Busdriver `i2c-isa') Chip `ITE IT8705F / IT8712F / SiS 950' (confidence: 8) I will now generate the commands needed to load the I2C modules. Sometimes, a chip is available both through the ISA bus and an I2C bus. ISA bus access is faster, but you need to load an additional driver module for it. If you have the choice, do you want to use the ISA bus or the I2C/SMBus (ISA/smbus)? here I hit enter because I know mine is on the ISA bus because it just told me so! Now you get To make the sensors modules behave correctly, add these lines to /etc/modules.conf: #----cut here---- # I2C module options alias char-major-89 i2c-dev #----cut here---- To load everything that is needed, add this to some /etc/rc* file: #----cut here---- # I2C adapter drivers modprobe i2c-isa # I2C chip drivers modprobe it87 # sleep 2 # optional /usr/local/bin/sensors -s # recommended #----cut here---- WARNING! If you have some things built into your kernel, the list above will contain too many modules. Skip the appropriate ones! You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until it's done. Do you want to generate /etc/sysconfig/lm_sensors? (YES/no) hit enter and ignore the lines that tell you to cut and paste. #reboot. #with a root konqueror, look in /usr/bin and copy ksensors, kcpuload and knetload into your /home/<user>/.kde/Autostart folder. then either reboot again to start them, or just click on them. knetload(2) and kcpuload(1) will put a 3 cute little graphs into your system tray (if you don't have one, right click on the taskbar, Add, Applet, system tray.) # ksensors icon looks like a film thing - right click on it, choose Configure, choose it8712 sensors, highlight CPU temp, click the Dock tab, check the "visible" box, click apply, click close. It now displays your CPUtemp continuously on your taskbar. This was intended to just help you get started. Have fun. Any comments or suggestions, PM me Kristi EDIT - another nice sersor - use MCC to install kdeaddons. right click your taskbar and choose add, applet, and click on system monitor (shows cpu, mem, swap in vert or horiz bars. (thanks devries!)

=> urpmi kernel-source & uname -r (I think it's to describe). Anyway, great work kristi <{POST_SNAPBACK}> not sure what you're saying... typo maybe? Right! 1. load the kernel source, and 2. check the name of the kernel you're using and that is the info I would need - note, both are the same in the last example. THANKS!!!

Thanks - next year I'll ask you how to do it, but I'm not brain ready at the moment... Kristi

I think now you can easily guess the mistakes I made when I was early on at Mandrivia!!!!!!!!!!!!! glad it worked!!! Kristi

noobs: Have you checked MUB forum Frequently Asked Questions and How To's, and Tips and Tricks ? Use MUB search if you can. You'll save yourself time and frustration. Read tips and faqs - there's a wealth of info in there!!!!!!! If you're reading my stuff, don't assume I didn't make a typo!!! - ask me PM. GET THE DISTRO : download 2005, or whatever iso, and install and burn it to a CD - Check the MD5SUMs - I always do this under Linux with k3b which has a nice sum checker. I always use Azureus to download because you can restart a download. Bittorrent and Azureus instructions are elsewhere. MANDRIVA INSTALL : Stick the CD or DVD in and boot from it and install Mandriva. Take the defaults unless you know what you are doing. I recommend security Standard, not High. Don't forget to configure your mouse. Also, when configuring your video, choose monitor VENDOR and pick your monitor vendor and then pick the model you have, then pick the res you want. At the end, it will tell you to reboot (don't forget to take your install disk out for the boot. put it right back in after it boots. This will boot to a level 3 command line and ask you for a logon. Login with root, enter your password, and type kde and hit enter. This will take you to a root kde GUI screen . EASYURPMI : Use firefox or konqueror (in menu, internet) to access http://www.mandrivausers.org/easyurpmi/ choose Mandriva version 2005 and select your architecture (usually i586) CLICK ON THE BUTTON that says "click toproceed to step 2". Choose the 6 mirrors that you want and make sure to put a checkmark by each if it doesn't do so automatically. CLICK ON THE BUTTON that says "click to proceed to step 3". A whole bunch (6) of lines will appear in the black background. Copy them all to a root console. They will start processing. Here you will learn that some mirrors are much faster than others. Don't forget to hit enter so the last line will process. GET WHAT YOU WANT : go to MCC (menu,system,configuration,Configure your Computer) It will dump you in software management which is where you want to be. [i find Kaffeine's desire to start whenever I stick in a CD and stay running when it's done to be damn anoying so I delete it. Others here love it! If you choose to delete it, click on the top right icon to "uninstall software packages", search on the name kaffein, select what you want to remove, and click remove. When that is done, click Quit and it will bounce you back to MCC. GET STUFF: click the top left icon to "install software packages" search on: source ...and check the 2.6.11.6 kernel source (or whichever one you want.) sensors ...and check lm_sensors and ksensors (often a little box will pop up saying it needs something additional - click OK) load ...and check kcpuload and knetload tvtime ...and check it xine ...and check 99ui libdvdcss ...and check it mplayer ...and check the plugin. then check the matching gui (the rest will be auto checked.) pan ...and check it (it's 3/4 of the way down the list)(nice NNTP newsreader. klibido ...if you need to use nzb files archive ...and check karchive and parchive2 thunderbird ...and check the one you want - usually the top one. games ...I check kdegames v3 [grab whatever else you think you will want] click Install (go have coffee)(mmm - good idea!!!) GET NVIDIA DRIVER: While that is chugging, use your browser of choice to go to http://www.nvidia.com/content/drivers/drivers.asp choose Graphics Driver, GeForce, Linux IA32 (or whatever, and click GO. Part way down the next page grab NVIDIA-Linux-x86-1.0-7174-pkg1.run I save mine in a user folder cause I'm always reinstalling somthing. (7174ONLY - in a root konqueror (you ARE in root, remember!!!), right click on the NVIDIA module, select properties and check "executable". For some reason, this one came through w/o that checked.) I then copy that to the root folder. [a root konqueror is easily made in user : drag konqueror from menu internet browsers to the task bar. Right click it and choose properties. choose the Application tab and make the command look like kdesu konqueror Go back to the first tab and click on the icon and choose a big red X or something so you will never forget this is a root konqueror.] After MCC installs are done, logout of root : menu, logout. this will drop you to a prompt. You are still in root, but no GUI! neato!!! Type ls (thats LS (phonetically: ell ess) in small letters) . Your NVIDIA-Linux-x86-1.0-7174-pkg1.run will be sitting there along with a tad of other stuffs. INSTALL NVIDIA DRIVER : This assumes you are already at a root prompt and the NVIDIA driver is also in root and has been set executable!!!!! type sh NVIDIA-Linux-x86-1.0-7174-pkg1.run and hit enter. on the first prompt, hit left arrow to choose accept and hit enter. hit enter at the next two questions. It will slowly build the driver. it will more rapidly build another module. It will then tell you the NVIDIA driver is installed - hit OK [guote] if you have an eror, type "rpm -qa | grep kernel" without the quotes, and ask for help and give the answer to that command. but if OK, then Follow these directions exactly - I did actually check them for typos 1 ) Change the line in /etc/inittab the one that says: id:3:initdefault: ...make it say: id:5:initdefault: ...this will cause you to boot next time to a level 5 which is defined as a GUI (KDE) 2 ) ADD a line to /etc/modprobe.preload that says nothing but nvidia 3 ) Change /etc/X11/xorg.conf where it says "nv" to: "nvidia" (keep the quotes that are there in the file) In the mouse section, change "6 7" to "4 5" . SENSORS: for a basic intro go to https://mandrivausers.org/index.php?showtopic=25579 "BASIC: Sensors - a very simple example. in MUB Tips and Tricks If no joy, post a specific question to MUB! :D Kristi ...(don't you just love that line: "kernel: nvidia: module license 'NVIDIA' taints kernel." (PM me for changes or additions to this)

Follow these directions exactly - I did actually check them for typos 1 ) I presume you changed the line in /etc/inittab the one that says: id:3:initdefault: ...make it say: id:5:initdefault: 2 ) I presume you ADDED a line to /etc/modprobe.preload that says nothing but nvidia 3 ) I presume you changed /etc/X11/xorg.conf where it says "nv" to: "nvidia" (keep the quotes that are there in the file) If no joy, get back to me! :D Kristi (don't you just love that line: "kernel: nvidia: module license 'NVIDIA' taints kernel."

which begs the question that since the nvidia drivers are built with gcc3.x, how do you get it to jive with the new kernels - I told it to go ahead on the shell install, but it was not successful. This is not an important question for me now cause I'm back on 2005 for now, but as a learning question.... and I was using 2.6.11.8 kern and source. (wayward readers, the 2.6.11.8 kern is not compatable with 2005, at least that was my experience.) tia!!! Kristi

type kde and hit enter.

hey devries, good to see you back again, I missed you! :D Kristi

He reported a few posts ago: yes login as root.. says' no such command' This means the NVIDIA* file is almost certainly not flagged as executable. I figured he had a typo in his "command" - still do. Huge appologies to scarecrow :woops: I finally got my lazy butt around to downloading it and guess what... :woops: :woops: :woops: sorry scarecrow! I blew it. Kristi

Agreed - definitely avoid KDE3.4 Be aware though that once you install 2005, you have the option of updating that system - menu,system,configuration,packaging,MandrakeLinuxUpdate. Take a look at it and decide if, and what you want to. As you probably know, I've been hoping back and forth between 2005 and cooker2006 - mostly just playing, but The last mass of updates failed to fix the 2006 printer prob so I'm back on 2005, and this time I updated everything, and it doesn't seem to have killed the system indeed, it seems to have speeded it up a tad. Just one more thing to be aware of, and something that is very Mandriva specific! :D Have fun!!! Kristi EDIT: by the way, hopping around and asking all sorts of questions like this is precisely what newbies, and not so newbies should do, imnsho!!! Go for it!!!!!

Holy moleys!!!!! That's intense!!! I figured that one would be with us for a while... Great work!!!!! :D Kristi