Search found 2227 matches
- Wed Dec 13, 2017 10:12 am
- Forum: General
- Topic: MX-17 Release Candidate 1 - Feedback
- Replies: 183
- Views: 31792
Re: MX-17 Release Candidate 1 - Feedback
Re: BCM4356 firmware issue: Xubuntu, MX & Debian all have exactly the same firmware files for that chipset. There is an extra file, brcmfmac4356-pcie.bin.txt that is used just for some chromebook type computers (including the GPD piwadam has). It is specific to that particular configuration and ...
- Tue Dec 12, 2017 11:47 pm
- Forum: Bugs and Non-Package Requests Forum
- Topic: "man init" reports MX init is systemd? [SOLVED]
- Replies: 23
- Views: 4943
Re: "man init" reports that MX init is systemd?
I believe it indexes all the commands listed in the man pages, and systemd (1) lists init as a command. So does init (8) of course. But systemd cheats and uses the wrong category # for its man page so it shows up first. Changing the search order in /etc/manpath.config to search 8 before 1 and rebuil...
- Tue Dec 12, 2017 11:06 pm
- Forum: Bugs and Non-Package Requests Forum
- Topic: "man init" reports MX init is systemd? [SOLVED]
- Replies: 23
- Views: 4943
Re: "man init" reports that MX init is systemd?
No, I didn't update any packages. It seems to have to do with /var/cache/man/init.db , a file not present running Live. Deleting that file results in man init returning init 8. Running sudo mandb -c to recreate it results in man init returning systemd 1 I'm assuming something during installation or ...
- Tue Dec 12, 2017 10:34 pm
- Forum: Bugs and Non-Package Requests Forum
- Topic: "man init" reports MX init is systemd? [SOLVED]
- Replies: 23
- Views: 4943
Re: "man init" reports that MX init is systemd?
However, if I boot up the iso as a LiveUSB in Vbox I do get what you do. So whatever happens, happens during installation.
- Tue Dec 12, 2017 10:30 pm
- Forum: Bugs and Non-Package Requests Forum
- Topic: "man init" reports MX init is systemd? [SOLVED]
- Replies: 23
- Views: 4943
Re: "man init" reports that MX init is systemd?
Different result here. From an installed, unmodified RC1 in VirtualBox tim@mx1:~ $ cat /etc/mx-version MX-17.RC1_x64 Horizon December 10, 2017 tim@mx1:~ $ man init SYSTEMD(1) systemd SYSTEMD(1) NAME systemd, init - systemd system and service manager SYNOPSIS systemd [OPTIONS...] init [OPTIONS...] {C...
- Tue Dec 12, 2017 4:31 pm
- Forum: General
- Topic: MX-17 Release Candidate 1 - Feedback
- Replies: 183
- Views: 31792
Re: MX-17 Release Candidate 1 - Feedback
What lubuntu version was that? t'would be good to have it available.
- Tue Dec 12, 2017 1:56 pm
- Forum: General
- Topic: MX-17 Release Candidate 1 - Feedback
- Replies: 183
- Views: 31792
Re: MX-17 Release Candidate 1 - Feedback
Debian hasn't updated the firmware for that chipset in quite a while, and I've seen threads from other distros where using the newest firmware fixes your problem. I just downloaded the latest from the kernel git repository Download this, extract the 2 files, and copy them as root to /lib/firmware/br...
- Tue Dec 12, 2017 9:25 am
- Forum: General
- Topic: MX-17 Release Candidate 1 - Feedback
- Replies: 183
- Views: 31792
Re: MX-17 Release Candidate 1 - Feedback
Looks like the common factor in the ones where it doesn't work is that modesetting is enabled. All the working models have it unloaded.
- Mon Dec 11, 2017 11:52 pm
- Forum: General
- Topic: MX-17 Release Candidate 1 - Feedback
- Replies: 183
- Views: 31792
Re: MX-17 Release Candidate 1 - Feedback
Eureka! Grub Customizer changes that filename. It sets up 10_linux_proxy and moves the original 10_linux to /etc/grub.d/backup/10_linux *and* to /etc/grub.d/proxifiedScripts/linux I'm pretty sure it's the latter one that is used by 10_linux_proxy. So I guess there needs to be a test to see if the us...
- Mon Dec 11, 2017 10:08 pm
- Forum: General
- Topic: MX-17 Release Candidate 1 - Feedback
- Replies: 183
- Views: 31792
Re: MX-17 Release Candidate 1 - Feedback
Thank You. That narrows the problem down to the postinst script in mx-system.
It works on a LiveUSB or VM from iso. Let me see why it doesn't work on a hardware install...
It works on a LiveUSB or VM from iso. Let me see why it doesn't work on a hardware install...