Hi,
I recently had a problem that forced me to try and boot from CD. It didn't work; it gets as far as the splash screen and then stops. I assumed the boot priority of my HDD was preventing the CD from booting.
I have since sorted that problem, and changed the boot priority on my bootable partition to -1, but I get the same result: the CD starts to boot, gets to the Amiga OS 4.1 Final Edition splash screeen and then stops.
When I built my X5000 last year, I booted from the CD to prep the HDD, so I was able to at some point. I can also boot from the emergency flash drive, provided I select the "Boot from [can't remember the actual term, something like attached storage]" in uBoot. uBoot also has an option to boot from optical, but this just dumps to a command line, so I guess this is a uBoot ENV that I have to set?
My disc was a little scratched, so I burnt a new one on a PC, but same result.
I'd be grateful for any help, I have been seeing some random crashes as of late and would not like to be without an emgerncy boot CD. Like I said, I can boot from flash, although the mouse behaves in an odd fashion that would make using it for recovery tedious.
Unable to boot from CD
Re: Unable to boot from CD
Have changed grachics card after you made your initial installation last year...? The basic RadeonHD driver on the OS4.1 CD does not support models with the Oland Chip set (R7 240/250), thus you cannot boot from the CD.daveyw wrote:Hi,
I recently had a problem that forced me to try and boot from CD. It didn't work; it gets as far as the splash screen and then stops. I assumed the boot priority of my HDD was preventing the CD from booting.
I have since sorted that problem, and changed the boot priority on my bootable partition to -1, but I get the same result: the CD starts to boot, gets to the Amiga OS 4.1 Final Edition splash screeen and then stops.
When I built my X5000 last year, I booted from the CD to prep the HDD, so I was able to at some point. I can also boot from the emergency flash drive, provided I select the "Boot from [can't remember the actual term, something like attached storage]" in uBoot. uBoot also has an option to boot from optical, but this just dumps to a command line, so I guess this is a uBoot ENV that I have to set?
My disc was a little scratched, so I burnt a new one on a PC, but same result.
I'd be grateful for any help, I have been seeing some random crashes as of late and would not like to be without an emgerncy boot CD. Like I said, I can boot from flash, although the mouse behaves in an odd fashion that would make using it for recovery tedious.
- Roland -
Re: Unable to boot from CD
Yes, initial set up was a hassle, went through 3 different GFX cards, but the one I have now isn't the one I did the initial install on.
But my current card is Southern Islands, Radeon 7850.
But my current card is Southern Islands, Radeon 7850.
- tonyw
- AmigaOS Core Developer
- Posts: 1479
- Joined: Wed Mar 09, 2011 1:36 pm
- Location: Sydney, Australia
Re: Unable to boot from CD
Dave-
Make sure that the SD RAM env-var "os4_bootdevice=auto" is set.
Also, remember that the X5k U-Boot can only boot from SATA, not from PCI.
Lastly, do you have a serial terminal available to see what is being spat out during boot?
Make sure that the SD RAM env-var "os4_bootdevice=auto" is set.
Also, remember that the X5k U-Boot can only boot from SATA, not from PCI.
Lastly, do you have a serial terminal available to see what is being spat out during boot?
cheers
tony
tony
Re: Unable to boot from CD
It is set.tonyw wrote:Make sure that the SD RAM env-var "os4_bootdevice=auto" is set.
Yes, my CD drive is connected to the onboard SATA, unit 1.tonyw wrote:Also, remember that the X5k U-Boot can only boot from SATA, not from PCI.
I'll need to get a serial cable.tonyw wrote:Lastly, do you have a serial terminal available to see what is being spat out during boot?
Re: Unable to boot from CD
Have you tested to a) unconnect totally your HD and b) connect your CD drive to Sata 0 port? That way you could exclude any effect caused by your HD and also check whether the Sata port 1 (or cable) has some problem.daveyw wrote:Yes, my CD drive is connected to the onboard SATA, unit 1.
- Roland -
Re: Unable to boot from CD
I tested a) when I had the problem I mentioned above - disconnected my SSD's data cable and was able to boot from CD. This is what led me to think it was the boot priority.Roland wrote:Have you tested to a) unconnect totally your HD and b) connect your CD drive to Sata 0 port? That way you could exclude any effect caused by your HD and also check whether the Sata port 1 (or cable) has some problem.
Re: Unable to boot from CD
Ok, then it is indeed the HD which, some way or another, disturbs booting from the CD drive. I was thinking of a situation where the Kickstart is loaded from different volume than Workbench. That may sometimes cause similar problems you have ...daveyw wrote:I tested a) when I had the problem I mentioned above - disconnected my SSD's data cable and was able to boot from CD. This is what led me to think it was the boot priority.Roland wrote:Have you tested to a) unconnect totally your HD and b) connect your CD drive to Sata 0 port? That way you could exclude any effect caused by your HD and also check whether the Sata port 1 (or cable) has some problem.
If you set in UBoot the variable "amigaboot_quiet" to "N", you should see listed all the bootable volumes before Kickstart is loaded, and be able to select any of them, independently of boot priorities. What if you try to boot from CD via this way, does it make any difference?
- Roland -
Re: Unable to boot from CD
Here's my output from uboot:
I disabled amigaboot_quiet and tried to select the CD on boot, but same result.
While I had my A1-XE up and running to do this, I double checked that it could boot from CD (it can), and checked the boot priority. It had a 5 (and 4 for a back-up partition), so I tried that priority, but it made no difference.
Code: Select all
U-Boot 2014.04 (Oct 17 2016 - 08:22:22)
CPU0: P5020, Version: 2.0, (0x82200020)
Core: e5500, Version: 1.2, (0x80240012)
Clock Configuration:
CPU0:1995 MHz, CPU1:1995 MHz,
CCB:798 MHz,
DDR:665 MHz (1330 MT/s data rate) (Asynchronous), LBC:49.875 MHz
FMAN1: 498.750 MHz
QMAN: 399 MHz
PME: 399 MHz
L1: D-cache 32 KiB enabled
I-cache 32 KiB enabled
Reset Configuration Word (RCW):
00000000: 0c540000 00000000 1e1e0000 00000000
00000010: 44808c00 ff002000 68000000 45000000
00000020: 00000000 00000000 00000000 0003000f
00000030: a0000000 00000000 00000000 00000000
Board: CYRUS
36-bit Addressing
I2C: ready
SPI: ready
DRAM: Initializing....using SPD
Detected UDIMM CT51264BD160BJ.C8F
Not enough bank(chip-select) for CS0+CS1 on controller 0, interleaving disabled!
There is no rank on CS0 for controller 1.
Not enough bank(cct) for CS0+CS1 o controller 1, interleaving disabled!
Not all controllers have compatible interleaving mode. All disabled.
2 GiB left unmapped
4 GiB (DDR3, 64-bit, CL=9, ECC off)
Local Bus Controller Registers
BR0 0xE0001001 OR0 0xFFF00010
BR1 0xE1001001 OR1 0xFFF00010
BR2 0x00000000 OR2 0x00000000
BR3 0x00000000 OR3 0x00000000
BR4 0x00000000 OR4 0x00000000
BR5 0x00000000 OR5 0x00000000
BR6 0x00000000 OR6 0x00000000
BR7 0x00000000 OR7 0x00000000
LBCR 0x40000000 LCRR 0x80010004
L2: 512 KiB enabled
Corenet Platform Cache: 2 MiB enabd
SERDES: bank 2 disabled
MMC: FSL_SDHC: 0
EEPROM: NXID v0
PCIe1: Root Complex, x4 gen2, regs @ 0xfe200000
01:00.0 - 1002:6819 - Display controller
01:00.1 - 1002:aab0 - Multimedia device
PCIe1: Bus 00 - 01
PCIe2: Root Complex, x4 gen2, regs @ 0xfe201000
03:00.0 - 111d:8092 - Bridge device
04:01.0 - 111d:8092 - Bridge device
05:00.0 - 12d8:e111 - Bridge device
06:04.0 - 1095:3112 - Mass storage controller
06:05.0 - 10ec:8169 - Network controller
04:02.0 - 111d:8092 - Bridge device
07:00.0 - 1b21:1080 - Bridge device
08:00.0 - 13f6:0111 - Multimedia device
08:00.1 - 13f6:0211 - Simple comm. controller
04:03.0 - 111d:8092 - Bridge device
04:08.0 - 111d:8092 - Bridge device
04:10.0 - 111d:8092 - Bridge device
PCIe2: Bus 02 - 0b
PCIe3: disabled
PCIe4: disabled
Looking for VGA
PINS: 0xfc000808
videoboot: Booting PCI video card bus 1, function 0, device 0
Begin BIOS POST
End BIOS POST
Setting VESA Mode
Found required VESA mode
About to set mode 279
About to get mode
Got mode 49431 (0xc117)
OK
XSize = 1024 YSize = 768 Base =0xe0000000
mmio_base = 0x80000000
bgx = 0xad55ad55 fgx = 0x0
In: serial
Out: serial
Err: serial
ID: NXID v0
SN: 116330047
UID: 4429431001910051847ea080a0800000
Errata: T
Build date: 2015/06/17 09:09:54
CRC: 7820fe40
SCSI: scanning bus for devices...
Found 0 device(s).
Net: Initializing Fman
MMC read: dev # 0, block # 1130, 28 ...
Fman1: Uploading microcode version 106.1.0
Tuning PHY @ 3
Tuning PHY @ 7
FM1@DTSEC4 [PRIME], FM1@DTSEC5
MMC read: dev # 0, block # 1280, count 512 ... 512 blocks read: OK
MMC read: dev # 0, block # 65536, count 131072 ... 131072 blocks read: OK
USB0: USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
USB1: USB EHCI 1.00
scanning bus 1 for devices... 2 USB Device(s) found
SATA0 (3 Gbps)
SATA1 (1.5 Gbps)
CE at device
scanning bus for devices...
Device 0: (1:0) Vendor: HL-DT-ST Prod.: DVDRAM GH22NS50 Rev: TN03
Type: Removable CD ROM
Capacity: 547.5 MB = 0.5 GB (280367 x 2048)
Found 1 device(s).
## Starting application at 0x00200000 ...
[0;0H[2J31mAmigaOS 4.x U-Boot Bootloader V53.21[0m
[3;1H
Please choose a configuration to boot:
1: AmigaOS 4.1 Final Edition [0m (Volume DH0X)
2: AmigaOS 4.1 Final Edition [0m (Volume DH0)
> 3: AmigaOS 4.1 Final Edition [0m (Volume AmigaOS 4.1 Final Edition)
[33m[RETURN][0m Boot default [33m[SPACE][0m Stop Countdown
Move default [33m[UP][0m or [33m[DOWN][0m with arrows
[33m[123][0m Boot appropriate config
(5 sec. until autoboot)> (4 sec. until autoboot)> (3 sec. until autoboot)> (2 sec. until autoboot)> (1 sec. until autoboot)> (0 sec. until autoboot)>
(Booting default)
Booting configuration AmigaOS 4.1 Final Edition
Loading loader [----------------------------------------] 0 %Loading kernel.debug [----------------------------------------] 1 %Loading FastFileSystem [#---------------------------------------] 3 %Loading CDFileSystem [##--------------------------------------] 5 %Loading NGFileSystem [##--------------------------------------] 7 %Loading battclock.resourc... [###-------------------------------------] 8 %Loading bootmenu.kmod [####------------------------------------] 10 %Loading bootimage [#####-----------------------------------] 12 %Loading bootsd.resource.k... [#####-----------------------------------] 14 %Loading con-handler.kmod [######----------------------------------] 16 %Loading console.device.kmod [#######---------------------------------] 17 %Loading dos.library.kmod [#######---------------------------------] 19 %Loading diskboot.kmod [########--------------------------------] 21 %Loading diskboot.config [#########-------------------------------] 23 %Loading elf.library.kmod [##########------------------------------] 25 %Loading env-handler.kmod [##########------------------------------] 26 %Loading FileSystem.resour... [###########-----------------------------] 28 %Loading gadtools.library.... [############----------------------------] 30 %Loading hunk.library.kmod [############----------------------------] 32 %Loading input.device.kmod [#############---------------------------] 33 %Loading intuition.library... [##############--------------------------] 35 %Loading keyboard.device.k... [###############-------------------------] 37 %Loading keymap.library.kmod [###############-------------------------] 39 %Loading mounter.library [################------------------------] 41 %Loading newlib.library.kmod [#################-----------------------] 42 %Loading nonvolatile.libra... [#################-----------------------] 44 %Loading petunia.library.k... [##################----------------------] 46 %Loading ram-handler.kmod [###################---------------------] 48 %Loading ramdrive.device.k... [####################--------------------] 50 %Loading ramlib.kmod [####################--
About to call loader entry at 0x7BD02020
While I had my A1-XE up and running to do this, I double checked that it could boot from CD (it can), and checked the boot priority. It had a 5 (and 4 for a back-up partition), so I tried that priority, but it made no difference.