Re: [NC10] Kernel 2.6.31
Posted: 15 Oct 2009, 11:10
New kernel 2.6.31-14 on repository (based on vanilla 2.6.31.4).
Linux On My Samsung
[NC10] Kernel 2.6.31
Page 7 of 8
Re: [NC10] Kernel 2.6.31
Posted: 15 Oct 2009, 13:21
Hum my partition is dead now... sda5 is unknown
Re: [NC10] Kernel 2.6.31
Posted: 16 Oct 2009, 15:58
found !
You have to add "rootflags=noload" to your menu.lst,at the kernel line, and you get rid of the journal from your system partition. (with the noload in the fstab ofcourse)
You have to add "rootflags=noload" to your menu.lst,at the kernel line, and you get rid of the journal from your system partition. (with the noload in the fstab ofcourse)
Re: [NC10] Kernel 2.6.31
Posted: 18 Oct 2009, 12:59
I'm glad you have found the solution, thanks for sharing it with us. 
Re: [NC10] Kernel 2.6.31
Posted: 18 Oct 2009, 18:20
Hi voRia,
I have a question about the kernel:
I had recently bought a Samsung E252 (comperable with R522) which have nearly the same Fn-Keys like the NC10. But have a Core2Duo-CPU inside so it runs properly with a 64bit-Kernel. How I get the Fn-functions also in this Notbook like the NC10? Were the differences to the NC10-Kernel too much for compiling a 64bit-Issue?
Your Fn-Key-Sripts are running well, but only Fn-Sleep, Fn2 , Brightness und Fn10-12 will do, Fn4 - Fn9 are without response.
I had done a workaround with desktop-icons.
Regards
André
I have a question about the kernel:
I had recently bought a Samsung E252 (comperable with R522) which have nearly the same Fn-Keys like the NC10. But have a Core2Duo-CPU inside so it runs properly with a 64bit-Kernel. How I get the Fn-functions also in this Notbook like the NC10? Were the differences to the NC10-Kernel too much for compiling a 64bit-Issue?
Your Fn-Key-Sripts are running well, but only Fn-Sleep, Fn2 , Brightness und Fn10-12 will do, Fn4 - Fn9 are without response.
I had done a workaround with desktop-icons. Regards
André
Re: [NC10] Kernel 2.6.31
Posted: 19 Oct 2009, 08:52
The Fn-F9 script is specific for the wireless card used by NC10. It removes/inserts the 'ath5k' module in order to toggle the wireless. It's highly probable that the E252 uses a different wireless device, so you have to modify the script and let it work with the kernel module you need.
Easily done: open the file '/usr/lib/nc10/wifi.sh' and replace every 'ath5k' instance with the name of the kernel module for your wireless device.
About the Fn-F4, first of all check if and how it's recognized by using the 'xev' command line utility, then let me know.
Easily done: open the file '/usr/lib/nc10/wifi.sh' and replace every 'ath5k' instance with the name of the kernel module for your wireless device.
About the Fn-F4, first of all check if and how it's recognized by using the 'xev' command line utility, then let me know.
Re: [NC10] Kernel 2.6.31
Posted: 19 Oct 2009, 10:41
Thanks, I don't know wich card exactly is used, but an ath5k driver is also running. With manually started script "sudo nc10 wifi", the wifi is running well. But not with the Fn9-Key.
xev hadt put out many lines like this:
Code: Select all
captain@hydra:~$ lsmod
Module Size Used by
ath5k 136840 0
mac80211 210232 1 ath5k
led_class 5256 1 ath5k
ath 10176 1 ath5k
cfg80211 108920 3 ath5k,mac80211,ath
cryptd 8168 0
aes_x86_64 8992 0
aes_generic 28000 1 aes_x86_64
binfmt_misc 10284 1
ppdev 8200 0
bridge 57152 0
stp 2980 1 bridge
bnep 15136 2
lp 11908 0
parport 42928 2 ppdev,lp
snd_hda_codec_atihdmi 4320 1
snd_hda_codec_realtek 277860 1
...
Code: Select all
MotionNotify event, serial 34, synthetic NO, window 0x3600001,
root 0x116, subw 0x0, time 33376590, (160,51), root:(718,449),
state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 34, synthetic NO, window 0x3600001,
root 0x116, subw 0x0, time 33376598, (171,55), root:(729,453),
state 0x0, is_hint 0, same_screen YES
LeaveNotify event, serial 34, synthetic NO, window 0x3600001,
root 0x116, subw 0x0, time 33376606, (182,57), root:(740,455),
mode NotifyNormal, detail NotifyNonlinear, same_screen YES,
focus YES, state 0
ClientMessage event, serial 34, synthetic YES, window 0x3600001,
message_type 0x113 (WM_PROTOCOLS), format 32, message 0x111 (WM_DELETE_WINDOW)
Re: [NC10] Kernel 2.6.31
Posted: 21 Oct 2009, 19:46
Using the 2.6.31-14. Using my Huawei E169 USB Modem causes NetworkManager to crash. NM will not restart whilst the E169 modem is plugged in. Once removed NM will restart and networking is restored.
Using a stock Jaunty 2.6.28-15 generic kernel this does not happen.
I have used previous 2.6.31 kernels where this worked but I don't have them installed right now to tell you which one.
Is this a known problem? (Perhaps bug 446146?)
Using a stock Jaunty 2.6.28-15 generic kernel this does not happen.
I have used previous 2.6.31 kernels where this worked but I don't have them installed right now to tell you which one.
Is this a known problem? (Perhaps bug 446146?)
Re: [NC10] Kernel 2.6.31
Posted: 21 Oct 2009, 20:11
I have also tested a Huawei-Stick with German D1-Net, it runs well without problems with the "-14-generic"
Re: [NC10] Kernel 2.6.31
Posted: 22 Oct 2009, 10:58
I also have problems with the USB Modem using the same kernel on Karmic. However there the USB modem is just not recognised and the bug 446146 applies. NetworkManager does not crash.
Here I am on Jaunty using Voria's 2.6.31-14 kernel. Using the USB E169 modem here causes NetworkManager to crash and it will not restart until removed. Going back to the current Jaunty kernel (2.6.28-15) fixes the problem.
With this info, there must be something wrong in the 2.6.31 kernel that 1) does not allow the USB modem to work and 2) subsequently crashes NM.
Any advice on how to go about trying to identify the cause of the NM crash. This is what I see in the /var/log/syslog when starting NM with the USB stick in.
Oct 22 11:01:54 JMFTheVCI NetworkManager: <info> starting...
Oct 22 11:01:54 JMFTheVCI NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/pci_168c_1c_rfkill_phy0_wlan
Oct 22 11:01:54 JMFTheVCI NetworkManager: <info> (eth0): new Ethernet device (driver: 'sky2')
Oct 22 11:01:54 JMFTheVCI NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_13_77_d3_ec_b2
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (wlan0): new 802.11 WiFi device (driver: 'ath5k')
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_24_2b_1c_df_bb
Oct 22 11:01:55 JMFTheVCI NetworkManager: <WARN> libudev_get_modem_capabilities(): couldn't inspect device '/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/ttyUSB2/tty/ttyUSB2' with libudev
Oct 22 11:01:55 JMFTheVCI NetworkManager: <WARN> modem_device_creator(): (ttyUSB2): udev probing failed; using only HAL modem capabilities.
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (ttyUSB2): found serial port (udev:GSM hal:GSM)
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (ttyUSB2): new Modem device (driver: 'option')
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (ttyUSB2): exported as /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if0_serial_usb_2_26
Oct 22 11:01:55 JMFTheVCI NetworkManager: <WARN> libudev_get_modem_capabilities(): couldn't inspect device '/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1/ttyUSB1/tty/ttyUSB1' with libudev
Oct 22 11:01:55 JMFTheVCI NetworkManager: <WARN> modem_device_creator(): (ttyUSB1): udev probing failed; using only HAL modem capabilities.
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> libudev_get_modem_capabilities(): couldn't inspect device '/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1/ttyUSB1/tty/ttyUSB1' with libudev
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> modem_device_creator(): (ttyUSB1): udev probing failed; using only HAL modem capabilities.
Oct 22 11:01:56 JMFTheVCI NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> libudev_get_modem_capabilities(): couldn't inspect device '/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1/ttyUSB1/tty/ttyUSB1' with libudev
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> modem_device_creator(): (ttyUSB1): udev probing failed; using only HAL modem capabilities.
Oct 22 11:01:56 JMFTheVCI NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> libudev_get_modem_capabilities(): couldn't inspect device '/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1/ttyUSB1/tty/ttyUSB1' with libudev
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> modem_device_creator(): (ttyUSB1): udev probing failed; using only HAL modem capabilities.
Oct 22 11:01:56 JMFTheVCI NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
I also see the following HAL messages (chopped a few off!)
Oct 22 11:02:26 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if1_serial_usb_1_1
Oct 22 11:02:28 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if0_serial_usb_2_26
Oct 22 11:02:30 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Oct 22 11:02:30 JMFTheVCI kernel: [12720.413086] hald[3068]: segfault at 6c79 ip 0013b3f8 sp bfca6600 error 4 in libglib-2.0.so.0.2000.1[110000+b6000]
Here I am on Jaunty using Voria's 2.6.31-14 kernel. Using the USB E169 modem here causes NetworkManager to crash and it will not restart until removed. Going back to the current Jaunty kernel (2.6.28-15) fixes the problem.
With this info, there must be something wrong in the 2.6.31 kernel that 1) does not allow the USB modem to work and 2) subsequently crashes NM.
Any advice on how to go about trying to identify the cause of the NM crash. This is what I see in the /var/log/syslog when starting NM with the USB stick in.
Oct 22 11:01:54 JMFTheVCI NetworkManager: <info> starting...
Oct 22 11:01:54 JMFTheVCI NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/pci_168c_1c_rfkill_phy0_wlan
Oct 22 11:01:54 JMFTheVCI NetworkManager: <info> (eth0): new Ethernet device (driver: 'sky2')
Oct 22 11:01:54 JMFTheVCI NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_13_77_d3_ec_b2
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (wlan0): new 802.11 WiFi device (driver: 'ath5k')
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_24_2b_1c_df_bb
Oct 22 11:01:55 JMFTheVCI NetworkManager: <WARN> libudev_get_modem_capabilities(): couldn't inspect device '/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/ttyUSB2/tty/ttyUSB2' with libudev
Oct 22 11:01:55 JMFTheVCI NetworkManager: <WARN> modem_device_creator(): (ttyUSB2): udev probing failed; using only HAL modem capabilities.
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (ttyUSB2): found serial port (udev:GSM hal:GSM)
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (ttyUSB2): new Modem device (driver: 'option')
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (ttyUSB2): exported as /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if0_serial_usb_2_26
Oct 22 11:01:55 JMFTheVCI NetworkManager: <WARN> libudev_get_modem_capabilities(): couldn't inspect device '/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1/ttyUSB1/tty/ttyUSB1' with libudev
Oct 22 11:01:55 JMFTheVCI NetworkManager: <WARN> modem_device_creator(): (ttyUSB1): udev probing failed; using only HAL modem capabilities.
Oct 22 11:01:55 JMFTheVCI NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> libudev_get_modem_capabilities(): couldn't inspect device '/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1/ttyUSB1/tty/ttyUSB1' with libudev
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> modem_device_creator(): (ttyUSB1): udev probing failed; using only HAL modem capabilities.
Oct 22 11:01:56 JMFTheVCI NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> libudev_get_modem_capabilities(): couldn't inspect device '/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1/ttyUSB1/tty/ttyUSB1' with libudev
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> modem_device_creator(): (ttyUSB1): udev probing failed; using only HAL modem capabilities.
Oct 22 11:01:56 JMFTheVCI NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> libudev_get_modem_capabilities(): couldn't inspect device '/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1/ttyUSB1/tty/ttyUSB1' with libudev
Oct 22 11:01:56 JMFTheVCI NetworkManager: <WARN> modem_device_creator(): (ttyUSB1): udev probing failed; using only HAL modem capabilities.
Oct 22 11:01:56 JMFTheVCI NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
I also see the following HAL messages (chopped a few off!)
Oct 22 11:02:26 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if1_serial_usb_1_1
Oct 22 11:02:28 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if0_serial_usb_2_26
Oct 22 11:02:30 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Oct 22 11:02:30 JMFTheVCI kernel: [12720.413086] hald[3068]: segfault at 6c79 ip 0013b3f8 sp bfca6600 error 4 in libglib-2.0.so.0.2000.1[110000+b6000]
Re: [NC10] Kernel 2.6.31
Posted: 22 Oct 2009, 11:13
Code: Select all
/var/log/messages
Oct 22 12:02:57 hydra kernel: [170671.142570] usb 2-3: new high speed USB device using ehci_hcd and address 3
Oct 22 12:02:57 hydra kernel: [170671.301496] usb 2-3: configuration #1 chosen f
rom 1 choice
Oct 22 12:02:57 hydra kernel: [170671.383427] Initializing USB Mass Storage driver...
Oct 22 12:02:57 hydra kernel: [170671.384168] scsi6 : SCSI emulation for USB Mass Storage devices
Oct 22 12:02:57 hydra kernel: [170671.384997] usb 2-3: USB disconnect, address 3
Oct 22 12:02:57 hydra kernel: [170671.385494] usbcore: registered new interface driver usb-storage
Oct 22 12:02:57 hydra kernel: [170671.385500] USB Mass Storage support registered.
Oct 22 12:03:04 hydra kernel: [170678.710059] usb 2-3: new high speed USB device using ehci_hcd and address 4
Oct 22 12:03:04 hydra kernel: [170678.871615] usb 2-3: configuration #1 chosen from 1 choice
Oct 22 12:03:04 hydra kernel: [170678.881741] scsi9 : SCSI emulation for USB Mass Storage devices
Oct 22 12:03:04 hydra kernel: [170678.882732] scsi10 : SCSI emulation for USB Mass Storage devices
Oct 22 12:03:05 hydra kernel: [170679.022479] usbcore: registered new interface driver usbserial
Oct 22 12:03:05 hydra kernel: [170679.024142] USB Serial support registered for generic
Oct 22 12:03:05 hydra kernel: [170679.024225] usbcore: registered new interface driver usbserial_generic
Oct 22 12:03:05 hydra kernel: [170679.024228] usbserial: USB Serial Driver core
Oct 22 12:03:05 hydra kernel: [170679.057468] USB Serial support registered for GSM modem (1-port)
Oct 22 12:03:05 hydra kernel: [170679.057549] option 2-3:1.0: GSM modem (1-port) converter detected
Oct 22 12:03:05 hydra kernel: [170679.057688] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB0
Oct 22 12:03:05 hydra kernel: [170679.057705] option 2-3:1.1: GSM modem (1-port) converter detected
Oct 22 12:03:05 hydra kernel: [170679.057777] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB1
Oct 22 12:03:05 hydra kernel: [170679.057806] usbcore: registered new interface driver option
Oct 22 12:03:05 hydra kernel: [170679.057810] option: v0.7.2:USB Driver for GSM modems
Oct 22 12:03:09 hydra kernel: [170683.875884] scsi 9:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
Oct 22 12:03:09 hydra kernel: [170683.888343] scsi 10:0:0:0: Direct-Access HUAWEI MMC Storage 2.31 PQ: 0 ANSI: 2
Oct 22 12:03:09 hydra kernel: [170683.900393] sr1: scsi-1 drive
Oct 22 12:03:09 hydra kernel: [170683.900694] sr 9:0:0:0: Attached scsi generic sg2 type 5
Oct 22 12:03:09 hydra kernel: [170683.900837] sd 10:0:0:0: Attached scsi generic sg3 type 0
Oct 22 12:03:09 hydra kernel: [170683.930930] sd 10:0:0:0: [sdb] Attached SCSI removable disk
captain@hydra:~$ lsusb
Bus 002 Device 004: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E270 HSDPA/HSUPA Modem
syslog:
Oct 22 12:03:04 hydra kernel: [170678.710059] usb 2-3: new high speed USB device using ehci_hcd and address 4
Oct 22 12:03:04 hydra kernel: [170678.871615] usb 2-3: configuration #1 chosen from 1 choice
Oct 22 12:03:04 hydra kernel: [170678.881741] scsi9 : SCSI emulation for USB Mass Storage devices
Oct 22 12:03:04 hydra kernel: [170678.881936] usb-storage: device found at 4
Oct 22 12:03:04 hydra kernel: [170678.881939] usb-storage: waiting for device to settle before scanning
Oct 22 12:03:04 hydra kernel: [170678.882732] scsi10 : SCSI emulation for USB Mass Storage devices
Oct 22 12:03:04 hydra kernel: [170678.882894] usb-storage: device found at 4
Oct 22 12:03:04 hydra kernel: [170678.882897] usb-storage: waiting for device to settle before scanning
Oct 22 12:03:05 hydra kernel: [170679.022479] usbcore: registered new interface driver usbserial
Oct 22 12:03:05 hydra kernel: [170679.024142] USB Serial support registered for generic
Oct 22 12:03:05 hydra kernel: [170679.024225] usbcore: registered new interface driver usbserial_generic
Oct 22 12:03:05 hydra kernel: [170679.024228] usbserial: USB Serial Driver core
Oct 22 12:03:05 hydra kernel: [170679.057468] USB Serial support registered for GSM modem (1-port)
Oct 22 12:03:05 hydra kernel: [170679.057549] option 2-3:1.0: GSM modem (1-port) converter detected
Oct 22 12:03:05 hydra kernel: [170679.057688] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB0
Oct 22 12:03:05 hydra kernel: [170679.057705] option 2-3:1.1: GSM modem (1-port) converter detected
Oct 22 12:03:05 hydra kernel: [170679.057777] usb 2-3: GSM modem (1-port) converter now attached to ttyUSB1
Oct 22 12:03:05 hydra kernel: [170679.057806] usbcore: registered new interface driver option
Oct 22 12:03:05 hydra kernel: [170679.057810] option: v0.7.2:USB Driver for GSM modems
Oct 22 12:03:05 hydra NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Oct 22 12:03:05 hydra nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0, iface: (null)): iface not found
Oct 22 12:03:05 hydra NetworkManager: <info> (ttyUSB0): found serial port (udev:GSM hal:GSM)
Oct 22 12:03:05 hydra NetworkManager: <info> (ttyUSB0): new Modem device (driver: 'option')
Oct 22 12:03:05 hydra NetworkManager: <info> (ttyUSB0): exported as /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0
Oct 22 12:03:09 hydra kernel: [170683.873968] usb-storage: device scan complete
Oct 22 12:03:09 hydra kernel: [170683.875884] scsi 9:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
Oct 22 12:03:09 hydra kernel: [170683.885895] usb-storage: device scan complete
Oct 22 12:03:09 hydra kernel: [170683.888343] scsi 10:0:0:0: Direct-Access HUAWEI MMC Storage 2.31 PQ: 0 ANSI: 2
So I had found out, that I use an E220, you use an E169? May be thats the difference?
Re: [NC10] Kernel 2.6.31
Posted: 22 Oct 2009, 11:25
Code: Select all
lsusb
Bus 004 Device 008: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem
tail -50 syslog
Oct 22 11:25:24 JMFTheVCI kernel: [14094.246168] usb 4-1: GSM modem (1-port) converter now attached to ttyUSB1
Oct 22 11:25:24 JMFTheVCI kernel: [14094.246985] option 4-1:1.0: GSM modem (1-port) converter detected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.247406] usb 4-1: GSM modem (1-port) converter now attached to ttyUSB2
Oct 22 11:25:24 JMFTheVCI kernel: [14094.292755] option: option_instat_callback: error -108
Oct 22 11:25:24 JMFTheVCI kernel: [14094.294437] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Oct 22 11:25:24 JMFTheVCI kernel: [14094.294501] option 4-1:1.0: device disconnected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.294710] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Oct 22 11:25:24 JMFTheVCI kernel: [14094.294767] option 4-1:1.1: device disconnected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.294962] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Oct 22 11:25:24 JMFTheVCI kernel: [14094.295018] option 4-1:1.2: device disconnected
Oct 22 11:25:24 JMFTheVCI nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if0_serial_usb_2_35, iface: (null)): iface not found
Oct 22 11:25:24 JMFTheVCI nm-system-settings: SCPlugin-Ifupdown: devices removed (udi: /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if0_serial_usb_2_35)
Oct 22 11:25:24 JMFTheVCI kernel: [14094.404530] usb 4-1: reset full speed USB device using uhci_hcd and address 8
Oct 22 11:25:24 JMFTheVCI kernel: [14094.560201] option 4-1:1.2: GSM modem (1-port) converter detected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.560448] usb 4-1: GSM modem (1-port) converter now attached to ttyUSB0
Oct 22 11:25:24 JMFTheVCI kernel: [14094.561499] option 4-1:1.1: GSM modem (1-port) converter detected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.561741] usb 4-1: GSM modem (1-port) converter now attached to ttyUSB1
Oct 22 11:25:24 JMFTheVCI kernel: [14094.572332] option 4-1:1.0: GSM modem (1-port) converter detected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.572595] usb 4-1: GSM modem (1-port) converter now attached to ttyUSB2
Oct 22 11:25:24 JMFTheVCI usb_id[5915]: unable to access '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1/ttyUSB1/tty/ttyUSB1'
Oct 22 11:25:24 JMFTheVCI usb_id[5917]: unable to access '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.2/ttyUSB0/tty/ttyUSB0'
Oct 22 11:25:24 JMFTheVCI kernel: [14094.596745] option: option_instat_callback: error -108
Oct 22 11:25:24 JMFTheVCI kernel: [14094.597266] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Oct 22 11:25:24 JMFTheVCI kernel: [14094.597330] option 4-1:1.0: device disconnected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.597539] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Oct 22 11:25:24 JMFTheVCI kernel: [14094.597593] option 4-1:1.1: device disconnected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.597788] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Oct 22 11:25:24 JMFTheVCI kernel: [14094.597852] option 4-1:1.2: device disconnected
Oct 22 11:25:24 JMFTheVCI usb_id[5914]: unable to access '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/ttyUSB2/tty/ttyUSB2'
Oct 22 11:25:24 JMFTheVCI kernel: [14094.712698] usb 4-1: reset full speed USB device using uhci_hcd and address 8
Oct 22 11:25:24 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if2_serial_usb_0
Oct 22 11:25:24 JMFTheVCI kernel: [14094.868196] option 4-1:1.2: GSM modem (1-port) converter detected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.868391] usb 4-1: GSM modem (1-port) converter now attached to ttyUSB0
Oct 22 11:25:24 JMFTheVCI kernel: [14094.868604] option 4-1:1.1: GSM modem (1-port) converter detected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.868812] usb 4-1: GSM modem (1-port) converter now attached to ttyUSB1
Oct 22 11:25:24 JMFTheVCI kernel: [14094.871536] option 4-1:1.0: GSM modem (1-port) converter detected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.871874] usb 4-1: GSM modem (1-port) converter now attached to ttyUSB2
Oct 22 11:25:24 JMFTheVCI kernel: [14094.883733] option: option_instat_callback: error -108
Oct 22 11:25:24 JMFTheVCI usb_id[5949]: unable to access '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1/ttyUSB1/tty/ttyUSB1'
Oct 22 11:25:24 JMFTheVCI usb_id[5951]: unable to access '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/ttyUSB2/tty/ttyUSB2'
Oct 22 11:25:24 JMFTheVCI kernel: [14094.885265] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Oct 22 11:25:24 JMFTheVCI kernel: [14094.885332] option 4-1:1.0: device disconnected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.885546] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Oct 22 11:25:24 JMFTheVCI kernel: [14094.885604] option 4-1:1.1: device disconnected
Oct 22 11:25:24 JMFTheVCI kernel: [14094.885784] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Oct 22 11:25:24 JMFTheVCI kernel: [14094.885838] option 4-1:1.2: device disconnected
Oct 22 11:25:24 JMFTheVCI usb_id[5957]: unable to access '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.2/ttyUSB0/tty/ttyUSB0'
Oct 22 11:25:24 JMFTheVCI kernel: [14095.000579] usb 4-1: reset full speed USB device using uhci_hcd and address 8
Oct 22 11:25:24 JMFTheVCI nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if0_serial_usb_2_35, iface: (null)): iface not found
Oct 22 11:25:24 JMFTheVCI nm-system-settings: SCPlugin-Ifupdown: devices removed (udi: /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if0_serial_usb_2_35)
Code: Select all
cat syslog | grep hal
Oct 22 11:30:19 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if1_serial_usb_1_0
Oct 22 11:30:23 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if1_serial_usb_1_0
Oct 22 11:30:23 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if1_serial_usb_1_0
Oct 22 11:30:24 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if2_serial_usb_0
Oct 22 11:30:25 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_12d1_1001________________________________________if1_serial_usb_1_0
Oct 22 11:30:26 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Oct 22 11:30:26 JMFTheVCI pulseaudio[3850]: module-hal-detect.c: D-Bus error while parsing HAL data: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Hal was not provided by any .service files
Oct 22 11:30:26 JMFTheVCI kernel: [14396.266540] hald[9033]: segfault at 73 ip 00491ca1 sp bff14460 error 4 in libgobject-2.0.so.0.2000.1[485000+3c000]
Re: [NC10] Kernel 2.6.31
Posted: 22 Oct 2009, 14:37
This seems to be a problem:
Probably a pci device mapping error, but I'm not an expert
Code: Select all
Oct 22 11:25:24 JMFTheVCI kernel: [14094.596745] option: option_instat_callback: error -108
Oct 22 11:25:24 JMFTheVCI usb_id[5917]: unable to access '/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.2/ttyUSB0/tty/ttyUSB0'
Re: [NC10] Kernel 2.6.31
Posted: 22 Oct 2009, 17:17
Re: [NC10] Kernel 2.6.31
Posted: 23 Oct 2009, 09:02
That is a useful post but it does not resolve my problem.
My USB modem is being correctly picked up. Yes, it is seen as usb-storage initially and using the commands listed in that link do help. However NetworkManager is still dead.
Remember that my USB modem works perfectly with the Jaunty 2.6.28 kernel. The USB stick is recognised and works first time with NetworkManager.
I suppose I will just have to wait until they fix the issue in the Karmic kernel (2.6.31-whatever) and then hopefully Voria will publish that kernel for Jaunty.
[Personally I would like to see Jaunty supported for a while longer as Voria, who is providing such a useful service to the NC10 community, is thinking of dropping all support except for Karmic once it is GA. I think that Karmic has too many open bugs at present whereas, for me, Jaunty is very stable.]
My USB modem is being correctly picked up. Yes, it is seen as usb-storage initially and using the commands listed in that link do help. However NetworkManager is still dead.
Remember that my USB modem works perfectly with the Jaunty 2.6.28 kernel. The USB stick is recognised and works first time with NetworkManager.
I suppose I will just have to wait until they fix the issue in the Karmic kernel (2.6.31-whatever) and then hopefully Voria will publish that kernel for Jaunty.
[Personally I would like to see Jaunty supported for a while longer as Voria, who is providing such a useful service to the NC10 community, is thinking of dropping all support except for Karmic once it is GA. I think that Karmic has too many open bugs at present whereas, for me, Jaunty is very stable.]