daily CVS update output
Updating src tree: P src/distrib/sets/lists/debug/shl.mi P src/external/gpl3/binutils/lib/libbfd/arch/x86_64/bfdver.h P src/sys/arch/amd64/amd64/genassym.cf P src/sys/arch/arm/nxp/if_enet_imx.c P src/sys/arch/i386/i386/genassym.cf P src/sys/arch/x86/include/specialreg.h P src/usr.sbin/sysinst/bsddisklabel.c Updating xsrc tree: Killing core files: Updating release-8 src tree (netbsd-8): Updating release-8 xsrc tree (netbsd-8): Updating release-9 src tree (netbsd-9): Updating release-9 xsrc tree (netbsd-9): Updating release-10 src tree (netbsd-10): U doc/CHANGES-10.0 P external/gpl3/gcc.old/dist/libsanitizer/sanitizer_common/sanitizer_interceptors_ioctl_netbsd.inc P external/gpl3/gcc.old/dist/libsanitizer/sanitizer_common/sanitizer_platform_limits_netbsd.cc P external/gpl3/gcc.old/dist/libsanitizer/sanitizer_common/sanitizer_platform_limits_netbsd.h P sys/arch/evbarm/conf/GENERIC64 P sys/external/bsd/compiler_rt/dist/lib/sanitizer_common/sanitizer_interceptors_ioctl_netbsd.inc P sys/external/bsd/compiler_rt/dist/lib/sanitizer_common/sanitizer_platform_limits_netbsd.cc P sys/external/bsd/compiler_rt/dist/lib/sanitizer_common/sanitizer_platform_limits_netbsd.h P usr.sbin/tprof/tprof.c Updating release-10 xsrc tree (netbsd-10): Updating file list: -rw-rw-r-- 1 srcmastr netbsd 48683734 Dec 28 03:14 ls-lRA.gz
Re: 10.0 BETA: Managed to get boot menu; it doesn't find kernel though
On Tue, Dec 27, 2022 at 09:00:05AM -0800, Paul Goyette wrote: > Check out /boot.cfg (on NetBSD root partition) and/or /EFI/boot.cfg (on > the UEFI partition, not on the NetBSD root). Placing this in boot.cfg in the same directory as bootx64.efi worked! Thanks. -- Mayuresh
Re: 10.0 BETA: Managed to get boot menu; it doesn't find kernel though
On Tue, 27 Dec 2022, Mayuresh wrote: On Tue, Dec 27, 2022 at 10:10:24PM +0530, Mayuresh wrote: The kernel happens to be on /dev/dk5. Is it required to be copied on the UEFI partition? Or alternatively, how to specify the disk path to a UEFI boot option? I figured out that boot hd0f:netbsd boots from the boot prompt, but where to write this information? Check out /boot.cfg (on NetBSD root partition) and/or /EFI/boot.cfg (on the UEFI partition, not on the NetBSD root). You may need to adjust. ++--+--+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses:| | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com| | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | | & Network Engineer | | pgoyett...@gmail.com | ++--+--+
Re: 10.0 BETA: Managed to get boot menu; it doesn't find kernel though
On Tue, Dec 27, 2022 at 10:10:24PM +0530, Mayuresh wrote: > The kernel happens to be on /dev/dk5. Is it required to be copied on the > UEFI partition? Or alternatively, how to specify the disk path to a UEFI > boot option? I figured out that boot hd0f:netbsd boots from the boot prompt, but where to write this information? -- Mayuresh
10.0 BETA: Managed to get boot menu; it doesn't find kernel though
On a laptop that allows me to add UEFI boot option, I could choose the path of bootx64.efi and the netbsd option appears in the UEFI menu on boot. On choosing this option when booting, I get the boot prompt. But on choosing default option 1 to boot normally, it complains that it doesn't find the netbsd kernel. The kernel happens to be on /dev/dk5. Is it required to be copied on the UEFI partition? Or alternatively, how to specify the disk path to a UEFI boot option? -- Mayuresh
Re: Kernel config options for drm [ Was Re: No HDMI output... ]
On 27 December 2022 15:01:40 (+00:00), Mayuresh wrote: > On Tue, Dec 27, 2022 at 02:56:07PM +, Chavdar Ivanov wrote: > > > > Had it worked on 9.99.x / 10.0 BETA as well? > > > > Yes. > > Sounds great. Was it with the GENERIC (default) kernel or did you have to > tweak anything? > GENERIC. It's been many years since I had to build a custom kernel for any reason. -- Chavdar Ivanov
Re: Kernel config options for drm [ Was Re: No HDMI output... ]
On Tue, Dec 27, 2022 at 02:56:07PM +, Chavdar Ivanov wrote: > > > Had it worked on 9.99.x / 10.0 BETA as well? > > Yes. Sounds great. Was it with the GENERIC (default) kernel or did you have to tweak anything? -- Mayuresh
Re: Kernel config options for drm [ Was Re: No HDMI output... ]
On 27 December 2022 14:51:29 (+00:00), Mayuresh wrote: > On Tue, Dec 27, 2022 at 02:33:27PM +, Chavdar Ivanov wrote: > > > #i915drm* at drm? # Intel i915, i945 DRM driver > > > #mach64drm* at drm? # mach64 (3D Rage Pro, Rage) DRM > > driver > > > #mgadrm*at drm? # Matrox G[24]00, G[45]50 DRM driver > > > #r128drm* at drm? # ATI Rage 128 DRM driver > > > #radeondrm* at drm? # ATI Radeon DRM driver > > > #savagedrm* at drm? # S3 Savage DRM driver > > > #sisdrm*at drm? # SiS DRM driver > > > #tdfxdrm* at drm? # 3dfx (voodoo) DRM driver > > > i915drmkms* at pci? dev ? function ? > > > radeondrmkmsfb* at radeonfbbus? > > > #viadrmums* at drm? > > > > That's the default... > > Right. But do I need to tinker with the defaults to get it working? Also > the nomenclature i915drm vs i915drmkms or radeondrm vs radeondrmkmsfb > isn't clear to me - which one is which? > > > Just in case someone is interested, this is what I get now (on 10.99.2 from > > yesterday, but it has been like that since I installed this graphics card): > > Had it worked on 9.99.x / 10.0 BETA as well? Yes. I installed NetBSD on this system sometimes around mid-September, it has generally worked like that since then. Well, perhaps a little later - it had initially an NVidia Quadro 600, which I swapped with the FirePro W5000 shortly after. > -- Chavdar Ivanov
Re: Kernel config options for drm [ Was Re: No HDMI output... ]
On Tue, Dec 27, 2022 at 02:33:27PM +, Chavdar Ivanov wrote: > > #i915drm* at drm? # Intel i915, i945 DRM driver > > #mach64drm* at drm? # mach64 (3D Rage Pro, Rage) DRM > driver > > #mgadrm*at drm? # Matrox G[24]00, G[45]50 DRM driver > > #r128drm* at drm? # ATI Rage 128 DRM driver > > #radeondrm* at drm? # ATI Radeon DRM driver > > #savagedrm* at drm? # S3 Savage DRM driver > > #sisdrm*at drm? # SiS DRM driver > > #tdfxdrm* at drm? # 3dfx (voodoo) DRM driver > > i915drmkms* at pci? dev ? function ? > > radeondrmkmsfb* at radeonfbbus? > > #viadrmums* at drm? > > That's the default... Right. But do I need to tinker with the defaults to get it working? Also the nomenclature i915drm vs i915drmkms or radeondrm vs radeondrmkmsfb isn't clear to me - which one is which? > Just in case someone is interested, this is what I get now (on 10.99.2 from > yesterday, but it has been like that since I installed this graphics card): Had it worked on 9.99.x / 10.0 BETA as well? -- Mayuresh
Re: Kernel config options for drm [ Was Re: No HDMI output... ]
On 27 December 2022 14:22:42 (+00:00), Mayuresh wrote: > On Mon, Dec 26, 2022 at 10:01:32PM +0530, Mayuresh wrote: > > # dmesg | grep -i -e Radeon -e drm > > [ 1.04] cpu0: AMD A6-9225 RADEON R4, 5 COMPUTE CORES 2C+3G , id 0x670f00 > > [ 1.04] cpu1: AMD A6-9225 RADEON R4, 5 COMPUTE CORES 2C+3G , id 0x670f00 > > [ 1.047740] genfb0 at pci0 dev 1 function 0: ATI Technologies Radeon R2/R3/R4/R5 Graphics (rev. 0xea) > > [ 1.047740] drm at genfb0 not configured > > > > Please suggest whether a kernel reconfiguration is required for HDMI to > > work. > > To be more specific: > > # config -x | grep drm > #i915drm* at drm? # Intel i915, i945 DRM driver > #mach64drm* at drm? # mach64 (3D Rage Pro, Rage) DRM driver > #mgadrm*at drm? # Matrox G[24]00, G[45]50 DRM driver > #r128drm* at drm? # ATI Rage 128 DRM driver > #radeondrm* at drm? # ATI Radeon DRM driver > #savagedrm* at drm? # S3 Savage DRM driver > #sisdrm*at drm? # SiS DRM driver > #tdfxdrm* at drm? # 3dfx (voodoo) DRM driver > i915drmkms* at pci? dev ? function ? > radeondrmkmsfb* at radeonfbbus? > #viadrmums* at drm? That's the default... > > > i915drm is disabled, but i915drmkms is enabled. Similarly radeondrm is > disabled and radeondrmkmsfb is enabled. What does this exactly mean? > > Also, how to interpret the message "drm at genfb0 not configured". > > # config -x | grep genfb > # enable splash screen support; requires genfb or radeonfb > genfb* at pci? dev ? function ? > genfb* at vmbus? # Hyper-V Synthetic Video Framebuffer Just in case someone is interested, this is what I get now (on 10.99.2 from yesterday, but it has been like that since I installed this graphics card): ... radeon0 at pci1 dev 0 function 0: ATI Technologies FirePro W5000 (rev. 0x00) [drm] initializing kernel modesetting (PITCAIRN 0x1002:0x6809 0x1002:0x0B06 0x00). [drm] register mmio base: 0xf050 [drm] register mmio size: 262144 radeon0: VRAM: 2048M 0x - 0x7FFF (2048M used) radeon0: GTT: 2048M 0x8000 - 0x [drm] Detected VRAM RAM=800M, BAR=256M [drm] RAM width 256bits DDR [drm] radeon: 2048M of VRAM memory ready [drm] radeon: 2048M of GTT memory ready. [drm] Loading pitcairn Microcode [drm] Internal thermal controller with fan control [drm] radeon: dpm initialized [drm] Found VCE firmware/feedback version 50.0.1 / 17! [drm] GART: num cpu pages 524288, num gpu pages 524288 [drm] PCIE gen 2 link speeds already enabled [drm] PCIE GART of 2048M enabled (table at 0x001D6000). radeon0: WB enabled radeon0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x0x87e4da456c00 radeon0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x0x87e4da456c04 radeon0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x0x87e4da456c08 radeon0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x0x87e4da456c0c radeon0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x0x87e4da456c10 radeon0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x0x99844f3f5a18 radeon0: fence driver on ring 6 use gpu addr 0x8c18 and cpu addr 0x0x87e4da456c18 radeon0: fence driver on ring 7 use gpu addr 0x8c1c and cpu addr 0x0x87e4da456c1c [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] Driver supports precise vblank timestamp query. radeon0: radeon: MSI limited to 32-bit radeon0: radeon: using MSI. radeon0: interrupting at msi9 vec 0 (radeon0) [drm] radeon: irq initialized. [drm] ring test on 0 succeeded in 3 usecs [drm] ring test on 1 succeeded in 1 usecs [drm] ring test on 2 succeeded in 1 usecs [drm] ring test on 3 succeeded in 7 usecs [drm] ring test on 4 succeeded in 7 usecs [drm] ring test on 5 succeeded in 2 usecs [drm] UVD initialized successfully. [drm] ring test on 6 succeeded in 24 usecs [drm] ring test on 7 succeeded in 4 usecs [drm] VCE initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 1 succeeded in 0 usecs [drm] ib test on ring 2 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs [drm] ib test on ring 4 succeeded in 0 usecs [drm] ib test on ring 5 succeeded [drm] ib test on ring 6 succeeded [drm] ib test on ring 7 succeeded [drm] Radeon Display Connectors [drm] Connector 0: [drm] DP-1 [drm] HPD4 [drm] DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c [drm] Encoders: [drm] DFP1: INTERNAL_UNIPHY2 [drm] Connector 1: [drm] DP-2 [drm] HPD5 [drm] DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c [drm] Encoders: [drm] DFP2: INTERNAL_UNIPHY2 [drm] Connector 2: [drm] DVI-I-1 [
Kernel config options for drm [ Was Re: No HDMI output... ]
On Mon, Dec 26, 2022 at 10:01:32PM +0530, Mayuresh wrote: > # dmesg | grep -i -e Radeon -e drm > [ 1.04] cpu0: AMD A6-9225 RADEON R4, 5 COMPUTE CORES 2C+3G , id > 0x670f00 > [ 1.04] cpu1: AMD A6-9225 RADEON R4, 5 COMPUTE CORES 2C+3G , id > 0x670f00 > [ 1.047740] genfb0 at pci0 dev 1 function 0: ATI Technologies Radeon > R2/R3/R4/R5 Graphics (rev. 0xea) > [ 1.047740] drm at genfb0 not configured > > Please suggest whether a kernel reconfiguration is required for HDMI to > work. To be more specific: # config -x | grep drm #i915drm* at drm? # Intel i915, i945 DRM driver #mach64drm* at drm? # mach64 (3D Rage Pro, Rage) DRM driver #mgadrm*at drm? # Matrox G[24]00, G[45]50 DRM driver #r128drm* at drm? # ATI Rage 128 DRM driver #radeondrm* at drm? # ATI Radeon DRM driver #savagedrm* at drm? # S3 Savage DRM driver #sisdrm*at drm? # SiS DRM driver #tdfxdrm* at drm? # 3dfx (voodoo) DRM driver i915drmkms* at pci? dev ? function ? radeondrmkmsfb* at radeonfbbus? #viadrmums* at drm? i915drm is disabled, but i915drmkms is enabled. Similarly radeondrm is disabled and radeondrmkmsfb is enabled. What does this exactly mean? Also, how to interpret the message "drm at genfb0 not configured". # config -x | grep genfb # enable splash screen support; requires genfb or radeonfb genfb* at pci? dev ? function ? genfb* at vmbus? # Hyper-V Synthetic Video Framebuffer -- Mayuresh
10.0 BETA : Status of Wireless N
I have a couple of USB wifi adapters. With either of them Wireless G network works, but Wireless N isn't seen working, on NetBSD 10 BETA amd64. These are identified as: [ 2.564469] urtwn0: Realtek (0x0bda) 802.11n NIC (0x8179), rev 2.00/0.00, addr 3 and [ 410.103478] run0: Ralink (0x148f) 802.11 n WLAN (0x5370), rev 2.00/1.01, addr 6 Is N supported on 10.0 BETA? Is some configuration required to enable the same? Also, curiously, urtwn0 is yielding better speed than run0 on the same network. (Not sure if it's a driver issue or hardware issue. Will try both on Linux and check.) -- Mayuresh
