10.0 BETA : Poor audio quality if 3.5mm jack is fully inserted
On NetBSD 10.0 BETA, amd64, build of 10 Jan 23, on an asus laptop I face this problem: If I use a 3.5mm headphone jack the audio is of very poor quality, barely some sort of a noise. If I insert the jack partially, then the audio is proper, but only through the left speaker. The outputs.master2 control seems to be relevant to the headphone jack. Have set others to 0. $ mixerctl -a outputs.master=0,0 outputs.master2=254,254 inputs.reclvl=92,92 inputs.reclvl.mute=on outputs.master3=0,0 outputs.master3.mute=off record.monitor=0,0 outputs.master4=0,0 outputs.master4.mute=off inputs.reclvl2=0,0 inputs.reclvl2.mute=on outputs.dacsel=DAC00,DAC01 record.source=ADC02 Possibly relevant bits of dmesg $ grep audio /var/run/dmesg.boot hdaudio0 at pci0 dev 14 function 0: HD Audio Controller hdaudio0: interrupting at msi0 vec 0 hdaudio0: HDA ver. 1.0, OSS 6, ISS 7, BSS 0, SDO 1, 64-bit hdafg0 at hdaudio0 vendor 0x10EC product 0x0256 nid 0x01: Realtek product 0256 nid=02 [audio output] [source: dac] nid=03 [audio output] [source: dac] audio0 at hdafg0: playback, capture, full duplex, independent audio0: slinear_le:16 2ch 48000Hz, blk 1920 bytes (10ms) for playback audio0: slinear_le:16 2ch 48000Hz, blk 1920 bytes (10ms) for recording spkr0 at audio0: PC Speaker (synthesized) hdafg1 at hdaudio0 vendor 0x8086 product 0x280D nid 0x01: Intel HDMI/DP nid=02 [audio output] [source: dac] audio1 at hdafg1: playback, capture, full duplex, independent audio1: slinear_le:16 2ch 48000Hz, blk 1920 bytes (10ms) for playback audio1: slinear_le:16 2ch 48000Hz, blk 1920 bytes (10ms) for recording spkr1 at audio1: PC Speaker (synthesized) Note: On Linux the headphone jack works fine, with fully inserted jack both left and right speakers work. So no hardware issue. Please help. -- Mayuresh
Re: i915 observations
On Tue, Jan 17, 2023 at 11:14:39PM +, RVP wrote: > So, SNA is needed on both Linux and NetBSD. Yes, just that it works on Linux and not on NetBSD! I do not know if it's a kernel driver level problem or xorg driver level problem. I am suspecting it's the former. There is a PR. Let's see. -- Mayuresh
Re: i915 observations
Just reviving this thread in the new year. Story so far for my laptop is: - On Linux both eDP and HDMI work fine, even with rotation. Linux uses intel driver with SNA acceleration. - On NetBSD 10.0 BETA, only intel driver works, only with UXA acceleration. No other driver or no other acceleration for intel driver works. In this mode rotation slows down refreshes on eDP alone as well as on HDMI (alone or together with eDP) - If I try UXA acceleration on Linux, it shows all the problems mentioned above on Linux as well. I have experimented with various options with UXA and SNA; using both native and modular X11 servers. None have helped so far. So, on the verge of giving up... That means once again no NetBSD on my laptop for indefinite time. Any suggestions are most welcome. -- Mayuresh
Re: Difference between i915drm and i915drmkms
On Sat, Jan 07, 2023 at 03:58:21PM +0700, Robert Elz wrote: > I doubt it is possible to make i915drm work on -10 or HEAD Ok. I get several linker errors if I enable i915drm, showing a few of them. ld: i915_dma.o:(.data+0x88): undefined reference to `i915_irq_emit' ld: i915_dma.o:(.data+0xa0): undefined reference to `i915_irq_wait' ld: i915_dma.o:(.data+0x160): undefined reference to `i915_vblank_pipe_set' ld: i915_dma.o:(.data+0x178): undefined reference to `i915_vblank_pipe_get' ld: i915_dma.o:(.data+0x190): undefined reference to `i915_vblank_swap' ld: ioconf.o:/usr/src/sys/arch/amd64/compile/MYKERNEL/ioconf.c:4868: undefined reference to `i915drm_ca' Perhaps it should be removed from the config to avoid confusion for some. -- Mayuresh
Difference between i915drm and i915drmkms
Have requested more information about these on multiple threads. Now stripping off all the context and just seeking to know the difference between these two drivers: $ config -x | grep i915 #i915drm* at drm? # Intel i915, i945 DRM driver i915drmkms* at pci? dev ? function ? -- Mayuresh
Re: Kernel config options for drm [ Was Re: No HDMI output... ]
> It works as close to perfect as one can desire. cad.onshape.com/check > returns some tens of millions tri/sec under the latest firefox. No > graphics artifacts whatsoever. Can you tell a bit more about cad.onshape.com? I can see it in "Measuring performance" state for long. Not sure what it is supposed to be reporting and after how long. -- Mayuresh
Re: NetBSD 10.0_BETA envstat hangs
On Thu, Jan 05, 2023 at 10:12:27AM +1300, Lloyd Parkes wrote: > 2) For the the fact that the device appears to be getting attached to > sysmon_envsys(9) even though device configuration failed. I filed for the other two, but did not find the word sysmon_envsys in dmesg. What observation shall I report in the PR? -- Mayuresh
NetBSD 10.0_BETA envstat hangs
envstat hangs (doesn't come out with Ctrl-C) on a laptop with following description: # uname -a NetBSD asusn 10.0_BETA NetBSD 10.0_BETA (GENERIC) #0: Mon Dec 19 14:00:35 UTC 2022 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 # dmesg | grep acpibat0 [ 1.046558] acpibat0 at acpi0 (BAT0, PNP0C0A-0): ACPI Battery [ 1.046558] acpibat0: ACPI 4.0 functionality present [ 2.056386] acpibat0: autoconfiguration error: failed to evaluate _STA: AE_NO_MEMORY [62.666971] acpibat0: workqueue busy: updates stopped Please advise. -- Mayuresh
Re: Does X11 user need permission to /dev/dri/card0
On Wed, Jan 04, 2023 at 06:30:05AM -, Michael van Elst wrote: > If the system crashes when you allow access, this means that > the DRM code is buggy Thanks. Logged a PR already. What do I miss if I don't give dri permission? E.g. would firefox be terribly slower? I can already see that I can't even run xscreensaver-demo. I can understand performance implications of not having access to dri, but this seems a functional restriction as well. -- Mayuresh
Re: 10.0 BETA : Status of Wireless N
On Wed, Jan 04, 2023 at 06:23:48AM -, Michael van Elst wrote: > Merging the FreeBSD wifi subsystem that supports 802.11n is work in > progress and is developed on a separate branch. Ok. Thank you for the information. > The Broadcom "full mac" chips (e.g. used by RaspberryPi) run most of > the Wifi protocol inside the firmware and will work with 802.11n networks. > Doesn't mean it is fast. > > If you are lucky, you can find the same chip with USB (only seen as the > orignal RPI Wifi dongle) or PCIe interface (some Mini-PCIe card). Are there `urndis' dongles - I couldn't find ones in a quick search. Basically, the way a mobile device will share its N network using USB tethering, but instead of mobile using a simple dongle. -- Mayuresh
Re: 10.0 BETA : Status of Wireless N
On Tue, Dec 27, 2022 at 07:35:56PM +0530, Mayuresh wrote: > Is N supported on 10.0 BETA? Is some configuration required to enable the > same? Which component decides this - firmware? driver? kernel? something else? 10.0 BETA seems to have up to date firmware in the right place, though I didn't notice explicit message showing it is loaded (may be it is not logged). In driver documentation (man urtwn) the title says `802.11b/g/n wireless network device', but no other mention of N mode. Is Wireless N generally not supported, or does it depend on the device? Are there any other devices for which on NetBSD I can get wireless N support? -- Mayuresh
Re: 10.0 BETA modular X11: amdgpu_dri.so not found
On Sun, Jan 01, 2023 at 12:56:31AM +0530, Mayuresh wrote: > Does base X11 provide and is it advisable to use the base X11 for this > hardware? Installed native X11 sets and it seems to work fine. Wonder what `magic' native X11 sets have that cannot be replicated with native... -- Mayuresh
Re: 10.0 BETA modular X11: amdgpu_dri.so not found
On Sat, Dec 31, 2022 at 11:27:09PM -0600, Clay Daniels wrote: > *Take a look at /usr/pkgsrc/emulators/compat90 and read (cat) the DESCR file > .* Have installed compat90 already. It does not provide amdgpu_dri.so Neither do the installation sets. -- Mayuresh
10.0 BETA modular X11: amdgpu_dri.so not found
This PR has the dmesg, Xorg log and xorg.conf http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=57144 Chronology: 1. I recompiled the kernel with amdgpu, amdgpufb enabled and now I get hdmi output. 2. My MesaLib was compiled without llvm option that was leading to some libraries not found by X and amdgpu driver wasn't getting loaded during startx. Now I have MesaLib with llvm option. Now I get the error: MESA-LOADER: failed to open amdgpu: Cannot open /usr/pkg/lib/dri/amdgpu_dri.so I am using modular X11. I searched through PLISTs, not sure if there is a package that provides the above file. Is there any reason why this is missing (if so) in pkgsrc? Does base X11 provide and is it advisable to use the base X11 for this hardware? -- Mayuresh
Re: Testing/Debugging amdgpu kernel driver in 10.0_BETA
On Fri, Dec 30, 2022 at 02:02:01PM -0800, Jeff Frasca wrote: > Hi all, I have a lenovo thinkpad E485 which has a Ryzen 3 2200U APU > in it (which is a Vega/RAVEN RIDGE GPU). I installed the NetBSD 10.0 > BETA on it this week, and that's actually working better than > Slackware 15.0 Great to read that. I have amdgpu based hardware, not same as yours, but Ubuntu uses amdgpu X11 driver for the same without any problems. With Generic NetBSD 10.0 BETA kernel eDP monitor was working, though there was no HDMI output during boot. After enabling amdgpu and amdgpufb and recompiling the kernel there is HDMI output but very faint eDP output - almost invisible. X11 is very slow. Xorg.0.log points to absence of radeonsi_dri. It unloads amdgpu driver. I'm not sure where to get radeonsi_dri from. I am using modular X11. I see the firmware loaded from these messages, though not sure whether that's the right one / anything else also is needed. [ 4.738987] [drm] Found UVD firmware Version: 1.43 Family ID: 15 [ 4.789087] [drm] Found VCE firmware Version: 34.0 Binary ID: 3 My dmesg/xorg.conf/Xorg.0.log details are captured on this PR. dmesg posted at the bottom of the thread is after recompiling the kernel with amdgpu and amdgpufb options, initial one is before that. http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=57144 Based on your experience with amdgpu, is there anything you can suggest - that will be really a great help. E.g. did you have to enable amdgpu in the kernel, did you have to drop in any additional firmware, any specific xorg.conf settings etc. -- Mayuresh
Re: i915 observations
On Mon, Dec 19, 2022 at 09:32:14PM +0530, Mayuresh wrote: I have captured all the information on Linux and NetBSD, dmseg and Xorg.log on this PR. http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=57143 -- Mayuresh
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, 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 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 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
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
Re: No HDMI output on Lenovo V145, trying since 8.0
On Tue, Dec 27, 2022 at 06:53:16AM +1030, Brett Lymn wrote: > On Mon, Dec 26, 2022 at 09:06:57PM +0530, Mayuresh wrote: > > > > 3. Laptop's touchpad isn't working: > > > > I believe you mentioned this before and did not respond when I asked for > details. You need > to provide more information. Does the trackpad get probed? Do a grep of > dmesg for pms and > provide the output. If the trackpad is probed then what does does not work > mean? Yes, I did visit that thread before posting this. But that was for a different issue and a different laptop (touchpad behaving erratically). This one is different - here touchpad is simply dead (may be not identified, no pms in dmesg). -- Mayuresh
Re: No HDMI output on Lenovo V145, trying since 8.0
On Mon, Dec 26, 2022 at 08:00:58PM +0530, Mayuresh wrote: > This thread [1] has the details discussed 3 years back. > > On 10.0 BETA X11 identifies it as amdgpu and it is working for laptop > monitor. But neither during boot nor after startx hdmi gets any output. > > Is this something that has a chance of working in 10.0 BETA? # 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. -- Mayuresh
Re: No HDMI output on Lenovo V145, trying since 8.0
On Mon, Dec 26, 2022 at 09:06:57PM +0530, Mayuresh wrote: > 2. There is no audio from the builtin speaker. mixerctl shows the audio > device as HDMI00 > > $ mixerctl -a > outputs.dacsel=HDMI00 Following fixed the audio issue: audiocfg default 1
Re: No HDMI output on Lenovo V145, trying since 8.0
On Mon, Dec 26, 2022 at 08:00:58PM +0530, Mayuresh wrote: > This thread [1] has the details discussed 3 years back. > > On 10.0 BETA X11 identifies it as amdgpu and it is working for laptop > monitor. But neither during boot nor after startx hdmi gets any output. > > Is this something that has a chance of working in 10.0 BETA? Other related information / issues: 1. xrandr built using modular X11 $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 default connected 1024x768+0+0 0mm x 0mm 1024x768 0.00* 2. There is no audio from the builtin speaker. mixerctl shows the audio device as HDMI00 $ mixerctl -a outputs.dacsel=HDMI00 3. Laptop's touchpad isn't working: -- Mayuresh
Re: 10.0 BETA: How to boot using UEFI or grub
On Sun, Dec 25, 2022 at 04:17:26PM -0800, Jim Bernard wrote:
> set -e
>
> # grub-mkconfig helper script.
>
> echo "menuentry 'NetBSD boot loader' --class netbsd --class os {
> chainloader (hd0,gpt1)/EFI/netbsd/bootx64.efi
> }"
Thanks. That helped. What I did was to append the following to
/etc/grub.d/40_custom and run update-grub.
# Added below this
menuentry "NetBSD" {
set root=(hd0,gpt1)
chainloader /efi/netbsd/bootx64.efi
}
--
Mayuresh
No HDMI output on Lenovo V145, trying since 8.0
This thread [1] has the details discussed 3 years back. On 10.0 BETA X11 identifies it as amdgpu and it is working for laptop monitor. But neither during boot nor after startx hdmi gets any output. Is this something that has a chance of working in 10.0 BETA? -- Mayuresh [1] https://www.mail-archive.com/netbsd-users@netbsd.org/msg11062.html
Re: 10.0 BETA: How to boot using UEFI or grub
On Sun, Dec 25, 2022 at 03:59:26PM +0100, Martin Husemann wrote: > NetBSD currently does not do it, and uses the default boot path instead > (EFI/boot/bootx64.efi). I copied bootx64.efi to EFI/BOOT, but still only existing Ubuntu option appears in UEFI boot options. Was anything else also needed? Also, can someone with grub knowhow please advise on the grub error in my last post? Even after insmod of part_gpt, part_bsd, knetbsd says "unknown filesystem" Lastly if I use bootinstall of NetBSD since neither UEFI nor grub is working for me, is there any way to give a menu option to boot Linux on the other partition? -- Mayuresh
10.0 BETA: How to boot using UEFI or grub
I have installed NetBSD 10.0 BETA amd64 on a Lenovo laptop with Ubuntu on an another partition. [ This is a different laptop than the one I am discussing on some other threads ]. The laptop supports UEFI and legacy boot. But the installation medium showed up only as legacy boot. So I think the installer worked in legacy boot mode. Now I wish to boot this using either UEFI or grub. 1. For UEFI: For UEFI boot, using utility menu, I copied /usr/mdec/*.efi /boot/EFI/netbsd (Ubuntu has its files on /boot/EFI/ubuntu.) However the firmware shows only Ubuntu among UEFI options. Do I need to copy some more files so that netbsd option shows up? 2. Using grub I tried on grub prompt set root=(hd0,gpt3) insmod part_gpt insmod part_bsd knetbsd /netbsd I get error: unknown filesystem Please advise. -- Mayuresh
Re: 10_BETA: Nice QOL improvements to the installer
On Thu, Dec 22, 2022 at 06:18:41AM +1300, Lloyd Parkes wrote: > I used the second (non-BIOS) image because I guessed it might be a hybrid > installer. I think that my old NUCs only support BIOS booting from USB > sticks, but I could easily be wrong. Ok. So, it appears the -bios image has become redundant now. Or hasn't it? If yes, they may want to stop building it to preempt such confusion. -- Mayuresh
Re: 10_BETA: Nice QOL improvements to the installer
On Wed, Dec 21, 2022 at 09:25:30AM +1300, Lloyd Parkes wrote: > I was installing on amd64 and the installer let me choose either MBR or GPT, I notice a separate image marked "bios" NetBSD-10.0_BETA-amd64-bios-install.img.gz NetBSD-10.0_BETA-amd64-install.img.gz So wonder, which installer you tried that gave you these two options. I got an impression that these two are just different installers - 1 UEFI and 1 BIOS. BTW I was about to download the -bios installer though I was so far trying -current using UEFI installer. Someone suggested me that some X11 issues may get resolved if I use the bios installer. I am not sure how though. -- Mayuresh
Re: i915 observations
On Mon, Dec 19, 2022 at 09:26:33PM +0530, Mayuresh wrote: > On Mon, Dec 19, 2022 at 09:20:53PM +0530, Mayuresh wrote: > > I do not know if there is a way to make a running X dump its conf. I > > searched for it, though could not find. > > On Linux, when X11 works (i.e. when xorg.conf is absent) I am attaching > its log - just in case if there is any way to figure out which driver and > options it might be using. Apologies.. Attached a wrong log to the previous mail. The correct one (when it works on Linux) is attached now. -- Mayuresh [ 1597.889] X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 [ 1597.889] Current Operating System: Linux asus2 6.0.10_1 #1 SMP PREEMPT_DYNAMIC Mon Nov 28 03:42:58 UTC 2022 x86_64 [ 1597.889] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.0.10_1 root=UUID=4147e9fb-400b-449c-a1b0-a64b6b720900 ro loglevel=4 [ 1597.889] [ 1597.889] Current version of pixman: 0.40.0 [ 1597.889]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 1597.889] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 1597.890] (==) Log file: "/var/log/Xorg.1.log", Time: Mon Dec 19 21:28:53 2022 [ 1597.890] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 1597.890] (==) No Layout section. Using the first Screen section. [ 1597.890] (==) No screen section available. Using defaults. [ 1597.890] (**) |-->Screen "Default Screen Section" (0) [ 1597.890] (**) | |-->Monitor "" [ 1597.890] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 1597.891] (==) Automatically adding devices [ 1597.891] (==) Automatically enabling devices [ 1597.891] (==) Automatically adding GPU devices [ 1597.891] (==) Automatically binding GPU devices [ 1597.891] (==) Max clients allowed: 256, resource mask: 0x1f [ 1597.891] (WW) The directory "/usr/share/fonts/X11/OTF" does not exist. [ 1597.891]Entry deleted from font path. [ 1597.891] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/TTF, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi [ 1597.891] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 1597.891] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 1597.891] (II) Module ABI versions: [ 1597.891]X.Org ANSI C Emulation: 0.4 [ 1597.891]X.Org Video Driver: 25.2 [ 1597.891]X.Org XInput driver : 24.4 [ 1597.891]X.Org Server Extension : 10.0 [ 1597.891] (II) xfree86: Adding drm device (/dev/dri/card0) [ 1597.891] (II) Platform probe for /sys/devices/pci:00/:00:02.0/drm/card0 [ 1597.910] (--) PCI:*(0@0:2:0) 8086:3184:1043:1232 rev 6, Mem @ 0xa000/16777216, 0x9000/268435456, I/O @ 0xf000/64, BIOS @ 0x/131072 [ 1597.910] (II) Open ACPI successful (/var/run/acpid.socket) [ 1597.910] (II) LoadModule: "glx" [ 1597.910] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 1597.912] (II) Module glx: vendor="X.Org Foundation" [ 1597.912]compiled for 1.21.1.4, module version = 1.0.0 [ 1597.912]ABI class: X.Org Server Extension, version 10.0 [ 1597.912] (==) Matched intel as autoconfigured driver 0 [ 1597.912] (==) Matched modesetting as autoconfigured driver 1 [ 1597.912] (==) Matched fbdev as autoconfigured driver 2 [ 1597.912] (==) Matched vesa as autoconfigured driver 3 [ 1597.912] (==) Assigned the driver to the xf86ConfigLayout [ 1597.912] (II) LoadModule: "intel" [ 1597.912] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 1597.913] (II) Module intel: vendor="X.Org Foundation" [ 1597.913]compiled for 1.21.1.3, module version = 2.99.917 [ 1597.913]Module class: X.Org Video Driver [ 1597.913]ABI class: X.Org Video Driver, version 25.2 [ 1597.913] (II) LoadModule: "modesetting" [ 1597.913] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 1597.913] (II) Module modesetting: vendor="X.Org Foundation" [ 1597.913]compiled for 1.21.1.4, module version = 1.21.1 [ 1597.913]Module class: X.Org Video Driver [ 1597.913]ABI class: X.Org Video Driver, version 25.2 [ 1597.913] (II) LoadModule: "fbdev" [ 1597.913] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 1597.914] (II) Module fbdev: vendor="X.Org Foundation" [ 1597.914]compiled for 1.21.1.3, module version = 0.5.0 [ 1597.914]Module class: X.Org Video Driver [ 1597.914]ABI class: X.Org Video Driver, versi
Re: i915 observations
On Mon, Dec 19, 2022 at 09:20:53PM +0530, Mayuresh wrote: > I do not know if there is a way to make a running X dump its conf. I > searched for it, though could not find. On Linux, when X11 works (i.e. when xorg.conf is absent) I am attaching its log - just in case if there is any way to figure out which driver and options it might be using. -- Mayuresh [ 142.152] X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 [ 142.158] Current Operating System: Linux asus2 6.0.10_1 #1 SMP PREEMPT_DYNAMIC Mon Nov 28 03:42:58 UTC 2022 x86_64 [ 142.158] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.0.10_1 root=UUID=4147e9fb-400b-449c-a1b0-a64b6b720900 ro loglevel=4 [ 142.163] [ 142.165] Current version of pixman: 0.40.0 [ 142.170]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 142.170] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 142.180] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 20 02:34:34 2022 [ 142.180] (II) Module ABI versions: [ 142.180]X.Org ANSI C Emulation: 0.4 [ 142.180]X.Org Video Driver: 25.2 [ 142.180]X.Org XInput driver : 24.4 [ 142.180]X.Org Server Extension : 10.0 [ 142.181] (II) xfree86: Adding drm device (/dev/dri/card0) [ 142.181] (II) Platform probe for /sys/devices/pci:00/:00:02.0/drm/card0 [ 142.198] (--) PCI:*(0@0:2:0) 8086:3184:1043:1232 rev 6, Mem @ 0xa000/16777216, 0x9000/268435456, I/O @ 0xf000/64, BIOS @ 0x/131072 [ 142.200] List of video drivers: [ 142.201]amdgpu [ 142.201]ati [ 142.202]dummy [ 142.203]intel [ 142.204]nouveau [ 142.205]radeon [ 142.206]vmware [ 142.208]modesetting [ 142.210]fbdev [ 142.211]vesa [ 142.211] (II) LoadModule: "amdgpu" [ 142.231] (II) Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so [ 142.314] (II) Module amdgpu: vendor="X.Org Foundation" [ 142.314]compiled for 1.21.1.3, module version = 22.0.0 [ 142.314]Module class: X.Org Video Driver [ 142.314]ABI class: X.Org Video Driver, version 25.2 [ 142.314] (II) LoadModule: "ati" [ 142.315] (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so [ 142.331] (II) Module ati: vendor="X.Org Foundation" [ 142.331]compiled for 1.21.1.3, module version = 19.1.0 [ 142.331]Module class: X.Org Video Driver [ 142.331]ABI class: X.Org Video Driver, version 25.2 [ 142.331] (II) LoadModule: "dummy" [ 142.332] (II) Loading /usr/lib64/xorg/modules/drivers/dummy_drv.so [ 142.345] (II) Module dummy: vendor="X.Org Foundation" [ 142.345]compiled for 1.21.1.3, module version = 0.3.8 [ 142.345]Module class: X.Org Video Driver [ 142.345]ABI class: X.Org Video Driver, version 25.2 [ 142.345] (II) LoadModule: "intel" [ 142.345] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 142.393] (II) Module intel: vendor="X.Org Foundation" [ 142.393]compiled for 1.21.1.3, module version = 2.99.917 [ 142.393]Module class: X.Org Video Driver [ 142.393]ABI class: X.Org Video Driver, version 25.2 [ 142.393] (II) LoadModule: "nouveau" [ 142.393] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so [ 142.395] (II) Module nouveau: vendor="X.Org Foundation" [ 142.395]compiled for 1.21.1.3, module version = 1.0.17 [ 142.395]Module class: X.Org Video Driver [ 142.395]ABI class: X.Org Video Driver, version 25.2 [ 142.395] (II) LoadModule: "radeon" [ 142.395] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so [ 142.414] (II) Module radeon: vendor="X.Org Foundation" [ 142.414]compiled for 1.21.1.3, module version = 19.1.0 [ 142.414]Module class: X.Org Video Driver [ 142.414]ABI class: X.Org Video Driver, version 25.2 [ 142.414] (II) LoadModule: "vmware" [ 142.414] (II) Loading /usr/lib64/xorg/modules/drivers/vmware_drv.so [ 143.631] (II) Module vmware: vendor="X.Org Foundation" [ 143.631]compiled for 1.21.1.4, module version = 13.3.0 [ 143.631]Module class: X.Org Video Driver [ 143.631]ABI class: X.Org Video Driver, version 25.2 [ 143.631] (II) LoadModule: "modesetting" [ 143.631] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 143.649] (II) Module modesetting: vendor="X.Org Foundation" [ 143.649]compiled for 1.21.1.4, module version = 1.21.1 [ 143.649]Module class: X.Org Video Driver [ 143.649]ABI class: X.Org Video Driver, version 25.2 [ 143.649] (II) LoadModule: "fbdev" [ 143.649] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 143.650] (I
Re: i915 observations
On Sun, Dec 18, 2022 at 11:35:26PM +, RVP wrote: > In any case, do your tests after forcing `UXA' on Linux too. Following things are weird: On Linux: If I do NOT have xorg.conf startx works. But if I generate one using X -configure then it doesn't (no matter I set UXA or not). I do not know if there is a way to make a running X dump its conf. I searched for it, though could not find. Attaching log, with xorg.conf present on Linux. This is grep -w EE of the log with up to EE) trimmed to keep it short AIGLX error: dlopen of /usr/lib64/dri/i965_dri.so failed (/usr/lib64/dri/i965_dri.so: cannot open shared object file: No such file or directory) AIGLX error: unable to load driver i965 Backtrace: 0: /usr/libexec/Xorg (xorg_backtrace+0x7d) [0x55bec268d9cd] 1: /usr/libexec/Xorg (0x55bec2549000+0x14f9b5) [0x55bec26989b5] 2: /usr/lib/libpthread.so.0 (0x7f976534f000+0x13900) [0x7f9765362900] 3: /usr/libexec/Xorg (xf86OptionValue+0x7) [0x55bec26a4cf7] 4: /usr/lib64/xorg/modules/extensions/libvnc.so (0x7f9764862000+0x362c0) [0x7f97648982c0] 5: /usr/libexec/Xorg (InitExtensions+0x89) [0x55bec2590329] 6: /usr/libexec/Xorg (0x55bec2549000+0x3aa3e) [0x55bec2583a3e] 7: /usr/lib/libc.so.6 (__libc_start_main+0xea) [0x7f9764e61e0a] 8: /usr/libexec/Xorg (_start+0x2a) [0x55bec2584e0a] Segmentation fault at address 0x10011 Caught signal 11 (Segmentation fault). Server aborting Please also check the log file at "/var/log/Xorg.1.log" for additional information. Server terminated with error (1). Closing log file. BTW /usr/lib64/dri/i965_dri.so is actually present. I'd rather not chase Linux specific issues. I'd use Linux to the extent of differentially diagnosing the problems with X11 on NetBSD, but looks like it's not helping much in that and adding its own mysteries that may digress us. -- Mayuresh [ 428.190] X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 [ 428.191] Current Operating System: Linux asus2 6.0.10_1 #1 SMP PREEMPT_DYNAMIC Mon Nov 28 03:42:58 UTC 2022 x86_64 [ 428.191] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.0.10_1 root=UUID=4147e9fb-400b-449c-a1b0-a64b6b720900 ro loglevel=4 [ 428.193] [ 428.193] Current version of pixman: 0.40.0 [ 428.195]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 428.195] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 428.198] (==) Log file: "/var/log/Xorg.1.log", Time: Mon Dec 19 21:09:23 2022 [ 428.199] (==) Using config file: "/etc/X11/xorg.conf" [ 428.199] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 428.200] (==) ServerLayout "X.org Configured" [ 428.200] (**) |-->Screen "Screen0" (0) [ 428.200] (**) | |-->Monitor "Monitor0" [ 428.200] (**) | |-->Device "Card0" [ 428.200] (**) |-->Input Device "Mouse0" [ 428.200] (**) |-->Input Device "Keyboard0" [ 428.200] (==) Automatically adding devices [ 428.200] (==) Automatically enabling devices [ 428.200] (==) Automatically adding GPU devices [ 428.200] (==) Automatically binding GPU devices [ 428.200] (==) Max clients allowed: 256, resource mask: 0x1f [ 428.200] (WW) The directory "/usr/share/fonts/X11/OTF" does not exist. [ 428.200]Entry deleted from font path. [ 428.200] (WW) The directory "/usr/share/fonts/X11/OTF" does not exist. [ 428.200]Entry deleted from font path. [ 428.200] (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/TTF, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/TTF, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi [ 428.200] (**) ModulePath set to "/usr/lib64/xorg/modules" [ 428.200] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [ 428.200] (WW) Disabling Mouse0 [ 428.200] (WW) Disabling Keyboard0 [ 428.200] (II) Module ABI versions: [ 428.200]X.Org ANSI C Emulation: 0.4 [ 428.200]X.Org Video Driver: 25.2 [ 428.200]X.Org XInput driver : 24.4 [ 428.200]X.Org Server Extension : 10.0 [ 428.201] (II) xfree86: Adding drm device (/dev/dri/card0) [ 428.201] (II) Platform probe for /sys/devices/pci:00/:00:02.0/drm/card0 [ 428.219] (--) PCI:*(0@0:2:0) 8086:3184:1043:1232 rev 6, Mem @ 0xa000/16777216, 0x9000/268435456, I/O @ 0xf000/64, BIOS @ 0x/131072 [
Re: i915 observations
On Mon, Dec 19, 2022 at 12:04:42AM +, RVP wrote: > b) xrandr (rotation--tested, multiple displays--can't test) works. With above settings, after connecting hdmi monitor and running xrandr rotate the system instantly rebooted! This is 9.99.108 -- Mayuresh
Re: i915 observations
On Sat, Dec 17, 2022 at 11:36:17PM +, RVP wrote: > On Sat, 17 Dec 2022, Mayuresh wrote: > > > On Linux it works with intel driver and without any AccelMethod explicitly > > set. > > [...] > > isn't it i915 driver that must be making a difference? > > > > Yes, which is why you should use the same config. file as on NetBSD: so > that we can have an apples-to-apples comparison--same driver; same config. I tried using Linux's xorg.conf on NetBSD as well as the other way round. - Both work on the system they are taken from, but both don't work on the other system. - Both use the driver intel, but still when they use the other's file they both give the same error Driver not found : intel. Attaching both. -- Mayuresh Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/pkg/lib/xorg/modules" FontPath "/usr/pkg/share/fonts/X11/misc" FontPath "/usr/pkg/share/fonts/X11/TTF" FontPath "/usr/pkg/share/fonts/X11/OTF" FontPath "/usr/pkg/share/fonts/X11/Type1" FontPath "/usr/pkg/share/fonts/X11/100dpi" FontPath "/usr/pkg/share/fonts/X11/75dpi" FontPath "/usr/pkg/share/fonts/X11/cyrillic" FontPath "/usr/pkg/lib/X11/fonts/misc" FontPath "/usr/pkg/lib/X11/fonts/TTF" FontPath "/usr/pkg/lib/X11/fonts/OTF" FontPath "/usr/pkg/lib/X11/fonts/Type1" FontPath "/usr/pkg/lib/X11/fonts/100dpi" FontPath "/usr/pkg/lib/X11/fonts/75dpi" FontPath "/usr/pkg/lib/X11/fonts/cyrillic" EndSection Section "Module" Load "dri" Load "dri2" Load "glx" EndSection Section "DRI" Group "wheel" Mode 0660 EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "wsmouse" Option "Device" "/dev/wsmouse" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz", ### : "%" ### [arg]: arg optional #Option "Accel" # [] #Option "AccelMethod" # #Option "Backlight" # #Option "CustomEDID"# #Option "DRI" # #Option "Present" # [] #Option "ColorKey" # #Option "VideoKey" # #Option "Tiling"# [] #Option "LinearFramebuffer" # [] #Option "HWRotation"# [] #Option "VSync" # [] #Option "PageFlip" # [] #Option "SwapbuffersWait" # [] #Option "TripleBuffer" # [] #Option "XvPreferOverlay" # [] #Option "HotPlug" # [] #Option "ReprobeOutputs"# [] #Option "XvMC" # [] #Option "ZaphodHeads" # #Option "VirtualHeads" # #Option "TearFree" # [] #Option "PerCrtcPixmaps"# [] #Option "FallbackDebug" # [] #Option "DebugFlushBatches" # [] #Option "DebugFlushCaches" # [] #Option "DebugWait" # [] #Option "BufferCache" # [] Identifier "Card0" #Driver "wsfb"
Re: i915 observations
On Wed, Dec 14, 2022 at 11:14:31PM +, RVP wrote: > xrandr rotation on my laptop display worked fine on Linux. (On NetBSD, > I have to use wsfb--the other drivers are either unusable or hang the > system.) On Linux it works with intel driver and without any AccelMethod explicitly set. On NetBSD it works with intel driver and with UXA but only in default mode of eDP1. Mode change on eDP1 or any mode on HDMI work sluggishly. Assuming x11 world may not differ much on both OSes (I am using modular x11), isn't it i915 driver that must be making a difference? -- Mayuresh
Re: i915 observations
On Tue, Dec 13, 2022 at 11:06:24PM +, RVP wrote: > Is this on the eDP or HDMI? Collect a blind dmesg (or better, ssh into > the laptop) after `boot -vx'. Another one where the display stays on > for comparison. Unluckily (rather luckily) with boot -vx the display always comes up! (I don't mind settling for it as a workaround!) Without -vx it's random. But when the display doesn't come up, the network doesn't come up either. I tried typing commands to save dmesg output. But may be it wasn't taking those. May be it had crashed where it was accepting only reboot command. -- Mayuresh
Re: i915 observations
On Tue, Dec 13, 2022 at 11:06:24PM +, RVP wrote: > > (Will get back on above points.) > Hmm. Don't know about this. Might be that UXA + HDMI doesn't work so well. > > a) Try out different output drivers with mpv(1): use `--vo=help' > > b) For DVD playback, see the XvMC-related options mentioned in intel(4). The problem is not only with videos. Even catting a file or opening vi updates the screen slowly, almost line by line left to right. The only time when above problem doesn't trigger is, if I do 'xrandr --same-as' to have hdmi a mirror of eDP. I like to use a vertical hdmi monitor, so above option isn't suitable for my usage. In fact, with hdmi completely out of the picture, if I do 'xrandr --rotate' on eDP screen, just to see what happens, the slow refresh occurs on eDP also. Does it mean the acceleration works only in certain mode(s)? So far intel-UXA is the only combination that has somewhat worked. *-none starts but is not usable. intel-SNA doesn't work, modestting/wsfb with defaults don't even start. -- Mayuresh
Re: i915 observations
On Tue, Dec 13, 2022 at 08:28:08AM +0530, Mayuresh wrote: > I'll test some video playing etc. and report back. Thanks to compat90 I was able to test immediately. Yeah, they seem to work alright. Even HDMI output seems fine and xrandr also seems to work. Now the only problem left is this: During boot when the display switches mode, sometimes it manages to remain on, some other times it goes blank. This is random. There are 4 gop values, all of which work sometimes and don't work some other times. I do not know exactly what happens when the display goes blank. I enter root username and password and type reboot and that seems to be rebooting it. Once in a few reboots the display holds on and then I can reach all the way to X11. -- Mayuresh
Re: i915 observations
On Tue, Dec 13, 2022 at 08:50:38AM +0530, Mayuresh wrote: > Even HDMI output seems fine Update: HDMI output has a slow refresh problem though eDP works fine. Can't play videos on hdmi, even command line usage is jittery. Tried experimenting with modes, including low resolutions, but the problem persists. -- Mayuresh
Re: i915 observations
On Mon, Dec 12, 2022 at 10:37:37PM +, RVP wrote: > Welcome to the club... You'll find the rest of the gang here already: > https://mail-index.netbsd.org/current-users/2022/07/21/msg042710.html > Please post to that thread: Merging the thread here. > Uncomment the `Option "AccelMethod" "none"' in the config. fragment I > sent you. Then see if modesetting(4) comes up. For the intel(4) driver, > try `Option "AccelMethod" "UXA"', or even `"none"' as a last resort. The > intelfb(4) manpage lists other options which you can turn off or disable > with the SNA or UXA accel-methods. modesetting - none and intel - none combinations start the display with a very poor refresh rate. They appear garbled and settle down slowly. intel - UXA is kind of working now. Finally some X11 on the device! I'll test some video playing etc. and report back. Thanks for your help! -- Mayuresh
Re: NetBSD 9.2 installer can't detect disk of some Hetzner VPSes
On Mon, Aug 15, 2022 at 12:35:21PM +0100, Robert Swindells wrote: > If "qemu -machine q35" fails to boot NetBSD in the same way then it will > be a lot easier to resolve this. It wasn't failing to boot. It was not detecting HDD and network. For NetBSD 9.3 CD image I tried this and it is able to detect the network device: qemu-system-x86_64 -machine q35 -cdrom $CD -- Mayuresh
Re: NetBSD 9.2 installer can't detect disk of some Hetzner VPSes
On Mon, Aug 15, 2022 at 11:55:21AM +0100, Robert Swindells wrote: > I don't think we can claim that their configuration is "less portable", > q35 has been in qemu since 2017. But i440FX works on more OSes than Q35 - hence more portable! Basically I do not know their motivation to switch over to Q35. It's just a perspective to convince a provider to give a setup that works for us, since there is no other way till NetBSD supports Q35, and we don't know when will that be. At last that's the impression I got from this thread. -- Mayuresh
Re: NetBSD 9.2 installer can't detect disk of some Hetzner VPSes
On Mon, Aug 15, 2022 at 11:54:11AM +0200, os...@fessel.org wrote: > I tried that, will see if they will do that (and when). > But that is not really a viable solution since I tended to delete and > recreate servers there. > Which is no at least not instanteneously possible when support is needed for > every setup. I understand. It's good to see that quite a few of us are NetBSD-Hetzner users. Hetzner maintains this issue to be a "bug in NetBSD", while we might try and convey a position that they are using configurations that are "less portable". I do not know their motivation to prefer one chipset over the other, when ultimately all of them are virtual. If there are sizable number of complaints they may reassess that - particularly your kind of requirements of dynamic provisioning where you can't keep filing tickets and waiting. -- Mayuresh
Re: NetBSD 9.2 installer can't detect disk of some Hetzner VPSes
On Thu, Jul 21, 2022 at 08:17:08AM +0200, Matthias Petermann wrote: > At the moment, I only encounter the described problem when I select the AMD > variant. Mayuresh, can you confirm this? I did observe this. But they said the following (pasted on the thread before) Most of our Systems and all AMD Hosts already use Q35 as default virtual chipset. It seems like you had luck to get a CX (Intel) Host that still uses i440FX. The way I interpret: AMD => Q35 Intel => some i440FX and some Q35. You are 'lucky' if you find host that 'still' uses i440FX => some intel have i440FX, though eventually all will have Q35. In my limited experiments I did not find Intel with Q35 though. On request, they reconfigure it to i440FX, which is what helped me set up AMD. -- Mayuresh
Re: RealTek wifi on -current amd64 on lenovo laptop
On Tue, May 18, 2021 at 09:12:46AM +, nia wrote: > There's no driver for Realtek 802.11ac PCIe hardware. > You could try porting a driver from another OS. Would like to give it a try, but I have never worked on device drivers in any OS. Would be useful to build the skill. Any good pointers to get started? There is a ddwg page/pdf[1]. But its date looks 2003. Is there anything else - more of tutorial than a reference to begin with? There are at least 3 laptop devices with me where I would prefer to use NetBSD, but can't due to one or more of these problems: 1. wifi (can work around using a dongle) 2. touchpad issues (external mouse is an option but not suitable for every usage pattern) 3. hdmi not working (show stopper in one usage) 4. envstat not working (may not sound critical, but I have an audible alert when battery falls to a threshold, which I'd like to work) All of these issues are reported on the mailing list. If I could solve even some of these myself I'll be glad. [1] https://www.netbsd.org/docs/kernel/ddwg.html -- Mayuresh
RealTek wifi on -current amd64 on lenovo laptop
On NetBSD -current, in dmesg, it appears as: [ 1.054279] Realtek Semiconductor product c821 (miscellaneous network) at pci2 dev 0 function 0 not configured On Linux, it works fine, lshw shows it as: *-network description: Wireless interface product: RTL8821CE 802.11ac PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: 28:39:26:65:a2:9f width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtl8821ce Is there any chance to get it to work in -current? -- Mayuresh
Atheros wifi status on NetBSD
Was about to report this on an asus laptop. Then I came across this existing PR filed in 2016: http://gnats.netbsd.org/51644 On my Asus X200MA laptop, the device appears as: [ 1.012971] vendor 168c product 0036 (miscellaneous network, revision 0x01) at pci2 dev 0 function 0 not configured Given the ageing PR, I think it's either too difficult to support or may be there are other issues such as hardware availability to test etc? Just curious. -- Mayuresh
envstat issue with -current amd64 lenovo laptop
On Lenovo v145[1], I was trying out -current (9th May daily snapshot). 9.1 didn't work on this device. I am getting incorrect envstat output when checking battery status. Basically looking to extract % charged state using envstat. envstat output: Current CritMax WarnMax WarnMin CritMin Unit [acpiacad0] connected: TRUE [acpibat0] present: TRUE design voltage: 0.000 V voltage: 8.517 V design cap: 0.000Wh last full cap: 0.000Wh charge: 2.703Wh charge rate: N/A discharge rate: N/A charging: FALSE charge state:NORMAL [amdzentemp0] cpu0 temperature:47.750 degC dmesg | grep acpibat0. [ 1.052113] acpibat0 at acpi0 (BAT1, PNP0C0A-0): ACPI Battery [ 1.052113] acpibat0: ACPI 4.0 functionality present [ 1.281460] acpibat0: autoconfiguration error: failed to evaluate _BIF: AE_ERROR ... Probably some BIOS issue. But on the same laptop, on Linux, I am getting required information from acpi, although there are error messages as follows in dmesg: [On Linux] $ dmesg | grep acpi [0.023673] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [0.023674] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [0.023675] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [0.023677] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [0.228258] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.257849] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] [0.257858] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM [0.257877] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge [0.299855] clocksource: acpi_pm: mask: 0xff max_cycles: 0xff, max_idle_ns: 2085701024 ns [0.911415] acpi_cpufreq: overriding BIOS provided _PSD data [1.045526] acpi device:00: registered as cooling_device2 $ acpi -V Battery 0: Unknown, 99% Battery 0: design capacity 3517 mAh, last full capacity 3171 mAh = 90% Adapter 0: on-line Cooling 0: Processor 0 of 10 Cooling 1: Processor 0 of 10 Please advise any further investigation. -- Mayuresh [1] https://www.lenovo.com/in/en/laptops/lenovo/v-series/Lenovo-V145-15AST/p/88LG80V1181
Re: X11 doesn't start -current amd64 lenovo laptop
On Tue, May 11, 2021 at 08:06:38AM +1000, matthew green wrote: > can you try without an xorg.conf at all? Yes, first tried that. I just thought reporting xorg.conf will help share what X thinks the hardware is. > this hardware is not currently supported by our kernel drm driver and > will need to fallback to wsfb or vesa. it should do automatically > without an xorg.conf to force a driver. Manually writing wsfb in xorg.conf worked. But it wasn't happening automatically. Also, vesa didn't work. But hdmi screen and touchpad are still not working. Any suggestions on those two? -- Mayuresh
Re: X11 doesn't start -current amd64 lenovo laptop
On Mon, May 10, 2021 at 11:57:10PM +0530, Mayuresh wrote: (With attachments.) [ 150.236] X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 [ 150.237] Build Operating System: NetBSD/amd64 9.99.82 - The NetBSD Foundation, Inc. [ 150.237] Current Operating System: NetBSD 9.99.82 NetBSD 9.99.82 (GENERIC) #0: Sun May 9 16:58:57 UTC 2021 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 [ 150.237] Build Date: 23 February 2020 07:11:23AM [ 150.237] [ 150.237] Current version of pixman: 0.38.4 [ 150.237]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 150.237] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 150.237] (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 10 23:37:32 2021 [ 150.237] (++) Using config file: "/root/xorg.conf.new" [ 150.238] (==) ServerLayout "X.org Configured" [ 150.238] (**) |-->Screen "Screen0" (0) [ 150.238] (**) | |-->Monitor "Monitor0" [ 150.238] (**) | |-->Device "Card0" [ 150.238] (**) |-->Screen "Screen1" (1) [ 150.238] (**) | |-->Monitor "Monitor1" [ 150.238] (**) | |-->Device "Card1" [ 150.238] (**) |-->Input Device "Mouse0" [ 150.238] (**) |-->Input Device "Keyboard0" [ 150.238] (==) Not automatically adding devices [ 150.238] (==) Not automatically enabling devices [ 150.238] (==) Not automatically adding GPU devices [ 150.238] (==) Max clients allowed: 256, resource mask: 0x1f [ 150.238] (**) FontPath set to: /usr/X11R7/lib/X11/fonts/misc/, /usr/X11R7/lib/X11/fonts/TTF/, /usr/X11R7/lib/X11/fonts/Type1/, /usr/X11R7/lib/X11/fonts/75dpi/, /usr/X11R7/lib/X11/fonts/100dpi/, /usr/X11R7/lib/X11/fonts/misc/, /usr/X11R7/lib/X11/fonts/TTF/, /usr/X11R7/lib/X11/fonts/Type1/, /usr/X11R7/lib/X11/fonts/75dpi/, /usr/X11R7/lib/X11/fonts/100dpi/ [ 150.238] (**) ModulePath set to "/usr/X11R7/lib/modules" [ 150.238] (II) Loader magic: 0x1f290a60 [ 150.238] (II) Module ABI versions: [ 150.238]X.Org ANSI C Emulation: 0.4 [ 150.238]X.Org Video Driver: 24.1 [ 150.238]X.Org XInput driver : 24.1 [ 150.238]X.Org Server Extension : 10.0 [ 150.242] (--) PCI:*(0@0:1:0) 1002:98e4:17aa:39f5 rev 234, Mem @ 0xe800/134217728, 0xf080/8388608, 0xf040/262144, I/O @ 0x4000/256, BIOS @ 0x/131072 [ 150.242] (II) "glx" will be loaded. This was enabled by default and also specified in the config file. [ 150.242] (II) LoadModule: "dri" [ 150.242] (II) Module "dri" already built-in [ 150.242] (II) LoadModule: "dri2" [ 150.242] (II) Module "dri2" already built-in [ 150.242] (II) LoadModule: "glx" [ 150.242] (II) Loading /usr/X11R7/lib/modules/extensions/libglx.so [ 150.243] (II) Module glx: vendor="X.Org Foundation" [ 150.243]compiled for 1.20.11, module version = 1.0.0 [ 150.243]ABI class: X.Org Server Extension, version 10.0 [ 150.243] (II) LoadModule: "shadow" [ 150.243] (II) Loading /usr/X11R7/lib/modules/extensions/libshadow.so [ 150.243] (II) Module shadow: vendor="X.Org Foundation" [ 150.243]compiled for 1.20.11, module version = 1.1.0 [ 150.243]ABI class: X.Org ANSI C Emulation, version 0.4 [ 150.243] (II) LoadModule: "amdgpu" [ 150.244] (II) Loading /usr/X11R7/lib/modules/drivers/amdgpu_drv.so [ 150.244] (II) Module amdgpu: vendor="X.Org Foundation" [ 150.244]compiled for 1.20.11, module version = 19.1.0 [ 150.244]Module class: X.Org Video Driver [ 150.244]ABI class: X.Org Video Driver, version 24.1 [ 150.244] (II) LoadModule: "mouse" [ 150.244] (II) Loading /usr/X11R7/lib/modules/drivers/mouse_drv.so [ 150.244] (II) Module mouse: vendor="X.Org Foundation" [ 150.244]compiled for 1.20.11, module version = 1.9.2 [ 150.245]Module class: X.Org XInput Driver [ 150.245]ABI class: X.Org XInput driver, version 24.1 [ 150.245] (II) LoadModule: "kbd" [ 150.245] (II) Loading /usr/X11R7/lib/modules/drivers/kbd_drv.so [ 150.245] (II) Module kbd: vendor="X.Org Foundation" [ 150.245]compiled for 1.20.11, module version = 1.9.0 [ 150.245]Module class: X.Org XInput Driver [ 150.245]ABI class: X.Org XInput driver, version 24.1 [ 150.245] (II) AMDGPU: Driver for AMD Radeon: All GPUs supported by the amdgpu kernel driver [ 150.245] (--) Using wscons driver on /dev/ttyE4 in pcvt compatibility mode (version 3.32) [ 150.245] (--) using VT number 5 [ 150.4
X11 doesn't start -current amd64 lenovo laptop
On Lenovo v145[1], I was trying out -current (10th May daily snapshot) (9.1 didn't work on this device), though unable to get startx to work. Attaching Xorg.0.log, xorg.conf.new generated by X -configure Also attaching lshw output on Linux that describes the display hardware. Please let me know if I should try/report anything more. -- Mayuresh [1] https://www.lenovo.com/in/en/laptops/lenovo/v-series/Lenovo-V145-15AST/p/88LG80V1181
Re: blacklist -> blocklist in current
On Tue, Jun 16, 2020 at 07:43:07AM +0200, Marc Balmer wrote: > Well, obviously anything with the word black in it must be considered > racist these days. Hmm... May be. Out of the 4k+ times the word occurred majority occurrences were for the black as in color (say of the terminal). May be we should invent a better word for that - at least till such newly invented word starts being regarded as racist in a few years time! Then, of course, we'll choose yet another word and so on. May be we should keep a watch on physicists who use the term blackhole and also see if they want to `correct' all the text written by the likes of Einstein to Stephen Hawking on the topic. Mayuresh
Re: blacklist -> blocklist in current
On Mon, Jun 15, 2020 at 03:44:22PM -0400, Christos Zoulas wrote: > We should be all doing whatever we can to correct social/race/gender/sex > injustices/prejudices around us, and every little bit helps. I am a great fan of bla^Hocklistd and I'd be happily using it even if you name it say timbuktud. But I think we are stretching above argument a bit too far. By any stretch of imagination I couldn't find any trace of racist link in a very commonly used word in Comp Sc like blacklist. Even tried searching its origin[1] and doesn't look like it has anything to do with any race. Just a quick grep in an arbitrary snapshot of the source tree of NetBSD shows the word 'black' appearing at 4146 places... There are `blackholes', `blackballs', `blacklist' (other than in bla^Hocklistd's code), blackfin (of course some like this are not names chosen by NetBSD but of 3rd party hardware, such as a processor or a company name), `black magic', `blackjack', `blackboard', `blackbook', `blackbox', `blackcrow', `blackberry', `black cathedral', `black helicopter', `black tree' ... And I am done only with 6% of the grep output. Mayuresh [1] https://en.wikipedia.org/wiki/Blacklisting
Re: httpd ssl failures
On Tue, Dec 17, 2019 at 03:22:17PM +1100, Geoff Wing wrote: > :> > Is this a problem with my setup? > :> Think it may be an httpd issue. Used the cert/key with postfix and tested > :> with openssl s_client and didn't see any issues. Notice this thread late. I have same issue with httpd occasionally. It works normally most of the time but once in a while exits with some errors. Next time around it exits I'll paste the errors on the thread. I am using letsencrypt and no problems with it with postfix or even httpd for most of the time. My setup is different though. I had compiled it from pkg with version 20181215 on NetBSD 8.1 amd64, as the base one of 8.1 did not have the features I needed. Mayuresh
Re: VirtualBox-6.0.6 fails build under 8.99.39
On Fri, May 10, 2019 at 08:25:45PM +0100, Chavdar Ivanov wrote: > You are using very old VirtualBox version from pkgsrc/wip. This is > something I haven't bothered ever to try. I download the source from > VirtualBox and build it myself. All you need is kbuild and yasm and > LocalConfig.kmk with the following contents: Sorry to trouble with more basic questions. I am not familiar with kmk or yasm. Can you please share some sample commands after creating LocalConfig.kmk? > We are talking about the guest additions drivers at the moment, not > the virtualisation product itself. Sorry, I missed the point here. You mean the core virtualization product builds and is usable or not. Mayuresh
Re: VirtualBox-6.0.6 fails build under 8.99.39
On Sat, May 11, 2019 at 12:05:03AM +0530, Mayuresh wrote: > pxe_call.c:(.text.pxe_api_call+0x12): undefined reference to > `__stack_chk_guard' PKGSRC_USE_SSP=no makes it go away, but that gives rise to following errors that weren't present when it was not set. In file included from /usr/pkgsrc/wip/virtualbox/work/VirtualBox-5.0.16/src/VBox/HostDrivers/Support/SUPR3HardenedMain.cpp:67:0: /usr/pkgsrc/wip/virtualbox/work/VirtualBox-5.0.16/include/VBox/types.h:78:37: error: expected unqualified-id before numeric constant typedef struct VM *PVM; ^ /usr/pkgsrc/wip/virtualbox/work/VirtualBox-5.0.16/include/VBox/types.h:78:37: error: expected initializer before numeric constant kmk: *** [/usr/pkgsrc/wip/virtualbox/work/VirtualBox-5.0.16/out/netbsd.amd64/release/obj/SUPR3HardenedStatic/SUPR3HardenedMain.o] Error 1 Mayuresh
Re: VirtualBox-6.0.6 fails build under 8.99.39
On Fri, May 10, 2019 at 09:30:06AM +0100, Chavdar Ivanov wrote: > Sure, although the last time I did this was months ago. Now, it needed python version to be set to 27. I have committed this change. Now there are linking errors for various sources but for these 3 symbols only. pxe_call.c:(.text.pxe_api_call+0x12): undefined reference to `__stack_chk_guard' pxe_call.c:(.text.pxe_api_call+0x96): undefined reference to `__stack_chk_guard' pxe_call.c:(.text.pxe_api_call+0x9d): undefined reference to `__stack_chk_fail' Any idea about these? Mayuresh
Re: urndis0 works on amd64-8.0 but not on evbarm-current
On Fri, May 10, 2019 at 06:05:34AM +, sc dying wrote: > Attached files look bogus, I'll resend. Due to some other compulsions (a lot of pkgs that I need not building under current, discussed on various threads) I reverted my environment to 8.0. Is there any possibility to try things on 8.0? Mayuresh
Re: VirtualBox-6.0.6 fails build under 8.99.39
On Thu, May 09, 2019 at 09:43:10PM +0100, Chavdar Ivanov wrote: > While The said version compiles cleanly under 8.99.37 (I did it a few > days ago), today under 8.99.39 it fails for me as follows: I am a late tuner to this development. Does it compile on 8.0? Mayuresh
Re: BFD .. invalid string offset .. for section `.strtab'
On Sat, May 04, 2019 at 03:56:34PM +0100, Robert Swindells wrote: > Been like that for a while: > > <http://mail-index.netbsd.org/tech-toolchain/2019/02/21/msg003411.html> > > >Please advise. > > Raise a PR. I filed a PR under port-arm. For now I have reverted to 8.0. Do not have the error environment with me now. Mayuresh
BFD .. invalid string offset .. for section `.strtab'
# uname -a NetBSD pi 8.99.37 NetBSD 8.99.37 (RPI2) #1: Thu Apr 25 16:01:51 UTC 2019 root@pi:/usr/src/sys/arch/evbarm/compile/RPI2 evbarm BFD: /usr/pkg/lib/libpango-1.0.so.0: invalid string offset 12338 >= 11106 for section `.strtab' BFD: /usr/pkg/lib/libfribidi.so.0: invalid string offset 1447 >= 1158 for section `.strtab' BFD: /usr/pkg/lib/libfribidi.so.0: invalid string offset 1652 >= 1158 for section `.strtab' Core was generated by `netsurf-gtk'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x698315f0 in memcpy () from /usr/lib/libc.so.12 [Current thread is 1 (process 1)] (gdb) where #0 0x698315f0 in memcpy () from /usr/lib/libc.so.12 #1 0x000d9888 in __memcpy_ichk (len=, src=, dst=0x7fe8ef34) at /usr/include/ssp/string.h:82 #2 curl_start_cert_validate (certs=certs@entry=0x7fe906e0, f=, f=) at content/fetchers/curl.c:967 #3 0x000d9f20 in fetch_curl_done (result=CURLE_PEER_FAILED_VERIFICATION, curl_handle=) at content/fetchers/curl.c:1132 #4 fetch_curl_poll (scheme_ignored=) at content/fetchers/curl.c:1223 #5 0x000d6474 in fetch_fdset (read_fd_set=read_fd_set@entry=0x7fe907a8, write_fd_set=write_fd_set@entry=0x7fe907c8, except_fd_set=except_fd_set@entry=0x7fe907e8, maxfd_out=maxfd_out@entry=0x7fe907a4) at content/fetch.c:404 #6 0x00183bc0 in nsgtk_main () at frontends/gtk/gui.c:404 #7 0x002325e0 in main (argc=, argv=) at frontends/gtk/gui.c:1206 Above trace occurred on netsurf core dump. There is a long chain of the "BFD:" errors on various libraries, only 2-3 samples of that are attached above. I think during build of the packages I had seen those errors as well, but not sure. Please advise. Mayuresh
Re: urndis0 works on amd64-8.0 but not on evbarm-current
On Thu, May 02, 2019 at 09:23:38PM +0530, Mayuresh wrote: > # uname -a > NetBSD pi 8.99.37 NetBSD 8.99.37 (RPI2) #1: Thu Apr 25 16:01:51 UTC 2019 > root@pi:/usr/src/sys/arch/evbarm/compile/RPI2 evbarm > > # dmesg | grep urndis > [47.388677] urndis0 at uhub2 port 3 configuration 1 interface 0 > [47.388677] urndis0: SAMSUNG (0x4e8) SAMSUNG_Android (0x6863), rev > 2.00/4.00, addr 8 > [47.388677] urndis0: IOERROR > [47.388677] urndis0: unable to get init response > [47.388677] urndis0: IOERROR > [47.388677] urndis0: unable to get query response > [47.388677] autoconfiguration error: urndis0: unable to get hardware > address > > > The same mobile phone works fine as urndis0 on NetBSD 8.0 amd64. > > I do not know whether this is a problem with -current or with evbarm. (I > do not have amd64 -current or evbarm 8.0, unfortunately.) > > What more can I try out? Marking current-users and port-arm. Mayuresh
Re: gcc 6 on Fedora
On Mon, Feb 22, 2016 at 02:45:35PM +0100, Thomas Klausner wrote: > On Mon, Feb 22, 2016 at 07:03:32PM +0530, Mayuresh wrote: > > On Mon, Feb 22, 2016 at 02:31:32PM +0100, Thomas Klausner wrote: > > > Some numbers of what pkgsrc breakage we can expect with gcc 6: > > > > > > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/DH7M2ADHM6XCRFTRRSKZD6MWFUJKHBZK/ > > > > Sorry, if I missed the posts. Is there such plan (to adopt gcc 6 in > > pkgsrc)? If it is not the default compiler does it indeed affect pkgsrc > > users? > > I'm posting this mainly because there is ongoing work to upgrade gcc > in the NetBSD base system to a newer version. I think it'll be 5.3 > though. Ok. Just a guess: NetBSD base may not face the same turmoil mentioned in cited posts. Root cause of the turmoil is bloated code, not the compiler itself (at least so is the impression I got from the post). Mayuresh.
Re: gcc 6 on Fedora
On Mon, Feb 22, 2016 at 02:31:32PM +0100, Thomas Klausner wrote: > Some numbers of what pkgsrc breakage we can expect with gcc 6: > > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/DH7M2ADHM6XCRFTRRSKZD6MWFUJKHBZK/ Sorry, if I missed the posts. Is there such plan (to adopt gcc 6 in pkgsrc)? If it is not the default compiler does it indeed affect pkgsrc users? Mayuresh.
Re: After i386 7.0 -> amd64 7.0 changeover can't mount ext2 partition
On Thu, Nov 05, 2015 at 11:34:10AM +0530, Mayuresh wrote: > On Thu, Nov 05, 2015 at 01:47:08PM +0800, Paul Goyette wrote: > > Rerun /dev/MAKEDEV > > I realize MAKEDEV is for i386, so it is keeping the numbers same. > > I had skipped the etc set. > > I should probably do etcupdate and then rerun MAKEDEV? (Didn't know > MAKEDEV would be related with this until I saw the following line in it:) > > # NetBSD: etc.i386/MAKEDEV.conf,v 1.25 2012/09/23 01:15:17 chs Exp Sorry, etcupdate wasn't going to do that. Copied MAKEDEV* from the installation medium to /dev. Now devices are created. Thanks. Mayuresh.
Re: After i386 7.0 -> amd64 7.0 changeover can't mount ext2 partition
On Thu, Nov 05, 2015 at 01:47:08PM +0800, Paul Goyette wrote: > Rerun /dev/MAKEDEV I realize MAKEDEV is for i386, so it is keeping the numbers same. I had skipped the etc set. I should probably do etcupdate and then rerun MAKEDEV? (Didn't know MAKEDEV would be related with this until I saw the following line in it:) # NetBSD: etc.i386/MAKEDEV.conf,v 1.25 2012/09/23 01:15:17 chs Exp Mayuresh
Re: After i386 7.0 -> amd64 7.0 changeover can't mount ext2 partition
On Thu, Nov 05, 2015 at 01:27:45PM +0800, Paul Goyette wrote: > Did you check to make sure you have a /dev/sd0j and /dev/rsd0j in > your /dev directory? > > And did you check to make sure that they have the correct major/minor > numbers? (4/9 for /dev/sd0j and 13/9 for /dev/rsd0j) Thanks. I think the second number is garbage. What is the solution? # ls -l /dev/*sd0j crw-r- 1 root operator 13, 524289 Jul 5 2013 /dev/rsd0j brw-r- 1 root operator 4, 524289 Jul 5 2013 /dev/sd0j How do I correct these? Mayuresh.
After i386 7.0 -> amd64 7.0 changeover can't mount ext2 partition
#uname -a NetBSD laptop 7.0 NetBSD 7.0 (MYKERNEL) #0: Wed Nov 4 20:53:55 IST 2015 root@laptop:/usr/src/sys/arch/amd64/compile/MYKERNEL amd64 Nothing relevant changed in MYKERNEL: # diff GENERIC MYKERNEL 891c891 < ulpt* at uhub? port ? configuration ? interface ? --- > #ulpt*at uhub? port ? configuration ? interface ? # disklabel /dev/sd0 # /dev/sd0d: type: unknown disk: FreeAgent Go label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 625142447 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] a: 102395904 103428096 4.2BSD 2048 16384 0 # (Cyl. 102607*- 204190*) c: 102395904 103428096 unused 0 0# (Cyl. 102607*- 204190*) d: 625142447 0 unused 0 0# (Cyl. 0 - 620180*) e: 1024000 2048 Linux Ext2 0 0# (Cyl. 2*- 1017*) g: 102398310 1028160 Linux Ext2 0 0# (Cyl. 1020 - 102605*) i: 8193087 205824843 swap # (Cyl. 204191*- 212319*) j: 49352 214017993 Linux Ext2 0 0# (Cyl. 212319*- 620175*) Portion of /etc/fstab /dev/sd0e /mnt/boot ext2fs noauto,rw 0 0 /dev/sd0g /mnt/pkgsrc ext2fs noauto,rw 0 0 /dev/sd0j /mnt/linuxhome ext2fs noauto,rw 0 0 When on i386 I was able to mount all 3 of the above mounts. However, after switching to amd64 I can mount only /dev/sd0e and /dev/sd0g. Trying to mount /dev/sd0j gives # mount -vvv /mnt/linuxhome/ exec: mount_ext2fs -o noauto /dev/sd0j /mnt/linuxhome mount_ext2fs: /dev/sd0j on /mnt/linuxhome: Device not configured I have done fsck check on all 3 partitions on Linux system and they are all healthy. Not able to mount this partition breaks my system badly. Request help in resolution of this. Mayuresh.
Re: NetBSD 7.0 i386 panic during boot
On Sat, Oct 17, 2015 at 01:33:32PM +0300, Andreas Gustafsson wrote: > The discussion that ensued branched out in lots of different > directions, but as far as I can see, none of them actually > offered a diagnosis of the original problem reported. > > To me, this looks very much like the same problem as PR 50060, which > was recently fixed in -current by riastradh@. A pullup to -7 is still > pending. Thanks for the confirmation. I'll try out current. Since the machine was critical I reverted to 6.1.5 for now. Mayuresh
Re: NetBSD 7.0 i386 panic during boot
On Wed, Oct 14, 2015 at 11:07:08AM -0400, Christos Zoulas wrote: > Add some printfs to vmem_alloc? This is happening way too early. I tried enabling following option to see whether trace shows source level info. But it didn't. makeoptions DEBUG="-g" Is there any way to get source level debug info in ddb trace? Mayuresh
Re: NetBSD 7.0 i386 panic during boot
On Wed, Oct 14, 2015 at 11:07:08AM -0400, Christos Zoulas wrote: > Add some printfs to vmem_alloc? This is happening way too early. Is there a way to read source level info (line number etc) in the trace? May be, if that doesn't give a clue, I'll get into printfs? Mayuresh.
Re: NetBSD 7.0 i386 panic during boot
On Tue, Oct 13, 2015 at 08:20:23AM -0400, Christos Zoulas wrote: > So you have a usb keyboard and it does not work for you? > Comment out the following lines: > > #pckbc* at acpi?# PC keyboard controller > #pckbc0 at isa? # pc keyboard controller > #pckbd* at pckbc? # PC keyboard > #pms*at pckbc? # PS/2 mouse for wsmouse > #wskbd* at pckbd? console ? > #wsmouse*at pms? mux 0 Tried these, but it did not enable the keyboard on panic. However in man pages I saw this and set DDB_COMMANDONENTER="trace" Surprisingly this option is not present in the GENERIC template configuration. May be not all options appear there... That apart. Now I get the trace, mentioning the function names: vmem_alloc uvm_km_kmem_alloc kmem_intr_alloc kmem_intr_zalloc mpbios_scan mainbus_attach config_attach_loc config_rootfound cpu_configure main (This is with acpi disabled.) Mayuresh
Re: NetBSD 7.0 i386 panic during boot
On Wed, Oct 14, 2015 at 07:51:53AM -0400, Christos Zoulas wrote: > | $sysctl ddb.onpanic > | ddb.onpanic = 2 > | > | So looks like my procedure was alright. Is there anything else needed to > | make kernel print trace on entering ddb, when keyboard can't be used? > > Did the instructions I posted to make the kernel accept keyboard input work? Sorry, if I missed your mail. I thought ddb.onpanic=2 would print the trace automatically on panic, thus not requiring keyboard. No? If there were more instructions to enable keyboard could you please repost? I don't seem to find them. Mayuresh
Re: NetBSD 7.0 i386 panic during boot
On Tue, Oct 13, 2015 at 05:24:31PM +0530, Mayuresh wrote: > On Sun, Oct 11, 2015 at 01:13:42PM -0400, Christos Zoulas wrote: > > | > This looks like a NULL pointer dereference. Do you have a backtrace? > > | > > | Unfortunately the keyboard stops working when db prompt appears. So cannot > > | gather complete trace. > > > > Compile a kernel with > > options DDB_ONPANIC 2 > > (man 4 options) > > Did just that, make depend and make. Copied the kernel to bootable USB and > tried to boot from it. Get the panic error but not stack trace. On a healthy system I tried triggering ddb with above kernel (with DDB_ONPANIC set), with Ctrl-Alt-Esc. It did not print trace. To cross check that the option is effective I did this: $sysctl ddb.onpanic ddb.onpanic = 2 Also commented out the following line in /etc/sysctl.conf as below to ensure that it is not overriding the compiled option. #ddb.onpanic?=1 So looks like my procedure was alright. Is there anything else needed to make kernel print trace on entering ddb, when keyboard can't be used? Mayuresh.
Re: NetBSD 7.0 i386 panic during boot
On Sun, Oct 11, 2015 at 01:13:42PM -0400, Christos Zoulas wrote: > | > This looks like a NULL pointer dereference. Do you have a backtrace? > | > | Unfortunately the keyboard stops working when db prompt appears. So cannot > | gather complete trace. > > Compile a kernel with > options DDB_ONPANIC 2 > (man 4 options) Did just that, make depend and make. Copied the kernel to bootable USB and tried to boot from it. Get the panic error but not stack trace. Following is the section of debugging options. Do I need to enable anything else? # Diagnostic/debugging support options #optionsDIAGNOSTIC # inexpensive kernel consistency checks # XXX to be commented out on release # branch #optionsDEBUG # expensive debugging checks/support #optionsLOCKDEBUG # expensive locking checks/support #optionsKMEMSTATS # kernel memory statistics (vmstat -m) options DDB # in-kernel debugger #optionsDDB_ONPANIC=1 # see also sysctl(7): `ddb.onpanic' options DDB_ONPANIC=2 # see also sysctl(7): `ddb.onpanic' options DDB_HISTORY_SIZE=512# enable history editing in DDB #optionsDDB_VERBOSE_HELP #optionsKGDB# remote debugger #options KGDB_DEVNAME="\"com\"",KGDB_DEVADDR=0x3f8,KGDB_DEVRATE=9600 #makeoptionsDEBUG="-g" # compile full symbol table #optionsSYSCALL_STATS # per syscall counts #optionsSYSCALL_TIMES # per syscall times #options SYSCALL_TIMES_HASCOUNTER# use 'broken' rdtsc (soekris) Mayuresh
Ways to report trace when boot panics [Was NetBSD 7.0 i386 panic during boot]
On Mon, Oct 12, 2015 at 11:21:41AM +0700, Robert Elz wrote: > Without that, all that you can get is what you can see on the screen. I think this topic is worth discussing. I have seen several mail threads where people paste threads, obviously gathered systematically. But I do not know how they do that. I see photograph of screen to be an quick and easy way (from skill and effort point of view). But doesn't look like too many people use it. > ps: it would be interesting to know if there was any rational way to > develop a NetBSD to NetBSD USB protocol that could maybe be used to > replace serial consoles ... requiring just a cable to link 2 NetBSD > systems to each other - I know nothing about USB, but if there's enough > access to the raw bits, it should be possible to make the running > NetBSD identify itself as some kind of new USB device, and have the > booting kernel look for that, and if found, use it as a console device. > Might that be possible? Even nicer if such device could be a smartphone, which can make it convenient to collect data, just from ease point of view. Mayuresh
Re: NetBSD 7.0 i386 panic during boot
On Sun, Oct 11, 2015 at 02:10:48PM -0400, Christos Zoulas wrote: > No, it does not matter. You are not making it that far yet. If you can't > get to userland to execute init, how do you expect the sysctl will make > a difference. Alright. So, I'll compile a kernel that will help me gather trace. At the same time shall I try disabling any modules? (agp is one but that is not in picture when I disable acpi.) What will help me gather the trace in a file? I think there is a notion of dump device, but that's all I know about it. Is there any good document? Mayuresh
Re: NetBSD 7.0 i386 panic during boot
On Sun, Oct 11, 2015 at 07:15:39PM +0200, Leonardo Taccari wrote: > Hello Mayuresh, > > Mayuresh writes: > > [...] > > Unfortunately the keyboard stops working when db prompt appears. So cannot > > gather complete trace. > I think that: > > # sysctl -w ddb.commandonenter="trace" > > will do the trick. Ok. But I am not able to boot. Probably I should boot with installation media and edit /etc/sysctl.conf? BTW, just for clarity - with 7.0 installation media I face the same problem. I have 5.0 installation media that works. Mayuresh
Re: NetBSD 7.0 i386 panic during boot
On Sun, Oct 11, 2015 at 12:31:51PM -0400, Christos Zoulas wrote: > | RTC BIOS diagnostic error 0x80 > > That means that something is wrong with the battery, it is not fatal. This is a desktop. You mean CMOS battery or something? 6.1 was working fine so far on this. I am trying to type out more text. (Sorry, not yet learned how to gather the trace.) RTC BIOS diagnostic error 0x80 mainbus0 (root) mainbus0: Intel MP Specification (Version 1.4) ( uvm_fault(...,0,1)->0xe fatal page fault in supervisor mode trap type 6 code 0 ... curlwp... kernel: supervisor trap page fault, code=0 Stopped in pid 0.1 (system) at netbsd:vmem_alloc+0x44 movl ... > | uvm_fault(...,0,1) -> 0xe > > This looks like a NULL pointer dereference. Do you have a backtrace? Unfortunately the keyboard stops working when db prompt appears. So cannot gather complete trace. Mayuresh
Re: NetBSD 7.0 i386 panic during boot
On Sun, Oct 11, 2015 at 03:41:57PM +, Christos Zoulas wrote: > >> agp0: can't find MMIO registers > > Disable agp? Could try that, but before that does this observation give any other clue: If I start with acpi disabled, I do not get agp error. Get the following instead: RTC BIOS diagnostic error 0x80 uvm_fault(...,0,1) -> 0xe Mayuresh.
Re: NetBSD 7.0 i386 panic during boot
+current list On Sun, Oct 11, 2015 at 04:00:49PM +0530, Mayuresh wrote: > On an i386 desktop I was running 6.x and just upgraded 7.0 sets (excluding > etc). After this I am not able to boot. > > I am not aware how to gather the error trace, though quoting lines that I > think are relevant: > > ACPI Exception: AE_NOT_FOUND > > pagp0 at pchb0: i965-family chipset > > pcim_mem_find: expected mem type 0004, found > > agp0: can't find MMIO registers > > uvm_fault(,2) -> 0xe > > Stopped in pid 0.1 (system) at netbsd:_atomic_swap_32+0x8 > > > Please help. I am not able to boot my system. > Let me know if any more details are needed. > > > If I disable ACPI I get: > > uvm_fault(..,0,1) -> 0xe > Stopped in pid 0.1 (system) at netbsd:vmem_alloc+0x44: movl.. > > Mayuresh.
Re: NetBSD 7.0_RC1 on Raspberry Pi : reboots on poweroff
On Sat, Jul 11, 2015 at 12:20:38PM +, Christos Zoulas wrote: > 2. the cpu_reboot code in src/sys/arch/arm/arm32/arm32_reboot.c in 1.6 >which is the revision in netbsd-7 reboots on halt. This has been >fixed in later revisions to loop and wait. Thanks. Would it be considered important enough to be patched in 7 as well? It's a show stopper for use of NetBSD on pi. Mayuresh.
Re: NetBSD 7.0_RC1 on Raspberry Pi : reboots on poweroff
On Sat, Jul 11, 2015 at 04:06:22AM +, Michael van Elst wrote: > The RPI cannot "power itself off" but it should really wait for > a keypress. This used to work with a serial console, but maybe > not with a USB keyboard. If I remove the USB keyboard and issue poweroff over ssh, it does not even wait at reboot message. It just reboots without waiting. (And if I have USB keyboard, it waits at reboot message for a few seconds and then reboots.) I am sure the issue is not about RPI's lack of ability to power itself down. Mayuresh.
NetBSD 7.0_RC1 on pi 2 fsck : why are odds of recovery low?
# uname -a NetBSD pinet 7.0_RC1 NetBSD 7.0_RC1 (RPI2.201506190427Z) evbarm I landed up in an unclean shutdown situation with above configuration on Raspberry Pi 2 on a few occasions. (This was due to poweroff actually not doing poweroff, on which I have a different thread.) On next reboot the system went for file system checks though could not recover the file system. (Sorry, I have lost the error messages and only when it crashes next time around I'll be able to get them, but it was something like fsck "giving up".) On each such occasion I ended up having to reinstall the image on the SD card and begin setting up system all over again. Now, I have faced unclean shutdowns on a laptop running NetBSD 6.1 i386 on a few occasions, though always fsck had recovered the file system. I am curious, why the odds of recovery so low on Pi 2. Does it have something to do with it being a microSD card? Does it have something to do with 7.0_RC1? Or is it plain simple bad luck? Mayuresh.
Re: NetBSD 7.0_RC1 on Raspberry Pi : reboots on poweroff
On Fri, Jul 10, 2015 at 05:54:43PM -0400, Louis Guillaume wrote: > # poweroff -p > > - or if you're not in single-user - > > # shutdown -p now > > Should do the trick. "shutdown -p now" also went to reboot prompt. Mayuresh.
NetBSD 7.0_RC1 on Raspberry Pi 2 not SMP?
#uname -a NetBSD pinet 7.0_RC1 NetBSD 7.0_RC1 (RPI2.201506190427Z) evbarm sysctl shows me the following: hw.ncpu = 1 cat /proc/cpuinfo shows no output. Is the default kernel in this release not SMP or is it that SMP is not yet supported for pi? Mayuresh
Re: 7.0_RC1 Raspberry Pi usb wifi
On Fri, Jul 10, 2015 at 12:59:57PM +0100, Robert Swindells wrote: > > NetBSD pinet 7.0_RC1 NetBSD 7.0_RC1 (RPI2.201506190427Z) evbarm > > If it doesn't get recognized by the run(4) driver then it isn't > supported, is this driver in your kernel ? I am not sure, haven't downloaded the sources. This is default kernel of snapshot mentioned above. Not sure whether the following is correct way to check: sysctl -a | grep drivers | grep run This did not show any output. I'll try and compile that in. Mayuresh.
Re: 7.0_RC1 Raspberry Pi usb wifi
On Fri, Jul 10, 2015 at 12:40:47PM +0100, Nick Hudson wrote: > >The adapter works fine on Raspbian. > > > >It is detected as ugen0 on NetBSD 7.0_RC1 > > > > # dmesg | grep ugen > > ugen0 at uhub1 port 5 > > ugen0: Ralink 802.11 n WLAN, rev 2.00/1.01, addr 4 > > > > # uname -a > > NetBSD pinet 7.0_RC1 NetBSD 7.0_RC1 (RPI2.201506190427Z) evbarm > > What does "usbdevs -v" say about it? port 5 addr 5: high speed, power 450 mA, config 1, 802.11 n WLAN(0x5370), Ralink(0x148f), rev 1.01, serial 1.0 Mayuresh.
NetBSD 7.0_RC1 on Raspberry Pi : reboots on poweroff
I find that when I run "poweroff" on pi on NetBSD 7.0_RC1, it goes to "Press any key to reboot" prompt instead of powering itself off. And after some time it reboots. I have to pull the power chord exactly in those moments when it is still at above prompt, else I run the risk of corrupting the sd card. (Already happened once, with the device going to file system checks.) Now, when I use the device in headless manner, I have difficulty deciding exact time of pulling the chord to safely poweroff the device. Is there any way out of this? Mayuresh.
7.0_RC1 Raspberry Pi usb wifi
I have a USB wifi adapter that came bundled with a Raspberry Pi 2 and accessories package. The adapter works fine on Raspbian. It is detected as ugen0 on NetBSD 7.0_RC1 # dmesg | grep ugen ugen0 at uhub1 port 5 ugen0: Ralink 802.11 n WLAN, rev 2.00/1.01, addr 4 # uname -a NetBSD pinet 7.0_RC1 NetBSD 7.0_RC1 (RPI2.201506190427Z) evbarm Browsing through past threads on this, I get an impression that this indicates it is just not supported. Or, is that something to be enabled in the kernel? Also, if not supported currently, is it likely to be supported in 7.0? Mayuresh.
Re: USB keyboard recognized during boot menu, not later
On Tue, Jun 23, 2015 at 08:12:16PM +0530, Mayuresh wrote: > If I type the same key on usb keyboard repeatedly at fast pace (or hold > down the key) only a few of them appear on screen. But if I type different > letters back to back at a fast pace, no letters are missed. Sorry, strike out the "hold down the key" observation. It behaves normally if I hold down the key, but if I type the same key fast, it accepts only a subset of keystrokes. Mayuresh
Re: USB keyboard recognized during boot menu, not later
On Mon, Jun 22, 2015 at 03:52:20PM +, Christos Zoulas wrote: > >Were those useful? Shall I share something more? > > Yes, shows that we are not parsing some string properly. What does > > $ vmstat -u usbhist > > say? One more observation that might definitely help: If I type the same key on usb keyboard repeatedly at fast pace (or hold down the key) only a few of them appear on screen. But if I type different letters back to back at a fast pace, no letters are missed. Mayuresh.
Re: USB keyboard recognized during boot menu, not later
On Mon, Jun 22, 2015 at 07:30:42PM +, Christos Zoulas wrote: > >>> Yes, shows that we are not parsing some string properly. What does > >>> > >>> $ vmstat -u usbhist > >>> > >>> say? > >> > >>It prints a blank line. Should I have check that in debug mode? > > > > Also do you have options UVMHIST defined? I don't find it enabled, though I got a lot of output for above command in debug mode (pasting in other mail), so I hope setting UVMHIST is not required. Mayuresh.
Re: USB keyboard recognized during boot menu, not later
On Mon, Jun 22, 2015 at 03:52:20PM +, Christos Zoulas wrote: > Yes, shows that we are not parsing some string properly. What does > > $ vmstat -u usbhist > > say? It prints a blank line. Should I have check that in debug mode? Mayuresh.
Re: USB keyboard recognized during boot menu, not later
On Sun, Jun 21, 2015 at 10:46:30PM +0530, Mayuresh wrote: > #dmesg | grep -i -e usb -e xhci -e ehci > xhci0 at pci0 dev 20 function 0: vendor 8086 product 0f35 (rev. 0x0e) > xhci0: interrupting at ioapic0 pin 20 > xhci0: xHCI version 1.0 > usb0 at xhci0: USB revision 2.0 > uhub0 at usb0: NetBSD xHCI Root Hub, class 9/0, rev 2.00/1.00, addr 0 > uhub1 at uhub0 port 3: vendor 1a40 USB 2.0 Hub, class 9/0, rev 2.00/1.11, > addr 1 > xhci0 at pci0 dev 20 function 0: vendor 8086 product 0f35 (rev. 0x0e) > xhci0: interrupting at ioapic0 pin 20 > xhci0: xHCI version 1.0 > usb0 at xhci0: USB revision 2.0 > uhub0 at usb0: NetBSD xHCI Root Hub, class 9/0, rev 2.00/1.00, addr 0 > uhidev0: GASIA USB KB > V11M-oM-?M-?M-aM-!M-(M-hM^DM^FM-oM-?M-?M-oM-?M-?M-`M-(M^@, rev 1.10/2.10, > addr 1, iclass 3/1 > uhidev1: GASIA USB KB > V11M-oM-?M-?M-aM-!M-(M-hM^DM^FM-oM-?M-?M-oM-?M-?M-gM-%M^V, rev 1.10/2.10, > addr 1, iclass 3/0 > uhub1 at uhub0 port 3: vendor 1a40 USB 2.0 Hub, class 9/0, rev 2.00/1.11, > addr 2 > > Got these with USB 3.0 enabled in the bios, setting xhcidebug=1, > connecting a usb kbd and then continue. Were those useful? Shall I share something more? Mayuresh.
Re: USB keyboard recognized during boot menu, not later
On Sun, Jun 21, 2015 at 02:33:54PM +, Christos Zoulas wrote: > So define both, and then set xhci_debug = 1 #dmesg | grep -i -e usb -e xhci -e ehci xhci0 at pci0 dev 20 function 0: vendor 8086 product 0f35 (rev. 0x0e) xhci0: interrupting at ioapic0 pin 20 xhci0: xHCI version 1.0 usb0 at xhci0: USB revision 2.0 uhub0 at usb0: NetBSD xHCI Root Hub, class 9/0, rev 2.00/1.00, addr 0 uhub1 at uhub0 port 3: vendor 1a40 USB 2.0 Hub, class 9/0, rev 2.00/1.11, addr 1 xhci0 at pci0 dev 20 function 0: vendor 8086 product 0f35 (rev. 0x0e) xhci0: interrupting at ioapic0 pin 20 xhci0: xHCI version 1.0 usb0 at xhci0: USB revision 2.0 uhub0 at usb0: NetBSD xHCI Root Hub, class 9/0, rev 2.00/1.00, addr 0 uhidev0: GASIA USB KB V11M-oM-?M-?M-aM-!M-(M-hM^DM^FM-oM-?M-?M-oM-?M-?M-`M-(M^@, rev 1.10/2.10, addr 1, iclass 3/1 uhidev1: GASIA USB KB V11M-oM-?M-?M-aM-!M-(M-hM^DM^FM-oM-?M-?M-oM-?M-?M-gM-%M^V, rev 1.10/2.10, addr 1, iclass 3/0 uhub1 at uhub0 port 3: vendor 1a40 USB 2.0 Hub, class 9/0, rev 2.00/1.11, addr 2 Got these with USB 3.0 enabled in the bios, setting xhcidebug=1, connecting a usb kbd and then continue. Mayuresh.
