[Bug 53923] Re: tifm: Texas Instruments Card reader not working
You should remove the logging. It's enough you found the files and made an easy script by collecting the backup and copying commands into one script. In install script there are some tabs/spaces i noticed. For example ... /usr /`uname -r` /kernel/etc etc etc I did not run the script as was, i deleted them first. In host.h you added some things and deleted others (probably obsolete). Well thanks a lot again... -- tifm: Texas Instruments Card reader not working https://bugs.launchpad.net/bugs/53923 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53923] Re: tifm: Texas Instruments Card reader not working
Thanks a lot. It works great. I don't know if the lines you removed in the code files will have any effect. The were some "timing" variables etc etc... My sony memory stick does not work but i think there is no support for it yet. Another thing. In my /lib/modules/2.6.20-15-generic/kernel/drivers/mmc there was no tifm_sd.ko. Maybe it's in all Feisty systems, maybe only on mine... Indeed the log file when a command fails the entry is: something backed up to somethingelse which is misleading. (ex: In my case there was no file to move to file-old) -- tifm: Texas Instruments Card reader not working https://bugs.launchpad.net/bugs/53923 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53923] Re: tifm: Texas Instruments Card reader not working
yes i have a Texas instruments card reader. The output of lspci [-nnv] is not exactly the same but it is Texas Instruments... Thanks so much for your help. I hope this works. I will then have fixed nearly all my bugs and will be able to never use windows again! What are those 40MB you mentioned? Aren't the files you posted source files? and we have to compile them and put them in the right places? (your script does that exactly. I had the chance to read the contents before i went to my office) PS: I would be very grateful if you have any idea as to how can i use bluepin instead of bluez-pin to pair my bluetooth devices (i can't find the file on my system so as to use it in some configuration file...) Sorry for the irrelevant subject -- tifm: Texas Instruments Card reader not working https://bugs.launchpad.net/bugs/53923 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53923] Re: tifm: Texas Instruments Card reader not working
maco do you know if this will work for me? I am new to linux. Just two months time and i just ugraded edgy to feisty. My card reader does not work. I can see in dmesg that my memory stick has been detected. I believe that an sd card ican be detected too but i don't see them on my desktop (so i believe they are not mounted correctly). I can see in your readme that thiese modules are of a newer version than the ones in feisty... Why is that there are no updates in update manager, if this is a newer version and it works? I suppose it needs testing...First of all how can i see which version is installed on my feisty? Thanks a lot in advance. -- tifm: Texas Instruments Card reader not working https://bugs.launchpad.net/bugs/53923 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53923] Re: tifm: Texas Instruments Card reader not working
No actually i downloaded it and it extracted. I dpn't know if you mean if it works or not, i haven't tried it yet. I will, when i get home like DaveQB. I keep my fingers crossed till then! -- tifm: Texas Instruments Card reader not working https://bugs.launchpad.net/bugs/53923 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82680] Re: [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy)
*** This bug is a duplicate of bug 53923 *** https://bugs.launchpad.net/bugs/53923 when i insert my sony memory stick duo pro (i have no idea if it is supported - i use kernel 2.6.20.15), in dmesg i can see this line: [ 8551.388000] tifm_7xx1: ms card detected in socket 2 When i remove the stick another entry appears: [ 8555.924000] tifm_7xx1: demand removing card from socket 2 in my /var/log/syslog i can see these lines and a lot more similar (with differences in sector numbers): Apr 21 18:06:08 FerrariUbuntu kernel: [14696.256000] mmcblk0: error 1 sending read/write command Apr 21 18:06:08 FerrariUbuntu kernel: [14696.256000] end_request: I/O error, dev mmcblk0, sector 105 Apr 21 18:06:08 FerrariUbuntu kernel: [14696.256000] mmcblk0: error 1 sending read/write command Apr 21 18:06:08 FerrariUbuntu kernel: [14696.256000] end_request: I/O error, dev mmcblk0, sector 106 Apr 21 18:06:08 FerrariUbuntu kernel: [14696.256000] mmcblk0: error 1 sending read/write command Apr 21 18:06:08 FerrariUbuntu kernel: [14696.256000] end_request: I/O error, dev mmcblk0, sector 16 Apr 21 18:06:08 FerrariUbuntu kernel: [14696.256000] mmcblk0: error 1 sending read/write command Apr 21 18:06:08 FerrariUbuntu kernel: [14696.256000] end_request: I/O error, dev mmcblk0, sector 24 Apr 21 18:06:08 FerrariUbuntu kernel: [14696.256000] mmcblk0: error 1 sending read/write command Apr 21 18:06:08 FerrariUbuntu kernel: [14696.256000] end_request: I/O error, dev mmcblk0, sector 0 Apr 21 18:06:08 FerrariUbuntu NetworkManager: ^I[1177167968.825884] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/devices/pci_104c_8033_mmc_host_mmc_card_rca40401'). Apr 21 18:06:08 FerrariUbuntu NetworkManager: ^I[1177167968.834043] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/devices/pci_104c_8033_mmc_host'). Apr 21 18:06:08 FerrariUbuntu NetworkManager: ^I[1177167968.834947] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/devices/pci_104c_8033_mmc_host_mmc_card_rca40401_storage'). I have added these lines to /etc/modules: #card reader tifm_core tifm_7xx1 tifm_sd mmc_core mmc_block sdhci (sudo lspci -nnv): 06:09.3 Mass storage controller [0180]: Texas Instruments PCIxx21 Integrated FlashMedia Controller [104c:8033] Subsystem: Acer Incorporated [ALI] Unknown device [1025:007e] Flags: bus master, medium devsel, latency 64, IRQ 16 Memory at c0306000 (32-bit, non-prefetchable) [size=8K] Capabilities: [44] Power Management version 2 and in my laptop this makes the insert/remove events not to show on dmesg sudo setpci -s 06:09.3 4c.b=0x22 while sudo setpci -s 06:09.3 4c.b=0x02 does nothing in particular... What can i do now? I upgraded to feisty two days ago. In Edgy my card reader did not work out of the box but i did not try to fix it. Now i am only a few steps away from completely abandoning Win XP and i want so much to just fix everything and get rid of them... -- [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy) https://bugs.launchpad.net/bugs/82680 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76329] Re: beryl-manager crashes.something wrong with xserver-xgl and direct rendering. ATI X700 Mobility (R420) AMD64 kernel 386
** Attachment added: "beryl-manager crash file" http://librarian.launchpad.net/5445456/_usr_bin_beryl-manager.1000.crash -- beryl-manager crashes.something wrong with xserver-xgl and direct rendering. ATI X700 Mobility (R420) AMD64 kernel 386 https://launchpad.net/bugs/76329 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76329] beryl-manager crashes.something wrong with xserver-xgl and direct rendering. ATI X700 Mobility (R420) AMD64 kernel 386
Public bug reported: Binary package hint: xserver-xgl [EMAIL PROTECTED]:~$ cat /var/log/Xorg.0.log | grep fglrx (II) LoadModule: "fglrx" (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so (II) Module fglrx: vendor="FireGL - ATI Technologies Inc." (II) fglrx(0): pEnt->device->identifier=0x81e1930 (II) fglrx(0): === [R200PreInit] === begin, [s] (II) fglrx(0): PCI bus 1 card 0 func 0 (**) fglrx(0): Depth 24, (--) framebuffer bpp 32 (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) (==) fglrx(0): Default visual is TrueColor (**) fglrx(0): Option "dri" "true" (**) fglrx(0): Option "MonitorLayout" "LVDS,CRT" (**) fglrx(0): Option "DPMS" (==) fglrx(0): RGB weight 888 (II) fglrx(0): Using 8 bits per RGB (8 bit DAC) (==) fglrx(0): Gamma Correction for I is 0x06419064 (==) fglrx(0): Gamma Correction for II is 0x06419064 (==) fglrx(0): Buffer Tiling is ON (II) fglrx(0): Primary V_BIOS segment is: 0xc000 (--) fglrx(0): Chipset: "MOBILITY RADEON X700 (M26 5653)" (Chipset = 0x5653) (--) fglrx(0): (PciSubVendor = 0x1025, PciSubDevice = 0x007e) (--) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI (--) fglrx(0): Linear framebuffer (phys) at 0xc800 (--) fglrx(0): MMIO registers at 0xc010 (==) fglrx(0): ROM-BIOS at 0x000c (II) fglrx(0): VESA BIOS detected (II) fglrx(0): VESA VBE Version 3.0 (II) fglrx(0): VESA VBE Total Mem: 16384 kB (II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS (II) fglrx(0): VESA VBE OEM Software Rev: 9.10 (II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc. (II) fglrx(0): VESA VBE OEM Product: M26-P (II) fglrx(0): VESA VBE OEM Product Rev: 01.00 (II) Loading sub module "fglrxdrm" (II) LoadModule: "fglrxdrm" (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc." (II) fglrx(0): ATI Video BIOS revision 9 or later detected (--) fglrx(0): VideoRAM: 131072 kByte, Type: DDR1 (II) fglrx(0): PCIE card detected (WW) fglrx(0): board is an unknown third party board, chipset is supported (WW) fglrx(0): MonitorLayout is no longer supported. (II) fglrx(0): Connected Display1: LCD on internal LVDS (II) fglrx(0): Display1 EDID data --- (II) fglrx(0): Manufacturer: SEC Model: 0 Serial#: 0 (II) fglrx(0): Year: 2003 Week: 0 (II) fglrx(0): EDID Version: 1.3 (II) fglrx(0): Digital Display Input (II) fglrx(0): Max H-Image Size [cm]: horiz.: 33 vert.: 21 (II) fglrx(0): Gamma: 2.20 (II) fglrx(0): No DPMS capabilities specified; RGB/Color Display (II) fglrx(0): First detailed timing is preferred mode (II) fglrx(0): redX: 0.580 redY: 0.340 greenX: 0.310 greenY: 0.550 (II) fglrx(0): blueX: 0.155 blueY: 0.155 whiteX: 0.313 whiteY: 0.329 (II) fglrx(0): Manufacturer's mask: 0 (II) fglrx(0): Supported additional Video Mode: (II) fglrx(0): clock: 121.0 MHz Image Size: 331 x 207 mm (II) fglrx(0): h_active: 1680 h_sync: 1704 h_sync_end 1792 h_blank_end 1876 h_border: 0 (II) fglrx(0): v_active: 1050 v_sync: 1051 v_sync_end 1054 v_blanking: 1065 v_border: 0 (II) fglrx(0): SAMSUNG (II) fglrx(0): LTN154P1-L02 (II) fglrx(0): End of Display1 EDID data (II) fglrx(0): Primary Controller - LCD on internal LVDS (II) fglrx(0): Internal Desktop Setting: 0x0008 (II) fglrx(0): POWERplay version 3. 3 power states available: (II) fglrx(0): 1. 358/331MHz @ 60Hz [enable load balancing] (II) fglrx(0): 2. 105/120MHz @ 60Hz [low voltage, enable sleep] (II) fglrx(0): 3. 209/182MHz @ 60Hz [low voltage, enable sleep] (==) fglrx(0): Qbs disabled (==) fglrx(0): FAST_SWAP disabled (==) fglrx(0): PseudoColor visuals disabled (==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0) (==) fglrx(0): Center Mode is disabled (==) fglrx(0): TMDS coherent mode is enabled (II) fglrx(0): Total of 15 modes found for primary display. (--) fglrx(0): Virtual size is 1680x1050 (pitch 0) (**) fglrx(0): *Mode "1680x1050": 121.0 MHz (scaled from 0.0 MHz), 64.5 kHz, 60.0 Hz (II) fglrx(0): Modeline "1680x1050" 121.00 1680 1704 1792 1876 1050 1051 1054 1065 +hsync +vsync (**) fglrx(0): Default mode "1280x1024": 121.0 MHz (scaled from 0.0 MHz), 64.5 kHz, 60.0 Hz (II) fglrx(0): Modeline "1280x1024" 121.00 1280 1304 1392 1876 1024 1051 1054 1065 +hsync +vsync (**) fglrx(0): Default mode "1152x864": 121.0 MHz (scaled from 0.0 MHz), 64.5 kHz, 60.0 Hz (II) fglrx(0): Modeline "1152x864" 121.00 1152 1176 1264 1876 864 1051 1054 1065 +hsync +vsync (**) fglrx(0): Default mode "1024x768": 121.0 MHz (scaled from 0.0 MHz), 64.5 kHz, 60.0 Hz (II) fglrx(0): Modeline "1024x768" 121.00 1024 1048 1136 1876 768 1051 1054 1065 +hsync +vsync (**) fglrx(0): Default mode "1024x480": 121.0 MHz (scaled from 0.0 MHz), 64.5 kHz, 60.0 Hz (II) fglrx(0): Modeline "1024x480" 121.00 1024 1048 1136 1876 480 1051 1054 1065 +hsync +vsync (**) fglrx(0): Default mode "848x480": 121.0 MHz (scaled from 0.0 MHz), 64.5 kHz, 60.0 Hz (II) fglrx(0): Modeline "848x480" 121.00
