From: Janina Sajka <janina@rednote.net>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: fedora core 1 mkinitrd problem
Date: Mon, 21 Jun 2004 14:26:19 -0400 [thread overview]
Message-ID: <20040621182619.GC32032@rednote.net> (raw)
In-Reply-To: <Pine.BSF.4.60.0406202347330.43985@server2.shellworld.net>
This command is missing some arguments. Please re-read the HOWTO.
In particular, you need to specify the kernel module. The purpose of
being in /lib/modules is to make that easy via the TAB key--but you
still have to back-space the / off. Are you doing that?
Jude DaShiell writes:
> From: Jude DaShiell <jdashiel@shellworld.net>
>
> I was doing a fedora core 1 install earlier with the speakup-HOWTO and got
> to the mkinitrd step and ran into what to me appears to be a strange
> problem. For background, all three yarrow discs passed integrity check
> and this is why I'm finding what happened strange. I do the line:
>
>
>
> /sbin/mkinitrd -v -f /boot/initrd-<tab> --with=speakup_ltlk <tab> <cr>
> and get back the message that speakup_ltlk module couldn't be found
> aborting.
> For now until I try to install something else that other computer is a
> paperweight. Fortunately pc-dos 2000 is on another computer able to back
> Linux up. How could the module not be found with a passing integrity
> check?
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
--
Janina Sajka, Director
Technology Research and Development
Governmental Relations Group
American Foundation for the Blind (AFB)
Chair, Accessibility Workgroup
Free Standards Group (FSG)
Email: janina@afb.net Phone: (202) 408-8175
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Jude DaShiell
` Janina Sajka [this message]
` Jude DaShiell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040621182619.GC32032@rednote.net \
--to=janina@rednote.net \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).