sn8kman

That's what I thought, but the description of the RPM file in RPMdrake seemed a bit ambiguous about the network booting being PXE (or vice versa). :wacko: Thanks again!

Thank you for your help. as an aside - I am currently installing RPMs and noticed one for PXE isn't that something for network booting or is it more along the lines of what a bootloader would use?

I'm sorry Zé. Me faulto. Thanks to you and Thac agian!

only possible error I get: Writing boot sector. /boot/boot.0800 exists - no boot sector backup copy made. full lilo output: lilo -v LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2004 John Coffman Released 17-Nov-2004, and compiled at 14:16:24 on Sep 12 2005 Reading boot sector from /dev/sda Using MENU secondary loader Calling map_insert_data Mapping message file /boot/message -> message-graphic Calling map_insert_file Boot image: /boot/vmlinuz -> vmlinuz-2.6.12-18mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.12-18mdk.img Added linux Boot image: /boot/vmlinuz -> vmlinuz-2.6.12-18mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.12-18mdk.img Added linux-nonfb Boot image: /boot/vmlinuz -> vmlinuz-2.6.12-18mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.12-18mdk.img Added failsafe Boot image: /boot/vmlinuz-2.6.12-18mdk-i686-up-4GB Mapping RAM disk /boot/initrd-i686-up-4GB.img -> initrd-2.6.12-18mdk-i686-up-4GB.img Added linux-i686-up-4GB Boot image: /boot/vmlinuz-2.6.12-18mdk-i586-up-1GB Mapping RAM disk /boot/initrd-i586-up-1GB.img -> initrd-2.6.12-18mdk-i586-up-1GB.img Added linux-i586-up-1GB * Boot image: /boot/vmlinuz-2.6.12-18mdk Mapping RAM disk /boot/initrd-2.6.12-18mdk.img Added 2612-18 Writing boot sector. /boot/boot.0800 exists - no boot sector backup copy made.

Again, did that - still not working. Maybe something to do with framebuffer? (just searching around and heard that mentioned once)

Thanks for the advise. However, once I get past LILO text the graphical boot works fine. It's the bootloader that I'm having a problem getting to go graphical. Call me weird, but I want my bootloader to be pretty

Well, it *was* fixed, then I hosed my MBR. :woops: Fixed that, but now I'm getting text again. However, the not a number error is gone. Here's my lilo.conf: # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file default="linux-i586-up-1GB" boot=/dev/sda map=/boot/map vga=normal keytable=/boot/us.klt menu-scheme=wb:bw:wb:bw prompt nowarn timeout=60 message=/boot/message disk=/dev/sda bios=0x80 image="/boot/vmlinuz" label="linux" root=/dev/sda1 initrd="/boot/initrd.img" append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz label="linux-nonfb" root=/dev/sda1 initrd=/boot/initrd.img append="resume=/dev/sda5 splash=silent" image=/boot/vmlinuz label="failsafe" root=/dev/sda1 initrd=/boot/initrd.img append="failsafe splash=silent resume=/dev/sda5" image=/boot/vmlinuz-2.6.12-18mdk-i686-up-4GB label="linux-i686-up-4GB" root=/dev/sda1 initrd=/boot/initrd-i686-up-4GB.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.12-18mdk-i586-up-1GB label="linux-i586-up-1GB" root=/dev/sda1 initrd=/boot/initrd-i586-up-1GB.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.12-18mdk label="2612-18" root=/dev/sda1 initrd=/boot/initrd-2.6.12-18mdk.img append="resume=/dev/sda5 splash=silent" vga=788 Any suggestions to get back to lilo with graphical would be appreciated.

I just wanted to post about a problem I had because I previously wiped the entire hard drive to solve the issue, but turns out there was an easy fix. After I reinstalled, was configuring the new MDE-KDE3.5.2 and hosed my lilo MBR somehow. I got L 99 99 99 99 99 etc when booting and couldn't get into Lilo or linux. Here's what I did: boot off the install DVD (CD) <F1> when first menu appears type rescue **may be optional** select reinstall bootloader - got errors hit <enter> select console type chroot /mnt type type lilo -M /dev/sda **note-this is my root hard drive. if you have a SATA hard drive for booting use this. If you have an IDE hard drive type lilo -M /dev/hda** type rescue-gui select reboot !all fixed! :woot_jump: Again, please correct me if I'm wrong, but this is what I did. BTW: I love the smilies!

I know it shouldn't make a difference with urpmi if you set 2006.0/RPMS or 2006.0/RPMS/ but get 404 erros none the less if set ~/2006.0/RPMS/ but not with ~/2006.0/RPMS - maybe older version of urpmi, since updated urpmi doesn't seem to have that problem. Thank you again for all your time and effort with your advise and repository - I'm now on a pure MDE install of 3.5.2 and already noticing a difference between SoS and MDE (MDE>SoS). Nothing against SoS, but I'm personally liking what you and Ze have done better. Also, thank you for your patience with me. Yes, I'm a win convertee since 12/25/2005. Now 100% winblows-free

thank you - i'll try that :D PERFECT! 771 (not "\"771\"") fixed it. Thank you again!

:huh: I understand that mixing and matching isn't good. I'm currently trying to get MDE to work completely without mixing. My problem: keep getting errors curl(22) couldn't connect to http://www.mde.djura.org/2006.0/RPMS/kdeba....2blah.blah.rpm Am I doing urpmi.addmedia wrong? I did: urpmi.addmedia MDE-2006 http://www.mde.djura.org/2006.0/RPMS/ with hdlist.cz I know KDE is in a sub-directory /kde-3.5.2/ but no hdlist.cz there. I don't have smart (I don't think). I must have gotten kdebase-kdm from somewhere else if it couldn't retrieve it from MDE because of this problem. I'm sorry if I mis-interpreted, but you have 2 versions of many files (ie:kdebase-kdm-3.5.2-8.i586.rpm and kdebase-kdm-3.5.2-9.i586.rpm) which usually means an update. I'm looking on your site for instructions now. *edit* yes, I've added urpmi as instructed. But I'm still getting these errors *edit* --update: apparently my fault (again) -- VERY IMPORTANT that ~/2006.0/RPMS NOT ~/2006.0/RPMS/

here's the first few lines: default="linux-i586-up-1GB" boot=/dev/sda map=/boot/map vga="\"771\"" keytable=/boot/us.klt menu-scheme=wb:bw:wb:bw prompt nowarn I assume I should remove the extra " from each side of \"771\"?

I've noticed that MDE has updated their RPMS to include some patched base KDE 3.5.2 files and SoS has also released his 3.5.2 files. Here's what I did to get it ot work: [/solution=on] rpm -e --nodeps kdebase-kdm urpmi.addmedia SoS http://seerofsouls.com/mandriva/KDE-3.5.2 with hdlist.cz urpmi.removemedia MDE urpmi kdebase-kdm (from SoS) urpmi.addmedia MDE http://www.mde.djura.org/2006.0/RPMS/ with hdlist.cz urpmi kdebase-kdm (from MDE) vi /etc/kde/kdm/kdmrc insert key to add under [general] section: ServerVTs=-7 esc key to get to commands :w to write the file :q to quit vi init 6 to reboot. [/solution=off] This was not the most eloquent method - but it worked. I had to manualy edit the kdmrc file because from what I can tell, both resources did not have the line for ServerVts so my keyboard input wouldn't go into the KDM login screen. I'm now up and running in KDE-3.5.2 but I'm patching other issues I caused in getting to this point. Thanks again for all the help.

Ok, since updating to KDE 3.5.2 and trying to customize my computer back to what I had in 3.5.1 I'm getting the following error from MCC>boot>configure how the system boots: :Fatal:not a number :""771"" Any idea how to fix this? :unsure:

Yes, the MDE KDM screen comes up but the sessions menu doesn't give me KDE as an option. I have verified that KDM is the login manager (per MCC) and that invoking it manually gives me the same thing.

Ok, here's where I'm at: Mandriva 2006.0 Installed Tried to update to KDE 3.5.2 from MDE - failed (couldn't find kdebase-3.5.2 or kdebase) Updated KDE to 3.5.1 from SoS Tried to update again to 3.5.2 from MDE - failed dependencies Reinstalled KDE 3.5.1 from SoS. I want to thank you for taking the time to create the MDE resources especially for 3.5.2. I'm sure if I was a little more knowledgeable with Linux they'd work fine. With everyone who had no problems, I'm positive the fault lies in my court. I'll read more and maybe try this again later unless anyone has a miracle fix that I don't know about (ie: something easy like patting your head and rubbing your tummy while using --wget instead of --curl) At least I have a useable mandriva installation again.

Thanks for the help. I'll be trying to update to 3.5.2 on a fresh and little-enhanced install of 2006.0-Free in about an hour. I'll post back tomorrow and let you all know how it goes. :D

The MDE login looks great. However, under the sessions 'button' my options are (were) Default, ICEWM, Previous, Failsafe. I would like the option to login to KDE. The only thing that actually works is ICEWM. I'll check out the KDM manual online (provided I can find it - but shouldn't be hard) but currently I'm booting off a live Kubuntu CD and downloading the Free DVD for 2006,0 to give it one last try. If it doesn't work - I may just use Kubuntu 6.0.6 since it comes with KDE 3.5.2

Ok, MCC>boot>autologin definately not the place. MCC>system>display manager only lets you pick which DM to use (KDM, GDM, XDM) but not configure it. Trying the genkdmconf --no-old and rebooting - BRB Also, I manually removed the kdebase-kdm with rpm -e --nodeps kdebase-kdm and then re-added it with urpmi kdebase-kdm which did use the MDE repository. Again, trying to reboot now. :mellow:

Ok, I'm rpm -e --nodeps mde-kde-config-file to manually remove the config file and then reinstalling it while in ICEWM. We'll see if that works. MCC doesn't have an option to change the session choices, but does have a GDM configurator option. I might have to invoke the KDM configurator through a terminal though - anyone know the command?

Ok, I feel like a total n00b, but I've done plenty of KDE upgrades before and 3.5.2 is throwing me for a loop. I've looked all over and found there's no kdebase-kdm-config-file I guess for this release. However, I have no idea how to tell kdm to give me the option to log into a KDE session instead of ICEWM (or custom, failsafe or default). I used the mde.djura resources and everything seems to have gone ok - ie:no errors and all signatures, etc. are fine. Can anyone give me a like with a how-to (like SoS has) that is specific to 3.5.2 or a fix for this specific issue? Thanks.