Re: [Leaf-user] dachstein CD v1.0.1 hangs during boot

2001-11-19 Thread Jack Coates

Don't you need to have support for serial console in the kernel as well?

Oh...
http://lrp.steinkuehler.net/files/kernels/Dachstein-normal/normal.config
CONFIG_SERIAL_CONSOLE=y

Well there you go then :-)

Dropping my Dachstein CD in for some VMWare work right now...

On Mon, 19 Nov 2001, Charles Steinkuehler wrote:

> > it all works now.  thanks again. one lingering question: is there a way to
> configure
> > a serial console when you boot from CD rather than from a floppy?
>
> You can simply add a serial console entry to /etc/inittab, and you'll get a
> serial console.  Of course, without changing your syslinux configuration
> (and kernel command line in the process) you won't see boot messages on the
> serial console, but it will work once the system is running.  If you have to
> see boot messges, you'll need to burn a new CD, using a modified
> bootdisk.bin.
>
> Charles Steinkuehler
> http://lrp.steinkuehler.net
> http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
>
>
>
> ___
> Leaf-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/leaf-user
>

-- 
Jack Coates
Monkeynoodle: A Scientific Venture...


___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user



Re: [Leaf-user] dachstein CD v1.0.1 hangs during boot

2001-11-19 Thread Charles Steinkuehler

> it all works now.  thanks again. one lingering question: is there a way to
configure
> a serial console when you boot from CD rather than from a floppy?

You can simply add a serial console entry to /etc/inittab, and you'll get a
serial console.  Of course, without changing your syslinux configuration
(and kernel command line in the process) you won't see boot messages on the
serial console, but it will work once the system is running.  If you have to
see boot messges, you'll need to burn a new CD, using a modified
bootdisk.bin.

Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)



___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user



Re: [Leaf-user] dachstein CD v1.0.1 hangs during boot

2001-11-18 Thread Mark T. Kennedy

"Mark T. Kennedy" wrote:
> 
> Charles Steinkuehler wrote:
> >
> > So what's going on?  Your system is *NOT* hung, it just looks that way.  The
> > console is running on your KB/Monitor, which you have disconnected.  The
> > default system doesn't have entries in /etc/inittab to bring up a console on
> > the serial port, so once your system is actually 'running', and out of the
> > init process (which uses the kernels definition of the console device), you
> > don't have a way to login.
> >
> 
> can you tell that i'm old?  weary?  that my in-laws are visiting this weekend?  sigh.
> i completely forgot that i have to start a getty.  double sigh.  and thanks.
> 
> /mark

it all works now.  thanks again. one lingering question: is there a way to configure
a serial console when you boot from CD rather than from a floppy?

/mark


begin:vcard 
n:Kennedy;Mark
x-mozilla-html:TRUE
org:The Kennedy Family
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
x-mozilla-cpt:;-19168
fn:Mark Kennedy
end:vcard



Re: [Leaf-user] dachstein CD v1.0.1 hangs during boot

2001-11-17 Thread Mark T. Kennedy

Charles Steinkuehler wrote:
> 
> So what's going on?  Your system is *NOT* hung, it just looks that way.  The
> console is running on your KB/Monitor, which you have disconnected.  The
> default system doesn't have entries in /etc/inittab to bring up a console on
> the serial port, so once your system is actually 'running', and out of the
> init process (which uses the kernels definition of the console device), you
> don't have a way to login.
> 

can you tell that i'm old?  weary?  that my in-laws are visiting this weekend?  sigh.
i completely forgot that i have to start a getty.  double sigh.  and thanks.

/mark


begin:vcard 
n:Kennedy;Mark
x-mozilla-html:TRUE
org:The Kennedy Family
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
x-mozilla-cpt:;-19168
fn:Mark Kennedy
end:vcard



Re: [Leaf-user] dachstein CD v1.0.1 hangs during boot

2001-11-17 Thread Charles Steinkuehler

> i pulled a copy of modules.lrp off the CD, added my driver entries,
> and dropped it on the floppy.  it found & configured the network
> cards, but it hung at exactly the same place while booting.
>
> the box has no monitor/keyboard and i modifed syslinux.cfg to turn
> on the serial console.  other than that and the modules.lrp change
> described above, it is vanilla.

Ah-Ha!

> i've attached a copy of the console log.  any idea what runs
> after the network_misc script?

Not much...on a handy test system:

# ls /etc/rc2.d/ -1
S00sysklogd
S02netstd_init
S03netbase
S10ssh
S10watchdog
S15cron
S16rmnologin
S30dhcpd
S30netstd_misc
S55vpn-ssh
S60dnscache

So the only thing running after netstd_misc is stuff from packages you're
not loading (ssh and dnscache).

So what's going on?  Your system is *NOT* hung, it just looks that way.  The
console is running on your KB/Monitor, which you have disconnected.  The
default system doesn't have entries in /etc/inittab to bring up a console on
the serial port, so once your system is actually 'running', and out of the
init process (which uses the kernels definition of the console device), you
don't have a way to login.

You need to temporarily hook up a KB/Monitor to your system, edit
/etc/inittab to create a console on one (or more) of your serial ports and
verify everything works.  Then you can pull the KB/Monitor, and leave them
disconnected.  NOTE:  You will likely also have to edit a couple other
files...see my serial-HOWTO for details:
http://lrp.steinkuehler.net/Documentation/LRP-Serial-HOWTO.txt

Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)



___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user



Re: [Leaf-user] dachstein CD v1.0.1 hangs during boot

2001-11-17 Thread Mark T. Kennedy

Charles Steinkuehler wrote:
> 
> > it is an old dell 166MHz box with 64M of ram.  any way to tell it to load
> > specific modules from the boot command line?
> 
> Your system should be OK...I typically run old Pentium 133/166 systems with
> 32 megs (old gateway systems with SDRAM support), and 64 megs is more then
> enough RAM.
> 
> There's no way to load specific modules from the command line, but you *CAN*
> use your modules.lrp file from your floppy disk.  The CD system is setup to
> load modules directly from the CD, but it can use the floppy version (with
> the modules in /lib/modules) as well.  I can't understand what would hang if
> you don't have NIC modules loaded, however.  I boot this way all the time
> when testing, and have never had the system hang...
> 
> Charles Steinkuehler
> http://lrp.steinkuehler.net
> http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)

i pulled a copy of modules.lrp off the CD, added my driver entries,
and dropped it on the floppy.  it found & configured the network
cards, but it hung at exactly the same place while booting.

the box has no monitor/keyboard and i modifed syslinux.cfg to turn
on the serial console.  other than that and the modules.lrp change
described above, it is vanilla.

i've attached a copy of the console log.  any idea what runs
after the network_misc script?

/mark


Linux version 2.2.19 (root@debian) (gcc version 2.7.2.3) #5 Fri Aug 17 13:21:56 CDT 
2001
BIOS-provided physical RAM map:
 BIOS-e820: 0009f000 @  (usable)
 BIOS-e820: 03f0 @ 0010 (usable)
Detected 166194 kHz processor.
Console: mono EGA+ 80x25
Calibrating delay loop... 331.77 BogoMIPS
Memory: 62264k/65536k available (1112k kernel code, 412k reserved, 964k data, 52k init)
Dentry hash table entries: 8192 (order 4, 64k)
Buffer cache hash table entries: 65536 (order 6, 256k)
Page cache hash table entries: 16384 (order 4, 64k)
CPU: Intel Pentium 75 - 200 stepping 0c
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
Intel Pentium with F0 0F bug - workaround enabled.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfc9d1
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 65536 bhash 65536)
Linux IP multicast router 0.06 plus PIM-SM
klips_info:ipsec_init: KLIPS startup, FreeS/WAN IPSec version: 1.91
early initialization of device ipsec0 is deferred
early initialization of device ipsec1 is deferred
early initialization of device ipsec2 is deferred
early initialization of device ipsec3 is deferred
Initializing RT netlink socket
Starting kswapd v 1.5 
Detected PS/2 Mouse Port.
Serial driver version 4.27 with<4>keyboard: Timeout - AT keyboard not present?
keyboard: Timeout - AT keyboard not present?
 MANY_PORTS MULTIPORT SHARE_IRQ enabled
ttyS01 at 0x02f8 (irq = 3) is a 16550A
ttyS02 at 0x03e8 (irq = 4) is a 16550A
Software Watchdog Timer: 0.05, timer margin: 60 sec
Real Time Clock Driver v1.09
RAM disk driver initialized:  16 RAM disks of 12288K size
PIIX: IDE controller on PCI bus 00 dev 38
PIIX: not 100% native mode: will probe irqs later
PIIX: neither IDE port enabled (BIOS)
hda: DC5-E6, ATAPI CDROM drive
ide2: ports already in use, skipping probe
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
   8regs :   171.831 MB/sec
   32regs:   130.683 MB/sec
using fastest function: 8regs (171.831 MB/sec)
NET4: Ethernet Bridge 007 for NET4.0
early initialization of device brg0 is deferred
brg0: network interface for Ethernet Bridge 007/NET4.0
brg0: generated MAC address FE:FD:06:00:93:0D
brg0: attached to bridge instance 0
md.c: sizeof(mdp_super_t) = 4096
Partition check:
RAMDISK: Compressed image found at block 0
RAMDISK: Uncompressing root archive: done.
RAMDISK: Auto Filesystem - minix: 4096i 12288bk 133fdz(133) 1024zs 2147483647ms
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (minix filesystem).
RAMDISK: Extracting root archive: done.
LINUXRC: Linux Router Project - Root v4.0.1
hda: ATAPI 6X CD-ROM drive, 256kB Cache
Uniform CD-ROM driver Revision: 3.11
Root Device: ram0

LINUXRC: Installing...
  etc: /dev/hda
  ramlog: /dev/hda
  local: /dev/hda
  modules: /dev/hda /dev/fd0
LINUXRC: Finished
autodetecting RAID arrays
autorun ...
... autorun DONE.
Freeing unused kernel memory: 52k freed
INIT: version 2.78 booting
Activating swap...
Loading modules: 
pci-scan - 8390 - ne2k-pci - ne2k-pci.c:v1.01a 10/4/2000 D. Becker/P. Gortmaker
  http://www.scyld.com/network/ne2k-pci.html
eth0: RealTek RTL-8029 found at 0xff80, IRQ 10, 00:80:C6:F4:0F:05.
rtl8139 - rtl8139.c:v1.12 9/14/2000 Donald Becker, 

Re: [Leaf-user] dachstein CD v1.0.1 hangs during boot

2001-11-17 Thread Charles Steinkuehler

> it is an old dell 166MHz box with 64M of ram.  any way to tell it to load
> specific modules from the boot command line?

Your system should be OK...I typically run old Pentium 133/166 systems with
32 megs (old gateway systems with SDRAM support), and 64 megs is more then
enough RAM.

There's no way to load specific modules from the command line, but you *CAN*
use your modules.lrp file from your floppy disk.  The CD system is setup to
load modules directly from the CD, but it can use the floppy version (with
the modules in /lib/modules) as well.  I can't understand what would hang if
you don't have NIC modules loaded, however.  I boot this way all the time
when testing, and have never had the system hang...

Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)



___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user



Re: [Leaf-user] dachstein CD v1.0.1 hangs during boot

2001-11-17 Thread Mark T. Kennedy

Charles Steinkuehler wrote:
> 
> > INIT: Entering runlevel: 2
> > Starting system log daemon: syslogd klogd.
> > Starting base networking daemons: inetd.
> > Starting software watchdog... done.
> > Starting periodic command scheduler: cron.
> > Starting additional networking services:.
> > -
> >
> > and that is the last thing it says.  my dachstein floppy config used
> > the modules pciscan, rtl8139, 8390, and ne2k-pci and worked without a
> > problem.
> >
> > thoughts/comments?
> 
> Looks like it's booting properly, but something is obviously going
> wrong...how much memory do you have?  The CD kind of assumes you've got a
> fair amount of RAM, creating a 12 Meg /dev/ram0 and a 4 meg /dev/ram1 by
> default, so you need something like 20Meg+ to actually run...I typically put
> 32 Meg in my systems.  Saddly, if you need to lower (or raise) the size of
> the initial ramdisk, you have to either boot from floppy, or burn a new CD
> image, with a modified bootdisk.bin (so you can pass new parameters to the
> kernel when it boots).
> 
> Charles Steinkuehler
> http://lrp.steinkuehler.net
> http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)

it is an old dell 166MHz box with 64M of ram.  any way to tell it to load
specific modules from the boot command line?

/mark


begin:vcard 
n:Kennedy;Mark
x-mozilla-html:TRUE
org:The Kennedy Family
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
x-mozilla-cpt:;-19168
fn:Mark Kennedy
end:vcard



Re: [Leaf-user] dachstein CD v1.0.1 hangs during boot

2001-11-17 Thread Charles Steinkuehler

> INIT: Entering runlevel: 2
> Starting system log daemon: syslogd klogd.
> Starting base networking daemons: inetd.
> Starting software watchdog... done.
> Starting periodic command scheduler: cron.
> Starting additional networking services:.
> -
>
> and that is the last thing it says.  my dachstein floppy config used
> the modules pciscan, rtl8139, 8390, and ne2k-pci and worked without a
> problem.
>
> thoughts/comments?

Looks like it's booting properly, but something is obviously going
wrong...how much memory do you have?  The CD kind of assumes you've got a
fair amount of RAM, creating a 12 Meg /dev/ram0 and a 4 meg /dev/ram1 by
default, so you need something like 20Meg+ to actually run...I typically put
32 Meg in my systems.  Saddly, if you need to lower (or raise) the size of
the initial ramdisk, you have to either boot from floppy, or burn a new CD
image, with a modified bootdisk.bin (so you can pass new parameters to the
kernel when it boots).

Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)



___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user