October 2001 - openSUSE Users - openSUSE Mailing Lists

RE: [SLE] NVidia v1.0-1541 driver, devfs and SuSE v7.2
by Richard Booth 04 Oct '01

04 Oct '01

Hi Simon I am not using devfs, but I have the same graphics card and was interested in your gears output. I find I only get a high fps (over 1000fps) when clicking/focusing on the xterm running gears, normally with the focus is elsewhere gears just plods along at 800 fps. Is this the same for you or does gears run along at 1500 fps without having to keep the mouse focus on the xterm? Thanks Rich > -----Original Message----- > From: Simon Heaton [SMTP:simon.heaton@softwareag.co.uk] > Sent: 03 October 2001 12:29 > To: SuSE ListServer > Subject: [SLE] NVidia v1.0-1541 driver, devfs and SuSE v7.2 > > Hi Folks, > > Seeing how there is a lot relating to NVidia cards/drivers on the list > at the moment: > > My system has an NVidia GForce 2 MX card. Getting this to work with SuSE > 7.0 required a few tweaks to get it working just so. Upon installation > of SuSE 7.2 card was detected correctly and everything worked out of the > box. > > I am now running a system based on SuSE 7.2 kernel 2.4.4-4GB with devfs > filesystem. Upon upgrade of NVidia drivers to those available from > NVidia site (driver version: v1.0-1541) X failed to start as the driver > would not load. After some reconfiguration cos of use of devfs, drivers > worked fine. If devfs was not mounted, then these drivers worked out of > the box. Frame rate/sec for gears went from 150 to 1500. > > If anyone is interested in the config changes needed to get these new > NVidia drivers working with a mounted devfs just let me know. > > Kind regards, > > Simon > > > -- > To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com > For additional commands send e-mail to suse-linux-e-help(a)suse.com > > Also check the FAQ at http://www.suse.com/support/faq and the > archives at http://lists.suse.com

1 0

Re: [SLE] Re: [LILO,HD] BIG BIG EMERGENCY!
by THOMAS ADAM 04 Oct '01

04 Oct '01

Oli, Did my suggestion of Toms root/boot not work then?? --Thomas > "Michael H. Warfield" schrieb: > > > > On Mon, Oct 01, 2001 at 08:23:24PM +0200, Oliver Ob wrote: > > > I repost this because people advise me to simply look inside > > > that partition (var log etc) and i _stress_ again_ that: > > > 1) i cannot read hda > > > 2) i cannot write hda _(fdisk) > > > 3) i cannot boot hda > > > > > ALL (!!!!!) > > > repeat: ALL i did was change boot order and run lilo > > > > > NOTHING has been done on the hardware which worked 5 mins before. > > > > > sorry, but i had to stress that because most advisory went into > > > those directions. > > > > > 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 > > > > This is a hardware error. It's saying that the drive is reporting > > an uncorrectable (that's as in, retries and ECC have both failed to correct > > the error on the drive) error and can not read the data. The failed sector > > happens to be in the partition table. > > > you are right. > > > > 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. > > > > Yup... Everything points to a bad sector error on the disk. > > > true. but I wonder why i cannot even REwrite pt and mbr > > > > 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! > > > > It is so unlikely to be any sort of a software bug it defies > > belief. There literally is nothing a "program" can do to corrupt a > > drive sector at that low level since ECC (Error Check Codes) are generated > > whenever data is written and SYNC patterns (low level head calibration > > patterns) are done when the drive is low-level formated / initialized > > (requires special vendor utilities). > > > you got me wrong. i meant maybe LILO contains a bug and maybe lilo > corrupted that mbr and pt. lilo neither is perfect. > I say this, because runnning lilo was all i did. (reboot afterwards) > > > What may have happened is that something went wrong in the drive > > when lilo went to reinitialize the boot sector. Since that area of the > > disk is very rarely written to, it could have been developing a potential > > write error for a long time (this is often track synchronization errors > > and was the primary reason companies came out with things like "spin-rite"). > > Low level formating might recover that sector. Merely repartitioning > > is highly unlikely to. > > > ok. order of 2do is like > 1. evacuate data > 2. low level format (need a tool for that quantum scirocco 2550) > 3. repartition > 4. try to get hda going again. > > > > HELP PLEEEEEEZ! > > > > You may be in big trouble... > > > > I've recovered drives like this in the past. It is NOT for the > > faint of heart. If it's what I think it is (corrupted sector in the > > partition table) it is recoverable, but it's not going to be easy. > > > yes. it seems to me too that there is some blocks damaged. > badblocks -b512 /dev/hda 1000 > gave me: > 0 > 1 > 130 > 131 > > what does that tell you? (cannot access manpages at this time > because they are on there...) > > > Several people have mentioned booting up from a bootable CD. > > You're gonna have to do it. > > > yes i did.. > running rescue system on cd now. > > > If you have another IDENTICAL drive, this would make life a lot > > simpler. If you know how the drive was partitioned, even better. If > i am going to buy a bigger drive tomorrow. > ====== > > > you don't have an identical drive, it's going to be tougher, but not > > impossible. If you don't know what the partition table was, you are > as long as the 2nd drive is larger there seems no problem for me. > > > going to require specialized tools to locate your partition boundries. > > The Coroners Toolkit (TCT) has some capabilities there and I've heard of > > other people who have mentioned other partition table tools as well. > > > where to dl? have you got a link handy? > > > IAC... If nothing else has worked (which it apparently has not) > > then you are forced to assume that cylinder 0 is toast and you are NOT > > getting it back. Only exception to that is as trick I describe below > read above: my values which badblocks gives me. > > > but which I don't recommend unless you are comfortable with the Bootable > > CDs and comfortable with using dd. Because that "trick" is going to > yes i am. > > > attempt to blindly write over those bad sectors you are writing > > directly to the drive with data you are trying to recover. If you > > are NOT comfortable with doing that, then just continue at this point. > > If you want to try the trick, fine, just come back here if it didn't work. > > > ok first the trick.... LOVE tricks.... > > > ============================================================ ============= > > > > 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 > > 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). > > > > 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. > > > > 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 > > 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. > > > > ============================================================ ============= > > > > One last trick if you are really REALLY brave. It is much less > > work and can be tried quickly but is also not realy likely to work, but > > it might. I've seen it happen. > > > > Boot from the Linux BBC or some other favorite bootable CD. > > Assuming that the drive is /dev/hda, run the following command: > > > ok > > > dd if=/dev/zero of=/dev/hda bs=1024 count=32 > > > ok. verified. run! BLOOOOOD! ahahah > > > Note: If you leave off the "count=32" it will eat your entire > > drive irrecoverably (and do it really fast). > > > > If you don't get an error from the above command, it may have > > laided down a clean zeroed sector over your partition table. NOW you > > may be able to go back and rebuild that partition table with fdisk, > > if you knew what it was. If you get ANY sort of error from that dd > > command, abort the effort and fall back to the suggestions above. > > > executed with no error. > just 32 records in and out. > > now run and try fdisk > > WOWW!!!!!! GOD! I SEE FDISK RUNNING!!!!! > > one should have an option for fdisk to FORCE fdisk to run in such > cases!! hope the programmers read this! > > only point: i have been now for FOUR hours searching my entire > appartment, i lost that sheet where i wrote the partition table > down. is there a tool to estimate partition sizes from their > boundaries? > > that tool should scan entire hda and report > 1st and last cylinder for any partition. > > is that popssible at all? > > at this time i am unsecure about editing an entire new pt. > i have not my sheet anymore, but if I try and enter totally > different values here, I guess it'll NOT work. > > it was more or less like this: > hda: 128h 63sec 621cyl > hda1: 6 256MB fat16 > hda2: 83 ???MB linux main > hda3: 82 32MB linux swap (or64?= > hda4: 6 1.9GB dos data drive > > 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? > > greetings and big big thanks for helping to all of you here! > > > Michael H. Warfield | (770) 985-6132 | mhw(a)WittsEnd.com > > (The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/ > > NIC whois: MHW9 | An optimist believes we live in the best of all > > PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it! > > what ACNs are 770 and 678? > leased ACNs? > > -- > *º¤., ¸¸,.¤º*¨¨¨*¤ =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 <<< > > -- > To unsubscribe send e-mail to suse-linux-e- unsubscribe(a)suse.com > For additional commands send e-mail to suse-linux-e- help(a)suse.com > Also check the FAQ at http://www.suse.com/support/faq and the > archives at http://lists.suse.com > > Thomas Adam "The Linux Weekend Mechanic" -- <www.linuxgazette.com> A Student at the "Southampton Institute", Southampton, Hants, ENGLAND

1 0

Re: [SLE] [LILO,HD] BIG BIG EMERGENCY!
by Oliver Ob 04 Oct '01

04 Oct '01

pa3gcu schrieb: > > On Saturday 29 September 2001 23:32, Oliver Ob wrote: > > > > If you can boot into Windows, you can use this to bring the data from the > > > Linux partition into the Windows partition, and back it up on removable > > > media > > > > > > >from there. The you can go about the arduous task of rebuilding your > > > > > > partition table, which may include repartitioning the drive. > > > > > > Good luck! > > > -Steven > > > > Problem is: I cannot even re write the partition data. When I run > > fdisk on hda, it exits (!!!!!) with "unable to read hda". > > So I cannot even edit data! > > Then its either broken or your cable is not connected properly, tell us what > does your BIOS say about "DRIVE 1" (/dev/hda) Does it read its geonomatry.? > it reads no geometry anymore. -- *º¤., ¸¸,.¤º*¨¨¨*¤ =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 <<<

1 2

Re: [SLE] [CD-BURN] mkisofs
by Volker Kuhlmann 04 Oct '01

04 Oct '01

> > From: Oliver Ob <ob_ok(a)gmx.net> > > To: undisclosed-recipients:; I'm not discounting the possibility that that is conforming to RFC-abnoxious, however it's very annoying as it doesn't show me to where I am getting mail, or why. > "TO: or CC:" field of messages to sort them into the proper folder. I'd filter Do not filter on to: or cc: because it's not reliable. I believe a mailing list is supposed to set sender:, but hey, this works well: :0: * ^From suse-linux-e-return- * ^Delivered-to: .*suse-linux-e * ^X-Mailinglist: suse-linux-e$ $LISTS/SuSE/suse-linux-e-List Volker

3 3

Re: [LILO,HD] BIG BIG EMERGENCY!
by Oliver Ob 04 Oct '01

04 Oct '01

lawson_whitney(a)juno.com schrieb: > > On Sun, 30 Sep 2001, Oliver Ob wrote: > > > > > ERRORS: > > > > ======= > > > > error 0x40 uncorrectable error LBAsect=9 sector=0 > > Is this a typo? The MBR should be at lba sector 0 Yes it is a type. Of course =0 is correct. Good eyes you have... :-) > dosemu used to refuse to touch a partition that was mounted, but I It was not mounted, because dosemu was running - see the difference? :-) The new dosemu has some bullshit features. See that on the msdos list > You don't have to touch the hardware to have the ribbon cable or > connectors stop working. ribbon cables and connectors are cheaply made > and not terribly reliable. > It is _not_ the cable. A cable cannot break withing a minute... well you know what I mean. read the other mail i wrote there that i can dd-read data from hda. but how many bytes have i got to skip and read the rest to restore my data to an image which i can later mount and copy files from? > You haven't tried anything to write the MBR without reading it first. > maybe it isn't so bad. maybe > > dd if=/dev/zero of=/dev/hda bs=512 count=1 > that clears the mbr with zeros, and then? > would succeed. Of course, it would destroy the partition table, but > what good is a partition table you can't read? I doubt it will work. > fully true what you say. > If it is an old 486 with a VLB bus, there are IDE interface chips that > will scramble the HD such that you can neither read nor write it, > - if you don't tell the IDE driver there is one. It can detect and > evade the PCI version. > no its p2-266 pci > If that is the case, the only way to make the drive usable again is to > use the hardware format track command. AFAIK there is no ioctl for does that apply for mine? i think not. > that, except one I wrote a long time ago for the 2.0.x and 2.2.x kernels > and put aside. If I hook up the HD they are on, it might still > work. Some BIOS's claim to be able to do format, or there is the msdose > install. > thanks lawson for trying to help. summarized I can say that accessing the hda is possible only with "dd" command (bios reads chs data). my idea is to clear mbr and then skip some 512-xxx bytes then then (where does hda1 start?) dd the whole bunch to an image. but what about geometry of harddisks in general 1. mbr 512 bytes 2. partition table 1 (how many bytes???) 3. partition table 2 (backup of 2.) and then the actual hda1 data. this is where i should start copy from. know what i want? -- *º¤., ¸¸,.¤º*¨¨¨*¤ =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 <<<

1 0

Re: [LILO,HD] BIG BIG EMERGENCY!
by Oliver Ob 04 Oct '01

04 Oct '01

"Michael H. Warfield" schrieb: > > On Mon, Oct 01, 2001 at 08:23:24PM +0200, Oliver Ob wrote: > > I repost this because people advise me to simply look inside > > that partition (var log etc) and i _stress_ again_ that: > > 1) i cannot read hda > > 2) i cannot write hda _(fdisk) > > 3) i cannot boot hda > > > ALL (!!!!!) > > repeat: ALL i did was change boot order and run lilo > > > NOTHING has been done on the hardware which worked 5 mins before. > > > sorry, but i had to stress that because most advisory went into > > those directions. > > > 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 > > This is a hardware error. It's saying that the drive is reporting > an uncorrectable (that's as in, retries and ECC have both failed to correct > the error on the drive) error and can not read the data. The failed sector > happens to be in the partition table. > you are right. > > 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. > > Yup... Everything points to a bad sector error on the disk. > true. but I wonder why i cannot even REwrite pt and mbr > > 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! > > It is so unlikely to be any sort of a software bug it defies > belief. There literally is nothing a "program" can do to corrupt a > drive sector at that low level since ECC (Error Check Codes) are generated > whenever data is written and SYNC patterns (low level head calibration > patterns) are done when the drive is low-level formated / initialized > (requires special vendor utilities). > you got me wrong. i meant maybe LILO contains a bug and maybe lilo corrupted that mbr and pt. lilo neither is perfect. I say this, because runnning lilo was all i did. (reboot afterwards) > What may have happened is that something went wrong in the drive > when lilo went to reinitialize the boot sector. Since that area of the > disk is very rarely written to, it could have been developing a potential > write error for a long time (this is often track synchronization errors > and was the primary reason companies came out with things like "spin-rite"). > Low level formating might recover that sector. Merely repartitioning > is highly unlikely to. > ok. order of 2do is like 1. evacuate data 2. low level format (need a tool for that quantum scirocco 2550) 3. repartition 4. try to get hda going again. > > HELP PLEEEEEEZ! > > You may be in big trouble... > > I've recovered drives like this in the past. It is NOT for the > faint of heart. If it's what I think it is (corrupted sector in the > partition table) it is recoverable, but it's not going to be easy. > yes. it seems to me too that there is some blocks damaged. badblocks -b512 /dev/hda 1000 gave me: 0 1 130 131 what does that tell you? (cannot access manpages at this time because they are on there...) > Several people have mentioned booting up from a bootable CD. > You're gonna have to do it. > yes i did.. running rescue system on cd now. > If you have another IDENTICAL drive, this would make life a lot > simpler. If you know how the drive was partitioned, even better. If i am going to buy a bigger drive tomorrow. ====== > you don't have an identical drive, it's going to be tougher, but not > impossible. If you don't know what the partition table was, you are as long as the 2nd drive is larger there seems no problem for me. > going to require specialized tools to locate your partition boundries. > The Coroners Toolkit (TCT) has some capabilities there and I've heard of > other people who have mentioned other partition table tools as well. > where to dl? have you got a link handy? > IAC... If nothing else has worked (which it apparently has not) > then you are forced to assume that cylinder 0 is toast and you are NOT > getting it back. Only exception to that is as trick I describe below read above: my values which badblocks gives me. > but which I don't recommend unless you are comfortable with the Bootable > CDs and comfortable with using dd. Because that "trick" is going to yes i am. > attempt to blindly write over those bad sectors you are writing > directly to the drive with data you are trying to recover. If you > are NOT comfortable with doing that, then just continue at this point. > If you want to try the trick, fine, just come back here if it didn't work. > ok first the trick.... LOVE tricks.... > ========================================================================= > > 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 > 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). > > 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. > > 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 > 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. > > ========================================================================= > > One last trick if you are really REALLY brave. It is much less > work and can be tried quickly but is also not realy likely to work, but > it might. I've seen it happen. > > Boot from the Linux BBC or some other favorite bootable CD. > Assuming that the drive is /dev/hda, run the following command: > ok > dd if=/dev/zero of=/dev/hda bs=1024 count=32 > ok. verified. run! BLOOOOOD! ahahah > Note: If you leave off the "count=32" it will eat your entire > drive irrecoverably (and do it really fast). > > If you don't get an error from the above command, it may have > laided down a clean zeroed sector over your partition table. NOW you > may be able to go back and rebuild that partition table with fdisk, > if you knew what it was. If you get ANY sort of error from that dd > command, abort the effort and fall back to the suggestions above. > executed with no error. just 32 records in and out. now run and try fdisk WOWW!!!!!! GOD! I SEE FDISK RUNNING!!!!! one should have an option for fdisk to FORCE fdisk to run in such cases!! hope the programmers read this! only point: i have been now for FOUR hours searching my entire appartment, i lost that sheet where i wrote the partition table down. is there a tool to estimate partition sizes from their boundaries? that tool should scan entire hda and report 1st and last cylinder for any partition. is that popssible at all? at this time i am unsecure about editing an entire new pt. i have not my sheet anymore, but if I try and enter totally different values here, I guess it'll NOT work. it was more or less like this: hda: 128h 63sec 621cyl hda1: 6 256MB fat16 hda2: 83 ???MB linux main hda3: 82 32MB linux swap (or64?= hda4: 6 1.9GB dos data drive 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? greetings and big big thanks for helping to all of you here! > Michael H. Warfield | (770) 985-6132 | mhw(a)WittsEnd.com > (The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/ > NIC whois: MHW9 | An optimist believes we live in the best of all > PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it! what ACNs are 770 and 678? leased ACNs? -- *º¤., ¸¸,.¤º*¨¨¨*¤ =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 <<<

1 0

Re: [SLE] [LILO,HD] BIG BIG EMERGENCY!
by Oliver Ob 04 Oct '01

04 Oct '01

THOMAS ADAM schrieb: > > Right, > > Lets take this from the top...... > > 1. Since you say that you can do nothing about booting, > writing, etc to your Linux partition, I am going to go > through some stages. > > I assume that you can access DOS, yes?? And that you > have "pkunzip" for DOS (which is easily got). > > I recommend using a program called "Tom's Root/Boot". This > is a single Linux floppy disk that can be used to access > your Linux partition in case of corruption. > > You can download the DOS installation version, here: > > http://www.tux.org/pub/distributions/tinylinux/tomsrtbt/toms > rtbt-1.7.361.dos.zip > > If you unzip it, and then install it onto a floppy, and > then boot from the floppy into "Tom's Linux", you can then > do the following: > > 1. Once booted, and into Linux (off the floppy), enter: > > bash > > 2. Mount the drive (Linux partition): > > mount -t ext2 /dev/hd?? /mnt -o rw (should make it rw) > > 2. Then see what state your files are in. From the mounted > drive, you can run a diagnostic test, as root, thus: > > fsck / > > which should diagnose your problem. Any lost cluster will > then appear in "/lost+found" > > --Thomas Adam thanks for writing thomas, but the whole pt is destroyed (now ZEROed) and thus i cannot mount anything at all. only way is up: get some tool to scan partition boundaries and then resetup using fdisk, evacuate and BURN that hd... -- *º¤., ¸¸,.¤º*¨¨¨*¤ =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 <<<

1 0

Re: [SLE] ping: sendto: Network is unreachable
by THOMAS ADAM 04 Oct '01

04 Oct '01

Hello, > Hi, I have two pc's connected to each other by a patc > h cable : pythia : 158.64.89.41 delphi : 158.64.89.40 > But when I try to ping from one pc to the other I rece > ive the error : PING delphi.men.lu (158.64.69.40): 56 da > ta bytes ping: sendto: Network is unreachable ping: wro > te delphi.men.lu 64 chars, ret=-1 Output from the ifco > nfig-command : eth0 Link encap:Ethernet HWaddr 00:D0:B > 7:BE:58:9A inet addr:158.64.89.41 Bcast:158.64.89.255 M > ask:255.255.255.0 inet6 addr: fe80::d0:b7be:589a/10 Scop > e:Link inet6 addr: fe80::2d0:b7ff:febe:589a/10 Scope:Lin > k UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX p > ackets:0 errors:0 dropped:0 overruns:0 frame:0 TX packet > s:10 errors:0 dropped:0 overruns:0 carrier:0 collisions: > 0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:732 (732.0 > b) Interrupt:10 Base address:0xa800 Memory:c8840000-c88 > 40c40 Output from the route-command : Kernel IP > routing table Destination Gateway Genmask Flags Metric R > ef Use Iface 158.64.89.0 * 255.255.255.0 U 0 0 0 eth0 >From what you have posted, it looks like there should be nothing wrong, and that it should work..... You might want to try some degenerative cases here..... 1. Just as an absolute test, try the following: ping 127.0.0.1 -c 5 2. Also check the following file: /etc/nsswitch.conf make sure that the following line exists: "hosts: dns files all" What you have to make sure is that the word "all" is at then end. 3. *This* is not necssary, but try entering the following: ifconfig 158.64.69.40 up Let me know how you get on, Regards, Thomas Adam

1 0

MD5 passwords problem
by Dragos 04 Oct '01

04 Oct '01

Hello, I just subscribed the suse-linux-e list and I want to salute everybody! Now, back to business: I'm testing suse linux 7.2 to move over our oracle server from redhat... it's OK until now, but I have a bugger: somehow I managed to install suse without MD5 passwords; it defaulted to crypt, which does not accept passwords longer than 8 chars...this is the third install&config (I'm trying to get used to yast) and first time that I noticed I don't have MD5 passwords. What did I do? there were no asking during the install...when I was asked a password for root, I noticed it told me the password would be truncated to 8 chars (my password was longer); I don't remember on the previous installs seeing that... I have the full tree exported on ftp, and I installed from that; What I need to know is, now that I have it installed, can I change it to use MD5 encrypted passwords? dragos

1 0

ping: sendto: Network is unreachable
by Vincent Botteman 04 Oct '01

04 Oct '01

Hi, I have two pc's connected to each other by a patch cable : pythia : 158.64.89.41 delphi : 158.64.89.40 But when I try to ping from one pc to the other I receive the error : PING delphi.men.lu (158.64.69.40): 56 data bytes ping: sendto: Network is unreachable ping: wrote delphi.men.lu 64 chars, ret=-1 Output from the ifconfig-command : eth0 Link encap:Ethernet HWaddr 00:D0:B7:BE:58:9A inet addr:158.64.89.41 Bcast:158.64.89.255 Mask:255.255.255.0 inet6 addr: fe80::d0:b7be:589a/10 Scope:Link inet6 addr: fe80::2d0:b7ff:febe:589a/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:732 (732.0 b) Interrupt:10 Base address:0xa800 Memory:c8840000-c8840c40 Output from the route-command : Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 158.64.89.0 * 255.255.255.0 U 0 0 0 eth0 Can someone say why it is not working or what I forgot ? Thanks, Vincent Botteman

2 1