applications/manjaro-settings-manager

Fork 0

Claims to find unsupported kernel on Manjaro 0.8.11-pre1 install media #6

New issue

Closed

opened 2014-07-20 07:07:10 +00:00 by philm · 11 comments

philm commented

2014-07-20 07:07:10 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: manjaro

This is a weird bug. MSM claims to find linux314 as unsupported on my latest testbuild install media. I ship ce42912d39 with this media. The question is, why MSM claims this new kernel is unsupported. Will worry users right from the get-go ...

*Created by: manjaro* This is a weird bug. MSM claims to find linux314 as unsupported on my latest testbuild install media. I ship ce42912d3983aa186c5e8da61b0057d648e833d4 with this media. The question is, why MSM claims this new kernel is unsupported. Will worry users right from the get-go ...

philm commented

2014-07-20 07:59:43 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: manjaro

I think it happens due no pacman databases on our install medias. This check should only happen at least we did "pacman -Syy" once.

*Created by: manjaro* I think it happens due no pacman databases on our install medias. This check should only happen at least we did "pacman -Syy" once.

philm commented

2014-07-20 08:18:35 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: manjaro

Ok, this is defiantly connected with #4. If you call "pacman -Syy" before you start XFCE desktop it will claim that there is a newer kernel available as currently installed, which is actually the latest available ...

*Created by: manjaro* Ok, this is defiantly connected with #4. If you call "pacman -Syy" before you start XFCE desktop it will claim that there is a newer kernel available as currently installed, which is actually the latest available ...

philm commented

2014-07-20 11:38:26 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: Kirek

Maybe with ef2b0c74b0 is enough to fix that, but I don't think this will totally fix that, I will test this later at night when I have more time.

*Created by: Kirek* Maybe with ef2b0c74b0f719165f058db7af2f54be296946a9 is enough to fix that, but I don't think this will totally fix that, I will test this later at night when I have more time.

philm commented

2014-07-20 14:23:07 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: manjaro

Ok, if you like to test it on my new install media you can get it from here.

*Created by: manjaro* Ok, if you like to test it on my new install media you can get it from <a href="http://sourceforge.net/projects/manjarotest/files/0.8.11/xfce-minimal/0.8.11-pre1/">here</a>.

philm commented

2014-07-24 19:14:55 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: manjaro

This is fixed in KDE 0.8.11-pre1

*Created by: manjaro* This is fixed in KDE 0.8.11-pre1

philm commented

2014-07-25 17:38:47 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: manjaro

This issue seems not to been fixed. It happens now with Manjaro Openbox 0.8.11-pre1 once again. We have to find out why linux314 seems to be claimed to be unsupported. We have to review this detection code once more. I think it has something to do with the local db and when no remote db was found MSM claims wrongly.

*Created by: manjaro* <img src="http://wstaw.org/m/2014/07/25/MSM-023_png_750x750_q85.jpg"> This issue seems not to been fixed. It happens now with Manjaro Openbox 0.8.11-pre1 once again. We have to find out why linux314 seems to be claimed to be unsupported. We have to review this detection code once more. I think it has something to do with the local db and when no remote db was found MSM claims wrongly.

philm commented

2014-07-25 17:56:28 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: Kirek

The problem is that there is no local pacman database yet, so no kernel is "available" (in the repos), I now check of internet connection and if pacman its up to date (which is useless as if it the database its not ever synced there is nothign to update...) , and this doesn't seem to be enough.
I will add a a check if /var/lib/pacman/sync/*.db files and if doesn't exist to not check for unsupported kernels...

*Created by: Kirek* The problem is that there is no local pacman database yet, so no kernel is "available" (in the repos), I now check of internet connection and if pacman its up to date (which is useless as if it the database its not ever synced there is nothign to update...) , and this doesn't seem to be enough. I will add a a check if /var/lib/pacman/sync/*.db files and if doesn't exist to not check for unsupported kernels...

philm commented

2014-07-25 18:15:19 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: manjaro

K, as I mentiond here: #7

*Created by: manjaro* K, as I mentiond here: #7

philm commented

2014-07-25 20:17:03 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: Kirek

Another try, with 978b061312 hopefully its fixed.
I don't check for "internet" connection as I found it unreliable (you may have LAN connection but not internet...)

*Created by: Kirek* Another try, with 978b061312b504cbe3a974210704744b2ab59145 hopefully its fixed. I don't check for "internet" connection as I found it unreliable (you may have LAN connection but not internet...)

philm commented

2014-08-10 09:57:56 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: Kirek

This problem still exists? At least in 0.8.11-pre2 I think its fixed (VM/live and with or without network)

*Created by: Kirek* This problem still exists? At least in 0.8.11-pre2 I think its fixed (VM/live and with or without network)

philm commented

2014-08-10 10:04:10 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: manjaro

Seems to been fixed. Else we can still re-open it.

*Created by: manjaro* Seems to been fixed. Else we can still re-open it.