re: devfs
>>> Please,
>>>
>>> We are using Debian in a s390 9672r34 g3 machine.
>>>How can I configure the devfs system in a new
instalation ?
>>>
>>> Step by step ( not exactly...):
>>>
>>>
>>> # echo 'add device range=102' >>
/proc/dasd/devices
>>> # echo 'add device range=103' >>
/proc/dasd/devices
>>>
>>> # dasdfmt -v -b4096 -l lxdeb2 -d cdl -n 102
>>> # dasdfmt -v -b4096 -l lxdeb2 -d cdl -n 103
>>>
>OK, for starters, is this under VM, or in an LPAR?
>What are you IPLing
>from? A Debian tape? A Debian card deck (if under
>VM), or something
>else? If something else, it's not going to recognize
>devfs because
>you're running some other kernel which doesn't know
>about it. In that
>case, use /dev/dasdX labels and I think when Debian
>IPLs it will figure
>out the new mapping, although you might have to edit
>/etc/fstab by hand.
We are using Debian in a LPAR w/o VM with disk IPL.
The kernel version is ...
Linux maracana.proderj.rj.gov.br 2.4.17 #1 SMP Thu Apr
3 08:58:03 UTC 2003 s390 unknow
and have the devfs option.
>>> Using fdasd to partioning...
>>>
>>> /dev/dasd/0102/part1 -> boot ( 16 mbytes )
>>> /dev/dasd/0102/part2 -> swap ( 512 mbytes )
>>> /dev/dasd/0102/part3 -> var ( ~1.4 gbytes )
>>>
>>> /dev/dasd/0103/part1 -> root ( 128 mbytes )
>>> /dev/dasd/0102/part2 -> home ( 512 mbytes )
>>> /dev/dasd/0102/part3 -> usr ( ~1.4 gbytes )
>And don't do this.
>S/390 expects one partition per device. It's
"part1";
>format it CDL so
>OS knows what to do with the disklabel. This is,
>obviously, a lot
>easier under VM, because you get to make disks as
>small as you want
>rather than having the 3390-3 as your minimal chunk.
We use the command
# echo 'add device range=XXX' >> /proc/dasd/devices
to mount another disk and make a cross-install
After the bootstrap, I have tried an IPL in disk 102 (
\boot partition ) but only the disk 103 have mounted.
The 102 disk mounts with 'mount' command, after IPL
boot:
maracana:~# mount
/dev/dasd/0103/part1 on / type ext3 (rw)
proc on /proc type proc (rw)
/dev/dasd/0103/part2 on /home type ext3 (rw,nosuid)
/dev/dasd/0103/part3 on /usr type ext3 (rw)
/dev/dasd/0102/part1 on /boot type ext3 (rw)
/dev/dasd/0102/part3 on /var type ext3 (rw,nosuid)
The complete dmesg output
maracana:~# dmesg
00B6E8C0 05C24417 00B92A08 00020028 00807485
00B6E8D0 04000000 00000000 00000000 00000000
00B6E8E0 91408800 02000100 0C005000 00E01C46
00B6E8F0 00013485 54880046 0C46FF03 00000024
Channel-Check or Interface-Control-Check received
... device 0046 on subchannel 0007, dev_stat : 00
sch_stat : 02
s390_process_IRQ(0007) - irb for device 0046 after
channel check
00B6E8C0 05C24417 00B92A08 00020028 00807485
00B6E8D0 04000000 00000000 00000000 00000000
00B6E8E0 91408800 02000100 0C005000 00E01C46
00B6E8F0 00023485 54880046 0C46FF03 00000004
Channel-Check or Interface-Control-Check received
... device 0046 on subchannel 0007, dev_stat : 00
sch_stat : 02
s390_process_IRQ(0007) - irb for device 0046 after
channel check
00B6E8C0 05C24417 00B92A08 00020028 00807485
00B6E8D0 04000000 00000000 00000000 00000000
00B6E8E0 91408800 02000100 0C005000 00E01C46
00B6E8F0 00033485 54880046 0C46FF02 00000024
Channel-Check or Interface-Control-Check received
... device 0046 on subchannel 0007, dev_stat : 00
sch_stat : 02
s390_process_IRQ(0007) - irb for device 0046 after
channel check
00B6E8C0 05C24417 00B92A08 00020028 00807485
00B6E8D0 04000000 00000000 00000000 00000000
00B6E8E0 91408800 02000100 0C005000 00E01C46
00B6E8F0 00043485 54880046 0C46FF00 00000004
Channel-Check or Interface-Control-Check received
... device 0046 on subchannel 0007, dev_stat : 00
sch_stat : 02
s390_process_IRQ(0007) - irb for device 0046 after
channel check
00B6E8C0 05C24417 00B92A08 00020028 00807485
00B6E8D0 04000000 00000000 00000000 00000000
00B6E8E0 91408800 02000100 0C005000 00E01C46
00B6E8F0 00053485 54880046 0C46FF00 00000004
Channel-Check or Interface-Control-Check received
... device 0047 on subchannel 000B, dev_stat : 00
sch_stat : 02
s390_process_IRQ(000B) - irb for device 0047 after
channel check
00B6EAC0 05C24417 00B92B08 00020028 00807485
00B6EAD0 04000000 00000000 00000000 00000000
00B6EAE0 91408800 02000100 0C005000 00E01C47
00B6EAF0 00063485 54880047 0C47FF03 00000014
Channel-Check or Interface-Control-Check received
... device 0047 on subchannel 000B, dev_stat : 00
sch_stat : 02
s390_process_IRQ(000B) - irb for device 0047 after
channel check
00B6EAC0 05C24417 00B92B08 00020028 00807485
00B6EAD0 04000000 00000000 00000000 00000000
00B6EAE0 91408800 02000100 0C005000 00E01C47
00B6EAF0 00073485 54880047 0C47FF02 00000004
Channel-Check or Interface-Control-Check received
... device 0047 on subchannel 000B, dev_stat : 00
sch_stat : 02
s390_process_IRQ(000B) - irb for device 0047 after
channel check
00B6EAC0 05C24417 00B92B08 00020028 00807485
00B6EAD0 04000000 00000000 00000000 00000000
00B6EAE0 91408800 02000100 0C005000 00E01C47
00B6EAF0 00083485 54880047 0C47FF01 00000024
Channel-Check or Interface-Control-Check received
... device 0047 on subchannel 000B, dev_stat : 00
sch_stat : 02
s390_process_IRQ(000B) - irb for device 0047 after
channel check
00B6EAC0 05C24417 00B92B08 00020028 00807485
00B6EAD0 04000000 00000000 00000000 00000000
00B6EAE0 91408800 02000100 0C005000 00E01C47
00B6EAF0 00093485 54880047 0C47FF00 00000024
Channel-Check or Interface-Control-Check received
... device 0047 on subchannel 000B, dev_stat : 00
sch_stat : 02
s390_process_IRQ(000B) - irb for device 0047 after
channel check
00B6EAC0 05C24417 00B92B08 00020028 00807485
00B6EAD0 04000000 00000000 00000000 00000000
00B6EAE0 91408800 02000100 0C005000 00E01C47
00B6EAF0 000A3485 54880047 0C47FF00 00000014
Channel-Check or Interface-Control-Check received
... device 050B on subchannel 04A9, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04A9) - irb for device 050B after
channel check
00B922C0 05C24417 00BA4708 00020028 00807485
00B922D0 04000000 00000000 00000000 00000000
00B922E0 91408800 02000100 0C005000 00E01C0B
00B922F0 000B3485 5488050B 0C0BFF03 00000024
Channel-Check or Interface-Control-Check received
... device 050B on subchannel 04A9, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04A9) - irb for device 050B after
channel check
00B922C0 05C24417 00BA4708 00020028 00807485
00B922D0 04000000 00000000 00000000 00000000
00B922E0 91408800 02000100 0C005000 00E01C0B
00B922F0 000C3485 5488050B 0C0BFF02 00000014
Channel-Check or Interface-Control-Check received
... device 050B on subchannel 04A9, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04A9) - irb for device 050B after
channel check
00B922C0 05C24417 00BA4708 00020028 00807485
00B922D0 04000000 00000000 00000000 00000000
00B922E0 91408800 02000100 0C005000 00E01C0B
00B922F0 000D3485 5488050B 0C0BFF01 00000024
Channel-Check or Interface-Control-Check received
... device 050B on subchannel 04A9, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04A9) - irb for device 050B after
channel check
00B922C0 05C24417 00BA4708 00020028 00807485
00B922D0 04000000 00000000 00000000 00000000
00B922E0 91408800 02000100 0C005000 00E01C0B
00B922F0 000E3485 5488050B 0C0BFF00 00000014
Channel-Check or Interface-Control-Check received
... device 050B on subchannel 04A9, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04A9) - irb for device 050B after
channel check
00B922C0 05C24417 00BA4708 00020028 00807485
00B922D0 04000000 00000000 00000000 00000000
00B922E0 91408800 02000100 0C005000 00E01C0B
00B922F0 000F3485 5488050B 0C0BFF00 00000024
Channel-Check or Interface-Control-Check received
... device 050C on subchannel 04AD, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04AD) - irb for device 050C after
channel check
00B924C0 05C24417 00BA4808 00020028 00807485
00B924D0 04000000 00000000 00000000 00000000
00B924E0 91408800 02000100 0C005000 00E01C0C
00B924F0 00103485 5488050C 0C0CFF03 00000004
Channel-Check or Interface-Control-Check received
... device 050C on subchannel 04AD, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04AD) - irb for device 050C after
channel check
00B924C0 05C24417 00BA4808 00020028 00807485
00B924D0 04000000 00000000 00000000 00000000
00B924E0 91408800 02000100 0C005000 00E01C0C
00B924F0 00113485 5488050C 0C0CFF02 00000024
Channel-Check or Interface-Control-Check received
... device 050C on subchannel 04AD, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04AD) - irb for device 050C after
channel check
00B924C0 05C24417 00BA4808 00020028 00807485
00B924D0 04000000 00000000 00000000 00000000
00B924E0 91408800 02000100 0C005000 00E01C0C
00B924F0 00123485 5488050C 0C0CFF01 00000004
Channel-Check or Interface-Control-Check received
... device 050C on subchannel 04AD, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04AD) - irb for device 050C after
channel check
00B924C0 05C24417 00BA4808 00020028 00807485
00B924D0 04000000 00000000 00000000 00000000
00B924E0 91408800 02000100 0C005000 00E01C0C
00B924F0 00133485 5488050C 0C0CFF00 00000024
Channel-Check or Interface-Control-Check received
... device 050C on subchannel 04AD, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04AD) - irb for device 050C after
channel check
00B924C0 05C24417 00BA4808 00020028 00807485
00B924D0 04000000 00000000 00000000 00000000
00B924E0 91408800 02000100 0C005000 00E01C0C
00B924F0 00143485 5488050C 0C0CFF00 00000004
Channel-Check or Interface-Control-Check received
... device 050D on subchannel 04B1, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04B1) - irb for device 050D after
channel check
00B926C0 05C24417 00BA4908 00020028 00807485
00B926D0 04000000 00000000 00000000 00000000
00B926E0 91408800 02000100 0C005000 00E01C0D
00B926F0 00153485 5488050D 0C0DFF03 00000024
Channel-Check or Interface-Control-Check received
... device 050D on subchannel 04B1, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04B1) - irb for device 050D after
channel check
00B926C0 05C24417 00BA4908 00020028 00807485
00B926D0 04000000 00000000 00000000 00000000
00B926E0 91408800 02000100 0C005000 00E01C0D
00B926F0 00163485 5488050D 0C0DFF02 00000004
Channel-Check or Interface-Control-Check received
... device 050D on subchannel 04B1, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04B1) - irb for device 050D after
channel check
00B926C0 05C24417 00BA4908 00020028 00807485
00B926D0 04000000 00000000 00000000 00000000
00B926E0 91408800 02000100 0C005000 00E01C0D
00B926F0 00173485 5488050D 0C0DFF01 00000004
Channel-Check or Interface-Control-Check received
... device 050D on subchannel 04B1, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04B1) - irb for device 050D after
channel check
00B926C0 05C24417 00BA4908 00020028 00807485
00B926D0 04000000 00000000 00000000 00000000
00B926E0 91408800 02000100 0C005000 00E01C0D
00B926F0 00183485 5488050D 0C0DFF00 00000014
Channel-Check or Interface-Control-Check received
... device 050D on subchannel 04B1, dev_stat : 00
sch_stat : 02
s390_process_IRQ(04B1) - irb for device 050D after
channel check
00B926C0 05C24417 00BA4908 00020028 00807485
00B926D0 04000000 00000000 00000000 00000000
00B926E0 91408800 02000100 0C005000 00E01C0D
00B926F0 00193485 5488050D 0C0DFF00 00000004
Calibrating delay loop... 299.00 BogoMIPS
Memory: 508156k/524288k available (1691k kernel code,
0k reserved, 654k data, 52k init)
Dentry-cache hash table entries: 65536 (order: 7,
524288 bytes)
Inode-cache hash table entries: 32768 (order: 6,
262144 bytes)
Mount-cache hash table entries: 8192 (order: 4, 65536
bytes)
Buffer-cache hash table entries: 32768 (order: 5,
131072 bytes)
Page-cache hash table entries: 131072 (order: 7,
524288 bytes)
debug: Initialization complete
POSIX conformance testing by UNIFIX
Detected 2 CPU's
Boot cpu address 0
cpu 0 phys_idx=0 vers=53 ident=045736 machine=9672
unused=0000
Waiting on wait_init_idle (map = 0x2)
cpu 1 phys_idx=1 vers=53 ident=145736 machine=9672
unused=0000
All processors have done init_idle
init_mach : starting machine check handler
mach_handler : ready
mach_handler : waiting for wakeup
init_mach : machine check buffer : head = 0021BEFC
init_mach : machine check buffer : tail = 0021BF00
init_mach : machine check buffer : free = 0021BF04
init_mach : CRW entry buffer anchor = 0021BF08
init_mach : machine check handler ready
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society
NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Diskquotas version dquot_6.4.0 initialized
Journalled Block Device driver loaded
devfs: v1.7 (20011216) Richard Gooch
(rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
pty: 256 Unix98 ptys configured
devfs: devfs_register(ttyS): could not append to
parent, err: -17
block: 128 slots per queue, batch=32
RAMDISK driver initialized: 16 RAM disks of 24576K
size 1024 blocksize
dasd: initializing...
debug: dasd: new level 3
dasd: Registered successfully to major no 94
dasd(eckd): ECKD discipline initializing
dasd(eckd): /dev/dasda ( 94: 0),0103@13f:
3380/1E(CU:3990/02) Cyl:2655 Head:15 Sec:222
dasd(eckd): /dev/dasda ( 94: 0),0103@13f:
3380/1E(CU:3990/02): Configuration data read
debug: dasda: new level 3
dasd: waiting for responses...
dasd(eckd): /dev/dasda ( 94: 0),0103@13f: (4kB
blks): 1593000kB at 40kB/trk compatible disk layout
Partition check:
/dev/dasd/0103:VOL1/ LXDEB3: p1 p2 p3
dasd(eckd): We are interested in: CU 3880/00
dasd(eckd): We are interested in: CU 3990/00
dasd(eckd): We are interested in: CU 2105/00
dasd(eckd): We are interested in: CU 9343/00
dasd: Registered ECKD discipline successfully
dasd(fba): FBA discipline initializing
dasd(fba): We are interested in: Dev 9336/00 @ CU
6310/00
dasd(fba): We are interested in: Dev 3370/00 @ CU
3880/00
dasd: Registered FBA discipline successfully
dasd: initialization finished
debug: cio_msg: new level 2
debug: cio_trace: new level 2
debug: cio_crw: new level 6
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 32Kbytes
TCP: Hash tables configured (established 65536 bind
65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 13k freed
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on dasd(94,1),
internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on dasd(94,2),
internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on dasd(94,3),
internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Starting lcs module $Revision: 1.128 $ $Date:
2002/03/01 16:56:47 $
with chandev support,with multicast support, with
ethernet support, with token ring support.
debug: lcs: new level 0
lcs_sleepon network card taking time responding
irq=0024 devno=0070,
please be patient, ctrl-c will exit if shell prompt is
available.
qipassist failed, ipassists assumed unsupported for
eth0
lcs: eth0 configured as follows read subchannel=24
write subchannel=25
read_devno=0070 write_devno=0071
hw_address=10:00:5A:D4:31:72 rel_adapter_no=0
debug: lcs: new level 0
s390_do_machine_check : starting ...
crw_info : looking for CRWs ...
crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=4,
anc=0, erc=3, rsid=91
s390_do_machine_check : done
mach_handler : wakeup ...
do_crw_pending : starting ...
do_crw_pending : source is channel path 91
do_crw_pending : done
mach_handler : nothing to do, sleeping
mach_handler : waiting for wakeup
s390_do_machine_check : starting ...
crw_info : looking for CRWs ...
crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=4,
anc=0, erc=3, rsid=91
s390_do_machine_check : done
mach_handler : wakeup ...
do_crw_pending : starting ...
do_crw_pending : source is channel path 91
do_crw_pending : done
mach_handler : nothing to do, sleeping
mach_handler : waiting for wakeup
s390_do_machine_check : starting ...
crw_info : looking for CRWs ...
crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=4,
anc=0, erc=3, rsid=91
s390_do_machine_check : done
mach_handler : wakeup ...
do_crw_pending : starting ...
do_crw_pending : source is channel path 91
do_crw_pending : done
mach_handler : nothing to do, sleeping
mach_handler : waiting for wakeup
s390_do_machine_check : starting ...
crw_info : looking for CRWs ...
crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=4,
anc=0, erc=3, rsid=91
s390_do_machine_check : done
mach_handler : wakeup ...
do_crw_pending : starting ...
do_crw_pending : source is channel path 91
do_crw_pending : done
mach_handler : nothing to do, sleeping
mach_handler : waiting for wakeup
dasd: /proc/dasd/devices: 'add device range=102'
dasd(eckd): /dev/dasdb ( 94: 4),0102@13e:
3380/1E(CU:3990/02) Cyl:2655 Head:15 Sec:222
dasd(eckd): /dev/dasdb ( 94: 4),0102@13e:
3380/1E(CU:3990/02): Configuration data read
debug: dasdb: new level 3
dasd: waiting for responses...
dasd(eckd): /dev/dasdb ( 94: 4),0102@13e: (4kB
blks): 1593000kB at 40kB/trk compatible disk layout
/dev/dasd/0102:VOL1/ LXDEB2: p1 p2 p3
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on dasd(94,5),
internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding Swap: 524272k swap-space (priority -1)
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on dasd(94,7),
internal journal
EXT3-fs: mounted filesystem with ordered data mode.
maracana:~# ls~~VFS: Diskquotas version dquot_6.4.0
initialized
su: ls~~VFS:: command not found
maracana:~# Journalled Block Device driver loaded
su: Journalled: command not found
maracana:~# devfs: v1.7 (20011216) Richard Gooch
(rgooch@atnf.csiro.au)
su: syntax error near unexpected token `(2'
maracana:~# devfs: boot_options: 0x1
su: devfs:: command not found
maracana:~# pty: 256 Unix98 ptys configured
su: pty:: command not found
maracana:~# devfs: devfs_register(ttyS): could not
append to parent, err: -17
su: syntax error near unexpected token
`devfs_register(t'
maracana:~# block: 128 slots per queue, batch=32
su: block:: command not found
maracana:~# RAMDISK driver initialized: 16 RAM disks
of 24576K size 1024 blocksize
su: RAMDISK: command not found
maracana:~# dasd: initializing...
su: dasd:: command not found
maracana:~#
Thanks for any help
=====
[]´s
Marco Antônio
______________________________________________________________________
Yahoo! Mail: 6MB, anti-spam e antivírus gratuito! Crie sua conta agora:
http://mail.yahoo.com.br
Reply to: