Like the title says, this is about "Feisty crashes after grub if usplash
enabled (amd64)". This has nothing to do with X.org, or problems with
X.org drivers, or non-amd64 machines. It seems it's limited to ATI's
R420/R423 cards (X800-series), though there was a mention about nvidia
GeForce Go 6100
What is this bug about? Is this bug about starting up an AMD64 system
with an ATI card and then being unable to ever get to X (even vesa X)
because the kernel crashed? Or is it about the previous problem AND
starting up an AMD64 system with an ATI/NVIDIA card and not seeing
usplash/progress output
You can start your system in standard mode with usplash disabled :
$ sudo gedit /boot/grub/menu.lst
#remove "splash" from the line you want to start, for example :
title Festy Fawn
root(hd1,1)
kernel /boot/vmlinuz root=/dev/hdd2 ro
--
Feisty crashes after grub if
Hello there, I am having the same issues with the same specs.
As almost everybody else I use an AMD 64 with the amd64-version of
ubuntu, a x850XT from ATI (using fglrx driver) and version 7.04 BTW.
Tell me if you'd like some log of any kind from me.
I try to boot from grub generic boot and I get
Tried to install from the i386 live-CD today, and it seems to work
flawlessly! The splash screen works perfectly, no hangups, and I can
even log out, thus using the fglrx driver. So it's pretty obvious it has
something to do with the amd64 version. Worth a note is that it didn't
work for me in edgy
The same thing occurs to me. After selecting what I want to start in
GRUB, i get a sign on my screen saying "No signal detected". I don't get
any LED's on my keyboard blinking though...
Starting in recovery mode and then startx works fine. Just adding a
vga=791 or vga=794 gets me a splsh screen, b
I don't think: many users here receive an alert email when other post a
reply. see you.
--
Feisty crashes after grub if usplash enabled (amd64)
https://bugs.launchpad.net/bugs/8
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
Is there anybody out there?
Is this post "closed" ? :O
--
Feisty crashes after grub if usplash enabled (amd64)
https://bugs.launchpad.net/bugs/8
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubu
Hi there!
Ubuntu 7.04 (x86_64)
ATI Technologies, Inc. Radeon X850 XT (R480)
fglrx 8.36.5 (XORG 7.2)
Some (i guess..) interesting news
On my Athlon 64 based PC I had Edgy (6.10 - x86-64 - custom Kernel
2.6.20amd64) installed, and I had the "notorious" problem with
U-SPLASH...all I could obtai
I saw an update, the device name seems to be ok .. also I've tried a
dpkg-reconfigure xserver-xorg but the bug is already here (kernel panic
while usplash).
Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies Inc R430 [Radeon X800 XL] (PCIe)"
The login screen size problem is fixed.
Section "Screen"
Identifier "Default Screen"
# VRW changed this to make login screen thge right size.
# Device "ATI Technologies Inc R430 [Radeon X800 XL] (PCIe)"
Device "aticonfig-Device[0]"
Monitor"Generic Monitor"
I did that - max resolution 1024x768, no difference. Thanks.
Stephen
--
Feisty crashes after grub if usplash enabled (amd64)
https://bugs.launchpad.net/bugs/8
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
Hi Stephen, using the "alternate" ISO, installing in text mode, you can
specify the max resolution used by X (If I remember well)
--
Feisty crashes after grub if usplash enabled (amd64)
https://bugs.launchpad.net/bugs/8
You received this bug notification because you are a member of Ubuntu
Bug
OS: Ubuntu 7.04 "Feisty Fawn" - amd64
Box: Shuttle SN25P, AMD4200X2
Video: Sapphire X800XL
Monitor: 10+ year old generic 17" CRT
I had the same problems of crash, monitor off, flashing keyboard LEDs. I
applied the suggested changes:
/boot/grub/menu.lst -> VGA=792
/etc/usplash.cof
xres=1024
y
@Lorenzo: If you installed the kernel source, it will be at
/usr/src//Documentation/kernel-parameters.txt.
Also, given your description, your current issue (waking up to a kernel
hard crash, with or without usplash, with or without vga=nnn) does not
seem related to this bug.
--
Feisty crashes af
@hggdh: 1) my kernel parameter is "splash", not "usplash"; 2) waking up
I got ALWAYS kernel panic (with or without "splash" or "vga" kernel
parameters);
@Lostpoet: me (I think others too) have another kernel panic keyboard
signal: Caps Lock + Scroll Lock blinking together, NOT Num Lock + Caps
Lock
I also have this problem. Adding "VGA=792" fixed it and now I have no
issues.
Chipset: Biostar K8VGA-m
Processor: AMD 64 3400+ (2.4GHZ)
GPU: ATI Radeon X800 Pro
OS: Ubuntu 7.04 "Feisty Fawn" - amd64
--
Feisty crashes after grub if usplash enabled (amd64)
https://bugs.launchpad.net/bugs/8
You
I have i386 with NVIDIA card. This happens to me when I boot (but not
every time) and it just happened once when I logged out to switch users
and the login screen tried to reload. The screen just goes blank and
the num lock and caps lock lights start blinking. The only thing I can
do to get out
@Lorenzo: if you disable usplash completely (by booting *without* the
usplash kernel parameter) do you still get a kernel crash on waking up
from suspend?
Reason is: right now this bug is pretty much contained to X800-based
cards, on AMD64 code, *and* with usplash active + no vga=nnn.
--
Feisty
other info:
I can see the splash adding de "vga=NNN" kernel parameter too, but the
bug "wakes up" when resuming from Suspend mode anyway... :(
So... sorry but I come back to alternate-i386 version for the moment...
Thanks to you and this forum: now I know this bug it's not my fault ;-)
--
Fei
Me too: same problem.
Chipset: nForce 4 Ultra
Processor: AMD 64 3000+
GPU: ATI Radeon X800XT
OS: #define DISKNAME Ubuntu 7.04 "Feisty Fawn" - Release amd64
--
Feisty crashes after grub if usplash enabled (amd64)
https://bugs.launchpad.net/bugs/8
You received this bug notification because yo
Same problem here. I couldn't start the live-cd (hard crash with
blinking leds), unless I explicitely set the VGA resolution. Same
problem after install. I could only login by using recovery mode,
default option crashed. Luckily for me, also both removing the splash
option or setting the VGA option
I cannot confirm this on a AMD64, nVidia 6600GT, nForce4 chipset.
--
Feisty crashes after grub if usplash enabled (amd64)
https://bugs.launchpad.net/bugs/8
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I can confirm this bug on several AMD64 installations of Feisty. Booting
the install CD with kernel parameter splash is a no-go.
PLEASE FIX IT.
--
Feisty crashes after grub if usplash enabled (amd64)
https://bugs.launchpad.net/bugs/8
You received this bug notification because you are a membe
I'm having the same problem. I used the alternate install CD (AMD64) in
textmode , so I could install without problems. But I have to disable splash
to boot into Feisty, otherwise I get the kernel panic incl. blinking keyboard
LEDs. The same happens on at least one other AMD64 machine I know of
@shirishag75: please do not add comments here that do not relate to this
bug, since it will just confuse the issue here. If you need immediate
help with a particular bug, then you should go to the respective IRC
channels, for example #ubuntu-bugs.
--
Feisty crashes after grub if usplash enabled (
** Changed in: Ubuntu
Sourcepackagename: libx86 => None
--
Feisty crashes after grub if usplash enabled (amd64)
https://bugs.launchpad.net/bugs/8
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMA
Wish I could edit. Does not play well, in the sense usplash crashes, not
feisty. Have to use HDD to monitor what is happening both while starting
as well as shutting down.
--
Feisty crashes after grub if usplash enabled (amd64)
https://bugs.launchpad.net/bugs/8
You received this bug notificat
Timo, I am not experiencing a crash but usplash does not play well. That
might well have to do with the experimental driver I am using . See bug
#90213 for details. Perhaps the driver needs more work or more test-
cases.
--
Feisty crashes after grub if usplash enabled (amd64)
https://bugs.launchp
I have the same problem with an X800XL card. It makes install crash by the way,
I had to make a text install to install feisty on a blank machine. The fact is
that sometimes, the system carshes when I log off my session.
My config :
Motherboard : DFI LanParty (nforce4)
Processor : ADM64 3200+
GP
So there seems to be at least one NVIDIA gfx card (8800GTX) user as well
who is experiencing this, plus someone who is experiencing this on a
non-amd64 machine.
Matthew Garret wrote:
> In any case, I'll see if I can determine a test case for this that will give
> us some more feedback.
Is there
Hi, I'm very new to Ubuntu, but have a little bit of familiarity with
linux.
I'm experiencing the same issue, and I thought my info could be helpful:
Motherboard: Gigabyte K8NS Pro (nForce3)
Processor: AMD64 3000+
GPU: Saphire X800 Pro
Ubuntu Version: 7.04
Here's my experience:
> Couldn't load
Same bug with AMD64 and an nvidia GeForce 8800GTX, nvidia nForce4
motherboard, Dell BIOS revision 1.4.0 (the latest). The vga=xxx
workaround works for me, too. Thanks.
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-b
just to confirm that I also experienced this with the Beta release.
Adding vga=792 to the appropriate pleces in /boot/grub/menu.lst did the
trick for me.
My laptop is an AMD64 with a nvidia GeForce Go 6100 but I am running 32
bit Feisty, so maybe this isnt the right bug to comment on. The 32 bit
fglrx driver problems are not related to this bug. It's closed source
anyway so it can't be fixed, you can only complain to AMD/ATI.
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
I tried fglrx for a while, and didn't have any problem with logging out!?
I did however have the same old ATI problem that suspend (well, actually
resume) doesn't work .
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-
The same things happens for me with my X800XL (R430), something seems to go
wrong with ati's R4XX-cards. The vga=xx solution works, but it's not perfect
because it gives me another problem; the same kind of kernel panics when I
leave X when using the fglrx driver (logout, ctrl-alt-f1 to get to t
Hi, just to say that I am getting the exact problem reported by Cesare
and Timo, and the same workaround (adding vga=nnn) works for me to.
Similarly, I am running an ATi X800XT.
On the two reported card query above, it's my understanding that the
"(secondary)" card is due to there being two output
Ditto here. Its working like a breeze, sorry, a feist, from the i386 CD.
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
To mjg:
Yes, does not happen with i386. And like I also told above, setting any vga=NNN
(NNN being a number, not "ask" etc.) works also on amd64, but without it (ie.
by default) it crashes. On my computer, the caps lock does not flash, whether
or not the keyboard is connected via USB or USB-to-P
Good info there Matthew!
I have a Sapphire card. I will now download and check the i386 live CD.
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
And just for some explanation - usplash accesses your video card
directly through calls to the video BIOS. On x86, it can run the code
directly in vm86 mode. Since amd64 systems running in 64 bit mode can't
use the vm86 instruction, the code is run through an emulator instead.
If you're getting a
Ok. Could you all please confirm that this doesn't happen on i386 live
CDs?
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
It seems we all also have and AMD-64.
I tried vga=ask, and no matter what I choose (with or without scan) there is a
kernel panic.
I suspect it is not a problem from video.S but with vesafb.c (I see some
changes have been made in 2.6.20).
I'll keep investigating .
--
Feisty crashes after gr
@Timo -- perhaps we should propose this one for Feisty?
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
@Timo -- thanks for the clarification.
Still, they are reported as two cards... and what we are looking for
here is commonality: something (well, perhaps somethingS) among all of
you is causing the hard crash.
And, so far, all I can find is this. BTW, Cesare also has his video card
reported as t
sorry thought I could send attachments by reply on email
** Attachment added: "lspci output"
http://librarian.launchpad.net/6806607/stuartmarsdenlspci
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
Could this be a VESA probing issue? Perhaps some ATI cards do not
implement the VESA 2.0 spec. correctly..
Re. the bootparm, I noted that in edgy vga=normal was used. This doesn't
work in feisty. I have not yet tried vga=ask.
--
Feisty crashes after grub if usplash enabled (amd64)
https://la
Ati seems to be common I have a single x800 PRO
lspci output is attached
On 14/03/07, hggdh <[EMAIL PROTECTED]> wrote:
>
> still open questions:
>
> 1. why didn't any of us get a vga bootparm when we installed feisty?
>
> 2. would it still happen on Herd5 or the daily?
>
> 3. What is common betw
> 1. why didn't any of us get a vga bootparm when we installed feisty?
I don't think vga bootparm is ever set for default installations, ie.
people sometimes like to set that themselves.
> 2. would it still happen on Herd5 or the daily?
I've tested both herd5 and many dailies.
> Cesare has two
still open questions:
1. why didn't any of us get a vga bootparm when we installed feisty?
2. would it still happen on Herd5 or the daily?
3. What is common between all of you?
Cesare has two cards:
01:00.0 VGA compatible controller: ATI Technologies Inc R420 JP [Radeon X800XT]
(prog-if 00 [VG
yes, it seems like its the same issue. BTW, I took out the vga bootparm
from my grub setup, and still I booted OK. So... no matter what, I still
cannot reproduce this one.
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu
I think this is the same issue as #90661?
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
usplash seems to misbehave on some AMD64, so I am upping importance
** Changed in: usplash (Ubuntu)
Importance: Medium => High
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
I will try it here as soon as I get home.
The problem with different resolutions was fixed a few ago (Herd2 time?)
and should now work.
So. It seems we need a vga bootparm. I *think* I did test it on my
laptop, but I may be confused -- looks like I have draw a prize in the
form of a migrane, at l
Adding vga=792 to my kernel stops the panic and I get the splash.
Unfortunately at the end of the boot when loading kdm it stuck but I believe
this has more to do with the fglrx driver that I am trying to get
configured. Strangely when I leave splash off and do not set vga X starts
fine. I will ha
Also working vga=786 (640x480 / 24-bit, with the little fault this time
that the progress bar is not correctly centered).
Now also tested 769 (640x480/8-bit), 775 (1280x1024/8-bit), 784
(640x480/15-bit), 791 (1024x768/16-bit), 789 (800x600/24-bit), 792
(1024x768/24-bit) and 795 (1280x1024/24-bit),
YES! We are getting somewhere -- exactly where I do not know, but
anyway... some other place looks better than being stuck where we were
so far :-)
Timo, please verify /etc/usplash.cfg -- does it match the resolution you
passed on the bootparm?
On my system, with vga=792 on bootparm *and* usplash
No, it's not enabled, I have "/boot/vmlinuz-2.6.20-10-generic root=UUID
=008801fe-8fa8-47d2-ae6d-ffc30a509bc0 ro quiet splash locale=fi_FI".
Also remember that I have also tried to boot from many daily-live CDs
(http://cdimage.ubuntu.com/daily-live/), which always have the default
configuration.
B
A question for you three (Timo, Habbit, and stuartmarsden): Do you have
framebuffer enabled with VGA extended resolution (thanks Habbit for
remembering)?
Look at your Grub configuration (/boot/grub/menu.lst; see if there is a
'VGA=' in the definitions; the 'defoptions line is a good candidate, but
Unfortunately, until we can find out what goes wrong here, there is not
much we can do.
This specific bug seems to affect only ADM64s with a kernel panic. I am
hoping that bug # 88915 resolution will also solve this problem.
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchp
I am experiencing the exact same problem when booting with splash on my
amd64 box.
If I remove splash no problem otherwise it freezes with blinking caps
lock light.
Was working fine on edgy prior to upgrade.
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8666
Just some thoughts: both Timo and I have a R480-based video card. How
does usplash do all the rendering? Directly with its own VGA driver or
through the kernel framebuffer? If it's through the kernel FB, how can I
activate the it without running usplash? - to check which of them is
defective. And l
Since my last post I have been trying to obtain such a console output,
and trying a "normal boot" everytime usplash gets updated -- with the
same results: computer hangs and caps lock blinks. I can't post a boot
log because nothing seems to be written to any file in /var/log/ when
usplash crashes (
we have had other bugs on usplash failing, at varying places.
Unfortunately, so far, none of the stack traces are not complete (i.e.
no debugging information). Also, all of them are on a i386 architecture.
You two are the only I have seen so far with x86_64. The problems
*might* be related -- I do
0.4-43 doesn't help, and I've been using it for many weeks already. I
now also downloaded the latest daily-live amd64, and the problem is
still there.
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
an additional comment here: usplash 0.4-43 (current level) has corrected
some memory manipulation errors that, by the maintainer, would cause all
sorts of unpredictable problems.
Please upgrade to this version (if not already done), and please try
again.
--
Feisty crashes after grub if usplash e
** Changed in: usplash (Ubuntu)
Assignee: (unassigned) => hggdh
Status: Unconfirmed => Needs Info
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listin
** Also affects: usplash (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I haven't done it myself, and information on the net is scarce. I found out
that following could be added to /boot/grub/menu.lst:
# Setup serial (COM1) here with baudrate 9600
# use --unit=1 (for COM2) and so on
serial --unit=0 --speed=9600
# Now setup terminal as both Serial Line(/dev/ttyS0) and
I have a laptop w/edgy and some serial cables... How can I send the
console output to the serial port and capture it in my laptop?
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
Maybe the problem is the video card itself? I didn't think that could
bring down the whole kernel, but I've noticed we both have a R480-based
ATI video card (I have an X850XT). I'll post the requested data ASA I
boot into Feisty - I'm currently in windoze due to some... game :P
--
Feisty crashes
indeed, this is a sign of a kernel hard crash -- your kernel died and,
just before giving up the ghost, tried to give you an indication is was
going down.
And... this, again, makes it much more difficult, since we do not know
what happened. It would probably have been written to the console, but
w
Did I mention that as soon as the monitor enters shutdown state, the
caps lock key starts blinking? Maybe it's some kind of kernel "death
message"
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
Yes, I understand that. What seems to be going on with your computer is
you are getting hit by a hard crash during boot, as it seems as soon as
usplash gets called -- and, most probably, the interrupt handler died
(and, as a result, not even sysrq will work).
This is a hard one to crack. We do not
Habbit: My motherboard is not failing, it is known that all the ATI
RS480/RS482 motherboards are buggy... people are basically being sold
(partially) broken hardware, something that is quite common these days.
Such hardware needs various workarounds to function properly, often done
in eg. Windows d
Timo, I see you have an ATI video board, but I do not see any references
to a framebuffer device, nor to extended VGA settings -- in fact, your
VGA is set to 80x25.
Can you try with a lower usplash setting (xres=640, yres=480) and see if
it works?
--
Feisty crashes after grub if usplash enabled
I don't think it has to be your motherboard failing: I have a perfectly
healthy Gigabyte board and also suffer from this bug when booting in
amd64 feisty. Haven't tried the x86 version though.
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bug
Version 0.99-1.2, ie. the newest. Contents of the /etc/usplash.conf are what
they are in the Herd-4 CD when booting from that, and as follows on the
installed feisty:
# Usplash configuration file
xres=1024
yres=768
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bu
Can you please state the version of libx86 you are running?
Also, what is the content of /etc/usplash.conf?
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinf
** Attachment added: "dmesg output"
http://librarian.launchpad.net/6489954/dmesg.txt
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "lspci -nvv output"
http://librarian.launchpad.net/6489938/lspci-nvv.txt
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bu
** Attachment added: "lspci -vv output"
http://librarian.launchpad.net/6489937/lspci-vv.txt
--
Feisty crashes after grub if usplash enabled (amd64)
https://launchpad.net/bugs/8
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
83 matches
Mail list logo
