LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 04-21-2003, 08:09 PM   #16
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 45

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.
 
Old 04-21-2003, 09:11 PM   #17
DaOne
Member
 
Registered: Jan 2003
Location: USA
Distribution: Slackware
Posts: 498

Rep: Reputation: 30
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.
 
Old 04-21-2003, 09:37 PM   #18
DaOne
Member
 
Registered: Jan 2003
Location: USA
Distribution: Slackware
Posts: 498

Rep: Reputation: 30
One more thought...when removing Watchdog Timer support, remove it altogether...not just the individual chipsets.
 
Old 04-22-2003, 02:18 PM   #19
Mattias
LQ Newbie
 
Registered: Apr 2003
Posts: 10

Original Poster
Rep: Reputation: 0
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'.
 
Old 04-22-2003, 02:40 PM   #20
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 45
Suggest try the compile commands separately, in the same order. Then post the error along with what part it was performing.
 
Old 04-25-2003, 08:37 AM   #21
Mattias
LQ Newbie
 
Registered: Apr 2003
Posts: 10

Original Poster
Rep: Reputation: 0
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
 
Old 04-25-2003, 09:59 AM   #22
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 45
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.
 
Old 04-25-2003, 10:15 AM   #23
Mattias
LQ Newbie
 
Registered: Apr 2003
Posts: 10

Original Poster
Rep: Reputation: 0
/*
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!

Last edited by Mattias; 04-25-2003 at 12:03 PM.
 
Old 04-25-2003, 08:59 PM   #24
DaOne
Member
 
Registered: Jan 2003
Location: USA
Distribution: Slackware
Posts: 498

Rep: Reputation: 30
It's been my experience that Linux is fussy with memory timing/speed.
 
Old 04-26-2003, 09:07 PM   #25
Aussie
Senior Member
 
Registered: Sep 2001
Location: Brisvegas, Antipodes
Distribution: Slackware
Posts: 4,590

Rep: Reputation: 56
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.
 
Old 07-31-2003, 08:47 AM   #26
Juniper34
LQ Newbie
 
Registered: Jul 2003
Distribution: Slackware 9.0, Mandrake 8.0
Posts: 26

Rep: Reputation: 15
blacklist

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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
rebooting spuppett Linux - Newbie 3 04-11-2004 04:21 PM
Need help rebooting SynnerST Slackware 5 10-29-2003 10:21 AM
Slackware 9.0 rebooting itself Mattias Linux - General 1 04-21-2003 01:44 PM
Slackware 9 rebooting after 15-20 secs chakotay Slackware 4 03-26-2003 09:00 AM
rebooting to a cd lot2learn Linux - Software 6 07-19-2001 09:29 AM


All times are GMT -5. The time now is 07:55 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration