Re: Synaptec connection problem




Elijah

The contents of my etc/hosts file is

127.0.0.1 localhost.localdomain localhost ubuntujohn

# The following lines are desirable for IPv6 capable
hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Thanks
--- ubuntu-users-request@xxxxxxxxxxxxxxxx wrote:

Send ubuntu-users mailing list submissions to
ubuntu-users@xxxxxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web,
visit


https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
or, via email, send a message with subject or body
'help' to
ubuntu-users-request@xxxxxxxxxxxxxxxx

You can reach the person managing the list at
ubuntu-users-owner@xxxxxxxxxxxxxxxx

When replying, please edit your Subject line so it
is more specific
than "Re: Contents of ubuntu-users digest..."


Today's Topics:

1. I'm afraid to reboot. menu.lst problem.
(Dapper) (Scott)
2. Re: Evolution - Memory Hog (Michael M.)
3. Re: Synaptec connection problem (Elijah
Lofgren)
4. Re: I'm afraid to reboot. menu.lst problem.
(Dapper) (albi)
5. Re: I'm afraid to reboot. menu.lst problem.
(Dapper)
(louis_nichols)
6. Re: [Off Topic] Re: Linux security (Jim
Richardson)
7. Re: Evolution - Memory Hog (Richard)
8. Re: I'm afraid to reboot. menu.lst problem.
(Dapper) (Sef)
9. Re: Evolution - Memory Hog (phummers)
10. Bluetooth mouse in Dapper (Cameron Hutchison)
11. Re: Has Ubuntu Replaced Windows on Your Box?
(phummers)



----------------------------------------------------------------------

Message: 1
Date: Fri, 05 May 2006 16:38:59 -0700
From: Scott <listboi@xxxxxxxxxxxxxxxxxxx>
Subject: I'm afraid to reboot. menu.lst problem.
(Dapper)
To: Ubuntu Help and User Discussions
<ubuntu-users@xxxxxxxxxxxxxxxx>,
Kubuntu Users <kubuntu-users@xxxxxxxxxxxxxxxx>
Message-ID: <445BE213.50608@xxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8

Or at least I think it is a problem.....

Several days ago a Kernel upgrade came out
(linux-image-2.6.15-22-686).

I upgraded.

I then found that there wasn't any corresponding
linux-restricted-modules file yet.

Since so I went back to using the previous kernel
which I had not
uninstalled.

After that, every time I booted/rebooted my computer
I'd wind up with
the newer
kernel unless I quickly hit the escape key and
selected the older one..

That was getting annoying so I'd planned on editing
my menu.lst file to
add more time to the timeout.

But after a day or so I noticed that if I didn't
catch it and the newer
kernel would boot, I'd not be able to get past the
usplash screen.

Strangely it would behave normally but instead of
taking me to the display
manager it would restart but appear blank (just the
logo would be there).

My computer would then freeze and I'd have to
reboot.

Upon rebooting I'd be sure to catch it in time and
go back to the older
kernel.

Finally I got tired of that so I just now
uninstalled the older kernel so
there would only be one for grub to choose from and
I'd not have that
problem anymore.

Now for some strange reason I felt compelled to take
a look at my
menu.lst file right after uninstalling the newer
kernel (I normally
never bother looking at it after installing a
kernel) and was a bit
alarmed at what I saw.

If I'm reading this correctly, the next time I boot,
GRUB will attempt
to boot not the kernel I have installed and not the
one I just
uninstalled, but the default kernel that was
installed when I first
installed Ubuntu to begin with (that would be
-2.6.15-20-386)! I got
rid of that ages ago.

I'd edit menu.lst to correct it, but I'm not 100%
sure this is a problem
(only 99%).

On the other hand the files it lists are nowhere to
be found in /boot
(which makes perfect sense).

Maybe I'm just misreading menu.lst?

I'm really afraid of screwing this up further
(assuming it is now). I've
never known what to do previously when I'd start my
computer and
couldn't get past GRUB (I'm talking well before
Ubuntu). I'd end up
reinstalling my complete distro from scratch (which
seems a bit drastic)
but I know nothing about how to "rescue" in those
cases.


Anyhow, here is the contents of my.menu.lst file.

Thanks. Any help would be appreciated.

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM.
Numbering starts from
0, and
# the entry number 0 is the default if the command
is not used.
#
# You can specify 'saved' instead of a number. In
this case, the default
entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change
this entry to 'saved'
or your
# array will desync and will not let you boot your
system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before
automatically booting the
default entry
# (normally the first entry defined).
timeout 3

## hiddenmenu
# Hides the menu by default (press ESC to see the
menu)
hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file,
disable all interactive
editing
# control (menu entry editor and command-line) and
entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5
$1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)

=== message truncated ===


__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
https://lists.ubuntu.com/mailman/listinfo/ubuntu-users



Relevant Pages

  • Re: Safe remote kernel install howto (Re: [Bugme-new] [Bug 6613] New: iptables broken on 32-
    ... once and reboot the default kernel next time. ... Force reboot on any panic after 10 seconds: ... And oh, yes, for this to work, in lilo.conf the new entry should be ... lilo.conf, restore the proper label, set proper order of entries if needed ...
    (Linux-Kernel)
  • On-disk indexing for "Project Ideas" page
    ... The kernel usually does the lookup by starting at the beginning ... of the directory and going through, comparing each entry in turn. ... name cache described in Section 6.6. ...
    (freebsd-current)
  • [PATCH] ppc32: rename head_e500.S to head_fsl_booke.S
    ... * Kernel execution entry point code. ... Initial PowerPC version. ... -/* Note that the SPE support is closely modeled after the AltiVec ...
    (Linux-Kernel)
  • Re:SOLVVED vinum crashes the Box... WRONG POSTING
    ... vinum crashes the Box by using more then ten disks on ... > With this configuration vinum crashes the Machine with this Message: ... > I'm going to enable the kernel debugger now... ... >> while devfs rules works for those, but they vanish on reboot. ...
    (freebsd-stable)
  • Re: Grub not right on new install.
    ... # Set the default entry to the entry number NUM. ... # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST ... ## should update-grub create alternative automagic boot options ... Linux install includes an entry for Windows in the menu.list ...
    (Ubuntu)