From: lich@tuxfamily.org
To: linux-kernel@vger.kernel.org
Cc: Dave Jones <davej@codemonkey.org.uk>,
Horst Von Brand <vonbrand@inf.utfsm.cl>
Subject: Re: 2.5.75 doesn't boot at all on x86
Date: Mon, 14 Jul 2003 07:28:05 +0200 [thread overview]
Message-ID: <1058160485.3f123f65da7fa@www.france-techno.com> (raw)
Dave Jones wrote:
> On Sun, Jul 13, 2003 at 03:50:31PM +0200, Anthony Lichnewsky wrote:
> > After lilo, the kernel is uncompressed, then the screen goes black.
> > the traditional init message is not even displayed
> > ( INIT version 2.85 booting ).
> > It accepts Ctrl+Alt+Suppr for reboot. but that's it.
> >
> > I checked that CONFIG_VT, CONFIG_VGA_CONSOLE are set in my .config.
> > I suspect the initrd image is not loaded correctly, but I don't have any
> > real clue. It was generated with mkinitrd version 3.4.43.
> > Any Idea of what it might be ?
>
> Try CONFIG_VIDEO_SELECT=n. If that doesn't help, post your .config.
> (That config option really needs to tighten up what it does in
> its EDID parser, see
http://www.cs.helsinki.fi/linux/linux-kernel/2003-20/052.html
> which still isn't fixed...)
>
> Dave
>
>
>
Thanks Dave.
I did that, and it left me with the kernel booting, but still no VT.
In fact, it appeared that rivafb that I use (says it detected my geForce
2, nevertheless ...) didn't do anything. I suppressed it and used vesafb
instead, and that was it.
I have now another strange problem, but I think I am not the only one to
experience it.
modprobe fails on /etc/modules.devfs and /etc/modules.conf at each
probeall line.
therefore, I dont have all modules up, particularly no mouse, no sound,
no pcmcia, no acpi, no ide-scsi cdrw/dvd ....
the message is
modprobe: WARNING: /etc/modules.xxxx line xx: ignoring bad line
starting with 'probeall'
my modules.devfs only has probeall lines.
I use it also for my 2.4 kernels. What should I do ?? updated my
modultils to use modprobe-25. It looks like it doesn't support probeall
yet. Do I change all probeall for simple probes ?
The idea of compiliing most of the modules into the kernel doesn't
appeal to me that much.
Is there any known workaround ?
Please cc me as I did not suscribe yet.
-anthony
---------------------------------------------------------
[FT] France Techno Web Mail - http://www.france-techno.com
next reply other threads:[~2003-07-14 5:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 5:28 lich [this message]
2003-07-14 6:01 ` Rahul Karnik
-- strict thread matches above, loose matches on Subject: below --
2003-07-13 13:50 Anthony Lichnewsky
2003-07-13 21:12 ` Dave Jones
2003-07-14 2:42 ` Horst von Brand
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=1058160485.3f123f65da7fa@www.france-techno.com \
--to=lich@tuxfamily.org \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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
all inboxes | Powered by JetHome®