I have a new Asus A7N8X Deluxe mobo and an 80GB Seagate SATA hard drive.
I booted from a Slack 9.1 iso that I made (md5 check passed) and the
install seemed to go through ok but I'm having trouble getting it to
boot. I have the BIOS set to boot from SCSI which appears to be the
right choice for the SATA drive.

The SATA drive shows up as /dev/hde. I have 1GB swap on /dev/hde1, 1GB
/boot on /dev/hde2 and the rest as / on /dev/hde3 using ext3 for both /
and /boot.

The install completed as I said, and it gets a good ways through booting
before it dies. The last two lines displayed are:

Warning: unable to open iniial console.
Kernel panic: No init found. try passing init= option to kernel.

I've tried a number of the kernels from the CD to no avail, and looked
without success in the docs and google for what init options to try. Can
someone point me in the right direction ?

DB

In article <vue88kmtq4qj05@corp.supernews.com>, DB wrote:
> boot. I have the BIOS set to boot from SCSI which appears to be the
> right choice for the SATA drive.

Seems so.

> The SATA drive shows up as /dev/hde. I have 1GB swap on /dev/hde1, 1GB
> /boot on /dev/hde2 and the rest as / on /dev/hde3 using ext3 for both /
> and /boot.

I know you're not asking about this, but since you posted I can comment
on it. That's odd partitioning. /boot, if separated out, is normally
very small. I feel wasteful when making a 50MB /boot partition, as each
kernel image is only about 1.5MB, and I seldom would have more than 3-4
of those. I use ext2 for my /boot partitions; journalling is a waste of
space and not beneficial on /boot.

If I only separate one filesystem off /, it would be /home. Some people
would say /usr/local, and depending on the use of the machine, that can
be a good idea. (You can get the benefit of both approaches through the
magic of /bin/ln.

> Warning: unable to open iniial console.
> Kernel panic: No init found. try passing init= option to kernel.
>
> I've tried a number of the kernels from the CD to no avail, and looked
> without success in the docs and google for what init options to try. Can

That's because init= options will not solve the problem. Your kernel is
mounting a root filesystem which has no /dev/console nor /sbin/init. It
could be that your LILO is misconfigured with "root=/dev/hde2", or that
your install on /dev/hde3 is missing vital components.

Boot the CD, mount /dev/hde3 at /mnt and /dev/hde2 at /mnt/boot, correct
any issues in /mnt/etc/lilo.conf, then run "lilo -v -r /mnt". Or, if the
previous install failed for some reason, just redo the setup. Good luck.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

/dev/rob0 wrote:
> In article <vue88kmtq4qj05@corp.supernews.com>, DB wrote:

>>
>>I've tried a number of the kernels from the CD to no avail, and looked
>>without success in the docs and google for what init options to try. Can
>
>
> That's because init= options will not solve the problem. Your kernel is
> mounting a root filesystem which has no /dev/console nor /sbin/init. It
> could be that your LILO is misconfigured with "root=/dev/hde2", or that
> your install on /dev/hde3 is missing vital components.
>
> Boot the CD, mount /dev/hde3 at /mnt and /dev/hde2 at /mnt/boot, correct
> any issues in /mnt/etc/lilo.conf, then run "lilo -v -r /mnt". Or, if the
> previous install failed for some reason, just redo the setup. Good luck.

Yep as ususal I figured it out shortly after posting. That happens every
time no matter how much digging I do prior to posting. I must have had
something misconfigured. I rethought the partitioning and used just a
swap at the end and kept the rest as one partition. I've done that many
times before and don't ever recall being sorry. Anyway it works well now
and my next step is to enable the onboard SATA RAID (RAID1 in my case)
as soon as the second SATA/IDE power adapter arrives The Asus A7N8X
Deluxe seems to be a very nice board for a server with two onboard NICS.
Seems a shame to not be using the onboad Dolby surround sound . BTW
this board talks thu the onboard sound card when it boots instead of
beeping.

DB

In alt.os.linux.slackware, DB dared to utter,
> Seems a shame to not be using the onboad Dolby surround sound . BTW
> this board talks thu the onboard sound card when it boots instead of
> beeping.

That's messed up! What if you don't have speakers, or the onboard sound
card dies, or the power isn't plugged up for your speakers on boot-up?
I'd hate to have to hook up external speakers to my sound card just to
debug the motherboard. I'd bitch to the manufacturer about that.

--
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

Alan Hicks wrote:
> In alt.os.linux.slackware, DB dared to utter,
>
>>Seems a shame to not be using the onboad Dolby surround sound . BTW
>>this board talks thu the onboard sound card when it boots instead of
>>beeping.
>
>
> That's messed up! What if you don't have speakers, or the onboard sound
> card dies, or the power isn't plugged up for your speakers on boot-up?
> I'd hate to have to hook up external speakers to my sound card just to
> debug the motherboard. I'd bitch to the manufacturer about that.
>

Don't worry... it can be set to beep, or to talk. I think the talking is
kinda neat but once the server is in place there will be no speaker
conneceted.

DB

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On 23 Dec 2003 13:23:03 -0600, Alan Hicks <1001298936@ettin.custom-consulting.com> wrote:
> That's messed up! What if you don't have speakers, or the onboard sound
> card dies, or the power isn't plugged up for your speakers on boot-up?
> I'd hate to have to hook up external speakers to my sound card just to
> debug the motherboard. I'd bitch to the manufacturer about that.

AFAIK, it uses an onboard speaker. If not, headphones and computer
speakers are very cheap.

Such a thing is useful for hardware diagnostics. If you've never
ordered all the parts for a system, assembled them, then had the system
not power up, you may not realize BIOS beep codes just plain *SUCK* ...
they're never the same from one manufacturer to another and only about
*three* are documented *anywhere*....

A speaking setup makes far more sense... no cryptic beeps to decipher.
If the built-in sound chip fails, odds are more than just that has
failed on the board... it's a bit rare to have half a motherboard die
while the other half functions properly.

Without this, how are you going to debug the board at all?

--
Rob | If not safe,
Email and Jabber: | one can never be free.
athlonrob at axpr dot net |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/6KbQhm6KEoOOAe0RAqdaAJ9DGjgy6BfAw/OTKtcWJHhURURvcgCgtO2K
HOqa4GM7s1leKTVITGax5v0=
=jBkh
-----END PGP SIGNATURE-----

AthlonRob <junkmail@axpr.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> NotDashEscaped: You need GnuPG to verify this message

pgp trash troll delete

> AFAIK, it uses an onboard speaker. If not, headphones and
> computer speakers are very cheap.

Perhaps if pgp wasn't free you would be a bit more careful about
how you use it. Not only is your use of pgp unwarranted, but it
violates usenet standards of netiquette. Please show some respect
for the other posters in this ng by refraining from the unwarranted
use of inline pgp.

Thank you.

cordially, as always,

rm