Re: NetBSD/zaurus 8.1 problems and possible fixes

[Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>]

I wrote:
> > (2) yet another kernel load failure
> > 
> > The modified above GENERIC kernel works, but when I removed
> > the "COPTS" line, "options DIAGNOSTIC", or "COPY_SYMTAB" line,
> > the each modified kernel is not loaded (or executed) properly.
> > 
> > The behavior is similar to the following movie reported
> > by Sevan Janiyan on this list back in 2017:
> >  https://mail-index.netbsd.org/port-zaurus/2017/04/01/msg000065.html
> >  >> https://www.geeklan.co.uk/files/tmp/zaurus3.mov
> > 
> > I have no idea what happens in this case.
> 
> This seems caused by uninitialized kernel BSS on loading kernel
> by zbsdmod.o.
> 
> With the following change, some kernels (that caused white-out screen
> like the above when loaded by the previous zbsdmod.o) are loaded
> properly.
 :

I've committed this fix to -current
 https://mail-index.netbsd.org/source-changes/2019/10/28/msg110352.html

and put a new liveimage including this fixed zbsdmod.o:
 http://teokurebsd.org/netbsd/liveimage/20191027-zaurus/

Loading netbsd on SL-C860 now works and
'COPTS="-Os"' in GENERIC is no longer necessary.

Index: conf/GENERIC
===================================================================
RCS file: /cvsroot/src/sys/arch/zaurus/conf/GENERIC,v
retrieving revision 1.73.6.3
diff -u -p -d -r1.73.6.3 GENERIC
--- conf/GENERIC	18 Apr 2018 14:45:09 -0000	1.73.6.3
+++ conf/GENERIC	28 Oct 2019 15:29:41 -0000
@@ -164,14 +164,14 @@ options 	WSDISPLAY_COMPAT_RAWKBD		# can 
 
 # Development and Debugging options
 
-#options 	DIAGNOSTIC		# internal consistency checks
+options 	DIAGNOSTIC		# internal consistency checks
 #options 	DEBUG
 #options 	VERBOSE_INIT_ARM	# verbose bootstraping messages
 options 	DDB			# in-kernel debugger
 options 	DDB_HISTORY_SIZE=100	# Enable history editing in DDB
 #options 	KGDB
 #makeoptions 	DEBUG="-g"		# compile full symbol table
-makeoptions	COPY_SYMTAB=1
+#makeoptions	COPY_SYMTAB=1
 
 
 # Kernel root file system and dump configuration.

---

DIAGNOSTIC is still necessary to work around
"Alignment Fault 3" issue on LCD console on SL-C1000.

---
Izumi Tsutsui