[SuSE Linux] Hosed system :(
Hi All I aqquired a compaq presairo and wanted to use a hd disk that I had already been using. The hd had lilo on the mbr and worked flawlessly. I removed and installed the hd into the compaq which come to find has a setup/diagnostic prog in the mbr?? anyway the hd booted with just LI so I figgured Id place it back in the machine it came from and reinstall lilo. here's the problem.. lilo wont go on the mbr correctly and my /vmlinuz is above the 1024 cylinders so I need it on the mbr I tried using a boot disk and reinstall lilo boot to the drive in single user, running yast and reinstalling onto the mbr (which worked before) boot to dos and fdisk /mbr after taht redoing the first 2 items any suggestions... Id sure appreciate it Id dont really want to reinstall. I just want my system back thanks rob - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
dizzy wrote:
Hi All I aqquired a compaq presairo and wanted to use a hd disk that I had already been using. The hd had lilo on the mbr and worked flawlessly. I removed and installed the hd into the compaq which come to find has a setup/diagnostic prog in the mbr?? anyway the hd booted with just LI so I figgured Id place it back in the machine it came from and reinstall lilo. here's the problem.. lilo wont go on the mbr correctly and my /vmlinuz is above the 1024 cylinders so I need it on the mbr I tried using a boot disk and reinstall lilo boot to the drive in single user, running yast and reinstalling onto the mbr (which worked before) boot to dos and fdisk /mbr after taht redoing the first 2 items any suggestions... Id sure appreciate it Id dont really want to reinstall. I just want my system back thanks rob
I'm not sure where the problem is. You took a working hd, put it in the Compaq, where it wouldn't work. Then you returned it to the original machine and it won't work anymore? And now you want your original machine to work as before, but lilo won't reinstall? Lilo should be restorable in your original setup. Unless the compaq diagnostic bios program messed it up. If you can make a tiny primary partition as the first on the disk, and mount /boot there in fstab, lilo should work even if vmlinuz is above the 1024 limit. Lilo on the mbr, looks for /boot, then boot tells it where vmlinuz is. To make the partition , you probably would need partition magic, or be able to copy everything off to another disk, fdisk, and copy back. I hope this didn't confuse you even more. W - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
zentara wrote:
dizzy wrote:
Hi All I aqquired a compaq presairo and wanted to use a hd disk that I had already been using. The hd had lilo on the mbr and worked flawlessly. I removed and installed the hd into the compaq which come to find has a setup/diagnostic prog in the mbr?? anyway the hd booted with just LI so I figgured Id place it back in the machine it came from and reinstall lilo. here's the problem.. lilo wont go on the mbr correctly and my /vmlinuz is above the 1024 cylinders so I need it on the mbr I tried using a boot disk and reinstall lilo boot to the drive in single user, running yast and reinstalling onto the mbr (which worked before) boot to dos and fdisk /mbr after taht redoing the first 2 items any suggestions... Id sure appreciate it Id dont really want to reinstall. I just want my system back thanks rob
I'm not sure where the problem is. You took a working hd, put it in the Compaq, where it wouldn't work. Then you returned it to the original machine and it won't work anymore? And now you want your original machine to work as before, but lilo won't reinstall? Lilo should be restorable in your original setup. Unless the compaq diagnostic bios program messed it up.
yes that seems to be what happened
If you can make a tiny primary partition as the first on the disk, and mount /boot there in fstab, lilo should work even if vmlinuz is above the 1024 limit. Lilo on the mbr, looks for /boot, then boot tells it where vmlinuz is.
To make the partition , you probably would need partition magic, or be able to copy everything off to another disk, fdisk, and copy back.
I hope this didn't confuse you even more.
no not at all. Thanks for your reply. Somehow.... the ps/1 bios got tweeked by tinkering with booting into single I managed to get lilo to go on the mbr... but now when its booting Im gettting messages to the effect hda: irq timeout: status=0xd2 {busy} ide0: reset: success: those messages repeat themselfs about 12x while booting then finaly I get to a prompt btw my / is /dev/hda3 This seems to be a bios/drive geometry problem (I think) thanks rob - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
dizzy wrote:
zentara wrote:
dizzy wrote:
Hi All I aqquired a compaq presairo and wanted to use a hd disk that I had already been using. The hd had lilo on the mbr and worked flawlessly. I removed and installed the hd into the compaq which come to find has a setup/diagnostic prog in the mbr?? anyway the hd booted with just LI so
not realy in the mbr, compaq uses a "diagnostics partition". If you want to go into setup, you have to press F10 as soon as the little square appears in the top right corner of the screen. this causes the setup-part. to be accessed. it must be a bios routine, that does it. if you want to create a diagnostics partition, you need 2 (nowerdays 3) Disks. Of course, you can create these disks from an existing diagnostics partition or get them from compaq's ftp site. If your disk is blows for some reason, this is very funraising, since you have to dig for (usually nonexisting) disks to boot setup from. You can run a compaq *very well* without that diagnostics part. and it wont complain, unless you press F10 and be prompted for (usually nonexisting) disks. ;-)) -- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| /\\ /__/ / _ \/ // /\ \/ / ==========================================_\_v __/_/_//_/\_,_/ /_/\_\ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Juergen Braukmann wrote:
dizzy wrote:
zentara wrote:
dizzy wrote:
Hi All I aqquired a compaq presairo and wanted to use a hd disk that I had already been using. The hd had lilo on the mbr and worked flawlessly. I removed and installed the hd into the compaq which come to find has a setup/diagnostic prog in the mbr?? anyway the hd booted with just LI so
not realy in the mbr, compaq uses a "diagnostics partition".
yes! it keeps telling me "If you are running unix you must run or go thru the setup utility" What happened was, I removed the existing hd and put in the 1200M suse somehow it got hosed :( when I put the disk back on the ps/1 I get errors to the effect described in the other messages ide0={busy}.... thne hd not ready for command
If you want to go into setup, you have to press F10 as soon as the little square appears in the top right corner of the screen. this causes the setup-part. to be accessed. it must be a bios routine, that does it. if you want to create a diagnostics partition, you need 2 (nowerdays 3) Disks. Of course, you can create these disks from an existing diagnostics partition or get them from compaq's ftp site.
Yes I origunally made the disks (floppies) but when I tried to create the partition it said their wasnt enough space left. So Im using the old hd 640M added a cdrom (which it dosent seem to like although I can get a drive letter) Then added another 840 as a secondary drive. This compac is a pressairo deskpro 590 apparently a pentium 90 with 24 ram Im desperatly trying to get suse on it but it diddnt like the 5.5G drive thne somehow screwed up my 1200M.... CAn you tell me if you think this would work? First I need I suppose the cdrom if not I can ftp install and not use the cdrom suggestions I have 1200M with a nice install of suse that seems hosed 840M empty a 640M that came with it and another 530 or so. I suppose I could try and remove the cdrom and use lan networking My impression, the compaq diddnt like Linux . so far its never booted a hd with linux on it Sorry to be confusing here .... but Im confused ;-) Thanks Alot rob - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
dizzy wrote:
Juergen Braukmann wrote:
dizzy wrote:
zentara wrote:
dizzy wrote:
Hi All I aqquired a compaq presairo and wanted to use a hd disk that I had already been using. The hd had lilo on the mbr and worked flawlessly. I removed and installed the hd into the compaq which come to find has a setup/diagnostic prog in the mbr?? anyway the hd booted with just LI so
not realy in the mbr, compaq uses a "diagnostics partition".
yes! it keeps telling me "If you are running unix you must run or go thru the setup utility"
cute, aren't they?? you can run setup from disk to do whatever they want, but I cannot see any reason for it.
What happened was, I removed the existing hd and put in the 1200M suse somehow it got hosed :(
Did you *install* the diagnostic partition in the end? than we are talking about a killed -probably root- partition.
when I put the disk back on the ps/1 I get errors to the effect described in the other messages ide0={busy}.... thne hd not ready for command
or, in any other case, did you run setup from disk only and did whatever setup suggested? this could mean a write to the disk (partition tables etc.) that sends the disk to oblivion. the idea for that is to place the disk back and undo the change. if it still wants to give unix a special treatment, ignore it. you are running Linux, a *kind* of unix. the dumb machine won't know the difference in the end.
...
Yes I origunally made the disks (floppies) but when I tried to create the partition it said their wasnt enough space left.
ure. it wants to see approx 5 MB free disk space (I suppose at the start of the disk)
So Im using the old hd 640M added a cdrom (which it dosent seem to like although I can get a drive letter) Then added another 840 as a secondary drive.
in DOS?? My way of doing things is booting from the install disk and viewing kernel messages. Be sure to have proper setting master/slave, even on the second port.
This compac is a pressairo deskpro 590 apparently a pentium 90 with 24 ram Im desperatly trying to get suse on it but it diddnt like the 5.5G drive thne somehow screwed up my 1200M....
BASH BASH BASH!!! the good old Compaqs never had a user defined Hard disk, only what they liked. Hate them for that. You probably cannot cheat the hardware detection?? I use on my old 486'ses the trick that I only enter the *size of my root partition* in setup, same geometry, but very less tracks. Linux realy needs the setup entry not at all, but the machine to find something to boot from. as soon the kernel starts it has it's own look around the neighbourhood. You do not need to bother to enter the second 3rd and 4th drive, it autodetected. Don't bother about the 512 MB limit for more then the boot partition is below that.
CAn you tell me if you think this would work? First I need I suppose the cdrom if not I can ftp install and not use the cdrom suggestions I have 1200M with a nice install of suse that seems hosed 840M empty a 640M that came with it and another 530 or so. I suppose I could try and remove the cdrom and use lan networking
i do not see a reason why the cd fails. I 've got *good* experiences with nfs installs. (i.e. installed Linux on a Compaq 386sx20 this way. Oh, this was a *slow* machine, but a very nice print server with samba!
My impression, the compaq diddnt like Linux . so far its never booted a hd with linux on it
you might get even more *fun* out of it once it is up and running. What kind of video is it using? our Compaqs at work from that era use a compaq qvision card (on board). very *cute and nice* card, have a look onto the unsupported video card section. ;-(( you might use the 16 colour vga16 x-server.
Sorry to be confusing here .... but Im confused ;-) Thanks Alot rob
got a bit confused about your explanation with hd's and cd roms. hope I've not been misunderstanding. To do some promised more Compaq bashing: I am *stuck* with Compaqs at work, I lost my liking of them long ago, sice they use special hardware, no user defined harddrives and their exorbitant prices for above hardware, not to mention the suport they gave to a friend, who asked for a memory upgrade for her -pressario- "you do not expect us to have memory for a two year old computer, do you?" (short form ;-)) Juergen -- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| /\\ /__/ / _ \/ // /\ \/ / ==========================================_\_v __/_/_//_/\_,_/ /_/\_\ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Juergen Braukmann wrote:
dizzy wrote:
Juergen Braukmann wrote:
not realy in the mbr, compaq uses a "diagnostics partition".
yes! it keeps telling me "If you are running unix you must run or go thru the setup utility"
cute, aren't they?? you can run setup from disk to do whatever they want, but I cannot see any reason for it.
yes well, I suppose Ill see for myself when I do a lan ftp install :-0
What happened was, I removed the existing hd and put in the 1200M suse somehow it got hosed :(
Did you *install* the diagnostic partition in the end?
no. I simply plugged in the hd turned it on and got LI I removed the hd and installed into a ps/1
than we are talking about a killed -probably root- partition.
when I put the disk back on the ps/1 I get errors to the effect described in the other messages ide0={busy}.... then hd not ready for command
or, in any other case, did you run setup from disk only and did whatever setup suggested? this could mean a write to the disk (partition tables etc.) that sends the disk to oblivion. the idea for that is to place the disk back and undo the change.
hummm....Is there no way for fsck to fix it? The thing is I have got lilo on the mbr and the drive does boot... only with the above errors which are repeated at least a dozen times or more
BASH BASH BASH!!! the good old Compaqs never had a user defined Hard disk, only what they liked.
exactly...
Hate them for that. You probably cannot cheat the hardware detection??
you might get even more *fun* out of it once it is up and running. What kind of video is it using? our Compaqs at work from that era use a compaq qvision card (on board). very *cute and nice* card, have a look onto the unsupported video card section. ;-(( you might use the 16 colour vga16 x-server.
oh....
hardware, not to mention the suport they gave to a friend, who asked for a memory upgrade for her -pressario- "you do not expect us to have memory for a two year old computer, do you?"
yes.. it diddnt like any of my 72pin simms I had on hand... so Im stuck with 24ram for now. Ill be installing either tonight or tomorrow Ill see how it goes any suggestions about repairing my 1200M suse disk? Thanks for your reply and have a good weekend rob - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
dizzy wrote:
Juergen Braukmann wrote:
dizzy wrote:
Juergen Braukmann wrote:
yes.. it diddnt like any of my 72pin simms I had on hand... so Im stuck with 24ram for now.
my neighbour had two 16M's left. said to be EDO, tin contacts. they worked. Compaq states that they need tinned contacts, no gold, since the connectors on the board are non gold. if you use different metals there, you might run in corrosion (insulation) problems in the long run. Katja is up to 24M as well now....
Ill be installing either tonight or tomorrow Ill see how it goes any suggestions about repairing my 1200M suse disk?
orry, no more. I'd try the earlier mentioned "undo" thing anyway. if they altered something with geometry information, it still might work. prior to that I'd suggest fsck, as others suggested. keep my hint for the last try.
Thanks for your reply and have a good weekend
thanks. Hope you'll have a successful as well. Jürgen -- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| /\\ /__/ / _ \/ // /\ \/ / ==========================================_\_v __/_/_//_/\_,_/ /_/\_\ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I compiled my sound.o file and How do i get it installed at boot time? right now I have to login as root and insmod sound I copied the sound.o file over the other two sound.o files in /lib/modules/2.0.32/misc/sound.o and /lib.modules/2.0.35/misc This didnt help. My Sound card is on IRQ 5 (non standard) I hate to mention Red Hat 5.0 found it. Also in YAST the install hardware sound card section is disabled an dI dont know why. Any ideas ?? thanks guys ! Best Regards, Ed //------------------------------------------------------------------------ // Edward March Jr. WB9RAA -- Mt. Prospect, IL // // ***> <A HREF="http://www.cl.ais.net/emarch"><A HREF="http://www.cl.ais.net/emarch</A">http://www.cl.ais.net/emarch</A</A>> // ***> <A HREF="http://www.bmtmicro.com/catalog/clone.html"><A HREF="http://www.bmtmicro.com/catalog/clone.html</A">http://www.bmtmicro.com/catalog/clone.html</A</A>> // // Win95 or Better, I chose better! // I Run OS/2 Warp 3.0 & 4.0 and Linux Red Hat 5.0 & S.u.S.E. 5.3 //------------------------------------------------------------------------ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
"Edward J. March Jr." wrote:
I compiled my sound.o file and How do i get it installed at boot time? right now I have to login as root and insmod sound I copied the sound.o file over the other two sound.o files in /lib/modules/2.0.32/misc/sound.o and /lib.modules/2.0.35/misc This didnt help. My Sound card is on IRQ 5 (non standard) I hate to mention Red Hat 5.0 found it.
The normal way to enable sound is to "insmod sound" as root. You can put that command in your boot.local file if you want it everytime you logon. Most people install "kerneld", the kernel daemon. This automatically loads any module that is needed to run any program. So the sound module would be loaded automatically as your program requests it. Look for package kerneld, and install it. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
zentara wrote:
The normal way to enable sound is to "insmod sound" as root. You can put that command in your boot.local file if you want it everytime you logon.
Most people install "kerneld", the kernel daemon. This automatically loads any module that is needed to run any program. So the sound module would be loaded automatically as your program requests it. Look for package kerneld, and install it.
I have the same problem with kerneld installed. While kerneld handle as I expect the floppy device and other stuff I compiled as module (i can see them with lsmod and the item automounted or whatever else - I don't remember exactly because I'm not at my Linux box- tell me that they are handled by kerneld) it doesn't for the sound device. As concerning YaST I remember that someone on this list wrote that the sound option on YaST is enabled only for OSS. Maurizio P.S. If you can manage it tell me because I am stuck with insmod, yet. M. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I have OSS installed and kermodd (or kerneld) and the menu sound card option is still disabled. looks like the boot.loca insmod sound is the best bet.. Hope 6.0 fixes these things... On Mon, 30 Nov 1998, Maurizio Firmani wrote: :> :>zentara wrote: :> :>> The normal way to enable sound is to "insmod sound" as root. :>> You can put that command in your boot.local file if :>> you want it everytime you logon. :>> :>> Most people install "kerneld", the kernel daemon. :>> This automatically loads any module that is needed to run :>> any program. So the sound module would be loaded :>> automatically as your program requests it. :>> Look for package kerneld, and install it. :> :>I have the same problem with kerneld installed. While kerneld handle as :>I expect the floppy device and other stuff I compiled as module (i can :>see them with lsmod and the item automounted or whatever else - I don't :>remember exactly because I'm not at my Linux box- tell me that they are :>handled by kerneld) it doesn't for the sound device. :> :>As concerning YaST I remember that someone on this list wrote that the :>sound option on YaST is enabled only for OSS. :> :>Maurizio :> :>P.S. :> :>If you can manage it tell me because I am stuck with insmod, yet. :> :>M. :>- :>To get out of this list, please send email to majordomo@suse.com with :>this text in its body: unsubscribe suse-linux-e :> :> Best Regards, Ed //------------------------------------------------------------------------ // Edward March Jr. WB9RAA -- Mt. Prospect, IL // // ***> <A HREF="http://www.cl.ais.net/emarch"><A HREF="http://www.cl.ais.net/emarch</A">http://www.cl.ais.net/emarch</A</A>> // ***> <A HREF="http://www.bmtmicro.com/catalog/clone.html"><A HREF="http://www.bmtmicro.com/catalog/clone.html</A">http://www.bmtmicro.com/catalog/clone.html</A</A>> // // Win95 or Better, I chose better! // I Run OS/2 Warp 3.0 & 4.0 and Linux Red Hat 5.0 & S.u.S.E. 5.3 //------------------------------------------------------------------------ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Mon, Nov 30, 1998 at 11:52 -0600, Edward J. March Jr. wrote:
I have OSS installed and kermodd (or kerneld) and the menu sound card option is still disabled. looks like the boot.loca insmod sound is the best bet.. Hope 6.0 fixes these things...
After installing OSS via YaST you have to run some file in /tmp (YaST will tell which exactly), it will setup OSS. Afterwards the sound configuaration in YaST should be accessible (AFAIR it will only call the OSS setup program). Btw., it doesn't make sense to have both OSS and the sound drivers supplied with the kernel installed. Ciao, Stefan - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Sun, Nov 29, 1998 at 09:59 -0600, Edward J. March Jr. wrote:
I compiled my sound.o file and How do i get it installed at boot time? right now I have to login as root and insmod sound
You could add an `insmod sound' to /sbin/init.d/boot.local. But IMHO it's better to let the kerneld do the module loading automatically when sound support is needed (and to remove the module when it's not needed). Make sure you have kerneld support compiled into the kernel and have a look at /etc/conf.modules, there's an alias char-major-14 off in there, change it to alias char-major-14 sound
Also in YAST the install hardware sound card section is disabled an dI dont know why. Any ideas ??
This does only work if OSS is installed. Ciao, Stefan - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Is there any way in KDE to put a sort of telnet URL (like the fancy FTP url's) on the desktop? thanks, chris - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi guys I downlaoded crisp (the brief like editor) It runs fine under the Console mode w/o X Funtions keys all work. under X when I run crisp F1 shows ^[[[A or some weird escape sequence. I know its something with Xmodmap -- its standard SuSE 5.3 setup. under KDE 1.0 any idea how to fix it w/o breaking something else?? Best Regards, Ed //------------------------------------------------------------------------ // Edward March Jr. WB9RAA -- Mt. Prospect, IL // // ***> <A HREF="http://www.cl.ais.net/emarch"><A HREF="http://www.cl.ais.net/emarch</A">http://www.cl.ais.net/emarch</A</A>> // ***> <A HREF="http://www.bmtmicro.com/catalog/clone.html"><A HREF="http://www.bmtmicro.com/catalog/clone.html</A">http://www.bmtmicro.com/catalog/clone.html</A</A>> // // Win95 or Better, I chose better! // I Run OS/2 Warp 3.0 & 4.0 and Linux Red Hat 5.0 & S.u.S.E. 5.3 //------------------------------------------------------------------------ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Sun, 29 Nov 1998, Christopher A. Martin wrote:
Is there any way in KDE to put a sort of telnet URL (like the fancy FTP url's) on the desktop?
Well - kind of. I've created an application icon, which executes the following: Exec=rxvt -title "Hostname" -e ssh -l <login> <hostname> Bye, LenZ ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH <A HREF="mailto:grimmer@suse.de">mailto:grimmer@suse.de</A> Schanzaeckerstr. 10 <A HREF="http://www.suse.de/~grimmer"><A HREF="http://www.suse.de/~grimmer</A">http://www.suse.de/~grimmer</A</A>> 90443 Nuernberg, Germany - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
In your 1st msg you mentioned lilo hanging after displaying "LI" on the screen. According to one of the lilo readme's, this is usually indicative of an inability of lilo being unable to ascertain the geometry of the disk, and is apparently more common with some SCSI controller/drive configurations. I just experienced this with a DTC 3130 (I believe) controller and a Quantum Viking II drive. The solution was to put the geomtery lines in the lilo config: bios=0x80 cylinders=blah heads=blah sectors=blah This information was displayd by linux fdisk, but for some reason was not available to lilo. Another point re Linux on Compaq: I had installed SuSE 5.1 on my Presario 1070 laptop as a dual-boot with W95, and it seemed to run OK for a few weeks. Then started to cause hangs and reboots when trying to mount/dismount the CD and DOS partitions. I re-installed but continued to have the problem. Finally I tried Slakware (3.4 I believe) and it seems to run better, although ocassionally I will experience the problem. I should also mention that I have upgraded the disk from the original 1G to 4G, which is unsupported by Compaq. IOW, they won't sell anything other than the 1G to run in these machines. They seem to deisgn these things in such a way that very tightly couples the hardware components. I also experienced a similar reboot problem when I attempted to upgrade the RAM fom 16 to 32 using 3rd party memory. On Sat, 28 Nov 1998, dizzy wrote:
Yes I origunally made the disks (floppies) but when I tried to create the partition it said their wasnt enough space left. So Im using the old hd 640M added a cdrom (which it dosent seem to like although I can get a drive letter) Then added another 840 as a secondary drive. This compac is a pressairo deskpro 590 apparently a pentium 90 with 24 ram Im desperatly trying to get suse on it but it diddnt like the 5.5G drive thne somehow screwed up my 1200M.... CAn you tell me if you think this would work? First I need I suppose the cdrom if not I can ftp install and not use the cdrom suggestions I have 1200M with a nice install of suse that seems hosed 840M empty a 640M that came with it and another 530 or so. I suppose I could try and remove the cdrom and use lan networking
My impression, the compaq diddnt like Linux . so far its never booted a hd with linux on it Sorry to be confusing here .... but Im confused ;-) Thanks Alot rob
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
--------------------------------------------------------------------- John Karns jkarns@ares.csd.net - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
jkarns wrote:
In your 1st msg you mentioned lilo hanging after displaying "LI" on the screen. According to one of the lilo readme's, this is usually indicative of an inability of lilo being unable to ascertain the geometry of the disk, and is apparently more common with some SCSI controller/drive configurations. I just experienced this with a DTC 3130 (I believe) controller and a Quantum Viking II drive. The solution was to put the geomtery lines in the lilo config:
bios=0x80 cylinders=blah heads=blah sectors=blah
This information was displayd by linux fdisk, but for some reason was not available to lilo.
very good suggestion..where exactly would one put that?where would I get the bios setting?
Another point re Linux on Compaq: I had installed SuSE 5.1 on my Presario 1070 laptop as a dual-boot with W95, and it seemed to run OK for a few weeks. Then started to cause hangs and reboots when trying to mount/dismount the CD and DOS partitions. I re-installed but continued to have the problem. Finally I tried Slakware (3.4 I believe) and it seems to run better, although ocassionally I will experience the problem.
I should also mention that I have upgraded the disk from the original 1G to 4G, which is unsupported by Compaq. IOW, they won't sell anything other than the 1G to run in these machines. They seem to deisgn these things in such a way that very tightly couples the hardware components. I also experienced a similar reboot problem when I attempted to upgrade the RAM fom 16 to 32 using 3rd party memory.
ok an update is in order Ive installed Suse on the compaq deskpro 590 I installed 2 hds 1 a 650M the other an 850M everything seems ok with that except the modem whish needs to be identified in the compaqs settings so far so good. As Jurgen mentioned the message regarding "if you're runnning unix you have to use the diagnostic program" He was correct, I never see that message <vbg> just the memory counting up... then lilo booting from the mbr. X and kde are setup and for me this is a big step up (to a pentium 90) for linux also when I tried to add the cdrom originally the system diddnt want it but upon installing linux it dectected it and thats working now! :-) Now the other hosed drive remains.... Ive got to look into running ex2fsck and seeing what I can do to fix that. That drive came out of a ps/1 x66 with 32ram and although it was slow with netscape it held its own. Id really like to get that disk back can anyone tell me specifically how to boot from a floppy and run ex2fsck? OR... any other ideas to repair it the status is the drive will boot and eventuall get to a somewhat working system however while booting I get these messages the go on and on maybe 20 or 30x hda: irq timeout: status=0xd2 {busy} ide0: reset: success: hda: irq timeout: status=0xd2 {busy} ide0: reset: success: hda: irq timeout: status=0xd2 {busy} ide0: reset: success: on and on then I get to a system prompt and everything seems ok but on some commands it says the hd not is ready for a command gos on to repeat that 10x or so thanks for all your feedback so far and hopefully I can get the 1200M samsung going again without reinstalling. Ive got alot of custom settings that id hate to loose. rob Bookmarks <A HREF="http://www.connix.com/~dizzy73/LBM.htm"><A HREF="http://www.connix.com/~dizzy73/LBM.htm</A">http://www.connix.com/~dizzy73/LBM.htm</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
As a sidenote here, my Presario laptop (1070) provides no method of creating these floppies. WHen I attempt it from the diagnostics program from the diag partition, it gives an error message that is unable to create them. I also tried to do so from Compaq's Windows-based diag app. .. very strange. On Sat, 28 Nov 1998, Juergen Braukmann wrote:
not realy in the mbr, compaq uses a "diagnostics partition". If you want to go into setup, you have to press F10 as soon as the little square appears in the top right corner of the screen. this causes the setup-part. to be accessed. it must be a bios routine, that does it. if you want to create a diagnostics partition, you need 2 (nowerdays 3) Disks. Of course, you can create these disks from an existing diagnostics partition or get them from compaq's ftp site.
If your disk is blows for some reason, this is very funraising, since you have to dig for (usually nonexisting) disks to boot setup from.
You can run a compaq *very well* without that diagnostics part. and it wont complain, unless you press F10 and be prompted for (usually nonexisting) disks. ;-))
-- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| /\\ /__/ / _ \/ // /\ \/ / ==========================================_\_v __/_/_//_/\_,_/ /_/\_\ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
--------------------------------------------------------------------- John Karns jkarns@ares.csd.net - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Sounds rather like a possible bug in the bios where it didn't like the drive geometry and somehow screwed up the HD's geometry table. Had something similar happen to me when my power supply started dropping out, trashed the drive's geometry information. If that's the case you're a pucked fuppy, the drive is gone. I tried the manufacturors low level formatter (drive was a conner, got the formatter from seagate) to no avail. However you MAY be EXTREMELY lucky and the high level info, such as the superblock is trashed, which a fdisk/repartition and reinstall would repair. Did you try booting from floppy and running e2fsck on the drive?
Hi All I aqquired a compaq presairo and wanted to use a hd disk that I had already been using. The hd had lilo on the mbr and worked flawlessly. I removed and installed the hd into the compaq which come to find has a setup/diagnostic prog in the mbr?? anyway the hd booted with just LI so I figgured Id place it back in the machine it came from and reinstall lilo. here's the problem.. lilo wont go on the mbr correctly and my /vmlinuz is above the 1024 cylinders so I need it on the mbr I tried using a boot disk and reinstall lilo boot to the drive in single user, running yast and reinstalling onto the mbr (which worked before) boot to dos and fdisk /mbr after taht redoing the first 2 items any suggestions... Id sure appreciate it Id dont really want to reinstall. I just want my system back thanks rob
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (10)
-
brauki＠cityweb.de -
camst65+＠pitt.edu -
dizzy73＠connix.com -
emarch＠eagle.ais.net -
grimmer＠suse.de -
jkarns＠ares.csd.net -
maurizio＠adriatico.prisma.rm.cnr.it -
stefan.troeger＠wirtschaft.tu-chemnitz.de -
wizard01＠impop.bellatlantic.net -
zentara＠mindspring.com