Public bug reported:
I just had some weird behaviour from the GNOME desktop on my Intrepid
laptop (x86 hardware, ath_hal wifi). I'm not sure this is the right
package; it might be the fault of the window manager (compiz in my
case), or something else. If anyone figures out what was actually
subscriber
of the bug.
--
#define X(x,y) x##y
Peter Cordes ; e-mail: X(pe...@cor , des.ca)
The gods confound the man who first found out how to distinguish the hours!
Confound him, too, who in this place set up a sundial, to cut and hack
my day so wretchedly into small pieces! -- Plautus, 200
*** This bug is a duplicate of bug 306016 ***
https://bugs.launchpad.net/bugs/306016
** This bug has been marked a duplicate of bug 306016
nfs client broken since 2.6.28-2-generic upgrade
--
nfs lockd broken
https://bugs.launchpad.net/bugs/306343
You received this bug notification
This does look the as same bug 306343 I reported. I didn't see this one
because I was only searching in linux, not nfs-common.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
nfs client broken since 2.6.28-2-generic upgrade
https://bugs.launchpad.net/bugs/306016
You received
Public bug reported:
I've tried AMD64 2.6.28-2.3-generic with Jaunty userspace, and with
Intrepid userspace, and NFS is b0rked with both (nfs client and nfs
server). Mounts work with -o nolock, though. (-o nolock doesn't
require NFS lockd to be running). Otherwise, NFS mount attempts time
out.
** This bug is no longer a duplicate of bug 99648
Sony memory reader in CB-712/4 does not work
--
automount problems in kubuntu feisty
https://bugs.launchpad.net/bugs/97398
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Description changed:
(original report was that SD/MMC didn't work, but SD works now according
- to Matt LaPaglia.
+ to Matt LaPaglia. He posted lspci and dmesg output on a fresh bug he
+ opened specifically about the Sony memory stick part: bug 200668, which
+ is marked as a dup of this
Thanks Darren. Looks like you don't have the same hardware as this bug
is talking about. Mine has a 1524:0550 subdevice, like yours, but lacks
a 1524:0551. Thanks for clearing that up.
Your kernel messages show that it is the 1524:0550 (mmc0, not mmc1)
that works for your SD card, but I
** Summary changed:
- SDHC Card reader I/O errors on Hardy
+ Ricoh R5C822 SDHC Card reader I/O errors
** Description changed:
+ (replies indicate that this problem wasn't specific to SDHC, more like
+ specific to this Ricoh reader. updating description and tags... Also,
+ 2.6.27-10 maybe have
** Tags added: sd
--
sdhci stops Dell XPS Gen2 from Resuming from Suspend
https://bugs.launchpad.net/bugs/48209
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Tags added: sd
--
sdhci: Nothing happens when a card is inserted
https://bugs.launchpad.net/bugs/41211
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Description changed:
My Toshiba A70 laptop's SD card reader with PCI ID 1524:0550 (part of
an ENE CB-710/2/4 Cardbus Controller) doesn't work with Linux. I
haven't tried Ubuntu pre-gutsy, but it hasn't worked with Gutsy, Hardy,
or Intrepid. I've never seen it work under Linux, so
your lspci output doesn't seem to include any card readers. There
should be a device that lspci says is handled by sdhci..., or tifm...
Also, lspci -vvnn includes the numeric and decoded outputs together; I
should have recommended that instead of two separate lspci commands.
(But wait until you
** Summary changed:
- MMC/SD memory card reader does not work
+ Sony memory reader in CB-712/4 does not work
** Description changed:
+ (original report was that SD/MMC didn't work, but SD works now according
+ to Matt LaPaglia.
+
+ This bug is specifically about readers that are part of the
Why did you all of a sudden change the summary of the bug?
I'm trying to sort out the SD card reader bugs so there is one open bug
for each specific piece of hardware that doesn't work. I thought this
bug looked like it should be about this hardware, not yours, since you
jumped in later and
Debian's kdeutils is only at version 3.5.10 in unstable, and still has
kregexpeditor. However, they have version 4:4.1.3-1 in experimental,
and it doesn't seem to have kregexpeditor.
http://packages.qa.debian.org/k/kdeutils.html
note the lack of mention of kregexpeditor in:
I've been trying to figure this out, since my Toshiba A70's card reader
still doesn't work with Linux, using Intrepid.
I found this mailing list post saying that the 0550 device ID has never worked,
but 0551 does work these days:
Hmm, someone seems to have had success with 1524:0550 card readers:
http://marc.info/?l=linux-kernelm=116758515323702w=2
--
Linux doesnt support ENE CB-712 SD card reader
https://bugs.launchpad.net/bugs/62995
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This seems similar to bug 62995, which is closed, so I'll repost here
some info I posted there about ENE chipsets.
I found this mailing list post saying that the 1524:0550 device ID has never
worked, but 1524:0551 does work these days:
** Summary changed:
- linux-image cannot read MMC partition table
+ tifm_7xx1 SD card reader cannot read MMC partition table
--
tifm_7xx1 SD card reader cannot read MMC partition table
https://bugs.launchpad.net/bugs/111756
You received this bug notification because you are a member of Ubuntu
Most of the problems with SD card readers are hardware-chipset
dependent. Someone should decide what they want this bug to be about,
and post some lspci -v and lspci -vn output, and dmesg output (for the
relevant devices, see e.g.
Richard posted on bug 137686, and it seems he has tifm_7xx1 hardware.
I'm just going to close this as invalid since it doesn't have enough
details about any specific hardware, and it looks like the original
submitter went with bug 137686 and abandoned this. Re-open this bug if
I'm incorrect.
**
That's odd that one card works and one doesn't. Is that repeatable, or
does your card reader just sometimes fail to detect the card, and it was
just chance that one card didn't work? I saw a mention in a mailing
list message of a card reader that only supported one voltage, unlike
some others
can someone update the bug title to say what hardware it's about?
There are a lot of mmc doesn't work bugs, and I'm trying to sort them
out so I can tell if my problem on the tosh A70 is already known. And
to help people find the right bug to post more info on. A lot of times
people post with
** Summary changed:
- ENE internal SD Card reader doesn't work with Hardy (but work with Gutsy)
+ ENE internal SD Card reader [PCI 1524:0751] doesn't work with Hardy (but work
with Gutsy)
--
ENE internal SD Card reader [PCI 1524:0751] doesn't work with Hardy (but work
with Gutsy)
I think you're SOL with that hardware, because the manufacturer won't
release the specs.
I think this quote
http://list.drzeus.cx/pipermail/sdhci-devel/2008-March/002181.html applies:
Your system only has a ENE specific interface, and we don't have any specs on
that beast. -- Pierre Ossman
Public bug reported:
My Toshiba A70 laptop's SD card reader with PCI ID 1524:0550 (part of
an ENE CB-710/2/4 Cardbus Controller) doesn't work with Linux. I
haven't tried Ubuntu pre-gutsy, but it hasn't worked with Gutsy, Hardy,
or Intrepid. I've never seen it work under Linux, so AFAIK this
** Attachment added: dmesg output from the A70
http://launchpadlibrarian.net/20083719/whale.dmesg
--
ENE CB-710/2/4 sdhci [PCI 1524:0550] doesn't work
https://bugs.launchpad.net/bugs/303844
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
no luck with an Edgy livecd (2.6.17-10.33-generic, built Fri Oct 13,
2006).
--
ENE CB-710/2/4 sdhci [PCI 1524:0550] doesn't work
https://bugs.launchpad.net/bugs/303844
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: friendly-recovery
I run with /usr on a lvm volume, and / on its own RAID1 md device, which
is GRUB-bootable. I wanted to xfs_admin my /usr, but friendly-recovery
leaves open files on /usr (e.g. /usr/share/recovery-mode/options/root)
when dropping to a
should i log a separate bugreport about this ?
I think that's already in Ubuntu's released Intrepid kernel, not just
the proposed-updates kernel. See the changelog.Debian.gz
linux (2.6.27-7.13) intrepid; urgency=low
...
* Fix barrier fail detection in XFS
...
-- Tim Gardner [EMAIL
I think that's already in Ubuntu's released Intrepid kernel
oops, no it isn't, the patch you posted a line-wrapped URL to is in
2.6.27.7. (No mention of it in ChangeLog-2.6.27.7, though. I though
the Changelogs were auto-generated, but obviously patches can be in
patch 2.6.27.7.gz without an
Public bug reported:
Binary package hint: audacity
Audacity works fine (most of the time) on my AMD64 Intrepid system,
using ALSA output to hw:0,0 (not alsa's default pcm, because that always
resamples to 48kHz!?)
I didn't expect this to work, but I used the Split stereo track track-
dropdown
Ubuntu AMD64 8.10.
[EMAIL PROTECTED]:~$ echo '\' | mawk '{ gsub( /\\/, ); print }'
\
[EMAIL PROTECTED]:~$ echo '\' | mawk '{ gsub( /\\/, \\ \\ ); print }'
\ \
The syntax is fine, it's all single-quoted. The submitter left out a print,
though. You can check that mawk is getting the right
It seems to be fixed. I don't see anything in the changelog, but it
works ok when run with 0- 1-
Now it does this (for two empty files)
5601 open(foo, O_RDONLY) = 0
5601 open(bar, O_RDONLY) = 3
5601 read(0, , 4096) = 0
5601 read(3, , 4096)
It seems to be fixed. I don't see anything in the changelog, but it
works ok when run with 0- 1-
Now it does this (for two empty files)
5601 open(foo, O_RDONLY) = 0
5601 open(bar, O_RDONLY) = 3
5601 read(0, , 4096) = 0
5601 read(3, , 4096)
I decided not to worry about it, and just get used to it. I _think_ the
old lower temps were more sensible, and I would only worry about my
machine if the old temp got really high.
If anything in the CPU really is as hot as the new readings indicate, it
doesn't seem to be a problem. And I
Leann, thanks for the reply on my bug that's a dup of this. I thought
I'd already posted my workaround, but it turns out I only posted it on
bug 253786 (/dev/.static/dev is left read-only). Since I found a
workaround, this bug hasn't caused me any problems.
Anyway, you can convince the init
BTW, happycoders-emacs conflicts with emacs-extra, and is from the same
Debian maintainer. It's version number is 2004.08.14, so it's old, too.
--
funny menu after install of emacs-extra
https://bugs.launchpad.net/bugs/112837
You received this bug notification because you are a member of
not fixed in intrepid either, and has no maintainer in Debian. The
package doesn't even exist on the PTS (http://packages.qa.debian.org/e
/emacs-extra.html - 404). So it's not exactly actively maintained.
I like the colour scheme it provides for light on dark, but it's
probably pretty
version 2.02r2-8 works on pre-Intrepid. This might well have been fixed
in Hardy, but I didn't check.
** Changed in: xevil (Ubuntu)
Status: Incomplete = Fix Released
--
crash on load on AMD64
https://bugs.launchpad.net/bugs/87422
You received this bug notification because you are a
looks like this is fixed in Linux 2.6.27.3:
commit c068663ae65e507814545b59a8e2090f48a85613
Author: Christoph Hellwig [EMAIL PROTECTED]
Date: Sun Oct 12 14:30:44 2008 +0200
xfs: fix remount rw with unrecognized options
[...]otherwise we may skip clearing
the xfs-internal read-only
USB module loading order: Linux 2.6.27.3's changelog says that Linux
will now warn if ehci isn't loaded before o/uhci. And that it has
always been better to load ehci first. So panic() should load ehci-hcd
first, then try the other two, in case the user works around a problem
and goes on to boot
I was looking into this because it triggered bug 278954.
initramfs bind-mounts /dev to /dev/.static/dev before the init scripts
remount / read-write.
I've been working around the XFS bug with a line in fstab:
/dev/dev/.static/dev bind remount,rw 0 0
This has the side-effect
Public bug reported:
Binary package hint: gawk-doc
in (gawk.info.gz)Records, this example is given:
$ echo | awk 'BEGIN { RS = a } ; { print NF }'
1
But that's wrong: real results
[EMAIL PROTECTED]:~$ echo | gawk 'BEGIN { RS = a } ; { print NF }'
0
[EMAIL PROTECTED]:~$ echo | gawk --posix
I was going to reply on the forum thread I originally started, but it's locked
now. sigh.
http://ubuntuforums.org/showthread.php?t=625076
Anyway, the solution to my problem was an updated firmware for my WD5000YS
hard drive.
Public bug reported:
oowriter's thesaurus feature doesn't work well for me. I have to mess
with document languages to get it to open. Being in Canada, I run
Ubuntu (pre-Intrepid, AMD64) with LANG=en_CA.utf8.
I have openoffice.org-thesaurus-en-us and ...-en-au installed. (but
not
** Changed in: linux (Ubuntu)
Status: Won't Fix = Fix Released
--
linux 2.6.27-2.3: pcspkr should be enabled too, now that snd-pcsp is
blacklisted by default
https://bugs.launchpad.net/bugs/263747
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I installed the Intrepid kernel (linux-image-2.6.27-5-server on an
otherwise-Hardy x86-64 server (I do have Intrepid's initramfs-tools, and
a non-current-Intrepid module-init-tools).
/dev being read-only bind mounted on /dev/.static/dev somehow causes
Linux to return EROFS
I was able to reproduce this on another server. It happens on XFS with
relatime,inode64,noikeep. It does not happen on 2.6.27-5 with just
relatime. I haven't checked which of inode64 or noikeep is the problem.
--
read-only bind mounts cause spurious EROFS
Public bug reported:
Binary package hint: xserver-xorg-video-ati
driver version 1:6.9.0+git20081003.f9826a56-0ubuntu2 Running GNOME with
metacity (not compiz for this bug...) on pre-Intrepid i386.
Toshiba A70 laptop (ATI IXP chipset: mobility radeon 9100IGP). Using
Xinerama on internal and
** Attachment added: Xorg.log from the crash
http://launchpadlibrarian.net/18229548/Xorg.0.log.old
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/18229549/Dependencies.txt
** Attachment added: LsMod.txt
http://launchpadlibrarian.net/18229550/LsMod.txt
**
Public bug reported:
Binary package hint: gucharmap
man -k guchar
gucharmap (1)- (unknown subject)
I couldn't find it when I was looking for it earlier with man -k
unicode and man -k character, etc.
I don't know nroff so I can't tell what's wrong with the page that
makes it not
I tried to reproduce this, but it works for me on a pre-Intrepid system. I'm
going to mark this fix-released, rather than invalid, on the assumption that
there was something going on. If anyone can reproduce this, or knows exactly
what the submitter meant by
only the first gnome-terminal
I hit this on the Intrepid i386 livecd daily build (Sept30, 2008). I
had compiz running with some extra stuff turned on (e.g. installed ccms
and enabled ezoom plugin).
HW: Toshiba A70 laptop: ATI IXP chipset, integrated ATI graphics (quite slow
with AWN)
00:00.0 Host bridge: ATI Technologies
I had thought this was bug 92338, but that was fixed by Hardy's N-M's support
for
iface eth0 inet manual
The fact that that no longer works is a different bug (this one, in fact). On
bug 92338,
---
Alexander Sack wrote on 2008-09-22: (permalink)
since gutsy we dont manage interfaces
? That would be a good idea.
thanks.
--
Peter Cordes
--
ubuntu-mobile-default-settings: better descriptions describing target MIDs
https://bugs.launchpad.net/bugs/275299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: ubuntu-mobile-default-settings
It's not obvious from the package descriptions that Ubuntu Mobile
targets small-screen netbooks. Although that does sound familiar from
reading news items, it would be appropriate to make it clear in the
package
Public bug reported:
Binary package hint: gksu
[EMAIL PROTECTED]:~$ gksudo xterm
[EMAIL PROTECTED]:/home/peter# ll $XAUTHORITY
-rw--- 1 peter peter 150 2008-09-27 20:20 /tmp/libgksu-3t0ebS/.Xauthority
The directory is also owned by the user who ran gksudo, so they could
modify
sorry, this is on an updated Intrepid i386 with
gksu 2.0.0-5ubuntu3
libgksu2-0 2.0.7-1ubuntu2
--
wrong ownership of .Xauthority and /tmp/libgksu-xxx
https://bugs.launchpad.net/bugs/275304
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The upstream developers realize this is a bug in evdev 1.2, which is
why it's been fixed in evdev 2.0.
I think Jeffrey was talking about just the lack of Emulate3Buttons,
which is now present in evdev in Intrepid. I don't see anything in its
man page about disabling evdev entirely.
I'd still
dhcp has a timezone option. I might not be widely used, but dhclient on
the livecd should be configured to request timezone or location or
whatever the option is. Then if the server does support it, you're all
set.
DHCP also supports a list of NTP servers, although that's not so
necessary
Public bug reported:
Binary package hint: lvm2
Ubuntu Hardy.
lvcreate --help shows
...
[-t|--test]
[--type VolumeType]
[-v|--verbose]
...
AFAICT, --type isn't documented in the man page or in
/usr/share/doc/lvm2. And I didn't have any luck with google.
lvcreate
MountainX, you don't need sudo in /etc/rc.local. It runs as root on
bootup, like all init scripts.
Are you sure your loadkeys method even works? loadkeys is a totally
different way to change your keymap: It changes the Linux kernel
keymap. I though X put the kbd in raw mode, and got keycodes
On more careful reading of this bug (#92338), it seems to be reporting the
problem that your main network interface can't be in /etc/network/interfaces if
you want to boot with nfsroot. The fix for that is support for the manual
setting in interfaces(5) to stop ifupdown breaking the nfsroot.
still present in Intrepid alpha6 i386.
I discovered that the Textured Video adaptor works, but not the
used-by-default video overlay.
xvinfo:
Adaptor #0: ATI Radeon Video Overlay 1 port at 57.
supports a bunch of attributes.
Adaptor #1: Radeon Textured Video 16 ports at 58
no port attributes
Is something using a lot of CPU time? run top, and look at the load
averages at the top right. (number of tasks waiting running/waiting to
run averaged over the last 5/10/15 minutes).
If it's not close to zero, something's keeping your CPU busy.
Is your CPU idling at low speed, like it should
I've been running 2.6.27-3 for the past couple days without problems.
Maybe the problems I had before really were due to overheating, since I
did knock over the case sometime shortly before trying 2.6.27-2.3 :(,
and I re-applied thermal paste on my CPU heatsink before trying
2.6.27-3. Still, even
Public bug reported:
Binary package hint: procps
sysctl keys don't start with sys.
This is
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494655
** Affects: procps (Ubuntu)
Importance: Undecided
Status: New
** Affects: procps (Debian)
Importance: Unknown
Status:
The coretemp scale change is normal, and is explained here:
http://kerneltrap.org/mailarchive/linux-kernel/2008/4/29/1661864
---
The thing is, the temperature is stored as a relative value in the CPU.
Relative to what, depends on the CPU model, can be 85°C or 100°C. Up to
kernel 2.6.24 we
** Also affects: casper (Ubuntu)
Importance: Undecided
Status: New
--
live cd from nfsroot breaks the nfs mount during bootup
https://bugs.launchpad.net/bugs/268005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
-t 7 is too short for my setup. -t 60 should be safe.
I was able to netboot the Hardy livecd (which detects my interfaces such
that eth1 is the one with the cable plugged in to it). (It does
boot=casper, not boot=nfs, so it doesn't normally look at ip= at all.)
I booted with break=mount, and
I marked this as also affecting casper, since it's with boot=casper, not
boot=nfs. Also, most nfsroot systems probably wouldn't have N-M
installed.
In Hardy and Intrepid, scripts/casper-bottom/23networking builds a
/etc/network/interfaces with
auto lo
iface lo inet loopback
auto eth0
iface
casper in Hardy (and maybe earlier) writes a /etc/network/interfaces with
auto eth0
iface eth0 inet manual
for each interface. This keeps N-M from touching it. Except in
Intrepid; see bug 268005 which is a dupe of this bug, since I didn't see
this before reporting it.
scripts/nfs doesn't
** Summary changed:
- Matrox Millennium G200 AGP fails 1074x768 resolution
+ Matrox Millennium G200 AGP fails 1024x768 resolution
--
Matrox Millennium G200 AGP fails 1024x768 resolution
https://bugs.launchpad.net/bugs/138920
You received this bug notification because you are a member of Ubuntu
Ubuntu can't detect what resolutions your monitor supports, and the
Monitor section of your xorg.conf doesn't list any.
I would mark this invalid, but one could consider it a bug that Ubuntu
doesn't have a better way to deal with situations where it can't autodetect
things. I don't think
It's not running. ps axuw | grep compiz doesn't return anything. And
the visual effects radio button on gnome-appearance-properties is set to
none.
Setting it to normal makes the screen go gray, then ~10 seconds later
back to normal with the radio button switched back to none. I didn't
see
unless this is a problem on other video cards that don't do 3D, this is
fixed.
** Changed in: compiz (Ubuntu)
Status: Incomplete = Fix Released
--
need to blacklist software direct rendering, e.g. ATI ES1000
https://bugs.launchpad.net/bugs/258469
You received this bug notification
This bug is a feature request for backward-compatible cmdline parsing.
NFSROOT is not a documented parameter in initramfs-tools(8), only
nfsroot.
IMHO, people who have old ROMs that append stuff that's no longer
compatible with current initramfs should do a two stage boot: have their
ROM load
posted to brainstorm as
http://brainstorm.ubuntu.com/idea/13027/
--
Include filesystem checking utilities into initramfs
https://bugs.launchpad.net/bugs/104697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
submitter says it's fixed for him. BTW, it's ok to change the status of
your own bugs. just click on the status line on launchpad, etc...
** Changed in: initramfs-tools (Ubuntu)
Status: New = Fix Released
--
/bin/sh:can't access tty; job control turned off
... but listed in /dev/disk/by-uuid and id but not when doing ls -l
/dev/disk/by-uuid ...
huh? Are you saying there are entries for your PATA disks in /dev/disk
/by-uuid, but ls -l doesn't list them?
What kind of PATA controller? post lspci output. (sorry, I don't feel
like reading MSI's
This is a linux bug, if linux doesn't detect your hard drives. The
linux package encompasses all the modules and config for loading them.
except blacklists in module-init-tools. upgrade that and initramfs-
tools to intrepid, too.
** Changed in: linux (Ubuntu)
Sourcepackagename: casper = linux
AFAIK, Ubuntu wants everything that outputs sound to go through
pulseaudio. (a software mixing daemon). Not everything supports pulse,
though, and will find the audio device unavailable if something else
already has it open through pulse.
sudo lsof /dev/snd/*
will almost always tell you what
casper finds devices not by looking for /casper/filesystem.squashfs, but
rather by checking .disk/casper-uuid.
in initramfs, scripts/casper:matches_uuid() looks like:
...
for try_uuid_file in $mountpoint/.disk/casper-uuid*
...
extract an initramfs with zcat | cpio -i, if you want to look at
*** This bug is a duplicate of bug 158976 ***
https://bugs.launchpad.net/bugs/158976
This is a dupe of
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/158976, which also
has some comments. e.g. I posted there about the device list to scan
not being updated as new devices are
This is basically a wishlist bug for casper to build /etc/fstab. People
using the GNOME gui from the livecd can get partitions mounted through
nautilus and GNOME's device manager stuff, which can handle removable as
well as static drives. /etc/fstab isn't needed for that.
It would be nice to
I tried mount from an initramfs, while trying to boot the livecd with
nfsroot. Regular mount works on Hardy, but the kernel prints warnings
that it's providing a workaround for not having a lockd running. This
support is no longer present in Intrepid's 2.6.27.
In Hardy, see
uhm? the bug is only appering in intrepid test release alpha 4 live cd.
, havent tested later live cd relases then alpha4.
but in installd alpha 4 intrepid testing
At this point Linux didn't see your PATA drives when you booted from
the installed system, either, right?
and later updated
I tried this again: I booted the i386 Intrepid alpha5 CD, and installed
lm-sensors. My idle temps are still 59C, which doesn't agree with the
BIOS or 2.6.24, which idles at ~42C (coretemp sensor).2x burnP6 only
gets me up to 72C on each core. Ambient temp is somewhat lower than
before... I
It sort of works to boot Intrepid's livecd with TORAM=yes, but you have
to give it a kick with ALT+SYSRQ+E when it gets stuck after the message
from the squashfs module.
The code for doing stuff if $TORAM is set (to non-zero length, IIRC)
is there, but nothing sets $TORAM. So do it yourself
The Hardy netboot issues can be debugged by booting with break=mount debug=y,
then running
t=/dev/tty2; sh $t $t 2$t # repeat for tty3 if you want
exit
boot will continue, and hang because the network is down. You can
debug by switching to another console and looking at /casper.log (where
I wasn't able to try this again until now, since I had limited time in the
machine room and I had trouble netbooting a livecd.
(see https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/268005...)
This bug doesn't seem to be present on this hardware anymore in the
i386 Hardy alpha5
This is only a problem with break=premount or earlier. break=mount
happens after hal/udev have loaded drivers for everything.
Note that some servers don't _support_ ps/2 keyboards anymore. e.g. I
have a rack of Dell PE1950 machines with a KVM-over-IP that connects to
1 USB port and their VGA
I have a workaround for nfsroot booting Intrepid:
boot with break=init
touch /cow/etc/init.d/NetworkManager
exit
You will boot normally, but N-M won't run (because files in /cow take
precedence over files in filesystem.squashfs, so it's init script is
empty).
--
live cd from nfsroot breaks
Any way of preventing NetworkManager from starting (or from bringing
your interface down and then up) is sufficient. Or maybe just pre-
caching the files it will try to access while the network is down, if
N-M gets stuck trying to access some files while the network is down.
--
live cd from
I have booted an i386 with 1.5GB of RAM from Intrepid alpha5 on a USB
stick, with TORAM=yes + a sysrq kick, and it did work.
Actually, what worked was PXE booting with TORAM=yes.
TORAM=yes doesn't work with isoscan/filename=, which is how I had my
USB drive set up.
--
toRam or copy2Ram (run
I booted a machine with a USB and a PS/2 keyboard from an i386 Intrepid alpha5
USB drive, with break=premount.
panic() should run (after the modprobe for ps/2 keyboards):
if ! grep -q '^H:.*kbd' /proc/bus/input/devices ; then
# no keyboard? Try USB.
modprobe uhci-hcd
modprobe ohci-hcd
** Tags added: patch
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed = In Progress
--
USB Keyboard drivers not loaded in initramfs
https://bugs.launchpad.net/bugs/229732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hardy does not suffer from this bug. The problems I was having with Hardy were
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/182940, because
as I said, Hardy's kernel detected interfaces in opposite order to how they're
labeled on the chassis.
I netboot Hardy at home on my
301 - 400 of 547 matches
Mail list logo
