https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521

--- Comment #250 from gn...@justmail.de ---
(In reply to Henri Hennebert from comment #240)

FYI, b1efa71bd7ebf308a59ae425d9b868e1f7c163b6 does not work for RTS5227. That
version produces timeouts and CMDx failures on my H730. During the
initialization the machine is frozen so that I cannot switch virtual consoles
but Ctrl-Alt-Del works ;) When the init code is done, the keyboard is
operational again. Additionally with that version the card detection is
inverted for me. Older versions (build through ports) have the card detection
correct.

Now some further observations: With ports version 2020-06-11/2020-06-16 the
driver works if I boot directly into FreeBSD when the machine is switched on.
Rebooting the machine into Windows 7 and then back again into FreeBSD results
in a non-working driver. If the card is inserted when loading the driver
failure output is generated. If the card is not inserted while loading the
driver, the driver prints information about the found HW but no card events are
printed. Unloading the driver yields something about "nothing attached".

Furthermore somehow I managed to confuse the older driver versions as well,
which then had the card detection inverted. I have to switched the machine off
and wait for a certain amount of time to get the HW back in state that the
older version like. I have no idea how I did that. Maybe booting Windows 7
first and then FreeBSD breaks the driver in a different way. IMHO this is a
strong indication that the HW initialization by the driver is incomplete.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Reply via email to