Enviado desde mi iphone jr
On 6/2/23 23:45, Roy J. Tellason, Sr. wrote:
On Sunday 05 February 2023 06:29:12 pm local10 wrote:
5 Feb 2023, 20:28 byy...@masson-informatique.fr:
Does anybody knows trusted manufacturers / brands I could find on the Internet? I am
really disappointed by this battery (brand "vhbw") partially
On Sunday 05 February 2023 06:29:12 pm local10 wrote:
> 5 Feb 2023, 20:28 by y...@masson-informatique.fr:
> > Does anybody knows trusted manufacturers / brands I could find on the
> > Internet? I am really disappointed by this battery (brand "vhbw") partially
> > broken after only two years…
> >
On 05/02/2023 23:32, gene heskett wrote:
Speaking as a CET with some knowledge of battery degradation, the
thought of replacing an individual cell in a li-ion battery scares me.
That new battery will have a bit more capacity, which in turn may force
other older cells into reverse polarity
> Does anybody knows trusted manufacturers / brands I could find on the
> Internet? I am really disappointed by this battery (brand "vhbw") partially
> broken after only two years…
I can't vouch for any specific company, sadly. I think it's largely
a crapshoot (except when you can still get an o
On Mon, 6 Feb 2023 00:29:12 +0100 (CET)
local10 wrote:
> Find out the exact battery model you laptop uses and then buy a
> replacement battery of that exact model (on Ebay or whatever). Other
> batteries may be better or worse but they may also be incompatible
> with your laptop.
And you may fin
5 Feb 2023, 20:28 by y...@masson-informatique.fr:
> Does anybody knows trusted manufacturers / brands I could find on the
> Internet? I am really disappointed by this battery (brand "vhbw") partially
> broken after only two years…
>
Find out the exact battery model you laptop uses and then buy
gene heskett wrote:
...
> Speaking as a CET with some knowledge of battery degradation, the
> thought of replacing an individual cell in a li-ion battery scares me.
> That new battery will have a bit more capacity, which in turn may force
> other older cells into reverse polarity,
and recycle the old one.
Regards,
Speaking as a CET with some knowledge of battery degradation, the
thought of replacing an individual cell in a li-ion battery scares me.
That new battery will have a bit more capacity, which in turn may force
other older cells into reverse polarity, acceleratin
with some knowledge of battery degradation, the
thought of replacing an individual cell in a li-ion battery scares me.
That new battery will have a bit more capacity, which in turn may force
other older cells into reverse polarity, accelerating the rate of
failure of the rest of the cells, wit
Feb 5, 2023, 10:45 by y...@masson-informatique.fr:
> I have a Dell Latitude e6220 with a 2 year 6600 mAh battery, which does not
> charge above 67% since a few weeks. It makes me think that 1/3 of the cells
> are in a bad state. However, upower says that the capacity is 95%, so
> remaining cell
Yvan Masson wrote:
...
> Price of a new battery is not really annoying, but I am more and more
> concerned about electronical waste.
if you have any local battery stores one of them may be
able to repair it for a reasonable charge.
songbird
On 05/02/2023 17:37, Yvan Masson wrote:
I don't know anything about battery, but I can do easy soldering.
1. Proper technology for rechargeable batteries is welding, not
soldering (to prevent overheating).
2. If you just disconnect a cell then a chip monitoring health status of
the assembly w
Hi list,
I have a Dell Latitude e6220 with a 2 year 6600 mAh battery, which does
not charge above 67% since a few weeks. It makes me think that 1/3 of
the cells are in a bad state. However, upower says that the capacity is
95%, so remaining cells are probably still good.
I don't know anythin
Just installed the subject linux-image and
linux-headers, apparently successfully, but libc6-i686
wont install with unmet dependencies. Console output
as follows:
ChatagnierL-Home:/var/log# aptitude install libc6-i686
E: Unable to correct problems, you have held broken
packages.
E: Unable to corr
Thanks Bob,
BP> Even if you think you only tweaked X if this is your behavior there
BP> must have been some other change to the boot sequence. Because
BP> changing X would not affect boot. (And if I were changing X I would
BP> not have rebooted personally because they are not related.)
No, I ag
debian wrote:
> I've just upgraded my "store" machine (behind my firewall) from
> woody to sarge and my firewall following the instructions. The
> store machine rebooted fine at first but then, after some tweaks to
> X, I rebooted again and the boot is hanging at "
I've just upgraded my "store" machine (behind my firewall) from woody to sarge
and my
firewall following the instructions. The store machine rebooted fine
at first but then, after some tweaks to X, I rebooted again and the
boot is hanging at "LI". I can get into the mac
Tom <[EMAIL PROTECTED]> writes:
> On Sat, Nov 08, 2003 at 01:38:56PM -0500, BruceG wrote:
> [cut]
>> > Willem-Jan Meijer wrote:
>> > > but when I wanted to boot I saw the letters LI, and after that the
>> system hangs.
>>
>> I had the same
On Sat, Nov 08, 2003 at 01:38:56PM -0500, BruceG wrote:
[cut]
> > Willem-Jan Meijer wrote:
> > > but when I wanted to boot I saw the letters LI, and after that the
> system hangs.
>
> I had the same problem after my upgrade. If you made a boot floppy during
> your ini
On Fri, 10 Oct 2003 at 05:34 GMT, Christof Hurschler penned:
> I didn't get chroot to work because I wasn't using chroot correctly,
> so thanks for the full command line on that. I think that will be
> something usefull to know in the future.
>
> Chris
>
I copied it from some notes I keep for m
t; On Thu, 09 Oct 2003 at 11:33 GMT, Christof Hurschler penned:
> > it just stops with "LI" and goes no further. I read in the archives
> > that this means that Lilo can't completely load.
> >
> > .. but what does the "rescue" command do?
> >
&
urschler wrote:
> > it just stops with "LI" and goes no further. I read in the archives that
> > this means that Lilo can't completely load.
> >
> > .. but what does the "rescue" command do?
>
> you have to boot from the cdrom/floppy in re
On Thu, 09 Oct 2003 at 11:33 GMT, Christof Hurschler penned:
> it just stops with "LI" and goes no further. I read in the archives
> that this means that Lilo can't completely load.
>
> .. but what does the "rescue" command do?
>
> Chris
>
>>
Christof Hurschler wrote:
> it just stops with "LI" and goes no further. I read in the archives that
> this means that Lilo can't completely load.
>
> .. but what does the "rescue" command do?
you have to boot from the cdrom/floppy in rescue mod, then moun
Christof Hurschler wrote:
Hi,
I'm getting the LI hang on boot.
Probably because LILO didn't completely, properly get installed.
I tried booting from my floppy, but it
gives me a kernel panic...
I never boot from floppy, so am unfamiliar with the issues. If you have
a Debian in
it just stops with "LI" and goes no further. I read in the archives that
this means that Lilo can't completely load.
.. but what does the "rescue" command do?
Chris
> On Thu, Oct 09, 2003 at 08:22:05AM +0200, Christof Hurschler wrote:
>
> > I'm get
On Thu, Oct 09, 2003 at 08:22:05AM +0200, Christof Hurschler wrote:
> I'm getting the LI hang on boot. I tried booting from my floppy, but it
> gives me a kernel panic...
with what message?
> I now read that I can boot from floppy with the "rescue root=/dev/hda1",
Hi,
I'm getting the LI hang on boot. I tried booting from my floppy, but it
gives me a kernel panic...
I now read that I can boot from floppy with the "rescue root=/dev/hda1", but
I'm assuming that this is the default mode the floppy boots in anyways, or
is it?
If I co
also sprach Jeremy Turner <[EMAIL PROTECTED]> [2002.09.09.1836 +0200]:
> I would suggest periodic swapping. It's a good idea to fully cycle a
> Li-ion battery once a month (atleast that's what IBM tells me). Also,
> if you do want to keep a battery in storage for some
On Monday 09 September 2002 07:03 pm, Derrick 'dman' Hudson wrote:
> On Mon, Sep 09, 2002 at 08:05:57PM +0200, martin f krafft wrote:
> | also sprach Joe Hendrix <[EMAIL PROTECTED]> [2002.09.09.2003 +0200]:
> | > Seal them in bags so they stay dry and store them in the freezer. They
> | > should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 09 September 2002 11:05 am, martin f krafft wrote:
> also sprach Joe Hendrix <[EMAIL PROTECTED]> [2002.09.09.2003 +0200]:
> > Seal them in bags so they stay dry and store them in the freezer. They
> > should stay charged quite a bit longer.
On Mon, Sep 09, 2002 at 08:05:57PM +0200, martin f krafft wrote:
| also sprach Joe Hendrix <[EMAIL PROTECTED]> [2002.09.09.2003 +0200]:
| > Seal them in bags so they stay dry and store them in the freezer. They
| > should stay charged quite a bit longer.
|
| Anyone ever done this?
No, but it s
also sprach Joe Hendrix <[EMAIL PROTECTED]> [2002.09.09.2003 +0200]:
> Seal them in bags so they stay dry and store them in the freezer. They
> should stay charged quite a bit longer.
Anyone ever done this?
--
martin; (greetings from the heart of the sun.)
\ echo mailto: !#
martin f krafft <[EMAIL PROTECTED]> writes:
> because one of my laptops died right after its warranty expired (how
> could it have been different), i am left with two spare batteries that
> i can use for my other laptop. thus, i now have four batteries, but
> the laptop only holds two at a time.
> -Original Message-
> From: martin f krafft [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 09, 2002 11:16 AM
> To: debian users
> Subject: OT: storing laptop (Li-ion) batteries
> or is the only real way to deal with this situation periodic swapping?
I woul
because one of my laptops died right after its warranty expired (how
could it have been different), i am left with two spare batteries that
i can use for my other laptop. thus, i now have four batteries, but
the laptop only holds two at a time. because i have just gone through
a battery trauma bec
On Mon, May 13, 2002 at 10:17:20PM +0100, Colin Watson wrote:
> On Mon, May 13, 2002 at 12:59:38PM -0700, Sean 'Shaleh' Perry wrote:
> > On 13-May-2002 Colin Watson wrote:
> > > On Mon, May 13, 2002 at 11:36:31PM +0530, Deepak Kotian wrote:
> > >> Is there any tool like purify(memory leak tool) for
>
> I'm informed by the guy at work who's been spending a lot of time
> working on and with valgrind that "yesterday's version is old".
>
I see (-:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, May 13, 2002 at 12:59:38PM -0700, Sean 'Shaleh' Perry wrote:
> On 13-May-2002 Colin Watson wrote:
> > On Mon, May 13, 2002 at 11:36:31PM +0530, Deepak Kotian wrote:
> >> Is there any tool like purify(memory leak tool) for LINUX. Or any free
> >> software which can be used to check memory le
On 13-May-2002 Colin Watson wrote:
> On Mon, May 13, 2002 at 11:36:31PM +0530, Deepak Kotian wrote:
>> Is there any tool like purify(memory leak tool) for LINUX. Or any free
>> software which can be used to check memory leaks on a C/c++ program.
>
> Try valgrind (http://devel-home.kde.org/~seward
Paul Smith said:
> %% "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> writes:
>
> sp> none of them are as cool and featureful as purify. Of all of the
> sp> tools I have used, I miss that one most. Unfortunately apps like
> sp> that are decidedly hard to write and the commercial ones are sp>
> REA
"Paul Smith" <[EMAIL PROTECTED]> writes:
> We'd buy it at work in a heartbeat if it were available on Linux: Purify
> _is_ cool. But, it's not available on Linux and I've not heard Rational
> provide any details on whether it ever will be :(.
Insure++ (http://www.parasoft.com) has almost all the
%% "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> writes:
sp> none of them are as cool and featureful as purify. Of all of the
sp> tools I have used, I miss that one most. Unfortunately apps like
sp> that are decidedly hard to write and the commercial ones are
sp> REALLY expensive for most ho
On 13-May-2002 dman wrote:
> On Mon, May 13, 2002 at 11:36:31PM +0530, Deepak Kotian wrote:
>| Hi,
>|
>| Is there any tool like purify(memory leak tool) for LINUX. Or any
>| free software which can be used to check memory leaks on a C/c++
>| program.
>
> memprof is one such tool. I've used it a
I noticed a few different posts from people having similar
problems to mine (a couple of examples follow), in which
LILO would stop after just typing "LI" on the screen and
hang up. Various different reasons for the problem were
proposed, centering on hardware compatibility proble
On Thu, Dec 07, 2000 at 11:32:17PM -0500, D-Man wrote:
>
> I had the problem of LILO stopping at "LI" when booting from the MBR on my
> machine. Upon further research I found that my BIOS is too cheap to boot from
> /dev/hdc. (Using LILO to boot from floppy worked, but cou
On 08 Dec 2000, kmself@ix.netcom.com wrote:
> on Fri, Dec 08, 2000 at 09:31:24AM -0600, Robert Guthrie ([EMAIL PROTECTED])
> wrote:
>
> > By the way, in my research, I discovered the vga = option in the lilo.conf
> > manual. Now I can avoid wasting all of the screen real-estate on 40x25
> > c
Quoth kmself@ix.netcom.com,
> In which case, you'll *love* SVGATextMode. Though I hear it's being
> replaced with something else in future versions of Linux.
The framebuffer console replaces SVGATextMode (although something else
might be replacing that, for all I know). Running the Matrox frameb
on Fri, Dec 08, 2000 at 09:31:24AM -0600, Robert Guthrie ([EMAIL PROTECTED])
wrote:
> By the way, in my research, I discovered the vga = option in the lilo.conf
> manual. Now I can avoid wasting all of the screen real-estate on 40x25
> characters. Check it out if you don't know about it alre
The prize goes to Jiri Klouda *applause* for the winning tip. I checked out
/usr/share/doc/lilo, and found the section that mentioned about 6
permutations of lilo just printing out "LIL-" (I mis-remembered, and thought
it was just "LI-". Anyway, the /boot/map file had not
I had the problem of LILO stopping at "LI" when booting from the MBR on my
machine. Upon further research I found that my BIOS is too cheap to boot from
/dev/hdc. (Using LILO to boot from floppy worked, but couldn't find /dev/hda).
My solution is to use loadlin.exe (from AUTOEXEC.BAT).
-D
On Tuesday 05 December 2000 15:31, Scott Patterson wrote:
> I would assume it's not a virus since the "LI-" is common when your MBR is
> messed up. Did you install a new kernel recently?
>
Yes, but after the re-boot, it worked for at least 2-3 reboots before the
problem
reboot and get:
> LI-
>
> And the computer just locks. I'm 99.9% sure that I didn't re-run lilo, so
> this must be some problem either with hardware, or some virus, or a bug in
> lilo. Anybody got a good starting point for investigation? I can still use
> the boot
>After setting up lilo on my MBR to allow me to dual-boot Debian and my
>game-OS, everything worked well. I had to use the lba32 option in lilo.conf
>to get this to work, so initially I was booting lilo from a floppy.
>
>Well everything is fine for a while, then one day, I rebo
After setting up lilo on my MBR to allow me to dual-boot Debian and my
game-OS, everything worked well. I had to use the lba32 option in lilo.conf
to get this to work, so initially I was booting lilo from a floppy.
Well everything is fine for a while, then one day, I reboot and get:
LI-
And
David Teague [EMAIL PROTECTED] wrote:
>
> Would someone please give me a reference on the reiserfs? That is a
> new fs on me. What advantage does it have over e2fs?
Have a look at:
http://www.namesys.com/
Basically, reiserfs is a journalling file system which gives better
performance (faster
On Fri, 27 Oct 2000, Ethan Benson wrote:
> On Fri, Oct 27, 2000 at 07:33:22PM +1100, Brian May wrote:
> > > "Ethan" == Ethan Benson <[EMAIL PROTECTED]> writes:
> >
> > Ethan> LILO is not compatible with reiserfs, either make /boot
> > Ethan> ext2 again or use GNU grub instead.
>[sni
On Fri, Oct 27, 2000 at 07:33:22PM +1100, Brian May wrote:
> > "Ethan" == Ethan Benson <[EMAIL PROTECTED]> writes:
>
> Ethan> LILO is not compatible with reiserfs, either make /boot
> Ethan> ext2 again or use GNU grub instead.
>
> I assume grub is compatible with reiserfs?
the docs a
> "Ethan" == Ethan Benson <[EMAIL PROTECTED]> writes:
Ethan> LILO is not compatible with reiserfs, either make /boot
Ethan> ext2 again or use GNU grub instead.
I assume grub is compatible with reiserfs?
I am a bit confused - why is lilo incompatible with reiserfs? I thought
all lilo
Cool. Good thing you have some other systems
you can call on. Unfortunately, my combination
of a 2.2 kernel and 56k modem prevents me from
helping more directly.
Goode luck.
On Fri, Oct 27, 2000 at 01:20:25AM -0500, Pascal Hos wrote:
> On Thu, Oct 26, 2000 at 11:20:02PM -0700, Rob wrote:
> > to
Well I just solved it. I compiled the 2.4-test9 kernel with reiser
patches on a different machine and wrote the image to a floppy using
make bzdisk and then used that disk as my boot disk. This let me mount
my reiser file systems. Then I backed up /boot, unmounted it and made it
ext2 again. Copied
On Fri, Oct 27, 2000 at 12:28:14AM -0500, Pascal Hos wrote:
>
> How do I get back into the system so that I can change these options?
> With the rescue disk I can only get into / and nothing else is available
> to me (No /usr, /boot, /var, etc)
> Any suggestions?
boot a debian rescue floppy, type
On Thu, Oct 26, 2000 at 11:20:02PM -0700, Rob wrote:
> touche.
>
> I recall someone on the -boot list posting about
> an unofficial rescue+reiserfs disk ( intended
> for install, but sure would help in this case ).
>
> check out this thread, mentions that lilo
> will handle a reiserfs /boot wit
touche.
I recall someone on the -boot list posting about
an unofficial rescue+reiserfs disk ( intended
for install, but sure would help in this case ).
check out this thread, mentions that lilo
will handle a reiserfs /boot with the -notail
option ( next in thread )
http://lists.debian.org/debi
On Thu, Oct 26, 2000 at 10:56:08PM -0700, Rob wrote:
> Boot the rescue disk.
>
> mount -a
>
> ( this will mount all filesystems listed in your /etc/fstab )
>
>
> > How do I get back into the system so that I can change these options?
> > With the rescue disk I can only get into / and nothing el
; > > I seem to have messed up now.
> > > I just made all my partitions except for / reiserfs (this includes
> > > /boot). Now when I try to boot the computer Lilo doesn't get past LI and
> > > just sits there. Of course I do not have a rescue disk that will
Lilo doesn't get past LI and
> > just sits there. Of course I do not have a rescue disk that will allow
> > me to mount a reiser partition, so I'm stuck.
> > I assume that I would have to rerun lilo to get out of this, however
> > since lilo can't read /boo
On Thu, Oct 26, 2000 at 11:35:57PM -0500, Pascal Hos wrote:
> I seem to have messed up now.
> I just made all my partitions except for / reiserfs (this includes
> /boot). Now when I try to boot the computer Lilo doesn't get past LI and
> just sits there. Of course I do not have a
I seem to have messed up now.
I just made all my partitions except for / reiserfs (this includes
/boot). Now when I try to boot the computer Lilo doesn't get past LI and
just sits there. Of course I do not have a rescue disk that will allow
me to mount a reiser partition, so I'm stuck
On Thu, Aug 31, 2000 at 11:47:25AM +0900, Jack Morgan wrote:
> I installed debian on a new HDD and after installing the base I get LI at
> boot time? Any suggestions as to what I did wrong?
I guess your kernel is below the 1024 limit...
The easiest way to avoid these problems is to cre
On Thu, 31 Aug 2000, Debian User Jean-Baptiste Note wrote:
>This limitation has only recently been left off, and could arise if you
>use your disk in normal mode.
This was it. Changed HDD to LBA from normal and all was fine!
Cheers
Jack Morgan Debian GNU/Linux Enthusia
Getting a prompt like "LI" or "LIL" is a situation from
where the system just cannot boot from the hard disk
because the LILO code placed in the MBR is broken. The
solution to this problem lies in fixing the Master Boot
Record.
You have no option but to boot from the ba
Here's what a get from "Linux Kernel Insternals" :
Startup Messages :
LI : the first step of the loaderhas been able ro load the second step
whose processing then failed. This can be caused by an incorrect
geometry or by repositionning the file boot.b without reinstalling the
lo
on a new HDD and after installing the base I get LI at
> >boot time? Any suggestions as to what I did wrong?
>
> I also tried Tom's boot disk and got LIL-
>
> Thanks
> Jack Morgan Debian GNU/Linux Enthusiast
> [EMAIL PROTECTED]
On Thu, 31 Aug 2000, Jack Morgan wrote:
>I installed debian on a new HDD and after installing the base I get LI at
>boot time? Any suggestions as to what I did wrong?
I also tried Tom's boot disk and got LIL-
Thanks
Jack Morgan Debian GNU/Linux Enthus
I installed debian on a new HDD and after installing the base I get LI at
boot time? Any suggestions as to what I did wrong?
Thanks
Jack Morgan Debian GNU/Linux Enthusiast
[EMAIL PROTECTED] http://www.mandinka.org
On 11-Aug-2000 USM Bish wrote:
> On Thu, 10 Aug 2000, Lehel Bernadt wrote:
>> On 09-Aug-2000 USM Bish wrote:
>> > I am at this game for the last few years. There are two solutions to this:
>> >
>> > Solution 1: If you have multiple OSs (like me) with Debian 2.1, Slack-7,
>> > and Win-98, (and BeO
On Thu, 10 Aug 2000, Lehel Bernadt wrote:
> On 09-Aug-2000 USM Bish wrote:
> > I am at this game for the last few years. There are two solutions to this:
> >
> > Solution 1: If you have multiple OSs (like me) with Debian 2.1, Slack-7,
> > and Win-98, (and BeOS till recently):
> >
> >a) Create
On 09-Aug-2000 USM Bish wrote:
> I am at this game for the last few years. There are two solutions to this:
>
> Solution 1: If you have multiple OSs (like me) with Debian 2.1, Slack-7,
> and Win-98, (and BeOS till recently):
>
>a) Create a separate partition, (Type of partition msdos or vfat
I've installed kernels many times in the last few weeks on my two Potato
systems, but last night for the first, after installing 2.2.15, the sysem
showed the same LI boot problem, would not go any further.
I don't have a floppies, don't have floppy drives on the systems, but I do
ha
I had the LI problem on the first install of Linux. I believe that for me
it occurred because my Linux boot partition was too far (>500MB) from the
master boot block. In that case, a boot floppy worked instead.
Arthur H. Edwards
712 Valencia Dr. NE
Abq. NM 87108
(505) 256-0834
On Fri, 16
/usr/doc/lilo/manual on Debian:
LI The first stage boot loader was able to load the second stage boot
loader, but has failed to execute it. This can either be caused by a
geometry mismatch or by moving /boot/boot.b without running the map
installer.
sorry, problems with
On Mon, 3 Apr 2000 21:33:56 +0200 (CEST), [EMAIL PROTECTED] wrote:
>
> Hi,
>
> I have'nt followed the thread, so it could be that i repeat
> someones answer. But here it goes anyway:
>
> If you want to boot from an scsi-disk in a mixed ide-scsi setup
> then do the following:
>
> 1. set your bios to
Hi,
I have'nt followed the thread, so it could be that i repeat
someones answer. But here it goes anyway:
If you want to boot from an scsi-disk in a mixed ide-scsi setup
then do the following:
1. set your bios to boot from scsi first
2. tell LILO about this with (lilo.conf)
disk=/dev/sda
ng lilo -v, it
detects hda1, and gives me the warning message that sda2 is not on the
first disc which leads to me getting "LI" at boot. I'm thinking the
BIOS might still report the IDE as the first device, but boot from the
SCSI. Don't know really. Last night, I tried putti
> > > drive. I CAN boot using the rescue floppy, and everything works
> > > fine. Normally the "LI" problem was easily fixed by rerunning lilo, but
> > > that doesn't seem to be working. This type of setup worked for a year
> > > and a half on
g make-kpkg), and now I can't boot my Linux
> > drive. I CAN boot using the rescue floppy, and everything works
> > fine. Normally the "LI" problem was easily fixed by rerunning lilo, but
> > that doesn't seem to be working. This type of setup worked for a y
sing the rescue floppy, and everything works
> fine. Normally the "LI" problem was easily fixed by rerunning lilo, but
> that doesn't seem to be working. This type of setup worked for a year
> and a half on my old system. If anyone has any suggestions, I'd be
> grateful.
I've recently install a new potato system that's been working well for a couple
of weeks. Yesterday I compiled a custom kernel (2.2.14) (installed using
make-kpkg), and now I can't boot my Linux drive. I CAN boot using the rescue
floppy, and everything works fine. Normally t
Subject: Re: "LI" for LILO or loading from a second harddrive
Date: Mon, Jan 10, 2000 at 04:42:29PM +0100
In reply to:[EMAIL PROTECTED]
Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]):
>| LILO can only boot Opertive Systems located in primary partitions
>| (max 4
[EMAIL PROTECTED] wrote:
>
> LILO can only boot Opertive Systems located in primary partitions
> (max 4) and located in the first hard drive that usually is "/dev/hda ".
>
> Bye bye.
This is not correct as stated.
Here is an informative item :
http://www.heise.de/ct/english/99/12/166/
I quot
y Genkin <[EMAIL PROTECTED]>
debian-user@lists.debian.org
From: Peter Ross <[EMAIL PROTECTED]>
Date: 10/01/2000 12.35.04 GMT
10/01/2000 15.49.36
Subject: Re: "LI" for LILO or loading from a second harddrive
- Memo - Message
On 08-Jan-2000, Bryan Scaringe <[EMAIL PROTECTED]> wrote:
> Lilo must be installed in the MBR of /dev/hda. That is where your BIOS
> looks to boot your system. change your boot" line to look like:
> boot=/dev/hda
>
> This will install LILO in the MBR of /dev/hda.
>
> LILO can *boot* things pr
st be located where the BIOS looks
(generally the boot sector of your first floopy drive, or the MBR of
your first Hard disk.
Bryan
On 08-Jan-2000 Arcady Genkin wrote:
> I've installed potato on the second harddrive. Lilo won't boot from
> the HD (hangs at "LI" prompt). I can
I've installed potato on the second harddrive. Lilo won't boot from
the HD (hangs at "LI" prompt). I can boot from the boot floppy just
fine.
My lilo.conf and the disk layout are quoted below. I tried adding
"linear" and "compact" (interchangeably) to l
Answer: linear...
[or lilo -l ]
boots fine now. Found this tidbit in an old lilo users guide at
http://www.yggdrasil.com/bible/lilo/user/user.html
though I should have thought of this earlier...
-dh
Dan Hugo wrote:
>
> Greetings-
>
> I am getting the
>
> LI_ (flashing _)
>
> at boot of
Greetings-
I am getting the
LI_ (flashing _)
at boot of my newly installed slink on a dual PPro machine.
I have a 14G IBM drive in there with /dev/hda1 partitioned to 200Megs,
exactly the same as another identical drive in my normal machine (in
other words, both have /dev/hda1 sizes the same,
Brian Boonstra wrote:
>
> Hi
>
> I can no longer boot into Debian! I installed IE5 in my WinNT
> partition, and after that Lilo would boot WinNT at the prompt, but hang on
> trying to boot Linux. Then after some fiddling it broke completely, giving
> me the le
ddling it broke completely, giving
> me the letters LI (in the same position as I previously saw a whole LILO
> prompt), and the system hung.
> I reckoned Lilo was the problem, and installed a different boot
> loader (PQBoot from Powerquest). Now I can still boot into WinNT, but if
1 - 100 of 146 matches
Mail list logo
