November 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] udev rules still in /lib/udev
by Alin M Elena 28 Nov '12

28 Nov '12

Hi, After some angst and one night without internet because rules being in the wrong folder /lib/udev/rules.d/ I have decided to add a blame list of packages that still install them in /lib/udev rather that /usr/lib/udev here are mine... rpm -qf /lib/udev/rules.d/*.rules | sort -u hdparm-9.43-1.1.x86_64 libgphoto2-6-2.5.0-5.1.x86_64 libgpod-tools-0.8.2-10.18.x86_64 lirc-0.9.0-3.6.x86_64 NetworkManager-0.9.6.4-2.1.x86_64 please add yours, ModemManager is already fixed... regards, Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________

4 6

[opensuse-factory] modem-manager and its daemons part II
by Alin M Elena 27 Nov '12

27 Nov '12

Hi, for reason independent on me I did a clean install of factory... net install last iso of 25th of November... and then I have updated all nicely to factory... All to have the surprise of having my usb mobile broadband (snail version) not working,,, from the exterior the blue led of the dongle is blinking... meaning ready for business... but from inside the box the thing does not even exist.. here it is some info dmesg part [ 526.208107] usb 2-4: new high-speed USB device number 10 using ehci_hcd [ 526.325249] usb 2-4: New USB device found, idVendor=12d1, idProduct=1446 [ 526.325255] usb 2-4: New USB device strings: Mfr=3, Product=2, SerialNumber=0 [ 526.325258] usb 2-4: Product: HUAWEI Mobile [ 526.325261] usb 2-4: Manufacturer: HUAWEI Technology [ 526.327084] scsi20 : usb-storage 2-4:1.0 [ 526.327252] scsi21 : usb-storage 2-4:1.1 [ 527.000571] usb 2-4: USB disconnect, device number 10 [ 535.998075] usb 2-4: new high-speed USB device number 11 using ehci_hcd [ 536.115225] usb 2-4: New USB device found, idVendor=12d1, idProduct=1446 [ 536.115237] usb 2-4: New USB device strings: Mfr=3, Product=2, SerialNumber=0 [ 536.115244] usb 2-4: Product: HUAWEI Mobile [ 536.115250] usb 2-4: Manufacturer: HUAWEI Technology [ 536.118558] scsi22 : usb-storage 2-4:1.0 [ 536.119476] scsi23 : usb-storage 2-4:1.1 [ 536.776596] usb 2-4: USB disconnect, device number 11 [ 541.023062] usb 2-4: new high-speed USB device number 12 using ehci_hcd [ 541.140092] usb 2-4: New USB device found, idVendor=12d1, idProduct=1436 [ 541.140098] usb 2-4: New USB device strings: Mfr=4, Product=3, SerialNumber=0 [ 541.140102] usb 2-4: Product: HUAWEI Mobile [ 541.140105] usb 2-4: Manufacturer: HUAWEI Technology [ 541.143027] option 2-4:1.0: GSM modem (1-port) converter detected [ 541.143245] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB0 [ 541.145156] cdc_ether 2-4:1.1 wwan0: register 'cdc_ether' at usb-0000:00:06.1-4, Mobile Broadband Network Device, 02:50:f3:00:00:00 [ 541.145306] option 2-4:1.3: GSM modem (1-port) converter detected [ 541.145378] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB1 [ 541.145724] option 2-4:1.4: GSM modem (1-port) converter detected [ 541.145874] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB2 [ 541.146667] scsi28 : usb-storage 2-4:1.5 [ 541.147142] scsi29 : usb-storage 2-4:1.6 [ 542.152286] scsi 28:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 [ 542.152601] scsi 29:0:0:0: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2 [ 542.153469] sd 29:0:0:0: Attached scsi generic sg3 type 0 [ 542.156198] sd 29:0:0:0: [sdc] Attached SCSI removable disk [ 542.157049] sr1: scsi-1 drive [ 542.157154] sr 28:0:0:0: Attached scsi CD-ROM sr1 [ 542.157242] sr 28:0:0:0: Attached scsi generic sg4 type 5 network manager part... nmcli nm RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running connected enabled enabled enabled disabled using the mm-test.py wget http://cgit.freedesktop.org/ModemManager/ModemManager/plain/test/mm- test.py ./mm-test.py No modems found zypper se -is modem Retrieving repository 'localRPMs' metadata ............................................................................................................. [done] Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+--------------------+---------+--------------------------+--------+--------------------------------------------------------- i | ModemManager | package | 0.6.0.0-1.3 | x86_64 | openSUSE-12.3-Oss i | libQtModemManager0 | package | 0.5.0git.1329528114-88.1 | x86_64 | home:rwooninck:UNSTABLE_KDE4 (KDE_Qt48_openSUSE_Factory) [root@abbaton:/home/alin]: zypper se -is ppp Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+--------+---------+-------------+--------+------------------ i | ppp | package | 2.4.5-14.4 | x86_64 | openSUSE-12.3-Oss i | smpppd | package | 1.60.56-4.5 | x86_64 | openSUSE-12.3-Oss Any help is much appreciated. Alin I have also observed that modem-manager still installs his udev rules in /lib/udev/rules.d rather than /usr/lib/udev/rules.d/ -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________

4 5

[opensuse-factory] KDE rebuilds in Tumbleweed
by Achim Gratz 27 Nov '12

27 Nov '12

Now that KDE is back in Tumbleweed it seems to rebuild almost daily. Even if that was intended, why does it also rebuild the noarch packages (all the artwork, icons and stuff) that surely never change? And if OBS absolutely must rebuild them, should they be packaged and delivered each time, with presumably the same content (the file sizes always differ by a few bytes, which seems to be logging information) and just a different label? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

Re: [opensuse-factory] modem-manager and its daemons part II
by Alin M Elena 27 Nov '12

27 Nov '12

this is the log from 12.2 and working modem-manager[23760]: <info> [1354041601.438126] [main.c:167] main(): ModemManager (version 0.5.2.0) starting... modem-manager[23760]: <info> [1354041601.440798] [mm-manager.c:120] load_plugin(): Loaded plugin Novatel modem-manager[23760]: <info> [1354041601.441017] [mm-manager.c:120] load_plugin(): Loaded plugin Option modem-manager[23760]: <info> [1354041601.441179] [mm-manager.c:120] load_plugin(): Loaded plugin Gobi modem-manager[23760]: <info> [1354041601.441338] [mm-manager.c:120] load_plugin(): Loaded plugin SimTech modem-manager[23760]: <info> [1354041601.441495] [mm-manager.c:120] load_plugin(): Loaded plugin Generic modem-manager[23760]: <info> [1354041601.441653] [mm-manager.c:120] load_plugin(): Loaded plugin Longcheer modem-manager[23760]: <info> [1354041601.441817] [mm-manager.c:120] load_plugin(): Loaded plugin Nokia modem-manager[23760]: <info> [1354041601.441978] [mm-manager.c:120] load_plugin(): Loaded plugin Samsung modem-manager[23760]: <info> [1354041601.442139] [mm-manager.c:120] load_plugin(): Loaded plugin Wavecom modem-manager[23760]: <info> [1354041601.442305] [mm-manager.c:120] load_plugin(): Loaded plugin ZTE modem-manager[23760]: <info> [1354041601.442467] [mm-manager.c:120] load_plugin(): Loaded plugin Linktop modem-manager[23760]: <info> [1354041601.442633] [mm-manager.c:120] load_plugin(): Loaded plugin AnyData modem-manager[23760]: <info> [1354041601.442795] [mm-manager.c:120] load_plugin(): Loaded plugin X22X modem-manager[23760]: <info> [1354041601.442961] [mm-manager.c:120] load_plugin(): Loaded plugin Ericsson MBM modem-manager[23760]: <info> [1354041601.443125] [mm-manager.c:120] load_plugin(): Loaded plugin MotoC modem-manager[23760]: <info> [1354041601.443299] [mm-manager.c:120] load_plugin(): Loaded plugin Option High-Speed modem-manager[23760]: <info> [1354041601.443470] [mm-manager.c:120] load_plugin(): Loaded plugin Huawei modem-manager[23760]: <info> [1354041601.443641] [mm-manager.c:120] load_plugin(): Loaded plugin Sierra modem-manager[23760]: <debug> [1354041601.445640] [mm-manager.c:809] device_added(): (tty/ttyS0): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.445792] [mm-manager.c:809] device_added(): (tty/ttyS1): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.445925] [mm-manager.c:809] device_added(): (tty/ttyS2): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.446047] [mm-manager.c:809] device_added(): (tty/ttyS3): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.446168] [mm-manager.c:809] device_added(): (tty/ttyS4): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.446289] [mm-manager.c:809] device_added(): (tty/ttyS5): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.446412] [mm-manager.c:809] device_added(): (tty/ttyS6): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.447003] [mm-manager.c:809] device_added(): (tty/ttyS7): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041637.441873] [mm-manager.c:491] try_supports_port(): (Huawei): (ttyUSB2) deferring support check modem-manager[23760]: <debug> [1354041637.445329] [mm-manager.c:491] try_supports_port(): (Huawei): (ttyUSB1) deferring support check modem-manager[23760]: <info> [1354041637.462561] [mm-serial-port.c:741] mm_serial_port_open(): (ttyUSB0) opening serial port... modem-manager[23760]: <debug> [1354041637.463613] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB0) device open count is 1 (open) modem-manager[23760]: <debug> [1354041637.463675] [mm-plugin-base.c:859] try_open(): (ttyUSB0): probe requested by plugin 'Huawei' modem-manager[23760]: <debug> [1354041637.599075] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GCAP<CR>' modem-manager[23760]: <debug> [1354041638.919454] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- 'AT+GCAP' modem-manager[23760]: <debug> [1354041638.920492] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR>' modem-manager[23760]: <debug> [1354041638.920938] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>+CME ERROR: SIM busy<CR><LF>' modem-manager[23760]: <debug> [1354041638.921017] [mm-serial-parsers.c:438] mm_serial_parser_v1_parse(): Got failure code 14: SIM busy modem-manager[23760]: <debug> [1354041638.921086] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GCAP<CR>' modem-manager[23760]: <debug> [1354041639.621239] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- 'AT+GCAP' modem-manager[23760]: <debug> [1354041639.622115] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR>' modem-manager[23760]: <debug> [1354041639.623237] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>+GCAP: +CGSM,+DS, +ES<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041639.623399] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 0 (close) modem-manager[23760]: <info> [1354041639.623418] [mm-serial-port.c:859] mm_serial_port_close(): (ttyUSB0) closing serial port... modem-manager[23760]: <info> [1354041639.624477] [mm-serial-port.c:880] mm_serial_port_close(): (ttyUSB0) serial port closed modem-manager[23760]: <debug> [1354041639.629922] [mm-modem-base.c:155] mm_modem_base_add_port(): (ttyUSB0) type primary claimed by /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <info> [1354041639.630077] [mm-serial-port.c:741] mm_serial_port_open(): (ttyUSB0) opening serial port... modem-manager[23760]: <debug> [1354041639.631124] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB0) device open count is 1 (open) modem-manager[23760]: <debug> [1354041639.631198] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB0) device open count is 2 (open) modem-manager[23760]: <debug> [1354041639.631221] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB0) device open count is 3 (open) modem-manager[23760]: <info> [1354041639.631350] [mm-manager.c:564] do_grab_port(): (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 claimed port ttyUSB0 modem-manager[23760]: <debug> [1354041639.631392] [mm-manager.c:317] add_modem(): Added modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041639.631411] [mm-manager.c:243] check_export_modem(): (tty/ttyUSB0): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041639.631524] [mm-manager.c:243] check_export_modem(): (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041639.631873] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'ATE0<CR>' modem-manager[23760]: <debug> [1354041639.642239] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- 'ATE' modem-manager[23760]: <debug> [1354041639.642491] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '0' modem-manager[23760]: <debug> [1354041639.650498] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR>' modem-manager[23760]: <debug> [1354041639.650857] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041639.650921] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GMI<CR>' modem-manager[23760]: <debug> [1354041639.968379] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>huawei<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041639.968928] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GMM<CR>' modem-manager[23760]: <debug> [1354041640.088869] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>E1752<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.089727] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GMR<CR>' modem-manager[23760]: <debug> [1354041640.132750] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>11.126.08.01.00<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.133270] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CGMI<CR>' modem-manager[23760]: <debug> [1354041640.174134] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>huawei<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.174286] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CGMM<CR>' modem-manager[23760]: <debug> [1354041640.241243] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>E1752<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.241312] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CGMR<CR>' modem-manager[23760]: <debug> [1354041640.288238] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>11.126.08.01.00<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.288728] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'ATI<CR>' modem-manager[23760]: <debug> [1354041640.313902] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>Manufacturer: huawei<CR><LF>Model: E1752<CR><LF>Revision: 11.126.08.01.00<CR><LF>IMEI: 353220040853787<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.313988] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'ATI1<CR>' modem-manager[23760]: <debug> [1354041640.346151] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>Manufacturer: huawei<CR><LF>Model: E1752<CR><LF>Revision: 11.126.08.01.00<CR><LF>IMEI: 353220040853787<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.346230] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GSN<CR>' modem-manager[23760]: <debug> [1354041640.390385] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>353220040853787<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.390525] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CGSN<CR>' modem-manager[23760]: <debug> [1354041640.441748] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>353220040853787<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.442241] [mm-manager.c:457] supports_defer_timeout(): (ttyUSB2): re-checking support... modem-manager[23760]: <info> [1354041640.443073] [mm-serial-port.c:741] mm_serial_port_open(): (ttyUSB2) opening serial port... modem-manager[23760]: <debug> [1354041640.444879] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB2) device open count is 1 (open) modem-manager[23760]: <debug> [1354041640.445023] [mm-modem-helpers.c:920] mm_create_device_identifier(): Device ID source '000012d100001436Manufacturer:huaweiModel:E1752Revision:11.126.08.01.00IMEI:353220040853787+GCAP: +CGSM,+DS,+ES35322004085378711.126.08.01.00E1752huawei' modem-manager[23760]: <debug> [1354041640.445045] [mm-modem-helpers.c:921] mm_create_device_identifier(): Device ID '9e5fcfd87c7028286423c289c6776ef5f143db5e' modem-manager[23760]: <debug> [1354041640.445085] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 2 (close) modem-manager[23760]: <debug> [1354041640.445111] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'ATE0<CR>' modem-manager[23760]: <debug> [1354041640.451761] [mm-manager.c:457] supports_defer_timeout(): (ttyUSB1): re-checking support... modem-manager[23760]: <info> [1354041640.452261] [mm-serial-port.c:741] mm_serial_port_open(): (ttyUSB1) opening serial port... modem-manager[23760]: <debug> [1354041640.453755] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB1) device open count is 1 (open) modem-manager[23760]: <debug> [1354041640.479242] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.480088] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 1 (close) modem-manager[23760]: <debug> [1354041640.480749] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CMEE=1<CR>' modem-manager[23760]: <debug> [1354041640.543745] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.544286] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CPIN?<CR>' modem-manager[23760]: <debug> [1354041640.600866] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>+CPIN: READY<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.601016] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB0) device open count is 2 (open) modem-manager[23760]: <debug> [1354041640.601041] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 1 (close) modem-manager[23760]: <debug> [1354041640.601070] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CRSM=176,12258,0,0,10<CR>' modem-manager[23760]: <debug> [1354041641.046263] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>+CRSM: 144,0,"985303120081004340F5"<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041641.047080] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 0 (close) modem-manager[23760]: <info> [1354041641.047125] [mm-serial-port.c:859] mm_serial_port_close(): (ttyUSB0) closing serial port... modem-manager[23760]: <info> [1354041641.047986] [mm-serial-port.c:880] mm_serial_port_close(): (ttyUSB0) serial port closed modem-manager[23760]: <debug> [1354041641.048066] [mm-generic-gsm.c:507] get_iccid_done(): SIM ID source '8935302100180034045' modem-manager[23760]: <debug> [1354041641.048082] [mm-generic-gsm.c:508] get_iccid_done(): SIM ID '00f77f4bb96a6dfb449b93a04e9b4d336174e8e5' modem-manager[23760]: <debug> [1354041641.048228] [mm-manager.c:243] check_export_modem(): (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041642.323343] [mm-at-serial-port.c:333] debug_log(): (ttyUSB2): <-- '<CR><LF>^SIMST:1<CR><LF>' modem-manager[23760]: <debug> [1354041642.324389] [mm-at-serial-port.c:333] debug_log(): (ttyUSB2): <-- '<CR><LF>^SRVST:2<CR><LF>' modem-manager[23760]: <debug> [1354041643.671363] [mm-at-serial-port.c:333] debug_log(): (ttyUSB2): <-- '<CR><LF>^RSSI:14<CR><LF>' modem-manager[23760]: <debug> [1354041643.671476] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB2) device open count is 0 (close) modem-manager[23760]: <info> [1354041643.671497] [mm-serial-port.c:859] mm_serial_port_close(): (ttyUSB2) closing serial port... modem-manager[23760]: <info> [1354041643.672492] [mm-serial-port.c:880] mm_serial_port_close(): (ttyUSB2) serial port closed modem-manager[23760]: <debug> [1354041643.673074] [mm-modem-base.c:155] mm_modem_base_add_port(): (ttyUSB2) type secondary claimed by /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <info> [1354041643.673306] [mm-manager.c:564] do_grab_port(): (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 claimed port ttyUSB2 modem-manager[23760]: <debug> [1354041643.673367] [mm-manager.c:243] check_export_modem(): (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041648.450016] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB1) device open count is 0 (close) modem-manager[23760]: <info> [1354041648.450065] [mm-serial-port.c:859] mm_serial_port_close(): (ttyUSB1) closing serial port... modem-manager[23760]: <info> [1354041648.451099] [mm-serial-port.c:880] mm_serial_port_close(): (ttyUSB1) serial port closed modem-manager[23760]: <debug> [1354041648.451599] [mm-modem-base.c:155] mm_modem_base_add_port(): (ttyUSB1) type ignored claimed by /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <info> [1354041648.451837] [mm-manager.c:564] do_grab_port(): (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 claimed port ttyUSB1 modem-manager[23760]: <debug> [1354041648.451954] [mm-manager.c:265] check_export_modem(): Exported modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 as /org/freedesktop/ModemManager/Modems/0 modem-manager[23760]: <debug> [1354041648.452005] [mm-manager.c:278] check_export_modem(): (/org/freedesktop/ModemManager/Modems/0): VID 0x12D1 PID 0x1436 (usb) modem-manager[23760]: <debug> [1354041648.452019] [mm-manager.c:279] check_export_modem(): (/org/freedesktop/ModemManager/Modems/0): data port is ttyUSB0 modem-manager[23760]: <info> [1354041665.939095] [mm-manager.c:862] device_removed(): (tty/ttyUSB0): released by modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041665.939178] [mm-modem-base.c:185] mm_modem_base_remove_port(): (ttyUSB0) type primary removed from /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041665.939217] [mm-manager.c:204] remove_modem(): Removed modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] modem-manager and its daemons part II
by Alin M Elena 27 Nov '12

27 Nov '12

> Please verify udev has created the device nodes. l /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 Nov 27 17:17 /dev/ttyUSB0 crw-rw---- 1 root dialout 188, 1 Nov 27 17:17 /dev/ttyUSB1 crw-rw---- 1 root dialout 188, 2 Nov 27 17:17 /dev/ttyUSB2 i this is what you mean by devices. Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Error or as designed? glu-devel not required by Mesa-devel (like before Mesa-libGLU-devel)
by Joop Boonen 27 Nov '12

27 Nov '12

Hi all, I saw quite a few packages fail to build in games for Factory due to a missing GL/glu.h this is provided by glu-devel. Since recently up to and including openSUSE 12.2 Mesa-devel has a requirement for Mesa-libGLU-devel. This package doesn't exist any more. This dependency can now be solved by glu-devel. I wonder has the dependency been removed accidentally or is it planned. If it's not planned it no use to fix involved packages. If it's planned the packages can be fixed by adding this to the spec file: %if 0%{?suse_version} > 1220 BuildRequires: glu-devel %endif Regards, Joop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] 12.3 samba trying to use port 1024?
by Linda Walsh 26 Nov '12

26 Nov '12

i was trying to fix some problems in network connectivity, so I'm not sure 100% if the problem was in samba -- but it appeared to be trying to make use of port 1024 for some ep or com like function (didn't get exact message -- was another boot time error that I saw.. not sure if it was samba trying to use a a port that's already allocated for local use, or some other problem. Only think I saw in the source was 1024-65535 being for user-level usage (vs. root), but didn't see anything that should have been using it. Is there anything in suse's configs that's trying to make use of this port? Is it configurable somewhere? tnx... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] unknown type name 'size_t' in /usr/include/scsi/sg.h
by Ilya Chernykh 26 Nov '12

26 Nov '12

Under latest Factory rebuild: [ 136s] /usr/include/scsi/sg.h:38:3: error: unknown type name 'size_t' I do not know to what package this file belongs. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Re: Why is initrd needed - to support moving bin files from root->/usr? That requires extra patches by Suse.
by Linda Walsh 26 Nov '12

26 Nov '12

Brian K. White wrote: > > Custom built kernels are probably a support nightmare. ----- How is a custom built kernel any more of a support nightmare than a custom built initrd? At least with the kernel, you can list out the config and easily see what went into it. Is there a proc interface for listing out the contents of initrd? I call phooey on this FUD... the initrd is more customized than any kernel. The kernel has a common interface for customization across all distros -- but show me the common initrd interface. The initrd interface is worse in this way and every way mentioned so far. > > I don't fault them for using initrd, but I do think it sucks that they > deliberately make it essentially required when it doesn't have to be. ---- At one point, it was an easy way out -- because it JUST contained the modules you needed to build -- it wasn't a custom boot disk. > > Using an initrd is a downgrade in some cases. _Requiring_ it is an even > bigger downgrade in general, as it's a loss in flexibility and in some > cases a loss in efficiency. > > I don't think xfs is a reasonable default fs for a linux distro like > opensuse either. There are special linux distros that target security > and reliability above all else, including at the expense of performance. > I don't think suse was ever one of those. It was a general purpose OS > that now targets desktops. xfs is not the best fs for desktops nor even > for all servers. ---- It is the best for servers, and it was part of a C2-evaluated security distro (Trusted Irix) before linux existed. But it was developed to meet the needs of the media creation industry who needed to write real-time media steams -- no other file system could do that at the time, and no other file system today has it's benefits in handling media files. Where it is weak is in handling tiny bits of info -- and then -- only really on deletion. It tries to be efficient -- to the point that it will store data and/or access information in the inode if the amount is very small you have large enough inodes. But there are some features in NON-unix standard FS's that have potential for being better than XFS -- ZFS and BTRFS... maybe... have to see where they end up.. right now, ZFS is slower due to implementation and BTRFS still is in early development. > > But opensuse isn't all linux itself, it's just opensuse. Every > distribution takes pieces from the world of available code and packages > them up in different ways that serve different needs. > > The targets opensuse serves has shifted from those suse used to serve > very well that's all. It's not a crime it just sucks for us. --- Not a crime, BUT it was a distro that was general purpose and one of the best... there is no other distro that has what Suse had -- or even what suse could have again if it really turned around. My last boss bet me suse would be out of business within a year -- that was back in 2001. I never take bets - but at the time, it was a safe bet, as I knew it had at least 3-6 years more, minimum. now...If the distro doesn't change directions -- it will be gone or a bit player in 3-5 and I don't see another similar one on the horizon with the same stability that OSuse had. > > I don't like that opensuse has veered off from the kind of distro it > used to be, because I was well served by what it used to be and I am not > well served by what it is now, and it means I now have to do a bunch of > work. > > But some of these things you're arguing are not really just. > They should be allowed for but I don't think they are reasonable to > expect as defaults. ---- I'm arguing for not *disallowing* them as default choices. People are saying there is no choice but to do "X", I am pointing out alternatives at every step and every point that belies that fact -- not that I am trying to convert everyone to my choices -- but I will fight to show my choices as solving all of their problems as long as they continue to hold up their problems as unsolvable and needing to kill off my choice as a consequence. What's happening is that they want to make sure there are no alternatives. That's really what is going on. Then they can more easily control the end user just as MS controls most of the afterboot env after win7 and and felt comfortable wiping out the desktop in win8. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] How to reliably check for SUSE distribution?
by Andrey Borzenkov 25 Nov '12

25 Nov '12

DKMS currently is using /etc/SuSEconfig to detect whether it is running on SUSE. As I understand SuSEconfig is scheduled to be removed entirely. What is the proper way to detect distribution? I would use /etc/SuSE-release, but may be there were reasons to use SuSEconfig in the first place. DKMS needs to know distribution to decide e.g. whether it needs to do kernel source preparation or it can skip it. TIA -andrey -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 6