LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-07-2010, 04:17 PM   #16
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 432

Rep: Reputation: 30

Quote:
Originally Posted by Keith Hedger View Post
Not too sure what you're asking but at the beginning of rc.S-Wrap the cursor is turned off for the vtty, this is the line:
Code:
setterm -msg off -cursor off -foreground red
at the end of rc.M-Wrap the terminal is set to the default
Code:
setterm -default
Which should have turned the cursor back on you may have to turn it back on explicitly ie
Code:
setterm -cursor on
Hope this helps
Yes, his response was a very useful :-)

Quote:
setterm -cursor on
resolve, but the letters are green and not white ...

With
Quote:
setterm -default
no cursor

Ha... my english is very bad

Thanks
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 08-07-2010, 04:59 PM   #17
Keith Hedger
Member
 
Registered: Jun 2010
Location: Devon,UK
Distribution: Linux From Scratch, Slackware64,
Posts: 833

Original Poster
Rep: Reputation: 167Reputation: 167
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.
 
Old 08-07-2010, 05:35 PM   #18
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 432

Rep: Reputation: 30
Quote:
Originally Posted by Keith Hedger View Post
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 ...

Quote:
setterm -msg on -cursor on -foreground white
Brazil uses the Portuguese :-)

Many Thanks
 
Old 08-07-2010, 09:22 PM   #19
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 432

Rep: Reputation: 30
Trying to be more accurate ...

Quote:
"setterm -default"
no cursor (also the letters are green)

Quote:
"setterm msg-off-off-cursor foreground red"
There's cursor (the letters are white, but the cursor is green in tty1)

Quote:
"setterm -cursor on
setterm -default"
Same as "setterm -msg on -cursor on -foreground white "

Thanks

Last edited by afreitascs; 08-07-2010 at 11:00 PM. Reason: typing error
 
Old 08-10-2010, 10:59 AM   #20
aocab
Member
 
Registered: Nov 2009
Location: Heart of Texas
Distribution: Slackware-current
Posts: 138

Rep: Reputation: 30
@Keith Hedger,

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
Again, Thanks and Cheers
 
Old 08-10-2010, 11:19 AM   #21
Keith Hedger
Member
 
Registered: Jun 2010
Location: Devon,UK
Distribution: Linux From Scratch, Slackware64,
Posts: 833

Original Poster
Rep: Reputation: 167Reputation: 167
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
 
Old 08-10-2010, 09:13 PM   #22
aocab
Member
 
Registered: Nov 2009
Location: Heart of Texas
Distribution: Slackware-current
Posts: 138

Rep: Reputation: 30
Quote:
Originally Posted by Keith Hedger View Post
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.
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).

Cheers
 
Old 08-10-2010, 10:39 PM   #23
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 432

Rep: Reputation: 30
Also appears in the mine, but I did not give importance ...
 
Old 08-10-2010, 11:23 PM   #24
aocab
Member
 
Registered: Nov 2009
Location: Heart of Texas
Distribution: Slackware-current
Posts: 138

Rep: Reputation: 30
Quote:
Originally Posted by afreitascs View Post
Also appears in the mine, but I did not give importance ...
No problem. It never hurts to ask.
At least I know now that it's not unique to just my machine.
Cheers
 
Old 08-11-2010, 12:28 PM   #25
Keith Hedger
Member
 
Registered: Jun 2010
Location: Devon,UK
Distribution: Linux From Scratch, Slackware64,
Posts: 833

Original Poster
Rep: Reputation: 167Reputation: 167
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?
 
Old 08-13-2010, 11:52 AM   #26
Keith Hedger
Member
 
Registered: Jun 2010
Location: Devon,UK
Distribution: Linux From Scratch, Slackware64,
Posts: 833

Original Poster
Rep: Reputation: 167Reputation: 167
Just updated the LQ Wiki page to include the shutdown wrapper
 
Old 08-13-2010, 10:55 PM   #27
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 432

Rep: Reputation: 30
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
 
Old 08-14-2010, 04:01 AM   #28
Keith Hedger
Member
 
Registered: Jun 2010
Location: Devon,UK
Distribution: Linux From Scratch, Slackware64,
Posts: 833

Original Poster
Rep: Reputation: 167Reputation: 167
Quote:
Originally Posted by afreitascs View Post
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.
 
Old 08-14-2010, 11:52 PM   #29
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 432

Rep: Reputation: 30
Quote:
Originally Posted by Keith Hedger View Post
Sorry I don't understand the question can you rephrase it.
Sorry, I think my question is not in accordance with your topic .
 
Old 08-15-2010, 03:39 AM   #30
veeall
Member
 
Registered: May 2007
Location: Estonia
Distribution: Slackware 12.1, slackware64-current
Posts: 252

Rep: Reputation: 43
I tried this howto and it worked fine and simple in my box. Big thanks!

Any info if it's possible to use this with kms(intel) too?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Poor man's graphical boot in Slackware 13.X... LuckyCyborg Slackware 38 05-21-2011 11:33 AM
Poor Man's VPN on smartphone - Putty Fatal error WSAEventSelect(): SOCKET_ERROR " Wildebeest2010 Linux - Software 1 02-15-2010 01:41 PM
Display a picture file as a poor-man's splash screen fudam Linux - General 1 12-01-2006 06:15 AM
Wanna do a poor man's slacktop... papa0822 Linux - Laptop and Netbook 2 10-12-2004 06:59 PM
Poor man's dual monitor (using two linux boxes)) alexferrer Linux - General 8 05-22-2003 03:02 PM


All times are GMT -5. The time now is 04:25 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration