Bug#764277: Graphical DE task don't install any DE
Hi Steven, Le 07/10/2014 01:44, Steven Chamberlain a écrit : There should have been several DEs listed in that menu to choose from; seems okay to me, or is that choice only shown for Expert-mode installs? The tasksel screen look like this (from memory) : [*]Graphical Desktop Environment [ ]...GNOME [ ]...Xfce [ ]...KDE [ ]...Cinnamon [ ]...MATE [ ]...LXDE [ ]SSH server [ ]and so on... I only choose the task « Graphical DE » without explicitly ask for a particular DE, in order to test the default behaviour. What I expected is : a) Only GDE is selected by default and it install the default DE choosen or b) GDE task don't install any DE, but one of the 5 is pre-selected. Baptiste -- 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/d404d7f50819f1b797fe145581fe9...@mailoo.org
Bug#764320: rsync in rescue mode
Package: debian-installer Severity: wishlist Control: submitter -1 r...@atlas.cz X-Debbugs-Cc: debian-test...@lists.debian.org - Forwarded message from r...@atlas.cz - From: r...@atlas.cz Date: Sun, 05 Oct 2014 11:36:51 +0200 To: debian-test...@lists.debian.org Subject: Ask for rsync Message-Id: <20141005113651.a111e...@atlas.cz> Dear Debian developers, I kindly ask you for help. I am using instalation CD in rescue mode and I need to rescue my data. In rescue environment there is no rsync command, which would resolve my task. I kindly ask you, please add rsync command to standalone rescue environment. Thank you for help, R. - End forwarded message - signature.asc Description: Digital signature
Processed: rsync in rescue mode
Processing control commands: > submitter -1 r...@atlas.cz Bug #764320 [debian-installer] rsync in rescue mode Changed Bug submitter to 'r...@atlas.cz' from 'Julien Cristau ' -- 764320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b.141267071523378.transcr...@bugs.debian.org
Bug#764320: rsync in rescue mode
Control: reassign -1 rsync Control: forcemerge 729069 764320 Note that https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729069 includes a link to http://lackof.org/taggart/hacking/d-i-tricks/ which may be helpful (but hacky!) to the original submitter (I've not tried the approach there myself). Another approach for now would be a live cd rather than the Debian installer CD in rescue mode. Cheers, Ian. On Tue, 2014-10-07 at 10:31 +0200, Julien Cristau wrote: > Package: debian-installer > Severity: wishlist > Control: submitter -1 r...@atlas.cz > X-Debbugs-Cc: debian-test...@lists.debian.org > > - Forwarded message from r...@atlas.cz - > > From: r...@atlas.cz > Date: Sun, 05 Oct 2014 11:36:51 +0200 > To: debian-test...@lists.debian.org > Subject: Ask for rsync > Message-Id: <20141005113651.a111e...@atlas.cz> > > > Dear Debian developers, > > I kindly ask you for help. I am using instalation CD > in rescue mode and I need to rescue my data. > In rescue environment there is no rsync command, > which would resolve my task. > > I kindly ask you, please add rsync command > to standalone rescue environment. > > Thank you for help, R. > > - End forwarded message - -- 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/1412675006.4972.20.ca...@hellion.org.uk
Processed: Re: Bug#764320: rsync in rescue mode
Processing control commands: > reassign -1 rsync Bug #764320 [debian-installer] rsync in rescue mode Bug reassigned from package 'debian-installer' to 'rsync'. Ignoring request to alter found versions of bug #764320 to the same values previously set Ignoring request to alter fixed versions of bug #764320 to the same values previously set > forcemerge 729069 764320 Bug #729069 [rsync] rsync: Please provide an rsync udeb Bug #764320 [rsync] rsync in rescue mode Marked as found in versions rsync/3.0.9-4. Merged 729069 764320 -- 729069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729069 764320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b764320.141267501124214.transcr...@bugs.debian.org
Processed: jessie
Processing commands for cont...@bugs.debian.org:
> tag 764287 + sid jessie
Bug #764287 [partman-zfs] GRUB before 2.02 doesn't support ZFS lz4 compression
Added tag(s) sid and jessie.
> tag 764310 + sid jessie
Bug #764310 [libcerf-doc,manpages-dev] manpages-dev and libcerf-doc: error when
trying to install together
Added tag(s) sid and jessie.
> tag 763476 + sid jessie
Bug #763476 [src:jpegjudge] jpegjudge: Please change build dependency to
libjpeg-dev (libjpeg-turbo transition)
Added tag(s) sid and jessie.
> tag 764268 + sid jessie
Bug #764268 {Done: Ludovic Brenta } [src:libaws]
libaws: build-dependency not satisfiable in sid
Added tag(s) sid and jessie.
> tag 764327 + sid jessie
Bug #764327 [thinkfan] thinfan: Startup Fails On PostInstall
Added tag(s) sid and jessie.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
763476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763476
764268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764268
764287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764287
764310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764310
764327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/handler.s.c.141267740310226.transcr...@bugs.debian.org
Re: Bug#725714: Partial fix using hw-setup for the missing firmware problem in d-i?
Here is another draft patch for hw-detect. This one is tested, and
find the missing firmware on my X200 test laptop.
This approach keep the non-functioning code and add two new
approaches, one looking at the meta information for loadmed modules,
and one parsing the dmesg output. The union from all three methods
are then presented as the list of wanted firmware.
diff --git a/check-missing-firmware.sh b/check-missing-firmware.sh
index 60c6ff4..74db55b 100755
--- a/check-missing-firmware.sh
+++ b/check-missing-firmware.sh
@@ -61,6 +61,18 @@ nic_is_configured() {
return 1
}
+add_if_fw_missing() {
+fwfile="$1"
+if [ ! -e /lib/firmware/$fwfile ] ; then
+if grep -q "^$fwfile$" $DENIED 2>/dev/null; then
+ log "listed in $DENIED"
+continue
+fi
+files="${files:+$files }$fwfile"
+modules="$module${modules:+ $modules}"
+fi
+}
+
check_missing () {
upnics
@@ -117,11 +129,30 @@ check_missing () {
done
done
+# Workaround for bug #725714, the kernel and udev no longer
+# let us know via /dev/.udev/firmware-missing and
+# /run/udev/firmware-missing which firmware files the kernel
+# drivers look for. This approach will only find firmware for
+# the loaded kernel modules. Modules refusing to
+# register/load when the firmware is missing will be missed.
+for module in $(cut -d" " -f1 /proc/modules); do
+for fwfile in $(modinfo $module | grep ^firmware: | cut -d: -f2);
do
+log "looking for firmware file $fwfile needed by $module"
+add_if_fw_missing "$fwfile"
+done
+done
+for fwfile in $(dmesg | grep 'firmware: failed' | sed 's/.*firmware:
failed to load //' | cut -d" " -f1); do
+# Dummy make sure '-n "$modules"' test below find something
+module=kernel
+log "looking for firmware file $fwfile requested by kernel"
+add_if_fw_missing "$fwfile"
+done
+
if [ -n "$modules" ]; then
log "missing firmware files ($files) for $modules"
return 0
else
- log "no missing firmware in $MISSING"
+ log "no missing firmware for any kernel module"
return 1
fi
}
--
Happy hacking
Petter Reinholdtsen
--
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/20141007135247.gp10...@ulrik.uio.no
Re: Bug#725714: Partial fix using hw-setup for the missing firmware problem in d-i?
On Tue, 2014-10-07 at 15:52 +0200, Petter Reinholdtsen wrote:
> Here is another draft patch for hw-detect. This one is tested, and
> find the missing firmware on my X200 test laptop.
>
> This approach keep the non-functioning code
The firmware agent is never coming back, so please do remove the related
code.
> and add two new
> approaches, one looking at the meta information for loadmed modules,
> and one parsing the dmesg output. The union from all three methods
> are then presented as the list of wanted firmware.
>
> diff --git a/check-missing-firmware.sh b/check-missing-firmware.sh
> index 60c6ff4..74db55b 100755
> --- a/check-missing-firmware.sh
> +++ b/check-missing-firmware.sh
[...]
> @@ -117,11 +129,30 @@ check_missing () {
> done
> done
>
> +# Workaround for bug #725714, the kernel and udev no longer
> +# let us know via /dev/.udev/firmware-missing and
> +# /run/udev/firmware-missing which firmware files the kernel
> +# drivers look for.
This belongs in the changelog not the code.
> This approach will only find firmware for
> +# the loaded kernel modules. Modules refusing to
> +# register/load when the firmware is missing will be missed.
> +for module in $(cut -d" " -f1 /proc/modules); do
> +for fwfile in $(modinfo $module | grep ^firmware: | cut -d:
> -f2); do
> +log "looking for firmware file $fwfile needed by $module"
> +add_if_fw_missing "$fwfile"
> +done
> +done
> +for fwfile in $(dmesg | grep 'firmware: failed' | sed 's/.*firmware:
> failed to load //' | cut -d" " -f1); do
Redundant use of grep; sed can do that (sed -n 's/.../.../p').
> +# Dummy make sure '-n "$modules"' test below find something
> +module=kernel
The driver name should appear at the start of the log line (after the
timestamp). Use that instead of 'kernel'.
> +log "looking for firmware file $fwfile requested by kernel"
> +add_if_fw_missing "$fwfile"
> +done
> +
Indentation of the above is inconsistent with the surrounding code (4
spaces vs hard tab).
Ben.
> if [ -n "$modules" ]; then
> log "missing firmware files ($files) for $modules"
> return 0
> else
> - log "no missing firmware in $MISSING"
> + log "no missing firmware for any kernel module"
> return 1
> fi
> }
>
> --
> Happy hacking
> Petter Reinholdtsen
>
>
--
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky
signature.asc
Description: This is a digitally signed message part
Bug#764361: installation-report: XFS filesystem fails to upgrade from kernel 3.2 to 3.16
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.49 Severity: minor Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** - -- Package-specific info: Boot method: USB Image version: http://gensho.acc.umu.se/debian-cd/7.6.0/multi-arch/iso-cd/debian-7.6.0-amd64-i386-netinst.iso Date: 2014-10-03 Machine: FSC Futro s400 Partitions: DateisystemTyp 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf rootfs rootfs14327741 3310290 11017451 24% / udev devtmpfs 10240 0 102400% /dev tmpfs tmpfs 96680 776 959041% /run /dev/disk/by-uuid/c0ac460c-acf0-4574-b674-f93a942bf13a xfs 14327741 3310290 11017451 24% / tmpfs tmpfs 5120 0 51200% /run/lock tmpfs tmpfs 402640 04026400% /run/shm 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: [e] Install base system:[o] Install tasks: [o] Install boot loader:[o] Overall install:[o] Comments/Problems: I knew before from other installations, that XFS-filesystems made with 3.2-kernels fail to upgrade to newer kernel versions. The workaround for this was to make the partitions from another PC with running Jessie/testing with gparted and make the filesystem manually, then choose to keep existing data in the installer and not to re-format the fs-root-partition. This works perfectly, because forward-compatibility is there. Originally I wanted to include backports in my installation for the most important applications and for the kernel, then it turned out, there were more than 60 uninstalled backported packages left, so I decided to pin those to a priority of 500, so they are automatically installed. Finally unused space was zeroed with dd, package-cache cleared and existing data defragmented. For existing installations the workaround for this XFS-problem would be to make an exact copy of the system from a live-system on file-level using tar, to remake the partition from a new enough live-system, then restore all files from that tar-archive. - -- 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 (wheezy) - installer build 20130613+deb7u2+b1" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux instant 3.2.0-4-486 #1 Debian 3.2.57-3 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 741/741GX/M741 Host [1039:0741] (rev 03) lspci -knn: Subsystem: Silicon Integrated Systems [SiS] 741/741GX/M741 Host [1039:0741] lspci -knn: Kernel driver in use: agpgart-sis lspci -knn: 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge) [1039:0002] lspci -knn: 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] LPC Controller [1039:0963] (rev 25) lspci -knn: 00:02.1 SMBus [0c05]: Silicon Integrated Systems [SiS] SiS961/2/3 SMBus controller [1039:0016] lspci -knn: 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 IDE Controller [1039:5513] lspci -knn: Subsystem: Silicon Integrated Systems [SiS] 5513 IDE Controller [1039:5513] lspci -knn: Kernel driver in use: pata_sis lspci -knn: 00:02.7 Multimedia audio controller [0401]: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller [1039:7012] (rev a0) lspci -knn: Subsystem: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller [1039:7012] lspci -knn: 00:03.0 USB controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn:Subsystem: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] lspci -knn: Kernel driver in use: ohci_hc
Re: Bug#725714: Partial fix using hw-setup for the missing firmware problem in d-i?
Thank you for the code review. :) [Ben Hutchings] > The firmware agent is never coming back, so please do remove the related > code. I know and agree, but https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725714#163 > asked for the non-working code to be kept to work with older kernels. I do not have any strong feelings, so I left it as it was. > This belongs in the changelog not the code. Actually, as long as there are several blocks doing similar things, I believe an explanation should be close to the code to explain why. I will wonder when I return in a few years time. :) > The driver name should appear at the start of the log line (after > the timestamp). Use that instead of 'kernel'. Yeah, but did not find a simple way to do it, and it is not affecting the functionallity, only the user messages. Should probably be fixed in the final version. > Redundant use of grep; sed can do that (sed -n 's/.../.../p'). Yeah. > Indentation of the above is inconsistent with the surrounding code > (4 spaces vs hard tab). It will happen before any commit is done. -- Happy hacking Petter Reinholdtsen -- 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/20141007150911.gq10...@ulrik.uio.no
Re: Bug#725714: Partial fix using hw-setup for the missing firmware problem in d-i?
On Tue, 2014-10-07 at 17:09 +0200, Petter Reinholdtsen wrote: > Thank you for the code review. :) > > [Ben Hutchings] > > The firmware agent is never coming back, so please do remove the related > > code. > > I know and agree, but > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725714#163 > > asked for the non-working code to be kept to work with older kernels. Actually it is udev that removed this feature originally. Anyway, I shan't argue this with KiBi. > I do not have any strong feelings, so I left it as it was. > > > This belongs in the changelog not the code. > > Actually, as long as there are several blocks doing similar things, I > believe an explanation should be close to the code to explain why. I > will wonder when I return in a few years time. :) Perhaps this would be better placed above the old code, as that is what should be cleaned up at some later date. > > The driver name should appear at the start of the log line (after > > the timestamp). Use that instead of 'kernel'. > > Yeah, but did not find a simple way to do it, and it is not affecting > the functionallity, only the user messages. Should probably be fixed > in the final version. > > > Redundant use of grep; sed can do that (sed -n 's/.../.../p'). > > Yeah. > > > Indentation of the above is inconsistent with the surrounding code > > (4 spaces vs hard tab). > > It will happen before any commit is done. Thanks. Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky signature.asc Description: This is a digitally signed message part
Bug#762399: console-setup: WARNING: Unknown X keysym "permille"
On Mon, Sep 22, 2014 at 12:33:25AM +0300, Martin-Éric Racine wrote: > > Setting up console-setup (1.113) ... > WARNING: Unknown X keysym "permille" > WARNING: Unknown X keysym "permille" > WARNING: Unknown X keysym "permille" > WARNING: Unknown X keysym "permille" > WARNING: Unknown X keysym "ezh" > WARNING: Unknown X keysym "EZH" > WARNING: Unknown X keysym "ezh" > WARNING: Unknown X keysym "EZH" > WARNING: Unknown X keysym "ezh" > WARNING: Unknown X keysym "EZH" > WARNING: Unknown X keysym "ezh" > WARNING: Unknown X keysym "EZH" > Setting up libprotobuf9:i386 (2.6.0-3) ... > > Could this be caused by ckbcomp's built-in (X keysym -> kernel keysym) > table missing these? Yes. Anton Zinoviev -- 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/20141007155255.ga20...@logic.fmi.uni-sofia.bg
Bug#762767: installation-reports: [ASRock N68-VGS3 FX with onboard Gigabit LAN PHY RTL8211CL] Networking and ACPI conflicts
"PATCH forcedeth bug fix: realtek phy 8211c errata" http://lists.openwall.net/netdev/2008/07/25/127 http://lists.openwall.net/netdev/2008/07/29/91
Bug#709883: [keyboard-configuration] RE: keyboard-configuration: X keyboard configuration lost after upgrade
On Tue, Sep 30, 2014 at 04:35:55PM +0100, OmegaPhil wrote: > > I maintain a /etc/default/keyboard configuration where capslock is > purged system-wide - I add ',caps:none' at the end of 'XKBOPTIONS'. > > Whenever this package is upgraded/reinstalled, my configuration is > overwritten back to the default. From what I can tell, I am correct in > editing this file - so please can this file be left alone unless I > specifically allow it to be altered (e.g. if aptitude wants to change > it, the usual config text UI comes up showing before and after changes > to the file). This is not the expected behaviour. Please send the contents of your /etc/default/keyboard so I can test. Anton Zinoviev -- 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/20141007160941.ga20...@logic.fmi.uni-sofia.bg
Bug#709883: [keyboard-configuration] RE: keyboard-configuration: X keyboard configuration lost after upgrade
On 07/10/14 17:09, Anton Zinoviev wrote: > On Tue, Sep 30, 2014 at 04:35:55PM +0100, OmegaPhil wrote: >> >> I maintain a /etc/default/keyboard configuration where capslock is >> purged system-wide - I add ',caps:none' at the end of 'XKBOPTIONS'. >> >> Whenever this package is upgraded/reinstalled, my configuration is >> overwritten back to the default. From what I can tell, I am correct in >> editing this file - so please can this file be left alone unless I >> specifically allow it to be altered (e.g. if aptitude wants to change >> it, the usual config text UI comes up showing before and after changes >> to the file). > > This is not the expected behaviour. Please send the contents of your > /etc/default/keyboard so I can test. > > Anton Zinoviev Attached. -- Libre software on Github: https://github.com/OmegaPhil FSF member #9442 # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL="pc105" XKBLAYOUT="gb" XKBVARIANT="" XKBOPTIONS="lv3:ralt_switch,caps:none" # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz BACKSPACE="guess" signature.asc Description: OpenPGP digital signature
Bug#762399: console-setup: WARNING: Unknown X keysym "permille"
2014-10-07 18:52 GMT+03:00 Anton Zinoviev : > On Mon, Sep 22, 2014 at 12:33:25AM +0300, Martin-Éric Racine wrote: >> >> Setting up console-setup (1.113) ... >> WARNING: Unknown X keysym "permille" >> WARNING: Unknown X keysym "permille" >> WARNING: Unknown X keysym "permille" >> WARNING: Unknown X keysym "permille" >> WARNING: Unknown X keysym "ezh" >> WARNING: Unknown X keysym "EZH" >> WARNING: Unknown X keysym "ezh" >> WARNING: Unknown X keysym "EZH" >> WARNING: Unknown X keysym "ezh" >> WARNING: Unknown X keysym "EZH" >> WARNING: Unknown X keysym "ezh" >> WARNING: Unknown X keysym "EZH" >> Setting up libprotobuf9:i386 (2.6.0-3) ... >> >> Could this be caused by ckbcomp's built-in (X keysym -> kernel keysym) >> table missing these? > > Yes. Alright. Would it be possible to re-generate that symbol table and fix the issue? :) Martin-Éric -- 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/debian-boot
Bug#762767: installation-reports: [ASRock N68-VGS3 FX with onboard Gigabit LAN PHY RTL8211CL] Networking and ACPI conflicts
I have discovered that the problem appears when I try to obtain one automatic IP version 4 from one network card (Realtek onboard) or the other (Dlink offboard) or both. After a long time, the computer turns on, but no real network connection is possible even though one or two NICs have a corret IP number provided from the dhcp server: -- #vi /etc/network/interfaces --- # The primary network interface auto eth0 eth1 allow-hotplug eth0 eth1 iface eth0 inet dhcp # The secondary network interface iface eth1 inet dhcp --- -- When I use static IP numbers (version 4) on one network card (Realtek onboard) or the other (Dlink offboard) or both, the computer turns on fast and real network connection is created and I can use the Internet and connect to and from others computers on my local network via SSH and SAMBA 4.1. I cannot put gateway information on the Realtek card. When I do, both network connections stop working and my computer gets isolated from the rest of my local network. Although everything seems fine, the computer freezes when I try to reset it (#shutdown -r now) or turn it off (shutdown -h now): -- #vi /etc/network/interfaces --- # The primary network interface auto eth0 eth1 allow-hotplug eth0 eth1 iface eth0 inet static address 192.168.0.100 netmask 255.255.255.0 # gateway 192.168.0.1 # The secondary network interface iface eth1 inet static address 192.168.0.200 netmask 255.255.255.0 gateway 192.168.0.1 --- -- Extra information that maybe helpful: "The Realtek RTL8211E is a RGMII 10/100/1000 Ethernet PHY, which is gigabit capable. It is commonly paired with GMAC for gigabit speeds. Generic PHY support is enough to make it work." http://linux-sunxi.org/Ethernet http://ircbots.debian.net/factoids/factoid.php?key=rtl8211cl "PATCH forcedeth bug fix: realtek phy 8211c errata" http://lists.openwall.net/netdev/2008/07/25/127 http://lists.openwall.net/netdev/2008/07/29/91 http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/drivers/net/forcedeth.c http://plugable.com/2010/10/18/howto-asix-88178-usb-ethernet-adapter-on-ubuntu-10-10-linux https://packages.debian.org/search?searchon=contents&keywords=forcedeth.ko&mode=exactfilename&suite=stable&arch=any http://unix.stackexchange.com/questions/97974/how-do-i-remove-acpi-warning-on-boot "The forcedeth story" http://liquidat.wordpress.com/2007/03/04/the-forcedeth-story/
Bug#705878: Change default Debian web browser to Chromium
Package: task-desktop Version: 3.28 Followup-For: Bug #705878 Default browser is still Iceweasel. I'd like to have chromium as default, too. Iceweasel is also installed as default in chromium desktop. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages task-desktop depends on: ii desktop-base7.0.3 ii tasksel 3.28 ii xorg1:7.7+7 ii xserver-xorg-input-all 1:7.7+7 ii xserver-xorg-video-all 1:7.7+7 Versions of packages task-desktop recommends: ii alsa-base 1.0.27+1 ii alsa-utils 1.0.28-1 ii anacron2.3-22 ii avahi-daemon 0.6.31-4 ii eject 2.1.5+deb1+cvs20081104-13.1 ii iw 3.14-1 ii libgl1-mesa-dri10.2.6-1 ii libnss-mdns0.10-6 ii pm-utils 1.4.1-15 ii task-cinnamon-desktop 3.28 ii xdg-utils 1.1.0~rc1+git20111210-7.1 task-desktop suggests no packages. -- 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: https://lists.debian.org/20141007205923.3512.41295.reportbug@lars-notebook-jessie
Processed: affects 705878 + cinnamon-desktop-environment
Processing commands for cont...@bugs.debian.org: > affects 705878 + cinnamon-desktop-environment Bug #705878 [task-desktop] Change default Debian web browser to Chromium Added indication that 705878 affects cinnamon-desktop-environment > End of message, stopping processing here. Please contact me if you need assistance. -- 705878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.141271676215557.transcr...@bugs.debian.org
Bug#705878: (no subject)
Sorry, I meant "Iceweasel is also installed as default in cinnamon-desktop", NOT "chromium desktop" :-P -- 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/54345e6c.2020...@gmail.com
Re: Bug#762762: Updating isc-dhcp udeb to dynamically link bind (was: Bug#762762: nmu fixing bind issues)
On Mon, Oct 6, 2014 at 9:11 PM, Steven Chamberlain wrote: > On 00:52, Steven Chamberlain wrote: >> Michael Gilbert wrote: >> > Would it be ok to stage the changes in unstable to make it somewhat >> > easy for porters to test? >> >> I don't particularly need that as I can build the udebs and d-i image >> from them myself. But doing so would allow others to be testing it >> meanwhile, so I'm okay with it. > > Did you already make a new version of the isc-dhcp package based on > these new export udebs? If so, where can I find it? No, not yet. Will probably get to that tomorrow. Best wishes, Mike -- 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/CANTw=MNmqCSH4fnnXCE80=f1Z3B1A+Y2F=1idn-tzifb9+x...@mail.gmail.com
Bug#735169: os-prober cannot work with the latest upstream blkid (util-linux-2.24)
Hi,
This patch works good for me.
-kcao
On Sat, Jul 12, 2014 at 12:55:08AM +0200, Andreas Henriksson wrote:
> Control: tags -1 + patch
>
> Hello!
>
> I'm working on an updated util-linux package (v2.24.2) and was pointed
> to this os-prober bug report.
>
> In my limited testing I haven't been able to reproduce any problems
> here with os-prober and util-linux 2.24.2.
>
> I can confirm though that the behaviour of running blkid against
> an extended dos partition has changed. In the new version information
> is correctly reported for those instead of just erroring out.
>
> The old blkid version (2.20.1) returns error code 2 when running
> against an extended dos partition.
>
> $ sudo blkid -V
> blkid from util-linux 2.24.2 (libblkid 2.24.0, 24-Apr-2014)
>
> $ sudo blkid -o export /dev/sda2
> DEVNAME=/dev/sda2
> PTUUID=dd6e951b
> PTTYPE=dos
> PARTUUID=000ae69f-02
>
> $ sudo blkid /dev/sda2
> /dev/sda2: PTUUID="dd6e951b" PTTYPE="dos" PARTUUID="000ae69f-02"
>
>
> I'm attaching a patch that should hopefully help. It tries to make the
> executed codepath similar to what it was by adding an extra check on the
> case where value of TYPE is "" and then exits 0 if it looks like an
> extended dos partition.
>
> Any feedback would be greatly appreciated.
>
> Regards,
> Andreas Henriksson
> diff --git a/common.sh b/common.sh
> index 30e245e..8734b62 100644
> --- a/common.sh
> +++ b/common.sh
> @@ -116,6 +116,29 @@ fs_type () {
> fi
> }
>
> +is_dos_extended_partition() {
> + if type blkid >/dev/null 2>&1; then
> + local output
> +
> + output="$(blkid -o export $1)"
> +
> + # old blkid (util-linux << 2.24) errors out on extended p.
> + if [ "$?" = "2" ]; then
> + return 0
> + fi
> +
> + # dos partition type and no filesystem type?...
> + if echo $output | grep -q ' PTTYPE=dos ' &&
> + ! echo $output | grep -q ' TYPE='; then
> + return 0
> + else
> + return 1
> + fi
> + fi
> +
> + return 1
> +}
> +
> parse_proc_mounts () {
> while read -r line; do
> set -f
> diff --git a/linux-boot-probes/common/50mounted-tests
> b/linux-boot-probes/common/50mounted-tests
> index 41e26e6..91b6dd9 100755
> --- a/linux-boot-probes/common/50mounted-tests
> +++ b/linux-boot-probes/common/50mounted-tests
> @@ -20,6 +20,10 @@ elif [ "$types" = ntfs ]; then
> types='ntfs-3g ntfs'
> fi
> elif [ -z "$types" ]; then
> + if is_dos_extended_partition "$partition"; then
> + debug "$1 looks like an extended dos partition; skipping"
> + exit 0
> + fi
> if type cryptsetup >/dev/null 2>&1 && \
> cryptsetup luksDump "$partition" >/dev/null 2>&1; then
> debug "$1 is a LUKS partition; skipping"
--
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/20141008001247.GA923@hp-mt
Bug#764429: os-prober: doen't clean up correctly on purge
Package: os-prober Version: 1.64 Severity: normal Hi. On purge, the package doesn't clean up correctly: Removing os-prober (1.64) ... dpkg: warning: while removing os-prober, directory '/var/lib/os-prober' not empty so not removed $ ls -al /var/lib/os-prober/ total 13k drwxr-xr-x 2 root root 4,1k Oct 8 01:41 . drwxr-xr-x 89 root root 4,1k Oct 8 01:31 .. -rw-r--r-- 1 root root 10 Oct 8 01:41 labels Cheers, Chris. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DE.utf8, LC_CTYPE=en_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20141008011635.14198.89822.report...@heisenberg.scientia.net
Debian Jessie Beta 2 - USB thumb drive not recognized after installation
Hi, After writing debian-jessie-DI-b2-amd64-DVD-1.iso to a USB drive, I installed Debian Jessie with it. I followed the instructions on the monitor asking me to remove the USB stick upon a successful installation. I had opted for a base/net install. I rebooted my computer and was taken to a console. After I had input the login credentials, I issued the command sudo apt-get install xorg An error message appeared on the black screen telling me that I had to re-insert my USB drive. I did as instructed, re-typed the command sudo apt-get install xorg and the same error message appeared. I googled for answers and it appears that the above problem has existed since Debian Wheezy. Someone even feedback to the Debian team about the same problem regarding Debian Jessie a few months ago. Could the Debian Installer team provide a fix for the above issue? Thanks. Vince _ Washington DC's Largest FREE Email service. ---> http://www.DCemail.com ---> A Washington Online Community Member ---> http://www.DCpages.com -- 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/20141007184347.e7d26...@m0005296.ppops.net
Bug#764437: console-setup hangs during install in jessie/wheezy on eeepc 1005ha
Package: console-setup Version: 1.113 Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, Installing Debian Wheezy or Jessie with a net install iso on my EEEPC 1005HA just won't work. It will hang or reboot on the "installing base system" around 99% when console-setup runs. I have tried running the setup with boot params "acpi=off, nomodeset, blacklisting the i915 module, ..." nothing gets the job done. Only way i've found to get around it is to rename or delete /target/usr/bin/ckbcomp during the install (and you have to be quick to catch it). After doing so and booting the now successful install, renaming /usr/bin/ckbcomp back, the system will not boot any more. I've tried installing with different keymaps/locales nothing seems to help... -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages console-setup depends on: ii console-setup-linux 1.113 ii debconf 1.5.53 ii keyboard-configuration 1.113 ii xkb-data2.12-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales 2.19-11 ii lsb-base 4.1+Debian13 Versions of packages keyboard-configuration depends on: ii debconf 1.5.53 ii initscripts 2.88dsf-53.4 ii liblocale-gettext-perl 1.05-8+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-1 ii keyboard-configuration 1.113 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii kbd 1.15.5-1 -- debconf information: console-setup/fontsize-fb47: 8x16 keyboard-configuration/unsupported_layout: true * keyboard-configuration/modelcode: pc105 * keyboard-configuration/layout: * keyboard-configuration/layoutcode: us console-setup/framebuffer_only: * keyboard-configuration/other: debian-installer/console-setup-udeb/title: keyboard-configuration/unsupported_config_options: true * keyboard-configuration/altgr: The default for the keyboard layout keyboard-configuration/unsupported_config_layout: true console-setup/fontsize: 8x16 console-setup/charmap47: UTF-8 console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages keyboard-configuration/unsupported_options: true * keyboard-configuration/model: Generic 105-key (Intl) PC * keyboard-configuration/variantcode: * keyboard-configuration/toggle: No toggling console-setup/use_system_font: * keyboard-configuration/switch: No temporary switch console-setup/fontsize-text47: 8x16 console-setup/guess_font: console-setup/store_defaults_in_debconf_db: true * keyboard-configuration/variant: English (US) console-setup/codesetcode: Lat15 * keyboard-configuration/xkb-keymap: us * keyboard-configuration/store_defaults_in_debconf_db: true * keyboard-configuration/compose: No compose key keyboard-configuration/ctrl_alt_bksp: false * keyboard-configuration/optionscode: console-setup/fontface47: Fixed -- 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/20141008051316.1605.93153.report...@ecstasy.yourfreaking.net
