scoopy
-
Posts
2302 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by scoopy
-
-
Hope they do well with it. I wonder how they can out do OO tho? Could only mean good things for Linux's future.
-
I am curious now...
hbob said he had kate open and used it at least twice before in this thread... which means it is installed... right? Why now won't it open as root user? Is this a sign there are deeper problems here?
-
.src.rpm's are used to make .rpms --- so, no, you don't need them.
A little trick to avoid the typos would be to type in
# urpmi apo
and then hit the tab key to automatically fill in the rest of the filename.
PS: I like newbie questions... as they are the only ones I can answer. :D
-
IF you would just like to be running the newer gnome 2.6, I would just wait a few days as I am sure somebody will build the rpms that will be much easier to install. Compiling a desktop environment can become quite a project for a "newbie".
IF it is for a learning experience, then I would start with compiling a smaller application... maybe the latest k3b ?
-
how do you set your audigy to get XMMS working properly?
Not sure if this is what your looking for, but,
there seems to be a bug...
http://www.mandrakeusers.org/index.php?showtopic=12260
I just made a icon for xmms on my desktop using command xmms (the one in menu uses soundwrapper xmms instead ).
-
What I do is look up this file @ rpmfind.net to see what package it belongs to.
Looking up libxvidcore.so.2 tells me it belongs to xvidcore-0.9.2-0.1.rh80.fr.i386.rpm --- but this aint' gonna do for us in MDK land.
So in this case, seeing the program you want to install belongs to PLF, I would add PLF's source to your "media sources" and then use urpmi to install.
You can use this to help you add sources:
-
To edit things in KDE with KATE as ROOT:
open up a terminal
su <enter root password> kate
you will now be able to edit and save files as root user.
-
kernel headers = kernel-source
you can install same way:
rpm -ivh kernel-2.6.3.7mdk-1-1mdk.i586.rpm
-
Well, it passed memtest86.
and while it was running, I was thinking, it could just be the new game we installed thats causing these latest crashes. I don't remember doing anything else the last couple of days when it happened.
Will just have to keep an eye on this for a while... as I burn and backup that stuff on the USB drive. (only got like 38 gigs out of 40 gigs capacity of stuff)
Meanwhile, I keep cruising that highway of insanity.
-
NOTE: The kernel package is not going to show up via the GUI software installer. Although kernel-source will.
From re-reading this thread and also your other thread in this forum, I think I may see what is happening here ???
You are looking to install a kernel package that is currently only listed in MDK 10 sources and you are most likely running a prior version and have sources configured for the prior version, which does not have this kernel available there and why your not getting it.
So instead of configuring a 10 source for an earlier version, I would just download the following and then install with rpm:
kernel-2.6.3.7mdk-1-1mdk.i586.rpm
kernel-source-2.6.3-7mdk.i586.rpm
Here's the commands:
cd RPMs (RPMs would be the folder I saved the files to) su <enter root password> rpm -ivh kernel-2.6.3.7mdk-1-1mdk.i586.rpm lilo
upon reboot, you should have a new entry to boot your new kernel (will look like "263" instead of "linux" if your booting lilo like me)
-
I was wrong... doesn't look like it was video related (unless this is a new problem now). Have since replaced the video card, but, although the sudden reboots have stopped, the sudden *poofs* have not.
What's new is that it gave me beep code that I found confirms a memory problem according to SOYO's website. So, moving on to Ix's step #2... I will be swapping ram and running memtest and see what that tells me.
I have also found that my USB drive is now unreadable by windows, tho Mandrake still sees all my files. Windows is reporting a CRC error #45 and that it is unformatted. Partition Magic sees it as formatted Fat32, but empty. So there... It works in Linux, but not in windows (na na na :P ) This seems like a possible side effect from the memory error ???
Any ideas how to go about fixing this CRC error?
-
probably a small bug... I don't think this script (or whatever it is) wasn't too polished as evident by the problems we have seen with CD number 4 listing that was included with the community release. You could try removing the 3 CDs (after making a note of how they are listed).
I have installed a couple apps from a "contrib" source (including gimp2... that is not on the 3 CD set) and I had to insert CD2 to complete the install. I unfortunately wasn't watching too closely... could of been a missing depend it wanted too?
-
Should be no need to be compiling a kernel. Why not post the results of the following two commands, and we can see where we are currently?
$ rpm -qa | grep kernel
(above will tell us what you have installed... kernel wise)
$ uname kernel -r
(this one tells us which kernel you have running)
-
NO... that was too easy. Although I get normal looking readings now and consider mine fixed as well. :D
But did you see that formula in the gkrellm docs to figure this out ?:
From: s - S1 t - T1 ------ = ------ S2 - S1 T2 - T1 T2 - T1 S2*T1 - S1*T2 t = s * ------- + ------------- S2 - S1 S2 - S1 So: T2 - T1 S2*T1 - S1*T2 factor = ------- offset = ------------- S2 - S1 S2 - S1
THANX Kjel Oslund
-
I believe we are getting to the root of this problem. Seems something just may be off a decimal point or two.
# cat /sys/devices/platform/i2c-0/0-6000/temp_input1 35800 # cat /sys/devices/platform/i2c-0/0-6000/temp_input2 53200 # cat /sys/devices/platform/i2c-0/0-6000/temp_input3 24500
and IF we change gkrellm to Celsius degrees.
temp1 358 temp2 532 temp3 245
which all looks like what sensors is reporting:
SYS Temp: +35.8°C CPU Temp: +53.2°C SBr Temp: +24.5°C
-
Well, it IS getting warmer outside...
Yes, it was quite nice today... but not hotter than hell.
-
Excellant reply Kjel Oslund, but seems I have one of those that hasn't been converted yet. This is on a SOYO K7VTA Pro socket A board.
$ sensors
via686a-isa-6000Adapter: ISA adapter
CPU core: +1.72 V (min = +1.99 V, max = +2.49 V) ALARM
+2.5V: +2.45 V (min = +2.24 V, max = +2.74 V)
I/O: +3.35 V (min = +2.95 V, max = +3.62 V)
+5V: +4.79 V (min = +4.47 V, max = +5.49 V)
+12V: +11.92 V (min = +10.79 V, max = +13.18 V)
CPU Fan: 6081 RPM (min = 3000 RPM, div = 2)
P/S Fan: 0 RPM (min = 3000 RPM, div = 2)
SYS Temp: +37.1°C (high = +45°C, hyst = +40°C)
CPU Temp: +56.6°C (high = +60°C, hyst = +55°C)
SBr Temp: +25.2°C (high = +65°C, hyst = +60°C)
(56 degrees C is more realistic, yes?)
chip "via686a-*"# VIA is very specific about the voltage sensor inputs, and our labels
# reflect what they say. Unfortunately, they are not at all specific about
# how to convert any of the register values to real units. Fortunately,
# Jonathan Yew <j.teh@iname.com> and Alex van Kaam <darkside@chello.nl>
# came through with some data for temp conversion and formulae for voltage
# conversion. However, the conversions should be regarded as our best guess-
# YMMV.
# On the Tyan S1598, the 2.5V sensor reads 0 and is not displayed in the BIOS.
# Linas Vepstas <linas@linas.org> reports that this sensor shows nothing of
# interest on the Abit KA7 (Athlon), and is also not displayed in the BIOS.
# Likewise, Johannes Drechsel-Burkhard <jdb@chello.at> reports that this
# sensor is unavailable in the BIOS of his MSI K7T Pro (Thunderbird). So,
# if you have one of these boards you may want to uncomment the 'ignore 2.5V'
# line below.
label "2.0V" "CPU core"
label "2.5V" "+2.5V"
#ignore "2.5V"
label "3.3V" "I/O"
label "5.0V" "+5V"
label "12V" "+12V"
label fan1 "CPU Fan"
label fan2 "P/S Fan"
# VIA suggests that temp3 is an internal temp sensor for the 686a. However,
# on the Tyan S1598 as well as the Abit KA7 (Athalon), the absolute values
# of the readings from that sensor are not valid. The readings do seem to
# correlate with temp changes, but the conversion factor may be quite
# different from temp1 & temp2 (as noted above, VIA has not provided
# conversion info). So, you may wish to 'ignore temp3'.
# Johannes Drechsel-Burkhard <jdb@chello.at> notes that on his MSI K7T Pro,
# temp1 is the CPU temp and temp2 is the SYS temp.
label temp1 "SYS Temp"
label temp2 "CPU Temp"
label temp3 "SBr Temp"
#ignore temp3
# Set your CPU core limits here. For the other voltage sensors, the
# built-in defaults should be fine.
set in0_min 2.0
set in0_max 2.5
# Set your temp limits here. Remember, 'tempX_over' is the temp at which an
# alarm is triggered, and 'tempX_hyst' is the temp at which an alarm turns off.
# Setting tempX_hyst to a few degrees below the corresponding tempX_over
# prevents an oscillation between alarm on and off states. This kind of
# oscillation is known as hyteresis, thus the name. (You typically get the
# most serious and troublesome hysteresis when a sensor triggers something to
# reduce the temp, thus creating a negative feedback loop. Even without that,
# we would still get some oscillation when the temp hovers around the limit
# due to noise.)
set temp1_hyst 40
set temp1_over 45
set temp2_hyst 55
set temp2_over 60
set temp3_hyst 60
set temp3_over 65
# You could set your fan limits too, but the defaults should be fine.
#set fan1_min 5000
#set fan2_min 5000
# For at least one Tyan S1598, the following corrections make the sensors
# readings more in-line with the BIOS readings on boot. Try these, and
# adjust as necessary.
#compute "2.0V" 1.02*@ , @/1.02
#compute "3.3V" 1.02*@ , @/1.02
#compute "5.0V" 1.009*@ , @/1.009
#compute "12V" 1.04*@ , @/1.04
(that was it for this chip)
-
Seems your drives are configured correctly (but post your fstab so we can double check) so I would guess to look elsewhere for the problem.
IF you open up "Software Media Manager" ( Kmenu --> Configuration --> Packaging )
are your CD's listed and enabled there? If no sources, you won't be able to update or have anything to install.
-
I thought Nero handled them all...
Hmmm, just an idea, try unzipping this file first. Sometimes you just never know what you'll find. :unsure:
-
nVidia card ?
su to root and reinstall driver.
OR, if that don't do the trick, try running XFdrake to reset the X server setup.
-
Everything else with gkrellm seems to be reporting correctly but the temperatures. From past releases / experiences, temp 2 should be somewhere around 131 degrees --- about what the bios reports during a restart.
The attached screenshot shows temps of 721, 1063, and 482 degrees fahrenheit, but there is no smoke emanating from my box ;)
Installed are gkrellm and lm_sensors. Ran sensors-detect and also added what it told me to in modules.conf. Running the 2.6.3.7 kernel.
I am thinking I need to set the "factor" and "offset" but how do I figure that out ???
tia
-
To tell them to get a clue on marketing and such, no one here knows... :P
I think they are trying to listen. That is why we now have a Community Edition and a Final Release. (AND we see how that worked out, did we not?)
A component would be like rpmdrake or rpmtools is to the product rpm.
-
Look what I just got in today's mail. :D
The image is sharper than I had imagined it would be --- but where the icey-blue background go ? Maybe it clashed with this grey shirt or something ? Looks good anyhoot.
PS: No promo/ discount (or press passes) used here either ;)
-
ditto... 9.2
Read up on this releases errata at http://www.mandrakelinux.com/en/92errata.php3 and be warned of the infamous LG problem, http://www.MandrakeUsers.org/index.php?showtopic=9559
and be sure to install those updates right away. Seems like a lot, but is worth it.
Anyone know anything about the 9.2.1 release to clubmembers? Any chance of snagging this one?
Sun joins forces with Microsoft
in Everything Linux
Posted
What's this mean for Star Office or Open Office, and what about JAVA ?
(PS: this story is dated April 02)