I upgraded from 6.2 to 6.3 back in December. After having many problems I decided I would just do a fresh install. I wanted to juggle some partitions anyway. The number 1 problem is that I can't boot to a recompiled kernel. I tried some suggestions (initrd/boot stuff) from Phillip Thomas last week with no luck. I tried to send a reply but I could not dial out from Linux (yet another persistent problem). I can boot to the standard SuSE kernel just fine. I recompiled 2.2.13 from lx_suse and plain vanilla linux sources, both from the 6.3 cd set. I also tried recompiling from 2.2.14 (supposed to fix my zip drive problem). I get no compile errors. I can't boot. I have recompiled successfully many, many times in the past. This is what happens during boot: ===================================================================================== ...checking file system... /dev/sda3,5,8 --> clean fsck.ext2: No such device while trying to open/dev/hda1 (null). The super block could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the super block is corrupt, and you might try running e2fsck with an alternate super block: e2fsck -b 8193 <device>. /dev/sda7,1,6 --> clean /sbin init.d/kbd: /usr/bin/find does not exist. Exit. fsck failed. Please repair manually and reboot. The root filesystem is currently mounted read only...etc. ===================================================================================== First, Suse is on /dev/sdax and windows is on /dev/hdax with the exeption of hda1 which is ext2 (about 8mb)and mounted as /spare. Also /dev/sda9 is vfat. Second, /usr/bin/find does in fact exist. When I boot to the standard suse (pentium) kernel I get no errors and I can r/w to hda1. I have confirmed the existence of /usr/bin/find. Also, with the plain linux kernel sources, I tried uncommenting the line in the make file about installing to /boot. I have no idea what this is supposed to do but it didn't help me. I still had to cp bzImage and System.map to /boot. Yes I edited lilo.config and ran /sbin/lilo. As stated above I tried the initrd stuff however, I just commented out the line in lilo.config instead of removing it. Makes a difference? I can't boot to standard kernel this way though. Have to boot from cd then edit lilo.config again. I've spent a lot of time on this because I wanted to try to figure it out myself, but I have to admit defeat. List of other problems just in case some are related: 1. Can't eject zip disk after umounting. Well, it does eject eventually. About 10-20 min. after pushing the button. 2. No sound. My motherboard won't allow me to use compiled in sound so I have to remove it from the kernel and use oss. I did this in 6.2 and it worked great. The only problem is everytime the kernel is recompiled oss.config (or whatever it's called) has to be rerun or even download an updated version for the whatever-new-kernel-version. What a pain. 3. xcdroast won't work because it can't find an sg device or module, as I recall. The device is there and is found at boot. So is my scanner. I haven't bothered to try the scanner. Modprobe can't find sg.o It's in there (is it /lib/modules/2.2.13/scsi/sg.o ?). Seems to me I was able to mount my cdrecorder as /dev/scd0 or /dev/sr0 . I would look this stuff up to be sure but I have to send this from windows 'cause... 4. As far as I am concerned Linux dialup sucks. I have two ISP's. I can sometimes access one with wvdial. And sometimes I can access the other with kppp. But never vis versa. In 6.2 I was able to access two ISP's with wvdial. Well, sort of. That is when I wasn't being denied permission to /dev/ttyS0. This continues today as well even though I tried the saved configuration files from 6.2. I have permissions set to secure/local and set local to give group rw permissions to /dev/ttyS0. I have tried setting to easy, easy/local, even warn and no. Makes no difference. Group write permissions keep getting yanked no matter what I do. I can't figure out what is causing the permission to change. I can download some stuff, hang up, then say oh yeah I forgot to check for mail, try to dial and wham! Permission denied. This happens within minutes. SuSEconfig didn't run. AFAIK Cron only runs once a day around midnight. Somtimes I can go a week or two and then it happens one time right after the other. This only seems to happen with wvdial not kppp. Right now I can dialout but I can't "go" anywhere. Hmm...DNS problem right? Funny thing is it worked two days ago. Yesterday it did not. I never changed a thing. I'm no fan of MS but they got dialout NAILED! I can set it up in 5 minutes and never have a problem with it. Sheesh. 5. Yeah there's more but the smoke coming out my ears is blurring my vision and I can't see to type anymore. I didn't bother booting to linux today, it's just become too frustrating. Maybe it's time again to take a couple months off from this mess. Did I just get a really BAD set of cd's or what? If anyone can help out I sure would appreciate it. Sorry, didn't intend to write a freakin' book. -- See Ya! Tim, pissed off and tired in NJ mailto:tajcs@mindspring.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/