Bug#772796: debian installer don't detect dmraid/sataraid/fakeraid
package: installation-reports severity: critical It took a long research online to finally install wheezy on Dell PowerEdge T20 server. I had to manually enter dmraid=true at installer prompt and then manually install grub. Bug report against grub for correctly installing when dmraid=true is set is here http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772795 Debian Installer should be able to detect if the system has a fakeraid and then load dm-raid module. signature.asc Description: OpenPGP digital signature
Re: Bug#771208: unblock: busybox/1:1.22.0-14
Control: tags -1 moreinfo Hi Michael, On Thu, Nov 27, 2014 at 07:08:49PM +0300, Michael Tokarev wrote: #768876 is tagged jessie-ignore so I'm really unconvinced by the debian/rules changes. It is jessie-ignore just to be non-RC. The fun with static linking and bugs it discovered shows that proper Built-Using field is really necessary (it is what #768876 is about). I guess by 'really necessary' you mean 'helps debugging', which isn't the same. This bug is jessie-ignore precisely because we want to avoid accepting complicated changes for jessie to fix it. However, bulk of d/rules changes are due to another build fix, to stop building arch-all package (busybox-syslogd) when building binary-arch. This one isn't RC at all, and can be fixed for stretch. Plus one block of added lines to check whenever libc is able to produce working statically-linked executables. This also looks like something for stretch. At this stage, I'd rather see the security fix only. Release team people, what's your take on this? As the libc issue with the static binary seems to be fixed in the libc version in both jessie and sid, the only remaining issue is the missing build-using, which can wait till after jessie. Could you do a new upload with only the security fix? Cheers, Ivo -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141211075205.gb16...@ugent.be
Bug#745717: di-utils: fetch-url runs mountmedia without cleaning up; blocks partitioner preseeding
This bug also affects the hd-media installer. With hd-media installer, iso-scan will try mount each partition to find isos with the following command: mount -t auto -o ro $device /hd-media Since the partition contains preseed file, which very likely contains the iso file, is mounted, this mount will fail, and iso-scan will eventually fail to find the iso file. The same problem also exists in /usr/lib/fetch-url/floppy, which also mount partitions without umount. I personally modified fetch-url/file and fetch-url/floppy, added `umount /media || true` before every return path, then the installer works incorrectly.
Processed: grub install should work once dm-raid is loaded
Processing commands for cont...@bugs.debian.org: block 772796 by 772795 Bug #772796 [installation-reports] debian installer don't detect dmraid/sataraid/fakeraid 772796 was not blocked by any bugs. 772796 was not blocking any bugs. Added blocking bug(s) of 772796: 772795 End of message, stopping processing here. Please contact me if you need assistance. -- 772796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.141828542825453.transcr...@bugs.debian.org
Bug#745717: di-utils: fetch-url runs mountmedia without cleaning up; blocks partitioner preseeding
I personally modified fetch-url/file and fetch-url/floppy, added `umount /media || true` before every return path, then the installer works incorrectly. Sorry, typo here, then the installer works *correctly*. BTW, this bug may not be triggered that frequently. fetch-url is invoked such early that most filesystem modules are not modprobed, thus will just fail to mount. I'm using a self-compiled linux kernel with the d-i initrd.gz, I compiled all needed filesystem modules into the kernel, so come into this problem. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CA+WCkBhk1j6O5VLSJVwHSWpXXJQwdteU-pULy9SQBoSrW3jH=q...@mail.gmail.com
Re: Bug#772595: UEFI fixes, round 2
Ivo De Decker iv...@debian.org (2014-12-11): Hi, I unblocked both. On Tue, Dec 09, 2014 at 10:07:07AM +0100, Cyril Brulebois wrote: Steve McIntyre st...@einval.com (2014-12-08): Clearly, this is also d-i material. KiBi has been letting me drive this, and I hope he's still happy here. I've added d-boot in CC accordingly. Clearly, he's still happy here. Thanks! Does this mean I can add the unblock-udeb? Sorry, I should have made myself clear: yes, please. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141211090106.ga20...@mraw.org
Processed: severity of 772796 is normal
Processing commands for cont...@bugs.debian.org: severity 772796 normal Bug #772796 [installation-reports] debian installer don't detect dmraid/sataraid/fakeraid Severity set to 'normal' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 772796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.141828839310996.transcr...@bugs.debian.org
Re: Bug#771208: unblock: busybox/1:1.22.0-14
11.12.2014 10:52, Ivo De Decker wrote: [] As the libc issue with the static binary seems to be fixed in the libc version in both jessie and sid, the only remaining issue is the missing build-using, which can wait till after jessie. Could you do a new upload with only the security fix? I'll leave this and other maintenance of busybox to others. I especially selected only the changes which I think are necessary for jessie. But since we obviously have different criteria for this, and for some other things too, I'd rather not mess up with the package further. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/548967db.4050...@msgid.tls.msk.ru
Re: Bug#771208: unblock: busybox/1:1.22.0-14
Michael Tokarev m...@tls.msk.ru (2014-12-11): 11.12.2014 10:52, Ivo De Decker wrote: [] As the libc issue with the static binary seems to be fixed in the libc version in both jessie and sid, the only remaining issue is the missing build-using, which can wait till after jessie. Could you do a new upload with only the security fix? I'll leave this and other maintenance of busybox to others. I especially selected only the changes which I think are necessary for jessie. But since we obviously have different criteria for this, and for some other things too, I'd rather not mess up with the package further. Hi, can you please still push your master branch and tags to the git repository? Last commit there points to debian/1.22.0-9 which is 5 revisions old, at least if I'm reading cgit and gitk properly. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141211100207.gb28...@mraw.org
Re: Bug#771208: unblock: busybox/1:1.22.0-14
11.12.2014 13:02, Cyril Brulebois wrote: Hi, Hello can you please still push your master branch and tags to the git repository? Last commit there points to debian/1.22.0-9 which is 5 revisions old, at least if I'm reading cgit and gitk properly. Oh yeah. I'm sorry about that. Pushed now. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54896d0a.70...@msgid.tls.msk.ru
Re: Bug#772595: UEFI fixes, round 2
Hi, On Thu, Dec 11, 2014 at 10:01:06AM +0100, Cyril Brulebois wrote: I unblocked both. On Tue, Dec 09, 2014 at 10:07:07AM +0100, Cyril Brulebois wrote: Steve McIntyre st...@einval.com (2014-12-08): Clearly, this is also d-i material. KiBi has been letting me drive this, and I hope he's still happy here. I've added d-boot in CC accordingly. Clearly, he's still happy here. Thanks! Does this mean I can add the unblock-udeb? Sorry, I should have made myself clear: yes, please. Added unblock-udeb for both. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141211102814.ga18...@ugent.be
Re: Bug#771208: unblock: busybox/1:1.22.0-14
On Thursday 11 December 2014 08:52:05 Ivo De Decker wrote: #768876 is tagged jessie-ignore so I'm really unconvinced by the debian/rules changes. It is jessie-ignore just to be non-RC. The fun with static linking and bugs it discovered shows that proper Built-Using field is really necessary (it is what #768876 is about). I guess by 'really necessary' you mean 'helps debugging', which isn't the same. It's my understand that it's really recessary so that the DNS resolver in busybox-static works *at all* But since I already raised that point (msg #20), I won't bug about it any further. -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug #729401
Hi all, bug #729401 [1] is still opened and I can confirm is blocking installation with xfs as a default file system. How can we manage this? Is it possible to add xfs-progs to the installed packages if xfs is chosen in partition creation? Bye Stefano [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729401
Processed: Bug#769728: reassign to systemd
Processing commands for cont...@bugs.debian.org: reassign 769728 systemd Bug #769728 [installation-reports] [jessie daily 2014-11-15] installation-report: regression when deselecting the standard system utilities task Bug reassigned from package 'installation-reports' to 'systemd'. Ignoring request to alter found versions of bug #769728 to the same values previously set Ignoring request to alter fixed versions of bug #769728 to the same values previously set retitle 769728 Logind does not start properly on freshly installed minimal systems Bug #769728 [systemd] [jessie daily 2014-11-15] installation-report: regression when deselecting the standard system utilities task Changed Bug title to 'Logind does not start properly on freshly installed minimal systems' from '[jessie daily 2014-11-15] installation-report: regression when deselecting the standard system utilities task' thanks Stopping processing here. Please contact me if you need assistance. -- 769728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.141831361115856.transcr...@bugs.debian.org
Bug#772855: installation-reports: unable to connect to a wifi network on channel 13
Package: installation-reports Severity: important Dear Maintainer, I downloaded Debian 7.7 installation image[1]. I followed the installation procedure and chose wlan0 networki interface when asked to configure the primary network interface. Then there was no WLAN on the list of availble networks. It appeared after I changed channel on my AP from 13 to 1. I suspect the reason of this problem MAY be the default regulatory settings of wifi stack/card driver in the Linux kernel if it is prepared for the USA where, according to Wikipedia[2], the channel may be used only under certain conditions. [1] debian-7.7.0-amd64-i386-netinst.iso (md5 afc576c3886f9abab9ba886c4cd51a88) [2] https://en.wikipedia.org/wiki/List_of_WLAN_channels -- Było mi bardzo miło. --- Rurku. --- ... Łukasz--- To dobrze, że mnie słuchasz. ... Od tej pory wszystko może się zdarzyć. Akcja toczy się... signature.asc Description: PGP signature
Processed: Re: Bug#772855: installation-reports: unable to connect to a wifi network on channel 13
Processing control commands: tag -1 moreinfo Bug #772855 [installation-reports] installation-reports: unable to connect to a wifi network on channel 13 Added tag(s) moreinfo. -- 772855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b772855.1418331464898.transcr...@bugs.debian.org
Bug#772855: installation-reports: unable to connect to a wifi network on channel 13
Control: tag -1 moreinfo On Thu, 2014-12-11 at 19:28 +0100, Łukasz Stelmach wrote: Package: installation-reports Severity: important Dear Maintainer, I downloaded Debian 7.7 installation image[1]. I followed the installation procedure and chose wlan0 networki interface when asked to configure the primary network interface. Then there was no WLAN on the list of availble networks. It appeared after I changed channel on my AP from 13 to 1. I suspect the reason of this problem MAY be the default regulatory settings of wifi stack/card driver in the Linux kernel if it is prepared for the USA where, according to Wikipedia[2], the channel may be used only under certain conditions. [1] debian-7.7.0-amd64-i386-netinst.iso (md5 afc576c3886f9abab9ba886c4cd51a88) [2] https://en.wikipedia.org/wiki/List_of_WLAN_channels The default is to use the 'world' regulatory domain, not the US domain. This still allows scanning for and using an AP on all channels; it just doesn't allow transmissions above channel 11 until an AP is found. However this might be overridden based on the country setting of the wireless network adapter. Or a particular driver might not implement the regulations correctly. Please specify what wireless network adapter you are using (if it's something built in and you don't know, lspci or lsusb will help to identify it). Also please provide the system log from the installer. Ben. -- Ben Hutchings You can't have everything. Where would you put it? signature.asc Description: This is a digitally signed message part
Re: 7.8 dates
On Tue, Dec 09, 2014 at 08:33:51PM +, Adam Barratt wrote: Hi, In theory the 7.8 point release should be in December, but that's often a pain to organise. So let's look at January instead: 3rd / 4th - I'm busy on the Saturday 10th / 11th - Fine for me 17th / 18th - jmw's BSP 24th / 25th - I can do Saturday morning, but will be afk from early afternoon to Sunday afternoon 31st / 1st - Fine for me I think they're all fine for me, modulo the BSP weekend. -- Steve McIntyre, Cambridge, UK.st...@einval.com Is there anybody out there? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141212000803.gc21...@einval.com
Bug#772898: win32-loader testing and newer fails with TRANSLATE error
Package: win32-loader Version: 0.7.5 Hi, I just got a new laptop preinstalled with Windows 7 Pro, and naturally wanted to install Debian via win32-loader. I tried several times, with the testing and unstable versions of win32-loader, and picking either stable or daily d-i. Here is one of the paths I tried with both the testing and unstable versions, and the resulting error: 1. Launch win32-loader and approve Windows's UAC prompt. 2. Choose Expert mode 3. Choose KDE. 4. Choose daily d-i. 5. Deal with the check for known issues prompt somehow, I tried both yes and no. 6. Confirm keyboard layout (mine was us). 7. Proceed with install, not specifying any proxy server or other changes. I got this error: Error: http://d-i.debian.org/daily-images/amd64/daily//MD5SUMS/TRANSLATE; When I tried with stable win32-loader, this worked (and will shortly remove my ability to test until I get virtualized Windows in place). - Jimmy Kaplowitz ji...@debian.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141212011549.gc5...@kaplowitz.org
Having trouble adding local repository to remastered iso
I am trying to add a local reprepro created repository containing some custom debs along with all the deps that get hauled in with it. I built the repository by installing a stock 7.7, then apt-getting all software and retrieving the debs from /var/cache/apt/archives. Fired up reprepro to build the repository (containing both i386 and amd64) and reprepro chugs away and builds the repository without issues. reprepro config Origin: Wheezy Label: Wheezy install Codename: wheezy Architectures: i386 amd64 Components: main Description: Apt repository for Install The repository relative to the root of the iso is at /ads/apt/debian test@textbox:/var/opt/wheezy/master/ads/apt$ tree . `-- debian |-- dists | `-- wheezy | |-- Release | `-- main | |-- binary-amd64 | | |-- Packages | | |-- Packages.gz | | `-- Release | `-- binary-i386 | |-- Packages | |-- Packages.gz | `-- Release `-- pool Pertinent entries in my preseed are d-i apt-setup/local0/repository string \ file:/ads/apt/debian wheezy main d-i debian-installer/allow_unauthenticated boolean true Preseeded install works fine, installs the base system, but the additional repository never gets configured properly, resulting in the additional software not getting installed. But leaves a usable stock system. Installer logs when apt fails to find the files Dec 12 03:08:32 debconf: -- GET apt-setup/use_mirror Dec 12 03:08:32 debconf: -- 0 false Dec 12 03:08:32 debconf: -- PROGRESS SET 700 Dec 12 03:08:32 debconf: -- 0 OK Dec 12 03:08:32 apt-setup: warning: /usr/lib/apt-setup/generators/50mirror returned error code 1; discarding output Dec 12 03:08:32 debconf: -- PROGRESS SET 800 Dec 12 03:08:32 debconf: -- 0 OK Dec 12 03:08:32 debconf: -- PROGRESS INFO apt-setup/progress/local Dec 12 03:08:32 debconf: -- 0 OK Dec 12 03:08:32 debconf: -- GET apt-setup/local0/repository Dec 12 03:08:32 debconf: -- 0 file:/ads/apt/debian wheezy main Dec 12 03:08:32 debconf: -- GET apt-setup/local0/comment Dec 12 03:08:32 debconf: -- 10 apt-setup/local0/comment doesn't exist Dec 12 03:08:32 debconf: -- GET apt-setup/local0/key Dec 12 03:08:32 debconf: -- 10 apt-setup/local0/key doesn't exist Dec 12 03:08:32 debconf: -- GET apt-setup/local0/source Dec 12 03:08:32 debconf: -- 10 apt-setup/local0/source doesn't exist Dec 12 03:08:33 in-target: Ign file: wheezy Release.gpg Dec 12 03:08:33 debconf: -- PROGRESS SET 900 Dec 12 03:08:33 in-target: Ign file: wheezy Release Dec 12 03:08:33 in-target: Err file: wheezy/main amd64 Packages Dec 12 03:08:33 in-target: File not found Dec 12 03:08:33 in-target: Ign file: wheezy/main Translation-en_CA Dec 12 03:08:33 in-target: Ign file: wheezy/main Translation-en Dec 12 03:08:33 debconf: -- 0 OK Dec 12 03:08:33 in-target: W: Failed to fetch file:/ads/apt/debian/dists/wheezy/main/binary-amd64/Packages File not found Dec 12 03:08:33 in-target: Dec 12 03:08:33 in-target: E: Some index files failed to download. They have been ignored, or old ones used instead. I've tried changing the apt-setup/local0/repository string to each of the following and each time it fails to find the Packages file. file:/media/cdrom/ads/apt... file:/cdrom/ads/apt... I know the repo does work, after booting into the freshly installed system and mounting the cdrom, I can fix sources.list to point to /media/cdrom/ads/apt/debian and apt will update and install all apps fine. I had this working at one point with a simple repo using dpkg-scanpackages, but once we had to install i386 and amd64, started using reprepro to build the repo. So I'm assuming I've got some kind of syntax error/typo here. Thanks -- Ryan Braun Defence Weather Services Chief Information Officer Branch, Environment Canada CIV: 204-833-2500x2824 CSN: 257-2824 FAX: 204-833-2558 E-Mail: ryan.br...@ec.gc.ca -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141212033328.ga11...@infinity.isb.ec.gc.ca
Bug#772901: os-prober wrong output with grep 2.21 or later
Package: os-prober Version: 1.65 Tags: patch os-prober uses 'grep' in an unportable way, in that it assumes that the regular expression . matches the NUL byte (all zero bits). POSIX doesn't guarantee this, and as of grep 2.21 this might not work. If os-prober assumes GNU grep the fix should be fairly straightforward; please see the attached (untested) patch. If os-prober is intended to be portable to non-GNU grep, more hacking will be needed, as POSIX says grep has undefined behavior when given binary input data. For more details about this issue please see: https://bugzilla.redhat.com/show_bug.cgi?id=1172405 https://bugzilla.redhat.com/show_bug.cgi?id=1172804 http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19348 diff -pru os-prober/os-probes/mounted/x86/20microsoft os-prober-fix/os-probes/mounted/x86/20microsoft --- os-prober/os-probes/mounted/x86/20microsoft 2014-11-12 07:19:18.0 -0800 +++ os-prober-fix/os-probes/mounted/x86/20microsoft 2014-12-11 19:25:06.749770598 -0800 @@ -31,19 +31,19 @@ if item_in_dir -q bootmgr $2; then for boot in $(item_in_dir boot $2); do bcd=$(item_in_dir bcd $2/$boot) if [ -n $bcd ]; then - if grep -qs W.i.n.d.o.w.s. .8 $2/$boot/$bcd; then + if grep -aqs W.i.n.d.o.w.s. .8 $2/$boot/$bcd; then long=Windows 8 (loader) - elif grep -qs W.i.n.d.o.w.s. .7 $2/$boot/$bcd; then + elif grep -aqs W.i.n.d.o.w.s. .7 $2/$boot/$bcd; then long=Windows 7 (loader) - elif grep -qs W.i.n.d.o.w.s. .V.i.s.t.a $2/$boot/$bcd; then + elif grep -aqs W.i.n.d.o.w.s. .V.i.s.t.a $2/$boot/$bcd; then long=Windows Vista (loader) - elif grep -qs W.i.n.d.o.w.s. .S.e.r.v.e.r. .2.0.0.8. .R.2. $2/$boot/$bcd; then + elif grep -aqs W.i.n.d.o.w.s. .S.e.r.v.e.r. .2.0.0.8. .R.2. $2/$boot/$bcd; then long=Windows Server 2008 R2 (loader) - elif grep -qs W.i.n.d.o.w.s. .S.e.r.v.e.r. .2.0.0.8. $2/$boot/$bcd; then + elif grep -aqs W.i.n.d.o.w.s. .S.e.r.v.e.r. .2.0.0.8. $2/$boot/$bcd; then long=Windows Server 2008 (loader) - elif grep -qs W.i.n.d.o.w.s. .R.e.c.o.v.e.r.y. .E.n.v.i.r.o.n.m.e.n.t $2/$boot/$bcd; then + elif grep -aqs W.i.n.d.o.w.s. .R.e.c.o.v.e.r.y. .E.n.v.i.r.o.n.m.e.n.t $2/$boot/$bcd; then long=Windows Recovery Environment (loader) - elif grep -qs W.i.n.d.o.w.s. .S.e.t.u.p $2/$boot/$bcd; then + elif grep -aqs W.i.n.d.o.w.s. .S.e.t.u.p $2/$boot/$bcd; then long=Windows Recovery Environment (loader) else long=Windows Vista (loader) diff -pru os-prober/os-probes/mounted/x86/83haiku os-prober-fix/os-probes/mounted/x86/83haiku --- os-prober/os-probes/mounted/x86/83haiku 2014-09-28 14:04:17.0 -0700 +++ os-prober-fix/os-probes/mounted/x86/83haiku 2014-12-11 19:32:45.177765083 -0800 @@ -13,7 +13,7 @@ case $type in *) debug $partition is not a BeFS partition: exiting; exit 1 ;; esac -if head -c 512 $partition | grep -qs system.haiku_loader; then +if head -c 512 $partition | grep -aqs system.haiku_loader; then debug Stage 1 bootloader found else debug Stage 1 bootloader not found: exiting
Bug#772915: debian installer fails to set up initial partitions on ECS Liva
Package: installation-reports Boot method: USB drive Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/ Date: 2014-12-10 Machine: ECS Liva mini PC Processor: Intel Bay Trail-M N2807 Memory: 2GB Partitions: These are the current partitions after a successful Ubuntu desktop installation: /dev/mmcblk0p2 ext4 27455692 5615676 20422288 22% / none tmpfs4 0 4 0% /sys/fs/cgroup udev devtmpfs956596 4956592 1% /dev tmpfs tmpfs 1935401060192480 1% /run none tmpfs 5120 4 5116 1% /run/lock none tmpfs 967700 0967700 0% /run/shm none tmpfs 102400 0102400 0% /run/user /dev/mmcblk0p1 vfat5232483436519812 1% /boot/efi Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register [8086:0f00] (rev 0e) 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics Display [8086:0f31] (rev 0e) 00:14.0 USB controller [0c03]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series USB xHCI [8086:0f35] (rev 0e) 00:1a.0 Encryption controller [1080]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine [8086:0f18] (rev 0e) 00:1b.0 Audio device [0403]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller [8086:0f04] (rev 0e) 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:0f48] (rev 0e) 00:1c.1 PCI bridge [0604]: Intel Corporation Device [8086:0f4a] (rev 0e) 00:1c.2 PCI bridge [0604]: Intel Corporation Device [8086:0f4c] (rev 0e) 00:1c.3 PCI bridge [0604]: Intel Corporation Device [8086:0f4e] (rev 0e) 00:1f.0 ISA bridge [0601]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit [8086:0f1c] (rev 0e) 00:1f.3 SMBus [0c05]: Intel Corporation Device [8086:0f12] (rev 0e) 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: The installer detects the 32GB emmc, but when it attempts to create partitions on it, it fails each time. Based on other people's published experiences, Ubuntu desktop installer will work, but Debian, Ubuntu server, and other distros will not. I chose force UEFI when given the option. After successfully installing Ubuntu, I've now gone back and used the Debian installer again, changing the ext4 partition to btrfs, and formatting the vfat partition as the efi boot partition, and time it worked fine; I now have the system installed and working with Debian. -Sage -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ca+qewsnlm5q2-vmxg1qjot6nm8htkvjtnzldj41zpda7dwx...@mail.gmail.com
