[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Problams at boot



I am running a standalone desktop Debian system ,version 2.4.27-2-386,
stable 3.1 release (Sarge) on the following machine:

Intel Pentium 4 CPU 1500Hz stepping 07
Intell corp 82850 850 (Tehama) chipset
500 MB ram memory

On boot I get the following messages lines.  These lines were not
included in the _dmesg_ or _syslog_ files but were hand copied to
include in this e-mail. The entire dmesg is included as an attachment.

Problem 1
Began lines:
INIT: version 2.86 booting
/etc/rcS.d/S02montvirtfs:line40:/dev/null: Read-only file system
/etc/rcS.d/S02montvirtfs:line40:/dev/null: Read-only file system
....
....
/etc/init.d/rcS:line 11:/dev/null:Read-only file system
/etc/init.d/rcS:line 1:/dev/null:Read-only file system
/etc/init.d/rcS:line 13:/dev/null:Read-only file system
Activating Swap
/etc/init.d/rcS:line 125:/dev/null:Read-only file system
/etc/init.d/rcS:line 1200:/dev/null:Read-only file system
Checking root file system ....
fsck 1.37 (21 mar. 2005)
ERROR: Couldn't open /dev/null (Read-only file system)
/: clean, 12758/192768 files, 119670/393217 blocks
/etc/init.d/rcS:line 287:/dev/null:Read-only file system
End lines

The /dev/null file is chmod 644, chown root, and chgrp root.
-rw-r--r--  1 root  root 10070 2006-06-18 20:11 /dev/null
 That is the way it seemed to have been compiled. 

 I am using Gnome2 as a desktop and the only way users, other than root,
can get anything other than a gnome2 terminal is to have write access to
the /dev/null file. I have made a work around by creating a separate
group, gdt (gnome desk top), and setting all users that need a desktop
to be members of that group.

-rw-rw-r--  1 root gdt 10070 2006-06-18 20:11 /dev/null

I have no idea what that has done to the security of the system.  I
would like to know if any one has any suggestion on what to do and how
to do it.

Problem 2
Begin lines:
insmod:/lib/modules/2.4.27-2-386/kernel/drivers/hotplug/pciehp.o:
init_module:
Operation not permitted
insmod:Hint:insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
You may find more information is syslog or the output from dmesg
insmod:/lib/modules/2.4.27-2-386/kernel/drivers/hotplug/pciehp.o:
init_module: insmod pciehp failed
pciehp: can't be loaded
missing kernel or user mode driver pciehp
End lines

I think the above has to do with a kernel driver.  As I said before
_dmesg_ , _kernel.log_ or _syslog_  does not contain these lines. 
Can you give me help on how to get these drivers in at boot time.

Problem 3
Begin lines:
hw_random:misc device register failed
insmod:/lib/modules/2.4.27-2-386/kernel/drivers/char/hw_random.o:init_module:
Device or resource busy
insmod:Hint:insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
You may find more information is syslog or the output from dmesg
insmod:/lib/modules/2.4.27-2-386/kernel/drivers/char/hw_random.o:init_module:insmod
hw_random:can't be loaded
missing kernel or user mode driver hw_random
End lines:

This is probably the same as  Problem 2 the (hotplug problem).

This is my first attempt to use the Debian system and it seems to be a
fantastic system.
Thanks to all who made it that way.
reliable



Reply to: