sinisterdomestik wrote: i wanted to start learnin how to keep that shit from happenin to me

I would suggest that not running shell scripts you get off IRC as root might be a good start.
etc might help you find out what's going on...

Error: Could not open /dev/nvidiactl because the permissions
are too resticitive. Please see the FREQUENTLY ASKED QUESTIONS
section of /usr/share/doc/NVIDIA_GLX-1.0/README for steps
to correct.

did the FAQ shed any light?

I would guess it's to do with

# Section "DRI"
# Mode 0666
# EndSection

Hi

I think this is harware related as I can can only reproduce it when using DRI to do hardware 3D acceleration.

I have a Dell Latitude C600 with a flat panel capable of 1024x768, but the graphics card ATI Rage Mobility M3 (8Mb) is supposedly capable of driving an external display at up to ...

colpaeko wrote:So could you give me the specs?

Sure! It's made by Billionton and uses the Texas Instruments OHCILynx chipset.
http://www.billionton.com/website/produ ... B1394T.htm

I got it from www.komplett.co.uk for 5 quid, but thy don't have it on their website anymore.


HTH


Huw

Does your linux box have USB2 ports? If not file transfer will be v.slow. Firewire cards are dirt cheap - probably a similar price to the cable..

Dunno what linux USB2 support is like. My iPod works great with a £5 PCMCIA firewire card on my laptop. I converted it from HFS+ to vfat with nothing ...

that will be due to the missing notail option.

Apparantly adding this increases the performance of reiserfs. However there's no mention of this here: http://www.namesys.com/mount-options.html

Huw

That's not supposed to be a personal attack. BTW. Just clarifying my 1st post which obviously wasn't clear enough

Huw

does "mount /mnt/hdc1" work?

It won't. This command uses the mount options in /etc/fstab. So it will try and use the umask option which IS NOT A VALID OPTION for Ext3 file systems.


try messing with fstab options, go slim at first (ditch the umask for now) and see if it works...

alternatively ...

george_mercury wrote: does anyone have an idea what is wrong?

EDIT: Yes:
This is not a valid mount option for Ext2/3 file systems.

HTH


Huw

I think I solved this by re-compiling vim with less agressive cflags.

GIve it a try...

anyway I have vim working with 2.6.7-mm2 and 2.6.7-mm4

opo wrote:shouldn't the cp command return an errormsg if it /boot wasn't mounted?

No because you almost certainly have a directory called /boot which is where you mount the boot partition.

get the patch from here:
http://www.bootsplash.de/files/bootspla ... 7-mm2.diff

cd to your /usr/src/linux-2.6.7-mm2 directory

patch -p1 </path/to/where/you/downloaded/the/patch


HTH


Huw

hmm

My clock runs too fast as well... Keyboard repeat is fine though.

Vim segfaults too!

Does it fail at the same point with all the kernel sources you've tried?

Can you compile a 2.6.5 kernel?

Hi

Glad you got it sorted! I agree it is strange that the gnome clock appears to keep time separately to the system clock, seems very illogical.


Huw

actually, just checking and unchecking the "use UTC" preference box in the gnome clock makes it update the time it shows to the system clock time.

Right. I've been experimenting some more,

Set hwclock as you did then use
hwclock --hctosys
to set system clock to the hardware clock (this will be the same as changing the hwclock time in the BIOS and then booting)

date now shows the new time, GNOME clock doesn't change until I remove the ...

arse. As you'd expect the clock init script syncs hwclock to system clock and vice versa on stop/start.

best to set the clock in the bios as you reboot.

sorry for all the hopeless suggestions, can't remember how exactly I sorted this problem out...

Err, shouldnt have to reboot, just restart the clock service.
/etc/init.d/clock restart

What you have done is wrong though:

if you set the system clock to local time the line in /etc/rc.conf should read local (as explained in the file)
# Set CLOCK to "UTC" if your system clock is set to UTC ...

yeah, read my post above your last one!

I think it's to do with whether your computer's hardware clock is set to GMT or BST and what CLOCK is set to in /etc/rc.conf.

scratch that. those two files are exactly the same.

Is your computers hardware clock set to GMT or localtime (ie BST)?

hmmm

mine is and I have the right time. Can you try altering the symlink to that?

the IP stuff in dmesg is logging from iptables, it's not a problem with your ethernet card.

right done some more playing.

My hwclock is set to UTC (ie GMT) using
hwclock --utc --set --date="5/4/04 12:26:00"

This can be confirmed by the presence of UTC in /etc/adjtime.

/etc/localtime is linked as below
lrwxrwxrwx 1 root root 22 Mar 29 16:13 /etc/localtime -> /usr/share/zoneinfo/GB ...