Installing 13.0-RELEASE on a new laptop

astyle said:
Looked through bsd-hardware.info... My hardware scan is the only one there with an N-KEY keyboard. Compared that with information from linux-hardware.org. Both places list device class as 03-01-01. And even Device ID looks similar: USB 0b05:19b6 for bsd-hardware.info, vs USB 0b05:1866 on linux-hardware.org...

Which suggests to me that covacat 's line


could be changed to:
hw.usb.quirk.0="0x0b05 0x1866 0 0xffff UQ_KBD_BOOTPROTO"

Does anyone think this just might work, or are there pitfalls to that idea?
Click to expand...
Tried that, no go. ?
 
astyle said:
ideas for other places
Click to expand...
The first time I try GhostBSD I had a mouse problem doesn't click till I plug it out and plug it in when I decide to try it again I didn't download the same ISO I download the latest one and I didn't have that issue, I know it doesn't make sense but this is what happens to me ¯\_(ツ)_/¯ u you can try to install it with another ISO.
 
Having the exact same issues on my asus zephyrus g15(13.1,13.2rc6,14current), keyboard registering randomly if I type fast and touchpad is dead.
compiled the asus modules based on the recommended links in this thread but nothing seems to work.
just for the record , Installing OpenBSD and everything is working perfectly, I don't understand why this I2C is not addresses during the installation.
 
ramib said:
Having the exact same issues on my asus zephyrus g15(13.1,13.2rc6,14current), keyboard registering randomly if I type fast and touchpad is dead.
compiled the asus modules based on the recommended links in this thread but nothing seems to work.
just for the record , Installing OpenBSD and everything is working perfectly, I don't understand why this I2C is not addresses during the installation.
Click to expand...
Just a few weeks ago, I tried playing with a 14-CURRENT boot iso on my Zephyrus. And, I discovered that the secret to making the keyboard register is frankly holding down the shift key as I type. In that case, the letters came out all lower-case. Pressing the Caps Lock key once (and still holding the shift key down afterwards) did make the letters come out in upper-case.

BUT...

I cannot type out the special characters like ~,@,#,%,^,&,*,(,),_,+,{,},|,:,",<,>,?...

I guess I will try OpenBSD on this thing sometime soon, just to see what's so different about how OpenBSD looks for a keyboard on my Zephyrus...
 
astyle said:
Just a few weeks ago, I tried playing with a 14-CURRENT boot iso on my Zephyrus. And, I discovered that the secret to making the keyboard register is frankly holding down the shift key as I type. In that case, the letters came out all lower-case. Pressing the Caps Lock key once (and still holding the shift key down afterwards) did make the letters come out in upper-case.

BUT...

I cannot type out the special characters like ~,@,#,%,^,&,*,(,),_,+,{,},|,:,",<,>,?...

I guess I will try OpenBSD on this thing sometime soon, just to see what's so different about how OpenBSD looks for a keyboard on my Zephyrus...
Click to expand...
completely different , enjoy , synaptics works perfectly
 
Actually tried OpenBSD on my Zephyrus... and while Xorg installs, and keyboard works, OpenBSD seems to be allergic to the USB-to-ethernet adapter! So I can't install anything beyond what's on the install ISO! ?

And, I have to correct myself on what it takes to properly type stuff under FreeBSD on my Zephyrus:

I have to simultaneously press down left Ctrl and nearly any one other key on the keyboard except:
  • Fn
  • Caps Lock
  • Windows
  • Alt (both left AND right keys)
  • Shift (both left AND right keys)
Shift key (when not part of the 2-key combo I have to press) doesn't work. Caps Lock key actually does, but it only capitalizes the letters, not special characters like : or " or even ~...

My hope is that a dev sees this, and can point out a fix that I can try...
 
tingo said:
Have you tried an external usb keyboard? I've had experiences in the past where that has helped.
Click to expand...
I have, and it works perfect, but kind of defeats the purpose.

I'd happily use a USB keyboard for diagnostics and troubleshooting of the issue if it helps me to tease out the correct parameters that solve my original issue.
 
astyle, I have the exact same laptop as you.... Well, I've replace the SSD in mine with 2TB and the Mediatek WiFi card with one from Intel, otherwise the same... ? I've tried to install GhostBSD several times, but after the live USB stick loads, the whole thing just froze in MATE — I thought something must have gone wrong in Xorg (eg., maybe something went wrong with the display or the mouse drivers), but since the keyboard or the hot keys to switch to console didn't work either, I figured maybe the entire Xorg got hosed or something. It didn't occur to me that there might be issues with built-in keyboard and mouse support until I recently tried to install FreeBSD instead.

tingo, thanks for the suggestion, as astyle have indicated, any subsequent USB keyboard plugged into the computer works perfectly, but this is a compact-to-medium sized laptop with a fairly decent touchpad mouse and keyboard (ie., when it is working), it would be a shame to have to lug around a separate keyboard and mouse just to get it to work with the OS....

I've got the laptop running Linux Mint 21.1 instead, which had no issues recognizing the keyboard or mouse. But I hate the way that everything is tied to systemd and it pisses me off trying to trace through the convoluted steps of how systemd works, but I digress.... I much rather help to get it working on FreeBSD.
 
astyle said:
Just a few weeks ago, I tried playing with a 14-CURRENT boot iso on my Zephyrus. And, I discovered that the secret to making the keyboard register is frankly holding down the shift key as I type. In that case, the letters came out all lower-case. Pressing the Caps Lock key once (and still holding the shift key down afterwards) did make the letters come out in upper-case.

BUT...

I cannot type out the special characters like ~,@,#,%,^,&,*,(,),_,+,{,},|,:,",<,>,?...

I guess I will try OpenBSD on this thing sometime soon, just to see what's so different about how OpenBSD looks for a keyboard on my Zephyrus...
Click to expand...
Just thinking out loud ...

Curious: does this shift/caps lock procedure only work with -CURRENT or is this behaviour also shown on for example 13.2-RELEASE?

As OpenBSD seems to work with your Zephyrus keyboard, that might be a good known fact to mention on the FreeBSD current mailing list. My guess is that more interest, cooperation and help would be forthcoming when a brotherly xBSD OS does support it (as compared to a Linux distro). Perhaps there is some useful info to be gained from an OpenBSD forum & mailing list as to how their driver works with respect to this particular internal keyboard, especially if it's all I2C driven ( what are its specifics? ) or has some "special sauce" (non-I2C) code.
 
Erichans said:
Curious: does this shift/caps lock procedure only work with -CURRENT or is this behaviour also shown on for example 13.2-RELEASE?
Click to expand...
I tried 13.1, 13.2, -RELEASE, -STABLE, everything. Same problem, no matter the version of FreeBSD...
 
minienigma said:
tingo, thanks for the suggestion, as astyle have indicated, any subsequent USB keyboard plugged into the computer works perfectly, but this is a compact-to-medium sized laptop with a fairly decent touchpad mouse and keyboard (ie., when it is working), it would be a shame to have to lug around a separate keyboard and mouse just to get it to work with the OS....
Click to expand...
I was suggesting this as a way to aid in debugging the issue, not a permanent fix. With a working keyboard on a machine, you can do things like booting it in verbose mode, turning on various debug knobs, etc. Sometimes, this (logs) helps to debug and pinpoint an issue, if you open a PR and describe the problem to the best of your ability.
 
tingo said:
I was suggesting this as a way to aid in debugging the issue, not a permanent fix. With a working keyboard on a machine, you can do things like booting it in verbose mode, turning on various debug knobs, etc. Sometimes, this (logs) helps to debug and pinpoint an issue, if you open a PR and describe the problem to the best of your ability.
Click to expand...
Please re-read this thread from the beginning, tingo ... what makes you think I haven't tried YOUR suggestions already?
 
astyle said:
Please re-read this thread from the beginning, tingo ... what makes you think I haven't tried YOUR suggestions already?
Click to expand...
I never said that you didn't try it; my advice was for others in this thread with the same problem - in case they didn't read the whole thread.
The world doesn't revolve around you, you know.
 
astyle said:
I got my hands on a nice new laptop, and I'm trying to install 13.0-RELEASE on it. But I'm experiencing weird issues that I have no idea how to troubleshoot (I last had any issues of that kind more than 5 years ago, so my brain has rusted on that topic since). The weird issue is: When I'm at the boot screen:
View attachment 13181
Laptop's keyboard starts out working fine. Escaping to loader prompt works fine. But when I try option 1 (Boot Multi user), the laptop's keyboard stops functioning. The weird thing is, if I plug in a USB keyboard and a USB mouse, that solves the problem. The mouse even works in bsdinstall, and I was able to install a barebones 13.0-RELEASE that way, and am able to use a USB keyboard to get around.

I have a USB->RJ45 adapter on the way (ordered it from Amazon), so I'm not worried too much about networking at this point.

I guess my question is: Is there a way to troubleshoot that kind of issue? As in, built-in keyboard not working, but USB keyboard working fine) I'm sure it cropped up before on older laptops - which is why I'm not sharing the brand of my laptop just yet. Can someone please share their troubleshooting experiences/solutions? I'd also appreciate pointers to info.
Click to expand...

Wow. That's funny. But I'm not surprised. I've seen funny bugs with FreeBSD before.

At the boot loader prompt, try adding some boot flags that might help. This can sometimes help with ACPI keyboard issues.

set hint.atkbd.0.flags="0x05" set hw.usb.no_boot_wait=1 boot

If you manage to boot into a shell with the USB keyboard, try manually loading the atkbd module

kldload atkbd

You might want to experiment with different console drivers. At the boot loader, try

set kern.vty=vt boot

If you think it's an ACPI issue, try booting without ACPI

set hint.acpi.0.disabled=1 boot

If none of these help, go down the rabbit hole of kernel debugging:

set boot_verbose=YES boot
 
astyle said:
Update: Got my USB to RJ45 adapter, and was able to SSH into the laptop, and even install editors/nano from quarterly packages. Legacy USB support is enabled (I actually did that before going ahead with the 13.0-RELEASE install, so I'm not sure if there's much to do in the BIOS any more.
--
It looks like there's still something I'm not doing right... The reddit post provided by grahamperrin suggested that I edit /boot/device.hints, and add the line, hint.atkbd.0.flags="4", which I did, rebooted, but no dice... ? I even tried reading the atkbd(4) manpage for hints, and to grep my own dmesg for anything that looks promising. (Complete output of dmesg is attached if anyone is interested).
Code: 
# dmesg | grep Keyboard
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x4 irq 1 on atkbdc0
ugen1.7: <SEM HCT Keyboard> at usbus1
ukbd4: <SEM HCT Keyboard, class 0/0, rev 1.10/1.10, addr 6> on usbus1
uhid0: <SEM HCT Keyboard, class 0/0, rev 1.10/1.10, addr 6> on usbus1
ugen1.7: <SEM HCT Keyboard> at usbus1 (disconnected)
# dmesg | grep kbd
WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 14.0.
kbd1 at kbdmux0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x4 irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 14.
ukbd0 on uhub4
ukbd0: <ASUSTeK Computer Inc.> on usbus0
kbd2 at ukbd0
ukbd1 on uhub4
ukbd1: <ASUSTeK Computer Inc.> on usbus0
kbd3 at ukbd1
ukbd2 on uhub4
ukbd2: <ASUSTeK Computer Inc.> on usbus0
kbd4 at ukbd2
ukbd3 on uhub4
ukbd3: <ASUSTeK Computer Inc.> on usbus0
kbd5 at ukbd3
ukbd4 on uhub5
ukbd4: <SEM HCT Keyboard, class 0/0, rev 1.10/1.10, addr 6> on usbus1
kbd6 at ukbd4
ukbd4: at uhub5, port 1, addr 6 (disconnected)
ukbd4: detached
Right now, I'm thinking, there may be some old instructions around on how to install a weird keyboard under FreeBSD - If somebody can point me to them (or help in other ways), that would be great! I vaguely recall such documentation being around, but my mind is rusty... ?
Click to expand...
Hmm. The built-in keyboard issue seems tied to the AT keyboard controller (atkbdc) or Advanced Configuration and Power Interface (ACPI). Based on the dmesg logs, atkbdc0 and atkbd0 are recognized, but errors such as ACPI-related failures and a note about "non-PNP ISA device" looks like a possible ACPI misconfiguration or conflicts, possibly with modern hardware like your AMD Ryzen 9 system.

Code: 
#!/bin/sh
{
    echo 'hw.acpi.disabled=1'
    echo 'hw.acpi.handle_reboot=1'
    echo 'hint.atkbd.0.disabled="1"'
    echo 'hint.atkbdc.0.disabled="1"'
} >> /boot/loader.conf
 
Douglas Burn said:
astyle, did you solve this problem? I have the same problem as you in FreeBSD 14.2. My keyboard does however work in 13.4 but it’s impractically slow.
Click to expand...
Wow, 13.4-RELEASE works??? Seems like my chance to try that! There's gotta be some kind of difference between what's in that release and what I've been trying so far...

Edit: Well, didn't work for me... typing is only possible as explained in post #56... This is looking still unresolved, as far as I can tell...
 
You must log in or register to reply here.
Back
Top