#10041: [PM] system unbootable after driver tweak (and /still/ unbootable after removing the offending driver ?!) -----------------------+------------------------------------- Reporter: ttcoder | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1/Package Management Keywords: | Blocked By: Blocking: | Has a Patch: 0 Platform: All | -----------------------+------------------------------------- This is with the 21st of Sep. PM-branch build (a few days before the merge). Can try with a more recent nightly if necessary. I have a (pre-built) version of the hda driver that I copy to new installs of Haiku to make them "multi-out-jacks" aware (pending integration of my changes some day). I have a 3 line script that shuts down media_server, unzips the driver, relaunches media_server ..etc. I tried to do the same thing as usual in a PM nightly, just adding {{{non- packaged}}} to the {{{config/non-packaged/add-ons ..etc}}} filepath to unzip the driver to, and... it made the system unbootable, block on the third icon at boot, consistently (found out that if I enable "on screen debug output" it allows to boot to the desktop, so maybe the problem is tied to the weird timing problems I've had on this Asus F2A55M mobo earlier). There are separate issues I should file about this maybe (should the Migration wiki document explain how to do this correctly, maybe non- packaged is not the right place to put it? or did I do it correctly but there's an issue with the hda driver ?), but in this ticket I'll focus on something that seems worrying at first, in italics for emphasis :-).. : ''Booting from another partition, I have removed the hda driver and its audio/hmulti/hda symlink and Haiku is _still_ unbootable'' Ok so the package code is not state-less, no problem, find the "state", right ?. So I Iooked into "administrative" directories ..etc and did not see anything that could explain it.. So the system is back to what it was (in appearance at least) before I changed the driver, and yet it still refuses to boot up. What am I missing ? Something's damaged or corrupted by my driver "upgrade", in the packagefs maybe ? -- Ticket URL: <http://dev.haiku-os.org/ticket/10041> Haiku <http://dev.haiku-os.org> Haiku - the operating system.