Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
03-23-2003, 12:10 PM
|
#1
|
Member
Registered: Jan 2002
Location: Singapore
Distribution: Slackware
Posts: 250
Rep:
|
Dont Understand
I have installed Slackware and running fine, but i notice that everytime i boot up the machine i get this error
ar 24 01:22:24 Keave kernel: i810 TCO timer init: failed to reset NO_REBOOT flag, reboot disabled by hardware
Mar 24 01:22:24 Keave kernel: i810_rng: cannot disable RNG, aborting
Mar 24 01:22:24 Keave kernel: i810 TCO timer init: failed to reset NO_REBOOT flag, reboot disabled by hardware
Mar 24 01:22:24 Keave last message repeated 11 times
Mar 24 01:22:33 Keave modprobe: modprobe: Can't locate module char-major-10-134
Mar 24 01:24:34 Keave modprobe: modprobe: Can't locate module sound-slot-1
Mar 24 01:24:34 Keave modprobe: modprobe: Can't locate module sound-service-1-0
Mar 24 01:24:34 Keave modprobe: modprobe: Can't locate module sound-slot-1
Mar 24 01:24:34 Keave modprobe: modprobe: Can't locate module sound-service-1-0
Mar 24 01:28:21 Keave modprobe: modprobe: Can't locate module char-major-10-134
Mar 24 01:29:10 Keave modprobe: modprobe: Can't locate module sound-slot-1
Mar 24 01:29:10 Keave modprobe: modprobe: Can't locate module sound-service-1-0
Mar 24 01:29:10 Keave modprobe: modprobe: Can't locate module sound-slot-1
Mar 24 01:29:10 Keave modprobe: modprobe: Can't locate module sound-service-1-0
Mar 24 01:50:43 Keave modprobe: modprobe: Can't locate module char-major-10-134
Mar 24 01:51:12 Keave modprobe: modprobe: Can't locate module sound-slot-1
Mar 24 01:51:12 Keave modprobe: modprobe: Can't locate module sound-service-1-0
Mar 24 01:51:12 Keave modprobe: modprobe: Can't locate module sound-slot-1
Mar 24 01:51:13 Keave modprobe: modprobe: Can't locate module sound-service-1-0
Mar 24 01:51:34 Keave modprobe: modprobe: Can't locate module char-major-10-134
Mar 24 01:51:45 Keave modprobe: modprobe: Can't locate module sound-slot-1
Mar 24 01:51:45 Keave modprobe: modprobe: Can't locate module sound-service-1-0
Mar 24 01:51:45 Keave modprobe: modprobe: Can't locate module sound-slot-1
Mar 24 01:51:45 Keave modprobe: modprobe: Can't locate module sound-service-1-0
Mar 24 01:51:55 Keave modprobe: modprobe: Can't locate module char-major-10-134
Mar 24 01:53:28 Keave kernel: Linux version 2.4.20 (root@midas) (gcc version 3.2.2) #2 Mon Mar 17 22:02:15 PST 2003
But i am able to get sound from my sound card and i don't what does i810 TCO timer init: failed to reset NO_REBOOT flag, reboot disabled by hardware this mean??? Anyone help?
when i do a lsmod it shows
Module Size Used by Not tainted
i810_rng 2624 0 (unused)
uhci 24560 0 (unused)
usbcore 58144 1 [uhci]
emu10k1 61288 1
ac97_codec 9512 0 [emu10k1]
soundcore 3332 4 [emu10k1]
emu10k1-gp 1352 0 (unused)
gameport 1452 0 [emu10k1-gp]
ide-scsi 8048 0
tulip
Thanks in advance
|
|
|
03-23-2003, 12:14 PM
|
#2
|
Member
Registered: Jan 2002
Location: Singapore
Distribution: Slackware
Posts: 250
Original Poster
Rep:
|
And one more thing I got a file call lastlog located in /var/log which is 320MB !!!! And when i try to open it with pico it tell me files with long lines and was not able to open it just keep running!! I find it weird.
|
|
|
03-23-2003, 12:29 PM
|
#3
|
Senior Member
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180
Rep:
|
What version Slackware are you running?
My lastlog file is only 287 KByte, but not MByte, on my system. Please verify. The file is a system file is not normally a readable text file. I tcontains the last login for users. Use the "lastlog" command to view the contents. (man lastlog - for more info)
|
|
|
03-23-2003, 12:41 PM
|
#4
|
LQ Newbie
Registered: Mar 2003
Distribution: Gentoo/Debian/LFS
Posts: 8
Rep:
|
/var/log/lastlog is a 'special' unix file; it is not really as big as reported. There are some posts ... try /var/log/lastlog on google.
|
|
|
03-23-2003, 07:39 PM
|
#5
|
Member
Registered: Jan 2002
Location: Singapore
Distribution: Slackware
Posts: 250
Original Poster
Rep:
|
Well it really show 320MB when I right click on it and go to properties of the file. OH I am running Slackware 9.0 Excalibur, do u know what are the errors mention above and the solution to solve it?
|
|
|
03-23-2003, 08:36 PM
|
#6
|
Member
Registered: Mar 2003
Distribution: Slackware Current
Posts: 42
Rep:
|
about the " Mar 24 01:51:45 Keave modprobe: modprobe: Can't locate module sound-slot-1 ", I think ur kernel is compiled with built in sound support for u sound card. try editing /etc/modules.conf stop trying to load the module at startup.
|
|
|
03-23-2003, 09:07 PM
|
#7
|
Senior Member
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180
Rep:
|
Unfortunately I have not seen Slack 9.0 as yet. I have it ordered, but the last I checked the ISO image files were not available. I assume people are either building their own or getting something somebody else has built.
But to your problem I can only suggest looking at the /etc/rc.d/rc.modules file. It would appear from the list, that none are required for a clean boot. So "chmod 000 /etc/rc.d/rc.modules" and reboot. That should stop all modules from loading. If error continues then it is builtin to the kernel and a new kernel will need to be built. Use 755 in the prior command to restore to normal.
On your lastlog file, I think I would verify from a console prompt. Unless of course you have created a few hundred thousand users and they have all logged in at least once. Because all the file contains is the userid, port, date for the last time a user logs in. Again, use the lastlog command to view the contents. If the console prompt verifies that it is 320 MByte, then I suggest running e2fsck to check the file system. All the systems I checked the file is only around 300 Kbytes. I would even think you could delete the file and then "touch /var/log/lastlog" to recreate it. (Empty of course.)
Also, the prior post mentioned the /etc/modules.conf file. I have the file but it is empty so I do not know what it is suppose to do or why it is there.
(Now I remember I think it is for autoloading modules.)
Last edited by Excalibur; 03-23-2003 at 09:16 PM.
|
|
|
03-23-2003, 09:15 PM
|
#8
|
Member
Registered: Jan 2002
Location: Singapore
Distribution: Slackware
Posts: 250
Original Poster
Rep:
|
Thanks bengo I will try on that when i get home.
Excalibur I get the iso image from slackware.at. I had try rm lastlog and create it but it still show 320MB its really weird as Iam had only create one user + root. And I got no idea what is 24 01:22:24 Keave kernel: i810 TCO timer init: failed to reset NO_REBOOT flag, reboot disabled by hardware about?
|
|
|
03-23-2003, 10:13 PM
|
#9
|
Member
Registered: Mar 2003
Distribution: Slackware Current
Posts: 42
Rep:
|
Quote:
Originally posted by Excalibur
Also, the prior post mentioned the /etc/modules.conf file. I have the file but it is empty so I do not know what it is suppose to do or why it is there.
(Now I remember I think it is for autoloading modules.)
|
it's where u find "alias sound-slot-1 blah blah blah"
used to load my sound module
|
|
|
03-23-2003, 11:23 PM
|
#10
|
Member
Registered: Jan 2002
Location: Singapore
Distribution: Slackware
Posts: 250
Original Poster
Rep:
|
Quote:
Originally posted by bengo
it's where u find "alias sound-slot-1 blah blah blah"
used to load my sound module
|
So i just comment out this part will do?
|
|
|
03-24-2003, 06:20 AM
|
#11
|
Member
Registered: Jan 2003
Location: USA
Distribution: Slackware
Posts: 498
Rep:
|
Quote:
And I got no idea what is 24 01:22:24 Keave kernel: i810 TCO timer init: failed to reset NO_REBOOT flag, reboot disabled by hardware about?
|
This is a module for Watchdog Timer support for the Intel i8x0 chipsets. Unless you need this support, you can remove support for this in your kernel configuration menu, then recompile. Don't compile it as a module either...just remove it.
|
|
|
03-24-2003, 07:25 AM
|
#12
|
Member
Registered: Jan 2002
Location: Singapore
Distribution: Slackware
Posts: 250
Original Poster
Rep:
|
Tried the /etc/rc.d.modules but it didnt work guess i need to recompile my kernel but I got a hard time figuring how to compile slackware 9.0 kernel and this is no kernel in /usr/src.
hai.....
|
|
|
03-24-2003, 08:11 AM
|
#13
|
Member
Registered: Jan 2003
Location: USA
Distribution: Slackware
Posts: 498
Rep:
|
Most of the ISOs do not include the kernel source to keep the ISO small enough to fit on a CD. So just download and install the source from one of the FTP mirrors from the /slackware/k directory, then you can recompile your kernel.
|
|
|
03-24-2003, 08:11 AM
|
#14
|
Member
Registered: Oct 2002
Distribution: Slackware 8.1
Posts: 33
Rep:
|
Quote:
Originally posted by Excalibur
On your lastlog file, I think I would verify from a console prompt. Unless of course you have created a few hundred thousand users and they have all logged in at least once. Because all the file contains is the userid, port, date for the last time a user logs in. Again, use the lastlog command to view the contents. If the console prompt verifies that it is 320 MByte, then I suggest running e2fsck to check the file system. All the systems I checked the file is only around 300 Kbytes. I would even think you could delete the file and then "touch /var/log/lastlog" to recreate it. (Empty of course.)
|
I'll chime in too:
bryan@whirlwind:~$ ls -lh /var/log/lastlog
-rw-r--r-- 1 root root 285k Mar 23 22:53 /var/log/lastlog
You say that you checked it in properties. What does the above command give you on the command line (in an xterm)? I trust that a whole more than nautilus :-)
BB
|
|
|
03-24-2003, 09:29 AM
|
#15
|
Member
Registered: Jan 2002
Location: Singapore
Distribution: Slackware
Posts: 250
Original Poster
Rep:
|
Quote:
Originally posted by otbibb
I'll chime in too:
bryan@whirlwind:~$ ls -lh /var/log/lastlog
-rw-r--r-- 1 root root 285k Mar 23 22:53 /var/log/lastlog
You say that you checked it in properties. What does the above command give you on the command line (in an xterm)? I trust that a whole more than nautilus :-)
BB
|
keave@keave's:/var/log$ ls -lh lastlog
-rw-r--r-- 1 root root 321M Mar 24 23:16 lastlog
I just did reinstallation again just to make sure everything is right but I think I am still have all the above problems.
|
|
|
All times are GMT -5. The time now is 07:16 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|