Installed Debian Jessie fails to recognize USB flash drive upon reboot
Package: Installation-reports Severity: Serious After successful installation using the USB thumb drive method, the installed OS fails to recognize the same USB drive. Boot method: USB flash drive Image version: Beta 2 installer amd64 DVD1 (burned the ISO to USB stick) Date: Oct 2014 Machine: DIY Partitions: Entire disk drive 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 ] Clock/timezone setup: [o ] User/password setup: [o ] Detect hard drives: [o ] Partition hard drives:[o ] Install base system: [o ] Install tasks: [ ] Install boot loader: [o ] Overall install: [E ] Comments/Problems: Although I burned the Debian Jessie beta 2 DVD-1 to a USB flash drive, during the installation process, I chose to do a base/net install only as I wanted to install only the packages that I needed. I did not wish to have the full Gnome, KDE, LXDE desktop environments. Upon reboot, I was presented with a black-background console, tty1, and typed in my login username and password. I proceeded to sudo apt-get install xorg gnome-core and failed, the reason being the CDROM was missing. Well, I re-inserted the USB flash drive and re-typed the same command. Again the machine responded with the CDROM was missing. I have been told that the above problem has existed since the days of pre-Debian Wheezy. -- 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/223411414746...@web17g.yandex.ru
Re: Bug#762762: Updating isc-dhcp udeb to dynamically link bind (was: Bug#762762: nmu fixing bind issues)
On Thu, 30 Oct 2014 22:37:24 + Steven Chamberlain ste...@pyro.eu.org wrote: On 20/10/14 01:09, Michael Gilbert wrote: The new isc-dhcp is now uploaded. Please let me know how your testing goes. After the upload of bind9/1:9.9.5.dfsg-5, this does seem to be working well now in sid d-i. Thanks. Just tested the netinst daily image as of 2014-10-31: dhcp now works again in the installer. Regards, Herbert -- Herbert Kaminski D-26122 Oldenburg -- 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/20141031114225.2a0918b1@toshi
Re: Bug#762762: Updating isc-dhcp udeb to dynamically link bind
31.10.2014 13:42, Herbert Kaminski wrote: On Thu, 30 Oct 2014 22:37:24 + Steven Chamberlain ste...@pyro.eu.org wrote: On 20/10/14 01:09, Michael Gilbert wrote: The new isc-dhcp is now uploaded. Please let me know how your testing goes. After the upload of bind9/1:9.9.5.dfsg-5, this does seem to be working well now in sid d-i. Thanks. Just tested the netinst daily image as of 2014-10-31: dhcp now works again in the installer. Is it on kfreebsd, or on linux kernel too? I wonder maybe we should switch to isc-dhcp on all variants/arches, and ditch udhcpc... 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/54536809.2020...@msgid.tls.msk.ru
Bug#767474: Installation kFreeBSD-amd64, Kernel 10.1: OK, but still quirks
Package: installation-reports Boot method: CD Image version: Daily netinst kfreebsd-amd64 as of 2014-10-29 from http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/kfreebsd-amd64/iso-cd/ Date: 2014-10-30 15:00 CEST Machine: noname Processor: Athlon64 X2 Memory: 2GByte Partitions: Disk /dev/ada0: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000919f8 Device Boot Start End Blocks Id System /dev/ada0p1 63 5863724 2931831 82 Linux swap / Solaris /dev/ada0p2 * 5863725 10352192848829102 a5 FreeBSD /dev/ada0p3 103522860 144541695205094187 HPFS/NTFS/exFAT /dev/ada0p4 201182056 488392064 143605004+ f W95 Ext'd (LBA) /dev/ada0p5 201182058 214853309 6835626 83 Linux /dev/ada0p6 214853373 29967650942411568+ 7 HPFS/NTFS/exFAT /dev/ada0p7 299676573 48063266990478048+ 83 Linux /dev/ada0p8 480632733 488392064 3879666 83 Linux Output of lspci -knn (or lspci -nn): 00:00.0 RAM memory [0500]: NVIDIA Corporation MCP67 Memory Controller [10de:0547] (rev a2) 00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP67 ISA Bridge [10de:0548] (rev a2) 00:01.1 SMBus [0c05]: NVIDIA Corporation MCP67 SMBus [10de:0542] (rev a2) 00:01.2 RAM memory [0500]: NVIDIA Corporation MCP67 Memory Controller [10de:0541] (rev a2) 00:02.0 USB controller [0c03]: NVIDIA Corporation MCP67 OHCI USB 1.1 Controller [10de:055e] (rev a2) 00:02.1 USB controller [0c03]: NVIDIA Corporation MCP67 EHCI USB 2.0 Controller [10de:055f] (rev a2) 00:04.0 USB controller [0c03]: NVIDIA Corporation MCP67 OHCI USB 1.1 Controller [10de:055e] (rev a2) 00:04.1 USB controller [0c03]: NVIDIA Corporation MCP67 EHCI USB 2.0 Controller [10de:055f] (rev a2) 00:06.0 IDE interface [0101]: NVIDIA Corporation MCP67 IDE Controller [10de:0560] (rev a1) 00:07.0 Audio device [0403]: NVIDIA Corporation MCP67 High Definition Audio [10de:055c] (rev a1) 00:08.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Bridge [10de:0561] (rev a2) 00:09.0 SATA controller [0106]: NVIDIA Corporation MCP67 AHCI Controller [10de:0554] (rev a2) 00:0b.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0562] (rev a2) 00:0c.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:0d.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:0e.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:0f.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:10.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:11.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express Bridge [10de:0563] (rev a2) 00:12.0 VGA compatible controller [0300]: NVIDIA Corporation C68 [GeForce 7025 / nForce 630a] [10de:053e] (rev a2) 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] 04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 01) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[O] Comments/Problems: I did several installations on this machine and a similar one. Installation itself was mostly OK, with some errors in the installed system, most were also observed in earlier installations, c.f. #762401 and #766423): - grub-install or update-grub did not recognize any other OS on the disk, not even a second instance of kFreeBSD, or FreeBSD proper. - grub-install was not able to install grub if the file system root was on a logical partition. Putting /boot on a primary partition did not help. (This was not tried in earlier installations) - X server (vesa instead of nv) did not recognize optimal screen resolution (1024x768 instead of 1280x1024), no way to change that. On the other machine with ATI/AMD graphics,
Bug#767480: d-i fails to install grub to first disk/partition with preseeding (hd0) or (hd0,0)
Package: debian-installer Version: daily-20141030 Architecture: amd64 Hi, i am using the daily build of the netboot images as of yesterday. The Documentation at: https://www.debian.org/releases/jessie/amd64/apbs04.html.en say that preseeding Grub with: d-i grub-installer/bootdev string (hd0,0) Should install grub in the first partition. Currently this fails with Unable to install GRUB in (hd0,0) Executing 'grub-install (hd0,0) failed. This is a fatal error. My hd0 is a virtio block device /dev/vda in a KVM host and its the only disk. Also d-i grub-installer/bootdev string (hd0) Does not work. Not preseeding this value will display a manual entry box. As with wheezy the first disk (and in my case only disk) will always be used as default, this doesnt seem to work anymore. Preseeding with /dev/vda will work though. Flo -- Florian Lohoff f...@zz.de signature.asc Description: Digital signature
Bug#767480: d-i fails to install grub to first disk/partition with preseeding (hd0) or (hd0,0)
Hi Florian, On Fri, Oct 31, 2014 at 12:41:34PM +0100, Florian Lohoff wrote: Package: debian-installer Version: daily-20141030 Architecture: amd64 Hi, i am using the daily build of the netboot images as of yesterday. The Documentation at: https://www.debian.org/releases/jessie/amd64/apbs04.html.en say that preseeding Grub with: d-i grub-installer/bootdev string (hd0,0) Should install grub in the first partition. Currently this fails with Unable to install GRUB in (hd0,0) Executing 'grub-install (hd0,0) failed. This is a fatal error. My hd0 is a virtio block device /dev/vda in a KVM host and its the only disk. Also d-i grub-installer/bootdev string (hd0) Does not work. Not preseeding this value will display a manual entry box. As with wheezy the first disk (and in my case only disk) will always be used as default, this doesnt seem to work anymore. Preseeding with /dev/vda will work though Your problem seen to be the same as for https://bugs.debian.org/712907 Regards, Salvatore -- 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/20141031120435.GA28937@eldamar.local
Bug#767487: debian-installer: virtio support for powerpc cdrom/netboot installs
Package: debian-installer
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: powerpc
Dear Maintainer,
virtio modules are more and more used in VMs and it would be nice to have those
into the netboot and cdrom installers for powerpc on which there are not at the
moment. I'm currently in need of these for ppc64 testing.
On ppc64el these were already added in a previous patch (#754093) I sent but I
should have think of powerpc too.
Thank you for your help,
F.
Index: debian-installer/installer/build/pkg-lists/cdrom/powerpc.cfg
===
--- debian-installer.orig/installer/build/pkg-lists/cdrom/powerpc.cfg 2014-10-31 10:46:54.285199730 +0100
+++ debian-installer/installer/build/pkg-lists/cdrom/powerpc.cfg 2014-10-31 13:01:23.162166973 +0100
@@ -18,6 +18,7 @@
pcmcia-storage-modules-${kernel:Version}
pcmcia-modules-${kernel:Version}
pcmciautils-udeb
+virtio-modules-${kernel:Version}
# Support for USB CD-ROMs
usb-storage-modules-${kernel:Version}
Index: debian-installer/installer/build/pkg-lists/netboot/powerpc.cfg
===
--- debian-installer.orig/installer/build/pkg-lists/netboot/powerpc.cfg 2014-10-31 10:46:54.289199728 +0100
+++ debian-installer/installer/build/pkg-lists/netboot/powerpc.cfg 2014-10-31 12:57:39.126163007 +0100
@@ -9,6 +9,7 @@
pcmciautils-udeb
#fb-modules-${kernel:Version}
usb-modules-${kernel:Version}
+virtio-modules-${kernel:Version}
console-setup-udeb
kbd-udeb
Bug#767474: Installation kFreeBSD-amd64, Kernel 10.1: OK, but still quirks
Hi, Many thanks for testing on real hardware. Adding my comments below; I'll further investigate some of the issues myself, but anyone else is welcome to look into these or the other points in the original mail: On 31/10/14 10:41, Herbert Kaminski wrote: - grub-install was not able to install grub if the file system root was on a logical partition. I once thought that was a limitation of what the FreeBSD kernel can use as a root device. In that case it should be more clearly documented. Or if not, it may turn out to be a bug in grub-probe. Putting /boot on a primary partition did not help. This needs to be investigated using grub-install and grub-probe by hand. It may also be worth trying to move /lib/modules into /boot/ then creating a symlink /lib/modules - /boot/modules. - a regression: now xfburn finds the CDR drive only when started by root. /dev/cd0 is owned by root:cdrom, and the standard user is member of the cdrom group. Is /dev/cd0 readable and/or writable by the group? Does changing that fix it? This will be determined by devfs rules in /etc. - in XFCE, all menu entries or buttons to shutdown, reboot etc are greyed, FWIW I don't see this bug on my own kfreebsd-amd64 sid/jessie install. and the notification area in the panel is only a vertcal bar. Obvious question, but were any applications running that would actually display something there? If I install+run something like psi-plus, then it correctly displays there. - in the installer, DHCP did not work. Fixed in sid AIUI: http://lists.debian.org/20141031114225.2a0918b1@toshi So, kFreeBSD on the desktop is usable after some manual intervention, if you do not use a NVidia graphics card. The nv driver should support at least *some* nVidia cards, perhaps older and not integrated chipsets. I've started a Wiki page where we can start to collect data on this: https://wiki.debian.org/Debian_GNU/kFreeBSD_Hardware#Graphics_cards The vesa fallback should be good enough for at least some uses. Regards, -- Steven Chamberlain ste...@pyro.eu.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/5453838a.1030...@pyro.eu.org
Re: Bug#762762: Updating isc-dhcp udeb to dynamically link bind
On Fri, 31 Oct 2014 13:44:25 +0300 Michael Tokarev m...@tls.msk.ru wrote: 31.10.2014 13:42, Herbert Kaminski wrote: Just tested the netinst daily image as of 2014-10-31: dhcp now works again in the installer. Is it on kfreebsd, or on linux kernel too? I wonder maybe we should switch to isc-dhcp on all variants/arches, and ditch udhcpc... I tested the linux netinst-amd64 daily yesterday, and DHCP was OK. I do linux test installations about once a week and never saw a DHCP problem. Herbert -- Herbert Kaminski D-26122 Oldenburg -- 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/20141031144452.1de7a62d@toshi
Re: Bug#762762: Updating isc-dhcp udeb to dynamically link bind
On 31/10/14 10:44, Michael Tokarev wrote: Is it on kfreebsd, or on linux kernel too? I wonder maybe we should switch to isc-dhcp on all variants/arches, and ditch udhcpc... Linux d-i only uses udhcpc at the moment. (Ubuntu uses isc-dhcp though IIRC). We did discuss converging on a single DHCP client across all Debian architectures, but: * it's way too late to do this for jessie, I doubt KiBi would even hear of it! d-i can be very sensitive to changes and this might break in non-obvious use cases that don't get tested much * for jessie+1, I think it's still early to decide this yet. I know that systemd will have a DHCP client - d-i doesn't currently use systemd, but who knows what could happen in 2 years; we also don't know yet if there'll be a kfreebsd in jessie+1 officially So I think we might come back to this a while after jessie is released. Regards, -- Steven Chamberlain ste...@pyro.eu.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/54539536.9030...@pyro.eu.org
Bug#767474: Installation kFreeBSD-amd64, Kernel 10.1: OK, but still quirks
Am Fri, 31 Oct 2014 12:41:46 + schrieb Steven Chamberlain ste...@pyro.eu.org: On 31/10/14 10:41, Herbert Kaminski wrote: - grub-install was not able to install grub if the file system root was on a logical partition. I once thought that was a limitation of what the FreeBSD kernel can use as a root device. In that case it should be more clearly documented. Or if not, it may turn out to be a bug in grub-probe. On VT4, grub-install complains that it is unable to determine the BIOS drive of the root partition and that I should check the map file, which I can't because there is none... - a regression: now xfburn finds the CDR drive only when started by root. /dev/cd0 is owned by root:cdrom, and the standard user is member of the cdrom group. Is /dev/cd0 readable and/or writable by the group? Does changing that fix it? This will be determined by devfs rules in /etc. It was rw for the group. chmod o+rw or a+w did not help either. and the notification area in the panel is only a vertcal bar. Obvious question, but were any applications running that would actually display something there? If I install+run something like psi-plus, then it correctly displays there. Installed psi-plus and started it: Voila, a star in the notification area! The nv driver should support at least *some* nVidia cards, perhaps older and not integrated chipsets. I've started a Wiki page where we can start to collect data on this: https://wiki.debian.org/Debian_GNU/kFreeBSD_Hardware#Graphics_cards When I got some more time, I will test that dozen old NVidia cards in my trash bin ;-) and report the results. The vesa fallback should be good enough for at least some uses. Sure, if 1024*768 or the text console is enough. Herbert -- -- 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/20141031162848.70611...@gmx.de
d-i bugs and freeze
Hi KiBi,
I'd like to fix d-i bugs, but I wonder how the impending freeze
affects this:
* may I still commit a non-RC bug fix to master
* is it likely to be uploaded to sid
* is it likely to get an unblock
As a real example, right now I have a fix for an issue mentioned in
two install reports, which I'd consider severity 'important'.
https://lists.debian.org/debian-bsd/2014/09/msg00125.html
| grub-mkdevicemap (in /target chroot) did not detect any (virtio)
| hard disks. I had to Enter device manually in the dialog and
| specify /dev/vtbd0, which worked.
https://lists.debian.org/debian-bsd/2014/10/msg00445.html
| Apart from that, the grub install step was not able to find the
| disk/partition by default, so I had to specify it in the prompt as
| '/dev/xbd0'.
And the rather simple change is attached. Not sure what to do.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index 463efd1..dcff27e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+grub-installer (1.101) UNRELEASED; urgency=medium
+
+ * In device_to_disk, recognise vtbd (KVM virtio) and xbd (Xen)
+disk devices on kfreebsd
+
+ -- Steven Chamberlain ste...@pyro.eu.org Fri, 31 Oct 2014 23:28:01 +
+
grub-installer (1.100) unstable; urgency=medium
[ Colin Watson ]
diff --git a/grub-installer b/grub-installer
index 2b61fb6..c29f2f1 100755
--- a/grub-installer
+++ b/grub-installer
@@ -134,7 +134,7 @@ hurd_convert () {
# This should probably be rewritten using udevadm or similar.
device_to_disk () {
echo $1 | \
- sed 's:\(/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'
+ sed 's:\(/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da|vtbd|xbd\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'
}
# Run update-grub in $ROOT
Bug#765839: some more data
I asked around, and: arm: Broadcom/VideoCore: not working. Adreno: unfortunately, Maarten Lankhorst (xserver-xorg-video-freedreno maintainer) says his only board just broke, and thus he's unable to test. This is sad as this driver is known to work on Fedora for at least some version of gnome -- it'd be nice to know whether it's a problem with drivers, gnome stack in Debian (cogl as Josselin suspects?) or perhaps just configuration. Other architectures: I did not get any answer. So for now there's not a single report of gnome on !amd64 !i386 working... -- // If you believe in so-called intellectual property, please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- 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/20141101020027.ga18...@angband.pl
default DE requalification: quality of task
Hi! In the default desktop environment requalification table, I think gnome's score for task quality should be downgraded -- although it might be better to axe the whole category. There are two criteria listed: * quality: task-gnome has the distinction of being the only desktop task with a severe bug. Installing a non-working desktop on all but two architectures (or at least a good part of machines for those architectures) counts as pretty bad in my book... * testing: as XFCE was the default for most of jessie's development, no one noticed what dropping of gnome-fallback really means, until recently. So, I'd say the correct score would be -1 rather than +1... However, I kind of fail to see the point of giving two whole points for something as minor as the tasksel task. It's just a link to the DE's primary metapackage plus a few goodies -- nothing as important as complete translations, etc. So what about removing this line instead of arguing? Meow! -- // If you believe in so-called intellectual property, please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- 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/20141101025829.gb18...@angband.pl
desktop requalification: KDE seems to be portable
Hi! I see the field for KDE/portability is left as a question mark. In case you won't get answers from official porters soon, I can confirm KDE does work at least on: * real metal: an armhf laptop * qemu: powerpc If you wish, I can test on more arms, and on anything qemu offers. I did notice, though, that on both of those setups KDE is excruciatingly slow. LXDE and Mate are decently fast, XFCE somewhat slower than these two... while with KDE, it's more like half a minute before a menu pops up. Qemu in true emulation mode is not exactly a speed demon, that laptop is damn weak as arms go[1], but this kind of speeds might be bad on less powerful x86 too. Thus, if by portability you mean works everywhere, please give it +1. If you want to extend this field to also include works well on weak hardware, I'd score it at 0. [1]. 1x1.2Ghz 1GB ram. -- // If you believe in so-called intellectual property, please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- 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/20141101032805.gc18...@angband.pl
Re: desktop requalification: KDE seems to be portable
On Sat, Nov 01, 2014 at 04:28:05AM +0100, Adam Borowski wrote: I see the field for KDE/portability is left as a question mark. In case you won't get answers from official porters soon, I can confirm KDE does work at least on: * real metal: an armhf laptop * qemu: powerpc Not so good on kfreebsd-amd64, though. Current d-i daily, KDE task: after kdm login, there's nothing but a wallpaper, cursor and a disk icon, clicking it makes the icon disappear and from that point nothing works. -- // If you believe in so-called intellectual property, please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- 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/20141101041332.ga24...@angband.pl
