Latest Bugs & Tasks
Crashing from USB but not from hard disk sounds to me like it's a USB3 issue, which is already a known bug as well. And what GCC was used to build should not matter in this case.
When I try to update Haiku via pkgman update, I get the following output:
The following changes will be made: in system: install package haiku_welcome-r1~alpha4_pm_hrev47819-1-any.hpkg from repository Haiku install package makefile_engine-r1~alpha4_pm_hrev47819-1-any.hpkg from repository Haiku install package haiku_userguide-r1~alpha4_pm_hrev47819-1-any.hpkg from repository Haiku install package haiku_loader-r1~alpha4_pm_hrev47819-1-x86_gcc2.hpkg from repository Haiku uninstall package haiku_welcome-r1~alpha4_pm_hrev47816-1 uninstall package makefile_engine-r1~alpha4_pm_hrev47816-1 uninstall package haiku_userguide-r1~alpha4_pm_hrev47816-1 uninstall package haiku_loader-r1~alpha4_pm_hrev47816-1
Note the absence of a few core packages. Does anybody have any idea about that?
Not tested, but it seems it was fixed. Two or more years ago.
No feedback in 21 months, closing.
No feedback in three years, closing.
Closing this as it is six years old, with no activity in three years.
Upon ACPI initialization, ACPI expects you to walk the namespace and init all _PRW's. This was done in old ACPICA code, but not anymore, since it should be handled together with drivers.
This needs to be implemented.
I started top in the Terminal and when it crashed I clicked Save debug report which also crashed.
About Atheros Wifi Driver Prototype:
WiFi-card driver (GCC2) for the atheros chipset from FreeBSD without any major changes to its codebase (had to move some interrupt handler code into driver-specific glue code).
The atheros driver should support every atheros chipset, which are supported by the FreeBSD driver (look in the corresponding FreeBSD manpage for more information on supported chipsets).
The driver-binary has a size of 500 KiB, due to compiling the WiFi-stack into a static library and statically linking it and the FreeBSD compat layer with the driver
There are no settings to set to make this driver work. Just put the driver in /home/config/add-ons/kernel/drivers/bin and make a symlink to /home/config/add-ons/kernel/drivers/dev/net/ath. A reboot could be required to make Haiku recognize the new driver.
X86 64 R47758 硬盘启动死机在第四个图标处 atheros ar9485无线网卡
Very well, closing as invalid as vboxsf is not tracked here.
Fixed in https://bitbucket.org/haikuports/haikuports/commits/1a61a2e2689a66e69394b7f9451911c069d82cdd -- looks like I forgot to close this.
And my bad again -- this is really a duplicate.
When booting haiku-nightly-hrev47649-x86_gcc2_hybrid-anyboot from USB on an Intel i5-4570 with Qualcomm Atheros AR8161/8165 PCI-E Gigabit ethernet controller, a page fault occurs after all the startup icons have lit up.
I'm using a computer with a Matrox G550 PCIe it has two dvi outputs, the problem is that when I switch on the computer the system uses the DVI1, but after the haiku boot screen (the one with the icons atom, disk magnifier, ..., rocket) when it starts the Desktop the DVI1 is switched off and the screen on DVI2 switches on showing the Desktop. (The DVI2 is used even if there are no monitors connected)
Haiku rev 47783
I have an Asus m5a97 evo R2.0 with 2 video cards (a Matrox G550 PCIe and a S3 Chrome S25)
randomly the mouse hangs for some seconds, actually it seems this problem happens when WebPositive is open (and probably when something is highlighted or maybe after using the keyboard).
Maybe enabling the IOMMU in uefi BIOS the problem is less aggressive (but I'm not sure) anyway it's still present.
By removing one video card (S3) the bug vanishes and all seem to go flawlessy.
BTW the video card is not the problem cause it seems that this bug happens to computers with other hardware (ask PulkoMandy).
I'm using 47783 revision
No reply from original poster and no way to reproduce, assuming fixed.