Date: Mon, 01 Oct 2001 19:53:53 +0300 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org> Cc: ache@nagual.pp.ru, msmith@FreeBSD.org, current@FreeBSD.org Subject: Re: ACPI: problem with fdc resource allocation Message-ID: <3BB89FA1.DD75D31C@FreeBSD.org> References: <3BA710D9.75544A23@FreeBSD.org> <3BA99FEA.7270C90A@FreeBSD.org> <3BB82160.8910B33A@FreeBSD.org> <20011002.005340.74695085.iwasaki@jp.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mitsuru IWASAKI wrote: > Hi, > > > Maxim Sobolev wrote: > > > > > Maxim Sobolev wrote: > > > > > > > "Andrey A. Chernov" wrote: > > > > > > > > > On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote: > > > > > > Hi, > > > > > > > > > > > > Finally decided to upgrade my current box to the post-ACPI/KSE and found > > > > > > that I'm having problem with resource allocation for floppy disk controller. > > > > > > I'm sure somebody already reported this some time ago, but the problems seems > > > > > > still here, so I would like to see it resolved. > > > > > > > > > > > fdc0: cannot reserve I/O port range (1 ports) > > > > > > > > > > It seems that here is conflict with your device.hints, try to remove fdc > > > > > from the hints. > > > > > > > > > > As I already write, it is very bad thing that ACPI is in conflicts with > > > > > default hints file correctly describing devices used. ACPI must ignore > > > > > duplicate devices from the hints. > > > > > > > > > > The problem with floppy is harder, because floppy controller present in > > > > > ACPI but the floppy itself not present (on my motherboard at least), so > > > > > in current situation fdc0 must not be in hints, but fd0 must be, it makes > > > > > whole thing even more cryptic. > > > > > > > > Doesn't work, exactly the same problem - see attached device.hints. > > > > > > Knock, knock... Is anybody home? > > > > Hmm, it is very sad to see that acpi code is totally unsupported, especially in the > > spite of recent "how to attract people to test -current" thread. The problem is still > > here, as of today's kernel. > > I'm not sure exactly what's the problem you are having, but it's too > little information to track it down... > Could you send acpi-jp@jp.freebsd.org ; > - acpidump output; like > # acpidump -o your_machine_name.dsdt > your_machine_name.dsdt.asl > I'll add them to > http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp > - dmesg output of kernel boot -v Just sent it to you privately. After hiting sed button I've realised that machine_name that you have requested != host_name. Since it isn't a brandname model you can identify it after the mainboard name - Tyan-S1590. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BB89FA1.DD75D31C>