Pages

Search

No init found (after reset) - Forums Linux

No init found (after reset) - Forums Linux

No init found (after reset)

Posted: 03 Sep 2004 10:28 AM PDT

Jose Maria Lopez Hernandez wrote:
 

Uh ... I'd say that if that was something that could happen from the
fsck, then the data was probably already lost ...

--
PeKaJe

Reader, suppose you were an idiot. And suppose you were a member of
Congress. But I repeat myself. -- Mark Twain

Grub Configuration

Posted: 02 Sep 2004 10:55 PM PDT

es (amanita) writes:
 

Or if you run a Redhat/Fedora system, but CD 1 in the CD drive, and type 'linux
rescue' at the lilo prompt, and then do the chroot, and grub-install.

--
Michael Meissner
email: org
http://www.the-meissners.org

X setup on Debian?

Posted: 02 Sep 2004 09:48 PM PDT

Hello

(Follow-Up to alt.os.linux.debian ignored, because it is not yet
available for me)

Madhusudan Singh (<invalid>) wrote: 

If the virtual consoles are broken as well, this /could/ be some
conflict between X and the console framebuffer driver. Did you try to
turn off the framebuffer driver, e.g. by passing

vga=normal
video=vga16:off

or something like that to the kernel?

Also, what kind of graphic card does the laptop use? And what version of
Debian do you use? XFree 4.1 in Woody does not support some older
cards, for which you would have to use XFree 3.3.6, or XFree 4.3.
 

By default, runlevels 2,3,4 and 5 on Debian systems are identical. You
could remove the xdm/kdm/gdm symlink for some runlevel, and boot into
that one. You can also boot into single user mode without the CDROM,
simply press <TAB> at the lilo prompt (if you use lilo), and append

init 1
or
init s

to the prompt.
 

If the card is not too old, you should rather try the VESA driver, which
should work with all VESA 2 compliant cards.
 

That depends on how X was started. If you use some login manager, this
is true. You would have to shut it down, e.g. using

/etc/init.d/xdm stop

But of course, this is difficult without working consoles.

best regards
Andreas Janssen

--
Andreas Janssen <com>
PGP-Key-ID: 0xDC801674 ICQ #17079270
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps.html

Fedora and SATA drives

Posted: 02 Sep 2004 02:57 PM PDT

In message <BmZZc.42648$videotron.net>, Wacha
<nospam> writes 

Thanks

Waiting for disks to arrive!

Tim

--
Tim
http://yingtong.co.uk

Saving and Viewing MP4 files

Posted: 02 Sep 2004 03:36 AM PDT

Zach Nation wrote:
 


You can also try VideoLAN's VLC: http://www.videolan.org/. I actually
got a MPEG that would not play on any other player to play on VLC. Go me.

--
Keith Gable
Lead Programmer of the Ignition Project
http://www.ignition-project.com/
ICBM: 35.540383, -94.988756
*Joshua 1:9 :: The Message:* Haven't I commanded you? Strength! Courage!
Don't be timid; don't get discouraged. GOD, your God, is with you every
step you take.
*Take back the web!* http://www.mozilla.org/products/firefox/

Xterm font size

Posted: 01 Sep 2004 10:19 AM PDT

Bit Twister wrote:
 

THANK YOU MISTER TWISTER!

umount fails, fuser silent

Posted: 01 Sep 2004 01:07 AM PDT

Jean-Paul Le Fevre wrote: 
As another poster suggested, what happens if you comment out the line
concerning this "/ker" from /etc/fstab? What does this "ker" contains?
Kernel stuff ??

nvidia driver install on debian

Posted: 01 Sep 2004 12:48 AM PDT

Gernot Frisch wrote:
 

You need to install kernel sources, usually under /usr/src/linux. Of course
that kernel will need to be the one that you run the X server under.

Nvidia video driver question?

Posted: 31 Aug 2004 06:50 PM PDT

In article news:<rr.com>,
Charles Sullivan wrote: 

I agree ... and would add that there is another difficulty in that
some news /servers/ reject postings to groups they don't handle,
while others silently drop those groups and effect the posting to
those that they are able.

If anything this argues against the use of follow-ups, because if a
posting is sent only to a group that is silently dropped by a
server it will disappear into the void.

I dislike cross-posting, but I firmly believe that once something
has been cross-posted it should stay that way. Experience suggests
that follow-ups actually increase the noise that they are intended
to reduce. A decent newsreader won't show you a cross-posted
message more than once, anyway.
 

It doesn't seem off-topic for either group, but as it's not a
RedHat-specific question a general group like cols is probably a
better place to ask than colr. Asking in both is only a good idea
if you think there's a good reason to suppose that there will be
people with the answer in colr who con't also follow cols. I don't
follow colr, so I can only guess, but I'd have thought asking in
cols alone would have been the best choice in this case.

I certainly agree that cross-posting is preferable to multi-posting
... but I wouldn't blame you for asking the same question in a
second group once it was clear that you weren't going to get an
answer in the first. Even the most experienced posters don't always
get it right first time.

Cheers,
Daniel.

MD 10: lilo troubles (volume, raid nonsense)

Posted: 31 Aug 2004 08:26 AM PDT


"Ron Gibson" <net> wrote in message
news:net... 
seem 

RedHat dumped it, so are other distributions. LILO has serious user
interaction issues and is far more difficult to recover from problems with,
and its fifteen or sixteen character limit in the apparent name of the boot
configurations is painful to cope with when you have multiple configurations
for testing or other purposes. As someone who's installed a series of a
dozen different kernels on the same machines and hopped among them to do
performance testing, I found that limitation painful. Mind you, I still miss
the LILO feature of doing "lilo -d [oldkernel]; lilo -R [newkernel]; reboot"
to reboot the first time only with a new kernel, and only set it as the
default if it was successful. It helped keep my hands off the hardware for
testing in remote locations and could be recovered from by a simple reboot
instead of having to bring up a console at boot time. But it's overwhelmed
by the overall flexibility and ease of configuration of the grub tools.

Whoops, I'm sorry, I thought you said I couldn't be bothered to learn LILO.

fedora core 1, system standby

Posted: 30 Aug 2004 06:01 PM PDT

com (com) wrote in message news:<google.com>... 

Very well could be -- hard to tell from lack of message outputs, etc.
See below ...
 


Checking the "usual" suspects is always a good idea -- no sense in
overlooking the obvious ;-)

But working mostly from your own "diagnosis" you may have a WOL
(wake-on-lan) nic that has been awakened by some recent change in your
setup -- most drivers turn it off as the default.

Sounds like you don't really need this "feature" if it is the source
of your problem. Each nic/driver is a bit different though so google:
linux nic wake-on-lan wol
and perhaps add your nic's brand/model# to the search.

You'll find a bunch of hits -- see this for _very_ quick primer:
http://ahh.sourceforge.net/wol/

Of course, this could be a sign of a WOL nic gone bad or a heartbeat
daemon screwing up -- these can be hard to track down. Took us
several months to figure out why stations were dropping from NetWare
net at school. Onboard WOL nics can be especially trying if there is
not extensive BIOS setup support.

hth,
prg
email above disabled