Bug#767474: Installation kFreeBSD-amd64, Kernel 10.1: OK, but still quirks
On Fri, 31 Oct 2014 11:41:51 +0100 Herbert Kaminski wrote: > - in XFCE, all menu entries or buttons to shutdown, reboot etc are greyed, >and the notification area in the panel is only a vertcal bar. On the same >hardware, I installed linux/XFCE and then removed systemd as described in >http://www.vitavonnni.de/blog/201410/2014102101-avoiding-systemd.htmlto be >This caused the same effect. I repeated this on a new installation of linux jessie, but uninstalled the dependencies of systemd one after the other. The shutdown/reboot controls were greyed after removing policykit and its depedencies. But policykit ist still there in kFreeBSD. So I am out of ideas about what/how to test further. 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/20141105212509.12c5efbe@toshi
Bug#767474: Installation kFreeBSD-amd64, Kernel 10.1: OK, but still quirks
Am Fri, 31 Oct 2014 12:41:46 + schrieb Steven Chamberlain : > 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
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
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, thi
