I have tried to install Salix 15.0 several times over the past few months but have always been unable to boot the newly installed system. I have tried several different variations on the installation process from different media but always come up with a problem that involves lack of UEFI.

I have ...

I think it may be a bit more complicated than that. I have what sounds like a similar problem and have tried many times. But my BIOS does support UEFI and I have a standard SATA drive on the PCI bus.

Hi folks,

I recently stumbled across GMountMan and think it looks like a useful tool. However, on startup it comes up with an empty display and only the 'About', 'Preferences' & 'Close' buttons enabled. It is as if I have no volumes on my computer which is, of course, completely wrong. I actually ...

I installed Salix 14.2 XFCE to a PC a couple of months ago. Gslapt was then used to install KDE, and the DM login screen was then used to set KDE as the default desktop.

KDEs 'System Settings' was then used to enable autologin. This failed to have any effect. A perusal of '/etc/kde/kdm/kdmrc ...

I do have Alejandro's original xcf file, so it's easy to make different color variations...
http://people.salixos.org/gapan/artwork/Salix_Wallpaper_light_blue.png


I do like this one. Alejandro had it basically right, but the lightening improved it. Not too 'busy' so items laid on it will be ...

.
'Shuffles back into forum with head hanging low, trying to look 'invisible'...
That got it. I corrected it, ran 'udevadm control --reload-rules && udevadm trigger' and a /dev/usb2nmea0 entry appeared. Duhhh.... How did I miss that? Thanks for your time, anyway.

Symlink not created.

I have just run ' grep -rnT 6001 *rule* ' & ' grep -rnT 6001 *rule* ' on the rules directories. Only the following showed up in addition to my entry, but it is commented out. Anyway I did check for '/dev/gps*' but no such entry is being created.
rules.d/97-gpsd.rules: 31 ...

ATTRS changed to ATTR, and no change. Even after rebooting.

Do you know how udev would behave if just one statement in the rule was garbage? Would it carry on and process the statements that made sense, or ignore the rule totally?

'lsusb' shows the device as:

Hi gapan,
The system has had a couple of weeks of rebooting since . I have tried the file in both directories, even simultaneously at times. (Yep, grasping at straws.)