headers
Frank Wille | 1 Apr 2011 18:22
Picon

Re: about Pegasos1 (april fix 2) support

nello martuscielli wrote:

> well, before i tried to boot from my hdd (first partition with FAT16
> fs).

I didn't know. Theoretically that would be the better option. Which files
were on your FAT16 partition and what did enter to boot the kernel?

ofwboot should have detected a valid MBR partition format here, which it
didn't.

>> I just tried tried the same with a CD and ofwbootdb on my Pegasos2 and
>> FS[1] does not return error 22. This is the ISO9660 file system.
>
> ok, i've now burned bsd files on a cd with iso9660  and i received the
> same output except for:
> FS[1]_OPEN - error=2

That's the best result so far. Error code 2 means that the file was not
found, which means the ISO9660 file system was correctly detected.

Do you prefer to continue debugging with CD or with FAT16? I would prepare
an ofwboot with appropriate debugging output.

--

-- 
Frank Wille
Permalink | Reply | 6 comments |
headers
nello martuscielli | 2 Apr 2011 00:06
Picon

Re: about Pegasos1 (april fix 2) support

On Fri, Apr 1, 2011 at 6:22 PM, Frank Wille <frank <at> phoenix.owl.de> wrote:
> nello martuscielli wrote:
>
>> well, before i tried to boot from my hdd (first partition with FAT16
>> fs).
>
> I didn't know. Theoretically that would be the better option. Which files
> were on your FAT16 partition and what did enter to boot the kernel?
>

i put netbsd.gz and ofwbootdb.gz and etered from smartfirmware prompt:
boot /ide/disk:0 ofwbootdb.gz
and
boot /ide/disk:0 ofwbootdb.gz netbsd.gz

> ofwboot should have detected a valid MBR partition format here, which it
> didn't.
>
>
>>> I just tried tried the same with a CD and ofwbootdb on my Pegasos2 and
>>> FS[1] does not return error 22. This is the ISO9660 file system.
>>
>> ok, i've now burned bsd files on a cd with iso9660  and i received the
>> same output except for:
>> FS[1]_OPEN - error=2
>
> That's the best result so far. Error code 2 means that the file was not
> found, which means the ISO9660 file system was correctly detected.
>
> Do you prefer to continue debugging with CD or with FAT16? I would prepare
(Continue reading)

Permalink | Reply | 5 comments |
headers
Frank Wille | 2 Apr 2011 11:56
Picon

Re: about Pegasos1 (april fix 2) support

nello martuscielli wrote:

> [..FAT16..]
> i put netbsd.gz and ofwbootdb.gz and etered from smartfirmware prompt:
> boot /ide/disk:0 ofwbootdb.gz
> and
> boot /ide/disk:0 ofwbootdb.gz netbsd.gz

To exclude another error source I would put the files uncompressed onto the
partition (although SmartFirmware and ofwboot can decompress on the fly).

> I prefer from hdd 'cause it's simpler and faster. Thus i can avoid to
> blank and burn cdrw for any tests.

Ok.

According to your last screenshot, which I understood was with a FAT16 RDB
partition, the detection of RDB failed with error 101 (meaning no valid
partition table found). So we should continue debugging there.

You say you were using an Amiga-style RDB partition format.
- Which program did you use to create the partitions?
- What other partitions are present? What is the exact partitioning of the
disk?
- Which ID did you use for the FAT16 partition? It should be 0x4d5344XX.
  (Maybe ofwboot should also support other IDs for FAT.)
- Blocksize of the partition is 512 bytes, I assume?
- Are you sure the RDB is within the first 16 blocks of the disk?

I have uploaded another ofwbootdb.gz on the usual location. It includes some
(Continue reading)

Permalink | Reply | 4 comments |
headers
nello martuscielli | 2 Apr 2011 14:42
Picon

Re: about Pegasos1 (april fix 2) support

On Sat, Apr 2, 2011 at 11:56 AM, Frank Wille <frank <at> phoenix.owl.de> wrote:
> nello martuscielli wrote:
>
>> [..FAT16..]
>> i put netbsd.gz and ofwbootdb.gz and etered from smartfirmware prompt:
>> boot /ide/disk:0 ofwbootdb.gz
>> and
>> boot /ide/disk:0 ofwbootdb.gz netbsd.gz
>
> To exclude another error source I would put the files uncompressed onto the
> partition (although SmartFirmware and ofwboot can decompress on the fly).
>
>

OK, I'll try new files asap.

>> I prefer from hdd 'cause it's simpler and faster. Thus i can avoid to
>> blank and burn cdrw for any tests.
>
> Ok.
>
> According to your last screenshot, which I understood was with a FAT16 RDB
> partition, the detection of RDB failed with error 101 (meaning no valid
> partition table found). So we should continue debugging there.
>
> You say you were using an Amiga-style RDB partition format.
> - Which program did you use to create the partitions?
> - What other partitions are present? What is the exact partitioning of the
> disk?
> - Which ID did you use for the FAT16 partition? It should be 0x4d5344XX.
(Continue reading)

Permalink | Reply | 3 comments |
headers
nello martuscielli | 2 Apr 2011 14:52
Picon

Re: about Pegasos1 (april fix 2) support

# lspci -nn
00:00.0 Host bridge [0600]: Mai Logic Incorporated Articia S Host
Bridge [10cc:0660] (rev 01)
00:01.0 PCI bridge [0604]: Mai Logic Incorporated Articia S PCI Bridge
[10cc:0661]
00:06.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. IEEE 1394
Host Controller [1106:3044] (rev 46)
00:07.0 ISA bridge [0601]: VIA Technologies, Inc. VT8231 [PCI-to-ISA
Bridge] [1106:8231] (rev 10)
00:07.1 IDE interface [0101]: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571]
(rev 06)
00:07.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI
USB 1.1 Controller [1106:3038] (rev 1e)
00:07.3 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI
USB 1.1 Controller [1106:3038] (rev 1e)
00:07.4 Non-VGA unclassified device [0000]: VIA Technologies, Inc.
VT8235 ACPI [1106:8235] (rev 10)
00:07.5 Multimedia audio controller [0401]: VIA Technologies, Inc.
VT82C686 AC97 Audio Controller [1106:3058] (rev 40)
00:07.6 Communication controller [0780]: VIA Technologies, Inc. AC'97
Modem Controller [1106:3068] (rev 20)
00:08.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102
[Rhine-II] [1106:3065] (rev 51)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV280
[Radeon 9200 SE] [1002:5964] (rev 01)
01:00.1 Display controller [0380]: ATI Technologies Inc RV280 [Radeon
9200 SE] (Secondary) [1002:5d44] (rev 01)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Frank Wille | 2 Apr 2011 20:38
Picon

Re: about Pegasos1 (april fix 2) support

On Sat, 2 Apr 2011 14:42:01 +0200
nello martuscielli <ppc.addon <at> gmail.com> wrote:

> Peg1 only manage amiga or msdos partition table, i've msdos.

Then I misunderstood you. I thought you meant amiga partition table in
your last mail.

> Here some info about the disk booting from  linux:
> [...]

Ok, I see the problem. You have MBR partitions and ofwboot must find
a NetBSD partition among them to read a disklabel. It cannot work.

I will see if it makes sense to create a fake disklabel out of FAT
partitions, when there is no NetBSD disklabel found. Maybe that is
also a useful enhancement of ofwboot for others.

Otherwise the only option for the Pegasos1 would be CD-booting.

--

-- 
Frank Wille
Permalink | Reply | 1 comment |
headers
nello martuscielli | 5 Apr 2011 17:30
Picon

Re: about Pegasos1 (april fix 2) support

On Sat, Apr 2, 2011 at 8:38 PM, Frank Wille <frank <at> phoenix.owl.de> wrote:
> On Sat, 2 Apr 2011 14:42:01 +0200
> nello martuscielli <ppc.addon <at> gmail.com> wrote:
>
>> Peg1 only manage amiga or msdos partition table, i've msdos.
>
> Then I misunderstood you. I thought you meant amiga partition table in
> your last mail.
>
>
>> Here some info about the disk booting from  linux:
>> [...]
>
> Ok, I see the problem. You have MBR partitions and ofwboot must find
> a NetBSD partition among them to read a disklabel. It cannot work.
>
> I will see if it makes sense to create a fake disklabel out of FAT
> partitions, when there is no NetBSD disklabel found. Maybe that is
> also a useful enhancement of ofwboot for others.
>
> Otherwise the only option for the Pegasos1 would be CD-booting.
>

it seems a nice step forward! It starts to load netbsd.

well, now booting from CD with gunzipped files:
http://oi51.tinypic.com/maxa8m.jpg

I'll give another try with a different new media in the next days even
i burned twice and i got tha same error at 3141982
(Continue reading)

Permalink | Reply | 0 comments |
headers
Frank Wille | 7 Apr 2011 16:24
Picon

ofwboot with DOS partition support

Hi,

I did some local changes to make ofwboot recognize a FAT partition as root
partition (wd0a), when no valid BSD disklabel was found.

When it works then it should simplify our tests on the Pegasos1.

Please try it. I cannot test it myself, as my disk is using RDB partitions.
An ofwboot with debugging output can be downloaded from:
  ftp://ftp.netbsd.org/pub/NetBSD/misc/phx/ofppc_peg1/ofwbootdb.gz

--

-- 
Frank Wille
Permalink | Reply | 3 comments |
headers
nello martuscielli | 8 Apr 2011 19:11
Picon

Re: ofwboot with DOS partition support

On Thu, Apr 7, 2011 at 4:24 PM, Frank Wille <frank <at> phoenix.owl.de> wrote:
> Hi,
>
> I did some local changes to make ofwboot recognize a FAT partition as root
> partition (wd0a), when no valid BSD disklabel was found.
>
> When it works then it should simplify our tests on the Pegasos1.
>
> Please try it. I cannot test it myself, as my disk is using RDB partitions.
> An ofwboot with debugging output can be downloaded from:
>  ftp://ftp.netbsd.org/pub/NetBSD/misc/phx/ofppc_peg1/ofwbootdb.gz
>

ok, now ofwboot is able to work from my hdd:
http://oi52.tinypic.com/2hs3y8l.jpg

eh,eh, another little step forward :)

cheers,
Nello
Permalink | Reply | 2 comments |
headers
Frank Wille | 8 Apr 2011 22:18
Picon

Re: ofwboot with DOS partition support

On Fri, 8 Apr 2011 19:11:33 +0200
nello martuscielli <ppc.addon <at> gmail.com> wrote:

> ok, now ofwboot is able to work from my hdd:
> http://oi52.tinypic.com/2hs3y8l.jpg

Good. Seems we reached the same situation as from CD.

Now I can insert some debugging output to find out why it stops
loading the ELF image.

--

-- 
Frank Wille
Permalink | Reply | 0 comments |

Gmane