Poor man's graphical boot in Slackware revisited...
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 3,129
Original Poster
Rep:
Don't know why setterm -default is not resetting your terminal see the setterm man page for full usage, you may just have to reset all the changes that setterm does in rc.S-Wrap manually ie
Code:
setterm -msg on -cursor on -foreground white
Your English is better than my Brazilian ( or is it Portuguese in Brazil? )
Last edited by Keith Hedger; 08-07-2010 at 05:01 PM.
Don't know why setterm -default is not resetting your terminal see the setterm man page for full usage, you may just have to reset all the changes that setterm does in rc.S-Wrap manually ie
Code:
setterm -msg on -cursor on -foreground white
Your English is better than my Brazilian ( or is it Portuguese in Brazil? )
I've done what you posted so but have not tested since I'm on the net ...
Thanks for all your hard work.
I tried this out and it appears to be working here
just fine except for a few odd messages in the S_LOG file
(the ones marked with an "*" below).
Code:
Starting rc.S
Triggering udev events: /sbin/udevadm trigger --action=add
Loading fuse module.
Mounting fuse control filesystem.
Setting system time from the hardware clock (localtime).
Testing root filesystem status: read-only filesystem
Checking root filesystem:
fsck from util-linux-ng 2.17.2
/dev/sdb1: clean, 291586/2379216 files, 1735178/9506455 blocks (check after next mount)
Remounting root device with read-write enabled.
/dev/sdb1 on / type ext3 (rw)
Running /etc/rc.d/rc.modules-2.6.33.4-smp:
Module dependencies up to date (no new kernel modules found).
Checking non-root filesystems:
fsck from util-linux-ng 2.17.2
usbfs on /proc/bus/usb type usbfs (rw)
Mounting non-root local filesystems:
tmpfs on /dev/shm type tmpfs (rw)
stty: standard input: Invalid argument
Using /etc/random-seed to initialize /dev/urandom.
Starting rc.M
Going multiuser...
Updating shared library links: /sbin/ldconfig &
* cannot (un)set powersave mode
* [9;15][14;60]Starting PCMCIA services:
<PCIC already loaded>
Starting sysklogd daemons: /usr/sbin/syslogd /usr/sbin/klogd -c 3 -x
Updating X font indexes: /usr/bin/fc-cache -f &
Triggering udev events: /sbin/udevadm trigger --type=failed
Starting Internet super-server daemon: /usr/sbin/inetd
Starting OpenSSH SSH daemon: /usr/sbin/sshd
Starting ACPI daemon: /usr/sbin/acpid
Updating MIME database: /usr/bin/update-mime-database /usr/share/mime &
Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system
Starting HAL daemon: /usr/sbin/hald --daemon=yes
Updating gtk.immodules for i486-slackware-linux:
/usr/bin/gtk-query-immodules-2.0-32 > /etc/gtk-2.0/i486-slackware-linux/gtk.immodules
Updating gdk-pixbuf.loaders for i486-slackware-linux:
/usr/bin/gdk-pixbuf-query-loaders-32 > /etc/gtk-2.0/i486-slackware-linux/gdk-pixbuf.loaders
Updating pango.modules for i486-slackware-linux:
/usr/bin/pango-querymodules-32 > /etc/pango/i486-slackware-linux/pango.modules
Loading OSS compatibility modules for ALSA.
Loading ALSA mixer settings: /usr/sbin/alsactl restore
Starting gpm: /usr/sbin/gpm -m /dev/mouse -t imps2
* stty: standard input: Invalid argument
EOFEOF
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 3,129
Original Poster
Rep:
Thanks for the kind words!
Ignore the strange symbols in the log file these are just escape codes that some startup progs/services use to pretty print their output.
If you look at about line 24 of rc.M you will find this
Code:
# Screen blanks after 15 minutes idle time, and powers down in one hour
# if the kernel supports APM or ACPI power management:
/bin/setterm -blank 15 -powersave powerdown -powerdown 60
obviously your kernel ( like mine doesn't support the power managment ) either ignore it comment it out or delete the offending line it doesn't seem to do any harm so I'd be inclined to just ignore it.
The last bit "* stty: standard input: Invalid argument" I don't know I don't get that check your rc.M rc.local file to find out what could be causing it and maybe repost.
Last edited by Keith Hedger; 08-10-2010 at 11:22 AM.
Reason: missed a bit
Ignore the strange symbols in the log file these are just escape codes that some startup progs/services use to pretty print their output.
If you look at about line 24 of rc.M you will find this
Code:
# Screen blanks after 15 minutes idle time, and powers down in one hour
# if the kernel supports APM or ACPI power management:
/bin/setterm -blank 15 -powersave powerdown -powerdown 60
obviously your kernel ( like mine doesn't support the power managment ) either ignore it comment it out or delete the offending line it doesn't seem to do any harm so I'd be inclined to just ignore it.
The last bit "* stty: standard input: Invalid argument" I don't know I don't get that check your rc.M rc.local file to find out what could be causing it and maybe repost.
I'll double check...
although I do not recall seeing these
when booting without the wrap scripts:
cannot (un)set powersave mode
-and-
stty: standard input: Invalid argument
rc.local is empty except for some comments and
rc.M has not been modified by me.
And the powersave stuff on the monitor is working...
at least it does what the comment says in rc.M
(screen blanks after 15min and powers off after 60).
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 3,129
Original Poster
Rep:
Well I've tracked down the "stty: standard input: Invalid argument" error it is comming from the rc.sysvinit script ( I commented out mine when debugging M-Wrap and as I don't have any sys v scripts I left them commented out hence I didn't get the error ) It does say in the script
Quote:
this is primarily intended to support commercial software, though, and probably shouldn't be considered bug free.
so just make the script unexecutable with
Code:
sudo chmod -x /etc/rc.d/rc.sysvinit
And the error message goes away.
Should this be sent as bug report to slackware?
People who use Slackware would like to have a graphic boot?
I watch a few guesses on the subject, but otherside, many visits ...
Of course I'm referring to those who are using slackware desktop ...
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 3,129
Original Poster
Rep:
Quote:
Originally Posted by afreitascs
Keith Hedger
A curious question, I'm really curious ...
People who use Slackware would like to have a graphic boot?
I watch a few guesses on the subject, but otherside, many visits ...
Of course I'm referring to those who are using slackware desktop ...
Please consider the question as technique.
Thank you
Sorry I don't understand the question can you rephrase it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.