Re: Linux auf 2. Platte booten: unable to open initial console
* Gregor Zattler [EMAIL PROTECTED] [06-03-02 20:52]: /dev/hdd, kriege ich als letzte Meldung des kernels beim booten: unable to open initial console. Kopiere mal /dev mit cp -a auf die 2.Platte. Gruss Uwe msg03287/pgp0.pgp Description: PGP signature
unable to open initial console
I am trying to install Debian 2.1 and I can't get the initial console to load. I have an old Packard Bell 486sx 16 with 8 MB of ram and a 120MB hard drive. Obviously it has no SCSI, PCI, or anything else that's up to date. The machine isn't really good for anything but familiarizing myself with Linux, which I hope it can do. I am trying to load from the DOS partition after which I intended to run fdisk etc. and complete the installation. I figured this should work because the install.bat appears to be calling a ram drive (loadlin linux root=/dev/ram initrd=root.bin). The system DOES have 128K of shadow ram which I can't disable. It gets through the device searches, mounts the root read-only, but then crashes with the above message. The S.u.S.E. support database has something about the wrong root partition but I don't know if that applies here (it seems it should work from ram). The only other errors of significance I get are the No BIOS32 extensions present. This release still depends on it. for eata_dma and eata_pio and a failure to load an NLS charset (something like cp437 - I can't remember off the top of my head). I did try the pci=off parameter but that didn't change anything. I have NO unix or linux experience, but am familiar with the DOS and windows boot processes and Linux appears to be doing a lot of the same things with different syntax. I went ahead and ran FIPS since this error and created a 20MB DOS partition with the rest dedicated to Linux. I may create a swap file later but would like to get through an install first. Is my machine hopeless or is the 2.1 kernel calling something my machine can't handle that could be disabled? Any help would be greatly appreciated.
Unable to open initial console
Hi, I´m getting this message when i was booting to install. It occurs booting with the official cdrom or from floopy disks. The message is: Unable to open inital console. Can somebody help me? Thanks, ATTENTION: Here are some of my opinions, just it. I'm not speaking for my Company. -- /\ / \/\ _Andre Luis Cardoso[EMAIL PROTECTED] /\ \ \ Akros S/A Joinville, SC, BRAZIL / \ \ \ Support Analyst Fone: +5547 461-7102 /\ \ \ Linux User 89701 Fax: +5547 461-7070 --
Unable to open initial console
Hi, I´m getting this message when i was booting to install. It occurs booting with the official cdrom or from floopy disks. The message is: Unable to open inital console. Can somebody help me? Thanks, ATTENTION: Here are some of my opinions, just it. I'm not speaking for my Company. -- /\ / \/\ _Andre Luis Cardoso[EMAIL PROTECTED] /\ \ \ Akros S/A Joinville, SC, BRAZIL / \ \ \ Support Analyst Fone: +5547 461-7102 /\ \ \ Linux User 89701 Fax: +5547 461-7070 --
Re: Unable to open initial console
I do think that this problem is related to /dev/console file. This file should exists and should be pointing to /dev/tty0 (usually.) Bye, Giuseppe Andre Luis Cardoso wrote: Hi, I´m getting this message when i was booting to install. It occurs booting with the official cdrom or from floopy disks. The message is: Unable to open inital console.
boot: unable to open initial console
I've moved my old system over to a new hard drive. I thought I was fairly meticulous in copying things over (compared all permissions, ownerships, links and other special files between the two file systems). I edited lilo.conf and fstab, then shutdown, changed the drives master/slave jumpers and rebooted from the rescue floppy. I used the install program to mount all the partitions and to mkswap. Next I switched to the console and copied my kernel to a floppy. Evidently, I have overlooked something. I only get through the first little bit of the boot sequence (I can write out the whole thing , one screen full, if anyone wants it) up to where all the partitions are named and VHS: Mounted root (ext2 filesystem) readonly. thenUnable to open an initial console Does anyone know what I need to do to fix this ? Thanks, Gerald -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: boot: unable to open initial console
G. Crimp wrote: I've moved my old system over to a new hard drive. I thought I was fairly meticulous in copying things over (compared all permissions, ownerships, links and other special files between the two file systems). I edited lilo.conf and fstab, then shutdown, changed the drives master/slave jumpers and rebooted from the rescue floppy. I used the install program to mount all the partitions and to mkswap. Next I switched to the console and copied my kernel to a floppy. Evidently, I have overlooked something. I only get through the first little bit of the boot sequence (I can write out the whole thing , one screen full, if anyone wants it) up to where all the partitions are named and VHS: Mounted root (ext2 filesystem) readonly. thenUnable to open an initial console Looks like /dev/tty0 isn't there. Are use sure you did copy the devices correctly (cp does not copy devices correctly, use tar or cpio). Dirk -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: boot: unable to open initial console
VHS: Mounted root (ext2 filesystem) readonly. thenUnable to open an initial console Looks like /dev/tty0 isn't there. Are use sure you did copy the devices correctly (cp does not copy devices correctly, use tar or cpio). Dirk Or the permissions aren't set right. I've found that when copying files from /dev, the permissions rarely stay the way they were originally Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: boot: unable to open initial console
Taren wrote: VHS: Mounted root (ext2 filesystem) readonly. thenUnable to open an initial console Looks like /dev/tty0 isn't there. Are use sure you did copy the devices correctly (cp does not copy devices correctly, use tar or cpio). Or the permissions aren't set right. I've found that when copying files from /dev, the permissions rarely stay the way they were originally They should with tar. e.g.: tar cf - . | (cd somewhere; tar xvf -) Of course, you must set umask to 000 beforehand Dirk -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: boot: unable to open initial console
In article [EMAIL PROTECTED], Dirk Bonne [EMAIL PROTECTED] wrote: They should with tar. e.g.: tar cf - . | (cd somewhere; tar xvf -) Of course, you must set umask to 000 beforehand Or use the p option with tar when you unpack i.e. tar xpvf - Mike. -- Miquel van Smoorenburg | Our vision is to speed up time, [EMAIL PROTECTED] | eventually eliminating it. * -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: boot: unable to open initial console
On Mon, Aug 03, 1998 at 02:58:58PM +0200, Dirk Bonne wrote: G. Crimp wrote: I've moved my old system over to a new hard drive. I thought I was fairly meticulous in copying things over (compared all permissions, ownerships, links and other special files between the two file systems). I edited lilo.conf and fstab, then shutdown, changed the drives master/slave jumpers and rebooted from the rescue floppy. I used the install program to mount all the partitions and to mkswap. Next I switched to the console and copied my kernel to a floppy. Evidently, I have overlooked something. I only get through the first little bit of the boot sequence (I can write out the whole thing , one screen full, if anyone wants it) up to where all the partitions are named and VHS: Mounted root (ext2 filesystem) readonly. thenUnable to open an initial console Looks like /dev/tty0 isn't there. Had a look. :( It's there. Symlink to console. Console is there, too. Permissions, ownership and major/minor numbers are exactly the same between the original and cloned tty0 and console. The only that is different is the time stamp. Thanks, Gerald -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: boot: unable to open initial console
On Mon, Aug 03, 1998 at 05:52:36PM +0200, Dirk Bonne wrote: Taren wrote: [snip] Or the permissions aren't set right. I've found that when copying files from /dev, the permissions rarely stay the way they were originally They should with tar. e.g.: tar cf - . | (cd somewhere; tar xvf -) Of course, you must set umask to 000 beforehand Actually, I tried pretty much the same command as you suggest: tar -cf - $dir | (cd /mnt; tar -xpsf -) This worked well for ordinary files and some special files, but any sockets in /dev or /var were turned into pipes. At least, the first mode bit changed from an 's' to a 'p'. I don't think the device numbers changed, but the mode bit change was enough to scare me. I used cpio in /dev and /var and it seemed to preserve everything. But I still have my Can't open initial console problem. Maybe all the device files got moved fine as far as ls -l is concerned but not on a more fundamental and functional level. Perhaps I should just cd /mnt/dev; rm * and then remake the device files. I've read about a command to make the devices. Can't remember where nor what the command was. Anyone know where to go to get info on recreating the device files ? Thanks, Gerald -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: boot: unable to open initial console
On Mon, Aug 03, 1998 at 05:58:46AM -0700, Taren wrote: VHS: Mounted root (ext2 filesystem) readonly. thenUnable to open an initial console Looks like /dev/tty0 isn't there. Are use sure you did copy the devices correctly (cp does not copy devices correctly, use tar or cpio). Dirk Or the permissions aren't set right. I've found that when copying files from /dev, the permissions rarely stay the way they were originally I'd checked that already. I used cpio to copy the dev and var directories. All mode bits and ownership are intact. Only the time stamp is different between the original and copied tty0 and console. I think more than likely the problem is somewhere else. I've copied everything over, but the partition structure is not the same between the two drives. In fact, on the old drive, there was only one partition (except for the swap of course). I've broken this down on the new disk. Also, root is partition 3 whereas it was 1 on the old disk (I'm not using the first two partitions for Debian). I'm thinking that there is some boot script that got blindly copied over to the new disk, and is still looking on hda1 from something that is now on a different partition. Kind of like if I'd forgotten to change the boot= and root= in lilo.conf I don't understand the Linux boot procedure very well, so I don't know where to start to look. Any more ideas out there? Thanks, Gerald -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: boot: unable to open initial console
There's no need to do that. Just cd /dev (or wherever your dev dir is), and type ./MAKEDEV *. That should recreate almost all the devices, with the correct permissions, afaik. Perhaps I should just cd /mnt/dev; rm * and then remake the device files. I've read about a command to make the devices. Can't remember where nor what the command was. Anyone know where to go to get info on recreating the device files ? Thanks, Gerald -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Unable to open initial console
On Sun, 7 Sep 1997, Jess Stryker wrote: : About every 1 out of 3 times my computer boots I get : a message that says something to the effect of: : Unable to open an initial console : and the boot process stops. I'm not familiar enough : with the boot process to know what might be causing : this and was unable to find anything helpful in the : booting Howto. Does anyone have any advice for me? : It's not a major problem, just annoying. Hmm, sounds familiar. I'm sure someone will come up with a solution, but I'll try to remember what my solution was. : : Information that may be related (?) or may indicate : a completely separate problem: : : Two error messages always appear in the kernels boot : records: : : Failed initialization of WD-7000 SCSI Card! I don't : have any SCSI drives on this computer (to my knowledge!). This is a device compiled into the stock kernel. Either roll your own kernel, or use a boot parameter to avoid probing the controller. : : PPA: unable to initialise controller at 0x378, error 2 : What is PPA? I believe this is the parallel port access for a ZIP drive. Same as above ... if you don't need it, get rid of it. For what it's worth, i routinely end up with a kernel that's about 62% the size of the stock kernel after i recompile. One a small machine that might make a difference. : : Hardware is: : DFI G586-IPV motherboard with Intel 430VX 512K and : AMD-K5 PR90 CPU. Award bios. : 16 mb EDO 60ns : Very old Maxtor 213MD hard drive Hey, that's more power than my dialup server!! grin : : Hopefully that's too much information, but better too : much than too little!!? : : Thanks very much for your assistance! : : Jess Stryker : : -- : Free Irrigation Tutorials on Design, Installation, and More! : -- Visit them at: -- : http://www.netyard.com/jsa/index.html -- Nathan Norman MidcoNet 410 South Phillips Avenue Sioux Falls, SD 57104 Voice: (605) 334-4454 Fax: (605) 335-1173 email: [EMAIL PROTECTED] or [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Unable to open initial console
About every 1 out of 3 times my computer boots I get a message that says something to the effect of: Unable to open an initial console and the boot process stops. I'm not familiar enough with the boot process to know what might be causing this and was unable to find anything helpful in the booting Howto. Does anyone have any advice for me? It's not a major problem, just annoying. Information that may be related (?) or may indicate a completely separate problem: Two error messages always appear in the kernels boot records: Failed initialization of WD-7000 SCSI Card! I don't have any SCSI drives on this computer (to my knowledge!). PPA: unable to initialise controller at 0x378, error 2 What is PPA? Hardware is: DFI G586-IPV motherboard with Intel 430VX 512K and AMD-K5 PR90 CPU. Award bios. 16 mb EDO 60ns Very old Maxtor 213MD hard drive Hopefully that's too much information, but better too much than too little!!? Thanks very much for your assistance! Jess Stryker -- Free Irrigation Tutorials on Design, Installation, and More! -- Visit them at: -- http://www.netyard.com/jsa/index.html -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Unable to open initial console
About every 1 out of 3 times my computer boots I get
a message that says something to the effect of:
Unable to open an initial console
and the boot process stops. I'm not familiar enough
with the boot process to know what might be causing
It's linux/init/main.c:1005
if ((open(/dev/tty1,O_RDWR,0) 0)
(open(/dev/ttyS0,O_RDWR,0) 0))
printk(Unable to open an initial console.\n);
Thus, the kernel cannot find /dev/tty{1,S0}. Now, I doubt very much
that those files appear or reappear spontaniously, so I very much
suspect that you eighter mount a different partition as root once every
3 reboots (how do you do that?), or your hardisk isn't as
reliable as it should be.
BTW, the kernel apparently does go on forking init() etc. Do
you see anything in the system logs for those failed boots?
(I guess not).
Failed initialization of WD-7000 SCSI Card! I don't
have any SCSI drives on this computer (to my knowledge!).
And that's where your root partition resides? seems like that
could be the source of your problems.
PPA: unable to initialise controller at 0x378, error 2
What is PPA?
Hardware is:
DFI G586-IPV motherboard with Intel 430VX 512K and
AMD-K5 PR90 CPU. Award bios.
16 mb EDO 60ns
Very old Maxtor 213MD hard drive
Maybe other people with Very Old Maxtor HD's will be able
to give you more info, but it seems to me that it's time
to by a new HD. (213M, how much are they, these days? $50?)
I strongly suspect that you'll see that 33% ratio go up
as time goes by, to suddenly go up to 100%. If I were you, I'd
make sure to make backups before it goes to 100%.
--
joost witteveen, [EMAIL PROTECTED]
#!/usr/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
