Re: [parisc-linux] palo II

Re: [parisc-linux] palo II

[Joel Soete]

Hi Bjoern,

Anoyed to change my fstab because I add or remove a disk to/from the external
scsi controler of my b2k (boot disk sda became sdb, sdc, or what else),
I decide so to test devfs kernel. It seems to works (excepted that I could
not specify root=/dev/scsi/host1/bus0/target5/lun0/part5)

Coming back to the actual pb with new palo:
the original ipl prompt is:
PALO(F0) partition contains:
    0/vmlinux32 3826722 bytes @ 0x44000

Information: No console specified on kernel command line. 
his is normal.
PALO will choose the console currently used by firmware (serial).Current
command line:
3/vmlinux-2.4.19-pre10-pa39-tsi root=/dev/sda5 HOME=/ console=ttyS0 TERM=vt102
 0: 3/vmlinux-2.4.19-pre10-pa39-tsi
 1: root=/dev/sda5
 2: HOME=/

 3: console=ttyS0
 4: TERM=vt102

which I would like to change in:
Current command line:
3/vmlinux-2.4.21-rc8-pa35-devfs root=/dev/scsi/host1/bus0/target5/lun0/part5
HOME=/ console=ttyS0 TERM=vt102
 0: 3/vmlinux-2.4.21-rc8-pa35-devfs
 1: root=/dev/scsi/host1/bus0/target5/lun0/part5
 2: HOME=/
 3: console=ttyS0
 4: TERM=vt102

Edit which field?
(or 'b' to boot with this command line)? b

Command line for kernel: 'root=/dev/scsi/host1/bus0/target5/lun0/part5 HOME=/
console=ttyS0 TERM=
t102 palo_kernel=3/vmlinux-2.4.21-rc8-pa35-devfs'
Selected kernel: /vmlinux-2.4.21-rc8-pa35-devfs from partition 3

the system hang here (just read on LCD "init c7ff")

(btw, there is no pb if I don't change root path and the final lenght of
cmd line is of 121 characters < 256 of buffer ??)

I so come back to palo-1.2 where the pb don't occure:
Command line for kernel: 'root=/dev/scsi/host1/bus0/target5/lun0/part5 HOME=/
console=ttyS0 TERM=vt102 palo_kernel=3/vmlinux-2.4.21-rc8-pa35-devfs'

Selected kernel: /vmlinux-2.4.21-rc8-pa35-devfs from partition 3
ELF32 executable
Entry 00100210 first 00100000 n 6
Segment 0 load 00100000 size 2101928 mediaptr 0x1000
[...]

Even thought later:
[...]
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "scsi/host1/bus0/target5/lun0/part5" or 02:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 02:00

Never the less, in the cmdln the root device seems to be well /dev/scsi/...
and here is just mentionned scsi/... (may be normal, don't know)?

Any idea (how to debug)?

Thanks in advance,
    Joel





---------------------------------
Découvrez les 6 clés et gagnez le Club Med à Vie avec Tiscali
http://www.tiscali.be/nl/subs/tiscali4life/default.asp?lang=fr

Re: [parisc-linux] palo II

[Matthew Wilcox]

On Wed, Jun 11, 2003 at 07:46:54PM +0200, Joel Soete wrote:
> Anoyed to change my fstab because I add or remove a disk to/from the external
> scsi controler of my b2k (boot disk sda became sdb, sdc, or what else),
> I decide so to test devfs kernel. It seems to works (excepted that I could
> not specify root=/dev/scsi/host1/bus0/target5/lun0/part5)

(a) devfs is shit.  do not use it.
(b) even if it's compiled in, the kernel still matches `root=' against a
built-in table that has nothing to do with devfs.
(c) devfs is shit.  do not use it.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

Re: [parisc-linux] palo II

[Stian Søiland]

On 2003-06-11 19:51:10, Matthew Wilcox wrote:

> On Wed, Jun 11, 2003 at 07:46:54PM +0200, Joel Soete wrote:
> > Anoyed to change my fstab because I add or remove a disk to/from the ex=
ternal
> > scsi controler of my b2k (boot disk sda became sdb, sdc, or what else),
> > I decide so to test devfs kernel. It seems to works (excepted that I co=
uld
> > not specify root=3D/dev/scsi/host1/bus0/target5/lun0/part5)
> (a) devfs is shit.  do not use it.
> (b) even if it's compiled in, the kernel still matches `root=3D' against a
> built-in table that has nothing to do with devfs.
> (c) devfs is shit.  do not use it.

This thread is going way off-topic for the parisc-list.. but.. I feel
the need to disagree anyway! =3D)

Your argumentation is flawed.

Joel gave a perfect example of when devfs would come of perfect use,
variation of scsi devices fucks up "sdb", "sdc" and so on.=20

I earlier mentioned another fine use of devfs, to avoid the trouble of
constantly changing major number for /dev/ttB0 =3D)

Matthew, I wonder if it would not be possible to have a ext3-label
'root' on the partition and say root=3DLABEL=3Droot (even though that would
look rather weird =3D) )

    tune2fs -L root /dev/bla/blah

LABEL=3Dblapp can be used in fstab aswell.

Sad things I've discovered:

  * reiserfs does not support those labels
 =20
  * you cannot have two devices with the same labels
    (I tried to have multiple BOOT-partitions, with hopes that
    witchever was available could be used, however, that won't
    work when both devices are present, of course =3D) )
 =20
  * Labels DON'T work with software raid, because the kernel will
    recognize the labels even on the seperate units of the raid,=20
    and start complaining about multible labels.
 =20
    However, you might specify raids using their UUIDs in=20
    /etc/mdadm/mdadm.conf:
 =20
    # root
    ARRAY /dev/md/0 UUID=3D9ec52c6f:af4958dd:4c8ff16e:95abab7c spare-group=
=3Dekstra
    # usr
    ARRAY /dev/md/1 UUID=3Dbd627bf7:8fcae3d0:4f3f4fe7:7b3786df spare-group=
=3Dekstra
    # home
    ARRAY /dev/md/2 UUID=3D47e9c924:5bbda641:b506006e:599c80e5 spare-group=
=3Dekstra
 =20
    ... but.. I've had trouble with usr and home switching place (md1 and
    md2) from now and then anyway, so maybe this is just a teoretical
    feature =3D)
 =20
    Obligatory quote from bash.org:

      #85899 +(53)- [X]
      * unchellmatt does the RAID lovers cheer... "ARRAY! ARRAY!"

I don't think you will be able to use devfs in root=3D as /dev can't be
mounted before / (unless you use initrd, that is, but I haven't figured
out how to do that with palo)

--=20
Stian S=F8iland               Work toward win-win situation. Win-lose
Trondheim, Norway           is where you win and the other lose.
http://www.soiland.no/      Lose-lose and lose-win are left as an
                            exercise to the reader.  [Limoncelli/Hogan]

Re: [parisc-linux] palo II

[Alan Cox]

> Joel gave a perfect example of when devfs would come of perfect use,
> variation of scsi devices fucks up "sdb", "sdc" and so on. 

Seperate the theory from the implementation. The implementation has real
problems. The theory has permission management problems

Dell have a nice little app that generates the right symlinks by device
all in user space

Re: [parisc-linux] palo II

[Grant Grundler]

On Wed, Jun 11, 2003 at 09:32:32PM +0100, Alan Cox wrote:
> Dell have a nice little app that generates the right symlinks by device
> all in user space

Happen to know the name of the app?
Does it handle adding/removing HBAs gracefully?

thanks,
grant

Re: [parisc-linux] palo II

[Joel Soete]

>
>> Joel gave a perfect example of when devfs would come of perfect use,
> variation of scsi devices fucks up "sdb", "sdc" and so on. 

>Seperate the theory from the implementation. The implementation has real
>problems. The theory has permission management problems

I was just looking for a sol to this anoying scsi disk named to refer to
(a la /dev/[r]dsk/cXtXdX on hpux or /dev/dsk/cXtXdXsX on solaris; ie a name
independent of the scan order of [scsi] interfaces)

>Dell have a nice little app that generates the right symlinks by device
>all in user space

I will try to find it and test

Thanks,
    Joel

ps: btw merge 2.4.21 any news? now for > 2.4.22 (for my part no info from
Marcelo neither 'no' nor 'yes'; is there some specific ml archive to read)

---------------------------------
Découvrez les 6 clés et gagnez le Club Med à Vie avec Tiscali
http://www.tiscali.be/nl/subs/tiscali4life/default.asp?lang=fr

Re: [parisc-linux] palo II

[Bjoern A. Zeeb]

On Wed, 11 Jun 2003, Joel Soete wrote:

Hi,

...
> the system hang here (just read on LCD "init c7ff")
....

> I so come back to palo-1.2 where the pb don't occure:
> Command line for kernel: 'root=/dev/scsi/host1/bus0/target5/lun0/part5 HOME=/
> console=ttyS0 TERM=vt102 palo_kernel=3/vmlinux-2.4.21-rc8-pa35-devfs'
>
> Selected kernel: /vmlinux-2.4.21-rc8-pa35-devfs from partition 3
> ELF32 executable
> Entry 00100210 first 00100000 n 6
> Segment 0 load 00100000 size 2101928 mediaptr 0x1000
> [...]

well if I got it right you changed disks ? And after re-running palo 1.2
from command line everything workd fine ? I don't know these internals
of palo - where it get's the kernel etc. from but it might be a problem
if boot disc completely changes ... you might simply try re-running
pal0-1.2patched from command line again and see what happens ?

And yes Matthew is 101% right that devfs at least on linux is a big
mess. It took me almost a week to fix some 2.5.xx and get it boot from
grub on an intel somewhen end of last year. Some weeks later I
installed FreeBSD 5.0R on that machine and I am happy with it ;-) so I
do no longer have the notes a hand (apart from backups) I took those
days about devfs.

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/

Re: [parisc-linux] palo II

[Joel Soete]

...
> the system hang here (just read on LCD "init c7ff")
....

> I so come back to palo-1.2 where the pb don't occure:
> Command line for kernel: 'root=/dev/scsi/host1/bus0/target5/lun0/part5
HOME=
>
> console=ttyS0 TERM=vt102 palo_kernel=3/vmlinux-2.4.21-rc8-pa35-devfs'
>
> Selected kernel: /vmlinux-2.4.21-rc8-pa35-devfs from partition 3
> ELF32 executable
> Entry 00100210 first 00100000 n 6
> Segment 0 load 00100000 size 2101928 mediaptr 0
>1000
> [...]

> well if I got it right you changed disks ?
No I just add a disk on to an additional scsi ctrlr plug into my hp box

[...]
> ... you might simply try re-running
> pal0-1.2patched from command line again and see what happens ?

I could so try also (even if the boot disk do not actually changed)

> And yes Matthew is 101% right that devfs at least on linux is a big
> mess. It took me almost a week to fix some 2.5.xx and get it boot
> from grub on an intel somewhen end of last year. Some weeks later I
> installed FreeBSD 5.0R on that machine and I am happy with it ;-) so I
> do no longer have the notes a hand (apart from backups) I took those
> days about devfs.
Doesn't matter, considering all advises, I will abandon this idea and try
to find another one. Never the less, the problem I encounter stand in ipl
(at this boot stage)
btw, is your pb is solved? eg is this patch could be comit?

Thanks,
    Joel

[btw: is your FreeBsd stand alone on its own disk or beside linux partition?]

---------------------------------
Découvrez les 6 clés et gagnez le Club Med à Vie avec Tiscali
http://www.tiscali.be/nl/subs/tiscali4life/default.asp?lang=fr

Re: [parisc-linux] palo II

[Joel Soete]

> I couldn't yet. It happened just the one time. What I did was:
>
> 1. power on apollo
> 2. log in to the host the serial line was attached to
> 3. start minicom
> 4. come back five minute
> later (the palo.conf entry has been wrong)
> 5. fin
 the above on the screen
> 6. delete line 1 five times
> 7. change path to kernel
> 8. boot

Could it be electrical interferences?

[I also use minicom with serial port configured as 9600 8N1 with "Hardware
Flow COntrol : yes" and cleanup "modem and dialing" init and reset strings]

> [dep building]

> I think I am missing a package for all this here where most of the
> dh_* are included ...

the package is debhelper (just in case you would find another file, it exists
a nice search tool in <http://www.debian.org/distrib/packages>; at the
bottom, you can search packages containing the file you know :) )

> Me using apt-get source then debian/rules build and finally I cannot
> use fakeroot at the moment (glibc issue though downgr
ded).

Yes there is some issue with glibc 2.3.1-17, better is 2.3.1-16

Joel





---------------------------------
Découvrez les 6 clés et gagnez le Club Med à Vie avec Tiscali
http://www.tiscali.be/nl/subs/tiscali4life/default.asp?lang=fr

Re: [parisc-linux] palo II

[Bjoern A. Zeeb]

On Thu, 5 Jun 2003, Joel Soete wrote:

Hi,

> Could it be electrical interferences?

shouldn't but could be. I thaught about some 'missbehaviour' of
minicom but nether had that before (also using cu sometimes).

I'd wait for reports from others if anyone else will see it or have a
more detailed look at the source I find the time. exams done :-)

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/

Re: [parisc-linux] palo II

[Bjoern A. Zeeb]

On Thu, 5 Jun 2003, Joel Soete wrote:

Hi,

> Could it be electrical interferences?

got it again. started minicom when it already waited for input.
perhaps that's the problem...
it's the same sequence I got last time for 1 .. 5

--- cut ---
A 74 00L 1X c 1Q
Current command line:
3/boot/vmlinux-2.5.60-pa1A 74 00L 1X c 1Q root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0
 0: 3/boot/vmlinux-2.5.60-pa1A
 1: 74
 2: 00L
 3: 1X
 4: c
 5: 1Q
 6: root=/dev/sdb3
 7: HOME=/
 8: TERM=linux
 9: console=ttyS0

Edit which field?
(or 'b' to boot with this command line)? 0
3/boot/vmlinux-2.5.69-pa1
Current command line:
3/boot/vmlinux-2.5.69-pa1 74 00L 1X c 1Q root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0
 0: 3/boot/vmlinux-2.5.69-pa1
 1: 74
 2: 00L
 3: 1X
 4: c
 5: 1Q
 6: root=/dev/sdb3
 7: HOME=/
 8: TERM=linux
 9: console=ttyS0

Edit which field?
(or 'b' to boot with this command line)? 0
--- /cut ---

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/

Re: [parisc-linux] palo II

[Bjoern A. Zeeb]

On Thu, 5 Jun 2003, Bjoern A. Zeeb wrote:

Hi,

> got it again. started minicom when it already waited for input.
> perhaps that's the problem...
> it's the same sequence I got last time for 1 .. 5

sorry for replying to myself but I discovered another thing:

it boots fine also with this command line ???

--- cut ---
Edit which field?
(or 'b' to boot with this command line)? b

Command line for kernel: '74 00L 1X c 1Q root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0 palo_kernel=3/boot/vmlinux-2.5.69-pa1'
Selected kernel: /boot/vmlinux-2.5.69-pa1 from partition 3
ELF32 executable
Entry 001002a0 first 00100000 n 3
Segment 0 load 00100000 size 1688080 mediaptr 0x1000
Segment 1 load 0029e000 size 307316 mediaptr 0x19e000
Segment 2 load 002ec000 size 438400 mediaptr 0x1ea000
Branching to kernel entry point 0x001002a0.  If this is the last
message you see, you may need to switch your console.  This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org

Linux version 2.5.69-pa1 (bz@apollo) (gcc version 3.3 20030509 (Debian prerelease)) #22 Sat May 17 16:48:19 UTC 2003
FP[0] enabled: Rev 1 Model 13
The 32-bit Kernel has started...
Determining PDC firmware type: Snake.
...
--- /cut ---


-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/

Re: [parisc-linux] palo II

[Joel Soete]

Hi Bjoern,

> On Mon, 2 Jun 2003, Bjoern A. Zeeb wrote:
>
> Hi,
>
> > g) here is the patch. Thanks I remember basic for the goto ;-)

Simple and efficent;

> > peherhaps ignore the part with the version number ...
>
> well please - before commiting - verifiy ... I t
ink there is a
> problem maybe with some pointer ... Will have to verify all possible
> paths ... going to re-check and let you know.
>
> --- cut ---
> /boot/vmlinux-2.5.69-pa1 74 00L 1X c 1Q root=/dev/sdb3 HOME=/ TERM=linux
conso0
>  0: 3/boot/vmlinux-2.5.69-pa1
>  1: 74
>  2: 00L
>  3: 1X
>  4: c
>  5: 1Q
>  6: root=/dev/sdb3
>  7: HOME=/
>  8: TERM=linux
>  9: console=ttyS0
>
> Edit which field?
> (or 'b' to boot with this command line)?
> --- cut ---

Hmm how may I reproduce?


btw (as rought draft) I also consider the case if you accidently choose
swap (even on a md), here is the full patch:
=====
diff -Naur --exclude iplboot palo-1.2/debian/changelog palo-1.3/debian/changelog
--- palo-1.2/debian/changelog	2003-01-14
21:07:52.000000000 +0100
+++ palo-1.3/debian/changelog	2003-06-05 11:20:38.000000000 +0200
@@ -1,3 +1,9 @@
+palo (1.3) unstable; urgency=low
+
+  * Comeback to interact if failled to find boot kernel (Bjoern A. Zeeb)
+
+ -- Paul Bame <bame@debian.org>  Tue, 14 Jan 2003 13:06:45 -0700
+
 palo (1.2) unstable; urgency=low

   * Recognize RAID partition types (Martin K. Petersen)
diff -Naur --exclude iplboot palo-1.2/ipl/ipl.c palo-1.3/ipl/ipl.c
--- palo-1.2/ipl/ipl.c	2003-01-14 20:44:49.000000000 +0100
+++ palo-1.3/ipl/ipl.c	2003-06-05 12:56:25.000000000 +0200
@@ -367,6 +367,7 @@
 	}
     }

+interactive_loop:
     if (is_interactive)
 	interact(&f);

@@ -406,7 +407,9 @@
     {
 	printf("ERROR: Requesting kernel from partition %d "
 		    "on unpartitioned media!\n", kern_part);
-	while(1);
+
+        is_interactive = 1;
+        goto interactive_loop;
     }

     if (rd_part != -1 && rd_part != kern_part)
@@ -510,7 +513,9 @@
 	    (partition[kern_part - 1].id != 0x83 && partition[kern_part - 1].id
!= 0xfd) )
 	{
 	    printf("ERROR: Partition %d must be ext2\n", kern_part);
-	    while(1);
+
+            is_interactive = 1;
+            goto interactive_loop;
 	}

 	pp = &partition[kern_part - 1];
@@
-518,8 +523,13 @@
 	part_fd = offset_open(bootdev, 512 * pp->start, 512 * pp->length);

 	mount_fd = ext2_mount(part_fd, 0, 0);
-	if (0) printf("ext2_mount(partition %d) returns %d\n",
-	    kern_part, mount_fd);
+	if (mount_fd < 0){
+            printf("ext2_mount(partition %d) returns %d\n",
+	            kern_part, mount_fd);
+
+            is_interactive = 1;
+            goto interactive_loop;
+	}

 	kern_fd = ext2_open(kern_name);
 	if (0) printf("ext2_open(%s) = %d\n", kern_name
 kern_fd);
@@ -527,7 +537,9 @@
 	{
 	    printf("ERROR: open %s from partition %d failed\n",
 		kern_name, kern_part);
-	    while(1);
+
+            is_interactive = 1;
+            goto interactive_loop;
 	}

 	bkern_fd = byteio_open(kern_fd);
diff -Naur --exclude iplboot palo-1.2/lib/common.h palo-1.3/lib/common.h
--- palo-1.2/lib/common.h	2003-01-14 21:06:14.000000000 +0100
+++ palo-1.3/lib/common.h	2003-06-05 11:53:20.000000000 +0200
@@ -11,7 +11,7 @@
 #include <asm/byteorder.h>

 #include <linux/genhd.h>

-#define PALOVERSION "1.2"
+#define PALOVERSION "1.3"

 /* size of I/O block used in HP firmware */
 #define FW_BLOCKSIZE	2048

====

Up to you to adapt changes in changelog and lib/common.h :)

I a not an expert 
n debian building pkg but to rebuild a source tree i
follow this small recipe:
A) grab palo_1.2.dsc palo_1.2.tar.gz into your test dir
B) dpkg-source -x palo_1.2.dsc
this will extract palo-1.2
C) I rename palo-1.2 into palo-1.3 [according to chang
log revision]
D) cd palo-1.3
E) apply above patch (patch -p1 -i YourPatchFile)
E) dpkg-buildpackage [ 2>&1 | tee ../palo-1.3.bpkg # to log build messages]
on a _linux-parisc_ box it would rebuild iplboot :)

if successfull, you would find in the 
pper dir palo_1.3_hppa.deb dpkg which
you can just install.

hth,
    Joel

PS: another kind thing would be add edition line capability (any idea?)



---------------------------------
Découvrez les 6 clés et gagnez le Club Med à Vie avec Tiscali
http://www.tiscali.be/nl/subs/tiscali4life/default.asp?lang=fr

Re: [parisc-linux] palo II

[Bjoern A. Zeeb]

On Thu, 5 Jun 2003, Joel Soete wrote:

> > problem maybe with some pointer ... Will have to verify all possible
> > paths ... going to re-check and let you know.
> >
> > --- cut ---
> > /boot/vmlinux-2.5.69-pa1 74 00L 1X c 1Q root=/dev/sdb3 HOME=/ TERM=linux conso0
> >  0: 3/boot/vmlinux-2.5.69-pa1
> >  1: 74
> >  2: 00L
> >  3: 1X
> >  4: c
> >  5: 1Q
> >  6: root=/dev/sdb3
> >  7: HOME=/
> >  8: TERM=linux
> >  9: console=ttyS0
> >
> > Edit which field?
> > (or 'b' to boot with this command line)?
> > --- cut ---
>
> Hmm how may I reproduce?

I couldn't yet. It happened just the one time. What I did was:

1. power on apollo
2. log in to the host the serial line was attached to
3. start minicom
4. come back five minutes later (the palo.conf entry has been wrong)
5. find the above on the screen
6. delete line 1 five times
7. change path to kernel
8. boot



[dep building]

I think I am missing a package for all this here where most of the
dh_* are included ...

Me using apt-get source then debian/rules build and finally I cannot
use fakeroot at the moment (glibc issue though downgraded).

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/

Re: [parisc-linux] palo II

[Matthew Wilcox]

On Thu, Jun 05, 2003 at 02:14:33PM +0000, Bjoern A. Zeeb wrote:
> I think I am missing a package for all this here where most of the
> dh_* are included ...
> 
> Me using apt-get source then debian/rules build and finally I cannot
> use fakeroot at the moment (glibc issue though downgraded).

use dpkg-buildpackage -rsudo
that'll tell you which deps are missing

or you can apt-get build-dep palo to install palo's build deps.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

[parisc-linux] palo II

[Bjoern A. Zeeb]

Hi,

is there a chance that one can recover from s.t.h like this ?

Command line for kernel: 'root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0 palo_kernel=3/boot/vmlinux-2.5.60-pa1'
Selected kernel: /boot/vmlinux-2.5.60-pa1 from partition 3
ERROR: open /boot/vmlinux-2.5.60-pa1 from partition 3 failed
--- dead end ---

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/

Re: [parisc-linux] palo II

[Helge Deller]

On Sunday 01 June 2003 15:04, Bjoern A. Zeeb wrote:
> is there a chance that one can recover from s.t.h like this ?
>
> Command line for kernel: 'root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0
> palo_kernel=3/boot/vmlinux-2.5.60-pa1' Selected kernel:
> /boot/vmlinux-2.5.60-pa1 from partition 3
> ERROR: open /boot/vmlinux-2.5.60-pa1 from partition 3 failed

You could boot a good kernel via tftp. That's how I test different kernels...

Helge

Re: [parisc-linux] palo II

[Bjoern A. Zeeb]

On Sun, 1 Jun 2003, Helge Deller wrote:

> > is there a chance that one can recover from s.t.h like this ?
> >
> > Command line for kernel: 'root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0
> > palo_kernel=3/boot/vmlinux-2.5.60-pa1' Selected kernel:
> > /boot/vmlinux-2.5.60-pa1 from partition 3
> > ERROR: open /boot/vmlinux-2.5.60-pa1 from partition 3 failed
>
> You could boot a good kernel via tftp. That's how I test different kernels...

not a too bad idea but that's not the problem here.

When palo cannot open the kernel and errors out shouldn't it fall back
to the dialog and ask one to which fields to change instead of simply
running into a dead end where I think I can only recover from with
physical access to the machine ?

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/

Re: [parisc-linux] palo II

[Joel Soete]

Bjoern A. Zeeb wrote:

>On Sun, 1 Jun 2003, Helge Deller wrote:
>
>  
>
>>>is there a chance that one can recover from s.t.h like this ?
>>>
>>>Command line for kernel: 'root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0
>>>palo_kernel=3/boot/vmlinux-2.5.60-pa1' Selected kernel:
>>>/boot/vmlinux-2.5.60-pa1 from partition 3
>>>ERROR: open /boot/vmlinux-2.5.60-pa1 from partition 3 failed
>>>      
>>>
>>You could boot a good kernel via tftp. That's how I test different kernels...
>>    
>>
>
>not a too bad idea but that's not the problem here.
>
>When palo cannot open the kernel and errors out shouldn't it fall back
>to the dialog and ask one to which fields to change instead of simply
>running into a dead end where I think I can only recover from with
>physical access to the machine ?
>
>  
>
Afaik no way right now and I think it would be a good idea to open a bug 
report about this subject.
The current palo status of is specialy anoying when you reboot a server 
as a N (selftest of about 1/4h) and you made some stupid typo (as you 
do: 60 in place of 69) .

Hmm if I still have some time to have a look on this (as well as for 
booting a compressed kernel), which is the best 'model' (the nearest of 
palo) that I would have to analyse?

Cheers,
    Joel

Re: [parisc-linux] palo II

[Grant Grundler]

On Sun, Jun 01, 2003 at 02:05:20PM +0000, Bjoern A. Zeeb wrote:
> When palo cannot open the kernel and errors out shouldn't it fall back
> to the dialog and ask one to which fields to change instead of simply
> running into a dead end where I think I can only recover from with
> physical access to the machine ?

The same issue has annoyed me too.
But not enough to hack on palo. I only work on machines remotely
if I have remote power control (eg A500).

Paul Bame is happy to take any patches people have to improve
this behaviour.  Source is available via anon CVS:
	cvs -d pserver:anonymous@cvs.parisc-linux.org login
	cvs -d pserver:anonymous@cvs.parisc-linux.org co palo

hth,
grant

Re: [parisc-linux] palo II

[Bjoern A. Zeeb]

On Mon, 2 Jun 2003, Grant Grundler wrote:

Hi,

> On Sun, Jun 01, 2003 at 02:05:20PM +0000, Bjoern A. Zeeb wrote:
> > When palo cannot open the kernel and errors out shouldn't it fall back
> > to the dialog and ask one to which fields to change instead of simply
> > running into a dead end where I think I can only recover from with
> > physical access to the machine ?
>
> The same issue has annoyed me too.
> But not enough to hack on palo. I only work on machines remotely
> if I have remote power control (eg A500).
>
> Paul Bame is happy to take any patches people have to improve
> this behaviour.  Source is available via anon CVS:
> 	cvs -d pserver:anonymous@cvs.parisc-linux.org login
> 	cvs -d pserver:anonymous@cvs.parisc-linux.org co palo

on sunday eve I already dowloaded 1.2 src tarball and had a quick look
at it. I may come up with a very dirty quick hack but I really hate
gotos in C.

The Problem is that I am currently in the middle of my final exams.
Perhaps I might come up with a patch next weekend.

-- 
Greetings

Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/

Re: [parisc-linux] palo II

[Bjoern A. Zeeb]

On Mon, 2 Jun 2003, Bjoern A. Zeeb wrote:

> > > When palo cannot open the kernel and errors out shouldn't it fall back
> > > to the dialog and ask one to which fields to change instead of simply
> > > running into a dead end where I think I can only recover from with
> > > physical access to the machine ?
> >
> > The same issue has annoyed me too.
> > But not enough to hack on palo. I only work on machines remotely
> > if I have remote power control (eg A500).
> >
> > Paul Bame is happy to take any patches people have to improve
> > this behaviour.  Source is available via anon CVS:
> > 	cvs -d pserver:anonymous@cvs.parisc-linux.org login
> > 	cvs -d pserver:anonymous@cvs.parisc-linux.org co palo
>
> on sunday eve I already dowloaded 1.2 src tarball and had a quick look
> at it. I may come up with a very dirty quick hack but I really hate
> gotos in C.
>
> The Problem is that I am currently in the middle of my final exams.
> Perhaps I might come up with a patch next weekend.

forget next weekend ;-) Though the machine time is out of sync :(

a) I am no debian package builder but in debian/rules dh_testdir is
unknown - whatever it should do - as are a lotta other things. Seems
some package(?) is missing locally.

b) going to test (press me your thumbs it will work else I will
   have to find a kernel to tftp boot ...) ...
   going back to my old 2.5.60-pa1 instead of 69 typo...
   still old palo on bootup ... maybe installing the new one would be
   better for testing ;-))

c) *hhm* debian/rules build doesn't do make iplboot ? ok, doing and
   installing manually ...

d) re-run palo

e) reboot 'n' pray ... (is this a song ? ;-)

f) Bingo:

--- cut ---
palo ipl 1.2bz01 bz@apollo Mon May 26 04:02:26 UTC 2003

Partition Start(MB) End(MB) Id Type
1               1      30   f0 Palo
2              31     156   82 swap
3             157    2046   83 ext2

PALO(F0) partition contains:
    0/vmlinux32 2955343 bytes @ 0x48000

Command line for kernel: 'root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0 palo_kernel=3/boot/vmlinux-2.5.60-pa1'
Selected kernel: /boot/vmlinux-2.5.60-pa1 from partition 3
ERROR: open /boot/vmlinux-2.5.60-pa1 from partition 3 failed
Current command line:
3/boot/vmlinux-2.5.60-pa1 root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0
 0: 3/boot/vmlinux-2.5.60-pa1
 1: root=/dev/sdb3
 2: HOME=/
 3: TERM=linux
 4: console=ttyS0

Edit which field?
(or 'b' to boot with this command line)? 0
3/boot/vmlinux-2.5.69-pa435
Current command line:
3/boot/vmlinux-2.5.69-pa435 root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0
 0: 3/boot/vmlinux-2.5.69-pa435
 1: root=/dev/sdb3
 2: HOME=/
 3: TERM=linux
 4: console=ttyS0

Edit which field?
(or 'b' to boot with this command line)? b

Command line for kernel: 'root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0 palo_kernel=3/boot/vmlinux-2.5.69-pa435'
Selected kernel: /boot/vmlinux-2.5.69-pa435 from partition 3
ERROR: open /boot/vmlinux-2.5.69-pa435 from partition 3 failed
Current command line:
3/boot/vmlinux-2.5.69-pa435 root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0
 0: 3/boot/vmlinux-2.5.69-pa435
 1: root=/dev/sdb3
 2: HOME=/
 3: TERM=linux
 4: console=ttyS0

Edit which field?
(or 'b' to boot with this command line)? 0
3/boot/vmlinux-2.5.69-pa1
Current command line:
3/boot/vmlinux-2.5.69-pa1 root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0
 0: 3/boot/vmlinux-2.5.69-pa1
 1: root=/dev/sdb3
 2: HOME=/
 3: TERM=linux
 4: console=ttyS0

Edit which field?
(or 'b' to boot with this command line)? b

Command line for kernel: 'root=/dev/sdb3 HOME=/ TERM=linux console=ttyS0 palo_kernel=3/boot/vmlinux-2.5.69-pa1'
Selected kernel: /boot/vmlinux-2.5.69-pa1 from partition 3
ELF32 executable
Entry 001002a0 first 00100000 n 3
Segment 0 load 00100000 size 1688080 mediaptr 0x1000
Segment 1 load 0029e000 size 307316 mediaptr 0x19e000
Segment 2 load 002ec000 size 438400 mediaptr 0x1ea000
...
--- /cut ---


g) here is the patch. Thanks I remember basic for the goto ;-)
peherhaps ignore the part with the version number ...


--- ./ipl/ipl.c.orig	2003-01-14 19:44:49.000000000 +0000
+++ ./ipl/ipl.c	2003-05-26 03:34:03.000000000 +0000
@@ -367,6 +367,7 @@
 	}
     }

+interactive_loop:
     if (is_interactive)
 	interact(&f);

@@ -510,7 +511,9 @@
 	    (partition[kern_part - 1].id != 0x83 && partition[kern_part - 1].id != 0xfd) )
 	{
 	    printf("ERROR: Partition %d must be ext2\n", kern_part);
-	    while(1);
+
+	    is_interactive = 1;
+	    goto interactive_loop;
 	}

 	pp = &partition[kern_part - 1];
@@ -527,7 +530,9 @@
 	{
 	    printf("ERROR: open %s from partition %d failed\n",
 		kern_name, kern_part);
-	    while(1);
+
+	    is_interactive = 1;
+	    goto interactive_loop;
 	}

 	bkern_fd = byteio_open(kern_fd);
--- ./lib/common.h.orig	2003-05-26 03:34:11.000000000 +0000
+++ ./lib/common.h	2003-05-26 03:34:18.000000000 +0000
@@ -11,7 +11,7 @@
 #include <asm/byteorder.h>
 #include <linux/genhd.h>

-#define PALOVERSION "1.2"
+#define PALOVERSION "1.2bz01"

 /* size of I/O block used in HP firmware */
 #define FW_BLOCKSIZE	2048


-- 
Greetings

Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/

Re: [parisc-linux] palo II

[Bjoern A. Zeeb]

On Mon, 2 Jun 2003, Bjoern A. Zeeb wrote:

Hi,

> g) here is the patch. Thanks I remember basic for the goto ;-)
> peherhaps ignore the part with the version number ...

well please - before commiting - verifiy ... I think there is a
problem maybe with some pointer ... Will have to verify all possible
paths ... going to re-check and let you know.

--- cut ---
/boot/vmlinux-2.5.69-pa1 74 00L 1X c 1Q root=/dev/sdb3 HOME=/ TERM=linux conso0
 0: 3/boot/vmlinux-2.5.69-pa1
 1: 74
 2: 00L
 3: 1X
 4: c
 5: 1Q
 6: root=/dev/sdb3
 7: HOME=/
 8: TERM=linux
 9: console=ttyS0

Edit which field?
(or 'b' to boot with this command line)?
--- cut ---

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/