chris:b

The 'noapic' kernel option-- --chris

Pete, we had a short downtime on the forum. Can you provide the informations I asked in this topic? lspcidrake -v su iwconfig

It is the darn "mille-xterm-busybox" package. Where does it come from? It will break the build system. We need the default installed busybox package. It must be a packager fault. mille-xterm-busybox should NOT override the normal busybox rpm. Please do not run any --auto-update or --auto-select. --chris, curious about what comes next :D

Ok, Pete, here we go. :) Let's start with the basics. * Can you tell me the exact notebook model you use? * Could you tell me what kind of wifi setup you use -- static DNS, DHCP, do you use WEP or WPA? * Which version of MCNLive: Toronto, I guess? The connection does not work at all? Or is not stable? * Can you provide/ post here the output of the following command, in a terminal: lspcidrake -v and (after 'su' the password is: root) su iwconfig PS: may I ask other MDV users to help here too -- I am not an expert in wifi and networking. It always just worked for me.

olddogface, thank you for trying - and the solution. You can safely ignore the error message about liblow.c (320) /dev/gpmctl - you don't need it. It is not a bad burn I am almost sure. Using the safeboot option: seems that your hardware (the keyboard/mouse) needed one of the kernel boot parameter that we are providing in the boot menu. Thanks again!

Hi Pete :-) when you are interested we can try to debug your problem, without any "exercise in ++C/Unix/VB/Java programming", I promise. :D I need to go working now, will be back when it is evening in Europe. May I ask to open a new topic here: https://mandrivausers.org/index.php?showforum=54 And just describe as good as you can what happens and when etc when your wifi connection fails. Also, which settings, which kind of Access point. See ya later.

Pete, I also have ipw2200 and it works very good on my hardware. I don't know what your problem is. We tried to do our best. If that is not enough -for your hardware- I would like to kindly ask you to use whatever works for you. Getting angry at Mandriva or other distros won't help. Oh, and it is not Paris here. --chris

No need to recompile or even install things. Start the live cd , at the very first boot screen, hit <tab>, and add the following to the so-called append-line: init 3 Now start with enter. It will boot non-graphical. At the login prompt type: root, password is root Type: keyboarddrake You'll get a menu where you can choose a keyboard. I can't say what you need to choose. Next type: mousedrake Here you can select a mouse. When you are done, type: exit And login: guest (password is guest) To start KDE you would type: startx Also, if you still can't use keyboard nor mouse, in init 3 you can start: mc (Midnight Commander), the filemanger and editor to have a look at the generated /etcX11//xorg.conf Thanks.

Thanks for reporting. Looks like the kernel still has some usb issues. Your xorg.conf is from sidux, I guess? MDV usually only writes one mouse device entry. We could try to make it work, even with this usb issue, by booting in init 3 and running the MDV config tool. Anyway, thanks. And greetings to the sidux/debian community. Great distro :-) --chris

gola, what you see is a non-critical error while trying to build the bootsplash. It will build a good iso with a working bootsplash. It is mentioned in the release notes. No worry. And it is not related to the problem with the updated packages. You'll see the same (silly) error without any updates. --chris

Hi all, Awaiting the summer season (without computers and software) I am glad to announce MCNLive, code name "Toronto". What's the difference to "Delft": VirtualBox OSE, KOffice Suite, Gimp, Gthumb, Gxine, Gftp, Bluefish, Quanta, kaudiocreator, Kopete, kdebluetooth-pin, bunch of networking tools and printer packages added. English only edition. Improved isolinux bootsplash, with keyboard navigation to select a boot option, different wallpapers, fixed (non-critical) error messages when shutting down the system in livecd persist mode. Download Toronto here: ftp://ftp.nluug.nl/pub/os/Linux/distr/man...cnlive/Toronto/ Release notes, md5sum and a list of installed packages available on the same mirror. --chris

No French in 'Toronto', I am sorry. But you will be able to add it!

Yesterday in the distrowatch weekly, an article about Deli Linux: http://distrowatch.com/weekly.php?issue=20070521 "DeLi Linux is a Linux distribution for old computers, from 486 to Pentium MMX 166 or so. It's focused on desktop usage. It includes email clients, a graphical Web browser, an office package with word processor and spreadsheet, etc. A full install, including XFree86 and development tools, needs no more than 300 MB of harddisk space." Has anyone tried it? Would love to read more about it. Unfortunately I don't have such old hardware, and not enough time to play with it.

The final does not boot on my notebook, hanging after the network stuff, I think. Had to go for VirtualBox. A bit slow, but finally comes up. I was interested in the initscripts and the base system and gcc ... It is Mandriva 2007 (not 2007.1), but without urpmi and rpmdrake. KDE one version behind cooker which I think is a good decision.

I am hesitating to post the following. I guess some won't appcreciate it. I am known as an opponent to install any Live CD /Live system as your main system on a hard disk. No matter which one, Mandriva One, MCNLive, Knoppix or any of the click-populars on distrowatch. Read on here for the reasons: http://www.mandrivaclub.nl/site/index.php?showtopic=8003 You'll never get a clean system after installing a live cd. The differences in the live distros is only: the amount of uncleanliness. The major distributions all offer a quick-and-dirty live install, because of popular demand. That does not make things better.

There are only very few system config files which were changed to be able to work with mklivecd. * rc.sysinit and halt and /etc/sysconfig/init (all from the initscript package) * an addition to the syslinux package * and of course the mklivecd package (from contrib), never ever install this broken package from the mdv repos All other settings are pure customization (KDE, GUI etc. ) that should not harm the basic functionality I can't see anything in the xinitrc package that could break it, it does not contain anything that would cause a 'Kernel panic', xinitrc are responsible for the X startup -- unless MDV made significant changes in this package. Installing a different or an updated kernel of course can cause everything. Adding **any** other sources than /main or /contrib can have the effect of breaking stuff. /main and /contrib are the only sources that are static and not updated! If someone adds for example 'testing' it will sooner or later hose the system.

Looks like the package initscripts (not only xinitrc) has an update. This will break a remaster for sure. I can't blacklist packages in urpmi.cfg, because people use MCNLive also as an normal installed system on their HD.

What is the content of the updated Xinitrc-2.4.19-zmdv2007.1 ? Which files? Some init scripts need some slight modifications to work with mklivecd. If they are replaced by an update, the remaster is broken. I disabled the 'update' source intentionally ! Thanks, gola!

Depending on your RAM (and a swap partition) you might want -when you plan to do a remaster- in this case not to boot with copy2ram 512 MB RAM --> i would not boot with copy2ram 768 MB --> copy2ram & remaster-on-the-fly should work, even after adding nvidia drivers etc. 1 GB RAM --> feel free to do the most craziest things

Ah ok, it was the CD. The usbhome thing: it does not work. That's why you see: (broken) To make all changes persitent Delft has the feature: livecd persist Reg. the 'copy2ram' It is one of the most amazing things in the live system linux world. Unfortunately folks just don't try it. Those who do are tempted to never run an HD installed system again -- because it is so much faster, snappier etc.

Yes, exactly. In the menu --> MCNLive there is an entry: Remaster Live - simple, it is a graphical wizard. Will ask you the basic stuff, and then build the iso. It does not affect anything on your normal installed system, only 'change' is: you get a new iso on the partition which you can choose when running the wizard. You can first test the iso on your main system with virtualbox or qemu if you like. No need to burn. The new version Toronto (with virtualbox bundled) will let you test the new iso even without rebooting your normal installed system B)

512 MB memory should be enough. When you create the virtual disk, just give it only 128-160 MB from your memory. And the slax iso should fly :-)

That's it, neddie. Will also work for MDV I guess. I am not familiar with GRUB, but basically it does confuse the drives when it generates the config file. Good catch. And have fun with Debian :-)

Copy the /boot/initrd-2.6.17-blah.img from your usb drive somewhere in a dir on your home/user dir. It is a gzip compressed archive. Right click on the file: extract ... Then in a terminal: cpio -i -d -H newc -F initrd-2.6.17-blah.img --no-absolute-filenames You'll get two files: bootsplash and init and some directories, one called: /lib ---> here you find the included kernel modules And the text file 'init' is also interesting :D

mount: Mounting /dev/loop0 on initrd/loopfs failed: invalid argument At this stage it either looses the contact to the cd/dvd drive, or can't read the medium, or the data on the medium is corrupted. Your hardware should not have a problem at all. Is it a laptop or a desktop? One cd/dvd drive or more? How is it connected, I guess IDE? Together with a hard disk? Internal or external? Can you boot any other Live CD's, burned on the _same_ brand medium, burned with the same burner? (some drives don't like specific brands, burned with specific bruners and so on ...) Does it boot on a different computer? Sorry, I am running out of ideas. I also can't think of a bootcode. You could try: livecd noapic nolapic acpi=off irqpoll debug