There was another thread recently on the same problem. Perhaps you might want to read it.

http://www.linuxquestions.org/questi...highlight=i810

But if you boot the install CD as normal for a regular setup. After login, mount your root partiton, and then delete the module from the system. No module, it can't load.

mount /dev/hda1 /mnt
cd /mnt/lib/modules/2.4.20/kernel/drivers/char
rm i810-tco.o.gz
rm i810-rng.o.gz
cd /
umount /mnt

and reboot.

You will be better off removing it from your kernel and recompiling...we can deal with the mouse issue also. You already know what to do for the Watchdog Timer thing...as for the other i810 stuff...also remove Intel i810 Random Number Generator Support (under character devices) and Intel i810/i815/i830M (onboard) support from the kernel. By the way...do you have any of these chipsets?

now for the USB issue...

Under USB support...enable the following...as modules...
UHCI Alternate Driver (JE) support
EHCI HCD (USB 2.0) support (EXPERIMENTAL) *(if using USB 2.0)*
USB HIDBP Mouse (basic) support
USB Human Interface Device (full HID) support

And enable this in the kernel...

HID input layer support
/dev/hiddev raw HID device support

Recompile, and let's see if your mouse issue goes away.

As Excalibur stated earlier, if you just remove the modules, the issue never really goes away.

One more thought...when removing Watchdog Timer support, remove it altogether...not just the individual chipsets.

OK everything works now.
But I'm having a problem compiling the kernel, if I use the default config, I seem to miss alot of stuff needed (mouse, and other things won't work) so I load /boot/config in 'make menuconfig' program because I don't know what I'm missing. Then I remove everything with i810 and Watchdog Timer but when doing:
'make dep && make clean && make bzImage && make && make install && make modules && make modules_install'
I get an error and the compile stops saying I should report the bug.
Before compiling I also change some stuff in /etc/lilo.conf to be able to boot back to the old kernel if the new one will fail, and I uncomment 'export INSTALL_PATH = /boot' in the Linux source 'Makefile'.

Suggest try the compile commands separately, in the same order. Then post the error along with what part it was performing.

This appears when 'make modules':

kernel BUG at page_alloc.c:217!
invalid operand: 0000
CPU: 0
EIP: 0010:[<c0130773>] Not tainted
EFLAGS: 00010002
eax: 00000000 ebx: c19a6744 ecx: 00001000 edx: 0000999e
esi: c0300d04 edi: 00000000 ebp: c0300cf0 esp: c86c3e7c
ds: 0018 es: 0018 ss: 0018
Process cc1 (pid: 11179, stackpage=c86c3000)
Stack: 00001000 c19a6744 c012aabb 0000899f 0000899e 00000282 00000000 c0300cf0
c0300e74 000001ff 00000000 000001d2 c0130c29 c0300cf0 c0300e70 00000001
00104025 dfe45b10 c8219b80 dd741c44 c0126b6c 40311000 dfe45b10 00000001
Call Trace: [<c012aabb>] [<c0130c29>] [<c0126b6c>] [<c0126e99>] [<c01140d1>]
[<c012a1e0>] [<c012a304>] [<c0137733>] [<c01360d7>] [<c0113f70>] [<c0109024>]

Code: 0f 0b d9 00 68 00 2c c0 8b 53 04 8b 03 89 50 04 89 02 c7 43
gcc: Internal error: Segmentation fault (program cc1)
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[2]: *** [arptable_filter.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.20/net/ipv4/netfilter'
make[1]: *** [_modsubdir_ipv4/netfilter] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.20/net'
make: *** [_mod_net] Error 2

It has been my experience that most segmentation faults are either faulty RAM or a corrupted file system. Of course other problems like a bad library can exhibit itself as a corrupted file system. Still results in bad code being run. As for memory you might consider running a good memory test program like memtest86 from

http://www.memtest86.com

From the earlier posts when you system was rebooting after startup, file system corruption could have been a result. So you might want to reinstall all the pcakages from the slackware/d tree on the install CD. That tree is the development tree where the compilers and stuff are at.

/*
What could have caused a corrupted file system and is that "something that happens" or faulty hardware (like a faulty RAM would be, I guess)?

Anyway, thanks for the tips.
*/

Got it working now. There was a problem with my RAM I guess. I have DDR 400mhz and had my computer overclocked, else the DDR would run at 266mhz (Ohh! ). Now everything works fine though, so I'm happy

Thanks everyone!

It's been my experience that Linux is fussy with memory timing/speed.

The linux kernel interacts directly with your hardware once it's loaded into memory, and when overclocking a small hardware glitch can cause all manner of problems - and spontanious reboots are caused by hardware problems.

Hey guys I just found this in a recent post and it took care of things if you don't want to recompile. Enter i810-tco and i810_rng modules in the /etc/hotplug/blacklist file to keep them from being loaded.