Bug#661910: debian-installer needs to be smarter when there is no floppy
Package: debian-installer Version: all versions Environment: - Dell Latitude 8100 - Dell Latitude C640 - Debian Wheezy (testing) / Debian Squeeze (stable) / Debian Lenny (oldstable) The Dell Latitude 8100 and C640 provide an optional floppy drive to be installed in the drive bay or connected to the parallel port. Nevertheless, if the floppy drive is not installed/connected, the debian-installer will hang forever at the network detection, despite the fact that the floppy drive is disabled in the BIOS. end_request: I/O error, dev fd0, sector 0 is reported in /var/log/syslog This behavior shows in all tested versions of debian-installer, regardless if the installation is started via the network or cd/dvd. This leaves the user unable to install Debian if now floppy drive is available! Rgds, Klaus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635278: rpcbind still utilizes tcp6/udp6 ports when IPv6 is disabled
Yupp, to comment out the appropriate entries in /etc/netconfig did the trick for rpcbind. Now I just have to convince nfs-common to not utilize udp6 and tcp6 ports. But this is going to be a different story (bug report). Thanks for the input. Rgds, Klaus PS.: I guess this report could be closed Am 23.10.2011 15:58, schrieb Jamie Heilman: I gather net.ipv6.conf.all.disable_ipv6 disables assignment of IPv6 addresses to your interfaces, but doesn't really disable IPv6 the protocol entirely. If you want to tell rpcbind to stop using IPv6, comment out the appropriate entries in /etc/netconfig, it should do what you want. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648635: rpc.nfsd still utilizes tcp6/udp6 ports when IPv6 is disabled
Package: nfs-kernel-server Version: 1.2.5-2 severity: minor Environment: - Dell Latitude 8100 - Debian Wheezy (testing) - Kernel 3.0.0-1-686-pae IPv6 is disabled by 'echo net.ipv6.conf.all.disable_ipv6=1 /etc/sysctl.d/disableipv6.conf'. Furthermore the tcp6 and udp6 entries in /etc/netconfig are commented out. Nevertheless 'netstat -lp', before and after starting the nfs-kernel-server, shows that rpc.nfsd still utilizes tcp6/udp6 ports. user@host:~# diff before after 3a4,8 tcp0 0 *:56535 *:* LISTEN - tcp0 0 *:38042 *:* LISTEN 1154/rpc.mountd tcp0 0 *:nfs *:* LISTEN - tcp0 0 *:48747 *:* LISTEN 1154/rpc.mountd tcp0 0 *:34316 *:* LISTEN 1154/rpc.mountd 4a10,11 tcp6 0 0 [::]:52795 [::]:* LISTEN - udp0 0 *:42604 *:* 1154/rpc.mountd 6a14,18 udp0 0 *:nfs *:* - udp0 0 *:49677 *:* - udp0 0 *:59174 *:* 1154/rpc.mountd udp0 0 *:60462 *:* 1154/rpc.mountd udp6 0 0 [::]:37407 [::]:* - How can this behavior be turned off? Rgds, Klaus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635278: rpcbind still utilizes tcp6/udp6 ports when IPv6 is disabled
Package: rpcbind (0.2.0-6) Version: 0.2.0-6 Environment: - Dell Latitude 8100 - Debian Wheezy (testing) - Kernel 2.6.39-2-686-pae After disabling IPv6 via 'echo net.ipv6.conf.all.disable_ipv6=1 /etc/sysctl.d/disableipv6.conf' it seems no IPv6 protocol is bound to any interface. Nevertheless 'netstat -lp' shows that rpcbind (and rpc.statd) still listen on tcp6/udp6 ports. Aktive Internetverbindungen (Nur Server) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 *:sunrpc*:* LISTEN 745/rpcbind tcp0 0 *:ssh *:* LISTEN 1108/sshd tcp0 0 *:42426 *:* LISTEN 773/rpc.statd tcp6 0 0 [::]:sunrpc [::]:* LISTEN 745/rpcbind tcp6 0 0 [::]:37841 [::]:* LISTEN 773/rpc.statd udp0 0 *:sunrpc*:* 745/rpcbind udp0 0 *:920 *:* 745/rpcbind udp0 0 *:949 *:* 773/rpc.statd udp0 0 *:58048 *:* 773/rpc.statd udp6 0 0 [::]:sunrpc [::]:* 745/rpcbind udp6 0 0 [::]:920[::]:* 745/rpcbind udp6 0 0 [::]:38376 [::]:* 773/rpc.statd Aktive Sockets in der UNIX-Domäne (Nur Server) Proto RefCnt Flags Type State I-Node PID/Program name Pfad unix 2 [ ACC ] STREAM HÖRT 3601 1090/gpm /dev/gpmctl unix 2 [ ACC ] STREAM HÖRT 3106 745/rpcbind /var/run/rpcbind.sock unix 2 [ ACC ] SEQPAKET HÖRT 1693 218/udevd @/org/kernel/udev/udevd unix 2 [ ACC ] STREAM HÖRT 3510 1035/acpid /var/run/acpid.socket unix 2 [ ACC ] STREAM HÖRT 3552 1077/dbus-daemon /var/run/dbus/system_bus_socket Do I need to file a second bug report against nfs-common (1:1.2.4-1) regarding the tcp6/udp6 ports from rpc.statd or is this related to rpcbind? Rgds, Klaus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514131: [linux-image-2.6.26-1-686]: network card 3ccfem656b (3c59x.ko) doesn't work
I guess it's now on me to apologize for a late response. ;-) I today installed and tested 2.6.32 and the problem seems not to exist with this version. Unfortunately not all installed software works with this kernel as it comes out of the box (e.g. NFS, nVidia, etc.) Is there a chance to get a fix for 2.6.26 ? Regards, Klaus Moritz Muehlenhoff wrote: The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576378: gpspipe requests given parameters
Package: gpsd-clients Version: 2.92-1 Severity: important Environment: - Dell Latitude C640 - Debian 6.0 (Squeeze) If I invoke 'gpspipe' with the arguments '-r -s /dev/ttyS0' I'll get an error message requesting the given combination of arguments. host:~# gpspipe -r -s /dev/ttyS0 gpspipe: use of '-s' requires '-r'. Regards, Klaus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576377: gpspipe can't connect to external gpsd
Package: gpsd-clients Version: 2.92-1 Severity: important Environment: - Dell Latitude C640 - Debian 6.0 (Squeeze) If I invoke 'gpspipe' with the arguments '-r gpsd.mainframe.cx:2947' I'll get an error message that gpspipe can't connect to gpsd host:~# gpspipe -r gpsd.mainframe.cx:2947 gpspipe: could not connect to gpsd (null):2947, Unknown error 4294967292(-4) A telnet session to this host will provide NMEA information. Regards, Klaus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562054: subprocess installed post-installation script
Wow,fastest fix ever. (at least for me :-) ) After applying both 'fixes' (modify '/etc/grub.d/30_os-prober' and run grub-install 'install_device' before update-grub) everything works like a charm. :-) Thanks for the excellent work, Klaus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514131: [linux-image-2.6.26-1-686]: network card 3ccfem656b (3c59x.ko) doesn't work
Package: linux-image-2.6.26-1-686 Version: 2.6.26-12 Environment: - Dell Latitude 8100 - 3Com 3CCFEM656B - Debian 2.6 (Lenny) After inserting the network card (3CCFEM656B) the module 3c59x.ko is loaded. Nevertheless, the following entries in /var/log/syslog appear: Feb 4 17:09:24 p933 last message repeated 2 times Feb 4 17:09:26 p933 kernel: [ 3213.560057] pccard: CardBus card inserted into slot 0 Feb 4 17:09:27 p933 kernel: [ 3214.515283] 3c59x :09:00.0: enabling device ( - 0003) Feb 4 17:09:27 p933 kernel: [ 3214.515313] ACPI: PCI Interrupt :09:00.0[A] - Link [LNKD] - GSI 10 (level, low) - IRQ 10 Feb 4 17:09:27 p933 kernel: [ 3214.515338] 3c59x: Donald Becker and others. Feb 4 17:09:27 p933 kernel: [ 3214.515351] :09:00.0: 3Com PCI 3CCFEM656B Cyclone+Winmodem CardBus at e0ad6000. Feb 4 17:09:27 p933 kernel: [ 3214.515367] PCI: Setting latency timer of device :09:00.0 to 64 Feb 4 17:09:27 p933 kernel: [ 3214.525943] ***INVALID CHECKSUM 0094*** 6eth1: setting half-duplex. Feb 4 17:09:27 p933 avahi-daemon[2423]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.20.69. Feb 4 17:09:27 p933 avahi-daemon[2423]: New relevant interface eth1.IPv4 for mDNS. Feb 4 17:09:27 p933 avahi-daemon[2423]: Registering new address record for 192.168.20.69 on eth1.IPv4. Feb 4 17:09:27 p933 modprobe: WARNING: Not loading blacklisted module ipv6 Feb 4 17:09:28 p933 last message repeated 2 times Feb 4 17:10:05 p933 kernel: [ 3252.748965] eth1: setting full-duplex. Feb 4 17:11:16 p933 kernel: [ 3322.592054] irq 10: nobody cared (try booting with the irqpoll option) Feb 4 17:11:16 p933 kernel: [ 3322.592054] Pid: 0, comm: swapper Tainted: P 2.6.26-1-686 #1 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c015280b] __report_bad_irq+0x24/0x69 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c0152812] __report_bad_irq+0x2b/0x69 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c0152a24] note_interrupt+0x1d4/0x208 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c0151fd2] handle_IRQ_event+0x23/0x51 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c0153285] handle_level_irq+0x87/0xb6 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c0105f3a] do_IRQ+0x4d/0x63 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c01042a7] common_interrupt+0x23/0x28 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c012656a] __do_softirq+0x57/0xd3 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c012662b] do_softirq+0x45/0x53 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c01268e2] irq_exit+0x35/0x67 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c0105f3f] do_IRQ+0x52/0x63 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c01042a7] common_interrupt+0x23/0x28 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c01300d8] param_set_charp+0x8/0x48 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [e082029b] acpi_idle_enter_simple+0x196/0x203 [processor] Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c02498cd] cpuidle_idle_call+0x5b/0x86 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c0249872] cpuidle_idle_call+0x0/0x86 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [c01025ce] cpu_idle+0xab/0xcb Feb 4 17:11:16 p933 kernel: [ 3322.592054] === Feb 4 17:11:16 p933 kernel: [ 3322.592054] handlers: Feb 4 17:11:16 p933 kernel: [ 3322.592054] [e088907f] (usb_hcd_irq+0x0/0x73 [usbcore]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] [e0829c11] (ohci_irq_handler+0x0/0x6be [ohci1394]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] [e09ba440] (yenta_interrupt+0x0/0xb3 [yenta_socket]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] [e09ba440] (yenta_interrupt+0x0/0xb3 [yenta_socket]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] [e086a3d6] (e100_intr+0x0/0x85 [e100]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] [e0cdbca5] (vortex_interrupt+0x0/0x2a8 [3c59x]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] Disabling IRQ #10 Also, while the real mac address starts with 00:50:DA:... the mac address reported by udev and ifconfig is usually one out of the following: 00:0a:00:50:16:3f 00:0a:00:50:2c:7f 00:14:00:50:16:3f 00:14:00:50:2c:7f 00:09:76:ab:da:ad (only seen once) The according interface looks ok (e.g. ifconfig eth1) but an attempt to ping a node on the network will either result in a system lookup or the appearance of the following entries in /var/log/syslog: Feb 4 17:15:11 p933 kernel: [ 3559.31] NETDEV WATCHDOG: eth1: transmit timed out Feb 4 17:15:11 p933 kernel: [ 3559.51] eth1: transmit timed out, tx_status 00 status 0604. Feb 4 17:15:11 p933 kernel: [ 3559.65] diagnostics: net media 0003 dma fifo Feb 4 17:15:11 p933 kernel: [ 3559.91] [ cut here ] Feb 4 17:15:11 p933 kernel: [ 3559.99] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x8f/0xdc() Feb 4 17:15:11 p933 kernel: [ 3559.000106] Modules linked in: 3c59x nvidia(P) i2c_core rfcomm l2cap bluetooth ppdev lp speedstep_smi speedstep_lib cpufreq_userspace
