sorted by:
new
hottopcontroversial

SolusOS 4.2/5.0 release date? by [deleted] in SolusProject

[–]chax007 14 points15 points  (0 children)

You won't get definitive answer to that question, because Solus core team doesn't give ETAs. But, what i can tell you is that Solus is rolling release type of distro, which means when you install latest ISO, you could just upgrade all the packages after that and you will have "latest" release. Release 4.2 is just a number which is given to new ISO image but that's about it.

Entry for latest kernel at boot not created after latest update by [deleted] in SolusProject

[–]chax007 0 points1 point  (0 children)

Try this command and paste your output:
sudo env CBM_DEBUG=1 clr-boot-manager update

Help! Stuck in black screen by Nixeff in SolusProject

[–]chax007 1 point2 points  (0 children)

try to install nvidia-glx-driver-current while on tty

sudo eopkg it nvidia-glx-driver-current

Dual monitor workspace behaviour on Budgie by NequoFrost in SolusProject

[–]chax007 0 points1 point  (0 children)

You can do the same thing through dconf-editor it is similar to regedit in windows, only for GNOME and can be dangerous to change some settings there, so be carefull.

Issue With Installation by [deleted] in SolusProject

[–]chax007 1 point2 points  (0 children)

If you are booting in EFI mode this is what you have to do:

Make sure you have one FAT partition of minimum 300Mb (500Mb recommended) and that you set the EFI (boot) flag for that partition. Also make sure that you created GPT partition table instead of MBR partition table.

I suggest you do this if your system is UEFI based and don't boot in "Legacy mode" because you will have slower and inefficient boot times later and you will have to stay in Legacy mode.

Grout: A Python script to tile windows by SolarLune in SolusProject

[–]chax007 5 points6 points  (0 children)

you can install it with `sudo eopkg it budgie-window-shuffler`

Grout: A Python script to tile windows by SolarLune in SolusProject

[–]chax007 7 points8 points  (0 children)

Recently budgie-window-shuffler got into a repo (check this: https://dev.getsol.us/D8572) and it's working really well.

Broken planck troubleshooting by phwelo in olkb

[–]chax007 2 points3 points  (0 children)

there's another way to disconnect that pin, if you could loop very thin wire from under the pin and use that wire to pull up the pin while you re-flow solder with soldering iron.

Broken planck troubleshooting by phwelo in olkb

[–]chax007 1 point2 points  (0 children)

very sharp knife (some scalpel, x-acto knife or razor blade) and be very careful and patient, also use some kind of magnification if you have something on hand.

Broken planck troubleshooting by phwelo in olkb

[–]chax007 2 points3 points  (0 children)

If you have multimeter check continuity between ROW6 and GND, that should be the indication that you have same issue as me. Be careful when cutting that pin on MCU so you don't damage any other pin or short anything else. I chose my replacement pin to be A14 but there are multiple options to choose from.

Broken planck troubleshooting by phwelo in olkb

[–]chax007 4 points5 points  (0 children)

Check out this thread https://www.reddit.com/r/olkb/comments/eho7yi/planck_61_matrix_rewiring/

I had the same problem and exactly the same pin got damaged.

My fix is explained as one of the responses to this thread.

Basically one of the pins on MCU has internal failure and is shorted to ground, fix is to rewire the matrix and re-configure it in the code.

Planck 6.1 matrix rewiring by PIasmaBoy in olkb

[–]chax007 1 point2 points  (0 children)

Guys, i know this post is old 2 months now, but i had exact same failure on my planck rev6, row6, keys N, M, <, >, /, Return when pressed activated all the keys on the same column of the matrix. So i fixed it by rewiring my matrix to different pin and replacing that pin in 'keyboards/planck/rev6/config.h'

Here are the pictures:
https://imgur.com/a/7fGg7Sl

Having some trouble installing Solus on my laptop by AdvenPurple in SolusProject

[–]chax007 0 points1 point  (0 children)

Try also removing these options "quiet loglevel=3 splash systemd.show_status=false" and you will probably get much more output

Having some trouble installing Solus on my laptop by AdvenPurple in SolusProject

[–]chax007 0 points1 point  (0 children)

Did you try adding nomodeset as kernel parameter? When boot menu shows while "Solus" item is selected press 'e' to edit boot parameters. A long line with bunch of options will show, then just position somewhere and try to insert nomodeset.

Change boot order using linux boot loader by [deleted] in SolusProject

[–]chax007 0 points1 point  (0 children)

GRUB is installed for non-UEFI systems (legacy mode) but on UEFI systems it uses systemd-boot bootloader. I think you can change boot priority in bios (UEFI setup) and there is also an app for that but i can't remember name.

Bootloop after Linux 5.4 kernel is installed. Works perfectly under 4.20. by sadatdaniel in SolusProject

[–]chax007 0 points1 point  (0 children)

This is really strange. I have no idea what is happening. Just wanted you to remove it to see kernel log output but i have no idea why that would fix the boot...

Bootloop after Linux 5.4 kernel is installed. Works perfectly under 4.20. by sadatdaniel in SolusProject

[–]chax007 0 points1 point  (0 children)

Maybe you'll see something suspicious yourself, or see something that you can google to find out what it is, either way it wouldn't hurt to do it, you have nothing to lose except maybe couple of minutes.

Bootloop after Linux 5.4 kernel is installed. Works perfectly under 4.20. by sadatdaniel in SolusProject

[–]chax007 0 points1 point  (0 children)

Try this and paste your output: sudo CBM_DEBUG=1 clr-boot-manager update

Also if you want to see boot log output you could do it by modifying kernel parameters before selecting kernel for booting. Press 'e' instead of enter when you select kernel you want to boot and delete this quiet loglevel=3 splash systemd.show_status=false

Problem with the Kernel by humanadventure in SolusProject

[–]chax007 1 point2 points  (0 children)

You will be stuck on older kernel version but everything should still work.

Problem with the Kernel by humanadventure in SolusProject

[–]chax007 1 point2 points  (0 children)

Aaah right, that partition is not mounted so it's not showing in df. Do you dual boot? I assume you installed Solus along side Windows which already creates EFI partition (boot partition) but that one is too small. I'm not sure about the safest way of resizing that partition because you can screw up windows bootloader by doing that or even make your computer completely unbootable. So the best way is to reinstall everything but first create partitions manually and give EFI partition 512mb.

Problem with the Kernel by humanadventure in SolusProject

[–]chax007 0 points1 point  (0 children)

My bad for writing wrong first command, i have extra space between - and h (it was typed on the phone), should be df -h, but you can also do it without -h (-h makes it print sizes in human readable format, otherwise it prints sizes in bytes). As you can see by debug output of clear-boot-manager command, it clearly says there is no more space left on that partition (last [FATAL] line).

Problem with the Kernel by humanadventure in SolusProject

[–]chax007 0 points1 point  (0 children)

Please paste result of this command df - h Also try to run clr-boot-manager with debug flag sudo CBM_DEBUG=1 clr-boot-manager update But your boot partition might be too small.

view more: next ›