Frustrated... multiple problems

jaa1180 · 05-09-2004, 10:55 PM

I am just a bit frustrated... here are the problems that I cannot find solutions on.
First... I am using a C600 Dell Latitude. Libranet 2.8.1 installed, upgraded to Libranet upgrades then did other packages upgrade to unstable. Ok... here we go....
1. I cannot hook my deskjet 870c printer up... it will not print. Using adminmenu to add printer...
2. How in the world can I add a second NIC? I hook into a docking station and it has its own 3com nic. When I was using Fedora it had no problems with this other NIC... but now I cannot find it. Using adminmenu again to try to detect the second NIC.
3. Openoffice does not have an dictoniary. Plus has problems with printing... I am sure that it is related to the latter above.

I don't really want to give up on debian yet... but I am having a hard time finding info on problems.

Thanks in advance for any advice that someone may have.
-Jeff

elluva · 05-10-2004, 02:20 AM

OO-prob: Get the dictionaries from the OO-site, they are standard not included.

printing prob: Make sure you have cups installed and then take a browser and go to localhost:631 this is almost the easiest way to configure your printer... if that doesn't work, take the wizard in the KDE control center under peripherals -> printers

good luck,
Elluva

jaa1180 · 05-10-2004, 09:52 AM

ok... thanks elluva.

jaa1180 · 05-10-2004, 10:03 AM

another unusual problem... the last install it found my 56k modem in my PCMCIA slot. Now after a reinstall it does not find it on ttyS2? It will not find it at all. What could be the problem???

elluva · 05-10-2004, 10:06 AM

is PCMCIA enabled in the kernel and are the needed modules loaded?

jaa1180 · 05-10-2004, 10:37 AM

should be.. I am using the default kernel 2.4.21, but I am having problems compiling 2.6.5. Any who.. I am using 2.4.21 or 2.4.26. but that is a very good point. I will look and see if it is there. Thanks for the reminder.

vinay_s_s · 05-10-2004, 11:53 AM

default kernels SUCK!!!
compile ur own kernel with whatever u want , and remove whatever u dont want.

elluva · 05-10-2004, 12:58 PM

@vinay_s_s
owkay, that was a calm and and intelligent view [says Elluva with a very ironic undertone]. Though custom kernels do have a lot of advantages, default kernels do as well. I don't use libranet, I use slackware and there the default kernel is perfect if you don't have exotic hardware. It is fast and very low in memory.
So think before you send something like this, you know as well as I do that jaa1180 isn't helped with your post.

motub · 05-10-2004, 01:57 PM

Ooh, well said, elluva. I passed by before and kept going because I couldn't have provided such a calm and reasonable rebuttal. Glad you stopped by and said your piece for both of us

.

jaa1180 · 05-10-2004, 06:00 PM

mmm... I am trying to compile 2.6.3 and getting errors...
Now my eth0 is not working...
What is going on? Ok... breath... ok.. I will post the kernel errors as soon as I finish trying to compile 2.4.26. I hope it works. I set it back to the defaults then went in and removed everything I don't use or need.

jaa1180 · 05-10-2004, 11:34 PM

ok, got 2.4.26 to compile right for the most part. Now here is the kernel errors.
The NIC and printing is resolved...

Code:

cp snd-vxpocket.ko snd-vx-cs.ko snd-vxp440.ko snd-vx-cs.ko /usr/src/modules/alsa-driver/debian/alsa-modules-2.6.3/lib/modules/2.6.3/alsa/pcmcia/vx
cp: warning: source file `snd-vx-cs.ko' specified more than once
make[3]: Leaving directory `/usr/src/modules/alsa-driver/pcmcia/vx'
make[2]: Leaving directory `/usr/src/modules/alsa-driver/pcmcia'
make[1]: Leaving directory `/usr/src/modules/alsa-driver'
dh_testdir
dh_testroot
dh_installdirs
dh_link usr/share/doc/alsa-base usr/share/doc/alsa-modules-2.6.3
dh_strip
dh_compress
dh_fixperms
dh_installdeb
dh_shlibdeps
dh_gencontrol -- -v"1.0.1-1+libranet-custom.1"
dh_md5sums 
dh_builddeb --destdir=/usr/src/modules/alsa-driver/..
dpkg-deb: building package `alsa-modules-2.6.3' in `/usr/src/modules/alsa-driver/../alsa-modules-2.6.3_1.0.1-1+libranet-custom.1_i386.deb'.
=== KERNEL HEADERS IN /usr/src/linux/include
=== SMP=0 MODULES=1 MODVERSIONS=1 AGP=1
=== Compiling for machine i686
=== WARNING
=== WARNING Use 2.4.x kernels ONLY !
=== WARNING
cc -O2 -Wall -Wwrite-strings -Wpointer-arith -Wcast-align -Wstrict-prototypes -Wnested-externs -Wpointer-arith -D__KERNEL__ -DMODULE -fomit-frame-pointer -fno-strict-aliasing -DCONFIG_AGP -DCONFIG_AGP_MODULE -DCONFIG_DRM_SIS -DMODVERSIONS -include /usr/src/linux/include/linux/modversions.h -DEXPORT_SYMTAB -I/usr/src/linux/include -c gamma_drv.c -o gamma_drv.o

Error: compilation of extra kernel modules failed

What am I not doing???

vinay_s_s · 05-11-2004, 01:15 AM

jaa1180, dont use 2.6.3, it is buggy!! (in scsi stuff mainly , i think the scsi base has probs)

elluva, motub, after i have slackware on my system, everything is CUSTOM!!!
sorry i acted like a jerk at replying to that!! I understand that some people like it the way it is. But dont u think recompiling the kernel to suit ur needs and ur processor is really worht it ???

motub · 05-11-2004, 06:24 AM

Quote:

But dont u think recompiling the kernel to suit ur needs and ur processor is really worht it ???

Not if it's a production system, you have (paid) work (that is on a deadline) to get done (so the system needs to be up and running), you don't know anything about compiling a kernel (so it will take you longer and you may mess up), and the default kernel works fine. So what if it's a few seconds slower to boot?

elluva · 05-11-2004, 06:58 AM

@vinay_s_s
about your reaction: Thanks for admitting, no hard feelings

about the compiling issue:
Don't forget that you need a default kernel to boot your system for the first time. I know it is worth it, IF you have the time to do it. On a system for commercial usage, this isn't the case. The fact is that many people really don't care about those few extra seconds or that bit extra memory... Compiling your kernel should only be needed of you have special hardware or want to get your systen optimal, else it would be plain stupid.

@poor jaa1188
If the 2.6.x kernels don't work, take the good old 2.4.22, normally if something during compilation of a kernel goes wrong, it isn't your fault. When something doesn't work afterwards, then this usually means you forgot something during the selection of your kernel options or you still have to load the proper module. I recommend you to google your way to the module name and then just run 'modprobe modulename' as root. If modprobe gives errors, then this means that you didn't have a good config for your kernel.
A good strategy to get a good config file is at first selecting way to many options (but not compiled into the kernel, compiled into modules). Then gradually removing options of which you are sure you won't need them, till you have a good config. This way, you can get your kernel to work quite fast (and your able to optimize it if you want to).
Once you have a working configuration, be shure to copy the .config file as a backup somewhere, 'cause usually quite some work goes into getting a good .config, and you will have to recompile your kernel in the future for other things.

EDIT: I forgot to mention that you can put the that 'modprobe modulename' line in one of your bootscripts, on slack its /etc/rc.d/rc.modules, (but on debian if I remeber well its something else, don't remember what though). This way you're sure it is loaded on bootup...

motub · 05-11-2004, 07:58 AM

Quote:

dpkg-deb: building package `alsa-modules-2.6.3' in `/usr/src/modules/alsa-driver/../alsa-modules-2.6.3_1.0.1-1+libranet-custom.1_i386.deb'.
=== KERNEL HEADERS IN /usr/src/linux/include
=== SMP=0 MODULES=1 MODVERSIONS=1 AGP=1
=== Compiling for machine i686
=== WARNING
=== WARNING Use 2.4.x kernels ONLY !
=== WARNING

Well, I don't know why a module that specifically is for a 2.4 series kernel is being compiled by a 2.6 series kernel, but that would seem to be the problem.

Is there anything in the Libranet support solutions database or their forums about this?