Dan C wrote:

> Please trim the quoted text to which you are replying.

I was about to write the same thing when I remembered that he has 'plonked'
both of us. Someone else will have to tell this psychologist who
has "exercised my interest in computers maybe 20 years ago" that he's not
following usual practice: <http://www.caliburn.nl/topposting.html>
<http://www.catb.org/~esr/faqs/smart-questions.html>
<http://www.netmeister.org/news/learn2quote.html>
--
Two Ravens
"...hit the squirrel..."

Damjan wrote:
>
> A psychologist is a scientist studying the working of the human mind
> (usually the healthy mind).
>
>
Thank you.
--
Two Ravens
"...hit the squirrel..."

On Sun, 29 Apr 2007 08:00:42 +0100, Two Ravens wrote:

>> Please trim the quoted text to which you are replying.

> I was about to write the same thing when I remembered that he has 'plonked'
> both of us. Someone else will have to tell this psychologist who
> has "exercised my interest in computers maybe 20 years ago" that he's not
> following usual practice:
> <http://www.caliburn.nl/topposting.html>
> <http://www.catb.org/~esr/faqs/smart-questions.html>
> <http://www.netmeister.org/news/learn2quote.html>

Heh, yeah I forgot about that. Could one of you non-plonkees quote this
so he'll see it (or remind the idiot directly)? Thanks.

And to think, I actually wasted a "please" in my request. Bummer.


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".

On Apr 29, 12:33 am, Dan C <youmustbejok...@lan.invalid> wrote:

> Please trim the quoted text to which you are replying.
>
you seem to give good advices sometimes;
anyway that doesn't change the dog you are. somethings never change.

On Apr 29, 1:15 am, e...@FreeNet.Carleton.CA (Michael Black) wrote:

> If you show us your lilo.conf that might help clear things up.
I think my config of lilo has nothing to do with the problem, because
it has never changed since i first installed slack and before i could
boot with anything plugged in any usb "slot".
any way i'm pasting the lilo.conf file to make ideas clear for you and
others.
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
#install=text
boot = /dev/sda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
# vga = 773
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# video=scrollback:128K
# Windows bootable partition config begins
other = /dev/sda1
label = Windows
table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda3
label = Linux
read-only
# Linux bootable partition config ends


> Because
> it will show where you are specifying the bootloader should go, and
> where the kernel is.
>
as i said this is not the problem
> But the more you post, the more it seems the issue is not the bootloader,
yes
> but that you've done something wrong about the kernel.
>
yes that's probably the origin of the problem

note that the framebuffer is not enabled in my kernel, i do never
enable it. I'm reminding that because s.o. said that this could be the
cause of the issue. But even that i think this is the cause of the
issue because i did never enabled it since i first configured my
custom kernel, this the same time as when i first installed slack
because no one of the suggested kernel was suitable for my laptop.

> Michael

On Apr 29, 2:11 am, "John K. Herreshoff" <n...@not.here> wrote:
> Michael Black wrote:
> >heavytull(heavyt...@hotmail.com) writes:
> >> the problem seems to be more serious than it was looking like.
> >> actually everytime my usbkey is plugged in linux won't boot.
> >> it still hangs at 'bios data check'
>
> >> after i unplugged the key and rebooted i saw the message:
> >> 'bios data checkbypassed'
>
> >> there is a real problem of dynamism
>
> > If it's really the boot order that you've played with, that should
> > not mean a thing. All it does is adjust the order that the computer
> > checks devices to look for bootable code. So if you tell it to
> > check the CDROM first, the computer will check that, before checking
> > the next thing on the list, and so on. If it finds bootable code,
> > then it will boot that. If not, it will move on.
>
> > So the only way changing the boot sequence will affect things is that
> > something else might boot first. So I have mine set to boot first from
> > the CDROM, and then the hard drive (or maybe the floppy drive is in the
> > middle). If nothing is in the CDROM drive when I start the computer, then
> > it will move to the next device, which is the hard drive, and boot from
> > that (because
> > there is bootable code there). If the hard drive wasn't there, or the
> > bootable code got mangled, then it would basically hang, because there's
> > nothing for it to boot. Though if I have the floppy drive last, and a
> > bootable floppy in the drive, then that would take off if the CDROM and
> > the hard drive had no bootable code on it.
>
> > (Some BIOSs do allow one to reassign the drives, which is a different
> > thing. I'm hazy on this because I don't have any experience, but it
> > fiddles with the hardware so so your first IDE channel becomes your second
> > IDE channel,
> > and vice versa. That might affect things, I've not given it real
> > thought. But you keep talking about boot order, not reassigning the
> > controller
> > channels. If you aren't talking about boot order, then you need to
> > make this clear.)
>
> > If your computer doesn't boot with the USB drive in place, then it's
> > simple,
> > there is no bootable code there. Either that, or you have some hardware
> > problem in the USB system, or the drive.
>
> > Lilo seems easy to misunderstand. Lilo, the command, puts a boot loader
> > somewhere that your computer can see it, and start that code. lilo.conf
> > is merely the configuration code, it tells lilo where to put the boot
> > loader,
> > and it tells lilo where to find the actual kernel. The boot loader is
> > pretty generic code, and it runs briefly, and then brings in the actual
> > kernel. If you get the screen asking what to load, then the bootloader
> > is fine, it's what comes later that is corrupted.
>
> > lilo.conf is only needed when running lilo. You can put /boot in a
> > separate partition, and the only time it needs to be mounted is when
> > you run lilo. Because lilo runs, it looks at lilo.conf to find
> > out where the boot loader is to be placed and where the kernel is.
> > But it hard codes the information about where the kernel is, by
> > track and sector on the hard drive, rather than something vague
> > like "/dev/hda1/boot/vmlinuz". The system will boot fine without
> > the partition with the kernel actually mounted, because the boot
> > loader isn't aware of partitions, it simply knows at Track XX,
> > Sector XX, there is some code (that happens to be the kernel) that
> > should be loaded and then run.
>
> > This "hard coding" is why it's necessary to run lilo every time something
> > is changed around the kernel. If you delete the actual kernel, and then
> > copy it back, chances are that it will no longer be in the same place
> > as before, so the bootloader will not find the needed code to load
> > and execute.
>
> > Note the bootloader does not have to be where the kernel is. Hence
> > you can put it on a floppy drive, on a hard drive with the actual
> > kernel on some secondary drive, or on a USB drive. Of course, if your
> > computer finds some sort of bootable code before it gets to where you've
> > placed the boot loader, then it will never get to the bootable code.
>
> > If you show us your lilo.conf that might help clear things up. Because
> > it will show where you are specifying the bootloader should go, and
> > where the kernel is.
>
> > But the more you post, the more it seems the issue is not the bootloader,
> > but that you've done something wrong about the kernel.
>
> > Michael
>
> If I'm reading some ofheavytullcorrectly, his hard drive is /dev/sda, and
> he is telling lilo to boot the usbkey as /dev/sda1,
I'm not telling lilo to boot on my usbkey, I'm telling the bios to
check a usb port to boot on if it is bootable.

> which will choke, as
> that is his windows partition. the usbkey should boot from /dev/sdb1.
>
forget about lilo booting on the usb

> ?
>
> John.