Both of my Viewsonic VE710 monitors seem to produce invalid EDIDs
leaving me stuck with 1024x768. The suggestion in #48 (appropriately
modified) allowed me to finally get to 1280x1024, but the 11.04 Unity
desktop is confused as it partly uses the old resolution. It is not
clear to me where to
I have successfully used usb-creator-kde 0.2.22 with Lucid Kubuntu CD,
but I had problems earlier that seem to have come from two sources.
Originally, I was testing on a machine that would only boot USB sticks
formatted with fat16 (Could not find kernel image: linux). I was able
to work around
Works for me also. I undid the Abene workaround that I had been using,
and used the new wubildr to booted a few times without difficulty. I
already had the -16 kernel installed, however, so I was not testing
after a new update. I did muck around quite a bit with /boot and
/boot/grub/ and used
Electron - In post #104, I listed each step that I used to implement
Mark Abene's fix (#69 #70) on my system where /dev/sda is the boot
drive and /dev/sda1 is the partition containing the Windows XP system.
That post might be what you are looking for. Be sure to study the man
pages to become
I made a test to see if Grub had difficulty reaching high up in an ext4
partition (no ntfs or wubi involved so may be irrelevant to present
bug).
First, I installed and fully updated (as of 12/2/09) Xubuntu 9.10 in a
desktop machine letting it use the entire 80GB disk with the root
directory at
The following might be helpful. It summarizes Mark Albene's solution to
this problem:
I did a fresh install of wubi-ubuntu into a Windows XP partition, performed all
updates, and observed the boot problem.
I was able to reboot by typing in the commands at the grub prompt:
grub linux
To #78:
I used the following instructions:
cd /win/ubuntu/disks
dd if=/dev/zero of=boot.disk bs=4096 count=8192
mke2fs boot.disk
See the man pages for dd and mke2fs if necessary.
--
Wubi/Karmic boot: kernel panic - not synching: VFS
https://bugs.launchpad.net/bugs/477169
Chuck,
After seeing no response to my bug report, I concluded that the problem was a
serious one that must be well known. I think that mailman was updated to use
python version 3.0 while Kubuntu was was still using 2.6. I decided to simply
run my small mail server operation by hand and wait
Chuck,
After seeing no response to my bug report, I concluded that the problem was a
serious one that must be well known. I think that mailman was updated to use
python version 3.0 while Kubuntu was was still using 2.6. I decided to simply
run my small mail server operation by hand and wait
Public bug reported:
Binary package hint: mailman
Error
Could not install
/var/cache/apt/archives/mailman_1%3a2.1.12-1_i386.deb
The upgrade will continue but the ... mailman package may be in a not working
state.
subprocess pre-installation script returned error exit status 1
** Affects:
** Description changed:
Binary package hint: mailman
Error
Could not install
/var/cache/apt/archives/mailman_1%3a2.1.12-1_i386.deb
The upgrade will continue but the ... mailman package may be in a not working
state.
subprocess pre-installation script returned error exit status
Public bug reported:
Binary package hint: mailman
Error
Could not install
/var/cache/apt/archives/mailman_1%3a2.1.12-1_i386.deb
The upgrade will continue but the ... mailman package may be in a not working
state.
subprocess pre-installation script returned error exit status 1
** Affects:
12 matches
Mail list logo
