Bug#650926: please include kfreebsd-9 images
Package: debian-cd Version: 3.1.7 Severity: wishlist Tags: patch Kernel of FreeBSD 9 is already available in unstable and supported by D-I. Please, could you include kfreebsd-image-9 packages in CD builds? Thanks -- System Information: Debian Release: 6.0.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 8.1-1-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Index: tools/generate_di+k_list === --- tools/generate_di+k_list (revision 2288) +++ tools/generate_di+k_list (working copy) @@ -204,6 +204,7 @@ #ifdef ARCH_kfreebsd_amd64 kfreebsd-image-8-amd64 +kfreebsd-image-9-amd64 grub-pc #endif @@ -211,6 +212,9 @@ kfreebsd-image-8-486 kfreebsd-image-8-686 kfreebsd-image-8-686-smp +kfreebsd-image-9-486 +kfreebsd-image-9-686 +kfreebsd-image-9-686-smp grub-pc libc0.1-i686 #endif
Bug#650859: typical weekend after black friday install, 2011 edition
Hi Joey, On Sat, Dec 3, 2011 at 20:46:45 -0400, Joey Hess wrote: > The graphics worked ok with stable's kernel; however when I upgraded the > kernel to 3.1.4-1 to try to get wifi working (which it did seem to), it > turned the display off as soon as the kernel did a mode switch on boot. Do you have the dmesg from that kernel? Thanks, Julien -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111204133841.gh3...@radis.cristau.org
Bug#650960: task-desktop: Please Recommends kerneloops-applet instead of kerneloops package
Package: task-desktop Version: 3.07 Severity: minor Hi, kerneloops package has been split into a kerneloops-applet and a kerneloops-daemon package, kerneloops package is now a transitional package. task-desktop should now Recommends kerneloops-applet instead. Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111204164140.78f7b...@fornost.bigon.be
Bug#650819: grub-installer: The contents of grub.cfg depend on the kernel installed
reassign 650819 os-prober 1.49 thanks On Sat 03 Dec 2011 at 14:08:21 +, Brian Potkin wrote: > In short: the 30_os-prober section of grub.cfg is empty when the kernel > installed is linux-image-686-pae but correctly written when > linux-image-486 is used. It becomes interesting if /usr/lib/os-probes/50mounted-tests from the 1,42 version of os-prober replaces the corresponding file on /target. With linux-image-686-pae the 30_os-prober section of grub.cfg still does not have any entries for a Linux OS but a Windows Vista OS is detected and recorded, Then, on replacing 50mounted-tests in /target/usr/lib/linux-boot-probes/ with the corresponding one from os-prober 1.42, the expected grub.cfg is generated. The methodology may not be the best but it seems sufficient to indicate the bug should be reassigned. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111204162435.GL3655@desktop
Bug#650239: Hello?
Are you guys going to help me or ain't you? For some reason during installation the "configure the package manager" is just skipped, so Synaptic can't work, Chrome can't install, and updates are either not found or disastrous. The file libcard3. (without a hyphenated addition to the filename) is not present, among others. How do I initiate configuring the package manager? I repeat: Are you guys going to help me or ain't you? PaB
Bug#650979: debian-installer: syslinux boot menu falls off the bottom of the screen
Package: debian-installer Version: 20110106+squeeze3+b1 Severity: normal The syslinux menu on squeeze installation media is configured in such a way that some of the menu entries, the "press TAB to edit a menu entry" message and the help messages fall off the bottom of the screen. I tested with netinst CDs and hd-media boot images, but I believe all installation media are configured in the same way. The configuration in stdmenu.cfg is this (comment included): menu vshift 17 menu rows 10 menu helpmsgrow 15 # The command line must be at least one line from the bottom. menu cmdlinerow 16 menu timeoutrow 16 menu tabmsgrow 18 There are 28 lines in VESA mode, according to the syslinux docs. With vshift set to 17 only 12 lines are available for the menu: the title and the hidden border use 4 lines so there are only 8 lines left for the menu entries. I'm attaching a screenshot from the amd64+i386 multiarch netinst CD's advanced menu (which is 13 lines long) where this problem is clearly visible: no item is selected because the selection went off the screen. Also, the "scrollbar" is not visible if the menu exceeds the configured number of lines, so the user has no clue that more entries are available. This is probably due to the choice of colors and the black background. A related, minor problem is that the display becomes corrupted if you edit a command line that is longer than one screen line: try for example to edit the "Graphical install" item on the multiarch netinst CD. This is because syslinux is smart enough to pull the command line within the visible screen, but then gets confused and scrolls things around wildly. I tried changing the configuration on a hd-media boot image like this: menu vshift 16 menu rows 7 menu helpmsgrow 12 menu cmdlinerow 12 menu tabmsgrow 13 It may need more tweaking, but at least all the menu entries and messages are within the screen whle still not covering the logo. Only a few menus have more than 7 entries. If further space is wanted, I'd suggest moving the logo up, there's plenty of black pixels at the top of the image. IMHO, the old boot screen was neater and looked defintely less "toyish", by the way. -- System Information: Debian Release: 6.0.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable'), (500, 'stable'), (400, 'testing'), (99, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111204190455.25708.56766.report...@forza.casa
Bug#650979: broken boot menu
Screenshot from the amd64+i386 multiarch netinst CD's advanced menu (which is 13 lines long) where no item is selected because the selection went off the screen. -- Ciao, Flavio Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer <>
Processed: Bug#650819: grub-installer: The contents of grub.cfg depend on the kernel installed
Processing commands for cont...@bugs.debian.org: > reassign 650819 os-prober 1.49 Bug #650819 [grub-installer] grub-installer: The contents of grub.cfg depend on the kernel installed Bug reassigned from package 'grub-installer' to 'os-prober'. Bug #650819 [os-prober] grub-installer: The contents of grub.cfg depend on the kernel installed Bug Marked as found in versions os-prober/1.49. > thanks Stopping processing here. Please contact me if you need assistance. -- 650819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650819 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: http://lists.debian.org/handler.s.c.132302663325361.transcr...@bugs.debian.org
Bug#650859: typical weekend after black friday install, 2011 edition
WRT to grub's menu not having windows in it, I found this in the syslog: Dec 3 13:18:11 kernel: [ 1108.179415] NTFS-fs warning (device sda2): load_system_files(): Volume is dirty. Will not be able to remount read-write. Run chkdsk and mount in Windows. Dec 3 13:18:11 50mounted-tests: debug: mounted as ntfs filesystem Dec 3 13:18:11 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/10freedos Dec 3 13:18:11 10freedos: debug: /dev/sda2 is not a FAT partition: exiting Dec 3 13:18:11 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/10qnx Dec 3 13:18:12 10qnx: debug: /dev/sda2 is not a QNX4 partition: exiting Dec 3 13:18:12 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/20macosx Dec 3 13:18:12 macosx-prober: debug: /dev/sda2 is not an HFS+ partition: exiting Dec 3 13:18:12 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/20microsoft Dec 3 13:18:12 20microsoft: debug: /dev/sda2 is a NTFS partition Dec 3 13:18:12 20microsoft: result: /dev/sda2:Windows Vista (loader):Windows1:chain And it also finds one of the recovery partitions as a windows partition: Dec 3 13:18:12 20microsoft: debug: /dev/sda3 is a NTFS partition Dec 3 13:18:13 20microsoft: result: /dev/sda3:Windows Vista (loader):Windows2:chain So I cannot see from the syslog why the grub menu did not have these in it. os-prober was also installed in /target , perhaps that os-prober somehow failed to find OS's the d-i os-prober found? -- see shy jo signature.asc Description: Digital signature
Bug#650992: installation-reports: buffalo linkstation pro duo aka "LS-WTGL/R1 (3)" or lsproduo needs custom kernel
Package: installation-reports
Severity: normal
hi,
Regular install went almost fine, but target cant be reachable once rebooted
so i had to install a custom kernel before rebooting...
More details on process at :
http://rzr.online.fr/q/armv5
Boot method: tftp
Image version:
http://d-i.debian.org/daily-images/armel/daily/orion5x/network-console/buffalo/lspro/#20111204
Date: 20111204
Machine: buffalo linkstation pro duo v2 aka "LS-WTGL/R1 (3)"
Partitions:
root@debian:/# parted /dev/sdb -s unit b print
Model: ATA SAMSUNG HD103UJ (scsi)
Disk /dev/sdb: 1000204886016B
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system
Flags
1 1048576B 1999634431B 1998585856Bprimary ext3
2 1999634432B65999470591B63999836160B primary ext4
3 66000518144B 965999591423B 89073280B extended
5 66000519168B 565999304703B 48785536B logical ext4
raid
6 566000353280B 965999591423B 39238144B logical ext4
raid
4 999204847616B 1000204140543B 999292928B primary linux-swap(v1)
(same for sdb)
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: [ ]
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:[ ]
Overall install:[ ]
Comments/Problems:
“Configure MD devices” seems to be stuck on :
12680 root 1724 Sudpkg --configure --force-configure mdcfg
12681 root 1936 R{mdcfg.postinst} /bin/sh
/var/lib/dpkg/info/mdcfg.postinst configure
kill -s INT ...
Also I noticed that previously :
Nov 26 20:29:40 finish-install: info: Running
/usr/lib/finish-install.d/21micro-evtd
Nov 26 20:29:40 finish-install: /usr/sbin/micro-evtd.command:
Nov 26 20:29:40 finish-install: line 10:
Nov 26 20:29:40 finish-install: syntax error: bad function name
Nov 26 20:29:40 finish-install:
Nov 26 20:29:40 finish-install: info: Running
/usr/lib/finish-install.d/21qcontrol
Before "Finishing the installation" I had to open a shell and install a
prebuild kernel as
shared at : http:/rzr.online.fr/q/armv5
I'll attach a patch for lsproduo support and will try to push it upstream too
(linux)
Note, I did not touch the bootloader,
I did before to change netconsole but it should be safe to keep it unmodified
--
Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.
Once you have filled out this report, mail it to sub...@bugs.debian.org.
==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7.0 (wheezy) - installer build 20111204-06:28"
X_INSTALLATION_MEDIUM=network-console
==
Installer hardware-summary:
==
uname -a: Linux debian 3.1.0-1-orion5x #1 Wed Nov 30 19:48:25 UTC 2011 armv5tel
GNU/Linux
usb-list:
usb-list: Bus 01 Device 01: Marvell Orion EHCI [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 3.1.0-1-orion5x ehci_hcd
usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub
usb-list:
usb-list: Bus 02 Device 01: Marvell Orion EHCI [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 3.1.0-1-orion5x ehci_hcd
usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub
lsmod: Module Size Used by
lsmod: nfsd 240976 13
lsmod: nfs 333498 0
lsmod: lockd 65485 2 nfsd,nfs
lsmod: fscache33171 1 nfs
lsmod: auth_rpcgss32713 2 nfsd,nfs
lsmod: nfs_acl 2189 2 nfsd,nfs
lsmod: sunrpc175795 15 nfsd,nfs,lockd,auth_rpcgss,nfs_acl
lsmod: dm_mod 59729 0
lsmod: raid1 23334 1
lsmod: raid0 7248 1
lsmod: md_mod 93152 2 raid1,raid0
lsmod: jfs 148806 0
lsmod: ext4 322727 1
lsmod: jbd2 56341 1 ext4
lsmod: crc16 1097 1 ext4
lsmod: ext3 161276 0
lsmod: jbd48601 1 ext3
lsmod: btrfs 606088 0
lsmod: zlib_deflate 19413 1 btrfs
lsmod: lzo_compress1696 1 b
Bug#650819: grub-installer: The contents of grub.cfg depend on the kernel installed
On Sun 04 Dec 2011 at 16:24:35 +, Brian Potkin wrote: > reassign 650819 os-prober 1.49 > thanks >From the changelog in the 1.49 package: * Attempt to load the fuse module, to improve the chances of grub-mount working. This line is in syslog-486 only: Dec 3 12:20:43 kernel: [ 967.581149] fuse init (API version 7.17) Another install was done with a 686-pae image. 'lsmod | grep fuse' was checked at frequent intervals while os-prober was in operation. It's output was empty. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111204234000.GN3655@desktop
nic-modules vs nic-extra-modules
The 'nic-modules' packages are described as containing 'Common NIC drivers'. However, I would estimate only two of those drivers are commonly used (tg3 and xen-netfront). The current module selection might make sense if the real purpose of the split is to support old systems that are short of memory. If that's the intent I would just like to change the description. Otherwise, I would guess that the real commonly-used modules (other than wireless) are: Atheros: atl1c, atl1e, atl2 [1] Broadcom: bnx2, tg3, broadcom[2] Intel:e1000, e1000e, igb Nvidia: forcedeth Realtek: r8169 paravirt: virtio_net[3], vmxnet3, xen-netfront library: dca, libphy, mii [1] I'm not sure about which of these are most common [2] PHY driver required by tg3 to support some boards [3] This is included for completeness but is currently in the 'virtio-modules' package which seems reasonable to me Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
