Search found 8 matches
- 20 Aug 2017, 15:06
- Forum: Porteus Praisers
- Topic: 4 months straight on RAMboot
- Replies: 2
- Views: 2349
4 months straight on RAMboot
guest@porteus:~$ uptime -p up 15 weeks, 1 day, 21 hours, 57 minutes And this is supposed to be my disposable distro, I'm using it almost as my DD! Interestingly, this was done on KDE which seems to have specific issues that the other 3 DEs don't have. What's the developer's intended "hero version" ...
- 18 Jan 2017, 13:05
- Forum: Development
- Topic: printing-3.2 for porteus 3.2
- Replies: 220
- Views: 63779
Re: printing-3.2 for porteus 3.2
Tested the latest module on 64bit 3.2.2 with KDE5 on an Epson L655 Inktank printer. The printing works. Including USB/Wifi printing, Dupex Printing, Print Quality Settings and Ink Level Readings are all working. If all that works on a L655, then it's quite likely that the entire L-series Ink Tank ra...
- 18 Jan 2017, 10:53
- Forum: Bug Reports
- Topic: Porteus-v3.2.2 bug reports here
- Replies: 214
- Views: 58773
Re: Porteus-v3.2.2 bug reports here
Using 3.2.2 64Bit with KDE5 on a Dell XPS 13 ... Doesn't Work: - Screen resolution setting missing in the KDE5 menu(However, changing the resolution via xrandr works) .... Anyone have any fixes for this? The command kscreen doesn't exist(as root) and kscreen_backend_launcher gives this error: kscre...
- 18 Jan 2017, 10:32
- Forum: Newbie questions
- Topic: Hardware specific cheatcode/modules
- Replies: 4
- Views: 1533
Re: Hardware specific cheatcode/modules
You can try add test to your /etc/rc.d/rc.local For chosen hardware execute in terminal dmidecode -t 1 | grep "Serial Number" next copy your Serial Number, replace mynum below with copied Serial Number, and paste all to /etc/rc.d/rc.local: check1=`dmidecode -t 1 | grep "Serial Number"` [[ $check1 =...
- 15 Jan 2017, 17:14
- Forum: Newbie questions
- Topic: Hardware specific cheatcode/modules
- Replies: 4
- Views: 1533
Hardware specific cheatcode/modules
Is it possible to trigger specific cheatcodes or load specific modules based on the detected hardware? I use Porteus as a Live OS on multiple systems and some of the blacklists in my modprobe config are contradictory between the various systems. Also certain optimizations for HiDPI displays will loo...
- 06 Jan 2017, 09:50
- Forum: Bug Reports
- Topic: Porteus-v3.2.2 bug reports here
- Replies: 214
- Views: 58773
Re: Porteus-v3.2.2 bug reports here
Using 3.2.2 64Bit with KDE5 on a Dell XPS 13 Works: - Wifi(after blacklisting wl) - Bluetooth Send/Receive - Touchscreen Single Touch(Multi touch probably works, but no application to test it on) - All ACPI functions triggered from the Fn keys(Backlight, Keyboard backlight, Volume, Wifi On/Off) Does...
- 06 Jan 2017, 08:13
- Forum: General chat
- Topic: Prevent Power Button from Shutting Down System
- Replies: 5
- Views: 1947
Re: Prevent Power Button from Shutting Down System
There is an acpi handler file at /etc/acpi/acpi_handler.sh Try changing the /sbin/init 0 line to something else. Elegant fix. Thanks mate. Is there a recommended runlevel though? I've set it as runlevel 1, and pressing the power button as the guest user successfully triggers the power menu in GUI m...
- 05 Jan 2017, 18:38
- Forum: General chat
- Topic: Prevent Power Button from Shutting Down System
- Replies: 5
- Views: 1947
Re: Prevent Power Button from Shutting Down System
hi cttan, you have to blacklist 'button' kernel driver: echo -en "Prevent system from going down:\nblacklist button" >/etc/modprobe.d/button.conf Cheers Sorry to bump an old thread(figured it's still better than to start a new one). How can this be achieved on 3.2.2? My family and I use Porteus exc...