Grub bad partition pointing after kernel upgrade
Hi, everytime I upgrade kernel (debian unstable), grub is automatically updated. But grub points to the $HOME partition and not '/' partition. And so I must modify menu.lst file manually. Is it a bug or a bad setting? example: If my kernel is in /dev/hda1 and my $HOME in /dev/hda3, after upgrade grub points for kernel image to /dev/hda3 instead of /dev/hda1 Thanks, Giulio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub bad partition pointing after kernel upgrade
On Tue, Aug 08, 2006 at 09:40:44AM +0200, antonio giulio wrote: example: If my kernel is in /dev/hda1 and my $HOME in /dev/hda3, after upgrade grub points for kernel image to /dev/hda3 instead of /dev/hda1 Can you post an excerpt from your menu.lst to show what you mean? There are defaults for some grub options earlier in the file eg root device, options etc. Check that those are set correctly for your setup. They are copied to the other menu items when that file is updated by adding/removing a kernel. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub bad partition pointing after kernel upgrade
Am Dienstag, 8. August 2006 09:40 schrieb antonio giulio: Hi, everytime I upgrade kernel (debian unstable), grub is automatically updated. But grub points to the $HOME partition and not '/' partition. And so I must modify menu.lst file manually. Is it a bug or a bad setting? example: If my kernel is in /dev/hda1 and my $HOME in /dev/hda3, after upgrade grub points for kernel image to /dev/hda3 instead of /dev/hda1 Thanks, Giulio Hi Gulio, should not be normal. Please check in /boot/grub/menul.lst the line # kopt=root=/dev/hda6 ro It is in the section with the many hashes. Do not remove the hashes (suppose, you know this). If you enter here the correct partition for root, an upgrade should be o.k. next time. Otherwise reinstall grub again and then check the mentioned line again. This should work. Best regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Grub gone from unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anyone know why grub has been removed from unstable and lilo brought back? I upgraded a test install from testing to unstable two days back and found that grub gets removed; lilo gets installed but no lilo-conf is generated. The system still boots off the old menu.lst, though. Sam - -- Sam Varghese http://www.gnubies.com Experiences are savings which a miser puts aside. Wisdom is an inheritance which a wastrel cannot exhaust. My PGP key: http://www.gnubies.com/encryption/sign.txt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE2E5pZyXhknb+33gRArNwAJ4gEareMTyp7XuT7LAhpOLjbFuqkQCeMDF6 XqkiwIwh10pKoD8nq8D8M4E= =V8pj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub gone from unstable
Sam Varghese wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anyone know why grub has been removed from unstable and lilo brought back? I upgraded a test install from testing to unstable two days back and found that grub gets removed; lilo gets installed but no lilo-conf is generated. The system still boots off the old menu.lst, though. Grub is still sat happily in Unstable - and as it happens, uses the same version as Testing. Sounds more like a related problem, or possibly aptitude being overly smart -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Grub: Installing the MBR
Hi All Thanks for Grub tips for Giulio, I needed some of that information too. I'm in the process of moving my AMD64 machine from the IDE drives over to SATA. I've copied all the partitions over, and the last step is to installed the MBR so grub will boot with just the SATA drive installed. What's the best way of intalling the MBR on /dev/sda0? I want to pull the old IDE disks for use in other projects. Steve signature.asc Description: This is a digitally signed message part
Re: amd64 situation in Mirrors.masterlist
Joey Hess wrote: A quick look at what Mirrors.masterlist says about mirrors carrying amd64 finds a lot of probably wrong information: * 154 mirrors listed as mirroring !amd64, but having all other arches. This is probably wrong for most of them ... it's definitly wrong for the couple I spot-checked. * 69 mirrors listed as mirroring only amd64 and one or two other arches. Probably correct for most of them. * 65 mirrors listed as mirroring some list of archirectures that does not include amd64. Such as mirroring only i386. Probably right for many and wrong for many others. Would someone like to go through and fix all this in Mirrors.masterlist? Bonus points if you fix the archive lists to be accurate for all other arches too. Super bonus points if you don't do it by hand like I did, last time I did it. :-) (In case you're not familier with Mirrors.masterlist, it is here: http://cvs.debian.org/webwml/english/mirror/Mirrors.masterlist?rev=1.636root=webwmlview=log And it controls what mirrors users are shown for their arch in d-i, amoung other things.) What's the correct procedure for a) Defunct, unresponsive or incorrect mirror entries such as 'Site: www.zentek-international.com' (wrong Archive-http) or 'Site: natasha.stmarytx.edu' (timeout) b) the six mirrors with sh architecture? I'm showing 288 responding archive mirrors, of which 65 have some error preventing automated querying (usually condition A above) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
2.6.8-12-amd64-k8 raid1 freezes with spurious interrupts
Hello, I have a problem with an Asus A8N-SLI motherboard, kernel 2.6.8-12-amd64-k8 and raid1 on two 300 GB Samsung harddrives Regulary while the raid syncs I get spurious interrupts 8859 IRQ7 etc. and the system freezes! In gernerall waiting brings the system after some hours (five) back. Rebooting brings me back to sync the raid and the freeze status. Any help is welcome. Regards, Harm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: amd64 situation in Mirrors.masterlist
Jo Shields wrote: Joey Hess wrote: A quick look at what Mirrors.masterlist says about mirrors carrying amd64 finds a lot of probably wrong information: * 154 mirrors listed as mirroring !amd64, but having all other arches. This is probably wrong for most of them ... it's definitly wrong for the couple I spot-checked. * 69 mirrors listed as mirroring only amd64 and one or two other arches. Probably correct for most of them. * 65 mirrors listed as mirroring some list of archirectures that does not include amd64. Such as mirroring only i386. Probably right for many and wrong for many others. Would someone like to go through and fix all this in Mirrors.masterlist? Bonus points if you fix the archive lists to be accurate for all other arches too. Super bonus points if you don't do it by hand like I did, last time I did it. :-) (In case you're not familier with Mirrors.masterlist, it is here: http://cvs.debian.org/webwml/english/mirror/Mirrors.masterlist?rev=1.636root=webwmlview=log And it controls what mirrors users are shown for their arch in d-i, amoung other things.) What's the correct procedure for a) Defunct, unresponsive or incorrect mirror entries such as 'Site: www.zentek-international.com' (wrong Archive-http) or 'Site: natasha.stmarytx.edu' (timeout) b) the six mirrors with sh architecture? I'm showing 288 responding archive mirrors, of which 65 have some error preventing automated querying (usually condition A above) The attached mirrorstatus file should be fairly easily to parse, both by eye and by machine. It's a list of each archive Site: entry and the architectures they actually host. The list was mostly generated by the attached C# source (the **TIMEOUT** entries are manual, as my cheap use of wget doesn't let me grab that info properly). I'm not actually sure what the correct format is for Archive-architecture when something's got all supported arches, and I'm not sure what to do about the hosts I couldn't contact - but this should save someone some time. **BADMIRROR** lines need manual checking, I'm afraid. 299 total archive mirrors (HTTP or FTP) made up of: 223 correct, valid, responding mirrors 65 BADMIRRORs (manual checking required) 11 TIMEOUTs (possible routing issues for me, or dead host) of the valid mirrors: 159 Alpha mirrors 208 AMD64 mirrors 149 ARM mirrors 147 HP PA-RISC mirrors 168 HURD-i386 mirrors 223 i386 mirrors 163 IA64 mirrors 149 Motorola 68000 mirrors 150 MIPS (big endian) mirrors 149 MIPS (little endian) mirrors 167 PowerPC mirrors 146 S/390 mirrors 170 SPARC mirrors 6 Hitachi SuperH mirrors (unofficial) ameba.sc-uni.ktu.lt:i386 archive.progeny.com:alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc carroll.aset.psu.edu: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc cdn.mirror.garr.it: **BADMIRROR*** cudlug.cudenver.edu:alpha amd64 hurd-i386 i386ia64powerpc sparc debian.2z.net: **BADMIRROR*** debian.3wsi.net:**BADMIRROR*** debian.balt.net:amd64 arm i386sparc debian.blueyonder.co.uk:alpha amd64 arm hppahurd-i386 i386ia64m68kmipsmipsel powerpc s390sparc debian.cites.uiuc.edu: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.cn99.com:amd64 i386 debian.crosslink.net: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.csie.ntu.edu.tw: amd64 hurd-i386 i386 debian.efis.ucr.ac.cr: **BADMIRROR*** debian.ens-cachan.fr: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.essentkabel.com: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.experimentos.cl: amd64 i386 debian.fastbull.org:amd64 hppai386ia64sparc debian.fastweb.it: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.fifi.org:amd64 i386sparc debian.funlam.edu.co: amd64 i386 debian.goldweb.com.au: hurd-i386 i386powerpc debian.hands.com: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.ihug.co.nz: alpha amd64 arm hppahurd-i386 i386 ia64mipsmipsel powerpc s390sh sparc debian.ihug.com.au: **BADMIRROR*** debian.indika.net.id: i386 debian.inf.elte.hu: alpha amd64 arm hppahurd-i386 i386 ia64m68kmipsmipsel powerpc s390sparc debian.inode.at:alpha amd64 arm i386powerpc sparc
Re: 2.6.8-12-amd64-k8 raid1 freezes with spurious interrupts
On Tuesday 08 August 2006 12:04, Harm Behrens wrote:
Hello,
I have a problem with an Asus A8N-SLI motherboard, kernel 2.6.8-12-amd64-k8
and raid1 on two 300 GB Samsung harddrives
Regulary while the raid syncs I get spurious interrupts 8859 IRQ7 etc.
and the system freezes!
I've seen spurious interrupt IRQ7 errors on boards with an unused Centronics
printer port. Does your mobo have such a port? If so, do you still get
these errors with a printer plugged in?
If the error does not manifest with a printer on the port then it is caused by
the pull-up resistance on pin 10 of the port {which creates an interrupt
when it goes to 0V} being too high. In fact, the resistor might be absent
altogether and the board will still apparently pass testing. But the pin
will pick up noise, and eventually cause a false interrupt signal.
You could try artificially tying pin 10 to +5V via a resistor of 4k7 or
thereabouts. Pin 14 {which tells the printer whether to do a line feed
whenever it gets a CR, or only when it receives an explicit LF} is normally
held high, so this might well do: just connect a 4.7kohm resistor (yellow,
violet, red) from pin 14 to pin 10 {If you measure with an AVO you should
see +5V between pin 14 and the PC chassis}.
More comprehensive circuit, which will get +5V from anywhere it can find it:
this can be built within a 25-pin DIN plug. Use any old diodes you can find.
1N4148s are as good as anything. Join all the cathodes together and connect
via a 4k7 resistor to pin 10. Connect the anodes to pins 1, 2, 3, 4, 5, 6,
7, 8, 9, 14, 16 and 17.
1 ---||---*---[4k7]--- 10
|
2 ---||---*
|
3 ---||---*
|
4 ---||---*
|
5 ---||---*
|
6 ---||---*
|
7 ---||---*
|
8 ---||---*
|
9 ---||---*
|
14 ---||---*
|
16 ---||---*
|
17 ---||---'
Alternatively, if you can find a +5V supply somewhere inside the PC, you could
solder a resistor between there and the motherboard connector itself.
This -should- not stop a printer working; but if the cable is very long, the
printer may have trouble pulling its zeros low enough and so skip characters.
In this case, just increase the resistance till it does work.
If plugging in a printer doesn't cure the problem, or if there is no
Centronics port, then this is not the answer. What is using IRQ7 in your
setup?
--
AJS
delta echo bravo six four at earthshod dot co dot uk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: amd64 situation in Mirrors.masterlist
* Jo Shields ([EMAIL PROTECTED]) [060808 12:17]: What's the correct procedure for a) Defunct, unresponsive or incorrect mirror entries such as 'Site: www.zentek-international.com' (wrong Archive-http) or 'Site: natasha.stmarytx.edu' (timeout) b) the six mirrors with sh architecture? Prodding the administrators, and, failing that, removing the entry. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.8-12-amd64-k8 raid1 freezes with spurious interrupts
Hi, I have a problem with an Asus A8N-SLI motherboard, kernel 2.6.8-12-amd64-k8 and raid1 on two 300 GB Samsung harddrives Regulary while the raid syncs I get spurious interrupts 8859 IRQ7 etc. and the system freezes! I've seen spurious interrupt IRQ7 errors on boards with an unused Centronics printer port. Does your mobo have such a port? If so, do you still get these errors with a printer plugged in? thanks for detailed help, I'll to diable the printer port via the bios and see if it helps, as I don't need it. Anyway there must be annother problem, while syncing the raid1. Because I don't see all the time spurious interrupts. Furthermore the freezing sometime halts for some minutes, where regualary work is possible. Harm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ia32-libs question
Hi all, I have on my system a 32-bit chroot and installed ia32-libs. In my /etc/ld.so.conf I got the chroot entries like /var/chroot/sid-ia32/ etc. Is it necessessary to get the entry for ia32-libs, too ? I mean, an entry like /emul/ia32-libs as ATI places some needed drivers below this. Or does Debian find this directory per default ? Regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: amd64 situation in Mirrors.masterlist
Andreas Barth wrote: * Jo Shields ([EMAIL PROTECTED]) [060808 12:17]: What's the correct procedure for a) Defunct, unresponsive or incorrect mirror entries such as 'Site: www.zentek-international.com' (wrong Archive-http) or 'Site: natasha.stmarytx.edu' (timeout) b) the six mirrors with sh architecture? Prodding the administrators, and, failing that, removing the entry. And bearing in mind that one or two mirrors are only accessible from inside their target country. (Which certianly makes it hard to check them..) -- see shy jo signature.asc Description: Digital signature
Re: Right kernel for AMD Athlon64-3000+
On Sun, Aug 06, 2006 at 01:27:21PM +1000, Sam Varghese wrote: I've been running an AMD64-3000+ with a generic kernel for the last six months: [EMAIL PROTECTED]:~$ uname -a Linux zizyphus 2.6.16-2-amd64-generic #1 Sun Jul 16 01:12:23 CEST 2006 x86_64 GNU/Linux Today I was just wondering if the amd64-k8 kernel wouldn't be more suited for this processor. It technically would, although the difference is pretty minor. I believe there are plans to drop -generic entirely for future kernels. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: amd64 situation in Mirrors.masterlist
Jo Shields wrote: I'm not actually sure what the correct format is for Archive-architecture when something's got all supported arches The best thing to do there is to list all the arches. and I'm not sure what to do about the hosts I couldn't contact - but this should save someone some time. **BADMIRROR** lines need manual checking, I'm afraid. A patch that updates Mirrors.masterlist with the arch info for the mirrors you could reach would be helpful. -- see shy jo signature.asc Description: Digital signature
Re: Grub bad partition pointing after kernel upgrade
should not be normal. Please check in /boot/grub/menul.lst the line # kopt=root=/dev/hda6 ro It is in the section with the many hashes. Do not remove the hashes (suppose, you know this). If you enter here the correct partition for root, an upgrade should be o.k. next time. this is an extract of my menu.lst: # kopt=root=/dev/hda7 ro ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,6) could it become like this? # kopt=root=/dev/hda3 ro ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,2) /dev/hda3 is my kernel-image partition... Thanks, Giulio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: amd64 situation in Mirrors.masterlist
Joey, Here's an update for my mirror: Old Site Name: mirror.mcs.anl.gov Updated entry: -- Site: mirror.anl.gov Aliases: n/a Type: leaf Archive-ftp: /pub/debian/ Archive-architecture: alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc Archive-http: /debian/ Mirrors-from: ftp.debian.org Maintainer: Brian Elliott Finley [EMAIL PROTECTED], [EMAIL PROTECTED] Country: US United States Location: Chicago, Illinois Sponsor: Argonne National Laboratory http://www.anl.gov/ Comment: This is a complete mirror, connected by Gigabit. Cheers, -Brian Thus spake Joey Hess ([EMAIL PROTECTED]): A quick look at what Mirrors.masterlist says about mirrors carrying amd64 finds a lot of probably wrong information: * 154 mirrors listed as mirroring !amd64, but having all other arches. This is probably wrong for most of them ... it's definitly wrong for the couple I spot-checked. * 69 mirrors listed as mirroring only amd64 and one or two other arches. Probably correct for most of them. * 65 mirrors listed as mirroring some list of archirectures that does not include amd64. Such as mirroring only i386. Probably right for many and wrong for many others. Would someone like to go through and fix all this in Mirrors.masterlist? Bonus points if you fix the archive lists to be accurate for all other arches too. Super bonus points if you don't do it by hand like I did, last time I did it. :-) (In case you're not familier with Mirrors.masterlist, it is here: http://cvs.debian.org/webwml/english/mirror/Mirrors.masterlist?rev=1.636root=webwmlview=log And it controls what mirrors users are shown for their arch in d-i, amoung other things.) -- see shy jo -- Brian Elliott Finley Mobile: 630.631.6621 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ia32-libs question
Hans-J. Ullrich [EMAIL PROTECTED] writes: as ATI places some needed drivers below this. Or does Debian find this directory per default ? It does already, thanks to special symlinks in /lib/ldconfig. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub bad partition pointing after kernel upgrade
On Tue, Aug 08, 2006 at 07:27:04PM +0200, antongiulio05 wrote: this is an extract of my menu.lst: # kopt=root=/dev/hda7 ro ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,6) could it become like this? # kopt=root=/dev/hda3 ro Yes, just edit it. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
chroot with NIS
Hi, I have never set up or used a chroot environment, but am forced to set one up in a new AMD64 system, to be able to run some 32 bit apps such as openoffice.org. I would like to install an easily reversible chroot environment; i.e. one that can be removed very easily. I have read some suggestions that setting up a chroot environment with NIS working as a client, and the 64 bit system as a server may be the cleanest way to do this. I have installed NIS, and read its documentation, but being completely inexperienced with it, can't make much sense of it. It would really help if I could see some configuration files (/etc/ypserv.conf, /etc/ypserv.securenets, /etc/default/nis, /etc/yp.conf). I would appreciate it if somebody can share these config files, whether in the context of setting up a chroot or not. Comments on alternatives or critiques would also be very welcome. Thanks in advance. Cheers, -- Seb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: What Utilities to check a Hard Disc?
On Sunday 06 August 2006 19:11, Daniel van Eeden wrote: The HDD tools I use are: * smartmontools smartctl -a -d ata /dev/sda # show info for SATA disk smartctl -a /dev/hda# show info for PATA disk smartctl -t long /dev/hda # start long test for PATA disk I have now installed smartmontools on a raid1 machine with debian amd64 dual opterons and two hard disks, used for computation only. At the installation: Not starting SMART daemon smartd, disabled via /etc/default/smartmontools Question: should I activate smartd? thank you francesco pietra * hddtemp hddtemp /dev/sda# check temperature for SATA disk * hdparm hdparm -I /dev/hda # show info about acoustics mgmt and more * e2fsprogs badblocks -w /dev/hda # do an DESTRUCTIVE write test on PATA disk Testing SCSI disks can be don with Seagate Seatools Enterprise for Linux. (32-bit only?) Cheers, Daniel On Mon, 2006-08-07 at 01:20 +0900, Craig Hagerman wrote: Hi, I am wondering what utilities I can use to check the health of my hard discs. On my mac powerbook I can check the S.M.A.R.T. status. A few months the powerbook indicated the drive was about the fail. I backed everythign up and sure enough it DID fail shortly aftewards. I just had some strange messages on the console. I did an update and rebooted to find messages like: driveready seekcomplete error which is worrying. Debian wouldn't start up infact. I shutdown and restarted in another partition (Ubuntu 32) which did start up OK. I tried Debian again and it failed to boot. Tried Ubuntu and it failed. (Getting quite worried here.) Tried the 3rd partition (windows) and it did boot. After shutting down, Debian booted with no problem. Now I am wondering if there is a serious underlying problem, but don't know what utilities I can use to assess the situation. Any advice about utilities to use would be much appreciated. Craig Hagerman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
