2.4 kernel rescue disks?
Hi, does anyone know where I can get a 2.4 kernel rescue disk? The latest LILO reconfigured my MBR (I guess) and I get the LI My rescue disk is 2.2 based and gives me the couldn't mount because of unsupported optional features which I haven't seen since I tried to use a 2.0 kernel rescue disk :-P. The standard rescue disks in freshmeat all seem to be 2.2 based for the moment, so I might need to make my own. does anyone know where i can find a compiled image and tell me how to install it on a disk with a windows machine? Caoilte
Editor for rescue disks/ floppy distros
Everthing's the same except the name. This is a re- post, just for change of thread for reasons as below. Yes, I clean forgot that there are people on our list who are on threaded mail readers .. I posted this on the thread of Joe editor yesterday. Thanks Curt for reminding me. USM Bish On Sat, Sep 09, 2000 at 05:58:31AM -0500, Debian Linux User wrote: Thanks for this post. This editor is amazing. With the subject line of the thread I just about missed reading it, however. You might want to make your recommendation about including it on the rescue disks in a separate post. Best regards, Curt Daugaard [EMAIL PROTECTED] On Fri, Sep 08, 2000 at 01:24:16PM +0518, USM Bish wrote: The joe editor seems to be rather popular, specially amongst people for whom wordstar keys have got ingrained in their genes. There is another editor called w3, which was introduced to me by some-one on this list. The URL is : http://www.sax.de/~adlibit/e3-0.7.tar.gz [82338 bytes] Have been using it for about 2 weeks now. EXCELLENT !! Just 4912 bytes long binary, written fully in assembly (nasm). Fully GPL (with source code). It is 100% Word Star (non-document) mode clone. Has auto-left align as well (remember TurboPascal 3?). It is definitely not a replacement for emacs / vi, but if wordstar compatibility is what you are looking for, this rivals joe any day. If an editor for rescue disks is what is you need,look no further. THIS IS IT. It would be difficult to find a smaller one with all facilites expected of an editor. USM Bish PS: Binary tarball with man (6080 bytes)! Private mail only.
Re: Re Rescue Disks, Tom's btrt
On Fri, Jul 21, 2000 at 03:31:20PM -0400, David Teague wrote: All This is tangential to Richard's inquiry, but Has anyone considered distributing Tomsbtrt with Debian? That is one of the most useful tools I have found. LinuxCare does, with their Bootable Business Card: ISO image: http://static.linuxcare.com/iso/lnx-gold.iso Info: http://www.linuxcare.com/bootable_cd/download.epl ...though I've found that while the TRB enclosed works, the Debian installer doesn't (tested on several systems). It's a cool idea though. Both TRB and the LinuxCare BBC earn my SMA award -- that's saved my ass. Damned useful. -- Karsten M. Self kmself@ix.netcom.com http://www.netcom.com/~kmself Evangelist, Opensales, Inc.http://www.opensales.org What part of Gestalt don't you understand? Debian GNU/Linux rocks! http://gestalt-system.sourceforge.net/K5: http://www.kuro5hin.org GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0 pgp2WslZVXfTl.pgp Description: PGP signature
Re: Re Rescue Disks, Tom's btrt
kmself@ix.netcom.com wrote: LinuxCare does, with their Bootable Business Card: ISO image: http://static.linuxcare.com/iso/lnx-gold.iso Info: http://www.linuxcare.com/bootable_cd/download.epl Looks very interesting. I don't have a writeable CDROM drive, but I do have an internal zip100 drive. Is there any way I can create a bootable Zip disk using the BBC? My motherboard will boot from the zipdrive. I know nothing about ISO images, but there must be a way to write them to other media. Cheers. -- Phillip Deackes Using Storm Linux
Re: Re Rescue Disks, Tom's btrt
On Sat, Jul 22, 2000 at 09:38:22PM +0100, Phillip Deackes wrote: kmself@ix.netcom.com wrote: LinuxCare does, with their Bootable Business Card: ISO image: http://static.linuxcare.com/iso/lnx-gold.iso Info: http://www.linuxcare.com/bootable_cd/download.epl Looks very interesting. I don't have a writeable CDROM drive, but I do have an internal zip100 drive. Is there any way I can create a bootable Zip disk using the BBC? My motherboard will boot from the zipdrive. I know nothing about ISO images, but there must be a way to write them to other media. You should be able to mount the Bootable Business Card (BBC) ISO image as a loopback filesystem on your system, then copy this to the zipdisk, which gets you part of your solution. The BBC uses syslinux as a boot manager, I'm not overly familiar with how this works, but I assume you'd have to muck with the Zip disk to make it work properly. Next, the BBC uses a file which starts off as a shell script then includes actual image data, in compressed format, as a mounted static image. I don't know what specific magic was done to this, but it's possible that this could be made to work without extensive changes. Finally, you'd have to find where the BBC expects things to be on the CDROM, probably changing /etc/fstab and other portions of the disk. If you do decide to do this, you might want to ask more generally for hints (or solutions) from other folks (try the LinuxCare website), and/or post your own results. Would make a cool little Linux Zip distro. ...of which there are several which you may also want to look at. Cheers. -- Karsten M. Self kmself@ix.netcom.com http://www.netcom.com/~kmself Evangelist, Opensales, Inc.http://www.opensales.org What part of Gestalt don't you understand? Debian GNU/Linux rocks! http://gestalt-system.sourceforge.net/K5: http://www.kuro5hin.org GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0
Re: Re Rescue Disks, Tom's btrt
LinuxCare does, with their Bootable Business Card: ISO image: http://static.linuxcare.com/iso/lnx-gold.iso Info: http://www.linuxcare.com/bootable_cd/download.epl You might also want to check out http://lubbock.sourceforge.net Lubbock is based on the BBC, but we are currently planning to switch to a Debian base... and broaden it to more than bootable cds, including zip drives, ls-120s and more... you'll be able to pick a selection of deb packages and build a custom image automagically. Next, the BBC uses a file which starts off as a shell script then includes actual image data, in compressed format, as a mounted static image. I don't know what specific magic was done to this, but it's possible that this could be made to work without extensive changes. check out the CVS for lubbock, we've got everything needed to make changes If you do decide to do this, you might want to ask more generally for hints (or solutions) from other folks (try the LinuxCare website), and/or post your own results. Would make a cool little Linux Zip distro. join the Lubbock mailing list, or even the Lubbock developer team... Seth Cohn lead developer
Re: Rescue Disks
On Thu, 20 Jul 2000, Richard Ingram wrote: RI I have been upgrading Xfree but something obviously went wrong as when I RI boot up now it hangs at the starting Xfontserver startup and does not even RI get to the login prompt. Before I blat over and reinstall debian is there an RI easy way of creating a set of rescue disks ? I just need to edit a startup RI file on my root disk. My system is booted from floppy and mounts the SCSI RI disc. At work we have a Debian system so if anyone knows of a shell script RI somwhere that I could use to create my file system on floppy that would be RI greatly appreciated (I know I could hack one up but we are flat out at RI work), if not it will only take an hour or so to reinstall :-( You could use the original boot floppy from the debian installation and instead answering the 1st question [i think it's about the type of keyboard what you have] you can go down the menu skipping all the configuration choices, and run the ash shell, then mount the drive what you have problem with to some subdirectory on a ramdisk and fix the problem. You will need rawrite from ftp.debian.org/debian/tools to create the boot floppy in dos/windows and some of the files from ftp.debian.org/debian/dists/potato/main/disks-i386/current, i'm sorry but i don't remember which one you will need, but there should be README file in the same directory. in the README file should be instructions how to create the install floppy/floppies. all this shouldn't take more than some 15-20 minutes :) Dingo. ).|.( '.`___'.` ' `(~)' ` -=-=-=-=-=-=-=-=-=-=-=-=-=-=-ooO-=(_)=-Ooo-=-=-=-=-=-=-=-=-=-=-=-=- Petr [Dingo] Dvorak [EMAIL PROTECTED] Coder - Purple Dragon MUD pdragon.inetsolve.com port -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-[ 369D93 ]=- Just because you paranoid, it doesn't mean, they're not after you -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: Rescue Disks
Richard Ingram [EMAIL PROTECTED] I have been upgrading Xfree but something obviously went wrong as when I boot up now it hangs at the starting Xfontserver startup and does not even get to the login prompt. Before I blat over and reinstall debian is there an easy way of creating a set of rescue disks ? I just need to edit a startup file on my root disk. My system is booted from floppy and mounts the SCSI disc. Is there a way to pass command arguments at boot time ? In that case you could boot with the arg 'single' into single user mode and fix the error. (why do you use a boot floppy btw ?) Another way to fix the thing would be to login remotely. AFAIK all networking systems are started way before xfs, so just ssh or telnet into the machine. If these methods are not applicable then search the debian ftp site (under dists/frozen/main/disks-i386/current/images-1.44) for rescue.bin and root.bin. These are the install disks you'll need to boot. HTH -- Ragga
Re Rescue Disks, Tom's btrt
All This is tangential to Richard's inquiry, but Has anyone considered distributing Tomsbtrt with Debian? That is one of the most useful tools I have found. David On Thu, 20 Jul 2000, Richard Ingram wrote: Hi, I have been upgrading Xfree but something obviously went wrong as when I boot up now it hangs at the starting Xfontserver startup and does not even get to the login prompt. Before I blat over and reinstall debian is there an easy way of creating a set of rescue disks ? I just need to edit a startup file on my root disk. My system is booted from floppy and mounts the SCSI disc. At work we have a Debian system so if anyone knows of a shell script somwhere that I could use to create my file system on floppy that would be greatly appreciated (I know I could hack one up but we are flat out at work), if not it will only take an hour or so to reinstall :-( Thanks. Richard. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (I hope this is all of the above.)
Rescue Disks
Hi, I have been upgrading Xfree but something obviously went wrong as when I boot up now it hangs at the starting Xfontserver startup and does not even get to the login prompt. Before I blat over and reinstall debian is there an easy way of creating a set of rescue disks ? I just need to edit a startup file on my root disk. My system is booted from floppy and mounts the SCSI disc. At work we have a Debian system so if anyone knows of a shell script somwhere that I could use to create my file system on floppy that would be greatly appreciated (I know I could hack one up but we are flat out at work), if not it will only take an hour or so to reinstall :-( Thanks. Richard.
Problem with rescue disks
Hi, I am attempting to modify the Debian rescue flopy to be an emergency recovery for my system. Actually it's root.bin which I am modifying. I am having problems adding utilities. I need to add the raid tools as well as restore(8). When I chroot to the floppy and try a restore, it give me this. restore: error in loading shared libraries: restore: symbol fchown, version GLIBC_2.0 not defined in file libc.so.6 with link time reference Now, libc.so.6 on my potato system is 800k, the one on the boot floppy is only 400k. Is this some sort of stripped glibc? If so, how can I compile additional utilities against it. I am looking to add restore, raidtools2, and agetty. Can this be done? Shane -- Shane Wegner: [EMAIL PROTECTED] Personal website: http://www.cm.nu/~shane/ pgpUPXrKvEJxo.pgp Description: PGP signature
RE: Problem with rescue disks
On 28-May-2000 Shane Wegner wrote: Hi, I am attempting to modify the Debian rescue flopy to be an emergency recovery for my system. Actually it's root.bin which I am modifying. I am having problems adding utilities. I need to add the raid tools as well as restore(8). When I chroot to the floppy and try a restore, it give me this. restore: error in loading shared libraries: restore: symbol fchown, version GLIBC_2.0 not defined in file libc.so.6 with link time reference Now, libc.so.6 on my potato system is 800k, the one on the boot floppy is only 400k. Is this some sort of stripped glibc? If so, how can I compile additional utilities against it. I am looking to add restore, raidtools2, and agetty. Can this be done? The libc6 on the boot-floppies is from package libc6-pic: Description: GNU C Library: PIC archive library Contains an archive library (ar file) composed of individual shared objects. This is used for creating a library which is a smaller subset of the standard libc shared library. The reduced library is used on the Debian boot floppies. If you are not making your own set of Debian boot floppies using the `boot-floppies' package, you probably don't need this package. But I suggest using the yard package to create the boot-floppy set. And you can regain the space lost because using the standard libc by formatting the floppies at a higher capacity (eg.1743K).
debian ppc rescue disks .... where ?
Do you know where i can find the rescue disk for ppc ? It isn't in ftp://ftp.debian.org/debian/dists/potato/main/disks-powerpc/2.1.8-1999-02-24/ thanks Xavier __ [EMAIL PROTECTED]
Linux' fdisk / rescue disks / LILO
Hi, I've been playing around with multi-OS installation (Debian/Window$98) for a bit and was wondering if it is possible to use Linux' `fdisk' without having Linux installed (yet) since it is more powerful than the `cfdisk' program the installer uses. More specifically, I would like to specify exactly what cylinders partitions are to start and to end on. I would guess this should be possible with the rescue diskettes, but I can seem to get these to boot. They just keep rebooting themselves no matter what I throw at the boot prompt. I have tried the tecra ones as well to no avail. A similar phenomenon appears after installation when I try to boot using LILO. It gets stuck in an infinite loop of booting Linux when booting Linux when booting Linux ... This happens at the reboot stage in the installer. Thanks in advance for any thoughts you might have, -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Olaf Meeuwissen Ph.D. student, Shinshu University, Japan [EMAIL PROTECTED]Information Management Systems Laboratory
Re: Linux' fdisk / rescue disks / LILO
Olaf Meeuwissen wrote: More specifically, I would like to specify exactly what cylinders partitions are to start and to end on. Take a look at Ranish Partition Manager. It's a DOS program (open source), but it can do what you want. The newer version (beta 2.38) can handle disks over 8.4 GB. The older version (2.37) can't, but it has some additional features not in the beta yet. http://www.users.intercom.com/~ranish/part/ Tom
Re: Grafting other kernels on Debian's rescue disks
On Sat, Jan 02, 1999 at 12:12:02 -0600, Gregory T. Norris wrote: I believe that you also need to run the rdev script on the diskette, after copying the new kernel over. Or provide the root=[device] option to the kernel via syslinux; something like linux root=/dev/hda2 (root fs on the second partition of the master IDE disk, first IDE channel) Ray -- UNFAIR Term applied to advantages enjoyed by other people which we tried to cheat them out of and didn't manage. See also DISHONESTY, SNEAKY, UNDERHAND and JUST LUCKY I GUESS. - The Hipcrime Vocab by Chad C. Mulligan
Grafting other kernels on Debian's rescue disks
As I am stuck on my Thinkpad with Debian, while other distributions happily boot (SuSe, Tom's RootBoot for example), I would like to know if and how can I graft the kernel on the working boot floppies on Debian's rescue. This is my last chance before sadly departing from Debian of which I have been a faithful follower since 1996. Happy 1999 to all of you. Bob Alexander
Re: Grafting other kernels on Debian's rescue disks
On Sat, Jan 02, 1999 at 08:22:53 -0500, Robert J. Alexander wrote: As I am stuck on my Thinkpad with Debian, while other distributions happily boot (SuSe, Tom's RootBoot for example), I would like to know if and how can I graft the kernel on the working boot floppies on Debian's rescue. The boot floppy uses plain FAT and syslinux; the kernel on it is named linux. It should be sufficient to replace the linux file on it with a kernel image that works for you. HTH, Ray -- Obsig: developing a new sig
Re: Grafting other kernels on Debian's rescue disks
Thank you Ray. I tried with the bzImage file on SuSe and copied it to the 2.1.4 boot floppy. The floppy obviously now boots but now the last lines of the boot log: RAMDISK . Uncompressing . VFS : Mounted root VFS : Cannot open root device 08:01 Kernel panic : VFS unable to mount and hangs there ... BTW 2.1.4 does NOT boot my old faithful Thinkpad 760 like the tecra did so just going to zImage does not appear to be enough. Any other ideas Ciao Bob. J.H.M. Dassen wrote: On Sat, Jan 02, 1999 at 08:22:53 -0500, Robert J. Alexander wrote: As I am stuck on my Thinkpad with Debian, while other distributions happily boot (SuSe, Tom's RootBoot for example), I would like to know if and how can I graft the kernel on the working boot floppies on Debian's rescue. The boot floppy uses plain FAT and syslinux; the kernel on it is named linux. It should be sufficient to replace the linux file on it with a kernel image that works for you. HTH, Ray -- Obsig: developing a new sig -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Grafting other kernels on Debian's rescue disks
I believe that you also need to run the rdev script on the diskette, after copying the new kernel over. Also, the scripts expects that /mnt is where you have it mounted. On Sat, Jan 02, 1999 at 05:52:01PM -0500, Robert J. Alexander wrote: Thank you Ray. I tried with the bzImage file on SuSe and copied it to the 2.1.4 boot floppy. The floppy obviously now boots but now the last lines of the boot log: RAMDISK . Uncompressing . VFS : Mounted root VFS : Cannot open root device 08:01 Kernel panic : VFS unable to mount and hangs there ... BTW 2.1.4 does NOT boot my old faithful Thinkpad 760 like the tecra did so just going to zImage does not appear to be enough. Any other ideas Ciao Bob. J.H.M. Dassen wrote: On Sat, Jan 02, 1999 at 08:22:53 -0500, Robert J. Alexander wrote: As I am stuck on my Thinkpad with Debian, while other distributions happily boot (SuSe, Tom's RootBoot for example), I would like to know if and how can I graft the kernel on the working boot floppies on Debian's rescue. The boot floppy uses plain FAT and syslinux; the kernel on it is named linux. It should be sufficient to replace the linux file on it with a kernel image that works for you. HTH, Ray -- Obsig: developing a new sig
Re: Grafting other kernels on Debian's rescue disks
GREAT !!! After a couple of days of sweat, headaches and the occasional fit of rage, mostly thanks to this great support group I made it. Recap: Dowload the 2.1.4 diskettes. Download tomsrtbt versio 1.7.102 (DOS ZIP) and extract the kernel Graft the kernel image from tom's (thank you tom) onto Debian as linux Boot with tom's diskette, mount the Debian Frankenstein floppy on /mnt Run the /mnt/rdev.sh script BUT . I have a deep obligation and an affectionate tie to Debian. A newcomer in my situation will probably skip to RedHat or SuSe or ... I mean that the Debian boot floppies are about the weakest link in the chain and it is a pity since most users will start from there ... Do not mean to denigrate Enrique's great effort but in my many Debian installation it is not the first time I had to fight to boot the beast. Anyway thank you again very very much. Bob
Re: HELP! Rescue disks?
OK == Oleg Krivosheev [EMAIL PROTECTED] writes: OK 1. How to create rescue disk(s)? Use the disk you install Debian from. This one is even called rescue disk. See ftp://ftp.debian.org/debian/dists/stable/main/disks-i386/current/install.html#s6 OK 2. How to boot in order to avoid /etc/rc.boot OK running? When you boot from the floppy, you will see a prompt. Type linux root=/dev/your root partition single This should start Linux without running rc.boot Or you could just start the installation from the rescue disk. Go to mount a previously ... partition (or such) and choose your root partition. Then change console with Alt-F2. Then cd /target/etc/rc.boot; chmod 644 *; reboot Scripts are only executed when they have they are executable :-) Then investigate the scripts to find out what causes the trouble to you. Ciao, Martin
HELP! Rescue disks?
Hi, All looks like i got a problem - system (Deb 2.0) hangs running /etc/rc.boot scripts. Therefore i do have few questions: 1. How to create rescue disk(s)? 2. How to boot in order to avoid /etc/rc.boot running? Any help is greatly appreciated thank you OK
Re: Adaptec 2940UW failure with current rescue disks; Buslogic BT-958 succeeds.
Hi! Jameson Burt ([EMAIL PROTECTED]): Debian rescue disks have supported my Adaptec 2940UW disk for 1 1/2 years. Now, none of the rescue disks in .../dists/hamm/disks-i386 work with my Adaptec 2940UW. I am not concerned about this problem; I do not seek a solution since I have a very old rescue disk. Still, I welcome comments in the interest of others and my understanding. I imagine these solutions / workarounds: - try to enter linux aic7xxx=no_reset at the boot prompt. *Sometimes* this helps :-) - use a kernel older than 2.0.34 and put it on the boot-disk ( I suppose there is a readme how to do this.) Maybe you can simply use the kernel of a bo boot disk. This should be possible without linux, too. - compile your own kernel with current 5.1.x-pre patches and put it on the boot disk. Don't forget to read the aic7xxx list :-) This is the only way to deal with adaptec's new U2W controllers. - ask someone to compile a kernel with 5.1.x(-pre) drivers for you. Rainer -- KeyID=58341901 fingerprint=A5 57 04 B3 69 88 A1 FB 78 1D B5 64 E0 BF 72 EB pgptMYeIN27MK.pgp Description: PGP signature
Adaptec 2940UW failure with current rescue disks; Buslogic BT-958 succeeds.
Debian rescue disks have supported my Adaptec 2940UW disk for 1 1/2 years. Now, none of the rescue disks in .../dists/hamm/disks-i386 work with my Adaptec 2940UW. I have tried all four .../dists/hamm/disks-i386/2.0.10_1998-07-21/resc1440* and I have tried .../dists/hamm/disks-i386/2.0.10_1998-07-17/resc1440.bin Since the bo lineage has been removed, I would not be able to install Debian Linux. I happen to still have a bo rescue disk from 11/17/97: it works with my Adaptec 2940UW. I got my Adaptec 2940UW two years ago with a new Dell computer. A sticker on the back says DP/N 00094974 RevA00, so it may have been an early 2940UW. The error messages I get (I forget exactly) repeat 2 lines infinitely concerning scsi. As an aside, curiously, even with the old rescue disk, when I mounted my working Debian, I couldn't run lilo. I mounted / on /mnt and /usr on /mnt2. Amongst other attempts, I tried (with various LD_LIBRARY_CONFIG settings) /mnt2/sbin/lilo -r /mnt -C lilo.conf.2-drives Eventually, I succeeded doing what lilo would have done by using two menu items from the rescue disk installation: I mounted the good / (ended up on /target), and I wrote to floppy. I had pulled scsi disk 0 from a daisy chain of three scsi devices, consequently I needed to rerun lilo [I understand new /dev names in future kernels will not require rerunning lilo]. So, when all else fails, carefully avoiding a new install yet using some of the installation menu entries can get Debian working. A week later, swapping a Mylex/Buslogic BT-958 for my Adaptec 2940, I had no problems using current hamm rescue disks! I am not concerned about this problem; I do not seek a solution since I have a very old rescue disk. Still, I welcome comments in the interest of others and my understanding. -- Jim Burt, NJ9L, Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.mnsinc.com/jameson [EMAIL PROTECTED] (703) 235-5213 ext. 132 (work) It is not the shortcomings of others, nor what others have done or not done that one should think about, but what one has done or not done oneself. --Dhammapada [dp command for quotes from the Dhammapada, in Linux]
Re: Adaptec 2940UW failure with current rescue disks; Buslogic BT-958 succeeds.
Jameson Burt [EMAIL PROTECTED] writes: | Debian rescue disks have supported my Adaptec 2940UW disk for 1 1/2 | years. [snip] | I happen to still have a bo rescue disk from 11/17/97: it works with | my Adaptec 2940UW. | | I got my Adaptec 2940UW two years ago with a new Dell computer. A | sticker on the back says DP/N 00094974 RevA00, so it may have been an | early 2940UW. The error messages I get (I forget exactly) repeat 2 | lines infinitely concerning scsi. [snip] | Eventually, I succeeded doing what lilo would have done by using two | menu items from the rescue disk installation: I mounted the good / | (ended up on /target), and I wrote to floppy. I had pulled scsi disk | 0 from a daisy chain of three scsi devices, consequently I needed to | rerun lilo [I understand new /dev names in future kernels will not | require rerunning lilo]. So, when all else fails, carefully avoiding | a new install yet using some of the installation menu entries can get | Debian working. | | A week later, swapping a Mylex/Buslogic BT-958 for my Adaptec 2940, I | had no problems using current hamm rescue disks! | | I am not concerned about this problem; I do not seek a solution since | I have a very old rescue disk. Still, I welcome comments in the | interest of others and my understanding. The 2940 drivers (aic7xxx) are undergoing some pretty major changes. Adaptec has recently started cooperating with the Linux developers and it's hoped that this will, eventually, mean better drivers. Unfortunately, this is a pretty recent development (starting with kernel 2.0.34) and so the drivers aren't reliable on all the hardware. They're getting there though. I used to have problems with devices on my 2940UW disappearing intermittently. Sometimes I'd boot and my tape drive wouldn't show up, sometimes it'd be the drive with my root partition that wouldn't show up. Needless to say it was pretty annoying. But I downloaded the kernel 2.0.35 source, applied the latest development version of the aic7xxx driver (ftp://ftp.dialnet.net/pub/linux/aic7xxx/testing) and I haven't had a problem since. So, the moral of the story is, be patient. And if you have the time, try out the latest aic7xxx patches and if you have problems report them to the aic7xxx mailing list. The mailing list can be subscribed to by sending email to [EMAIL PROTECTED] (don't let the name fool you, all the traffic I've seen on the group has been related to Linux, not FreeBSD) with the line subscribe aic7xxx in the message body. Gary Hennigan
Adaptec 2940UW failure with current rescue disks; Buslogic BT958 succeeds
Debian rescue disks have supported my Adaptec 2940UW disk for 1 1/2 years. Now, none of the rescue disks in .../dists/hamm/disks-i386 work with my Adaptec 2940UW. I have tried all four .../dists/hamm/disks-i386/2.0.10_1998-07-21/resc1440* and I have tried .../dists/hamm/disks-i386/2.0.10_1998-07-17/resc1440.bin Since the bo lineage has been removed, I would not be able to install Debian Linux. I happen to still have a bo rescue disk from 11/17/97: it works with my Adaptec 2940UW. I got my Adaptec 2940UW two years ago with a new Dell computer. A sticker on the back says DP/N 00094974 RevA00, so it may have been an early 2940UW. The error messages I get (I forget exactly) repeat 2 lines infinitely concerning scsi. As an aside, curiously, even with the old rescue disk, when I mounted my working Debian, I couldn't run lilo. I mounted / on /mnt and /usr on /mnt2. Amongst other attempts, I tried (with various LD_LIBRARY_CONFIG settings) /mnt2/sbin/lilo -r /mnt -C lilo.conf.2-drives Eventually, I succeeded doing what lilo would have done by using two menu items from the rescue disk installation: I mounted the good / (ended up on /target), and I wrote to floppy. I had pulled scsi disk 0 from a daisy chain of three scsi devices, consequently I needed to rerun lilo [I understand new /dev names in future kernels will not require rerunning lilo]. So, when all else fails, carefully avoiding a new install yet using some of the installation menu entries can get Debian working. A week later, swapping a Mylex/Buslogic BT-958 for my Adaptec 2940, I had no problems using current hamm rescue disks! I am not concerned about this problem; I do not seek a solution since I have a very old rescue disk. Still, I welcome comments in the interest of others and my understanding. --- Jim Burt, NJ9L, Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.mnsinc.com/jameson [EMAIL PROTECTED] (703) 235-5213 ext. 132 (work) It is not the shortcomings of others, nor what others have done or not done that one should think about, but what one has done or not done oneself. ---Dhammapada [dp command for quotes from the Dhammapada, in Linux]
Rescue Disks
I am looking fro a good resource and information on making Emergency Boot Floppies Specifically I need to mke one for my own system with some specific system dependant stuff... It needs the obvious stuff...custom kerenl and command line options for it but thats th eeasy part (I kno whow to do that) it is the rest of it that is a problem basically I need a disk with enough functionaliy to boot me into a small filesystem where I can mount drives and repair (my real emphasis is more on being able to mount the filesystem and re-dump a tape bakup back onto it...so I guess I need mt and tar) hmm thinkin gabout it...I have a parallel port zip drive that works great...maybe I shoul djust follow the Zip-Install howto and instal a small system on that for repair use BTW I plan to test all this by dumping a backup to tape and repartitioning my hard drive and backing up -Steve -- PGP Key at: http://www.gis.net/~sjc/pgp.asc (BTW Thanx allot Noah for pointing out why putting my pgp key here was a bad idea...now I hafta find a new funny quote or something for here) Ummm, me make *one* change. Stone hot so me soak in stream so stone not burn Lorto hand. Small change, shoul dnot keep Lorto from make Fire. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Rescue Disks
On Tue, May 05, 1998 at 09:11:39AM -0400, Stephen Carpenter wrote: I am looking fro a good resource and information on making Emergency Boot [...] basically I need a disk with enough functionaliy to boot me into a small filesystem where I can mount drives and repair There was a recent comp.os.linux.announce article regarding tomsrtbt Tom's UNIX on a floppy where rt stands for root and bt stands for boot. It has an image to copy to a floppy formatted to 1920kb. There is lots of room and facility for customization. -- [EMAIL PROTECTED] Jack Kern Yarmouth, Nova Scotia Debian GNU/Linux i386 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
re: Rescue disks
On Tue, May 05, 1998 at 09:11:39AM -0400, Stephen Carpenter wrote: basically I need a disk with enough functionaliy to boot me into a small filesystem where I can mount drives and repair I've found a floppy or two just ain't big enough. Since you said you have a zip drive, by all means use it! :) I boot off a rescue floppy that points to the zip drive as the root file system. Plenty of room on that disk for everything but X. I simply copied over most of my root partition, /sbin, recursive /etc, kernels, /bin, some /usr/bin, school work archives/backups, my ~ directory, dynamic libraries, etc. No need to suffer through a primitive shell, get stuck with vi, have an unfamiliar user environment, etc. I think PPP even works with that setup in case you need access to the 'net, but I'm not sure. You may want to edit some of your init files. IIRC, lots of logging failed because I didn't create the /var/log directory. I turned most of it off since it would be useless to me for rescue purposes and the failed messages got annoying. :) A few other things must be modified as well, like /etc/fstab (you don't want it to try and mount your damaged drive;). Mostly the bootup stuff. HTH, Devin -- Reply to [EMAIL PROTECTED] http://www.engr.csulb.edu/~dbwong -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Rescue Disks
On Tue, 5 May 1998, Stephen Carpenter wrote: I am looking fro a good resource and information on making Emergency Boot Floppies Specifically I need to mke one for my own system with some specific system dependant stuff... It needs the obvious stuff...custom kerenl and command line options for it but thats th eeasy part (I kno whow to do that) it is the rest of it that is a problem basically I need a disk with enough functionaliy to boot me into a small filesystem where I can mount drives and repair (my real emphasis is more on being able to mount the filesystem and re-dump a tape bakup back onto it...so I guess I need mt and tar) hmm thinkin gabout it...I have a parallel port zip drive that works great...maybe I shoul djust follow the Zip-Install howto The Bootdisk-HOWTO has the best info. Also look in initrd package or howto. Also, at Sunsite under , I think, system/recovery there are rescue disks images. King Lee -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
rescue disks for a tecra
Does anybody know where I can get these? Bruce mentioned a bug in the exisisting set, but didn't mention what the bug was. He's off line for a while, so if anyone else could point me in the direction of a working set of boot disks for a tecra for 1.2, I'd appreciate it. I used make-kpkg to install a new custom kernel-image, but it was the same upstream version, so it blew away the previous working kernel (i.e. they were both 2.0.24, but had different package versions a la 2.0.24-1.1 and 1.2). The new kernel doesn't boot and the old kernel has been overwritten. This was a 1.1 upgraded, so I don't even have an older working set of 1.2 floppies. Any help would be appreciated as I'm quite hosed at the moment :-) Thanks in advance. Richard G. Roberto [EMAIL PROTECTED] 011-81-3-3437-7967 - Tokyo, Japan -- *** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. *** -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: rescue disks for a tecra
I must admit that only my second thought when I read Bruce's note was for his family's and his property's safety, my first being, Oh no! There goes the new boot disks. The problem is that on Tecra 710/720/730 laptops (I don't know about the 500 series) lilo cannot load a bzImage. With the rescue disk, you get Loading root.bin and Loading linux , and then the laptop reboots and gives the boot: prompt again. Loadlin (version 1.6), however, does not have a problem with bzImages. It has been reported that the Tecra 710/720 BIOS upgrade (720V580.EXE of 12-06-96) fixes this. The Tecra 730 BIOS upgrade (730V530.EXE also of 12-06-96) does not. I contacted Toshiba about this, and the Technical representative that I spoke with was very friendly, but I have not heard back from them yet. The BIOS upgrades are available at http://www.toshiba.com/tais/csd/support/files/. At http://www.cck.uni-kl.de/misc/tecra710/, Jens Maurer discusses the problem and gives a kernel patch which works around it, a patch which Bruce was going to incorporate it into the next set of boot disks. I would try it myself as a service to other Tecra owners if I knew what went into the boot disks (possible just the rescue disk). Can any of the developers out there help? Debian 1.2 was going to be an initial installation on my machine, but due to the problem, I had to install 1.1 first and then upgrade. (PHT Linux Monthly CDs finally had a use!) I made a minimal installation from the 1.1 CD, but for the service of those who only have a 1.2 CD, I could test to see what the absolute minimum of 1.1 is necessary. Perhaps it is possible to use only the 1.1 floppies, and then use the 1.2 CD when dselect is first run. I doubt that it would be possible to use the 1.1 boot and root disks, and then substitute the 1.2 base disks, but I could try. Once you have a working system, you can make it bootable with the new bzImage via loadlin, but make sure that you use loadlin version 1.6 which is in the Debian 1.2 loadlin package, not loadlin version 1.5 which is in the /tools directory and can't handle bzImages at all (nothing to do with Tecras). (I have notified the loadlin maintainer about this, but he was not sure who maintained /tools, so he past the note on to Bruce. I notice that ftp.debian.org still has loadlin version 1.5.) The alternative to using loadlin, of course, is building a kernel with the patch. Richard G. Roberto [EMAIL PROTECTED] wrote: The new kernel doesn't boot and the old kernel has been overwritten. This was a 1.1 upgraded, so I don't even have an older working set of 1.2 floppies. Richard, If you have a 710/720, I recommend the BIOS upgrade. If you have a 730, you need to boot your system somehow. If you could get a copy of the 1.1 boot and root disks, you could mount your system and then grab your new kernel for use with loadlin. Unfortunately, buzz seems to have disappeared from ftp.debian.org. Alternatively, I could send you a vmlinuz and loadlin.exe (657183 and 32208 bytes). Can you uudecode? If not, what other options are there for email binary transfer? I could try to get a minimal web site up tonight as an alternative. I don't have access to outgoing ftp, but a link to a binary should be downloadable over the web. Kirk Hilliard -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: rescue disks for a tecra
[Klippa, klapp, kluppit] At http://www.cck.uni-kl.de/misc/tecra710/, Jens Maurer discusses the problem and gives a kernel patch which works around it, a patch which Bruce was going to incorporate it into the next set of boot disks. I would try it myself as a service to other Tecra owners if I knew what went into the boot disks (possible just the rescue disk). Can any of the developers out there help? If it's a kernel patch, then all you have to do is recompile the kernel, mount the rescue floppy on /mnt, copy the resulting vmlinuz to /mnt/linux, and run /mnt/rdev.sh. Note: You might have to adjust your path if you are not doing this as root, because the /mnt/rdev.sh needs to find rdev. [Klippa, klapp, kluppit] Kirk Hilliard Good luck, Martin S. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
