chef_kunal

did it sound nice?

Maybe theres water in your cpu

:lol: :lol: :lol: :lol: :lol:

Ok sorry

I Mean no i havent seen this before

ok the damn thing crashed and now i turned off renderaccel and now im waiting and using

which brand nvidia ti4200 are you using?

what error messages are you getting?

show the contents of /var/log/XFree86.0.log here so we have more info?

after your linux crashes for the first time start linux in test mode by typing linux 3 at the lilo prompt. If you get the graphocal lilo the press escape to get the lilo prompt.

then log in as root and then get that output.

while youre at it use drakxconf to configure your X again so you can start in grapphics mode again and post here.

u may have to remove the Nvidia drivers using rpm -e

anyway see if that output helps u

:?: more and more wierd.

Ok i changed the pernmissions to 666

all shit happened. X wouldnt start giving a log message of too many input devices.

Ok then i restarted

now i have

Section "Device"

Identifier "device1"

VendorName "nVidia Corporation"

BoardName "NVIDIA GeForce2 DDR (generic)"

Driver "nvidia"

#Option "DPMS"

#Option "nvagp" ""

Option "NoLogo" "on"

Option "PageFlip" "on"

Option "HWCursor" "on"

Option "RenderAccel" "on"

Option "DigitalVibrance" "20"

EndSection

and also........

 

[root@chefsbox chefkunal]# ls -al /dev/nv*

crw------- 1 chefkunal root 195, 0 Jan 1 1970 /dev/nvidia0

crw------- 1 chefkunal root 195, 255 Jan 1 1970 /dev/nvidiactl

--

]

so what gives?

my kde is not crashing. hope it stays that way!!! :lol:

so i guess youre right....

well just as long as it works.....

Firstly, overclocking ur geforce2 is not a good idea.

I did overclock it and that was for a small time just to test and that was it. I wasnt running it with the overclock on except this one time nd that was with windows.

I am using the 4191 drivers with render accel on.

by default, /dev/nvidia* has 666 mode

I actually didnt check the mode in /dev so i dont know what mode was there before i 777'ed it. Also i didnt try 666 at all!!!

Let me see if it wirks as welland ill post it here.

I doubt the mode change has anything to do with the lockups.

Well once i had this prob with ut2003 crashing at the splash screen.

Then i did the same thing. and ut2003 worked. thats what led me to think of this. While i may share your doubt the point is that it worked. Of course in this case also UT2003 did run fine when i was in root. That too me at least strongly suggest that its a permission problem. also considering that all i did was change the permisison to 777 and didnt do anything except login again, would suggest it as a permission problem , wouldnt it? Any way while i can tinker im no expert!!!

666 sounds more restrictive and yes i should try that out and ill post my experiebce here.

try this.

1. connect the hardrive as master on the irst ide channel

2. connect the cdrw as master on the second ide chqannel

the prompt

What CDs I have? I haven't ever seen that prompt.

EDIT: Alright, checked the manual, that prompt doesn't get a chance to come up.

will only come up if you choose an exper rther than recommended install right at the start of the instaqll.

hope this helps

ok lets hope it works. will try it

one other thing you could do..... this should definetly work..

do an expert install.

Then when it asks you what cds you got just say no to the second two cds.

See if the install goes smoothly then.

also any packages you can install from the other two cds later when you have a running system by adding them to your urpmi sources.

Think thatll work?

well you could still check them. You could be the one guy who got bad cds??.....

why dont you check the md5 sums for your cds?

there are a number of articles here on how to do this.

Then if your cds are ok you can plan your next action.

hmmm...

what di you umm... do to it?

well just as an after note - this is what i did to get my scanner to work in mdk 9

snapscan.conf:

------------------------------------------------------------------------------------------------

# If not automatically found from above, then you may manually specify

# a device name.

# For USB devices, make sure that the name contains 'usb' somewhere, as in

# '/dev/usbscanner' or '/dev/usb/scanner0'. Do not use a link

# from /dev/scanner to your USB device.

# For SCSI, use the generic device (e.g. /dev/sg0 in Linux).

#/dev/sg0

/dev/usb/scanner0

# Change to the fully qualified filename of your firmware file, if

# firmware upload is needed by the scanner

firmware /etc/sane.d/U176V042.BIN

-------------------------------------------------------------------------------------------------------

************then i changed dll.conf:

dll.conf----------

-------------------------------------------------------------------------------------------------------

-# enable the next line if you want to allow access through the network:

net

/dev/usb/scanner0

snapscan

-------------------------------------------------------------------------------------------------------

and now it just worked with the original mdk 9.0 sane--no reinstalling or recompiling from tar.gz

my guess is that your partitions are messed up

i could be wrong but you could try checking the disk with fdisk and use v to verify the partition table.

try step by step to debug your problem....

First try to burn a cd with cdrecord. also with a new cd

then lets see the output. if the same message comes then well you have to post details of your system.

ok good that it works

now you can eat your cookie

ok one last guess try passing idebus=66 or idebus=100.

with the appropriate bios settings

maybe that works???????????

http://www.club-nihil.net/mub/viewtopic.ph...7310&highlight=

http://www.mandrakeusers.org/viewtopic.php...1926&highlight=

I was thinking this was the nature of his problem.

And of course you could be right. It could be a problem with that, but if on selecting logout from the kde menu what would happen is..(IMHO)

1. KDE does its bit closoing files whatever,

2. kde exits and then X

3. hes back to the shell or to his kdm /gdm.

on saying init 3 or shutdown -r now etc. he will never get any kde related error messages. the pc will do a straight shutdown or init 3 killing all the processes it has to. If the error was with kde or whatever Wm hes using youll never know with init 3 or shutdown.

by the way to logout from a terminal you use 'logout'. xterm konsole etc are terminal emulators not terminals. Try saying logout in an xterm and youll see what i meant from my first reply.

Also to get back to the topic, ethrbunny try this.....

when you start the pc and you get a mouse pointer such as when kde starts up press ctrl-alt-bkspc to kill it. then login to gnome or black box or something. then im sure youll be able to logoff.

anyway i hope that helps a bit

try passing mem=nopentium?

just a try

also try passing noapic to the kernel.

you could try loading failsafe cmos defaults and then booting.

Try disabling one of the cd or dvd on the bios. Also ideally you should have hdd + dvd and then hdd + cdrw on the primary and secondary ide channels respectively.

Try a new bios?

See this....http://www.viaarena.com/?PageID=88 (ide drivers issue 11)

but actually etherbunny .....

you havent told us about what window manager ure using, if its gnome or kde or what? and also if youre autologing in or doing a login from kdm or gdm.

maybe u wont have that problem if you try loging in from gnome?

let me know

actually that doesnt solve any problem about why he cant shutdown or logoff.

you cannot logof from an xterm.

but ctrl-alt- bkspc then 'exit' should log u off.

or

8.86 secs

actaully this happens in gnome also

see my first post

seems to be a kde problem because i dont get his with blackbox. and also my problem is reproducible.

also any body overclocked their gf2's? before they had this prob?

hi.

i have thougt about what you said and actaully the newest thing on the pc is my 80gb harddrive thqat i was first using at udma5 using hdparm -d1X69m16. My tablet is really old . i have been using it or the past two years and most of the time it quietly lies in one place without using. Although in the case of a system hang it still works. Just like the mouse.

Is there any thing else someone can think of?