Displaying 9 results from an estimated 9 matches for "udevstart".
2005 Oct 01
2
Problem getting x86_64 dom0 to boot on a FC4 machine
...in/nash
mount -t proc /proc /proc
setquiet
echo Mounted /proc filesystem
echo Mounting sysfs
mount -t sysfs /sys /sys
echo Creating /dev
mount -o mode=0755 -t tmpfs /dev /dev
mknod /dev/console c 5 1
mknod /dev/null c 1 3
mknod /dev/zero c 1 5
mkdir /dev/pts
mkdir /dev/shm
echo Starting udev
/sbin/udevstart
echo -n "/sbin/hotplug" > /proc/sys/kernel/hotplug
echo "Loading sata_sil.ko module"
insmod /lib/sata_sil.ko
echo "Loading md.ko module"
insmod /lib/md.ko
echo "Loading raid1.ko module"
insmod /lib/raid1.ko
echo "Loading xor.ko module"
insmod /li...
2004 Jun 07
2
run-init warning
Please be aware that I HAVE NOT TESTED THIS PROGRAM... please try it in
a "safe" environment since for all I know it could nuke your "real root"
by mistake.
-hpa
2006 Jun 15
1
Strange Zaptel issue
...ot;zap/pseudo"
KERNEL="zap[0-9]*", NAME="zap/%n"
[beta@staging ]# ls /dev/*z*
/dev/zero
[beta@staging zaptel-1.2.6] make ; make linux26 ; make install
[beta@staging zaptel-1.2.6]# make devices
build_tools/genudevrules > /etc/udev/rules.d/zaptel.rules
[beta@staging ]# udevstart
[beta@staging ]# modprobe zaptel
FATAL: Module zaptel not found.
[beta@staging question]# ztcfg
Notice: Configuration file is /etc/zaptel.conf
line 0: Unable to open master device '/dev/zap/ctl'
1 error(s) detected
[beta@staging question]#
TAKE NOTE BEFORE POINTING OUT ANOTHER POST ON TH...
2006 Apr 20
1
Fun and games with newhidups, udev rules and permissions
...ppears odd that
newhidups insists on scanning the bus nomatter what is fed to it as
the mandatory command-line device filename.
Finally, a disclaimer - I only just got this going. I thought I had
the bugs out last night, but they all came back after a reboot. I've
rebooted, restarted udev with udevstart, unplugged and replugged the
UPS into different USB ports etc. And it still seems to be OK. But no
guarantees I'm not missing something here!
Hope this might be useful to someone.
Lincoln
2006 Jun 04
0
Kernel panic on change from 2.4.x to 2.6.x
...ot; (reason: pcmcia-stuff):
------------------------- [ BEGIN linuxrc ] -------------------------
PCIC="ide_cs yenta_socket pcmcia_core pcmcia rsrc_nonstatic"
PCIC_OPTS=
CORE_OPTS=
DEBUG=1
mount -t proc /proc /proc
mount /sys
echo "/sbin/udev" > /proc/sys/kernel/hotplug
/sbin/udevstart
echo "==== initrd: starting PCMCIA services ===="
CreateCF-Node
for Module in $PCIC
do
modprobe $Module
done
pcmcia-socket-startup
echo -n "42" > /sys/bus/pcmcia/devices/1.0/allow_func_id_match
sleep 5
umount /proc
umount /dev/ram
if [ "$DEBUG" != "&qu...
2007 Dec 17
4
take plunge and yum update to 4.6
Usually I am one of the first ones to do it
I have resisted this time...
It is almost the Holidays and out centos 4 boxes have been online for like 2
years or whatever
Has anyone boldly taken the plunge on any high use and/or Internet facing
Centos$ servers and done a
yum update
or a
yum -y update
without any problems at all?
:-)
- rh
2006 Jun 10
1
PXELINUX with Kernel 2.6.15.4: VFS: Cannot open root device "hde1" or unknown-block(0, 0)
...s on unknown-block(0,0)"
becomes
"VFS: Unable to mount root fs on unknown-block(51,1)"
I tried in "linuxrc":
--------------------------------------------------
...
mount /dev/hde1
umount /proc
umount /sys
cd /mnt
/mnt/sbin/pivot_root . initrd
mount /sys /sys -t sysfs
/sbin/udevstart
/sbin/pcmcia-socket-startup
mount /proc
echo -n "42" > /sys/bus/pcmcia/devices/1.0/allow_func_id_match
echo 0x3301 > /proc/sys/kernel/real-root-dev
sleep 5
exec <dev/console >dev/console 2>&1
exec chroot . /bin/sh <<EOF
umount initrd
/sbin/blockdev --f...
2007 Feb 08
5
kernel 2.6.9-42.0.8.EL error while booting - CentOS 4.4
Hi ,
I am ruuning Senmail with MailScanner on CentOS 4.4. It has updated to
kernel 2.6.9-42.0.8.EL from its past kernel 2.6.9-42.0.3.EL.
Now the Server can not boot up and gives the below error.
mkrootdev: label / not found
Mounting root filesystem
mount: error 2 mouting ext3
switchroot: mount failed: 22
Kernel panic - not syncing: Attempted to kill init!
But I can boot up from its
2006 Jan 13
9
loading zaptel drivers automatically upon reboot
Just installed Asterisk 1.2 on a brand new clean machine running
RedHat 9.0. I have a TDM400 card inside. When I boot, the card seems
dead. When I do:
modprobe wctdm
modprobe Zaptel
the lights come on and all seems fine, until I reboot that is...
After a reboot I have to repeat the modprobe.
I shouldn't have to do a modprobe every re-boot should I? How do you
get the drivers to load