** Branch linked: lp:ubuntu/ubiquity
--
Black screen, and bad usplash.conf after installation
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
Gutsy task.
** Changed in: ubiquity (Ubuntu Gutsy)
Status: In Progress = Won't Fix
** Changed in: ubiquity (Ubuntu Gutsy)
Confirming for Ubuntu Hardy PPC
Fresh install on PowerBook G4 (nvidia graphics 867mhz). I changed the
conf file to match my resolution but the colors are still messed up. I
think they have to be increased to 16 bit color? I'm not sure how to do
that however :/
--
Black screen, and bad
# Usplash configuration file
xres=1280
yres=1024
Reflects my Ctrl-F1 thru Ctrl-F6 screen settings. While my X-Windows
screen is set for 1680x1050.
My Display Adapter is a Nvidia 8600 GT
Thanks,
Bruce
--
Black screen, and bad usplash.conf after installation
Hi Saïvann
I did not fix the problem in gutsy, I used nosplash at grub instead. So perhaps
that means that this was an old usplash.conf as you say.
I changed the resolution in /etc/usplash.conf in hardy and the problem
went away. My resolution is 1440x900.
--
Black screen, and bad
Thank you for your confirmation, that means that the bug is still fixed.
--
Black screen, and bad usplash.conf after installation
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I can confirm this problem is still in latest hardy, upgraded yesterday
--
Black screen, and bad usplash.conf after installation
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Åskar : Thanks for your comment, can your provide the following
informations?
1. Did you fix the problem while you used Gutsy with the workaround? If not, no
need to go further, installing a brand new Hardy system should not have this
bug, but if you already have wrong values in
xserver-xorg.postinst no longer sets up xserver-
xorg/config/display/modes; instead, the X server deals with mode
configuration at run-time. This means that usplash.postinst no longer
has anywhere to get the correct modes.
In the desktop CD case, we can cope with this since we have a running X
7.10 had xserver-xorg/config/display/modes, so the usplash task is not
relevant for gutsy.
** Changed in: usplash (Ubuntu Gutsy)
Status: New = Invalid
--
Black screen, and bad usplash.conf after installation
https://bugs.launchpad.net/bugs/150930
You received this bug notification
Colin Watson : The current issue with Hardy is different from the
initial issue described in this bug report. I believe that we should
work on this in bug 188764 or, if you prefer, set bug 188764 as a
duplicate of this one.
--
Black screen, and bad usplash.conf after installation
Bouncing around between bugs is boring, but sure, whatever you like ...
** Changed in: usplash (Ubuntu)
Status: In Progress = Invalid
** Changed in: usplash (Ubuntu)
Assignee: Colin Watson (kamion) = (unassigned)
Target: ubuntu-8.04 = None
--
Black screen, and bad
I just wanted to say thanks. Ubuntu 8.04 fixed this problem for me.
The half-screen I was getting on login that I had to hit CTRL+ALT+DEL to
resolve is also fixed.
--
Black screen, and bad usplash.conf after installation
https://bugs.launchpad.net/bugs/150930
You received this bug notification
I have two graphic cards.
One is nVidia 6600
Other is nVidia 8600GT
The 6600 works with usplash
THe 8600 does not work with usplash. It does work with X though.
THis is on a 7.10 xubuntu install.
Also, I noticed I don't have my text consoles when using the 8600.
When removing the 8600, and
Bram Stolk : That means that your bug is bug 147623. Thanks :)
--
Black screen, and bad usplash.conf after installation
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I re-installed Gutsy one week ago in my Intel845 machine with only one
hard disk and let Gutsy to be my only OS,in these days ,this bug has
not re -occurred.I have not changed the usplash.conf file ,because the
1280*1024 setting is correct.
--
Black screen, and bad usplash.conf after
I've got the same problem, infact i can't even boot of the livecd i had
to install of the alternate cd. In all honesty this is a huge bug, i
could imagine alot of people being put of ubuntu because the live cd not
working. If it makes a difference i using dvi.
here are my specs.
Samsung
Just to let people know who might not. If none of the work arounds here seem to
help you particular computer. You can always type sudo gedit
/boot/grub/menu.lst Go to the this line in the document:
kernel/boot/vmlinuz-2.6.22-14-generic
Colin Watson : Numerous comments in different bug reports says that
usplash often get 640x480 resolution in Hardy. My own laptop which is
always in 1440x900 resolution with Xorg did have a /etc/usplash.conf of
640x480 in Hardy Alpha 4. I suggest that we take a look at this before
the final
Saïvann Carignan:
Thank you for clarifying. I was unaware this bug report was for the
Hardy Desktop i386 edition.
I've installed Hardy Desktop i386 Alpha 4 as you recommended and can
confirm this bug is NOT an issue for this edition on my hardware. I
will continue to watch bug 147623 instead.
Harvey Muller : Thanks for your comment. You are using a amd64 bit
ubuntu edition with nvidia geforce 8400M GS, this is a known but with
nvidia cards which you can find here : bug 147623. In order to make sure
that you reproduced the good bug, can you try the same with ubuntu 32
bit? Thanks for
Colin,
In a fresh installation of Hardy Desktop amd64 Alpha 4, the problem is
still present on the Dell Inspiron 1420 (nVidia GeForce 8400M GS). The
screen blanks during normal boot period until gdm starts. Normal
behaviour returns after manual fix.
Screens and Graphics reports the expected
** Tags added: metabug
--
Black screen, and bad usplash.conf after installation
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
If you are experiencing this bug and wish to verify whether it's due to
the problem originally reported here, then please compare the resolution
shown in System - Administration - Screens and Graphics (assuming you
haven't changed it) with that in the file /etc/usplash.conf. They should
be the
** Summary changed:
- Black screen, and bad usplash.conf
+ Black screen, and bad usplash.conf after installation
--
Black screen, and bad usplash.conf after installation
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Colin,
comparing these two values is impossible for me because displayconfig-gtk is
not running properly (Bug 178061):
[EMAIL PROTECTED]:~$ cat /etc/usplash.conf
# Usplash configuration file
xres=640
yres=480
[EMAIL PROTECTED]:~$ displayconfig-gtk
*** Error: couldn't find any ServerLayout
The black usplash screen problem with any {k}{x}ubuntu for AMD64 is bug
#147623. This bug has enough information, unless you know something that
has not been said in this bug report. However, you can contribute by
testing new releases when this bug will be fixed. From now on, the bug
is on the
I posted this in Bug # 147623 as well (as I'm not sure which one is the
most appropriate) - but I just tried Kubuntu 64 Hardy Alpha 3 and got
this bug again. Booting off of the live cd with any of the default boot
options results in a black screen (with monitor entering sleep mode
eventually) and
Yesterday I downloaded Hardy 64-bit, and today I tried it. It still boots with
no splash and no progress bar, so it looks like this problem hasn`t been fixed,
yet.
Hardy (LiveCD) has (on my system) also another bug with display: when I set it
to 1280x1024 resolution - 85 Hz, it switches to 84Hz
wangi : Thanks for your comment and for your hard testing.
From what you say, it seems clear that your bug is the bug #147623 and
not this one, this was important to confirm this. bug #147623 does
already have a lot of debugging informations so I think that we should
wait. Concerning the new
Will do, downloading the ISO now. I can see the relationship and perhaps
for many these are the same bugs. One difference is I boot into X fine,
it's just that i'm in powersave until then. One of the dupes of this bug
is a x64 only one, and when i386 is used it works.
--
Black screen, and bad
As expected the i386 build works, although with a usplash resolution of
640x480.
(However it's got its own problems and is less usable than the x86
version without usplash - after logon at gdm your stuck on the beige
screen)
--
Black screen, and bad usplash.conf
Sure:
[EMAIL PROTECTED]:~$ lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600 GT (rev a1)
Thanks/L
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is
wangi : Can you install ubuntu for i386 architecture and see if the
problem still happens? I found the existence of bug #147623 which looks
a lot like your problem and only happens with AMD64 ubuntu.
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this
Thanks for these informations. Can you also provide the result of that
command in a terminal : lspci | grep VGA
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Hi Saïvann, yes the system still boots fine - monitor goes into
powersave, boots up, out of powersave and shows gdm. I will reply with
requested information later this evening. Thanks/L
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug
wangi : Thanks for your comment. Can you confirm that ubuntu still boot?
If you don't even get to your Desktop, that is another bug like bug
#179336. If your computer boot but that you just don't see usplash, it
looks like we're talking about the same bug.
In case it's really the usplash bug, can
As requested:
[EMAIL PROTECTED]:~$ cat /etc/usplash.conf
# Usplash configuration file
xres=640
yres=480
[EMAIL PROTECTED]:~$ cat /etc/X11/xorg.conf | grep -A 4 'Section Device'
Section Device
Identifier Configured Video Device
EndSection
Section Monitor
[EMAIL PROTECTED]:~$
**
Today in the morning I installed my old Radeon x550 instead current
NVidia 6600GT. And it works! At least system is booting from LiveCD...
freezing a little, but I hope that after installing everything will be
fine.
I surprised a little, because considering that ATI give more headache with
This problem occurredyesterday after a system update of 10
packages,so I tried to set the 640*480 resolution in the usplash.conf
file and ran the 'sudo update-initramfs -u -k `uname -r` command ,it
worked then.It seems ok today.
--
Black screen, and bad usplash.conf
I think the method mentioned in the comment by timbl is better
than mine.
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
As mentioned, none of the workarounds solved the issue for me on Fiesty
or Gutsy and I was left with powersave during boot. Tonight I have
downloaded the fresh Hardy Alpha 3 image (alternative 64bit) and done a
clean install. I still have the same symptoms - the fix in Hardy does
*not* make
Oh, do I need to / should I report this elsewhere specifically against
the Hardy alpha 3?
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Hello again!
update-initramfs now works fine, but...
I've tried to insert
xres=1024
yres=768
and I've tried to leave they blank, as ffstar said.
But it did not work
I've even tried 1680x1050 (native monitor resolution). Same result.
Have any idea?
--
Black screen, and bad usplash.conf
i think
sudo dpkg-reconfigure usplash
is sufficient
(after inserting the correct resolution in usplash.conf)
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
I leave
xres=(blank)
yres=(blank)
and then
sudo dpkg-reconfigure usplash
Did not help
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
It depends of ubuntu version? I installed latest 8.04 RC 2, because 7.10 showed
black screen as well.
8.04 alternate PC (Intel x86) install/live DVD said that I have incompatible
system! :-)
But I am on Core 2 Duo.
May be I should use 7.10 alternate?
Guys, I am in blank despair. 2 days with
Please don't ask for support in bug reports. You can get support through
Launchpads 'answer' section, in the official Ubuntu Forums
(ubuntuforums.org) or on IRC.
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a
Have you tried just setting xres and yres to the native (highest)
resolution of your monitor and then re-booting?
On Wed, 2008-01-09 at 18:15 +, warmrobot wrote:
I leave
xres=(blank)
yres=(blank)
and then
sudo dpkg-reconfigure usplash
Did not help
--
Black screen, and bad
Yes, I insert
xres=1680
yres=1050
and then
sudo dpkg-reconfigure usplash
then
reboot
same result :-(
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Ok. Thank you, guys. I think I am not ready to spent any more time for this OS.
See you next year. Viva la Vista!
:-)
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Like warmrobot (and commented on somewhere higher up in this thread), I
too am stuck with this bug - none of the workarounds make any difference
(and if it makes any difference I'm an IT professional). While warmrobot
might be asking the wrong questions in the wrong places it is pretty
poor form
You guys realize this is not required to get your system running?
If it doesn't work, just delete the word splash anywhere it appears in
/etc/boot/grub.conf. You will get text messages during boot instead.
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You
And what? X did not start anyway after login.
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This conversation is not helpful to anybody. I think that we should take
a look at the Code of conduct : http://www.ubuntu.com/community/conduct
We all want to fix this issue so we need to collaborate and contribute
to this bug report. To warmrobot, it's true that launchpad isn't like a
forum but
Hello, guys!
I try to use all the methods but id did not help.
Want to ask you. After I type:
sudo update-initramfs -u -k `uname -r`
then I get the message:
update-initramfs: Generating /boot/initrd.img-uname -r
Cannot find /lib/modules/uname -r
update-uniframes: failed for
I think you have typed the command wrong.
The symbols around uname -r must be backticks (`) not quotes ('). The
backtick key is next to the 1 key at the top left of the keyboard.
If you still can't get it to work, try changing `uname -r` to $(uname
-r).
--
Black screen, and bad usplash.conf
Oh, thank you!
I guess you right. I will try it in the evening.
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I reinstalled Gusty several days ago.After boot from CD, I found there was no
resolution settings for usplash in the /etc/usplash.conf file.so after
finishing the installation,I cleared the resolution settings for usplash
by editing the usplash.conf file, then ran the command
the comment by fsstar worked for me as well (thank you!). I've now got a
640x480 usplash, which is much better than a blank screen.
Additionally, I found after making the changes the machine failed to
shutdown the first time around, it didn't even respond to SysRQ
commands. However, this problem
Confirmed bug with:
Ubuntu 7.10 Gutsy Gibbon installed to hard disk from Desktop CD
Compaq Presario 900 Laptop
AMD 1700+ cpu, 512M ram, ATI Radeon Mobility 320M U1 video
Fixed with:
$sudo gedit /etc/usplash.conf
# Usplash configuration file
xres=1024
yres=768
Method1:
$sudo aptitude install
Gutsy: In Progress
Looks like it will.
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ubiquity (1.7.2) hardy; urgency=low
[ Evan Dandrea ]
* XS-Vcs-Bzr is now Vcs-Bzr.
* Strip out support for creating multiple users in migration-assistant.
* Save state in between runs of migration-assistant (LP: #151126).
* Added partman/check.d/03partition_too_small to warn the user
Great! Will this be backported to Gutsy though?
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Colin:
[Hardy / Alpha 1 / amd64 - daily 12122007]
The error is still present in the Hardy i386 and amd64 alpha 1 resease isos,
including today's daily version of amd64. The only way to get past the black
screen when booting the LiveCD is to hit F6 and remove 'splash' from the kernel
line.
Opps!
Has is minimum two monts as it's problem cannot do resolving! ^)
How many words uses about it... :)
Hardware Software environments writes many strings, but body persons don't
has a true looks to root of the problem... It situation is ruefully and it's
characteristically of Linux World!..
** Also affects: ubiquity (Baltix)
Importance: Undecided
Status: New
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I just wanted to confirm that this bug still seems to apply to Hardy
Alpha 1 - If we want Hardy to be a big success (particularly as a LTS)
then we need bugs like this to be absent from Hardy.
Pat
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug
My fault, I never resurrected my ubiquity patch after 7.10 RC. I've
committed it now, so it should be in alpha-2 for testing.
** Changed in: ubiquity (Ubuntu)
Status: In Progress = Fix Committed
Target: ubuntu-7.10-rc = hardy-alpha-2
--
Black screen, and bad usplash.conf
Thanks Colin, that was good and speedy work :)
Pat
On Dec 3, 2007 10:27 AM, Colin Watson [EMAIL PROTECTED] wrote:
My fault, I never resurrected my ubiquity patch after 7.10 RC. I've
committed it now, so it should be in alpha-2 for testing.
** Changed in: ubiquity (Ubuntu)
Status: In
** Tags added: alpha-1-desktop fix-to-verify
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
How come the final release is out and this hasnt been finalized? not
even in the updates?
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I can confirm that on Intel E6750 platform, GA-P35-DS3 mobo and Gigabyte 8600GT
card the fix by Orange2k works (plus startup-manager of course).
Startup manager did not work by itself, I think it's adding the modules to
initram.
Thanks Orange2k! I've been intimidated by the lack of usplash
None of the three workarounds here (startup-manager; usplash.conf;
orange2k) work me. Graphics card is an nVidia GeForce 8600 GT running on
a Dell 2405FPW display at native 1920x1200. System is a Dell Inspiron
530. I also had this problem with Fiesty and the Gutsy install (64bit)
was upgraded from
Compaq Presario v5015us Gutsy fixed by changing resolution in
usplash.conf and updating initramfs.
changed /etc/usplash.conf (yres had been set to 1024):
# Usplash configuration file
xres=1280
yres=800
Ran update-initramfs:
sudo update-initramfs -c -k all
Please note that when I changed
Dell Latitude D810 gutsy fixed:
Altered the resolution in /etc/usplash.conf to 1024x768 and also ran sudo
update-initramfs -u -k `uname -r`
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs,
On my father's widescreen, /etc/usplash.conf defaults to:
# Usplash configuration file
xres=1680
yres=1680
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
startup manager worked great
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
-# defoptions=quiet splash
+# defoptions=splash vga=791
## should update-grub lock old automagic boot options
## e.g.
In response to Kamal's post:
I also had this black screen during boot.
There's some debate on the vga=791 option not properly working for
Gutsy. I removed it and this happened to work for me:
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=8d6cb6c2-79d8-4e49
-ac5d-9ad8f2d3df42 ro quiet
Hello!
orange2k' solution works here on Nvidia 8500GT! Non of the other
solutions worked!
I had a fresh installed (from live cd, 7.10, 64bit) ubuntu.
Thanks!
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a
I have a black screen during boot.
My machine is a Dell Precision M6300 with a native resolution of 1920x1200. I
changed my configuration to the settings suggested but without results.
My /etc/usplash.conf is set at 1024x768.
My /boot/grub/menu.lst has
kernel /vmlinuz-2.6.22-14-generic
Just letting you know that I switched my father's computer from Ubuntu
to Xubuntu and used the official Xubuntu alternative CD and his USplash
still doesn't show. He has a HP Pavilion 503n with a 22 widescreen
monitor. My own fix by using startupmanager and setting the resolution
to 640x480 @
Confirmed with a Dell Latitude D610 Laptop, among other big bugs - like
HAL not working - and minor troubles.
Booted in Recovery Mode and executed GDM for Gnome to work. Also I
corrected the /etc/usplash.conf file and seems like it works.
The strangest thing is that during Live-CD boot I can
My Compaq 1700US laptop screen was also not detected. I also remember it
working in 1024x768 by default in Feisty, and in 640x480 (I think,
guessing here) in the LiveCD of Gutsy, however not in the installed copy
(like xnt).
--
Black screen, and bad usplash.conf
I confirm on Thinkpad X30 (Intel VGA)
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I was experiencing a similar problem. Finally got the ubuntu logo and
progress bar to show on boot and shutdown, but if I press ctrl+alt+f1 I
am presented with a blank screen with a flashing _ cursor - ie no login
prompt. Is this related, if so, any ideas for fixes?
--
Black screen, and bad
I can confirm on a Dell E772c monitor (non-plug-n-play unfortunately).
It'd be nice if they asked about monitor configurations during setup to
be sure everything's OK instead of confusing users with a black screen
for whole minutes.
--
Black screen, and bad usplash.conf
Kuoso: Your question is a separate bug
https://bugs.launchpad.net/bugs/129910
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Confirmed:
Fresh Ubuntu Gutsy 32-bit desktop version on my Asus M6R laptop (ATI
Radeon 9100)
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Confirmed:
Fresh Ubuntu Gutsy Final installation, ATI Mobility Radeon M10 RV350, Laptop,
1280x800 LCD, Centrino (Pentium M Dothan).
--
Black screen, and bad usplash.conf
https://bugs.launchpad.net/bugs/150930
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Rene,
I can confirm that I should have paid greater attention to detail. I
apologize to any I may have inconvenienced by communicating BAD
information. On another hunch last night, I checked
/etc/apt/sources.list to confirm that I was indeed using amd64, and not
i386. To my horror and deep
I have the same problem, but I actually get an INVALID SCAN FREQ message
on the black screen, presumably from the monitor (Hitachi CM772).
Checked usplash.conf, and has 1024x768, well within the monitor
capabilities (max 1600x1200 @ 85 Hz). So it may be a problem with the
frequency setting, and
Malaeum, I think that setting to 1280x1024 16-bit may be a bit too much,
(I`ve set it later on to 1024x768) so you could try with some lower
resolution in the StartupManager. With 1280x1024 the splash is too
small, and besides, with that resolution, I couldn`t get the Fingerpring
usplash to show
I'll give it another go later on. I am relatively new to Ubuntu, I had
Fiesty for all of about 5 days before Gutsy came out but I am pretty
sure that the splash screen didn't work for me there either. I just
was playing around at that point evaluating if I wanted to dump gentoo
and finally make
I applied orange2k's fix
(https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/150930/comments/56),
and it just works now. Thank you, orange2k.
I still have a problem when shutting down/restarting: KDE shows black
screen before the Kubuntu shutdown-splash is correctly shown; do you
know if it
the problem here is its supposed to detect the correct settings and set
it accordingly. however for some reason it doesn't. it worked fine on
fiesty but on gutsy it doesn't detect it for some reason. on fiesty it
set it to 1024 768 (this is the max resolution of my monitor). however
on gutsy it
I have a new install of Gutsy amd64 on a brand new Thinkpad T61. The video is
nVidia Quadro NVS 140M (rev a1).
I have tried all the fixes here without success. My most recent attempt was
brettalton's post. The command after rebooting does not seem to have generated
a menu.diff file, but it did
I`ve tried every solution offered so far, with no luck. But I found a post on
kubuntuforums that solved my problem.
BTW. I have a Samsung Syncmaster 757 NF, Geforce 8500 GT, Athlon 64-bit X2
4400, 1 GB RAM...
Here is the solution I`ve found:
(before I did what follows, I used StartupManager
Brett and others,
On a hunch I checked the date on the amd64 desktop iso I downloaded on
the 18th of October last night (this was supposed to be the final
release). To my amazement, it is dated 15 October. This is what people
are getting when they click the download link.
So I downloaded
Newer versions of the .iso should eliminate these issues on some
(probably not all) of the machines during the liveCD bootup process.
However if there is a fix (I'm assuming its most likely a config file,
as opposed to a newer version of a binary), we should be able to port
this to current
1 - 100 of 157 matches
Mail list logo
