Bug#712529: installation-reports: Wheezy netinst problems when desktop selected, works when not selected.
Package: installation-reports Severity: normal Tags: d-i Dear Maintainer, Installed from the CD in expert mode, standard packages and ssh server, but w/o desktop, installation completed successfully. Then decided to make change, so restarted install with minor partitioning changes, and selected desktop option as well. Got warning that there was a problem. Went back, retried, same error. Went back, remove desktop, and the install completed successfully. Manually installed X11 without a problem. -- Package-specific info: Boot method: cd Image version: downloaded stable debian 7.0 wheezy netinst iso june 15 2013 from mirror off of debian.org Date: 16 june 2013 Machine: AMD FX 8-core processor and ASUS MB (homebuilt) Partitions: $ df -Tl Filesystem Type 1K-blocksUsed Available Use% Mounted on rootfs rootfs 960504 176992734720 20% / udev devtmpfs 10240 0 10240 0% /dev tmpfstmpfs 1619728 324 1619404 1% /run /dev/disk/by-label/GAME-ROOT ext4960504 176992734720 20% / tmpfstmpfs 5120 0 5120 0% /run/lock tmpfstmpfs 3435440 0 3435440 0% /run/shm /dev/sda5ext2233191 81220669 1% /tmp /dev/sda7ext4 1921036 1001248822204 55% /usr /dev/sda8ext4960504 418880492832 46% /var /dev/sda9ext4 2882592 69968 2666192 3% /home /dev/sda10 ext2 403705522520 38317320 1% /shared $ Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[E] Install tasks: [ ] Install boot loader:[ ] Overall install:[O] Comments/Problems: The problem was in the package selection process. Didn't try to test the other permutations. This is the second linux system that is being installed on this box. The first install is slackware 14. Swap is being shared. All of the debian partitions are logical partitions. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7.0 (wheezy) - installer build 20130430" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux gaming 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS880 Host Bridge [1022:9601] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:843e] lspci -knn: 00:01.0 PCI bridge [0604]: ASUSTeK Computer Inc. RS880 PCI to PCI bridge (int gfx) [1043:9602] lspci -knn: 00:09.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 4) [1022:9608] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:0a.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 5) [1022:9609] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] [1002:4390] (rev 40) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8443] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8443] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8443] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8443] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8
Bug#367947: Ultra10 X Problems after dist-upgrade
Package: xserver-xfree86 Version: 4.3.0.dfsg.1-14sarge1 I recently did an apt-get update ; apt-get dist-upgrade, and when all was said and done, X no longer worked. I still get the speckled screen and the X pointer for just a second, and then it quits with a signal 11. The startx output, config file, and log file are available at http://www.stremler.net/temp/u10errors.tgz -- Stremler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367947: Ultra10 X Problems after dist-upgrade
begin quoting Brice Goglin as of Thu, Jan 18, 2007 at 12:34:09AM +0100: > Hi, > > Last year, you reported a bug to the Debian BTS regarding X not working > anymore on a Ultra 10 machine after dist-upgrade to 4.3.0.dfsg.1-14sarge1. > Did you reproduce this problem recently? If not, I will close this bug > in the next weeks. As of last week, X still didn't work on that machine. Thanks for the followup. I wish I could report a more positive result. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367947: Ultra10 X Problems after dist-upgrade
begin quoting Brice Goglin as of Wed, Jan 24, 2007 at 07:17:00PM +0100: > Stewart Stremler wrote: > > Still, no joy, although now it seems to be complaining about libGLcore, > > > > glcore should not be loaded explicitly nowadays. You should remove "load > glcore" from xorg.conf. The server will load it when it needs it. Done. > The _gl_dispatch error looks strange to me. It looks like an > incompatible GL library is installed. You seem to have an ATI board. Did > you try a ATI binary driver in the past? Not that I am aware of. (Then again, it's been quite some time since I last fought with this machine.) There's an xserver-xorg-video-ati package installed. > Are you sure you don't have any > DRI/GL related library package that did not get upgraded? For instance > because it is "hold". Which xorg and mesa packages do you have > installed? The output of "dpkg -l | grep xorg" and "dpkg -l | grep mesa" > might help. Done, and done. For that output (and other output) see: http://www.stremler.net/temp/Debian/03/ > > Any further suggestions? > > It is better if you disable DRI in xorg.conf too? It changes, in that it but it's not better. It complains about the DRI module not being loaded instead of complaining about screen 0 not being DRI capable. > Eventually, you could try a recent kernel. Etch has a 2.6.18-3, it could > be better than your 2.4.24. Last time I tried that, the system wouldn't boot at all. I haven't tried recently, however. Thanks for all your help, by the way. -- Stewart Stremler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367947: Ultra10 X Problems after dist-upgrade
begin quoting Brice Goglin as of Tue, Feb 20, 2007 at 12:07:26AM +0100:
> Brice Goglin wrote:
> >>> Let's see what you get with the ATI driver, the other warnings might be
> >>> related to the VGA driver. Try without DRI first.
> >>>
> >>>
> >> Okay. I now get a new and different behavior: an all black screen. I
> >> commented out the 1600x1280 resolutions ('cuz it's an older CRT that
> >> might not handle it, I guessed), and no change. Oh, and it beeps at
> >> me -- I can't alt-Fn or control-alt-Fn to another virtual desktop.
> >>
> >>
> >
> > Are you sure that your vertical and horizontal sync ranges are ok? Or
> > did you just choose them randomly? Do you by chance remember what you
> > had in XF86Config when it worked? Looking at the /etc/X11/XF86Config*
> > files that remains on your machine might help, we never know...
> >
> > Also, you could eventually try much lower resolutions. Once we'll have
> > found a working setup, even very minimal, it might be better to fix the
> > remaining problems.
> >
> > Just to be sure, could you look at http://wiki.debian.org/XorgOnSparc
> > and see whether it talks of some hardware you have?
> >
> > There are still things about DRI in your Xorg.0.log, apparently caused
> > by AIGLX being enabled by default. You could try add Option "AIGLX"
> > "false" to the ServerLayout section and see what happens. But there are
> > very few chances that it actually helps.
> >
> > I am running out of ideas here, apart from trying a 2.6 kernel.
> > Eventually, you could install xserver-xorg-video-vesa and try the vesa
> > driver instead of ati.
> >
>
> Hi Stewart,
>
> Is there anything new about this bug? Did you manage to look at what I
> said above?
Sorry, got a little busy.
I let the system choose the horizontal and vertical sync ranges;
however, it *used* to come up with the black-and-white stippled
background with the X cursor, which implies (to me) that the sync
values are okay, 'cuz that's what I expect to see when I type
"startx".
I'm not sure the XF86Config values will be any good, as I did full
purges of all things X and then reinstalled a few times.
Using control-alt-keypad-{+/-} should step through the resolutions,
so I should get to a much lower resolution that way, yes? It doesn't
work, but it beeps like mad when I hit the alt key anyway, and I
can't even alt-Fn or control-alt-Fn, so there's something screwy
about the input now.
The Wiki has a mention of someone using an Ultra10, but having to
disable some sort of card. I have not chased this down, as I
don't know if I have that card, nor what the card would look like, nor
am I sure my work would like my playing with the hardware like that.
That does seem to be the most promising line at the moment, however.
IIRC, I added the Option AIGLX false as recommended, and as you guessed,
no change.
I have not tried installing the 2.6 kernel (I'd like to hear of someone
running 2.6 on an Ultra10 first, as I had very bad luck with that from
before).
I have not tried the xserver-org-video-vesa yet (I had wanted to try
that before responding, and then Stuff Came Up, and it got pushed
off my plate for the moment).
I truly appreciate the efforts you've made in trying to chase this
down. I hope I can solve this before the whole issue is rendered
moot, as long-running problems are apt to be overcome by events.
Thanks again. I meant to find out if you were going to be at SCALE,
but I forgot to ask. Were you, by any chance?
-Stewart
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367947: Ultra10 X Problems after dist-upgrade
begin quoting Brice Goglin as of Thu, Jan 25, 2007 at 02:12:07AM +0100:
> Stewart Stremler wrote:
> > Not that I am aware of. (Then again, it's been quite some time since
> > I last fought with this machine.) There's an xserver-xorg-video-ati
> > package
> > installed.
>
> Since you have an ATI board and this ATI driver package, why do you use
> the VGA driver? :)
Erm... because I just want the bare minimum working, so I haven't
played around with the options much.
> Section "Device"
> Identifier "Generic Video Card"
> Driver "vga" <<<< try with "ati" instead
> EndSection
Done!
> > It changes, in that it but it's not better. It complains about the
> > DRI module not being loaded instead of complaining about screen 0
> > not being DRI capable.
>
> Right, AIGLX won't be enabled, but it is not important.
> The possibly bad warnings that remain are:
>
> INVALID IO ALLOCATION b: 0x2c00400 e: 0x2c004ff correcting
> (WW) VGA(0): Cannot read colourmap from VGA. Will restore with default
Well, the Invalid IO Allocation warning is still there. :-/
> But there is something strange, you have lots of line like:
> (II) VGA(0): Not using default mode "640x350" (insufficient memory
> for mode)
> followed in the end by:
> (WW) VGA(0): Mode pool is empty
> All this could be caused by:
> (==) VGA(0): videoRam: 64 kBytes.
> Your ATI board probably has much more memory than that (maybe 8MB). The
> ATI driver should detect it fine. If not, we could even hardcode it in
> xorg.conf.
Hm. The dmesg output says it has "4M SGRAM", if I read the output
correctly. ( http://www.stremler.net/temp/Debian/03/save-dmesg )
> Let's see what you get with the ATI driver, the other warnings might be
> related to the VGA driver. Try without DRI first.
Okay. I now get a new and different behavior: an all black screen. I
commented out the 1600x1280 resolutions ('cuz it's an older CRT that
might not handle it, I guessed), and no change. Oh, and it beeps at
me -- I can't alt-Fn or control-alt-Fn to another virtual desktop.
Output and config file can be found at
http://www.stremler.net/temp/Debian/04/
I added the (filtered) output of ps to show my processes and those
processes running with "x" in the name.
--
Stewart Stremler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#642389: installation-reports: Garbage screen after install
Package: installation-reports Severity: normal Tags: d-i Boot after installing wheezy results in scrambled screen. (unreadable, looks like noise) (console, no xorg, or desktop options) Installing from squeeze and upgrading results in the same problem. However booting with the older 2.6 kernel worked fine, (3.0 didn't) After installing xorg and fglrx (without gnome yet booting to console, or later booting to gdm) 3.0 also works fine. Possibly the radeon driver in the kernel is no good and when fglrx takes over it works fine? (works fine to booting to console, or booting to gdm) -- Package-specific info: Boot method: debian-amd64-netinst yesterdays build 20-sep-2011 Image version: debian-amd64-netinst 20-sep-2011 Date: Machine: Lenovo x120e Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="6.0 (squeeze) - installer build 20110106+squeeze3" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux think4 2.6.32-5-amd64 #1 SMP Tue Jun 14 09:42:28 UTC 2011 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1510] lspci -knn: Subsystem: Advanced Micro Devices [AMD] Device [1022:1510] lspci -knn: 00:01.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:9802] lspci -knn: Subsystem: Lenovo Device [17aa:21df] lspci -knn: 00:01.1 Audio device [0403]: ATI Technologies Inc Device [1002:1314] lspci -knn: Subsystem: ATI Technologies Inc Device [1002:1314] lspci -knn: 00:06.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:1514] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] lspci -knn: Subsystem: Lenovo Device [17aa:21df] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: Lenovo Device [17aa:21df] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] lspci -knn: Subsystem: Lenovo Device [17aa:21df] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: Lenovo Device [17aa:21df] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] lspci -knn: Subsystem: Lenovo Device [17aa:21df] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 42) lspci -knn: 00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) lspci -knn: Subsystem: Lenovo Device [17aa:21df] lspci -knn: 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] (rev 40) lspci -knn: Subsystem: Lenovo Device [17aa:21df] lspci -knn: 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] (rev 40) lspci -knn: 00:15.0 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a0] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:15.1 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a1] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 0 [1022:1700] (rev 43) lspci -knn: 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 1 [1022:1701] lspci -knn: 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 2 [1022:1702] lspci -knn: 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 3 [1022:1703] lspci -knn: 00:18.4 Host bridge [0600]: Advanced Micro De
Bug#642389: installation-reports: Garbage screen after install
I tried it again today. Removed fglrx-driver and related packages. Booted fine untill I actually purged them, then everything went back to the garbage screen problem with the 3.0 kernel. Used 2.6.32-5 kernel to boot and blacklist radeon, and update initramfs. After this 3.0 kernel is booting successfully again. Viktor On Mon, Sep 26, 2011 at 4:32 PM, Miguel Figueiredo wrote: > A Quinta, 22 de Setembro de 2011 06:16:13 Viktor Stremler você escreveu: >> Package: installation-reports >> Severity: normal >> Tags: d-i >> >> Boot after installing wheezy results in scrambled screen. (unreadable, >> looks like noise) (console, no xorg, or desktop options) >> >> Installing from squeeze and upgrading results in the same problem. However >> booting with the older 2.6 kernel worked fine, (3.0 didn't) >> >> After installing xorg and fglrx (without gnome yet booting to console, or >> later booting to gdm) 3.0 also works fine. >> >> Possibly the radeon driver in the kernel is no good and when fglrx takes >> over it works fine? (works fine to booting to console, or booting to gdm) > > I've had similar problems with my recent laptop: > > 01:00.0 VGA compatible controller: ATI Technologies Inc NI Seymour [AMD Radeon > HD 6470M] > > I've also seen here another person complaining about the same, also with a > newer ATI Radeon graphic card. > Please blacklist the module radeon to be sure it's the cause of the problem. > If this is confirmed we should reassign the bug report to the proper package. > > > -- > Melhores cumprimentos/Best Regards, > > Miguel Figueiredo > http://www.DebianPT.org > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642389: Info received (Bug#642389: installation-reports: Garbage screen after install)
I have looked into the problem further. After installing firmware-linux-nonfree now radeon works on 3.0 kernel. Viktor -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#367947: Ultra10 X Problems after dist-upgrade
begin quoting Brice Goglin as of Thu, Jun 21, 2007 at 08:09:47PM +0200: > Hi Stewart, > > Did you have a chance to try upgrading you system to Debian Etch with > its 2.6.18 kernel? Did it help getting Xorg to work on your ATI board? Sorry, I recently lost access to that machine. I will not be regaining access to it. -Stewart -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
