Re: System Freeze and python-central_0.5.9_all
Igor TAmara wrote: Hi, confirming freezing not depends on python-central for me. Anders> Hi, Anders> Anders> Today python-central was upgraded on my testing system to version 0.5.9. Anders> After a reboot the system started to freeze randomly like described in Anders> the System Freeze thread. Anders> Anders> I downgraded to 0.5.8 and the freezing went away - at least for now. Anders> Anders> So it seems like the problem with the freeze is related to Anders> python-central_0.5.9_all.deb. This would also explain why 32 bit Anders> experience same symptoms. Anders> Anders> Can anyone confirm this? Anders> Hi, I downgraded the library too, then I tried some screensavers with xscreensaver-demo and my pc frozen :( Linux compu 2.6.17-2-amd64 #1 SMP xorg 7.0.23 Same kernel xorg 7.1.0.5 (testing) Did you reboot after the downgrade? I left my machine running all night and still no freeze. Anders> Kind Regards Anders> Anders Anders> Anders> Anders> -- Anders> To UNSUBSCRIBE, email to [EMAIL PROTECTED] Anders> with a subject of "unsubscribe". Trouble? Contact Anders> [EMAIL PROTECTED] Anders> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help: NO longer boots ;
I had exactly the same problem and solved it by creating labels for the drives. For more info see this thread: http://lists.debian.org/debian-amd64/2006/09/msg00449.html and especially this message: http://lists.debian.org/debian-amd64/2006/09/msg00454.html -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help: NO longer boots ;
On 11/11/06 08:29:02PM -0600, helices wrote: > I have a dual Opteron box (Odin) that went down while I was gone, due to > an extended power failure. > > When it comes up, it fails to complete boot. Please, help me get this > system running again. > > uname -a > Linux (none) 2.6.17-2-amd64 #1 SMP ... > > Bootup sequence from obvious problems: > > ... > Success: loaded module raid10. > Done. > device-mapper: 4.6.0-ioctl (2006-02-17) initialised: ... > 1 logical volume(s) in volume group "VG2" now active > 7 logical volume(s) in volume group "VG1" now active > Done. > stdin: error 0 > Begin: Running /scripts/local-premount ... > kinit: name_to_dev_t(/dev/mapper/VG1-swap) = dm-3(253,3) > kinit: trying to resume from /dev/mapper/VG1-swap > Attempting manual resume > kinit: No resume image, doing normal boot ... > Done. > Usage: modprobe ... > ... > > Begin: running /scripts/init-bottom ... > mount: Mounting /root/dev on /dev/.static/dev failed: No such file or > directory > Done. > mount: Mounting /sys on /root/sys failed: ... > mount: Mounting /proc on /root/proc failed: ... > Target filesystem doesn't have /sbin/init > ... > > (initramfs)_ > First see if anything is in /root, it looks like it's attempts to mount the root filesystem there so if something is there it'll tell you if it just mounted the wrong filesystem or if there's a real problem with your root filesystem. If there's nothing at all there just run 'mount' and see if it thinks something is mounted there, if not look in /dev/mapper and see if there's a LVM volume for your root, considering that your swap is called VG1-swap it'll probably be VG1-root or VG2-root. If it's there try mounting it, although I'm not totally sure all of what capabilities you'll have in the initramfs. It might also be a good idea to look around for a Knoppix, Ubuntu LiveCD, etc so that you can have more tools handy in case there is a real problem with your disks. Jim. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
sshd signal blocking on aptitude upgrade
Hi It seems that every time I do an upgrade of sshd using aptitude the window change size event is blocked. Know I can restart it with at and /etc/init.d/ssh restart. But I was looking for a quick c program that would simple unblock the signal SIGWINCH on the current thread this is the thread which describes the problem http://lists.debian.org/debian-user/2006/07/msg00465.html unfortunately it has been a very long time since I looked at C. Thanks Alex signature.asc Description: Digital signature
Re: Help: NO longer boots ;
* helices <[EMAIL PROTECTED]> [2006:11:11:20:29:02-0600] scribed: > uname -a > Linux (none) 2.6.17-2-amd64 #1 SMP ... > > Bootup sequence from obvious problems: > > ... > Success: loaded module raid10. > Done. > device-mapper: 4.6.0-ioctl (2006-02-17) initialised: ... > 1 logical volume(s) in volume group "VG2" now active > 7 logical volume(s) in volume group "VG1" now active > Done. * Anders Brandt Petersen <[EMAIL PROTECTED]> [2006:11:13:00:31:21+0100] scribed: > You haven't made it easy. > > Does it detect your LVM's? Yes, see above. > Did it refer to a different root device than the ones getting detected, > because it could be that the BIOS could be configured to a different > bootorder so it points to the correct device? No, I don't think so. > I have no experience in saving LVMs in a chroot env. I don't know if it > will automatically map the LVM's if you use a bootdevice - what could go > wrong it is not in a RAID also? No, this device is NOT raided. -- Best Regards, helices - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: System Freeze and python-central_0.5.9_all
Hi, confirming freezing not depends on python-central for me. Anders> Hi, Anders> Anders> Today python-central was upgraded on my testing system to version 0.5.9. Anders> After a reboot the system started to freeze randomly like described in Anders> the System Freeze thread. Anders> Anders> I downgraded to 0.5.8 and the freezing went away - at least for now. Anders> Anders> So it seems like the problem with the freeze is related to Anders> python-central_0.5.9_all.deb. This would also explain why 32 bit Anders> experience same symptoms. Anders> Anders> Can anyone confirm this? Anders> Hi, I downgraded the library too, then I tried some screensavers with xscreensaver-demo and my pc frozen :( Linux compu 2.6.17-2-amd64 #1 SMP xorg 7.0.23 Anders> Kind Regards Anders> Anders Anders> Anders> Anders> -- Anders> To UNSUBSCRIBE, email to [EMAIL PROTECTED] Anders> with a subject of "unsubscribe". Trouble? Contact Anders> [EMAIL PROTECTED] Anders> -- Recomiendo Inkscape para hacer gráficos vectoriales http://www.inkscape.org signature.asc Description: Digital signature
Re: Help: NO longer boots ;
helices wrote: * Anders Brandt Petersen <[EMAIL PROTECTED]> [2006:11:12:22:56:23+0100] scribed: helices wrote: No, it does NOT complete bootup. Instead, it leaves me in that initramfs shell ;< Will `update-initramfs -c` work there? No that would create a new initrd - you are inside the initrd (Busybox). Is the root pointing to the correct harddisk. Heard stories of the dev changing at boot: You can see the root device in grub and see in the messages when the system boots what devices are detected. If they are different then you can change it in grub before booting. This system uses lilo. Else: Can you boot on another kernel? If not then I would use a bootcd/ramdisk have a look at the system and probably chroot into the system and try to create a new initrd/reinstall kernel. Apparently, that is the only kernel, because lilo does NOT pause at the red menu. The major complication is that root, and ALL partitions, are inside LVM. That is the part that confuses me. I do NOT want to try something destructive -- at least, until I have NO more options ;> What do you think? You haven't made it easy. Does it detect your LVM's? Did it refer to a different root device than the ones getting detected, because it could be that the BIOS could be configured to a different bootorder so it points to the correct device? I have no experience in saving LVMs in a chroot env. I don't know if it will automatically map the LVM's if you use a bootdevice - what could go wrong it is not in a RAID also? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: flash...
On Sun, Nov 12, 2006 at 03:16:39PM -0800, Simon Rocher wrote: > libflash-mozplugin ? > No, it had a name not obviously connected to flash - thats why I don't find it again, I think libflash-mozplugin I tried, but it seems not to display _any_ flash-page/-menu. sigi. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: flash...
libflash-mozplugin ? - Original Message From: sigi <[EMAIL PROTECTED]> To: debian-amd64@lists.debian.org Sent: Sunday, November 12, 2006 9:05:59 PM Subject: flash... Hi, I know, that there is no real flashplayer for amd64 out there... but some times ago I had a library installed, that displayed simple flash-pages on the web - but I forgot it's name, and found nothing via google anymore... I think, I got it's name here on this list. It was not gnash or swf-player - only one little lib, which I had to install, afaik. Does anybody here now something else besides gnash and swf-player? Thanks for your help, sigi. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
flash...
Hi, I know, that there is no real flashplayer for amd64 out there... but some times ago I had a library installed, that displayed simple flash-pages on the web - but I forgot it's name, and found nothing via google anymore... I think, I got it's name here on this list. It was not gnash or swf-player - only one little lib, which I had to install, afaik. Does anybody here now something else besides gnash and swf-player? Thanks for your help, sigi. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help: NO longer boots ;
* Anders Brandt Petersen <[EMAIL PROTECTED]> [2006:11:12:22:56:23+0100] scribed: > helices wrote: > >No, it does NOT complete bootup. Instead, it leaves me in that > >initramfs shell ;< > > > >Will `update-initramfs -c` work there? > > > No that would create a new initrd - you are inside the initrd (Busybox). > Is the root pointing to the correct harddisk. Heard stories of the dev > changing at boot: You can see the root device in grub and see in the > messages when the system boots what devices are detected. If they are > different then you can change it in grub before booting. This system uses lilo. > Else: > Can you boot on another kernel? If not then I would use a > bootcd/ramdisk have a look at the system and probably chroot into the > system and try to create a new initrd/reinstall kernel. Apparently, that is the only kernel, because lilo does NOT pause at the red menu. The major complication is that root, and ALL partitions, are inside LVM. That is the part that confuses me. I do NOT want to try something destructive -- at least, until I have NO more options ;> What do you think? -- Best Regards, helices - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: Help: NO longer boots ;
helices wrote: No, it does NOT complete bootup. Instead, it leaves me in that initramfs shell ;< Will `update-initramfs -c` work there? No that would create a new initrd - you are inside the initrd (Busybox). Is the root pointing to the correct harddisk. Heard stories of the dev changing at boot: You can see the root device in grub and see in the messages when the system boots what devices are detected. If they are different then you can change it in grub before booting. Else: Can you boot on another kernel? If not then I would use a bootcd/ramdisk have a look at the system and probably chroot into the system and try to create a new initrd/reinstall kernel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help: NO longer boots ;
* Anders Brandt Petersen <[EMAIL PROTECTED]> [2006:11:12:18:52:54+0100] scribed: > helices wrote: > >I have a dual Opteron box (Odin) that went down while I was gone, due to > >an extended power failure. > > > >When it comes up, it fails to complete boot. Please, help me get this > >system running again. > > > >uname -a > >Linux (none) 2.6.17-2-amd64 #1 SMP ... > > > >Bootup sequence from obvious problems: > >Begin: running /scripts/init-bottom ... > >mount: Mounting /root/dev on /dev/.static/dev failed: No such file or > >directory > >Done. > >mount: Mounting /sys on /root/sys failed: ... > >mount: Mounting /proc on /root/proc failed: ... > >Target filesystem doesn't have /sbin/init > >... > > > >(initramfs)_ > > > Are you in the system or can't you boot at all? > > Seems like somethings are corrupted especially your initrd. > > Have you tried an update-initramfs -c? No, it does NOT complete bootup. Instead, it leaves me in that initramfs shell ;< Will `update-initramfs -c` work there? -- Best Regards, helices - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: Help: NO longer boots ;
helices wrote: I have a dual Opteron box (Odin) that went down while I was gone, due to an extended power failure. When it comes up, it fails to complete boot. Please, help me get this system running again. uname -a Linux (none) 2.6.17-2-amd64 #1 SMP ... Bootup sequence from obvious problems: ... Success: loaded module raid10. Done. device-mapper: 4.6.0-ioctl (2006-02-17) initialised: ... 1 logical volume(s) in volume group "VG2" now active 7 logical volume(s) in volume group "VG1" now active Done. stdin: error 0 Begin: Running /scripts/local-premount ... kinit: name_to_dev_t(/dev/mapper/VG1-swap) = dm-3(253,3) kinit: trying to resume from /dev/mapper/VG1-swap Attempting manual resume kinit: No resume image, doing normal boot ... Done. Usage: modprobe ... ... Begin: running /scripts/init-bottom ... mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory Done. mount: Mounting /sys on /root/sys failed: ... mount: Mounting /proc on /root/proc failed: ... Target filesystem doesn't have /sbin/init ... (initramfs)_ Are you in the system or can't you boot at all? Seems like somethings are corrupted especially your initrd. Have you tried an update-initramfs -c? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
System Freeze and python-central_0.5.9_all
Hi, Today python-central was upgraded on my testing system to version 0.5.9. After a reboot the system started to freeze randomly like described in the System Freeze thread. I downgraded to 0.5.8 and the freezing went away - at least for now. So it seems like the problem with the freeze is related to python-central_0.5.9_all.deb. This would also explain why 32 bit experience same symptoms. Can anyone confirm this? Kind Regards Anders -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
