This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on
the current status under
could this be a hardware issue?
https://help.ubuntu.com/community/SquashfsErrors
--
Ubuntu feisty: Failed to set xfermode with 2.6.20-14
https://bugs.launchpad.net/bugs/103677
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi JW,
Thanks for testing and the update. It would definitely appear you've
got a new issue than what was original reported. Intrepid's final
release is set to come out tomorrow. I'd be interested in knowing if
these new issues still exist. If so, we'll likely want to have you open
a new bug
Tested amd64 image with similar results.
- after booting, got a garbled screen (looked like it was vertically scanning);
ctrl-alt-f1 got me a CLI, ctrl-alt-f7 got me the desktop.
- shutting down was flawless from what I could tell.
There appeared to be some graphical artifacts, but I have to
Leann: I was able to try the i386 image this morning. It booted to a
black screen. ctrl-alt-f1 gave me a command prompt; ctrl-alt-f7
displayed the desktop.
That was oddity number 1.
Oddity number 2 was when I shutdown. It stopped on Checking battery
state[ok]. I had to ctrl-alt-del to
Leann: I will give this a try soon, hopefully today. I have to
download the images again as my previous ones were corrupt.
--
Ubuntu feisty: Failed to set xfermode with 2.6.20-14
https://bugs.launchpad.net/bugs/103677
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi JW,
Sorry for the delayed response. I've typically seen the SQUASHFS errors
attributed to a bad media. Care to maybe try burning the latest
Intrepid Beta that came out today? If you are still unable to boot, if
you could boot with the 'quiet' and 'splash' options removed and take a
digital
I tried the Live CD and it would not get to the login screen. I got the
usplash and then after a couple minutes, it went over to a console where
there were a lot of messages scrolling by. Some of which looked like...
Buffered I/O error on device sr0...
and
SQUASHFS error: sb_bread failed
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
This problem appears to have completely gone away upon running aptitude
update.
Appending piix to the modules file actually caused me NOT to be able to
boot the machine. I left the disk in the fdd and did an update. I
noticed on subsequent reboots that the fdd was not being spun up as it
was
Yupp. The issue was gone the moment I removed my IDE drive, leaving only
my SATA drive.
--
Ubuntu feisty: Failed to set xfermode with 2.6.20-14
https://bugs.launchpad.net/bugs/103677
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I had a problem from the LiveCD (7.04 64-bit). I found a solution to
the problem which called for putting a non-bootable disc in my fdd.
That, believe it or not, worked.
The other solution that I read for this was to insert break=top in the
startup parameters for the LiveCD and then type
I have a simular problem with the new feisty 7.04
My system will boot and stop at
/bin/sh: can't access tty; job control turned off
(initramfs)
If i disable the ite8211 in the bios I can run the live cd.
--
Ubuntu feisty: Failed to set xfermode with 2.6.20-14
same problem with 2.6.20-15-generic kernel !
--
Ubuntu feisty: Failed to set xfermode with 2.6.20-14
https://bugs.launchpad.net/bugs/103677
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
same here with ASUS P5NSLI motherboard. Searched all over for a
solution; this is the first bug report I've found with exact same
symptoms as me (able to boot 2.6.20-13, but not 2.6.20-14).
--
Ubuntu feisty: Failed to set xfermode with 2.6.20-14
https://bugs.launchpad.net/bugs/103677
You
dmesg with 2.6.20-13.
** Attachment added: dmesg
http://librarian.launchpad.net/7179250/dmesg_2.6.20-13.txt
--
Ubuntu feisty: Failed to set xfermode with 2.6.20-14
https://bugs.launchpad.net/bugs/103677
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None = linux-source-2.6.20
Assignee: (unassigned) = Ubuntu Kernel Team
Status: Unconfirmed = Confirmed
--
Ubuntu feisty: Failed to set xfermode with 2.6.20-14
https://bugs.launchpad.net/bugs/103677
You received this bug
17 matches
Mail list logo
