@nbache

If I reset the A1 and disable the second IDE-port in U-Boot menu, it boots fast and nicely, but if I enable the second IDE-port with an Acer CDRW drive attached, it doesn't boot anymore (ok, it sort of does, but it takes ages and then OS4 feels like something is performing a busy-wait loop at the highest priority). Resetting the A1 and disabling the second IDE-port makes OS4 boot as normal again. I assume a1ide.device just don't like the CDRW drive since it wrongfully thinks I've made a diskchange (have a look at the serial output I've pasted in a post above) without me neither touching the drive, nor having a CD in it in the first place.

It's probably the same issue people are having with various brands of CD-drives which can't even be used to install OS4. I'll just have to live without a CDRW until this issue gets fixed in OS4, assuming someone figures out why it fails with many drives.

@Niolator

* You need to check if you HD0 has boot option enabled, if not boot from the install CD and fix the problem, use ffs/7 and not ffs/3

if you insert a CD, use ide reset to rescan the ide bus.

* You need to check that you gfx card is pluged inn,

* You need to check the boot1 inn uboot, use printenv boot1, you need to boot AmigaOS whit boota and not boot.

* You need to check uboot options are they correct? use the PDF as guide line for the settings.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@AmiDog

Quote:

This is my IDE unit setup: Primary master: 80GB Hitachi harddrive. Primary slave: Samsung DVD-ROM. Secondary master: Acer CD-RW. Secondary slave: none.

Compare with mine:

Primary master: 120GB IBM harddrive.
Primary slave: Western Digital 160GB harddrive
Secondary master: NEC DVD+RW
Secondary slave: Hitachi CD-ROM.

I have not had any problems with this setup, neither in Linux or in OS4.

Try with a setup change to this:

Primary master: 80GB Hitachi harddrive.
Primary slave: none
Secondary master: Acer CD-RW.
Secondary slave: Samsung DVD-ROM


Try with cable-select too.

_________________
Site admins are people too..pooff!

@Juzz

Quote:

setenv ide_config 1200

That won't work - its ide_conf


@AmiDog

For the following config:

Primary master: 80GB Hitachi harddrive.
Primary slave: Samsung DVD-ROM.
Secondary master: Acer CD-RW.
Secondary slave: none.


In UBoot, try the following:

setenv ide_conf 1220
saveenv

and reboot. That will stop a1ide from trying to determine the drive type thats connected, and instead force it to use a HDD, CD/DVD, CD/DVD and Nothing for the devices connected. Just remember if you change the drive layouts to change the ide_conf variable!

@Rogue

Quote:

Quote: I doubt it´s the harddrive, I have cleaned it, there is nothing on it and the Debian CD boots fine I'm getting confused. You say that U-Boot cannot see the CD-Rom but the Debian CD boots fine? How is that possible?

I of course have the HD connected when I try this (remember that it sees the CD-rom just fine when the harddrive is present).

Quote:

Quote: The HD led doesn´t even blink when the kickstart is loading so I don´t think the hardrive is even accessed before everything stops. Ugh, where is it loading the kickstart from, then?

From the CD of course...


I have the CD-rom set as Master, maybe I should try Slave? For the U-boot to see the CD-rom whitout the HD connected I mean. Or maybe I should try to format he HD? It´s unformatted now. But as I say, it ain´t even trying to read from the HD.

I am more and more convinced that it´s the U-boot. Now I have checked how the AmigaOne acts with another CD-rom drive. I checked it with the DVD drive I have in my PC. It stops at exactly the same spot. The U-boot couldn´t see this one either if I didn´t have the harddrive connected. If it doesn´t work with the new U-boot I have ordered I guess I will have to get a serial cable...

@Niolator

Quote:

The problem is that U-boot can´t see the CD-rom if I don´t have the harddrive connected, no matter how I connect it. The CD-rom worked fine before so that should not be the reason.

Did you re-jumper your CD-ROM to master ? Otherwise, it's no wonder you don't see a CD-ROM... you can't run only a slave, a master must be present.

_________________
Thomas, the kernel guy

"I don't have a frigging clue. I'm norwegian" -- Ole-Egil

All opinions expressed are my own and do not necessarily represent those of Hyperion Entertainment

@Niolator

Quote:

The U-boot couldn´t see this one either if I didn´t have the harddrive connected.

How is your cabling? The master always goes at the far end of the cable, and the long end of the cable goes to the mainboard. Make sure that you have connected it to the right IDE port.

What do you mean with "couldn't see this"? Please quote the output of "ide reset".

Quote:

If it doesn´t work with the new U-boot I have ordered I guess I will have to get a serial cable...

I doubt it's U-Boot. If there was something wrong with your rom it would most likely not boot at all. I can only repeat again that a serial cable is the best debugging aid in this case, and you should really look at this first.

_________________
Seriously, if you want to contact me do not bother sending me a PM here. Write me a mail

@Niolator

Quote:

I am more and more convinced that it´s the U-boo

If it stops at "kickstart loaded...", then it's definitely *NOT* U-Boot. At that point in time, U-Boot is a goner.

If the screen stays in text mode, it's the graphics card.

You never said what graphics card you have ?

Quote:

If it doesn´t work with the new U-boot I have ordered

Does that mean you ordered a new ROM chip ? What for ? If your machine boots, the ROM is ok, and no new chip will change that.

Believe me, it's _NOT_ U-Boot. Please tell me what graphics card you have.

_________________
Thomas, the kernel guy

"I don't have a frigging clue. I'm norwegian" -- Ole-Egil

All opinions expressed are my own and do not necessarily represent those of Hyperion Entertainment

@Niolator

Quote:

Isn´t there any possibility to start AmigaOS 4.0 in a safemode?[

What is "save mode" ?

If you boot from the CD, you'll boot into a defined environment. That's all the safe mode you need.

_________________
Thomas, the kernel guy

"I don't have a frigging clue. I'm norwegian" -- Ole-Egil

All opinions expressed are my own and do not necessarily represent those of Hyperion Entertainment

@EntilZha

I always have the CD-rom set as master as I have it on a separate cable from the HD and I have it cabled as Rouge described.

If I take out the HD the U-boot detects nothing on any position of any cable, I havent tried ide reset though I just see what it reads when I boot up, I will try to ide reset the next time but I doubt it will help.

I use a Radeon 9100 128 Mb but that worked fine before, I have a serial cable that might work, otherwise I´ll have to buy one on monday (there are national holidays today and tomorrow here in Sweden).

If it´s not the U-boot I guess I have to send it back before opening the package. But why should the graphics card start acting up suddenly? Surely that can not be damaged by shutting down at the wrong moment?

@EntilZha

Quote:

If the screen stays in text mode, it's the graphics card.

I don´t think it´s the graphics card. I have now tested with another graphics card, a Voodoo 3/3000 but it´s the same thing. I even removed my Soundcard (a Soundblaster 128) to see if that caused the problem, no effect.

It is obvious that you are very convinced that it isn´t the U-boot that´s causing the problem as the boot sequnce have passed the U-boot a long time ago when it reaches where it all stops. What if it has given the wrong information earlier and that is what´s destroying the boot up at that later moment?

The cable I have is of the wrong type so I´ll have to wait untill monday.

@Vader

I tried your suggestion and it did have some kind of effect. OS4 booted a lot faster, but it still made some weird pauses when browsing the harddrive and Media Toolbox didn't find the CDRW. I guess that whatever U-Boot does right to find the CDRW, a1ide.device does wrong... I'll just wait for the OS4pre update, maybe it'll fix things...

@Niolator

Did you get my PM? Also drop sometimes by in the #AmigaOS4 room. And also have your HD on a separate cable and also the cdrom drive on a separate cable. And make SURE the cdrom drive is secondary master! But like I said, drop by the OS4 room and it talkes much better.

Coder

_________________
Can't get enough of me?
The Bucket Diary Blog
The Bucket Diary Twitter Account

@Coder

That´s an IRC-channel, right? I am not so familiar with IRC but if I don´t make any progress elsewhere I guess I have to become familiar with it...

Sorry that I didn´t answer your PM, I didn´t notice it. I am used to a swedish Amiga forum where you get a blinking icon when you log in if you have a private message. I´ll be more watchful in the future.

Anyway, I have now gotten hold of a serial cable and here is what the output of that says:

Quote:

U-Boot 1.0.0 (Apr 12 2004 - 14:05:39), Build: 04/12/04 CPU: MPC7455 v2.1 @ 800 MHz Board: AmigaOne DRAM: 256 MB FLASH: 0 kB VGA: OK In: serial Out: serial Err: serial ] boota Loading .text @ 0x014000a0 (29632 bytes) Loading .rodata @ 0x01407460 (2273 bytes) Loading .data @ 0x01417d44 (448 bytes) Loading .got2 @ 0x01417f04 (728 bytes) Loading .sdata @ 0x014181dc (16 bytes) Clearing .sbss @ 0x014181f0 (204 bytes) Clearing .bss @ 0x014182bc (3852 bytes) A1 Second-level booter V2. Idea, design and main code: Andrea Vallinotto. Testing and fixes: Stefan Burstroem SFS and ISO9660 reading rout Linux booting extensions: Andrea and the GRUB team. Booting configuration Default OS4 kernel panic! Caught ISI exception System Halted r0 -r7 : 01A10414 01414E90 00000400 014C08F0 01414ED8 014E2330 00010001 FFF00000 r8 -r15: FFFFFFFF 00000069 014C08F0 00022047 28004024 00000000 0FFB8200 10056000 r16-r23: 00000000 00000000 00000000 00000258 00000000 00001810 FFFFFFBA 01430000 r24-r31: 00001808 01440000 01440000 00000000 01414ED8 0142D620 014C08F0 014E2330 LR: 01218EFC XER: 20000000 CTR: FFFE9537 DSISR: 00000000 DAR: 00000000 DEC: F8A31530 SDR1: 0100001F SRR0: 01A10414 SRR1: 10003030 TBL: 62FFCD96 TBU: 00000001 EAR: 00000000 HID0: 840000BC HID1: 0001A880 IBAT0: 0120003F - 01200002 IBAT1: 00000000 - 00000000 IBAT2: 00000000 - 00000000 IBAT3: 00000000 - 00000000 DBAT0: 00000000 - 00000000 DBAT1: 00000000 - 00000000 DBAT2: 00000000 - 00000000 DBAT3: F0001FFF - F000002A MSR: 00001000 CR: 42004023 Disassembly of crash site: 01A1040C: 00000000 .word 0x00000000 01A10410: 40000000 bdnzf- 0 >01A10414: 00000000 .word 0x00000000 01A10418: 00000000 .word 0x00000000 01A1041C: 00010000 .word 0x00010000 01A10420: 00000000 .word 0x00000000

Kernel panic sounds bad, that indicates overheating on Linux doesn´t it? Maybe my change of fan didn´t go so well after all?

@Niolator

Yup, IRC. So this output is from booting Linux or an install (Linux) cd? What is the output when booting the OS4 cd?

Coder

_________________
Can't get enough of me?
The Bucket Diary Blog
The Bucket Diary Twitter Account

@Coder

It is the output from booting the AOS 4.0 Pre-release CD...

@Niolator

Quote:

It is the output from booting the AOS 4.0 Pre-release CD...

Ok. I am sure the Frieden brothers can answer this one.

Coder

_________________
Can't get enough of me?
The Bucket Diary Blog
The Bucket Diary Twitter Account

@Niolator

Please repeat that test, with a debug config, and setting "debuglevel=10" in the boot options menu.

_________________
Seriously, if you want to contact me do not bother sending me a PM here. Write me a mail

@Rogue

OK, here it comes:

Quote:

U-Boot 1.0.0 (Apr 12 2004 - 14:05:39), Build: 04/12/04 CPU: MPC7455 v2.1 @ 800 MHz Board: AmigaOne DRAM: 256 MB FLASH: 0 kB VGA: OK In: serial Out: serial Err: serial ] boota Loading .text @ 0x014000a0 (29632 bytes) Loading .rodata @ 0x01407460 (2273 bytes) Loading .data @ 0x01417d44 (448 bytes) Loading .got2 @ 0x01417f04 (728 bytes) Loading .sdata @ 0x014181dc (16 bytes) Clearing .sbss @ 0x014181f0 ( Clearing .bss @ 0x014182bc (3852 bytes) A1 Second-level booter V2. Idea, design and main code: Andrea Vallinotto. Testing and fixes: Stefan Burstroem SFS and ISO9660 reading routines: Joerg Strohmayer. Linux booting extensions: Andrea and the GRUB team. Booting configuration Debug [ColdStart] ExecSG [ColdStart] Copyright (c) 2002-2004 Thomas and Hans-Joerg Frieden [HAL_InitCPU] Initializing CPU specific code [HAL_InitCPU] Selecting 745x/744x Apollo cache code [HAL_GetMemoryMap] Physical memory start: 0x00000000 [HAL_GetMemoryMap] Physical memory on board: 256 MB [HAL_GetMemoryMap] Kernel text base: 0x01200000 [HAL_GetMemoryMap] Physically mapped memory @ 0x014D0000 size 3E60000 [HAL_GetMemoryMap] Page area 1 @ 0x05330000 size 181207040 (2765 pages) [HAL_GetMemoryMap] Page area 2 @ 0x00010000 size 16711680 (255 pages) [HAL_GetMemoryMap] Node 0 (expansion memory, KERNEL): 0x014D0000 - 0x0532FFFF [HAL_GetMemoryMap] Node 1 (virtual memory, PAGES): 0x05330000 - 0x0FFFFFFF [HAL_GetMemoryMap] Node 2 (virtual memory, PAGES): [HAL_GetMemoryMap] Node 3 (IO area, IO): 0x80000000 - 0xFFFFFFFF [HAL_GetMemoryMap] Node 4 (executable memory, EXECUTABLE): 0x70000000 - 0x7FFFFF FF [HAL_GetMemoryMap] Node 5 (virtual memory, VIRTUAL): 0x10000000 - 0x6FFFFFFF [ColdStart] g_pMemoryMap == 0x01413910 [HAL_SetupMMU] Setting up MMU [HAL_SetupMMU] MMUtable base address: 0x01000000 [HAL_SetupMMU] MMUtable size: 0x00200000 [HAL_SetupMMU] HTABORG = 0x01000000, HTABMASK = 0x0000001F, SDR1 = 0x0100001F [HAL_SetupMMU] Executable segment at 7 [HAL_SetupMemoryEnvironment] Setting up memory environment [HAL_SetupMemoryEnvironment] Turning off MMU [HAL_SetupMemoryEnvironment] Removing BAT mappings [HAL_SetupMemoryEnvironment] textSize == 0x001FFFFF, batval = 0x0000003C [HAL_SetupMemoryEnvironment] Setting up default mapping [HAL_SetupMemoryEnvironment] Restarting MMU [HAL_SetupMemoryEnvironment] Environment setup complete [AddMemListInternal] base = 0x014D0000 [AddMemListInternal] size = 65404928, adjusted size = 65404896 [ColdStart] Kernel memory area: [ColdStart] AbsExecBase points to 0xFDFFEFFF [ColdStart] No ExecBase found [ColdStart] Memory map: [ColdStart] expansion memory Kernel 0x014D0000 - 0x0532FFFF [ColdStart] virtual memory Pages 0x05330000 - 0x0FFFFFFF [ColdStart] virtual memory Pages 0x00010000 - 0x00FFFFFF [ColdStart] IO area I/O 0x80000000 - 0xFFFFFFFF [ColdStart] executable memory Executable 0x70000000 - 0x7FFFFFFF [ColdStart] virtual memory Virtual 0x10000000 - 0x6FFFFFFF [ColdStart] ExecBase starts at 0x014D03B2, top=0x014D0DB0, bottom=0x014D0028 [ColdStart] Vector table has 151 entries [ColdStart] Filling ExecBase (allocated at 0x014D03B2) [HAL_GetAttnFlags] Detected 745x/744x with AltiVec (Apollo, Silicon revision 2.1 ) [ColdStart] Adding memory lists [ColdStart] Adding memory area virtual memory (0x05330000 - 0x0FFFFFFF) as page memory [AddPhysicalMemory] Adding physical memory area at 0x05330000, size 181207040 [AddPhysicalMemory] Initializing [AddPhysicalMemory] Number of p [AddPhysicalMemory] Allocating bitmap (size 345, leftover 5, realsize 346) [AddPhysicalMemory] Initializing bitmap [AddPhysicalMemory] Done [ColdStart] 2765 pages in region virtual memory [ColdStart] Adding memory area virtual memory (0x00010000 - 0x00FFFFFF) as page memory [AddPhysicalMemory] Adding physical memory area at 0x00010000, size 16711680 [AddPhysicalMemory] Initializing [AddPhysicalMemory] Number of pages: 255 [AddPhysicalMemory] Allocating bitmap (size 31, leftover 7, realsize 32) [AddPhysicalMemory] Initializing bitmap [AddPhysicalMemory] Done [ColdStart] 255 pages in region virtual memory [ColdStart] Replacing StackSwap [ColdStart] Replacing AddIntServer [ColdStart] Replacing RemIntServer [ColdStart] Replacing SetIntVector [ColdStart] Replacing SuperState [ColdStart] Replacing UserState [ColdStart] Replacing Supervisor [ColdStart] Replacing SetTaskTrap [ColdStart] Creating primary interface (vectors at 0x0143B634) [ColdStart] Main interface created at 0x014D08F0 [ColdStart] Creating utility interface (vectors at 0x0143B964) [ColdStart] Creating kernel stack [HAL_CreateKernelStack] Kernel stack allocated at 0x014D0D80 [HAL_CreateKernelStack] Kernel stack pointer 0x014F0D90 [ColdStart] Calibrating time base [HAL_CalibrateTimer] Frontside bus frequency: 133 MHz [HAL_CalibrateTimer] Internal frequency: 800 MHz [ColdStart] 3020 pages available for virtual addressing architecture [ColdStart] Setting up virtual memory system [AddVMArea] VMArea initialized: [AddVMArea] Attribut [AddVMArea] Flags: 0x00000000 [AddVMArea] Lower: 0x70000000 [AddVMArea] Upper: 0x7FFFFFFF [ColdStart] Added executable range 0x70000000 - 0x80000000 [AddVMArea] VMArea initialized: [AddVMArea] Attributes: 0x00001808 [AddVMArea] Flags: 0x00000000 [AddVMArea] Lower: 0x10000000 [AddVMArea] Upper: 0x6FFFFFFF [ColdStart] Added primary virtual memory area [AddVMArea] VMArea initialized: [AddVMArea] Attributes: 0x00001D07 [AddVMArea] Flags: 0x00000000 [AddVMArea] Lower: 0x014D0020 [AddVMArea] Upper: 0x0532FFFF [ColdStart] Added 'expansion memory' as legacy to memory system [AddVMArea] VMArea initialized: [AddVMArea] Attributes: 0x00000000 [AddVMArea] Flags: 0x00000001 [AddVMArea] Lower: 0x01400000 [AddVMArea] Upper: 0x014CFFFE [HAL_SetupMemoryEnvironment2] Kernel data segment VMArea created [AddVMArea] VMArea initialized: [AddVMArea] Attributes: 0x00000010 [AddVMArea] Flags: 0x00000001 [AddVMArea] Lower: 0x01200000 [AddVMArea] Upper: 0x013FFFFE [HAL_SetupMemoryEnvironment2] Kernel text segment VMArea created [AddVMArea] VMArea initialized: [AddVMArea] Attributes: 0x00000000 [AddVMArea] Flags: 0x00000001 [AddVMArea] Lower: 0x00DFF000 [AddVMArea] Upper: 0x00DFFFFF [HAL_SetupMemoryEnvironment2] Custom chip interceptor VMArea created [AddVMArea] VMArea initialized: [AddVMArea] Attributes: 0x00000000 [AddVMArea] Flags: 0x00000001 [AddVMArea] Lower: 0x00BF0000 [AddVMArea] Upper: 0x00BFFFFF [HAL_SetupMemoryEnvironment2] Custom chip interceptor VMArea created [HAL_7450CacheControl] 7450CacheControl(40000101, 40000101) [HAL_7450CacheControl] Turning ICache on [HAL_7450CacheControl] Turning DCache on [HAL_7450CacheControl] rethinkl2 = 2 [HAL_7450CacheControl] cacheMask = 0x40000101, cacheBits = 0x40000101 [HAL_7450CacheControl] Turning L2 cache on [_impl_CacheControl] Old cache settings (0x0): DCache off, ICache off [ColdStart] CPU initialisation, stage 2 (CPU special feature setup) [HAL_InitCPU2] Setting up CPU-Specific features [ColdStart] CPU initialisation, stage 2 finished [ColdStart] Scanning ROM tags [FindAllTags] Scanning for resident tags: 0x01400000 - 0x014CFFFF OS4 kernel panic! Caught ISI exception System Halted r0 -r7 : 01A14DFC 01423450 00000400 014D08F0 014234D8 014F2450 00010001 00000000 r8 -r15: 01423420 0000004F 0000000A 00022167 01423440 00000000 00000000 00000000 r16-r23: 01410000 01410000 01410000 01410000 01410000 01440000 014234D8 0000000F r24-r31: 014234D8 01440000 01410000 01410000 0143BCE4 014D08F0 01447438 014F2450 LR: 0122EE88 XER: 20000000 CTR: 00000000 DSISR: 00000000 DAR: 00000000 DEC: E5DC90A7 SDR1: 0100001F SRR0: 01A14DFC SRR1: 10003030 TBL: 4FADE8A3 TBU: 00000001 EAR: 00000000 HID0: 840000BC HID1: 0001A880 IBAT0: 0120003F - 01200002 IBAT1: 00000000 - 00000000 IBAT2: 00000000 - 00000000 IBAT3: 00000000 - 00000000 DBAT0: 00000000 - 00000000 DBAT1: 00000000 - 00000000 DBAT2: 00000000 - 00000000 DBAT3: F0001FFF - F000002A MSR: 00001000 CR: 40004023 Disassembly of crash site: 01A14DF4: 00000002 .word 0x00000002 01A14DF8: 00001000 .word 0x00001000 >01A14DFC: 00000000 .word 0x00000000 01A14E00: 00004002 .word 0x00004002 01A14E04: 00000000 .word 0x00000000 01A14E08: 00020000 .word 0x00020000

I really appriciate that you are trying to help me, I just hope you succeed.