Bug#697265: Corresponding Xorg.0.log
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 see attachment -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlDlOMsACgkQ5+rBHyUt5wv8TwCgodwrSt4Q2vdvJmLBhpcClI5w qQQAoIknLqiRpfkOI56iYDdicKHqH5Jg =65CO -END PGP SIGNATURE- Xorg.0.log.gz Description: GNU Zip compressed data
Bug#697264: cdebconf-entropy: Missing build dependency on autoconf?
On second thought, I believe it is better to get rid of all the redundant stuff from the rules file, and just use dh-autoreconf. This patch is tested and found to be working. With this patch the autogen.sh file can be removed too. -- Happy hacking Petter Reinholdtsen diff --git a/debian/control b/debian/control index 4d7fe8b..e8a52f1 100644 --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Priority: extra Section: debian-installer Maintainer: Debian Install System Team Uploaders: Max Vozeler , Jérémy Bobbio , Christian Perrier , Colin Watson -Build-Depends: debhelper (>= 7.0.50~), po-debconf (>= 0.5.0), libdebian-installer4-dev, libnewt-dev, libtextwrap-dev, libdebconfclient0-dev (>= 0.130), libgtk2.0-dev (>= 2.18.7-2), autotools-dev +Build-Depends: debhelper (>= 7.0.50~), po-debconf (>= 0.5.0), dh-autoreconf, libdebian-installer4-dev, libnewt-dev, libtextwrap-dev, libdebconfclient0-dev (>= 0.130), libgtk2.0-dev (>= 2.18.7-2), autotools-dev Vcs-Browser: http://git.debian.org/?p=d-i/cdebconf-entropy.git Vcs-Git: git://git.debian.org/d-i/cdebconf-entropy.git diff --git a/debian/rules b/debian/rules index 03ef31a..593976c 100755 --- a/debian/rules +++ b/debian/rules @@ -1,24 +1,3 @@ #! /usr/bin/make -f %: - dh $@ - -CFLAGS = -Wall -g - -ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) - CFLAGS += -O0 -else - CFLAGS += -O2 -endif - -override_dh_auto_configure: - CFLAGS="$(CFLAGS)" dh_auto_configure - -override_dh_auto_clean: - [ -e configure ] || ./autogen.sh - dh_auto_clean -ifneq "$(wildcard /usr/share/misc/config.sub)" "" - cp -f /usr/share/misc/config.sub config.sub -endif -ifneq "$(wildcard /usr/share/misc/config.guess)" "" - cp -f /usr/share/misc/config.guess config.guess -endif + dh $@ --with autoreconf
Bug#696521: dvorak
Hi, Well, dvorak US is in the debian-installer. Why not the french dvorak ? Regards, Étienne -- 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/1357208336.11541.0.camel@berule
Re: Switching to graphical installer by default?
Bob Proulx, le Wed 02 Jan 2013 22:51:56 -0700, a écrit : > Cyril Brulebois wrote: > > Also, is there anyone aware of any reasons against switching to > > graphical installer by default? > > Can I at least say that I don't like the mouse installer and much > prefer the standard keyboard one? ? I never use the mouse in the graphical installer, it can entirely be used with the keyboard. Samuel -- 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/20130103110928.gg8...@type.youpi.perso.aquilenet.fr
Bug#696521: dvorak
Étienne BERSAC, le Thu 03 Jan 2013 11:18:56 +0100, a écrit : > Well, dvorak US is in the debian-installer. Why not the french dvorak ? As I mention along the thread, the presence of dvorak itself is questionable. Samuel -- 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/20130103111008.gh8...@type.youpi.perso.aquilenet.fr
Bug#697264: marked as done (cdebconf-entropy: Missing build dependency on autoconf?)
Your message dated Thu, 3 Jan 2013 17:21:54 +0100 with message-id <20130103162154.gb13...@radis.cristau.org> and subject line Re: Bug#697264: cdebconf-entropy: Missing build dependency on autoconf? has caused the Debian Bug report #697264, regarding cdebconf-entropy: Missing build dependency on autoconf? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 697264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cdebconf-entropy Version: 0.24 Tags: patch http://jenkins.debian.net/job/d-i_build_cdebconf-entropy/ > report the following build error: dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean dh clean dh_testdir debian/rules override_dh_auto_clean make[1]: Entering directory `/var/lib/jenkins/jobs/d-i_build_cdebconf-entropy/workspace' [ -e configure ] || ./autogen.sh ./autogen.sh: 3: ./autogen.sh: autoreconf: not found rm: cannot remove 'autom4te.cache': No such file or directory make[1]: *** [override_dh_auto_clean] Error 1 make[1]: Leaving directory `/var/lib/jenkins/jobs/d-i_build_cdebconf-entropy/workspace' make: *** [clean] Error 2 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 Is the package missing a build dependency? I suspect it should build-depend on autoconf. Here is a patch: --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Priority: extra Section: debian-installer Maintainer: Debian Install System Team Uploaders: Max Vozeler , Jérémy Bobbio , Christian Perr -Build-Depends: debhelper (>= 7.0.50~), po-debconf (>= 0.5.0), libdebian-installer4-dev, l +Build-Depends: debhelper (>= 7.0.50~), po-debconf (>= 0.5.0), autoconf, libdebian-install Vcs-Browser: http://git.debian.org/?p=d-i/cdebconf-entropy.git Vcs-Git: git://git.debian.org/d-i/cdebconf-entropy.git -- Happy hacking Petter Reinholdtsen --- End Message --- --- Begin Message --- On Thu, Jan 3, 2013 at 08:11:47 +0100, Petter Reinholdtsen wrote: > > Package: cdebconf-entropy > Version: 0.24 > Tags: patch > > http://jenkins.debian.net/job/d-i_build_cdebconf-entropy/ > report > the following build error: > Closing as not a bug. The package builds fine. Cheers, Julien signature.asc Description: Digital signature --- End Message ---
Bug#697265: installation-report: Wheezy beta set up with GA-MA-78GM-S2H Mainboard
On Thu, Jan 3, 2013 at 08:23:21 +0100, Andreas Glaeser wrote: > This time I used the graphical installer and had the harddisk partitioned > automatically > with all files in one ext4-partition. It went fair enough, but then upon > reboot gnome3 > started in fallback mode. So obviously manual configuration of Xorg is > necessary. I do I assume that's just missing firmware (the firmware-linux-nonfree package). > not want to do that now, because downloading the proprietary graphics-driver > directly > from AMD and using that is recommended. It integrates perfectly into the > system and is Recommended by whom? > rebuilt automatically via dkms when new kernel-versions are installed. > Xorg.0.log.gz is > included for further analysis. Gnome-Shell works when started manually, but > swrast is > used for 3d. glxgears runs at about 400 fps. > Cheers, Julien signature.asc Description: Digital signature
Bug#697309: installation-reports: Wheezy installation with D-I 7.0 Beta4
Package: installation-reports Severity: normal Dear Maintainers, I wanted to do a Debian Wheezy desktop (LXDE) installation, dit it, and it worked very well. I faced only one little problem, please see comments below. -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta4/i386/iso-cd/debian-wheezy-DI-b4-i386-netinst.iso Official Snapshot i386 NETINST Binary-1 20121118-12:43 (from README.txt in image) Date: 20130102 Machine: White box with Abit NF7 motherboard Partitions: df -Tl output: FilesystemType 1K-blocks Used Available Use% Mounted on rootfsrootfs 2882592 198544 2537616 8% / udev devtmpfs 102400 10240 0% /dev tmpfs tmpfs 207456 608206848 1% /run /dev/mapper/main-root ext4 2882592 198544 2537616 8% / tmpfs tmpfs 51200 5120 0% /run/lock tmpfs tmpfs 4149000414900 0% /run/shm /dev/sda1 ext447444027436422507 7% /boot /dev/mapper/main-home ext3 275882224 12295448 249572724 5% /home /dev/mapper/main-tmp ext4 4805760 140696 4420944 4% /tmp /dev/mapper/main-usr ext4 9611492 2149096 6974156 24% /usr /dev/mapper/main-var ext4 2882592 267044 2469116 10% /var 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: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: I started the installation from the netinst CD by choosing: Advanced options > Alternative desktop environment > LXDE > Install. Everything else went fine, but one error occured during package manager configuration, when selecting a Debian archive mirror. I wanted to use the nearest mirror to me, so I tried to choose ftp.jyu.fi (Finland). Then I got an error saying "Bad mirror archive". >From virtual console 4, I saw the error message: choose-mirror[6748]: WARNING **: mirror does not support the speficied release (wheezy). Well, I just chose another mirror (ftp.funet.fi) as the installer suggested, and continued the installation. The rest went just fine. Thanks for the great work! Regards, Christoph Joohs -- 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 20121114" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux koltiainen 3.2.0-4-486 #1 Debian 3.2.32-1 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: NVIDIA Corporation nForce2 IGP2 [10de:01e0] (rev c1) lspci -knn: Subsystem: ABIT Computer Corp. Device [147b:1c02] lspci -knn: Kernel driver in use: agpgart-nvidia lspci -knn: 00:00.1 RAM memory [0500]: NVIDIA Corporation nForce2 Memory Controller 1 [10de:01eb] (rev c1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:0c17] lspci -knn: 00:00.2 RAM memory [0500]: NVIDIA Corporation nForce2 Memory Controller 4 [10de:01ee] (rev c1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:0c17] lspci -knn: 00:00.3 RAM memory [0500]: NVIDIA Corporation nForce2 Memory Controller 3 [10de:01ed] (rev c1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:0c17] lspci -knn: 00:00.4 RAM memory [0500]: NVIDIA Corporation nForce2 Memory Controller 2 [10de:01ec] (rev c1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:0c17] lspci -knn: 00:00.5 RAM memory [0500]: NVIDIA Corporation nForce2 Memory Controller 5 [10de:01ef] (rev c1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:0c17] lspci -knn: 00:01.0 ISA bridge [0601]: NVIDIA Corporation nForce2 ISA Bridge [10de:0060] (rev a4) lspci -knn: Subsystem: ABIT Computer Corp. Device [147b:1c02] lspci -knn: 00:01.1 SMBus [0c05]: NVIDIA Corporation nForce2 SMBus (MCP) [10de:0064] (rev a2) lspci -knn: Subsystem: ABIT Computer Corp. Device [147b:1c02] lspci -knn: 00:02.0 USB controller [0c03]: NVIDIA Corporation nForce2 USB Controller [10de:0067] (rev a4) lspci -knn: Subsystem: ABIT Computer Corp. Device [147b:1c02] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:02.1
Re: Switching to graphical installer by default?
Em 03-01-2013 01:27, Steve McIntyre escreveu: [...] None here, we could/should have done it a while back IMO. +1 -- Melhores cumprimentos/Best regards, Miguel Figueiredo -- 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/50e5f240.5090...@debianpt.org
Bug#433568: add vlan support
On Sat, Dec 29, 2012 at 4:37 AM, Philipp Kern wrote: > On Sat, Dec 29, 2012 at 03:41:33AM +0800, Aron Xu wrote: >> The Linux kernel's vlan udeb is added in linux/3.2.35-1, so there is >> no outside thing to block us from adding vlan support to netcfg, can >> anyone review the patch? > > It needs a rewrite, IMHO. I started reviewing / rewriting it, but I'm not > stopping others to work on it. (More debugging output, more sane memory > handling, coding style adjustments.) > > I'm not sure I get to it before the next rc, though. At least, if it > works, it could probably also be backported to wheezy's d-i if it's too > late. It's pretty self-contained. > Thank you for working on this, and sorry for my not able to provide more help. I don't expect it to be included to Wheezy in current stage of freeze, and a backport will work. I work part-time in an IDC and the needs of some not-so-common usages (like vlan support in d-i) are obvious to me. Replacing some of RHEL/CentOS installations with Debian helps quite a log in daily operation, but this gives me some chances to find problems and help on improving Debian in such environments. It would be handy if the option is shown if vlan udeb is selected when choosing additional functions during installation, but I doubt whether this can apply for kBSD as they seem to have vlan support built-in to the kernel. Also hurd does not support 8021q vlan yet, showing the option does not make sense for it. -- Regards, Aron Xu -- 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/CAMr=8w4wghes4lsvyu2u1_yxgkhsw+ljvj6bht8kejagbjb...@mail.gmail.com
Bug#697327: installation-reports: Can not write on usb flash memory
Package: installation-reports Severity: normal Tags: d-i Dear Maintainer, * What led up to the situation? I installed wheezy-xfce (testing - build cd binay-1 20121217-05:10) on a new partition. Can not write to USB flash memory (~ "operation not allowed"). * What exactly did you do (or not do) that was effective (or ineffective)? Commented out following lines in /etc/fstab : #/dev/sdb1 /media/usb0 autorw,user,noauto 0 0 #/dev/sdb2 /media/usb1 autorw,user,noauto 0 0 #/dev/sdb3 /media/usb2 autorw,user,noauto 0 0 NB : I may have left some USB devices while installing wheezy from CD. * What was the outcome of this action? Problem fixed. -- Package-specific info: Boot method: Image version: Date: Machine: Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: -- 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 20121217-00:04" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux pc4 3.2.0-4-amd64 #1 SMP Debian 3.2.35-1 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 05) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 [8086:1c1a] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation HM65 Express Chipset Family LPC Controller [8086:1c49] (rev 05) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 05) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 05) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: 02:00.0 Network controller [0280]: Ralink corp. R
Processing of console-setup_1.91_i386.changes
console-setup_1.91.dsc doesn't exist console-setup_1.91.tar.gz doesn't exist keyboard-configuration_1.91_all.deb doesn't exist console-setup-freebsd_1.91_all.deb doesn't exist console-setup-pc-ekmap_1.91_all.udeb doesn't exist console-setup-sun4-ekmap_1.91_all.udeb doesn't exist console-setup-sun5-ekmap_1.91_all.udeb doesn't exist console-setup-linux-fonts-udeb_1.91_all.udeb doesn't exist Due to the errors above, the .changes file couldn't be processed. Please fix the problems for the upload to happen. Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1tquwt-0005eq...@franck.debian.org
Bug#697331: installation-reports: Printer not working / recognised
Package: installation-reports Severity: normal Tags: d-i Dear Maintainer, * What led up to the situation? I installed wheezy-xfce amd64 build 20121217:0510 on a new partition. I have an Epson BX300F "all in one" printer/scan/fax. I can scan documents with xsane but can not print (tried from simple text file & libre office document) * What exactly did you do (or not do) that was effective (or ineffective)? check cups package is installed set xfce print parameters to use cups (from menu) added package system-config-printer-udev (auto detect printers) reboot * What was the outcome of this action? Problem remains. test: print text document from mousepad editor >>> ** (xfprint4:4267): WARNING **: Unable to load printing system module cups_plugin.so ** (xfprint4:4267): WARNING **: no printer in the list, may be the CUPS server isn't running or you haven't configured any printer ** (xfprint4:4267): WARNING **: no printer in the list, may be the CUPS server isn't running or you haven't configured any printer <<< check: root? ls -l /usr/lib/x86_64-linux-gnu/xfce4/xfprint-plugins/cups_plugin.so -rw-r--r-- 1 root root 22408 jan 23 2012 /usr/lib/x86_64-linux-gnu/xfce4 /xfprint-plugins/cups_plugin.so root? tried: root? xfprint4-manager >>> (xfprint4-manager:3862): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfprint4-manager:3862): WARNING **: xfprint: /printing-system is not set <<< and nothing in the popup ~"print manager" check: package dbus-x11 : installed -- Package-specific info: Boot method: Image version: Date: Machine: Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: -- 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 20121217-00:04" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux pc4 3.2.0-4-amd64 #1 SMP Debian 3.2.35-1 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 05) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 [8086:1c1a] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (
Re: d-i manual (Re: building and testing d-i with jenkins)
Hi Holger, On Samstag, 29. Dezember 2012, Holger Wansing wrote: > today I found the following on > http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_pt_pdf/lastBuild/c > onsole > > rmdir: failed to remove `pdf/pt.amd64': Directory not empty > rmdir: failed to remove `pdf/pt.armel': Directory not empty > rmdir: failed to remove `pdf/pt.armhf': Directory not empty > rmdir: failed to remove `pdf/pt.hppa': Directory not empty > rmdir: failed to remove `pdf/pt.hurd-i386': Directory not empty > rmdir: failed to remove `pdf/pt.i386': Directory not empty > rmdir: failed to remove `pdf/pt.ia64': Directory not empty > rmdir: failed to remove `pdf/pt.kfreebsd-amd64': Directory not empty > rmdir: failed to remove `pdf/pt.kfreebsd-i386': Directory not empty > rmdir: failed to remove `pdf/pt.mips': Directory not empty > rmdir: failed to remove `pdf/pt.mipsel': Directory not empty > rmdir: failed to remove `pdf/pt.powerpc': Directory not empty > rmdir: failed to remove `pdf/pt.s390': Directory not empty > rmdir: failed to remove `pdf/pt.s390x': Directory not empty > rmdir: failed to remove `pdf/pt.sparc': Directory not empty > > Just to let you know ... > > This is most probably not an issue, as long as the remaining directories > don't make problems at the next build ... thanks for letting me know, though this was indeed harmless, nevertheless I took it to improve the code, to not show these removal attempts here. These directories are forcefully removed at the beginning of the build, so not being able to remove them at the end is a feature. cheers, Holger -- 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/201301040222.43565.hol...@layer-acht.org
Re: building and testing d-i with jenkins
Hi Steven, thanks for your feedback! On Sonntag, 30. Dezember 2012, Steven Chamberlain wrote: > > http://jenkins.debian.net/view/cd-tests/job/cd-test_wheezy_lxde/ > > doing a g-i installation of lxde desktop and producing a nice video > This is great! But what happened to that link, it is a 404 already? yes, it's 404 because I renamed the jobs so the new URL is http://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_wheezy_lxde/ > I see that wheezy d-i is at least being tested regularly for the > purposes of Debian Edu so that's good. I noticed what looks like some > false positives though, e.g.: all the g-i* tests are not as stable yet as I want them to be. I just had all the Debian wheezy tests working when suddenly they stopped working: i dont get it, since 2 days the g-i-installation tests hang, that is, d-i is not getting a dhcp address... but this only happens for wheezy installs, squeeze still works nicely i've reviewed all 20 commits since then twice, and dont get it coincidently, 2 days ago i also updated that wheezy, which updated kernel+qemu, but... the changelogs doesnt say anything and also its strange that the squeeze tests still work no free leases? i rebooted two days ago too. and its the qemu internal dhcp server (The g-i*debian-edu* tests still have other problems, but the Debian installations worked nicely: full desktop install, log in, open www.debian.org in iceweasel, start a shell, apt-get moo, su, poweroff. And a video of this as result.) > The install was thought to 'hang' and fail, because it rebooted into the > installed system within qemu. I think you are missing the qemu > '-no-reboot' flag here? No, I use "no-shutdown" and then issue a poweroff and then I wait for matching screenshots and then I gocr them and check that the last line there is "Power down." - that's better to check reliably, then a non-existing process, which could have died for a millions of reasons. :-) So summary: the g-i installation tests still need some work and this is mostly why I still havent announce jenkins.debian.net properly. cheers, Holger -- 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/201301040231.07809.hol...@layer-acht.org
Bug#697035: installer: kb and mouse don't work on a decTop (NSC geode processor)
Hello KiBi, > What keyboard and mouse are you using? > > Mraw, > KiBi. > Totally generic USB kb and USB mouse, i swap them around between various other machines, mostly running debian squeeze on generic amd64 hardware, and they work ok everywhere else. i've also used the same kb/mouse on the same decTop machine, up to and including debian lenny. the problems began when i tried to upgrade the os from lenny, first to squeeze, then to wheezy when that didn't work. some more info that might or might not be useful: 1. kb and mouse work fine with same hardware (decTop) with knoppix 6.7 2. they also work ok after booting debian live once X.org is running. 3. i tried the wheezy beta4 installer. in textmode neither the kb or mouse work. 4. in the wheezy b4 installer in graphical mode, the mouse worked but not the kb. 5. so just for fun, i tried doing the install in graphical mode using only the mouse, accepting the default text input for every question. when it wanted a username and passwd for the non-root user, i used the mouse to copy and paste text from the screen to make the installer happy. the installation succeeded, and i was able to boot into the textmode-only system and the kb worked ok in the installed system. 6. unfortunately, i also need encrypted partitions, so i had to redo the installation. since the kb and mouse both work in X.org on the live cd's, i figured i'd i try running the installer from X using the "testing" debian-live cd. alas, it froze (memory leak?), while creating a large ext4 filesystem on the target. 7. next, i tried the "stable" debian-live cd, again running the installer from X. so as to be able to use the kb and mouse. the installation completed, encrypted filesystems and all, but alas the installed system wouldn't boot, since the necessary infrastructure wasn't in place to get the kb working early in the boot process for cryptsetup. it seems like some fairly simple config problem, since the kb and mouse work ok in X, and also usually work in textmode on a fully-booted system. i hope you can get it working, at this point i've pretty much run out of options with linux for these machines and am about to try kfreebsd. thanks, and good luck! let me know if i can help in any way. phil. btw, the DecTop doesn't have any ps/2 kb or mouse ports, just 4 USB 1.1 ports for everything: kb, mouse, ethernet and usb stick for booting the installer. --- On Wed, 1/2/13, Cyril Brulebois wrote: > From: Cyril Brulebois > Subject: Re: Bug#697035: installer: kb and mouse don't work on a decTop (NSC > geode processor) > To: "Phil McCracken" , 697...@bugs.debian.org > Date: Wednesday, January 2, 2013, 5:19 PM > Hi Phil, > > Phil McCracken > (30/12/2012): > > 00:0f.4 USB Controller [0c03]: National Semiconductor > Corporation CS5535 USB [100b:002f] (rev 06) > > Subsystem: National Semiconductor > Corporation CS5535 USB [100b:002f] > > Kernel driver in use: ohci_hcd > > 00:0f.5 USB Controller [0c03]: National Semiconductor > Corporation CS5535 USB [100b:002f] (rev 06) > > Subsystem: National Semiconductor > Corporation CS5535 USB [100b:002f] > > Kernel driver in use: ohci_hcd > > (fwiw ohci_hcd is included in the usb-modules udebs.) > > > booting the > > kernel. but the moment it tried to use the installer > kernel, the kb and > > mouse stopped working with the ncurses installer. using > the gtk installer, > > the mouse worked, but the kb never did. how sad. btw i > successfully (that > > is, the kb and mouse worked) booted the machine from a > USB stick with > > knoppix 6.7 in order to get the lspci -knn listing > above.> > > What keyboard and mouse are you using? > > Mraw, > KiBi. > -- 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/1357193166.88962.yahoomailclas...@web162902.mail.bf1.yahoo.com
Bug#697035: installer: kb and mouse don't work on a decTop (NSC geode processor)
Hi, On 03/01/13 06:06, Phil McCracken wrote: > Totally generic USB kb and USB mouse [...] I have some AMD Geode NX / CS5535-based devices (Wyse Sx0) which only allow me to enter the BIOS menu with a *specific* USB keyboard out of about 3 or 4 that I tried. (A cheap and uninteresting one branded "SWEEX" works; a more expensive Cherry and some others didn't). It would be interesting to see your output of `lsusb -v` when the keyboard is working. I think at GRUB/syslinux prompts, these devices had the same problem so I ended up setting up a serial console to work on them. I guess they don't initialise keyboard input (similar to a PS/2 keyboard not plugged in at boot time), unless it detects some particular USB vendor/model/chipset or something. After booting a 'full' system such as Debian Live, something triggers the keyboard/mouse to start working. I'm surprised graphical-mode d-i doesn't do this though. > [...] pretty much run out of options with linux for these machines and > am about to try kfreebsd. If you do actually try that, please let me know how it goes! 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: http://lists.debian.org/50e65530.9060...@pyro.eu.org
Bug#697035: installer: kb and mouse don't work on a decTop (NSC geode processor)
On Fri, 2013-01-04 at 04:06 +, Steven Chamberlain wrote: > Hi, > > On 03/01/13 06:06, Phil McCracken wrote: > > Totally generic USB kb and USB mouse [...] > > I have some AMD Geode NX / CS5535-based devices (Wyse Sx0) which only > allow me to enter the BIOS menu with a *specific* USB keyboard out of > about 3 or 4 that I tried. (A cheap and uninteresting one branded > "SWEEX" works; a more expensive Cherry and some others didn't). > > It would be interesting to see your output of `lsusb -v` when the > keyboard is working. > > > I think at GRUB/syslinux prompts, these devices had the same problem so > I ended up setting up a serial console to work on them. > > I guess they don't initialise keyboard input (similar to a PS/2 keyboard > not plugged in at boot time), unless it detects some particular USB > vendor/model/chipset or something. Most likely it is a poor USB implementation in the BIOS and/or the keyboard. For example, the keyboard may be slow to initialise and the BIOS may not wait very long for USB devices to appear. BIOSes also normally communicate with USB keyboards using the simple 'boot protocol' and not the full HID protocol. > After booting a 'full' system such as Debian Live, something triggers > the keyboard/mouse to start working. I'm surprised graphical-mode d-i > doesn't do this though. So far as USB and HID drivers go, there shouldn't be any difference in capabilities between a text-mode installer, graphical installer, or the 'full' system. For a Geode NX we'll even install the same kernel flavour (486) as is used in the installer itself. Although it's always possible we're failing to include a specialised HID driver that we really need... What are the USB vendor and device IDs for the devices that don't work in the installer? Ben. > > [...] pretty much run out of options with linux for these machines and > > am about to try kfreebsd. > > If you do actually try that, please let me know how it goes! -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way. signature.asc Description: This is a digitally signed message part
Bug#696521: dvorak
Quoting Samuel Thibault (sthiba...@debian.org): > Étienne BERSAC, le Thu 03 Jan 2013 11:18:56 +0100, a écrit : > > Well, dvorak US is in the debian-installer. Why not the french dvorak ? > > As I mention along the thread, the presence of dvorak itself is > questionable. Historical reasons, only. It has been there since I know the installer, IIRC, so around 2003-2004. Not removing it is only because we want to avoid regressions more than we want to be consistent in the stance we have wrt exotic keymaps. signature.asc Description: Digital signature
Bug#697327: installation-reports: Can not write on usb flash memory
Quoting d28jm (jswmb...@mobistarmail.be): > Package: installation-reports > Severity: normal > Tags: d-i > > Dear Maintainer, > >* What led up to the situation? > I installed wheezy-xfce (testing - build cd binay-1 20121217-05:10) on a new > partition. > Can not write to USB flash memory (~ "operation not allowed"). > > >* What exactly did you do (or not do) that was effective (or > ineffective)? > Commented out following lines in /etc/fstab : > #/dev/sdb1 /media/usb0 autorw,user,noauto 0 0 > #/dev/sdb2 /media/usb1 autorw,user,noauto 0 0 > #/dev/sdb3 /media/usb2 autorw,user,noauto 0 0 > > NB : I may have left some USB devices while installing wheezy from CD. > >* What was the outcome of this action? > Problem fixed. It's unclear to me whether you experienced this problem after install or during the install. If that's after the install, then the problem probably doesn't belong to the installe ritself. signature.asc Description: Digital signature
Bug#697309: marked as done (installation-reports: Wheezy installation with D-I 7.0 Beta4)
Your message dated Fri, 4 Jan 2013 07:08:16 +0100 with message-id <20130104060816.gi5...@mykerinos.kheops.frmug.org> and subject line Re: Bug#697309: installation-reports: Wheezy installation with D-I 7.0 Beta4 has caused the Debian Bug report #697309, regarding installation-reports: Wheezy installation with D-I 7.0 Beta4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 697309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Dear Maintainers, I wanted to do a Debian Wheezy desktop (LXDE) installation, dit it, and it worked very well. I faced only one little problem, please see comments below. -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta4/i386/iso-cd/debian-wheezy-DI-b4-i386-netinst.iso Official Snapshot i386 NETINST Binary-1 20121118-12:43 (from README.txt in image) Date: 20130102 Machine: White box with Abit NF7 motherboard Partitions: df -Tl output: FilesystemType 1K-blocks Used Available Use% Mounted on rootfsrootfs 2882592 198544 2537616 8% / udev devtmpfs 102400 10240 0% /dev tmpfs tmpfs 207456 608206848 1% /run /dev/mapper/main-root ext4 2882592 198544 2537616 8% / tmpfs tmpfs 51200 5120 0% /run/lock tmpfs tmpfs 4149000414900 0% /run/shm /dev/sda1 ext447444027436422507 7% /boot /dev/mapper/main-home ext3 275882224 12295448 249572724 5% /home /dev/mapper/main-tmp ext4 4805760 140696 4420944 4% /tmp /dev/mapper/main-usr ext4 9611492 2149096 6974156 24% /usr /dev/mapper/main-var ext4 2882592 267044 2469116 10% /var 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: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: I started the installation from the netinst CD by choosing: Advanced options > Alternative desktop environment > LXDE > Install. Everything else went fine, but one error occured during package manager configuration, when selecting a Debian archive mirror. I wanted to use the nearest mirror to me, so I tried to choose ftp.jyu.fi (Finland). Then I got an error saying "Bad mirror archive". >From virtual console 4, I saw the error message: choose-mirror[6748]: WARNING **: mirror does not support the speficied release (wheezy). Well, I just chose another mirror (ftp.funet.fi) as the installer suggested, and continued the installation. The rest went just fine. Thanks for the great work! Regards, Christoph Joohs -- 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 20121114" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux koltiainen 3.2.0-4-486 #1 Debian 3.2.32-1 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: NVIDIA Corporation nForce2 IGP2 [10de:01e0] (rev c1) lspci -knn: Subsystem: ABIT Computer Corp. Device [147b:1c02] lspci -knn: Kernel driver in use: agpgart-nvidia lspci -knn: 00:00.1 RAM memory [0500]: NVIDIA Corporation nForce2 Memory Controller 1 [10de:01eb] (rev c1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:0c17] lspci -knn: 00:00.2 RAM memory [0500]: NVIDIA Corporation nForce2 Memory Controller 4 [10de:01ee] (rev c1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:0c17] lspci -knn: 00:00.3 RAM memory [0500]: NVIDIA Corporation nForce2 Memory Controller 3 [10de:01ed] (rev c1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:0c17
