Re: problems with GRUB
On Sat, 25 Jul 2020 anthony gennard wrote: Almost 15 months ago I suffered a massive stroke and am left with memory loss. I am 90 years of age, and i`m westling with trying to recover some computer skill. Welcome back, and good luck with your project. I have managed to build a further machine and double installed Debian 10 from a CD received with Debian magazine There is a magazine? With glossy pictures, top ten lists and letters to the editor? and Windows 10. The install process installed Grub in two parts and makes it difficult to catch the option to launch the first, it flies passed too fast. I`m too slow to react. Grub's default timeout of five seconds makes me anxious too. Makes me feel like I'm holding up the checkout line at the grocery store or something. In the file /etc/default/grub I edit the line GRUB_TIMEOUT=5 to read instead GRUB_TIMEOUT=10 and then I run # update-grub This gives me a 10 second timeout, which for me makes all the difference. You can disable the timeout entirely by setting the value to -1, so that it looks like this (don't leave out the minus sign): GRUB_TIMEOUT=-1 With that setting, it will wait for your input as long as you like. I am reluctant to try to set up a graphic. How do I do that please. I doubt I can help you with this, if I understand you correctly. I prefer just-the-facts while booting. I'd be more likely to have notes on removing splash screens than setting them up. Is the typeface legible? The second problem I have is with the second machine with a very old install for which I cannot remember the login details. I have done research but I think the advice is not correct. Does anyone have any advice please. I've got nothing to add to Dan's advice here. I`m sorry this is so vague Nothing vague here. You're doing fine on that score. but it is very difficult for me. I`m getting a little better but I think I`m hoping for too much/ I know that feeling all too well. Good luck. -- Ce qui est important est rarement urgent et ce qui est urgent est rarement important -- Dwight David Eisenhower
Re: problems with GRUB
anthony gennard wrote: > Almost 15 months ago I suffered a massive stroke and am left with memory > loss. I am 90 years of age, and i`m westling with trying to recover some > computer skill. > > I have managed to build a further machine and double installed Debian > 10 from a CD received with Debian magazine and Windows 10. The install > process installed Grub in two parts and makes it difficult to catch the > option to launch the first, it flies passed too fast. I`m too slow to > react. I am reluctant to try to set up a graphic. How do I do that please. Hold down an arrow key as the machine boots. Grub will stop the countdown. > The second problem I have is with the second machine with a very old > install for which I cannot remember the login details. I have done > research but I think the advice is not correct. Does anyone have any > advice please. Generically, you can change the root password this way: Use the arrow key method to stop GRUB from booting immediately. Choose to edit the boot command. Add the string init=/bin/sh to the command line, then boot. It should make you root, with no network and no services started. mount -o remount,rw / will make the disk read/write instead of read-only. Now run the passwd command to reset root's password. You will not need to supply the old one. Finally: sync and then reboot or power-cycle. -dsr-
problems with GRUB
Almost 15 months ago I suffered a massive stroke and am left with memory loss. I am 90 years of age, and i`m westling with trying to recover some computer skill. I have managed to build a further machine and double installed Debian 10 from a CD received with Debian magazine and Windows 10. The install process installed Grub in two parts and makes it difficult to catch the option to launch the first, it flies passed too fast. I`m too slow to react. I am reluctant to try to set up a graphic. How do I do that please. The second problem I have is with the second machine with a very old install for which I cannot remember the login details. I have done research but I think the advice is not correct. Does anyone have any advice please. I`m sorry this is so vague but it is very difficult for me. I`m getting a little better but I think I`m hoping for too much/ John
[Solved] Re: Problems upgrading grub-pc
On Thu, 21 Feb 2019 23:27:04 + Brad Rogers wrote: Hello, >Today, upgrading a testing install at the end of which report was >"setting up grub-pc" The problem is that it just sat there, and didn't >complete. Attempts to correct the problem with; Well, in exasperation, and with a sense of trepidation, I rebooted the system. Exasperation, because I'd run out of ideas and clues. Trepidation, because I had no idea whether the machine would reboot successfully. All went well, thankfully. I then retried the upgrade and that proceeded without errors. I have no idea what was wrong, but clearly it was a transient issue. So, problem overcome. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Stained glass windows keep the cold outside Religion - Public Image Ltd pgpBCCYMAWrf1.pgp Description: OpenPGP digital signature
Problems upgrading grub-pc
Hello, Today, upgrading a testing install at the end of which report was "setting up grub-pc" The problem is that it just sat there, and didn't complete. Attempts to correct the problem with; '# dpkg --configure grub-pc' also failed to complete the update. Downgrading to the previous version didn't help, that too just sits there failing to complete. Anybody else seeing this? If anybody has a solution, I'd love to know what it is, as my searches failed to get me anywhere. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" I guess I shouldn't have strangled her to death Ugly - The Stranglers pgpqCHtX0MlYy.pgp Description: OpenPGP digital signature
Re: Problems installing grub/lilo with RAID1 on /
tv.deb...@googlemail.com tv.deb...@googlemail.com writes: Hi, 06/06/2011 20:16, Felix Natter wrote: Tom H tomh0...@gmail.com writes: hello Tom, On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter felix.nat...@smail.inf.fh-brs.de wrote: I am trying to install squeeze (from live DVD[1]) with a RAID1 root filesystem (/dev/md0). There is an error when running grub-install: Jun 5 18:38:18 grub-installer: error: Running 'grub-install --no-floppy --force /dev/sda' failed. I tried to run it manually: chroot /target grub-install --no-floppy --force /dev/sda /usr/sbin/grub-probe: error: no such disk. Auto-detection of a filesystem of /dev/md0 failed. Please report this together with the output of /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub to bug-g...@gnu.org Does /target/etc/mtab exist and is it correct? Seems like it's correct: -- /dev/md0 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0 tmpfs /dev tmpfs rw,relatime,mode=755 0 0 none /proc proc rw,relatime 0 0 -- chroot /target /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: changing current directory to /dev. /usr/sbin/grub-probe: info: changing current directory to mapper. /usr/sbin/grub-probe: info: opening md0. /usr/sbin/grub-probe: error: no such disk. On both Debian and Ubuntu, I used to be able to run dpkg-reconfigure grub-pc, choose md0, sda, and sdb, and grub would be installed on all This results in the same error. three. For a while now (I can't remember for how long), installing to md0's failed. Is this a known bug or unsupported? There have been a longstanding non-reliability of grub-pc with /boot on raid1, have a look at the bug tracker and you'll find several reports revolving around /boot or / on raid1 (#624232 is mine). Problem is solved with the recent mduuid patch that went into grub-pc 1.99 (is in Wheezy/Testing). But I don't know if your problem is related to this or due to the metadata weirdness (see below). Thanks for the suggestion, it all works fine with today's testing (net) installer! Best Regards! -- Felix Natter -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8762og86on@smail.inf.fh-brs.de
Re: Problems installing grub/lilo with RAID1 on /
Tom H tomh0...@gmail.com writes: Tom H tomh0...@gmail.com writes: On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter felix.nat...@smail.inf.fh-brs.de wrote: When trying to install lilo (with the debian-installler), I get inconsistent raid information (but the RAID1 (2x 208G) was created with debian-installer): Jun 5 19:22:00 in-target: Running lilo... Jun 5 19:22:01 in-target: Fatal: Jun 5 19:22:01 in-target: Inconsistent Raid version information on /dev/md0 (RV=0.90 GAI=1.2) What do RV and GAI mean? I've googled both and not foudn anything to help. 0.90 and 1.2 are mdraid metadata versions. Were these disks previously in another array and do you now have two types of metada on them? No, I did not change any hardware config before reinstalling with squeeze. I also had a RAID1 root fs with those two disks before. hi Tom, There may be more to your problem than this but you definitely have a metadata problem. Some more googing yielded RV and GAI as raid version and get array info so your previous mdraid metadata must've been v0.90 and you're new metadata's the Squeeze d-i default, v1.2. Since they're written to different parts of the HD, they can co-exist and must be confusing grub and lilo. I only know how to remove all metadata (with --zero-superblock) so I have no idea how to fix your problem short of backing up your install, recreating your array, and restoring the install... Sorry. No change after I called: mdadm --zero-superblock /dev/sda2 mdadm --zero-superblock /dev/sdb2 Next I tried to create the array directly with mdadm and bypassing partman (d-i partitioner). That way, I can install grub when creating the array with old metadata: $ mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda2 \ /dev/sdb2 --metadata=0.9 However, when I reboot the system, I get: --- Gave up waiting for root device. Common Problems: - Boot args (cat /proc/cmdline): check root=, rootdelay= - Missing modules (cat /proc/modules; ls /dev) - ALERT! /dev/md0 does not exist. Dropping to a shell! --- Here is the fstab from the installed system: --- # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc/proc procdefaults0 0 # / was on /dev/md0 during installation UUID=0a94e4b3-9b3b-4290-9fa3-9e8ed167136a / ext3 errors=remount-ro 0 1 # swap was on /dev/sdb1 during installation UUID=ce46b046-fce5-4298-a06e-2b3680406eaa noneswapsw 0 0 /dev/scd1 /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/scd0 /media/cdrom1 udf,iso9660 user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 --- Could it be that the /dev/md0 I created manually is not permanent because d-i didn't create it (although the manually created /dev/md0 could be seen in partman)? Thank you! -- Felix Natter -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ei35wh9g@smail.inf.fh-brs.de
Re: Problems installing grub/lilo with RAID1 on /
Tom H tomh0...@gmail.com writes: hello Tom, On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter felix.nat...@smail.inf.fh-brs.de wrote: I am trying to install squeeze (from live DVD[1]) with a RAID1 root filesystem (/dev/md0). There is an error when running grub-install: Jun 5 18:38:18 grub-installer: error: Running 'grub-install --no-floppy --force /dev/sda' failed. I tried to run it manually: chroot /target grub-install --no-floppy --force /dev/sda /usr/sbin/grub-probe: error: no such disk. Auto-detection of a filesystem of /dev/md0 failed. Please report this together with the output of /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub to bug-g...@gnu.org Does /target/etc/mtab exist and is it correct? Seems like it's correct: -- /dev/md0 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0 tmpfs /dev tmpfs rw,relatime,mode=755 0 0 none /proc proc rw,relatime 0 0 -- chroot /target /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: changing current directory to /dev. /usr/sbin/grub-probe: info: changing current directory to mapper. /usr/sbin/grub-probe: info: opening md0. /usr/sbin/grub-probe: error: no such disk. On both Debian and Ubuntu, I used to be able to run dpkg-reconfigure grub-pc, choose md0, sda, and sdb, and grub would be installed on all This results in the same error. three. For a while now (I can't remember for how long), installing to md0's failed. Is this a known bug or unsupported? When trying to install lilo (with the debian-installler), I get inconsistent raid information (but the RAID1 (2x 208G) was created with debian-installer): Jun 5 19:22:00 in-target: Running lilo... Jun 5 19:22:01 in-target: Fatal: Jun 5 19:22:01 in-target: Inconsistent Raid version information on /dev/md0 (RV=0.90 GAI=1.2) What do RV and GAI mean? I've googled both and not foudn anything to help. 0.90 and 1.2 are mdraid metadata versions. Were these disks previously in another array and do you now have two types of metada on them? No, I did not change any hardware config before reinstalling with squeeze. I also had a RAID1 root fs with those two disks before. I think it is justified to file a bug against debian-installer. Thanks, -- Felix Natter -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87zkluddvb@smail.inf.fh-brs.de
Re: Problems installing grub/lilo with RAID1 on /
Hi, 06/06/2011 20:16, Felix Natter wrote: Tom H tomh0...@gmail.com writes: hello Tom, On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter felix.nat...@smail.inf.fh-brs.de wrote: I am trying to install squeeze (from live DVD[1]) with a RAID1 root filesystem (/dev/md0). There is an error when running grub-install: Jun 5 18:38:18 grub-installer: error: Running 'grub-install --no-floppy --force /dev/sda' failed. I tried to run it manually: chroot /target grub-install --no-floppy --force /dev/sda /usr/sbin/grub-probe: error: no such disk. Auto-detection of a filesystem of /dev/md0 failed. Please report this together with the output of /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub to bug-g...@gnu.org Does /target/etc/mtab exist and is it correct? Seems like it's correct: -- /dev/md0 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0 tmpfs /dev tmpfs rw,relatime,mode=755 0 0 none /proc proc rw,relatime 0 0 -- chroot /target /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: changing current directory to /dev. /usr/sbin/grub-probe: info: changing current directory to mapper. /usr/sbin/grub-probe: info: opening md0. /usr/sbin/grub-probe: error: no such disk. On both Debian and Ubuntu, I used to be able to run dpkg-reconfigure grub-pc, choose md0, sda, and sdb, and grub would be installed on all This results in the same error. three. For a while now (I can't remember for how long), installing to md0's failed. Is this a known bug or unsupported? There have been a longstanding non-reliability of grub-pc with /boot on raid1, have a look at the bug tracker and you'll find several reports revolving around /boot or / on raid1 (#624232 is mine). Problem is solved with the recent mduuid patch that went into grub-pc 1.99 (is in Wheezy/Testing). But I don't know if your problem is related to this or due to the metadata weirdness (see below). When trying to install lilo (with the debian-installler), I get inconsistent raid information (but the RAID1 (2x 208G) was created with debian-installer): Jun 5 19:22:00 in-target: Running lilo... Jun 5 19:22:01 in-target: Fatal: Jun 5 19:22:01 in-target: Inconsistent Raid version information on /dev/md0 (RV=0.90 GAI=1.2) What do RV and GAI mean? I've googled both and not foudn anything to help. 0.90 and 1.2 are mdraid metadata versions. Were these disks previously in another array and do you now have two types of metada on them? No, I did not change any hardware config before reinstalling with squeeze. I also had a RAID1 root fs with those two disks before. I think it is justified to file a bug against debian-installer. Thanks, Since the different metadata were not stored at the place, it may be possible that your disks retained the old metadata (0.90) together with the new ones (1.2). Did you mdadm --zero-superblock your volumes et some point before doing a new install ? What does mdadm --examine $(raid_member) tell you ? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ded238a.8020...@googlemail.com
Re: Re: Problems installing grub/lilo with RAID1 on /
Tom H tomh0...@gmail.com writes: On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter felix.nat...@smail.inf.fh-brs.de wrote: When trying to install lilo (with the debian-installler), I get inconsistent raid information (but the RAID1 (2x 208G) was created with debian-installer): Jun 5 19:22:00 in-target: Running lilo... Jun 5 19:22:01 in-target: Fatal: Jun 5 19:22:01 in-target: Inconsistent Raid version information on /dev/md0 (RV=0.90 GAI=1.2) What do RV and GAI mean? I've googled both and not foudn anything to help. 0.90 and 1.2 are mdraid metadata versions. Were these disks previously in another array and do you now have two types of metada on them? No, I did not change any hardware config before reinstalling with squeeze. I also had a RAID1 root fs with those two disks before. There may be more to your problem than this but you definitely have a metadata problem. Some more googing yielded RV and GAI as raid version and get array info so your previous mdraid metadata must've been v0.90 and you're new metadata's the Squeeze d-i default, v1.2. Since they're written to different parts of the HD, they can co-exist and must be confusing grub and lilo. I only know how to remove all metadata (with --zero-superblock) so I have no idea how to fix your problem short of backing up your install, recreating your array, and restoring the install... Sorry. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/de3b97f0-5140-4c39-a2f2-b7b9d2c66...@gmail.com
Problems installing grub/lilo with RAID1 on /
hello, I am trying to install squeeze (from live DVD[1]) with a RAID1 root filesystem (/dev/md0). [1] http://cdimage.debian.org/cdimage/release/current-live/i386/iso-hybrid/debian-live-6.0.1-i386-gnome-desktop.iso There is an error when running grub-install: - Jun 5 18:38:08 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro Jun 5 18:38:08 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90solaris Jun 5 18:38:16 grub-installer: info: Installing grub on '/dev/sda' Jun 5 18:38:16 grub-installer: info: grub-install supports --no-floppy Jun 5 18:38:16 grub-installer: info: Running chroot /target grub-install --no-floppy --force /dev/sda Jun 5 18:38:18 grub-installer: /usr/sbin/grub-probe: error: no such disk. Jun 5 18:38:18 grub-installer: Auto-detection of a filesystem of /dev/md0 failed. Jun 5 18:38:18 grub-installer: Please report this together with the output of /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub to bug-g...@gnu.org Jun 5 18:38:18 grub-installer: error: Running 'grub-install --no-floppy --force /dev/sda' failed. Jun 5 18:39:51 init: starting pid 361, tty '/dev/tty3': '-/bin/sh' - I tried to run it manually: - chroot /target grub-install --no-floppy --force /dev/sda /usr/sbin/grub-probe: error: no such disk. Auto-detection of a filesystem of /dev/md0 failed. Please report this together with the output of /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub to bug-g...@gnu.org - Should I report this as d-i bug? The output of grub-probe is as follows: - chroot /target /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: changing current directory to /dev. /usr/sbin/grub-probe: info: changing current directory to mapper. /usr/sbin/grub-probe: info: opening md0. /usr/sbin/grub-probe: error: no such disk. - Should I report this to grub-bug? Is there a way to tell grub-install that this is a ext3 filesystem? Here is /target/fstab: - # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc/proc procdefaults0 0 # / was on /dev/md0 during installation UUID=602edfeb-17c2-4904-a972-ffaa89496418 / ext3 errors=remount-ro 0 1 # swap was on /dev/sdb1 during installation UUID=5c3c731c-0183-4131-ac01-ffab7b5600d9 noneswapsw 0 0 /dev/scd1 /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/scd0 /media/cdrom1 udf,iso9660 user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 - chroot /target mount produces: - rootfs on / type rootfs (rw) none on /proc type proc (rw,relatime) none on /sys type sysfs (rw,relatime) tmpfs on /dev type tmpfs (rw,relatime,mode=755) none on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) /dev/md0 on /target type ext3 (rw,relatime,errors=remount-ro,data=ordered) tmpfs on /target/dev type tmpfs (rw,relatime,mode=755) none on /target/proc type proc (rw,relatime) /dev/sr1 on /cdrom type iso9660 (ro,relatime) /dev/sdg1 on /media type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount-ro) - When trying to install lilo (with the debian-installler), I get inconsistent raid information (but the RAID1 (2x 208G) was created with debian-installer): - Jun 5 19:21:57 in-target: Vormals
Re: Problems installing grub/lilo with RAID1 on /
On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter felix.nat...@smail.inf.fh-brs.de wrote: I am trying to install squeeze (from live DVD[1]) with a RAID1 root filesystem (/dev/md0). There is an error when running grub-install: Jun 5 18:38:18 grub-installer: error: Running 'grub-install --no-floppy --force /dev/sda' failed. I tried to run it manually: chroot /target grub-install --no-floppy --force /dev/sda /usr/sbin/grub-probe: error: no such disk. Auto-detection of a filesystem of /dev/md0 failed. Please report this together with the output of /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub to bug-g...@gnu.org Does /target/etc/mtab exist and is it correct? chroot /target /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub /usr/sbin/grub-probe: info: the size of hd0 is 488397168. /usr/sbin/grub-probe: info: the size of hd1 is 488397168. /usr/sbin/grub-probe: info: changing current directory to /dev. /usr/sbin/grub-probe: info: changing current directory to mapper. /usr/sbin/grub-probe: info: opening md0. /usr/sbin/grub-probe: error: no such disk. On both Debian and Ubuntu, I used to be able to run dpkg-reconfigure grub-pc, choose md0, sda, and sdb, and grub would be installed on all three. For a while now (I can't remember for how long), installing to md0's failed. When trying to install lilo (with the debian-installler), I get inconsistent raid information (but the RAID1 (2x 208G) was created with debian-installer): Jun 5 19:22:00 in-target: Running lilo... Jun 5 19:22:01 in-target: Fatal: Jun 5 19:22:01 in-target: Inconsistent Raid version information on /dev/md0 (RV=0.90 GAI=1.2) What do RV and GAI mean? I've googled both and not foudn anything to help. 0.90 and 1.2 are mdraid metadata versions. Were these disks previously in another array and do you now have two types of metada on them? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktimn946v25zojxqtgfzmerdtncc...@mail.gmail.com
Re: Problems upgrading GRUB to GRUB2 while upgrading to Squeeze from Lenny
On Sat, Feb 5, 2011 at 9:56 PM, Markus Viitamäki mar...@viitamaki.net wrote: On 6 February 2011 03:21, Tom H tomh0...@gmail.com wrote: grub-pc doesn't seem to like your hardware RAID. Does grub-mkdevicemap --verbose --no-floppy give a better clue to what's failing? Sadly no. As it does not say anything more than 'Killed'. grub-mkdevicemap --verbose --no-floppy Killed :( Do any of the following output anything? grub-probe --verbose --target=fs /boot grub-probe --verbose --target=fs_uuid /boot grub-probe --verbose --target=device /boot grub-probe --verbose --target=drive /boot grub-probe --verbose --target=drive --device /dev/sdXY where XY corresponds to /boot or/and / -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTikqjUQvyna8ZnsvYyVFE9B+PXMnydiPQDXYEV=3...@mail.gmail.com
Problems upgrading GRUB to GRUB2 while upgrading to Squeeze from Lenny
Hello! I have this small problem to upgrade GRUB to GRUB2 when upgrading my boxes from Lenny to Squeeze. This problem seems to be related to using Raid or not, as the servers I've tested on and want to upgrade is either using mdadm-raid or hardware-raid. (I have not been able to test on a non-raid system as i don't have one) The problem is that grub-pc package wont install as it fails on a problem like this: Setting up grub-pc (1.98+20100804-14) ... /var/lib/dpkg/info/grub-pc.postinst: line 270: 18302 Killed grub-mkdevicemap --no-floppy dpkg: error processing grub-pc (--configure): subprocess installed post-installation script returned error exit status 137 configured to not write apport reports dpkg: dependency problems prevent configuration of grub: grub depends on grub-pc; however: Package grub-pc is not configured yet. dpkg: error processing grub (--configure): dependency problems - leaving unconfigured configured to not write apport reports Errors were encountered while processing: grub-pc grub E: Sub-process /usr/bin/dpkg returned an error code (1) And I've tried a few other things to just get more information but without success. grub-install --recheck /dev/sda /usr/sbin/grub-install: line 285: 18340 Killed $grub_mkdevicemap --device-map=$device_map $no_floppy grub-mkdevicemap --no-floppy Killed This is the setup of the system and partitions I have: df -h FilesystemSize Used Avail Use% Mounted on /dev/sda3 5.1G 2.7G 2.2G 55% / tmpfs1013M 0 1013M 0% /lib/init/rw udev 10M 2.6M 7.5M 26% /dev tmpfs1013M 0 1013M 0% /dev/shm /dev/sda1 59M 19M 37M 34% /boot /dev/sda4 129G 63G 60G 52% /var uname -a Linux web2-old 2.6.32.15-1-grsec #1 SMP Mon Jun 28 05:23:44 BST 2010 i686 GNU/Linux So now I am asking for advice from you guys for a solution on this. Kind regards, Markus Viitamäki -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=olx2yzjptdxtez1oynw72tfotj91762xzh...@mail.gmail.com
Re: Problems upgrading GRUB to GRUB2 while upgrading to Squeeze from Lenny
On Sat, Feb 5, 2011 at 9:04 PM, Markus Viitamäki mar...@viitamaki.net wrote: I have this small problem to upgrade GRUB to GRUB2 when upgrading my boxes from Lenny to Squeeze. This problem seems to be related to using Raid or not, as the servers I've tested on and want to upgrade is either using mdadm-raid or hardware-raid. (I have not been able to test on a non-raid system as i don't have one) The problem is that grub-pc package wont install as it fails on a problem like this: Setting up grub-pc (1.98+20100804-14) ... /var/lib/dpkg/info/grub-pc.postinst: line 270: 18302 Killed grub-mkdevicemap --no-floppy dpkg: error processing grub-pc (--configure): subprocess installed post-installation script returned error exit status 137 configured to not write apport reports dpkg: dependency problems prevent configuration of grub: grub depends on grub-pc; however: Package grub-pc is not configured yet. dpkg: error processing grub (--configure): dependency problems - leaving unconfigured configured to not write apport reports Errors were encountered while processing: grub-pc grub E: Sub-process /usr/bin/dpkg returned an error code (1) And I've tried a few other things to just get more information but without success. grub-install --recheck /dev/sda /usr/sbin/grub-install: line 285: 18340 Killed $grub_mkdevicemap --device-map=$device_map $no_floppy grub-mkdevicemap --no-floppy Killed This is the setup of the system and partitions I have: df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 5.1G 2.7G 2.2G 55% / /dev/sda1 59M 19M 37M 34% /boot /dev/sda4 129G 63G 60G 52% /var grub-pc doesn't seem to like your hardware RAID. Does grub-mkdevicemap --verbose --no-floppy give a better clue to what's failing? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTindyzCqJ3B3ptv=jmdeoxmpznm562gsn3cnt...@mail.gmail.com
Re: Problems upgrading GRUB to GRUB2 while upgrading to Squeeze from Lenny
On 6 February 2011 03:21, Tom H tomh0...@gmail.com wrote: On Sat, Feb 5, 2011 at 9:04 PM, Markus Viitamäki mar...@viitamaki.net wrote: I have this small problem to upgrade GRUB to GRUB2 when upgrading my boxes from Lenny to Squeeze. This problem seems to be related to using Raid or not, as the servers I've tested on and want to upgrade is either using mdadm-raid or hardware-raid. (I have not been able to test on a non-raid system as i don't have one) The problem is that grub-pc package wont install as it fails on a problem like this: Setting up grub-pc (1.98+20100804-14) ... /var/lib/dpkg/info/grub-pc.postinst: line 270: 18302 Killed grub-mkdevicemap --no-floppy dpkg: error processing grub-pc (--configure): subprocess installed post-installation script returned error exit status 137 configured to not write apport reports dpkg: dependency problems prevent configuration of grub: grub depends on grub-pc; however: Package grub-pc is not configured yet. dpkg: error processing grub (--configure): dependency problems - leaving unconfigured configured to not write apport reports Errors were encountered while processing: grub-pc grub E: Sub-process /usr/bin/dpkg returned an error code (1) And I've tried a few other things to just get more information but without success. grub-install --recheck /dev/sda /usr/sbin/grub-install: line 285: 18340 Killed $grub_mkdevicemap --device-map=$device_map $no_floppy grub-mkdevicemap --no-floppy Killed This is the setup of the system and partitions I have: df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 5.1G 2.7G 2.2G 55% / /dev/sda1 59M 19M 37M 34% /boot /dev/sda4 129G 63G 60G 52% /var grub-pc doesn't seem to like your hardware RAID. Does grub-mkdevicemap --verbose --no-floppy give a better clue to what's failing? Hello! Sadly no. As it does not say anything more than 'Killed'. grub-mkdevicemap --verbose --no-floppy Killed // Markus -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimbmkhkmpmef_treabwkuyk2r1hqwdbr+xwd...@mail.gmail.com
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
On Wed, Mar 28, 2007 at 05:52:23AM +0100, Ian Broadbent wrote: You could of snipped the unnecessary bits. Chris. errr.. that might be good advice Chris BUT, it kinda ASSumes that I knew what the 'unnecessary bits' were ... doesn't it? If I'd known that ... then I would have been able to spot the error instantly (as others did when they saw the full detailed listing). That was the lspci -v listing I was referring to. -- Chris. == Don't forget to check that your /etc/apt/sources.lst entries point to etch and not testing, otherwise you may end up with a broken system once etch goes stable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
On Sun, Mar 25, 2007 at 18:44:30 +0100, ieb wrote: Hello folks, [..] I have rebuilt the 2.6.18-4-amd64 with the NVIDIA components, have installed the nvidia-glx module, but whenever I let the etc/X11/xorg.conf build with the nvidia configuration tool it builds the 'conf' with a declaration for the driver to be nvidia, ...but ... X wont start then, ... warns me that there is no device for NVIDIA 00:1:3 (and/or if I manually change it to include 00:1:3) 00:13:0, and finally stops with a grumble about the kernel kicking out an error 11. BUT, ... if I change xorg.conf to use the driver nv (rather than nvidia) X (gdm) will start, does have the higher resolution set (1600x1200), but has a significant 'pink' colour cast. I can't find a configuration tool for the nvidia settings (such as Gamma etc). Question please... should the driver be 'nvidia' or 'nv', (if 'nvidia' - any suggestions as to what I am missing?) ... if it's should be 'nv' in any event .. then can someone help me find the settings for this to get the colours to be accurately displayed? It depends. IIRC 'nv' is the open source driver that comes with Xorg and 'nvidia' is the proprietary driver. Which one you use depends on what you want out of your card I suppose. Also note that there are two versions of the proprietary driver available in Debian (at least in Sid); the package names for the older one end with -legacy. On top of this there's a new version of the driver out, but it doesn't seem to have hit Sid yet AFAIU it removes support for some older cards. Sorry I can't help you out more than this... /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] http://therning.org/magnus pgpkM6N6TpD9a.pgp Description: PGP signature
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
Question please... should the driver be 'nvidia' or 'nv', (if 'nvidia' - any suggestions as to what I am missing?) ... if it's should be 'nv' in any event .. then can someone help me find the settings for this to get the colours to be accurately displayed? It depends. IIRC 'nv' is the open source driver that comes with Xorg and 'nvidia' is the proprietary driver. Which one you use depends on what you want out of your card I suppose. Thanks Magnus, with the 'nv' all I get is basic graphics. The modules and various bits'n'pieces for the 3d acceleration and advanced elements all load and report (via the log files) as being 'ok', but each time (and I have now rebuilt the kernel with the proprietory driver pack 5 times with various options selected and deselected) I fire it up with 'nvidia' in the xorg.conf file it fails with warnings about no instance for NVIDIA and the X-server failing with a 'Caught signal 11'. Also note that there are two versions of the proprietary driver available in Debian (at least in Sid); the package names for the older one end with -legacy. On top of this there's a new version of the driver out, but it doesn't seem to have hit Sid yet AFAIU it removes support for some older cards. Yep, I was aware of that thanks I haven't gone the legacy route because this is meant to be a 'new' motherboard and revised NVIDIA chipset (NF-6100-406)... so I presumed that going 'legacy' would not be much use. Sorry I can't help you out more than this... /M Thanks for at least responding Magnus I have been asking the same questions now for days of various forums ... and folks must be getting as sick of me asking as I am of trying to get this thing to work. I have read dozens of trails about this 'Signal 11' ... but so far not one of them has thrown any light on it. (The error codes listed for the xserver are about as obscure as they could be ... at least the version I downloaded was). I must have done something really dumn... but I just can't figure this one out. I suspect it has somethign to do with the warning about there being no instance for NVIDIA at 00:1:3 (or 00:0:13 ... quite why they keep alternating is also a mystery to me). Ah well, ... as written .. thanks for responding at least. Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
Ian Broadbent wrote: Question please... should the driver be 'nvidia' or 'nv', (if 'nvidia' - any suggestions as to what I am missing?) ... if it's should be 'nv' in any event .. then can someone help me find the settings for this to get the colours to be accurately displayed? It depends. IIRC 'nv' is the open source driver that comes with Xorg and 'nvidia' is the proprietary driver. Which one you use depends on what you want out of your card I suppose. Thanks Magnus, with the 'nv' all I get is basic graphics. The modules and various bits'n'pieces for the 3d acceleration and advanced elements all load and report (via the log files) as being 'ok', but each time (and I have now rebuilt the kernel with the proprietory driver pack 5 times with various options selected and deselected) I fire it up with 'nvidia' in the xorg.conf file it fails with warnings about no instance for NVIDIA and the X-server failing with a 'Caught signal 11'. Also note that there are two versions of the proprietary driver available in Debian (at least in Sid); the package names for the older one end with -legacy. On top of this there's a new version of the driver out, but it doesn't seem to have hit Sid yet AFAIU it removes support for some older cards. Yep, I was aware of that thanks I haven't gone the legacy route because this is meant to be a 'new' motherboard and revised NVIDIA chipset (NF-6100-406)... so I presumed that going 'legacy' would not be much use. Sorry I can't help you out more than this... /M Thanks for at least responding Magnus I have been asking the same questions now for days of various forums ... and folks must be getting as sick of me asking as I am of trying to get this thing to work. I have read dozens of trails about this 'Signal 11' ... but so far not one of them has thrown any light on it. (The error codes listed for the xserver are about as obscure as they could be ... at least the version I downloaded was). I must have done something really dumn... but I just can't figure this one out. I suspect it has somethign to do with the warning about there being no instance for NVIDIA at 00:1:3 (or 00:0:13 ... quite why they keep alternating is also a mystery to me). Try commenting the PCI bus line out of the xorg.conf and see if the driver can auto detect the card. Otherwise, look at lspci -v for details of the bus. Ah well, ... as written .. thanks for responding at least. Ian HTH Wackojacko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
On Tue, 2007-03-27 at 13:05 +0100, Wackojacko wrote: I have read dozens of trails about this 'Signal 11' ... but so far not one of them has thrown any light on it. (The error codes listed for the xserver are about as obscure as they could be ... at least the version I downloaded was). Try commenting the PCI bus line out of the xorg.conf and see if the driver can auto detect the card. Otherwise, look at lspci -v for details of the bus. HTH Wackojacko OK, now I am really into DEEP water I have run the lspci command ... but I'm not too sure what it is telling me on a quick scan down this lot (below) I only see the entry for VGA graphics controller. Would you not expect to see something that looked like GeForce6 or DX9.0 or similar? Sorry folks this is now at the 'bleeding-edge' of my limited knowledge Does this list below give anyone a clue? Ian brutus:~# lspci -v 00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1) Subsystem: ASRock Incorporation Unknown device 03ea Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [dc] HyperTransport: MSI Mapping 00:01.0 ISA bridge: nVidia Corporation MCP61 LPC Bridge (rev a2) Subsystem: ASRock Incorporation Unknown device 03e0 Flags: bus master, 66MHz, fast devsel, latency 0 00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2) Subsystem: ASRock Incorporation Unknown device 03eb Flags: 66MHz, fast devsel, IRQ 11 I/O ports at ec00 [size=64] I/O ports at 5000 [size=64] I/O ports at 6000 [size=64] Capabilities: [44] Power Management version 2 00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2) Subsystem: ASRock Incorporation Unknown device 03eb Flags: 66MHz, fast devsel 00:01.3 Co-processor: nVidia Corporation MCP61 SMU (rev a2) Subsystem: ASRock Incorporation Unknown device 03f4 Flags: 66MHz, fast devsel Memory at 8000 (32-bit, non-prefetchable) [disabled] [size=512K] 00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev a2) (prog-i f 10 [OHCI]) Subsystem: ASRock Incorporation Unknown device 03f1 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 225 Memory at d000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev a2) (prog-i f 20 [EHCI]) Subsystem: ASRock Incorporation Unknown device 03f2 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 209 Memory at dfffec00 (32-bit, non-prefetchable) [size=256] Capabilities: [44] Debug port Capabilities: [80] Power Management version 2 00:04.0 PCI bridge: nVidia Corporation MCP61 PCI bridge (rev a1) (prog-if 01 [Su btractive decode]) Flags: bus master, 66MHz, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 Capabilities: [b8] Subsystem: ASRock Incorporation Unknown device 03f3 Capabilities: [8c] HyperTransport: MSI Mapping 00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2) Subsystem: ASRock Incorporation Unknown device 0888 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 11 Memory at dfff8000 (32-bit, non-prefetchable) [size=16K] Capabilities: [44] Power Management version 2 Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/0 Enable- Capabilities: [6c] HyperTransport: MSI Mapping 00:06.0 IDE interface: nVidia Corporation MCP61 IDE (rev a2) (prog-if 8a [Master SecP PriP]) Subsystem: ASRock Incorporation Unknown device 03ec Flags: bus master, 66MHz, fast devsel, latency 0 I/O ports at ffa0 [size=16] Capabilities: [44] Power Management version 2 00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2) Subsystem: ASRock Incorporation Unknown device 03ef Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 50 Memory at dfffd000 (32-bit, non-prefetchable) [size=4K] I/O ports at e480 [size=8] Capabilities: [44] Power Management version 2 Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/3 Enable+ Capabilities: [6c] HyperTransport: MSI Mapping 00:08.0 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2) (prog-i f 85 [Master SecO PriO]) Subsystem: ASRock Incorporation Unknown device 03f6 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 233 I/O ports at e400 [size=8] I/O ports at e080 [size=4] I/O ports at e000 [size=8] I/O ports at dc00 [size=4] I/O ports at d880 [size=16] Memory at dfffc000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
Try commenting the PCI bus line out of the xorg.conf and see if the driver can auto detect the card. Otherwise, look at lspci -v for details of the bus. Oh and BTW. I had already tried that (and have just repeated it 'just in case') ... no effect whatsoever. same error-11 , same warnings. Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
Ian Broadbent wrote: Try commenting the PCI bus line out of the xorg.conf and see if the driver can auto detect the card. Otherwise, look at lspci -v for details of the bus. Oh and BTW. I had already tried that (and have just repeated it 'just in case') ... no effect whatsoever. same error-11 , same warnings. Ian OK, rename the current xorg file and rerun dpkg-reconfigure xserver-xorg and select nvidia, leave the PCI BUS empty and restart X. Also post the output of lspci -v |grep VGA (should show video controller) and /var/log/xorg if no luck. HTH Wackojacko PS no need to CC me I am subscribed to the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
On 27 Mar 2007, Ian Broadbent wrote: Question please... should the driver be 'nvidia' or 'nv', (if 'nvidia' - any suggestions as to what I am missing?) ... if it's should be 'nv' in any event .. then can someone help me find the settings for this to get the colours to be accurately displayed? [snip] Have you tried the fglrx packages (fglrx-driver and fglrx-kernel-src)? I installed these recently on a Thinkpad X61M and got 3d acceleration. I can't remember the exact steps I used (and the machine is not here at present to check) but it's explained in the docs and there is stuff on Google about doing it. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Magnus Therning wrote: On Sun, Mar 25, 2007 at 18:44:30 +0100, ieb wrote: Hello folks, [..] I have rebuilt the 2.6.18-4-amd64 with the NVIDIA components, have installed the nvidia-glx module, but whenever I let the etc/X11/xorg.conf build with the nvidia configuration tool it builds the 'conf' with a declaration for the driver to be nvidia, ...but ... X wont start then, ... warns me that there is no device for NVIDIA 00:1:3 (and/or if I manually change it to include 00:1:3) 00:13:0, and finally stops with a grumble about the kernel kicking out an error 11. BUT, ... if I change xorg.conf to use the driver nv (rather than nvidia) X (gdm) will start, does have the higher resolution set (1600x1200), but has a significant 'pink' colour cast. I can't find a configuration tool for the nvidia settings (such as Gamma etc). Question please... should the driver be 'nvidia' or 'nv', (if 'nvidia' - any suggestions as to what I am missing?) ... if it's should be 'nv' in any event .. then can someone help me find the settings for this to get the colours to be accurately displayed? It depends. IIRC 'nv' is the open source driver that comes with Xorg and 'nvidia' is the proprietary driver. Which one you use depends on what you want out of your card I suppose. Also note that there are two versions of the proprietary driver available in Debian (at least in Sid); the package names for the older one end with -legacy. On top of this there's a new version of the driver out, but it doesn't seem to have hit Sid yet AFAIU it removes support for some older cards. Sorry I can't help you out more than this... I can. The nvidia-glx package available in Sid (and I believe Etch as well) is the proprietary driver from Nvidia for the newer cards. However, it is an old version of it (8776). Nvidia's web site has two newer versions, both marked stable. 9746 and 9755. If one is willing to use proprietary drivers in their computer, and their card is still supported by Nvidia, then I would strongly recommend using the drivers from nvidia directly and not installing the 8776 drivers that are old. Unless 8776 is the last version that supports the video card you have, use the more recent versions of the driver. Keep in mind though, if you update your kernel, you'll need to reinstall the nvidia drivers. So keep the .run file you download from Nvidia handy unless you want to download the drivers again. Of course all of this is refers to someone who doesn't mind going against the dsfg and installing proprietary stuff. For people who free software is everything, then the nv drivers are the best you can get, and work fine for 2D things, but are quite sub-par in the 3D world specifically because Nvidia will not release the source code. Joe - -- Registerd Linux user #443289 at http://counter.li.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGCP+3iXBCVWpc5J4RAju6AKCh1IelCYYt9kfPq6dMGWe2Ibiy3gCfUYTp ctROkOZ9dIRBkj15tT1/yIk= =U3Lu -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anthony Campbell wrote: On 27 Mar 2007, Ian Broadbent wrote: Question please... should the driver be 'nvidia' or 'nv', (if 'nvidia' - any suggestions as to what I am missing?) ... if it's should be 'nv' in any event .. then can someone help me find the settings for this to get the colours to be accurately displayed? [snip] Have you tried the fglrx packages (fglrx-driver and fglrx-kernel-src)? I installed these recently on a Thinkpad X61M and got 3d acceleration. I can't remember the exact steps I used (and the machine is not here at present to check) but it's explained in the docs and there is stuff on Google about doing it. Anthony flgrx is for ati cards. OP has nvidia. Ian, don't do that. Ian, It sounds to me like your xorg.conf is still messed up. Can you post that too? Just the relevant Device and Screen sections should be enough. But you can put the whole thing here too. Then we should get a pretty good idea what is going on. - -- Registerd Linux user #443289 at http://counter.li.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGCQGgiXBCVWpc5J4RAismAJ4k6celWxvDeVL7iES/6kVtdBnHjQCcDPww Kr/U0j3yyKJbrkzQKJWnecY= =alli -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joe Hart wrote: Anthony Campbell wrote: On 27 Mar 2007, Ian Broadbent wrote: Question please... should the driver be 'nvidia' or 'nv', (if 'nvidia' - any suggestions as to what I am missing?) ... if it's should be 'nv' in any event .. then can someone help me find the settings for this to get the colours to be accurately displayed? [snip] Have you tried the fglrx packages (fglrx-driver and fglrx-kernel-src)? I installed these recently on a Thinkpad X61M and got 3d acceleration. I can't remember the exact steps I used (and the machine is not here at present to check) but it's explained in the docs and there is stuff on Google about doing it. Anthony flgrx is for ati cards. OP has nvidia. Ian, don't do that. Ian, It sounds to me like your xorg.conf is still messed up. Can you post that too? Just the relevant Device and Screen sections should be enough. But you can put the whole thing here too. Then we should get a pretty good idea what is going on. It would help if I slow down on my typing. I meant fglrx is for ati. Joe - -- Registerd Linux user #443289 at http://counter.li.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGCQIqiXBCVWpc5J4RAh0ZAJwPLOD0rbxglcSRnUf0Vzz/99zzsACePCIw xwB/3VOnB9UrngGFs0+2SJI= =L2G5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
Ian, It sounds to me like your xorg.conf is still messed up. Can you post that too? Just the relevant Device and Screen sections should be enough. But you can put the whole thing here too. Then we should get a pretty good idea what is going on. Will do... but just now I have to go and get some work done... I only meant to spend 15-20 minutes on this this morning... and have just noticed the time oops I have meetings soon and I haven't even prepared for them yet. more later... thanks folks. Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
On 27 Mar 2007, Joe Hart wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anthony Campbell wrote: On 27 Mar 2007, Ian Broadbent wrote: Question please... should the driver be 'nvidia' or 'nv', (if 'nvidia' - any suggestions as to what I am missing?) ... if it's should be 'nv' in any event .. then can someone help me find the settings for this to get the colours to be accurately displayed? [snip] Have you tried the fglrx packages (fglrx-driver and fglrx-kernel-src)? I installed these recently on a Thinkpad X61M and got 3d acceleration. I can't remember the exact steps I used (and the machine is not here at present to check) but it's explained in the docs and there is stuff on Google about doing it. Anthony flgrx is for ati cards. OP has nvidia. Ian, don't do that. Sorry - yes, of course. Brain not working properly this morning. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
Ian Broadbent wrote: On Tue, 2007-03-27 at 13:39 +0100, Wackojacko wrote: Ian Broadbent wrote: Try commenting the PCI bus line out of the xorg.conf and see if the driver can auto detect the card. Otherwise, look at lspci -v for details of the bus. Oh and BTW. I had already tried that (and have just repeated it 'just in case') ... no effect whatsoever. same error-11 , same warnings. Ian OK, rename the current xorg file and rerun dpkg-reconfigure xserver-xorg and select nvidia, leave the PCI BUS empty and restart X. Done.Same warnings (only this time for PCI 00:1:3 rather than 00:13:0) Same error 11. Also post the output of lspci -v |grep VGA (should show video controller) and /var/log/xorg if no luck. return from root call to lspci. brutus:~# lspci -v |grep VGA 00:0d.0 VGA compatible controller: nVidia Corporation Unknown device 03d1 (rev a2) (prog-if 00 [VGA]) IIRC, this suggests the bus id is 00:0d.0. Also try installing the pciutils package and running update-pciids as root. Then rerun the lspci command. which looks very similar to the entry in the longer lspci report. The log file(s) are attached. Xorg.0.log.old is the one from when it fails using 'nvidia' Xorg.0.log is the most recent after I reset the xorg.conf to use 'nv' I presume that the fonts having warnings is just that warnings as it appears to find alternatives later. ...as for the rest, I don't know what I am missing, ...perhaps i am too hooked up on the PCI warning and missing something more obvious. Ian snip xorg nv log (II) Primary Device is: PCI 00:0d:0 (WW) NV: No matching Device section for instance (BusID PCI:0:1:3) found Again suggests different PCI Bus ID as above. snip xorg nvidia log (II) Initializing extension GLX Backtrace: 0: /usr/bin/X(xf86SigHandler+0x6d) [0x4802ed] 1: /lib/libc.so.6 [0x2ac51f460110] 2: /lib/libc.so.6(__ctype_tolower_loc+0x25) [0x2ac51f45a2c5] 3: /usr/bin/X(xf86nameCompare+0xfe) [0x4a4cde] 4: /usr/bin/X(InitInput+0x103) [0x45ea23] 5: /usr/bin/X(main+0x337) [0x430e57] 6: /lib/libc.so.6(__libc_start_main+0xda) [0x2ac51f44d4ca] 7: /usr/bin/X(FontFileCompleteXLFD+0x9a) [0x43026a] Fatal server error: Caught signal 11. Server aborting Ah! Seems to be a problem with the GLX extension, are you sure the nvidia-glx package matches the source from which you compiled the module? I have googled this error (last line of backtrace) and it appears others are having problems and it does seem to be the nvidia-glx package causing the problem. Bug#415878 (1) seems similar to your problem and suggests commenting the Load glx from xorg. Might want to try this and see if it loads (albeit without glx acceleration) and add to the bug report if necessary. HTH Wackojacko (1) http://people.debian.org/~terpstra/thread/20070324.205818.d7d3b216.en.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
snip xorg nvidia log (II) Initializing extension GLX Backtrace: 0: /usr/bin/X(xf86SigHandler+0x6d) [0x4802ed] 1: /lib/libc.so.6 [0x2ac51f460110] 2: /lib/libc.so.6(__ctype_tolower_loc+0x25) [0x2ac51f45a2c5] 3: /usr/bin/X(xf86nameCompare+0xfe) [0x4a4cde] 4: /usr/bin/X(InitInput+0x103) [0x45ea23] 5: /usr/bin/X(main+0x337) [0x430e57] 6: /lib/libc.so.6(__libc_start_main+0xda) [0x2ac51f44d4ca] 7: /usr/bin/X(FontFileCompleteXLFD+0x9a) [0x43026a] Fatal server error: Caught signal 11. Server aborting Ah! Seems to be a problem with the GLX extension, are you sure the nvidia-glx package matches the source from which you compiled the module? I have googled this error (last line of backtrace) and it appears others are having problems and it does seem to be the nvidia-glx package causing the problem. Bug#415878 (1) seems similar to your problem and suggests commenting the Load glx from xorg. Might want to try this and see if it loads (albeit without glx acceleration) and add to the bug report if necessary. HTH Wackojacko My thanks to Anthony, Joe, Magnus and especially to Jacko (can't bring myself to write 'Wackojacko') You were spot on... remove the Load GLX from xorg.conf and set the driver back to 'nvidia' and it started up perfectly ...well .'almost'. As you may recall from earlier posts I had a heavy pink cast over the KDE desktop it's still there, but now at least it goes away as soon as I start the nvidia-settings programme unfortunately, it returns when I switch to Gnome but as don't usually switch between display-managers it shouldn't be a major problem. Can I ask (and learn) then about the backtrace reporting. I presume than the backtrace always then applies to the last element on the log prior to it? I didn't know that (if correct).. so although I read the backtrace I thought it was telling me that step seven in the trace was the root problem (something to do with the fonts)... rather than the actual bugbear being the last thing in the log above the point where the backtrace begins. Is my assumption correct? Is it always so? If yes... then todays been helpful on two counts. So ... final question (if you don't mind) how do I add this to the bug report as you suggested? Sorry, bug reporting is also new to me. Thanks again folks... it really is very much appreciated Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
On Tue, Mar 27, 2007 at 11:23:14AM +0100, Ian Broadbent wrote: OK, now I am really into DEEP water I have run the lspci command ... but I'm not too sure what it is telling me on a quick scan down this lot (below) I only see the entry for VGA graphics controller. Would you not expect to see something that looked like GeForce6 or DX9.0 or similar? Sorry folks this is now at the 'bleeding-edge' of my limited knowledge Does this list below give anyone a clue? brutus:~# lspci -v 00:0d.0 VGA compatible controller: nVidia Corporation Unknown device 03d1 (rev a 2) (prog-if 00 [VGA]) Subsystem: ASRock Incorporation Unknown device 03d1 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10 Memory at de00 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at dd00 (64-bit, non-prefetchable) [size=16M] Expansion ROM at dffc [disabled] [size=128K] Capabilities: [48] Power Management version 2 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ You could of snipped the unnecessary bits. Looks like recent h/w. Try running, as root, the following: update-pciids from a command line while you are online. Then try as root lspci | grep VGA -- Chris. == Don't forget to check that your /etc/apt/sources.lst entries point to etch and not testing, otherwise you may end up with a broken system once etch goes stable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
You could of snipped the unnecessary bits. Chris. errr.. that might be good advice Chris BUT, it kinda ASSumes that I knew what the 'unnecessary bits' were ... doesn't it? If I'd known that ... then I would have been able to spot the error instantly (as others did when they saw the full detailed listing). Thanks anyway. As written previously it's now at least resolved in that we know what the problem is/was and I have NVIDIA running (crippled.. but running). Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
Hello folks, I'm still puzzling with my build of Etch on this new machine I've solved the GRUB error 16 and error 18 problems, by disabling the SMART options in the BIOS and stopping the appropriate services for smartmon. Everything on that front now appears to be stable ...and I don't appear to have a faulty disc-controller after all. But I am still puzzling over the NVIDIA and sound modules. My latest 'problem' is with NVIDIA. (I'll worry about why ALSA isn't working next). I have rebuilt the 2.6.18-4-amd64 with the NVIDIA components, have installed the nvidia-glx module, but whenever I let the etc/X11/xorg.conf build with the nvidia configuration tool it builds the 'conf' with a declaration for the driver to be nvidia, ...but ... X wont start then, ... warns me that there is no device for NVIDIA 00:1:3 (and/or if I manually change it to include 00:1:3) 00:13:0, and finally stops with a grumble about the kernel kicking out an error 11. BUT, ... if I change xorg.conf to use the driver nv (rather than nvidia) X (gdm) will start, does have the higher resolution set (1600x1200), but has a significant 'pink' colour cast. I can't find a configuration tool for the nvidia settings (such as Gamma etc). Question please... should the driver be 'nvidia' or 'nv', (if 'nvidia' - any suggestions as to what I am missing?) ... if it's should be 'nv' in any event .. then can someone help me find the settings for this to get the colours to be accurately displayed? Thanks again folks, Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems with GRUB and SATA
I asked last week about getting Debian to run on my new box. Joe Hart pointed me in the direction of ETCH rather than the SID I was trying to use. Everything worked fin until Saturday switched on and it failed with an Error 18 at the GRUB. It took me 8 attempts over the weekend to reinstall to system it kept failing at the 'Installing Software' stage and wouldn't proceed. I downloaded the latest installer yesterday- - burnt another dic and tried again it all seemed to go fine and the system was up and running again. I have just switched on the machine - it booted OK - got to Gnome desktop... and the whole thing froze (reminiscent of the bad old Windoze days) ... switched it off (couldn't shutdown ... wouldn't take any inputs) switched back on and I'm back with my Error 18 during GRUB again Any sage advice please. I will remind folks that I am not 'that' technical, so please be gentle with me with I ask stpid questions. It seems as if I have a hard disk problem but I even went and bought a new drive at the weekend so this has happened to two separate SATA drives. A kinda obvious question but is anyone else having problems with SATA and ETCH? I understand that Error 18 is a read attempt beyond 8GB on older machines. but this is a brand new Motherboard, AND in any event I always have BOOT in a separate 50meg partition at the front of the disk. Advice / comments please, Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with GRUB and SATA
ieb wrote: It took me 8 attempts over the weekend to reinstall to system it kept failing at the 'Installing Software' stage and wouldn't proceed. I downloaded the latest installer yesterday- - burnt another dic and tried again it all seemed to go fine and the system was up and running again. I saw a similar problem like this on a recent install; turns out one of the packages was looking for awk, but mawk was installed instead. We created a symlink to connect the two, and then the process got past that point. We ran into other problems, so eventually we just scrapped installing from the Etch installer, and did a Sarge install and then dist-upgraded from there. I should have filed a bug report, but failed to do so at the time, and now don't remember the details and no longer have access even to that machine to check the logs (assuming they have the info). I have just switched on the machine - it booted OK - got to Gnome desktop... and the whole thing froze (reminiscent of the bad old Windoze days) ... switched it off (couldn't shutdown ... wouldn't take any inputs) switched back on and I'm back with my Error 18 during GRUB again But it sounds like you've got different issues, so you can probably never mind my comments above. I believe I'd boot off a LiveCD and run fsck on your hard drive. What file system format are you using on your hard drive? (ext3, jfs, etc) -- Kent West http://kentwest.blogspot.com http://kentwest.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with GRUB and SATA
On Thu, Mar 22, 2007 at 01:27:07PM +, ieb wrote: I asked last week about getting Debian to run on my new box. [snip: running Etch] Everything worked fin until Saturday switched on and it failed with an Error 18 at the GRUB. It took me 8 attempts over the weekend to reinstall to system it kept failing at the 'Installing Software' stage and wouldn't proceed. I downloaded the latest installer yesterday- - burnt another dic and tried again it all seemed to go fine and the system was up and running again. I have just switched on the machine - it booted OK - got to Gnome desktop... and the whole thing froze (reminiscent of the bad old Windoze days) ... switched it off (couldn't shutdown ... wouldn't take any inputs) switched back on and I'm back with my Error 18 during GRUB again Any sage advice please. I will remind folks that I am not 'that' technical, so please be gentle with me with I ask stpid questions. It seems as if I have a hard disk problem but I even went and bought a new drive at the weekend so this has happened to two separate SATA drives. A kinda obvious question but is anyone else having problems with SATA and ETCH? I understand that Error 18 is a read attempt beyond 8GB on older machines. but this is a brand new Motherboard, AND in any event I always have BOOT in a separate 50meg partition at the front of the disk. Advice / comments please, Hello Ian I read some great advice yesterday in one of the *BSD books talking about what to do when a drive failure happens: PANIC: you will anyway, so just PANIC away from your computer so you don't make things worse. Then calm down. First, the reason I use Etch is _because_ I have SATA drives. I don't know what a desktop (e.g. Gnome) may be trying to do. I don't use one. Instead, when I want X, I use startx from a shell. Since you're running Etch, is it up-to-date? That is, have you run aptitude or apt-get update/upgrade? --- Since this is a booting issue, don't let it boot to runlevel 2. What you want is single-user mode, accessed by the 'single' kernel parameter. Boot the computer. When you get the grub menu, edit the kernel line and add 'single', then boot the entry. That is, unless you already have a single-user or maintenance mode. If you don't get Grub, boot the installer in rescue mode and reinstall grub. Once you get to a command shell in single-user mode, edit the grub menu.lst file to give you an added line for single-user mode if it isn't there already. When you shutdown, use the -F command to force a filesystem check on next boot. If after booting grub you get errors on the screen, write them down so you can send them to us. Then reboot but instead of using 'single', use 'init=/bin/sh' to bypass all the init stuff and just get a shell to work in. Once you get a functioning system again, install smartmon (or whatever its called) to monitor the S.M.A.R.T. status of your drives. You shouldn't have to reinstall unless, after sharing the errors here, there is no alternative. For this to be the case, something very serious must have happened. Good luck, Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with GRUB and SATA
On Thu, Mar 22, 2007 at 01:27:07PM +, ieb wrote: I asked last week about getting Debian to run on my new box. [...] I have just switched on the machine - it booted OK - got to Gnome desktop... and the whole thing froze (reminiscent of the bad old Windoze days) ... switched it off (couldn't shutdown ... wouldn't take any inputs) switched back on and I'm back with my Error 18 during GRUB again couple things I've found. grub error 18 could be caused by problems with the BIOS hd settings. try turning off block mode in the bios and/or using a manual disk setup instead of autodetect. [0] the other possibility is that you've just got some bad hardware (disk controller maybe). The intermittent nature of the problem leads me to suspect hardware more than software and the fact that a new disk didn't fix it points to something farther up the chain: cables, disk-controller etc. A [0] http://www.linuxforums.org/forum/debian-linux-help/52256-first-time-trying-linux-grub-error-18-a.html signature.asc Description: Digital signature
Re: 30-minutes with scripts [was Re: Fixing boot problems with grub]
William Ballard wrote: On Sun, Nov 28, 2004 at 07:57:20AM -0600, Hugo Vanwoerkom wrote: For now I just reinstalled the OS. It takes me 30 minutes with scripts. But I looked like a tool having to do that. What does 30 minutes with scripts mean? I talked about this a year ago. Several people told me with chroot and partimage, I could restore a clean OS image in a couple minutes, which is basically what I do with XP, but I keep a partial mirror of the sid debs I use and point apt to that. My 30 minutes is: (1) Install Sarge, wipe the disk, use one giant partition for everything. (10 minutes?) (2) Install nothing during Sarge. (3) Mount my apt repository, point apt to it. (4) aptitude install everything in that repository. (20 minutes?) (5) Reboot. (6) Manually run a script which does everything else I need to do to the system. (7) Log in as non-user, run a script which sets up the profile. Probably takes closer to 40 minutes, but I do this process every couple months. I treat home as transient; I treat the whole system as transient. I know you all probably find this process shlocky but it works for me, because apt is so nice. With XP I use partimage. Interesting. I have a similar script. The ultimate reason is to get a clean install, meaning, you get everything that you need and nothing more. I do it with a script that only presumes an existing Sarge. To finetune it I need the Sarge iso's because otherwise it takes too long to install everything and I am on a dialup line, with no DSL or cable in sight. This is the reason I am about to purchase the 14 Sarge CD's: it is too hard chasing the jigdo-lite templates: too much. Now I have a broken package problem with only 6. And indeed it takes about 40 minutes, may be less, I need to compile the kernel for the Ruby multi-seat Linux patch. Then there are some programs for which there are no Debian packages. This project has an additional benefit: you find out what exactly you are dependent upon in terms of data resources, in case of disk failure, which happened a while ago. H. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fixing boot problems with grub
William Ballard wrote: Whenever Lilo used to mess up with Woody, I'd: 1) Boot from the Woody CD. 2) Mount my existing single Debian partition as / 3) Execute a shell 4) Make sure /vmlinuz and /vmlinuz-old pointed to the right places in /boot. 5) Exit the shell. 6) Run make system bootable. which would Lilo it up. Today I horked my Sarge Grub install, booted from the Sarge CD, screwed up my paritions when I tried to do (2) (because creating, formatting, and mounting partitions is all connected), verified 4) was correct, couldn't figure out how to do 6), and running upgrade-grub from within a chroot didn't work. When I entered partition my disks, formatting my swap part was already highlighed. I picked my big Debian ReiserFS part and told it not to format it, but to mount it as /, and clicked Finish. D-I told me it was going to make changes to my partition table, even though I didn't tell it to change any partitions. Somehow when it was done my swap part was gone. In Sarge D-I, how can I just mount something as / without changing part tables or formatting anything, and run the make system bootable step to recover from botched grub? Or how can I do it from within a chroot. I don't usually keep a second install of Debian around to chroot from, so I'd have to chroot from the Sarge emergency shell or (less desirably) a Knoppix CD. For now I just reinstalled the OS. It takes me 30 minutes with scripts. But I looked like a tool having to do that. What does 30 minutes with scripts mean? I guess you ended up with a partition that can't be booted by either Lilo or Grub. So I am still a Lilo fan, I modified Lilo's mkrescue to create an iso that is a little more descriptive than linux and I keep that around, *always* when using d-i. Because it does grub natively I just let it do grub and use the lilo-rescue to set lilo straight again. My take on grub vs. lilo from a while ago was that if lilo does me good, keep it. H. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fixing boot problems with grub
Hugo Vanwoerkom wrote: William Ballard wrote: Whenever Lilo used to mess up with Woody, I'd: 1) Boot from the Woody CD. 2) Mount my existing single Debian partition as / 3) Execute a shell 4) Make sure /vmlinuz and /vmlinuz-old pointed to the right places in /boot. 5) Exit the shell. 6) Run make system bootable. which would Lilo it up. Today I horked my Sarge Grub install, booted from the Sarge CD, screwed up my paritions when I tried to do (2) (because creating, formatting, and mounting partitions is all connected), verified 4) was correct, couldn't figure out how to do 6), and running upgrade-grub from within a chroot didn't work. When I entered partition my disks, formatting my swap part was already highlighed. I picked my big Debian ReiserFS part and told it not to format it, but to mount it as /, and clicked Finish. D-I told me it was going to make changes to my partition table, even though I didn't tell it to change any partitions. Somehow when it was done my swap part was gone. In Sarge D-I, how can I just mount something as / without changing part tables or formatting anything, and run the make system bootable step to recover from botched grub? Or how can I do it from within a chroot. I don't usually keep a second install of Debian around to chroot from, so I'd have to chroot from the Sarge emergency shell or (less desirably) a Knoppix CD. For now I just reinstalled the OS. It takes me 30 minutes with scripts. But I looked like a tool having to do that. What does 30 minutes with scripts mean? I guess you ended up with a partition that can't be booted by either Lilo or Grub. So I am still a Lilo fan, I modified Lilo's mkrescue to create an iso that is a little more descriptive than linux and I keep that around, *always* when using d-i. Because it does grub natively I just let it do grub and use the lilo-rescue to set lilo straight again. My take on grub vs. lilo from a while ago was that if lilo does me good, keep it. H. I'm trying to understand Grub as well. I finally found out how to make a boot disk from the FAQ (see link). The Grub project calls this the legacy version (0.9x). http://www.gnu.org/software/grub/grub-legacy-faq.en.html The relavent QA is: 4. How to create a GRUB boot floppy with the menu interface? 1. Create a filesystem in your floppy disk (e.g. mke2fs /dev/fd0). 2. Mount the floppy on somewhere, say, /mnt. 3. Copy the GRUB images to the directory /mnt/boot/grub. Only stage1, stage2 and menu.lst are necessary. You may not copy *stage1_5. 4. Unmount the floppy. 5. Run the following commands (note that the executable grub may reside in a different directory in your system, for example, /usr/sbin): /sbin/grub --batch --device-map=/dev/null EOF device (fd0) /dev/fd0 root (fd0) setup (fd0) quit EOF I tried the result, and it worked. My take is that this won't fix anything that breaks, and there must be a working Grub install on the HD to get the files from. Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
30-minutes with scripts [was Re: Fixing boot problems with grub]
On Sun, Nov 28, 2004 at 07:57:20AM -0600, Hugo Vanwoerkom wrote: For now I just reinstalled the OS. It takes me 30 minutes with scripts. But I looked like a tool having to do that. What does 30 minutes with scripts mean? I talked about this a year ago. Several people told me with chroot and partimage, I could restore a clean OS image in a couple minutes, which is basically what I do with XP, but I keep a partial mirror of the sid debs I use and point apt to that. My 30 minutes is: (1) Install Sarge, wipe the disk, use one giant partition for everything. (10 minutes?) (2) Install nothing during Sarge. (3) Mount my apt repository, point apt to it. (4) aptitude install everything in that repository. (20 minutes?) (5) Reboot. (6) Manually run a script which does everything else I need to do to the system. (7) Log in as non-user, run a script which sets up the profile. Probably takes closer to 40 minutes, but I do this process every couple months. I treat home as transient; I treat the whole system as transient. I know you all probably find this process shlocky but it works for me, because apt is so nice. With XP I use partimage. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fixing boot problems with grub
On Sun, Nov 28, 2004 at 03:55:27PM -0600, Jim Hall wrote: I'm trying to understand Grub as well. I finally found out how to make a boot disk from the FAQ (see link). The Grub project calls this the legacy version (0.9x). http://www.gnu.org/software/grub/grub-legacy-faq.en.html The relavent QA is: 4. How to create a GRUB boot floppy with the menu interface? Thanks for this pointer. I'll try to follow this and Greg Fokkert's advice about grub-install within a chroot and try to educate myself about how to fix broken grubs. I was pretty slick at lilo. The other thing I'm stuck at in Sarge is Exim4. First thing I do in Sarge is downgrade to Exim3. I'll ask about that in another thread. Sarge has a bit of a learning curve for upgraders. But what in Linux doesn't? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fixing boot problems with grub
Whenever Lilo used to mess up with Woody, I'd: 1) Boot from the Woody CD. 2) Mount my existing single Debian partition as / 3) Execute a shell 4) Make sure /vmlinuz and /vmlinuz-old pointed to the right places in /boot. 5) Exit the shell. 6) Run make system bootable. which would Lilo it up. Today I horked my Sarge Grub install, booted from the Sarge CD, screwed up my paritions when I tried to do (2) (because creating, formatting, and mounting partitions is all connected), verified 4) was correct, couldn't figure out how to do 6), and running upgrade-grub from within a chroot didn't work. When I entered partition my disks, formatting my swap part was already highlighed. I picked my big Debian ReiserFS part and told it not to format it, but to mount it as /, and clicked Finish. D-I told me it was going to make changes to my partition table, even though I didn't tell it to change any partitions. Somehow when it was done my swap part was gone. In Sarge D-I, how can I just mount something as / without changing part tables or formatting anything, and run the make system bootable step to recover from botched grub? Or how can I do it from within a chroot. I don't usually keep a second install of Debian around to chroot from, so I'd have to chroot from the Sarge emergency shell or (less desirably) a Knoppix CD. For now I just reinstalled the OS. It takes me 30 minutes with scripts. But I looked like a tool having to do that. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fixing boot problems with grub
On Sun, 2004-11-28 at 00:24 -0500, William Ballard wrote: Whenever Lilo used to mess up with Woody, I'd: 1) Boot from the Woody CD. 2) Mount my existing single Debian partition as / 3) Execute a shell 4) Make sure /vmlinuz and /vmlinuz-old pointed to the right places in /boot. 5) Exit the shell. 6) Run make system bootable. which would Lilo it up. Today I horked my Sarge Grub install, booted from the Sarge CD, screwed up my paritions when I tried to do (2) (because creating, formatting, and mounting partitions is all connected), verified 4) was correct, couldn't figure out how to do 6), and running upgrade-grub from within a chroot didn't work. When I entered partition my disks, formatting my swap part was already highlighed. I picked my big Debian ReiserFS part and told it not to format it, but to mount it as /, and clicked Finish. D-I told me it was going to make changes to my partition table, even though I didn't tell it to change any partitions. Somehow when it was done my swap part was gone. In Sarge D-I, how can I just mount something as / without changing part tables or formatting anything, and run the make system bootable step to recover from botched grub? Or how can I do it from within a chroot. I don't usually keep a second install of Debian around to chroot from, so I'd have to chroot from the Sarge emergency shell or (less desirably) a Knoppix CD. For now I just reinstalled the OS. It takes me 30 minutes with scripts. But I looked like a tool having to do that. Use grub-install. And given the root FS for the chroot, Where you have / and /boot properly mounted on /targ and /targ/boot. Without a chroot. /targ/sbin/grub-install --root-directory=/targ /dev/hda Then edit a bare /targ/boot/grub/menu.lst. Reboot. Or do the same with a Knoppix/Gnoppix/liveCD with grub-install on it. -- greg, [EMAIL PROTECTED] The technology that is Stronger, better, faster: Linux signature.asc Description: This is a digitally signed message part
boot problems with grub
I have been using debian with kernel 2.4.25 (I tried 2.6.8 but it had issues with my onboard sound and so I stuck with 2.4.25). My problem is the following: Ileft emule runningovernight (which was never a problem before). I found that emule had failed and shut down my computer. When I turned it on emule would not work. But more importantly, my system was slow. Eventually KDE 3.0 decided to freeze on me. So I manually shutdown and restarted. But since then I haven't been able to boot. Grub returns error 18 at stage 1.5. I tried booting with a Knoppix 3.0 cd to check my harddrive. However, Knoppix tells me that ext3 fs cannot be viewed (the linux harddrive uses ext3). I have been told that Knoppix should recognize ext3, so does that failure tell me that my hd is screwed and needs formatting? Or is there a way to reinstallmy boot loader without rewriting my partition table? (boot loader contains several linux kernels and windows, if that makes a difference). Can anyone help me? - Jonathan Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages!
Re: boot problems with grub
On Fri, Oct 01, 2004 at 01:50:57PM -0700, Jonathan wrote: I have been using debian with kernel 2.4.25 (I tried 2.6.8 but it had issues with my onboard sound and so I stuck with 2.4.25). My problem is the following: I left emule running overnight (which was never a problem before). I found that emule had failed and shut down my computer. When I turned it on emule would not work. But more importantly, my system was slow. Eventually KDE 3.0 decided to freeze on me. So I manually shutdown and restarted. But since then I haven't been able to boot. Grub returns error 18 at stage 1.5. I tried booting with a Knoppix 3.0 cd to check my harddrive. However, Knoppix tells me that ext3 fs cannot be viewed (the linux harddrive uses ext3). I have been told that Knoppix should recognize ext3, so does that failure tell me that my hd is screwed and needs formatting? Or is there a way to reinstall my boot loader without rewriting my partition table? (boot loader contains several linux kernels and windows, if that makes a difference). If the partition can't be viewed, your problem is probably more than the boot loader. Have you tried to fsck that partition? Have you looked at the partition table with fdisk -l ? According to info grub, error 18 is Selected cylinder exceeds maximum supported by BIOS. Do you have an old PC with a newer hard drive, such that the BIOS can't see the entire drive? Do you (or did you) have a separate boot partition? -- System Events =-=-=-=-=-=-= Sep 16 03:31:11 don kernel: lp0 on fire -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot problems with grub
On Fri, Oct 01, 2004 at 01:50:57PM -0700, Jonathan wrote: I have been using debian with kernel 2.4.25 (I tried 2.6.8 but it had issues with my onboard sound and so I stuck with 2.4.25). My problem is the following: I left emule running overnight (which was never a problem before). I found that emule had failed and shut down my computer. When I turned it on emule would not work. But more importantly, my system was slow. Eventually KDE 3.0 decided to freeze on me. So I manually shutdown and restarted. But since then I haven't been able to boot. Grub returns error 18 at stage 1.5. I tried booting with a Knoppix 3.0 cd to check my harddrive. However, Knoppix tells me that ext3 fs cannot be viewed (the linux harddrive uses ext3). I have been told that Knoppix should recognize ext3, so does that failure tell me that my hd is screwed and needs formatting? Or is there a way to reinstall my boot loader without rewriting my partition table? (boot loader contains several linux kernels and windows, if that makes a difference). If the partition can't be viewed, your problem is probably more than the boot loader. Have you tried to fsck that partition? Have you looked at the partition table with fdisk -l ? According to info grub, error 18 is Selected cylinder exceeds maximum supported by BIOS. Do you have an old PC with a newer hard drive, such that the BIOS can't see the entire drive? Do you (or did you) have a separate boot partition? My computer is a late 90's Compaq Presario, but I've been running debian on my PC for several months. So I don't think that is an issue. I can only boot using a knoppix cd so everything is readonly. I ran fdisk -l and both /dev/hda and /dev/hdb cannot be opened. However, hda isn't effected. I can mount it without a problem. hdb is the disk with linux and the where the problem lives. fsck won't work. To the other reply, I can't boot into anything other than knoppix. linux 2 and starting grub does not do anything, but thanks for trying! - Jonathan ___ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Booting Problems with grub
Dear all, booting Debianized kernels with grub does not create any troubles. However, when I try to build a kernel myself optimized for my laptop, the kernel panics because it believes not to be able to mount root. Except for the initrd, I exactly copied the configuration settings. Of course, the correct IDE-drivers for accessing the disk as well as the filesystems are statically linked into the kernel. Any idea? wbr, Lukas -- Lukas Ruf | Wanna know anything about raw | http://www.lpr.ch | IP? - http://www.rawip.org | eMail Style Guide: http://www.rawip.org/style.html| -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Booting Problems with grub
* Lukas Ruf [EMAIL PROTECTED] [031202 16:38]: Except for the initrd, I exactly copied the configuration settings. What do you mean except for the initrd? Are you building from debian kernel sources (which are patched for initrd)? How are you building your initrd, and how are you linking to it? Are you issuing the GRUB command initrd /filename? -- Lance Simmons signature.asc Description: Digital signature
