Lilo problem after pacman -Syu

Arielext · 2003-03-11 15:43:11

22.5 (euhm ... the lastest)
gives me the 10101010101 error as well
22.4 worked like a charm. So I'm sticking with that one, where is the "don't ever update this package" option in pacman ?

sarah31 · 2003-03-11 16:07:04

actually after looking at how the last three versions built it should be 22.4.1 that did not work because it produced no files in /boot. It must have been the files from the previous versio or some trickery in it that causes it it not to have troubles.

as for the patched version above i am hoping that is the fix for most of course it is not in the trees so you will have to use the PKGBUILD to build yourself a fresh lilo. for me i was getting the 01 error and after rebuilding with the patches i did not.

orelien · 2003-03-11 18:16:24

sarah31 wrote:

for me i was getting the 01 error and after rebuilding with the patches i did not.

Yes! I've just built lilo 22.5 with the patches, and it now it works

I hope these patches will found their way in the trees soon

apeiro · 2003-03-11 18:18:58

Posted by John Coffman (author of lilo) on freshmeat:

A sensitivity of 22.5 to the video BIOS unexpectedly trashing the DX register has been tracked down on one system. The DX register contains the boot device code, so this is a fatal error. Symptoms were very similar to the two reports described here.

So the protectDX patch should fix the problems for those of us experiencing it. I've updated the lilo package with the protectDX patch. Please confirm that this fixes it for you (all), so I can stop looking for other answers.

orelien · 2003-03-18 16:26:25

arielext wrote:

where is the "don't ever update this package" option in pacman ?

It is now available in pacman-2.3.2
Check your /etc/pacman.conf file...

sinister · 2003-03-18 20:47:16

HI all.

I had the same problem as all of you.. the 010101010110 error.

so i did something simple.. i added the following to my /etc/lilo.conf and it works fine now.

disk=/dev/discs/disc0/disc bios=0x80 (for master) or 0x81 (for slave)

I discovered this as a bios geometry mismatch.. but my solution above solved it.

good luck.

sarah31 · 2003-03-18 23:20:19

heh simple eh?

not a simple a the patch applied

simple as pie pacman -Syu grabs the new fixed lilo. no changing of the conf file is necessary.

sinister · 2003-03-19 16:35:06

simple now.. hehehe.. not simple then..

(i damn near pulled all my hair out looking.. )

sarah31 · 2003-03-19 18:34:09

well i did too but after trying a few of the suggestions here i decided that it would be more prudent to find a universalo "fix" for everyone. that search ultimately led to looking in the lilo download trees for the fix. fortunately for me they had one.

sinister · 2003-03-19 19:17:32

Wish i'd had you on my side "BEFORE" i suffered trying to find a solution.

Arch Linux

#26 2003-03-11 15:43:11

Re: Lilo problem after pacman -Syu

#27 2003-03-11 16:07:04

Re: Lilo problem after pacman -Syu

#28 2003-03-11 18:16:24

Re: Lilo problem after pacman -Syu

#29 2003-03-11 18:18:58

Re: Lilo problem after pacman -Syu

#30 2003-03-18 16:26:25

Re: Lilo problem after pacman -Syu

#31 2003-03-18 20:47:16

Re: Lilo problem after pacman -Syu

#32 2003-03-18 23:20:19

Re: Lilo problem after pacman -Syu

#33 2003-03-19 16:35:06

Re: Lilo problem after pacman -Syu

#34 2003-03-19 18:34:09

Re: Lilo problem after pacman -Syu

#35 2003-03-19 19:17:32

Re: Lilo problem after pacman -Syu

Board footer