Re: IntelliJ IDEA for java development on NetBSD
I am using PyCharm Pro (2021.3.3) with a modified pycharm.sh file. I use Pycharm for Python development (shock) and Rust. I am running into the same slowness issue. I see the sluggishness with 9.3, 10_Beta and Current (NetBSD 10.99.2). Right now my only solution is to quit PyCharm, reboot and restart. I just started running htop to see if I can identify what is causing the issue. Actually, the slowness has forced me to use vim a little more. :) Yup... I still love vim. On 3/26/23 12:47 PM, David Brownlee wrote: On Sun, 26 Mar 2023 at 14:36, Ron Georgia wrote: I cannot get the early access edition to work. In fact to get the Intellij from pkgin to work I have to change the idea.sh file to use jdk11. Any hints on getting the EAP version to work? Hi Ron, What version of NetBSD are you running? I'm using NetBSD-10 with self compiled binaries. It looks like the 2022Q4 pkgin netbsd-9 binaries have openjdk17-1.17.0.4.8nb1, which is missing a libxrender fix needed for the EAP version. 2023Q1 should have openjdk17-1.17.0.6.10nb2 and _hopeful;y_ should be showing up soon. (I tend to forget that binary packages lag behind on non security updates). I also found that on my laptop under netbsd-9 IDEA became slower and slower over time (which I think was more related to how drm was driving the Intel display chipset in the T480) I tried to run up a quick netbsd-9 openjdk17 package compatible with 2022Q4, but hit a snag (waiting for a reply on tech-pkg@ :) David
Re: IntelliJ IDEA for java development on NetBSD
I cannot get the early access edition to work. In fact to get the Intellij from pkgin to work I have to change the idea.sh file to use jdk11. Any hints on getting the EAP version to work? On 3/25/23 11:06, David Brownlee wrote: Just a quick note that if anyone else is using IntelliJ IDEA to develop Java or other related languages on NetBSD, it might a good idea to download the EAP version from - https://www.jetbrains.com/idea/nextversion/ have a play with it, and then complete the feedback form - https://surveys.jetbrains.com/s3/feedback-survey-for-intellij-idea-eap-2023-1 making sure to indicate that you are using it on NetBSD. Also let them know what you think of their new UI (Strangely for a rearrangement of something I spend so much time looking at on a daily basis, I actually liked the changes) There are never going to be a huge number of NetBSD users, but it's always good to make sure they are aware that there are *some* :) Note - you may need at least openjdk17-1.17.0.6.10nb2 from pkgsrc to run it David -- There seems to be a scratch in the prism of my understanding
Re: i915 observations
I had the same issues with current and with 10_beta. The single line with wsfb as driver and the tearing with intel and modesetting. But now, for me, it works. This is what I did. I did a git clone of https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git and copied all the files from linux-firmware/i915 to /libdata/firmware/i915drmkms/i915/. I stuck my xorg.conf in /etc/X11/xorg.conf.d/. I edited the xorg.conf trying the following Option "Accel" "True" Option "AccelMethod" "SNA" -- OR -- Option "AccelMethod" "UXA" -- OR -- Option "AccelMethod" "none" With Identifier "Card0" Driver "intel" or "modesetting BusID "PCI:0:2:0" All configurations were a bust. Then I copied all linux-firmware/intel to /libdata/firmware/intel/ My Device section of my xorg.conf looks like this: Section "Device" Option "Accel" "True" Option "AccelMethod" "UXA" Identifier "Card0" Driver "intel" BusID "PCI:0:2:0" EndSection Everything works! Well, the response is a little sluggish and firefox takes forever to load, but the video is solid. I do have a lot of "heartbeat" messages in dmesg. I also see this with dmesg: [ 1633.783213] heartbeat On hold?: 0 [ 1633.783213] heartbeat MMIO base: 0x2000 [ 1633.783213] heartbeat CCID: 0x01b5610d [ 1633.783213] heartbeat RING_START: 0x7fffb000 [ 1633.783213] heartbeat RING_HEAD: 0x0798 [ 1633.783213] heartbeat RING_TAIL: 0x0bb0 [ 1633.783213] heartbeat RING_CTL: 0x3001 [ 1633.783213] heartbeat RING_MODE: 0x4000 [ 1633.783213] heartbeat RING_IMR: fffe [ 1633.783213] heartbeat ACTHD: 0x_01b0731c [ 1633.783213] heartbeat BBADDR: 0x_01b0731d [ 1633.783213] heartbeat DMA_FADDR: 0x_01b07500 [ 1633.783213] heartbeat IPEIR: 0x [ 1633.783213] heartbeat IPEHR: 0x7a03 [ 1633.783213] heartbeat PP_DIR_BASE: 0x0221 [ 1633.783213] heartbeat PP_DIR_BASE_READ: 0x [ 1633.783213] heartbeat PP_DIR_DCLV: 0x [ 1633.783213] heartbeat E 2:350a5*- @ 5950ms: firefox[13741] [ 1633.783213] heartbeat E 2:350a6- @ 5940ms: X[1020] [ 1633.783213] heartbeat E 2:350a7 @ 5920ms: firefox[13741] [ 1633.783213] heartbeat E 2:350a8 @ 5920ms: X[1020] [ 1633.783213] heartbeat E 2:350a9 @ 5920ms: X[1020] [ 1633.783213] heartbeat E 2:350aa @ 3000ms: [i915][ 1633.783213] heartbeat * [ 1633.783213] heartbeat Idle? no [ 1633.783213] heartbeat Signals: [ 1633.783213] heartbeat [2:350a5*] @ 5950ms [ 1633.783213] heartbeat [2:350a6] @ 5940ms [ 1633.783213] i915drmkms0: notice: Resetting chip for stopped heartbeat on rcs0 [ 1633.783213] i915drmkms0: notice: firefox[13741] context reset due to GPU hang I have no idea what heartbeat is a reference to, but for now things are working. % uname -mpr 10.0_BETA amd64 x86_64 On 12/12/22 21:58, Mayuresh wrote: 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!
NetBSD-9.99.x No Video
I apologize if this has already been addressed. I installed NetBSD 9.2 on my Intel computer. Everything works well. (Well, the video lags a little). I downloaded netbsd-GENERIC.gz from http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/latest/. I unzipped the file and copy it to the root directory as a file called current. I reboot and select the new kernel. Everything appears to be working until the acpi checks? The PC locks up with a blank screen. This Intel is efi boot. When I try the same process with my Lenovo X200 mbr, it works. cat /boot.cfg banner=*** banner=* Welcome to NetBSD * banner=*** banner= banner= Please choose an option from the following menu: menu=Boot normally:rndseed /var/db/entropy-file;boot menu=Boot single user:rndseed /var/db/entropy-file;boot -s menu=Boot current:rndseed /var/db/entropy-file;boot current menu=Boot current single user:rndseed /var/db/entropy-file;boot current -s menu=Boot previous current:rndseed /var/db/entropy-file;boot ocurrent menu=Boot previous current single user:rndseed /var/db/entropy-file;boot ocurrent -s menu=Drop to boot prompt:prompt default=1 timeout=5 clear=1 Kernels in root directory -rw-r--r-- 1 root wheel 620B Apr 11 04:37 boot.cfg -rwxr-xr-x 1 root wheel 28M Apr 11 04:47 current* -rwxr-xr-x 1 root wheel 24M May 12 2021 netbsd* -rwxr-xr-x 1 root wheel 24M Apr 11 04:34 ocurrent* dmesg snippets [ 1.00] total memory = 32633 MB [ 1.00] avail memory = 31659 MB [ 1.03] ioapic0 at mainbus0 apid 2: pa 0xfec0, version 0x20, 120 pins [ 1.03] cpu0 at mainbus0 apid 0 [ 1.03] cpu0: CPU base freq 30 Hz [ 1.03] cpu0: CPU max freq 35 Hz [ 1.03] cpu0: TSC freq CPUID 30 Hz [ 1.03] cpu0: Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz, id 0x906e9 [ 1.03] cpu0: package 0, core 0, smt 0 [ 1.03] cpu1 at mainbus0 apid 2 [ 1.03] cpu1: Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz, id 0x906e9 [ 1.03] cpu1: package 0, core 1, smt 0 [ 1.03] cpu2 at mainbus0 apid 4 [ 1.03] cpu2: Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz, id 0x906e9 [ 1.03] cpu2: package 0, core 2, smt 0 [ 1.03] cpu3 at mainbus0 apid 6 [ 1.03] cpu3: Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz, id 0x906e9 [ 1.03] cpu3: package 0, core 3, smt 0 [ 5.636320] kern.module.path=/stand/amd64/9.2/modules [ 5.636320] kern info: [drm] Memory usable by graphics device = 4096M [ 5.646318] kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 5.676318] kern info: [drm] Driver supports precise vblank timestamp query. [ 5.696319] kern info: [drm] failed to find VBIOS tables [ 5.734893] i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0) [ 5.796320] kern info: [drm] failed to retrieve link info, disabling eDP [ 5.846320] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:636)i915_firmware_load_error_print] *ERROR* failed to load firmware i915/kbl_dmc_ver1.bin (0) [ 5.846320] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:651)i915_firmware_load_error_print] *ERROR* The driver is built-in, so to load the firmware you need to [ 5.846320] include it either in the kernel (see CONFIG_EXTRA_FIRMWARE) or [ 5.846320] in your initrd/initramfs image. [ 5.846320] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_guc_loader.c:560)guc_fw_fetch] *ERROR* Failed to fetch GuC firmware from i915/kbl_guc_ver9_14.bin (error -2) [ 5.966318] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem.c:5417)i915_gem_init_hw] *ERROR* Failed to initialize GuC, error -5 (ignored) [ 6.146318] intelfb0 at i915drmkms0 [ 6.166318] intelfb0: framebuffer at 0x830259ed8000, size 1920x1080, depth 32, stride 7680 [ 6.216320] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3624: WARN_ON(!wm_changed)wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0 --- Ron Georgia "There seems to be a scratch in the prism of my understanding."
Re: pkgsrc current dbus build failure
Thank you for pointing that out. I am updating now. I downloaded the NetBSD-9.99.60-amd64-install.img (date stamped May 07, 2020) this morning and installed on my Lenovo X200. I did select the option to download pkgsrc. I changed the path from stable to current and that is what was pulled in. On 5/8/20 11:10 AM, Roland Illig wrote: On 08.05.2020 16:44, Ron Georgia wrote: Installed current NetBSD 9.99.60 (GENERIC) #0 and pkgsrc current on 05/08/2020 at about 0900 EST. I tried to build dbus but got an error when it tried to build perl5. sh: 1: Syntax error: Word "/d"p" unexpected (expecting ")") That was a bug in mk/subst.mk r1.91. It was fixed in r1.92, which is from 2020-05-02. This contradicts that you are using pkgsrc-current from 2020-05-08, which is 6 days later. -- “90% of my problems are due to ignorance, the other 10% is because I just don’t know any better.”
pkgsrc current dbus build failure
Installed current NetBSD 9.99.60 (GENERIC) #0 and pkgsrc current on
05/08/2020 at about 0900 EST. I tried to build dbus but got an error
when it tried to build perl5.
sh: 1: Syntax error: Word "/d"p" unexpected (expecting ")")
*** Error code 2
Stop.
make[1]: stopped in /usr/pkgsrc/lang/perl5
*** Error code 1
Stop.
make: stopped in /usr/pkgsrc/lang/perl5
I "fixed" the problem in the Makefile. See diff:
# diff Makefile Makefile.orig
277c277
< SUBST_SED.dirmode= -e "s/755/${PKGDIRMODE}/g;/umask/d"
---
> SUBST_SED.dirmode= -e "s/755/${PKGDIRMODE}/g;/umask(/d"
After that it failed again with the following message:
Making utilities
Everything is up to date. Type '/usr/bin/make test' to run test suite.
LD_LIBRARY_PATH=/usr/pkgsrc/lang/perl5/work/perl-5.30.2 ./perl -Ilib -I.
installperl --destdir=/usr/pkgsrc/lang/perl5/work/.destdir
Unmatched right curly bracket at ./install_lib.pl line 42, at end of line
syntax error at ./install_lib.pl line 42, near "}"
Compilation failed in require at installperl line 10.
BEGIN failed--compilation aborted at installperl line 11.
*** Error code 255
I removed the stray } and it finished building. See diff
# diff work/perl-5.30.2/install_lib.pl work/perl-5.30.2/install_lib.pl.orig
41a42
> }
--
“90% of my problems are due to ignorance, the other 10% is because I just don’t
know any better.”
Re: No uefi install in VM
I did install 9.0_RC1 on a bare metal machine accepting all the defaults, and it boots fine with UEFI. On 12/12/19 5:00 AM, Chavdar Ivanov wrote: I can confirm - in the case of yesterday's -current - that there is nothing wrong with the efi/gpt installation procedure and the problem is with the two .efi files. On VirtualBox I attached the new 'bad' disk to the working EFI NetBSD instance, renamed the 'boot' folder in the FAT partition to 'boot.bad'. created 'boot' folder and placed there the working .efi files. This resulted in perfectly bootable new NetBSD vm. For comparison: ... ./boot: total 420 -r-xr-xr-x 1 root wheel 217139 Dec 12 09:48 bootia32.efi -r-xr-xr-x 1 root wheel 205820 Dec 12 09:48 bootx64.efi ./boot.bad: total 448 -r-xr-xr-x 1 root wheel 234874 Dec 11 21:34 bootia32.efi -r-xr-xr-x 1 root wheel 220293 Dec 11 21:34 bootx64.efi ... The 'bad' ones are a little bigger, created yesterday under -current build. The good ones were from sometimes in July this year. Chavdar On Thu, 12 Dec 2019 at 08:33, Martin Husemann wrote: On Thu, Dec 12, 2019 at 09:10:57AM +0100, Emmanuel Dreyfus wrote: Martin Husemann wrote: Emmanuel, could you please have a look? I do not reproduce that one. Can you share the exact commands to build the testbed? This one had been created manually and worked with old efiboot. Instructions would be: boot 9.0 RC1 installer uefi image, let sysinst install onto hard disk. But maybe the details below help you spot something. Martin # gpt show -a wd0 start size index contents 0 1 PMBR 1 1 Pri GPT header 232 Pri GPT table 3430 Unused 64262144 1 GPT part - Windows basic data Type: windows TypeID: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 GUID: e4c1b47a-0e33-4800-acd5-8755f42eeabd Size: 128 M Label: Attributes: None 26220864 Unused 262272 45875133 2 GPT part - NetBSD FFSv1/FFSv2 Type: ffs TypeID: 49f48d5a-b10e-11dc-b99b-0019d1879648 GUID: 7878519c-4b35-427a-9e89-7b68cfd96920 Size: 22400 M Label: Attributes: biosboot, bootme 46137405 3 Unused 46137408 16777119 3 GPT part - NetBSD swap Type: swap TypeID: 49f48d32-b10e-11dc-b99b-0019d1879648 GUID: 6173740a-d903-4c13-84a3-ad7b516bd5ce Size: 8192 M Label: Attributes: None 6291452732 Sec GPT table 62914559 1 Sec GPT header # dkctl wd0 listwedges /dev/rwd0: 3 wedges: dk0: e4c1b47a-0e33-4800-acd5-8755f42eeabd, 262144 blocks at 64, type: ntfs dk1: 7878519c-4b35-427a-9e89-7b68cfd96920, 45875133 blocks at 262272, type: ffs dk2: 6173740a-d903-4c13-84a3-ad7b516bd5ce, 16777119 blocks at 46137408, type: swap # moutnt /dev/dk1 /mnt # ls -l /mnt/netbsd -rwxr-xr-x 1 root wheel 26214320 Jul 14 21:37 /mnt/netbsd -- 90% of my problems are due to ignorance, the other 10% is because I just don't know any better.
Re: No uefi install in VM
Thanks for responding Martin. Actually I did both. Selecting GPT did set things up but it does not boot. On 12/11/19 1:31 PM, Martin Husemann wrote: On Wed, Dec 11, 2019 at 01:28:31PM -0500, Ron Georgia wrote: I installed NetBSD 9.0_RC1 as a guest on VirtualBox 5.2.34 r133883 with GhostBSD as a host. I enabled EFI and booted from the iso image. I did follow the "instructions" on creating a gpt partition for efi I guess you followed the wiki page for NetBSD 8? With 9.0 you should not need to do anyhthing special, the installer knows about EFI and GPT. If you boot the install system via UEFI it will automatically create an EFI boot setup. Martin -- 90% of my problems are due to ignorance, the other 10% is because I just don't know any better.
No uefi install in VM
This feels like this question has been asked before, but I could not find what I was looking for in the mailing list archives. I installed NetBSD 9.0_RC1 as a guest on VirtualBox 5.2.34 r133883 with GhostBSD as a host. I enabled EFI and booted from the iso image. I did follow the "instructions" on creating a gpt partition for efi; however, when I exit to the menu and point the install target to dk1 (labeled NetBSD) it just returns me to the menu. I was able to install with mbr and legacy "bios." If I install allowing the gpt option to create the EFI boot it fails to boot with: mem[0x0 ... vbox> 0x11] >> NetBSD/x86 EFI Boot (x64), Revision 1.1... >> Memory: 640/3684184 k Press return to boot now, any other key for boot menu booting Name: netbsd - starting in 0 seconds. open netbsd: No such file or directory ... > ls The ls command is not currently supported for dosfs > If I boot from the iso image again and exit to the prompt I see this: # gpt show wd0 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Unused 64 262144 1 GPT part - Windows basic data ... # dkctl wd0 listwedges dk0: some-dashed-number, 262144 blocks at 64, type: ntfs dk1: some-dashed-number, blah, type: ffs dk2: some-dashed-number, blah, type: swap I am sure I am doing something wrong or am not understanding something correctly. Perhaps a friendly pointer, or a link to help me on my way? -- 90% of my problems are due to ignorance, the other 10% is because I just don't know any better.
Re: NetBSD 9.99.1 Quick Question
Perfect! On 7/31/19, 1:31 PM, "J. Lewis Muir" wrote: On 07/31, Ron Georgia wrote: > I noticed that images and sets for NetBSD 9.99.1 is out. I have a > totally noob question. According to the docs this would be current for > version 10. Does this mean version 9 will be released soon? Sorry for > my exuberant impatience. FYI, just today there was a message on netbsd-announce related to that (not directly an answer to your question, though): https://mail-index.netbsd.org/netbsd-announce/2019/07/31/msg000301.html Regards, Lewis
NetBSD 9.99.1 Quick Question
All, I noticed that images and sets for NetBSD 9.99.1 is out. I have a totally noob question. According to the docs this would be current for version 10. Does this mean version 9 will be released soon? Sorry for my exuberant impatience. Ron Georgia “90% of my problems are due to ignorance, the other 10% is because I just don’t know any better.”
Re: current - still problems with X11 and intel video
Thanks Matthew, this was helpful. On 6/25/19, 7:10 AM, "matthew green" wrote: Riccardo Mottola writes: > Hi, > > I just upgraded all kernel and userland, it took some time because of > the long buiild [*] [ .. ] > [*] what option to avoid building whole llvm again? I think it is not > needed for the intel driver, right? I remember some discussion to skip > that part two things to try: use UXA instead of SNA. just this in xorg.conf is all you need (or similar): Section "Device" Identifier "Card0" Driver "intel" Option "AccelMethod" "UXA" EndSection alternatively, downgrade the driver. if you cleandir and rebuild in src/external/mit/xorg/server/drivers/xf86-video-intel with 'nbmake-amd64 INTEL_DRIVER_DATE=2014', and install that. .mrg.
Re: aarch64 rust install failure
Sorry. I meant to send this to port-arm list.
On 6/16/19, 9:03 AM, "Robert Swindells" wrote:
Ron Georgia wrote:
>I have a Pinebook 1080P. I tried to build firefox on it and after three
>days of building I got the error listed below. I tried to install rustup
>but got an error; no evbarm. I added evbarm to the rust-init.sh switch
>statement. Another error I keep running into is libstdc++.so.8 not
>found.
This isn't really a problem with -current, rust bugs should go to
pkgsrc-us...@netbsd.org or raise a PR. You will probably get a better
response to ARM questions on port-arm too.
Someone needs to rebuild the bootstrap rust on a newer system to get
rid of the libstdc++ error. You shouldn't need to run rust-init.sh.
If you want a browser then firefox52 is easier to build on aarch64 as it
doesn't use rust. You will also want LIBRSVG_TYPE=c in /etc/mk.conf if
you go this route.
aarch64 rust install failure
I have a Pinebook 1080P. I tried to build firefox on it and after three days of building I got the error listed below. I tried to install rustup but got an error; no evbarm. I added evbarm to the rust-init.sh switch statement. Another error I keep running into is libstdc++.so.8 not found. evbarm) _cputype=aarch64 ;; Now when I run it I get this error: $ ./rustup-init.sh info: downloading installer curl: (22) The requested URL returned error: 404 Not Found rustup: command failed: downloader https://static.rust-lang.org/rustup/dist/aarch64-unknown-netbsd/rustup-init /tmp/mktemp.eaADP6ji/rustup-init MAKE INSTALL ERROR FOR FIREFOX error: process didn't exit successfully: `/usr/pkgsrc/lang/rust/work/rust-bootstrap/bin/rustc -vV` (exit code: 1) --- stdout rustc 1.35.0 binary: rustc commit-hash: unknown commit-date: unknown host: aarch64-unknown-netbsd release: 1.35.0 --- stderr error: couldn't load codegen backend "/usr/pkgsrc/lang/rust/work/rust-bootstrap/lib/rustlib/aarch64-unknown-netbsd/codegen-backends/librustc_codegen_llvm-llvm.so": "/usr/pkgsrc/lang/rust/work/rust-bootstrap/lib/rustlib/aarch64-unknown-netbsd/codegen-backends/librustc_codegen_llvm-llvm.so: Shared object \"libstdc++.so.8\" not found" Traceback (most recent call last): File "./x.py", line 11, in bootstrap.main() File "/usr/pkgsrc/lang/rust/work/rustc-1.35.0-src/src/bootstrap/bootstrap.py", line 849, in main bootstrap(help_triggered) File "/usr/pkgsrc/lang/rust/work/rustc-1.35.0-src/src/bootstrap/bootstrap.py", line 820, in bootstrap build.build_bootstrap() File "/usr/pkgsrc/lang/rust/work/rustc-1.35.0-src/src/bootstrap/bootstrap.py", line 656, in build_bootstrap run(args, env=env, verbose=self.verbose) File "/usr/pkgsrc/lang/rust/work/rustc-1.35.0-src/src/bootstrap/bootstrap.py", line 141, in run raise RuntimeError(err) RuntimeError: failed to run: /usr/pkgsrc/lang/rust/work/rust-bootstrap/bin/cargo build --manifest-path /usr/pkgsrc/lang/rust/work/rustc-1.35.0-src/src/bootstrap/Cargo.toml --frozen *** Error code 1 Stop. make[2]: stopped in /usr/pkgsrc/lang/rust *** Error code 1 Stop. make[1]: stopped in /usr/pkgsrc/lang/rust *** Error code 1 Stop. make: stopped in /usr/pkgsrc/www/firefox60 Ron Georgia “90% of my problems are due to ignorance, the other 10% is because I just don’t know any better.”
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
Thanks for all your help. I'll just stick with Ubuntu and KDE for now until my new 64G eMMC device arrives. A bit if irony, the microSD -> eMMC install works and shows a 16G device. I tried to install Archlinux and ran into problems as well. Again... thank you all for your help. I learned a lot. On 5/17/19, 9:10 AM, "Manuel Bouyer" wrote: On Fri, May 17, 2019 at 08:59:37AM -0400, Ron Georgia wrote: > What I did: > # sudo dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c bs=1m conv=sync > > dd: /dev/rld2c: Input/output error > 30+0 records in > 29+0 records out > 30408704 bytes transferred in 11.034 secs (2755909 bytes/sec) > > The link includes fdisk and disklabel info, along with before dd and after dd dmesg. > https://pastebin.com/vAR5U0tj it looks like you have real hardware errors here ... -- Manuel Bouyer NetBSD: 26 ans d'experience feront toujours la difference --
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
What I did: # sudo dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c bs=1m conv=sync dd: /dev/rld2c: Input/output error 30+0 records in 29+0 records out 30408704 bytes transferred in 11.034 secs (2755909 bytes/sec) The link includes fdisk and disklabel info, along with before dd and after dd dmesg. https://pastebin.com/vAR5U0tj On 5/16/19, 8:19 PM, "Mathew, Cherry G." wrote: On 17 May 2019 2:20:40 AM GMT+05:30, Manuel Bouyer wrote: >On Thu, May 16, 2019 at 02:47:02PM -0400, Ron Georgia wrote: >> I did try that, but did not get the results I expected. >> >> Expected: >> 1641+1 records in >> 1642+0 records out >> 1721761792 bytes transferred in 14.421 secs (119392676 bytes/sec) >> >> Actual: >> arm64# time dd if=pinebook1080p.img of=/dev/rld2c bs=1m conv=sync >> dd: /dev/rld2c: Input/output error >> 30+0 records in >> 29+0 records out >> 30408704 bytes transferred in 10.334 secs (2942587 bytes/sec) > >Anything in dmesg about this ? > >> >> Trying hard to not sound frustrated, but what am I missing. Is the >eMMC messed up maybe? Once I boot from the microSD card, what do I dd >to the raw ld2 device? I was able to dd arm64.img to /dev/rld2c, but I >am not sure how to install the u-boot portion. I hate being a pain, but >I really want my NetBSD. (Blast from the 80s?) > >You should be able to do it the same way to did your sd card. Silly unrelated question. Does anyone have pinebook 'ROM' image originals somewhere for download ? -- Sent from my phone. Please excuse my brevity.
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
I did try that, but did not get the results I expected. Expected: 1641+1 records in 1642+0 records out 1721761792 bytes transferred in 14.421 secs (119392676 bytes/sec) Actual: arm64# time dd if=pinebook1080p.img of=/dev/rld2c bs=1m conv=sync dd: /dev/rld2c: Input/output error 30+0 records in 29+0 records out 30408704 bytes transferred in 10.334 secs (2942587 bytes/sec) Trying hard to not sound frustrated, but what am I missing. Is the eMMC messed up maybe? Once I boot from the microSD card, what do I dd to the raw ld2 device? I was able to dd arm64.img to /dev/rld2c, but I am not sure how to install the u-boot portion. I hate being a pain, but I really want my NetBSD. (Blast from the 80s?) On 5/16/19, 1:31 PM, "Manuel Bouyer" wrote: On Thu, May 16, 2019 at 12:55:03PM -0400, Ron Georgia wrote: > I am trying this again. A little different take. > 1. Downloaded arm64.img to my NetBSD workstation > 2. make, install of pkgsrc/sysutils/u-boot-pinebook > 3. dd if=arm64.img of=pinebook1080p.img bs=1m conv=sync,notrunc > 4. dd if=/usr/pkg/share/u-boot/pinebook/u-boot-sunxi-with-spl.bin of=pinebook1080p.img bs=1k seek=8 conv=sync > 5. scp image to Mac > 6. used Pinebook flash program for Mac to "flash" microSD with image pinebook1080p.img > 7. Booted Pinebook with pinebook1080p.img microSD card (booted perfectly) > 8. scp a copy of pinebook1080p.img to Pinebook booted from SD card > 9. arm64# dd if=pinebook1080p.img of=/dev/ld2c bs=1m conv=sync This should be /dev/rld2c -- Manuel Bouyer NetBSD: 26 ans d'experience feront toujours la difference --
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
I am trying this again. A little different take.
1. Downloaded arm64.img to my NetBSD workstation
2. make, install of pkgsrc/sysutils/u-boot-pinebook
3. dd if=arm64.img of=pinebook1080p.img bs=1m conv=sync,notrunc
4. dd if=/usr/pkg/share/u-boot/pinebook/u-boot-sunxi-with-spl.bin
of=pinebook1080p.img bs=1k seek=8 conv=sync
5. scp image to Mac
6. used Pinebook flash program for Mac to "flash" microSD with image
pinebook1080p.img
7. Booted Pinebook with pinebook1080p.img microSD card (booted perfectly)
8. scp a copy of pinebook1080p.img to Pinebook booted from SD card
9. arm64# dd if=pinebook1080p.img of=/dev/ld2c bs=1m conv=sync
The last step, as usual, is generating a TON (907.185kg) of errors. It has been
running for about three hours. I am thinking that's not a good sign. I'll let
it run all night to see if it finishes.
Question: should I instead try to dd if=/dev/ld0 of=/dev/ld2 bs=1m conv=sync? I
mean, as long as the SD is the same size as eMMC (16G).
On 5/14/19, 3:38 PM, "Jared McNeill" wrote:
You have to write the image to the “entire disk” partition (rld2c), which
will overwrite the disk label anyway.
> On May 14, 2019, at 4:27 PM, Ron Georgia wrote:
>
> Question: if I disklabel -eI ld2 and remove partition e, then dd the
image again to /dev/rld2e, will that work or will I have a Pinebrick?
>
> On 5/14/19, 1:54 PM, "Ron Georgia" wrote:
>
>Well... I did both
>
>arm64# dd if=arm64.img of=/dev/rld2c bs=1m conv=sync
>dd: /dev/rld2c: Input/output error
>30+0 records in
>29+0 records out
>30408704 bytes transferred in 9.927 secs (3063231 bytes/sec)
>
>And
>
>arm64# dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img
of=/dev/rld2c bs=1m conv=sync
>dd: /dev/rld2c: Input/output error
>30+0 records in
>29+0 records out
>30408704 bytes transferred in 11.143 secs (2728951 bytes/sec)
>
>Both commands generated a ton of "ld2c: error writing fsbn..." errors.
When I reboot I get a blank screen. ( Any thoughts on what I can do?
>
>Disklabel looks like this:
>arm64# disklabel ld2
># /dev/rld2:
>type: ld
>disk: ld2
>label: default label
>flags:
>bytes/sector: 512
>sectors/track: 63
>tracks/cylinder: 32
>sectors/cylinder: 2016
>cylinders: 1040
>total sectors: 2097152
>rpm: 3600
>interleave: 1
>trackskew: 0
>cylinderskew: 0
>headswitch: 0 # microseconds
>track-to-track seek: 0 # microseconds
>drivedata: 0
>
>5 partitions:
>#sizeoffset fstype [fsize bsize cpg/sgs]
> c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0
- 1040*)
> e:163840 32768 MSDOS # (Cyl.
16*- 97*)
>disklabel: boot block size 0
>disklabel: super block size 0
>disklabel: partitions c and e overlap
>
>I will surmise that overlapping partitions are not good?
>
>On 5/14/19, 12:53 PM, "Jason Thorpe" wrote:
>
>
>
>> On May 14, 2019, at 9:33 AM, Ron Georgia wrote:
>>
>> If I understand correctly:
>> 1. boot Pinebook from microSD loaded with Pinebook NetBSD ARM Bootable
Images from https://www.invisible.ca/arm/
>> 2. download arm64.img from
ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/
to microSD card.
>
>You can dd the invisible.ca imagine to the eMMC as well. It's
just a standard arm64.img with u-boot helpfully added by Jared; no need to
download a second one (to which you would then need to add u-boot).
>
>> 3. dd image to /dev/rld2c
>> 4. Power down, remove SD card and reboot.
>>
>> Correct?
>> For YES, press 1
>> For NO, press 2
>>
>> On 5/14/19, 10:15 AM, "Jared McNeill" wrote:
>>
>> Easiest way is to download the image to the SD card, then dd it to the
>> eMMC:
>>
>> # dd if=arm64.img of=/dev/rld2c bs=1m conv=sync
>>
>> You can't "wreck" your Pinebook this way as it will always try to boot
>> from SD card first. So after writing the image to eMMC, shutdown the
>> computer, remove the SD card, and power it back on. If something goes
>> wrong, plug the SD card back in and it will boot from that device when
you
>> power it bac
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
Okay… let’s try this again. I restored my Pinebook 1080p to its original
condition. I am including some maybe, helpful data below. I just want to make
sure I understand the process so I do not end up in the same place I just came
out of.
1. I created a NetBSD bootable microSD card using the image from invisible.ca
2. I boot the Pinebook and ftp that same image to the microSD card.
3. I dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c bs=1m
sync=conv
4. Power off Pinebook and remove microSD card.
5. Power on. Should boot NetBSD.
Is that correct?
What about the message “ld2: mbr partition exceeds disk size?” Is that a
problem?
arm64$ ll -h
total 1.6G
-rw-r--r-- 1 xxx users 1.6G May 14 17:10
NetBSD-evbarm-aarch64-201905120950Z-pinebook.img
arm64$ sudo disklabel ld2
# /dev/rld2:
type: ld
disk: ld2
label: default label
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 32
sectors/cylinder: 2016
cylinders: 1040
total sectors: 2097152
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
3 partitions:
#sizeoffset fstype [fsize bsize cpg/sgs]
a: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*)
c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*)
disklabel: boot block size 0
disklabel: super block size 0
disklabel: partitions a and c overlap
arm64$ dmesg | grep -i ld2
[ 2.830954] ld2 at sdmmc2: <0x45:0x0100:DF4016:0x00:0xfe875b0b:0x000>
[ 2.849514] ld2: 1024 MB, 1040 cyl, 32 head, 63 sec, 512 bytes/sect x
2097152 sectors
[ 2.879516] ld2: mbr partition exceeds disk size
[ 2.879516] ld2: 8-bit width, 200.000 MHz
[ 7.895029] ld2: mbr partition exceeds disk size
[75.708145] ld2: mbr partition exceeds disk size
[ 398.482117] ld2: mbr partition exceeds disk size
arm64$ sudo fdisk ld2
fdisk: Cannot determine the number of heads
Disk: /dev/rld2
NetBSD disklabel disk geometry:
cylinders: 1040, heads: 32, sectors/track: 63 (2016 sectors/cylinder)
total sectors: 2097152, bytes/sector: 512
BIOS disk geometry:
cylinders: 130, heads: 255, sectors/track: 63 (16065 sectors/cylinder)
total sectors: 2097152
Partitions aligned to 2048 sector boundaries, offset 63
Partition table:
0: Linux native (sysid 131)
start 40960, size 30736384 (15008 MB, Cyls 2/140/11-1915/204/17)
PBR is not bootable: All bytes are identical (0x00)
1:
2:
3:
No active partition.
Drive serial number: 1687624172 (0x649719ec)
On 5/14/19, 3:38 PM, "Jared McNeill" wrote:
You have to write the image to the “entire disk” partition (rld2c), which
will overwrite the disk label anyway.
> On May 14, 2019, at 4:27 PM, Ron Georgia wrote:
>
> Question: if I disklabel -eI ld2 and remove partition e, then dd the
image again to /dev/rld2e, will that work or will I have a Pinebrick?
>
> On 5/14/19, 1:54 PM, "Ron Georgia" wrote:
>
>Well... I did both
>
>arm64# dd if=arm64.img of=/dev/rld2c bs=1m conv=sync
>dd: /dev/rld2c: Input/output error
>30+0 records in
>29+0 records out
>30408704 bytes transferred in 9.927 secs (3063231 bytes/sec)
>
>And
>
>arm64# dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img
of=/dev/rld2c bs=1m conv=sync
>dd: /dev/rld2c: Input/output error
>30+0 records in
>29+0 records out
>30408704 bytes transferred in 11.143 secs (2728951 bytes/sec)
>
>Both commands generated a ton of "ld2c: error writing fsbn..." errors.
When I reboot I get a blank screen. ( Any thoughts on what I can do?
>
>Disklabel looks like this:
>arm64# disklabel ld2
># /dev/rld2:
>type: ld
>disk: ld2
>label: default label
>flags:
>bytes/sector: 512
>sectors/track: 63
>tracks/cylinder: 32
>sectors/cylinder: 2016
>cylinders: 1040
>total sectors: 2097152
>rpm: 3600
>interleave: 1
>trackskew: 0
>cylinderskew: 0
>headswitch: 0 # microseconds
>track-to-track seek: 0 # microseconds
>drivedata: 0
>
>5 partit
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
When I dd from a terminal on my Mac, I get an error printed to the console,
"ld2: mbr partition exceeds disk size"
On 5/14/19, 3:38 PM, "Jared McNeill" wrote:
You have to write the image to the “entire disk” partition (rld2c), which
will overwrite the disk label anyway.
> On May 14, 2019, at 4:27 PM, Ron Georgia wrote:
>
> Question: if I disklabel -eI ld2 and remove partition e, then dd the
image again to /dev/rld2e, will that work or will I have a Pinebrick?
>
> On 5/14/19, 1:54 PM, "Ron Georgia" wrote:
>
>Well... I did both
>
>arm64# dd if=arm64.img of=/dev/rld2c bs=1m conv=sync
>dd: /dev/rld2c: Input/output error
>30+0 records in
>29+0 records out
>30408704 bytes transferred in 9.927 secs (3063231 bytes/sec)
>
>And
>
>arm64# dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img
of=/dev/rld2c bs=1m conv=sync
>dd: /dev/rld2c: Input/output error
>30+0 records in
>29+0 records out
>30408704 bytes transferred in 11.143 secs (2728951 bytes/sec)
>
>Both commands generated a ton of "ld2c: error writing fsbn..." errors.
When I reboot I get a blank screen. ( Any thoughts on what I can do?
>
>Disklabel looks like this:
>arm64# disklabel ld2
># /dev/rld2:
>type: ld
>disk: ld2
>label: default label
>flags:
>bytes/sector: 512
>sectors/track: 63
>tracks/cylinder: 32
>sectors/cylinder: 2016
>cylinders: 1040
>total sectors: 2097152
>rpm: 3600
>interleave: 1
>trackskew: 0
>cylinderskew: 0
>headswitch: 0 # microseconds
>track-to-track seek: 0 # microseconds
>drivedata: 0
>
>5 partitions:
>#sizeoffset fstype [fsize bsize cpg/sgs]
> c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0
- 1040*)
> e:163840 32768 MSDOS # (Cyl.
16*- 97*)
>disklabel: boot block size 0
>disklabel: super block size 0
>disklabel: partitions c and e overlap
>
>I will surmise that overlapping partitions are not good?
>
>On 5/14/19, 12:53 PM, "Jason Thorpe" wrote:
>
>
>
>> On May 14, 2019, at 9:33 AM, Ron Georgia wrote:
>>
>> If I understand correctly:
>> 1. boot Pinebook from microSD loaded with Pinebook NetBSD ARM Bootable
Images from https://www.invisible.ca/arm/
>> 2. download arm64.img from
ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/
to microSD card.
>
>You can dd the invisible.ca imagine to the eMMC as well. It's
just a standard arm64.img with u-boot helpfully added by Jared; no need to
download a second one (to which you would then need to add u-boot).
>
>> 3. dd image to /dev/rld2c
>> 4. Power down, remove SD card and reboot.
>>
>> Correct?
>> For YES, press 1
>> For NO, press 2
>>
>> On 5/14/19, 10:15 AM, "Jared McNeill" wrote:
>>
>> Easiest way is to download the image to the SD card, then dd it to the
>> eMMC:
>>
>> # dd if=arm64.img of=/dev/rld2c bs=1m conv=sync
>>
>> You can't "wreck" your Pinebook this way as it will always try to boot
>> from SD card first. So after writing the image to eMMC, shutdown the
>> computer, remove the SD card, and power it back on. If something goes
>> wrong, plug the SD card back in and it will boot from that device when
you
>> power it back on.
>>
>>
>> On Tue, 14 May 2019, Ron Georgia wrote:
>>
>>> Instead of creating the image with dd, I followed the suggestion of
building the image with "highly recommend" Etcher. I am now able to login as
root! Not sure what happened. I am documenting every step of the way in order
to make my journey, mistakes and all, available to other "not so savvy"
Pinebook users.
>>>
>>> How do I install NetBSD directly onto my Pinebook? Do I use sysinst
(per https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)?
>>> Before I "wreck" my Pinebook, do I select ld2 as the drive to partition
and install?
>>>
>>> === MISC DATA ===
>>> arm64# disklabel ld0
>>> # /de
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
I did, but I get a massive amount of errors. On 5/14/19, 3:38 PM, "Jared McNeill" wrote: You have to write the image to the “entire disk” partition (rld2c), which will overwrite the disk label anyway. > On May 14, 2019, at 4:27 PM, Ron Georgia wrote: > > Question: if I disklabel -eI ld2 and remove partition e, then dd the image again to /dev/rld2e, will that work or will I have a Pinebrick? > > On 5/14/19, 1:54 PM, "Ron Georgia" wrote: > >Well... I did both > >arm64# dd if=arm64.img of=/dev/rld2c bs=1m conv=sync >dd: /dev/rld2c: Input/output error >30+0 records in >29+0 records out >30408704 bytes transferred in 9.927 secs (3063231 bytes/sec) > >And > >arm64# dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c bs=1m conv=sync >dd: /dev/rld2c: Input/output error >30+0 records in >29+0 records out >30408704 bytes transferred in 11.143 secs (2728951 bytes/sec) > >Both commands generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen. ( Any thoughts on what I can do? > >Disklabel looks like this: >arm64# disklabel ld2 ># /dev/rld2: >type: ld >disk: ld2 >label: default label >flags: >bytes/sector: 512 >sectors/track: 63 >tracks/cylinder: 32 >sectors/cylinder: 2016 >cylinders: 1040 >total sectors: 2097152 >rpm: 3600 >interleave: 1 >trackskew: 0 >cylinderskew: 0 >headswitch: 0 # microseconds >track-to-track seek: 0 # microseconds >drivedata: 0 > >5 partitions: >#sizeoffset fstype [fsize bsize cpg/sgs] > c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) > e:163840 32768 MSDOS # (Cyl. 16*- 97*) >disklabel: boot block size 0 >disklabel: super block size 0 >disklabel: partitions c and e overlap > >I will surmise that overlapping partitions are not good? > >On 5/14/19, 12:53 PM, "Jason Thorpe" wrote: > > > >> On May 14, 2019, at 9:33 AM, Ron Georgia wrote: >> >> If I understand correctly: >> 1. boot Pinebook from microSD loaded with Pinebook NetBSD ARM Bootable Images from https://www.invisible.ca/arm/ >> 2. download arm64.img from ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/ to microSD card. > >You can dd the invisible.ca imagine to the eMMC as well. It's just a standard arm64.img with u-boot helpfully added by Jared; no need to download a second one (to which you would then need to add u-boot). > >> 3. dd image to /dev/rld2c >> 4. Power down, remove SD card and reboot. >> >> Correct? >> For YES, press 1 >> For NO, press 2 >> >> On 5/14/19, 10:15 AM, "Jared McNeill" wrote: >> >> Easiest way is to download the image to the SD card, then dd it to the >> eMMC: >> >> # dd if=arm64.img of=/dev/rld2c bs=1m conv=sync >> >> You can't "wreck" your Pinebook this way as it will always try to boot >> from SD card first. So after writing the image to eMMC, shutdown the >> computer, remove the SD card, and power it back on. If something goes >> wrong, plug the SD card back in and it will boot from that device when you >> power it back on. >> >> >> On Tue, 14 May 2019, Ron Georgia wrote: >> >>> Instead of creating the image with dd, I followed the suggestion of building the image with "highly recommend" Etcher. I am now able to login as root! Not sure what happened. I am documenting every step of the way in order to make my journey, mistakes and all, available to other "not so savvy" Pinebook users. >>> >>> How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? >>> Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and install? >>> >>> === MISC DATA === >>> arm64# disklabel ld0 >>> # /dev/rld0: >>> type: SCSI >>> disk: STORAGE DEVICE >&g
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
Question: if I disklabel -eI ld2 and remove partition e, then dd the image again to /dev/rld2e, will that work or will I have a Pinebrick? On 5/14/19, 1:54 PM, "Ron Georgia" wrote: Well... I did both arm64# dd if=arm64.img of=/dev/rld2c bs=1m conv=sync dd: /dev/rld2c: Input/output error 30+0 records in 29+0 records out 30408704 bytes transferred in 9.927 secs (3063231 bytes/sec) And arm64# dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c bs=1m conv=sync dd: /dev/rld2c: Input/output error 30+0 records in 29+0 records out 30408704 bytes transferred in 11.143 secs (2728951 bytes/sec) Both commands generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen. ( Any thoughts on what I can do? Disklabel looks like this: arm64# disklabel ld2 # /dev/rld2: type: ld disk: ld2 label: default label flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 32 sectors/cylinder: 2016 cylinders: 1040 total sectors: 2097152 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 5 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) e:163840 32768 MSDOS # (Cyl. 16*- 97*) disklabel: boot block size 0 disklabel: super block size 0 disklabel: partitions c and e overlap I will surmise that overlapping partitions are not good? On 5/14/19, 12:53 PM, "Jason Thorpe" wrote: > On May 14, 2019, at 9:33 AM, Ron Georgia wrote: > > If I understand correctly: > 1. boot Pinebook from microSD loaded with Pinebook NetBSD ARM Bootable Images from https://www.invisible.ca/arm/ > 2. download arm64.img from ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/ to microSD card. You can dd the invisible.ca imagine to the eMMC as well. It's just a standard arm64.img with u-boot helpfully added by Jared; no need to download a second one (to which you would then need to add u-boot). > 3. dd image to /dev/rld2c > 4. Power down, remove SD card and reboot. > > Correct? > For YES, press 1 > For NO, press 2 > > On 5/14/19, 10:15 AM, "Jared McNeill" wrote: > >Easiest way is to download the image to the SD card, then dd it to the >eMMC: > > # dd if=arm64.img of=/dev/rld2c bs=1m conv=sync > >You can't "wreck" your Pinebook this way as it will always try to boot >from SD card first. So after writing the image to eMMC, shutdown the >computer, remove the SD card, and power it back on. If something goes >wrong, plug the SD card back in and it will boot from that device when you >power it back on. > > >On Tue, 14 May 2019, Ron Georgia wrote: > >> Instead of creating the image with dd, I followed the suggestion of building the image with "highly recommend" Etcher. I am now able to login as root! Not sure what happened. I am documenting every step of the way in order to make my journey, mistakes and all, available to other "not so savvy" Pinebook users. >> >> How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? >> Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and install? >> >> === MISC DATA === >> arm64# disklabel ld0 >> # /dev/rld0: >> type: SCSI >> disk: STORAGE DEVICE >> label: fictitious >> flags: removable >> bytes/sector: 512 >> sectors/track: 32 >> tracks/cylinder: 64 >> sectors/cylinder: 2048 >> cylinders: 1641 >> total sectors: 31116288 >> rpm: 3600 >> interleave: 1 >> trackskew: 0 >> cylinderskew: 0 >> headswitch: 0 # microseconds >> track-to-track seek: 0 # microseconds >> drivedata: 0 >> >> 8 partitions: >> #sizeoffset fstype [fsize bsize cpg/sgs] >> a: 30657536
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
Well... I did both arm64# dd if=arm64.img of=/dev/rld2c bs=1m conv=sync dd: /dev/rld2c: Input/output error 30+0 records in 29+0 records out 30408704 bytes transferred in 9.927 secs (3063231 bytes/sec) And arm64# dd if=NetBSD-evbarm-aarch64-201905120950Z-pinebook.img of=/dev/rld2c bs=1m conv=sync dd: /dev/rld2c: Input/output error 30+0 records in 29+0 records out 30408704 bytes transferred in 11.143 secs (2728951 bytes/sec) Both commands generated a ton of "ld2c: error writing fsbn..." errors. When I reboot I get a blank screen. ( Any thoughts on what I can do? Disklabel looks like this: arm64# disklabel ld2 # /dev/rld2: type: ld disk: ld2 label: default label flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 32 sectors/cylinder: 2016 cylinders: 1040 total sectors: 2097152 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 5 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) e:163840 32768 MSDOS # (Cyl. 16*- 97*) disklabel: boot block size 0 disklabel: super block size 0 disklabel: partitions c and e overlap I will surmise that overlapping partitions are not good? On 5/14/19, 12:53 PM, "Jason Thorpe" wrote: > On May 14, 2019, at 9:33 AM, Ron Georgia wrote: > > If I understand correctly: > 1. boot Pinebook from microSD loaded with Pinebook NetBSD ARM Bootable Images from https://www.invisible.ca/arm/ > 2. download arm64.img from ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/ to microSD card. You can dd the invisible.ca imagine to the eMMC as well. It's just a standard arm64.img with u-boot helpfully added by Jared; no need to download a second one (to which you would then need to add u-boot). > 3. dd image to /dev/rld2c > 4. Power down, remove SD card and reboot. > > Correct? > For YES, press 1 > For NO, press 2 > > On 5/14/19, 10:15 AM, "Jared McNeill" wrote: > >Easiest way is to download the image to the SD card, then dd it to the >eMMC: > > # dd if=arm64.img of=/dev/rld2c bs=1m conv=sync > >You can't "wreck" your Pinebook this way as it will always try to boot >from SD card first. So after writing the image to eMMC, shutdown the >computer, remove the SD card, and power it back on. If something goes >wrong, plug the SD card back in and it will boot from that device when you >power it back on. > > >On Tue, 14 May 2019, Ron Georgia wrote: > >> Instead of creating the image with dd, I followed the suggestion of building the image with "highly recommend" Etcher. I am now able to login as root! Not sure what happened. I am documenting every step of the way in order to make my journey, mistakes and all, available to other "not so savvy" Pinebook users. >> >> How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? >> Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and install? >> >> === MISC DATA === >> arm64# disklabel ld0 >> # /dev/rld0: >> type: SCSI >> disk: STORAGE DEVICE >> label: fictitious >> flags: removable >> bytes/sector: 512 >> sectors/track: 32 >> tracks/cylinder: 64 >> sectors/cylinder: 2048 >> cylinders: 1641 >> total sectors: 31116288 >> rpm: 3600 >> interleave: 1 >> trackskew: 0 >> cylinderskew: 0 >> headswitch: 0 # microseconds >> track-to-track seek: 0 # microseconds >> drivedata: 0 >> >> 8 partitions: >> #sizeoffset fstype [fsize bsize cpg/sgs] >> a: 30657536458752 4.2BSD 0 0 0 # (Cyl.224 - 15193*) >> b:262144196608 swap # (Cyl. 96 - 223) >> c: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) >> d: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) >> e:163840 32768 MSDOS # (Cyl. 16 - 95) >> >> arm64# disklabel ld2 >> # /dev/rld2: >> type: ld >> disk: ld2 >> label: default label >> flags: >> bytes/sector: 512 >> sector
Re: Pinebook and NetBSD 8.99.39 [UPDATE]
If I understand correctly: 1. boot Pinebook from microSD loaded with Pinebook NetBSD ARM Bootable Images from https://www.invisible.ca/arm/ 2. download arm64.img from ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201905140810Z/evbarm-aarch64/binary/gzimg/ to microSD card. 3. dd image to /dev/rld2c 4. Power down, remove SD card and reboot. Correct? For YES, press 1 For NO, press 2 On 5/14/19, 10:15 AM, "Jared McNeill" wrote: Easiest way is to download the image to the SD card, then dd it to the eMMC: # dd if=arm64.img of=/dev/rld2c bs=1m conv=sync You can't "wreck" your Pinebook this way as it will always try to boot from SD card first. So after writing the image to eMMC, shutdown the computer, remove the SD card, and power it back on. If something goes wrong, plug the SD card back in and it will boot from that device when you power it back on. On Tue, 14 May 2019, Ron Georgia wrote: > Instead of creating the image with dd, I followed the suggestion of building the image with "highly recommend" Etcher. I am now able to login as root! Not sure what happened. I am documenting every step of the way in order to make my journey, mistakes and all, available to other "not so savvy" Pinebook users. > > How do I install NetBSD directly onto my Pinebook? Do I use sysinst (per https://wiki.netbsd.org/ports/evbarm/install_using_sysinst/)? > Before I "wreck" my Pinebook, do I select ld2 as the drive to partition and install? > > === MISC DATA === > arm64# disklabel ld0 > # /dev/rld0: > type: SCSI > disk: STORAGE DEVICE > label: fictitious > flags: removable > bytes/sector: 512 > sectors/track: 32 > tracks/cylinder: 64 > sectors/cylinder: 2048 > cylinders: 1641 > total sectors: 31116288 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # microseconds > track-to-track seek: 0 # microseconds > drivedata: 0 > > 8 partitions: > #sizeoffset fstype [fsize bsize cpg/sgs] > a: 30657536458752 4.2BSD 0 0 0 # (Cyl.224 - 15193*) > b:262144196608 swap # (Cyl. 96 - 223) > c: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) > d: 31116288 0 unused 0 0# (Cyl. 0 - 15193*) > e:163840 32768 MSDOS # (Cyl. 16 - 95) > > arm64# disklabel ld2 > # /dev/rld2: > type: ld > disk: ld2 > label: default label > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 32 > sectors/cylinder: 2016 > cylinders: 1040 > total sectors: 2097152 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # microseconds > track-to-track seek: 0 # microseconds > drivedata: 0 > > 3 partitions: > #sizeoffset fstype [fsize bsize cpg/sgs] > a: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) > c: 2097152 0 4.2BSD 0 0 0 # (Cyl. 0 - 1040*) > disklabel: boot block size 0 > disklabel: super block size 0 > disklabel: partitions a and c overlap > > arm64# gpt show ld0 > GPT not found, displaying data from MBR. > > start size index contents > 0 1 MBR > 1 32767 Unused > 32768163840 1 MBR part 12 (active) >196608262144 Unused >458752 30657536 2 MBR part 169 > > arm64# gpt show ld2 > gpt: /dev/rld2: map entry doesn't fit media: new start + new size < start + size > (1 + 1f < a000 + 1d5) > > arm64# dmesg | grep ld > [ 1.16] axpreg5 at axppmic0: eldo2 > [ 2.737735] sdmmc1: autoconfiguration error: couldn't enable card: 60 > [ 2.811871] ld2 at sdmmc2: <0x45:0x0100:DF4016:0x00:0xfe875b0b:0x000> > [ 2.811871] ld2: 1024 MB, 1040 cyl, 32 head, 63 sec, 512 bytes/sect x 2097152 sectors > [ 2.828746] ld0 at sdmmc0: <0x03:0x5344:SS16G:0x80:0x42ce3d51:0x122> > [ 2.848748] ld0: 15193 MB, 7717 cyl, 64 head, 63 sec, 512 bytes/sect x 31116288 sectors > [ 2.848748] ld2: mbr partition exceeds disk size > [ 2.848748] ld2: 8-bit width, 200.000 MHz > [ 2.876482] ld0: 4-bit width, High-Speed/SDR25, 50.000 MHz > [ 7.617842] ld2: mbr partition ex
Pinebook and NetBSD 8.99.39 [UPDATE]
BSD to a hard disk, or upgrade an existing NetBSD system, with a minimum of work. In the following menus type the reference letter (a, b, c, ...) to select an item, or type CTRL+N/CTRL+P to select the next/previous item. The arrow keys and Page-up/Page-down may also work. Activate the current selection from the menu by typing the enter key. If you booted from a floppy, you may now remove the disk. Thank you for using NetBSD! NetBSD-8.99.39 Install System >a: Install NetBSD to hard disk b: Upgrade NetBSD on a hard disk c: Re-install sets or install additional sets d: Reboot the computer e: Utility menu f: Config menu x: Exit Install System On which disk do you want to install NetBSD? ┌──┐ │ Available disks │ │ │ │>a: ld2 │ │ b: Extended partitioning │ │ x: Exit │ └──┘ ============ I do not see ld0. On 5/14/19, 8:59 AM, "Ron Georgia" wrote: I just received my new 1080P 11inch (27.94 cm) Pinebook. It was pre-loaded with Ubuntu and KDE. While I like KDE, it seems a bit heavy. Ubuntu is ... ok, but I would rather have NetBSD and LXDE or Mate. I attempted to install NetBSD but ran into some problems. Most likely due to my incomplete understanding (see tag line below). 1. I downloaded the Pinebook image (NetBSD-evbarm-aarch64-201905120950Z-pinebook.img) from https://www.invisible.ca/arm/ 2. dd the image to my microSD card. 3. Inserted the micro SD into the SD slot of the Pinebook and booted. The first boot ended in a ==> prompt. Not sure what that was all about. Reboot produced the NetBSD "arm" boot processes; however, there was a problem. When presented with the login prompt I tried to type "root" but the right side of the keyboard acts like a number pad. Pressing "o" gives me the escape sequence for a "6" without the numlock engaged. Pressing shift "o" gets me a capital O while Fn + o gets me a "6." Questions: 1. Is there a way to make the keyboard a standard keyboard? 2. Once booted, now do I "reflash" the internal drive to boot NetBSD without having to boot from the micro SD card? Ron Georgia “90% of my problems are due to ignorance, the other 10% is because I just don’t know any better.”
Pinebook and NetBSD 8.99.39
I just received my new 1080P 11inch (27.94 cm) Pinebook. It was pre-loaded with Ubuntu and KDE. While I like KDE, it seems a bit heavy. Ubuntu is ... ok, but I would rather have NetBSD and LXDE or Mate. I attempted to install NetBSD but ran into some problems. Most likely due to my incomplete understanding (see tag line below). 1. I downloaded the Pinebook image (NetBSD-evbarm-aarch64-201905120950Z-pinebook.img) from https://www.invisible.ca/arm/ 2. dd the image to my microSD card. 3. Inserted the micro SD into the SD slot of the Pinebook and booted. The first boot ended in a ==> prompt. Not sure what that was all about. Reboot produced the NetBSD "arm" boot processes; however, there was a problem. When presented with the login prompt I tried to type "root" but the right side of the keyboard acts like a number pad. Pressing "o" gives me the escape sequence for a "6" without the numlock engaged. Pressing shift "o" gets me a capital O while Fn + o gets me a "6." Questions: 1. Is there a way to make the keyboard a standard keyboard? 2. Once booted, now do I "reflash" the internal drive to boot NetBSD without having to boot from the micro SD card? using the "highly recommend" Etcher Ron Georgia “90% of my problems are due to ignorance, the other 10% is because I just don’t know any better.”
Re: Funky Display Output:
All, When I switched to using modesetting the tearing issue went away; however the display was a little grainy and there was a lot of "lag" in the video when doing things like moving a window (like when I used to use Window 3.1.1 on my 286 6MHz beast of a machine). I changed the driver to intel and, as stated before, set Option "TearFree" to "true" and "AccelMethod" to "sna" I do not see any performance hits with those settings. I need to dig into what those really do, since I found those settings on the web, maybe Arch Linux or something. As a refresher here are some snippets of my dmesg, in case that will help someone else with similar hardware. $ dmesg | grep 915 [ 11702.721326] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:132)intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe A: -35 [ 20965.874027] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)urtwn0: autoconfiguration error: timeout waiting for firmware readiness [ 239105.050842] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:132)intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe A: -35 [ 239242.105019] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/drm_edid.c:1148)drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 113 [ 239250.238323] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)syncing disks... done [ 1.073974] i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product 5912 (rev. 0x04) [ 5.915292] uhid1 at uhidev1 reportid 23: input=0, output=0, feature=1 [ 7.915232] wsmouse1 at ums1 mux 0 [ 8.766356] i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0) [ 8.919713] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:636)i915_firmware_load_error_print] *ERROR* failed to load firmware i915/kbl_dmc_ver1.bin (0) [ 8.993574] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:651)i915_firmware_load_error_print] *ERROR* The driver is built-in, so to load the firmware you need to [ 9.135295] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_guc_loader.c:560)guc_fw_fetch] *ERROR* Failed to fetch GuC firmware from i915/kbl_guc_ver9_14.bin (error -2) [ 9.260212] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem.c:5417)i915_gem_init_hw] *ERROR* Failed to initialize GuC, error -5 (ignored) [ 9.400418] intelfb0 at i915drmkms0 $ dmesg | grep intelfb0 [ 9.400418] intelfb0 at i915drmkms0 [ 9.430463] intelfb0: framebuffer at 0xb30259d9c000, size 1920x1080, depth 32, stride 7680 [10.051376] wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0 $ dmesg | grep -i error [ 11702.721326] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:132)intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe A: -35 [ 20965.874027] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)urtwn0: autoconfiguration error: timeout waiting for firmware readiness [ 239105.050842] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:132)intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe A: -35 [ 239242.105019] warning: /usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c:3616: WARN_ON(!wm_changed)kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/drm_edid.c:1148)drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 113 [ 239250.158191] kern error: Raw EDID: [ 1.073974] acpiec0 at acpi0 (H_EC, PNP0C09-1)acpiec0: autoconfiguration error: unable to evaluate _GPE: AE_NOT_FOUND [ 1.073974] acpivga0: autoconfiguration error: unknown output device acpiout0 [ 1.073974] acpivga0: autoconfiguration error: unknown output device acpiout1 [ 1.073974] acpivga0: autoconfiguration error: unknown output device acpiout2 [ 1.073974] acpivga0: autoconfiguration error: unknown output device acpiout3 [ 1.073974] acpivga0: autoconfiguration error: unknown output device acpiout4 [ 1.073974] acpivga0: autoconfiguration error: unknown output device acpiout5 [ 1.073974] acpivga0: autoconfiguration error: unknown output device acpiout6 [ 1.073974] acpivga0: autoconfiguration error:
Re: intelfb0 at i915drmkms0
The thread titled " Funky Display Output" has an on going discussion that involves this issue. On 4/29/19, 5:13 AM, "Travis Paul" wrote: Is anyone else seeing artifacts when using X in base, with i915 Intel graphics? [1][2][3] I have 2 identical machines that experience this behavior, the artifacts never stop appearing so X is fairly unusable. The artifacts are even worse with fluxbox. I also see the following kernel errors often: kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:132)intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe C: -35 kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:205)intel_pipe_update_end] *ERROR* Atomic update failure on pipe C (start=13132 end=13133) time 5 us, min 1073, max 1079, scanline start 1076, end 1079 I’m was using a current build from April 27, I switched back to NetBSD 8 to see if the issue is present there (as I’ve never used X on these machines before.) The issue does not occur in NetBSD 8. Thanks in advance, Travis [1] https://us-east.manta.joyent.com/tpaul/public/netbsd/X11/1.jpg [2] https://us-east.manta.joyent.com/tpaul/public/netbsd/X11/2.jpg [3] https://us-east.manta.joyent.com/tpaul/public/netbsd/X11/3.jpg
Re: Funky Display Output
Update: Using "modesetting" did clear up the issue. Keeping the Driver as "intel" and setting "TearFree" to "true" with "AccelMethod" set to "sna" also worked. Not sure how this email group looks on adding links to emails. I found some info on TearFree and sna on askubuntu and the Archlinux wiki. Here's a good resource for explaining a little about TearFree and sna. (archlinux wiki, search intel_graphics#Tearing) On 4/12/19, 5:08 AM, "Benny Siegert" wrote: I don't think this is related to xf86. I started seeing these issues when upgrading my kernel to the latest version while keeping all the userland as is. So I assume it is related to an updated Intel kernel driver. I haven't tried but perhaps the "NoTear" option to the Xorg intel driver would help? On Thu, Apr 11, 2019 at 11:39 PM matthew green wrote: > > i am fairly sure the new display glitches you are seeing are > related to the newer xf86-video-intel driver. > > can people who are seeing issues not related to GL/Mesa try > forcing the "modesetting" driver instead? see if that makes > things go away? i am probably going to revert the driver in > -current until someone fixes the new one, and perhaps make > the new one optional since it works better for me on > kabylake, but it would be nice to know if modesetting helps > fix some problems. > > thanks. > > > .mrg. -- Benny
Funky Display Output
tch] *ERROR* Failed to fetch GuC firmware from i915/kbl_guc_ver9_14.bin (error -2) [ 8.008648] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem.c:5417)i915_gem_init_hw] *ERROR* Failed to initialize GuC, error -5 (ignored) Ron Georgia “90% of my problems are due to ignorance, the other 10% is because I just don’t know any better.”
npm successfully installed -- via hacking install.sh
I tried to install npm via pkgsrc but got the error listed below and a 0B node.core file. PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/usr/pkgsrc/lang/npm/work/.cwrapper/config node bin/npm-cli.js install /usr/pkgsrc/lang/npm/work/marked-0.6.0 --no-global --no-timing --no-save [1] Segmentation fault /usr/bin/env USE...ng /usr/pkgsrc/lang/npm/work/.home/.npm/_locks/staging-b2d0450 *** Error code 139 Stop. make[1]: stopped in /usr/pkgsrc/lang/npm *** Error code 1 Stop. make: stopped in /usr/pkgsrc/lang/npm The first mention of a npm build issue is here: http://mail-index.netbsd.org/pkgsrc-users/2018/10/16/msg027550.html BUT! I did get it to install, although I get the same empty node.core file when I use npm. Here what I did. 1. cd /usr/pkgsrc/lang/npm 2. sudo make configure. 3. cd /usr/pkgsrc/lang/npm/work/cli-6.8.0/scripts 4. There you find install.sh. Executing that fails because it does some tar commands with invalid (UNIX) flags. 5. Below is the diff from my hacking around to make it work, which it did. ~/nowhere> diff install.sh nb_npm_install.sh 11c11 < # https://www.gnu.org/s/hello/manual/autoconf/Portable-Shell.html --- > # http://www.gnu.org/s/hello/manual/autoconf/Portable-Shell.html 21c21,30 < curl -f -L -s https://www.npmjs.org/install.sh > npm-install-$$.sh --- > # curl -f -L -s https://www.npmjs.org/install.sh > npm-install.sh > # ret=$? > # if [ $ret -eq 0 ]; then > # (exit 0) > # else > # rm npm-install.sh > # echo "Failed to download script" >&2 > # exit $ret > # fi > sh npm-install.sh 23,32c32 < if [ $ret -eq 0 ]; then < (exit 0) < else < rm npm-install-$$.sh < echo "Failed to download script" >&2 < exit $ret < fi < sh npm-install-$$.sh < ret=$? < rm npm-install-$$.sh --- > rm npm-install.sh 102c102 < $tar --version --- > # $tar --version Ron Georgia “90% of my problems are due to ignorance, the other 10% is because I just don’t know any better.”
Re: current fails to boot on VirtualBox
Same here. Fails to boot on both my workstation and laptop, fell back to 8.99.33 On 2/16/19, 3:15 PM, "Arto Huusko" wrote: Hello, it seems latest -current amd64 kernel no longer boots on VirtualBox. Booting GENERIC from http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/201902161050Z/amd64/binary/kernel/ stops after detecting CPUs and acpiacad0. After CPU detection there is ERROR: 3591 cycle TSC drift observed. CPU is AMD Ryzen 5 1500X. I can break into ddb, bt command on all CPUs shows they are in idle_loop. It makes no difference if I configure only one CPU for VirtualBox. bt for cpu 0: ddb backtrace --- interrupt x86_stihlt acpicpu_cstate_idle_enter acpicpu_cstate_idle idle_loop bt for cpu1: x86_stihlt acpicpu_cstate_idle_enter acpicpu_cstate_idle cpu_hatch md_root_setconf Booting with -2 switch (no ACPI) gets a bit further, but then has other problems detecting devices. However a few days old GENERIC from http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/201902131540Z/amd64/binary/kernel/ does boot successfully. (But vioif is broken again, ifconfig just hangs) A lot older kernel (8.99.18, I don't have the exact date) works without problems. Arto
Installing on MacBook Air 2010 - hangs on install boot
I am trying to install NetBSD-current on my 2010 Mac book Air; however, it
hangs on booting from USB drive. Of course, I see the USB EFI drive by holding
down the option key after power up. If I select the normal boot it hangs with
this being the last printed line:
[1.0836119]pci0 at mainbus0: configuration mode 1
When selecting NO ACPI or NO ACPI, no SMP the last printed line before hanging
is this:
[1.0578911] root device:
There is a whole slew of nouveau0 errors, like
pci:init failed -22
init failed -22
kern error: nouveau: DRM : init failed -22
nouveau0: unable to attach DRM
I did burn a CD and booted NO ACPI and NO ACPI, no SMP
It ended with a db{0} prompt. The keyboard was locked.
The probed video card is NVIDIA MCP89
Ron Georgia
“90% of my problems are due to ignorance, the other 10% is because I just don’t
know any better.”
Codelite from source fails
I am trying to build codelite from source but get the failure listed below. However, clang-c/Index.h is present in /usr/pkg/include/clang-c $ ls -l /usr/pkg/include/clang-c/Index.h -rw-r--r-- 1 root wheel 214020 Jul 30 2018 /usr/pkg/include/clang-c/Index.h If I change clangpch_cache.h line 35 from #include To #include "/usr/pkg/include/clang-c/Index.h" The process does move forward to the next reference to Noob question: is there an environment or make variable that I can set that points the "/usr/pkg/include/" directory? CLANG_INCLUDE I did read through the makefile and the make man page. == MORE INFO == $ gcc --version gcc (nb4 20181109) 6.5.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ clang --version clang version 7.0.1 (tags/RELEASE_701/final) Target: x86_64-unknown-netbsd8.99 Thread model: posix InstalledDir: /usr/pkg/bin $ uname -a NetBSD clement.ronverbs.dev 8.99.33 NetBSD 8.99.33 (GENERIC) #0: Thu Jan 31 22:07:46 UTC 2019 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 ERROR CODE: [ 61%] Building CXX object LiteEditor/CMakeFiles/codelite.dir/ClangOutputTab.cpp.o In file included from /usr/pkgsrc/editors/codelite/work/codelite-9.1/LiteEditor/clang_driver.h:34:0, from /usr/pkgsrc/editors/codelite/work/codelite-9.1/LiteEditor/clang_code_completion.h:35, from /usr/pkgsrc/editors/codelite/work/codelite-9.1/LiteEditor/ClangOutputTab.cpp:8: /usr/pkgsrc/editors/codelite/work/codelite-9.1/LiteEditor/clangpch_cache.h:35:27: fatal error: clang-c/Index.h: No such file or directory #include ^ compilation terminated. *** Error code 1 Stop. make[2]: stopped in /usr/pkgsrc/editors/codelite/work/codelite-9.1 *** Error code 1 Stop. make[1]: stopped in /usr/pkgsrc/editors/codelite/work/codelite-9.1 *** Error code 1 Stop. make: stopped in /usr/pkgsrc/editors/codelite/work/codelite-9.1 *** Error code 1 Stop. make[1]: stopped in /usr/pkgsrc/editors/codelite *** Error code 1 Stop. make: stopped in /usr/pkgsrc/editors/codelite Ron Georgia “90% of my problems are due to ignorance, the other 10% is because I just don’t know any better.”
Re: Install of 8.99.30 libcrypto.so.12 not found
Here is what I found and how I "solved" my missing lib issue.
If during the installation process you select the option to install pkgin,
pkgin does get installed; however, when it tries to pull pkg_summary.tgz it
fails with the now infamous '/usr/pkg/bin/pkgin: Shared object
"libcrypto.so.12" not found error message.' On my second attempt to install I
skipped that step. Once I logged in as root I was able to ftp base.tgz and
pkg_summary.tgz. As a side note, I had to use ftp since wget, curl and fetch
all depend on libcrypto.so.12. I knew to grab those files based on Manuel
Bouyer's timely respond to my first "cry for help." I unpacked both files.
Since I am nigh unto a noob I searched the pkg_summary in order to find where
libcrypto.so.12 should live. BTW, the other missing lib file was libssl.so.12.
Here is what I did:
$ cat pkg_summary| grep -i requires | grep libcrypto.so.12 | sort -u
REQUIRES=/usr/lib/libcrypto.so.12
$ cat pkg_summary| grep -i requires | grep libssl.so.12 | sort -u
REQUIRES=/usr/lib/libssl.so.12
I already unpacked base.tgz, so I simply copied usr/lib/libcrypto.so.12 to /
usr/lib/libcrypto.so.12. BAM! My world just got a little brighter!
Now I can continue building my NetBSD desktop.
On 1/18/19, 7:35 PM, "Chavdar Ivanov" wrote:
I had the same earlier. I added pkg_install using /usr/sbin/pkg_add,
this brought the necessary libraries for pkgin, which I then installed
and setup. Obviously it didn't work from the installation cd.
On Fri, 18 Jan 2019 at 01:02, Ron Georgia wrote:
>
> I am installing NetBSD-8.99.03-amd64. When I try to add pkgin from the
install screen I get the message-
> /usr/pkg/bin/pkgin: Shared object "libcrypto.so.12" not found.
>
> Is there a work around for this? I suppose I could resort to pkg_add, but
pkgin is so much nicer. Plus, I am not sure what else depends on
libcrypto.so.12. Your thoughts?
>
>
> Ron Georgia
> “90% of my problems are due to ignorance, the other 10% is because I just
don’t know any better.”
>
>
>
--
Curl, fetch, wget Shared object "libssl.so.12" not found
I installed curl, fetch and wget using pkg_add, since pkgin is missing libcrypto.so.12, but when I try to use any of those I get this error: Shared object "libssl.so.12" not found $ uname -a NetBSD clement.ronverbs.dev 8.99.30 NetBSD 8.99.30 (GENERIC) #0: Tue Jan 15 01:23:49 UTC 2019 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 At the risk of sounding ignorant (see tag line) I am using ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.0/All since ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.99/All does not exist. Is that alright? Ron Georgia “90% of my problems are due to ignorance, the other 10% is because I just don’t know any better.”
Install of 8.99.30 libcrypto.so.12 not found
I am installing NetBSD-8.99.03-amd64. When I try to add pkgin from the install screen I get the message- /usr/pkg/bin/pkgin: Shared object "libcrypto.so.12" not found. Is there a work around for this? I suppose I could resort to pkg_add, but pkgin is so much nicer. Plus, I am not sure what else depends on libcrypto.so.12. Your thoughts? Ron Georgia “90% of my problems are due to ignorance, the other 10% is because I just don’t know any better.”
Install Current - Hostname not set
All, Just an FYI. I’ve installed Netbsd-8 on two different machines and one VM and in all cases the hostname did not make into the rc.conf file. -- Ron Georgia “Fail fast, fail often.”
