Here is a log for an initial startup. Looks like most of the time is
spent powering up:
Apr 15 14:12:50 laptop NetworkManager: (ttyACM0): powering up...
Apr 15 14:13:24 laptop NetworkManager: (wlan0): supplicant connection
state: completed -> associat
Notice takes 34 seconds to power up.
Here is a log with a manual disconnect, then I reconnect. This is very
fast to connect.
** Attachment added: "daemon.log"
http://launchpadlibrarian.net/25506907/daemon.log
--
Network Manager not giving 3G Ericsson F3507g Mobile Broadband enough time to
initialize in Jaunty
https://bugs.laun
Actually nix that statement I made on the first post. I realized that
that the power the next entry was for the wifi card.
Apr 15 14:12:50 laptop NetworkManager: (ttyACM0): powering up...
Apr 15 14:13:41 laptop NetworkManager: Associated with network: +COPS:
0,0,"AT&T",0
... actually 51 se
Actually nix that statement I made on the first post. I realized that
that the power the next entry was for the wifi card.
Apr 15 14:12:50 laptop NetworkManager: (ttyACM0): powering up...
Apr 15 14:13:41 laptop NetworkManager: Associated with network: +COPS:
0,0,"AT&T",0
... actually 59 se
So it looks like the missing piece was in the kernel. This card has to allocate
all it's memory via AGP. The intrepid kernel was missing AGP support:
http://kernel.ubuntu.com/git?p=apw/ubuntu-jaunty.git;a=commit;h=4e8b6e25943a22036a6b704ebef634c7dec4c10e
@jacyfan
Ensure that you are usin
Well on the Lenovo x301 I have the f3507g is completely powered down
till the initial bring up. Which is the long one. After that the device
stays up and on the connecing a second time it works really quick. I
think it would be the same on a reboot, as the card doesn't power down
(you can tell by t
David Chen verified that the experiment did work!
1) So we now need to build an official Intrepid kernel with this patch:
http://kernel.ubuntu.com/git?p=apw/ubuntu-jaunty.git;a=commit;h=4e8b6e25943a22036a6b704ebef634c7dec4c10e
2)Build an offical Intrepid xserver-xorg-intel driver with patch
http:
Dell no longer has a use for this request with their current recovery
solution.
** Changed in: dell
Status: Confirmed => Invalid
** Changed in: partman-auto (Ubuntu Hardy)
Status: Confirmed => Invalid
--
[Feature Request] enhance recipe format to allow specifying an existing
part
No longer a valid use case for Dell at this point.
** Changed in: dell
Status: Triaged => Invalid
--
[Feature Request] Allow Boot Modifications with Driver Updates
https://bugs.launchpad.net/bugs/120286
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
@lisaYue
I must have copied the wrong link. I meant to post that patch link.
Please try the kernel that David Chen posted.
--
[West Lake] Ubuntu 8.10: System unable to detect optimized graphic resolution.
https://bugs.launchpad.net/bugs/338598
You received this bug notification because you a
@lisaYue
I must have copied the wrong link. I meant to post that patch link.
--
[West Lake] Ubuntu 8.10: System unable to detect optimized graphic resolution.
https://bugs.launchpad.net/bugs/338598
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Also wanted to note that the kernel linked by David Chen is in the
proposed repository.
--
[West Lake] Ubuntu 8.10: System unable to detect optimized graphic resolution.
https://bugs.launchpad.net/bugs/338598
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Which Intel graphics card is on this board? Can you post the output of
"sudo lspci -vnn" ?
--
[West Lake] Ubuntu 8.10: System unable to detect optimized graphic resolution.
https://bugs.launchpad.net/bugs/338598
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Jason
I read the logs. The reason you are seeing this is that the machine is
using the "Vesa" video driver and not the intel video driver. The revision of
the intel chip may not be in the database of supported intel chips in 8.10.
Could you try out a Jaunty Live CD and see if you get the
Welch sends an acpi event. We handled in acpi-support package.
** Changed in: hotkey-setup (Ubuntu)
Status: New => Invalid
--
[Welch's]-Ubuntu8.10:Fn+F8 has no function in Ubuntu.
https://bugs.launchpad.net/bugs/337236
You received this bug notification because you are a member of Ubuntu
@Jason
This looks lot be a newer version of the Intel 4500 chip. The chip id
may not be in the driver. Could you try out the Jaunty live CD .. you don't
need to install it , you can see if comes up with the proper resolution in the
Live Session.
If that works it better helps narro
F3507g is support is now completely broken in Network Manger in Jaunty,
as of April 5th.
It no longer is listed in Network Manger. Last week it was listed but it
would not activate the card. It was working through out Jaunty Alpha
(just listing 4 instances), now lists no instances.
This card is o
Just did a update and now it magically is working. So I must have been
in between updates in Jaunty.
@Robbie
You your going to want to try the lastest updates as of 8pm CST. Something
fixed the problem though I'm not sure what.
--
Ericsson F3507g WWAN Card doesn't work with NetworkManager
Could you try adding the following to your /etc/X11/xorg.conf:
Section "Device"
Driver "intel"
Option "DRI" "false"
Option "Tiling" "false"
EndSection
Could you attach the logs. Also if this does not work. Can you first
update your system with the latest kernel and all
@Jason
If you are at a prompt. You can still update.
To bring up networking (hooked up via ethernet):
sudo ifconfig eth0 up
sudo dhclient
Then to update:
sudo apt-get update
sudo apt-get upgrade
I'm looking at behavior and it does not appear that Mike's patch is
being applied in gnome-control-center - 1:2.26.0-0ubuntu2. I see it in
the queue for the package. But the applet is not changed in anyway for
smaller resolutions and still has the same issue. The applet still eat
571 vertical pixel
@Jason
That means the intel driver failed to load and it then fell back to
safe graphics mode. I'll see what more I can look into. It appears backporting
support for the G41 is a lot more involved then expected. Will get back to you
shortly.
--
[West Lake] Ubuntu 8.10: System unable
** Attachment added: "NM_network_status_Jaunty_not_smooth.ogv"
http://launchpadlibrarian.net/25307422/NM_network_status_Jaunty_not_smooth.ogv
--
[Regression] nm-applet extremely sluggish when reporting AP status in Jaunty
https://bugs.launchpad.net/bugs/360321
You received this bug notificat
Public bug reported:
nm-applet is extremely sluggish and not as responsive in Jaunty as it is
in Intrepid. To show this I created videos on my Lenovo Thinkpad T61
with a 2ghz dual core Core 2 dou & Intel wireless 4965.
I notice this on any machine running Jaunty though.
** Affects: network-manag
** Attachment added: "NM_network_status_intrepid_smooth.ogv"
http://launchpadlibrarian.net/25307457/NM_network_status_intrepid_smooth.ogv
--
[Regression] nm-applet extremely sluggish when reporting AP status in Jaunty
https://bugs.launchpad.net/bugs/360321
You received this bug notification b
@Tim
When do you plan to put this fix into the so it tested out with our kernel?
@Steve
While yours does kick off a rescan the card still tries to connect to the
old AP.
I notice this in dmesg:
[4253.476743] wlan0: direct probe to AP 00:21:55:b1:d9:01 try 1
[ 4253.676061] wlan0: direct
When using 2.6.26 kernel provided by Freescale, NM detects the network
device just fine. While they do compile the network driver into the
kernel. Maybe that info can help some.
--
NetworkManager does not detect eth0 on armel
https://bugs.launchpad.net/bugs/356517
You received this bug notificati
Thishas been resolved in jaunty. It does take up to 3 times trying to
connect at times though. But it does work.
** Changed in: network-manager (Ubuntu)
Status: New => Fix Released
--
nm is not able to use Ericsson F3507g Mobile Broadband
https://bugs.launchpad.net/bugs/334964
You receive
Public bug reported:
Binary package hint: network-manager
Network manager is not giving Ericsson F3507g Mobile Broadband Minicard
Network Adapter enough time to fully initialize and make a connection to
the 3G network. It looks to take about a minute for the card to
completely initilized and then
** Attachment added: "Trying to connect 3G.ogv"
http://launchpadlibrarian.net/25327359/Trying%20to%20connect%203G.ogv
--
Network Manager not giving 3G Ericsson F3507g Mobile Broadband enough time to
initialize in Jaunty
https://bugs.launchpad.net/bugs/360343
You received this bug notificatio
Public bug reported:
Binary package hint: openoffice.org
OpenOffice Wizards are not working even though package
openoffice.org-java-common is installed.
These are File->Wizards.
I'm using openoffice version 1:3.0.1-9ubuntu2.
** Affects: openoffice.org (Ubuntu)
Importance: Undecided
** Attachment added: "openoffice_wizards_no_work.png"
http://launchpadlibrarian.net/25327740/openoffice_wizards_no_work.png
--
[Regression] Wizards not working in open office in Jaunty even with
openoffice.org-java-common installed
https://bugs.launchpad.net/bugs/360346
You received this bu
** Attachment added: "openoffice_wizards_no_work2.png"
http://launchpadlibrarian.net/25327755/openoffice_wizards_no_work2.png
** Tags added: jaunty
--
[Regression] Wizards not working in open office in Jaunty even with
openoffice.org-java-common installed
https://bugs.launchpad.net/bugs/36
I failed to mention that I am running all the latest update as of April
13 and I'm running on AMD64.
--
[Regression] Wizards not working in open office in Jaunty even with
openoffice.org-java-common installed
https://bugs.launchpad.net/bugs/360346
You received this bug notification because you
@jacyfan
Hmm. According the the log it failed due to an error in the xorg.conf
file.
(==) Using config file: "/etc/X11/xorg.conf"
Parse error on line 25 of section Device in file /etc/X11/xorg.conf
This section must have an Identifier line.
(EE) Problem parsing the config file
I left ou
Ok I verified. It was because I left out the "Identifier" line in the
stanza. Please try out the stanza in the post above and let me know what
happens.
--
[West Lake] Ubuntu 8.10: System unable to detect optimized graphic resolution.
https://bugs.launchpad.net/bugs/338598
You received this bug no
*** This bug is a duplicate of bug 360120 ***
https://bugs.launchpad.net/bugs/360120
That is odd. I have 2 seperate Jaunty installs that the wizards do not
work. Let me try a fresh install on one today and see what happens.
--
[Regression] Wizards not working in open office in Jaunty even wi
Checked into this a little more. Guys from Freescale tried it out with
our latest build. It's broken for that case now too.
It seems that what I said is no longer true with the newest builds. It
was this way till around early March with the monolithic Freescale
kernel. Now this is nolonger the cas
*** This bug is a duplicate of bug 360120 ***
https://bugs.launchpad.net/bugs/360120
@Chris
Looks like that is the case. after installing openjdk-6-jre things work.
--
[Regression] Wizards not working in open office in Jaunty even with
openoffice.org-java-common installed
https://bugs
** Also affects: oem-priority
Importance: Undecided
Status: New
--
NetworkManager does not detect eth0 on armel
https://bugs.launchpad.net/bugs/356517
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Verified fixed.
** Changed in: oem-priority
Status: New => Fix Released
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Assignee: (unassigned) => Jerone Young (jerone)
--
[West Lake] Ubuntu 8.10: System unable to detect optimized graphic resolution.
https://bugs.launchpad.net/bugs/338598
You received th
Freescale engineer is reporting pulse audio consumes 30%-40% CPU during
video playback with latest build as of april 12 09.
They have now removed pulse audio using aptitude, and are no longer
using it.
--
[ARM] Pulse Audio eating up to much CPU
https://bugs.launchpad.net/bugs/358831
You receive
Verified fix in now in 9.04 and applet works for 1024x576 displays.
** Changed in: oem-priority
Status: New => Fix Released
--
Quite hard to change screen resolution back to normal when resolution is set
very low
https://bugs.launchpad.net/bugs/224229
You received this bug notification b
For ARM the reason this is important is that Pulse Audio eating
significant CPU means less battery life for ARM based devices. So we
need to minimize the CPU utilization of Pulse Audio on ARM.
--
[ARM] Pulse Audio eating up to much CPU
https://bugs.launchpad.net/bugs/358831
You received this bug
It looks like there is one more patch that needs to be added:
http://cgit.freedesktop.org/xorg/driver/xf86-video-
intel/commit/?id=4dd00681dd0f9fce8dfd4592b46418edbbd2eeb4
--
[West Lake] Ubuntu 8.10: System unable to detect optimized graphic resolution.
https://bugs.launchpad.net/bugs/338598
You
Actually nevermind that patch was already in the source.
@jacy fan @Jason Lee
Please try the new xorg.conf entry that I have above.
--
[West Lake] Ubuntu 8.10: System unable to detect optimized graphic resolution.
https://bugs.launchpad.net/bugs/338598
You received this bug notification beca
@jacyfan
It looks like this is going to get way more involved. The driver can't
seem to allocate video memory.
(EE) GARTInit: Unable to open /dev/agpgart (No such file or directory)
(WW) intel(0): /dev/agpgart is either not available, or no memory is available
for allocation. Using pre-al
@Jason
That is the same error as in jacyfan log. But thanks for verifying.
--
[West Lake] Ubuntu 8.10: System unable to detect optimized graphic resolution.
https://bugs.launchpad.net/bugs/338598
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
@Alex
Yes. The device is not on initally. But on power up it takes about ... what
I guess 30-40 seconds (need to measure this better) for the device itself to
power up (about 7 seconds) and then connect to the Wireless network.
But if I connected once, then disconnect. The device remains
@Alex
Yes. The device is not on initally. But on power up it takes about ... what
I guess 30-40 seconds (need to measure this better) for the device itself to
power up (about 7 seconds) and then connect to the Wireless network.
But if I connected once, then disconnect. The device remains
I've attached a log. I am connected to wifi access point "AustinJava".
It took 3 tries this time to connect to the AT&T network.
** Attachment added: "Fresh startup trying to connect to AT&T network"
http://launchpadlibrarian.net/25458172/nm.log.txt
--
Network Manager not giving 3G Ericsson
Actually the post above never actually gets a full connection. Looks
like it's not getting a gateway. I'll try again later.
--
Network Manager not giving 3G Ericsson F3507g Mobile Broadband enough time to
initialize in Jaunty
https://bugs.launchpad.net/bugs/360343
You received this bug notificat
With compiz on in Jaunty. Users can no longer use ALT+Left Mouse click
to drag the "Display Prefrences" to see the rest of the applet that is
cut off. Now it is impossible for users to actually use the app without
cutting off compiz. Compiz is on by default.
--
Quite hard to change screen resolut
** Attachment added: "Display Prefences with 1024x576 screen"
http://launchpadlibrarian.net/24553512/1024_576_display_prefrences.png
--
Quite hard to change screen resolution back to normal when resolution is set
very low
https://bugs.launchpad.net/bugs/224229
You received this bug notificat
Running kernel 2.6.28-11-generic with the iwlwifi driver with a 5350
card. This problem still exists now, from a fresh beta install with
updates as of March 31. Network manager still tries to connect to a
ghost network (that I last was connected to before suspending).
** Changed in: linux (Ubuntu
** Summary changed:
- default user audio goes to /dev/null
+ [ARM] default user audio goes to /dev/null
--
[ARM] default user audio goes to /dev/null
https://bugs.launchpad.net/bugs/396716
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Private bug reported:
The Soltech TA12 netbook does not send a release key when pressing
volume up, volume down, or mute. This causes Ubuntu to see the key
constantly being pressed.
Zareason (www.zareason.com) is evaluating to this product to ship with
Ubuntu 9.04.
A patch attached was written f
** Attachment added: "Patch to fix issue with Jaunty 2.6.28 kernel"
http://launchpadlibrarian.net/28851684/soltech_hot_keyboard_fix_2_6_28_jaunty.diff
--
Soltech TA12 netbook volume hotkeys not sending key release in Jaunty
https://bugs.launchpad.net/bugs/397499
You received this bug notific
Attached is the DMI decode info, to add more info to understand the
patch.
** Attachment added: "DMI decode info for the Soltech TA12"
http://launchpadlibrarian.net/28851707/dmidecode.txt
** Summary changed:
- Soltech TA12 netbook volume hotkeys not sending key release
+ Soltech TA12 netbook
** Description changed:
The Soltech TA12 netbook does not send a release key when pressing
volume up, volume down, or mute. This causes Ubuntu to see the key
constantly being pressed.
- Zareason (www.zareason.com) is evaluating to this product to ship with
- Ubuntu 9.04.
+ Zareason (www.z
** Visibility changed to: Public
--
Soltech TA12 netbook volume hotkeys not sending key release in Jaunty
https://bugs.launchpad.net/bugs/397499
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
This problem can be seen on any machine actually. I was seeing it
earlier. The key is to NOT run "lsusb". This kicks off a fresh scan of
the USB bus and then it's seen.
So to reproduce:
1) Connect USB hub to usb port
2) Connect any device to it .. in this case try a USB stick .. though it's for
Narrowing the fix down. This problem does not appear on upstream kernels 2.24.4
and up. Have to try lower point releases. But I was able to get a binary for
2.24.4 & up here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Now to try lower 2.24 point releases.
--
Ubuntu 8.04.3 amd64 on Dell PE
Trying upstream 2.24.0 , 2.24.1, & 2.24.2 with the server kernel config
all work without issue. I also tried 2.6.25 before and that worked
without issue also.
So their appears to be a patch in our kernel that has caused a
regression.
--
Ubuntu 8.04.3 amd64 on Dell PE R610 : Front USB ports do no
This is a regression in the hardy server kernel starting with version
2.6.24-21.42 in the Ubuntu archive. Here are results of me trying
various kernels from the archive:
kernel Result
-
2.6.24-16.30 works!
2.6.24-20.38 works!
2.6.24-21.42 Broken!
2.6.24-21.4
This patch is potentially what is causing the issue:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=6ca9208c22280928597bcc738bf4248de0ab359d
--
Ubuntu 8.04.3 amd64 on Dell PE R610 : Front USB ports do not detect newly
inserted USB device
https://bugs.launchpad.net/bugs/406419
** Package changed: ubuntu => linux (Ubuntu)
--
Ubuntu 8.04.3 amd64 on Dell PE R610 : Front USB ports do not detect newly
inserted USB device
https://bugs.launchpad.net/bugs/406419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Trying the patch above with vanilla 2.6.24.0 source you see the problem.
The 2.6.24 source worked fine without this patch (see past comments).
So the patch pointed above is the source of the problem here.
--
Ubuntu 8.04.3 amd64 on Dell PE R610 : Front USB ports do not detect newly
inserted USB
Confirmed that the patch pointed to by Stuart does fix the issue.
--
Ubuntu 8.04.3 amd64 on Dell PE R610 : Front USB ports do not detect newly
inserted USB device
https://bugs.launchpad.net/bugs/406419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I was able to reproduce this issue on my laptop. Very easy to reproduce.
1) Take a USB port
2) Connect USB hub to it
3) Try any USB device connected to the USB hub and notice that it never see it
seen by the kernel.
So this isn't a machine specific issue. It's a problem for any USB hub.
Though
So looks like my findings where actually wrong. I just needed to wait a
few seconds. Once I did things worked fine. Will have to try it on the
actual Dell machine the problem is being reported on.
--
Ubuntu 8.04.3 amd64 on Dell PE R610 : Front USB ports do not detect newly
inserted USB device
ht
Public bug reported:
In 9.10 init configurations for upstart have been moved to /etc/init ,
where as all other versions of Ubuntu before now have them in
/etc/event.d. So to ensure that all documentation out their still remain
accurate for 9.10, as well as application that may put configurations
f
Well in a since it is hung. This is what I've found.
*)Turning off Xorg and just using the console.
Using pm-suspend on wake up it still hangs. When it wakes you can see the
console, though you can't actually put input into it. I figure it's most likely
what was in the framebuffer last. Funny e
So things appear to work now using 2.6.31-3-generic with using the
internal hard disk. I was using a USB drive for root. It still fails
with the USB drive, but works fine with the internal disk being used.
The odd part of this is when I try other machines that use KMS with the
USB drive, they have
Here is an example video. You normally see the little indicator in the
red bar, even with other systems using kernel mode settings:
http://www.youtube.com/user/jerone222#play/all/uploads-all/0/jaG0JsNuiN8
--
Usplash not displaying progress indicator on Dell Mini 10v using KMS & 1024x576
screen
** Summary changed:
- karmic alpha2 candidate doesn't boot up on Studio XPS 1340
+ Karmic doesn't boot up on Studio XPS 1340 with Nvidia Hybrid graphics
--
Karmic doesn't boot up on Studio XPS 1340 with Nvidia Hybrid graphics
https://bugs.launchpad.net/bugs/385658
You received this bug notificat
This issue is being discussed upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=21614
** Package changed: ubuntu => xorg (Ubuntu)
** Bug watch added: freedesktop.org Bugzilla #21614
https://bugs.freedesktop.org/show_bug.cgi?id=21614
--
trackpad jumpy on Dell mini 10v
https://bugs.launch
*** This bug is a duplicate of bug 365943 ***
https://bugs.launchpad.net/bugs/365943
** This bug has been marked a duplicate of bug 365943
Mouse cursor jumps when two fingers are used
--
trackpad jumpy on Dell mini 10v
https://bugs.launchpad.net/bugs/395515
You received this bug notificat
This has returned in 9.10 alpha builds. Yet none of the issue have been
addressed.
** Also affects: oem-priority
Importance: Undecided
Status: New
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
You received
@Sebastien
Since this decision has been made, how does the ubuntu team plan to deal
with all the regressions caused by this decision?
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
You received this bug notificat
** Also affects: oem-priority
Importance: Undecided
Status: New
--
9.04 Jaunty Junk characters in oem-config
https://bugs.launchpad.net/bugs/402733
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
** Attachment added: "This is a version of the patch for 2.6.31 karmic kernel &
upstream"
http://launchpadlibrarian.net/29001595/soltech_ta12_volume_key_fix_2_6_31.diff
--
Soltech TA12 netbook volume hotkeys not sending key release in Jaunty
https://bugs.launchpad.net/bugs/397499
You receiv
** Attachment added: "lscpi output of the Dell Mini 10v"
http://launchpadlibrarian.net/29013440/lspci
** Summary changed:
- Intel 945GM unable to wake properly from suspend with KMS enabled
+ Intel 945GME unable to wake properly from suspend with KMS enabled
** Description changed:
- The De
Public bug reported:
The Dell Mini 10v comes with a 945GME intel graphics card. In 9.10 beta
using 2.6.30 with KMS (kernel mode settings) enabled the machine is not
able wake from suspend.
Checking the intel-next tree (things going into upstream) as of July 13.
I am able to wake and see a mouse c
Public bug reported:
The issue is when the Dell Mini 10v with 1024x576 screen, boots up in
karmic (as of July 14 09) the usplash boot screen comes up but does not
show the little indicator peg moving horizontally under Ubuntu logo.
Just a red bar.
I'm not sure though if it's
1) upslash not workin
** Package changed: ubuntu => linux (Ubuntu)
** Also affects: usplash (Ubuntu)
Importance: Undecided
Status: New
--
Usplash not displaying progress indicator on Dell Mini 10v using KMS & 1024x576
screen
https://bugs.launchpad.net/bugs/399369
You received this bug notification because
So tried out both kernels. Looks like they both are on par with each
other. Though the problem still exists.
No real good info from the logs though, I need to get a usb serial
connector and see if I can get anything through that. I'll attach what I
got from the machine after rebooting it.
@Jesse
** Attachment added: "Dmesg output of mini 10 after supsend hang"
http://launchpadlibrarian.net/29074658/dmesg
--
Intel 945GME unable to wake properly from suspend with KMS enabled
https://bugs.launchpad.net/bugs/399362
You received this bug notification because you are a member of Ubuntu
Bug
** Attachment added: "Xorg.0.log.old log after suspend hang"
http://launchpadlibrarian.net/29074669/Xorg.0.log.old
--
Intel 945GME unable to wake properly from suspend with KMS enabled
https://bugs.launchpad.net/bugs/399362
You received this bug notification because you are a member of Ubuntu
@Jesse
I renamed the vbetool to ensure it's not run and still see the same issue.
Doesn't appear anything is running vbetool after replacing to see if anything
is calling it. That patch was actually in the intel-next kernel I tried out. So
no effect on this problem.
--
Intel 945GME unable
Created a video so you guys can see the problem in action:
http://www.youtube.com/watch?v=CUKsGsv8gnMhttp://www.youtube.com/watch?v=CUKsGsv8gnM
--
Intel 945GME unable to wake properly from suspend with KMS enabled
https://bugs.launchpad.net/bugs/399362
You received this bug notification because
Actually that was a bad link. Here is the correct link for the video:
http://www.youtube.com/jerone222#play/all/uploads-all/0/CUKsGsv8gnM
--
Intel 945GME unable to wake properly from suspend with KMS enabled
https://bugs.launchpad.net/bugs/399362
You received this bug notification because you ar
The device is a Realtek Mass Storage Device and it is connected via USB.
I've posted more extensive lsusb info on it.
** Attachment added: "Realtek Storage Device lsusb info"
http://launchpadlibrarian.net/30493521/lsusb_info.txt
--
dell mini 10v SD/SDHC slot gets ejected from the USB bus on
Another observation is if I use the "eject" command on the comand line
the Realtek device does get ejected from the USB bus. Only when you
eject from nautilus does it do it.
--
dell mini 10v SD/SDHC slot gets ejected from the USB bus on nautilus 'eject'
https://bugs.launchpad.net/bugs/404185
You
This definitely seems to only be happing with Nautilus & gvfs. I believe
this patch is the culprit if it made it in :
http://cgit.freedesktop.org/~david/gvfs/commit/?h=gdu-volume-
monitor&id=303cfd43578f0a4198c063f1a5fbcd16fec2b0bf
When using other programs such as Palimpsest (it's the new disk
So reverting the patch pointed to above does resolve the issue.
This patch needs better logic added to it. I assume this problem will
also effect other Dell & other vendor machines with SD card readers.
** Also affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gv
I'm posting a tarball with compiled packages with the reverted patch.
This will allow for quick testing for folks.
** Attachment added: "gvfs-package-with-reverted-patch-fix-issue.tar.bz2"
http://launchpadlibrarian.net/30496581/gvfs-package-with-reverted-patch-fix-issue.tar.bz2
--
dell mini
To add another thing. With the reverted patch the card reader will be
removed from the usb bus on eject. But once you remove the SD card and
place it back in it shows back up and works as it should.
I believe this is the same behavior it does with Ubuntu 9.04 also.
--
dell mini 10v SD/SDHC slot
** Attachment added: "Screenshot-Bluetooth Preferences.png"
http://launchpadlibrarian.net/30527669/Screenshot-Bluetooth%20Preferences.png
--
In prefrences has button "Setup_new device" .. "_" should not be their or
should be under "n" in new
https://bugs.launchpad.net/bugs/416099
You receive
201 - 300 of 1105 matches
Mail list logo
