Re: Bug#129940: boot-floppies: S/390 (hercules): Can't find CTC adapter
>>>>> "Stefan" == Stefan Gybas <gybas@trustsec.de> writes:
Stefan> I have found the bug, it was a missing line in the
Stefan> interactive CTC setup script. A new test version of the
Stefan> 3.0.19 root.bin can be found at
Stefan> http://people.debian.org/~sgybas/deb390/boot-floppies/root.bin-3.0.19
Stefan> Please tell me if this works for you in interactive mode.
Yes it works! My first try:
> Enter your choice (0-2):
> .1
> 1
> chan cu cu dev dev in chandev
> irq devno type type model type model pim chpids use reg.
> ===============================================================================
> 0x000a 0x0400 0x05 0x3088 0x08 0x3088 0x01 0x80 0x0400000000000000 no no
> 0x000b 0x0401 0x05 0x3088 0x08 0x3088 0x01 0x80 0x0400000000000000 no no
> The following device numbers might belong to CTC or ESCON connections, but
> please note that OSA-2 or OSA-Express cards might also be listed here:
> 0x0400 0x0401
> Please enter the read device numbers for your device in hexadecimal notation
> preceeded by 0x, e.g. "0x1000" or "auto" for automatic probing. However,
> auto probing might not work because OSA-2 cards use the same device type.
> Note: The read device numer must be an even number and the write device
> number must be the following number.
> Advanced users may also enter all chandev parameters for the ctc module, e.g.
> "ctc0,0x1000,0x1001". See the chapter about the "Channel device layer" in
> "LINUX for S/390: Device Drivers and Installation Commands" for details.
> ctc read device number: 0x0400!
> .0x400
> Please enter the protocol number for this connection (0 to 3)
> ctc protocol number: 0!
> .0
Uh, what's that protocol number? Shouldn't be there some explanation?
Or is it documented in the cited manual?
What disturbs me something is that the search domain is derived from
the hostnames domain. That ist mostly correct, and will work most of
the time, but there may be situations where it is not what you want.
I Haven't tried to answer "no" to the "is this correct" question.
My second try:
> Please enter the read device numbers for your device in hexadecimal notation
> preceeded by 0x, e.g. "0x1000" or "auto" for automatic probing. However,
> auto probing might not work because OSA-2 cards use the same device type.
> Note: The read device numer must be an even number and the write device
> number must be the following number.
> Advanced users may also enter all chandev parameters for the ctc module, e.g.
> "ctc0,0x1000,0x1001". See the chapter about the "Channel device layer" in
> "LINUX for S/390: Device Drivers and Installation Commands" for details.
> ctc read device number: 0x0400!
> .auto
> auto
> Module configuration will be:
> Module name : ctc
> Generic chandev parameter:
> Chandev module parameter :
> Is this correct (Yes/No) ?
> .yes
> yes
> The ctc has been loaded but no network interface was defined.
> Please retry with different settings or try a manual setup
> Select the type of your network device
> 0) no network configuration (to use this as a rescue system)
Auto setup seems not to be automatic. Hm.
Jochen
--
#include <~/.signature>: permission denied
Reply to: