Bug#345931: grub 0.97 doesn't work on several machines
The first installation report states that /grub/stage1 exists. Is that indeed true? Checking if "/boot/grub/stage1" exists... no Checking if "/grub/stage1" exists... yes Checking if "/grub/stage2" exists... yes Checking if "/grub/e2fs_stage1_5" exists... yes
Bug#352207: grub-update does not work since update to 0.97-3
Well that defininatly explains why update-grub stops. It gets 1 as return value and therefore exits. It seems that the file /dev/sda1 does not exist or something goes wrong in readlink. Can you try ls -la /dev/sda1 in order to see what /dev/sda1 points to? Kristian On 2/12/06, Didrik Pinte <[EMAIL PROTECTED]> wrote: > Le dimanche 12 février 2006 à 19:22 +0100, Kristian Edlund a écrit : > > Hi again > > > > It doesn't fail on my machine, so either it is caused by the amd64 > > architecture or the raid device. > > > > It seems to fail around the command readlink -f /dev/sda1 > > Can you send the output of > > > > readlink -f /dev/sda1 > > and > > readlink -f /dev/sda1 ; echo $? > > > > Kristian > > Here you are ;-) > --- > serveurmeteo:/home/did# readlink -f /dev/sda1 > serveurmeteo:/home/did# readlink -f /dev/sda1 ; echo $? > 1 > serveurmeteo:/home/did# > --- > > Didrik > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.2 (GNU/Linux) > > iD8DBQBD735Z9Rlh4Zs4yBMRArq3AJ0ScNiD5Tei3tjRZW1RQEPP3vRjQgCeONC5 > naJ0iqUgOEP212TJY23dxK4= > =LuLN > -END PGP SIGNATURE- > > > ___ > Pkg-grub-devel mailing list > [EMAIL PROTECTED] > http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel > > >
Bug#352207: grub-update does not work since update to 0.97-3
Hi again It doesn't fail on my machine, so either it is caused by the amd64 architecture or the raid device. It seems to fail around the command readlink -f /dev/sda1 Can you send the output of readlink -f /dev/sda1 and readlink -f /dev/sda1 ; echo $? Kristian On 2/12/06, Didrik Pinte <[EMAIL PROTECTED]> wrote: > Le samedi 11 février 2006 à 10:19 +0100, Kristian Edlund a écrit : > > Can you reproduce the error when you run update-grub with "sh update-grub"? > > > > Can you send supply your menu.lst file, and try to run update-grub > > with "sh -x update-grub " and send the output of that file as well. > > > > Kristian > > The output of "sh -x /sbin/update-grub" is the following (showing no > errors) : > > -- > serveurmeteo:/home/did# sh -x /sbin/update-grub > + set -e > + grub_dirs='/boot/grub /boot/boot/grub' > ++ find_grub_dir > ++ echo -n 'Searching for GRUB installation directory ... ' > Searching for GRUB installation directory ... ++ for d in '$grub_dirs' > ++ '[' -d /boot/grub ']' > ++ grub_dir=/boot/grub > ++ break > ++ '[' -z /boot/grub ']' > ++ echo 'found: /boot/grub' > found: /boot/grub > ++ echo /boot/grub > + grub_dir=/boot/grub > + menu_file=/boot/grub/menu.lst > ++ find_root_device > +++ find_device / > +++ mount_point=/ > +++ device= > +++ '[' -f /etc/fstab ']' > +++ read DEV MNT FOO > grep -q '^#' > echo '#' > +++ continue > +++ read DEV MNT FOO > echo '#' > grep -q '^#' > +++ continue > +++ read DEV MNT FOO > echo '#' > grep -q '^#' > +++ continue > +++ read DEV MNT FOO > echo proc > grep -q '^#' > +++ '[' /proc = / ']' > +++ read DEV MNT FOO > echo /dev/sda1 > grep -q '^#' > +++ '[' / = / ']' > +++ device=/dev/sda1 > +++ read DEV MNT FOO > echo /dev/sda5 > grep -q '^#' > +++ '[' none = / ']' > +++ read DEV MNT FOO > echo /dev/hda > grep -q '^#' > +++ '[' /media/cdrom0 = / ']' > +++ read DEV MNT FOO > echo /dev/fd0 > grep -q '^#' > +++ '[' /media/floppy0 = / ']' > +++ read DEV MNT FOO > echo '' > grep -q '^#' > +++ '[' '' = / ']' > +++ read DEV MNT FOO > +++ '[' -n /dev/sda1 ']' > +++ case "$device" in > readlink -f /dev/sda1 > +++ device= > ++ device= > + root_device= > -- > It seems it did not find any root_device ... > > I've attached the menu.lst file to the mail > > > Didrik > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.2 (GNU/Linux) > > iD8DBQBD7ySo9Rlh4Zs4yBMRAnoNAKCkEVrOfB5aGERYiLarBlPxjSOQawCfaO/s > toYG31UKDRjYhsLEoLsD8os= > =R0nC > -END PGP SIGNATURE- > > > ___ > Pkg-grub-devel mailing list > [EMAIL PROTECTED] > http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel > > > >
Bug#352207: grub-update does not work since update to 0.97-3
Can you reproduce the error when you run update-grub with "sh update-grub"? Can you send supply your menu.lst file, and try to run update-grub with "sh -x update-grub " and send the output of that file as well. Kristian
Bug#344767: This bug is fixed
Yes I believe that he bug is fixed in the 0.97-3 release. I just tried to install kernel 2.4.17-2-k7 and remove it again, and there was no problems with the scripts running. After that I purged the configuration, which also went without problems. I have tested with 2.6.15 as well, which also runs without problems. So I doubt that #349291, is related to this bug. When you try to purge your kernel, what command are you using and what happens? -- Best Regards Kristian Edlund GPG ID: 7DD7559F -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#349313: Error message
A little additional infomation. I realised I can get the error message: XIO: fatal IO error 14 (Bad address) on X server ":0.0" after 2514 requests (2513 known processed) with 0 events remaining. -- Best Regards Kristian Edlund GPG ID: 7DD7559F -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#349313: Crashes when using copy/paste
Package: aterm Version: 1.0.0-1 Severity: normal Aterm crashes when I try to copy and paste stuff. I can reproduce it by: 1. opening two terminal. 2. In terminal 1 mark some text with the mouse 3. Use the 3rd mousebutton (whatever it is called, the one that is used to paste text) to paste the text into the other terminal. It just closes, no error message I can find. It started recently, probably around the time you upgrade to 1.0.0. Kristian -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14 Locale: LANG=en_DK, LC_CTYPE=en_DK (charmap=ISO-8859-1) Versions of packages aterm depends on: ii libc6 2.3.5-12 GNU C Library: Shared libraries an ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li aterm recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#239111: XFS status
Hi everyone Do you know the status of the xfs bug in grub which casues #309218, #239111, #243835 and #246111. There is a supplied patch, but I do not have the possibility to test it. -- Best Regards Kristian Edlund GPG ID: 7DD7559F -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#221398: grub: provide a sample bootsplash image and corresponding menu.lst stanzas
Hi Hi I am "new" on the grub development team, and I found your bugreport a few days ago, I intend to look into it, and test it. But I haven't had the time so far. So the patch has not been merged and the current status is still that nothing is done afaik. Kristian On 1/16/06, Martin-Éric Racine <[EMAIL PROTECTED]> wrote: > I'm just wondering whatever happened to this bug. Was the patch ever > merged? Was it instead rejected? What is the current status? > > -- > Martin-Éric Racine > http://q-funk.iki.fi > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.2 (GNU/Linux) > > iD8DBQBDywfIeXr56x4Muc0RAv66AKCBIwi/2DAOrOPT0uKeiot2lIlMiACfUO8u > QjAC995OpkoXEivjIyFSt9w= > =PlNc > -END PGP SIGNATURE- > > > ___ > Pkg-grub-devel mailing list > [EMAIL PROTECTED] > http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel > > >
Bug#283308: Fixed
Seems that I was wrong before, I accidently broke the script so it was not updating correctly, so the patch for 346596 did not fix the problem. However, I made a patch and applied it, so now it is really fixed and pending. No really, I promise :) -- Best Regards Kristian Edlund GPG ID: 7DD7559F -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#346596: Updated the patch
I just updated the patch to fit on the 0.97-3 release on grub.
I have attached the patch
Kristian
--- update-grub.orig2006-01-10 13:57:26.0 +0100
+++ update-grub 2006-01-10 13:58:55.0 +0100
@@ -760,7 +760,7 @@
echo "$splashimage_path" >> $buffer
echo >> $buffer
elif [ "$current_splash" != "" ] && [ "$current_splash" != "$splashimage_path"
]; then
- echo "found but preserving previous setting: $(grep '^splashimage='
/boot/grub/menu.lst)" >&2
+ echo "found but preserving previous setting: $(grep '^splashimage='
${grub_dir}/menu.lst)" >&2
echo "$current_splash" >> $buffer
echo >> $buffer
else
Bug#264312: New patch
Since the last part only partly solved one of the problems. here is a
new patch that actually solves both problems. My test list of kernels is
sorted:
/boot/vmlinuz-2.6.15
/boot/vmlinuz-2.6.14.2+pre2
/boot/vmlinuz-2.6.14.2-ac99
/boot/vmlinuz-2.6.14.2pre2
/boot/vmlinuz-2.6.14.2-pre2
/boot/vmlinuz-2.6.14-ac99
/boot/vmlinuz-2.6.14pre2
/boot/vmlinuz-2.6.14-pre2
/boot/vmlinuz-2.6.14
The +pre2 is put in the top since it does not understand it and
therefore is treated as an unknown.
I have attached the patch
Kristian
--- update-grub.orig2006-01-05 16:44:42.0 +0100
+++ update-grub 2006-01-06 10:41:43.0 +0100
@@ -445,13 +445,23 @@
# 0 if A==B
# 1 if A>B
# This compares version numbers of the form
-# 2.4.14-random > 2.4.14-ac10 > 2.4.14 > 2.4.14-pre2 >
+# 2.4.14.2 > 2.4.14
+# 2.4.14random = 2.4.14-random > 2.4.14-ac10 > 2.4.14 > 2.4.14-pre2 >
# 2.4.14-pre1 > 2.4.13-ac99
CompareVersions()
-{
- # First split the version number and remove any '.' 's or dashes
- v1=$(echo $1 | sed -e 's![-\.]\+! !g' -e 's![\.\-]!!g')
- v2=$(echo $2 | sed -e 's![-\.]\+! !g' -e 's![\.\-]!!g')
+{
+ #Changes the line something-x.y.z into somthing-x.y.z.q
+ #This is to ensure that kernels with a .q is treated as higher than the
ones without
+#First a space is put after the version number
+v1=$(echo $1 | sed -e 's!^\(.*-\([0-9]\+\.\)\{2,3\}[0-9]\+\)\(.*\)!\1
\3!g')
+ v2=$(echo $2 | sed -e 's!^\(.*-\([0-9]\+\.\)\{2,3\}[0-9]\+\)\(.*\)!\1
\3!g')
+ #If the version number only has 3 digits then put in another .0
+v1=$(echo $v1 | sed -e 's!^\(.*-\([0-9]\+\.\)\{2\}[0-9]\+\)\(
.*\)!\1.0 \3!g')
+v2=$(echo $v2 | sed -e 's!^\(.*-\([0-9]\+\.\)\{2\}[0-9]\+\)\(
.*\)!\1.0 \3!g')
+
+ # Then split the version number and remove any '.' 's or dashes
+ v1=$(echo $v1 | sed -e 's![-\.]\+! !g' -e 's![\.\-]!!g')
+ v2=$(echo $v2 | sed -e 's![-\.]\+! !g' -e 's![\.\-]!!g')
# we weight different kernel suffixes here
# ac = 50
Bug#164140: Status
This bug is reported in 0.92-3.0.skolelinux.1, is it still the case in newer versions of the grub? Kristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#130353: Status of this bug
This seems to be a bug in a version of grub that was used before woody, does anybuddy know if this if this bug exists in the newer releases of grub? Kristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#264312: ops
I just realised, this pacth will not fix this problem, since it the kernel name looked different from the standard. So please disregard the info on this bug, it should still close #342221 though. Kristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#264312: Patch
I made a patch that I think will sort the kernels correctly.
When comparing the kernel version if the kernel looks like
vmlinuz-2.6.14-pre2 it will change it to vmlinuz-2.6.14.0-pre2
thereby ensuring that 2.6.14.2 is treated as newer since 2>0 and
therefore it is placed higher in the menu than 2.6.14
This patch will close #264312 and #342221
Kristian
--- grub-0.97/debian/update-grub.orig 2005-12-08 04:23:53.0 +0100
+++ grub-0.97/debian/update-grub2005-12-08 04:24:57.0 +0100
@@ -436,13 +436,20 @@
# 0 if A==B
# 1 if A>B
# This compares version numbers of the form
+# 2.4.14.2 > 2.4.14
# 2.4.14-random > 2.4.14-ac10 > 2.4.14 > 2.4.14-pre2 >
# 2.4.14-pre1 > 2.4.13-ac99
CompareVersions()
{
- # First split the version number and remove any '.' 's or dashes
- v1=$(echo $1 | sed -e 's![-\.]\+! !g' -e 's![\.\-]!!g')
- v2=$(echo $2 | sed -e 's![-\.]\+! !g' -e 's![\.\-]!!g')
+
+ #Changes the line something-x.y.z into somthing-x.y.z.q
+ #This is to ensure that kernels with a .q is treated as higher than the
once without
+ v1=$(echo $1 | sed -e
's!\(^.*-\([0-9]\+\.\)\{2\}[0-9]\+\)\(-\|$\)!\1.0\3!g')
+ v2=$(echo $2 | sed -e
's!\(^.*-\([0-9]\+\.\)\{2\}[0-9]\+\)\(-\|$\)!\1.0\3!g')
+
+ # Then split the version number and remove any '.' 's or dashes
+ v1=$(echo $v1 | sed -e 's![-\.]\+! !g' -e 's![\.\-]!!g')
+ v2=$(echo $v2 | sed -e 's![-\.]\+! !g' -e 's![\.\-]!!g')
# we weight different kernel suffixes here
# ac = 50
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#260391: fixed in 0.97-1
grub-set-default is included in the 0.97-1 release of grub. This fixes this bug as far as I know. Kristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306899: fixed?
In 0.97-1 grub-set-default is included. I think that closes this bug. Kristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342221: merging?
This sounds like the same bug as #264312, you might want to consider merging them. Kristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#264038: patch
The files are placed in /lib/grub/i386-pc in Debian instead of
/usr/lib/grub/i386-pc.
I attached a pacth for the documentation, if that is of any use.
Kristian
=
--- grub-0.97/docs/grub.texi.orig2005-12-06 03:22:16.0 +0100
+++ grub-0.97/docs/grub.texi2005-12-06 03:14:39.0 +0100
@@ -479,13 +479,13 @@
if, by any chance, your hard drive becomes unusable (unbootable).
GRUB comes with boot images, which are normally put in the directory
[EMAIL PROTECTED]/usr/lib/grub/i386-pc}. If you do not use grub-install, then
[EMAIL PROTECTED]/lib/grub/i386-pc}. If you do not use grub-install, then
you need to copy the files @file{stage1}, @file{stage2}, and
@file{*stage1_5} to the directory @file{/boot/grub}, and run the
@command{grub-set-default} (@pxref{Invoking grub-set-default}) if you
intend to use @samp{default saved} (@pxref{default}) in your
configuration file. Hereafter, the directory where GRUB images are
-initially placed (normally @file{/usr/lib/grub/i386-pc}) will be
+initially placed (normally @file{/lib/grub/i386-pc}) will be
called the @dfn{image directory}, and the directory where the boot
loader needs to find them (usually @file{/boot/grub}) will be called
the @dfn{boot directory}.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#243858: fixed
This bug is to the best of my knowlegde fixed in version 0.97-1. Kristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
