Hi,

Is my PegII dying?
I got everytime when trying to start my PegII the following message:

General device failure
The device is not in an invalid state
errorcode =45
io_command = 2
io_Offset = 24110080
etc.

I tried to format a new Harddisk, but while copying the Morphos-stuff I got everytime this message....
Starting for the CD is no problem. Everything seems to work fine.....

even Icedoctor is of no use....

What is going wrong?

regards Tom

try to change the cable... i used to have simmilar problems, and after ide cable exchange it's okay...

bye, MarK.

I will give it a try and buy a new cable.
But I exchanged already the 2 cables and that didn't work.
Formatting is no problem, but installing (writing stuff) gives all trouble.
My wife already bought me a new computer (for christmas) and my son installed linux on it, but I miss my Peg dearly.....

Regards Tom

Sorry for answering so late.
I changed the cables and now my Peg most of the time starts, but not always.
To start booting from the HD (starting from the CD is now mostly no problem) I have to type every time in the firmware 'boot /pci/ide/disk@0,0:dho boot.img'. It doesn't start in a normal automatic way. What can be the problem?
I'm using a new formatted ata-disk with 4 partitons and only one partiton is bootable(SFS).

regards Tom

Normaly the path to your boot-parition should be defines in firmware env-variables and devalias. If this already set to factory-state and not modyfied, than the path should be only <boot ide:0 boot.img.......> for the first partition on your HD. You can check this by typing printenv and devalias in OF. How to set these variables you will find in SmartFirmware-Manual, located on your MOS-CD.
Most users uses a bootscript for booting different OS, written in forth (this is the intepreter language which can be run by OF) like this:

\ FORTH - Script created by BootCreator (MorphOS) 0.6 (Jul 2 2004) by Marcin Kurek (Morgoth/D-CAPS)
\
\ terminal control stuff
\
: TTY.CSI d# 27 EMIT ASCII [ EMIT ;
: TTY.HOME TTY.CSI ASCII H EMIT ;
: TTY.CLR_EOS TTY.CSI ASCII J EMIT ;
: TTY.HOME_CLR TTY.HOME TTY.CLR_EOS ;
\
\ boot menu stuff
\
: my-max-boot-num 6 ;
: my-boot-default 1 ;
: my-boot-delay d# 100 ; \ unit = 100 ms
: my-print-menu ( -- )
TTY.HOME_CLR
." Wellcome to PEGASOS PowerPC Core-Menue V1.01" cr
." " cr
." Open Firmware booting complete - please select your prefered system: " cr
." " cr
." Bootselector-Menu" cr
." " cr
." 1: Harddisk -> MorphOS (default)" cr
." 2: Harddisk -> Debian GNU/Linux" cr
." 3: Harddisk -> CD32 Emulation" cr
." 4: CD-ROM -> MOL (Mac on Linux/Ubuntu) Insert Live-CD first!!" cr
." 5: CD-ROM -> MorphOS emercency (Insert CD MorphOSBoot first)" cr
." 6: Any other key -> **Break** (Return to Open Firmware) " cr
." " cr
." Boot MorphOS (last working config) from build-in ROM: Type <boot cf> in OF" cr
." " cr
;
: my-boot-case ( num -- )
." " cr
case
1 of " ide:0 boot.img rd rds 1" endof
2 of " ide:0 vmlinuz-2.6.18-5 root=/dev/hda9" endof
3 of " ide:0 cd32" endof
4 of " cd install/pegasos" endof
5 of " boot cd boot.img" endof
6 of " none" endof
endcase
['] $boot catch drop
user-abort
;
: my-input-num ( wait-period max-boot-num default-num -- boot-num )
1 \ loop-inc = 1
3 pick 0 do
0d emit
." Press key 1-"
( wait-period max-boot-num default-num loop-inc )
2 pick ascii 0 + emit
dup 1 = if
." during the next "
3 pick i - d# 10 / .d
." seconds"
then
." (Default: "
over ascii 0 + emit
." ) : "
d# 100 ms
key? if
key
( wait-period max-boot-num default-num loop-inc key )
dup 0d = if \ return pressed
drop leave
then

ascii 0 -
( wait-period max-boot-num default-num loop-inc num )
dup 1 5 pick
( wait-period max-boot-num default-num loop-inc num num 1 max-boot-num )
between if
rot drop swap leave
then

( wait-period max-boot-num default-num loop-inc num )
TTY.HOME_CLR abort ( -- )
then
dup +loop
drop
( wait-period max-boot-num boot-num )
nip nip
;

my-print-menu
my-boot-delay my-max-boot-num my-boot-default my-input-num
my-boot-case

Look at this code- its easy to understand. Your pathes have to be changed in the "case"-block....
If you use this then save the bootscript as ASCII(Text)-file on your boot-partition and name it "menu". Then set env-variable "boot-file" to "menu". Boot-command will then execute the menu-file.....
If you don't need so many entries, then delete them and reduce my-max-boot-num to your propper value.......
If you use this bootscript you can do following in OF-variables:
To shorten boot time you can set auto-boot-timeout to 2000 or 1500 (auto-boot should be set true...).






[ Editiert durch Amigaharry2 04.02.2012 - 14:17 ]

Very weird

Are you using 80 wire cables? are they round? If so use flat.

Also, did you try a diff cd rom.

The psu could also not be supplying enough voltage on 12v rails.

HI,

well, two months ago I had a severe crash. HD1 isn't usable anymore (I tried even on a linux computer) but HD2 is now working sometimes. The new HD is since today up for one whole day. Booting up with 'boot ide:0 boot.img' works fine. So today I will take a look in setenv and devalias. But perhaps it is better to wait for my son, he knows a lot more of computers than I do..
Ik will also look for an other powersupply, the one used is rather old. And yes, I use flat cables.

thanks for you help, Tom

check out also the maxtransfer value in partition definition... should be 0x0001fe00.

bye, MarK.

This won't influence OF-bootcommand anyway......
The problem Tomo describes, seems to be caused in a wrong path, set in env-variables........otherwise booting with full path won't work too......

@Tomo: hope you have removed HD1 meanwhile.....otherwise i'm not wondering about this behaviour.....


[ Editiert durch Amigaharry2 05.02.2012 - 19:25 ]

Well maybe it is a good time to call it a loss and get a Powermac to replace it? I got a 1.5GHZ Duel CPU MDD one for only $80 last month, it runs the latest MOS very well, much better than my old Peg II ever could.

If you have a key and show the PEg II is no longer working I believe you can even transfer it to your new Mac. Its one solution at least.

Hi Folks,

thanks for all your help.
I'm no computerfreak so for me it was diving in an unknown world. But...
The good news is that my dear old Peggy is working again!!
It was looking in disk@1,0:0 instead of disk@0,0:0.
Thanks to the Pegasos Manual I printed long ago and finding it back (under the dust) I find the right command and that was the trick....
But now a new question. Finding one ATA-disk (80GB) was already difficult. Can I use other Harddisks in my Peg2?
Thanks for your help anyway.

Regards Tom

You may use any IDE-HD or SATA-HD (with IDE2SATA-Adapter) in all sizes.
But you have to partition the drive -for example:
1. A boot-partion for the boot.img, which has to be SFS (or FFS) and should be first partition on disk (I suggest a size of max. 300MB to store boot.img and, if wished, boot-stuff for Linux, CD32-emulator, aso.)
2. A System-Partition (2GB is more than enough) for MOS-Installation and addon progs.... Here you can use SFS or ICEFS. SFS supports only files <4GB and partitions <127GB......with ICEFS there is no restriction (but you have to download seperately - its not part of the MOS-distribution)
3. A Work-partition for your user-progs (suggest ICEFS) - I use 20GB
4. One ore more large DATA-Partions for your media-datas like pics, mp3, videos, etc. (strongly recommand ICEFS!!)
5. I use a additional partition for temp-data, which is used by YAM, Showgirls, Turboprint, ..... as cache-space. 500MB is enough.
6. Partitions for Linux (eg. root 10GB, Swap 3GB, home100GB)

If you will use some other software with extensive diskcache usage, then it may be usefull to use a seperate cache-partition (about 4GB) with more buffers for higher datatransfer........

Hi Harry,

I was first thinking of a second HD (SATA), but because the ATA-drive I'm no using is a second-hand it is perhaps better to follow your advice and buy a new SATA- disk. I understand that the new ICEFile-system is much better (and faster).
I'm an enthousiastic photographer and I need lots of space (and also for my classic music)

With many thanks, Tom

Please be carefull buying a IDE2SATA-adapter - most of the cheap adapters won't work propper... It's better to spend more money to get a good working thing....

If you think about a external USB-HD for media-data, please notice that there are sometimes errors (system hangs) on USB-Bus transfering big data-amounts..... Under normal circumstances you won't recognize any problem, but when transfering big video-files, which may have some GB, or many, many pics/mp3/etc. in one turn, then you can get errors.... This behaviour will be a little bit better when useing the HD with it's own power-source and/or with a selfpowered hub....
This problem is not new and is afaik caused by the pci.device for USB - maybe it will be fixed in future.....