Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IDE drivers or Nextor BIOSes conflict with each other if 2 separate IDE devices are used #63

Open
Wierzbowsky opened this issue Jul 22, 2020 · 0 comments
Labels
driver An issue related to a device driver (not to the Nextor kernel itself)

Comments

@Wierzbowsky
Copy link

Wierzbowsky commented Jul 22, 2020

When using Carnivore2 with Nextor 2.1.0 Beta 2 (IDE driver 0.1.5 or 0.1.7) in slot 1 of MSX2 computer (Yamaha YIS805/256) and FDD/IDE controller with Nextor 2.1.0 Alpha 2 (IDE driver 0.1.5) in slot 2, there's a conflict and the CF card in the FDD/IDE controller is not visible as a drive. When switching the IDE/FDD controller to the original Sunrise BIOS, the card becomes visible. Looks like there's a conflict between similar IDE drivers or BIOSes used on 2 separate IDE devices.

If there is a conflict between similar IDE drivers, only one of them should become active. I am no hardware expert, but I am pretty sure that the guys who write these drivers could adjust them to avoid such conflicts. The same problem was reported with other IDE devices, for example with Carnivore2 and Maxiol's IDE/CF controller with Nextor BIOS.

@Konamiman Konamiman added the driver An issue related to a device driver (not to the Nextor kernel itself) label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
driver An issue related to a device driver (not to the Nextor kernel itself)
Projects
None yet
Development

No branches or pull requests

2 participants