Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Michael Meissner]

I have two Powerstacks, one of which can boot recent Linuxes, and the
other can't.  The one that can boot 2.2.0-pre6 is the original
PowerStack with a 603 processor (67 Mhz, no cache, 48 meg of memory,
note this is a 603, not a 603e if it matters).  The one that can't is
a PowerStack-II (Net 4000/200, 200 Mhz 604e processor, 512k sync. L2
cache, 128 meg of memory).  I am able to run a version of 2.0.32 that
Gary Thomas built for me last year on both machines without problems
(though that kernel has some problems, which is why I want to run
something newer).  I did the following:

	make prep_config
	make menuconfig
	make dep clean zImage modules modules_install floppy

and tried to use the same floppy on both.  The only dialog I get on
both the screen and the com1 line are:

	loaded at:     00400400 00415FD0
	relocated to:  00600000 00615BD0
	zimage at:     0040A400 0049A889
	avail ram:     00400000 00600000

	Linux/PPC load: console=tty0 console=ttyS0,9600n8 root=/dev/sda2 mem=127M
	Uncompressing Linux...done.
	Now booting the kernel

(I typed in the root=/dev/sda2 mem=127M to the load line when it
paused to specify memory and disk).  I really, really would prefer to
run a more recent version of the kernel on the fast machine (for one
thing, the 2.0.32 kernel has a tendency to spam our network every so
often when it loses the loopback routing, and a 200 Mhz ppc can spit
out packets quite fast, thank you very much :-).

Also, I found Alan Cox's patches 2.2.0-pre6-ac1 could not build a prep
based kernel (it kept trying to build the mac adb support and
failing).

Here is the .config file I'm currently using on the slow machine (I've
tried several different config files, including common support, etc.):

#
# Automatically generated by make menuconfig: don't edit
#

#
# Platform support
#
CONFIG_PPC=y
CONFIG_6xx=y
# CONFIG_8xx is not set
# CONFIG_PMAC is not set
CONFIG_PREP=y
# CONFIG_CHRP is not set
# CONFIG_ALL_PPC is not set
# CONFIG_APUS is not set
# CONFIG_MBX is not set
CONFIG_MACH_SPECIFIC=y
# CONFIG_SMP is not set

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
CONFIG_PCI=y
# CONFIG_PCI_QUIRKS is not set
CONFIG_PCI_OLD_PROC=y
CONFIG_NET=y
CONFIG_SYSCTL=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BINFMT_ELF=y
CONFIG_KERNEL_ELF=y
CONFIG_BINFMT_MISC=y
# CONFIG_BINFMT_JAVA is not set
# CONFIG_PARPORT is not set
CONFIG_VGA_CONSOLE=y
# CONFIG_FB is not set
# CONFIG_PMAC_PBOOK is not set
# CONFIG_MAC_KEYBOARD is not set
# CONFIG_MAC_FLOPPY is not set
# CONFIG_MAC_SERIAL is not set
# CONFIG_ADBMOUSE is not set
# CONFIG_BLK_DEV_IDE_PMAC is not set
# CONFIG_PROC_DEVICETREE is not set
# CONFIG_KGDB is not set
# CONFIG_XMON is not set
# CONFIG_TOTALMP is not set
# CONFIG_BOOTX_TEXT is not set

#
# Plug and Play support
#
# CONFIG_PNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=m
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=m
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDETAPE=m
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_IDEPCI is not set
# CONFIG_BLK_DEV_SL82C105 is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_INITRD=y
# CONFIG_BLK_DEV_XD is not set
CONFIG_PARIDE_PARPORT=y
# CONFIG_PARIDE is not set
# CONFIG_BLK_DEV_HD is not set

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_NETLINK is not set
# CONFIG_FIREWALL is not set
# CONFIG_NET_ALIAS is not set
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP 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_SYN_COOKIES=y
# CONFIG_INET_RARP is not set
CONFIG_IP_NOSR=y
CONFIG_SKB_LARGE=y
# CONFIG_IPV6 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_BRIDGE 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
# CONFIG_CPU_IS_SLOW is not set

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

#
# SCSI support
#
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y

#
# SCSI low-level drivers
#
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AHA1740 is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_DMA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_NCR53C7xx is not set
CONFIG_SCSI_NCR53C8XX=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=8
CONFIG_SCSI_NCR53C8XX_SYNC=10
# CONFIG_SCSI_NCR53C8XX_PROFILE is not set
CONFIG_SCSI_NCR53C8XX_IOMAPPED=y
# CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_MESH is not set
# CONFIG_SCSI_MAC53C94 is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_EQUALIZER is not set
CONFIG_NET_ETHERNET=y
# CONFIG_MACE is not set
# CONFIG_BMAC is not set
# 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_RTL8139 is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_ACENIC is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_EISA=y
# CONFIG_PCNET32 is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_CS89x0 is not set
CONFIG_DE4X5=y
# CONFIG_DEC_ELCP is not set
# CONFIG_DGRS is not set
# CONFIG_EEXPRESS_PRO100 is not set
# CONFIG_LNE390 is not set
# CONFIG_NE3210 is not set
# CONFIG_NE2K_PCI 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_ZNET is not set
# CONFIG_NET_POCKET is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_DLCI is not set
CONFIG_PPP=m
# CONFIG_SLIP is not set
# CONFIG_NET_RADIO is not set
# CONFIG_TR is not set
CONFIG_SHAPER=m
# CONFIG_HOSTESS_SV11 is not set
# CONFIG_COSA is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# CD-ROM drivers (not for SCSI or IDE/ATAPI drives)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Console drivers
#

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_UNIX98_PTYS is not set
CONFIG_MOUSE=y

#
# Mice
#
# CONFIG_ATIXL_BUSMOUSE is not set
# CONFIG_BUSMOUSE is not set
# CONFIG_MS_BUSMOUSE is not set
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set
# CONFIG_QIC02_TAPE is not set
# CONFIG_WATCHDOG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set

#
# Video For Linux
#
# CONFIG_VIDEO_DEV is not set

#
# Joystick support
#
# CONFIG_JOYSTICK is not set

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

#
# Filesystems
#
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_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_ISO9660_FS=y
# CONFIG_JOLIET is not set
# CONFIG_MINIX_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
CONFIG_NFS_FS=y
CONFIG_NFSD=m
# CONFIG_NFSD_SUN is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_SMB_FS=m
CONFIG_SMB_WIN95=y
# CONFIG_NCP_FS is not set

#
# Partition Types
#
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MAC_PARTITION is not set
# CONFIG_SMD_DISKLABEL is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_NLS is not set

#
# Sound
#
# CONFIG_SOUND is not set

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Cort Dougan]

It looks like your zImage is being stomped on before it can be
decompressed.  I'll take a look at the boot loader code and see why it
isn't adjusting your free ram section.  You might want to try changing to
load address in the PPCBug to be near the top of memory in the mean time.


}	loaded at:     00400400 00415FD0
}	relocated to:  00600000 00615BD0
}	zimage at:     0040A400 0049A889
}	avail ram:     00400000 00600000
}
}	Linux/PPC load: console=tty0 console=ttyS0,9600n8 root=/dev/sda2 mem=127M
}	Uncompressing Linux...done.
}	Now booting the kernel


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Alois Fertl]

Cort Dougan wrote:
> 
> It looks like your zImage is being stomped on before it can be
> decompressed.  I'll take a look at the boot loader code and see why it
> isn't adjusting your free ram section.  You might want to try changing to
> load address in the PPCBug to be near the top of memory in the mean time.
I guess this system is running "PowerPC Open Firmware". You can change the
load address via the firmware menu:
  Administrative Options...
    ---> Modify the Configuration Settings...
          ---> Edit Configuration Variables
step to the parameter "load-base" and enter a new value (decimal).
One other problem is the this firmware version obviously does not provide
residual data. So Linux will probably not find the PCI devices correctly.

> 
> }       loaded at:     00400400 00415FD0
> }       relocated to:  00600000 00615BD0
> }       zimage at:     0040A400 0049A889
> }       avail ram:     00400000 00600000
> }
> }       Linux/PPC load: console=tty0 console=ttyS0,9600n8 root=/dev/sda2 mem=127M
> }       Uncompressing Linux...done.
> }       Now booting the kernel

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Cort Dougan]

It should find the pci devices.  It doesn't use residual data, it uses the
hard code table for interrupt routing.


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Michael Meissner]

On Fri, Jan 15, 1999 at 04:28:55PM +0100, Alois Fertl wrote:
> Cort Dougan wrote:
> > 
> > It looks like your zImage is being stomped on before it can be
> > decompressed.  I'll take a look at the boot loader code and see why it
> > isn't adjusting your free ram section.  You might want to try changing to
> > load address in the PPCBug to be near the top of memory in the mean time.
> I guess this system is running "PowerPC Open Firmware". You can change the
> load address via the firmware menu:
>   Administrative Options...
>     ---> Modify the Configuration Settings...
>           ---> Edit Configuration Variables
> step to the parameter "load-base" and enter a new value (decimal).
> One other problem is the this firmware version obviously does not provide
> residual data. So Linux will probably not find the PCI devices correctly.

I tried setting the load-base to various values, and all of them caused dumps
within the monitor (I tried 10 meg, 64 meg, 3 meg, 120 meg, and even 4 meg + 4
all to no avail).

Also, Gary Thomas's 2.0.32 kernel seemed to have no problem in sizing memory,
so I presume it is able to pick up the residual data.

> > 
> > }       loaded at:     00400400 00415FD0
> > }       relocated to:  00600000 00615BD0
> > }       zimage at:     0040A400 0049A889
> > }       avail ram:     00400000 00600000
> > }
> > }       Linux/PPC load: console=tty0 console=ttyS0,9600n8 root=/dev/sda2 mem=127M
> > }       Uncompressing Linux...done.
> > }       Now booting the kernel

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Cort Dougan]

His gets it from the OF.  There's no OF code used in the prep bootloader
in the current kernels.

Are you netbooting or floppy booting?

}Also, Gary Thomas's 2.0.32 kernel seemed to have no problem in sizing memory,
}so I presume it is able to pick up the residual data.


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Michael Meissner]

On Fri, Jan 15, 1999 at 03:04:30PM -0700, Cort Dougan wrote:
> His gets it from the OF.  There's no OF code used in the prep bootloader
> in the current kernels.
> 
> Are you netbooting or floppy booting?
> 
> }Also, Gary Thomas's 2.0.32 kernel seemed to have no problem in sizing memory,
> }so I presume it is able to pick up the residual data.

Floppy booting, and I've also tried installing it in /dev/sda1. 

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Alois Fertl]

What version of PowerPC Open Firmware is this?

Michael Meissner wrote:
> 
> On Fri, Jan 15, 1999 at 03:04:30PM -0700, Cort Dougan wrote:
> > His gets it from the OF.  There's no OF code used in the prep bootloader
> > in the current kernels.
> >
> > Are you netbooting or floppy booting?
> >
> > }Also, Gary Thomas's 2.0.32 kernel seemed to have no problem in sizing memory,
> > }so I presume it is able to pick up the residual data.
> 
> Floppy booting, and I've also tried installing it in /dev/sda1.
> 
> --
> Michael Meissner, Cygnus Solutions (Massachusetts office)
> 4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
> meissner@cygnus.com,    617-354-5416 (office),  617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Johnnie Peters]

I think this is the same problem I was seeing.  This machine is also the known as
the Utah.  I fixed this in arch/ppc/boot/misc.c.  Here is the diff:



Michael Meissner wrote: 454c454
<       if (( (unsigned long)zimage_start <= 0x01000000 ) && initrd_start)
---
>       if ( (unsigned long)zimage_start <= 0x01000000 )

Johnnie


> On Fri, Jan 15, 1999 at 04:28:55PM +0100, Alois Fertl wrote:
> > Cort Dougan wrote:
> > >
> > > It looks like your zImage is being stomped on before it can be
> > > decompressed.  I'll take a look at the boot loader code and see why it
> > > isn't adjusting your free ram section.  You might want to try changing to
> > > load address in the PPCBug to be near the top of memory in the mean time.
> > I guess this system is running "PowerPC Open Firmware". You can change the
> > load address via the firmware menu:
> >   Administrative Options...
> >     ---> Modify the Configuration Settings...
> >           ---> Edit Configuration Variables
> > step to the parameter "load-base" and enter a new value (decimal).
> > One other problem is the this firmware version obviously does not provide
> > residual data. So Linux will probably not find the PCI devices correctly.
>
> I tried setting the load-base to various values, and all of them caused dumps
> within the monitor (I tried 10 meg, 64 meg, 3 meg, 120 meg, and even 4 meg + 4
> all to no avail).
>
> Also, Gary Thomas's 2.0.32 kernel seemed to have no problem in sizing memory,
> so I presume it is able to pick up the residual data.
>
> > >
> > > }       loaded at:     00400400 00415FD0
> > > }       relocated to:  00600000 00615BD0
> > > }       zimage at:     0040A400 0049A889
> > > }       avail ram:     00400000 00600000
> > > }
> > > }       Linux/PPC load: console=tty0 console=ttyS0,9600n8 root=/dev/sda2 mem=127M
> > > }       Uncompressing Linux...done.
> > > }       Now booting the kernel
>
> --
> Michael Meissner, Cygnus Solutions (Massachusetts office)
> 4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
> meissner@cygnus.com,    617-354-5416 (office),  617-354-7161 (fax)




[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Dan Malek]

Johnnie Peters wrote:

> I think this is the same problem I was seeing.  This machine is also the known as
> the Utah.  I fixed this in arch/ppc/boot/misc.c.  Here is the diff:
>
> Michael Meissner wrote: 454c454
> <       if (( (unsigned long)zimage_start <= 0x01000000 ) && initrd_start)
> ---
> >       if ( (unsigned long)zimage_start <= 0x01000000 )

Wait a minute.....this isn't the problem.  Making this change will
break other machines.


> > > > }       loaded at:     00400400 00415FD0
> > > > }       relocated to:  00600000 00615BD0
> > > > }       zimage at:     0040A400 0049A889
> > > > }       avail ram:     00400000 00600000

For whatever reason, at the end of the memory relocation process,
we force the available ram buffer to the location above.  What happened
in this case is the load image was copied into memory into the space
we assumed was to be used for free memory.

This boot process has become a nightmare.  At first glance it looks
pretty generic, but it is full of assumptions about how specific types
of systems load images.  There are actually two different loading
locations, above 8 Meg (physical) for most machines or at exactly
2 Meg for small memory systems like the 8xx boards.  When you load
the initial image between these locations, as in this example, the boot
process is unlikely to work.

The initial boot code is built to run at either 1 Meg or 6 Meg.  When started
it relocates itself to those locations.  We should clean up the code in
misc.c to do something similar.  The only restriction in this case would be
the boot code (plus bss, which people often forget) must not overlap the
zImage or the ramdisk.  In other words, the correct thing to do is not
force the abosolute location of the free memory.  We already go through
the arithmetic to find some free memory, so why not just use it?

In this case, removing the fragment of code:

    #ifndef CONFIG_MBX
        /* this is safe, just use it */
        /* I don't know why it didn't work for me on the MBX with 20 MB
         * memory.  I guess something was saved up there, but I can't
         * figure it out......we are running on luck.  -- Dan.
         */
        avail_ram = (char *)0x00400000;
        end_avail = (char *)0x00600000;
#endif

would likely work.  Just change the #ifdef above to #if 0.  Let me know
what happens in this case.


Thanks.


    -- Dan



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Cort Dougan]

The prep/mbx boot code is a mess right now and I'm hesitant to touch it
at the moment because we're at 2.2 and it works for most machines right
now.  I know from the past that touching it breaks at least some machine 
somewhere.

What I would like to do is keep arch/ppc/boot/ for MBX and prep since
they're so similar but setup a different relocation strategy.  Right now
it's mostly a result of me trying out things and stopping when everything
I could get ahold of worked and patching it as bug reports came in.

The new one should be linked at a safe address (for PReP this could be
10-16M).  After load we relocate ourselves there, use the 10-12M range for
free space and decompress the kernel.  This requires 16M but I'm not sure
there are many machines out there with <16M.

This would take care of every prep I know of.  They all load at a
different address (sometimes depending on how you boot) but that region
should be safe.  Does anyone see problems with that?


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Gabriel Paubert]

On Sun, 17 Jan 1999, Cort Dougan wrote:

> 
> The prep/mbx boot code is a mess right now and I'm hesitant to touch it
> at the moment because we're at 2.2 and it works for most machines right
> now.  I know from the past that touching it breaks at least some machine 
> somewhere.
> 
> What I would like to do is keep arch/ppc/boot/ for MBX and prep since
> they're so similar but setup a different relocation strategy.  Right now
> it's mostly a result of me trying out things and stopping when everything
> I could get ahold of worked and patching it as bug reports came in.
> 
> The new one should be linked at a safe address (for PReP this could be
> 10-16M).  After load we relocate ourselves there, use the 10-12M range for
> free space and decompress the kernel.  This requires 16M but I'm not sure
> there are many machines out there with <16M.
> 
> This would take care of every prep I know of.  They all load at a
> different address (sometimes depending on how you boot) but that region
> should be safe.  Does anyone see problems with that?


Why don't you compile with the -m relocatable option for PreP, which
allows executing at any addres. Have a look at how I've done it in the
prep loader I've written. Some assembly glue at the beginning performs the
relocation and calls a C routine which essentially decides where to
relocate and set the stack and other things. Then it relocates again at
the highest possible address (everything as a single block like boot).

You may have problem with preploader for other reasons (multiplying the 
number of boot methods) but this part is quite clean and does not rely
on any fixed address.

Nevertheless, since the MBX firmware understands ELF AFAIK, they should be
handled somewhat differently than PreP. However, this is only a matter
of linker scripts and compiler option depending on CONFIG_MBX. 
(There is so much condiftional code on CONFIG_MBX in the source that 
adding a couple of them should not matter, -mrelocatable increases
somewhat the code size so it should be PreP specific since the machines
are much less memory constrained, and I've been careful to write the
code in a way which minimizes this kind of bloat). 

I'm in the process of improving preploader to handle the no residual data
case of preploader (I've finally some hints on how to do it). I could not
do it during the week-end due to serious problems with the computer system
here requiring major reconfiguration. 

	Gabriel


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Gary Thomas]

On 16-Jan-99 Dan Malek wrote:
> 
> Johnnie Peters wrote:
> 
>> I think this is the same problem I was seeing.  This machine is also the known as
>> the Utah.  I fixed this in arch/ppc/boot/misc.c.  Here is the diff:
>>
>> Michael Meissner wrote: 454c454
>> <       if (( (unsigned long)zimage_start <= 0x01000000 ) && initrd_start)
>> ---
>> >       if ( (unsigned long)zimage_start <= 0x01000000 )
> 
> Wait a minute.....this isn't the problem.  Making this change will
> break other machines.
> 
> 
>> > > > }       loaded at:     00400400 00415FD0
>> > > > }       relocated to:  00600000 00615BD0
>> > > > }       zimage at:     0040A400 0049A889
>> > > > }       avail ram:     00400000 00600000
> 
> For whatever reason, at the end of the memory relocation process,
> we force the available ram buffer to the location above.  What happened
> in this case is the load image was copied into memory into the space
> we assumed was to be used for free memory.
> 
> This boot process has become a nightmare.  At first glance it looks
> pretty generic, but it is full of assumptions about how specific types
> of systems load images.  There are actually two different loading
> locations, above 8 Meg (physical) for most machines or at exactly
> 2 Meg for small memory systems like the 8xx boards.  When you load
> the initial image between these locations, as in this example, the boot
> process is unlikely to work.
> 
> The initial boot code is built to run at either 1 Meg or 6 Meg.  When started
> it relocates itself to those locations.  We should clean up the code in
> misc.c to do something similar.  The only restriction in this case would be
> the boot code (plus bss, which people often forget) must not overlap the
> zImage or the ramdisk.  In other words, the correct thing to do is not
> force the abosolute location of the free memory.  We already go through
> the arithmetic to find some free memory, so why not just use it?
> 
> In this case, removing the fragment of code:
> 
>     #ifndef CONFIG_MBX
>         /* this is safe, just use it */
>         /* I don't know why it didn't work for me on the MBX with 20 MB
>          * memory.  I guess something was saved up there, but I can't
>          * figure it out......we are running on luck.  -- Dan.
>          */
>         avail_ram = (char *)0x00400000;
>         end_avail = (char *)0x00600000;
>#endif
> 
> would likely work.  Just change the #ifdef above to #if 0.  Let me know
> what happens in this case.
> 
> 
> Thanks.
> 
> 
>     -- Dan

Here's what I got to work (patches):

diff -ur /tmp/linux-2.2.0p5/arch/ppc/boot/misc.c /usr/src/linux-2.2.0p5/arch/ppc/boot/misc.c
--- /tmp/linux-2.2.0p5/arch/ppc/boot/misc.c     Mon Dec 21 16:37:20 1998
+++ /usr/src/linux-2.2.0p5/arch/ppc/boot/misc.c Sun Jan 17 12:15:03 1999
@@ -411,7 +417,7 @@
        if ( INITRD_OFFSET )
                end_avail = (char *)0x01000000;
        else
-               end_avail = (char *)0x00400000;
+               end_avail = (char *)0x00800000;
 
        /* let residual data tell us it's higher */
        if ( (unsigned long)residual > 0x00800000 )
@@ -522,6 +528,7 @@
 
 #ifndef CONFIG_MBX
        /* this is safe, just use it */
+#if 0 /* Hah!  This is really wrong on PreP boxes with OF */
        /* I don't know why it didn't work for me on the MBX with 20 MB
         * memory.  I guess something was saved up there, but I can't
         * figure it out......we are running on luck.  -- Dan.
@@ -529,6 +536,7 @@
        avail_ram = (char *)0x00400000;
        end_avail = (char *)0x00600000;
 #endif
+#endif
        puts("avail ram:     "); puthex((unsigned long)avail_ram); puts(" ");
        puthex((unsigned long)end_avail); puts("\n");
 
I'll try upgrading to 2.2.0p7 tonight and see how that works.

I haven't been able to get the PS/2 mouse working yet.  Also, I'll try to stitch
in the code I had in the 2.0.XX kernels to handle/fake residual data on the PreP
boxes - so I can have my 64M RAM back :-)

Please note: I'm either 'gthomas@cygnus.co.uk' or 'gdt@linuxppc.org', not 'gdt@cygnus.com'.


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Cort Dougan]

Please ship that to me and I'll stick it in.

I like Garbriels bootloader and I think it may be worthwhile to make the
MBX/PReP bootloader break sometime soon.  A relocatable bootloader for
prep would solve a lot of problems.

}I'll try upgrading to 2.2.0p7 tonight and see how that works.
}
}I haven't been able to get the PS/2 mouse working yet.  Also, I'll try to stitch
}in the code I had in the 2.0.XX kernels to handle/fake residual data on the PreP
}boxes - so I can have my 64M RAM back :-)
}
}Please note: I'm either 'gthomas@cygnus.co.uk' or 'gdt@linuxppc.org', not 'gdt@cygnus.com'.



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Michael Meissner]

Thanks for all the suggestions regarding booting the OF prep machine I have.  I
will try the patches as soon as I get into the office (I'm iced in at home
today).

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Michael Meissner]

On Mon, Jan 18, 1999 at 12:58:56PM -0500, Michael Meissner wrote:
> Thanks for all the suggestions regarding booting the OF prep machine I have.  I
> will try the patches as soon as I get into the office (I'm iced in at home
> today).

And unfortunately, I broke my right arm and wrist today, so I'm probably not
going to be near the hardware for some time.  So hopefully, somebody with a
Utah machine can try the patches.

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Johnnie Peters]

I will volunteer to try the patches on:

Blackhawk
Comet
Utah
Mequite
MTX
VME2600/2700/3600

just as soon as they are available.

Johnnie


Michael Meissner wrote:

> On Mon, Jan 18, 1999 at 12:58:56PM -0500, Michael Meissner wrote:
> > Thanks for all the suggestions regarding booting the OF prep machine I have.  I
> > will try the patches as soon as I get into the office (I'm iced in at home
> > today).
>
> And unfortunately, I broke my right arm and wrist today, so I'm probably not
> going to be near the hardware for some time.  So hopefully, somebody with a
> Utah machine can try the patches.
>
> --
> Michael Meissner, Cygnus Solutions (Massachusetts office)
> 4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
> meissner@cygnus.com,    617-354-5416 (office),  617-354-7161 (fax)




[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

3-button mouse

[Brent H Mundy]

I have looked on the F-o-M for a supplier of 3-button mice.  All I could
find were entries for installing/trouble shooting.  Can anyone suggest a
3-button mouse (ADB).  I am looking to spend ~$30.  All I can find is
either 2-button mice, expensive 3-button mice, or 3-button USB mice.
Suggestions?  

Thanks in advance,
Brent

___________________________________________________

ZenCrafters:  Total Enlightenment, in about an hour
___________________________________________________



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: 3-button mouse

[Benjamin Herrenschmidt]

On Tue, Jan 19, 1999, Brent H Mundy <bmundy@indiana.edu> wrote:

>I have looked on the F-o-M for a supplier of 3-button mice.  All I could
>find were entries for installing/trouble shooting.  Can anyone suggest a
>3-button mouse (ADB).  I am looking to spend ~$30.  All I can find is
>either 2-button mice, expensive 3-button mice, or 3-button USB mice.
>Suggestions?  

Let's be off-topic too ;-)

I'm looking for a place where I could order one or two 3 button mice. My
problem is that I want mice that currently cause trouble with Linux (in
order to fix them of course ;-). I'm looking for a MacX compatible one,
and eventually one of those that needs mousehack to work but I don't know
where to find them since those people don't usually put the kind of
protocol used by their mice on the web page...

So if someone could give me a set (model,place_to_buy,protocol_used) I
would be grateful !


-- 
           E-Mail: <mailto:bh40@calva.net>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>




[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

pre8(vger) kills button 3 on 1-button mouse

[Martin Costabel]

The latest changes for 2-to-4-button mice on vger in
drivers/macintosh/mac_keyb.c (rev 1.24) break the emulation of button 3
on my 1-button Apple adb mouse.

This happens both in Xpmac, where option_right+click is hard-coded to
button 3, and in XF68_FBDev, where I use a patch by Franz Sirl for the
adb_buttons kernel command to get the same effect.

The reason seems to be that in rev 1.24 option_right gets mapped to
option_left even in raw mode (same for ctrl, BTW). I don't understand
this from the code, which is too complicated for me, anyway, but from
looking at the effect, as witnessed by xev in Xpmac, for example.

For the moment, I went back to rev 1.23 which doesn't have this problem.

--
Martin

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: 3-button mouse

[fritzwe.linux]

I'm using a A/3 optical mouse from Mouse Systems 
http://www.mousesystems.com/dld.htm
Unfortunatly they discontinue the optical mouse but they have a 3-button ball
mouse called MacPoint Pro which should be MacX compatible.
I'm not sure but as far as I know they use the MouseSystems-protocoll.
 
On 20-Jan-99 Benjamin Herrenschmidt wrote:
> 
> On Tue, Jan 19, 1999, Brent H Mundy <bmundy@indiana.edu> wrote:
> 
>>I have looked on the F-o-M for a supplier of 3-button mice.  All I could
>>find were entries for installing/trouble shooting.  Can anyone suggest a
>>3-button mouse (ADB).  I am looking to spend ~$30.  All I can find is
>>either 2-button mice, expensive 3-button mice, or 3-button USB mice.
>>Suggestions?  
> 
> Let's be off-topic too ;-)
> 
> I'm looking for a place where I could order one or two 3 button mice. My
> problem is that I want mice that currently cause trouble with Linux (in
> order to fix them of course ;-). I'm looking for a MacX compatible one,
> and eventually one of those that needs mousehack to work but I don't know
> where to find them since those people don't usually put the kind of
> protocol used by their mice on the web page...
> 
> So if someone could give me a set (model,place_to_buy,protocol_used) I
> would be grateful !
> 

Fritz
----------------------------------
Date: 21-Jan-99
Time: 10:57:59

TA-Media AG                             Phone +41 1 248 4732
Telematik                                 Fax +41 1 248 5152
Fritz Wettstein                                     

This message was sent by XFMail
----------------------------------

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Gary Thomas]

On 20-Jan-99 Johnnie Peters wrote:
> 
> I will volunteer to try the patches on:
> 
> Blackhawk
> Comet
> Utah
> Mequite
> MTX
> VME2600/2700/3600
> 
> just as soon as they are available.
> 

I have put up all my patches against 2.2.0p7 at:
  ftp://ftp.linuxppc.org/gary/diffs-2.2.0p7-Jan20
These are diffs against the virgin 2.2.0-pre7.

This includes the changes to fix boot problems on my Utah box,
as well as the changes to get the PS/2 mouse working again.

I also did some restructuring of the PPC main configuration menu
so that Pmac questions are ignored if you aren't configuring for
a PowerMac.  I also added a configuration option to set the default
kernel boot line, passed to the bootstrap code.

Note: I have had persistent problems with the cache test in the
NCR driver.  It seems to work fine if I just ignore it, so I also
left it that way.  I also had to "tone down" the driver a lot,
the default of WIDE+20Mhz just doesn't cut it on my drives :-)



------------------------------------------------------------------------
Gary Thomas                              |
email: gdt@linuxppc.org                  | "Fine wine is a necessity of
   ... opinions expressed here are mine  |        life for me"
       and no one else would claim them! |
                                         |      Thomas Jefferson
------------------------------------------------------------------------



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Johnnie Peters]

I will pull this down today and give it a try.

Johnnie


Gary Thomas wrote:

> On 20-Jan-99 Johnnie Peters wrote:
> >
> > I will volunteer to try the patches on:
> >
> > Blackhawk
> > Comet
> > Utah
> > Mequite
> > MTX
> > VME2600/2700/3600
> >
> > just as soon as they are available.
> >
>
> I have put up all my patches against 2.2.0p7 at:
>   ftp://ftp.linuxppc.org/gary/diffs-2.2.0p7-Jan20
> These are diffs against the virgin 2.2.0-pre7.
>
> This includes the changes to fix boot problems on my Utah box,
> as well as the changes to get the PS/2 mouse working again.
>
> I also did some restructuring of the PPC main configuration menu
> so that Pmac questions are ignored if you aren't configuring for
> a PowerMac.  I also added a configuration option to set the default
> kernel boot line, passed to the bootstrap code.
>
> Note: I have had persistent problems with the cache test in the
> NCR driver.  It seems to work fine if I just ignore it, so I also
> left it that way.  I also had to "tone down" the driver a lot,
> the default of WIDE+20Mhz just doesn't cut it on my drives :-)
>
> ------------------------------------------------------------------------
> Gary Thomas                              |
> email: gdt@linuxppc.org                  | "Fine wine is a necessity of
>    ... opinions expressed here are mine  |        life for me"
>        and no one else would claim them! |
>                                          |      Thomas Jefferson
> ------------------------------------------------------------------------




[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Johnnie Peters]

Hi Everybody

I downloaded this stuff, merged it in and tried it.  Everything worked
fine except the serial console connections are not showing the
bootloader information that was introduced with Cort's serial
console changes.  I don't yet know why as I am suddenly swamped
with work but I will track it down in the next few days if nobody else
does.  Othwise this looks really great.

I really like the configuration changes Gary mode for the command
line stuff and being able to configure the mouse to force initialization.

Johnnie


Gary Thomas wrote:

> On 20-Jan-99 Johnnie Peters wrote:
> >
> > I will volunteer to try the patches on:
> >
> > Blackhawk
> > Comet
> > Utah
> > Mequite
> > MTX
> > VME2600/2700/3600
> >
> > just as soon as they are available.
> >
>
> I have put up all my patches against 2.2.0p7 at:
>   ftp://ftp.linuxppc.org/gary/diffs-2.2.0p7-Jan20
> These are diffs against the virgin 2.2.0-pre7.
>
> This includes the changes to fix boot problems on my Utah box,
> as well as the changes to get the PS/2 mouse working again.
>
> I also did some restructuring of the PPC main configuration menu
> so that Pmac questions are ignored if you aren't configuring for
> a PowerMac.  I also added a configuration option to set the default
> kernel boot line, passed to the bootstrap code.
>
> Note: I have had persistent problems with the cache test in the
> NCR driver.  It seems to work fine if I just ignore it, so I also
> left it that way.  I also had to "tone down" the driver a lot,
> the default of WIDE+20Mhz just doesn't cut it on my drives :-)
>
> ------------------------------------------------------------------------
> Gary Thomas                              |
> email: gdt@linuxppc.org                  | "Fine wine is a necessity of
>    ... opinions expressed here are mine  |        life for me"
>        and no one else would claim them! |
>                                          |      Thomas Jefferson
> ------------------------------------------------------------------------




[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Michael Meissner]

On Thu, Jan 21, 1999 at 04:46:44PM -0700, Johnnie Peters wrote:
> 
> Hi Everybody
> 
> I downloaded this stuff, merged it in and tried it.  Everything worked
> fine except the serial console connections are not showing the
> bootloader information that was introduced with Cort's serial
> console changes.  I don't yet know why as I am suddenly swamped
> with work but I will track it down in the next few days if nobody else
> does.  Othwise this looks really great.
> 
> I really like the configuration changes Gary mode for the command
> line stuff and being able to configure the mouse to force initialization.

I suspose it is too late to get this in the real 2.2.0 release?

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Cort Dougan]

The changes are not minor.  I'm going to hold off for a while.

arch/ppc/boot needs to be redone anyway so until that happens (which
should happen soon) I think it best to wait.  

My current thinking is that there will be a arch/ppc/prepboot for prep and
a arch/ppc/8xxboot for the 8xx processor systems (mbx, rpx lite and so
on).  prepboot will likely be based on Gabriels prepboot code.  Those are
just my rough ideas right now so they're subject to change.  Anyone have
suggestions or opinions about that?

}I suspose it is too late to get this in the real 2.2.0 release?


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Gary Thomas]

On 22-Jan-99 Cort Dougan wrote:
> 
> The changes are not minor.  I'm going to hold off for a while.
> 

What about the fixes for the PS/2 mouse?  These are not large, but
significant for systems that need to intialize the mouse from scratch.

> arch/ppc/boot needs to be redone anyway so until that happens (which
> should happen soon) I think it best to wait.  
> 
> My current thinking is that there will be a arch/ppc/prepboot for prep and
> a arch/ppc/8xxboot for the 8xx processor systems (mbx, rpx lite and so
> on).  prepboot will likely be based on Gabriels prepboot code.  Those are
> just my rough ideas right now so they're subject to change.  Anyone have
> suggestions or opinions about that?
> 
> }I suspose it is too late to get this in the real 2.2.0 release?
> 

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Cort Dougan]

You're right.

}What about the fixes for the PS/2 mouse?  These are not large, but
}significant for systems that need to intialize the mouse from scratch.

I'll take another look at the patch.


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Gary Thomas]

On 22-Jan-99 Cort Dougan wrote:
> You're right.
> 
> }What about the fixes for the PS/2 mouse?  These are not large, but
> }significant for systems that need to intialize the mouse from scratch.
> 
> I'll take another look at the patch.

Thanks.  The important files [for this one] are:
  drivers/char/pc_keyb.[ch]
  drivers/char/Config.in

Also the changes I made to the PPC configure files are useful and can be
separated from the boot changes.


------------------------------------------------------------------------
Gary Thomas                              |
email: gdt@linuxppc.org                  | "Fine wine is a necessity of
   ... opinions expressed here are mine  |        life for me"
       and no one else would claim them! |
                                         |      Thomas Jefferson
------------------------------------------------------------------------



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Johnnie Peters]

I find that this also would be a great plus as they are needed for
the Utahs.

Johnnie


Gary Thomas wrote:

> On 22-Jan-99 Cort Dougan wrote:
> >
> > The changes are not minor.  I'm going to hold off for a while.
> >
>
> What about the fixes for the PS/2 mouse?  These are not large, but
> significant for systems that need to intialize the mouse from scratch.
>
> > arch/ppc/boot needs to be redone anyway so until that happens (which
> > should happen soon) I think it best to wait.
> >
> > My current thinking is that there will be a arch/ppc/prepboot for prep and
> > a arch/ppc/8xxboot for the 8xx processor systems (mbx, rpx lite and so
> > on).  prepboot will likely be based on Gabriels prepboot code.  Those are
> > just my rough ideas right now so they're subject to change.  Anyone have
> > suggestions or opinions about that?
> >
> > }I suspose it is too late to get this in the real 2.2.0 release?
> >




[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Michael Meissner]

On Wed, Jan 20, 1999 at 03:21:36PM -0000, Gary Thomas wrote:
> I have put up all my patches against 2.2.0p7 at:
>   ftp://ftp.linuxppc.org/gary/diffs-2.2.0p7-Jan20
> These are diffs against the virgin 2.2.0-pre7.

Over the weekend, I moved the PowerPC to my home, and confirmed Gary's patches
do allow me to boot on my Utah machine.  Note, the patch for
drives/char/pc_keyb.c won't apply to 2.2.1, but its a simple matter to adjust
the patch.

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Gary Thomas]

On 01-Feb-99 Michael Meissner wrote:
> On Wed, Jan 20, 1999 at 03:21:36PM -0000, Gary Thomas wrote:
>> I have put up all my patches against 2.2.0p7 at:
>>   ftp://ftp.linuxppc.org/gary/diffs-2.2.0p7-Jan20
>> These are diffs against the virgin 2.2.0-pre7.
> 
> Over the weekend, I moved the PowerPC to my home, and confirmed Gary's patches
> do allow me to boot on my Utah machine.  Note, the patch for
> drives/char/pc_keyb.c won't apply to 2.2.1, but its a simple matter to adjust
> the patch.
> 

I'll re-post these for 2.2.1 later [possibly today], along with a
couple of others I have.


------------------------------------------------------------------------
Gary Thomas                              |
email: gdt@linuxppc.org                  | "Fine wine is a necessity of
   ... opinions expressed here are mine  |        life for me"
       and no one else would claim them! |
                                         |      Thomas Jefferson
------------------------------------------------------------------------



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Michael Meissner]

On Mon, Feb 01, 1999 at 04:18:25PM -0000, Gary Thomas wrote:
> 
> On 01-Feb-99 Michael Meissner wrote:
> > On Wed, Jan 20, 1999 at 03:21:36PM -0000, Gary Thomas wrote:
> >> I have put up all my patches against 2.2.0p7 at:
> >>   ftp://ftp.linuxppc.org/gary/diffs-2.2.0p7-Jan20
> >> These are diffs against the virgin 2.2.0-pre7.
> > 
> > Over the weekend, I moved the PowerPC to my home, and confirmed Gary's patches
> > do allow me to boot on my Utah machine.  Note, the patch for
> > drives/char/pc_keyb.c won't apply to 2.2.1, but its a simple matter to adjust
> > the patch.
> > 
> 
> I'll re-post these for 2.2.1 later [possibly today], along with a
> couple of others I have.

Note, I went into the office yesterday, and tried my boot disk with Gary's
changes on the older PowerStack-1 I have in the office (603, no L2 cache, 48
meg of non-pairity memory), and it wouldn't boot due to insufficient memory.
As I mentioned, it does boot fine on my PowerStack-II (Utah, 604e, 128 meg of
memory, 512K L2 cache).

> 
> ------------------------------------------------------------------------
> Gary Thomas                              |
> email: gdt@linuxppc.org                  | "Fine wine is a necessity of
>    ... opinions expressed here are mine  |        life for me"
>        and no one else would claim them! |
>                                          |      Thomas Jefferson
> ------------------------------------------------------------------------
> 
> 

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Gary Thomas]

Before it quit, did it tell you how much memory it thought it had?
Perhaps the OFW memory sizing stuff is wrong...  Although I thought
I had forced it to think that there was 32M if there was no OFW.

On 04-Feb-99 Michael Meissner wrote:
> On Mon, Feb 01, 1999 at 04:18:25PM -0000, Gary Thomas wrote:
>> 
>> On 01-Feb-99 Michael Meissner wrote:
>> > On Wed, Jan 20, 1999 at 03:21:36PM -0000, Gary Thomas wrote:
>> >> I have put up all my patches against 2.2.0p7 at:
>> >>   ftp://ftp.linuxppc.org/gary/diffs-2.2.0p7-Jan20
>> >> These are diffs against the virgin 2.2.0-pre7.
>> > 
>> > Over the weekend, I moved the PowerPC to my home, and confirmed Gary's patches
>> > do allow me to boot on my Utah machine.  Note, the patch for
>> > drives/char/pc_keyb.c won't apply to 2.2.1, but its a simple matter to adjust
>> > the patch.
>> > 
>> 
>> I'll re-post these for 2.2.1 later [possibly today], along with a
>> couple of others I have.
> 
> Note, I went into the office yesterday, and tried my boot disk with Gary's
> changes on the older PowerStack-1 I have in the office (603, no L2 cache, 48
> meg of non-pairity memory), and it wouldn't boot due to insufficient memory.
> As I mentioned, it does boot fine on my PowerStack-II (Utah, 604e, 128 meg of
> memory, 512K L2 cache).
> 
>> 
>> ------------------------------------------------------------------------
>> Gary Thomas                              |
>> email: gdt@linuxppc.org                  | "Fine wine is a necessity of
>>    ... opinions expressed here are mine  |        life for me"
>>        and no one else would claim them! |
>>                                          |      Thomas Jefferson
>> ------------------------------------------------------------------------
>> 
>> 
> 
> -- 
> Michael Meissner, Cygnus Solutions (Massachusetts office)
> 4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
> meissner@cygnus.com,  617-354-5416 (office),  617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Michael Meissner]

On Thu, Feb 04, 1999 at 07:21:34PM -0000, Gary Thomas wrote:
> Before it quit, did it tell you how much memory it thought it had?
> Perhaps the OFW memory sizing stuff is wrong...  Although I thought
> I had forced it to think that there was 32M if there was no OFW.

I don't remember (and its likely to be a few days before I go in again).
The machine in question only has PPCbug installed in ROM, no OF.  It does boot
fine with an unpatched 2.2.0-pre7 floppy.

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Michael Meissner]

On Tue, Jan 19, 1999 at 10:27:30AM -0000, Gary Thomas wrote:
> 
> On 18-Jan-99 Cort Dougan wrote:
> > Please ship that to me and I'll stick it in.
> > 
> > I like Garbriels bootloader and I think it may be worthwhile to make the
> > MBX/PReP bootloader break sometime soon.  A relocatable bootloader for
> > prep would solve a lot of problems.
> > 
> > }I'll try upgrading to 2.2.0p7 tonight and see how that works.
> > }
> 
> Attached are my changes to add [minimal] residual data to PreP booting.
> I've also had to make some minor compatability changes to get extended
> partitions to work with old disks.

I see you added changes to set the initial cmd config.  Is there any way we can
add a configure line when building the kernel, so I can build a kernel with
different data (ie, my disk is /dev/sda2 and not /dev/sdb2, etc.).  That way it
has a better chance of working if rebooted in the middle of the night due to
power failure.

-- 
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA
meissner@cygnus.com,	617-354-5416 (office),	617-354-7161 (fax)

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Gary Thomas]

On 19-Jan-99 Michael Meissner wrote:
> On Tue, Jan 19, 1999 at 10:27:30AM -0000, Gary Thomas wrote:
>> 
>> On 18-Jan-99 Cort Dougan wrote:
>> > Please ship that to me and I'll stick it in.
>> > 
>> > I like Garbriels bootloader and I think it may be worthwhile to make the
>> > MBX/PReP bootloader break sometime soon.  A relocatable bootloader for
>> > prep would solve a lot of problems.
>> > 
>> > }I'll try upgrading to 2.2.0p7 tonight and see how that works.
>> > }
>> 
>> Attached are my changes to add [minimal] residual data to PreP booting.
>> I've also had to make some minor compatability changes to get extended
>> partitions to work with old disks.
> 
> I see you added changes to set the initial cmd config.  Is there any way we can
> add a configure line when building the kernel, so I can build a kernel with
> different data (ie, my disk is /dev/sda2 and not /dev/sdb2, etc.).  That way it
> has a better chance of working if rebooted in the middle of the night due to
> power failure.
> 

I like this idea.  I'll see what I can do with it tonight.

------------------------------------------------------------------------
Gary Thomas                              |
email: gdt@linuxppc.org                  | "Fine wine is a necessity of
   ... opinions expressed here are mine  |        life for me"
       and no one else would claim them! |
                                         |      Thomas Jefferson
------------------------------------------------------------------------



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Dan Malek]

Gary Thomas wrote:

> I like this idea.  I'll see what I can do with it tonight.

Just copy the stuff I did for the 8xx/MBX ports in misc.c.
Add a #define string to the config process and pass it into
misc.c during compilation.

When a system has some type of environment strings you
could rummage around in there to find the default information.
An example can be found in the embedded 2.1.127 kernel tarball.
There are modifications in there that I have not yet added to
the real kernel.  It reads serial EEPROM or other NVRAM storage
commonly found on the 8xx cards.  Using any type of environment
string would allow system changes without recompiling.

Have fun :-).


    -- Dan



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Loic Prylli]

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


Michael Meissner writes:
 > 
 > I see you added changes to set the initial cmd config.  Is there any way we can
 > add a configure line when building the kernel, so I can build a kernel with
 > different data (ie, my disk is /dev/sda2 and not /dev/sdb2, etc.).  That way it
 > has a better chance of working if rebooted in the middle of the night due to
 > power failure.
 > 

Some time ago, I made a small addition to Gabriel preploader, including
 a simple "prepctl" program, that permit to modify the
command-line stored in the zImage.

In my case, it is much more useful than getting the command-line
through residual data or NVRAM, because I can modify the command-line
parameters for the next reboot without needing access to the console
(you win a lot of time if you have 16 machines, moreover they are in a
closed room for which it is tedious to get the key:-). Of course this
is not an advantage anymore if there is some tools to modify NVRAM or
residual data after Linux is booted.

Anyway below is the patch, to modify the command-line of a zImage,
simply run "prepctl <zImage> <command line parameters>..." or "prepctl
/dev/sda1 ..." if it is installed on a disk partition.


[-- Attachment #2: preploader.diff --]
[-- Type: application/octet-stream, Size: 5925 bytes --]

Index: preploader/Makefile
diff -c preploader/Makefile:1.1.1.3 preploader/Makefile:1.2
*** preploader/Makefile:1.1.1.3	Wed Jan 20 09:45:40 1999
--- preploader/Makefile	Wed Jan 20 14:26:39 1999
***************
*** 59,68 ****
  
  #OBJECTS += vreset.o kbd.o
  
! zImage: $(OBJECTS) $(IMAGES) $(SIZES) ppcboot.lds
  	ld -o zImage $(OBJECTS) -b binary $(IMAGES) -T ppcboot.lds \
  	--defsym _vmlinux_size=`cut -f 1 <.vmlinux.size` -Map zImage.map
  
  # The 2 objcopy are quite ugly, but for now it was the simplest solution
  # since the flags to expand the bss do not work on a binary output format.
  # It would be better to know where the bss is and clear it in the bootloader,
--- 59,72 ----
  
  #OBJECTS += vreset.o kbd.o
  
! zImage: $(OBJECTS) $(IMAGES) $(SIZES) ppcboot.lds prepctl
  	ld -o zImage $(OBJECTS) -b binary $(IMAGES) -T ppcboot.lds \
  	--defsym _vmlinux_size=`cut -f 1 <.vmlinux.size` -Map zImage.map
  
+ prepctl: prepctl.c
+ 	$(CC) -O -o $@ $<
+ 
+ 
  # The 2 objcopy are quite ugly, but for now it was the simplest solution
  # since the flags to expand the bss do not work on a binary output format.
  # It would be better to know where the bss is and clear it in the bootloader,
Index: preploader/bootdata.h
diff -c /dev/null preploader/bootdata.h:1.1
*** /dev/null	Wed Jan 20 14:54:39 1999
--- preploader/bootdata.h	Wed Jan 20 14:27:27 1999
***************
*** 0 ****
--- 1,3 ----
+ #define MAGIC1_CMDLINE 0xe08ed9f7
+ #define MAGIC2_CMDLINE 0x3c0b8c88
+ 
Index: preploader/bootldr.h
diff -c preploader/bootldr.h:1.1.1.3 preploader/bootldr.h:1.2
*** preploader/bootldr.h:1.1.1.3	Wed Jan 20 09:45:19 1999
--- preploader/bootldr.h	Wed Jan 20 14:26:41 1999
***************
*** 73,78 ****
--- 73,81 ----
   * functions who have to access the .got2 sections (this increases the 
   * size of the prologue in every function).
   */
+ 
+ #include "bootdata.h"
+ 
  typedef struct _boot_data {
  	RESIDUAL *residual;
  	void *load_address;
***************
*** 95,101 ****
  	const struct console_io *console_functions;
  	opaque * console_private;
  	u_long ticks_per_ms;
! 	char cmd_line[256];
  } boot_data;
  
  register boot_data *bd __asm__("r13");
--- 98,106 ----
  	const struct console_io *console_functions;
  	opaque * console_private;
  	u_long ticks_per_ms;
!   unsigned long magic1;
!   char cmd_line[256];
!   unsigned long magic2;
  } boot_data;
  
  register boot_data *bd __asm__("r13");
Index: preploader/misc.c
diff -c preploader/misc.c:1.1.1.3 preploader/misc.c:1.2
*** preploader/misc.c:1.1.1.3	Wed Jan 20 09:45:33 1999
--- preploader/misc.c	Wed Jan 20 14:26:43 1999
***************
*** 48,54 ****
  		  &vacuum_console_functions,
  		  &console_private,
  		  1000000,	/* Decrementer ticks per ms (true for 601) */
! 		  "console=ttyS0"	
  		 };
  
  void exit()
--- 48,54 ----
  		  &vacuum_console_functions,
  		  &console_private,
  		  1000000,	/* Decrementer ticks per ms (true for 601) */
!                   MAGIC1_CMDLINE, "console=ttyS0" ,MAGIC2_CMDLINE
  		 };
  
  void exit()
***************
*** 70,75 ****
--- 70,88 ----
  	return dst;
  }
  
+ int strcmp(const char *p1,const char *p2) {
+   int vs1,vs2;
+   const unsigned char *s1 = p1;
+   const unsigned char *s2 = p2;
+   do {
+     vs1 = *s1++;
+     vs2 = *s2++;
+     if (vs1 != vs2)
+       return vs1 - vs2;
+   } while (vs1 && vs2);
+   return 0;
+ }
+ 
  void hang(const char *s, u_long x, ctxt *p) {
  	u_long *r1;
  #ifdef DEBUG
***************
*** 291,297 ****
  		} else {
  			select_console(&vga_console_setup);
  			/* Remove the kernel serial console parameter */
! 			bd->cmd_line[0]='\0';
  		}
  	} else if (!err) {
  		select_console(&serial_console_setup);
--- 304,311 ----
  		} else {
  			select_console(&vga_console_setup);
  			/* Remove the kernel serial console parameter */
!                         if (strcmp(bd->cmd_line,"console=ttyS0") == 0)
!                           bd->cmd_line[0]='\0';
  		}
  	} else if (!err) {
  		select_console(&serial_console_setup);
Index: preploader/prepctl.c
diff -c /dev/null preploader/prepctl.c:1.1
*** /dev/null	Wed Jan 20 14:54:40 1999
--- preploader/prepctl.c	Wed Jan 20 14:27:30 1999
***************
*** 0 ****
--- 1,64 ----
+ #include <stdio.h>
+ #include <stdlib.h>
+ #include <string.h>
+ 
+ #include "bootdata.h"
+ 
+ #define NBINT 4096
+ #define CMDLENGTH (256/sizeof(int))
+ 
+ int main(int argc,char*argv[])
+ {
+   char buf[256];
+   static unsigned int data[NBINT*2];
+   FILE *f;
+   long pos;
+ 
+   if (argc < 2) {
+     fprintf(stderr,"usage:prepctl <zImage-file> [new command line]\n");
+     exit(1);
+   }
+   f = fopen(argv[1],argc > 2 ? "r+": "r");
+   if (!f) {
+     fprintf(stderr,"cannot open file %s\n",argv[1]);
+     perror("erreur:");
+     exit(1);
+   }
+   
+   while (1) { 
+     int i;
+     pos = ftell(f);
+     if (fread(data,sizeof(data[0]),NBINT,f) <= 0)
+       break;
+     for (i=0;i<NBINT;i++) {
+       if (data[i] == MAGIC1_CMDLINE) {
+         if (i+1+CMDLENGTH < NBINT || fread(data+NBINT,sizeof(data[0]),NBINT,f) >= i+1+CMDLENGTH-NBINT) {
+           char *p = (char*)(data+i+1);
+           int j;
+           if (data[i+1+CMDLENGTH] != MAGIC2_CMDLINE) {
+             fprintf(stderr,"ERROR:found magic1 but no magic2\n");
+             exit(1);
+           }
+           printf("current cmdline=%s\n",p);
+           if (argc <= 2)
+             return 0;
+           p[0] = 0;
+           for (j=2;j<argc;j++) {
+             strcat(p,argv[j]);
+             strcat(p," ");
+           }
+           printf("writing new cmdline=%s\n",p);
+           fflush(f);
+           fseek(f,pos,SEEK_SET);
+           if (fwrite(data,sizeof(data[0]),i+1+CMDLENGTH,f) != i+1+CMDLENGTH) {
+             perror("writing new cmd line\n");
+             exit(1);
+           }
+           return 0;
+         }
+       }
+     }
+   }
+   fprintf(stderr,"magic1 number not found in image\n");
+   return 0;
+ }

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Dan Malek]

Gary Thomas wrote:

> Here's what I got to work (patches):

Yeah.  You just moved the free space out of the way of the image
you loaded.  That is the right thing to do, now we just need to make
this happen

Let's take Cort's suggestion and break the loader.  Make it work
correctly for the Prep machines.  I will then take that and make
minor changes for the 8xx ports.  I am considering throwing out
all of the hacks for the MBX (inet addresses and stuff).  I have
only two goals for the 8xx ports.  One, it should load in a small
memory (less than 4 Meg) configuration.  Two, it should load
from a high memory flash rom address.  I am willing to toss the 4M
goal because I don't think you can do anything useful in that
amount of space (you can't use a ramdisk).


> I'll try upgrading to 2.2.0p7 tonight and see how that works.

I should do that too :-).


    -- Dan



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)

[Johnnie Peters]

I think this is the same problem I was seeing.  This machine is also the

known as
the Utah.  I fixed this in arch/ppc/boot/misc.c.  Here is the diff:



454c454
<       if (( (unsigned long)zimage_start <= 0x01000000 ) &&
initrd_start)
---
>       if ( (unsigned long)zimage_start <= 0x01000000 )

Johnnie

Michael Meissner wrote:

> On Fri, Jan 15, 1999 at 04:28:55PM +0100, Alois Fertl wrote:
> > Cort Dougan wrote:
> > >
> > > It looks like your zImage is being stomped on before it can be
> > > decompressed.  I'll take a look at the boot loader code and see
why it
> > > isn't adjusting your free ram section.  You might want to try
changing to
> > > load address in the PPCBug to be near the top of memory in the
mean time.
> > I guess this system is running "PowerPC Open Firmware". You can
change the
> > load address via the firmware menu:
> >   Administrative Options...
> >     ---> Modify the Configuration Settings...
> >           ---> Edit Configuration Variables
> > step to the parameter "load-base" and enter a new value (decimal).
> > One other problem is the this firmware version obviously does not
provide
> > residual data. So Linux will probably not find the PCI devices
correctly.
>
> I tried setting the load-base to various values, and all of them
caused dumps
> within the monitor (I tried 10 meg, 64 meg, 3 meg, 120 meg, and even 4

meg + 4
> all to no avail).
>
> Also, Gary Thomas's 2.0.32 kernel seemed to have no problem in sizing
memory,
> so I presume it is able to pick up the residual data.
>
> > >
> > > }       loaded at:     00400400 00415FD0
> > > }       relocated to:  00600000 00615BD0
> > > }       zimage at:     0040A400 0049A889
> > > }       avail ram:     00400000 00600000
> > > }
> > > }       Linux/PPC load: console=tty0 console=ttyS0,9600n8
root=/dev/sda2 mem=127M
> > > }       Uncompressing Linux...done.
> > > }       Now booting the kernel
>




[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]