any update on this bug?
thanks
--
xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
https://bugs.launchpad.net/bugs/102683
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
Hi Robert,
My Feisty just got update few minutes ago (april 10). I rebooted and
the ethernet connection was not setup after reboot. I had to click again
on the small network applet in toolbar and select "Wired Connection".
I tried to change the config of the network interface in "Network
S
Unfortunately this new driver did not fix the problem. The problem is still
there and there is no behavior change with this new driver.
This new driver work only ONCE and it's when it's used IMMEDIATELY after the
proprietary nVidia driver from the company nVidia.
In all other circumstance it fail
Here is the other attachement. In this case the new driver failed.
What you want me to do next?
thanks very much
** Attachment added: "Xorg.0.log_nvafternv.txt"
http://librarian.launchpad.net/7315307/Xorg.0.log_nvafternv.txt
--
xorg won't start on nvida 6600 card due to nv driver not suppor
-Adding this parameter did make the new "nv" driver you asked me to try work
all the time.
-Here are the "nv" pameters used in xorg.conf;
Section "Device"
Identifier "nVidia Corporation NV43 [GeForce 6600 GT]"
Driver "nv"
Option "CrtcNumber" "0"
Busi
unfortunately, the Gusty Tribes 5 live CD fails the same way. When it
launches the GUI, the screen becomes garbled and the only thing to do is
to reset. In the previous Ubuntu release, adding the line below in
Xorg.conf, fixed the problem . Doing "man nv" in a shell shows what the
parameter is use
*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
Gutsy Tribe 5 is also working fine for me. My wired ethernet interface
is up when I'm logged in the GUI.
--
Ethernet interface not configured at boot time
https://bugs.launchpad.net/bugs/94095
You received thi
The problem is fixed for me in Gutsy Tribe 5. My wired ethernet
interface is up when I log in the GUI. Before I had to use the network
manager applet and pick "wired interface" for it to come up.
--
network-manager stops and restarts already ifup'ed interfaces
https://bugs.launchpad.net/bugs/9026
The problem is fixed for me in Gutsy Tribe 5. My wired ethernet
interface is up when I log in the GUI.
--
does not automatically start the wired connection due to missing link beat
https://bugs.launchpad.net/bugs/83143
You received this bug notification because you are a member of Ubuntu
Bugs, wh
This problem has never been fixed in Ubuntu 7.04 but it's fixed in 7.10.
I hope the fix would be backported into the impacted previous release...
--
does not automatically start the wired connection due to missing link beat
https://bugs.launchpad.net/bugs/83143
You received this bug notification
*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
This problem has never been fixed in Ubuntu 7.04 but it's fixed in 7.10.
I hope the fix would be backported into the impacted previous release...
--
Wired network not enabled upon system boot
https://bugs.laun
*** This bug is a duplicate of bug 83143 ***
https://bugs.launchpad.net/bugs/83143
Thanks,
BTW after a fresh install of latest Debian Etch 4.0, it also show the exact
same problem. I assume the fix will also be pushed to Debian.
--
Ethernet interface not configured at boot time
https://bug
The screen display I've got when the problem is occuring is identical to the
screenshot attached to Bug #41979
The issue is with the autodection of monitor. Adding line;
Option "CrtcNumber" "0"
makes the problem go away.
Is there any new driver we can try to see if the problem is now fixed?
W
This seems a duplicate of Bug #102683 . The screenshot is exactly what's
I've got. The problem seems to be with the autodection of monitor.
Try putting back the driver as "nv" and assuming your monitor is plugged in
port 0 of the videocard add the line below in the section describing the "nv"
dr
The problem where the "nv' driver doesn't auto detect the monitor is not fixed
for ALL configuration. On my PC this is not fixed. I need to add manually the
line below for it to work;
Option "CrtcNumber" "0"
--
xserver-xorg crashes when handling newer nvidia cards
https://bugs.launchpad.net/bug
agreed that if the bug is not in that application you should track the
problem.
Just to correct some of your comment; The hardware which is not working
with Feisty has been working PERFECTLY with Debian, Suse, Fedora, Ubuntu
Dapper for the longest time. There really is a bug in Feisty somewhere
in
OK, it's understandable that the fix may not be in for Feisty release.
It would be appreciated if the investigation can continue as soon as possible.
Is there any timeframe estimate for continuing to look into the issue?
As soon as you have new things to try out to isolate the problem tell
me.
th
In attachement are 4 files.
deamon.log (/var/log/daemon.log) and messages (/var/log/messages) take after a
clean bootup. I recapture the same file after clicking on the networking applet
and on the "wired connection" so that Feisty connect to the network. If you do
a diff of the two logs files
** Attachment added: "daemon_after.log"
http://librarian.launchpad.net/7338122/daemon_after.log
--
Ethernet interface not configured at boot time
https://bugs.launchpad.net/bugs/94095
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubun
** Attachment added: "messages"
http://librarian.launchpad.net/7338123/messages
--
Ethernet interface not configured at boot time
https://bugs.launchpad.net/bugs/94095
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
** Attachment added: "messages_after"
http://librarian.launchpad.net/7338137/messages_after
--
Ethernet interface not configured at boot time
https://bugs.launchpad.net/bugs/94095
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
forgot to mention in my reply above that the system got many package
updated today and the networking problem is still there.
What other information might be usefull to you for debugging?
thanks
--
Ethernet interface not configured at boot time
https://bugs.launchpad.net/bugs/94095
You received
sorry, this bug is NOT fixed. Please re open the bug
--
Ethernet interface not configured at boot time
https://bugs.launchpad.net/bugs/94095
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@l
Is there someone with enough privilege to re-open the bug status to
"confirmed"? The problem is NOT fixed.
Do I need to re-open a new bug with same description?
** Changed in: network-manager (Ubuntu)
Status: Fix Released => Unconfirmed
--
Ethernet interface not configured at boot time
h
bug is NOT fixed. Changing the bug status to "unconfirmed".
--
Ethernet interface not configured at boot time
https://bugs.launchpad.net/bugs/94095
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
Hi Martin,
That network card has been working without problem with Ubuntu 6.06 without
a glitch and with many different Linux distro. It's only in Feisty that this
problem occurs.
Here is the output;
$ dmesg | grep link
[ 23.772183] audit: initializing netlink socket (disabled)
Did y
Thanks Timo.
How will I know this update has been pulled from my computer? The next time I
see changes to xserver-xorg-video-nv?
Is there any expected timeframe? 1-2 weeks?
thanks
--
xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
https://bugs.launchpad.net/bugs/1026
I think the bug priority is at least medium
-The problem after the install of Feisty (2007-04-15 build) is that it leaves
TWO identical entries in "Software Source application" for the CDROM. These
entries read as;
Cdrom with Ubuntu 7.04 "Feisty Fawn"
Officially supported
Restricted
Using Feisty Beta I have same problem.
The PC has a single Ethernet card "eth0" using DHCP.
When Feisty boots, the eth0 interface is not enabled. The first time I
log on after each reboot, I have to click on the small networking applet
and click on "wired connection". Then the eth0 is braught up a
Where should I report that the driver nv don't work for Geforce 6600
AGP?
--
xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
https://launchpad.net/bugs/14762
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Description changed:
Binary package hint: software-properties-gtk
After clean install of Ubuntu 7.04 Beta (i386 alternate), update-manager
ran and downloaded some package from the net and prompted me to insert
CD-ROM to install updated. I didn't want to install packages from CD-
RO
Public bug reported:
Ubuntu Feisty 7.04 Beta running kernel linux-image-2.6.20-12-generic
(for i386) is working fine. Using kernel from linux-
image-2.6.20-13-generic make the system hang at line;
Uniform CD-ROM drive Revision: 3.20
Some other people on IRC indicated they had the problem and was
** Tags added: cd-rom feisty linux-image
--
feisty linux-image 2.6.20-13 stop booting at; Uniform CD-ROM driver Revision:
3.20
https://launchpad.net/bugs/15
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I meant after setting root=/dev/hdb7, problem went away.
--
feisty linux-image 2.6.20-13 stop booting at; Uniform CD-ROM driver Revision:
3.20
https://launchpad.net/bugs/15
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Problem has been found.
Feisty is not the booting partition this PC, hence the kernel parameters in
grub are located in another partition. After an update of feisty, I need to
changes manually the grub parameters by manually mounting and editing the grub
menu.lst. After Feisty upgrade to 2.6.20-
During Ubuntu 7.04 Beta1 installation, Geforce 6600 been detected and
assigned video driver "nv" in /etc/xorg.conf
After reboot xorg start and video is garbled. Switching to console
(CTRL-ALT-F1) and doing "telinit 1". You can change (sudo vi
/etc/xorg.conf ) the video driver from "nv" to "vesa".
Public bug reported:
Binary package hint: software-properties-gtk
After clean install of Ubuntu 7.04 Beta, update-manager ran and
downloaded some package from the net and prompted me to insert CD-ROM to
install updated. I didn't want to install packages from CD-ROM, I then
clicked "cancel" and wa
** Description changed:
Binary package hint: software-properties-gtk
- After clean install of Ubuntu 7.04 Beta, update-manager ran and
- downloaded some package from the net and prompted me to insert CD-ROM to
- install updated. I didn't want to install packages from CD-ROM, I then
- clicked
The computer has many linux partition. It has one main Linux (ubuntu 6.06)
partition which is the ONLY ONE having grub installed. Feisty was installed in
a separate parition. During feisty installation, grub installation was skipped
BUT the dialog box indicated to boot feisty from /dev/sdb7. I a
This seems also to be related to the bug 98795 I raised. Not only you
can't remove CD-ROM but if you click on any options in software source
dialog shown by in the screenshot.png dialog will endup by corrupting
the source.lust.
I think this bug is very serious as no other application that reads th
** Summary changed:
- software-properties-gtk corrupted /etc/apt/source.list
+ [Feisty Beta] software-properties-gtk corrupts /etc/apt/source.list
--
[Feisty Beta] software-properties-gtk corrupts /etc/apt/source.list
https://bugs.launchpad.net/bugs/98795
You received this bug notification becau
Public bug reported:
Binary package hint: xserver-xorg-driver-nv
During Ubuntu 7.04 Beta installation, the Geforce 6600 has been detected
and assigned video driver xorg "nv" in /etc/xorg.conf. This is what was
expected.
After reboot into newly installed Feisty, Xorg started and video display
is
Problem still there. Reported the bug and number is bug # 102683
P.S. I clicked by mistake on a button that makes bug 14762 being
reported to "kubuntu-default-settings (Ubuntu)". Unfortunately, there is
no undo button... Please ignore the "kubuntu-default-settings
(Ubuntu)"...
--
xorg won't star
Monitor is Viewsonic P225fb 21inchs monitor (tube)
$ lspci |grep nVidia
01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce
6600/GeForce 6600 GT] (rev a2)
$ cat /proc/cmdline
root=/dev/hdb7 ro vga=0x31A
Logs are attached when Xorg is using NV driver
(Note: after installing nvidia
The /etc/X11/xorg.conf with vesa
anything else you need?
thanks again
** Attachment added: "xorg.conf"
http://librarian.launchpad.net/7140533/xorg.conf
--
xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
https://bugs.launchpad.net/bugs/102683
You received this bug
logs when starting with vesa
** Attachment added: "Xorg.0.log_VESA"
http://librarian.launchpad.net/7140512/Xorg.0.log_VESA
--
xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
https://bugs.launchpad.net/bugs/102683
You received this bug notification because you are a
-The 'splash' kernel command line is never used.
-I Tried with and without vga=0x31A and it makes no difference. In both
case the "nv" driver fails and screen is all garbled. This parameters
(vga=0x31A ) is for using the video frame buffer and have high
resolution font at the console.
-I Found ou
** Attachment added: "nvafternvidiaok"
http://librarian.launchpad.net/7176575/nvafternvidiaok
--
xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
https://bugs.launchpad.net/bugs/102683
You received this bug notification because you are a member of Ubuntu
Bugs, which
surpise! I just updated Feisty and a new kernel as been downloaded;
linux-image-2.6.20-14-generic
Beleive it or not, for this kernel I must use root=/dev/sdb7 else kernel
stop booting at "Uniform CD-ROM drive Revision: 3.20"
In summary,
linux-image-2.6.20-12-generic -> the Kernel boot parameter h
I tested using 0.59.3 the problem seems fixed. Thanks very much
I have two questions;
Q1 - I find strange that there is two exactly identical entry for CR-ROM. Line
2 and 4 are the same and this shows in the dialog box I put in attachment.;
1:#
2:# deb cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Beta i38
50 matches
Mail list logo
