Re: device.hints PCI detection conflict
In article [EMAIL PROTECTED] Andrey A. Chernov [EMAIL PROTECTED] wrote: Bootverbose shows that second copy of devices appearse on ASUS CUSL2-C or TUSL2-C: atkbdc-: atkbdc0 already exists, using atkbdc1 instead sc-: sc0 already exists, using sc1 instead vga-: vga0 already exists, using vga1 instead vga-: line is especially dangerous since cause fake second VGA detection (as MDA) which cause panic with recent duplicate make_dev panics commit. It looks like conflict with /boot/device.hints here. If I remove this line hint.sc.0.at=isa from device.hints, no fake second VGA appearse (the bug is gone), BUT... I have absolutely NO console output. If I put this line back, console oputput appearse and bug too. Removing atkbdc vga hints from device.hints cause atkbdc- vga- lines gone, which indicates conflict too. But sc hint can't be removed because it results with no console output. Please fix it somehow. In my case (ABIT's BP6 motherboard) the problem disapear after switching on ACPI (there is the problem with the fdc0 - cannot reserve I/O port range (1 ports) but now I can some time live without floppies :-). N.Dudorov To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: device.hints PCI detection conflict
On Sun, Oct 28, 2001 at 07:14:13 +0600, Nickolay Dudorov wrote: In article [EMAIL PROTECTED] Andrey A. Chernov [EMAIL PROTECTED] wrote: Bootverbose shows that second copy of devices appearse on ASUS CUSL2-C or TUSL2-C: atkbdc-: atkbdc0 already exists, using atkbdc1 instead sc-: sc0 already exists, using sc1 instead vga-: vga0 already exists, using vga1 instead vga-: line is especially dangerous since cause fake second VGA detection (as MDA) which cause panic with recent duplicate make_dev panics commit. It looks like conflict with /boot/device.hints here. If I remove this line hint.sc.0.at=isa from device.hints, no fake second VGA appearse (the bug is gone), BUT... I have absolutely NO console output. If I put this line back, console oputput appearse and bug too. Removing atkbdc vga hints from device.hints cause atkbdc- vga- lines gone, which indicates conflict too. But sc hint can't be removed because it results with no console output. Please fix it somehow. In my case (ABIT's BP6 motherboard) the problem disapear after switching on ACPI (there is the problem with the fdc0 - cannot reserve I/O port range (1 ports) but now I can some time live without floppies :-). In my case APCI or no ACPI gives absolutely no difference... -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
device.hints PCI detection conflict
Bootverbose shows that second copy of devices appearse on ASUS CUSL2-C or TUSL2-C: atkbdc-: atkbdc0 already exists, using atkbdc1 instead sc-: sc0 already exists, using sc1 instead vga-: vga0 already exists, using vga1 instead vga-: line is especially dangerous since cause fake second VGA detection (as MDA) which cause panic with recent duplicate make_dev panics commit. It looks like conflict with /boot/device.hints here. If I remove this line hint.sc.0.at=isa from device.hints, no fake second VGA appearse (the bug is gone), BUT... I have absolutely NO console output. If I put this line back, console oputput appearse and bug too. Removing atkbdc vga hints from device.hints cause atkbdc- vga- lines gone, which indicates conflict too. But sc hint can't be removed because it results with no console output. Please fix it somehow. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
