Re: I get it now! (smbfs support)

From: Andreas Janssen (andreas.janssen_at_bigfoot.com)
Date: 02/14/04 

Date: Sat, 14 Feb 2004 19:47:08 +0100

Hello

Film (<film@eleven.org>) wrote:

> I've reinstalled WoodyR2 about 100 times now but at least I'm getting
> a handle on it.
>
> I discovered the key piece of information I was missing: The option
> to install the 2.4 kernel right from the boot CD1 and INSTEAD OF as a
> package upgrade later using dselect. It all makes sense now! It was
> not obvious to me that installing kernel 2.4 from the CD1 was
> possible.

It is always a good idea to carefully read the instructions before
hitting the enter key or clicking on "OK". The boot screen tells you
that you can hit F1, F2 or F3 to get more information.

> WHAT DOESN'T WORK: I thought the only way to install Debian was to
> boot to the CD1 and press enter. This installs a basic kernel 2.2.20
> without smbfs support despite smbfs showing up later as an option
> under dselect and no dependency warnings being issued.

The smbfs package only gives you the programs to mount the shares. The
dependency system cannot see if your kernel has smbfs support. Imagine
you use a self-compiled kernel that is not installed as a deb. It would
be annoying if you had to install another kernel only to get the smbfs
tools, wouldn't it?

> To fix this I was then trying to install a 2.4 kernel upgrade after
> the fact through dselect. This should probably work but I encountered
> the bizarre disappearing mstab problem and text display problem
> documented below. (I didn't bother to troubleshoot that install after
> discovering the fix below).
>
> WHAT DOES WORK: On a (or yet another) new install, I pressed F3 at
> the boot: prompt when I boot from the ISO image CD1 of Woody R2.
> There I selected the option bf24 which installs kernel 2.4 instead (as
> you pointed out in another post, selecting the 'vanilla' kernel option
> here might also include smbfs support but in a 2.2 kernel). What a
> difference! Going through the setup I eventually received a screen
> where I could select optional kernel device or module support (can't
> remember exactly what it was called.

The program is called modconf, and you can also run it after
installation from the command line to load additional modules. Normally
all it does is to load the driver and add it't name to /etc/modules so
it will be autoloaded at boot time.

> It was before the network setup). There I selected the optional
> smbfs support. After everything was complete smbfs (smbmount) works
> great. I mounted a Windows 2000 Server share with no problems.

Modconf is used to load modules. It probably would have worked without
loading it in modconf, because the module can be autoloaded when you
try to mount a smb share.

> Please note the unresolved problem with the fstab disappearing and the
> video display change when installing an optional 2.4 kernel using
> dselect. Based on what you said I should have been able to install
> the 2.4 kernel upgrade from dselect and achieved essentially the same
> results as installing the 2.4 kernel right from the CD.

You can install the kernel-image-2.4.18-bf2.4 package via dselect or
apt-get. This something you should do anyway, because right now, your
package management does not know about the installed installation
kernel. It will not upgrade it, although there is a security update for
that kernel available.

> I observed these problems during two different installations. I point
> this out in case there is a problem with the kernel upgrade package
> when installed over the default 2.2.20 CD install.

As for the video problem and the lost fstab, please read my previous
post in this thread, try the vga16:off parameter and tell us about
error messages regarding the fstab.

best regards
        Andreas Janssen 

-- 
Andreas Janssen
andreas.janssen@bigfoot.com
PGP-Key-ID: 0xDC801674
Registered Linux User #267976

Relevant Pages

  • Re: Upgrading from old Sarge (Testing) to Unstable
    ... > The package I'm most concerned about upgrading is the kernel. ... If you installed it via the debian tools, ie. via a .deb package it will be found in the 'Obsolete and locally created packages' section in aptitude. ... You can later install a new kernel or compile a new kernel, but as said in the release info, I strongly recommend to do this in a separate step: use your existing kernel to see if everything works fine; ... 50% Building Dependency Tree Reading extended state information... ...
    (Debian-User)
  • Yum upgrade from F8 to F9 with KDE desktop - installation notes
    ... nVidia drivers from Freshrpms, and I had to install the latest nVidia driver ... kernel in step 5; once I did that, the dkms package (which gets installed from ... Use your preferred method to install the above file: ...
    (Fedora)
  • SUSE Security Announcement: several kernel security problems (SUSE-SA:2005:044)
    ... please install the update packages. ... Use the following command to determine which kind of kernel is ... Download the kernel RPM package for your distribution with the ... Starting from SUSE LINUX 9.2, ...
    (Bugtraq)
  • Re: Using yum to update livna nvidia packages?
    ... >> Yum by default does an install on new kernels and modules. ... >> package and since that comes from livna the issue at that point would ... 6629 drive installed for the existing kernel 2.6.10-1.770. ...
    (Fedora)
  • Re: dselect and a Recent Experience
    ... > done while installing a single package. ... > Debian system and I used dselect to list the packages in order to find ... It found it and I started to install from there except I ... problems and thought I'd try aptitude. ...
    (Debian-User)
Quantcast