Hi,

I've just installed this snapshot and have a couple questions:

I have an internal quantum drive and an external IBM drive with scsi id =
2
This set up works perfectly (I mean there : no termination or id=20
problems) BUT
here is some of my dmesg output:

sd0 at scsibus0 target 0 lun 0: <QUANTUM, MAVERICK 270S, 0901> SCSI2=20
0/direct fixed
sd0: 258 MB, 2853 cyl, 2 head, 92 sec, 512 bytes/sect x 528879 sectors
sd1 at scsibus0 target 2 lun 0: <, , > SCSI2 0/direct fixed
sd1: 2063 MB, 7936 cyl, 3 head, 177 sec, 512 bytes/sect x 4226725 =
sectors
sd2 at scsibus0 target 2 lun 1: <, , > SCSI2 0/direct fixed
sd2: mode sense (5) returned nonsense; using fictitious geometry
sd2: 1315 MB, 1315 cyl, 64 head, 32 sec, 512 bytes/sect x 2694437 =
sectors

So sd1 is my IBM drive (and I could mount it), but it used to be=20
recognized better (name of manufacturer, etc...) with an earlier=20
snapshot (1.5X)
But sd2 is quite strange !

Second, here is another part of the dmesg output:
total memory =3D 16384 KB
avail memory =3D 27020 KB

This is obviously not right, and has been happening for a long time now.=20=

I don't see a PR for that. Should I send one ?

Finally,
PR #13334 (http://www.NetBSD.org/cgi-bin/query-pr-
single.pl?number=3D13334, NetBSD Problem Report #13334: "reboot" command=20=

causes kernel panic) is still happening with this snapshot.
This is not critical, but still annoying. Who should I mail to so that=20=

it may be fixed ?

R=E9mi

Le vendredi 28 d=E9cembre 2001, =E0 08:06 , Space Case a =E9crit :

> Hi.
>
> They've been there a couple of days, but I just got around to putting=20=

> them
> in place....
>
> There's a new snapshot at:
>
>  =20
> =
ftp://ftp.netbsd.org/pub/NetBSD/arch/mac68k/snapshot/elf-20011222/binary/
>
> This snapshot is based on Dec. 22 sources.
>
> Enjoy,
> ~Steve

--
R=E9mi Zara
web: http://www.remi-zara.net/