[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#290368: Further information

I've done a little more research so I can add a little to this: 

> My sound card didn't work (couldn't find /dev/dsp). I installed

Still no idea about this! Any advice would be good. I have a fairly standard card:

> 0000:00:0b.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)

and if I hadn't thought to try installing alsa-related packages & then
run the config I would have been stuck without sound.

> /media/cdrom0 & /media/cdrom1 were not automatically created. I created

Any suggestions? Is the d-i normally responsible for this? Or is it
handled by udev/hal? Where should I start looking & what package should
I be reporting this against?

> cfdisk complains that "FATAL ERROR: Bad logical partition 9: enlarged
> (should be called hda4, not hda9?)

I still don't know if this is a bug in cfdisk or in the initial
partitioning. It does seem strange that the numbering isn't sequential.
I should also mention that it was actually the d-i bundled with ubuntu
warty which created the partition. I just pointed my RC2 install to it
when replacing warty with sarge. I'm guessing that there is a problem
of some sort with my partitioning as 'parted' gives me:

Using /dev/hda Warning: Unable to align partition properly.  This
probably means that another partitioning tool generated an incorrect
partition table, because it didn't havethe correct BIOS geometry.  It
is safe to ignore,but ignoring may cause (fixable) problems with some
boot loaders.

Is there anything I can do to repair my partitions?

> I would have liked it if the debian installer had added entries to my
> fstab for all my partitions. Other linux distros do this by default & I

I ended up just writing the fstab with reference to 'man fstab' & 'man
mount'. I'd still be interested in a more automated way of doing it. I
imagine this is not done automatically for security/safety reasons but
I also think it is something that would be very welcome in the
installer. I'd suggest a question "Would you like the debian installer
to allow users to access pre-exisiting partitions?" which would then
run whatever code it is that the debian-derived Knoppix uses to
generate the fstab/mount points for partitions not already listed in
the fstab. It would be nice if the user could easily get back to this
as well.. Should I submit this as a wish-list bug on the d-i? Or am I
talking about functionality that already exists?

> When autodetected my LCD monitor (LG Flatron L1710B) & video card (ATI
> Radeon 9600) left X set to a maximum resolution of 800x600. Native res
> for my monitor is 1280x1024. 'dpkg-reconfigure xserver-xfree86' & some
> guessing at the more advanced options left it with the right
> resolution. 

Is there a good place to report this lower than expected maximum
resolution? Maybe against X?

> Out of interest, is there a way to get back to the X &
> keyboard configuring parts of the installer? 'base-config' only seems
> to give me a subset of the functions of the installer.

Again, still interested! Anyone able to answer this?

> I probably would have prefered if the installer had been less
> conservative and gone straight for the 2.6 kernel. Is there a way to

I can answer this! To install the 2.6 kernel 'use the "linux26" boot
method for the installer' although in RC2 '2.6 installer has the
potential to mess up Windows partitioning' See errata:


Reply to: