* Re: Please help
Please help Fouta Hafida
@ ` L. C. Robinson
0 siblings, 0 replies; 2+ messages in thread
From: L. C. Robinson @ UTC (permalink / raw)
To: blinux-list
On Fri, 4 Jan 2002, Fouta Hafida wrote:
> I am using redhat 6.2. I have a lot of interesting files stored
> there. It was working properly till I configured the sound
> card. Once I reboot the system everything was well mounted but
> the windowx didn't want to appear. I get a black screen. I
> waited for 5 min and I got a login prompt but in vain it
> doesn't give even the option to enter the password. I don't
> want to reinstall it cause I ll loose everything my whole
> project is there. Please if anybady can help me I will be
> really thankful
First boot up in confirm mode (add the word "confirm" to the boot
command line). This assumes you have speech working by that time
in the boot process. You will be asked to confirm before each
daemon or background process is started. Naturally you would
refuse any you suspect.
If that doesn't help, try booting up in single user or emergency
mode, thus preventing most things from being started or
configured. Add "s", "single", or, if things are really bad, and
you want a really bare bones system, add the word "emergency" or
-b to the boot line.
Then you might need to comment out the stuff in /etc/modules.conf
related to the hardware that might have an interrupt conflict, or
whatever. You may be able to look in some of the psuedo files
(really kernel tables) in /proc, such as "interrupts" to see what
your other hardware is using; ie:
cat /proc/ioports
cat /proc/interrupts
Finally, if nothing else works, you can boot up in rescue mode.
Many rescue disk schemes are available on linux archive sites.
Red Hat provides one of them, which can be found on their install
disk. The Red Hat Linux Reference Guide has a chapter on how to
do this (available on the documentation CD, or on the web, at
redhat.com).
For more specific help, you would need to tell us the particulars
of your sound card, what interrupts and ioports are in use,
what you did to configure it, and generally whatever detail might
be useful.
LCR
--
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid
People buy MicroShaft for compatibility, but get incompatibility and
instability instead. This is award winning "innovation". Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
^ permalink raw reply [flat|nested] 2+ messages in thread