Re: jessie installation problem on arm sheevaplug
* Rick Thomas rbtho...@pobox.com [2015-06-07 19:39]: I’ve attached a screenlog file from “screen -L /dev/ttyUSB0 115200” if that’s any help. The VT100-style curses stuff makes it a bit hard to interpret… From the log it looks like you didn't finish the installation. These are the last messages in the log: Abort the installation If you have not finished the install, your system may be left in an unusable state. Are you sure you want to exit now? The system is going down NOW! -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150608140120.gb17...@jirafa.cyrius.com
Re: Re: Re: jessie installation problem on arm sheevaplug
* Rodrigo Valiña Gutiérrez rodr...@gmail.com [2015-05-18 13:42]: The relevant part of /var/log/installer/syslog seems to be this: ... May 17 15:19:13 base-installer: info: could not determine kernel flavour The installer is fixed now and you can install Debian on the SheevaPlug (and other plug variants) again. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150606175503.ga6...@jirafa.cyrius.com
Re: Instructions for upgrading U-boot on Marvell OpenRD Base computer?
* Vagrant Cascadian vagr...@debian.org [2015-06-02 13:37]: There isn't much traction in upstream u-boot on this, and I suspect u-boot is basically broken on sheevaplug, guruplug and openrd_ultimate in jessie, stretch and sid... With no activity upstream, I'm hesitant to I booted u-boot from jessie on the SheevaPlug yesterday and it seemed to work fine. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150603151049.gf27...@jirafa.cyrius.com
Re: Instructions for upgrading U-boot on Marvell OpenRD Base computer?
* Rick Thomas rbtho...@pobox.com [2015-06-02 13:05]: I gather from what you say about DTB that that transition does not depend on U-Boot? So I should be able to upgrade to and beyond Jessie without problems? That's correct. The ideal scenario would be for the boot loader (u-boot in this case) to pass the device tree information to the kernel. However, since you cannot upgrade the boot loader on every device, it's possible to simply append a Debice Tree Blob (DTB) to the kernel image. In Debian, the flash-kernel tool has been updated to append the DTB when needed. (For Debian stretch, we also need to add the DTB in Debian installer so the installer will boot, but I'll make that change this week.) Can you tell me what the most recent U-Boot version is that actually does support the OpenRD Base? If there is such a thing, do you have a suggested procedure for doing the upgrade? Get u-boot from unstable, add the target (see the patch I quoted in my previous email which removed the ultimate target) and build. Make sure you have a backup of u-boot and know how to use OpenOCD. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150602204114.gb4...@jirafa.cyrius.com
Re: Instructions for upgrading U-boot on Marvell OpenRD Base computer?
* Rick Thomas rbtho...@pobox.com [2015-05-31 19:11]: I’ve got an old Marvell OpenRD Base computer that I’d like to install Debian Jessie on. I believe that I’ll need to up-grade the u-boot on it to handle new features in the Jessie kernel. I haven't had an OpenRD in years but back then I always used the original u-boot without any problems. Why do you think a new u-boot is required for jessie? Have you tried it and things are not working? (After jessie, the kernel has been converted to DTB, but flash-kernel already appends the correct DTB.) 1) Where to get a suitable u-boot image? (Will the one at https://people.debian.org/~tbm/u-boot/2014.10+dfsg1-4/openrd_ultimate/ work? No, the Ultimate and Base are different. I just checked and I was going to say that there's support for the Base in DENX. However, I noticed that even the Ultimate target was removed in Debian's u-boot recently: http://anonscm.debian.org/cgit/collab-maint/u-boot.git/commit/debian/targets?id=ea2f6ce84b7788cda2cb7deb29690cb368451e8c So if you want to work out why it doesn't build and whether it boots, I'm sure Vagrant Cascadian would be interested in hearing from you; but it's probably easier to stay with the original u-boot unless that has problems. Unfortunately, it seems there aren't many OpenRD users left. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150602161536.gi26...@jirafa.cyrius.com
Re: Re: jessie installation problem on arm sheevaplug
* Rodrigo Valiña Gutiérrez rodr...@gmail.com [2015-05-17 16:09]: But now the installer fails in the Install the base system step, saying: No installable kernel was found in the defined APT sources... when the last time I tested with changed machid and original uImage it worked with the same sources. What does /var/log/syslog say when this happens? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150517232447.gb9...@jirafa.cyrius.com
Re: jessie installation problem on arm sheevaplug
* Rick Thomas rbtho...@pobox.com [2015-05-16 17:47]: - In u-boot: setenv machid 0692 saveenv This is not the correct solution. The problem is that there are different ways to boot on ARM machines. The old way was for the boot loader to pass a machine ID to the kernel which would tell the kernel which machine it's running on. The new way requires u-boot to pass a device tree to the kernel which describes the hardware components of the system. (The workaround suggested here simply tells the kernel a wrong machine ID and that works because that particular device has not been converted over to device tree yet, but this is not a good solution since you're telling the kernel a wrong device, so it's possible some hardware components won't work correctly.) The u-boot in Debian passes the machine ID (because that's how you configured it) but not the device tree. Newer kernels require the device tree on the SheevaPlug and no longer support the machine ID, which is why you get the error about the machine ID not being known. Ideally, u-boot would pass the device tree to the kernel, but this is currently not done in Debian's u-boot (see #782293). So the best solution now is to append the device tree blob (DTB) to the kernel in the installer. This way, the kernel will find the correct device tree and can boot (and everything else will work since flash-kernel already appends the DTB on the SheevaPlug). I've to catch a flight now but I'll post a kernel image with the DTB tomorrow. Sorry for not fixing this earlier. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150517013718.ga5...@jirafa.cyrius.com
Re: jessie installation problem on arm sheevaplug
* Martin Michlmayr t...@cyrius.com [2015-05-16 21:37]: So the best solution now is to append the device tree blob (DTB) to the kernel in the installer. This way, the kernel will find the correct device tree and can boot (and everything else will work since flash-kernel already appends the DTB on the SheevaPlug). Here's a test image. Take the kernel from http://www.cyrius.com/tmp/sheevaplug/uImage Take the ramdisk from http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uInitrd Boot it as described here: http://www.cyrius.com/debian/kirkwood/sheevaplug/install/ Does this boot? This is how I prepare the image: wget http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/device-tree/kirkwood-sheevaplug.dtb wget http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uImage # Remove the u-boot header dd if=uImage of=kernel.without bs=1 skip=64 rm -f uImage # Append device tree cat kirkwood-sheevaplug.dtb kernel.without # Create new uImage sudo apt-get install u-boot-tools mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n Debian kernel -d kernel.without uImage -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150517015607.ga6...@jirafa.cyrius.com
Re: Bug#367418: probleme X-server
Can someone please respond to this message: * mamah [EMAIL PROTECTED] [2006-05-15 22:12]: Quand j'ai installée Linux debian,il fait l'installation jusqu'ai la fin ,et quand je lance Linux il me dit que le server x est mal installer,il me met sur un terminal ,je met le login et le mot de passe,et je met startx,il chercher l'interface graphique mais il le trouve pas et il me donne l'erreur suivante: (EE) No devices detecde Fatal sever error: no screens found Var/log/XFree86.0.log Trés cordialement. -- Martin Michlmayr http://www.cyrius.com/ -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian package installation
* Rajasekaran J. [EMAIL PROTECTED] [2006-03-29 10:43]: i am not looking for Graphical packet manager. when we double click rpm package it is installing same as i need for debian package. I don't use GNOME or KDE myself, but I'm pretty sure they offer something like that. However, you're asking this question on the wrong mailing list (this is for development of the packaging system). I think you'll get much better responses if you mail debian-user@lists.debian.org I'm CCing this list now: is there any way to configure GNOME and/or KDE to install .deb packages when you double click on them? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Congratulations
* mal icous [EMAIL PROTECTED] [2004-02-19 22:37]: i probably should not waste your time with complaints, but i really feel i need to get someone to listen to my complaints, in the purpose of making the Linux / Debian Distribtuion a better world / product. In the interests of constructive critisim and driving the computing world forward though competition breeding exellence, please make Debian a better installer (even if it is _not_ gui based, just for f**ksakes make it easier). I'm off-line right now because I'm at a conference, so I cannot check if someone on debian-user has responded to you already; I assume someone did, so I'll keep this briefly. We are aware that the installation process has been quite hard in Debian traditionally (although I'd like to add that woody was a great improvement over potato), and this is the reason we are currently working on a new installer for our next release. beta2 of this debian-installer has recently been released, and the development team is looking for users to test it and to report problems and make suggestions. You can find information about downloading and reporting feedback at http://www.debian.org/devel/debian-installer/ and I'm sure the developers will appreciate your feedback. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Request for Help: write man pages for Debian
As you know, Debian is a community effort. I'm asking for help from intermediate to advanced users to make Debian even better than it is. As per Debian's Policy, every executable file in Debian has to supply a man page. However, many packages don't follow this requirement yet. I have created a listing of all executables for which no corresponding man page is available yet. If you use any of these packages listed below, please consider writing a man page for its executable files and submit it to the Bug Tracking System (BTS), http://bugs.debian.org. Writing man pages is not very difficult. You can simply look at some man pages in /usr/share/man and follow their structure (also see the file /usr/share/doc/man-db/examples/manpage.example). Furthermore, some information about the format of man pages is available in the man page of man (man 7 man) and pod2man (man 1 pod2man). Finally, you can also install the package help2man (man help2man) which is an automatic manpage generator. When you decide to help out, please write the man pages for a whole package. Send e-mail to [EMAIL PROTECTED] and tell us which package you are working on. We can then add you to this web site so other people know that someone is working on that particular package already. The full listing together with more instructions are available at http://qa.debian.org/man-pages.html Currently, 614 man pages are missing. Thanks in advance for your help to improve Debian! If you have any questions, don't hesitate to contact me. -- Martin Michlmayr [EMAIL PROTECTED]