[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Then I'm puzzled. I'll retest later with WD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
My Samsung is indeed [144d:a808]. I'll check WD later on - it's not connected at this time. I was not able to reproduce this bug using Clear Linux current kernel (4.18.16-645). I checked kernel https://people.canonical.com/~khfeng/lp1785715/ with no nvme-core.default_ps_max_latency_us= settings and I was not able to reproduce the issue with my "copy lots of data" scenario that triggered the bug every time yesterday. So it looks like success! I'll keep using that kernel for now and report if any problems arise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
My Samsung is indeed [144d:a808]. I'll check WD later on - it's not connected at this time. I was not able to reproduce this bug using Clear Linux current kernel (4.18.16-645). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Attachment contains error from dmesg output. For me reproduction steps are: write large (>10G) amount of data to NVMe ssd. ** Attachment added: "nvme-heavy-write-error.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5204874/+files/nvme-heavy-write-error.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696422] Re: Sudden Read Only File System
The same problem appears for me with 4.18.0-10-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696422 Title: Sudden Read Only File System To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I can confirm that bug with two different NVMe drivers - Samsung EVO970 and WD Black in 4.18.0-10-generic and in 4.15.0-20-generic kernels. H270 Intel chipset on the motherboard -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122494] Re: pinnacle pctv 110i remote does not work in feisty
It does not work in gutsy either -- pinnacle pctv 110i remote does not work in feisty https://bugs.launchpad.net/bugs/122494 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 189574] Re: totem-gstreamer crashed with SIGSEGV in g_object_set_valist()
I think I encountered something similar -- totem-gstreamer crashed with SIGSEGV in g_object_set_valist() https://bugs.launchpad.net/bugs/189574 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86798] Re: r8169 driver does not detect link
That problem is fixed in Gutsy, so I think it can be closed -- r8169 driver does not detect link https://bugs.launchpad.net/bugs/86798 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 132238] Re: Dolphin crash
I have a way of reproducing dolphin crash in Beta 2 1. open dolphin choose view->decrease several times in my system this produces crash repeatedly (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1234409792 (LWP 9638)] [KCrash handler] #6 0xb7155e50 in QIconView::calcGridNum () from /usr/lib/libqt-mt.so.3 #7 0xb7158c68 in QIconView::makeRowLayout () from /usr/lib/libqt-mt.so.3 #8 0xb715c3f8 in QIconView::arrangeItemsInGrid () from /usr/lib/libqt-mt.so.3 #9 0xb7cd8f67 in KFileIconView::arrangeItemsInGrid () from /usr/lib/libkio.so.4 #10 0x080808cc in ?? () #11 0x082ab388 in ?? () #12 0x0001 in ?? () #13 0x0075 in ?? () #14 0xb6f99530 in QTimer::stop () from /usr/lib/libqt-mt.so.3 #15 0xb7156121 in QIconView::adjustItems () from /usr/lib/libqt-mt.so.3 #16 0xb715be5e in QIconView::resizeEvent () from /usr/lib/libqt-mt.so.3 #17 0xb6fa8ab9 in QWidget::event () from /usr/lib/libqt-mt.so.3 #18 0xb6f08af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #19 0xb6f0b4ba in QApplication::notify () from /usr/lib/libqt-mt.so.3 #20 0xb76b5212 in KApplication::notify () from /usr/lib/libkdecore.so.4 #21 0xb6e9b209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #22 0xb6f09b28 in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3 #23 0xb6faae5f in QWidget::show () from /usr/lib/libqt-mt.so.3 #24 0xb70ab4a2 in QScrollView::show () from /usr/lib/libqt-mt.so.3 #25 0xb6fa7cbf in QWidget::showChildren () from /usr/lib/libqt-mt.so.3 #26 0xb6fab0f0 in QWidget::show () from /usr/lib/libqt-mt.so.3 #27 0x0806eb5e in ?? () #28 0x08285d38 in ?? () #29 0x082aadb8 in ?? () #30 0x in ?? () -- Dolphin crash https://bugs.launchpad.net/bugs/132238 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 80645] Re: vmware tools install fails
As vmware open-sourced vmware-tools we can close this bug. -- vmware tools install fails https://bugs.launchpad.net/bugs/80645 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 127529] Re: nv driver - widescreen not recoginzed Asus A8Jn
I checked today with Tribe-5. It work's flawlessly! Thank you!. ** Changed in: xorg (Ubuntu) Status: Incomplete => Fix Released -- nv driver - widescreen not recoginzed Asus A8Jn https://bugs.launchpad.net/bugs/127529 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 127529] Re: nv driver - widescreen not recoginzed Asus A8Jn
I'll try with tribe-5 tomorrow. -- nv driver - widescreen not recoginzed Asus A8Jn https://bugs.launchpad.net/bugs/127529 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 127529] Re: nv driver - widescreen not recoginzed Asus A8Jn
O course adding "1280x800" in xorg.conf is a work around, but it does not a valid bug solution. Screen resolution should be determined at live-cd startup and should not require manual xorg.conf editing. -- nv driver - widescreen not recoginzed Asus A8Jn https://bugs.launchpad.net/bugs/127529 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 127529] Re: nv driver - widescreen not recoginzed Asus A8Jn
it is a typical laptop 1280x800 screen. in Xorg.0.log it is recognized properly: (--) NV(0): Panel size is 1280 x 800 (II) NV(0): Panel is LVDS but somehow that information is ignored afterwards -- nv driver - widescreen not recoginzed Asus A8Jn https://bugs.launchpad.net/bugs/127529 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 127529] Re: nv driver - widescreen not recoginzed Asus A8Jn
I also notice very high cpu usage during basic operations like moving windows - top shows 60-70% cpu utilization -- nv driver - widescreen not recoginzed Asus A8Jn https://bugs.launchpad.net/bugs/127529 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 127529] Re: nv driver - widescreen not recoginzed Asus A8Jn
** Attachment added: "xorg.conf" http://launchpadlibrarian.net/8545412/xorg.conf -- nv driver - widescreen not recoginzed Asus A8Jn https://bugs.launchpad.net/bugs/127529 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 127529] Re: nv driver - widescreen not recoginzed Asus A8Jn
** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/8545414/Xorg.0.log -- nv driver - widescreen not recoginzed Asus A8Jn https://bugs.launchpad.net/bugs/127529 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 127526] Re: Intel 3945 wireless card not detected on Asus A9Js
Please close that report. False alarm. At the second boot card is detected. Maybe It was just accident at the first time. I wonder why it didn't for for the first time. -- Intel 3945 wireless card not detected on Asus A9Js https://bugs.launchpad.net/bugs/127526 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 127529] nv driver - widescreen not recoginzed Asus A8Jn
Public bug reported: Binary package hint: xorg Gutsy - tribe 3 Widescreen screen is not recognized after cd-boot. I am left with 1024x768 max resolution, and there is no way to change it. Asus A8Js - Nvidia 7300 and 1280x800 screen. It never worked in Ubuntu, so probably won't work now either ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- nv driver - widescreen not recoginzed Asus A8Jn https://bugs.launchpad.net/bugs/127529 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 124590] No sound card in Gutsy with Asus A8Js too
The same situation with my Asus A8Js - no sound card detected in gutsy -- No sound card in Gutsy with D630 https://bugs.launchpad.net/bugs/124590 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 127526] Intel 3945 wireless card not detected on Asus A9Js
Public bug reported: (gusty - tribe 3) As in summary, wireless card is not detected. Driver is not loaded. ifconfig and iwconfig shows nothing It worked fine in 6.10 and 7.04 ** Affects: Ubuntu Importance: Undecided Status: New -- Intel 3945 wireless card not detected on Asus A9Js https://bugs.launchpad.net/bugs/127526 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 122494] pinnacle pctv 110i remote does not work in feisty
Public bug reported: feisty with all recent updates. TV card pinnacle 110i (saa7134 module, card=77) remote detected by kernel dmesg: 41.065255] saa7130/34: v4l2 driver version 0.2.14 loaded [ 41.065844] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16 [ 41.065856] ACPI: PCI Interrupt :04:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 21 [ 41.065864] saa7133[0]: found at :04:08.0, rev: 209, irq: 21, latency: 32, mmio: 0xfdbfe000 [ 41.065870] saa7133[0]: subsystem: 11bd:002e, board: Pinnacle PCTV 40i/50i/110i (saa7133) [card=77,insmod option] [ 41.065880] saa7133[0]: board init: gpio is 200e000 41.178669] input: Pinnacle PCTV as /class/input/input6 [ 41.178700] ir-kbd-i2c: Pinnacle PCTV detected at i2c-2/2-0047/ir0 [saa7133[0]] [ 41.218532] saa7133[0]: i2c eeprom 00: bd 11 2e 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 [ 41.218540] saa7133[0]: i2c eeprom 10: ff e0 60 02 ff 20 ff ff ff ff ff ff ff ff ff ff [ 41.218546] saa7133[0]: i2c eeprom 20: 01 2c 01 23 23 01 04 30 98 ff 00 e2 ff 22 00 c2 [ 41.218553] saa7133[0]: i2c eeprom 30: 96 ff 03 30 15 01 ff 15 0e 6c a3 ea 03 c4 6e 26 [ 41.218559] saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 41.218565] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 41.218571] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 41.218577] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 41.390591] tuner 2-004b: chip found @ 0x96 (saa7133[0]) [ 41.442578] tuner 2-004b: setting tuner address to 61 [ 41.482584] tuner 2-004b: type set to tda8290+75a [ 41.765592] input: ImPS/2 Generic Wheel Mouse as /class/input/input7 [ 42.946887] tuner 2-004b: setting tuner address to 61 [ 42.994895] tuner 2-004b: type set to tda8290+75a [ 44.341590] saa7133[0]: registered device video0 [v4l2] [ 44.341701] saa7133[0]: registered device vbi0 [ 44.341813] saa7133[0]: registered device radio0 [ 44.427788] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22 [ 44.427793] ACPI: PCI Interrupt :00:10.1[B] -> Link [AAZA] -> GSI 22 (level, low) -> IRQ 17 [ 44.427816] PCI: Setting latency timer of device :00:10.1 to 64 [ 44.452443] saa7134 ALSA driver for DMA sound loaded [ 44.452470] saa7133[0]/alsa: saa7133[0] at 0xfdbfe000 irq 21 registered as card -2 lsinput: /dev/input/event4 bustype : BUS_I2C vendor : 0x0 product : 0x0 version : 0 name: "Pinnacle PCTV" phys: "i2c-2/2-0047/ir0" bits ev : EV_SYN EV_KEY EV_REP [EMAIL PROTECTED]:~$ uname -a Linux myszka 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux no events are generated from the remote ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: New -- pinnacle pctv 110i remote does not work in feisty https://bugs.launchpad.net/bugs/122494 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 86798] Re: r8169 driver does not detect link
I have checked today with Linux ali 2.6.20-15-generic (linux- image-2.6.20-15-generic_2.6.20-15.27) and the bug is still present -- r8169 driver does not detect link https://bugs.launchpad.net/bugs/86798 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 97540] Re: [apport] beryl crashed with SIGSEGV in KIPC::sendMessageAll()
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/7037173/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7037174/Dependencies.txt ** Attachment added: "Disassembly.txt" http://librarian.launchpad.net/7037175/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7037176/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7037177/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/7037178/Registers.txt ** Attachment added: "Stacktrace.txt" http://librarian.launchpad.net/7037179/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/7037180/ThreadStacktrace.txt -- [apport] beryl crashed with SIGSEGV in KIPC::sendMessageAll() https://launchpad.net/bugs/97540 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97540] [apport] beryl crashed with SIGSEGV in KIPC::sendMessageAll()
Public bug reported: Binary package hint: beryl-core Beryl with aquamarine as for 27.03 ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Tue Mar 27 21:33:52 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/beryl Package: beryl-core 0.2.1.dfsg+git20070318-0ubuntu2 PackageArchitecture: i386 ProcCmdline: beryl --skip-gl-yield ProcCwd: /home/mar ProcEnviron: PATH=/home/mar/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: beryl-core StacktraceTop: KIPC::sendMessageAll () from /usr/lib/libkdecore.so.4 write_done () from /usr/lib/beryl/backends/libkconfig.so beryl_settings_context_write () ?? () ?? () Uname: Linux ali 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video ** Affects: beryl-core (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] beryl crashed with SIGSEGV in KIPC::sendMessageAll() https://launchpad.net/bugs/97540 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93241] Re: Fan not activated on recover from hibernate
I can confirm this behaviour with Asus A8Jn laptop and kernel 2.6.20-11. I'll post required information later. -- Fan not activated on recover from hibernate https://launchpad.net/bugs/93241 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94089] Re: knetworkmanager crashes on login
I confirm. Knetwork manager almost always crashes at first login. On subsequent logins it works though. -- knetworkmanager crashes on login https://launchpad.net/bugs/94089 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 86798] Re: r8169 driver does not detect link
ethtool: before connecting cable:Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 10Mb/s Duplex: Half Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0033 (51) Link detected: no after connecting cable: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 10Mb/s Duplex: Half Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0033 (51) Link detected: no after reloading driver: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0033 (51) Link detected: yes -- r8169 driver does not detect link https://launchpad.net/bugs/86798 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86798] r8169 driver does not detect link
Public bug reported: Binary package hint: linux-source-2.6.20 You need system with r8169 card (Realtek Gigabit card) 1. start system with ethernet cable _disconnected_ 2. connect ethernet cable - system says no link detected - not true To overcome this you have to 1) unload driver - rmmod r8169 2) load the driver again - modprobe r8169 after that opreations driver sees link important pieces from dmesg: loading driver [4.184000] r8169 Gigabit Ethernet driver 2.2LK loaded [4.184000] ACPI: PCI Interrupt :03:00.0[A] -> GSI 18 (level, low) -> IRQ 17 [4.184000] PCI: Setting latency timer of device :03:00.0 to 64 [4.184000] eth0: RTL8168b/8111b at 0xf88b8000, 00:18:f3:ee:2f:2a, IRQ 17 init driver (ethernet disconnected) [ 16.372000] r8169: eth0: link down [ 17.252000] NET: Registered protocol family 10 [ 17.252000] lo: Disabled Privacy Extensions [ 17.252000] ADDRCONF(NETDEV_UP): eth0: link is not ready at this point ethtool says that there is no link detected (machine at the other side of the cable says otherwise) unloading driver: [ 5641.472000] ACPI: PCI interrupt for device :03:00.0 disabled and loading it again: 5644.756000] r8169 Gigabit Ethernet driver 2.2LK loaded [ 5644.756000] ACPI: PCI Interrupt :03:00.0[A] -> GSI 18 (level, low) -> IRQ 17 [ 5644.756000] PCI: Setting latency timer of device :03:00.0 to 64 [ 5644.756000] eth0: RTL8168b/8111b at 0xf8d42000, 00:18:f3:ee:2f:2a, IRQ 17 [ 5644.804000] r8169: eth0: link down [ 5644.804000] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 5646.38] r8169: eth0: link up [ 5646.38] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 5656.756000] eth0: no IPv6 routers present and now link is properly detected important lspci -vvnn piece 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01) Subsystem: ASUSTeK Computer Inc. Unknown device [1043:11f5] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://launchpad.net/bugs/86798 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85407] Re: asus_acpi in old version, does not support notebooks
I attached required information.
My architecture is ubuntu-x86
Essential information:
in dmesg:
[ 76.976000] Asus Laptop ACPI Extras version 0.30
[ 76.976000] unsupported model A8JN, trying default values
[ 76.976000] send /proc/acpi/dsdt to the developers
I checked in acpi4asus.sf.net - there is version 0.32 available. I
compiled it and inserted. The newer version recognizes my notebook
properly.
There can be one problem during merge: method signature of
backlight_device_register in kernel source is different than in acpi4asus
driver.
I changed the driver (asus_acpi.c: line 2094) to match kernel
bd = backlight_device_register ("asus", NULL, NULL, &asusbl_data);
After that change drivers compiles and inserts properly.
--
asus_acpi in old version, does not support notebooks
https://launchpad.net/bugs/85407
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85407] Re: asus_acpi in old version, does not support notebooks
lspci output ** Attachment added: "lspci-vvnn.log" http://librarian.launchpad.net/6466149/lspci-vvnn.log -- asus_acpi in old version, does not support notebooks https://launchpad.net/bugs/85407 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85407] Re: asus_acpi in old version, does not support notebooks
uname -a Linux ali 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux ** Attachment added: "dmesg" http://librarian.launchpad.net/6466148/dmesg.log -- asus_acpi in old version, does not support notebooks https://launchpad.net/bugs/85407 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85407] asus_acpi in old version, does not support notebooks
Public bug reported: In feisty asus_acpi is in version 0.30 which does not support many current notebooks (ie popular A8J series) please update to version 0.32 ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- asus_acpi in old version, does not support notebooks https://launchpad.net/bugs/85407 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80645] vmware tools install fails
Public bug reported: Binary package hint: linux-386 Kubuntu fiesty 2 is installed in vmware server 1.01 after issuing "instal VM tools" command and nothing happens - kernel does not see new device ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: Unconfirmed -- vmware tools install fails https://launchpad.net/bugs/80645 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74262] Re: Two "Manage Repositories" entries under different menus in Adept Manager
Sorry for previous post. The bug is of course present. -- Two "Manage Repositories" entries under different menus in Adept Manager https://launchpad.net/bugs/74262 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 74262] Re: Two "Manage Repositories" entries under different menus in Adept Manager
This bug is not present in Kubuntu Fiesty 7.4 (12.01.2007 update) -- Two "Manage Repositories" entries under different menus in Adept Manager https://launchpad.net/bugs/74262 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 78664] Kubuntu installer crash
Public bug reported:
Binary package hint: ubiquity
I choose polish locale
Traceback (most recent call last):
File "/usr/bin/ubiquity", line 166, in ?
main()
File "/usr/bin/ubiquity", line 161, in main
install(sys.argv[1])
File "/usr/bin/ubiquity", line 57, in install
ret = wizard.run()
File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 334, in run
self.process_step()
File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 828, in
process_step
self.progress_loop()
File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 599, in
progress_loop
raise RuntimeError, ("Install failed with exit code %s\n%s" %
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
File "/usr/share/ubiquity/install.py", line 1421, in ?
install.run()
File "/usr/share/ubiquity/install.py", line 355, in run
self.install_language_packs()
File "/usr/share/ubiquity/install.py", line 849, in install_language_packs
self.mark_install(cache, lp)
File "/usr/share/ubiquity/install.py", line 776, in mark_install
assert cache._depcache.BrokenCount == 0
AssertionError
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Kubuntu installer crash
https://launchpad.net/bugs/78664
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
