[parisc-linux] booting on 712/60

[parisc-linux] booting on 712/60

[James Waterhouse]

Hello,
	I just compiled a ramdisk using mondays cvs src for everything. I'm
using the graphics console ramdisk file off the puffin.external.hp.com
(ramdisk20000530-sticon.tgz) to make the ramdisk. Now when I got to boot
it boots up until the point where the kernel says...

Sending BOOTP request.... OK
IP-Config: Got BOOTP answer.. bla bla
Switching from PDC console

And then I get nothing. So what is happening when we switch from the PDC
console? Is the output going to the serial port, or am I crashing
because my graphics hardware is not supported, or am I crashing for some
other reason?

Thanks,
James


-- 
Can you discern the signs of the times? || www.danielrevelation.com
Do you see the storm fast approaching?  || www.sundaylaw.com
Is your future built on "The Rock"?     ||
www.bibleinfo.com/sc/toc_sc.html

Re: [parisc-linux] booting on 712/60

[Helge Deller]

Hello James,

Am Wednesday 18 October 2000 09:03 schrieb James Waterhouse:
> Hello,
> 	I just compiled a ramdisk using mondays cvs src for everything. I'm
> using the graphics console ramdisk file off the puffin.external.hp.com
> (ramdisk20000530-sticon.tgz) to make the ramdisk. Now when I got to boot
> it boots up until the point where the kernel says...
>
> Sending BOOTP request.... OK
> IP-Config: Got BOOTP answer.. bla bla
> Switching from PDC console
>
> And then I get nothing. So what is happening when we switch from the PDC
> console? Is the output going to the serial port, or am I crashing
> because my graphics hardware is not supported, or am I crashing for some
> other reason?

I'm seeing the same here. The kernel switches independend of your 
kernel-settings (STI-Console - no STI-Console) to serial-console and just 
puts some of it's error-messages to the STI-console. 
If you don't have a nullmodem cable, you could try to ping/telnet your 
parisc, to see if it's still alive.
I currently don't know which change in CVS disallowed us to use just 
STI-Console, but will try to figure out later today. 

Helge.
 
>
> Thanks,
> James

Re: [parisc-linux] booting on 712/60

[David Huggins-Daines]

Helge Deller <deller@gmx.de> writes:

> I'm seeing the same here. The kernel switches independend of your 
> kernel-settings (STI-Console - no STI-Console) to serial-console and just 
> puts some of it's error-messages to the STI-console. 
> If you don't have a nullmodem cable, you could try to ping/telnet your 
> parisc, to see if it's still alive.
> I currently don't know which change in CVS disallowed us to use just 
> STI-Console, but will try to figure out later today. 

Very strange, because it worked for me.  But perhaps I had a magical
combination of .config settings that eludes others.

Of course sticon and the keyboard driver are so broken that I have a
hard time imagining that anyone is actually using them for serious
work, so I don't feel a great urgency here.

I will look into it now if it's not already fixed.

-- 
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [parisc-linux] booting on 712/60

[David Huggins-Daines]

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

David Huggins-Daines <dhd@linuxcare.com> writes:

> Helge Deller <deller@gmx.de> writes:
> 
> > I'm seeing the same here. The kernel switches independend of your 
> > kernel-settings (STI-Console - no STI-Console) to serial-console and just 
> > puts some of it's error-messages to the STI-console. 
> > If you don't have a nullmodem cable, you could try to ping/telnet your 
> > parisc, to see if it's still alive.
> > I currently don't know which change in CVS disallowed us to use just 
> > STI-Console, but will try to figure out later today. 
> 
> Very strange, because it worked for me.  But perhaps I had a magical
> combination of .config settings that eludes others.

Well, I can't reproduce this on my 712/80 with either sticon or stifb.
I've attached my .config for sticon.


[-- Attachment #2: config --]
[-- Type: text/plain, Size: 7102 bytes --]

#
# Automatically generated make config: don't edit
#
CONFIG_PARISC=y
# CONFIG_UID16 is not set

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# General options
#
# CONFIG_SMP is not set
# CONFIG_KWDB is not set
CONFIG_GSC=y
CONFIG_IOMMU_CCIO=y
CONFIG_GSC_LASI=y
CONFIG_PCI=y
CONFIG_GSC_DINO=y
# CONFIG_PCI_LBA is not set

#
# Loadable module support
#
# CONFIG_MODULES is not set

#
# General setup
#
CONFIG_NET=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_BINFMT_SOM=y
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_BINFMT_JAVA is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_LVM is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y

#
# Networking options
#
# CONFIG_PACKET is not set
# CONFIG_NETLINK is not set
# CONFIG_NETFILTER is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_PNP=y
CONFIG_IP_PNP_BOOTP=y
# CONFIG_IP_PNP_RARP is not set
# CONFIG_IP_ROUTER is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_ALIAS is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set

#
#  
#
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# SCSI support
#
CONFIG_SCSI=y

#
# SCSI support type (disk, tape, CDrom)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set

#
# SCSI low-level drivers
#
CONFIG_SCSI_LASI=y
CONFIG_SCSI_ZALON=y
CONFIG_SCSI_SYM53C8XX=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
# CONFIG_SCSI_NCR53C8XX_PROFILE is not set
# CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_LASI_82596=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_NET_SB1000 is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_CS89x0 is not set
# CONFIG_DE4X5 is not set
CONFIG_TULIP=y
# CONFIG_DGRS is not set
# CONFIG_DM9102 is not set
# CONFIG_EEPRO100 is not set
# CONFIG_LNE390 is not set
# CONFIG_NE3210 is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_RTL8129 is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_ES3210 is not set
# CONFIG_EPIC100 is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_YELLOWFIN is not set
# CONFIG_ACENIC is not set
# CONFIG_SK98LIN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_GSC_PS2=y
CONFIG_HIL=y
CONFIG_SERIAL=y
# CONFIG_SERIAL_CONSOLE is not set
CONFIG_SERIAL_GSC=y
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256

#
# I2C support
#
# CONFIG_I2C is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_MOUSE is not set

#
# Joysticks
#
# CONFIG_JOYSTICK is not set
# CONFIG_QIC02_TAPE is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_GENRTC is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set

#
# Video For Linux
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_FAT_FS is not set
# CONFIG_MSDOS_FS is not set
# CONFIG_UMSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_RAMFS is not set
CONFIG_ISO9660_FS=y
# CONFIG_JOLIET is not set
# CONFIG_MINIX_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_SYSV_FS_WRITE is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_ROOT_NFS=y
# CONFIG_NFSD is not set
# CONFIG_NFSD_V3 is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_MOUNT_SUBDIR is not set
# CONFIG_NCPFS_NDS_DOMAINS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_NLS is not set

#
# Sound Drivers
#
# CONFIG_SOUND is not set

#
# Console drivers
#

#
# Frame-buffer support
#
# CONFIG_FB is not set
CONFIG_STI_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y

#
# Kernel hacking
#
CONFIG_MAGIC_SYSRQ=y

[-- Attachment #3: Type: text/plain, Size: 89 bytes --]


-- 
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [parisc-linux] booting on 712/60

[Grant Grundler]

James Waterhouse wrote:
> Hello,
> 	I just compiled a ramdisk using mondays cvs src for everything. I'm
> using the graphics console ramdisk file off the puffin.external.hp.com
> (ramdisk20000530-sticon.tgz) to make the ramdisk. Now when I got to boot
> it boots up until the point where the kernel says...

iirc, ramdisk20000530-sticon.tgz uses a "kluge" /dev/tty major/minor number.
I was reading old mail on this and the kluge to use a different
major/minor confused me. I was told this was no longer needed.
So you can use a newer/regular ramdisk.

Mathew Wilcox posted the "how-to" on ramdisk:
    http://puffin.external.hp.com/mailing-lists/parisc-linux/2000/01-Jan/0078.html

grant

Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253

Re: [parisc-linux] booting on 712/60

[David Huggins-Daines]

Grant Grundler <grundler@cup.hp.com> writes:

> James Waterhouse wrote:
> > Hello,
> > 	I just compiled a ramdisk using mondays cvs src for everything. I'm
> > using the graphics console ramdisk file off the puffin.external.hp.com
> > (ramdisk20000530-sticon.tgz) to make the ramdisk. Now when I got to boot
> > it boots up until the point where the kernel says...
> 
> iirc, ramdisk20000530-sticon.tgz uses a "kluge" /dev/tty major/minor number.
> I was reading old mail on this and the kluge to use a different
> major/minor confused me. I was told this was no longer needed.
> So you can use a newer/regular ramdisk.

Ah!  Actually that triggers my memory.  You *must* append
'console=tty' to the kernel command line in order to use sticon (or
probably fbcon too for that matter), or else it will default to
serial.

Usually the PALO makefile handles this for you though.

-- 
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [parisc-linux] booting on 712/60

[Helge Deller]

Am Wednesday 18 October 2000 19:04 schrieb David Huggins-Daines:
> Grant Grundler <grundler@cup.hp.com> writes:
> 
> > James Waterhouse wrote:
> > > Hello,
> > > 	I just compiled a ramdisk using mondays cvs src for everything. I'm
> > > using the graphics console ramdisk file off the puffin.external.hp.com
> > > (ramdisk20000530-sticon.tgz) to make the ramdisk. Now when I got to boot
> > > it boots up until the point where the kernel says...
> > 
> > iirc, ramdisk20000530-sticon.tgz uses a "kluge" /dev/tty major/minor 
number.
> > I was reading old mail on this and the kluge to use a different
> > major/minor confused me. I was told this was no longer needed.
> > So you can use a newer/regular ramdisk.
> 
> Ah!  Actually that triggers my memory.  You *must* append
> 'console=tty' to the kernel command line in order to use sticon (or
> probably fbcon too for that matter), or else it will default to
> serial.
> 
> Usually the PALO makefile handles this for you though.

Yeah, that was the problem ! I just found it too !
(And you need to enable getty in /etc/inittab).

Thanks,
Helge

> 
> -- 
> dhd@linuxcare.com, http://www.linuxcare.com/
> Linuxcare. Support for the revolution.
> 
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.

Re: [parisc-linux] booting on 712/60

[James Waterhouse]

Hello Helge,

Helge Deller wrote:
> 
> Am Wednesday 18 October 2000 19:04 schrieb David Huggins-Daines:
> > Grant Grundler <grundler@cup.hp.com> writes:
> >
> > > James Waterhouse wrote:
> > > > Hello,
> > > >   I just compiled a ramdisk using mondays cvs src for everything. I'm
> > > > using the graphics console ramdisk file off the puffin.external.hp.com
> > > > (ramdisk20000530-sticon.tgz) to make the ramdisk. Now when I got to boot
> > > > it boots up until the point where the kernel says...
> > >
> > > iirc, ramdisk20000530-sticon.tgz uses a "kluge" /dev/tty major/minor
> number.
> > > I was reading old mail on this and the kluge to use a different
> > > major/minor confused me. I was told this was no longer needed.
> > > So you can use a newer/regular ramdisk.
> >
> > Ah!  Actually that triggers my memory.  You *must* append
> > 'console=tty' to the kernel command line in order to use sticon (or
> > probably fbcon too for that matter), or else it will default to
> > serial.
> >
> > Usually the PALO makefile handles this for you though.
> 
> Yeah, that was the problem ! I just found it too !
> (And you need to enable getty in /etc/inittab).

So what did you do to get it to work? You gave 'console=tty' to the
kernel command line? Where is it that you give the command line? Do you
have to modify a make file or what? Or are you just running palo/palo
with args as given in the palo doc? Which ramdisk did you have to modify
inittab in?

Jame




> 
> Thanks,
> Helge
> 
> >
> > --
> > dhd@linuxcare.com, http://www.linuxcare.com/
> > Linuxcare. Support for the revolution.
> >
> > ---------------------------------------------------------------------------
> > To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> > `unsubscribe' as the subject.
> 
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.

-- 
Can you discern the signs of the times? || www.danielrevelation.com
Do you see the storm fast approaching?  || www.sundaylaw.com
Is your future built on "The Rock"?     ||
www.bibleinfo.com/sc/toc_sc.html

Re: [parisc-linux] booting on 712/60

[Helge Deller]

Am Wednesday 18 October 2000 23:13 schrieb James Waterhouse:
> Hello Helge,
> 
> Helge Deller wrote:
> > 
> > Am Wednesday 18 October 2000 19:04 schrieb David Huggins-Daines:
> > > Grant Grundler <grundler@cup.hp.com> writes:
> > >
> > > > James Waterhouse wrote:
> > > > > Hello,
> > > > >   I just compiled a ramdisk using mondays cvs src for everything. 
I'm
> > > > > using the graphics console ramdisk file off the 
puffin.external.hp.com
> > > > > (ramdisk20000530-sticon.tgz) to make the ramdisk. Now when I got to 
boot
> > > > > it boots up until the point where the kernel says...
> > > >
> > > > iirc, ramdisk20000530-sticon.tgz uses a "kluge" /dev/tty major/minor
> > number.
> > > > I was reading old mail on this and the kluge to use a different
> > > > major/minor confused me. I was told this was no longer needed.
> > > > So you can use a newer/regular ramdisk.
> > >
> > > Ah!  Actually that triggers my memory.  You *must* append
> > > 'console=tty' to the kernel command line in order to use sticon (or
> > > probably fbcon too for that matter), or else it will default to
> > > serial.
> > >
> > > Usually the PALO makefile handles this for you though.
> > 
> > Yeah, that was the problem ! I just found it too !
> > (And you need to enable getty in /etc/inittab).
> 
> So what did you do to get it to work? You gave 'console=tty' to the
> kernel command line? Where is it that you give the command line? Do you
> have to modify a make file or what? Or are you just running palo/palo
> with args as given in the palo doc? Which ramdisk did you have to modify
> inittab in?
> 
> Jame
> 

Hi James,

Here are some hints:

1. I'm using no ramdisk, but the nfsroot-20001009.tgz, which you can get from 
ftp://puffin.external.hp.com/pub/parisc/binaries/nfsroot/
This has the great advantage, that you can modify all configuration files 
without the need to build a new kernel for every change - but you will need 
to setup one of your machines as nfs-server and export that directory.
More than that, the ramdisks on puffin.external.hp.com are mostly outdated !

2. Take a look at the documention in palo/Makefile. 
There I modified the NFSROOT = 10.10.10.2 to
NFSROOT = 192.168.100.100:/tftpboot/nfsroot    with 192.168.100.100 as the 
IP-address of my local nfs-server and the contents of nfsroot-20001009.tgz in 
/tftpboot/nfsroot.

3. Follow the hints from Thomas Marteau (copied from his mail):

>cat /etc/inittab (! just the interesting thing!)
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
#  <id>:<runlevels>:<action>:<process>
1:2345:respawn:/sbin/getty 38400 tty1
#2:23:respawn:/sbin/getty 38400 tty2
#3:23:respawn:/sbin/getty 38400 tty3
#4:23:respawn:/sbin/getty 38400 tty4
#5:23:respawn:/sbin/getty 38400 tty5
#6:23:respawn:/sbin/getty 38400 tty6

>cat /etc/securetty
# /etc/securetty: list of terminals on which root is allowed to login.
# See securetty(5) and login(1).
ttyS0
tty1


Helge.