[WPS] a start job is running for lsb raise network interfaces
Hi, I want to configure my system to use WPS, so I put this into /etc/network/interfaces.d/wlan0: auto wlan0 iface wlan0 inet dhcp wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf And this into /etc/wpa_supplicant/wpa_supplicant.conf: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 update_config=1 If I run "wpa_cli wps_pbc" everything works flawlessly, and it updates my wpa_supplicant.conf with the wifi association details. Unfortunately, when I reboot my system without any association in wpa_supplicant.conf (or when the access point is out of range) it gets stuck at "a start job is running for lsb raise network interfaces". Any idea? Thanks, Niccolò Belli
Marvell 88SE9235 support in Debian Wheezy
Hi, Does Wheezy support this chipset? I'd like to buy the Syba SI-PEX40062: http://www.sybausa.com/productInfo.php?iid=1373 Thanks, Niccolò -- http://www.linuxsystems.it -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/513e38c4.3040...@linuxsystems.it
raid1 issue after disk failure: both disks of the array are still active
Hi,
I have a raid1 array with two disks, distro is Squeeze amd64. /dev/sda
is slowly dying, here is a snippet of smartctl -a /dev/sda:
197 Current_Pending_Sector 0x0012 100 100 000Old_age Always
- 2
198 Offline_Uncorrectable 0x0030 100 100 000Old_age
Offline - 1
The bad sector is in the second half-MB of the disk, in fact with dd
if=/dev/sda1 of=/dev/null bs=524228 count=1 skip=1 I get this output in
/var/log/syslog:
root@asterisk:~# dd if=/dev/sda1 of=/dev/null bs=524228 count=1 skip=1
0+1 record dentro
0+1 record fuori
430140 byte (430 kB) copiati, 11,7265 s, 36,7 kB/s
Sep 12 22:15:02 asterisk kernel: [ 8921.561978] dd: sending ioctl
80306d02 to a partition!
Sep 12 22:15:02 asterisk kernel: [ 8921.561986] dd: sending ioctl
80306d02 to a partition!
Sep 12 22:15:03 asterisk kernel: [ 8922.529099] ata3.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 12 22:15:03 asterisk kernel: [ 8922.531774] ata3.00: BMDMA stat 0x44
Sep 12 22:15:03 asterisk kernel: [ 8922.533547] ata3.00: failed command:
READ DMA
Sep 12 22:15:03 asterisk kernel: [ 8922.535313] ata3.00: cmd
c8/00:08:48:0f:00/00:00:00:00:00/e0 tag 0 dma 4096 in
Sep 12 22:15:03 asterisk kernel: [ 8922.535316] res
51/40:00:48:0f:00/40:00:00:00:00/e0 Emask 0x9 (media error)
Sep 12 22:15:03 asterisk kernel: [ 8922.538891] ata3.00: status: { DRDY
ERR }
Sep 12 22:15:03 asterisk kernel: [ 8922.540675] ata3.00: error: { UNC }
Sep 12 22:15:04 asterisk kernel: [ 8923.508206] ata3.00: configured for
UDMA/133
Sep 12 22:15:04 asterisk kernel: [ 8923.508220] ata3: EH complete
Sep 12 22:15:05 asterisk kernel: [ 8924.469512] ata3.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 12 22:15:05 asterisk kernel: [ 8924.472323] ata3.00: BMDMA stat 0x44
Sep 12 22:15:05 asterisk kernel: [ 8924.475260] ata3.00: failed command:
READ DMA
Sep 12 22:15:05 asterisk kernel: [ 8924.477023] ata3.00: cmd
c8/00:08:48:0f:00/00:00:00:00:00/e0 tag 0 dma 4096 in
Sep 12 22:15:05 asterisk kernel: [ 8924.477025] res
51/40:00:48:0f:00/40:00:00:00:00/e0 Emask 0x9 (media error)
Sep 12 22:15:05 asterisk kernel: [ 8924.480595] ata3.00: status: { DRDY
ERR }
Sep 12 22:15:05 asterisk kernel: [ 8924.482370] ata3.00: error: { UNC }
Sep 12 22:15:06 asterisk kernel: [ 8925.452209] ata3.00: configured for
UDMA/133
Sep 12 22:15:06 asterisk kernel: [ 8925.452224] ata3: EH complete
Sep 12 22:15:07 asterisk kernel: [ 8926.418504] ata3.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 12 22:15:07 asterisk kernel: [ 8926.420741] ata3.00: BMDMA stat 0x44
Sep 12 22:15:07 asterisk kernel: [ 8926.422486] ata3.00: failed command:
READ DMA
Sep 12 22:15:07 asterisk kernel: [ 8926.424279] ata3.00: cmd
c8/00:08:48:0f:00/00:00:00:00:00/e0 tag 0 dma 4096 in
Sep 12 22:15:07 asterisk kernel: [ 8926.424281] res
51/40:00:48:0f:00/40:00:00:00:00/e0 Emask 0x9 (media error)
Sep 12 22:15:07 asterisk kernel: [ 8926.427861] ata3.00: status: { DRDY
ERR }
Sep 12 22:15:07 asterisk kernel: [ 8926.429660] ata3.00: error: { UNC }
Sep 12 22:15:08 asterisk kernel: [ 8927.396270] ata3.00: configured for
UDMA/133
Sep 12 22:15:08 asterisk kernel: [ 8927.396285] ata3: EH complete
Sep 12 22:15:09 asterisk kernel: [ 8928.359173] ata3.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 12 22:15:09 asterisk kernel: [ 8928.361647] ata3.00: BMDMA stat 0x44
Sep 12 22:15:09 asterisk kernel: [ 8928.364273] ata3.00: failed command:
READ DMA
Sep 12 22:15:09 asterisk kernel: [ 8928.366028] ata3.00: cmd
c8/00:08:48:0f:00/00:00:00:00:00/e0 tag 0 dma 4096 in
Sep 12 22:15:09 asterisk kernel: [ 8928.366030] res
51/40:00:48:0f:00/40:00:00:00:00/e0 Emask 0x9 (media error)
Sep 12 22:15:09 asterisk kernel: [ 8928.369643] ata3.00: status: { DRDY
ERR }
Sep 12 22:15:09 asterisk kernel: [ 8928.371420] ata3.00: error: { UNC }
Sep 12 22:15:10 asterisk kernel: [ 8929.340218] ata3.00: configured for
UDMA/133
Sep 12 22:15:10 asterisk kernel: [ 8929.340233] ata3: EH complete
Sep 12 22:15:11 asterisk kernel: [ 8930.332648] ata3.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 12 22:15:11 asterisk kernel: [ 8930.334453] ata3.00: BMDMA stat 0x44
Sep 12 22:15:11 asterisk kernel: [ 8930.336245] ata3.00: failed command:
READ DMA
Sep 12 22:15:11 asterisk kernel: [ 8930.337995] ata3.00: cmd
c8/00:08:48:0f:00/00:00:00:00:00/e0 tag 0 dma 4096 in
Sep 12 22:15:11 asterisk kernel: [ 8930.337998] res
51/40:00:48:0f:00/40:00:00:00:00/e0 Emask 0x9 (media error)
Sep 12 22:15:11 asterisk kernel: [ 8930.341583] ata3.00: status: { DRDY
ERR }
Sep 12 22:15:11 asterisk kernel: [ 8930.343360] ata3.00: error: { UNC }
Sep 12 22:15:12 asterisk kernel: [ 8931.344205] ata3.00: configured for
UDMA/133
Sep 12 22:15:12 asterisk kernel: [ 8931.344220] ata3: EH complete
Sep 12 22:15:13 asterisk kernel: [ 8932.306376] ata3.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 12 22:15:13 asterisk kernel: [ 8932.308201]
pbuilder and CONCURRENCY_LEVEL
How can I set CONCURRENCY_LEVEL when using pbuilder? CONCURRENCY_LEVEL=9 pbuilder build file.dsc doesn't work. Thank you, Darkbasic -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4daefc2a.3050...@gmail.com
Re: pbuilder and CONCURRENCY_LEVEL
Il 20/04/2011 17:30, Niccolò Belli ha scritto: How can I set CONCURRENCY_LEVEL when using pbuilder? CONCURRENCY_LEVEL=9 pbuilder build file.dsc doesn't work. Found it, there is an option to pass parameters to dpkg-buildpackage: --debbuildopts -j9 Darkbasic -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4daf5bb5.3050...@gmail.com
Re: No input in serial console
SOLVED: https://savannah.gnu.org/bugs/index.php?32115 Il 12 gennaio 2011 20:57, Niccolò Belli darkbas...@gmail.com ha scritto: I'm sorry, it isn't Lenny, it's Squeeze (Debian unstable). Il 12 gennaio 2011 20:53, Niccolò Belli darkbas...@gmail.com ha scritto: Hi, I'm using an RS232 serial console with Debian Lenny. Output works fine (I can see the output since grub starts), but input doesn't (both in grub and when it prompts for login). Here is my /etc/default/grub: [...] GRUB_CMDLINE_LINUX_DEFAULT=quiet console=tty0 console=ttyS0,115200n8 [...] GRUB_TERMINAL=console serial GRUB_SERIAL_COMMAND=serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1 [...] and my /etc/inittab: [...] T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100 Here is how I configured minicom in the client: | A - Serial Device : /dev/ttyS0 | B - Lockfile Location : /var/lock | C - Callin Program : | D - Callout Program : | E - Bps/Par/Bits : 115200 8N1| | F - Hardware Flow Control : No | G - Software Flow Control : No Can someone help me? Thank you, Darkbasic -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTinMGJeZ803XoYExJH8E+OsXwwaSiXbiqÛv...@mail.gmail.com
No input in serial console
Hi, I'm using an RS232 serial console with Debian Lenny. Output works fine (I can see the output since grub starts), but input doesn't (both in grub and when it prompts for login). Here is my /etc/default/grub: [...] GRUB_CMDLINE_LINUX_DEFAULT=quiet console=tty0 console=ttyS0,115200n8 [...] GRUB_TERMINAL=console serial GRUB_SERIAL_COMMAND=serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1 [...] and my /etc/inittab: [...] T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100 Here is how I configured minicom in the client: | A -Serial Device : /dev/ttyS0 | B - Lockfile Location : /var/lock | C - Callin Program : | D - Callout Program : | E -Bps/Par/Bits : 115200 8N1| | F - Hardware Flow Control : No | G - Software Flow Control : No Can someone help me? Thank you, Darkbasic -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktim9waa5zj5u1bopf0y+8uaboi7yf+5whzw7z...@mail.gmail.com
Re: No input in serial console
I'm sorry, it isn't Lenny, it's Squeeze (Debian unstable). Il 12 gennaio 2011 20:53, Niccolò Belli darkbas...@gmail.com ha scritto: Hi, I'm using an RS232 serial console with Debian Lenny. Output works fine (I can see the output since grub starts), but input doesn't (both in grub and when it prompts for login). Here is my /etc/default/grub: [...] GRUB_CMDLINE_LINUX_DEFAULT=quiet console=tty0 console=ttyS0,115200n8 [...] GRUB_TERMINAL=console serial GRUB_SERIAL_COMMAND=serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1 [...] and my /etc/inittab: [...] T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100 Here is how I configured minicom in the client: | A - Serial Device : /dev/ttyS0 | B - Lockfile Location : /var/lock | C - Callin Program : | D - Callout Program : | E - Bps/Par/Bits : 115200 8N1| | F - Hardware Flow Control : No | G - Software Flow Control : No Can someone help me? Thank you, Darkbasic -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikup_1u5mihsgiyzy6h0qkqnqrum-vcoslg0...@mail.gmail.com
