Date: Tue, 28 Jan 1997 15:34:33 -0800 (PST) From: Simon Shapiro <Shimon@i-Connect.Net> To: (Joerg Wunsch) <joerg_wunsch@uriah.heep.sax.de> Cc: hackers@freebsd.org, (J Wunsch) <j@uriah.heep.sax.de> Subject: Re: 2.2-BETA Questions Message-ID: <XFMail.970128170519.Shimon@i-Connect.Net> In-Reply-To: <Mutt.19970128092153.j@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi J Wunsch; On 28-Jan-97 you wrote:
...
> 2.1.6 is the latest release.
> 2.2 is the next release, currently in post-BETA.
> 3.0 is the head of the development (``3.0-current'')
Thanx. Iam now doubly aware of these intricacies. I am also of
the understanding that all three are actively maintained. How do
bug fixes cross the lines? Ah. something to learn...
...
[ Linux NFS Server mess ]
> That's funny. Never seen this, but i never had an occasion to test
> against a Linux NFS server.
The solution is to mount with the resvport option. Go figure :-)
Thanx to all...
...
> ENXIO. You `cd' driver seems confused.
I know it is ENXIO. I know the CD driver is confused. I am too
new to FreeBSD to maintain this code (which I assume has a
maintainer...)
> You could hook a few printf's into /sys/scsi/cd.c (inside cd_open())
> to see which of the ENXIO's hits. Either the drive claims there's no
> medium inside, or it fails a READ CAPACITY command.
This sounds like debugging to me... ;-) Who is the maintainer?
Maybe {s{he can help?
> What drive is it?
wdc1 at 0x170-0x177 irq 15 on isa
wdc1: unit 0 (atapi): <FX600S/P01>, removable, intr, dma, iordis
The drive wooked correctly for a few days, but will refuse to mount
iso9660 disks after playing music ones. Now the roles reveresed.
> Of course, all this doesn't matter. ENXIO must not be confused with
> any part on the device node itself. It's a plain driver message.
I also understand that. It was posted in case minor/major error.
>
> > 4. Shutdown questions:
> >
> > a. When init goes to single user, prompts, asking for a shell.
> > You press ENTER and it sits on ``(.???msg - Cannot exactly
> > remember) not found''
> > ^C will get you a prompt, most of the time. Sometimes you get
> > a fast roll talking about some malloc() failure. Sometimes a
> > ^C will stop it, sometimes it will not.
>
> David Greenman has been the only one by now who also reported such a
> behaviour.
So now there is a confirmation...
...
> Well, that's what the `-a' means: umount everything in fstab.
Ah. BSD vs. SYSV. Sorry. But ``wolud be nice'' if shutdown would
really shut down the system, and correctly too. Even Linux
(Debian) now knows to do that, finally.
> Btw., try `cdcontrol' to play your audio CD, and see if it does make a
> difference. xmcd is a little too funny to trust it as a generic
> debugging tool. They have a tendency to hack on the SCSI bus, so i
> wouldn't be surprised if this leaves the driver confused if something
> behaves different on your drive.
Tried that. No change. Also tried cd[0-2]*. Just in case.
Same thing.
...
> This seems to happen only on your system, for whatever reason. I know
> of several people who are running a partition that is full-size the
> slice (or entire disk).
As I posted before, this happens unless I use disklabel with
/etc/disktab. The system will crash, but AFTER reboot the very
same partition is OK. I suspect something fishy...
...
> If it's assigned using the config stuff, the ISA bus driver code will
> assure this. Some drivers (like syscons) don't fit right; they
> use too many ports to describe in config's syntax.
>
> The number of ports used by this driver is returned from the driver
> attach routine.
Ah. But I need to write one. I just need to ``know'' that. Easy.
The question was relating to a PCI controller's driver which wants
to know if an IDE card is in that slot already (The card in
question is a SCSI card that can ``play IDE'' if setup correctly.
Thanx for your support.
Simon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.970128170519.Shimon>