This is a discussion on slack hang at BIOS data check within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> John K. Herreshoff wrote: >> >> Please see Message-ID: <slrnf2pgce.3lkm.syl@alcor.concordia.ca>, in >> which I believe I did exactly that. ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| John K. Herreshoff wrote: >> >> Please see Message-ID: <slrnf2pgce.3lkm.syl@alcor.concordia.ca>, in >> which I believe I did exactly that. >> > > Pretend that the readers are 8 years old. > > Make it simple. Its a long time since I've had to go into my BIOS but I seem to remember that there was a command to re-instate the defaults for each separate function, have you tried doing that, <restore default>? -- Two Ravens "...hit the squirrel..." |
| |||
| On 23 Apr 2007 10:21:10 -0700, heavytull <heavytull@hotmail.com> wrote: >plpease anyone can tell me what the vga has to do with the boot >devices order, because that's what i changed in the BIOS. Nothing > >I personally don't think that's the problem; >initialy everything was working well. >I think the BIOS data doesn't not comply anymore with what was >previously recorded in the init files. Your kernel moved? Seems lilo finds itself but not the kernel? Try booting with install CD, mount the root partition to /mnt (if you have a separate /boot mount it to /mnt/boot) then run: lilo -r /mnt Then reboot if no errors reported. If errors, fix /mnt/etc/lilo.conf and retry. Or report the result here and someone pickup the story. Grant. -- http://bugsplatter.mine.nu/ |
| |||
| John K. Herreshoff wrote: >> Please see Message-ID: <slrnf2pgce.3lkm.syl@alcor.concordia.ca>, in >> which I believe I did exactly that. > > Pretend that the readers are 8 years old. Pretend that the reader has at least enough experience to have already installed Slackware on his system (since we know from the OP that he has). Pretend also that the reader has at least enough experience to deliberately make changes to the system's BIOS configuration (since we know from the OP that he has). I'm quite confident that any 8-year-old that could get himself into the situation described by the OP, and describe as the OP has, would be able to make sense of my message. > Make it simple. Which part of my message <slrnf2pgce.3lkm.syl@alcor.concordia.ca> is unclear? -- ---------------------------------------------------------------------- Sylvain Robitaille syl@alcor.concordia.ca Systems and Network analyst Concordia University Instructional & Information Technology Montreal, Quebec, Canada ---------------------------------------------------------------------- |
| |||
| Sylvain Robitaille wrote: > John K. Herreshoff wrote: > >>> Please see Message-ID: <slrnf2pgce.3lkm.syl@alcor.concordia.ca>, in >>> which I believe I did exactly that. >> >> Pretend that the readers are 8 years old. > > Pretend that the reader has at least enough experience to have already > installed Slackware on his system (since we know from the OP that he > has). Pretend also that the reader has at least enough experience to > deliberately make changes to the system's BIOS configuration (since we > know from the OP that he has). I'm quite confident that any 8-year-old > that could get himself into the situation described by the OP, and > describe as the OP has, would be able to make sense of my message. > >> Make it simple. > > Which part of my message <slrnf2pgce.3lkm.syl@alcor.concordia.ca> is > unclear? > Just make it simple, not difficult. I'll let you have the last paragraphs. John. |
| |||
| John K. Herreshoff wrote: >> Which part of my message <slrnf2pgce.3lkm.syl@alcor.concordia.ca> is >> unclear? > > Just make it simple, not difficult. It took you three messages (see below) to describe how you would approach this problem, and it took me one to describe how I would do it, yet you're telling me that my way is difficult and I should "make it simple": Message-ID: <heednXHY1velW7HbnZ2dnUVZ_gadnZ2d@giganews.com> Message-ID: <heednXDY1vdHW7HbnZ2dnUVZ_gadnZ2d@giganews.com> Message-ID: <4-6dnZzMvLf1UbHbnZ2dnUVZ_veinZ2d@giganews.com> > I'll let you have the last paragraphs. Right. For the sake of simplicity, I'm sure ... -- ---------------------------------------------------------------------- Sylvain Robitaille syl@alcor.concordia.ca Systems and Network analyst Concordia University Instructional & Information Technology Montreal, Quebec, Canada ---------------------------------------------------------------------- |
| |||
| On Mon, 23 Apr 2007 15:02:32 -0400, John K. Herreshoff wrote: > Sylvain Robitaille wrote: > >> John K. Herreshoff wrote: >> >>> Please spell it out step by step for the guy who cannot start his box. >> >> Please see Message-ID: <slrnf2pgce.3lkm.syl@alcor.concordia.ca>, in >> which I believe I did exactly that. >> >> > Pretend that the readers are 8 years old. > > Make it simple. I don't know how it went so sharp so fast in your posts but just in case you're just having trouble with your ISP to get some ntp segments from (near) past here is the main part of the step one by step manpage from 'syl' ;-) ---------- Boot the CD you used to install Slackware from, using "root=/dev/sda1" (or whatever your root device is) as an argument to the boot command. ---------- And the rest of his post was just the "caveat" part of many manpages :-) ---------- This is actually described in the informational screen that comes up at the boot prompt of the installation CD. ---------- I suppose all the fast irate game comes from the continuous heatwaves that nowadays hurt EU an CA. Note to AU and NZ (condensed list for brevity [these notes really make the stuff long I think {besides, I hate long parenthesis}])/*letmeout! Good, then: Note to A-Z I know it'd seem curious to many of you that some 28°C in town is hard to live, but please just read again a short stoty in the Klondike series from Jack London (eg: 'To build a fire' ;D) |
| |||
| On 2007-04-23, John K. Herreshoff <nope@not.here> wrote: > Sylvain Robitaille wrote: > >> John K. Herreshoff wrote: >> >>> Please spell it out step by step for the guy who cannot start his box. >> >> Please see Message-ID: <slrnf2pgce.3lkm.syl@alcor.concordia.ca>, in >> which I believe I did exactly that. > > Pretend that the readers are 8 years old. Just because you are behaving like an 8 year old does not mean the OP has the comprehension of such. Sylvain spelled out exactly what to do in the above post. It's a very reliable method for booting with a given root partition when the bootloader is hosed, and I don't see what's not simple enough about his description. --keith -- kkeller-usenet@wombat.san-francisco.ca.us (try just my userid to email me) AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt see X- headers for PGP signature information |
| |||
| Keith Keller wrote: > Sylvain spelled out exactly what to do in the above post. It's a very > reliable method for booting with a given root partition when the > bootloader is hosed, and I don't see what's not simple enough about his > description. > > --keith > > The answer was telegraphic. Immediately understandable to the writer and to those who know the drill, mystification to those that don't... That's all. I did not know that drill until about 2 minutes ago, when I went back to booting from the CD. There it was... written out in a paragraph or two, telling the user to boot, or if in a pinch, enter the kernel needed, and a command such as boot=/dev/sda1 if the boot loader were trash. I got it sorta by piecing together what has been going on in this thread, and by reading the obvious on the boot screen. The first time that I read boot=/dev/sda1 in this thread, I was wondering where that went... The answer was absolutely right on, but probably only to the initiated. For someone in that situation for the first time, it did not tell a whole lot. I guess we want to be helpful to those lost in the woods... Anyway, the real problem is the guy who fiddled with his machine and cannot get it going. We're trying to help him, right. Sylvain (and maybe a few others) you 'won' this one if that is important to you. John. |
| |||
| On 2007-04-23, John K. Herreshoff <nope@not.here> wrote: > > I got it sorta by piecing together what has been going on in this thread, > and by reading the obvious on the boot screen. The first time that I read > boot=/dev/sda1 in this thread, I was wondering where that went... The > answer was absolutely right on, but probably only to the initiated. For > someone in that situation for the first time, it did not tell a whole lot. > I guess we want to be helpful to those lost in the woods... It was immediately obvious to me the first time I tried it many many years ago, when I was still a bit of a n00b. If it was not obvious to the OP, then he should post about it. If you believe it's not obvious, you should clarify; if you can't, you should ask in a less obnoxious way, *specifically* explaining *exactly* which part you don't get. Part of being uninitiated is learning how to extract information from the initiated, not because the initiated want to treat the uninitiated poorly, but because often the initiated take things for granted. How can they know what they're taking for granted if it's not explained by the uninitiated? To extend your analogy, we can't help those lost in the woods if all they tell us is "We're in the woods". Imagine: Q: I'm lost in the woods. A: What's that tree to your right say? Q: I'm lost in the woods. A: Okay, take ten steps left and tell me what you see. Q: I'm lost in the woods! > Sylvain (and maybe a few others) you 'won' this one if that is important to > you. If you knew anything about Sylvain's posting history, you'd know ''winning'' an argument isn't important to him. If you'd posted with specific objections instead of "Spoon-feed the OP everything", his response would probably have been more to your liking. --keith -- kkeller-usenet@wombat.san-francisco.ca.us (try just my userid to email me) AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt see X- headers for PGP signature information |