Bug#858308: flash-kernel: documentation for upgrading Odroid-U2/U3 to flash-kernel
On Tue, Mar 21, 2017 at 06:45:30AM +0100, Geert Stappers wrote: > On Tue, Mar 21, 2017 at 12:31:46AM +0100, Adam Borowski wrote: > > If you're booting from a SD card, skip until running sd-fusing.sh > > Edit sd_fusing.sh, change sector numbers to those listed in > s/sd_fusing.sh/sd-fusing.sh/ > > ./sd-fusing.sh /dev/mmcblk0boot0 > s/sd-fusing.sh/sd_fusing.sh/ > > Hyphen or underscore D'oh! > > what doesn't work > > - > > > > * rebooting: the machine gets stuck and needs to be physically power-cycled BTW, Vagrant reports that rebooting _usually_ works on his U3, it rebooted correctly only once on my U2. Never had such a problem with the vendor kernel before. > > * audio > > > > * the kernel whines about broken HDMI, video capture -- I can't even test > > those but I don't care > > Please add 'Whoever can test HDMI, please report your milage' Okay. > > * the machine gets very hot; with 3.8 it never was even noticeably warm > > What does mean: Kernel 3.8 is good or bad? Please remove ambigous mean I dropped this entire line: that "very hot" is up to 77⁰ (at 70⁰ right now in the middle of a libreoffice build) and never tripped, thus I have nothing but subjective feelings from touching it by hand. It's not unlikely the difference comes from me having moved the machine, it was AFAIR resting on a big whole-metal router before which could have drained heat well. The fun thing is that all those years before I bought a fan for this box, but because of delusions of replacing my main machine with this non-noisy thing never actually mounted it. Could do it now and play with overclocking to 2GHz as Samsung used to advertise the U2 can do... New version attached. Also, I'm not married to being the sole editor of this file, please feel free to make any edits you want... -- ⢀⣴⠾⠻⢶⣦⠀ Meow! ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second ⠈⠳⣄ preimage for double rot13! How to upgrade an Odroid-U2/U3 to the modern kernel. requirements While strictly speaking, with perfect luck you don't need any extra bits, in reality you need at least: * an eMMC reader (if you bought your eMMC from Hardkernel, the included adapter works well in _some_ SD readers) * a serial console (UART). If you don't have one yet, with shipping it costs its weight in gold -- but fortunately it's not too heavy. u-boot and other pre-kernel gubbins --- apt install u-boot-exynos wget http://odroid.in/guides/ubuntu-lfs/boot.tar.gz Replace u-boot.bin from that tarball (2013 Samsung-private build) with /usr/lib/u-boot/odroid/u-boot.bin (2016 vanilla), the other pieces are ok. If you're booting from a SD card, skip until running sd_fusing.sh On eMMC: Edit sd_fusing.sh, change sector numbers to those listed in /usr/share/doc/u-boot-exynos/README.odroid.gz : . signed_bl1_position=0 bl2_position=30 uboot_position=62 tzsw_position=2110 ` You may notice that these positions look wrong: on your eMMC (as originally shipped) you have all those pieces in "SD" positions. Tʜᴏꜱᴇ ᴀʀᴇ ᴅᴇᴄᴏʏꜱ ᴍᴀᴅᴇ ᴛᴏ ᴡᴀꜱᴛᴇ ʏᴏᴜʀ ᴛɪᴍᴇ! Replacing them does exactly nothing, the real bits are on hidden parts of the eMMC. There are rumours that it is possible to access them from a SD reader by a "partition switch", but despite hours of searching I found no information how to do that. The only way seems to be using the U2 itself. Which is a dangerous thing as if anything goes wrong you won't be able to boot. Fortunately, recovery is possible with a micro-USB cable and a SD card with a special image: http://forum.odroid.com/viewtopic.php?f=53&t=969 -- I did not have the need to test that, though. On the U2, you need to unlock the secret partition first: https://www.kernel.org/doc/Documentation/mmc/mmc-dev-parts.txt . echo 0 > /sys/block/mmcblk0boot0/force_ro ` The device name does vary: it's /dev/mmcblk0 on some kernels (vendor and Debian's 4.10-trunk-armmp), /dev/mmcblk1 on others (Debian 4.9 and vanilla 4.11-rc2). Only boot0 has anything, boot1 and rpmb are full of zeroes. Run: . ./sd_fusing.sh /dev/mmcblk0boot0 ` Watch the output -- it has no error detection at all and will lie that all went ok even if it didn't! Now pray and reboot. u-boot console -- Fortunately, unlike some other SoCs, modern u-boot _can_ boot both vendor and mainline kernels. Be prepared to do some manual loading, though. For convenience, here are relevant bits of old /boot/boot.scr: . setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; fatload mmc 0:1 0x4200 uInitrd; bootm 0x40008000 0x4200" setenv bootargs "console=tty1 console=ttySAC1,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro mem=2047M" ` If boot fails, type the commands inside bootcmd manually, perhaps replacing "fatload" with "ext4load" (also helpful "ext4ls mmc 0:1" and so on). The "bootm"
Bug#853855: di-utils: Kernel boot options containing a dot are not propagated to the installed system
BTW the jenkins tests have now been duplicated on the proper jenkins.debian.net setup. The successful run using the pu/bug-853855 branches of di-utils and rootskel is here: https://jenkins.debian.net/job/lvc_debian-miniiso/355/console and the same test failing with the current daily build is here (look for "did not give the expected outcome"): https://jenkins.debian.net/view/lvc/job/lvc_debian-DI-miniiso-gui-daily-bugtest/3/console Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Bug#858299: installer doesn't load on an acer Aspire one
Stable (8.7) doesn't work, too. I just checked it's an old Debian 7 usb stick which works. With an Debian 8.7 usb stick I get also the line SYSLINUX 6.03 EDD [...] and then only a cursor.
Bug#858308: flash-kernel: documentation for upgrading Odroid-U2/U3 to flash-kernel
On Tue, 2017-03-21 at 00:31 +0100, Adam Borowski wrote: > Package: flash-kernel Not sure that this (or u-boot) is really the best place for it, it certainly wouldn't occur to look under either of those packages for such documentation. Perhaps a wiki page under wiki.debian.org/DebianOn might be better? Or the installation guide perhaps? Ian.
Bug#858308: flash-kernel: documentation for upgrading Odroid-U2/U3 to flash-kernel
On Tue, Mar 21, 2017 at 09:45:01AM +, Ian Campbell wrote: > On Tue, 2017-03-21 at 00:31 +0100, Adam Borowski wrote: > > Package: flash-kernel > > Not sure that this (or u-boot) is really the best place for it, it > certainly wouldn't occur to look under either of those packages for > such documentation. This doc is for converting to flash-kernel (and other modern bits), thus I went for flash-kernel first. You guys know what would be appropriate better than me. > Perhaps a wiki page under wiki.debian.org/DebianOn might be better? Or > the installation guide perhaps? It's not installation, merely upgrading from parts shipped by the vendor. You need their parts to even boot from eMMC, and the only way I know to put Debian pieces to eMMC is... booting from said eMMC. -- ⢀⣴⠾⠻⢶⣦⠀ Meow! ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second ⠈⠳⣄ preimage for double rot13!
Re: Installing chapter in the release notes
Hi Vince, Dixit Vincent McIntyre, le 20/03/2017 : >> +ifname instead of mac address ... >Not having really worked with stretch yet (ie target audience member), >I'm had no real idea what this meant when I first read it. Found in the Alpha 1 release annoucement: https://www.debian.org/devel/debian-installer/News/2015/20150721 linking to this thread: https://lists.debian.org/debian-devel/2015/05/msg00170.html >Can you say what you mean in fuller terms that we could pare back >to something suitable for the notes? I understand it as: Network interfaces will be named using their firmware/BIOS name, or their physical location, or using a static mapping (as before). This won't depend on the discoveriong order. This won't apply for the upgrade. (I see it as the /dev/hdXY -> UUID transition) >Currently jessie systems use e.g. eth0 for the interface names. >Reading [1] it seems it is possible to use the MAC address, eg >enx78e7d1ea46da for the interface with MAC 78:e7:d1:ea:46:da. Reading it (thanks for the link), I see that mac-adress naming is available but not used. So network interfaces will have unusual name, but not as exotic as this! >IIUC your text is stating that the eth0 scheme will be default? I try to say the opposite! Baptiste [1] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ pgpa9sry0tvDs.pgp Description: OpenPGP digital signature
speech-enabled expert/rescue/autoinstall keyboard shortcuts
Hello, Somehow somebody managed to raise that there is no menu entry for starting the rescue mode with speech synthesis enabled. That actually also raises the question of doing the same for expert install and automated install. It's really a matter of adding the menu entry: just copy/paste the existing expert/rescue/automated entries, and append speakup.synth=soft to it. Now the question is: which keyboard shortcut to use? For now, the only documented accessible keyboard shortcut is "s" to start a speech-enabled installation. I guess we don't want to add yet other entries to the main menu, so we'd put these additional entries under the "advanced options" submenu, which already has shortcut "a". However, the natural "e", "r" and "a" shortcuts are already taken for the non-speech versions. Would it really be a problem to change the meaning of those shortcuts, to make them start the speech versions instead of the non-speech version? I have to say I myself never used those shortcuts, since it's so fast to just move down a few times when one is sighted :) Samuel
Re: speech-enabled expert/rescue/autoinstall keyboard shortcuts
On Wed, Mar 22, 2017 at 01:40:11AM +0100, Samuel Thibault wrote: >Hello, > >Somehow somebody managed to raise that there is no menu entry for >starting the rescue mode with speech synthesis enabled. That actually >also raises the question of doing the same for expert install and >automated install. > >It's really a matter of adding the menu entry: just copy/paste the >existing expert/rescue/automated entries, and append speakup.synth=soft >to it. > >Now the question is: which keyboard shortcut to use? > >For now, the only documented accessible keyboard shortcut is "s" to >start a speech-enabled installation. I guess we don't want to add yet >other entries to the main menu, so we'd put these additional entries >under the "advanced options" submenu, which already has shortcut "a". >However, the natural "e", "r" and "a" shortcuts are already taken for >the non-speech versions. > >Would it really be a problem to change the meaning of those shortcuts, >to make them start the speech versions instead of the non-speech >version? I have to say I myself never used those shortcuts, since it's >so fast to just move down a few times when one is sighted :) I've personally never used the shortcuts, but I'd be curious if anybody might be for automated testing possibly? It'd be easier to do that than parse the boot menus... -- Steve McIntyre, Cambridge, UK.st...@einval.com < sladen> I actually stayed in a hotel and arrived to find a post-it note stuck to the mini-bar saying "Paul: This fridge and fittings are the correct way around and do not need altering"
Re: Bug#858066: unblock: xfsprogs/4.9.0+nmu1
Hi, Emilio Pozuelo Monfort (2017-03-19): > Approved, but needs d-i ack, cc'ing Cyril. Automated tests with a basic install on xfs show no regressions between testing and sid versions; so no objections, thanks. KiBi. signature.asc Description: Digital signature
Re: Installing chapter in the release notes
On Tue, Mar 21, 2017 at 09:45:24PM +0100, Baptiste Jammet wrote: > Hi Vince, > > Dixit Vincent McIntyre, le 20/03/2017 : > > >> +ifname instead of mac address > ... > >Not having really worked with stretch yet (ie target audience member), > >I'm had no real idea what this meant when I first read it. > Found in the Alpha 1 release annoucement: > https://www.debian.org/devel/debian-installer/News/2015/20150721 > linking to this thread: > https://lists.debian.org/debian-devel/2015/05/msg00170.html > Thanks for the background. I now see the terms 'ifname' and 'mac' have special meanings in this context. That's quite a thread to plow through but worth the read. Round 2 is here http://lists.debian.org/debian-devel/2015/06/msg00018.html But I failed to find the final resolution of this on a mailing list, the last word seems to be the Alpha 2 announcement https://www.debian.org/devel/debian-installer/News/2015/20150815 So let's take the version 2 proposal and try to work with that. + + +New method for naming network interfaces + + +The installer and newly installed systems will use a different +naming scheme for network interfaces instead of eth0, eth1 etc. +The old naming method suffered from enumeration race conditions +that made it possible for interface names to change unexpectedly +and is incompatible with mounting the root filesystem read-only. +The new enumeration method relies on more sources of information, +to produce a more repeatable outcome. It uses the firmware/BIOS +provided index numbers and then tries PCI card slot numbers, +producing names line ens0 or enp1s1 (ethernet) or wlp3s0 (wlan). +USB devices, which can be added to the system at any time, +will have names based upon their ethernet MAC addresses. + + +This change does not apply to upgrades of jessie systems, +the naming will continue to be enforced by +/etc/udev/rules.d/70-persistent-net.rules. +For more information, see /usr/share/doc/udev/README.Debian.gz + + + > I understand it as: Network interfaces will be named using their > firmware/BIOS name, or their physical location, or using a static > mapping (as before). This won't depend on the discoveriong order. > This won't apply for the upgrade. > (I see it as the /dev/hdXY -> UUID transition) My suggested text above is far from the final word here and I have questions: * Is it even accurate? * How are the firmware/BIOS and PCI slot methods that were discussed related to the NamePolicy methods in the udev file: NamePolicy=kernel database onboard mac * Is biosdevname still out of the picture? Cheers Vince PS it would be nice to have a cumulative list of all changes (wiki?) as well as the debian-installer/News items. Happy to help with setting something up if I can.
Re: speech-enabled expert/rescue/autoinstall keyboard shortcuts
And what about affecting shift-s or ctrl-s to run tts in the rescue mode? Doesn't seem so hard for user, and avoids to change further. And easy to remebrer as related to original "s" used today. But is it possible to set multikexs bindings? Le 22/03/2017 à 01:40, Samuel Thibault a écrit : > Hello, > > Somehow somebody managed to raise that there is no menu entry for > starting the rescue mode with speech synthesis enabled. That actually > also raises the question of doing the same for expert install and > automated install. > > It's really a matter of adding the menu entry: just copy/paste the > existing expert/rescue/automated entries, and append speakup.synth=soft > to it. > > Now the question is: which keyboard shortcut to use? > > For now, the only documented accessible keyboard shortcut is "s" to > start a speech-enabled installation. I guess we don't want to add yet > other entries to the main menu, so we'd put these additional entries > under the "advanced options" submenu, which already has shortcut "a". > However, the natural "e", "r" and "a" shortcuts are already taken for > the non-speech versions. > > Would it really be a problem to change the meaning of those shortcuts, > to make them start the speech versions instead of the non-speech > version? I have to say I myself never used those shortcuts, since it's > so fast to just move down a few times when one is sighted :) > > Samuel > > -- Jean-Philippe MENGUAL HYPRA, progressons ensemble Tél.: 01 84 73 06 61 Mail: cont...@hypra.fr Site Web: http://hypra.fr
