Re: current installation image fails to boot up

[bsdprg%tuta.io@localhost]

Jun 4, 2023, 15:20 by lloyd%must-have-coffee.gen.nz@localhost:

> You can use "userconf" commands from the boot prompt to disable auto-detection of problematic devices. You should be able to interrupt the boot and disable ugen0 with the command "userconf disable ugen*".
>
> You can also put that command into boot.cfg so that you don't have to interrupt the boot process and type it in all the time. It's all in the manual pages for "boot" and "boot.cfg".
>
> Cheers,
> Lloyd
>

Thank you, Lloyd. I was trying to install the current version. So, I think I need to boot in a single user mode on the boot prompt, make this change to boot.cfg and then boot again to install it.


>
> On 2/06/23 14:10, bsdprg%tuta.io@localhost wrote:
>
>> When I boot up from the NetBSD HEAD image, it fails to enumerate USB devices and I get this error:
>>
>> ubt0: vendor 8087 (Ox8087) product 0a2b (Ox0a2b), rev 2.00/0.10, addr 3
>> ugen0 at uhub1 port 10
>> ugenB: Broadcon Corp (Ox0a5c) 5888 (Ox5832), rev 1.10/1.01, addr 4
>> panic: kernel diagnostic assertion “dev=>ud_ifaces == NULL” failed: file "/usr/src/sys/dev/usb/usb_subr.c", line 870, ud_ifaces=OxfffTadv425d89940
>> cpul: Begin traceback...
>> vpanic() at netbsd:vpanic+0x173
>> kern_assert() at netbsd:kern_assert+Ox4b
>> usbd_set_config_index() at netbsd:usbd_set_config_index+0x59d
>> ugenif_attach() at netbsd:ugenif_attach+0x241
>> ugen_attach() at netbsd:ugen_attach+0x5c
>> config_attach_internal() at netbsd:config_attach_internal+0x1a7
>> config_found_acquire() at netbsd:config_found_acquire+0xd9
>> config_found() at netbsd:config_found+0x32
>> usbd_attachwholedevice() at netbsd:usbd_attachwholedevice+0xf8
>> usbd_probe_and_attach() at netbsd:usbd_probe_and_attach+0x14a
>> xhci_new_device() at netbsd:xhci_new_device+0x54a
>> uhub_explore() at netbsd:uhub_explore+0x4bd
>> usb_discover() at netbsd:usb_discover+0x4f
>> usb_event_thread() at netbsd:usb_event_thread+0x46
>> cpul: End traceback... :
>>
>> I did an OCR from a camera image, and tried my best to fix the text. So, some text might be a little off. Does anyone know the workaround for this?
>>
>> Thank youSalil
>>