Installing FreeBSD 11.xx/12.xx - Atkbd0 GIANT LOCKED

freebsduser1234

New Member


Messages: 3

Hi
I use a Mini-PC with a Intel Celeron J1900 Quad Core CPU. This PC has 4 NICS (none are connected), 2 USB Ports (1 Keyboard, 1 Usb Stick with ISO) and VGA.

I tried all versions of FreeBSD (11 and 12). All versions stop loading at boot with the message:
atkbd0 : [GIANT LOCKED]

I tried using different keyboards, no keyboard, different USB sticks. Nothing works.
When installing any other linux which is not BSD based, it works perfectly fine.
Also, the installed USB sticks are perfectly valid and boot on my Intel Core i7 machine.

I also tried derivates, in this case pfsense, opnsense, ... it is definetely a question for the FreeBSD kernel.

Can someone assist? Im on this since a week without any solution.
Is it possible that some component on the mainboard is causing this issue?
 
B

badbrain

Guest


Hi
I use a Mini-PC with a Intel Celeron J1900 Quad Core CPU. This PC has 4 NICS (none are connected), 2 USB Ports (1 Keyboard, 1 Usb Stick with ISO) and VGA.

I tried all versions of FreeBSD (11 and 12). All versions stop loading at boot with the message:
atkbd0 : [GIANT LOCKED]

I tried using different keyboards, no keyboard, different USB sticks. Nothing works.
When installing any other linux which is not BSD based, it works perfectly fine.
Also, the installed USB sticks are perfectly valid and boot on my Intel Core i7 machine.

I also tried derivates, in this case pfsense, opnsense, ... it is definetely a question for the FreeBSD kernel.

Can someone assist? Im on this since a week without any solution.
Is it possible that some component on the mainboard is causing this issue?
Linux is unrelated to BSD, so Linux based on BSD doesn't exist, except you want to mention Debian GNU/kFreeBSD, which I think already deprecated.
I also see this [GIANT LOCKED] on VirtualBox but the boot process just continue and brings me to the login prompt. So I don't think it's about the keyboard at all.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 8,050
Messages: 31,634

I also tried derivates, in this case pfsense, opnsense, ... it is definetely a question for the FreeBSD kernel.
Look at their kernel outputs when it boots, what is detected after atkbd0?
 
OP
OP
F

freebsduser1234

New Member


Messages: 3

after atkbd0 the terminal does not show any more information and hangs. same for freebsd opnsense and pfsense.
is there a way i can access some more logs stored somewhere?
 

Phishfry

Son of Beastie

Reaction score: 1,524
Messages: 4,429

This sounds around the time that a serial console would kick in.
Make sure you have no settings for serial console in /boot/loader.conf
Try disabling any BIOS settings for serial console.
Maybe unplug your keyboard and see if it boots up.

Is this one of those little Qotum boxes?
 
OP
OP
F

freebsduser1234

New Member


Messages: 3

How can i mount the bootable USB Stick in Ubuntu so i can access /boot/loader.conf?
Or can i do this in the EFI Shell?

No its unfortunatelly a non-brand-mini-pc.
 

userxbw

Well-Known Member

Reaction score: 29
Messages: 294

I had to get into loader.conf once a little bit back, I just used my usb stick that I used to install this, then when it got to that one spot during the boot process of that stick, I selected shell when it showed the options, now having a root shell, I just used vi to get to loader.conf, edited what I needed to, saved it, then rebooted, and was allowed to boot in to the (my) system again.

Hope that helps.

I read back again and seen this is for VBox.... I don't think that is going to work.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 8,050
Messages: 31,634

Looking at a couple of different machines, the next step is psm(4), then uart(4). I also get a couple of apic(4) messages thrown in.

With regards to psm(4) check your BIOS for USB/PS2 compatibility settings.
For uart(4) maybe turn off the serial interfaces in the BIOS. Definitely make sure none of them are used to redirect the console (some BIOS's have that option).

Also check your SATA configuration, you can often switch between IDE, AHCI or RAID. Make sure it's set to AHCI.
 

olli@

Well-Known Member
Developer

Reaction score: 375
Messages: 486

after atkbd0 the terminal does not show any more information and hangs. same for freebsd opnsense and pfsense.
is there a way i can access some more logs stored somewhere?
Did you try booting in verbose mode? That's an option that can be selected in the boot menu, before the kernel starts. In verbose mode, the kernel prints a lot more information during the boot process. Maybe this will give you more output after the “atkbd0” line.
 

pgauret

New Member

Reaction score: 4
Messages: 9

At boot loader prompt, choose to configure boot options (or similar wording) and try:
unset hint.uart.1.at
boot


If this works, you can permanently comment the
Code:
hint.uart.1.at="isa"
entry in /boot/device.hints
 
Top