FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 06-10-2008, 12:36 PM
Frans Pop
 
Default Bug#485609: Problem with device renaming and grub after clean install

reassign 485609 linux-2.6 2.6.24-7
retitle 485609 modules.pcimap lists both pata_sis and sis5513 for [1039:5513]
thanks

On Tuesday 10 June 2008, gray@shadowglade.net wrote:
> It seems that the kernel is remapping /dev/hda using the scsi
> emulation, which I did not enable and grub doesn't know about during
> the installation. Oddly I have the same kernel installed for the
> unstable partition and I do not run into the same problem. I took a
> look at the kernel config on both and nothing stands out.

Reason for this is that the Debian kernel provides two modules that
support your IDE controller:
$ grep 1039.*5513 /lib/modules/2.6.24-1-amd64/modules.pcimap
pata_sis 0x00001039 0x00005513 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
sis5513 0x00001039 0x00005513 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0

Which gets loaded is somewhat random and apparently the installer used
the second (setting the system up to use /dev/hda), while after the
reboot the first was used (changing the device name to /dev/sda).

This is a known issue listed in the errata.

Reassigning your report to the kernel team because AFAIK we should not
be listing two modules for the same controller.

Cheers,
FJP


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 06-10-2008, 12:39 PM
Frans Pop
 
Default Bug#485609: Problem with device renaming and grub after clean install

On Tuesday 10 June 2008, Frans Pop wrote:
> Which gets loaded is somewhat random and apparently the installer used
> the second (setting the system up to use /dev/hda), while after the
> reboot the first was used (changing the device name to /dev/sda).

You can work around this issue by blacklisting one of the modules when you
boot the installer:
http://www.debian.org/releases/testing/i386/ch05s02.html.en#installer-args

For example:
sis5513.blacklist=yes



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 06-10-2008, 09:55 PM
 
Default Bug#485609: Problem with device renaming and grub after clean install

Frans Pop wrote:
> reassign 485609 linux-2.6 2.6.24-7
> retitle 485609 modules.pcimap lists both pata_sis and sis5513 for [1039:5513]
> thanks
>
> On Tuesday 10 June 2008, gray@shadowglade.net wrote:
>> It seems that the kernel is remapping /dev/hda using the scsi
>> emulation, which I did not enable and grub doesn't know about during
>> the installation. Oddly I have the same kernel installed for the
>> unstable partition and I do not run into the same problem. I took a
>> look at the kernel config on both and nothing stands out.
>
> Reason for this is that the Debian kernel provides two modules that
> support your IDE controller:
> $ grep 1039.*5513 /lib/modules/2.6.24-1-amd64/modules.pcimap
> pata_sis 0x00001039 0x00005513 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
> sis5513 0x00001039 0x00005513 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
>
> Which gets loaded is somewhat random and apparently the installer used
> the second (setting the system up to use /dev/hda), while after the
> reboot the first was used (changing the device name to /dev/sda).
>
> This is a known issue listed in the errata.
>
> Reassigning your report to the kernel team because AFAIK we should not
> be listing two modules for the same controller.
>
> Cheers,
> FJP

Why am I not surprised that its related to the crappy sis chipset on this
motherboard? Anywho, thanks for the help. Now I can go on and test more of testing.

Interesting note, although I have both modules in my Unstable install as well,
the kernel loads them both in unstable but never swaps which one is in control.
I dunno. If I see anything useful I will let you know.

Thanks!

Matthew



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-19-2008, 10:42 PM
 
Default Bug#485609: Problem with device renaming and grub after clean install

Hi Frans,

I know we discussed this lomg ago but I finally got around to trying the
workaround and even some derivative ideas. None of this is critical but I send
it to you as some general feedback. I read over the errata you referred to and
the directions you referred to as well.

First, I tried to fix the drive naming on the actively installed kernel by
blacklisting the pata_sis module using /etc/modprobe.d/blacklist. This had no
effect on the module or the drive device assignment. I tried blacklisting the
sis5513 module also to no avail. That seemed really strange to me. Then again I
am not entirely positive how changing that on the file system is going to
carryover to the next boot process.

Then I tried to run the same installer snapshot using either

installgui sis5513.blacklist=yes
or
installgui pata_sis.blacklist=yes

...like you suggested. In both cases the kernel responded with an option
unrecognized, option ignored message at the very beginning of the boot process.
So it seems as though I can't use those arguments for some reason. Sorry to be a
pest, but I thought you should know that the suggestion didn't work for me. It
is very strange that the blacklisting didn't work either. If you have any
recommendations let me know. After the upcoming freeze I will retest this whole
process again. It won't hurt me a bit and it may well start working.

Would a problem with the blacklisting argument be serious? Or did I overlook
something?

Thanks,

Matthew McGuire


Frans Pop wrote:
> On Tuesday 10 June 2008, Frans Pop wrote:
>> Which gets loaded is somewhat random and apparently the installer used
>> the second (setting the system up to use /dev/hda), while after the
>> reboot the first was used (changing the device name to /dev/sda).
>
> You can work around this issue by blacklisting one of the modules when you
> boot the installer:
> http://www.debian.org/releases/testing/i386/ch05s02.html.en#installer-args
>
> For example:
> sis5513.blacklist=yes




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 10:51 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org