Haiku bugs at boot time (sends me to KDL)

1

Hello, I’ve been trying for a week or so to test out Haiku on a usb key, but haven’t been able to yet. I was told on the forums to file this as a bug, but I can’t find where (devel mailing-list?). Anyways, maybe somebody here can help?

When booting haiku, it kicks me into kdebug land at loading HD time. The error reads: did not find any boot partition.
(Thread 12 “Main2” running on CPU0).

Same problem with r28521 and my current r28633.

So I did my homework, spent lots of time on the IRC channel and really nothing is working. I’ve tested all usb ports, tried booting safemode, updated to latest version etc… Hopefully someone can guide me. I’ve been told to contact mmlbr on the devel list, because he was supposed to have fixed a bug related to my problem.

Here are my syslog results (all pictures obviously, you can zoom in alot for more clairity):

Here is my backtrace:

Here is my lspci, even though I think my hardware is listed in syslog, this list seems a bit more readable:

Edit: My computer is a heavily modified hp pavilion a800n

00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge [1106:3205]
Subsystem: ASUSTeK Computer Inc. Device [1043:8118]
Flags: bus master, 66MHz, medium devsel, latency 8
Memory at e0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [80] AGP version 3.5
Capabilities: [c0] Power Management version 2
Kernel driver in use: agpgart-via
Kernel modules: via-agp

00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237/VX700 PCI Bridge [1106:b198]
Flags: bus master, 66MHz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00009000-00009fff
Memory behind bridge: e4000000-e5ffffff
Prefetchable memory behind bridge: d0000000-dfffffff
Capabilities: [80] Power Management version 2
Kernel modules: shpchp

00:0a.0 Communication controller [0780]: Agere Systems V.92 56K WinModem [11c1:048c] (rev 03)
Subsystem: Agere Systems Device [11c1:044c]
Flags: bus master, medium devsel, latency 32, IRQ 255
Memory at e6000000 (32-bit, non-prefetchable) [size=256]
I/O ports at a000 [size=8]
I/O ports at a400 [size=256]
Capabilities: [f8] Power Management version 2

00:0b.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller [1106:3044] (rev 80) (prog-if 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:808a]
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at e6001000 (32-bit, non-prefetchable) [size=2K]
I/O ports at a800 [size=128]
Capabilities: [50] Power Management version 2
Kernel driver in use: ohci1394
Kernel modules: ohci1394

00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller [1106:3149] (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: ASUSTeK Computer Inc. Device [1043:80ed]
Flags: bus master, medium devsel, latency 32, IRQ 20
I/O ports at ac00 [size=8]
I/O ports at b000 [size=4]
I/O ports at b400 [size=8]
I/O ports at b800 [size=4]
I/O ports at bc00 [size=16]
I/O ports at c000 [size=256]
Capabilities: [c0] Power Management version 2
Kernel driver in use: sata_via
Kernel modules: sata_via

00:0f.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. Device [1043:80ed]
Flags: bus master, medium devsel, latency 32, IRQ 20
[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
[virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
I/O ports at c400 [size=16]
Capabilities: [c0] Power Management version 2
Kernel driver in use: pata_via
Kernel modules: pata_via

00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
Subsystem: ASUSTeK Computer Inc. Device [1043:80ed]
Flags: bus master, medium devsel, latency 32, IRQ 21
I/O ports at c800 [size=32]
Capabilities: [80] Power Management version 2
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd

00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
Subsystem: ASUSTeK Computer Inc. Device [1043:80ed]
Flags: bus master, medium devsel, latency 32, IRQ 21
I/O ports at cc00 [size=32]
Capabilities: [80] Power Management version 2
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd

00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
Subsystem: ASUSTeK Computer Inc. Device [1043:80ed]
Flags: bus master, medium devsel, latency 32, IRQ 21
I/O ports at d000 [size=32]
Capabilities: [80] Power Management version 2
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd

00:10.3 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 81)
Subsystem: ASUSTeK Computer Inc. Device [1043:80ed]
Flags: bus master, medium devsel, latency 32, IRQ 21
I/O ports at d400 [size=32]
Capabilities: [80] Power Management version 2
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd

00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 86) (prog-if 20)
Subsystem: ASUSTeK Computer Inc. Device [1043:80ed]
Flags: bus master, medium devsel, latency 32, IRQ 21
Memory at e6002000 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd

00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] [1106:3227]
Subsystem: ASUSTeK Computer Inc. Device [1043:80ed]
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2
Kernel modules: i2c-viapro

00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 60)
Subsystem: ASUSTeK Computer Inc. Device [1043:810a]
Flags: medium devsel, IRQ 22
I/O ports at d800 [size=256]
Capabilities: [c0] Power Management version 2
Kernel driver in use: VIA 82xx Audio
Kernel modules: snd-via82xx

00:11.6 Communication controller [0780]: VIA Technologies, Inc. AC’97 Modem Controller [1106:3068] (rev 80)
Flags: medium devsel, IRQ 22
I/O ports at dc00 [size=256]
Capabilities: [d0] Power Management version 2
Kernel modules: snd-via82xx-modem

00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102 [Rhine-II] [1106:3065] (rev 78)
Subsystem: ASUSTeK Computer Inc. Device [1043:80ff]
Flags: bus master, medium devsel, latency 32, IRQ 23
I/O ports at e000 [size=256]
Memory at e6003000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2
Kernel driver in use: via-rhine
Kernel modules: via-rhine

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV535 [Radeon X1650 Series] [1002:71c7] (rev 9e)
Subsystem: Hightech Information System Ltd. Device [1787:3000]
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16
Memory at d0000000 (32-bit, prefetchable) [size=256M]
I/O ports at 9000 [size=256]
Memory at e5000000 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at e4000000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Capabilities: [58] AGP version 3.0
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

01:00.1 Display controller [0380]: ATI Technologies Inc RV535 [Radeon X1650 Series] [1002:71e7] (rev 9e)
Subsystem: Hightech Information System Ltd. Device [1787:3001]
Flags: 66MHz, medium devsel
Memory at e5010000 (32-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [50] Power Management version 2

Hope all of this can help. If you need more results or info, please tell me. I will do what is possible to get it. And if I should post this as a bug, I would like to know where to send my report. Thanks again for any help!

2

From the looks of it, the error is in the PCI module. It finds the USB controller, gets an invalid IRQ line and I’m hazarding a guess here that this stops it reporting the USB disk attached.

It then continues the boot process to the part where the root file system is mounted only to find that there is nothing it can boot off of since it doesn’t know about the USB disk.

Definitely a bug which needs reporting. Go to dev.haiku-os.org and make an account there. Then create a new ticket and file it under kernel.

Edit: just realized from your post that it’s a known bug. Try the mailing list option mentioned below first.

Mailing lists are on this page

Hope this helps.

3

Hey, thank you for the answer. It is pretty much as I have been told on IRC channel, except I was told bug #5 was supposed to have been fixed, oh well. I guess I wont bother the mailing lists with another duplicate, but at least I know where to file bugs now :slight_smile:

Have a good day,
Socapex_2K

4

I would still contact mmlbr if you haven’t done already. They might be able to request more information. Unfortunatly I have yet to join the mailing list so I’m not sure how you find the address.

Regardless of the problem thanks for your vigilance in testing the builds. =)

5

I have contacted the dev team. My issue was ticket #5, and it’s not really a bug, but a feature that isn’t implemented yet. Anyway, I got some good help and now I’ve tried haiku for the first time, woohoo!

For anybody with the same issue, your only option is to disable PnP OS in your BIOS. If that doesn’t do it, tough luck. It worked for me though :slight_smile:

Good day,
Socapex_2K

6

This isn’t the place to file a bug. You should open a new ticket here:

http://dev.haiku-os.org/

And delete this.

7

Have you read my post?

Socapex_2K wrote: “I was told on the forums to file this as a bug, but I can’t find where [to file it] (devel mailing-list?).”

Sorry for the mistake, but if you read my latest post, I just mentioned that my problem is ticket #5, which is not a bug, which is itself already blocking 2 tickets. So no need to post another ticket. People on the dev are quite informed on the subject and working on it for R1 (check out the timelist).

If the moderators want to delete my topic they should. But as a beginner to this site, my first reaction was IRC, then here. And who knows, it might help somebody someday?

Regards,
Socapex_2K

8

I find no compelling reason to delete it :slight_smile:

It’s certainly not offensive, and isn’t in a blog or anything.