[Bug 89627] Feisty alternate installer random crashes on Abit KU8 ULI M1689 M/B

2007-03-04 Thread Mark Honman
Public bug reported: Problems experienced in installing from Feisty alternate i386 CD (both Herds 2 and 5 tried). It's a truly random crash/reboot situation... sometime it will go a long way though the installation before crashing, other times it will crash as soon as the installation environment

[Bug 89627] Re: Feisty alternate installer random crashes on Abit KU8 ULI M1689 M/B

2007-04-01 Thread Mark Honman
In subsequent testing it was not possible to get Windows running on the board - so it's most likely that that the board is defective (espacially as no-one else seems to have had this problem). It's just funny that 6.06 was happy with it. Since the board has been binned, you might like to do the sa

[Bug 75011] Re: Hurd 1 Alternative installation: partition manager fails under specific circumstances

2007-01-03 Thread Mark Honman
A further report on what is probably the same bug. Target: HP NC6120 (centrino) laptop with Windows XP Professional, 512MB RAM, 80GB HDD. The first partitioner screen gave a number of options, of which the first two were quite odd: 0 Guided - resize cdrom-retriever and use freed space Selecting

[Bug 46510] Re: At boot doesn't recognize aic9405 controller sas/sata

2007-01-11 Thread Mark Honman
On dapper (6.06.1 LTS) the method outlined in the previous comment can also be used. However the file to be modified is /etc/mkinitramfs/modules Here is the procedure when using the Alternate CD After the install has completed and ejected the CD #chroot /target #mount /boot edit /etc/mkinitramfs/

[Bug 78863] Feisty Herd 1 alternate CD: aic94xx not recognised

2007-01-11 Thread Mark Honman
Public bug reported: Attempted to do a command-line installation from the Feisty Herd 1 i386 Alternate CD, on an IBM x206m with an Adaptec 94xx SAS controller. The installer reported that no disks were found, and presented a list of drivers, including the aic94xx driver. Selecting it had no effec

[Bug 75011] Re: Hurd 1 Alternative installation: partition manager fails under specific circumstances

2007-01-16 Thread Mark Honman
I'll be a while before I can get back to you with the logs, as the laptop is presently acting as a temporary server! Should be 1-2 weeks. -- Hurd 1 Alternative installation: partition manager fails under specific circumstances https://launchpad.net/bugs/75011 -- ubuntu-bugs mailing list ubuntu

[Bug 75011] Re: Hurd 1 Alternative installation: partition manager fails under specific circumstances

2007-01-24 Thread Mark Honman
Here are the logs as requested.The problem also occurs with Herd 2, and these logs are from that installation attempt. Unfortunately I won't be able to do further tests on this machine... and I could not reproduce the problem on a different centrino machine (the 2nd machine had a different partiti

[Bug 75011] Re: Hurd 1 Alternative installation: partition manager fails under specific circumstances

2007-01-24 Thread Mark Honman
syslog attachment ** Attachment added: "/var/log/syslog" http://librarian.launchpad.net/5852555/syslog -- Hurd 1 Alternative installation: partition manager fails under specific circumstances https://launchpad.net/bugs/75011 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://

[Bug 78863] retest with Herd 2 i386 Alternate

2007-01-28 Thread Mark Honman
Unfortunately with Herd 2 Alternate the situation is worse... on the x206m the installer did not get beyond the keyboard selection screens (did not get to "dectecting hardware"). The "console" VT shows rapidly repeating "kernel: not found" messages. The CD verifies OK, but not on the x206... attem

[Bug 976862] Re: Compilation errors on compat_xtables.c

2012-04-08 Thread Mark Honman
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976862 Title: Compilation errors on compat_xtables.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-add

[Bug 641112] [NEW] serverCA and clientCA certificates have a notAfter date in the past

2010-09-17 Thread Mark Honman
Public bug reported: Binary package hint: boxbackup-server In /usr/bin/bbstored-certs, the default CA certificate expiry time of 1 days is too long - putting the expiry date after the Unix epoch, which causes wrap-around to approx 1901. When clients attempt to connect to a boxbackup server,

[Bug 641112] Re: serverCA and clientCA certificates have a notAfter date in the past

2010-09-17 Thread Mark Honman
** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/641112/+attachment/1597251/+files/Dependencies.txt -- serverCA and clientCA certificates have a notAfter date in the past https://bugs.launchpad.net/bugs/641112 You received this bug notification because you are a member