# downgraded because the image is generally bootable severity 240575 important thanks On Sun, Mar 28, 2004 at 11:20:07AM +1000, Craig Small wrote: > Package: installation-reports > Version: beta 3 > Severity: grave > Justification: renders package unusable > I tried the beta 3 CD on my alpha, it doesn't boot. > Here is what happens from the SRM console, the command I used was > "boot dqb" > (boot dqb1.1.1.208.0 -flags 0) > block 0 of dqb1.1.1.208.0 is a valid boot block > reading 171 blocks from dqb1.1.1.208.0 > bootstrap code read in > vase = 200000, image_start = 0, image_bytes = 15600 > initializing HWRPB at 2000 > initializing page table at ffee000 > initializing machine state > setting affinity to the primary CPU > jumping to bootstrap code > aboot: Linux/Alpha SRM bootloaded version 0.9b > aboot: switching to OSF/1 PALcode version 1.23 > aboot: booting from device 'IDE 0 208 1 1 1 0 0' > cb_open: failed IDE 0 208 1 1 1 0 0, dqb1.1.1.208.0 > aboot: unable to open boot device 'IDE 0 208 1 1 1 0 0': c000000000000000 > aboot: kernel load failed (-1) > halted CPU 0 > halt code = 5 > HALT instruction executed > PC = 2000005c > boot failure (Follow-up info: talking with Craig on IRC, he's verified the md5sum of the image he downloaded. He was using the netinst variant of the beta3 isos.) FWIW, Craig, my test machine is also an AlphaPC 164SX 533, and I don't see *this* problem (just a bunch of others ;). My CD drive is on dqb0 rather than on dqb1; I'll try switching it to a slave configuration, to see if that impacts the bootability of the disks on my system. I don't suppose you have any other SRM-bootable CDs you could compare with, to see whether this is an aboot-specific problem? It does seem to predate d-i, at least: http://www.geocrawler.com/archives/3/86/2001/3/0/5430356/ Also, does booting with 'boot dqb1 -fl i' get you through to the boot menu ok? If you boot '0' from there to load the default kernel, do you get the same error? You mentioned you did get an "Input/output error" when dd'ing from the cdrom device to verify the md5sum; any chance you have a different IDE CDROM you could boot from, to rule out a flaky drive as the cause? If none of the above provides any insight, please check what version of SRM you have loaded on this system. > lspci info > 00:05.0 VGA compatible controller: Cirrus Logic GD 5434-8 [Alpine] (rev fc) > 00:07.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74) > 00:08.0 ISA bridge: Contaq Microsystems 82c693 > 00:08.1 IDE interface: Contaq Microsystems 82c693 > 00:08.2 IDE interface: Contaq Microsystems 82c693 > 00:08.3 USB Controller: Contaq Microsystems 82c693 > 00:09.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] You seem to be one of the lucky ones for whom d-i would work well on alpha, if not for this one issue. :) Cheers, -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature