mac68k Model Support Docs?

I was also wondering if it would be worthwhile to create a
page for  
NetBSD/mac68k like the following:

http:/
/www.netbsd.org/Ports/macppc/models.html

There really isn't any clear instruction on what works and
what  
doesn't. The install document gives some info but more
would be nice.  
I know the following documents exist but they aren't very
helpful  
because they are very outdated:

http://www.macbsd.com/macbsd/macbsd-docs/machine-status/


htt
p://www.netbsd.org/Ports/mac68k/curr_info.html

For example, the Color Classic II is theoretically supported
but I  
wasn't able to get it installed with NetBSD/mac68k 3.0.1
last night.  
I kept getting errors with the SCSI bus. It could be a bad
disk but I  
don't think that is the problem. It would be great to
gather reports  
of people running 1.6, 2.0, and 2.1 on a machine while 3.x
isn't  
working or something to that effect. I would think that this
would  
help developers as well as users. Any thoughts? Thanks for
your time.

Bryan

On Tue, 5 Sep 2006, Bryan Vyhmeister wrote:

> I was also wondering if it would be worthwhile to
create a page for 
> NetBSD/mac68k like the following:
>
> http:/
/www.netbsd.org/Ports/macppc/models.html
>
> There really isn't any clear instruction on what works
and what doesn't. The 
> install document gives some info but more would be
nice. I know the following 
> documents exist but they aren't very helpful because
they are very outdated:
>
> http://www.macbsd.com/macbsd/macbsd-docs/machine-status/

>
> htt
p://www.netbsd.org/Ports/mac68k/curr_info.html
>
> For example, the Color Classic II is theoretically
supported but I wasn't 
> able to get it installed with NetBSD/mac68k 3.0.1 last
night. I kept getting 
> errors with the SCSI bus. It could be a bad disk but I
don't think that is 
> the problem. It would be great to gather reports of
people running 1.6, 2.0, 
> and 2.1 on a machine while 3.x isn't working or
something to that effect. I 
> would think that this would help developers as well as
users. Any thoughts? 
> Thanks for your time.

 	The next question would be... are you interested in doing
the
 	initial version of this? 

-- 
 		David/absolute       -- www.NetBSD.org: No hype required
--

> > http://www.macbsd.com/macbsd/macbsd-docs/machine-status/

> > htt
p://www.netbsd.org/Ports/mac68k/curr_info.html

>  	The next question would be... are you interested in
doing the
>  	initial version of this? 

I've actually been considering doing a new version of the
page for awhile
as my contribution back to NetBSD. If no one else is highly
interested in
the job, I'd be willing to be a central reporting point for
working configs
and to create a new model and hardware support page based on
that data.

-- 
--------------------------------- personal: http://www.armory.com
/~spectre/ ---
  Cameron Kaiser * Floodgap Systems * www.floodgap.com *
ckaiserfloodgap.com
-- The point of good writing is knowing when to stop. --
Lucy Montgomery ------

On Sep 25, 2006, at 8:30 AM, David Brownlee wrote:

> 	The next question would be... are you interested in
doing the
> 	initial version of this? 

I am willing to work on that unless someone would rather do
it.

Bryan

On Sep 25, 2006, at 8:36 AM, Cameron Kaiser wrote:

>>> http://www.macbsd.com/macbsd/macbsd-docs/machine-status/

>>> htt
p://www.netbsd.org/Ports/mac68k/curr_info.html
>
>>  	The next question would be... are you interested
in doing the
>>  	initial version of this? 
>
> I've actually been considering doing a new version of
the page for  
> awhile
> as my contribution back to NetBSD. If no one else is
highly  
> interested in
> the job, I'd be willing to be a central reporting point
for working  
> configs
> and to create a new model and hardware support page
based on that  
> data.

That works for me.

Bryan

On Mon, 25 Sep 2006, Bryan Vyhmeister wrote:

> On Sep 25, 2006, at 8:36 AM, Cameron Kaiser wrote:
>
> >>> http://www.macbsd.com/macbsd/macbsd-docs/machine-status/

> >>> htt
p://www.netbsd.org/Ports/mac68k/curr_info.html
> >
> >>  	The next question would be... are you
interested in doing the
> >>  	initial version of this? 
> >
> > I've actually been considering doing a new version
of the page for
> > awhile
> > as my contribution back to NetBSD. If no one else
is highly
> > interested in
> > the job, I'd be willing to be a central reporting
point for working
> > configs
> > and to create a new model and hardware support
page based on that
> > data.
>
> That works for me.
>
> Bryan

I'd like to contribute with reports about my mac68k models
(IIvi, P600,
LCII, LCIII, LC450, LC475, Q700, Q950). So just say to whom
and when
should we send the reports (I'd like to send also dmesg for
this macs).

Concerning the NetBSD 3.0 on this machines: I am having
problems
installing 3.0 on any 68030 based mac (FTP installation). I
am getting a
lot of errors about .tgz archive being corrupted if the file
is bigger
than a given size (e.g. etc.tgz  installs ok but not the
base.tgz or even
the kernel_GENERIC.tgz despite the fact that MacOS 7.6.1
works without
problems on the same computer). The same release with the
same HDD
installs just fine on a 68040 based Mac (e.g. Q700).

Regards,

Gheorghe Ardelean (Johny).

> > >>> http://www.macbsd.com/macbsd/macbsd-docs/machine-status/

> > >>> htt
p://www.netbsd.org/Ports/mac68k/curr_info.html

> > > I've actually been considering doing a new
version of the page [...]

> I'd like to contribute with reports about my mac68k
models (IIvi, P600,
> LCII, LCIII, LC450, LC475, Q700, Q950). So just say to
whom and when
> should we send the reports (I'd like to send also dmesg
for this macs).

What I might end up doing is making a form to just cut and
paste dmesg output
into, and parsing those to make up the support matrix. How
do people find
that?

-- 
--------------------------------- personal: http://www.armory.com
/~spectre/ ---
  Cameron Kaiser * Floodgap Systems * www.floodgap.com *
ckaiserfloodgap.com
-- Murphy's Law is recursive. Washing your car to make it
rain doesn't work. --

Hi,

> Concerning the NetBSD 3.0 on this machines: I am having
problems
> installing 3.0 on any 68030 based mac (FTP
installation). I am getting a
> lot of errors about .tgz archive being corrupted if the
file is bigger
> than a given size (e.g. etc.tgz  installs ok but not
the base.tgz or even
> the kernel_GENERIC.tgz despite the fact that MacOS
7.6.1 works without
> problems on the same computer). The same release with
the same HDD
> installs just fine on a 68040 based Mac (e.g. Q700).

I experienced this same problem when installing NetBSD 3 and
2 on my
68040-based Quadra 700 with the 'SONIC' sn(4) Ethernet chip.

What I don't recall is if NetBSD 1.6.x had this problem too.
In fact it's something weird, since sometimes all the files
transfer
fine without corruptions but sometimes (especially in
'large' files
such as 'xfont.tgz' or 'base.tgz') they get corrupted and
get checksum
errors...

     -Marco

On Sep 26, 2006, at 7:33 AM, Cameron Kaiser wrote:

> What I might end up doing is making a form to just cut
and paste  
> dmesg output
> into, and parsing those to make up the support matrix.
How do  
> people find
> that?

That sounds good to me.

Bryan

At 13:59 Uhr +0200 26.9.2006, Gheorghe Ardelean wrote:
>I am having problems
>installing 3.0 on any 68030 based mac (FTP
installation). I am getting a
>lot of errors about .tgz archive being corrupted if the
file is bigger
>than a given size (e.g. etc.tgz  installs ok but not the
base.tgz or even
>the kernel_GENERIC.tgz despite the fact that MacOS 7.6.1
works without
>problems on the same computer). The same release with
the same HDD
>installs just fine on a 68040 based Mac (e.g. Q700).

Check the RAM.

I have lost countless hours with a Q700/68 MB that would run
just fine with
System 7.x and NetBSD 1.5.x, but would fail installing any
later NetBSD
version, complaining about corrupted archives.

In the end NewerTech's Guru showed me one (1) sticky byte in
the 64 MBytes
of RAM, apparently high enough in the memory map that
neither MacOS nor
netbsd 1.5 ever used it.

	hauke

--
"It's never straight up and down"     (DEVO)