LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 03-19-2008, 07:56 PM   #1
jerf
Member
 
Registered: Sep 2007
Posts: 46

Rep: Reputation: 15
Newbie Slackware Troubles


Hi all,

I'm very new to slackware and linux in general and was wondering about a few post install troubles Ive been having.

A couple of issues are concerning my boot/startup process.

There are two things I'd like to change about my LILO menu to start. One is the 2 minute timer that is the default after intsall i guess. I tried changing the timeout in lilo.conf to no avail. Second thing I'd like to change is the fact that I have to hit enter for the kernel to boot. I would prefer a list of kernel choices that would select and boot a default choice after 3 or 4 seconds.

After these minor issues I notice a few things funny about my startup log. First thing I notice that doesnt seem right are a number of messages like this:

Quote:
kobject_add failed for ehci_hcd with -EEXIST, don't try to register things with
the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
=======================
kobject_add failed for ehci_hcd with -EEXIST, don't try to register things with
the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
=======================
Not sure what that is telling me.

Second issue I'm having is long pause/hang following a message like:

Quote:
Triggering udev events: /sbin/udevtrigger --retry failed
I also have a question about inetd.conf. I edited the default file and commented out the following:

Quote:
time stream tcp nowait root internal
time dgram udp wait root internal
shell stream tcp nowait root /usr/sbin/tcpd in.rshd -L
login stream tcp nowait root /usr/sbin/tcpd in.rlogind
exec stream tcp nowait root /usr/sbin/tcpd in.rexecd
talk dgram udp wait root /usr/sbin/tcpd in.talkd
ntalk dgram udp wait root /usr/sbin/tcpd in.talkd
auth stream tcp wait root /usr/sbin/in.identd in.identd
After having commented out those lines I was unable to connect to my local network and I'm wondering what they are responsible for.

Lastly I'm wondering about my terminal in X. The terminal doesnt display my working path, it only shows the version of bash that I'm running. Now that I'm thinking about it, this would likely be changed in bash.rc correct? If so which value needs to be changed to what?

I know this is a few questions but I figured it would be best to post them together.

Thats all for now I suppose.

Thank you for any and all help. It is ofcourse appreciated.
 
Old 03-19-2008, 08:03 PM   #2
budword
Member
 
Registered: Apr 2003
Location: Wisconsin
Distribution: Switched to regualr Ubuntu, because I don't like KDE4, at all. Looks like vista on crack.....
Posts: 675

Rep: Reputation: 31
Run lilo again for the changes to take effect.
 
Old 03-19-2008, 08:59 PM   #3
DonnieP
Member
 
Registered: Jan 2008
Location: Richmond, VA USA
Distribution: Slackware
Posts: 144

Rep: Reputation: 29
Quote:
Originally Posted by jerf View Post
After these minor issues I notice a few things funny about my startup log. First thing I notice that doesnt seem right are a number of messages like this:
Quote:
kobject_add failed for ehci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
=======================
kobject_add failed for ehci_hcd with -EEXIST, don't try to register things with
the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
=======================
Not sure what that is telling me.
From CHANGES_AND_HINTS.TXT:
Quote:
As stated earlier, it is recommended that you use one of the generic kernels rather than the huge kernels; the huge kernels are primarily intended as "installer" and "emergency" kernels in case you forget to make an initrd. For most systems, you should use the generic SMP kernel if it will run, even if your system is not SMP-capable. <snip>

If you decide to use one of the huge kernels anyway, you will encounter errors like this:
kobject_add failed for uhci_hcd with -EEXIST, don't try to register
These occur because the respective drivers are compiled statically into the huge kernels but udev tries to load them anyway. These errors should be safe to ignore, but if you really don't want them to appear, you can blacklist the modules that try to load in /etc/modprobe.d/blacklist. However, make sure you remove them from the blacklist if you ever decide to use the (recommended) generic kernels.
 
Old 03-19-2008, 09:09 PM   #4
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Rep: Reputation: 70
Quote:
Originally Posted by jerf View Post
Lastly I'm wondering about my terminal in X. The terminal doesnt display my working path, it only shows the version of bash that I'm running. Now that I'm thinking about it, this would likely be changed in bash.rc correct? If so which value needs to be changed to what?
Check this site out:
http://www.pantz.org/software/shell/...ellprompt.html

You want to make your changes in ~/.profile. You should also source that file in ~/.bashrc

~/.bashrc
Code:
#!/bin/sh
if [ -f ~/.profile ]; then
        source ~/.profile
fi
Here's my ~/.profile
Code:
#!/bin/sh
alias ls='ls --color=always -Fsh -T 0'
alias snano='nano -Y sh'

PATH=~/ProgramBuilds:$PATH

case "$TERM" in
xterm*|rxvt*)
        # PROMPT_COMMAND Sets title.
        PROMPT_COMMAND='echo -ne "\033]0;$(date +%T) - ${USER}: ${PWD/$HOME/~}\007"'
        export PS1="\n[ \t ] \n\[\e[34;1m\]\u@\[\e[31;1m\]\H:\w\n\[\e[0m\]$> "
        ;;
screen*)
        PROMPT_COMMAND='echo -ne "\033]0;$(date +%T) - ${USER}: ${PWD/$HOME/~}\007"'
        export PS1="\nScreen Session: [ \t ]\n\[\e[34;1m\]\u@\[\e[31;1m\]\H:\w\n\[\e[0m\]$> "
        ;;
linux*)
        export PS1="\nPhil's Terminal Prefs \t\a\n\[\e[34;1m\]\u@\[\e[31;1m\]\H:\w\n\[\e[0m\]$> "
        ;;
*)
        # First section attempts to set title with "\n\[\e]2;"
        # Title ends at first '\n' after title escape sequence
        # If setting title not possible, then "\n\[\e]2" is ignored and the ';' is shown along with contents of title.
        # On some terminals the entire title section will be ignored.
        export PS1="\n\[\e]2;Phil's Terminal Prefs \t\n\[\e[34;1m\]\u@\[\e[31;1m\]\H:\w\n\[\e[0m\]$> "
        ;;
esac
The ls alias gives me fancy colors and always shows me file sizes. I run /bin/ls when I don't want them.

snano is my alias so that nano will show syntax highlighting for bash files that don't have a .sh extension. I use it all the time. You will have to edit /etc/nanorc to activate syntax highlighting.

~/ProgramBuilds is my user's local software builds. Since I put it in the beginning of my path I can have special scripts to start firefox, for instance, instead of using the global script at /usr/bin.

The prompt section will make your username and '@' blue and the hostname and current working directory red. I put the '$>' on a new line for readability and add a newline before the prompt for the same reason. I also have the time displayed in white so I always know what time it is in the command line (and at what time I ran certain commands). Notice that I modify my prompt depending on what kind of terminal it is executed in. Part of this is that I like to have an easy way to know what I am in based upon my prompt, but it is also useful to set the title bar in some kinds of terminals and not others. Note the title bar will contain the time, username, and cwd as well. Enjoy!

Don't forget to make the files executable.
 
Old 03-20-2008, 12:24 AM   #5
jerf
Member
 
Registered: Sep 2007
Posts: 46

Original Poster
Rep: Reputation: 15
Thanks for the advice folks.

I'm still wondering about how to fix my LILO menu, how to add kernels to my menu and such.

I'll try these things out, continue to read up and get back with any questions/results.
 
Old 03-20-2008, 02:08 AM   #6
mcnalu
Member
 
Registered: Dec 2006
Location: Glasgow, UK
Distribution: Slackware 13.37 and 13.1
Posts: 389

Rep: Reputation: 60
The easiest way to change lilo in slackware is to su to root and run liloconfig.

If you want to edit /etc/lilo.conf yourself, then have a read of man lilo.conf. To alter timeout you need to add/edit this line (number is in tenths of seconds):

timeout=100

Once you've edited lilo.conf, you can run lilo to install it (lilo -t will test it without installing, and the -v option will give you verbose info).

Adding kernels is easy enough. See my lilo.conf below (from slackware 11, with some kernels left over from my switch to 2.4 to 2.6 kernels). It was originally generated by liloconfig and then hacked by me quite a bit:

Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda5
compact
message = /boot/boot_message.txt
prompt
timeout = 100
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x64k
 vga=791
# End LILO global section

# Windows bootable partition config begins
#other = /dev/hda1
#  label = Windows
#  table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda5
  label = Linux
  append="resume=/dev/hda6"
  read-only
# Linux bootable partition config ends
image = /boot/vmlinuz-ide-2.4.33.3
  root = /dev/hda5
  label = Linux-ide-2.4
  read-only
image = /boot/vmlinuz-ajc-2.4.33.3
  root = /dev/hda5
  label = Linux-ajc-2.4
  read-only
image = /boot/vmlinuz-usb
  root = /dev/hda5
  label = Linux-usb
  read-only
 
Old 03-20-2008, 08:10 AM   #7
zoran119
Member
 
Registered: Dec 2007
Posts: 215

Rep: Reputation: 18
Quote:
Originally Posted by DonnieP View Post
From CHANGES_AND_HINTS.TXT:
How do we get the generic kernel going? Is this /boot/vmlinuz-generic-smp-2.6.21.5-smp? I had to create initrd.gz to get it going.

Also, how to you tell which kernel you have running? uname -r seems to give you the modules that you are running (2.6.21.5-smp) but you cannot tell if this is vmlinuz-generic-smp-2.6.21.5-smp or vmlinuz-huge-smp-2.6.21.5-smp. I am playing with both and sometimes forget which one have I selected from lilo menu.

Last edited by zoran119; 03-20-2008 at 08:12 AM.
 
Old 03-20-2008, 12:29 PM   #8
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Rep: Reputation: 70
Quote:
Originally Posted by zoran119 View Post
How do we get the generic kernel going? Is this /boot/vmlinuz-generic-smp-2.6.21.5-smp? I had to create initrd.gz to get it going.

Also, how to you tell which kernel you have running? uname -r seems to give you the modules that you are running (2.6.21.5-smp) but you cannot tell if this is vmlinuz-generic-smp-2.6.21.5-smp or vmlinuz-huge-smp-2.6.21.5-smp. I am playing with both and sometimes forget which one have I selected from lilo menu.
You only need an initrd if you need something to boot that is not built into your kernel (typically a filesystem compiled as a module is the reason).

lsmod lists the modules you are running.
uname -r prints the kernel release

The sure fire way to tell which kernel you are running is to compare the running kernel's config with a known kernel's config. The stock Slackware kernels have the proc config interface builtin.

example
Code:
zcat /proc/config.gz > CurrentConfig
diff -s CurrentConfig /boot/config-VERSION
Obviously you would need to replace VERSION so that you are testing the appropriate config. If they are the same then diff -s will tell you. To see the actual differences, if any, use the -u switch for a unified diff.

Edit:
I just wanted to add that if anybody reading this thread has never done so, they should check out OneBuck's Slackware Links page.

Last edited by shadowsnipes; 03-20-2008 at 12:31 PM. Reason: slackware links
 
Old 03-20-2008, 06:09 PM   #9
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,044
Blog Entries: 1

Rep: Reputation: 1369Reputation: 1369Reputation: 1369Reputation: 1369Reputation: 1369Reputation: 1369Reputation: 1369Reputation: 1369Reputation: 1369Reputation: 1369
Hi,
Quote:
Originally Posted by jerf View Post
Thanks for the advice folks.

I'm still wondering about how to fix my LILO menu, how to add kernels to my menu and such.

I'll try these things out, continue to read up and get back with any questions/results.
You would edit the '/etc/lilo.conf' file with a text editor as root; I would 'cd /etc' and 'vi lilo.conf'. Make your changes as desired then write the file.

After that you would need to run 'lilo' again;

Code:
example;
~#cd /etc
~#vi lilo.conf                       #edit lilo.conf, if need be
a modified example from 'man lilo.conf';
 # lilo.conf
              #
              #  global options:
              boot=/dev/hda
              prompt
              timeout=150
              lba32
              compact
              vga=normal
              root=/dev/hda1
              read-only
>>>           append="panic=15"              
              menu-title=" John's Computer "
              #
              #  bootable kernel images:
              image=/boot/zImage-1.5.99
                   label=try
              image=/boot/zImage-1.0.9
                   label=1.0.9
              image=/tamu/vmlinuz
                   label=tamu
                   initrd=initramdisk.img
                   addappend="panic=30" << add to global append
or                 append="panic=15"       <<< not both
                   root=/dev/hdb2
                   vga=ask
              #
              #  other operating systems:
              other=/dev/hda3
                   label=dos
                   boot-as=0x80    # must be C:
              other=/dev/hdb1
                   label=Win98
                   boot-as=0x80    # must be C:
              other=/dev/hdb5
                   label=os2
                   loader=os2_d
                   table=E:   # os2 sees as E:

~#lilo -v -t -b /dev/your_device     #sda, hda this will only test 
~#lilo -v -b /dev/your_device        #this will write MBR to your_device
Note: red arrows indicate sugesstions.

If you run 'liloconfig' your existing '/etc/lilo.conf' will be over written. You can 'man lilo.conf' and 'man lilo' for definitions and examples.

I would create a separate stanza for your new kernel and include 'addappend ="panic=15" within the stanza. Alien Bob suggests that you include it in the Global section of the '/etc/lilo.conf' file as part of the append. I think it would be wise if you expect to get oops. But if the system has been stable and you are just experimenting with your kernel then the only change would be in the stanza for the new kernel with the 'addappend='. I believe you can use 'append=' in each stanza without trouble either since the stanza 'append=' will override a global. The 'addappend=" will pass addition parameters to the kernel. This can sometimes be used to aid in debuging with other possible parameters you wish to pass. The time can be adjusted so you can get information before a reboot, so increase the 15 to a suitable time.
 
Old 03-21-2008, 06:34 AM   #10
jerf
Member
 
Registered: Sep 2007
Posts: 46

Original Poster
Rep: Reputation: 15
Here's an easy one.

If I do this...

Quote:
cp /boot/config-generic-smp-2.6.21.5-smp /usr/src/linux/.config
what/where is the .config file? If I cd to /usr/src/linux and ls I see no .config so what did I actually do?

Also

Quote:
Note

It is always a good idea to keep your old kernel in modules around, in the case that you have made a configuration error. If the to be compiled kernel has the same version number as the running kernel, you should seriously consider modifying the CONFIG_LOCALVERSION option. The string specified in this option is appended to the version name. For example, if the kernel has version 2.6.21.6, and CONFIG_LOCALVERSION is set to "-smp-ddk", the kernel version will be 2.6.21.6-smp-ddk.

If you don't modify the version in this manner, the installation of modules from the new kernel will overwrite the modules from the running kernel. This is highly uncomfortable if you need to fall back to the old kernel.
http://www.slackbasics.org/html-sing...cs.html#kernel

I'm not clear on how to modify CONFIG_LOCALVERSION or what the author really means.

I'm attempting to use a leaner kernel and I'm sucha noob.

Thanks again.
 
Old 03-21-2008, 06:40 AM   #11
mcnalu
Member
 
Registered: Dec 2006
Location: Glasgow, UK
Distribution: Slackware 13.37 and 13.1
Posts: 389

Rep: Reputation: 60
Do ls -a to list hidden files starting with .

Other than that, just treat them like all other files, e.g. less .config to view it.

Quote:
I'm attempting to use a leaner kernel and I'm sucha noob.
We all were once. Do lots of reading, go slow, back things up and don't
experiment on a machine that you depend on!
 
Old 03-21-2008, 11:05 AM   #12
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Rep: Reputation: 70
Quote:
Originally Posted by jerf View Post

http://www.slackbasics.org/html-sing...cs.html#kernel

I'm not clear on how to modify CONFIG_LOCALVERSION or what the author really means.

I'm attempting to use a leaner kernel and I'm sucha noob.

Thanks again.
CONFIG_LOCALVERSION can be set by changing
General Setup -> Local Version()
in the config (if you aren't sure what to use then use
make menuconfig

You only need to append a local version if you are compiling a kernel image for a kernel version you already have. This is so you can have separate module directories under /lib/modules. The stock slackware smp kernels have a '-smp' local version appended (notice the separate module directory?).

As a tip, I suggest copying (use -a switch) your entire linux sources somewhere under your home directory and working with those as your normal user. Don't get root involved until you install stuff. This is generally the way you should compile everything if doing it manually. For software other than kernel I recommend seeing if there is a build script at slackbuilds.org.

The reason I say leave your original kernel sources alone is that you may want compile something that depends on them the way they are now (say if you are going to compile a graphics driver, ndiswrapper, vmware driver, etc).

The concise steps you need to compile and install your new kernel are:

(from the kernel directory as NORMAL user)
Code:
make mrproper

# Copy a config over so you don't start from scratch
cp /boot/config-VERSION .config
# - or -
zcat /proc/config.gz > .config

make menuconfig

# Select the options you need for everything
# Use the Help if you don't know what something is.

make
as ROOT
Code:
make modules_install
cp arch/i386/boot/bzImage /boot/vmlinuz-VERSION-NAME-BLAH-BLAH
cp System.map /boot/System.map-VERSION-NAME-BLAH-BLAH
cp .config /boot/config-VERSION-NAME-BLAH-BLAH
Then you need to add your new kernel to /etc/lilo.conf and then run lilo.

If you like vi editor then use that, but since you are new to this stuff I think you will nano better. CTRL+k cuts a line into a buffer. Do this for all the old kernel lines and then CTRL+u "uncuts". Do this to restore your old lines, and then do it a second to make a copy of them. Edit them for your new kernel. To cut specific parts of a line use CTRL+^ to begin a place to mark.

nano also has syntax highlighting but you will need to modify /etc/nanorc. If you don't have one you can find one under usr/doc/nano-VERSION/nanorc.sample. Uncomment the lines at the bottom for syntax. Do note that you will have to manually specify syntax for sh files that don't have a .sh extension (such as /etc/lilo.conf). That's what my snano alias is for that I showed you earlier.

Either way, though, you should have a basic understanding of vi since it is a universal editor.
 
Old 03-21-2008, 05:52 PM   #13
jerf
Member
 
Registered: Sep 2007
Posts: 46

Original Poster
Rep: Reputation: 15
Hi there.

Shadowsnipes could you clarify?

Quote:
As a tip, I suggest copying (use -a switch) your entire linux sources somewhere under your home directory
I thought I was copying my sources to home but now in my home directory is (in bright green)linux@

is that what you meant for me to do? it seems like a simple idea, copy my sources to another dir and work from them leaving the old intact but I think Im doing something wrong.

Thanks.
 
Old 03-21-2008, 08:23 PM   #14
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.0
Posts: 2,242

Rep: Reputation: 614Reputation: 614Reputation: 614Reputation: 614Reputation: 614Reputation: 614
jerf, if you simply use `cp file /path/to/destination/` it'll only copy the one file. However, if you use `cp -a folder /path/to/destination/` it'll copy the folder and everything in it to the destination. Hope that helps.
 
Old 03-22-2008, 12:09 AM   #15
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Rep: Reputation: 70
jerf,

looks like T3slider already answered your question. In general, though, if you don't understand how to use a command the first thing you should do is
Code:
man command
and read the manual page. Most of them are online as well.

Even if you have used linux for years you will probably still have to occasionally (if not frequently) read a man page to find some command argument. I don't think anybody has memorized them all.

When you are using a man page use the '/' key and type a word to search for it. This will save you a lot of time when reading long pages.
 
  


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
Newbie with login troubles mclieu Fedora 14 03-07-2005 04:27 PM
NFS newbie troubles hiwa Linux - Networking 3 10-12-2004 10:34 AM
Newbie hardware troubles ... czechripper Linux - Newbie 6 10-18-2003 07:46 AM
Newbie modem troubles Theylan Linux - Hardware 2 09-24-2003 08:28 PM
Newbie in troubles CleonII Linux - General 3 05-15-2003 07:22 AM


All times are GMT -5. The time now is 07:20 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