)
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
see.
--
Mayuresh
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
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
? function ?
--
Mayuresh
long. Not sure what it is supposed to be reporting
and after how long.
--
Mayuresh
hall I report in the PR?
--
Mayuresh
] 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
dy 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
is' 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
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
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
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
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
ve to enable amdgpu in
the kernel, did you have to drop in any additional firmware, any specific
xorg.conf settings etc.
--
Mayuresh
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
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
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,
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
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
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
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
> [
.)
--
Mayuresh
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
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
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
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
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
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
on to boot Linux on
the other partition?
--
Mayuresh
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
as become redundant now. Or hasn't it?
If yes, they may want to stop building it to preempt such confusion.
--
Mayuresh
get resolved if I use the bios installer. I am not sure how though.
--
Mayuresh
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 x
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
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
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
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?
> >
&
citly
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
(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
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
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 l
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 prob
s 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
s and it is able to detect the network
device:
qemu-system-x86_64 -machine q35 -cdrom $CD
--
Mayuresh
n 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
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
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 a
)
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
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
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
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
on
those two?
--
Mayuresh
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
if I should try/report anything more.
--
Mayuresh
[1]
https://www.lenovo.com/in/en/laptops/lenovo/v-series/Lenovo-V145-15AST/p/88LG80V1181
t' all the text written by the likes of
Einstein to Stephen Hawking on the topic.
Mayuresh
rdware, 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
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
itself.
Sorry, I missed the point here. You mean the core virtualization product
builds and is usable or not.
Mayuresh
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/
l.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
8.0?
Mayuresh
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
to 8.0. Do not have the error environment with me
now.
Mayuresh
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
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 configura
saw the following line in it:)
# NetBSD: etc.i386/MAKEDEV.conf,v 1.25 2012/09/23 01:15:17 chs Exp
Mayuresh
j /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.
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
d0j)
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.
h 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
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.
source level debug info in ddb trace?
Mayuresh
tr_alloc
kmem_intr_zalloc
mpbios_scan
mainbus_attach
config_attach_loc
config_rootfound
cpu_configure
main
(This is with acpi disabled.)
Mayuresh
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 p
id 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
able
#optionsSYSCALL_STATS # per syscall counts
#optionsSYSCALL_TIMES # per syscall times
#optionsSYSCALL_TIMES_HASCOUNTER# use 'broken' rdtsc
(soekris)
Mayuresh
+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
> thi
ead:
RTC BIOS diagnostic error 0x80
uvm_fault(...,0,1) -> 0xe
Mayuresh.
de=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
her 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
enough to be patched in 7 as well?
It's a show stopper for use of NetBSD on pi.
Mayuresh.
. 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.
#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
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.
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.
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.
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.
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.
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.
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
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.
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.
On Sun, Jun 21, 2015 at 10:01:15PM +0530, Mayuresh wrote:
On Sun, Jun 21, 2015 at 02:33:54PM +, Christos Zoulas wrote:
fgrep _DEBUG *.c | grep xh
xhci.c:#ifdef USB_DEBUG
xhci.c:#ifndef XHCI_DEBUG
xhci.c:#else /* !XHCI_DEBUG */
xhci.c:#endif /* !XHCI_DEBUG */
xhci.c:#endif
, 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.
, eventually I want to deliver
my system for production use. So curious whether these changes will be
making it to released 7.0.
Mayuresh.
-PSK authentication, if that
matters. There are 4 other devices on same wifi network, 2 of which run a
similar NetBSD setup without any problems.
Mayuresh
97 matches
Mail list logo
