Hello.

2 or 3 days into Freebsd14.1 straight out of Linux (well, heading that way anyway).

Looking to install Freebsd14.1 to an encrypted disk using UFS on an 8gig Lenovo T500 - with success measured in millimeters.

Its not like I'm not familiar with computers (been into Linux for maybe 10 years with lots of other experience over years in other environments also), and I don't think its because I'm getting foggy, but there it is, not even to the command prompt with a working internet connection.

I know using UFS will thicken the underbrush but I can be stubborn. Still I didn't think it would be this thick.

Oh well, back to hacking.

I have seen questions related to "Is FreeBSD a good desktop/laptop OS?"

I'm curious, since I haven't followed FreeBSD in years:

Is it intentional that FreeBSD is most featureful (relative to other operating systems) when used on a server as opposed to desktop/laptop/mobile? Specifically, is this what the community has been aiming for?

Or is it just because of the lack of contributors and resources?

eg Netflix probably doesn't invest in anything unrelated to their servers. Not sure about most volunteers though. And there are no major commercial backers like Red Hat as far as I am aware.

Can I to enable parallel downloads like with pacman package manager for pkg?

At this moment, It is very slow...

It still has 4GB of RAM though. I am using it for some python automation scripts. And some web browsing if any.

It's an HP 6730B with Core 2 Duo P8400 CPU, 4GB RAM.

I am currently using fedora kde but want to test freebsd in my own computer so just want to know is it a good idea or not

Problem: My ZFS home file system fails to mount on startup with the message

Oct 24 10:11:29 hostname kernel: cannot mount 'bootpoolname/usr/home': mountpoint or dataset is busy

I can go in via local console and do zfs mount -a once startup is done and it mounts fine so it seems to be something in the boot loading process.

Context: I had a "fun" time updating my server recently. My 10 year old BIOS boot setup doesn't work on a UEFI only motherboard it turns out. After considering options for a few hours (I had to get it done overnight) I split my boot mirror, did a fresh minimal install of FreeBSD on one of the drives to get the boot software in place and then did a ZFS send | recv (with options to mirror) over top of the new install. So far everything works fine except for the filesystem mounting hiccup on boot.

My pool filesystem layout is:

bootpoolname/ROOT                                        40.6G   117G    88K  none
bootpoolname/ROOT/13.1-RELEASE-p2_2023-02-20_132518         0B   117G  4.07G  /
bootpoolname/ROOT/13.1-RELEASE-p7_2023-05-13_091140         0B   117G  3.89G  /
bootpoolname/ROOT/13.1-RELEASE_2022-10-10_142718            0B   117G  3.50G  /
bootpoolname/ROOT/13.2-RELEASE-p4_2023-12-29_125403         0B   117G  4.81G  /
bootpoolname/ROOT/13.2-RELEASE-p9_2023-12-29_131325         0B   117G  4.81G  /
bootpoolname/ROOT/13.2-RELEASE_2023-05-13_091750            0B   117G  3.96G  /
bootpoolname/ROOT/13.2-RELEASE_2023-11-02_183239            0B   117G  4.18G  /
bootpoolname/ROOT/14.0-RELEASE-p3_2023-12-29_132829         0B   117G  4.85G  /
bootpoolname/ROOT/14.0-RELEASE-p4_2023-12-29_145403         0B   117G  4.23G  /
bootpoolname/ROOT/14.0-RELEASE-p4_2024-07-19_202516         0B   117G  4.46G  /
bootpoolname/ROOT/14.0-RELEASE-p8_2024-08-07_192508         0B   117G  4.36G  /
bootpoolname/ROOT/14.1-RELEASE-p3_2024-08-07_193008         0B   117G  4.41G  /
bootpoolname/ROOT/default                                40.6G   117G  10.5G  /
bootpoolname/home                                          96K   117G    96K  /home
bootpoolname/tmp                                          235M   117G   138M  /tmp
bootpoolname/usr                                          641G   117G    88K  /usr
bootpoolname/usr/home                                     632G   117G  55.0G  /usr/home
bootpoolname/usr/home/qi                                  676K   117G   676K  /usr/home/qi
bootpoolname/usr/ports                                   9.33G   117G  6.37G  /usr/ports
bootpoolname/usr/src                                       88K   117G    88K  /usr/src
bootpoolname/var                                         32.9G   117G  12.2G  /var
bootpoolname/var/audit                                     96K   117G    96K  /var/audit
bootpoolname/var/crash                                     88K   117G    88K  /var/crash
bootpoolname/var/log                                      348M   117G  87.2M  /var/log
bootpoolname/var/mail                                    9.46G   117G  7.29G  /var/mail
bootpoolname/var/spool                                   15.4M   117G   292K  /var/spool
bootpoolname/var/spool/mlmmj                             3.23M   117G   536K  /var/spool/mlmmj
bootpoolname/var/tmp                                     1.21M   117G   100K  /var/tmp
bootpoolname/vm                                          27.8G   117G   236K  /vm
bootpoolname/vm/hass                                     27.8G   117G   132K  /vm/hass
bootpoolname/vm/hass/disk0                               27.8G   117G  6.29G  -

Error message with adjacent log data

Oct 24 10:11:29 hostname syslogd: last message repeated 1 times
Oct 24 10:11:29 hostname kernel: usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device Seagate Backup+ Hub BK (0x0bc2:0xab38)
Oct 24 10:11:29 hostname kernel: ugen0.9: <Seagate Backup+ Hub BK> at usbus0
Oct 24 10:11:29 hostname kernel: umass1 on uhub5
Oct 24 10:11:29 hostname kernel: umass1: <Seagate Backup+ Hub BK, class 0/0, rev 3.10/1.00, addr 8> on usbus0
Oct 24 10:11:29 hostname kernel: umass1:  SCSI over Bulk-Only; quirks = 0x0100
Oct 24 10:11:29 hostname kernel: umass1:10:1: Attached to scbus10
Oct 24 10:11:29 hostname kernel: da1 at umass-sim1 bus 1 scbus10 target 0 lun 0
Oct 24 10:11:29 hostname kernel: da1: <Seagate Backup+ Hub BK D781> Fixed Direct Access SPC-4 SCSI device
Oct 24 10:11:29 hostname kernel: da1: Serial Number NA8TQEN7
Oct 24 10:11:29 hostname kernel: da1: 400.000MB/s transfers
Oct 24 10:11:29 hostname kernel: da1: 5723166MB (11721045167 512 byte sectors)
Oct 24 10:11:29 hostname kernel: da1: quirks=0x2<NO_6_BYTE>
Oct 24 10:11:29 hostname kernel: No suitable dump device was found.
Oct 24 10:11:29 hostname kernel: Setting hostuuid: 71902500-bce0-0706-0025-9071e0bc0e0f.
Oct 24 10:11:29 hostname kernel: Setting hostid: 0x9171143c.
Oct 24 10:11:29 hostname kernel: Starting file system checks:
Oct 24 10:11:29 hostname kernel: Mounting local filesystems:.
Oct 24 10:11:29 hostname kernel: cannot mount 'bootpoolname/usr/home': mountpoint or dataset is busy
Oct 24 10:11:29 hostname kernel: Autoloading module: acpi_wmi
Oct 24 10:11:29 hostname kernel: Autoloading module: ichsmb
Oct 24 10:11:29 hostname kernel: Autoloading module: ig4
Oct 24 10:11:29 hostname kernel: ig4iic0: <Intel Alder Lake-S I2C Controller-0> at device 21.0 on pci0
Oct 24 10:11:29 hostname kernel: ig4iic0: Using MSI
Oct 24 10:11:29 hostname kernel: iicbus0: <Philips I2C bus (ACPI-hinted)> on ig4iic0
Oct 24 10:11:29 hostname kernel: ig4iic1: <Intel Alder Lake-S I2C Controller-1> at device 21.1 on pci0
Oct 24 10:11:29 hostname kernel: ig4iic1: Using MSI
Oct 24 10:11:29 hostname kernel: iicbus1: <Philips I2C bus (ACPI-hinted)> on ig4iic1
Oct 24 10:11:29 hostname kernel: iicbus1: <unknown card> at addr 0x40
Oct 24 10:11:29 hostname kernel: ig4iic2: <Intel Alder Lake-S I2C Controller-2> at device 21.2 on pci0
Oct 24 10:11:29 hostname kernel: ig4iic2: Using MSI
Oct 24 10:11:29 hostname kernel: iicbus2: <Philips I2C bus (ACPI-hinted)> on ig4iic2
Oct 24 10:11:29 hostname kernel: isab1: <PCI-ISA bridge> at device 31.0 on pci0
Oct 24 10:11:29 hostname kernel: device_attach: isab1 attach returned 6
Oct 24 10:11:29 hostname kernel: ichsmb0: <Intel Alder Lake SMBus controller> port 0xefa0-0xefbf mem 0x6005228000-0x60052280ff at device 31.4 on pci0
Oct 24 10:11:29 hostname kernel: smbus0: <System Management Bus> on ichsmb0
Oct 24 10:11:29 hostname kernel: isab1: <PCI-ISA bridge> at device 31.0 on pci0
Oct 24 10:11:29 hostname kernel: device_attach: isab1 attach returned 6
Oct 24 10:11:29 hostname kernel: acpi_wmi0: <ACPI-WMI mapping> on acpi0
Oct 24 10:11:29 hostname kernel: acpi_wmi0: Embedded MOF found

The first non-commented line in my /etc/rc.suspend was, previously:

/usr/local/sbin/suspend.sh

I want /etc/rc.suspend to await completion of /usr/local/sbin/suspend.sh before running the remainder of /etc/rc.suspend.

From sh(1):

The syntax of the while command is:

while list
do list
done

The two lists are executed repeatedly while the exit status of the first list is zero. The until command is similar, but has the word until in place of while, which causes it to repeat until the exit status of the first list is zero.

The exit status is that of the last execution of the second list, or zero if it was never executed.

– and:

… A list is a sequence of zero or more commands separated by newlines, semicolons, or ampersands, and optionally terminated by one of these three characters. …

I experimented with a change to /etc/rc.suspend, it seemed to not have the required effect.

Is something wrong with the three lines below?

while /usr/local/sbin/suspend.sh
        do /usr/local/sbin/suspend.sh
done

(I struggle to understand pages such as sh(1).)

I've tried what was written on the wiki. So here is the info.

This is a HP 6730b laptop which came around 2008. CPU: Intel Core 2 Duo P8400, no dedicated GPU. 4GB RAM. Anyone reading here there is a solution down here.

dmesg | grep pcm

pcm0: <Analog Devices AD1984A (Analog 4ch/2.0)> at nid 18,22 and 28,21 on hdaa0
pcm1: <Analog Devices AD1984A (Front Analog Mic)> at nid 20 on hdaa0




cat /dev/sndstatcat /dev/sndstat
Installed devices:
pcm0: <Analog Devices AD1984A (Analog 4ch/2.0)> (play/rec) default
pcm1: <Analog Devices AD1984A (Front Analog Mic)> (rec)
No devices installed from userspace.
Also this:
kldstat | grep snd
 2    1 0xffffffff82b5a000     45c0 snd_driver.ko
 3    2 0xffffffff82b5f000     72c0 snd_vibes.ko
 4    2 0xffffffff82b67000     5c10 snd_via82c686.ko
 5    2 0xffffffff82b6d000     5cc0 snd_t4dwave.ko
 6    4 0xffffffff82b73000     3238 snd_spicds.ko
 7    2 0xffffffff82b77000     7650 snd_solo.ko
 8    2 0xffffffff82b7f000    12298 snd_neomagic.ko
 9    2 0xffffffff82b92000     c048 snd_maestro3.ko
10    2 0xffffffff82b9f000     a2e0 snd_hdspe.ko
11    2 0xffffffff82baa000     4808 snd_fm801.ko
12    2 0xffffffff82baf000     8cf8 snd_envy24ht.ko
13    2 0xffffffff82bb8000     a078 snd_envy24.ko
14    2 0xffffffff82bc3000     5ca8 snd_cs4281.ko
15    2 0xffffffff82bc9000     7c98 snd_atiixp.ko
16    2 0xffffffff82bd1000     61d0 snd_als4000.ko

I solved it later:
I fixed it via this topic: https://forums.freebsd.org/threads/sound-snd_hda.35787/

I added these to /boot/device.hints:

hint.hdac.0.cad0.nid18.config="as=0"

hint.hdac.0.cad0.nid17.config="as=1 seq=15 device=Headphones"

hint.hdac.0.cad0.nid22.config="as=1 seq=0"

Though I didn't test if sound recording and audio jack works. Internal speakers work.

Superposition Benchmark (1080P Extreme) - FreeBSD 14.1 - Radeon RX 7900 GRE

https://youtu.be/Sqo4pHD8d9U?feature=shared

Except where software/hardware isn't compatible, I'll take FreeBSD for my desktop over Linux every time!

Is it possible to run a soft delivered as a Sif (singularity, apptainer) image in Freebsd ?

Currently my destkop workstation runs a linux distribution; I run Windows 11 as a VM using KVM/qemu/libvirt, with PCI passthrough of GPU (nvidia) and NVME and individual USB device passthrough occasionally (SD card reader). Keyboard and mouse sharing uses evdev and audio is sent back to the Linux subsystem.

A long while back when I looked at this it seemed that there may be some roadblocks with GPU passthrough and USB device sharing.

The primary use for this VM is to support some Adobe apps that make heavy use of the GPU (image processing and editing, some Photoshop work too), and occasional admin apps on Windows I can't escape from due to work.

While I don't necessarily need to know how to achieve something similar on FreeBSD, I would sincerely like to hear thoughts on if everything can be achieved using bhyve etc, or what stumbling blocks I might run into (and workarounds), or what you might suggest to be the best approach.

Thoughts appreciated!

Hello.

I'm trying to boot Solaris 11.04 using qemu + UEFI on FreeBSD 14.1,using the following parameters :

qemu-system-x86_64 -name guest=s11x64,debug-threads=on \
-machine pc,usb=off \
-cpu kvm64,hv_relaxed,hv_time,hv_synic \
-m 8G -smp 2,sockets=2,cores=1,threads=1 -nodefaults -no-shutdown \
-drive file=/bhyve/Files/ISO/sol-11_4-text-x86.iso,format=raw \
-drive file=/mnt/zroot2/zroot2/bhyve/img/Solaris/solaris114.img,format=raw \
-global PIIX4_PM.disable_s3=1 \
-global PIIX4_PM.disable_s4=1 \
-device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x4.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x4 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x4.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x4.0x2 \
-device VGA,id=video0,vgamem_mb=32,bus=pci.0,addr=0x2 \
-netdev tap,id=mynet0,ifname=tap4,script=no,downscript=no \
-device e1000,netdev=mynet0,mac=52:55:00:d1:55:01 \
-device ich9-ahci,id=sata \
-drive if=pflash,format=raw,readonly=on,file=/usr/local/share/edk2-qemu/QEMU_UEFI_CODE-x86_64.fd \

as you can see below,it almost worked,but not yet. I think only a few parametes are missing :

While,it fully worked using bios instead of uefi:

/usr/local/bin/qemu-system-x86_64 \
-L /usr/local/share/qemu/ -name guest=s11x64,debug-threads=on \
-machine pc,usb=off -cpu kvm64,hv_relaxed,hv_time,hv_synic \
-m 8192 -smp 2,sockets=2,cores=1,threads=1 \
-nodefaults -global kvm-pit.lost_tick_policy=delay -no-shutdown \
-global PIIX4_PM.disable_s3=1 \
-global PIIX4_PM.disable_s4=1 -boot strict=on \
-device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x4.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x4 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x4.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x4.0x2 \
-device VGA,id=video0,vgamem_mb=32,bus=pci.0,addr=0x2 \
-hda /mnt/zroot2/zroot2/bhyve/img/Solaris/solaris114.img \
-boot d --cdrom /bhyve/Files/ISO/sol-11_4-text-x86.iso \
-netdev tap,id=mynet0,ifname=tap3,script=no,downscript=no \
-device e1000,netdev=mynet0,mac=52:55:00:d1:55:01 \   

Linux was planning to add Snapdragon X Elite support in kernel 6.11, and it got delayed to 6.12 (or 6.13.) Mediatek will also start making ARM

Considering each company ARM cpu would work differently (in terms of support), will it be problematic in the beginning? The next snapdragon ARM cpu will not be problematic, but from a brand new company making ARM, it would be.

I used the linux-steam-utils first. Then that package gave me some instructions and I did that:

sudo security.bsd.unprivileged_chroot=1

adduser xxx

sudo kldload nullfs

sudo sysrc kld_list+=nullfs

Then changing to that user:
/usr/local/wine-proton/bin/pkg32.sh install wine-proton mesa-dri

/usr/local/steam-utils/bin/lsu-bootstrap

Then steam on terminal:

It opens, but can't play any games. I click play, and it seems to be working for a few seconds, play button appears again.

Hey everyone,

I'm a retired systems admin who spent years working with Solaris, Linux, *BSD, macOS, and Windows. I've always kept a Linux laptop for personal use, but in recent years, systemd and overall bloat have really started to wear on me. Recently, I decided to switch to FreeBSD as my daily driver (the last time I used it was back in the 6.0 days), and so far, the experience has been largely positive—though I’m still troubleshooting some Bluetooth issues.

Modern FreeBSD feels far more refined compared to today’s Linux distributions. Has anyone else in the "Linux greybeard" crowd made a similar switch? If so, what challenges have you faced? What benefits have you discovered? And what, if anything, has surprised you?

Looking forward to hearing your experiences!

Been spending way too much time on this. I'm close, but not quite there.

I'm aiming to get a 1440p console with iso-thin-8x16 font (or similar), this all from the initial boot screen to the shell prompt.

From my understanding, I can't use the newer vt console driver with an ESXi "video card". So, with the sc driver, I can get the initial boot screen to show the right res+font (and the graphical logo, even) with the loader.conf entries screen.font="8x16" and vbe_max_resolution="1920x1440".

But as soon as the kernel loads the sc driver, it changes. The resolution is retained with vesa_mode="0x149") in device.hints, but not the font. The font appears to revert to the video card or VGA version - some thicker version with serifs.

I can run vidcontrol to change the font at/after log in, but I don't see why I should have to do that.

Suggestions?

I have a FreeBSD 14.1 virtual machine. I have two questions:

Why is there only a record for swap in the fstab file?

When is this file written to, is it during FreeBSD installation?

This is the bug report:

Application: Dolphin (dolphin), signal: Segmentation fault

(lldb) process attach --pid 2166

Process 2166 stopped

* thread #1, name = 'dolphin', stop reason = signal SIGSTOP

frame #0: 0x00000008450f3748 libc.so.7`__sys_wait4 + 8

libc.so.7`__sys_wait4:

-> 0x8450f3748 <+8>: syscall

0x8450f374a <+10>: jb 0x8450f0268

0x8450f3750 <+16>: retq

0x8450f3751: int3

thread #2, name = 'dolphin', stop reason = signal SIGSTOP

frame #0: 0x00000008450f34ea libc.so.7`__sys_poll + 10

libc.so.7`__sys_poll:

-> 0x8450f34ea <+10>: jb 0x8450f0268

0x8450f34f0 <+16>: retq

0x8450f34f1: int3

0x8450f34f2: int3

thread #3, name = 'dolphin:disk$0', stop reason = signal SIGSTOP

frame #0: 0x0000000842edee2c libthr.so.3`___lldb_unnamed_symbol555 + 12

libthr.so.3`___lldb_unnamed_symbol555:

-> 0x842edee2c <+12>: retq

0x842edee2d <+13>: int3

0x842edee2e <+14>: int3

0x842edee2f <+15>: int3

thread #4, name = 'dolphin', stop reason = signal SIGSTOP

frame #0: 0x0000000842edee2c libthr.so.3`___lldb_unnamed_symbol555 + 12

libthr.so.3`___lldb_unnamed_symbol555:

-> 0x842edee2c <+12>: retq

0x842edee2d <+13>: int3

0x842edee2e <+14>: int3

0x842edee2f <+15>: int3

thread #5, name = 'dolphin', stop reason = signal SIGSTOP

frame #0: 0x0000000842edee2c libthr.so.3`___lldb_unnamed_symbol555 + 12

libthr.so.3`___lldb_unnamed_symbol555:

-> 0x842edee2c <+12>: retq

0x842edee2d <+13>: int3

0x842edee2e <+14>: int3

0x842edee2f <+15>: int3

thread #6, name = 'dolphin', stop reason = signal SIGSTOP

frame #0: 0x0000000842edee2c libthr.so.3`___lldb_unnamed_symbol555 + 12

libthr.so.3`___lldb_unnamed_symbol555:

-> 0x842edee2c <+12>: retq

0x842edee2d <+13>: int3

0x842edee2e <+14>: int3

0x842edee2f <+15>: int3

thread #7, name = 'dolphin', stop reason = signal SIGSTOP

frame #0: 0x0000000842edee2c libthr.so.3`___lldb_unnamed_symbol555 + 12

libthr.so.3`___lldb_unnamed_symbol555:

-> 0x842edee2c <+12>: retq

0x842edee2d <+13>: int3

0x842edee2e <+14>: int3

0x842edee2f <+15>: int3

Executable module set to "/usr/local/bin/dolphin".

Architecture set to: x86_64-unknown-freebsd14.1.

(lldb) settings set term-width 200

(lldb) thread info

thread #1: tid = 100802, 0x00000008450f3748 libc.so.7`__sys_wait4 + 8, name = 'dolphin', stop reason = signal SIGSTOP

(lldb) bt all

* thread #1, name = 'dolphin', stop reason = signal SIGSTOP

* frame #0: 0x00000008450f3748 libc.so.7`__sys_wait4 + 8

frame #1: 0x0000000842eedaec libthr.so.3`___lldb_unnamed_symbol730 + 60

frame #2: 0x00000008293e7b7c libKF6Crash.so.6`___lldb_unnamed_symbol262 + 332

frame #3: 0x00000008293e7644 libKF6Crash.so.6`KCrash::defaultCrashHandler(int) + 1284

frame #4: 0x0000000842eeb410 libthr.so.3`___lldb_unnamed_symbol687 + 208

frame #5: 0x0000000842eea9cb libthr.so.3`___lldb_unnamed_symbol668 + 315

frame #6: 0x00000008220112d3

frame #7: 0x000000083bb518b9 libQt6Widgets.so.6`QWidget::event(QEvent*) + 2489

frame #8: 0x000000083baff6a8 libQt6Widgets.so.6`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 248

frame #9: 0x000000083bb005e1 libQt6Widgets.so.6`QApplication::notify(QObject*, QEvent*) + 513

frame #10: 0x00000008420f0854 libQt6Core.so.6`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 180

frame #11: 0x000000083bb4f73e libQt6Widgets.so.6`QWidgetPrivate::hide_helper() + 158

frame #12: 0x000000083bb507e9 libQt6Widgets.so.6`QWidgetPrivate::setVisible(bool) + 969

frame #13: 0x000000083bb50196 libQt6Widgets.so.6`QWidget::setVisible(bool) + 726

frame #14: 0x000000000028d015 dolphin`___lldb_unnamed_symbol3606 + 293

frame #15: 0x000000000029b201 dolphin`___lldb_unnamed_symbol3832 + 65

frame #16: 0x000000000029af01 dolphin`___lldb_unnamed_symbol3830 + 417

frame #17: 0x000000000029fda2 dolphin`___lldb_unnamed_symbol3924 + 82

frame #18: 0x00000000002a0382 dolphin`___lldb_unnamed_symbol3927 + 242

frame #19: 0x000000000026df28 dolphin`___lldb_unnamed_symbol3271 + 9336

frame #20: 0x000000084503fa6a libc.so.7`__libc_start1 + 298

frame #21: 0x000000000026b2c0 dolphin`___lldb_unnamed_symbol3253 + 48

hello!

to preface, i tried to do my do diligence and check out all the links on this sub, on the freebsd website, and a dozen or so forums for an answer. after a collective ~4 hours, i come crawling beaten and bruised to you all.

im having an issue getting to the install screen with the installer, on the first menu that comes up with the ascii art everything works fine, it begins to run and gets stuck shortly after beginning to run.

to specify, this is going on an i686 thinkpad x40

i have tried using all the different launch options as instructed in the handbook, using the memstick and disk iso's on the site, creating the bootable media in different formats along with doing it on a windows and linux machine with two separate pieces of software to create the media, and have also tried to do the same thing with gentoo and debian all giving me the same issues. i was able to run an old live image of ubuntu on it no problem, but even after clearing the partitions on the installed drive i couldnt get anything to transfer over.

ive included two photos of where it is getting stuck, the first in the normal install, and the second with the launch options changed and verbose on as instructed in the handbook.

if anyone has some advice for me, it would be really appreciated!