This happened this morning while I was attempting to update on my
Averatec 3280 laptop.
Ubuntu version and kernel version
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
DISTRIB_DESCRIPTION=Ubuntu karmic (development branch)
Linux cupid 2.6.31-11-generic #38-Ubuntu SMP Fri Oct 2
Public bug reported:
Binary package hint: update-manager
This system was updated online to Karmic from 9.04, leaving the legacy
grub in place (0.97-29ubuntu45).
When I ran Update Manager today, one of the listed upgrades was for
grub-common (version 2) - as follows:
Changes for the versions:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33044240/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33044241/XsessionErrors.txt
--
Update-manager tries to install grub-2 update on system with legacy grub
This sort of error would especially be a problem for someone updating
with apt-get or aptitude, without carefully examining the list of
updates.
--
Update-manager tries to install grub-2 update on system with legacy grub
https://bugs.launchpad.net/bugs/443326
You received this bug notification
Public bug reported:
Binary package hint: update-manager
While trying to update this system a few minutes ago, Update Manager
showed a list of updates, and then shortly after I clicked on the button
for starting the downloads, the program froze after displaying a message
saying that the deamon
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33044781/Dependencies.txt
--
Message daemon died appeared while running update-manager
https://bugs.launchpad.net/bugs/443344
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
in `ps aux` output, I find
peter 5193 2.8 9.1 86332 43704 ?S10:22 1:16
/usr/bin/python2.6 /usr/bin/update-manager
So I killed it.
--
Message daemon died appeared while running update-manager
https://bugs.launchpad.net/bugs/443344
You received this bug notification because
I then tried running update-manager again. Both this time and the
previous time I noticed that the program requested authentication twice,
which is odd.
After clicking on Install Updates, a message popped up 'Waiting for
other tasks', presumably the dead daemon.
peter23332 7.3 8.9 85676
Then I tried to run `apt-get update` and found there's still a lock
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily
unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another
process using it?
which is not surprising since update-manager
After deleting the lock file, I was able to complete the update with
apt-get.
--
Message daemon died appeared while running update-manager
https://bugs.launchpad.net/bugs/443344
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Having tried this a few minutes ago, I'm convinced that this is still
very buggy, and also very confusing to use.
I'll have to wait until tomorrow to retest this and provide more
details.
On Mon, Oct 5, 2009 at 3:25 PM, Launchpad Bug Tracker
438...@bugs.launchpad.net wrote:
This bug was fixed
Note: the Pulse utilities may seem a bit confusing at first, since there
are many choices for configuration of output devices, only a few of
which may work on a given machine.
--
Sound output with Rhythmbox and pulseaudio is extremely faint
https://bugs.launchpad.net/bugs/438474
You received
This may be a duplicate of bug #438474, and the solution for that may
apply here - to install the appropriate Pulse Audio volume and output
chooser utilities.
--
pulseaudio don't play on rhythmbox
https://bugs.launchpad.net/bugs/323287
You received this bug notification because you are a member
This was an even more serious problem when I booted this system this
morning: this message kept repeating for several minutes, and I was
afraid the OS would never finish booting.
The message shows up 199 times in dmesg (attached)
** Attachment added: dmesg from boot at 07:23 PDT this morning
A really serious problem is that I can't use a console screen
(tty1...tty6) because the message keeps repeating on console screens.
(Beta Karmic updated as of 3 oct 09)
--
Many cardbus cards are not supported booting Karmic on Averatec 3280
https://bugs.launchpad.net/bugs/436341
You received
This was solved by installing the PulseAudio Device Chooser and Volume
Control. Ubuntu has changed to using the PulseAudio sound utilities.
I did an upgrade install from Ubuntu 9.04 on this system - the installer
installed some PulseAudio components, but not those. I'm not sure if a
fresh install
It sounds like you need to configure your networking manually - in
particular /etc/resolv.conf and /etc/network/interfaces - which have
manual pages.
On Fri, Oct 2, 2009 at 4:15 PM, vexorian vexor...@gmail.com wrote:
in my case, the configuration dialog also crashes, can't send the report
since
This still happening on 2 Oct 2009 at 9:46 PDT updated to Beta with
further updates.
--
Sound output with Rhythmbox and pulseaudio is extremely faint
https://bugs.launchpad.net/bugs/438474
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've added contents of /var/log/dmesg after booting.
This is still happening with the beta + a number of updates installed as
of today.
** Attachment added: dmesg
http://launchpadlibrarian.net/32897170/dmesg
--
Many cardbus cards are not supported booting Karmic on Averatec 3280
Adding the PPA and updating does not fix this for me. However, now the
network settings, including IP, gateway, additional route, etc. are
retained SOMEwhere, so they show up the next time the Network Settings
dialog is run, but they have no effect: nothing shows up in
/etc/network/interfaces, the
A note: I also have the resolvconf package installed.
On Thu, Oct 1, 2009 at 8:34 AM, Mike Basinger mike.basin...@ubuntu.com wrote:
Fixed for me allso.
--
nm-connection-editor crashed with SIGSEGV in gtk_button_set_label()
https://bugs.launchpad.net/bugs/436109
You received this bug
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32792157/Dependencies.txt
--
service fails to start/stop/restart a daemon
https://bugs.launchpad.net/bugs/440179
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This problem occurs on both my test systems for Karmic, for all the
alpha versions I've tried.
--
service fails to start/stop/restart a daemon
https://bugs.launchpad.net/bugs/440179
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: sysvinit-utils
The 'service' program (in sysvinit-utils) fails to start, stop, or
restart a daemon, as follows:
r...@lightning:~# service networking restart
restart: Unknown instance:
It should have the same effect as the following:
r...@lightning:~#
I ended up having to hand-edit /etc/network/interfaces to provide the
static IP address and default route, also either /etc/resolv.conf or
some config file for the resolvconf file (if that's installed) to make
things work. The NetManager GUI is useless for that, and it should not
be. Plus the
I finally got the boot into FreeBSD to work. Here's what I put in
40_custom before running update-grub:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the
Actually, the problem of *detection* of FreeBSD or other BSD systems is
NOT solved yet, but at least we know how to set up a boot selection for
FreeBSD manually.
--
FreeBSD not detected by os-prober
https://bugs.launchpad.net/bugs/432254
You received this bug notification because you are a
Until now, the wi-fi killswitch had no effect on this laptop, running
either Ubuntu or Debian versions, over a period of several years. So
when this was finally implemented in this alpha release, I was caught by
surprise and didn't realize at first what was happening.
--
wifi does not work on
Public bug reported:
Binary package hint: network-manager
uname -a output: Linux lightning 2.6.31-11-generic #36-Ubuntu SMP Fri Sep 25
06:37:51 UTC 2009 i686 GNU/Linux
Karmic alpha 6 with updates up to the current time
CPU model name : VIA Samuel 2
With a default /etc/network/interfaces file,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32653969/Dependencies.txt
** Attachment added: IfupdownConfig.txt
http://launchpadlibrarian.net/32653970/IfupdownConfig.txt
** Attachment added: IpAddr.txt
http://launchpadlibrarian.net/32653971/IpAddr.txt
**
Public bug reported:
Binary package hint: pulseaudio
I get virtually no sound output when using pulseaudio, running rhythmbox
or trying to make default window sounds heard.
The system is an Averatec 3180 laptop.
Ubuntu version and kernel version (Karmic alpha updated a few minutes ago
online)
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/32658352/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/32658353/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/32658354/ArecordDevices.txt
This is probably the same as bugs #408784 and #323287, which report NO
sound output, but in this case I was trying to play some particularly
loud music and had selected an output mode which works a little. It's
very faint.
--
Sound output with Rhythmbox and pulseaudio is extremely faint
Correction: The system is an Averatec 3280, NOT 3180. Launchpad would
not let me edit this!!
--
Sound output with Rhythmbox and pulseaudio is extremely faint
https://bugs.launchpad.net/bugs/438474
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Notes about the UI:
- The fields for entering IPs, masks, etc. are very narrow - it's necessary to
drag the edges of the dialogs to provide enough space.
- You can't use tab or space to move from field to field - you have to use the
mouse to move from the IP field to the netmask field, etc. If
I put the following in 40_custom and then ran update-grub:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry freebsd {
On my initial attempt to do this, I somehow made the system unbootable.
I have a working installation with the legacy GRUB, but I don't want
to touch that because I am in the middle of doing some work with the
FreeBSD on that system and don't want that to be unbootable.
So I've reinstalled
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/32393862/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32393863/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/32393864/Disassembly.txt
** Attachment
Public bug reported:
While booting Karmic (Alpha 6 plus updates to present time) many (30 to
50) messages cardbus cards are not supported are displayed. They show
up in /var/log/kern.log.
Ubuntu version and kernel version
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
The message cupid kernel: [ 805.200043] pcmcia_socket pcmcia_socket0:
cs: cardbus cards are not supported. occurs 46 times in kern.log (and
on the screen while booting).
** Attachment added: recent portion of kern.log
http://launchpadlibrarian.net/32414706/last-kern.log
--
Many cardbus
*** This bug is a duplicate of bug 422585 ***
https://bugs.launchpad.net/bugs/422585
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32325647/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/32325648/ProcMaps.txt
** Attachment
This shows the RaLink pci card
** Attachment added: lspci output
http://launchpadlibrarian.net/32327613/lspci.txt
--
wifi does not work on Averatec 3280 in Karmic
https://bugs.launchpad.net/bugs/435441
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I am running Karmic, updated from 9.04 yesterday, with online updates up
to a few minutes ago. Since installing this version, wi-fi interfaces
don't work, but Ethernet does. Several wifi interfaces were working well
under 9.04. Karmic was installed online using update
This shows the Hawking HWUG1 USB wireless adapter, with the RaLink
RT2501USB chipset.
** Attachment added: lsusb output
http://launchpadlibrarian.net/32327653/lsusb.txt
--
wifi does not work on Averatec 3280 in Karmic
https://bugs.launchpad.net/bugs/435441
You received this bug notification
This shows that the drivers for the RaLink devices are loaded.
** Attachment added: lsmod output
http://launchpadlibrarian.net/32327735/lsmod.txt
--
wifi does not work on Averatec 3280 in Karmic
https://bugs.launchpad.net/bugs/435441
You received this bug notification because you are a
The Hawking USB HWUG1 USB wireless adapter with the RT2501USB chipset
does work on a desktop system which is also running an up-to-date Karmic
OS.
--
wifi does not work on Averatec 3280 in Karmic
https://bugs.launchpad.net/bugs/435441
You received this bug notification because you are a member
I have run the Network Manager from both Gnome and Xfce.
This system is dual-boot between Ubuntu and Debian Lenny. The wireless
cardbus cards work well from Debian (the Hawking USB adapter is not yet
supported under Lenny).
Also, I have tried a NetBSD-live-2007 live cd, and wifi works fine from
I also verified that this problem occurred when running the Alpha 4 and
Alpha 6 live CDs.
THEN - I happened to push the wireless button on the laptop. This was
the problem - after years, the wireless software in Ubuntu looks at this
button on this particular laptop, at least. The other OSes I
This problem also occurs with the live CDs for Karmic Alpha 4 and Alpha
6. I am continuing to use an xorg.conf file, as above, in my Karmic
installation on this laptop, in order to restrict screen resolution to
1024x768 and lower. Again, refer to #296142 for some details.
This computer works best
My current version information running Karmic is
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
DISTRIB_DESCRIPTION=Ubuntu karmic (development branch)
Linux cupid 2.6.31-10-generic #35-Ubuntu SMP Tue Sep 22 17:33:42 UTC 2009 i686
GNU/Linux
That includes updates to today, 23 Sept
I just updated the above Karmic installation (which uses the legacy GRUB
1) and noticed an update of os-prober. In this contact (without GRUB 2
installed) it produces no screen output when run. I would assume this
program requires that GRUB 2 is installed, though.
--
FreeBSD not detected by
I think that if Ubuntu is being installed in separate partitions from
existing Linux partitions, one reasonable approach would be to install
GRUB in the new partitions, and somehow inform the user that one should
set up chainloading from the original.
If some other OS's boot loader is in the MBR,
FreeBSD is installed in one or more primary partitions, which FreeBSD
refers to as 'slices'. Then the slices are broken down into partitions,
identified by lower-case letters. This subdivision is different from the
usual DOS/Windows/IBM scheme of dividing extended partitions.
In Linux fdisk, a
Some Links
http://www.bsd.org/
http://www.freebsd.org/
http://www.pcbsd.org/
http://www.openbsd.org/
http://www.netbsd.org/
--
FreeBSD not detected by os-prober
https://bugs.launchpad.net/bugs/432254
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I would suggest downloading the boot-only mini-CD image from here:
ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/7.2/
and doing a minimal install after booting from that (it will allow you
to install from an FTP site, such as that one). That will take up a
whole primary partition ('slice').
Actually I have given up on this issue, for all practical purposes. I
just installed 9.04 first, then did the online update with Update
Manager - which is advertised NOT to replace the legacy GRUB with GRUB
2. The procedure is described here:
http://www.ubuntu.com/testing/karmic/alpha5
I do
I would like to create an entry in grub.cfg by creating a file for that
in /etc/grub.d and running ubdate-grub2
I have tried modifying /etc/grub.d/40_custom as follows:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you
That was a 9.04 Alpha-4 CD.
On Thu, Sep 17, 2009 at 3:10 AM, Bryce Harrington
br...@bryceharrington.org wrote:
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete = Invalid
--
Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP
I have just booted a Karmic Koala 9.10 disk (with the Aug 1 kernel
build) on this system and eventually (it's only a 400 mHz system) it
comes up fine in 1024x768 resolution. The Display Preferences dialog
shows a number of possible lower resolution settings. I tried several
of the selections, down
Public bug reported:
Binary package hint: os-prober
I have a multiboot system with Windows XP, Ubuntu 9.10 alpha, and
FreeBSD 7.2 installed. After Karmic Alpha-4 (upgrading with apt-get up
to the time of the bug report) installing with Grub 2 in the MBR, the
FreeBSD partition is not recognized.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32000627/Dependencies.txt
--
FreeBSD not detected by os-prober
https://bugs.launchpad.net/bugs/432254
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Note that I can boot into Ubuntu or FreeBSD by
1) use the Windows NT Pro tools to replace the Windows MBR
2) use Linux (Knoppix or another live CD) to make the desired partition
bootable instead
of /dev/sda1
3) reboot.
I have to make sure a boot loader is in the Ubuntu partition /dev/sda2
It turns out I had actually built an openchrome driver some time ago
(I have to look at my Launchpad email to determine the date) in order
to deal with this or a related problem.
At any rate, I downloaded the current sources from the OpenChrome
server, copied in the patched via_driver.c file, and
Please see my comments in bug #296142 regarding my earlier installation
of the openchrome driver (in both ubuntu and debian).
Also, I tried the live CD for Karmic Koala 9.10, and the only real
problem with display is that it also chooses a too-high resolution for
the screen, so that only the
Thank you - since I'm away today, I may not get to this until tomorrow.
I assume this means I'll have to download the rest of the source and
build and install the driver .
On Mon, Aug 17, 2009 at 12:00 PM, Bartoszgan...@poczta.onet.pl wrote:
If it easier for you please replace the
Actually, I have no idea where to get the rest of the sources
(configuration and makefiles etc) to build this.
On Mon, Aug 17, 2009 at 12:32 PM, Peter Belewabcru...@gmail.com wrote:
Thank you - since I'm away today, I may not get to this until tomorrow.
I assume this means I'll have to
** Attachment added: ApportLog.txt
http://launchpadlibrarian.net/30441542/ApportLog.txt
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/30441543/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30441544/Dependencies.txt
** Attachment
Public bug reported:
Binary package hint: xserver-xorg-video-vesa
System with S3 ProSavage8 running 8.04.3 LTS crashes on logout
The 8.04.3 LTS system runs Ok, but crashes when switching to a text
console, when logging out (to change users), or when shutting down. (See
below)
This is the same
** Attachment added: lspci --vv output
http://launchpadlibrarian.net/30381465/lspci.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30381466/Dependencies.txt
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving
** Attachment added: lsmod output
http://launchpadlibrarian.net/30381507/lsmod.txt
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You received this bug notification because you are a
** Attachment added: /var/log/messages
http://launchpadlibrarian.net/30381619/messages
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You received this bug notification because you are
Information about file system usage
** Attachment added: fdisk and df output
http://launchpadlibrarian.net/30381714/fdisk.txt
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You received
** Attachment added: /var/log/kern.log
http://launchpadlibrarian.net/30381742/kern.log
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You received this bug notification because you are
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/30381853/Xorg.0.log
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You received this bug notification because you are a
** Attachment added: xorg.conf - using vesa driver
http://launchpadlibrarian.net/30381801/xorg.conf
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
https://bugs.launchpad.net/bugs/414330
You received this bug notification
From comments to bug 217004:
From Tormod Volden:
Peter, I updated the Hardy xserver-xorg-video-savage package on
https://launchpad.net/~tormodvolden/+archive/ppa to the latest version,
so you can try it (I haven't tested it myself).
From me to Tormod Volden:
Tormod - installing your savage
I finally submitted this problem with the vesa driver as bug 414330
half an hour ago, using the ubuntu-bug program.
On Sat, Aug 15, 2009 at 10:20 PM, Peter Belewabcru...@gmail.com wrote:
I've been unable to report the bug on the vesa driver - Launchpad
won't let me report any new bugs!
BTW
I'm downloading the Karmic alpha 4 ISO right now.
Also I downloaded and installed the new vesa driver -
r...@billy:/home/peter/crash# dpkg -i
xserver-xorg-video-vesa_2.2.1-1ubuntu1~hardy_i386.deb
(Reading database ... 112177 files and directories currently installed.)
Preparing to replace
I just booted the Karmic CD with no special settings, and it came up with the
Savage driver running at 800x600.
I've enclosed the
I'll try the safe-mode text boot next ...
** Attachment added: Xorg.0.log - running savage driver
http://launchpadlibrarian.net/30397835/Xorg.0.log
--
When
When I put 'text' in the command line (after selecting safe mode with
the menu) I eventually get a login prompt. How do I log in at that
point?
--
When using vesa driver system with S3 Inc. VT8375 [ProSavage8 KM266/KL266]
crashes when leaving graphics mode
I booted the Karmic alpha 4 CD in safe mode, and X came up eventually in
800x600 resolution, apparently using the savage driver, after trying
vesa first. The log is interesting ... a lot of tests resulted in a
useable mode selection.
I would certainly appreciate the revival of the old boot-time
Actually, I was able to insert the xorg.conf file while running from the
CD. I mounted the disk partition with /etc/X11 on it, and copied
xorg.conf into the live CD's /etc/X11, switched to a text console, and
restarted X with 'service gdm restart'. The Gnome screen came up with
half a dozen
Here's xrandr.log
In this case, I renamed the xorg.conf file to xorg0.log, to disable it,
switched to a text console, shut down X with 'service gdm stop', and ran
the command
xinit -e 'sh -c xrandr --verbose xrandr.log '
** Attachment added: xrandr.log after performing this procedure.
Karmic Koala 9.10 live CD:
I have just tried the 9.10 Karmic alpha 4 live/desktop cd on this
Averatec laptop. As before, it boots properly and starts the X server,
but with too high a screen resolution. The maximum resolution of the
screen is 1024x768.
It is necessary to put an xorg.conf file
I created a minimal xorg.conf file (attached), and placed it in the
livecd's /etc/X11/ directory (in RAM). I then ran 'sudo gdm restart'.
When gdm had restarted, and Gnome stuff appeared, the resolution was
then 1024x768. You can see the various resolution settings which I could
select, in the
Xorg.0.log generated starting gdm without the xorg.conf in place.
Note the several allowed screen resolutions greater than 1024x768, which
this display cannot handle (except by cropping the display to 1024x768.
Either:
1) the system has to determine the maximum screen resolution automatically,
Here is the Xorg.0.log file generated when restarting gdm with the above
xorg.conf file in place.
** Attachment added: Xorg.0.log after starting with xorg.conf in place
http://launchpadlibrarian.net/30406199/Xorg.0.log
--
[K8M800] Panel on K8M800 is not supported (Averatec 3280)
I've been unable to report the bug on the vesa driver - Launchpad
won't let me report any new bugs!
BTW this system is set up to triple-boot into XP, Ubuntu, and FreeBSD
7.1. I just set up Xorg and Gnome on the FreeBSD partition - and the
vesa driver on that behaves the same way - the system
I recently did a new installation on the gBox computer mentioned above.
It now runs hardy 8.04.3 LTS with a vesa driver - I installed it by
installing first 6.06.1 LTS (in safe mode with screen resolution
specified explicitly) then upgrading. This system works, but crashes
when switching to a text
Thanks, Tormod - I just downloaded
xserver-xorg-video-
savage_2.3.1~git20090813.36ab23a9-0ubuntu0tormod~hardy_i386.deb
to my laptop ... is that the right one?
I'll install it once I get back to that system.
On Fri, Aug 14, 2009 at 11:37 AM, Tormod Voldenbugpost.tor...@gmail.com wrote:
Tormod - installing your savage driver solved the problem. After
installing it, I disabled Xorg running at runlevel 2 by renaming the
symlink to gdm in /etc/rc2.d and restarting the system (with the reset
button this time), then booting and determining that 'reboot' works
properly from the shell,
I have just installed Ubuntu 7.10 on this system. On starting the
installer, I specified the screen resolution as 1024x768x24. The
installation went well, though this system is slow by today's
standards.
Now I am doing an online upgrade to 8.04 LTS. I'm not sure what driver
was selected. In the
In my case, the upgrade to 8.04 after the installation of 7.10 went
well. The display driver selected in xorg.conf is 'vesa'.
On Wed, Aug 12, 2009 at 12:28 AM, Peter Belewabcru...@gmail.com wrote:
I have just installed Ubuntu 7.10 on this system. On starting the
installer, I specified the
Public bug reported:
Binary package hint: xserver-xorg-video-ati
I am able to make video work on this system running the 6.06 LTS
live/desktop CD, manually selecting the screen resolution.
But I am unable to get Xorg to work under later releases. In this case,
I installed 8.10 using the
Result of lspci -vv
** Attachment added: lspci -vv output
http://launchpadlibrarian.net/30089592/lspci.txt
--
Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP
https://bugs.launchpad.net/bugs/411164
You received this bug notification because you are a member of Ubuntu
Bugs,
lsmod output
** Attachment added: lsmod output
http://launchpadlibrarian.net/30089614/lsmod.txt
--
Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP
https://bugs.launchpad.net/bugs/411164
You received this bug notification because you are a member of Ubuntu
Bugs, which is
xorg.conf file based on one generated running 6.06 LTS
** Attachment added: xorg.conf
http://launchpadlibrarian.net/30089711/xorg.conf
--
Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP
https://bugs.launchpad.net/bugs/411164
You received this bug notification because you
xorg.conf.new - generated on FreeBSD 7.1 using command
Xorg -configure
on the same system.
Running the same command on Ubuntu crashed.
** Attachment added: xorg.conf.new from FreeBSD
http://launchpadlibrarian.net/30089746/xorg.conf.new
--
Xorg won't start on PC with ATI Technologies Inc
Xorg.0.log - from trying to run with vesa driver.
** Attachment added: Xorg.0.log - running vesa
http://launchpadlibrarian.net/30089776/Xorg.0.log
--
Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP
https://bugs.launchpad.net/bugs/411164
You received this bug notification
Xorg.0.log - trying to use ati driver
** Attachment added: Xorg.0.log - running ati driver
http://launchpadlibrarian.net/30092974/Xorg.0.log2
--
Xorg won't start on PC with ATI Technologies Inc 3D Rage IIC AGP
https://bugs.launchpad.net/bugs/411164
You received this bug notification because
601 - 700 of 907 matches
Mail list logo
