http://bugzilla.kernel.org/show_bug.cgi?id=8034





------- Comment #25 from [EMAIL PROTECTED]  2007-09-19 02:00 -------
(In reply to comment #23)
> Arne, so, the harddrive is detected on 2.6.18 (SL102) but it doesn't get
> detected if you upgrade the kernel to 2.6.22, right?  This can be one of the
> following two things.
> 

NOTE: I no longer have OpenSuse installed. Current install is Fedora8 test2

> 1. Distro's initrd generation is messed up and fails to load sata_nv.  In 
> SL102
> emergency shell, run "cat /proc/modules" and see whether sata_nv is there.  If
> not, run "insmod /lib/modules/{version}/kernel/drivers/ata/sata_nv.ko" and see
> whether devices get detected.
> 
> 2. Something went wrong with sata_nv or other component and sata_nv can't
> detect the device anymore.
> 
> In any case, full boot log will be very helpful in determining what's going 
> on.
>  If you have a second machine, setting up netconsole is usually the easiest 
> way
> (Documentation/networking/netconsole.txt) to get boot log.  I'm not sure
> whether this would work with root mount failure tho (module for network
> interface should either be in the kernel or initrd).
> 

BUT let me add some info regarding these previous kernels:

a:) Release version Fedora core 6  - did get installed, but
failed on receiving upgraded kernels. 

b:) Release Fedora7 + different test releases all failed.
( in the above, this include both i386 and x86_64 )

c:) However, I did download something from Cambridge?-and 
got some Fedora7 installed with ZEN. But as I don't have
a clue what is involved, I gave it up.

d:) A reason for this purchase, was to get wireless. While
in contact with bcm43xx, I tried OpenSuse 10.2 which installed.
Then downloaded a more recent kernel. Used clone-config, in
order to get comparable versions. Did report this (comment #14)

e:) The most troublesome issue has been the touchpad. Even after
removing "tapping" ( gsynaptics or ksynaptics ) it is still
troublesome. However it is a good indicator when things are
very wrong, like it start executing applications on it's own.
( a hellish device that has cost me lot of grief )

                 ------------------

Comments to what you said:

1.  I had the results as presented in (comment#19)
2.  At bcm43xx - similar questions as yours came up.
3.  Followed directions:
3.1 From YaST: libata and scsi_mod added to "INITRD MODULES"
3.2 executed : /sbin/mkinitrd
3.3 restarted: no apparent change 
3.4 power off, restart hours later - didn't work. Machine dead,
    no lights, no display, no keys working. 
3.5 Pulled out the RTC battery, and it did the trick.
3.6 Checked HP and found a report that did discribe this experience.
    Did install a BIOS upgrade ( done through Vista ), just in case.
    But also because perhaps it would give some new settings ? but nope.
3.7 Because of info (comment#16) I installed Fedora8 test2, as OpenSuse
    didn't have anything matching the kernel mentioned.

In closing: - I think what I said in (comment#19) is correct. Have compared
both situations, and the disk dies out - don't respond to "resume" as
described.


NOTE !  - you may have expected to see more things installed, more io to be
reported. What I have reported - is kernels up until that latest OpenSuse.
note (comment#16) - I have not supplied anything what the machine may
give me now.

If you compare with Florian, my chipset isn't in the kernel until recently.
So, a lot of devices are not detected. The chipset enable that bridge, is
what it seem like to me.

This isn't a computer, it is a "movie/game/player". The chipset include
encryptions/decoders on all "steams". It may be used for pay by download
movies,
and much more, mp3, you name it. Microsoft have the keys that may disconnect
us.

So ?  - I am tempted to return it, see if something with a better keyboard and
screen resolution can be found. But that isn't easy, as most are pretty much
the
same, geared towards the same marked. 

//ARNE 


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to