Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Graphics error after boot menu, boot unsuccessful.
#11
Thank you so much for the info!

 I managed to get the AntiX 23.2 runit image downloaded, tried to DD it to flash drive, actually bricked one. Other one I was barely able to revive? Honestly unsure. It'll boot into the bootloader for DSL2024 but picking the first boot option no longer heads into rainbow snow, just flashing cursor in top left. Other boot modes return snow as expected thus far. 

Something I can say with certainty is that the netbook will run on a 6.x kernel, as I tested with tinycore 14. It also runs 5.1x kernels on 12 and 13. Obviously they're a bit different but if such tiny packages have the drivers/wiring required to operate the screen    Huh . It also runs on Debian 12.7, albeit unusably slow. I believe that is the newest kernel. 

Tiny core 14 uses xvesa, has zero issues. So maybe the issue is with Xorg? Will update more later tonight, still trying to wrangle the different flash drives into working. In older Linux distributions, choice between xorg and xvesa at boot menu was a simple flag, haven't been able to find one for DSL so far. Honestly stumped, especially as to how I managed to brick a flash drive entirely with the AntiX ISO and temporarily brick another as well.  Huh Hardware, am I right?  Big Grin

Thanks again!

EDIT:
After much messing around, managed to get TinyCorePlus15 to boot up and run, using a 6.1.x ish kernel, the plus image having wireless support so that I could install inxi to compare outputs. Oddly enough, the inxi program there recognizes the graphics as the HD6290 yet names the driver as N/A. As for display options, it states TinyX Xvesa, driver: vesa. I believe you are right, and xorg may simply not support the 6000 series. So it's looking like I either need to tear into the DSL iso and reroll, or force use of Xvesa. Resolution will take a bit of a hit at 1024x600 but at least it would run? 

Something to do with installing AntiX on the second flash drive definitely did something very strange to it, was able to halfway restore it, can install other images and boot from them successfully, yet the text displayed looks like something straight out of "The Matrix" and is unusable  Huh 
  Big Grin I have no idea what the cause, brand new flash drive. 

I am unsure if swapping the version of X.org and it's dependencies to an earlier version such as the 1.12.4 which was used by Slitaz would be an effective way of fixing the issue, or if that'll just end in dependency clobbering and breaking the whole system. Will attempt and see, possibly try an AntiX kernel from an earlier release, hopefully not lose any more flash drives in the process. I'm running out!  Tongue
Will update. Thanks again for your time.
Reply
#12
Currently rolling a new "linuxfs" image with updated x.org.conf.in and amdgpu blob installed, will see if I can manage to pack it back up into something usable or if I broke it  Big Grin hopefully I'll have some new results to share soon. Probably should have tested changes one at a time for the sake of troubleshooting but... I didn't. Oh well.

Update:
Rerolled .iso, was able to get the iso itself bootable on flash drive after using iso hybrid, still will not boot into usable graphics no matter what boot parameters I set. AMD blob is within firmware files, can't invoke xvesa, can't invoke Radeon drivers. I am at a bit of a loss here. Perhaps someone with more in depth kernel experience than I have could figure this out, but I simply don't understand where or how to point the system to use either xvesa or the correct drivers for Xorg.
Reply
#13
OK you beat me--wrote a big response that should be fixed/revised but I'll just tack it on the end of this right now.

First, are you referring to DSL or to AntiX that you re-did the image in?

Also, can you append a 3 and boot in text mode?

----------------------------------
Yeah, tinycore isn't going to help us debug the Debian/AntiX tree because it indeed uses tinyX and they alone (tinycore devs) are (heroically!) keeping it alive at all. And, in general, one can't just mix and match entire subsystems as things are built together.

Ideally, we need to figure out if proper "normal" Xorg has the support in the
xserver-xorg-video-radeon

(Note: xserver-xorg-video-ati seems to be for older chips but it says to leave it in there for autodetection unless you're sure you don't need it )

and if we need the
firmware-amd-graphics
blob to be able to recognize the device. Getting AntiX full or Bookworm to boot would likely give us this answer. Onward.

If we root-around for your chip, the GPU seems to be Cedar so that looks good for what we can tell, anyway:

apt-cache show xserver-xorg-video-radeon

Package: xserver-xorg-video-radeon
Source: xserver-xorg-video-ati
Version: 1:19.1.0-3
Installed-Size: 869
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Architecture: i386
Provides: xorg-driver-video
Depends: libc6 (>= 2.17), libdrm-radeon1 (>= 2.4.39), libgbm1 (>= 8.1~0), libudev1 (>= 183), xorg-video-abi-25, xserver-xorg-core (>= 2:21.1.1)
Suggests: firmware-amd-graphics
Description-en: X.Org X server -- AMD/ATI Radeon display driver
This package provides the 'radeon' driver for the AMD/ATI cards. The
following chips should be supported: R100, RV100, RS100, RV200, RS200,
RS250, R200, RV250, RV280, RS300, RS350, RS400/RS480, R300, R350, R360,
RV350, RV360, RV370, RV380, RV410, R420, R423/R430, R480/R481,
RV505/RV515/RV516/RV550, R520, RV530/RV560, RV570/R580,
RS600/RS690/RS740, R600, RV610/RV630, RV620/RV635, RV670, RS780/RS880,
RV710/RV730, RV740/RV770/RV790, CEDAR, REDWOOD, JUNIPER, CYPRESS,
HEMLOCK, PALM, SUMO/SUMO2, BARTS, TURKS, CAICOS, CAYMAN, ARUBA, TAHITI,
PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI, MULLINS, KAVERI, HAWAII.

Check (CEDAR), and firmware is a suggest but not dependency.

Soooo...this should work(?) (given the higher-labor customizing to get the firmware in). Thinking it'll find the module if we just give it firmware. Wikipedia shows a lot of support /drm/radeon (but of course yours isn't listed) and there's the 2011 gap right where yours belongs.

Diving in the radeon modinfo, it looks like the minimal Cedar firmware files are:

firmware: radeon/CEDAR_smc.bin
firmware: radeon/CEDAR_rlc.bin
firmware: radeon/CEDAR_me.bin
firmware: radeon/CEDAR_pfp.bin

but I'm far out of my depth here so those might not be all you need--call it a start if you're trying to keep it minimal when you make a new image.

As a suitable "also-ran" solution, some sort of vesa support would be acceptable, but it'll need to be in the current Xorg as that's what AntiX releases (or in bookworm), ie, not xvesa (xvesa is long-gone, too).

There is also
xserver-xorg-video-amdgpu
but that seems to be for "3rd generation" chips released after 2015. You can see that it depends on the
xserver-xorg-video-radeon

Yeah, so if Xorg works at all for your 6290 chip, it's the current -radeon that should be the right package.

If I have this straight, you are unable to boot the full 23.2 AntiX but it just sits there flashing cursor or do you get a grub menu? I've not used that 23.2 image (any of them) so I don't know if you need to run isohybrid on them before you do the dd (?). If the machine can't even find the image to boot, I'd do the isohybrid & re- mkfs.vfat & re-dd. If you're doing all this stuff in ventoy or something else, I'd have no idea how to fix that.

So we still have the same questions. If you got it going in AntiX or Debian something, maybe we start there (?) Otherwise--yeah--you'd be off on a different distro path.
Reply
#14
Okay, after some more testing, I have managed to get Antix23.2 Runit Core to boot with no errors, correctly changed resolution from 800x600 or whatever the grub menu runs in, to 1366x768 about halfway through booting up. Ran Inxi -Fv7 and got the following for output:
(Hand typing this on another computer, sorry for formatting) 

Graphics:
   Device-1: AMD Wrestler [Radeon HD 6290] vendor: Acer Incorporated ALI driver: radeon v: kernel
    arch: TeraScale-2 ports: active: LVDS-1 empty: HDMI-A-1,VGA1 bus-id: 00:01.0 chip-ID: 1002:9807
    class-ID: 0300
   Device-2: Chicony WebCam driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
     bus-ID: 2-1:2 chip-ID: 04f2:b209 class-ID: 0e02
   Display: server: No display server data found. Headless machine? tty: 124x34
   Monitor-1: LVDS-1 model: Chi Mei Opto 0x1113 res: 1366x768 dpi: 136
      size: 256x144mm (10.08x5.67") diag: 294mm (11.6") modes: max: 1366x768 min:640x480
   API: N/A Message: No API data available in console. Headless machine?

So, while this isn't the base or full edition of AntiX23.2 with desktop environment, it does boot into text mode just fine and appears to be able to properly display on this graphics card. Doesn't appear to be using Xorg, does appear to be using the Radeon driver... its a start? Radeon driver is present within the DSL2024.R7 firmware directory, just need to force it to use it.

Can't determine why DSL won't allow text only mode yet at this time. Will attempt to build up a functioning desktop using the package manager and Xorg within Antix23.2-runit-core, see if I can get it to run X, and will update afterwards. I figure if I have to install and configure the DE myself, maybe I'll learn something needed to tell DSL how to do what I want in the process? Huh

Noted on xvesa, I had no idea it had been discontinued! Apparently a lot has changed since the last time I was mucking around inside of a distribution besides TinyCore or some older variant of BSD.

Thanks again for your time!
Will keep updated.

UPDATE:
Have some success! Sort of. AntiX23.2-runit-core will properly display graphics via Xorg.
Was able to use the package manager within AntiX-cli-cc preinstalled application to install Xorg, and XFCE4. Installation unremarkable, instant startup into remarkably snappy DE upon using startx as root, no configuration required. Post being written from within AntiX23.2-runit-core.

With XFCE4 running, Inxi -Fv7 returns as thus:

Graphics:
Device-1: AMD Wrestler [Radeon HD 6290] vendor: Acer Incorporated ALI
driver: radeon v: kernel arch: TeraScale-2 ports: active: LVDS-1
empty: HDMI-A-1,VGA-1 bus-ID: 00:01.0 chip-ID: 1002:9807 class-ID: 0300
Device-2: Chicony WebCam driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 2-1:2 chip-ID: 04f2:b209 class-ID: 0e02
Display: server: X.org v: 1.21.1.7 compositor: xfwm4 v: 4.18.0 driver: X:
loaded: radeon unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
Monitor-1: LVDS-1 mapped: LVDS model: Chi Mei Opto 0x1113 res: 1366x768
hz: 60 dpi: 136 size:256x144mm (10.08x5.67") diag: 294mm (11.6") modes:
max: 1366x768 min: 640x480
API: OpenGL Message: Unable to show GL data. glxinfo is missing.

So, there's that. I will attempt to pull my Xorg configuration file to see what it says, hopefully it's shorter than the one which comes pre-installed with DSL2024.R7, as that file is large and complex. At this point, I've determined that AntiX23.2 has zero issue displaying graphics on this netbook (AO722) as I'm posting this from said netbook via Palemoon while running AntiX23.2. Issue with DSL seems to be in configuration, not sure yet. Maybe it's missing a driver that the standard Xorg package includes, but I didn't see anything special besides drm-radeon, pertaining to radeon graphics cards, while installing. Seeing as this firmware is also included in the DSL2024.R7 ISO, it should just be a matter of invoking it properly? Unsure. Will update with more info as I figure it out.
Reply
#15
Alright, here's the contents of my Xorg.conf.in file:

Section "ServerFlags"
    Option "DontZap" "Off"
    Option "AllowMouseOpenFail" "true"
    Option "blank time" "0"
    Option "standby time" "0"
    Option "suspend time" "0"
    Option "off time" "0"
EndSection
 
Section "InputClass"
    Identifier "middle button emulation class"
    MatchIsPointer "on"
    #Option "Emulate3Buttons" "on"
    #Option "Emulate3Timeout" "50"
EndSection
 
Section "InputDevice"
    Identifier "Touchpad"
    Driver "synaptics"
    Option "Device" "/dev/psaux"
    Option "Protocol" "auto-dev"
    Option "LeftEdge" "1700"
    Option "RightEdge" "5300"
    Option "TopEdge" "1700"
    Option "BottomEdge" "4200"
    Option "FingerLow" "25"
    Option "FingerHigh" "30"
    Option "MaxTapTime" "180"
    Option "MaxTapMove" "220"
    Option "VertScrollDelta" "100"
    Option "HorizScrollDelta" "0"
    Option "MinSpeed" "0.09"
    Option "MaxSpeed" "0.18"
    Option "AccelFactor" "0.0015"
    Option "SHMConfig" "on"
EndSection
 
Section "InputDevice"
    Driver "synaptics"
    Identifier "ALPS Touchpad"
    Option "Device" "/dev/input/mice"
    Option "Protocol" "event"
    Option "LeftEdge" "130"
    Option "RightEdge" "840"
    Option "TopEdge" "130"
    Option "BottomEdge" "640"
    Option "FingerLow" "7"
    Option "FingerHigh" "8"
    Option "MaxTapTime" "180"
    Option "MaxTapMove" "110"
    Option "EmulateMidButtonTime" "75"
    Option "VertScrollDelta" "20"
    Option "HorizScrollDelta" "0"
    Option "MinSpeed" "0.25"
    Option "MaxSpeed" "0.50"
    Option "AccelFactor" "0.030"
    Option "EdgeMotionMinSpeed" "200"
    Option "EdgeMotionMaxSpeed" "200"
    Option "UpDownScrolling" "1"
    Option "CircularScrolling" "1"
    Option "CircScrollDelta" "0.1"
    Option "CircScrollTrigger" "2"
    Option "SHMConfig" "on"
EndSection
 
Section "InputDevice"
    Identifier "Appletouch"
    Driver "synaptics"
    Option "Device" "/dev/psaux"
    Option "Protocol" "auto-dev"
    Option "LeftEdge" "100"
    Option "RightEdge" "1120"
    Option "TopEdge" "50"
    Option "BottomEdge" "310"
    Option "FingerLow" "25"
    Option "FingerHigh" "30"
    Option "MaxTapMove" "220"
    Option "TapButton1" "1"
    Option "TapButton2" "3"
    Option "TapButton3" "2"
    Option "MinSpeed" "0.79"
    Option "MaxSpeed" "0.88"
    Option "AccelFactor" "0.0015"
    Option "SHMConfig" "on"
EndSection
 
Section "Monitor"
    Identifier "Monitor0"
    VendorName "unknown"
    ModelName "unknown"
    Option "DPMS" "true"
    HorizSync    30-75
    VertRefresh  55-70
EndSection
 
Section "Device"
    Identifier  "Card0"
    Driver "@@XMODULE@@"
    BoardName "unknown"
 
    Screen 0
  #Option "UseDisplayDevice" "dfp"
  #Option "MonitorLayout" "crt,crt"
  #BusID  "PCI:1:0:0"
  #Option "sw_cursor" # needed for some ati cards
  #Option "hw_cursor"
  #Option "NoAccel"
  #Option "ShowCache"
  #Option "ShadowFB"
  #Option "UseFBDev"
  #Option "Rotate"
    Option "UseInternalAGPGART" "no"
 
    Option "XAANoOffscreenPixmaps" "true"
 
# savage special options, use with care
  #Option "NoUseBios"
  #Option "BusType" "PCI"
    Option "DmaMode" "None"
 
# nvidia special options, use with care
    Option "CursorShadow" "1"
    Option "CursorShadowAlpha" "63"
    Option "CursorShadowYOffset" "2"
    Option "CursorShadowXOffset" "4"
    Option "FlatPanelProperties" "Scaling = native"
    Option "NoLogo" "true"
    Option "UseEDID" "true"
    Option "AddARGBGLXVisuals" "true"
    Option "RenderAccel" "true"
  #Option "AllowGLXWithComposite" "true"
EndSection
 
Section "Device"
    Identifier  "Card1"
    Driver "@@XMODULE@@"
    BoardName "unknown"
 
    Screen 1
  #Option "MonitorLayout" "crt,crt"
  #BusID  "PCI:1:0:0"
EndSection
 
Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    DefaultColorDepth 16
   
    SubSection "Display"
    Depth 8
    @@MODES@@
    EndSubSection
    SubSection "Display"
    Depth 15
    @@MODES@@
    EndSubSection
    SubSection "Display"
    Depth 16
    @@MODES@@
    EndSubSection
    SubSection "Display"
    Depth 24
    @@MODES@@
    EndSubSection
    SubSection "Display"
    Depth 32
    @@MODES@@
    EndSubSection
   
    # Only the official NVIDIA driver supports twinview
    # these setting are an example
    Option "TwinView" "false"
    Option "SecondMonitorVendorName" "unknown"
    Option "SecondMonitorModelName" "unknown"
    Option "SecondMonitorHorizSync" "30-75"
    Option "SecondMonitorVertRefresh" "55-70"
  #Option "MetaModes" "1024x768, 1024x768"
    Option "TwinViewOrientation" "RightOf"
    Option "ConnectedMonitor" "dfp,dfp"
EndSection
 
Section "DRI"
    Mode 0666
EndSection
 
Section "Extensions"
    Option "Composite" "Enable"
EndSection

Unsure if also necessary, but here is my Xsession.options as well:

# $Id: Xsession.options 189 2005-06-11 00:04:27Z branden $
#
# configuration options for /etc/X11/Xsession
# See Xsession.options(5) for an explanation of the available options.
allow-failsafe
allow-user-resources
allow-user-xsession
use-ssh-agent
use-session-dbus

So, with these bits of information, can we figure this out? After using XFCE4 on the hardware within AntiX23.2 with success, I am optimistic.

Thanks again for your time!

EDIT:

Did some basic visual comparison of the xorg.conf.in files between DSL2024.R7 and the AntiX23.2-runit-core which is successfully running XFCE4, do not see much difference at all. Confused as to why this would be, did the Xorg package that I installed have drivers included which are not included within the DSL2024 Radeon package? Why won't DSL auto-configure into running the same way that the installed Xorg package from AntiX base repo will?
Reply
#16
Woo-hoo--nice work Smile Perfect. No, I'm not sure we can assume that its the same firmware in 23.2-core and in RC7 as John is doing a size-based balancing act to support as much as he can in a CD. They _might_ be the same for ATI/AMD but we don't know that yet until we look. I'm still new to this entire tree, myself, so I'm thinking how to get us a diff w/o having to do a frugal install of both a clean RC7 *and* clean 23.2-core. At the moment, I think we need to diff the package lists and find a way to do the same for relevant /usr/lib/firmware for the ATI/AMD GPU stuff.

Elsewhere, and maybe unrelated, I did see someone report a boot freeze before display owing to a network driver support problem, too. Maybe nothing, maybe something. I'd save yourself some text files with the lspci and lsmod info as well as that inxi and the conf, just for reference.
Reply
#17
(11-12-2024, 02:20 PM)grindstone Wrote: Woo-hoo--nice work Smile  Perfect.  No, I'm not sure we can assume that its the same firmware in 23.2-core and in RC7 as John is doing a size-based balancing act to support as much as he can in a CD.  They _might_ be the same for ATI/AMD but we don't know that yet until we look.  I'm still new to this entire tree, myself, so I'm thinking how to get us a diff w/o having to do a frugal install of both a clean RC7 *and* clean 23.2-core.  At the moment, I think we need to diff the package lists and find a way to do the same for relevant /usr/lib/firmware for the ATI/AMD GPU stuff. 

Elsewhere, and maybe unrelated, I did see someone report a boot freeze before display owing to a network driver support problem, too.  Maybe nothing, maybe something.  I'd save yourself some text files with the lspci and lsmod info as well as that inxi and the conf, just for reference.

I will do so shortly, and post them here. I apologize for the post "spam" but I am currently unable to find any other way to save the files due to hardware detection issues within the AntiX core wrt SD cards, my last USB is in use for the AntiX live system.

Aside from performing a frugal install, could I not simply mount the ISO images of both on loopback and extract their respective "linuxfs" files? Not familiar with any sort of Diff program so I'll need to look that up but it appears that the AntiX23.2 package manager has a Diff tool easily available, so should be able to figure that out. If not, can always use eyes. Big Grin

Boot freeze before display would make sense, I've used waitusb=5 a lot on the older Aspire ZG5 to get distributions to properly boot up with the 8gb flash drive from ~2010 soldered to the inside of the USB port and tucked into the space where the HDD used to be, quick fix when it failed a long time ago... I've been meaning to update it to a modern flash drive as it was already quite worn out when pushed into service in this manner nearly 15 years ago but have been using primarily TORAM distributions as if they're ROM files and SD cards as the storage device for the files I wish to save, in an attempt to make the flash drive last as long as possible, or else I'd simply install DSL on that and not look back! Big Grin

Very excited, thanks again for all of your help!
Will update soon.

Okay, heres the output of LSMOD:

Module                  Size  Used by
ccm                    20480  6
uvcvideo              90112  0
videobuf2_vmalloc      16384  1 uvcvideo
videobuf2_memops      16384  1 videobuf2_vmalloc
videobuf2_v4l2        24576  1 uvcvideo
videobuf2_common      45056  2 uvcvideo,videobuf2_v4l2
videodev              172032  3 uvcvideo,videobuf2_common,videobuf2_v4l2
mc                    28672  4 uvcvideo,videobuf2_common,videodev,videobuf2_v4l2
wl                  6160384  0
joydev                20480  0
acer_wmi              20480  0
wmi_bmof              16384  0
sparse_keymap          16384  1 acer_wmi
ath9k                102400  0
ath9k_common          16384  1 ath9k
kvm_amd                73728  0
ath9k_hw              421888  2 ath9k,ath9k_common
snd_hda_codec_conexant    16384  1
radeon              1331200  8
snd_hda_codec_generic    65536  1 snd_hda_codec_conexant
kvm                  569344  1 kvm_amd
ledtrig_audio          16384  1 snd_hda_codec_generic
ath                    28672  3 ath9k_hw,ath9k,ath9k_common
snd_hda_codec_hdmi    49152  1
mac80211              643072  2 ath9k_hw,ath9k
snd_hda_intel          36864  0
snd_intel_dspcfg      24576  1 snd_hda_intel
soundwire_intel        24576  1 snd_intel_dspcfg
soundwire_generic_allocation    16384  1 soundwire_intel
soundwire_cadence      20480  1 soundwire_intel
snd_hda_codec          94208  4 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_codec_generic
evdev                  20480  8
snd_hda_core          61440  5 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic
irqbypass              16384  1 kvm
soundwire_bus          57344  3 soundwire_intel,soundwire_cadence,soundwire_generic_allocation
ttm                    69632  1 radeon
input_leds            16384  0
psmouse              118784  0
snd_hwdep              16384  1 snd_hda_codec
cfg80211              577536  5 wl,mac80211,ath9k,ath,ath9k_common
snd_soc_core          188416  1 soundwire_intel
drm_kms_helper        155648  1 radeon
serio_raw              16384  0
atl1c                  40960  0
cec                    40960  1 drm_kms_helper
rfkill                20480  3 acer_wmi,cfg80211
snd_compress          20480  1 snd_soc_core
snd_pcm_dmaengine      16384  1 snd_soc_core
drm                  372736  8 radeon,ttm,drm_kms_helper
ac97_bus              16384  1 snd_soc_core
libarc4                16384  1 mac80211
snd_pcm                81920  8 snd_compress,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_pcm_dmaengine,snd_hda_core,snd_hda_codec_hdmi,snd_soc_core
snd_timer              28672  1 snd_pcm
snd                    57344  10 snd_compress,snd_hda_intel,snd_hwdep,snd_hda_codec_conexant,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_soc_core,snd_pcm
soundcore              16384  1 snd
fb_sys_fops            16384  1 drm_kms_helper
syscopyarea            16384  1 drm_kms_helper
sysfillrect            16384  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
k10temp                16384  0
i2c_algo_bit          16384  1 radeon
sp5100_tco            16384  0
i2c_piix4              20480  0
rtc_cmos              20480  1
tiny_power_button      16384  0
acpi_cpufreq          24576  0
button                16384  0
ac                    16384  0
video                  53248  1 acer_wmi
wmi                    20480  2 wmi_bmof,acer_wmi
nls_utf8              16384  0
nls_cp437              16384  0
uas                    24576  0
ums_realtek            20480  0
usb_storage            53248  3 uas,ums_realtek
dm_crypt              36864  0
dm_mod                98304  1 dm_crypt
overlay                94208  1
battery                20480  0
fotg210_hcd            40960  0

And here is the output of LSPCI:

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 14h Processor Root Complex
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290]
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler HDMI Audio
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42)
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40)
00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0)
00:15.2 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 2)
00:15.3 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 3)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 0 (rev 43)
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 6
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 5
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 7
06:00.0 Ethernet controller: Qualcomm Atheros AR8152 v2.0 Fast Ethernet (rev c1)
07:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)

I will work on extracting and comparing the two ISO "linuxfs" images in a little while, have to go run some errands. Will post the update here. I'm thinking it may be a matter of swapping the Xorg files from one to the other, to make it function properly. In -MY SPECIFIC USE CASE- I have no issues with an .ISO file that results being larger than what fits on a standard CD, as these netbooks never came with CD drives and the flash drives I have are of about 16gb. So long as it works, it will fit. It may not align perfectly with the ideas of the project, but oh well. Big Grin  Resizing can be done later.

Thanks again!
Reply
#18
Sitting on a month-end data-limit right now, personally, so 23.1 core (to be apples-to-apples for RC7) can't happen here today. 

Took a (manual) look at package lists for 23.0 core (what I had here already) vs. RC7

- RADEON bits of kernel configs identical
- relevant X libs in core are all in RC7
- core contains 5 more firmware packages than RC7
     firmware-amd-graphics
     firmware-ast
     firmware-linux
     firmware-linux-nonfree
     firmware-samsung

firmware-linux is the top-level meta package dep on both -free (present already) and firmware-linux-nonfree (not included in RC7).  Top-level descriptions are no help and I haven't dug online for details. 

At the individual file level (/usr/lib/firmware):

- Something like 3200+ lines in firmware under core, ~2600 RC7 (forgot/bleery)

If memory serves, John has "hand-adjusted" certain firmware for other users but perhaps not installed the entire packages, so conclusions at the package level, on one hand, are an "easy" install+snapshot/remaster away.  OTOH, if that works, we still wouldn't know why.

Arguably more sane way to look at packages is to swipe bitjam's "spin" investigation method; for each version, run (redirect to different filenames):

dpkg-query -l | sed -n 's/^ii\s\+//p' > installed-packages.txt

then use the following commands to get lists of added and removed packages:

comm -23 <(sort f.old) <(sort f.new)
comm -13 <(sort f.old) <(sort f.new)

man comm Smile

->  The beauty of you using -core is that it can only be a kernel module and firmware (and radeon.ko and radeonfb.ko are present in core). 
->  You already custom-made an image with the firmware-amd-graphics contents, right, and that didn't work.  apt-cache show on that package might be the answer: 
                      replaces:  firmware-linux-nonfree
     which is what was in core but not in RC7.  Certainly it's large and that's likely among the reasons why it has been pruned. 

Here's some raw (unsorted) stuff for now.

--------------
Edit:  I missed the obvious again.  What happens if you just swipe all of /usr/lib/firmware from -core runit 23.2 and chuck it in your DSL re-brew?


Attached Files
.txt   inst_pkgs_rc7_.txt (Size: 141.59 KB / Downloads: 0)
.txt   rc7_fw_raw_dir_list.txt (Size: 44.57 KB / Downloads: 0)
.txt   pkg_list_1column_rc7.txt (Size: 16.75 KB / Downloads: 0)
.txt   core_23_0_fw_raw_dir_listing.txt (Size: 57.19 KB / Downloads: 0)
.txt   package_list_1column_23_0_core.txt (Size: 6.77 KB / Downloads: 0)
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)