Re: ProtectLi w/ OpenBSD
On 1/3/24 12:17, Stuart Henderson wrote: On 2024-01-03, Kenneth Hendrickson wrote: Is there any newer information than this: https://OpenBsdMailBox.blogspot.com/2023/05/protectli-vp2420-with-dasharo.html That is exactly how a boot looks if you are on a device with serial console and don't tell the boot loader to use the serial console. stty com0 set tty com0 boot If the activation of the serial console did't work, maybe it helps to switch to bios/seabios mode [1] or to disable some large device drivers e.g. amdgpu [2] [1] https://marc.info/?l=openbsd-misc=159023150810596=2 [2] https://marc.info/?l=openbsd-misc=159276382718317=2
Re: netcup.eu arm64 (kvm, Ampere Altra), bsd.rd hangup
On 12/28/23 12:30, Michael Hekeler wrote: I try to install OpenBSD on netcup ARM, too... I disabled the pluart driver in the ramdisk kernel (on a other machine with config -e -f /bsd.rd and copied the ramdisk kernel over to the nectup server) and got access the the installation script. How did you disable pluart driver? I installed OpenBSD on a Hetzner ARM64 system (CAX11) and modified the ramdisk with config -e -f /bsd.rd disable pluart quit The modification should also be possible on any other ARM64 system (e.g. Raspberry Pi 4). Then I copied the modified bsd.rd and https://cdn.openbsd.org/pub/OpenBSD/snapshots/arm64/BOOTAA64.EFI to the EFI partition (directly under /boot/efi) on the Netcup server. After that I started the OpenBSD BOOTAA64.EFI directly from the TianoCore UEFI. Could you provide more info, or share the bsd.rd? You'll find my modified bsd.rd here: https://download.fusion-zone.net/
Re: Another kernel fault incident on a Vultr OpenBSD VM
I also can recommend openbsd.amsterdam :) My OpenBSD VM at netcup.de (KVM) also runs without any issues for over year On 4/18/22 00:00, Alexis wrote: Mihai Popescu writes: It lowers my confidence in Vultr as a reliable OpenBSD host. Very well, it will match the confidence of running OpenBSD on a virtual machine. Not sure exactly what you mean by that, but i can say i'm very happy with my OpenBSD VM provided by openbsd.amsterdam. Alexis.
Re: Either intel nor glamor drivers do not work for Samsung NC215S
On 2/3/22 21:33, Sergey Andrianov wrote: Yes, it did not help. Just noticed that in README for xf86-video-intel it's written: PineView-M (Atom N400 series) but mine is N570. The N455 and N570 should have the same 3150 GFX, see https://news.samsung.com/global/samsung-electronics-launches-eco-friendly-solar-powered-rechargeable-netbook-nc-215s https://ark.intel.com/content/www/us/en/ark/compare.html?productIds=49491,55637
Re: Either intel nor glamor drivers do not work for Samsung NC215S
On 2/3/22 17:59, Sergey Andrianov wrote: [ 1833.653] (--) Using wscons driver on /dev/ttyC4 [ 1833.671] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Permission denied) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details Hi, have you tried to set machdep.allowaperture=1 ? Sven
Re: Supported 4K video cards
On 11/24/21 19:06, Allan Streib wrote: Recently a 4K monitor became available at work, it appears to support 3840x2160 at 60Hz only. My video card (ATI Radeon HD 5870) will do that but only at 30Hz. Anyone know of a supported card that will do 3840x2160 60Hz on DisplayPort? Allan I've a Radeon RX 5700 XT which also works under OpenBSD. I only have a single monitor setup. Sven
Question to usbdevs and dmesg
Hi list, I've attached an XBOX 360 controller to my system. The controller gets detected as: usbdev: addr 02: 045e:028e \M-)Microsoft Corporation, Controller dmesg: uhidev1 at uhub1 port 1 configuration 1 interface 0 "\M-)Microsoft Corporation Controller" rev 2.00/1.14 addr 2 ugen1 at uhub1 port 1 configuration 1 "\M-)Microsoft Corporation Controller" rev 2.00/1.14 addr 2 Do you have an idea why the controller is detected as "\M-)Microsoft Corporation, Controller" and not as "XBOX 360 Controller" as it is defined in /usr/src/sys/dev/usb/usbdevs "vendor MICROSOFT 0x045e Microsoft" "product MICROSOFT XBOX360_CONTROLLER 0x028e XBOX 360 Controller" Thanks, Sven
Re: latest snapshots, Xorg, wrong dpi, i3wm
Hi, here is the answer from Matthieu https://marc.info/?l=openbsd-tech=163674121630769=2 "If your fonts have chanded sizes too much after the last snapshot update, you can add xrandr --dpi 96 in your ~/.xsession (or ~/.xinitrc) file to set the resolution manually to the previous default. You can also fiddle with the X resources (~/.Xresources ) to fix font sizes in invidual applications." Sven On 11/12/21 5:16 PM, Sven Wolf wrote: Hi list, I've upgraded three computers to the current snapshot OpenBSD 7.0-current (GENERIC.MP) #90: Thu Nov 11 22:43:05 MST 2021 I use i3 as window manager. On my Intel based systems the dpi changed X230 (inteldrm,i5-3320/HD4000) from 96 to 125 L14 (inteldrm,i5-10210U/UHD) from 96 to 157 On my AMD based system the dpi changed amdgpu,RX 5700XT from 96 to 94 In the Xorg logfile there are the entries: old snapshot modeset(0): DPI set to (96, 96) current snapshot modeset(0): DPI set to (157, 158) old snapshot AMDGPU(0): DPI set to (96, 96) current snapshot AMDGPU(0): DPI set to (94, 94) As far as I've checked this problem has been introduced between the snapshots 2021-11-09 and 2021-11-11. As a workaround I now define Xft.dpi: 96 in my .Xdefaults An pkg update doesn't solve the problem. Maybe it's related to Update xorgprotos to 2021.5 https://marc.info/?l=openbsd-cvs=163662095531059=2 Sven
latest snapshots, Xorg, wrong dpi, i3wm
Hi list, I've upgraded three computers to the current snapshot OpenBSD 7.0-current (GENERIC.MP) #90: Thu Nov 11 22:43:05 MST 2021 I use i3 as window manager. On my Intel based systems the dpi changed X230 (inteldrm,i5-3320/HD4000) from 96 to 125 L14 (inteldrm,i5-10210U/UHD) from 96 to 157 On my AMD based system the dpi changed amdgpu,RX 5700XT from 96 to 94 In the Xorg logfile there are the entries: old snapshotmodeset(0): DPI set to (96, 96) current snapshotmodeset(0): DPI set to (157, 158) old snapshotAMDGPU(0): DPI set to (96, 96) current snapshotAMDGPU(0): DPI set to (94, 94) As far as I've checked this problem has been introduced between the snapshots 2021-11-09 and 2021-11-11. As a workaround I now define Xft.dpi: 96 in my .Xdefaults An pkg update doesn't solve the problem. Maybe it's related to Update xorgprotos to 2021.5 https://marc.info/?l=openbsd-cvs=163662095531059=2 Sven
Re: rsync over ssh, slow speed (700 kB/s) on x230
Hi, over cable/lan everything is fine. On my router (OpenWRT) I detected a speed/bandwidth drop from 72 Mbit/s down to 6 Mbit/s when I start the copy over wireless. That's strange, because under Linux I don't see this issue. Lesson learned: use the cable :) Best regards, Sven On 2/2/21 11:04 PM, Sven Wolf wrote: Hi, on my x230 the rsync over ssh speed is extremly slow - about 700 kB/s over wireless. I don't see a performance issue on the source and target systems. When I reboot to Linux the speed is acceptable - about 12 mB/s over wireless. The compression an ciphers parameters don't have impact to the speed. Interesting is that under OpenBSD in debug mode the lines get printed slowly. 692.05kB/s 0:17:16 debug2: channel 0: rcvd adjust 32768 Under Linux the debug lines scroll really fast over the screen debug2: channel 0: rcvd adjust 114688 Do you have any ideas how I can solve the problem? ulimit, openfiles limit etc. don't show any problems. Thanks and best regards, Sven
rsync over ssh, slow speed (700 kB/s) on x230
Hi, on my x230 the rsync over ssh speed is extremly slow - about 700 kB/s over wireless. I don't see a performance issue on the source and target systems. When I reboot to Linux the speed is acceptable - about 12 mB/s over wireless. The compression an ciphers parameters don't have impact to the speed. Interesting is that under OpenBSD in debug mode the lines get printed slowly. 692.05kB/s0:17:16 debug2: channel 0: rcvd adjust 32768 Under Linux the debug lines scroll really fast over the screen debug2: channel 0: rcvd adjust 114688 Do you have any ideas how I can solve the problem? ulimit, openfiles limit etc. don't show any problems. Thanks and best regards, Sven
Re: PayPal pool for developer M1 Mac mini for OpenBSD port
Hi, the guys at corellium can boot the Linux kernel and also Ubuntu Linux on a arm based mac mini. Some details can be found at: https://corellium.com/blog/linux-m1 https://github.com/corellium https://asahilinux.org/ Some details sound strange: "...If that wasn't enough, Apple designed their own interrupt controller, the Apple Interrupt Controller (AIC), not compatible with either of the major ARM GIC standards. And not only that: the timer interrupts - normally connected to a regular per-CPU interrupt on ARM - are instead routed to the FIQ, an abstruse architectural feature, seen more frequently in the old 32-bit ARM days. Naturally, Linux kernel did not support delivering any interrupts via the FIQ path, so we had to add that..." Best regards, Sven On 12/3/20 8:35 AM, Otto Moerbeek wrote: On Thu, Dec 03, 2020 at 03:18:54AM +0200, Mihai Popescu wrote: I have only good wishes for the project, but I still don't get one thing: why do some people start to behave oddly whenever Apple comes into discussion. They are doing a proprietary thing, closed as hell, no documentation and so on. Why is this impulse to write code for such a thing. Just asking ... It's a new interesting ARM platform with very good performance. Yes, it is closed but it's also kind of a nice challenge to overcome that hurdle. So mixed feelings about that part. -Otto
Re: Snapshot crash on boot, "entry point at: 0x1001000" (Intel Gemini Lake)
Hi, thanks to the fix from Mark, see https://marc.info/?l=openbsd-tech=160383074317608=2 the problem is solved for my machine. Best regards, Sven On 10/10/20 11:56 AM, Sven Wolf wrote: Hi, on my Lenovo V130 I've to build a custom kernel without radeondrm and amdgpu. https://marc.info/?l=openbsd-misc=159276382718317=2 The modified efiboot.c, see https://marc.info/?l=openbsd-misc=159401011632149=2, doesnt work on this machine. Best regards, Sven On 10/9/20 9:32 PM, Kastus Shchuka wrote: On Fri, Oct 09, 2020 at 03:37:37PM +0400, Michel von Behr wrote: Hi all, I'm trying to run snapshot on a Chuwi Lapbook laptop (Intel Gemini Lake), but I get stuck at boot time with the message "entry point at: 0x1001000". Based on previous discussions [1] it looks like the problem is with BOOTX64.EFI For now I'll be running -stable, but I would like to follow -current. Is there a way to run -current with an old version of BOOTX64.EFI for example? (i.e., the only alternatives I'm seeing is either 1) compiling a GENERIC kernel with the older version of BOOTX64.EFI src, or 2) (try to) compile a custom/smaller kernel to avoid the issue). [1] https://marc.info/?l=openbsd-misc=159147446008114=2 Any pointing to the right direction is welcome. I had the same problem with EFI on ASRock J4105M system, essentially failing to boot a kernel larger than certain size. I posted my solution here: https://marc.info/?l=openbsd-misc=159401011632149=2 I guess the patch requires more testing before asking for it to be committed. Thanks, Kastus
Re: OpenBSD 6.8 release boot stuck on Intel NUC NUC7PJYH
Hi Fabian, the today posted patch from Marc Kettenis works on my system - https://marc.info/?l=openbsd-tech=160383074317608=2 For test purposes you can download my build BOOTX64.EFI from http://mailinglist.fusion-zone.net/BOOTX64.EFI Just replace it in your EFI partition. Please make a backup of your BOOTX64.efi or download the original BOOTX64.EFI from https://cdn.openbsd.org/pub/OpenBSD/6.7/amd64/ (in case of an error) again. Best regards, Sven On 10/27/20 9:30 PM, Fabian wrote: Hello misc, I recently upgraded from OpenBSD 6.7 release to the new 6.8 release on an Intel NUC Kit NUC7PJYH mini server. That machine ran OpenBSD without problems since version 6.5 and has been running 6.7 release (including all sypatches) until a day or so. The machine boots via UEFI and the disk is GPT partitioned. See below for a dmesg from OpenBSD 6.7. However, after I performed an interactive upgrade to OpenBSD 6.8 release, the machine remains stuck during boot after displaying the message "entry point at: 0x1001000", and nothing else happens. I have to long-press the power button to force it to shut down. I spent some time researching the issue, and I know the following so far: * The machine boots exclusively via UEFI. There is no legacy boot option available, as far as I can see, that could act as a temporary workaround. * The new boot loader version from OpenBSD 6.8 that is installed now on disk does not seem to be the problem. I can do various things in the boot menu, including changing the terminal configuration and all the other usual things. So boot loader stages 1 and 2 load fine. During my trials to debug the problem, I realised that I had an old OpenBSD 6.7 kernel file on disk in the form of a 'bsd.booted' file. Surprisingly, that kernel booted without problems using the new boot loader and with the latest release binaries. Of course, the booted system was not 100 per cent usable, because of the mismatch between kernel and binaries. * I had a look at the output of 'machine memory' in the boot menu, but could not see any obvious problems there. * The OpenBSD 6.8 ram disk kernel boots fine, but neither do the installed 6.8 single or multiprocessor kernels. I tried both. * I noticed in the dmesg from the OpenBSD 6.8 ram disk kernel that the EFI frame buffer (efifb) is now recognised, which was not the case before. This probably has nothing to do with the boot problem, but I wanted to mention it for completeness. * There have been various reports of similar boot problems recently. Here are some examples: https://www.reddit.com/r/openbsd/comments/je7c8r/stuck_at_boot_after_upgrading_to_68/ https://andinus.nand.sh/writings/2020/OpenBSD-6.8-EFI-boot-failure.html https://marc.info/?l=openbsd-misc=160376706629651 https://marc.info/?l=openbsd-misc=160224393101534 https://marc.info/?l=openbsd-misc=159147446008114 * I saw the patches posted by Kastus Shchuka and Marc Kettenis, but I haven't had time to build a custom release yet to test them. I want to avoid rolling back to version 6.7 and figure out what the problem is. What else can I try? Cheers. Fabian OpenBSD 6.7 (GENERIC.MP) #2: Thu Jun 4 09:55:08 MDT 2020 r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8166744064 (7788MB) avail mem = 7906615296 (7540MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.1 @ 0x6bf67000 (49 entries) bios0: vendor Intel Corp. version "JYGLKCPX.86A.0055.2020.0603.1745" date 06/03/2020 bios0: Intel Corporation NUC7PJYH acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI BGRT TPM2 DMAR WDAT WSMT acpi0: wakeup devices SIO1(S3) HDAS(S3) XHC_(S4) XDCI(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) Silver J5005 CPU @ 1.50GHz, 1496.43 MHz, 06-7a-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,UMIP,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 19MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Pentium(R) Silver J5005
Re: snapshot boot fails with error "entry point at 0x1001000"
Hi Mark, on my Lenovo V130 the patch works. Now I'm able to boot the current kernel again, without the need to remove the radeon and amdgpu driver (https://marc.info/?l=openbsd-misc=159276382718317=2) Thanks and best regards, Sven On 10/27/20 1:40 PM, Mark Kettenis wrote: Hi Kastus, Please don't have technical discussions on misc@; some developers, like me, only read it sporadically. The tech@ list is a much better place. The problem with your approach is that you allocate memory at a fixed address, and we can't be sure that memory is available. We may have to extend the amount of memory we allocate such that larger kernels fit. The diff below bumps it from 32MB to 64MB. Does this work for you? Index: arch/amd64/stand/efiboot/efiboot.c === RCS file: /cvs/src/sys/arch/amd64/stand/efiboot/efiboot.c,v retrieving revision 1.35 diff -u -p -r1.35 efiboot.c --- arch/amd64/stand/efiboot/efiboot.c 22 Mar 2020 14:59:11 - 1.35 +++ arch/amd64/stand/efiboot/efiboot.c 27 Oct 2020 12:36:45 - @@ -39,7 +39,7 @@ #include "eficall.h" #include "run_i386.h" -#define KERN_LOADSPACE_SIZE (32 * 1024 * 1024) +#defineKERN_LOADSPACE_SIZE (64 * 1024 * 1024) EFI_SYSTEM_TABLE *ST; EFI_BOOT_SERVICES *BS;
Re: Snapshot crash on boot, "entry point at: 0x1001000" (Intel Gemini Lake)
Hi, on my Lenovo V130 I've to build a custom kernel without radeondrm and amdgpu. https://marc.info/?l=openbsd-misc=159276382718317=2 The modified efiboot.c, see https://marc.info/?l=openbsd-misc=159401011632149=2, doesnt work on this machine. Best regards, Sven On 10/9/20 9:32 PM, Kastus Shchuka wrote: On Fri, Oct 09, 2020 at 03:37:37PM +0400, Michel von Behr wrote: Hi all, I'm trying to run snapshot on a Chuwi Lapbook laptop (Intel Gemini Lake), but I get stuck at boot time with the message "entry point at: 0x1001000". Based on previous discussions [1] it looks like the problem is with BOOTX64.EFI For now I'll be running -stable, but I would like to follow -current. Is there a way to run -current with an old version of BOOTX64.EFI for example? (i.e., the only alternatives I'm seeing is either 1) compiling a GENERIC kernel with the older version of BOOTX64.EFI src, or 2) (try to) compile a custom/smaller kernel to avoid the issue). [1] https://marc.info/?l=openbsd-misc=159147446008114=2 Any pointing to the right direction is welcome. I had the same problem with EFI on ASRock J4105M system, essentially failing to boot a kernel larger than certain size. I posted my solution here: https://marc.info/?l=openbsd-misc=159401011632149=2 I guess the patch requires more testing before asking for it to be committed. Thanks, Kastus
Re: snapshot boot fails with error "entry point at 0x1001000"
Hi guys,
with the patch the kernel loads and doesn't stop at "entry point at
0x1001000". But the kernel stops with a "Stopped at
gfx_v9_0_wait_reg_mem+0x307: int $3"
So for my machine the patch is the right direction but not the solution
:( I've tried the boot with the current snapshot kernel.
Thanks and best regards,
Sven
On 7/6/20 6:32 AM, Kastus Shchuka wrote:
On Sat, Jul 04, 2020 at 11:09:54AM +, Michael Baehr wrote:
Kastus Shchuka wrote:
“I installed 2020-07-03 snapshot on ASRock J4105M system and I am not able to
boot it.
Boot stops at the line
entry point at 0x1001000
If I try bsd.rd kernel, it boots just fine. After this failure with snapshot I
installed 6.7-release, and it boots without any issues.”
I've experienced something similar, including the sensitivity to kernel size.
As best I can observe, the EFI bootloader is being handed a different block of
RAM than where the kernel is actually loaded (which is at a fixed address
defined in boot.c). Which block of memory gets returned, and whether boot
fails, seems to be dependent on the particular UEFI ROM/chipset. In my case,
debugging over serial, I observe a page fault while the kernel is still being
loaded into RAM.
“Are there any other solutions than compiling a custom smaller kernel?”
Patching efiboot.c as follows and recompiling bootia32/bootx64 resolved it for
me:
--- a/sys/arch/amd64/stand/efiboot/efiboot.c
+++ b/sys/arch/amd64/stand/efiboot/efiboot.c
@@ -303,9 +303,9 @@ efi_memprobe(void)
bios_memmap_t *bm;
EFI_STATUS status;
EFI_PHYSICAL_ADDRESS
-addr = 0x1000ULL; /* Below 256MB */
+addr = 0x100;
- status = EFI_CALL(BS->AllocatePages, AllocateMaxAddress, EfiLoaderData,
+ status = EFI_CALL(BS->AllocatePages, AllocateAddress, EfiLoaderData,
EFI_SIZE_TO_PAGES(KERN_LOADSPACE_SIZE), );
if (status != EFI_SUCCESS)
panic("BS->AllocatePages()");
Let me know if that helps. I can't guarantee that this is actually what is
causing your issue but it worked for me.
I tried this patch and was able to boot kernel from snapshot 2007-07-03 with
recompiled BOOTX64.EFI.
It fixes the problem with EFI memory mapping on ASRock J4105M motherboard.
I wonder what would it take for the patch to be accepted in -current?
Thanks,
Kastus
Re: Lenovo V130, boot failed with error "entry point at 0x1001000"
Hi, after hours of kernel compilations I think I've found the cause for the hang with the message "entry point at 0x1001000". It seems that the kernel is to large to boot. Kernels (/bsd) larger than about 18 MB won't boot on this machine. The last successful kernel compilation and boot was with a cvs checkout from 2020-06-27. All kernel builds after this date don't boot. First I thought it was the efifb change http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/amd64/amd64/efifb.c?f=h After that I thought it was the umstc and acpihid device driver. But that not true :) I can run a current kernel when I reduce the kernel size by disabling the amdgpu and radeondrm devices in the GENERIC configuration file. I like to stay on -current by running regularly sysupgrade. But I don't want to recompile the kernel to reduce the kernel size. Also disabling the amdgpu and radeondrm devices via boot_config doesn't work. Do you have an idea if its possible to specify the memory areas which the loader should choose to load the kernel, e.g. boot> machine memory =M ? My machine memory looks like this: Region 0: type 1 at 0x0 for 352KB Region 1: type 2 at 0x58000 for 4KB Region 2: type 1 at 0x59000 for 180KB Region 3: type 2 at 0x86000 for 488KB Region 4: type 1 at 0x10 for 261120KB ... The kernel doesn't boot/hang at "entry point 0x100100" with following (I think memory mappings): booting sr0a:bsd: 14447944+3175440+34+0+... The kernel boots successfully Default 6.7 MP kernel booting sr0a:bsd: 12952904+2753544+331808+0+... and also my custom kernel without radeondrm und amdgpu booting sr0a:bsd: 10409288+2253840+306784+0+... Thanks and best regards, Sven On 6/24/20 6:02 PM, Sven Wolf wrote: Hi, I did some more tests/new installations on this machine. A clean reinstallation of 6.7 release boots without any problems with the loaders 3.50 (release 6.7) and also 3.52 (snapshot 2020-06-23). Kernel 6.7 GENERIC.MP#182 build time 2020-05-07 Also after an syspatch the kernel 6.7 GENERIC.MP#2 build time 2020-06-04 boots without any problems with the loaders 3.50 and 3.52 (snapshot 2020-06-23). So in my opinion the problem is the kernel. I think between 2020-06-04 and 2020-06-23 the where some changes which prevents that the 6.7 and 6.7/current loader boots the kernel on this and maybe on some other Lenovo (e.g. X1 Gen7) machines. The loader always show "entry point at 0x1001000" for some milliseconds, also when the kernel 6.7 gets loaded successfully. Maybe we'll find the changes for the kernel, which are responsible for this error. An another point for the kernel issue is in my opinion that the current RAMDISK kernel (from the latest snapshot) boots also without any problems. I'll do some more testing with a current kernel. Best regards, Sven On 6/23/20 10:20 PM, Matt Kunkel wrote: Here is the offending patch. -current boots fine with it removed: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/amd64/stand/efiboot/exec_i386.c.diff?r1=1.2=1.3=h Appears bootx64.efi is carrying some board specific workaround for HP / Computrace that breaks many others, including tianocore. Guess I'll submit a patch to reverse it since I don't have an Elitebook to test with? As a workaround, mount the efi partition and copy in boot64.efi from 6.6. -Matt Kunkel June 23, 2020 2:16 PM, "Sven Wolf" wrote: Hi, also after the new installation of the current snapshot the system stops with "entry point at 0x1001000". It's interesting, that a installation via bsd.rd is possible. But after that the system doesn't boot via bsd.mp/bsd.sp. Best regards, Sven On 6/21/20 8:55 PM, Sven Wolf wrote: Hi, the update of the loader didn't help. I've updated the bootx64.efi from 3.48 to 3.52. But the current kernel > doesn't load. I'll try a re-installation. Maybe @Otto can explain why the start of bsd.rd is possible and the > start of bsd.sp/bsd.mp is not possible. Maybe I can build a custom kernel. Best regards, Sven On 6/21/20 8:33 PM, Sven Wolf wrote: Hi, I found the same issue in a thread some weeks ago. https://marc.info/?l=openbsd-misc=159039904132502=2 I'll test an reinstall/older loader. Boot from mbr isn't an option :( Best regards, Sven On 6/21/20 8:20 PM, Sven Wolf wrote: Hi, I've upgraded my Lenovo V130 from snapshot 6.6 (April 2020) to the >>> snapshot from 2020-06-20. The boot via boot.rd is always possible. But when I load bsd.sp or bsd.rd the boot process stops with the >>> error "entry point 0x1001000". Do you have an idea how I can fix this >>> error? In the past I did't have any problem with openbsd on this machine. I'll try tomorrow the next snapshot. Thanks and best regards, Sven
Re: Lenovo V130, boot failed with error "entry point at 0x1001000"
Hi, I did some more tests/new installations on this machine. A clean reinstallation of 6.7 release boots without any problems with the loaders 3.50 (release 6.7) and also 3.52 (snapshot 2020-06-23). Kernel 6.7 GENERIC.MP#182 build time 2020-05-07 Also after an syspatch the kernel 6.7 GENERIC.MP#2 build time 2020-06-04 boots without any problems with the loaders 3.50 and 3.52 (snapshot 2020-06-23). So in my opinion the problem is the kernel. I think between 2020-06-04 and 2020-06-23 the where some changes which prevents that the 6.7 and 6.7/current loader boots the kernel on this and maybe on some other Lenovo (e.g. X1 Gen7) machines. The loader always show "entry point at 0x1001000" for some milliseconds, also when the kernel 6.7 gets loaded successfully. Maybe we'll find the changes for the kernel, which are responsible for this error. An another point for the kernel issue is in my opinion that the current RAMDISK kernel (from the latest snapshot) boots also without any problems. I'll do some more testing with a current kernel. Best regards, Sven On 6/23/20 10:20 PM, Matt Kunkel wrote: Here is the offending patch. -current boots fine with it removed: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/amd64/stand/efiboot/exec_i386.c.diff?r1=1.2=1.3=h Appears bootx64.efi is carrying some board specific workaround for HP / Computrace that breaks many others, including tianocore. Guess I'll submit a patch to reverse it since I don't have an Elitebook to test with? As a workaround, mount the efi partition and copy in boot64.efi from 6.6. -Matt Kunkel June 23, 2020 2:16 PM, "Sven Wolf" wrote: Hi, also after the new installation of the current snapshot the system stops with "entry point at 0x1001000". It's interesting, that a installation via bsd.rd is possible. But after that the system doesn't boot via bsd.mp/bsd.sp. Best regards, Sven On 6/21/20 8:55 PM, Sven Wolf wrote: Hi, the update of the loader didn't help. I've updated the bootx64.efi from 3.48 to 3.52. But the current kernel > doesn't load. I'll try a re-installation. Maybe @Otto can explain why the start of bsd.rd is possible and the > start of bsd.sp/bsd.mp is not possible. Maybe I can build a custom kernel. Best regards, Sven On 6/21/20 8:33 PM, Sven Wolf wrote: Hi, I found the same issue in a thread some weeks ago. https://marc.info/?l=openbsd-misc=159039904132502=2 I'll test an reinstall/older loader. Boot from mbr isn't an option :( Best regards, Sven On 6/21/20 8:20 PM, Sven Wolf wrote: Hi, I've upgraded my Lenovo V130 from snapshot 6.6 (April 2020) to the >>> snapshot from 2020-06-20. The boot via boot.rd is always possible. But when I load bsd.sp or bsd.rd the boot process stops with the >>> error "entry point 0x1001000". Do you have an idea how I can fix this >>> error? In the past I did't have any problem with openbsd on this machine. I'll try tomorrow the next snapshot. Thanks and best regards, Sven
Re: Lenovo V130, boot failed with error "entry point at 0x1001000"
Hi, also after the new installation of the current snapshot the system stops with "entry point at 0x1001000". It's interesting, that a installation via bsd.rd is possible. But after that the system doesn't boot via bsd.mp/bsd.sp. Best regards, Sven On 6/21/20 8:55 PM, Sven Wolf wrote: Hi, the update of the loader didn't help. I've updated the bootx64.efi from 3.48 to 3.52. But the current kernel doesn't load. I'll try a re-installation. Maybe @Otto can explain why the start of bsd.rd is possible and the start of bsd.sp/bsd.mp is not possible. Maybe I can build a custom kernel. Best regards, Sven On 6/21/20 8:33 PM, Sven Wolf wrote: Hi, I found the same issue in a thread some weeks ago. https://marc.info/?l=openbsd-misc=159039904132502=2 I'll test an reinstall/older loader. Boot from mbr isn't an option :( Best regards, Sven On 6/21/20 8:20 PM, Sven Wolf wrote: Hi, I've upgraded my Lenovo V130 from snapshot 6.6 (April 2020) to the snapshot from 2020-06-20. The boot via boot.rd is always possible. But when I load bsd.sp or bsd.rd the boot process stops with the error "entry point 0x1001000". Do you have an idea how I can fix this error? In the past I did't have any problem with openbsd on this machine. I'll try tomorrow the next snapshot. Thanks and best regards, Sven
Re: Lenovo V130, boot failed with error "entry point at 0x1001000"
Hi, the update of the loader didn't help. I've updated the bootx64.efi from 3.48 to 3.52. But the current kernel doesn't load. I'll try a re-installation. Maybe @Otto can explain why the start of bsd.rd is possible and the start of bsd.sp/bsd.mp is not possible. Maybe I can build a custom kernel. Best regards, Sven On 6/21/20 8:33 PM, Sven Wolf wrote: Hi, I found the same issue in a thread some weeks ago. https://marc.info/?l=openbsd-misc=159039904132502=2 I'll test an reinstall/older loader. Boot from mbr isn't an option :( Best regards, Sven On 6/21/20 8:20 PM, Sven Wolf wrote: Hi, I've upgraded my Lenovo V130 from snapshot 6.6 (April 2020) to the snapshot from 2020-06-20. The boot via boot.rd is always possible. But when I load bsd.sp or bsd.rd the boot process stops with the error "entry point 0x1001000". Do you have an idea how I can fix this error? In the past I did't have any problem with openbsd on this machine. I'll try tomorrow the next snapshot. Thanks and best regards, Sven
Re: Lenovo V130, boot failed with error "entry point at 0x1001000"
Hi, I found the same issue in a thread some weeks ago. https://marc.info/?l=openbsd-misc=159039904132502=2 I'll test an reinstall/older loader. Boot from mbr isn't an option :( Best regards, Sven On 6/21/20 8:20 PM, Sven Wolf wrote: Hi, I've upgraded my Lenovo V130 from snapshot 6.6 (April 2020) to the snapshot from 2020-06-20. The boot via boot.rd is always possible. But when I load bsd.sp or bsd.rd the boot process stops with the error "entry point 0x1001000". Do you have an idea how I can fix this error? In the past I did't have any problem with openbsd on this machine. I'll try tomorrow the next snapshot. Thanks and best regards, Sven
Lenovo V130, boot failed with error "entry point at 0x1001000"
Hi, I've upgraded my Lenovo V130 from snapshot 6.6 (April 2020) to the snapshot from 2020-06-20. The boot via boot.rd is always possible. But when I load bsd.sp or bsd.rd the boot process stops with the error "entry point 0x1001000". Do you have an idea how I can fix this error? In the past I did't have any problem with openbsd on this machine. I'll try tomorrow the next snapshot. Thanks and best regards, Sven
Re: last snapshot points to /pub/OpenBSD/6.3/ instead to /pub/OpenBSD/snapshots/
Hi Peter, thanks for your information. Everything is fine now :) Thanks, Sven On 03/19/18 12:43, Peter N. M. Hansteen wrote: On Mon, Mar 19, 2018 at 12:34:43PM +0100, Sven Wolf wrote: I've updated my system to the latest amd64 snapshot. When I run a system updade from bsd.rd and pkg_add then it points to /pub/OpenBSD/6.3/ instead to /pub/OpenBSD/snapshots/. The problem occurs in my opinion since last friday. Is there something which I can fix on my machine? Or is this an error from kernel? Not the kernel, but the snapshot is close enough to release that this is expected behavior. for a little while now, you will need to prepend -D snap to your other pkg_add options if you're running a snapshot. It's in the pkg_add man page, but easy to miss I guess. - Peter
last snapshot points to /pub/OpenBSD/6.3/ instead to /pub/OpenBSD/snapshots/
Hi, I've updated my system to the latest amd64 snapshot. When I run a system updade from bsd.rd and pkg_add then it points to /pub/OpenBSD/6.3/ instead to /pub/OpenBSD/snapshots/. The problem occurs in my opinion since last friday. Is there something which I can fix on my machine? Or is this an error from kernel? When I installed the snapshot from 2018-03-10 (about a week ago) everything worked as expected. Here are the kernel informations from dmesg: OpenBSD 6.3 (GENERIC.MP) #68: Fri Mar 16 01:24:47 MDT 2018 OpenBSD 6.3 (RAMDISK_CD) #64: Sun Mar 18 15:14:26 MDT 2018 OpenBSD 6.3 (GENERIC.MP) #72: Sun Mar 18 15:09:43 MDT 2018 I've tested the upgrade via bsd.rd and also via install63.fs. Thanks and best regards, Sven
dmesg Asus EEE Box 202
Hello, I've successfully installed OpenBSD -current on a Asus EEE Box 202. There are some minor issues: - only the bsd.rd and bsd.mp kernel boots the system, bsd just stops at entry point 0x200120 - re0 detected wrong media options (10BaseT), so I set it manually to 100basetx full-duplex I didn't test sound and wireless lan but as far as I know ral0 and azalia0 are the same than in the Asus EEE PC 1000H and there wireless lan and sound works without any problems. Best regards, Sven [EMAIL PROTECTED]@[EMAIL PROTECTED] at acpi0: PWRB acpivideo at acpi0 not configured bios0: ROM list: 0xc/0xec00! 0xcf000/0x1000 cpu0: unknown Enhanced SpeedStep CPU, msr 0x060f0c2606000c26 cpu0: using only highest and lowest power states cpu0: Enhanced SpeedStep 1600 MHz (1308 mV): speeds: 1600, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1\^C\M-`\^_\M-=\^C\M-p\^_\M-=\^C \M-=\^C\^P \M-=\^C \M-=\^C0 \M-=\^C@ \M-=\^CP \M-=\^C` \M-=\^Cp \M-=\^C\M^@ \M-=\^C\M^P \M-=\^C\240 \M-=\^C\M-0 \M-=\^C\M-@ \M-=\^C\M-P \M-=\^C\M-` \M-=\^C\M-p \M-=\^C!\M-=\^C\^P!\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) w\^C\M-`\M-=\^C\M-p\M-=\^C#\M-=\^C\^P#\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED] at vga1 drm0 at inteldrm0 Intel 82945GM Video rev 0x03\^C\M-`%\M-=\^C\M-p%\M-=\^C\M-=\^C\^P\M-=\^C \M-=\^C0\M-=\^C@\M-=\^CP\M-=\^C`\M-=\^Cp\M-=\^C\M^@\M-=\^C\M^P\M-=\^C\240\M-=\^C\M-0\M-=\^C\M-@\M-=\^C\M-P\M-=function 0 Intel 82801GB HD Audio rev 0x02: apic 2 int 16 (irq 5) azalia0: codecs: Realtek ALC888 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 2 int 16 (irq 5) pci1 at ppb0 bus 4 re0 at pci1 dev 0 function 0 Realt\^C\M-`*\M-=\^C\M-p*\M-=\^C+\M-=\^C\^P+\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED]), address 00:23:54:xx:yy:zz rgephy0 at re0 phy 7: RTL8169S/8110\^C\M-`,\M-=\^C\M-p,\M-=\^C-\M-=\^C\^P-\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] rev 0x02: apic 2 int 17 (irq 10) pci2 at ppb1 bus 3 ral0 at pc\^C\M-`.\M-=\^C\M-p.\M-=\^C/\M-=\^C\^P/\M-=\^C /\M-=\^C0/\M-=\^C@/\M-=\^CP/\M-=\^C`/\M-=\^Cp/\M-=\^C\M^@/\M-=\^C\M^P/\M-=\^C\240/\M-=\^C\M-0/\M-=\^C\M-@/\M-=\^C\M-P/\M-=\^C\M-`/\M-=\^C\M-p/\M-=\^C0\M-=\^C\^P0\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED] PCIE rev 0x02: apic 2 int 18 (irq 11) pci3 at ppb2 bus 1 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 2 int 23 (irq 3) uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 2 int 19 (irq 7) uhci2 at pci0 dev 29 functio\^C\M-`5\M-=\^C\M-p5\M-=\^C6\M-=\^C\^P6\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: apic 2 in\^C\M-`7\M-=\^C\M-p7\M-=\^C8\M-=\^C\^P8\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] rev 0x02: apic 2 int 23 (irq 3) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb3 a\^C\M-`:\M-=\^C\M-p:\M-=\^C;\M-=\^C\^P;\M-=\^C ;\M-=\^C0;\M-=\^C@;\M-=\^CP;\M-=\^C`;\M-=\^Cp;\M-=\^C\M^@;\M-=\^C\M^P;\M-=\^C\240;\M-=\^C\M-0;\M-=\^C\M-@;\M-=\^C\M-P;\M-=\^C\M-`;\M-=\^C\M-p;\M-=\^C\M-=\^C\^P\M-=\^C \M-=\^C0\M-=\^C@\M-=\^CP\M-=\^C`\M-=\^Cp\M-=\^C\M^@\M-=\^C\M^P\M-=\^C\240\M-=\^C\M-0\M-=\^C\M-@\M-=\^C\M-P\M-=GBM LPC rev 0x02: PM disabled pciide0 at pci0 dev 31 function 2 Intel 82801GBM SATA rev 0x02: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: ST9160310AS wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 ichiic0 at pci0 dev 31 function 3 Intel 82801GB SMBus rev 0x02: apic 2 int 19 (irq 7) iic0 at ichiic0 spdmem0 at iic0 add\^C\M-`C\M-=\^C\M-pC\M-=\^CD\M-=\^C\^PD\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED] usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI roo\^C\M-`F\M-=\^C\M-pF\M-=\^CG\M-=\^C\^PG\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 usb3 at uhc\^C\M-`H\M-=\^C\M-pH\M-=\^CI\M-=\^C\^PI\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@N\M-=\^C\M^PN\M-=\^C\240N\M-=! [EMAIL PROTECTED] speaker spkr0 at pcppi0 wbsio0 at isa0 port 0x2e/2: W83627DH\^C\M-`O\M-=\^C\M-pO\M-=\^CP\M-=\^C\^PP\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED] MTRR support umass0 at uhub0 port 6 configuration 1 interface 0 Generic USB2.0-CRW rev 2.00/58.87 addr 2 umass0: using SCS\^C\M-`S\M-=\^C\M-pS\M-=\^CT\M-=\^C\^PT\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] scsibus0 targ 1 lun 0: Generic-, Multi-Card, 1.00 SCSI0 0/d\^C\M-`U\M-=\^C\M-pU\M-=\^CV\M-=\^C\^PV\M-=\^C [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL
Re: dmesg ASUS EEEPC 1000H
Hi Martin, ral0 works out of the box and without any problems. Currently I've got the wireless lan with WPA2 working with following hostname.ral0 dhcp NONE NONE NONE nwid %my_ssid% wpa wpapsk\ %my_wpa_key_generated_with_'wpa-psk'% Best regards, Sven Martin Toft wrote: On Mon, Sep 15, 2008 at 10:26:26PM +0200, Sven Wolf wrote: Hi, I've successfully installed -current on a ASUS EEEPC 1000H (via an usb stick). At the moment lii doesn't detect the wired lan adapter: Attansic Technology L1E rev 0xb0 but maybe there will be a patch in the future... For the LAN connection I've used an USB adapter: axe0 at uhub0 port 2 configuration 1 interface 0 Cisco-Linksys USB200M v2 If you have any question just contact me. I've tried to install some packages but it seems that libiconv-1.12 is broken in the current snaphot :( Best regards, Sven Hi Sven I've done almost the same thing with my Eee PC1000H :-D Only almost, though, as I'm tracking -current instead of running a snapshot. I installed a snapshot using an USB cdrom drive, checked out the -current source and built it. I know snapshots are the the best way to test things, but I did it this way to be able to hack around with the source and test patches (as much as time and competence allow me to). I'm writing this mail on the Eee laptop, connected to the world through a Linksys USB200M v2 USB Ethernet adaptor :-) Don't you experience problems with the wireless Ralink RT2790 network device? I've had it working in 2-3 boots right after I got the laptop and never since. From dmesg: ral0 at pci3 dev 0 function 0 Ralink RT2790 rev 0x00: irq 11ral0: timeout waiting for NIC to initialize If you wonder how to unmute the sound card, try this: mixerctl outputs.speaker2.eapd=on (see also mixerctl.conf(5)) I have attached the mail that I sent to [EMAIL PROTECTED] a while ago. Martin - Forwarded message from Martin Toft [EMAIL PROTECTED] - Date: Thu, 4 Sep 2008 21:21:45 +0200 From: Martin Toft [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Asus Eee PC 1000H laptop Notable things that work: - Boots without problems every time. - Sound. - USB. - X (it detects everything automatically and Just Works(tm)). - Touchpad. Things that doesn't work or only work partially: - APM. AC is detected, but battery charge is unknown. - LAN (Attansic Technology L1E rev 0xb0). I have tried forcing it to use lii(4) but it fails init with can't get MAC address-ish. - WLAN (Ralink RT2790). I have had it working in about two boots out of approx 30. I haven't found a pattern. I'm multibooting with the preinstalled Windows at the moment, and maybe it has something to do with the way Windows handles the card. I have included dmesg and pcidump -v. Thanks for everyting! You're welcome to contact me if you need me to test something or want more info. If you want an entry for the i386-laptop page, I'm eager to write one and make my dmesg available somewhere. dmesg = OpenBSD 4.4-current (GENERIC) #2: Thu Sep 4 01:33:19 CEST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR real mem = 1064529920 (1015MB) avail mem = 1020891136 (973MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/11/08, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.5 @ 0xf0700 (30 entries) bios0: vendor American Megatrends Inc. version 0901 date 07/11/2008 bios0: ASUSTeK Computer INC. 1000H apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 3.0 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf8770/176 (9 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801GBM LPC rev 0x00) pcibios0: PCI bus #5 is the last bus bios0: ROM list: 0xc/0xec00! cpu0 at mainbus0 cpu0: unknown Enhanced SpeedStep CPU, msr 0x060f0c2406000c24 cpu0: using only highest and lowest power states cpu0: Enhanced SpeedStep 1600 MHz (1276 mV): speeds: 1600, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82945GME Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GME Video rev 0x03 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) agp0 at vga1: aperture at 0xd000, size 0x1000 Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: irq 5 azalia0: codec[s]: Realtek/0x0269 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: irq 5 pci1 at ppb0 bus 4 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: irq 10 pci2
Re: pkg_add c.48.0 lib error on current
as written on [EMAIL PROTECTED] the solution is Either wait, or build from ports. Currently I build my own packages from the ports. Because the offical snapshot packages haven't been updated since august. Best regards, Sven Stanislaus Hoppe wrote: Hello, I've tried to install the bash package (PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/i386/) on a -*current* system (4.4 GENERIC#1050 i386) but I get following error: pkg_add -v bash parsing bash-3.2.39 Dependencies for bash-3.2.39 resolve to: *libiconv*-1.12, gettext-*0*.17 (todo: *libiconv*-1.12,gettext-*0*.17) bash-3.2.39:parsing *libiconv*-1.12 *Can*'t install *libiconv*-1.12: *lib* *not* *found* *c*.*48*.*0* *c*.*48*.*0*: partial match in /usr/*lib*: major=49, minor=*0* (bad major) bash-3.2.39:parsing gettext-*0*.17 Dependencies for gettext-*0*.17 resolve to: *libiconv*-1.12 (todo: *libiconv*-1.12) bash-3.2.39:parsing *libiconv*-1.12 *Can*'t install *libiconv*-1.12: *lib* *not* *found* *c*.*48*.*0* *c*.*48*.*0*: partial match in /usr/*lib*: major=49, minor=*0* (bad major) *Can*'t install gettext-*0*.17: *can*'t resolve *libiconv*-1.12 *Can*'t install bash-3.2.39: *can*'t resolve *libiconv*-1.12,gettext-*0*.17 Is there anything that I *can* do to fix this issue? In my opinion the *libiconv* package has to be packaged on a -*current* (#1050) system. Best regards, zm0
dmesg ASUS EEEPC 1000H
Hi, I've successfully installed -current on a ASUS EEEPC 1000H (via an usb stick). At the moment lii doesn't detect the wired lan adapter: Attansic Technology L1E rev 0xb0 but maybe there will be a patch in the future... For the LAN connection I've used an USB adapter: axe0 at uhub0 port 2 configuration 1 interface 0 Cisco-Linksys USB200M v2 If you have any question just contact me. I've tried to install some packages but it seems that libiconv-1.12 is broken in the current snaphot :( Best regards, Sven OpenBSD 4.4-current (GENERIC) #1050: Wed Sep 10 12:18:05 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR real mem = 1064529920 (1015MB) avail mem = 1020891136 (973MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 08/01/08, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.5 @ 0xf0700 (30 entries) bios0: vendor American Megatrends Inc. version 1005 date 08/01/2008 bios0: ASUSTeK Computer INC. 1000H apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 3.0 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf8720/176 (9 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801GBM LPC rev 0x00) pcibios0: PCI bus #5 is the last bus bios0: ROM list: 0xc/0xec00! 0xcf000/0x1000 cpu0 at mainbus0 cpu0: unknown Enhanced SpeedStep CPU, msr 0x060f0c1f06000c1f cpu0: using only highest and lowest power states cpu0: Enhanced SpeedStep 1600 MHz (1196 mV): speeds: 1600, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82945GME Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GME Video rev 0x03 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) agp0 at vga1: aperture at 0xd000, size 0x1000 Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: irq 5 azalia0: codec[s]: Realtek/0x0269 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: irq 5 pci1 at ppb0 bus 4 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: irq 10 pci2 at ppb1 bus 3 Attansic Technology L1E rev 0xb0 at pci2 dev 0 function 0 not configured ppb2 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x02: irq 11 pci3 at ppb2 bus 1 ral0 at pci3 dev 0 function 0 Ralink RT2790 rev 0x00: irq 11, address 00:22:xx:xx:xx:xx ral0: MAC/BBP RT2872 (rev 0x0200), RF RT2720 (1T2R) uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: irq 3 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: irq 11 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x02: irq 7 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: irq 5 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x02: irq 3 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb3 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe2 pci4 at ppb3 bus 5 ichpcib0 at pci0 dev 31 function 0 Intel 82801GBM LPC rev 0x02: PM disabled pciide0 at pci0 dev 31 function 2 Intel 82801GBM SATA rev 0x02: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: ST9160827AS wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 usb3 at uhci2: USB revision 1.0 uhub3 at usb3 Intel UHCI root hub rev 1.00/1.00 addr 1 usb4 at uhci3: USB revision 1.0 uhub4 at usb4 Intel UHCI root hub rev 1.00/1.00 addr 1 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 biomask ebfd netmask ebfd ttymask mtrr: Pentium Pro MTRR support axe0 at uhub0 port 2 configuration 1 interface 0 Cisco-Linksys USB200M v2 rev 2.00/0.01 addr 2 axe0: AX88772, address 00:1d:xx:xx:xx:xx ukphy0 at axe0 phy 16: Generic IEEE 802.3u media interface, rev. 1: OUI 0x000ec6, model 0x0001 ugen0 at uhub4 port 1 Broadcom Corp BT-253 rev 2.00/2.41 addr 2 softraid0 at root root on wd0a swap on wd0b dump on wd0b
Thanks for the great os and xenocara
Hi, I say thank you to all developers for the great operating system. With xorg 7.2 (xenocara) now I can use my nvidia 7600 gs on my 1680x1050 widescreen without any problems. Best regards, Sven
Re: OpenBSD 4.0 released Nov 1, 2006
Theo de Raadt wrote: Nov 1, 2006. We are pleased to announce the official release of OpenBSD 4.0. This is our 20th release on CD-ROM (and 21st via FTP). We remain proud of OpenBSD's record of ten years with only a single remote hole in the default install. As in our previous releases, 4.0 provides significant improvements, including new features, in nearly all areas of the system: I thank all for the great release, even for the cdrom package (nice booklet/artwork ;) Sven
Re: OpenBSD dedicated hosting
Oops, maybe something went wrong at my last post :( Here is the missing wd0 line: wd0 at pciide0 channel 0 drive 0: ExcelStor Technology J360 Stuart Henderson wrote: On 2006/09/21 22:50, Sven Wolf wrote: wd0 at pciide0 channel 0 drive 0: ^ haven't noticed that before (no drive model listed) - do they have something to hide?!
Re: OpenBSD dedicated hosting
Hi Gilles, I've switched my Strato Power Server (dedicated server - http://www.strato.de/server/power/index.html) from Linux to OpenBSD 3.9. For more information read: http://www.dettus.net/openbsd_at_strato.txt And here is the dmesg of my Power Server: OpenBSD 3.9 (GENERIC) #617: Thu Mar 2 02:26:48 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(R) CPU 2.40GHz (GenuineIntel 686-class) 2.40 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID real mem = 536387584 (523816K) avail mem = 482426880 (471120K) using 4278 buffers containing 26923008 bytes (26292K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(c0) BIOS, date 05/27/03, BIOS32 rev. 0 @ 0xfb330 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xdf84 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfde90/240 (13 entries) pcibios0: PCI Exclusive IRQs: 5 10 11 12 pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371SB ISA rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82845 Host rev 0x04 ppb0 at pci0 dev 1 function 0 Intel 82845 AGP rev 0x04 pci1 at ppb0 bus 1 ppb1 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0x05 pci2 at ppb1 bus 2 fxp0 at pci2 dev 6 function 0 Intel 8255x rev 0x08, i82559: irq 12, address 00:30:48:52:c9:fc inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4 fxp1 at pci2 dev 7 function 0 Intel 8255x rev 0x08, i82559: irq 12, address 00:30:48:52:c9:fd inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 4 vga1 at pci2 dev 8 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ichpcib0 at pci0 dev 31 function 0 Intel 82801BA LPC rev 0x05 pciide0 at pci0 dev 31 function 1 Intel 82801BA IDE rev 0x05: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: wd0: 16-sector PIO, LBA48, 58644MB, 120103200 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 pciide0: channel 1 disabled (no drives) ichiic0 at pci0 dev 31 function 3 Intel 82801BA SMBus rev 0x05: irq 5 iic0 at ichiic0 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 lm0 at isa0 port 0x290/8: W83627HF npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom0: console pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 biomask ef65 netmask ff65 ttymask ffe7 pctr: user-level cycle counter enabled dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 Best regards, Sven Hi misc@, I am looking for companies that provide OpenBSD-powered dedicated hosting. Currently, I am being hosted by a french company which turned out to be as incompetent as can be, and I am willing to switch as soon as possible (preferably before the 25th of September). I have google-d a bit and found out a few companies, but its hard to know in advance which are competent and which will drive me into depression. So I'm turning to you, if you know of companies that do good work, that aren't too expensive and that provide OpenBSD based services, please mail me off-list so I can start digging their offers. Thanks a lot people ;)
Re: OpenBSD hardware router
z0mbix wrote: On 2/2/06, Kenny Mann [EMAIL PROTECTED] wrote: I'm looking for something that which I can slap OpenBSD 3.8 on and use it as a router. This will be used for a house (~ 4 people) and I'm looking for something small in form factor and that which doesn't run hot because it will run in a closet. I'm seeking to replace our D-Link router because it seems to lock up on an occasion and this seem like a fun little project to do. I'd also like it to have wireless capabilities as well. Anyone know where I can start looking or can point in a direction to start? Or are my hopes too high and I should just get a PC and make it happen that route (pun not intended)? Kenny Mann Don't forget the wrap: http://www.pcengines.ch/wrap.htm They're slightly cheaper than the soekris. I use one with 3.8 and it runs as a cable router/firewall and runs ipsec between home and work. Hi z0mbix, how did you install OpenBSD on a wrap? Like: http://wiki.bsdforen.de/index.php/OpenBSD_-_WRAP and the links on the bottom (websites of Jonathan Weiss Thomas Kaschwig) Thanks, Sven
OpenBSD 3.8, fxp, device timeout
Hello, I've a server at the German hoster Strato and I try to install OpenBSD 3.8 on this machine. But I always get a device timeout of the Intel Nic (because of a wrong irq assignment?) :( Here is the dmesg output: OpenBSD 3.8 (RAMDISK) #9: Tue Jan 17 18:24:51 CET 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK cpu0: Intel(R) Celeron(R) CPU 2.40GHz (GenuineIntel 686-class) 2.40 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH, ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID real mem = 536387584 (523816K) avail mem = 485179392 (473808K) using 4278 buffers containing 26923008 bytes (26292K) of memory mainbus0 (root) acpi0 at mainbus0: revision 0 attached acpitimer at acpi0 not configured acpi device at acpi0 from table DSDT not configured acpi device at acpi0 from table FACP not configured bios0 at mainbus0: AT/286+(c0) BIOS, date 05/27/03, BIOS32 rev. 0 @ 0xfb330 apm0 at bios0: Power Management spec V1.2 apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xdf84 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfde90/240 (13 entries) pcibios0: PCI Exclusive IRQs: 5 10 11 12 pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371SB ISA rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82845 Host rev 0x04 ppb0 at pci0 dev 1 function 0 Intel 82845 AGP rev 0x04 pci1 at ppb0 bus 1 ppb1 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0x05 pci2 at ppb1 bus 2 fxp0 at pci2 dev 6 function 0 Intel 82557 rev 0x08, i82559: irq 12, address 00:30:48:52:c9:fc inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4 fxp1 at pci2 dev 7 function 0 Intel 82557 rev 0x08, i82559: irq 12, address 00:30:48:52:c9:fd inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 4 vga1 at pci2 dev 8 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) ichpcib0 at pci0 dev 31 function 0 Intel 82801BA LPC rev 0x05: failed to map I/O space pciide0 at pci0 dev 31 function 1 Intel 82801BA IDE rev 0x05: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: ExcelStor Technology J360 wd0: 16-sector PIO, LBA48, 58644MB, 120103200 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 pciide0: channel 1 disabled (no drives) Intel 82801BA SMBus rev 0x05 at pci0 dev 31 function 3 not configured isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom0: console pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 biomask ede5 netmask fde5 ttymask ffe7 rd0: fixed, 3800 blocks dkcsum: wd0 matches BIOS drive 0x80 root on rd0a rootdev=0x1100 rrootdev=0x2f00 rawdev=0x2f02 I've created my own bootfloppy because with the default OpenBSD 3.8 bootfloppy I get the same error. I've played (enabled/disabled) with following kernel options without luck: option PCIBIOS_INTR_FIXUP_FORCE option PCI_INTR_FIXUP (as for the netbsd kernel) optionUSER_PCICONF# user-space PCI configuration optionBOOT_CONFIG# boot-time kernel config pcibios0 at bios0 flags 0x0008 (set to 0x0004, 0x0008, 0x0030) acpi0at mainbus? #acpitimer* at acpi? #hpet*at acpi? optionACPIVERBOSE optionACPI_ENABLE Has anyone any idea how I can assign an another irq than 12 to fxp? In my opinion this is the problem :( Thanks and best regards, Sven
