Opened 14 years ago

Closed 6 years ago

Last modified 5 years ago

#6811 closed bug (invalid)

GCC4H versions constantly rebooting while used from usb pendrive

Reported by: streak Owned by: nobody
Priority: normal Milestone:
Component: System/Boot Loader Version: R1/alpha2
Keywords: Cc:
Blocked By: #2479 Blocking:
Platform: All

Description

I find it really disturbing :/. While all versions of GCC2H / GCC2 are working [and booting from USB drive] fine including hrev39402 / hrev39382 / hrev39360 / hrev39349 / hrev39330 seems that ALL hrev39402 / hrev39382 / hrev39360 / hrev39349 / hrev39330 GCC4H / GCC4 versions are fail to boot from usb. They're just constantly rebooting [i even dont see a haiku splashscreen loaded] after one second after starting PC.

Change History (11)

comment:1 by stargatefan, 14 years ago

Sounds like your thumbdrive is corrupted. I have seen no issues like this and I update with flash drives nearly everyday specifically using gcc4h builds.

What kind of hardware are you running ? This might be a bios setup issue.

comment:2 by streak, 14 years ago

My usb pendrive is ok. I double checked it. I can install on it GCC2 and GCC2H and it works. But with GCC4 will constantly reset haiku.

comment:3 by streak, 14 years ago

BTW. im using the same USB drive for GCC2 and GCC4..

comment:4 by vooshy, 14 years ago

Your issue seems similar to ticket 6710, possibly check the size of the boot logo, but without getting further with the boot, serial output is difficult. Obviously it could be a completly different issue.

comment:5 by mmlr, 14 years ago

Possibly this is the same issue fixed in hrev39961. I wouldn't really see how the host GCC would affect things here, but it's worth at least retesting. Can you please try a current revision and report your findings?

comment:6 by starsseed, 14 years ago

Blocked By: 2479 added

a possible duplicate of #2479

comment:7 by scottmc, 13 years ago

Blocking: 7665 added

comment:8 by pulkomandy, 10 years ago

Blocking: 7665 removed
Milestone: R1Unscheduled

gcc4-only issue, moving out of R1.

Does this still happen btw?

comment:9 by axeld, 8 years ago

Owner: changed from axeld to nobody
Status: newassigned

comment:10 by waddlesplash, 6 years ago

Resolution: invalid
Status: assignedclosed

No reply in 4 years.

comment:11 by nielx, 5 years ago

Milestone: Unscheduled

Remove milestone for tickets with status = closed and resolution != fixed

Note: See TracTickets for help on using tickets.