Only the Kernel section
listimage
KERNEL TEAM:
ID Text Data Seq# Init# Name
--------------------------------------------------------------------------------
1 0xffffffff80000000 0xffffffff801a5000 0 0 kernel_x86_64
9 0xffffffff826b7000 0xffffffff826e7000 0 0 ramfs
10 0xffffffff8265d000 0xffffffff826b4000 0 0 ntfs
13 0xffffffff8261a000 0xffffffff8263a000 0 0 fat
23 0xffffffff8256c000 0xffffffff82584000 0 0 xhci
27 0xffffffff824f2000 0xffffffff82504000 0 0 usb_disk
28 0xffffffff824e2000 0xffffffff824f1000 0 0 usb
36 0xffffffff82272000 0xffffffff8241b000 0 0 pci
37 0xffffffff821ad000 0xffffffff8223e000 0 0 packagefs
38 0xffffffff8219c000 0xffffffff821ac000 0 0 nvme_disk
45 0xffffffff8217b000 0xffffffff8217c000 0 0 isa
47 0xffffffff8215c000 0xffffffff82167000 0 0 efi_gpt
48 0xffffffff8215a000 0xffffffff8215b000 0 0 dpc
49 0xffffffff82111000 0xffffffff82148000 0 0 bfs
53 0xffffffff82099000 0xffffffff820e1000 0 0 acpi
54 0x0000000000000000 0x0000000000000000 0 0 commpage
89 0xffffffff82ffd000 0xffffffff82ffe000 0 0 /boot/system/add-ons/kernel/generic/smbios
124 0xffffffff82652000 0xffffffff82659000 0 0 /boot/system/add-ons/kernel/drivers/disk/virtual/ram_disk
132 0xffffffff82179000 0xffffffff8217a000 0 0 /boot/system/add-ons/kernel/drivers/dev/zero
134 0xffffffff824ba000 0xffffffff824c4000 0 0 /boot/system/add-ons/kernel/drivers/dev/tty
135 0xffffffff8265a000 0xffffffff8265b000 0 0 /boot/system/add-ons/kernel/drivers/dev/null
136 0xffffffff827a4000 0xffffffff827a5000 0 0 /boot/system/add-ons/kernel/drivers/dev/dprintf
137 0xffffffff8263c000 0xffffffff8263f000 0 0 /boot/system/add-ons/kernel/drivers/dev/console
622 0xffffffff82585000 0xffffffff82587000 0 0 /boot/system/add-ons/kernel/cpu/generic_x86
623 0xffffffff820f4000 0xffffffff820f6000 0 0 /boot/system/add-ons/kernel/power/cpufreq/intel_pstates
624 0xffffffff827a6000 0xffffffff827a7000 0 0 /boot/system/add-ons/kernel/power/cpuidle/intel_cstates
625 0xffffffff82640000 0xffffffff82641000 0 0 /boot/system/add-ons/kernel/debugger/run_on_exit
626 0xffffffff8217d000 0xffffffff8217e000 0 0 /boot/system/add-ons/kernel/debugger/usb_keyboard
627 0xffffffff82588000 0xffffffff82589000 0 0 /boot/system/add-ons/kernel/debugger/invalidate_on_exit
628 0xffffffff824d0000 0xffffffff824d2000 0 0 /boot/system/add-ons/kernel/debugger/hangman
629 0xffffffff8273a000 0xffffffff8274f000 0 0 /boot/system/add-ons/kernel/debugger/disasm
630 0xffffffff82706000 0xffffffff8271b000 0 0 /boot/system/add-ons/kernel/debugger/demangle
632 0xffffffff8271d000 0xffffffff82720000 0 0 /boot/system/add-ons/kernel/bus_managers/random
668 0xffffffff804ba000 0xffffffff804bc000 0 0 /boot/system/add-ons/kernel/drivers/power/acpi_button
1760 0xffffffff824d3000 0xffffffff824d6000 0 0 /boot/system/add-ons/kernel/drivers/power/acpi_battery
5704 0xffffffff824d7000 0xffffffff824db000 0 0 /boot/system/add-ons/kernel/drivers/wmi
9377 0xffffffff8275f000 0xffffffff82784000 0 0 /boot/system/add-ons/kernel/network/stack
9378 0xffffffff82173000 0xffffffff82175000 0 0 /boot/system/add-ons/kernel/network/notifications
9394 0xffffffff82786000 0xffffffff8278e000 0 0 /boot/system/add-ons/kernel/network/protocols/udp
9395 0xffffffff8278f000 0xffffffff8279a000 0 0 /boot/system/add-ons/kernel/network/protocols/ipv4
9396 0xffffffff8299b000 0xffffffff8299d000 0 0 /boot/system/add-ons/kernel/network/devices/loopback
9397 0xffffffff804bd000 0xffffffff804be000 0 0 /boot/system/add-ons/kernel/network/datalink_protocols/loopback_frame
9415 0xffffffff8225c000 0xffffffff82267000 0 0 /boot/system/add-ons/kernel/network/protocols/ipv6
9696 0xffffffff8258a000 0xffffffff825e5000 0 0 /boot/system/add-ons/kernel/drivers/dev/net/iaxwifi200
10462 0xffffffff8071f000 0xffffffff8072a000 0 0 /boot/system/add-ons/kernel/drivers/dev/graphics/intel_extreme
10463 0xffffffff82091000 0xffffffff82096000 0 0 /boot/system/add-ons/kernel/bus_managers/agp_gart
10469 0xffffffff82702000 0xffffffff82704000 0 0 /boot/system/add-ons/kernel/drivers/dev/graphics/framebuffer
10472 0xffffffff8073c000 0xffffffff80742000 0 0 /boot/system/add-ons/kernel/busses/agp_gart/intel
10497 0xffffffff82258000 0xffffffff8225b000 0 0 /boot/system/add-ons/kernel/network/devices/ethernet
10498 0xffffffff80744000 0xffffffff80748000 0 0 /boot/system/add-ons/kernel/network/datalink_protocols/arp
10499 0xffffffff825ee000 0xffffffff825f0000 0 0 /boot/system/add-ons/kernel/network/datalink_protocols/ethernet_frame
10530 0xffffffff80761000 0xffffffff80770000 0 0 /boot/system/add-ons/kernel/network/protocols/tcp
10601 0xffffffff807d0000 0xffffffff807dc000 0 0 /boot/system/add-ons/kernel/bus_managers/ps2
10903 0xffffffff824b4000 0xffffffff824b7000 0 0 /boot/system/add-ons/kernel/drivers/dev/bus/usb_raw
11048 0xffffffff8067f000 0xffffffff8068c000 0 0 /boot/system/add-ons/kernel/drivers/dev/audio/hmulti/hda
11776 0xffffffff80703000 0xffffffff8070f000 0 0 /boot/system/add-ons/kernel/network/protocols/unix
11809 0xffffffff806d1000 0xffffffff806d4000 0 0 /boot/system/add-ons/kernel/network/protocols/icmp
14939 0xffffffffa8b6e000 0xffffffffa8b72000 0 0 /boot/system/add-ons/kernel/network/datalink_protocols/ipv6_datagram
14997 0xffffffffa8c31000 0xffffffffa8c33000 0 0 /boot/system/add-ons/kernel/network/protocols/icmp6
1 Like
In Terminal
uname -a
1 Like
Please submit a bug report, with the syslog ("Can’t boot from usb when connected on …).
When the system is running, plug/unplug a USB device in the non-working port so that there is more info in the syslog.
1 Like
“uname -a Haiku shredder 1 hrev56578+59 Dec 17 2022 07:02: x86_64 x86_64 Haiku” very old
In Terminal
pkgman full
Sorry, that was from when I booted the ISO so I could get a syslog of plugging the device into the USB-C port.
On the external SSD I’ve already updated everything:
Haiku shredder 1 hrev56578+93 Nov 14 2023 07:35: x86_64 x86_64 Haiku
~>
100% repochecksum-1 [65 bytes]
Validating checksum for Haiku...done.
100% repochecksum-1 [64 bytes]
Validating checksum for HaikuPorts...done.
Nothing to do.
2 Likes
Delete all files and catalogs in the catalog /boot/system/packages/administrative.
And reboot.
This should fix the problems with packages.
As a result of a network failure, errors of the package manager in the administrative directory may be unfinished transactions. They can create problems when mounting system packages.
What problem? don’t tell people to just randomly delete that dir! If you remove it you can’t boot into earlier states anymore in case of errors >.>
https://download.haiku-os.org/nightly-images/x86_64/
Try nightly builds
The filling of an administrative directory gradually leads to a slowdown in the load of the operating system.
It does not. There was one specific bug that was fixed quite a while back.
Please don’t tell people to delete random system folders.
1 Like
I’ve tried to build from source so I could test the bleeding edge and maybe experiment with making changes if it came to that… but I’ve failed to buld 
...failed Link objects/haiku/x86_64/release/apps/haikudepot/HaikuDepot ...
BUILD FAILURE:
...failed updating 2 target(s)...
...skipped 214 target(s)...
...updated 78 target(s)...
I think maybe soemething to do with this:
AddSymlinkToContainerCopyFilesScript <FloppyBootImage>system/add-ons/kernel/drivers/dev/disk/usb/usb_disk
Link objects/haiku/x86_64/release/apps/haikudepot/HaikuDepot
/boot/home/dev/Haiku/haiku/generated.x86_64/cross-tools-x86_64/lib/gcc/x86_64-unknown-haiku/13.2.0/../../../../x86_64-unknown-haiku/bin/ld: cannot find objects/haiku/x86_64/release/apps/haikudepot/AccessToken.o: No such file or directory
/boot/home/dev/Haiku/haiku/generated.x86_64/cross-tools-x86_64/lib/gcc/x86_64-unknown-haiku/13.2.0/../../../../x86_64-unknown-haiku/bin/ld: cannot find objects/haiku/x86_64/release/apps/haikudepot/BitmapView.o: No such file or directory
/boot/home/dev/Haiku/haiku/generated.x86_64/cross-tools-x86_64/lib/gcc/x86_64-unknown-haiku/13.2.0/../../../../x86_64-unknown-haiku/bin/ld: cannot find objects/haiku/x86_64/release/apps/haikudepot/Captcha.o: No such file or directory
/boot/home/dev/Haiku/haiku/generated.x86_64/cross-tools-x86_64/lib/gcc/x86_64-unknown-haiku/13.2.0/../../../../x86_64-unknown-haiku/bin/ld: cannot find objects/haiku/x86_64/release/apps/haikudepot/CreateUserDetail.o: No such file or directory
which lists quite a bit more objects that can’t be found.
I’ve no idea why that’s happening or what to do about it.
I just followed the instructions at Compiling for x86_64 | Haiku Project
Any clue how to proceed?
1 Like
open a bug report with the build log
1 Like
hard to guess without a fuld build log. It looks like these .o files failed to build sometime earlier in the build, maybe because they are built from c++ sourcefiles generated from a Python script
Tried again today without the -q parameter to jam (I have no idea what that does)
It got farther & seemed to build a lot of those missing objects.
I scanned the output and noticed this:
Error: you are using a Haiku clone without tags, please set
the revision tag to use (e.g. HAIKU_REVISION=hrev43210)
That isn’t mentioned in the build instructions. I have no idea what number to use.
I tried to
HAIKU_INSTALL_DIR=/HaikuBuild HAIKU_REVISION=hrev57388 jam -q @install
and got this:
mkindex: Could not create index: Read-only file system
Populating image ...
Error: Failed to write attribute "SYS:NAME" of file "/HaikuBuild/home/Desktop": Read-only file system
The read-only filesystem message is complete BS. I just made that folder. But sure enough, if I try to make any files in there it fails:
/Haiku/home/dev/Haiku/haiku/generated.x86_64> cd /HaikuBuild/home/Desktop/
/HaikuBuild/home/Desktop> touch something
touch: cannot touch 'something': Invalid Argument
/HaikuBuild/home/Desktop> echo Hi mom > test.txt
bash: test.txt: Invalid Argument
/HaikuBuild/home/Desktop>
I don’t get it. I can make directories under that path (the build already made several), but no files… it always says “Invalid Argument”
Ah… Well now that was dumb…
Why did I think that / was the root of my Haiku volume? I guess I didn’t expect to be able to run mkdir outside of it.
… workingbetter now that I’ve used a sane folder.
Hopefully I can try booting with the latest-ish code…
/ is purely virtual, you can run mkdir in it in order to mount filesystems there. 
The kernel I built doesn’t even break into the kernel debugger.
I had to boot with the ISO flash drive so I could overwrite the kernel image on the SSD with the image in my
haiku/generated.x86_64/objects/haiku/x86_64/release/system/kernel/ folder.
It just gets stuck forever on the fourth icon when booting from the USB-C port. It still works from the USB-A port.
Aside: I tried using pkgman to update to a nightly, but that failed with a different message. Nothing about finding a boot partition: (took a photo with iPhone, did text recognition and cleaned it up…so hopefully this is accurate)
PANIC: page fault, but interrupts were disabled. Touching address 0X000000000000001c from ip Oxffffffff800637d1
Welcome to Kernel Debugging Land...
Thread 1 "idle thread 1"
running on CPU 0
stack trace for thread 1 "idle thread 1"
kernel stack: 0xffffffff82906000 to 0xffffffff8290b000
frame caller <image>:function + offset
0 ffffffff8290a4e0 (+ 32) ffffffff8014adb0 <kernel_x86_64> arch_debug_call_with_fault_handler() + 0x1a
1 ffffffff8290a500 {+ 80) ffffffff800b3ab8 <kernel_x86_64> debug_call_with_fault_handler() + 0x78
2 ffffffff8290a550 (+ 96) ffffffff800b5164 <kernel_х86_64> _ZL20kernel_debugger_loopPKcS0_P13__va_list_tagi() + 0xf4
3 ffffffff8290a5b0 (+ 80) ffffffff800b54fe <kernel_×86_64> _ZL24kernel_debugger_internalPKcS0_P13__va_list_yagi() + 0x6e
4 ffffffff8290a600 (+ 240) ffffffff800b5897 <kernel_x86_64> panic() + 0xb7
5 ffffffff8290a6f0 (+ 904) ffffffff8014c68c <kernel_×86_64> int_bottom() + 0x80
kernel iframe at 0xffffffff8290aa78 (end = 0xffffffff8290ab40)
rax 0x0 rbx 0x1 rcx 0x2
rdx 0x1 rsi 0x2c rdi 0xffffffff801c2e90
rbp 0xffffffff8290ab90 r8 0x186e r9 0xffffffff8290aa70
r10 0xffffffff801c2e78 r11 0x6a2e4 r12 0x9
r13 0x2d0 r14 0x1 г15 0х44b
rip 0xffffffff800637d1 rsp 0xffffffff8290ab40 rflags 0x10002
vector: 0xe, error code: 0x2
6 ffffffff8290aa78 (+ 280) ffffffff800637d1 <kernel_x86_64> int_io_interrupt_handler() + 0x261
7 ffffffff8290ab90 (+ 32) ffffffff80156ec1 <kernel_x86_64> x86_hardware_interrupt 0 + 0x111
8 ffffffff8290abb0 (+ 856) ffffffff8014c68c <kernel_x86_64> int_bottom() + 0x80
kernel iframe at 0xffffffff8290af08 (end = 0xffffffff8290afd0)
rax 0x0 rbx 0x48166520 rcx 0x0
rdx 0xffffffff801c9280 rsi 0xffffffff83010c08 rdi 0x0
rbp 0xffffffff8290aff0 r8 0xffffffff82910040 r9 0xffffffff82910040
r10 0x0 r11 0x1 r12 0×0
г13 0x496a9000 r14 0x47c706c0 r15 0x4814b577
rip 0xffffffff80150141 rsp Oxffffffff8290afd8 rflags 0x10246
vector: 0x29, error code: 0x0
9 ffffffff8290af08 (+ 232) ffffffff88150141 <kernel_×86_64> _ZL9halt_idlev() + 0x01
10 ffffffff8290aff0 (+2104446992) 000000004811b070
kdebug>