LiloSetup has recently been known to crash the entire system. But so far, the cases I investigated led to pinpoint os-prober (a dependency) as the culprit.
Please report here if you experienced that problem. Tx
[SOLVED]LiloSetup / os-prober
[SOLVED]LiloSetup / os-prober
What really matters is where you are going, not where you come from.
Re: LiloSetup / os-prober
I`ve just tested and indeed os-prober crashes the system, however it looks that only X is affected as I managed to regain control with Ctr+Alt+SysRq+k (or +r - not sure) and switch to tty. It looks that my suspicion, that btrfs is the cause, was wrong. Currently I wiped btrfs with ext4 and the crash still happens.
Re: LiloSetup / os-prober
http://www.salixos.org/forum/viewtopic. ... 734#p15734
.. see the last few posts on the first page of this thread. Not sure if it's the same thing though.
EDIT
For what it's worth, I just installed os-prober in Ratpoison beta and it appears to work fine from the command line. lilosetup, which I then installed (no further deps) exited with "Finished [127]" without getting to the GUI.
.. see the last few posts on the first page of this thread. Not sure if it's the same thing though.
EDIT
For what it's worth, I just installed os-prober in Ratpoison beta and it appears to work fine from the command line. lilosetup, which I then installed (no further deps) exited with "Finished [127]" without getting to the GUI.
Re: LiloSetup / os-prober
Did you launch lilosetup.py from the command line? Wasn't there any other messages? If so, is it possible to copy-paste it integrally?mimosa wrote:lilosetup, which I then installed (no further deps) exited with "Finished [127]" without getting to the GUI.
Tx
OK, Tx for the confirmation. Could you give me the specs of your machine? Could you try os-prober on some other machines?witek wrote:I`ve just tested and indeed os-prober crashes the system,
So far I had this behavior only on an Asus laptop, not on any other machine.
What really matters is where you are going, not where you come from.
Re: LiloSetup / os-prober
No, I ran it using the ratpoison colon command. When I just tried from console, it opened normally (though only with the .py extension). Maybe this is simply a root permissions issue. In fact, of course it is. Sorry, I should have realised.
I didn't try actually doing anything with lisosetup, just in case - though now I come to think of it, I'd like to make the beta default.
I didn't try actually doing anything with lisosetup, just in case - though now I come to think of it, I'd like to make the beta default.
Re: LiloSetup / os-prober
One is indeed asus laptop A9RP; the second Fujitsu Amilo Pro. Neither has currently any btrfs partition thouh the system complains something about btrfs. Both have ntfs partitions. One has system on JFS the second on XFS partition. Both crash with os-prober. It looks that kernel has a problem (this is last part of the message copied via cat /dev/vcs as standard error redirection doesn`t work)Akuna wrote:OK, Tx for the confirmation. Could you give me the specs of your machine? Could you try os-prober on some other machines?
Code: Select all
[ 6305.498400] Modules linked in: btrfs(+) ufs qnx4 hfsplus hfs minix snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss ipv6 cpufreq_ondemand speedstep_lib freq_table mperf ppdev lp parport_pc parport fuse radeon ttm drm_kms_helper sdhci_pci sdhci drm mmc_core processor asus_laptop video pcmcia joydev yenta_socket i2c_piix4 zd1211rw ati_agp agpgart i2c_algo_bit pcmcia_rsrc 8139too mii i2c_core pcmcia_core shpchp snd_hda_codec_si3054 thermal snd_hda_codec_realtek thermal_sys snd_hda_intel snd_hda_codec sg snd_hwdep battery usbhid button rtc_cmos rtc_core rtc_lib ac hwmon psmouse sparse_keymap hid snd_pcm snd_timer snd evdev serio_raw mac80211 soundcore snd_page_alloc cfg80211 output rfkill [ 6305.515476] Pid: 6755, comm: modprobe Tainted: G D 2.6.37.6-smp #2 [ 6305.518324] Call Trace: [ 6305.521131] [<c1042972>] warn_slowpath_common+0x72/0xa0 [ 6305.523977] [<c1150486>] ? sysfs_add_one+0xb6/0x130 [ 6305.526811] [<c1150486>] ? sysfs_add_one+0xb6/0x130 [ 6305.529710] [<c1042a43>] warn_slowpath_fmt+0x33/0x40 [ 6305.532536] [<c1150486>] sysfs_add_one+0xb6/0x130 [ 6305.535356] [<c114ff6b>] ? sysfs_new_dirent+0x5b/0x100 [ 6305.538171] [<c1150561>] create_dir+0x61/0xb0 [ 6305.541048] [<c1150651>] sysfs_create_dir+0x71/0xb0 [ 6305.543875] [<c14e50ec>] kobject_add_internal+0x8c/0x200 [ 6305.546658] [<c14ef0d3>] ? kvasprintf+0x43/0x60 [ 6305.549454] [<c14e5807>] kset_register+0x27/0x60 [ 6305.552288] [<c14e58b7>] kset_create_and_add+0x77/0x100 [ 6305.555018] [<f9a83004>] ? btrfs_test_super+0x4/0x40 [btrfs] [ 6305.557713] [<f9ab615a>] btrfs_init_sysfs+0x1a/0x30 [btrfs] [ 6305.560443] [<f8ba900c>] init_btrfs_fs+0xc/0x89 [btrfs] [ 6305.563208] [<c1001235>] do_one_initcall+0x35/0x170 [ 6305.565901] [<f8ba9000>] ? init_btrfs_fs+0x0/0x89 [btrfs] [ 6305.568554] [<c107777b>] sys_init_module+0x10b/0x18b0 [ 6305.571194] [<c19dd5ac>] syscall_call+0x7/0xb [ 6305.573804] ---[ end trace 661c9a7c957183f1 ]--- [ 6305.576377] kobject_add_internal failed for btrfs with -EEXIST, don't try to register things with the same name in the same directory. [ 6305.581743] Pid: 6755, comm: modprobe Tainted: G D W 2.6.37.6-smp #2 [ 6305.584544] Call Trace: [ 6305.587309] [<c19daa01>] ? printk+0x1d/0x1f [ 6305.590026] [<c14e51cf>] kobject_add_internal+0x16f/0x200 [ 6305.592735] [<c14e5807>] kset_register+0x27/0x60 [ 6305.595491] [<c14e58b7>] kset_create_and_add+0x77/0x100 [ 6305.598195] [<f9a83004>] ? btrfs_test_super+0x4/0x40 [btrfs] [ 6305.600891] [<f9ab615a>] btrfs_init_sysfs+0x1a/0x30 [btrfs] [ 6305.603568] [<f8ba900c>] init_btrfs_fs+0xc/0x89 [btrfs] [ 6305.606233] [<c1001235>] do_one_initcall+0x35/0x170 [ 6305.608967] [<f8ba9000>] ? init_btrfs_fs+0x0/0x89 [btrfs] [ 6305.611623] [<c107777b>] sys_init_module+0x10b/0x18b0 [ 6305.614282] [<c19dd5ac>] syscall_call+0x7/0xb No volume groups found /dev/sda1:Microsoft Windows XP Professional:Windows:chain [ 6307.721348] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) /dev/sda6:Fedora release 15 (Lovelock):Fedora:linux
Re: LiloSetup / os-prober
I'm working on a new version of LiloSetup with no dependency on os-prober (much easier for me than debugging os-prober)
Here is a test version: http://people.salixos.org/akuna/livetoo ... h-1plb.txz
Let me know if it works as expected & if you encounter any problem with it. Tx
Here is a test version: http://people.salixos.org/akuna/livetoo ... h-1plb.txz
Let me know if it works as expected & if you encounter any problem with it. Tx
What really matters is where you are going, not where you come from.
Re: LiloSetup / os-prober
It looks just the same, though I did get this error message:
I do wonder, I just installed the downloaded package using installpkg - did that replace the old one?
Code: Select all
Package lilosetup-20110706-noarch-1plb.txz installed.
root[lucy]# lilosetup.py
(lilosetup.py:3831): IBUS-WARNING **: Connect to unix:abstract=/tmp/dbus-4ZzvG3LXa4,guid=4a291b2c29126ea2eed7efea00000023 failed: Failed to connect to socket /tmp/dbus-4ZzvG3LXa4: Connection refused.
root[lucy]# Re: LiloSetup / os-prober
you should use upgradepkg or even better spkg -umimosa wrote:I do wonder, I just installed the downloaded package using installpkg - did that replace the old one?
I upgraded and lilosetup starts without crash, however I didn`t test if it works properly further.
Re: LiloSetup / os-prober
Please somebody with this problem try an older kernel version. For example install the kernel packages from 13.1. Then run os-prober.