83mercedes

thanks, # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> /dev/hda2 / ext3 errors=remount-ro 0 1 /dev/hda3 none swap sw 0 0 proc /proc proc defaults 0 0 /dev/fd0 /floppy auto user,noauto 0 0 /dev/cdrom /cdrom iso9660 ro,user,noauto 0 0 # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)', # --------------- `install-mbr(8)', `/usr/share/doc/lilo/', # and `/usr/share/doc/mbr/'. # +---------------------------------------------------------------+ # | !! Reminder !! | # | | # | Don't forget to run `lilo' after you make changes to this | # | conffile, `/boot/bootmess.txt', or install a new kernel. The | # | computer will most likely fail to boot if a kernel-image | # | post-install script or you don't remember to run `lilo'. | # | | # +---------------------------------------------------------------+ # Support LBA for large hard disks. # lba32 # Overrides the default mapping between harddisk names and the BIOS' # harddisk order. Use with caution. #disk=/dev/hde # bios=0x81 #disk=/dev/sda # bios=0x80 # Specifies the boot device. This is where Lilo installs its boot # block. It can be either a partition, or the raw device, in which # case it installs in the MBR, and will overwrite the current MBR. # boot=/dev/hda # Specifies the device that should be mounted as root. (`/') # root=/dev/hda2 # Enable map compaction: # Tries to merge read requests for adjacent sectors into a single # read request. This drastically reduces load time and keeps the # map smaller. Using `compact' is especially recommended when # booting from a floppy disk. It is disabled here by default # because it doesn't always work. # # compact # Installs the specified file as the new boot sector # You have the choice between: bmp, compat, menu and text # Look in /boot/ and in lilo.conf(5) manpage for details # install=/boot/boot-menu.b # Specifies the location of the map file # map=/boot/map # You can set a password here, and uncomment the `restricted' lines # in the image definitions below to make it so that a password must # be typed to boot anything but a default configuration. If a # command line is given, other than one specified by an `append' # statement in `lilo.conf', the password will be required, but a # standard default boot will not require one. # # This will, for instance, prevent anyone with access to the # console from booting with something like `Linux init=/bin/sh', # and thus becoming `root' without proper authorization. # # Note that if you really need this type of security, you will # likely also want to use `install-mbr' to reconfigure the MBR # program, as well as set up your BIOS to disallow booting from # removable disk or CD-ROM, then put a password on getting into the # BIOS configuration as well. Please RTFM `install-mbr(8)'. # # password=tatercounter2000 # Specifies the number of deciseconds (0.1 seconds) LILO should # wait before booting the first image. # delay=20 # You can put a customized boot message up if you like. If you use # `prompt', and this computer may need to reboot unattended, you # must specify a `timeout', or it will sit there forever waiting # for a keypress. `single-key' goes with the `alias' lines in the # `image' configurations below. eg: You can press `1' to boot # `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'. # # message=/boot/bootmess.txt prompt timeout=150 # prompt # single-key # delay=100 # timeout=100 # Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>) # # vga=ask # vga=9 # vga=normal # Kernel command line options that apply to all installed images go # here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in # the Linux kernel `Documentation' directory. # append="" # Boot up Linux by default. # default=Linux image=/vmlinuz initrd=/initrd.img label=Linux read-only # restricted # alias=1 image=/vmlinuz label=LinuxOLD read-only optional # restricted # alias=2 # If you have another OS on this machine to boot, you can uncomment the # following lines, changing the device name on the `other' line to # where your other OS' partition is. # # other=/dev/hda4 # label=HURD # restricted # alias=3 other=/dev/hda1 label="WinNT(hda1)" I couldn't make a working 'options' file, so I deleted it, I will have to try it again. I uninstalled nvidia, because I thought it might be messing me up, but I can install it again later.

All I really did was change the kernel and uninstall nvidia. The only issue I really have now, at the moment, is getting CD-writer usable. For example, I put a data cd in the drive, right click to mount it, and get this: Could not mount device. The reported error was: mount: wrong fs type, bad option, bad superblock on /dev/cdrom, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) I still don't know why it worked on Woody, but it did...

I am now running Debian Sid with the test kernel. I have removed the nvidia driver. Still cannot make cd-writer or DVD player be recognized, or work in any way. The cd-writer worked in Debian woody. I have gone over the previous posts, and nothing seems to help. Still running lilo: append="hdc=ide-scsi devfs=mount" # Boot up Linux by default. # default=Linux image=/vmlinuz initrd=/initrd.img label=Linux read-only # restricted # alias=1 Maybe if I could start from scratch, one step at a time?? Thanks

Update, I got some rest, and am back at it. Here's what's up: I redid the install, this time carefully picking out the appropriate modules for my system, and got 2.4.18-bf2.4 to work vey well, including cd-writer, and dist-upgraded, (love kde3!) only problem is, cannot make X work with NVIDIA, even after I got nvidia installed by providing the IGNORE_CC_MISMATCH=1 and the whole path of the kernel-source. Another weird thing about the stable version of Debian on my machine, it comes with kde2 (I think), but I couldn't get into X with or without nvidia. No X, no way! Strange??? What else I did was install the 2.4.21-4-k7 kernel. This kernel WILL work with nvidia, however there is no CD, which is I guess related to the scsi emulation, which I compiled into 2.4.18-bf2.4. It seems to me that by apt-get installing the new kernel, it should configure itself the same as the 'old' kernel- but it doesn't, which I just dont understand. Anyhow, I am back to trying to install grub, so I can enable scsi support (I THINK that's why I wanted to do that...) so DOlson, bvc and cybrjackle, here we go. And thanks again for your support! (Sounds like an old Bartles & James advertisement)

Sorry, it's been too hot here, and I been getting grouchy. Anyway, X was working, till I installed grub, then it quit. What I'm gonna do is leave it for a day or two and recoup my patience, then I won't get so frustrated. I sincerely do appreciate the help. Thanks, I'll be back.

Thanks, but Mandrake is on seperate machine... and I have Debian dual booting with XP. I am thinking, at this point, of starting over from scratch with Debian, and perhaps only updating to Sarge. Honestly, I am out of patience. If Mandrake had been this tough, I'd still be using windows only.

OK, I'm licked. I have tried every conceivable variance of those commands, it won't work. Now lilo is gone, and there is nothing I can do with grub, I can't get lilo back, and booting off the CD is the closest I can get to a working system, and now, even that won't get into X. I am frustrated. Here I just thought I would give this a try, but after 5 days of beating my head against the wall, still no X, no cdrom, no printer, etc. Thank God for Mandrake. If you still think I can salvage this mess, please let me know.

Ok, now I AM dumb, I installed grub, and it pushed lilo right out of the picture during boot-up, but I have no idea how to begin configuring it so it's usable. It just says grub> and I hit 'tab' for a list of possible words, there must be 50 of them, so I pick 'boot' for my first word, but what to type after that? It says kernel must be loaded first. As I said, I am sorry, guys, I had no idea...

By the way, I'd like to try grub, if you say it's better, but I don't know how to change from lilo. :?:

OK, yes I did apt-get to get that, and it installed OK, it said. But when I 'append' lilo.conf, I get a syntax error, here is just that section of lilo.conf: # Kernel command line options that apply to all installed images go # here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in # the Linux kernel `Documentation' directory. # append=hdc=ide-scsi devfs=mount # Boot up Linux by default. # default=Linux

Need to know exactly where tp put 'devfs=mount' in lilo.conf. It keeps saying it is an "unrecognised token at line so-and-so." when I run lilo.

Hey all, I'm still here, just giving you a day off!!! :lol: Actually I have been waiting, thinking about whether I want to risk losing the whole install, in order to make the cd burner work again. But now that I think about it, it's only a valuable install if it all works, so what the heck? I'll try it. EDIT: ( I downloaded devfsd) here we go...

You are too kind- I checked in lilo.conf, and the 'hdd=ide-scsi ' option I put had been commented out, so I uncommented it and ran lilo: debian:/home/mike# lilo Warning: '/proc/partitions' does not match '/dev' directory structure. Name change: '/dev/ide/host0/bus0/target0/lun0/disc' -> '/dev/hda' The kernel was compiled with DEVFS_FS, but 'devfs=mount' was omitted as a kernel command-line boot parameter; hence, the '/dev' directory structure does not reflect DEVFS_FS device names. That should mean something to me, but of course it don't... :?

Great! :lol: nvidia is IN, and X came up OK!!! You guys are terrific. Not to be a smarta**, but at this point I need to ask, what is the attraction to Debian? Other than the ability to upgrade your entire system with apt. I honestly could NOT have done any of this without you guys. Where did you learn all this stuff? And now it's on to figurring out how to make my cd burner and dvd-rom work again. (They quit working with the kernel upgrade). And if I can ask, how the heck does Debian handle configuring hardware (printer)? Of course in Mandrake, we have harddrake, which makes it simple... I have searched through as best I can, the documentation for Deb, but haven't found anything yet. My printer is an HP psc2110, and all functions work fine under Mandrake, so I assume it will work here as well, am I correct? Again, thanks a lot, and if ya feel like tackling these questions, I appreciate it - but if not, I will certainly understand!

Hey , Did what you said, and I am closer... but not yet... Error: You appear to be compiling the NVIDIA kernel module with a compiler different from the one that was used to compile the running kernel. This may be perfectly fine, but there are cases where this can lead to unexpected behaviour and system crashes. If you know what you are doing and want to override this check, you can do so by setting IGNORE_CC_MISMATCH. In any other case, set the CC environment variable to the name of the compiler that was used to compile the kernel. [1;31m*** Failed cc sanity check. Bailing out! *** [0mmake: *** [gcc-check] Error 1 -> Error. ERROR: Unable to build the NVIDIA kernel module. ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.

Here we go guys: Installing nvidia gives this error: The kernel header file '/lib/modules/2.4.21-4-k7/build/include/linux/modversions.h' does not exist.The most likely reason is that the kernel header files in '/lib/modules/2.4.21-4-k7/build/include' have not been configured. OK, it's greek to me, what do I have to do now? Thanks-- you guys are tough.

OK I did the command, got this: mike@debian:/lib/modules/2.4.21-4-k7$ ls -l total 364 drwxr-xr-x 2 root root 4096 Aug 21 21:03 initrd drwxr-xr-x 8 root root 4096 Aug 21 21:03 kernel -rw-r--r-- 1 root root 117683 Aug 22 06:27 modules.dep -rw-r--r-- 1 root root 31 Aug 22 06:27 modules.generic_string -rw-r--r-- 1 root root 443 Aug 22 06:27 modules.ieee1394map -rw-r--r-- 1 root root 8038 Aug 22 06:27 modules.isapnpmap -rw-r--r-- 1 root root 29 Aug 22 06:27 modules.parportmap -rw-r--r-- 1 root root 66053 Aug 22 06:27 modules.pcimap -rw-r--r-- 1 root root 24 Aug 22 06:27 modules.pnpbiosmap -rw-r--r-- 1 root root 136113 Aug 22 06:27 modules.usbmap Obviously, no symlink there, so I do ln -s /usr/src/kernel-source-2.4.21/ build Now the symlink is there, so I try again install nvida, I'll get back to you tonight... gotta work.

Crud. This is what I get: mike@debian:~$ ls /usr/src kernel-headers-2.4.21-4 kernel-headers-2.4.21_10.00.Custom_i386.deb rpm kernel-headers-2.4.21-4-k7 kernel-image-2.4.21_10.00.Custom_i386.deb I can't figure this out, I have 2 kernel-headers and no kernel-source. But it is installed, I am pretty sure, EDIT : Ok I screwed up, I installed kernel-source, now my list looks like this: mike@debian:~$ ls /usr/src kernel-headers-2.4.21-4 kernel-source-2.4.21 kernel-headers-2.4.21-4-k7 kernel-source-2.4.21.tar.bz2 kernel-headers-2.4.21_10.00.Custom_i386.deb rpm kernel-image-2.4.21_10.00.Custom_i386.deb Nvidia still don't see it. And why is my kernel-image not there? mike@debian:~$ uname -r 2.4.21-4-k7

bvc and DOlson and cybrjackle, thanks a lot guys. The new kernel is in, and a whole lot easier than sdoing it the other way, thanks to apt. Still, nvidia complains about no kernel-headers, and fails. I also apt-got kernel-source and kernel-headers. One little step at a time I guess. I'm gonna go bak to DOlson's nvidia tutorial and re-read it again. :)

Thanks DOlson, Im past that, and I don't recall seeing that, I just copied the bzImage created to /boot, edited lilo.conf to include it, and ran lilo. Lilo won't see it for some reason. By the way, Im about to give up, and that's something I hate to do. PS I followed your example on the second page of this post, and I got errors when I got to: dpkg -i kernel-image-2.4.21-preempt_10.00.Custom_i386.deb kernel-headers-2.4.21-preempt_10.00.Custom_i386.deb so I guess that part didn't go... all I wanted to do is get nvidia going, and man! So I can't use the default kernel 2.4.18-bf2.4, since there is no available matching kernel-source that I can find, and I can't seem to locate it on the CD. I guess I'm done whining now! :wink:

OK, I have tried to install kernel-2.4.21 as per DOlson's advice. The problem is after I edit lilo.conf and then run lilo, it keeps saying no such file or directory, I can see that the new vmlinuz is there, I cdan even re-name it to whatever I want, but...lilo only sees my 2 old entries, for linux and xp. I don't know, so I hope somebody does... Thanks!

Don't have /etc/modutils/options...but I have /etc/modutils/actions is that it?

OK, boot menu meaning lilo.conf?

Thanks, I did that, k3b won't function properly, when I go to copy cd, it crashes. Thought I would try to compile it... by the way, that same error occurs with anything I try to compile. Suggestions? (I have automake installed as well...)

Hi, Debian sid, trying to compile k3b from source, doing ./configure gives the above error. I have gcc installed... Thanks. :?