Testers needed for upcoming 3.1 release

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

please download the release candidate iso image here
ftp://ftp.netbsd.org/pub/NetBSD-daily/netbsd-3-1-RC2/2006090
31430Z/iso/
and test it ( does it boot, does the installer work properly
if you 
happen to have a partition you can wipe, etc. )
Right now I have only an iBook G4 ( works fine ) and a beige
G3 ( known 
to be troublesome ) to test so please try it on different
hardware and 
report failures, successes and so on.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRP3UO8pnzkX8Yg2nAQItywgAu/8CjUQ/w7yT62Og2QijfvlTRr1e
4+vn
5nbfEBnhY9A/F67Lw5j461FLtEoysT9ovb+z9JIYbJ3Erl8QEi8HG9dAiVbd
jRDS
zvxreHyAV81FsZ7QBXbzwkWcUycUOHWWzhv0JRc9dJF7jXgkYH1QzWQlwqja
FYOQ
QIW4+wH/4qpTr8Kl3g+8E8wjirBOhYmD4o8gxbHXzgnV/NZ0KgqB8ENoc4ZH
Vif9
iwMTVvnjThQzn4RnrgPaORMgTHwwT4H2NdYuEQ8X2HJw9PQ7Enbk+hEfII9s
pdzg
JbIwTHwE/JGfajZU7hocjH7O5x6RPAPTTGVa7Te2GR0DT1qKVkXT6w==
=uOvU
-----END PGP SIGNATURE-----

On 5-Sep-06, at 4:47 PM, Michael Lorenz wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> please download the release candidate iso image here
>
ftp://ftp.netbsd.org/pub/NetBSD-daily/netbsd-3-1-RC2/2006090
31430Z/ 
> iso/
> and test it ( does it boot, does the installer work
properly if you  
> happen to have a partition you can wipe, etc. )
> Right now I have only an iBook G4 ( works fine ) and a
beige G3  
> ( known to be troublesome ) to test so please try it on
different  
> hardware and report failures, successes and so on.

Negative on a Performa 6360. As we have discussed before, it
cannot  
boot from CD, and the install floppies *always* end up
timing out.

Furthermore, I am unable to boot a 3.x+ GENERIC kernel with
an  
already-installed system -- if I build a custom (smaller)
image, all  
works well.

Cheers,
Jared

Hi, Michael!

I'm a NetBSD user for several years with pmax, vax and i386
ports, but 
rather new to the mappc-port..
I have got a Powerbook5,8  bought in Nov. 2005 (with
15" display and the 
DVD/CD-ROM Superdrive).

I've downloaded the RC2-iso image and burned it onto a
CD-ROM. Is it 
correct, that the CD is not bootable?
So I copied the installation kernel file an the correspondig

kernel-symbols file to the root of the
"Mcintosh-HD" partition, which is 
the first HPFS+ partition (where I boot MAC OS X from).
I renamed the (corresponding, decompressed) files to
"netbsd" and 
"netbsd.sym" and also copied the ofwboot.xcf
from the CD-ROm to the same 
location

Then I booted into the OFW an did a    

 > boot hd:,ofwboot.xcf  netbsd

The kernel shows the hardware devices, it recognizes.
...
...
last devices, I can  see is:

usb2 at ...
ubusb2: ...
here the kernel output stops for a second or two, then

obio2 at pci1 dev2 ....
zsc0 at obio0 offset...
zstty0 at zsc0 ....
zstty0 at zsc0 ....
zstty1 at zsc0 ....
i2s at obio0 ,,,,

After this last line the system is switch off  (power off)
!!!

I had this also with rel. 3.0 and 3.01.
Is this a known problem? I saw a short comment on this in
the macppc 
list early this year, but no solution.

Result is: Installtaion is impossible!

I'd be really glad , if this problem could be fixed. I can
help on it in 
any way, pleae let me know!

Best regards. / Hilmar.

------------------------------------------------------------
------------------------------------------------------------
--

Michael Lorenz schrieb:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> please download the release candidate iso image here
>
ftp://ftp.netbsd.org/pub/NetBSD-daily/netbsd-3-1-RC2/2006090
31430Z/iso/
> and test it ( does it boot, does the installer work
properly if you 
> happen to have a partition you can wipe, etc. )
> Right now I have only an iBook G4 ( works fine ) and a
beige G3 ( 
> known to be troublesome ) to test so please try it on
different 
> hardware and report failures, successes and so on.
>
> have fun
> Michael
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (Darwin)
>
>
iQEVAwUBRP3UO8pnzkX8Yg2nAQItywgAu/8CjUQ/w7yT62Og2QijfvlTRr1e
4+vn
>
5nbfEBnhY9A/F67Lw5j461FLtEoysT9ovb+z9JIYbJ3Erl8QEi8HG9dAiVbd
jRDS
>
zvxreHyAV81FsZ7QBXbzwkWcUycUOHWWzhv0JRc9dJF7jXgkYH1QzWQlwqja
FYOQ
>
QIW4+wH/4qpTr8Kl3g+8E8wjirBOhYmD4o8gxbHXzgnV/NZ0KgqB8ENoc4ZH
Vif9
>
iwMTVvnjThQzn4RnrgPaORMgTHwwT4H2NdYuEQ8X2HJw9PQ7Enbk+hEfII9s
pdzg
>
JbIwTHwE/JGfajZU7hocjH7O5x6RPAPTTGVa7Te2GR0DT1qKVkXT6w==
> =uOvU
> -----END PGP SIGNATURE-----
>
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Sep 5, 2006, at 21:06, MLS wrote:

> I have got a Powerbook5,8  bought in Nov. 2005 (with
15" display and 
> the DVD/CD-ROM Superdrive).
>
> I've downloaded the RC2-iso image and burned it onto a
CD-ROM. Is it 
> correct, that the CD is not bootable?

The CD is bootable, just not in the way MacOS expects it.
Bootable as 
in there's something on it that OpenFirmware can run to
load an 
operating system.

> So I copied the installation kernel file an the
correspondig 
> kernel-symbols file to the root of the
"Mcintosh-HD" partition, which 
> is the first HPFS+ partition (where I boot MAC OS X
from).
> I renamed the (corresponding, decompressed) files to
"netbsd" and 
> "netbsd.sym" and also copied the
ofwboot.xcf from the CD-ROm to the 
> same location
>
> Then I booted into the OFW an did a
> > boot hd:,ofwboot.xcf  netbsd

'boot cd:,ofwboot.xcf' should have done the trick - what
happens when 
you try that? I know that the firmware used in 1st
generation iMacs 
won't load ofwboot.xcf from a CD but it works fine when run
from a 
harddisk. Yes, Apple OF is screwy.

> The kernel shows the hardware devices, it recognizes.
> ...
> ...
> obio2 at pci1 dev2 ....
> zsc0 at obio0 offset...
> zstty0 at zsc0 ....
> zstty0 at zsc0 ....
> zstty1 at zsc0 ....
> i2s at obio0 ,,,,
>
> After this last line the system is switch off  (power
off) !!!

Ouch. Please file a PR about that with as much from the
kernel's output 
as possible.

> I had this also with rel. 3.0 and 3.01.
> Is this a known problem? I saw a short comment on this
in the macppc 
> list early this year, but no solution.

Similar problems are known. There's code in the ADB driver
that's 
supposed to change display brightness when you press the
res. keys 
which is known to do Bad Things on some hardware. Do you
have any other 
macppc hardware to build a different kernel?
Maybe we should make this code optional, seems to break more
and more 
machines recently.

> I'd be really glad , if this problem could be fixed. I
can help on it 
> in any way, pleae let me know!

I'm pretty sure it can be worked around at least.
Someone's working on 
a rewrite of out PMU communication code, not sure when it
will be ready 
though.

So, if you can please build a kernel without
abtn*	at adb?
and see if that helps. If you can't build a kernel please
let me know 
and I'll build one for you.

thanks for testing the CD

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRP4bHMpnzkX8Yg2nAQIMoAf+LQ0rOhpcKwlL8I0o7fYI7hrTv5tX
3uC+
wyoBuBnKxSBLxKLtU+Rt5FiXjOlhJfiNUBxn90rMAtE5IIaWy05PJiYPdwJt
O8t6
WwAvccSWq4dIvcQCZRhtRRVJx2raFIie4jZcGy3pv4YXD2xyOkl6twvheRL7
T1iF
LIVJdu3FcR9GtMiJKAHgLp8bRs1Cy61JzI3c5+wKGYFX7L2FQEZRCF7wpVnT
ZaKh
rqd8Er1SiBN8XXRj1gDOIqCjqVDi8TP3aWtxVD7AxtCdtFFEqkkvlu3yfVhK
VueZ
GtTDRzuOgShV8yyC9ZiCI921aiwFgRr+v6sXOiWW5++VdKQsF4CgeQ==
=u6D0
-----END PGP SIGNATURE-----

On Sep 5, 2006, at 8:49 PM, Michael Lorenz wrote:

> I'm pretty sure it can be worked around at least.
Someone's working  
> on a rewrite of out PMU communication code, not sure
when it will  
> be ready though.
>
> So, if you can please build a kernel without
> abtn*	at adb?
> and see if that helps. If you can't build a kernel
please let me  
> know and I'll build one for you.
>

Does userconf not work? boot -a and add -c to the kernel
arguments to  
stop at userconf and just disable abtn. (That is if the
keyboard will  
work at this point)

jmcneillinvisible.ca wrote:

> Negative on a Performa 6360. As we have discussed
before, it cannot  
> boot from CD, and the install floppies *always* end up
timing out.

On my Apus2000/200 (603ev and Tsunami based compatible,
maybe
a similar machine with performa 6xxx) install floppies just
work.
Note the "TIME OUT" message actually means
floppy read errors.
(I also got it first)

I don't know how to specify to load ofwboot.xcf on HFS
partition
on OF 2 machines, but "boot scsi-int/sd3:0
NETBSD.MACPPC" method
(which is mentioned in INSTALL note) will never work.
(see PR toolchain/30245)
---
Izumi Tsutsui

---
Open Firmware, 2.0
To continue booting the MacOS type:
BYE<return>
To continue booting from the default boot device type:
BOOT<return>
 ok
0 > boot fd:0 -
OF_open bootpath=fd
read stage 2 blocks: 0123456. done!
starting stage 2...

>> NetBSD/macppc OpenFirmware Boot, Revision 1.10
>> (buildsb4.netbsd.org, Sun Sep  3 19:56:44 UTC
2006)
4473680
Please remove disk 1, insert disk 2, and press return...
+105536=0x45e26c
 start=0x100000
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002,
2003, 2004, 2005
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights
reserved.

NetBSD 3.1_RC2 (INSTALL) #0: Sun Sep  3 20:20:59 UTC 2006
	buildsb4.netbsd.org:/home/builds/ab/netbsd-3-1-RC2/macppc/2
00609031430Z-obj/home/builds/ab/netbsd-3-1-RC2/src/sys/arch/
macppc/compile/INSTALL
total memory = 65536 KB
avail memory = 57744 KB
no active packagemainbus0 (root)
cpu0 at mainbus0: 603ev (Revision 2.1), ID 0 (primary)
cpu0: HID0 90c001<DOZE,DPM,ICE,DCE,NOPTI>
cpu0: ohare L2 cache enabled
bandit0 at mainbus0
pci0 at bandit0 bus 0
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 11 function 0
pchb0: vendor 0x106b product 0x0008 (rev. 0x02)
epic0 at pci0 dev 13 function 0: SMC 83c170 Fast Ethernet,
rev. 6
epic0: interrupting at irq 23
epic0: SMC9432TX, Ethernet address 00:e0:29:1a:b1:ab
qsphy0 at epic0 phy 3: QS6612 10/100 media interface, rev. 1
qsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
obio0 at pci0 dev 16 function 0: addr 0xf3000000
mesh0 at obio0 offset 0x10000 irq 12: 50MHz, SCSI ID 7
scsibus0 at mesh0: 8 targets, 8 luns per target
zsc0 at obio0 offset 0x13000: irq 15,16
zstty0 at zsc0 channel 0 (console)
zstty1 at zsc0 channel 1
awacs at obio0 offset 0x14000 not configured
swim3 at obio0 offset 0x15000 not configured
nvram0 at obio0 offset 0x60000
adb0 at obio0 offset 0x16000 irq 18: 1 targets
akbd0 at adb0 addr 2: extended keyboard
wskbd0 at akbd0 mux 1
wdc0 at obio0 offset 0x20000 irq property not found; using
13: DMA transfer
atabus0 at wdc0 channel 0
md0: internal 2048 KB image area
Kernelized RAIDframe activated
scsibus0: waiting 2 seconds for devices to settle...
cd0 at scsibus0 target 3 lun 0: <MATSHITA, CD-ROM CR-506,
8S05> cdrom removable
wd0 at atabus0 drive 0: <Maxtor 82160D2>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 2014 MB, 4092 cyl, 16 head, 63 sec, 512 bytes/sect x
4124736 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2
(Ultra/33)
wd0(wdc0:0:0): using PIO mode 4, DMA mode 2 (using DMA)
boot device: <unknown>
root on md0a dumps on md0b
root file system type: ffs
WARNING: clock lost 115 days -- CHECK AND RESET THE DATE!
erase ^H, werase ^W, kill ^U, intr ^C, status ^T
mount_mfs: Unable to determine file system size
Terminal type? [vt100] 
Erase is backspace.
(I)nstall, (S)hell or (H)alt ? s
# 

On Sep 7, 2006, at 9:24 AM, Izumi Tsutsui wrote:

> wdc0 at obio0 offset 0x20000 irq property not found;
using 13: DMA  
> transfer

Is that "normal"? Can you dump your OF device
tree with ofdump and  
see if it does in fact have an IRQ property and we're not
parsing it  
correctly? I don't remember seeing that on any of the
bandit systems  
I played with in the past.

ctribodtcc.edu wrote:

> > wdc0 at obio0 offset 0x20000 irq property not
found; using 13: DMA  
> > transfer
> 
> Is that "normal"?

Yes. My Apus2000 has no AAPL,interrupt property for ATA:

---
0 > dev /bandit/ohare/ATA  ok
0 > .properties 
name                    ATA
device_type             ATA
reg                     00020000  00002000 
                        00008B00  00000200 
AAPL,connector          ata

 ok
0 > 
---

That's the reason why wdc_obio.c has such "using
default" path.

> Can you dump your OF device tree with ofdump and  
> see if it does in fact have an IRQ property and we're
not parsing it  
> correctly? I don't remember seeing that on any of the
bandit systems  
> I played with in the past.

Well, maybe my Apus2000 was the first 603 based macppc
which booted NetBSD, and I also wrote obio wdc driver in
1998.
Older OF implementation is quite awful anyway...
---
Izumi Tsutsui

jmcneillinvisible.ca wrote:

> Furthermore, I am unable to boot a 3.x+ GENERIC kernel
with an  
> already-installed system -- if I build a custom
(smaller) image, all  
> works well.

Just FYI, older (pre-2.0) bootloader (bootxx + ofwboot)
can't load
lager kernels than ~5MB.
http://cvsweb.netbsd.org/b
sdweb.cgi/src/sys/arch/macppc/stand/ofwboot/Makefile#rev1.42

---
Izumi Tsutsui

On Thu, 7 Sep 2006, Izumi Tsutsui wrote:
> Just FYI, older (pre-2.0) bootloader (bootxx + ofwboot)
can't load
> lager kernels than ~5MB.
> http://cvsweb.netbsd.org/b
sdweb.cgi/src/sys/arch/macppc/stand/ofwboot/Makefile#rev1.42


Ahh, that would be it -- I'm running the bootloader from
whichever the 
last release was that the install image fit on a single
floppy disk. I was 
unable to upgrade the bootstrap using the older
installboot/kernel 
combination, and the newer installboot binary failed on the
older kernel.

Thanks for the info!

Cheers,
Jared