I was able to modify my sources.list and test linux-image-2.6.24-5-386.
I use the nvidia driver, so it could not load the kernel module, but it
worked with the nv driver. The devices mounted fine without
modification.
After booting to the gutsy kernel and removing the hardy kernel, apt
gave me the
For those who have *some* method of booting into their system...
It should be noted that there were a number of issues related to booting
as a result of what was done in Gutsy. See bug 133666 for one prominent
example. This documents an issue that had a known fix that will not be
put into Gutsy
I have a laptop here too with Gutsy using a SiS5513 HDD controller. It
fails to boot using the 'default' kernel, 2.6.22-14.
My current workaround is to set 2.6.20 as the default kernel, which
still has the module, but I can hardly call that a proper solution. Why
has this driver been removed? Will
Not sure if I'm having the same issue, but looks similar
I have a "sis5513" IDE controller and "Toshiba mk8025gas" hard drive. The
update to gusty went ok (had to remove evms).
However yesterday (28.12.07) I've updated my system. The
linux-image-2.6.22-14-386_2.6.22-14.47_i386.deb has been instal
The following might help . . .
https://help.ubuntu.com/community/UsingUUID
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.launchpad.net/bugs/152820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
David: I see this exact issue even on a freshly installed system, and my
fstab and menu.lst files only contain UIDs (no reference to /dev/{sh}d*
at all!)
I can confirm that my drive was changed from hdaN to sdbN in the switch
from feisty to gutsy.
--
Upgrade to linux-image-2.6.22-14 kernel rende
I mean, screenshots of unsuccessful boot attempts)))
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.launchpad.net/bugs/152820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
How can i make this changes, if 2.6.22 kernel won't boot?
P.S. I do not have digital photocamera, so its not easy for me to
present screenshots here.
Here is my fstab (on 2.6.20-15-generic)
proc /proc proc defaults 0 0
# Entry for /dev/sda1 :
UUID=222b8e3c-9dda-4ac5-90ba-4fec03f27d09 / ext3 nous
It appears that the *intent* with Gutsy was to switch the drives over to
/dev/sd* completely. That did not happen for SiS 5513 IDE controllers.
According to my personal experience, these changes allowed me to use the
stock Ubuntu kernels:
Feisty: No changes from previous installs. Feisty kernel
Here's a quick rundown of my Gutsy kernel issue.
Feisty was working fine with my computer. An upgrade to Gutsy worked --
with the exception of needing to either use the Feisty kernel, or
compile my own with the SiS 5513 module compiled (it was removed by the
Ubuntu folks).
Then I finally read th
Also, David, have you removed the evms packages? If you're not sure,
running the command
dpkg-query -s evms
will give you the status. If the status says deinstall ok config-files,
then you're good. If it says install ok installed, then you'll need to
remove it:
sudo apt-get remove evms.
--
Upg
David,
Can you boot with any of the kernels, such as 2.6.20-16-386? If you can,
can you attach the contents of /var/log/kern.log?
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.launchpad.net/bugs/152820
You received this bug notification because you are a member
I would disagree that this issue is *fixed*. Bolek indicated that an
*upgrade* from Feisty to Gutsy on a certain architecture (including a
SiS 5513 IDE driver) will cause the computer to be unbootable, while a
fresh install on the same computer will have it working like a charm.
There is some dis
Hi Bolek, thanks for the update. I'm going to close this report for now
as this is no loner an issue for you.
Kamba, I'll follow up with you at bug 151088. However, just to answer
some of the questions you raised here. . . the reason we ask that bug
reports specifically target one particular bug
Ok. I'll open a new bug.
No, i do not have EXACTLY the same hardware configuration as topic starter. BUT!
>From september i have reported about my problem in some existing bugreports,
>and created the new one
>https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/151088
which even
Sorry for the delay. This is no longer an issue for me. Since my original
post and initial investigation, I decided to do a straight up re-load. That
fixed my issue.
On 12/13/07, Leann Ogasawara <[EMAIL PROTECTED]> wrote:
>
> Bolek, can you comment if this is still an issue for you since you ar
Bolek, can you comment if this is still an issue for you since you are
the original bug reporter? Please let us know.
Kamba, I'm sorry you are still experiencing issues. Can you verify you
have the same hardware at the original reporter? If not, can you please
open a new bug. It helps the kern
I experienced the very same problem.
The solution was to remove any evms-packages.
Even though https://wiki.ubuntu.com/Evms states, that it recomends removing
emvs during the update process, I was not aware.
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.launc
I do not have EVMS installed.
Developers, is it ok, that OS doesn't boot on laptops, and we don't have
any patches about this bug for more than 3 months?
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.launchpad.net/bugs/152820
You received this bug notification
I hope this helps answer some questions here:
1) The reason you drives are appearing as /dev/sd* rather than /dev/hd* is
because is kernel is now using the libata subsystem which makes all ATA devices
appear with the /dev/sd* syntax.
2) As of Ubuntu 7.10 official support of EVMS has been dropp
The master is a Western Digital WD400EB-00CPF0 and the slave is a
Seagate ST3120026A, both as reported by the bios.
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.launchpad.net/bugs/152820
You received this bug notification because you are a member of Ubuntu
Bugs
Do you hava a Seagate harddrive?
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.launchpad.net/bugs/152820
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@li
I did change fstab to reference /dev/sda2 and /dev/sdb2 instead of
/dev/hda2 and /dev/hdb2 and it works now. It seems as if the kernel is
detecting my drives as SCSI instead of IDE as they were detected
previously.
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.l
** Tags added: kernel-oops
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.launchpad.net/bugs/152820
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.ub
I mean mounting the drives manually. I believe if I change fstab, it
will work now.
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.launchpad.net/bugs/152820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
I got mine to work by removing evms and related packages, then changing
mounting manually.
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.launchpad.net/bugs/152820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
In my case the 2.6.22-14-386 kernel is detecting my hard drives as sdx
instead of hdx, so nothing in fstab mounts. I cannot manually mount the
drives, and if I change fstab and restart, I get nothing.
It mounts the primary drive fine, but it's supposed to be hda2, yet
22-14 mounts it as sda2. I ha
This is an update to the bug I posted. It is my believe that there is
something horribly wrong going on during the upgrade that causes
subsequent kernel upgrades to be unusable. I bit the bullet and
installed Gutsy from scratch after the official release. After doing
it, I have no issues.
My th
I am having a similar problem with kernel 2.6.22-14-386. I am able to
boot with 2.6.20-16-386. I'm running kubuntu and this happened after my
upgrade to gutsy.
I get to a screen that says it couldn't find the ext3 filesystem on
/dev/hdb and the system ends up in repair mode with an option to hit
C
2.6.22-14 has rendered my PC unbootable too. This is true for both
i386, and AMD64 flavors of the kernel.
The problem appears when it tries to load the ide drivers for the disks I have.
Modprobe exists abnormally,
and there's no ide support, so can't be booted. The kernel dumps to busybox.
T
maybe, the same bug? https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/150739
--
Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
https://bugs.launchpad.net/bugs/152820
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug c
31 matches
Mail list logo
