| Author |
Message |
|
|
Post subject:
 Posted: Jul 17, 2008 - 07:22 AM
|
|
Team Member
Joined: Nov 24, 2006
Posts: 2870
Location: berlin
Status: Offline
|
|
snvv,
what version of dmsetup do you have?
greetz
devil |
_________________
>>we are sidux - resistance is futile - you will be assimilated<<
|
| |
|
|
|
 |
|
|
|
Post subject:
Posted: Jul 17, 2008 - 08:04 AM
|
|
Joined: May 28, 2007
Posts: 545
Status: Offline
|
|
devil
Package description for "dmsetup"
Installed 2:1.02.27-1
Candidate 2:1.02.27-2+c0.sidux.1
I am one DU behind right now but I will not upgrade.
I will be away for some hours.
Any way I think is the 2:1.02.27-1 that created the problem.
I don't know if it helps but in my xorg.conf I have commended out the :
#Section "InputDevice"
# Identifier "ALPS TouchPad"
# Driver "synaptics"
# Option "Device" "/dev/psaux"
...
&
#Section "InputDevice"
# Identifier "Synaptics TouchPad"
# Driver "synaptics"
# Option "Device" "/dev/psaux" |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 17, 2008 - 08:31 AM
|
|
Joined: Dec 05, 2006
Posts: 241
Status: Offline
|
|
Thanks for all the replies. I hope my post saved a few people from hassle.
I didn't have time to attempt a repair last night (along the lines suggested above) because I was out. However, I was able to du out of it this morning and my system is once again fine.
Once again, thanks to the sidux team for being so sharp. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 17, 2008 - 11:23 AM
|
|
Joined: Apr 06, 2008
Posts: 28
Status: Offline
|
|
Unfortunately, I did not see the warnings in time and I now have a unusable machine. I can get to the KDM login and no further (no mouse either). I can, of course, boot to init 3 OK. The problem I have at the moment is that the network is not working. so I cannot do a DU or other correction.
I take it that I need to chmod /dev and that will get network going again? |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 17, 2008 - 11:51 AM
|
|
Joined: Nov 25, 2006
Posts: 2571
Status: Offline
|
|
| As long as you can boot into a shell, network or not, this issue can be fixed relatively straight forward - it only gets complicated in case you can no longer boot normally (even then it's fixable, just more difficult to explain).
Code:
rm /etc/udev/rules.d/65_dmsetup.rules
update-initramfs -u
reboot
complete the dist-upgrade. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 17, 2008 - 12:09 PM
|
|
Joined: Apr 06, 2008
Posts: 28
Status: Offline
|
|
Sorry! I didn't see the post on the home page.
rm /etc/udev/rules.d/65_dmsetup.rules did the trick!
Thanks very much! |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 17, 2008 - 02:34 PM
|
|
Joined: May 28, 2007
Posts: 545
Status: Offline
|
|
I am upgraded up to the minute without problems.
Obviously this is not a generic problem. If you like to debug your systems you may ask whatever you think relevant about mine... |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 17, 2008 - 02:59 PM
|
|
Joined: Nov 25, 2006
Posts: 2571
Status: Offline
|
|
| it was a generic problem affecting everyone, but with slightly varying severity (depending if anything in the same update triggered an initrd rebuild, udev update or new kernel - this rendered the system unbootable, while all others "just" couldn't log into X anymore or lost network access, or ..., or ...) - now, it is fixed in our repo. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 17, 2008 - 04:26 PM
|
|
Joined: Mar 01, 2007
Posts: 20
Status: Offline
|
|
Thanks for great support from the team here !
I plugged in my old cable keyboard, started an older kernel, loged in as root, followed the 3 steps described by shl above, let run through smxi including grafic installer, started X from smxi and had a clean system again (64 bit).
When I rebooted with the current latest sidux kernel I had no X. So I loged in as root, made the grafic install in smxi one more time and started X. Now everything works fine again here. Great ! |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 18, 2008 - 07:26 PM
|
|
Joined: Jun 10, 2008
Posts: 18
Location: USA
Status: Offline
|
|
| i got hit by this, but after 'd-u'ing today, it was fixed. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 19, 2008 - 09:05 PM
|
|
Joined: May 20, 2008
Posts: 72
Location: AZ
Status: Offline
|
|
I deleted the rule and everything seems to be fine, but when I try to update initramfs, I get this :/boot/initrd.img-2.6.24-2.6.24.4.slh.5-sidux-686 does not exist. Cannot update. I removed this kernel along time ago. Is this a problem?
dmsetup and lsb-base are also upgraded as reccomended. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 19, 2008 - 09:22 PM
|
|
Joined: Nov 25, 2006
Posts: 2571
Status: Offline
|
|
Do you have dangling symlinks in /boot/?
If you do, delete them, update menu.lst and regenerate the initrd:
Code:
rm /boot/vmlinuz /boot/initrd.img /boot/System.map
update-grub
update-initramfs -u
|
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 19, 2008 - 10:37 PM
|
|
Joined: May 20, 2008
Posts: 72
Location: AZ
Status: Offline
|
|
| will upgrading grub rewrite grub.conf.? Only asking because triplebooting sidux XP and Mepis 7, and had a hard time figuring how to edit grub. Disks are not recognized properly. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 19, 2008 - 11:10 PM
|
|
Joined: May 20, 2008
Posts: 72
Location: AZ
Status: Offline
|
|
| slh, I did have a hangig symlink from the .24 kernel that I uninstalled. Grub would not update(disk config) but was able to update initramfs, thank you. |
|
|
| |
|
|
|
|
|
|
