November 1998 - openSUSE Users - openSUSE Mailing Lists

[SuSE Linux] network cards
by luca＠thehub.co.uk 10 Nov '98

10 Nov '98

Hi, I'm having a problem with the installation of a second network card. I use Linux SuSE 5.2 with Kernel 2.0.34 The two network cards are: - SMC EtherPower II 10/100 PCI - 3Com EtherLink III 10 ISA The card are correctly probed at boot up. 'ifconfig eth0/eth1', 'netstat -in' and 'dmesg | grep eth0/eth1' confirm my theory. The cards use two different IP address and are on the same network. The problem is that I can only ping one of the two cards (SMC) the other seams not receiving any signal (3Com). I have used different cables as well to test the connection but with no luck. Any advice? -- Luca Colombi System Administrator The Hub Communications Co. Ltd. The Farmhouse Syon Park Middlesex TW8 8JF Tel: +44(0)181 560 9222 Fax: +44(0)181 560 9333 E-mail: luca(a)thehub.co.uk URL: <A HREF="http://www.thehub.co.uk"><A HREF="http://www.thehub.co.uk</A">http://www.thehub.co.uk</A</A>> - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [SuSE Linux] Printing woes
by chandlerrick＠hotmail.com 10 Nov '98

10 Nov '98

>> Please help!!! I've been using Linux for about a year and a half >>and have never set up printing before. >1. Ensure packages lprold and apsfilter are installed. >2. Incorporate your printer into your installation using YaST. >3. Send your text to the print queue, not the device: cat test.txt | >lpr >4. Let us know if this fixes it. > >George Got it going! What I had to do was this lp1=0x378,7 ; tunelp lp1 -i7 After that it started working! Still have no clue as why. Thanks to all.. ______________________________________________________ Get Your Private, Free Email at <A HREF="http://www.hotmail.com"><A HREF="http://www.hotmail.com</A">http://www.hotmail.com</A</A>> - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

[SuSE Linux] Observations and questions
by j.logsdon＠lancaster.ac.uk 10 Nov '98

10 Nov '98

Hello As a new SuSE 5.3 user I have a few questions and observations. 1 I have a problem mounting my SuSE machine from RH4.1 Vanderbilt. Yes I will in due course load SuSE on that m/c but it needs a considerable hardware upgrade. The problem is that: mount -t nfs SuSE:/ /SuSEmnt ie mounting the SuSE root sytem onto a mount point on the RH system, enables me to do ls /SuSEmnt which gives all the SuSE root directories, as expected but ls -l /SuSEmnt or any other operation to look at the real files, gives a Permissions denied message. I have checked that the /etc/exports file on the SuSE m/c is mounted (rw,no_root_squash) and that root has UID and GID of zero(0) on both machines and everything else I can think of but to no avail. Mounting the other way round is not a problem. Any clues? I have posted a question on the Manchester mailing list, which contains some experts, but no solution has been forthcoming other than checking with showmount and rpcinfo etc. 2 I have a few observations re YaST. 2.1 One of the PC's which has SuSE 5.3 mounted had, it turned out, a dodgy hard disk and a sligtly flaky CD. With YaST, (whats this with capitals other than at the beginning of a word? From now on, it is yast and suse to save my little finger!) you cannot go into fdisk proper so I could not get into the disk system. You only have the opportunity to format the partition as native Linux and swap. I think this should be changed to allow the user to access fdisk, as the RH installation tool does. This also helped on another machine where the partitioning had to be changed but I couldn't repartition for MSDOS. 2.2 I had a number of cases (I think due to the CD) where an error -1 or worse -2 arose during installation. Yast (well you have to have a capital letter at the beginning of the sentence) just returns to the Start Installation and then tries to reinstall the failed package again. This does not exercise the CD and so the same occurs all over again. The solution I used was to restart completely but I think yast should (i) skip over a faulted package and collect them all for a final installation try at the end and (ii) provide a proper Back and Abort facility. The Abort does not work properly. 3 Someone posted that they were wondering what SuperSocket7 board worked. On a separate PC, which is actually dedicated to Windows at the moment, dispalyed via VNC on my susebox, I have 5.3 mounted OK. The board is a TX Pro 100 with an AGP slot, model M577, and 128Mb of 100MHz memory. I had problems with the AGP slot and so currently have an S3Virge card in it and I found that you needed to put the CD on IDE2 as master since the installation froze if it was a slave on IDE1. Since this motherboard comes in at 41UKP, it is a good bargain. I am running the AMD K6/II 350 Mhz chip quite OK on it. TIA for suggestions re 1 above John - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

RE: [SuSE Linux] Creating floppy
by Bjorn.W.Nilsson＠edt.ericsson.se 10 Nov '98

10 Nov '98

Hi! The /floppy directory is an ordinary directory. "mkdir /floppy" will do just fine. Björn -----Original Message----- From: G.C.Newson(a)warwick.ac.uk [<A HREF="mailto:mavlj@csv.warwick.ac.uk">mailto:mavlj@csv.warwick.ac.uk</A>] Sent: Tuesday, November 10, 1998 10:51 AM To: suse-linux-e(a)suse.com Subject: [SuSE Linux] Creating floppy On Sun, 8 Nov 1998, zentara wrote: > > As root: > > mount -t vfat /dev/fd0 /floppy > or > mount -t msdos /dev/fd0 /floppy > > > then umount /floppy > > Of course, you must have /floppy already created, but you > can mount it anywhere such as /mnt, or /A, etc > How do you create /floppy? Geoff Newson. - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [SuSE Linux] String search in all text files
by Michael.Salmon＠uab.ericsson.se 10 Nov '98

10 Nov '98

+----- On Sat, 07 Nov 1998 17:29:51 EST, "Casey Bralla" writes: | | I want to search every file on my hard disk for a specific | text string. Anybody got a simple way of doing this? You probably don't want to do that but if you really must: find / -type f -print | xargs -e egrep "text string" You will probably want to include a -size option in the find command so that you don't search large binaries and an -fstype if you NFS mount file systems. /Michael - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

[SuSE Linux] Creating floppy
by mavlj＠csv.warwick.ac.uk 10 Nov '98

10 Nov '98

On Sun, 8 Nov 1998, zentara wrote: > > As root: > > mount -t vfat /dev/fd0 /floppy > or > mount -t msdos /dev/fd0 /floppy > > > then umount /floppy > > Of course, you must have /floppy already created, but you > can mount it anywhere such as /mnt, or /A, etc > How do you create /floppy? Geoff Newson. - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

2 1

[SuSE Linux] copying text from terminal output
by a-supde＠microsoft.com 10 Nov '98

10 Nov '98

Is there a way to copy text from a terminal screen into a file? I've got what appears to be a corrupted SuSE 5.3 boot disk, and I want to capture the text that displays when I try to mount it so that I can send to SuSE support. I've tried redirecting the output in various ways (note, these may not be entirely correct, as I'm pretty new to Linux): mount /dev/fd0 /mnt/floppy > err mount /dev/fd0 /mnt/floppy 2> err mount /dev/fd0 /mnt/floppy >& err

4 3

Re: [SuSE Linux] compiling qt libs 1.4x on suse 5.3
by hflaxman＠meganet.net 10 Nov '98

10 Nov '98

Lenz Grimmer wrote: > > If you are lazy, just grap the RPMs from > > <A HREF="ftp://ftp.suse.com/pub/suse_update/KDE/qt-1.41/"><A HREF="ftp://ftp.suse.com/pub/suse_update/KDE/qt-1.41/</A">ftp://ftp.suse.com/pub/suse_update/KDE/qt-1.41/</A</A>> > > Please also read README.qt-1.41 in this directory! It contains imortant > installation notes. Did this and downloaded the qtdevel.rpm twice and twice got a segmentation fault. Harry -- Harry Flaxman ICQ: 22086907 <A HREF="http://web.meganet.net/hflaxman/"><A HREF="http://web.meganet.net/hflaxman/</A">http://web.meganet.net/hflaxman/</A</A>> - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

2 1

[SuSE Linux] What does S.u.S.E. stand for?
by elum＠ibm.net 10 Nov '98

10 Nov '98

Just curious, what do the letters in SuSE stand for? Eric - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

2 1

Re: [SuSE Linux] SuSE 5.3 initial boot failure
by jpg＠hpcvsjpg.cv.hp.com 10 Nov '98

10 Nov '98

Nevermind about the fdisk and initial boot failure. I did a total re-install of SuSE on '/dev/sdb' and this time the final reboot, after Yast was done, went fine. Got a new and similar problem though. LILO cannot boot off of /dev/sdb1 now, I have to boot off of SuSE CD #1, load the SCSI modules and then select 'Boot Installed System', it queries me for the disk to boot from, I enter '/dev/sdb1' and everything is fine. I use PowerBoot boot manager to allow me to use the NT boot manager on '/dev/sda' and LILO boot manager on '/dev/sdb'. The PowerBoot manager is working on 5 other systems similarly configured, so I know I can eliminate it. Here is the contents of '/etc/lilo.conf' on /dev/sdb1 ========================================================================== # LILO Konfigurations-Datei # Start LILO global Section boot=/dev/sdb1 #compact # faster, but won't work on all systems. read-only prompt timeout=10 vga = normal # force sane state # End LILO global section # Linux bootable partition config begins image = /vmlinuz root = /dev/sdb1 label = suse_linux # Linux bootable partition config ends # ========================================================================== I successfully execute '/sbin/lilo' after modifying the '/etc/lilo.conf' file, yet during the boot LILO complains with: ========================================================================== You may be trying to booot from an unformatted diskette or hard driver partition Insert a bootable diskette into drive a. Press any key to boot ... ========================================================================== I even tried configuring through Yast, same results. Below is the output of fdisk /dev/sdb with option 'p' pressed: ========================================================================== # fdisk /dev/sdb The number of cylinders for this disk is set to 2048. This is larger than 1024, and may cause problems with: 1) software that runs at boot time (e.g., LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): p Disk /dev/sdb: 64 heads, 32 sectors, 2048 cylinders Units = cylinders of 2048 * 512 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 1920 1966064 83 Linux native /dev/sdb2 1921 2048 131072 82 Linux swap ========================================================================== Anybody got a guess as to why LILO won't accept booting off of /dev/sdb ?? John Griffin jpg(a)cv.hp.com > The partitioning of the disk looks to be the problem. > > This system has two disks, the first disk at '/dev/sda1' is NT 4.0, and the > second disk at '/dev/sdb[1-3]' is the SuSE Linux disk. > > When I run 'fdisk /dev/sda1' and then press 'p' for print partition table > it shows the size of the NT partition, that it is bootable and active. > > Then when I run 'fdisk /dev/sdb1' and press 'p', no information is printed > for the Linux partition. I get the standard banner for 'p' but no information > about size, cyl, bootable, etc. is displayed. > > The linux '/sbin/fdisk' doesn't seem to be able to change any of the > flags associated with this partition. When I press 'a (Toggle bootable flag)' > it then asks 'Partition [1-4]', in selecting any of the partitions 1 through > 4, it comes back with 'partition [1-4] has empty type'. I then exit with > 'w write table to disk and exit' and then reboot, yields no difference. > I have no clue as to what it wants for 'Partition [1-4]' since I only have > three partitions: > > /dev/sdb1 -> boot > /dev/sdb2 -> swap > /dev/sdb3 -> root (/) > > Also after successfully exiting Linux's /sbin/fdisk with a 'w' option, > subsequent calls to 'fdisk /dev/sdb1' show no partition information (using > 'p' option) for the linux disk. > > I am not an MS/NT4.0 admin so I don't know if it even has fdisk to mark > a disk bootable/active. And if it does, I wouldn't know where to begin > looking for it. I tried the > 'Start->Programs->Administrative Tools->Disk Administrator' tool, yet it > doesn't seem to allow marking a partition active/bootable either. I also > looked under the '\windows\system32' directory for executables that looked > like an 'fdisk', but no luck. > > Any other clues would be helpful?? > > John Griffin > jpg(a)cv.hp.com > > > > > "John P. Griffin" <jpg(a)hpcvsjpg.cv.hp.com> wrote: > > > > > > In the process of installing SuSE 5.3 on another computer (HP Kayak XU) > > > and after successfully going through the complete install, Yast, and > > > configuring LILO. Rebooted the system. > > > > > > Everything looks good during the boot, up until right after the partition > > > check, below is the console output during boot, at the point of failure. > > > > > > ===================================== > > > Partition check: > > > sda: sda1 > > > sdb: sdb1 sdb2 sdb3 > > > VFS: Mounted root (ext2 filesystem) readonly. > > > Unable to open an initial console > > > ===================================== > > > > > > At this point the system hangs. > > > Any clues as to what went wrong with my install??? > > > > > > I had the same problem. Do you have the boot drive set up as bootable > > in fdisk ? Do you have a boot disk to check the lilo/kernel ? > > > > I just added the bootable drive flag and I was OK. > > > > -Dee > > > > > > W.D.McKinney (Dee) deem(a)wdm.com > > Faith is acting on your passions & beliefs. > > - > > To get out of this list, please send email to majordomo(a)suse.com with > > this text in its body: unsubscribe suse-linux-e > > > -- > > -- - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0