Jump to content

chris:b

Members
  • Posts

    862
  • Joined

  • Last visited

Posts posted by chris:b

  1. 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

  2. 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.

  3. 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!

  4. 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.

  5. 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

  6. Anna if there was more that I could do to assist in anyway I would be glad to try, I am really fairly new to linux and am

    not skilled in doing a compile if that is what MDV config tool does, I would need more information to be of help.

    I do have 10 gig HD's that I routinely swap into that computer to run tests so it would not be a problem to install

    I will try booting to init 3 with the live, what is the command to start the MDV config tool? MDV ?

     

    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.

  7. 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

  8. 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

  9. Hi all,

     

    Awaiting the summer season (without computers and software) I am glad to announce MCNLive, code name "Toronto".

    img001.jpeg.medium.jpeg

    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

  10. 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.

  11. The final does not boot on my notebook, hanging after the network stuff, I think. :wall:

     

    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.

  12. I am hesitating to post the following. I guess some won't appcreciate it. :lol2:

     

    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.

  13. 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.

  14. 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

  15. 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.

  16. 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)

  17. When grub loads from the external drive, I can press "e" to edit the boot command. There, the first line says
    root  (hd1,0)

    Following instructions found on the ubuntu forums, I changed this to

    root  (hd0,0)

    (apparently because grub is now loading from the external drive, the external drive becomes 0, not 1. Don't ask me). Note that this change is only temporary, it only works for this boot and on the next boot grub will again try to load from 1. But anyway, just with this temporary edit, when I press "b" to boot, it finds everything and loads up into my first ever Debian! :D

     

    Apparently if I edit grub's menu.lst file this change will become permanent, but I haven't tried that yet, I just wanted to get the thing booting.

     

    So to sum it up, I tried installing Mandriva, it didn't work so I tried again with Debian. This didn't work either, with very similar error messages, but with this grub config change Debian now boots. So it's possible, -maybe even probable- that the same edit would fix the Spring install too. But I'm not much inclined to try it out cos I've already got Spring on my internal drive and want to continue looking at Debian. :D

     

    Thanks for your help, chris and pmpatrick! :thumbs:

     

    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 :-)

  18. As to the suggestion to "extract the created initrd and try to found out if all modules are included.", I have absolutely no clue where to start trying that.

     

    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

  19. 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

×
×
  • Create New...