Setting up Printers
I am trying to set up an HP 4050N printer on a Red Hat Linux v7.2 virtual machine running Samba v2.21 . The server IP is 172.17.60.6, and the printer IP is 172.16.0.116 . Since they appear to be on different subnets, I was inclined to suspect that I simply needed to specify 172.16.0.255 in the remote announce field. Here are some other pertinent settings: [global] workgroupcofrny netbios name cofr3 interfaces 172.16.60.6/255.255.255.0 security DOMAIN printing sysv map to guest Bad User preferred master TRUE local masterYES domain masterTRUE dns proxy Yes wins server 172.16.0.121 [bhrshp1] path/var/spool/lpd/bhrshp1 valid users root,illingsk,@Treasury printable Yes After restarting the Samba daemons, I still could not locate the printer via the add new printer wizard on a Win2kPro workstation. I am struggling to ascertain what else should be done. Can you help? Thank you in advance for your time.
Problems with adding dasd device (2.4 kernel)
RH 7.2 in an LPAR (2.4.9-38tape) Does anyone see the mistake here? # echo -n add device range=7675-7677 /proc/dasd/devices (/var/log/messages says: kernel: dasd:/proc/dasd/devices: 'add device range=7675-7677 ') # cat /proc/dasd/devices 6b40(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 601020 blocks, 2347 MB 6b41(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 601020 blocks, 2347 MB 6b42(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 601020 blocks, 2347 MB 6b43(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc0(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc1(ECKD) at ( 94: 20) is dasdf : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc2(ECKD) at ( 94: 24) is dasdg : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc3(ECKD) at ( 94: 28) is dasdh : active at blocksize: 4096, 601020 blocks, 2347 MB 7675(none) at ( 94: 32) is dasdi : unknown 7676(none) at ( 94: 36) is dasdj : unknown 7677(none) at ( 94: 40) is dasdk : unknown # dasdfmt --label=LNX001 --device=/dev/dasdi Please enter the blocksize of the formatting [4096]: dasdfmt: error opening device /dev/dasdi: No such device (/var/log/messages says: kernel: dasd:No device registered as (94:32)) # ls -l /dev/dasdi brw-rw1 root disk 94, 32 Sep 23 2001 /dev/dasdi # echo -n set device range=7675-7677 on /proc/dasd/devices # cat /proc/dasd/devices 6b40(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 601020 blocks, 2347 MB 6b41(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 601020 blocks, 2347 MB 6b42(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 601020 blocks, 2347 MB 6b43(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc0(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc1(ECKD) at ( 94: 20) is dasdf : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc2(ECKD) at ( 94: 24) is dasdg : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc3(ECKD) at ( 94: 28) is dasdh : active at blocksize: 4096, 601020 blocks, 2347 MB 7675(none) at ( 94: 32) is dasdi : unknown 7676(none) at ( 94: 36) is dasdj : unknown 7677(none) at ( 94: 40) is dasdk : unknown For more background info, the new address range is carved up as Mod-9's. I plan on moving from the 8 volumes to the 3. What does it take to register these devices? Thanks ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
Network connections
I have cloned an image of Linux. SuSE 7.0 - 2.2.16 I checked /etc/rc.config, /etc/route.conf and have found nothing in these files. Is there another way to change the IP address of this image and the peer address. I'm using VCTC 900 901 how do I define these to Linux, they are in both tcpip and linux directory entry and I have a couple statement in the profile exec's. This Linux image was installed by someone else and I don't have any documentation about the installation or modifications.
mkraid failure
I thought I was doing everything right, based on all the HOWTOs and such, but it's not working for me. The DASD devices have been formatted, and I even put an ext2 file system on them (out of desperation). I can mount them as ext2 file systems, so I know they're accessible. # cat /proc/dasd/devices 0300(ECKD) at (94:0) is dasda:active at blocksize: 4096, 600840 blocks, 2347 MB 0301(ECKD) at (94:4) is dasdb:active at blocksize: 4096, 600840 blocks, 2347 MB 0302(ECKD) at (94:8) is dasdc:active at blocksize: 4096, 600840 blocks, 2347 MB 0303(ECKD) at (94:12) is dasdd:active at blocksize: 4096, 600840 blocks, 2347 MB 0400(FBA ) at (94:64) is dasdq:active at blocksize: 512, 50 blocks, 244 MB 0401(ECKD) at (94:68) is dasdr:active at blocksize: 4096, 600840 blocks, 2347 MB Here's my /etc/raidtab: raiddev /dev/md0 raid-level linear nr-raid-disks 2 persistent-superblock 1 chunk-size 64k device /dev/dasdc1 raid-disk 0 device /dev/dasdd1 raid-disk 1 I have the linear.o module loaded, and /proc/mdstat shows that: Personalities : [1 linear] read_ahead not set md0 : inactive md1 : inactive md2 : inactive md3 : inactive The device node is defined: brw-r-1 root root 9, 0 Apr 1 1998 /dev/md0 But, when I issue the mkraid command, I get an error: # mkraid /dev/md0 handling MD device /dev/md0 analyzing super-block disk 0: /dev/dasdc1, 2403348kB, raid superblock at 2403264kB disk 1: /dev/dasdd1, 2403348kB, raid superblock at 2403264kB mkraid: aborted, see the syslog and /proc/mdstat for potential clues. But, there are no messages in /var/log/messages, or dmesg, or anywhere else that I can see. Anybody have any ideas? Mark Post
Re: Network connections
To set up your vCTC PtP connection you should edit /etc/chandev.conf
There should be a line :
ctc0,0x900,0x901
In your /etc/rc.config you should also modify the network interface
On Mon, 9 Dec 2002, Abruzzese, Pat wrote:
I have cloned an image of Linux. SuSE 7.0 - 2.2.16 I checked /etc/rc.config,
/etc/route.conf and have found nothing in these files. Is there another way
to change the IP address of this image and the peer address. I'm using VCTC
900 901 how do I define these to
Linux, they are in both tcpip and linux directory entry and I have a couple
statement in the profile exec's. This Linux image was installed by someone
else and I don't have any documentation about the installation or
modifications.
---
[EMAIL PROTECTED]
---
(' - WARP :: http://www.warp.be
//\ - Asian Project :: http://www.clients.warp.be/asianproject
v_/_- Industria :: http://www.industria.be
---
Re: Network connections
Davy,
Except he's running 2.2.16, which doesn't have chandev. In 2.2.16, the
driver parameters are either specified on the parmline for the kernel, or in
/etc/modules.conf.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of
Davy Michiels
Sent: Monday, December 09, 2002 4:57 PM
To: [EMAIL PROTECTED]
Subject: Re: Network connections
To set up your vCTC PtP connection you should edit /etc/chandev.conf
There should be a line :
ctc0,0x900,0x901
In your /etc/rc.config you should also modify the network interface
On Mon, 9 Dec 2002, Abruzzese, Pat wrote:
I have cloned an image of Linux. SuSE 7.0 - 2.2.16 I checked
/etc/rc.config,
/etc/route.conf and have found nothing in these files. Is there another
way
to change the IP address of this image and the peer address. I'm using
VCTC
900 901 how do I define these to
Linux, they are in both tcpip and linux directory entry and I have a
couple
statement in the profile exec's. This Linux image was installed by
someone
else and I don't have any documentation about the installation or
modifications.
---
[EMAIL PROTECTED]
---
(' - WARP :: http://www.warp.be
//\ - Asian Project :: http://www.clients.warp.be/asianproject
v_/_- Industria :: http://www.industria.be
---
Re: Network connections
Pat, You need to go back and look again. Here are the relevant lines from /etc/rc.config on my LCDS image: # # IP Adresses # IPADDR_0=10.1.15.62 # # network device names (e.g. eth0) # NETDEV_0=iucv0 # # parameteres for ifconfig, simply enter bootp or dhcpclient to use the # respective service for configuration # sample entry for ethernet: # IFCONFIG_0=192.168.81.38 broadcast 192.168.81.63 netmask 255.255.255.224 # IFCONFIG_0=10.1.15.62 pointopoint 10.1.15.61 mtu 1500 up Once you've updated the file, run /sbin/SuSEconfig to update all the files that are fed from /etc/rc.config. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Abruzzese, Pat Sent: Monday, December 09, 2002 2:37 PM To: [EMAIL PROTECTED] Subject: Network connections I have cloned an image of Linux. SuSE 7.0 - 2.2.16 I checked /etc/rc.config, /etc/route.conf and have found nothing in these files. Is there another way to change the IP address of this image and the peer address. I'm using VCTC 900 901 how do I define these to Linux, they are in both tcpip and linux directory entry and I have a couple statement in the profile exec's. This Linux image was installed by someone else and I don't have any documentation about the installation or modifications.
Problem loading qesh module
I've installed the 2.4.7 kernel / Suse. Originally installed using a virtual ctc connection. Now I would like to begin using the OSA connection. I searched the archives and came up with the following procedure to load the qeth module: insmod qdio this works fine no problems insmod qeth qeth_options=noauto,0x0206,0x0207,0x0208,portname:hallole I get this error: /lib/modules/2.4.7-SuSE-SMP/net/qeth.o: invalid parameter parm_qeth_options What format is format for specifying parameters to qeth? Is it different for the 2.4 kernel? Thanks. Rich ASG
Re: Problem loading qesh module
Rich, Yes, it is, due to chandev. In /etc/chandev, put something like this: noauto;add_parms,0x10,0x0206,0x0207,0x0208,portname:hallole Double check that portname. If other systems are sharing that card, most likely it has been specified in all upper case letters. If so, you must specify it in all upper case for this system as well. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Rich Blair Sent: Monday, December 09, 2002 6:46 PM To: [EMAIL PROTECTED] Subject: Problem loading qesh module I've installed the 2.4.7 kernel / Suse. Originally installed using a virtual ctc connection. Now I would like to begin using the OSA connection. I searched the archives and came up with the following procedure to load the qeth module: insmod qdio this works fine no problems insmod qeth qeth_options=noauto,0x0206,0x0207,0x0208,portname:hallole I get this error: /lib/modules/2.4.7-SuSE-SMP/net/qeth.o: invalid parameter parm_qeth_options What format is format for specifying parameters to qeth? Is it different for the 2.4 kernel? Thanks. Rich ASG
IPL device number
Is there a single command or file somewhere in RH7.2 that will reveal the device name/number from which the RH7.2 LPAR was IPLed? Thanks, Paul
Re: Problems with adding dasd device (2.4 kernel)
Daniel, This looks kind of like a new CHP and devices were added to the LPAR, and the equivalent of an MVS config online wasn't done. The reason I say that is that when you add devices this way, and they're not detected, you get the symptoms you're seeing. One of the few situations where this happens is when a brand new channel path is added to an LPAR without either doing a power-on reset, or configuring it online to the LPAR. If that is the case, you should be able to do that from the service console. If that isn't the case, then I would have to think about it some more. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Jarboe Sent: Monday, December 09, 2002 10:54 AM To: [EMAIL PROTECTED] Subject: Problems with adding dasd device (2.4 kernel) RH 7.2 in an LPAR (2.4.9-38tape) Does anyone see the mistake here? # echo -n add device range=7675-7677 /proc/dasd/devices (/var/log/messages says: kernel: dasd:/proc/dasd/devices: 'add device range=7675-7677 ') # cat /proc/dasd/devices 6b40(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 601020 blocks, 2347 MB 6b41(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 601020 blocks, 2347 MB 6b42(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 601020 blocks, 2347 MB 6b43(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc0(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc1(ECKD) at ( 94: 20) is dasdf : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc2(ECKD) at ( 94: 24) is dasdg : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc3(ECKD) at ( 94: 28) is dasdh : active at blocksize: 4096, 601020 blocks, 2347 MB 7675(none) at ( 94: 32) is dasdi : unknown 7676(none) at ( 94: 36) is dasdj : unknown 7677(none) at ( 94: 40) is dasdk : unknown # dasdfmt --label=LNX001 --device=/dev/dasdi Please enter the blocksize of the formatting [4096]: dasdfmt: error opening device /dev/dasdi: No such device (/var/log/messages says: kernel: dasd:No device registered as (94:32)) # ls -l /dev/dasdi brw-rw1 root disk 94, 32 Sep 23 2001 /dev/dasdi # echo -n set device range=7675-7677 on /proc/dasd/devices # cat /proc/dasd/devices 6b40(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 601020 blocks, 2347 MB 6b41(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 601020 blocks, 2347 MB 6b42(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 601020 blocks, 2347 MB 6b43(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc0(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc1(ECKD) at ( 94: 20) is dasdf : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc2(ECKD) at ( 94: 24) is dasdg : active at blocksize: 4096, 601020 blocks, 2347 MB 6bc3(ECKD) at ( 94: 28) is dasdh : active at blocksize: 4096, 601020 blocks, 2347 MB 7675(none) at ( 94: 32) is dasdi : unknown 7676(none) at ( 94: 36) is dasdj : unknown 7677(none) at ( 94: 40) is dasdk : unknown For more background info, the new address range is carved up as Mod-9's. I plan on moving from the 8 volumes to the 3. What does it take to register these devices? Thanks ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
Re: Setting up Printers
On Mon, 9 Dec 2002 22:29, you wrote: I am trying to set up an HP 4050N printer on a Red Hat Linux v7.2 virtual machine running Samba v2.21 . The server IP is 172.17.60.6, and the printer IP is 172.16.0.116 . Since they appear to be on different subnets, I was inclined to suspect that I simply needed to specify 172.16.0.255 in the remote announce field. I'm not familiar with the printer, but I would expect it to emulate a Unix printer. If so, wouldn't lpd, LPRng or CUPS be a better way to access it? Then you can share it as a local (to your server) printer, and that just happens. -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Join the Linux Support by Small Businesses list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Re: IPL device number
Paul, I'm not aware of anything like that on any distribution. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of paultz Sent: Monday, December 09, 2002 8:03 PM To: [EMAIL PROTECTED] Subject: IPL device number Is there a single command or file somewhere in RH7.2 that will reveal the device name/number from which the RH7.2 LPAR was IPLed? Thanks, Paul
[no subject]
I will be out of the office starting 12/09/2002 and will not return until 12/10/2002. In case of emergency, contact J.Michael Strom.
Re: IPL device number
At 20:03 09-12-02 -0500, paultz wrote: Is there a single command or file somewhere in RH7.2 that will reveal the device name/number from which the RH7.2 LPAR was IPLed? The subchannel address of your IPL device is stored in 0x10404 during the boot process, so if you have 'gdb' installed it goes like this: gdb -c /proc/kcore display the contents of 10404 x/x 0x10404 quit look for that subchannel address (the rightmost 2 bytes shown in gdb) in the list of devices, like with cat /proc/subchannels Rob
