FCP problem on Debian s390 hardware

[Shrirang Kulkarni]

I installed Debian (2.6.18-6-s390) on one my guest image on z/VM. The

Guest has both DASD and FCP attached to it.

I created / and swap on DASD.

At install time Debian was not showing any FCP which is attached to

Guest image thought let me try to enable same after install of OS.



Once Install was done went to



Steps

1. chccwdev -e 0.0.b001



2. echo 0x5005076305080310 > /sys/bus/ccw/devices/0.0.b001/port_add



3. echo 0x4010400100000000 > /sys/bus/ccw/devices/0.0.b001/0x5005076305080310/



enabled all SCSI devices of FCP



4. cd /sys/bus/ccw/devices/0.0.b001/0x5005076305080310/



5. /sys/bus/ccw/devices/0.0.b001/0x5005076305080310 # ls



0x4010400100000000 0x4010400b00000000 0x4010401500000000

0x4011400a00000000 0x4011401400000000 0x4011401e00000000



6. So able to see all devices on FCP and made partions and mounted
able to use in Debian Linux



7. I tried to create initrd as new devices added by



mkinitrams -o initrd.img-2.6.18-6-s390 2.6.18-6



8.  But when i reboot machine No FCP devices detected.



Once again I need repeat 1-6 steps for FCP to get enable







Thanks and Regards

Shrirang B. Kulkarni

______________________________________________________________


--
To UNSUBSCRIBE, email to debian-s390-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Frans Pop-3]

Please do not start two separate threads for basically the same
question/problem in two days!

Shrirang Kulkarni wrote:

> Steps
> 1. chccwdev -e 0.0.b001
> 2. echo 0x5005076305080310 > /sys/bus/ccw/devices/0.0.b001/port_add
> 3. echo 0x4010400100000000 >
> /sys/bus/ccw/devices/0.0.b001/0x5005076305080310/
> enabled all SCSI devices of FCP
>
> 4. cd /sys/bus/ccw/devices/0.0.b001/0x5005076305080310/
>
> 5. /sys/bus/ccw/devices/0.0.b001/0x5005076305080310 # ls
> 0x4010400100000000 0x4010400b00000000 0x4010401500000000
> 0x4011400a00000000 0x4011401400000000 0x4011401e00000000
>
> 6. So able to see all devices on FCP and made partions and mounted
> able to use in Debian Linux
>
> 7. I tried to create initrd as new devices added by
> mkinitrams -o initrd.img-2.6.18-6-s390 2.6.18-6
>
> 8.  But when i reboot machine No FCP devices detected.
>
> Once again I need repeat 1-6 steps for FCP to get enable

Right, so you enabled things manually on one boot and now expect them to
somehow magically be enabled on the next boot too, without laying
anything down in configuration.
Seems to me you are making some flawed assumptions here about how things
are supposed to work...

Please take a look at the sysconfig-hardware package. That is the tool
intended to set up devices at boot on s390 based on info from /sys.

Quite probably it will need some extentions to support FCP, but I think it
should be relatively straightforward. If you figure out what/how, please
send a patch (by opening a wishlist bug report against the
sysconfig-hardware package with the problem description and patch)!

Cheers,
FJP

[Bastian Blank]

On Thu, Jun 19, 2008 at 10:35:47AM +0200, Frans Pop wrote:
> Quite probably it will need some extentions to support FCP, but I think it
> should be relatively straightforward. If you figure out what/how, please
> send a patch (by opening a wishlist bug report against the
> sysconfig-hardware package with the problem description and patch)!

It is already supported.

| # cat /etc/sysconfig/hardware/config-ccw-0.0.2900
| ZFCP_DEVICES=( \
|   0x210000XXXXXXXXXX:0 \
|   0x220000XXXXXXXXXX:0 \
[...]
| )

Bastian

--
Genius doesn't work on an assembly line basis.  You can't simply say,
"Today I will be brilliant."
                -- Kirk, "The Ultimate Computer", stardate 4731.3


--
To UNSUBSCRIBE, email to debian-s390-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...