December 2001 - openSUSE Users - openSUSE Mailing Lists

RadeonVE+AcceleratedX
by Sergei Rodionov 31 Dec '01

31 Dec '01

Hi, I am trying to get 7.3Pro to work with XiG's AcceleratedX (Summit 2.0 (2.0.3 platinum DX) my RadeonVE and so far only 2D seems to be OK.. Is there anyone who managed to configure 3D (i.e openGL) for such thing? B/c any gl-programm (glinfo, glxinfo, gears & etc) just segmentation faults on me.. :( (and FAQ from xig.com for Suse7.2 arent much help.. followed every single letter of it - still no luck) Thanks, Sergei -- Life is like a simile.

1 0

DMA in 7.3 only nodma for hda?
by Constant Brouerius van Nidek 31 Dec '01

31 Dec '01

>From my instalation with version 7.2 I know that from my 3 harddrives the hda does not like to have DMA put on. In 7.2 I could choose to not include hda. In 7.3 I heard that DMA is automatically put on. I can of course start with the failsafe possibility but would like to have DMA working on hdc and hdd (hdb is my cdrom). Could somebody instruct me how to proceed? Happy 2002

1 0

[/DEV/HDA] BIG BIG EMERGENCY! (was since 28092001)
by Oliver Ob 31 Dec '01

31 Dec '01

WHAT HAPPENED: ============== I am unable to access the harddrisk hda, I cannot read the partition table since: WHAT I DID: =========== I just executed lilo after changing the boot _order_ (boot dos second, linux first), nothing extraordinary really. Lilo completed correctly as always, but since then I cannot boot nor even access any partition n that hda. ERRORS: ======= error 0x40 uncorrectable error LBAsect=9 sector=0 end_request: I/O error dev 03:00 (hda) sector unable to read partition table It is according to badblocks a physical problem with bad sectors on my hd, which accidently cover precisely the first sectors (i.e. the partition table is dead), so we zero'ed the entire partition table AND NOW?: ========= Running fdisk /dev/hda says "cannot read partition data" Even trying with DOS6.22' DOS-FDISK (fdisk /mbr) did not bring me on, since it complains it cannot read/write the partition table. the disk hda is accessible via "dd" command, I can even output files on that dos partition such as config.sys to screen. The bios reads/autodetects the correct CHS data. EMERGENCY!!!!!!!!!!!!!!!!!!!!!!!!!!! REAL TROUBLE!!!!!!!! ========================================================= I need my data back. I cannot repartition hda, is there any tool to help me out of this desaster? Maybe this is a lilo bug? Since I have not done any thing to the data inside /etc/lilo.conf, only changed the order of appearance!!!! not more! HELP PLEEEEEEZ! -=================================================================- I included this original portion of my initial mail dated 28092001 to give you the background again, now what you advised me to do is "Rafael E. Herrera" wrote: > > I'd suggest you use the program "gpart" at: > > http://www.stud.uni-hannover.de/user/76201/gpart/ > > It is supposed to be able to recover a damaged partition. READ the > instructions. > I tried that one thanks, but either it has a bug or I have more problems: If I run gpart (265910 bytes long) I get "segmentation fault" only. Why is that? Originally I wanted to simply copy it onto a 3,5" disk and boot from rescue CD 1 and run gpart from disk then, but when it does not even work on a different machine? Since I do not have any sheet of paper where I have written down the partition borders, I am somehow stuck here. Isn't there a way of dd'ng the partition contents into an ISO image? maybe like dd if=/dev/hda of=image.iso skip=??? bs=512 count=??? Then how should I set the offset to skip and the counts? There are no further errors on that hd except for the 4 sectors 0,1, 130, 131 (0,1 apparently are the partition table): badblocks -b512 -o /test /dev/hda 1000 gave me: 0 1 130 131 Also tried > ranish partition manager > available from: > http://www.users.intercom.com/~ranish/part/part.zip but to no avail. Now that gpart did not work Michael H Warfield showed me some way to get a little ahead. Thanks Michael, you really teach me harddrives :-) -=================================================================- We did: "Project Cyl 0 is toast" " Boot from the Linux BBC or some other favorite bootable CD. Assuming that the drive is /dev/hda, run the following command: dd if=/dev/zero of=/dev/hda bs=1024 count=32" to zero all the partition table. I can execute fdisk on /dev/hda ever since! No errors, executed with no error. just 32 records in and out. Now running clean fdisk/cfdisk. Cool... You've written out 32 1K blocks (which is 64 sectors). That whiped out track 0 (plus one sector of track 1, but that should not be a problem). It didn't get near track 2 where those other two bad sectors are, but they shouldn't be giving you any trouble. Your first partition SHOULD start on cylinder 1 (partitions are normally on cylinder boundries - there are sloppy exceptions). The only problem here is that I have no clue of how my partitions were set, it was something like this /dev/hda1 6 0256 MB fat16/dos /dev/hda2 83 .... MB Linux 83 /dev/hda3 82 .... MD Linux Swap (presumably 0032 MB) /dev/hda4 6 1900 MB Rest: fat16 Data of my BBS only way is up: get some tool to scan partition boundaries and then resetup using fdisk, evacuate and BURN that hd... what tool does scan the boundaries? it is because the values above are far from estimated. -=================================================================- We did: "The soft solution" We'll assume that you know the geometry of the drive. Take your C/H/S and multiply them together and divide by 2 to get the size of that first cylinder in 1K blocks. Booted off the bootable CD, you can use ; what exactly do you mean? ; c*h*s ?? ; michael, please explain a little more, because I tried a dd ; and am sure i can access all the files on that hda (i can even ; output them to screen!), so that would help a lot. ; in case i missed something: i assume that I am supposed to ; multiply H*s, which is 128*63=8064 and divide that by 2, ; which results in 4032 ; is that correct ?? ; I ask before I try that out because I fear MORE damage. dd to copy from the bad drive (lets say /dev/hdb) to a file on a good drive (which is why the drive needs to be larger). ;original hda geometry: size 2564, 621 cyls, 128heads, 0 precomp landzone 4968, 63 sectors, LBA mode ;hdparg -g /dev/hda shows: ;geometry=621/128/63, sectors=5008752, start=0 CYLSIZE will be the size of cylinder zero here... I'll also assume that you have a big fat file system mounted on /mnt/0 to which you can write a copy of your file system. ; that cylsize equals the "first" cyl number zero, right? dd if=/dev/zero of=/mnt/0/oldfilesys bs=1024 count=$CYLSIZE dd if=/dev/hdb of=/mnt/0/oldfilesys bs=1024 skip=$CYLSIZE If that second dd command gives you errors, your drive is in serious hurt and you've had a hard drive hardware failure. Recovery will be expensive and unlikely to be successful. Now you should have an image of your drive on /mnt/0/oldfilesys with the first "cylinder" zeroed. Now either low-level format your old drive or replace it with an identical new drive. Partition the drive to EXACTLY what it was before the failure (or get ready to learn TCT). Now go back to your bootable CD and copy the data back... dd if=/mnt/0/oldfilesys of=/dev/hdb bs=1024 skip=$CYLSIZE Notes: I put $CYLSIZE into the head of the file to allow for the case where you might try reconstructive work on the image itself. It might also help with TCT in resurrecting a viable image if you want to work directly on that image. If you KNOW your partition table layout in cylinders and are real good at CHS -> sector number math, you can also try copyin off individual ; unfortunately I am not good at that ; furthermore, i have no idea of what my original partition table ; looked like partitions to other identically sized partitions. This is really not for the faint of heart and I would only try it if I had everything documented to the nines and it was a final act of despiration. Note... Preferred method of attack is to get the data copied to another identical drive. That way you don't run the risk of scragging that original drive and then discovering that you made a mistake in the copy process somewhere. If you have to use the single drive / lowlevel format approach, make sure the image contains good data and is intact, BEFORE begining the initialization. -=================================================================- I TRIED IT! I CAN ***ONLY*** VIA THIS WAY ACCESS THE DRIVE!!!! i just tried for a start dd if=/dev/hda of=/image skip=1024 bs=512 count=xxx and guess what? i have now been able to read the autoexec.bat of my there existing dos paartition. now, i plan to entirely evacuate all the data of the 4 partitions which still ARE there on hda. WHERE exactly does the data of the partition start on the drive? if i run using skip=63 with count=100 i get an i/o error and only 67 records copied. so it seems that a bit of the beginning of my valuable hda1 is damaged (test: 100-67=33*512 bytes lost ###IS THAT RIGHT?###) this question is about the SKIP= value which i shall enter. next, can you go into detail for the above "N" value (count=N) i tried with 63 but am unsure about it. What we can further test: On of the tools pointed to by that page is "fixdisktable". That tool is on the LNX-BBC rescue CD. It may well be on others. I can't find a lot of documentation on it, not even in the sources which are available here: ftp://bmrc.berkeley.edu/pub/linux/rescue/fixdisktable-0.3.tar.gz Oh, and regarding the TCT (The Coroner's Toolkit). That's on a lot of the bootable CD sets already. You can find out everything you wanted to know and a lot more about the TCT on their home page: http://www.porcupine.org/forensics/ Next, Michael, I did not quite get what you meant with these passages: Hmmm... You are only using primary partitions. Not sure if that's good news or bad news. Means that the table is all in one place. The secondary partitions under and extended partition are actually dazy chained through the drive. Means they are harder to find, but it also means they can be scanned for. But not applicable to partitions 1-4 that are in the primary table. > so varying all those values could end in even more desaster, so > I await your advise and do not yet write the pt. > isn't there TWO pt (one backup) on any hd? > so why not simply copying the backup over the first? Not sure, but if you read the man pages on sfdisk (use with EXTREME caution) you'll find options for dumping a partition table to a file that can be later restored (assuming the file is not on a file system you can't get to :-) ). Could you please go into "clearer" detail? This fog around hds is hard to see through :-) I would like to test some partition sizes using fdisk, is that dangerous? I suppose not, as the only destination where partition data is written to, is the track 0 of the hda, isn't it? and I can easily overwrite that one, as above :-) i would like to edit these partition values from my brain to have them tested: hda1 001-066 266080 06 fat16 hda2 067-132 266112 83 Linux hda3 133-141 36288 82 Swap hda4 142-621 1.9G 06 fat16 i ask before i try that because i want to know if i could possible destroy even more using this test. tia! -- *º¤., ¸¸,.¤º*¨¨¨*¤ =Oliver@home= *º¤., ¸¸,.¤º*¨¨*¤ I http://www.bmw-roadster.de/Friends/Olli/olli.html I I http://www.bmw-roadster.de/Friends/friends.html I I http://groups.yahoo.com/group/VGAP-93 I I http://home.t-online.de/home/spacecraft.portal I >>> Telek0ma iBBMS - soon back online +49.4503.TRSi1/TRSi2 <<<

2 1

Re: [SLE] HOW TO PRINT COLORS
by John Lamb 31 Dec '01

31 Dec '01

This is a log of my last download. You should avoid the ghostscript part unless you really know what you are doing-in any case I haven't noticed much improvement. You'll need quite a few development packages, e.g. gcc, flex, bison, libtool, gettext, indent, imlibdev, gtk libraries. The usual EULA applies: don't blame me if this goes belly-up. -------------------------------------------------------------------- Download gimp-print-4.2.0 from http://gimp-print.sourceforge.net Create a symbolic link to /usr/src/packages/SOURCES/gimp-print-4.2.0.tar.gz Use konqueror (link) or # ln -s gimp-print-4.2.0.tar.gz /usr/src/packages/SOURCES/gimp-print-4.2.0.tar.gz Uncompress: # cd /usr/src/packages/SOURCES # tar zxvf gimp-print-4.2.0.tar.gz Remove link (no longer needed) # rm gimp-print-4.2.0.tar.gz Change directory and compile # cd gimp-print-4.2.0 Read README. # CFLAGS="-O2 -march=i686" ./configure --prefix=/usr --with-cups # make # su # make install # exit Notes: Only use -march=i686 if you are sure you have a 686 (PII or celeron or better) processor. AMD users can use -march=k6. Pentium (original) users can use -march=i585. If you don't have gimp installed, you may want to use --without-gimp after --with-cups. You don't need to tell gimp-print whether or not you intend to recompile ghostscript. The --prefix=/usr puts gimp-print in the /usr directory, which is more sensible with a SuSE installation. If you want to recompile ghostscript - I haven't noticed any great difference - proceed as follows, but don't be too surprised if it doesn't work. Install the following source packages from the 7.3 CD ghostscript-library.spm libz.spm libpng.spm jpeg.spm They all get installed in /usr/src/packages/SOURCES Uncompress the bits you need # cd /usr/src/packages/SOURCES # tar Ixvf ghostscript-6.51.tar.bz2 # tar Ixvf jpegsrc.v6b.tar.bz2 # tar zxvf libpng-1.0.12.tar.gz # tar zxvf zlib-1.1.3.tar.gz Move the library sources to the ghostscript directory # mv jpeg-6b ghostscript-6.51 # mv libpng-1.0.12 ghostscript-6.51 # mv zlib-1.1.3 ghostscript-6.51 Apply a couple of patches (otherwise it won't compile) # cp ../ghostscript-6.51-align.dif . # cp ../ghostscript-6.51-time.dif . # patch -p1 < ghostscript-6.51-align.dif # patch -p1 < ghostscript-6.51-time.dif I got these not quite right because I had to copy the names of the files from the output of the patch file to the filename then requested by patch several times. The important thing is that the files got patched correctly. As root, remove all non-directory files from /usr/src/packages/SOURCES Then set up ghostscript for compiling # cd /usr/src/packages/SOURCES/ghostscript-6.51 # mv jpeg-6b jpeg # mv libpng-1.0.12 libpng # mv zlib-1.1.3 zlib # ln -s src/unix-gcc.mak Makefile Edit src/unix-gcc.mak: Line 59: change prefix=/usr/local to prefix=/usr (this puts ghostscript in the SuSE default location). Follow the instructions in /usr/src/packages/SOURCES/gimp-print-4.2.0/src/ghost/README carefully. Note for step 3) that gimp-print is already installed. For step 12): # cd /usr/src/packages/SOURCES/ghostscript-6.51 # make (cooking time should be 3-30 minutes depending on processor speed) # su # make install # exit Some man pages in gs 6.51 get created in / and so I moved them to /usr/man/man1. ----------------------------------------------------------------------------- Maura Edelweiss Monville wrote: > If I download the latest gimp-print 4.2 version from the network then my > question is where am I supposed to dowload them ?? I mean in which > system directory shall I be (cd ???) in order to overwrite the present > gimp-print files and have SuSE kernel use the new ones ??? > Could you please outline the operation sequence with some more details ???

1 0

Mainboard & Chipset
by Oliver Ob 31 Dec '01

31 Dec '01

BIOS-Info, c't/Andreas Stiller, V. 1.3 5/99 Computer ID : FC, SubTyp: 01, BIOS-Level: 0 Rechnertyp : AT-3, Konfigurationsbyte $70 Maus laut BIOS : nicht PS/2-Typ Maustreiber : nicht gefunden Bus : ISA/PCI Hauptspeicher : 640 KB, davon verfgbar : 640 KB Extended Memory : 65472 KB BIOS Date : 07/31/95 PCI-BIOS gefunden : Version 02.10 Konfigurations-Mech. : 1 Special-Cycle-Mech. : 0 PCI-Busse : 1 32-Bit-PCI-BIOS : Revision:0 Award BIOS found : Award Modular BIOS v4.50G Award ID-String : 07/31/95-TRITON-2A59CF54C-00 Board/BIOS-Version : Release 09/01/1995 ON ROM - NOT FOR SALE OEM : FUGU URL : http://www.fugu.com.tw Chipset : TRITON //Intel Triton-FX INT-13h BIOS Extension: ja, Version:1.x, Fknt 41..48 untersttzt is the information that I have about that board and its chipset. Apparently, it is a TRiTON FX(430?) chipset from Intel. I have now wasted 45 minutes on the Intel homepage to see if I can get the information about sort of this little outdated board - no. Not even the search function knows about TriTon fx and what I would like to know is the maximum of addressable memory that this board and its chipset can handle. Is there anyone of you knowing how to get that info? Thanks! Olli -- *º¤., ¸¸,.¤º*¨¨¨*¤ =Oliver@home= *º¤., ¸¸,.¤º*¨¨*¤ I http://www.bmw-roadster.de/Friends/Olli/olli.html I I http://www.bmw-roadster.de/Friends/friends.html I I http://groups.yahoo.com/group/VGAP-93 I I http://home.t-online.de/home/spacecraft.portal I >>> Telek0ma iBBMS - soon back online +49.4503.TRSi1/TRSi2 <<<

3 5

RE: Sorry
by Harry G 31 Dec '01

31 Dec '01

It appears he is over quota. I sent to him and recieved the following: ---------- Forwarded Message ---------- Subject: Mail System Error - Returned Mail Date: Mon, 31 Dec 2001 17:03:01 +0000 From: Mail Administrator <Postmaster(a)attbi.com> To: harrycg(a)bellsouth.net This Message was undeliverable due to the following reason: The user(s) account is temporarily over quota. <bliss(a)attbi.com> Please reply to Postmaster(a)attbi.com if you feel this message to be in error. ------------------------------------------------------- Kind of hard to tell him now. Harry G

1 0

Sorry,
by James Bliss 31 Dec '01

31 Dec '01

Sorry about this, but I have not received any messages from this list or others in more than 12 hours. That does not make sense to me with how active this board is. So, I am sending this message to see if I get it in my email. Again, SORRY. Jim

3 2

Re: [SLE] Strange network problems
by Alexandr Malusek 31 Dec '01

31 Dec '01

"Gerard Rowe" <rowegg(a)telocity.com> writes: > Bottom line is this, I can ping numerical IP addresses but not by > hostnames. nslookup and dig work just fine in resolving hostnames > from the Linux boxes. It happened to me on Solaris when /etc/resolv.conf was OK but dns was missing in /etc/nsswitch.conf. But I haven't tested if it applies to Linux too. Anyway, look at the network traffic with tcpdump. It usually gives some clues. > I'm running my own DNS server and it seems to be working just fine. :-) -- Alexandr.Malusek(a)imv.liu.se

1 0

gkrellm
by Landy Roman 31 Dec '01

31 Dec '01

i have noticed the cpu usage in gkrellm is not the same as the one from top... even when pc is idle is ready 99% anyone experiencing that

1 0

XAWTV error messages
by Constant Brouerius van Nidek 31 Dec '01

31 Dec '01

After upgrading to a clean 7.3 I have lost my TV screen. Right now it gives only a black screen and nothing more. I have not changed anything in thesettings for my Hauppage (old) card. After running xawtv in a console window I get following info: ' ioctl: VIDIONSYNC (0) Input.output error." Could somebody tell me what that means? And what I should to to get my TV screen back to business?

1 0